Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:6601 comp.os.386bsd.bugs:1742 comp.os.386bsd.misc:1405 Path: sserve!newshost.anu.edu.au!munnari.oz.au!ariel.ucs.unimelb.EDU.AU!ucsvc.ucs.unimelb.edu.au!lugb!latcs1!latcs5.lat.oz.au!wongm Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.bugs,comp.os.386bsd.misc Subject: Re: [FreeBSD-1.0R] Epsilon -> Release patches - problems Message-ID: <CG5nMw.Gnq@latcs1.lat.oz.au> From: wongm@latcs5.lat.oz.au (M.C. Wong) Date: Mon, 8 Nov 1993 04:11:19 GMT Sender: news@latcs1.lat.oz.au (news) References: <g89r4222.752427162@kudu> <2bc56h$h1p@pdq.coe.montana.edu> Organization: Comp Sci, La Trobe Uni, Australia Lines: 53 In article <2bc56h$h1p@pdq.coe.montana.edu> nate@bsd.coe.montana.edu (Nate Williams) writes: >In article <g89r4222.752427162@kudu>, >Geoff Rehmet <g89r4222@kudu.ru.ac.za> wrote: >>Hi, >> >>I have just been trying to install the Epsilon to Release patches >>for FreeBSD, and have found a few problems (me being braindead?). >> >>Anyhow, the instructions say to use patch -p1 -E - I think that >>should say patch -p2 -E (that's not really the problem). > >If you cd into /usr (and not /usr/src) as the instructions say, > patch -p1 -E will work. (I just tried it) > >>When I got the patches applied (or rather tried to) I got a lot >>of rejects in the sys tree. >> >>What mileage have other people had with these patches? >> > >I just took the entire EPSILON source release as it sits on freefall, >unpacked it, and then applied the EPSILON->RELEASE file to the resulting >sources which gave me NO rejects. I'm not sure if that's bad news, but >the patch should work on a virgin EPSILON source tree. > > > >Nate > >-- >nate@bsd.coe.montana.edu | Freely available *nix clones benefit everyone, >nate@cs.montana.edu | so let's not compete with each other, let's >work #: (406) 994-4836 | compete with folks who try to tie us down to >home #: (406) 586-0579 | proprietary O.S.'s (Microsloth) - Me Hi, Tried as Nate suggested, and it worked, but only with the existence of /usr/X386/include/X11/bitmaps, ie XFree installed properly, I think. Otherwise it will fail during 'make world' when compiling groff, complaining something about <X11/bitmaps/gray> not found. Otherwise, all of the rest goes well without any complaint. But after make world, I did build a new kernel before rebooting (as from the upgrade instruction) and when it reboots up, it still says FreeBSD-1.0e in the header before probing for devices. And I confirmed that by logging in and use : uname -a. Should it be something like FreeBSD-1.0R or 1.0r ? I will try rebuilding yet another kernel and see what uname will say this time. - wongm@latcs1.lat.oz.au (M.C Wong) -- - wongm@latcs1.lat.oz.au