Can someone tell me where in the startup sequence 'syslogd' is being started. I have been through everwhere I can think of like inittab, RC5, RCS, knoppix_autoconfig files, but I can't find what is calling syslogd daemon. I do not have the syslogd boot command option.

Also, as far as I can tell, if you default to runlevel 5 (ie. X gui) the actual call to 'startx' comes from ~/.bash_profile. However its not backgrounded, so you can't use the F1 console. If you change the line in .bash_profile to 'startx &' you can then CTRL-ALT-F1 to a usable console at the same time. Should this be the default? Its sometimes useful to drop to a console quickly to do something.

Can someone tell me where in the startup sequence 'syslogd' is being started. I have been through everwhere I can think of like inittab, RC5, RCS, knoppix_autoconfig files, but I can't find what is calling syslogd daemon. I do not have the syslogd boot command option.

Also, as far as I can tell, if you default to runlevel 5 (ie. X gui) the actual call to 'startx' comes from ~/.bash_profile. However its not backgrounded, so you can't use the F1 console. If you change the line in .bash_profile to 'startx &' you can then CTRL-ALT-F1 to a usable console at the same time. Should this be the default? Its sometimes useful to drop to a console quickly to do something.

The daemon is started at boot by init. I don't understand what you're trying to do with syslogd since it only logs system events to /var/log (unless you need to tweak it to log virtual machine/services output). It's a default daemon and doesn't require a boot code.

As far as run levels, most users are more comfortable in X than in console most of the time. Defaults are set for the comfort zone of most users, not for those who already know how to get (back) into console.

--------------"It felt kind of like having a pitbull terrier on my rear end."-- meo (copyright(c)2008, all rights reserved)

For DSL, it is disabled and requires a bootcode to save on memory/speed I would assume (and since general livecd desktop usage sessions don't really need logs)

However, I would also like to have the ctrl+alt+f1 capability by default, if there isn't any other technical problem about it. Shouldn't be a problem for those who don't use it, as they wouldn't know the key combo and therefore would not be affected.

Backgrounding X isn't an ideal thing to do as a default, in my opinion.On the other hand, having multiple virtual terminals available is standard on most distros, and is my preferred way to run the system, but DSL typically runs only one. You can change this by modifying /etc/inittab