On 01/03/15 19:35, Kevin Oberman wrote: [ .. snip .. ]> As per an earlier suggestion, did you put: > kern.geom.label.gpt.enable=0 > into /boot/loader.conf? If so, that's why you lack a /dev/gpt label. This > is usually a "friendlier" string than the diskid, but both work equally > well.bsdinstall does that on its own - you have to manually remove/comment/set to "1" after installation :-( imb
On Sat, 03 Jan 2015 19:46:51 -0500 Michael Butler <imb at protected-networks.net> wrote> On 01/03/15 19:35, Kevin Oberman wrote: > > [ .. snip .. ] > > > As per an earlier suggestion, did you put: > > kern.geom.label.gpt.enable=0 > > into /boot/loader.conf? If so, that's why you lack a /dev/gpt label. This > > is usually a "friendlier" string than the diskid, but both work equally > > well. > > bsdinstall does that on its own - you have to manually > remove/comment/set to "1" after installation :-(This _is_ a disappointment, and I have no idea why that should be so. sysctl kern.geom.label.gpt.enable=1 will give it to you immediately. But I'm not aware as to whether it will stick. So loader.conf(5) (as Kevin Oberman stated) should probably be used as, well. --Chris> > imb > > > _______________________________________________ > freebsd-stable at freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
On Sat, 3 Jan 2015, Michael Butler wrote:> On 01/03/15 19:35, Kevin Oberman wrote: > > [ .. snip .. ] > >> As per an earlier suggestion, did you put: >> kern.geom.label.gpt.enable=0 >> into /boot/loader.conf? If so, that's why you lack a /dev/gpt label. This >> is usually a "friendlier" string than the diskid, but both work equally >> well. > > bsdinstall does that on its own - you have to manually > remove/comment/set to "1" after installation :-(gpt, or gptid? The first would be a terrible regression, the second, not so much.