On Sun, Jan 04, 2015 at 06:37:18PM -0700, Warren Block wrote:> 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.The more I read of this thread the more confused I get. What should I have in /boot/loader.conf to get the old behavior with more traditional device names? Also, if bsdinstall doesn't do this for me automatically, why did it put /dev/ada0p2 in the fstab for swap? Bob> _______________________________________________ > 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"-- Bob Willcox | Men who cherish for women the highest bob at immure.com | respect are seldom popular with them. Austin, TX | -- Joseph Addison
On Mon, 5 Jan 2015, Bob Willcox wrote:> On Sun, Jan 04, 2015 at 06:37:18PM -0700, Warren Block wrote: >> 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. > > The more I read of this thread the more confused I get. What should I have in > /boot/loader.conf to get the old behavior with more traditional device names? > > Also, if bsdinstall doesn't do this for me automatically, why did it put > /dev/ada0p2 in the fstab for swap?The best way is to use GPT labels, which are stored in the GPT header. They are portable, so keep working if the drive device name changes (ada0 to da1, say). GPT labels can be set with gpart modify. The labels appear in /dev/gpt/. As mentioned before, they might not appear if a partition is mounted due to GEOM "withering". GPT labels are enabled by default. If bsdinstall is disabling them, it is a regression. GPT IDs, on the other hand, are a unique generated ID code that can appear at the same time. Many of us find them not very useful and disable them in loader.conf. I have only upgraded systems to 10.1, so don't know what bsdinstall does on a new install.
On Mon, 5 Jan 2015 16:50:29 -0600 Bob Willcox <bob at immure.com> wrote> On Sun, Jan 04, 2015 at 06:37:18PM -0700, Warren Block wrote: > > 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. > > The more I read of this thread the more confused I get. What should I have in > /boot/loader.conf to get the old behavior with more traditional device names? > > Also, if bsdinstall doesn't do this for me automatically, why did it put > /dev/ada0p2 in the fstab for swap?I imagine this has probably been addressed/responded to, but... For the sake of confusion; MBR - so-called "legacy" is probably the version you are most accustomed to seeing: /dev/adaNpN GPT gpart(8)/glabal(8) is the newer alternative. It creates more *human readable* names, eg; /gpt/my-bright-shiny-root /gpt/my-new-usr /gpt/my-yadda-yadda-yadda GPTID is yet another alternative. You used it to get your swap mounted. I suggested using a GPT setup because; - Your disk indicated it had a label - The names are easier to read/identify Adding kern.geom.label.gpt.enable=1 to loader.conf(5) will give you that (/boot/loader.conf) In the end, it's all a matter of personal preference. Use what you think works best for you, you're most comfortable with. *Do* read the appropriate man pages, to insure you'll be using one that will *continue* to work with you. --Chris> > Bob > > > _______________________________________________ > > 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" > > -- > Bob Willcox | Men who cherish for women the highest > bob at immure.com | respect are seldom popular with them. > Austin, TX | -- Joseph Addison > > _______________________________________________ > 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"