Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:4964 comp.os.386bsd.misc:940 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!saimiri.primate.wisc.edu!caen!usenet.coe.montana.edu!bsd.coe.montana.edu!nate From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc Subject: Re: Can I delete the /patch directory ? Date: 10 Sep 1993 16:45:32 GMT Organization: Montana Stateu University, Bozeman MT Lines: 39 Message-ID: <26qavc$3q2@pdq.coe.montana.edu> References: <CD4E5C.3Jw@latcs1.lat.oz.au> NNTP-Posting-Host: bsd.coe.montana.edu In article <CD4E5C.3Jw@latcs1.lat.oz.au>, M.C. Wong <wongm@ipc2.lat.oz.au> wrote: >Hi, > With FreeBSD out now , it seems as if patchkit way of upgrading/fixing bugs >in the 386bsd 0.1 days is ended ! I wonder can I now safely get rid of all >of the stuff under dir /patch ? How about those patched source files ? > > I need to make room for other use, and the first thing I can think of is >to rid the pk-0.2.4! If you are running FreeBSD, you can remove /patch and everything below it. :-) > currently I have 386bsd-0.1 + pk0.2.4 on IDE, and I plan to get a SCSI-2 > disk, I plan to installed FreeBSD boot blocks on IDE, and transfer /usr > and most other useful (not 386bsd or kernel related stuff) to new SCSI > disk. I plan to disklabel the new disk with 386bsd first, and do the > transfer (cpio etc) with 386bsd from old /usr to new partition on new > disk. If I reinstalled FreeBSD before doing so, the stuff I want might > get wiped out! Having done the transfer, I will installed the bootable + > etc on IDE HDD, so will the FreeBSD recognize the new disk/ufs/ > partitions created using disklabel with 386bsd-0.1 ? Of course. FreeBSD is just 386BSD with some real support (and fixes that you can actually touch and feel, not just promises that haven't yet been fulfilled). The only big difference between running 386BSD binaries on FreeBSD binaries is that FreeBSD binaries require a new password database format because the database support in 386BSD is badly broken, and was replaced by a non-compatabile version which actually works. Nate -- nate@bsd.coe.montana.edu | In the middle of it ........ again. nate@cs.montana.edu | Running/supporting one of many freely available work #: (406) 994-4836 | Operating Systems for [34]86 machines. home #: (406) 586-0579 | (based on Net/2, name changes all the time :-)