On Wed, 10 Jan 2001, Andreas Dilger wrote:
> I've heard "soon" on the LVM list, but I'm just one of the chickens. If
> it were up to me, the fixes would go to Linus as soon as they are found.
indeed. it looks bad when code is updated irregularly, and it's a
pain for users.
> Cheers, Andreas
Paul Jakma writes:
> On Wed, 10 Jan 2001, Andreas Dilger wrote:
> > You should also get the LVM user tools from CVS (with TAG LVM_0-9-patches)
> > to solve this problem. There will hopefully be a new LVM release soon.
>
> any word on when the kernel fixes are going to linus?
I've heard "soon" o
On Wed, 10 Jan 2001, Andreas Dilger wrote:
> You should also get the LVM user tools from CVS (with TAG LVM_0-9-patches)
> to solve this problem. There will hopefully be a new LVM release soon.
any word on when the kernel fixes are going to linus?
--
Paul Jakma [EMAIL PROTECTED] [EMAIL
Gustavo Zacarias writes:
> I was just trying LVM's vgextend, maybe i'm missing something??
> LVM works as long as i don't try to extend the VG.
> I can do testing/patching without trouble here...
There is a patch to the LVM kernel code which should help:
ftp://ftp.us.kernel.org/pub/linux/kernel/p
Motherboard is ASUS P2B (BX/PIIX4) w/Intel P3-550 Katmai.
No OCing, RAM is perfectly OK (been using it for a year).
hda = Quantum Fireball ST3.2A
hdb = IBM-DTLA-307045
I know i should have them in separate IDE channels, but for
now i was setting up LVM to move another fast/big disk in.
Kernel i
5 matches
Mail list logo
