-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Vittorio De Martino wrote:
| # fdisk -B -b /boot/boot0 ad0
| fdisk: cannot open disk /dev/ad0: No such file or directory
|
| and with
|
| # fdisk -B -b /boot/boot0 ad1
| fdisk: cannot open disk /dev/ad1: No such file or directory
I
[EMAIL PROTECTED] writes:
>>From dmesg:
> ad0: 9541MB [19386/16/63] at ata0-master UDMA33
I think you just said that
> vicbsd root# fdisk /dev/ad0
> vicbsd root# bsdlabel /dev/ad0s1
work OK, but that your problem (from a prior msg) is:
>>># fdisk -B -b /boot/boot0 ad0
>>>fdisk: cannot open di
gt;To: Vittorio De Martino <[EMAIL PROTECTED]>
>From: Glenn Dawson <[EMAIL PROTECTED]>
>Subject: Re: Problems with booting & MBR
>
>
>At 08:25 AM 7/29/2005, you wrote:
>>Friends,
>>as suggested in the docs in the internet I tried both with
>>
>>
Alle 11:16, giovedì 28 luglio 2005, [EMAIL PROTECTED] ha scritto:
> In the first disk ad0 (master) of a computer at office I had installed
> linux to be used as a postgresql server. Later I installed FreeBSD 5.4
> (just to have a go at it) on a partition of the second disk ad1 (slave) to
> be a po
Gary W. Swearingen wrote:
If you're sticking to FreeBSD's boot0 MBR, you'll have to put one on
each disk. I don't know if boot0 can remember "F5" as the default
choice for auto-booting or not. But one way or another the first
disk's boot0 needs to use "F5" to start the second disk's MBR/boot0
[EMAIL PROTECTED] writes:
> # DeviceMountpoint FStype Options DumpPass#
> /dev/ad1s2b noneswapsw 0 0
> /dev/ad1s2a / ufs rw 1 1
> /dev/ad0s1a /usr/local
In the first disk ad0 (master) of a computer at office I had installed linux
to be used as a postgresql server. Later I installed FreeBSD 5.4 (just to
have a go at it) on a partition of the second disk ad1 (slave) to be a
postgrresql
server too.
Linux lilo was the boot loader, booting linux by de