Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!gatech!howland.reston.ans.net!pipex!uunet!psinntp!isc-newsserver!ritvax.isc.rit.edu!DSF5454 From: dsf5454@ritvax.isc.rit.edu Subject: NetBSD's / file system full..??! Message-ID: <1993Sep28.232704.5576@ultb.isc.rit.edu> Sender: news@ultb.isc.rit.edu (USENET News System) Nntp-Posting-Host: vaxa.isc.rit.edu Reply-To: dsf5454@ritvax.isc.rit.edu Organization: Rochester Institute of Technology Date: Tue, 28 Sep 1993 23:27:04 GMT Lines: 28 When my roomie's trying to install NetBSD-0.9 on his 486/33, we give it parameters such as: ESDI disk, y for auto remap, 1209 disk cylinders, 9 tracks, 36 sectors, 391716 (entire disk) for NetBSD, 39172 (aprx. 20 MB) for root, 39172 for swap, 313372 for the usable portion of NetBSD. Well...it goes to mount wd0a as the root partition on /mnt, wd0e as usable partition on /mnt/tmp, and proceeds to try to copy files over. But it eventually crashes to the # prompt when it says: uid 0 on /: file system full /: write failed, file system is full Memory fault mkdir: /mnt/tmp: file exists ./install: cannot create etc/fstab: directory nonexistent What is / file system full supposed to mean?! :-) Any ideas, help, suggestions, hints, tips, pointers would GREATLY be appreciated!! We really like it now as opposed to the last time we tried 386BSD!! So that's why we're hopeful that somebody will be able to help us out. And yes, we did read ALL the pertinent documentations related to this whole thing, too. :-) Direct any e-mails to dsf5454@ritvax.isc.rit.edu