From owner-freebsd-current@FreeBSD.ORG Fri Jan 4 06:15:41 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5B13076 for ; Fri, 4 Jan 2013 06:15:41 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ea0-f169.google.com (mail-ea0-f169.google.com [209.85.215.169]) by mx1.freebsd.org (Postfix) with ESMTP id C95DEE2E for ; Fri, 4 Jan 2013 06:15:40 +0000 (UTC) Received: by mail-ea0-f169.google.com with SMTP id a12so6448379eaa.14 for ; Thu, 03 Jan 2013 22:15:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=cECCWVSshykraGyhUp8n2lzQFrs3WzLzAYvEIZMLeGA=; b=TDE9yM/TcR5IMNqSJGKNl5Y4MixLg8CiatFNhz4068jjD7jpLgn5HTwE/0LOst5+yF /tAQPh2o016eQ26390yY5QTh//CxGrE6pmWzdPu74HcX40NkNRKAgNOdUZubApyJs3BC ihTj+kNu9zBII0pGUhn+QKlXH5HDqSjOhGezqidxrqjXYVThrJH/NLfRq46+RnrxiL7i S9W/smlMymCQU6pDvus2IfvLaiD+1qUnrbbN5YQ3q9NrOA0cWvWHsiXA3jRLPrVo5aaN QD5hoYUs5LsBTTtjS2odKnlmfyEcvt+N9e6lHPggsvUEV9z79y2avgS5ONB/3mlMvUR+ 6juw== MIME-Version: 1.0 Received: by 10.14.2.196 with SMTP id 44mr140555538eef.25.1357280134315; Thu, 03 Jan 2013 22:15:34 -0800 (PST) Received: by 10.223.170.193 with HTTP; Thu, 3 Jan 2013 22:15:34 -0800 (PST) In-Reply-To: References: <50E0BFA0.6070702@rcn.com> <50E476D3.2030609@rcn.com> <50E612DA.8020704@rcn.com> Date: Thu, 3 Jan 2013 22:15:34 -0800 Message-ID: Subject: Re: problem after installkernel going from 9.0 to CURRENT From: Kevin Oberman To: Warren Block Content-Type: text/plain; charset=UTF-8 Cc: Robert Huff , current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jan 2013 06:15:41 -0000 On Thu, Jan 3, 2013 at 7:24 PM, Warren Block wrote: > On Thu, 3 Jan 2013, Kevin Oberman wrote: > >>> One possibility: I believe I labeled each of the partitions >>> during >>> the gpt creation process. Can I use those labels to (hopefully) by-pass >>> this issue? >> >> >> Yes! This is the current recommended way of doing it. >>> >>> cat /etc/fstab >> >> # Device Mountpoint FStype Options Dump >> Pass# >> /dev/gpt/swap none swap sw 0 0 >> /dev/gpt/root / ufs rw 1 1 >> /dev/gpt/tmp /tmp ufs rw 2 2 >> /dev/gpt/usr /usr ufs rw 2 2 >> /dev/gpt/var /var ufs rw 2 2 > > > To avoid collisions, I recommend people use unique labels on each system. I > sometimes pick a couple of letters from the system name or drive: xfswap, > xfrootfs, xftmpfs, xfusrfs, xfvarfs. Good point (as usual). The example was from my laptop where this is not an issue, but in larger environments it is an excellent suggestion. I would put the unique ID at the end of the label as the eye tends to read from left to right (at least in most language so you can recognize whether it is usr or swap or home pretty much instantly. Sticking letters at the start make the most fundamental information harder to see. swaprxf xfswap usrfsxf xfusrfs Still, this is a nit and I appreciate the suggestion!.. -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com