lvm sysinst patch
Adam Hamsik
I have done some initial work on integration of our LVM into the
sysinst look at attached patch. I think that best way how to add
support for LVM to sysinst is add new entry to Utility menu which will
execute lvm in a shell mode. User can then set up his LV disks, create
Physical Volumes and Volume Groups. We will need /sbin/lvm
binary on install disk and dm driver in installation kernel. After
exit from lvm shell user can choose created logical disks and install
e.g. /usr on them except / (we do not support / on the Logical Volume).
I found that sysinst doesn't detect LV's properly because DISK_NAMES
value doesn't match them. We should probably find way how to get list
of all disk devices with out hardcoding their name in sysinst code,
because LV can have user defined name. LV's are place in this
directory structure /dev/{volume_group_name}/{lv_name}.
I really appreciate to hear any feedback from you, even about our new
sysinst implementation.
Any comments ?
Hubert Feyrer
> Any comments ?
Is offering the menu item really worth the increase in space for the
ramdisk? If there's a deeper thought, then this should be reflected in the
install docs, at least ("If you intend to use LVM, do ...").
Having LVM documented in the NetBSD Guide could go as a nice alternative
for this (Have a chapter "How to install a system with LVM enabled" in
the Guide, and the reference this in the install docs).
Right now, I wouldn't know what to do.
- Hubert
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-...@muc.de
Adam Hamsik
On Jan,Sunday 4 2009, at 11:42 PM, Hubert Feyrer wrote:
> On Sun, 4 Jan 2009, Adam Hamsik wrote:
>> Any comments ?
>
> Is offering the menu item really worth the increase in space for the
> ramdisk? If there's a deeper thought, then this should be reflected
> in the install docs, at least ("If you intend to use LVM, do ...").
I have prepared lvm chapter about LVM for the NetBSD guide and I will
add installation part when I
will be sure how it will be done. There are still some problems to
solve because our sysinst doesn't
support multiple disks instalation. Patch is located here [1].
>
>
> Having LVM documented in the NetBSD Guide could go as a nice
> alternative for this (Have a chapter "How to install a system with
> LVM enabled" in the Guide, and the reference this in the install
> docs).
>
> Right now, I wouldn't know what to do.
[1]http://www.netbsd.org/~haad/lvm_doc.diff
Regards
Adam.
Eric Haszlakiewicz
> On Sun, 4 Jan 2009, Adam Hamsik wrote:
> >Any comments ?
>
> Is offering the menu item really worth the increase in space for the
> ramdisk? If there's a deeper thought, then this should be reflected in the
> install docs, at least ("If you intend to use LVM, do ...").
>
> Having LVM documented in the NetBSD Guide could go as a nice alternative
> for this (Have a chapter "How to install a system with LVM enabled" in
> the Guide, and the reference this in the install docs).
imo, if we're going to offer a feature and have any desire for it to be
widely used it should be obviously present in the "normal" way of installing
a system.
You seem to be arguing *against* making the use of lvm user friendly. Am
I interpreting you correctly? And if so, why?
(I'm assuming that the menu item to run "lvm" actually does something
user friendly, but I haven't looked at it)
eric
Hubert Feyrer
>> Is offering the menu item really worth the increase in space for the
>> ramdisk? If there's a deeper thought, then this should be reflected in the
>> install docs, at least ("If you intend to use LVM, do ...").
>>
>> Having LVM documented in the NetBSD Guide could go as a nice alternative
>> for this (Have a chapter "How to install a system with LVM enabled" in
>> the Guide, and the reference this in the install docs).
>
> widely used it should be obviously present in the "normal" way of installing
> a system.
> You seem to be arguing *against* making the use of lvm user friendly. Am
> I interpreting you correctly?
No, I agree with you.