Date: Mon, 02 Oct 2000 19:47:31 -0700 From: xavian anderson macpherson <professional3d@home.com> To: Greg Lehey <grog@lemis.com>, "freebsd-questions@FreeBSD.ORG" <freebsd-questions@FreeBSD.ORG> Subject: Re: "Defining" vinum (was: APOLOGIES GIVEN TO ALL) Message-ID: <39D948C3.44B4D479@home.com> References: <39D8FAA6.3C2CE669@home.com> <14809.216.377993.679478@chris.xsb.com> <39D90385.C9397AEA@home.com> <20001003113126.D759@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
in bsd, it's; [page 279 the complete freebsd] # newfs -v /dev/vinum/concat i geuss you would then mount a directory to that partition; that's how it is done in linux. in linux, my volumes were /dev/ODIN/THOR01,2,3 etc. [my kernel is VALHALA ;-) ] the directories were then assigned to the volumes. # mount /dev/ODIN/THOR01 /usr if i specify a logical volume (in linux) after i already have data on the partition it is assigned to, it erases the data on that partition. that's why with suse, it done in the beginning in the installation, before anything else is done. i have been told that i have to wait until after i have installed my system, before i can define a vinum volume. what do i have to do? install a small incomplete but running system, only so that i can later specify the vinum volume on a separate partition? as i pointed out in suse-linux, the specification of logical volumes is done in the initial installation process. not later! if i have to first create a partial running system, on separate partition to create my volumes, that means that i then have to go back and move (or erase) the original partial system to make the partition it was on usable as a vinum device. is this clear enough? if this is the process, it is redundant to say the least. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39D948C3.44B4D479>