I have being in that environment before, so don't let us break the rules. Norm wrote: > No. It's the only Linux computer in the airplane though I suppose I could > bring in a portable after clearing it with security. I'll have to think > about the possibility of that. There's a pure MS-DOS computer and a Windows > 95 box but I'm not sure if the Win95 PC even has a NIC. WHOA. We've got > several Silicon Graphics IRIX computers in there. I'll see if I can work a > telnet connection (even a temporary one) from the Indigo2 -- assuming we > don't tell security about it until after we've done it. [They really hate > the "I've done the following:..." messages but there's not much they can do > about it except slap my hand and since I'm overdue for retirement anyway > ...] > > Thanks for the suggestion. > > Norm > > ----- Original Message ----- > From: "Bukie Mabayoje" <bukiemab@xxxxxxx> > To: <xfree86@xxxxxxxxxxx> > Sent: Friday, March 11, 2005 3:40 PM > Subject: Re: Partially successful installation/startup > > > Can you telnet to the system? > > > > Norm wrote: > > > > > You've already got the Configuration File which was posted before with > just > > > the recommended change of the FontServer socket. I'm not sure how to > get a > > > log file if I have to cycle power to regain control of the system > because > > > the process is cycling and uninterruptible. I suppose I could try to > write > > > a Q&D shell script to sleep for a few seconds and then perform a > shutdown. > > > Do you think this would work? > > > > > > Norm > > > ----- Original Message ----- > > > From: "Bukie Mabayoje" <bukiemab@xxxxxxx> > > > To: <xfree86@xxxxxxxxxxx> > > > Sent: Friday, March 11, 2005 3:19 PM > > > Subject: Re: Partially successful installation/startup > > > > > > > Post the log and configuration file when you try to start X > automatically. > > > > > > > > Norm wrote: > > > > > > > > > ----- Original Message ----- > > > > > From: "Bukie Mabayoje" <bukiemab@xxxxxxx> > > > > > To: <xfree86@xxxxxxxxxxx> > > > > > Sent: Wednesday, March 09, 2005 7:31 PM > > > > > Subject: Re: Partially successful installation/startup > > > > > > > > > > > You need to update the Font Server Port # in your configuration > file. > > > > > > Change the line FontPath "unix/:-1" to FontPath > "unix/:7100" > > > > > > > > > > > > Norm wrote: > > > > > > > > > > > > > Sorry for the delay but I don't get on the 737 very often any > more. > > > > > > > > > > > > > > Anyway, while I was watching it boot today, I noticed that > during > > > the > > > > > boot > > > > > > > process it said that the startup of the Font Server failed. > That's > > > > > probably > > > > > > > why we can't execute 'init 5' to start X Window. Since we can > > > execute > > > > > the > > > > > > > 'startx' script, everything we need is obviously there, but, I'd > > > guess, > > > > > not > > > > > > > in the right places. What do I need to do to get the Font > Server to > > > > > start > > > > > > > up during bootup? > > > > > > > > > > > > Go into /etc/init.d directory and search for xfs. > > > > > > Login as root > > > > > > do ./xfs start > > > > > > Did it start or failed? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Okay -- quick summary: > > > > > 1. Linux based on RedHat 6.2 with 2.2.18 kernel with Real-Time > Linux > > > v3.1 > > > > > patches applied. > > > > > 2. Pentium III on a Single Board Computer with on-board Chips & > > > Technology > > > > > (C&T) 69000 AGP with 2 MB video memory. > > > > > 3. If we try to execute 'init 5' the system goes into a endless -- > and > > > > > uninterruptible -- cycling of trying and failing to start the X > Window > > > > > system > > > > > 4. If, at a text shell prompt, we execute 'startx' the X Window > system > > > > > starts perfectly. > > > > > 5. During bootup one of the messages is that the X-Font Server > failed > > > to > > > > > start. > > > > > > > > > > A. I changed the FontPath line in the XF86Config file as directed > > > above. > > > > > B.. I executed '/etc/rc.d/init.d/xfs start' and it (apparently) > > > > > succeeds. > > > > > BUT .. trying to execute 'startx' afterwards fails with the > > > message > > > > > [not exact wording] > > > > > "...can't find font: fixed ..." > > > > > and the system starts the endless > trying-to-start-and-failing > > > loop. > > > > > It was necessary to change the FontServer back to -1 in > order to > > > > > have 'startx' work. > > > > > AND 'init 5' fails as before. > > > > > > > > > > Clearly we can manually execute 'startx' after logging into a text > shell > > > > > each time but we'd really like to get it to happen automatically on > > > bootup. > > > > > Any suggestions? > > > > > > > > > > Norm > > > > > > > > > > _______________________________________________ > > > > > XFree86 mailing list > > > > > XFree86@xxxxxxxxxxx > > > > > http://XFree86.Org/mailman/listinfo/xfree86 > > > > _______________________________________________ > > > > XFree86 mailing list > > > > XFree86@xxxxxxxxxxx > > > > http://XFree86.Org/mailman/listinfo/xfree86 > > > > > > _______________________________________________ > > > XFree86 mailing list > > > XFree86@xxxxxxxxxxx > > > http://XFree86.Org/mailman/listinfo/xfree86 > > _______________________________________________ > > XFree86 mailing list > > XFree86@xxxxxxxxxxx > > http://XFree86.Org/mailman/listinfo/xfree86 > > _______________________________________________ > XFree86 mailing list > XFree86@xxxxxxxxxxx > http://XFree86.Org/mailman/listinfo/xfree86 _______________________________________________ XFree86 mailing list XFree86@xxxxxxxxxxx http://XFree86.Org/mailman/listinfo/xfree86
