rczero at mail.com
Sat Mar 11 21:18:58 UTC 2006
You were right. There is nothing wrong.
Part of my problem was that I had never had or seen anything on other slices. Now I have two fbsd installs, ad0s1 and ad02 and I mistook ad0s2's missing info as applying to ad0s1.
What I really want to do is use ad0s1 as my production install and ad0s2 as my test install. I guess my procedure would be to copy prod to test, then perform any testing for new ports, etc. Then once tested, perform those same actions on ad0s1.
I have been reading up on how to "clone" a disk, so I can boot into a copy. Seems like some say tar can do it, but I have seen a place that said to only use dump. Oh, well. I am not quite there yet, working on baby steps.
----- Original Message -----
From: "illoai at gmail.com"
To: "Steve P."
Subject: Re: disklabel messup.
Date: Sat, 11 Mar 2006 04:33:25 -0600
On 3/10/06, Steve P. wrote:
> I was using sysinstall's disklabel facility to poke around. I
> accidentally did "Undo" on my installed 6.0 working slice.
Are you sure you actually did anything?
If /etc/fstab shows them correctly still
and running 'df' shows them still as they
should be, I'm pretty sure that running
sysinstall again will show the slices and
partitions correctly. I would advise that
'bsdlabel /dev/ad0' will show you your
label just as effectively, and that df(1)
is probably the correct method of gazing
in rapture at your mounted partitions.
Other commands to read up on might
be fdisk and diskinfo.
Play 100s of games for FREE! http://games.mail.com/
More information about the freebsd-questions