I think support for configuring LVM at install time would be great.
It is already there. What does not work is configuring LVM with
diskdrake after installation (due to devfs naming confusion). Everything
you describe further on is already there if you configure as expert. You
say yourself it
Borsenkow Andrej wrote:
I think support for configuring LVM at install time would be great.
and what about striped LVM ( creating, stripesize),who asks you for the
name of the LV, readahead, wich PV's to use
It is already there. What does not work is configuring LVM with
diskdrake after
I think support for configuring LVM at install time would be great.
and what about striped LVM ( creating, stripesize),who asks you for
the
name of the LV, readahead, wich PV's to use
O.K. not in these details. You create 0x8e (IIRC) partition that becomes
PV (hmm ... not sure what
Borsenkow Andrej wrote:
I think support for configuring LVM at install time would be great.
and what about striped LVM ( creating, stripesize),who asks you for
the
name of the LV, readahead, wich PV's to use
O.K. not in these details. You create 0x8e (IIRC) partition that becomes
PV (hmm
echo 0x3a00 /proc/sys/kernel/real-root-dev
This is not needed at all. Currently initrd mounts kernel and leaves
real-root-dev to be RAM disk and system is happy with it:
[root@cooker root]# cat /proc/sys/kernel/real-root-dev
256
Even worse, you *must*not* do it. If you change
I have finally gotten some time to get back to my project of making
the installer install on an LVM root (and boot it afterward :-) and I
am pleased to report that my mods work! With a caveat or two that I
am hoping I can get help working out here.
Congratulations! :-) Still, have you
I am pretty new to LVM and have not tried it yet but
this thought came to mind. Since LVM can dynamically
change partition sizes and allow for you to add and
subtract hard drive space on the fly... why not have
mandrake create lvm by default? Even if the root
directory was not run with LVM every
but if we had the the lvm-1.0.1rc2 code in the kernel and the tools
after Sistina we should heve access to both pre lvm-0.9.1beta8 and
lvm-1.0 and after
created VG's and LV's
Pixel wrote:
Christian Bricart [EMAIL PROTECTED] writes:
[...]
- Downward compatibility pb
Not true (anymore). LVM
