> You can use ext3 as a module if ext2 is also a module, I believe.
> That's why the stock 2.4.17-686 kernel works with ext3 out of the box,
> whereas 2.4.17-386 and 2.4.17-k7 and probably all others don't--they
> have ext2 built into the kernel.
2.4.17-k7 boots my ext3 root partition fine it has
Alexander List writes:
> On Thu, 31 Jan 2002, Sven Schumacher wrote:
>
> > > 5.) edit /etc/fstab replacing ext2 with ext3
>
> > You cant use ext3 for root fs if you use ext3 as a module.
>
> Are you sure about this? ext2 is also a module in the latest stock
> kernels, have a closer look
On Thu, 31 Jan 2002, Terry Carney wrote:
> I opted to compile the initrd-related stuff right into the kernel.
>
> When you use make-kpkg to create your kernel_image just add --initrd as
> a make-kpkg option .
I know that I can do this, but it would however be nicer to have ext3 also
in the stock
On Thu, 31 Jan 2002, Sven Schumacher wrote:
> > 5.) edit /etc/fstab replacing ext2 with ext3
> You cant use ext3 for root fs if you use ext3 as a module.
Are you sure about this? ext2 is also a module in the latest stock
kernels, have a closer look at the /boot/config.x.y! I was surprised by
thi
On Thu, 31 Jan 2002, Alexander List wrote:
> Unfortunately, this means that I have to recreate my initrd everytime a
> new kernel package is to be installed. What do you think about enabling
> ext3 support in the standard kernels by default? I'm not talking about
> switching the default fs type al
[Please CC me in replies, as I'm not currently subscribed to debian-user]
Hi,
I just successfully did the following:
1.) add ext3 to /etc/mkinitrd/modules
2.) mkinitrd -o /boot/initrd.img-2.4.17+ext3-686 /lib/modules/2.4.17-686/
3.) in /etc/lilo.conf set initrd=/boot/initrd.img-2.4.17+ext3-686
4
6 matches
Mail list logo
