Lennart Poetterings opinion on building udev without having to build systemd:Besides that it would
probably be the first package where you can disable building the main
component.My recommendation for distros who want udev without the rest of systemd
is to build systemd normally and just pick the files you are interested
in from "make install".
But when I had destroyed my dbus installation, I chrooted into the installation and readed the log in the usual way with journalctl.
I don't think the networkamanger project has anything to do with Lennart Poettering.I had a bit of a reaction to LP's stuff at first too but nothing's perfect. Pulse had its problems, but they got fixed. NetworkManager wasn't perfect (still missing Bridging support though I think thats coming in the next version, or at least the groundwork is), and systemd once upon a time would fail to boot every once and awhile. Bugs were found. Bugs were fixed. Projects improved. I can very confidently say now that on all of my arch machines, with varying hardware, I have zero second-thoughts about installing systemd + Pulseaudio + Networkmanager + Avahi. They just ARE the standard to me now because I know they DO work.
Was I pissed when UDEV got forced to systemd, yeah, I got over it.
Do I like systemd? I guess, I am warming up to it.. still not super fond of the daemon setup however.
edit: by not being fond of the daemons I mean this crap "systemctl enable servicename.service" <- do I really need to type .service all the time? fuck.
Last edited by nightmarex; 01-27-2013 at 03:02 PM.
As for the journal thing, why would I want two logs on the same machine? Either make sure that I can recover the logs, from a mostly corrupt HDD as long as I can read at least some of the file, or let me not run journal at all, and pass everything to syslog-ng. chrooting and running the installed copy of journal is not good enough and not being able to get anything out on a partially corrupted file is also not good enough.
http://en.gentoo-wiki.com/wiki/Systemd#Services) has a mediatomb .service, for the record. And if mediatomb doesn't ship a .service file then thats mediatomb's fault, just as it would be if they didnt ship a sysV init or an upstart job