home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!charnel!sifon!clouso.crim.ca!IRO.UMontreal.CA!matrox!altitude!Nyongwa.CAM.ORG!steve
- From: steve@Nyongwa.CAM.ORG (Steve M. Robbins)
- Newsgroups: comp.os.linux
- Subject: Re: Some considerations when making a new Linux kernel
- Message-ID: <C1FEr7.91o@Nyongwa.CAM.ORG>
- Date: 25 Jan 93 20:11:31 GMT
- References: <1993Jan23.111158.26550@athena.mit.edu> <1993Jan24.005436.578@unislc.uucp> <C1DGHG.H3r@nmrdc1.nmrdc.nnmc.navy.mil>
- Organization: Radio Free Nyongwa -- public unix/usenet in Montreal, 284-6693
- Lines: 31
- X-Advert: Mail/News feeds available -- email postmaster for details.
-
- In article <C1DGHG.H3r@nmrdc1.nmrdc.nnmc.navy.mil> dsc3pzp@nmrdc1.nmrdc.nnmc.navy.mil (Philip Perucci) writes:
- >In article <1993Jan24.005436.578@unislc.uucp> erc@unislc.uucp (Ed Carp) writes:
- >>Mario Guerra (MGUERRA%UCRVM2.BITNET@mitvma.mit.edu) wrote:
- >>
- >>: One should be careful of checking some parameters in the general Makefile:
- >>:
- >>: [ ... ]
-
- >>Also, make sure that the lines in mm/memory.c that bomb processes that write
- >>to code space are commented out (look for SEGV) if you are running uucp or
- >>certain releases of getty_ps. I have to do that, because the latest version of
- >>getty_ps I can find will thrash if I don't.
- >>--
- >
- >Could you elaborate? I use getty_ps and have no problem. Still, if I can
- >improve the kernel for my configuration...
-
- It sounds like Ed hasn't set up his getty or init stuff correctly. There
- isn't any need to muck up the kernel for getty_ps, nor for taylor uucp that
- I have seen.
-
- I did compile uucp with -fwritable-strings, but that was out of laziness.
- I suspect fixing the uucp sources to behave isn't too much trouble.
-
- For getty, you don't even need writable strings. You do need to have a
- recent version (gettyps204) since the earlier ones had a stupid bug in them.
-
-
- --
- Steve Robbins -- steve@nyongwa.cam.org
- %SYSTEM-F-ANARCHISM, the operating system has been overthrown
-