xfs
[Top] [All Lists]

Re: mounting loop devices Thanx for the mkinitrd-3.0.5 patch!

To: Tom Duffy <tduffy@xxxxxxxxxxxx>
Subject: Re: mounting loop devices Thanx for the mkinitrd-3.0.5 patch!
From: Russell Cattelan <cattelan@xxxxxxxxxxx>
Date: Tue, 20 Mar 2001 14:09:38 -0500
Cc: thebs@xxxxxxxxxxx, b.j.smith@xxxxxxxx, linux-xfs@xxxxxxxxxxx
References: <Pine.LNX.4.30.0103201024210.2403-100000@dbear.engr.sgi.com>
Sender: owner-linux-xfs@xxxxxxxxxxx
Tom Duffy wrote:

> > Opps sorry it wasn't removed.
> > cmd/xfstests/misc/mkinitrd.xfs
> >
> > Suppose we could find a better place for this; "xfstests"  is a bit
> > misleading.
>
> right, but this is still 2.6 based.  should I check in my 3.0.9 based
> mkinitrd?

Hmm is it RedHat specific? The last time I updated mkinitrd I had revert the
mktemp portion; as Redhat seems to be the only one that supports mktemp -d
(aka temp directory)


>
>
> btw, jeremy brown will be adding some functionality real soon to mkinitrd
> to detect which filesystem you will need for boot and slap that into the
> mkinitrd (we were getting problems with reiserfs as well).  it does not
> make sense to include xfs and pagebuf in the initrd if you do not have to.

>
>
> I guess we should check that in as well once it is available.

I guess we can defer the whole thing for now.

The rpm's I'm building for prerelease 0.10 has XFS build into the kernel
which
renders the changes to mkinitrd un necessary unless somebody really wants
have
XFS as a module again.

For now I can export your is now that I know about it.


>
>
> -tduffy

--
Russell Cattelan
--
Digital Elves inc. -- Currently on loan to SGI
Linux XFS core developer.




<Prev in Thread] Current Thread [Next in Thread>