Newsgroups: comp.os.minix
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.kei.com!newshost.marcam.com!usc!crash!cwr
From: cwr@crash.cts.com (Will Rose)
Subject: Re: bios vs ps HD drivers
Organization: CTS Network Services (CTSNET), San Diego, CA
Date: Sat, 8 Jul 1995 23:21:56 GMT
Message-ID: <DBF7Kn.JAI@crash.cts.com>
X-Newsreader: TIN [version 1.2 PL2]
References: <radugaDBAI1A.5oo@netcom.com> <DBApCw.4w1.0.-s@cs.vu.nl> <radugaDBB9A0.DJ4@netcom.com> <DBC3Lv.BE@crash.cts.com> <radugaDBDHsw.8wu@netcom.com>
Sender: news@crash.cts.com (news subsystem)
Nntp-Posting-Host: crash.cts.com
Lines: 49

raduga@netcom.com wrote:
: Will Rose (cwr@crash.cts.com) wrote:

: : I'd be inclined to forget subpartitions for now - I don't think
: : there's anything else on the disk to take up a partition, is there?

: : Just make a 1 or 2 MB hd1 to boot from, and use the rest for hd2.
: : Then use dd to dump the image of the boot floppy you are using to
: : hd1.

: so, set up a partition for /dev/hd1,  with part;
: use 'dd if=/dev/fd0 of=/dev/hd1' or somethihing
: (could you tell me what syntax would be apropriate? :)

If hd1 is big enough (bigger than the floppy) then that's
all you need: otherwise tack on an argument blocks=XXX,
where XXX is the size of the if filesystem *in 512K blocks*.
(I think the right answer is 1200, from the 600KB root file
system).

: *then* do installboot -m to fix the MBR, right?
: (if i did a dd, i wouldnt need installboot -d, would i?)

I don't trust my memory on installboot commands - I have to
look them up every time.  Basically, load the mbr, load the
minix bootloader, load the minix kernel file, then patch
everything.  As you say, if you move an image with dd a lot
of that is unecessary; certainly not loading the bootloader
and minix kernel.  I'm not sure if patching is necessary or
not - try it and see.  I think the need for the new mbr
depends on whether you are booting from a partition or sub-
partition - for hd1, it should be in place.

: running part on my *existing* fs, (having been previously created
: under the BIOS driver) it shows a table that looks okay.
: Meaning presumably, that its able to read the partition table 
: alright.

: Even if it cant figure out the filesystem....

: Might there be a problem, with trying to mount a RO fs,
: as RW, that would cause it not-to-recognise same?

I doubt it.  A filesystem is a filesystem (there are a couple of
versions, but all the ones you have are V2).

Will
cwr@crash.cts.com

