Date: Thu, 31 Aug 1995 07:46:50 +1000 From: Bruce Evans <bde@zeta.org.au> To: bde@zeta.org.au, hackers@freebsd.org, jdl@chrome.onramp.net, rcarter@geli.com Subject: Re: /etc/disktab and stuff Message-ID: <199508302146.HAA23375@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>|Something like the following should work, but I'm less sure about it: >| >| disklabel /dev/rsd1 >/etc/label.sd1 # get sub-minimal label >| vi /etc/label.sd1 # fix deficiencies in label; >| # partition as required >| disklabel -R -r sd1 /etc/label.sd1 >| >Would this work with the ncr controller, which has trouble guessing >the right parameters with large drives? I can see an opportunity It doesn't depend on the controller or the drive (except for old ST506 and ESDI drive/controllers that don't report their geometry. >for a lot of experimenting on both the msdog/FreeBSD sides getting >an initial set of parameters that would work with fdisk. These are the BIOS geometry parameters. They aren't directly related to the drive or the controller. They are only used for booting, and then only if the bootstrap isn't on the first track as the BIOS sees it. The above method puts the bootstrap on the first track (if tracks have >= 16 sectors :-). The above method fails if the existing MBR is magic in some way, e.g., if it has Disk Manager on it. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199508302146.HAA23375>