> At 8:01 PM +0200 8/3/99, Robert Nordier wrote:
>
> > > - If I select 3.2 at the PowerBoot menu, it comes up
> > > with two messages about "invalid partition", [...]
> > > It seems to want to boot 'da(0,a)/kernel', but if I
> > > type in 'da(0,e)/kernel', then it boots up fine.
> >
> >The problem here is a missing `a' partition. Seems like your
> >first partition on that slice is `e'. There's a one-line
> >patch to boot2 to get this working, but the standard version
> >only autoboots from the `a' partition.
I have my main machine setup to boot 3 different operating systems all
on one harddisk. My disk is paritioned into 4 fdisk partitions, as follows:
1: Win98 (ugh, but I need to have it to play games :-) (bootable)
2: extended dos partition (non-bootable)
3: FreeBSD 3.2-stable (bootable)
4: FreeBSD 4.0 -current (bootable)
Here is my file system layout when running 4.0:
/dev/wd0s4a on / (local, soft-updates, writes: sync 16 async 14249)
/dev/wd0s3a on /root32 (local, writes: sync 2 async 44)
/dev/wd0s3e on /root32/usr (local, writes: sync 2 async 7099)
/dev/wd0s4f on /usr (local, soft-updates, writes: sync 2 async 8148)
/dev/wd0s4h on /shared (local, soft-updates, writes: sync 1963 async 263656)
/dev/wd0s3f on /root32/var (local, writes: sync 2 async 40)
/dev/wd0s4g on /var (local, soft-updates, writes: sync 4604 async 69441)
(along with a wd0s4b swap partition, which is shared between both
FreeBSD versions)
When I first tried this, I couldn't boot the 4.0 version because
the 4.0 root device was named wd0s4e by my initial 3.2 sysinstall. I had
to run disklabel and change the partition name to wd0s4a. After doing
that, both versions would boot no problem. I just hit F3 for 3.2-stable,
or F4 for 4.0-current.
All of my boot blocks were orignally written out with 3.2-stable,
but I've since re-written them with 4.0-current boot blocks.
-Mike
--
Mike Pritchard
[EMAIL PROTECTED] or [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
