Date: Mon, 02 Oct 2000 18:13:16 -0700 From: xavian anderson macpherson <professional3d@home.com> To: Christopher Rued <c.rued@xsb.com>, "freebsd-questions@FreeBSD.ORG" <freebsd-questions@FreeBSD.ORG> Subject: Re: vinum question Message-ID: <39D932AC.4D3D9C06@home.com> References: <39D8FAA6.3C2CE669@home.com> <14809.216.377993.679478@chris.xsb.com> <39D90385.C9397AEA@home.com> <14809.1418.335403.207878@chris.xsb.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--------------1E000CF856E357CF90457611
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
let me state once more that i have the book and am reading it! i
brought the 10cd power-pak. i like the manual. it was because of the
manual that i brought the power-pak. so much for the guy who said i was
lazy for not reading. if i didn't want to read, and didn't think that i
should have to, i wouldn't have brought the book. i tried to download
the freebsd kernel from the web. but i could make heads or tails of
it. i was expecting to find the kernel to be one contiguous unit as it
is in linux. now maybe it is. but what i found was kernel modules as
they would appear in linux after the kernel and it's components had been
compiled. i didn't find any file of the size that i expected the kernel
to be (17-21MB's for linux). it was because of this recognition, that i
was erroneously applying concepts from one system to another, that i
chose to admit that i don't know what i am doing. it is also because of
this that i am approaching this (installation) with great trepidation.
Christopher Rued <c.rued@xsb.com>
chris wrote;
After you install, the kld should be in /modules/vinum.ko. According
what I just read, you should not even have to explicitly load the
module. When you try to use vinum, it will automatically be loaded.
You do not have to do anything special to install the kld. Just
install the OS, and you will be able to run vinum.
====================================================================
thank you. the reason why i did not proceed, was that with linux, if
you change the definition of the partition type, after it's initial
declaration, you inevitably erase all the data on the partition. does
it at least seem reasonable that someone should not want to have to
erase their canvas to add a new color? it is for this reason that i
chose not to proceed without knowing (explicitly) the results of my
actions beforehand. i didn't buy freebsd to make mistakes, but rather
to have a solution to them! what i still have not been told is, `when
you define the partition labels at installation, is that also where you
define vinum?' is that simply put enough?
in linux, my system (kernel) is VALHALA, my volume group was `ODIN'.
the physical volumes were `THOR'. such that the labels went like
this;
/dev/ODIN/THOR01, /THOR02, /THOR03, etc.
that was very simple and straight-forward. it didn't require a math
degree to interpret this. it is done at the time of the initial
installation. you did not first load (any) data on the partitions and
then go back and relabel them, for the very reasons already stated
above. if freebsd is different, great! but i have not read where that
is the case. and it would not be ligitimate for me to assume so. in
fact, i assume the worst, and expect it.
--------------1E000CF856E357CF90457611
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<b><font face="Arial,Helvetica"><font size=+1>let me state once more that
i have the book and am reading it! i brought the 10cd power-pak.
i like the manual. it was because of the manual that i brought the
power-pak. so much for the guy who said i was lazy for not reading.
if i didn't want to read, and didn't think that i should have to, i wouldn't
have brought the book. i tried to download the freebsd kernel from
the web. but i could make heads or tails of it. i was expecting
to find the kernel to be one contiguous unit as it is in linux. now
maybe it is. but what i found was kernel modules as they would appear
in linux after the kernel and it's components had been compiled.
i didn't find any file of the size that i expected the kernel to be (17-21MB's
for linux). it was because of this recognition, that i was erroneously
applying concepts from one system to another, that i chose to admit that
i don't know what i am doing. it is also because of this that i am
approaching this (installation) with great trepidation.</font></font></b><b><font face="Arial,Helvetica"><font size=+1></font></font></b>
<p><b><font face="Arial,Helvetica"><font size=+1>Christopher Rued <c.rued@xsb.com></font></font></b>
<br><b><font face="Arial,Helvetica"><font size=+1>chris wrote;</font></font></b><b><font face="Arial,Helvetica"><font size=+1></font></font></b>
<p><b><font face="Arial,Helvetica"><font size=+1>After you install, the
kld should be in /modules/vinum.ko. According</font></font></b>
<br><b><font face="Arial,Helvetica"><font size=+1>what I just read, you
should not even have to explicitly load the</font></font></b>
<br><b><font face="Arial,Helvetica"><font size=+1>module. When you
try to use vinum, it will automatically be loaded.</font></font></b>
<br><b><font face="Arial,Helvetica"><font size=+1>You do not have to do
anything special to install the kld. Just</font></font></b>
<br><b><font face="Arial,Helvetica"><font size=+1>install the OS, and you
will be able to run vinum.</font></font></b>
<br><b><font face="Arial,Helvetica"><font size=+1>====================================================================</font></font></b>
<br><b><font face="Arial,Helvetica"><font size=+1>thank you. the
reason why i did not proceed, was that with linux, if you change the definition
of the partition type, after it's initial declaration, you inevitably erase
all the data on the partition. does it at least seem reasonable that
someone should not want to have to erase their canvas to add a new color?
it is for this reason that i chose not to proceed without knowing (explicitly)
the results of my actions beforehand. i didn't buy freebsd to make
mistakes, but rather to have a solution to them! what i still have
not been told is, `when you define the partition labels at installation,
is that also where you define vinum?' is that simply put enough?</font></font></b><b><font face="Arial,Helvetica"><font size=+1></font></font></b>
<p><b><font face="Arial,Helvetica"><font size=+1>in linux, my system (kernel)
is VALHALA, my volume group was `ODIN'. the physical volumes were
`THOR'. such that the labels went like this;</font></font></b><b><font face="Arial,Helvetica"><font size=+1></font></font></b>
<p><b><font face="Arial,Helvetica"><font size=+1> /dev/ODIN/THOR01,
/THOR02, /THOR03, etc.</font></font></b><b><font face="Arial,Helvetica"><font size=+1></font></font></b>
<p><b><font face="Arial,Helvetica"><font size=+1>that was very simple and
straight-forward. it didn't require a math degree to interpret this.
it is done at the time of the initial installation. you did not first
load (any) data on the partitions and then go back and relabel them, for
the very reasons already stated above. if freebsd is different, great!
but i have not read where that is the case. and it would not be ligitimate
for me to assume so. in fact, i assume the worst, and expect it.</font></font></b></html>
--------------1E000CF856E357CF90457611--
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?39D932AC.4D3D9C06>