Date: Mon, 14 Feb 2011 20:39:44 -0500 From: "illoai@gmail.com" <illoai@gmail.com> To: Rem P Roberti <remegius@comcast.net> Cc: Rem P Roberti <rem@remdog.net>, Polytropon <freebsd@edvax.de>, FreeBSD <freebsd-questions@freebsd.org> Subject: Re: Redux Message-ID: <AANLkTim7FPQh1O-DBrPyiKNva_g7==S0MtCXVJ1GdSP5@mail.gmail.com> In-Reply-To: <4D59C7AD.1070300@comcast.net> References: <4D59BCF4.2040209@remdog.net> <20110215011220.16606770.freebsd@edvax.de> <4D59C7AD.1070300@comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 14 February 2011 19:24, Rem P Roberti <remegius@comcast.net> wrote: > >> On Mon, 14 Feb 2011 15:38:28 -0800, Rem P Roberti<rem@remdog.net> =A0wro= te: >>> >>> I need to ask this question again in the hopes that something will come >>> of it. =A0In the process of going through an update (I finally got that >>> sorted out) all of my partitions were renamed. =A0Here they are: >>> >>> Filesystem =A0 =A0 =A0 =A0 =A0 =A0 =A0 1K-blocks =A0 =A0 =A0 Used =A0 = =A0 =A0 Avail =A0 =A0 =A0Capacity >>> =A0 =A0 =A0 =A0Mounted on >>> /dev/label/rootfs0 =A0 =A0507630 =A0 =A0 =A0 =A0 326734 =A0 140286 =A0 = =A0 =A0 70% >>> =A0 =A0 =A0 =A0 =A0 / >>> devfs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A01 =A0 =A0 =A0 =A0 =A0 =A0 =A0 1 =A0 =A0 =A0 =A0 =A00 >>> =A0 =A0 100% =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0/dev >>> /dev/label/var0 =A0 =A0 =A01012974 =A0 =A0 =A0 =A0 170386 =A0 761552 = =A0 =A0 =A0 18% >>> =A0 =A0 =A0 =A0 =A0/var >>> /dev/label/usr0 =A0 =A0 33292236 =A0 =A0 =A0 9358560 21270298 =A0 =A0 3= 1% >>> =A0 =A0/usr >>> linprocfs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A04 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 4 =A0 =A0 =A0 =A0 =A00 >>> =A0 =A0 =A0100% =A0 =A0/usr/compat/linux/proc >>> /dev/md0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0789518 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 16 =A0 =A0 726342 =A0 =A0 =A00% >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0/tmp >>> >>> As you can see, root, which was once /dev/ad0s1a, is now >>> /dev/label/rootfs0, and /var, which was once /dev/ad0s1d, is now >>> /dev/label/var0. =A0Along with these changes the /etc/fstab was >>> automatically modified to allow the boot process to take place. =A0Can >>> someone give me a heads up as to what is going on here. >> >> Seems that you - or something - did make the switch from >> device names to labels. Maybe your kernel now includes >> GEOM functionality for work with labels? But I don't know >> of a process that changes /etc/fstab automatically... >> >> You can still use the device names for the /etc/fstab >> entries, you just need to make sure that you select >> the correct names (as you described above). Then there >> should be no problem as labels are optional. >> >> > > > Honestly, I certainly didn't make the change from device names to labels.= =A0I > wouldn't know how to do that, although I gather from what you've said tha= t > the kernel config file contains that information. =A0I'm not sure, howeve= r, > what you mean when you say that I can still use the device names, as the > system will not boot unless fstab has in it the entries shown above. FreeBSD is wonderful, don't get me wrong, but it is not magical. Partitions don't just accrue labels and /etc/fstab doesn't edit itself. Are you running PCBSD? Anyway, if you want to go back to device names in the /dev/ad0s1[a-g] scheme you can extract the correct names with: geom label list (you might want to pipe it into a pager) then edit your /etc/fstab accordingly and reboot. Although, why bother really? The label names may come in handy if you have to move the hdd to another machine to extract the information, or for various other reasons. --=20 --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTim7FPQh1O-DBrPyiKNva_g7==S0MtCXVJ1GdSP5>