At 11:34 AM 4/28/00 -0400, you wrote:
>As part of a research project at the university where I work, we need to
>have both FreeBSD and Linux installed on the same system in a dual-boot
>configuration (we'll be doing some network statistics gathering so we need
>at least two different tcp stacks to work with).
>
>The installation of this system was trivial, and with console access,
>everything is fine -- we're using System Commander as the initial boot
>loader, so everything works.
>
>The problem is that we need a way to reboot from Linux into FreeBSD
>remotely. In the past, with a similar configuration, I set up LILO to boot
>bsd with an entry like this:
>
> other=/dev/hda2
> label=bsd
>
>So that one could do a 'lilo -R bsd' before rebooting and have lilo boot
>FreeBSD when the system came up.
>
>Unfortunately, this isn't working on the current system: attempts to boot
>FreeBSD from lilo result in the following error:
>
> Loading bsd
> Boot error
>
>Oddly enough, we've run into another problem -- with both BSD disklabel
>support and UFS support compiled into the kernel, we ought to be able to
>see (and mount) BSD filesystems. However, the kernel doesn't appear to
>recognize any of the slices on the BSD partition.
>
>This shows up in dmesg:
>
> hda: hda1 hda2 hda3 < hda5 hda6 >
>
>hda1 is a DOS partition for System Commander, hda2 contains the BSD
>installation, and hda3 is an extended partition containing the Linux
>installation.
>
>This problem is especially frustrating because a similar configuration used
>to work just fine. Any help would be greatly appreciated.
>
>Thanks,
>
> -- Lars
>
>Lars Kellogg-Stedman <[EMAIL PROTECTED]> --> http://www.larsshack.org/
>
Just a shot in the dark - is System Commander "hiding" the BSD partitions
by changing the partition type code?
Mikkel
--
Do not meddle in the affairs of dragons,
for you are crunchy and taste good with ketchup.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
