home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!news!brtmac
- From: brtmac@maverick.ksu.ksu.edu (Brett McCoy)
- Newsgroups: comp.unix.bsd
- Subject: Re: More on X386 1.2E 1.0.1 startup problems
- Date: 8 Sep 92 13:49:30
- Organization: Kansas State University
- Lines: 27
- Message-ID: <BRTMAC.92Sep8134930@maverick.ksu.ksu.edu>
- References: <1992Sep8.045813.11493@noose.ecn.purdue.edu>
- NNTP-Posting-Host: maverick.ksu.ksu.edu
- In-reply-to: tgt@neon.ecn.purdue.edu's message of Tue, 8 Sep 1992 04:58:13 GMT
-
- In article <1992Sep8.045813.11493@noose.ecn.purdue.edu> tgt@neon.ecn.purdue.edu (Conan the Librarian) writes:
-
- >Regarding my being unable to startup X386 1.2E on my system
- >(I get a blank screen and then nothing...apparently xinit is
- >gagging) someone suggested that the 386bsd kernel packed with
- >the X386 1.2E 1.0.1 binaries on agate.berkeley.edu doesn't work.
- >Is this true? If so, could someone either A) tell me where
- >I can get a kernel which will work with X386 or B) tell me
- >what the kernel problem is and where the patches are, so I
- >can attempt a kernel remake myself?
-
- I could not get that kernel to work. Patching the sources and
- building my own got me a working kernel. The patches are in with
- the X distribution.
-
- >Lastly, is anyone going to place the X386 1.2E 1.0.2 binaries
- >in an archive, like on agate? I keep hearing people say
- >"check the pub/incoming/X386 directory" but boys, there's
- >nothing there!
-
- Do an anon ftp to agate, then do a cd pub/incoming/X386. Then
- do a 'dir' and walla, there it is. The incoming directory does
- not have read permissions for the world so you have to know what
- you are looking for. It's impossible to get a listing of the
- files that are there.
-
- ++Brett;
-