freebsd stable - Jan 2015 - I need some swap partion help on new 10.1 install

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, Jan 5, 2015 at 7:04 PM, Warren Block <wblock at wonkity.com>
wrote:
> 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.
>
Just checked head and bsdinstall does not disable GPT labels. It does
disable gptid labels (which IMHO is a good thing).
--
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkoberman at gmail.com