From owner-freebsd-stable@FreeBSD.ORG Tue Jan 6 04:11:27 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 E9B9A21C for ; Tue, 6 Jan 2015 04:11:27 +0000 (UTC) Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B469528E1 for ; Tue, 6 Jan 2015 04:11:27 +0000 (UTC) Received: by mail-ie0-f171.google.com with SMTP id ar1so876583iec.2 for ; Mon, 05 Jan 2015 20:11:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=VGONVmbwa3xNfloRZEdMQVtgRxafmdSXUQAc9mAGudU=; b=Ref5FK2NNn8et7zrITEh4xkln0R/FzusKKqkhZJC8lq3BcgxXaYX2ol3TXbYe2mD4j ksrqirZQhqmGZSdZxiLQG9PTgXvdv8QlTwuxRgsmQdCqiJrteBD3ZZRT+RyN24bia2Op 05M4Fvx89YPNLo+9HTUaZ3kD9+JUUApupgN0BANX664Av093FPjTMYZYgcDe8OXSZRR1 muEVWCDnZAsiUgGxY5HifX/NMPEISoKUdtXO+Dj4d/b9rbWUjHfBsLlkob97gUzBvsKL eTBheAimtJQAlXilnGSQzXHGGTieKHW1dXlWR+W4f33XQ10FW3sr83tTgFq0bIz3vnnH OJzg== MIME-Version: 1.0 X-Received: by 10.51.17.11 with SMTP id ga11mr14234215igd.0.1420517487134; Mon, 05 Jan 2015 20:11:27 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.107.52.19 with HTTP; Mon, 5 Jan 2015 20:11:27 -0800 (PST) In-Reply-To: References: <20150102144223.14a2987e@nunki.holyordnance.org> <20150102215604.GF867@rancor.immure.com> <20150102145801.6ea92658@nunki.holyordnance.org> <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> Date: Mon, 5 Jan 2015 20:11:27 -0800 X-Google-Sender-Auth: K1_zKXr64fSUTLuRl4n8ZsgZajs Message-ID: Subject: Re: I need some swap partion help on new 10.1 install From: Kevin Oberman To: Warren Block Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD-STABLE Mailing List , Chris H 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 04:11:28 -0000 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). -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com