Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!werple.apana.org.au!otis.apana.org.au!serval.net.wsu.edu!netnews.nwnet.net!oracle.pnl.gov!osi-east2.es.net!cronkite.nersc.gov!dancer.ca.sandia.gov!overload.lbl.gov!agate!howland.reston.ans.net!pipex!warwick!news.ncl.ac.uk!lakeb1.ncl.ac.uk!n20hr From: "A.M. Zanker" <A.M.Zanker@ncl.ac.uk> Newsgroups: comp.os.386bsd.questions Subject: disklabel -B has no effect. Date: 9 Dec 1994 09:44:32 GMT Organization: University of Newcastle upon Tyne Lines: 25 Message-ID: <3c98u0$4st@whitbeck.ncl.ac.uk> NNTP-Posting-Host: lakeb1.ncl.ac.uk X-Newsreader: TIN [version 1.2 PL2] I have a strange problem with the FreeBSD 2.0R disklabel utility. I installed the system on my 2nd IDE drive (a 170MB IBM model) and decided to edit the bootblocks to allow default booting from this drive. Having successfully edited and recompiled bootwd and wdboot I proceeded to install them with "disklabel -B wd1". However, the boot blocks on the disk were completely unaffected by this (as od -c /dev/rwd1c revealed). I tried a number of other incantations of the disklabel command without success. I eventually solved the problem by copying wdboot and bootwd to /stand/sdboot and /stand/bootsd (yes, SD) and running the sysinstall utility to write the MBR/disklabel for my 2nd drive. So, why does the sysinstall utility manage this and disklabel doesn't? I've searched the FAQs and found no mention of this situation other than using just wd1 instead of /dev/rwd1c as a parameter to disklabel (which didn't work). Thanks in advance, Mike -- Mike Zanker | A.M.Zanker@ncl.ac.uk Department of Mathematics and Statistics | University of Newcastle upon Tyne, UK | PGP public key available