397 liens privés
Une doc assez complète sur systemd, puisque c'est l'avenir.
Voir aussi: https://wiki.archlinux.org/index.php/systemd
Bon tuto.
Ils ont juste zappé la partie systemd: http://uname.pingveno.net/blog/index.php/post/2015/05/23/Migrate-an-OpenVPN-configuration-to-Debian-8-%28Jessie%29-with-systemd
Le nom de l'unit va dépendre du nom du fichier de conf.
Par exemple, ce sera openvpn@server.service si on a /etc/openvpn/server.conf.
$ systemctl enable openvpn@server.service pour activer.
Mes règles uif (https://github.com/cajus/uif https://packages.debian.org/jessie/uif)
in+ s=all(4) p=openvpn
in+ s=all(6) p=openvpn
fw+ o=main i=vpnif
fw+ o=vpnif i=main
fw+ s=ovpnclients(4)
masq+ s=ovpnclients(4) o=main- openvpn = protocole (udp/1194)
- vpnif = interface openvpn tun0
- main = interface principale eth0
- ovpnclients = nom du réseau openvpn
Aujourd'hui... un tip systemd :D
Pour changer le répertoire par défaut des données docker (/var/lib/docker) avec systemd. Ne pas utiliser /etc/default/docker qui est réservé à sysvinit && upstart.
Faire plutôt ceci:
"""
mkdir /etc/systemd/system/docker.service.d
cat << EOF > /etc/systemd/system/docker.service.d/dir.conf
[Service]
ExecStart=
ExecStart=/usr/bin/docker daemon -H fd:// --graph /path/to/docker
EOF
systemctl daemon-reload
"""
doc officielle basée sur la même source: https://docs.docker.com/articles/systemd/
'"'"
Apart from the inevitable problems associated with being a jack-of-all-trades (and) master-of-none, the result will be the death of innovation for all functions absorbed into systemd as it is impossible to replace any one of them without replacing systemd entirely... which makes the job of developing improvements just too big a job.
"Right now, we have several alternatives to choose between for cron, ntp, logging, etc – each of them with different advantages and disadvantages. With systemd, it becomes a one-size-fits-all-or-else situation. If what it does doesn't suit you then tough luck, because you can't replace it without breaking your system.
"The second major problem with systemd is that it is becoming (or has become) mandatory - unnecessary dependencies on logind or systemd itself make it nearly impossible to avoid having systemd installed."
It remains to be seen which other functions systemd will seek to take over. As one wag put it, it might come to the point where one has just systemd and the kernel making up a LInux distribution.
"""
"""
We don't merge kernel code just because user space was written by a retarded monkey on crack.
‒ Linus Torvalds
"""
en réponse à Andy Lutomirski (https://lkml.org/lkml/2015/6/23/22) qui explique notamment que:
"""
The current state of uncertainty is problematic, I think. The kdbus
team is spending a lot of time making things compatible with kdbus,
and the latest systemd release makes kdbus userspace support
mandatory. The kernel people who would review it (myself included)
probably don't want to review new versions at a line-by-line level,
because we (myself included) either don't know whether there's any
point or don't think that it should be merged even if the
implementation were flawless.
"""
Les dernières versions de systemd dépendent de kdbus, donc ils mettent la pression sur Linus pour accepter kdbus dans linux.
Popcorn time. Stay tuned.
EDIT: pour rappel tout comme systemd, dbus est l'oeuvre de Lennart.
""'
One of the "features" of systemd is that it allows you to boot a system without needing a shell at all. This seems like such a senseless manoeuvre that I can't help but think of it as a knee-jerk reaction to the perception of Too Much Shell in sysv init scripts.
In exactly which universe is it reasonable to assume that you have a running D-Bus service (or kdbus) and a filesystem containing unit files, all the binaries they refer to, all the libraries they link against, and all the configuration files any of them reference, but that you lack that most ubiquitous of UNIX binaries, /bin/sh?
The use case often cited for this is managing services inside a container. I don't see why the init on my desktop needs to be complicated and restricted for the sake of a feature used by a minority of people with specialised use cases. By all means, write a tool for bootstrapping containers that doesn't rely on a shell, but don't shoehorn that into a one-size-fits-all init.
"""
Quoi de mieux pour commencer la semaine qu'une vidéo trollesque sur systemd?
systemd's haters gonna hate..
surtout utile sur desktop.
à lire
résumé, façon Ace Attorney, des discussions autour de l'init de debian qui auront mené au choix de systemd.
Tous les 'Cases': http://aceattorney.sparklin.org/V6_Test/search.php?search&criteria%5BsequenceId-is%5D=6512_en_Debian%20init%20case
/!\ nécessite flash* /!\
- patchez
la stabilité et la simplicité
c'est tout ce qu'on demande à un init.
c'est pourtant pas compliqué à comprendre.
mais visiblement, ça l'est plus pour ceux qui ne gèrent pas de serveurs en production.
https://framasphere.org/posts/273711
systemd va bien sur du desktop.
laissons juste le choix à ceux qui le souhaitent de ne pas l'utiliser.
"""
Package: systemd
Pin: origin *
Pin-Priority: -100
Package: systemd-sysv
Pin: origin *
Pin-Priority: -100
Package: libpam-systemd
Pin: origin *
Pin-Priority: -100
Package: systemd
Pin: origin
Pin-Priority: -100
"""
pour un serveur ça va.
le problème c'est pour les desktops car les paquets debian des composants desktop ont systemd en dépendance. va comprendre pourquoi... ce n'est pas le cas chez freebsd (qui n'a pas systemd).
alternative (fork): https://devuan.org
via http://www.linuxquestions.org/questions/linux-general-1/systemdont-how-to-avoid-installing-systemd-in-any-distro-4175517146/
je pose ça là.
Lennart Poettering, un des principaux auteurs de systemd, parle. Extrait:
"""
People have started multiple "petitions" on petition web sites, asking me to stop working (google for it). Recently, people started collecting Bitcoins to hire a hitman for me (this really happened!). Just the other day, some idiot posted a "song" on youtube, a creepy work, filled with expletives about me and suggestions of violence. People post websites about boycotting my projects, containing pretty personal attacks. On IRC, people /msg me sometimes, with nasty messages, and references to artwork in 4chan style. And there's more. A lot more.
"""
ça va loin, putain.
quelques réaction ici (parce que faut avoir un compte pour pouvoir lire les putains de commentaires sur g+): https://news.ycombinator.com/item?id=8414859
Selection d'un commentaire en particulier:
"""
I don't advocate bullying nor would I dare to justify such personal attacks. But the abusive content aside, he does deserve constructive criticism because, frankly, his contributions towards open source have brought far more problems than any of the solutions he looked to replace.
I could write a lengthy blog post about the unnecessary problems that PulseAudio and systemd have thrown up over the years (problems I'd never had an issue with in all the years of running Linux and other UNIX-like platforms), but those topics are done to death now. However my point is I think Lennart's been so carelessly cavalier in rolling out his code, and so unapologetic about the shitstorm he started that he's gotten a lot of peoples back up. Obviously this doesn't warrant the kind of bullying that he discussed in his post; however although he doesn't deserve such attacks, he has largely brought them on himself.
Maybe instead of fighting against the community as he tries to impose his own imperial vision of Linux, maybe if he worked with the community then the aggressive dickheads might leave him alone (or at least he'd receive more supporters from friendly folk - of who massively outnumber the aforementioned dickheads).
But just to be clear, as much as I think he might draw negative attention to himself, I think that any kind of personal abuse, let alone of the quantity that Lennart's been subject to, is absolutely disgusting and undeserved. Period.
"""
lire aussi: http://linuxfr.org/users/bluestorm/journaux/lennart-poettering-trouve-la-communaute-linux-desagreable
"""
This package emulates the systemd function that are required to run the systemd helpers without using the init service
"""
Si vous souhaitez comprendre comment fontionne systemd et pourquoi il fait tant débat (https://jeekajoo.eu/links/?SLhwfQ), regardez cette vidéo.
Vous pourrez ainsi vous faire votre propre idée.
voir aussi cet article de l'auteur de systemd (donc pour..): http://0pointer.de/blog/projects/the-biggest-myths.html