Date: Mon, 27 Nov 95 9:10:46 CST From: Joe Greco <jgreco@solaria.sol.net> To: joerg_wunsch@uriah.heep.sax.de Cc: maral@webnet.com.au, hackers@FreeBSD.ORG Subject: Re: Argh, lost console :-( Message-ID: <199511271510.JAA28202@solaria.sol.net> In-Reply-To: <199511270854.JAA04879@uriah.heep.sax.de> from "J Wunsch" at Nov 27, 95 09:54:47 am
next in thread | previous in thread | raw e-mail | index | archive | help
> As Peter Marelas wrote: > > > > > What happened: I put xdm as the last entry in /etc/rc.local on a 486DX/33 > > > with 32MB RAM, Fahrenheit 1280 VGA card, running 2.0.5R. > > Put a "sleep 2" (or some other activity) behind, in order to allow xdm > to properly daemonize itself. Otherwise, the rc shell will exit > before xdm changed its session, and consequently kill xdm halfways > while launching the Xserver. That's not the problem (I actually do an "fsck -y /dev/homepartition" after launching xdm which takes longer than a few seconds)... xdm is running just dandy and X comes up "fine" - but the kbd isn't there. Now if only there was a way to do the equivalent of "fsck -p /dev/somepartition" :-) > > The README in XF86312 says to start xdm from a tty in /etc/ttys > > > > The easiest way to automatically start the display manager on boot is > > to add a line in /etc/ttys to start it on one of the unoccupied > > virtual terminals: > > > > > > ttyv4 "/usr/X11R6/bin/xdm -nodaemon" xterm on secure > > I wholeheartedly disagree with this method. It's a crock. Ditto. I don't like being forced to launch it and hate having to edit a file and send signals to init rather than just kill the little pig to disable it. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199511271510.JAA28202>