Date: Sat, 7 Aug 2010 21:47:37 +0200 From: Polytropon <freebsd@edvax.de> To: freebsd-questions@freebsd.org Subject: Re: ANNOUNCE: Custom 64bit FreeBSD 8.1-RELEASE with XFCE packages released Message-ID: <20100807214737.75ebc397.freebsd@edvax.de> In-Reply-To: <AANLkTi=YoER4nBaq2noap_pFbhcLD8BLYbRxzBpcK5JP@mail.gmail.com> References: <4C566252.6010605@otenet.gr> <4C5CFEE0.5060000@speakeasy.net> <AANLkTin1vfjfM98gmc2P5a-hZ78q_PDChyFTbGqTbJA_@mail.gmail.com> <201008071157.00180.eliaschr@cha.forthnet.gr> <AANLkTi=YoER4nBaq2noap_pFbhcLD8BLYbRxzBpcK5JP@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Just an addition: My solution works in the same way (modification of /etc/ttys and /etc/gettytab), but I avoid this step: On Sat, 7 Aug 2010 04:49:00 -0500, Antonio Olivares <olivares14031@gmail.com> wrote: > Then created file /etc/rc.local > with > su - user_to_be_logged_in -c startx In fact, I use the autologin-user's ~/.login script (which is executed after login) to contain a line to check for X's lock file and then run startx. This gives the possibility to the specific user to NOT have to need root permissions to change the behaviour after autologin. The simple line in ~/.login is this one: [ -f /tmp/.X0-lock ] && startx Depending on requirements, this can be seen as an advantage or disadvantage (usually in considerations about security); it's also possible to create a "loop" that an accidental logout won't drop the user to "DOS". :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100807214737.75ebc397.freebsd>