Craig Sanders <cas@taz.net.au> writes:
On Tue, Nov 27, 2012 at 10:33:31AM +1100, Trent W. Buck wrote:
trentbuck@gmail.com (Trent W. Buck) writes:
Compared to Debian 6, or compared to what you remember booting being like five years ago?
Apropos, this just appeared on LWN: http://web.dodds.net/~vorlon/wiki/blog/Upstart_in_Debian/
wow. that's amazing!
compared to sysvinit+startpar, systemd improves boot time by 1.1 seconds, and upstart improves it by 0.62 seconds.
To be fair, that is a VM with a minimal install. I bet if you installed NetworkManager and pulseaudio, systemd's speed gain would jump to as much as five seconds ;-)
and just remember kids, shell scripts are bad. lennart pottering says so...and what unix really needs is yet another minimalist ^^^^ BZZT, wrong. Lennart cares *Linux* not unix. Debian kfbsd and Debian GNU can FOAD as far as he's concerned.
domain-specific configuration language that requires you to learn its peculiarities and limitations.
Personally I liked minit/cinit's approach -- "config files? What is that?" -- you had something like /etc/minit/smbd/exec -> /usr/sbin/smbd /etc/minit/smbd/args /etc/minit/smbd/depends/nmbd where "args" is newline-delimited list of arguments. You could just about use xattrs, and avoid ever open a file at all. Oh, and if you can't do it in a one-liner, your exec symlink is to a sh shebang script (or whatever the hell else you want). Allegedly it was inspired by qmail's config format -- I can't comment on that. It certainly makes sense to me to avoid heavyweight parsing when your init's target environment is ucLinux-level embedded systems (as at about eight years ago).
also, unix sucks and linux should be made to work more like mac or nextstep, because grotesquely long variable and setting names
XML-based config files (written in a binary serialization, so you can't view or edit them with TECO even if you wanted to).