Originally posted by balouba
View Post
Announcement
Collapse
No announcement yet.
Lennart Poettering Takes To Battling Systemd Myths
Collapse
X
-
-
Originally posted by Ericg View PostMajor distros who are using SysV?
Gentoo, Slackware, Debian (Im leaving RHEL + its clones out of this because RHEL7 uses systemd)
Major distros using Upstart?
Ubuntu, (+derivatives, but basically Ubuntu.)
Everyone else? systemd
Leave a comment:
-
Originally posted by Ericg View PostHe said he'd EVENTUALLY remove support for non-systemd. People always forget the "EVENTUALLY." Once people started freaking out he clarified that it was not a short-term goal by any means and would only happen once systemd was THE standard in the linux ecosystem and there WERE no competitors TO support.
Leave a comment:
-
Originally posted by cynyr View PostI could use the gentoo init file, except that it's not a sysV init file. It is not standalone and depends on other bits of software to work (namely runscript) and includes dependancy info in the init file. I don't really want to write init scrips just so that I can use a different init system, when the one I have works well and is fast enough. So, until everything is shipping with .system files I think I'll stick with the distro default, and a distro that doesn't use systemd.
Originally posted by cynyr View PostAs 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.
Leave a comment:
-
Originally posted by Ericg View PostSystemd can also parse init.d/rc.d scripts so theres that OR you could set it up where the .service file for your app actually just calls your custom written rc.d/init.d script. Make a script for mediatomb, drop it in /etc/init.d/ then just whip up a quick mediatomb.service file, drop it in /etc/systemd/system. have:
ExecStart=/etc/init.d/mediatomb start
ExecStop=/etc/init.d/mediatomb stop
this way you dont have to really mix and match init systems. a quick "systemctl enable mediatomb" will tell it to start on boot. and a "systemctl start mediatomb" will run ExecStart. Because its in /etc/systemd/system you dont have to worry about it ever being overwritten. The only problem would be if mediatomb did ever ship a default .service file, yours would automatically override it because they have the same name. So you might want to make it be "my-mediatomb.service" or something like that.
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.
Leave a comment:
-
Originally posted by nightmarex View PostWas 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.
Leave a comment:
-
Originally posted by nightmarex View PostWas 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.
Leave a comment:
-
eh meh and eh meh
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; 27 January 2013, 04:02 PM.
Leave a comment:
Leave a comment: