Karsten M. Self said:
> more consistent than Red Hat (which sticks X display manager startup into
> /etc/inittab for some strange reason), and provides generaly
the one thing I do like about this setup is init itself.. if X is hosed
and [gdkw]dm is in a loop, init will kill it automatically after a few
seconds("X is respawning too fast disabled for 5 minutes" or whatever).
whereas in debian it can be somewhat complicated for a newbie to fix
a system that is stuck in a [gdkw]dm loop, only way I know of is to
boot to single user mode(unless the person can login to the machine
via network). then disable the display manager.
besides that I agree, debian has some of the cleanest init setups
I've come accross in my journeys. I don't know about others but
I really don't like the redhat/suse/etc init scripts that source
that functions script, really makes it more difficult to understand
what is going on, I mean its a 440 line script(redhat 7.3)!
and of course I really don't like having to make my own init scripts
for services on freebsd, seems only a minority of 'ports' on
freebsd come with sample init scripts, and why they make their
init scripts so they don't work unless you call them from the
full path(/usr/local/etc/rc.d/script.sh) I wish I knew..
nate
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
