>Date: Wed, 4 Dec 2002 15:17:39 +0200 >From: Vallo Kallaste <[EMAIL PROTECTED]>
>I'm using both -current and -stable on the same machine, very >common. Boot0cfg has -s [12345] flag to set the slice to boot on and >it has been working so far. Beginning from Dec 1, I'm unable to set >the slice: >root:vallo# boot0cfg -v ad0 ># flag start chs type end chs offset size >1 0x80 0: 1: 1 0xa5 1023: 15:63 63 16382961 >2 0x00 1023:255:63 0xa5 1023: 15:63 16383024 16383024 >version=1.0 drive=0x80 mask=0xf ticks=182 >options=packet,update,nosetdrv >default_selection=F1 (Slice 1) >root:vallo# boot0cfg -v -s 2 ad0 >boot0cfg: /dev/ad0: Operation not permitted >root:vallo# disklabel -W ad0 >disklabel: /dev/ad0: Operation not permitted Yes; it is an artifact of GEOM (per phk). >This is probably related to recent (re)work to protect disk labels, >but I'm not authoritative. This is not a fair way to stick me to >-current :-) Right; I have the same problem. By interrupting the boot sequence early enough (by hitting the space bar) -- before loader is, itself, loaded, and the prompt is >> FreeBSD/i386 BOOT Default: 0:ad(0,a)/boot/loader boot: -- you can override it by typing 0:ad(0,1,a)/boot/loader (to boot from slice 1) -- ref. "man boot". The timing can be tricky enough to be a nuisance when one is doing this on a machine with (only) a serial console, especially when the machine is not close enough to hear the disk seeks. :-} Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill [EMAIL PROTECTED] I have no confidence in results obtained through the use of Microsoft products. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
