OK; after building today's -CURRENt on my build machine, I had time to try building the kernel again, but with GEOM.
3 observations so far: * Nearly everything still works. :-) * A verbose boot (my default on the machine in question, since I often need to check things or quote boot messages) with GEOM is *very* verbose. Just thought it might be of interest to mention this. * The ability to use boot0cfg to change the default boot slice seems broken: freebeast(5.0-C)[4] sudo boot0cfg -v ad0 # flag start chs type end chs offset size 1 0x00 0: 1: 1 0xa5 260:254:63 63 4192902 2 0x00 261: 0: 1 0xa5 521:254:63 4192965 4192965 3 0x00 522: 0: 1 0xa5 782:254:63 8385930 4192965 4 0x80 783: 0: 1 0xa5 1023:254:63 12578895 67697910 version=1.0 drive=0x80 mask=0xf ticks=182 options=nopacket,update,nosetdrv default_selection=F4 (Slice 4) freebeast(5.0-C)[5] sudo boot0cfg -s 1 ad0 && sudo halt -p boot0cfg: /dev/ad0: Operation not permitted freebeast(5.0-C)[6] Is this intentional? (I run the box headless, and boot different vesions of FreeBSD on different slices. Generally, I use slice 1 for today's -STABLE and slice 4 for today's -CURRENT; the other slices get clones of these, then get various forms of "customization" (hacks) that I test.) Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill [EMAIL PROTECTED] To paraphrase David Hilbert, there can be no conflicts between the discipline of systems administration and Microsoft, since they have nothing in common. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
