Date: 22 Jun 1998 09:59:44 +0200 From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) To: robert@chalmers.com.au Cc: Mike Smith <mike@smith.net.au>, Robert Chalmers <robert@nanguo.chalmers.com.au>, hackers@FreeBSD.ORG Subject: Re: Is using fdisk a must? Message-ID: <rx4iultrhn3.fsf@oslo.geco-prakla.slb.com> In-Reply-To: Robert Chalmers's message of Mon, 22 Jun 1998 15:48:47 %2B1000 References: <199806220347.UAA03208@antipodes.cdrom.com> <358DF03F.BFA47ED9@chalmers.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Chalmers <robert@chalmers.com.au> writes: > This of course builds a _bootable_ disk, right? The -B loads a boot image. > Least wise it did on mine, and I had the devil of a job disabling it, and > rebooting off the correct, primary, drive. Are you certain that the "correct, primary drive" really is the primary drive? (i.e. the one probed first and assigned the lowest device ID) > I have the drive up and running, it just gives the 'no magic' warning at boot > time... as mentioned in the first post. > [...] > I am beginning to believe that FreeBSD simply has no facility for building new > drives from disktab entires entirely? If there is a way, perhaps someone would > like to tell me what it is - barring the use of fdisk, which doesn't exist on > most Unix systems! it's a DOS-i386'ism. You must have done something wrong somewhere. I have two SCSI and one ESDI drive, all manually partitioned and labeled the way Mike described, in a 24/7 box. The only problem I ever had doing this was having to swap my SCSI controllers them so the right one would be probed and attached first. Since the PCI bus has numbered slots and devices are probed in order, that was practically a no-brainer. -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?rx4iultrhn3.fsf>