Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!uunet!mcsun!sunic!chalmers.se!dtek.chalmers.se!dxper From: dxper@dtek.chalmers.se (Per Anders Olausson) Newsgroups: comp.unix.bsd Subject: Re: 386BSD 0.1 fixit.fs Message-ID: <12823@chalmers.se> Date: 18 Jul 92 22:40:15 GMT References: <1992Jul18.164414.3181@Urmel.Informatik.RWTH-Aachen.DE> Sender: news@chalmers.se Organization: Chalmers University of Technology, Gothenburg Sweden Lines: 73 kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) writes: >There is dist.fs which is the bootable distribution (Is it equal to >"Tiny386BSD? The INSTALL.NOTE is not very clear about that) Yes it is. >There is also fixit.fs (which is bootable, but does *not* contain the >install script) >Assuming that fixit.fs "fixes" something I wonder how I can use it. The fixit floppy is there for stupid people like me who doesn't like having only one partition on the whole harddisk. If you don't you have to use the utilities on the fixit disk in order to manually partition it. Btw, when I used V0.0 it was quite a feat to get stick on a proper disklabel but in this version things seems to have become more relaxed when it comes to bad144 error msgs. The worst thing about the install programs idea of partitioning is that it sets block size to 8K/1K so on a tight system you'll waste precious memory. And what about swap? Now doing this isn't so difficult since all you have to do is: *) get the floppy in writeable mode (mount -u /dev/fd0a /) *) cd /etc *) add an entry to the disktab file (vi disktab). Look at one of the present ones as you do this and ensure that you leave 126 sectors + one track unused at the end of the disk *) put the label on the disk (disklabel -r -w wd0 your_entry_name) *) zero out the bad144 data (bad144 wd0 0) *) initialise the new filesystems (eg. newfs wd0a if you have a partition a) This is all you have to do, but please note that making a disktab entry for the first time can be a real pain to the brain! Unfortunately there is no simple way of transfering the tiny386bsd disk (ie. dist.fs...) but perhaps someone could write a little shell script to do it or perhaps if someone updated install so that it could be used. (no, I did *not* figure out how to do it with install or any other stuff on that damn disk so I grabbed tar and used the V0.0 way and then I manually unpacked the baseutils.cpio.Z stuff! *Don't* ask how I grabbed the tar image. B-() By the way. 10Mb of isode and a couple of megs with games. (on the etc01.*) That's what I call a bad joke! B-( pao PS! Am I the only one who had to cat all the etc01 files together by hand because cat doesn't close files after it has read them. (remember the old 64 open file limit?) What I did was: for i in etc01.0 etc01.1 etc... do cat $i? >$i rm $i? done # DO NOT HIT CTRL-Z WHILE THIS RUNNING. YOU'LL REGRET IT! GUESS WHO DID? @!#$@ cat etc01.? >etc01 cat etc01 | compress -d | cpio -iadm -- -------------------------------Andrew Olausson-------------------------------- --------------------------Unemployed Unix Specialist-------------------------- ------------------------------pao@cd.chalmers.se------------------------------ -------------------------------pa-ola@proxxi.se-------------------------------