Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!network.ucsd.edu!pacbell.com!decwrl!parc!biosci!agate!howland.reston.ans.net!noc.near.net!uunet!news.smith.edu!sophia.smith.edu!jfieber From: jfieber@sophia.smith.edu (J Fieber) Newsgroups: comp.os.386bsd.development Subject: Re: Future Directions for BSD (was Re: What happened to these projects ?) Message-ID: <1993Apr28.155210.22315@sophia.smith.edu> Date: 28 Apr 93 15:52:10 GMT References: <hastyC62oIE.BFH@netcom.com> <1rk5v8INN6vp@no-names.nerdc.ufl.edu> <1993Apr28.135512.4010@alw.nih.gov> Sender: root@sophia.smith.edu (Operator) Organization: Smith College Lines: 26 In article <1993Apr28.135512.4010@alw.nih.gov> crtb@helix.nih.gov (Chuck Bacon) writes: >So I catted 10 chunks at a time, and built the one great etc01.cpio.Z >file. Tried to mv the etc01.?? files out of /tmp, but mv complained >that the target was a directory!! What the hell is going on, anyway? >OF COURSE it's a directory! So I had to use foreach f (etc01.??) to >mv the files one by one. > >I thought 386bsd derived substantially from bsd4.4, and that this was >such a superior implementation. Is 386bsd really such a student project? This is because the programs, such as mv, on the dist.fs floppy are tiny versions of the "real" programs and thus have very limited functionality. Once you get the system installed you get the real ones. The mv on the floppy is about 3k whereas the regular mv is about 30k. This was done to cram everything onto one floppy. A solution that is generally regarded as better is to have a 2 floppy boot; one disk with the kernel which leaves a lot more space for useful stuff on the other floppy that becomes the root filesystem. -john -- === jfieber@sophia.smith.edu ================================================ ======================================= Come up and be a kite! --K. Bush ===