From owner-freebsd-stable@FreeBSD.ORG Tue Jan 6 20:03:59 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A324BEFF for ; Tue, 6 Jan 2015 20:03:59 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 335AA26B for ; Tue, 6 Jan 2015 18:04:10 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t06I4Vmc047702 for ; Tue, 6 Jan 2015 10:04:32 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: <20150106155623.GA61837@rancor.immure.com> References: <6b9041859ceb265eedaf6f56f9178a7b@ultimatedns.net> <20150102163539.1eaadbc7@nunki.holyordnance.org> <20150103172527.GI867@rancor.immure.com> <745af5f28074a940e743f6094be15991@ultimatedns.net> <54A88D7B.8010901@protected-networks.net> <20150105225028.GC57206@rancor.immure.com> , <20150106155623.GA61837@rancor.immure.com> From: "Chris H" Subject: Re: I need some swap partion help on new 10.1 install Date: Tue, 06 Jan 2015 10:04:32 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jan 2015 20:03:59 -0000 On Tue, 6 Jan 2015 09:56:24 -0600 Bob Willcox wrote > On Mon, Jan 05, 2015 at 08:11:27PM -0800, Kevin Oberman wrote: > > On Mon, Jan 5, 2015 at 7:04 PM, Warren Block 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). > > So, what should I put in /boot/loader.conf? Can I enable both GPT and GPT IDs > with this: > > kern.geom.label.gpt.enable="1" > kern.geom.label.gptid.enable="1" Adding the 2 above will give you both. Adding both will not result in any harm. But *do* remove the quotes from the value; as they aren't required/desired (in this case). issuing sysctl kern.geom.label.gptid.enable=1 will return kern.geom.label.gptid.enable=0 -> 1 if it was previously UNet (0) Same applies to kern.geom.label.gpt.enable Simply issuing sysctl kern.geom.label.gpt.enable will return it's *current* value. Same applies to kern.geom.label.gptid.enable, or any other setting. HTH --Chris > > And if I do, should I expect any problems with doing that? > > Bob > > > > -- > > R. Kevin Oberman, Network Engineer, Retired > > E-mail: rkoberman@gmail.com > > -- > Bob Willcox | Men who cherish for women the highest > bob@immure.com | respect are seldom popular with them. > Austin, TX | -- Joseph Addison > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"