On Thu, 2005-06-30 at 15:38 +1000, Peter Hardy wrote: > On Thu, Jun 30, 2005 at 03:15:49PM +1000, Ken Caldwell wrote: > > The lines in /etc/inittab that would normally start a getty are in this > > distribution replaced by, for example, > > > > 1:12345:respawn:/bin/bash -login >/dev/tty1 2>&1 </dev/tty1 > > *snip* > > > In /home/dsl there exist, among others, the following > > files: .bash_profile .xinitrc and .xserverrc > > > > I can see how X starts once the user is logged in as dsl but cannot see > > how this is managed. > > > > If you do ctrl+alt+F1 you can see the tail end of the boot up process > > the last five lines showing: > > > > INIT: Entering runlevel: 5 > > su(pam_unix)[375]: session opened for user dsl by (uid=0) > > Using Xvesa default 1024x768x32 -mouse "/dev/psaux",5 mouse > > xauth: creating new authority file /home/dsl/.Xauthority > > xauth: creating new authority file /home/dsl/.Xauthority > > *snip again* > > > My question really boils down to "what causes the su to dsl?" I cannot > > find a reference to su in any of the boot scripts. > > Can anyone shed any light on this? > > What follows is pure speculation and brainstorming; I've never used > dsl.. > > You've got bash being run as a login shell from init (and owned by the > root user). It's launching su to the dsl user. > > Have you checked root's bash config files? Errr. probably .bash_profile > for a login shell. Possibly also .bashrc. And of course the global ones > in /etc . Bingo! There was a .bash_profile hiding in / (I'm not in the habit of doing ls -A on /) many thanks, Ken
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
