Message-ID: <40DC7539.7000803@comcast.net>
Date: Fri, 25 Jun 2004 14:55:53 -0400
From: David van Hoose <david.vanhoose@comcast.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510
MIME-Version: 1.0
To: Tigran Aivazian <tigran@aivazian.fsnet.co.uk>
CC: "Philip R. Auld" <pauld@egenera.com>,
       Christoph Hellwig <hch@infradead.org>,
       Helge Hafting <helge.hafting@hist.no>, linux-kernel@vger.kernel.org
Subject: Re: Collapse ext2 and 3 please
References: <Pine.LNX.4.44.0406251438420.15676-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.44.0406251438420.15676-100000@localhost.localdomain>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1205
Lines: 32

Thank you.
It says ext2. Based on other messages, I look at /sbin/mkinitrd.
It looks to me that RedHat/Fedora are pretty dumb making stupid 
assumptions about the fs type instead of looking at the filesystem types 
that root has setup in fstab.
I've patched my mkinitrd script to check the fs type of the root 
partition according to /proc/mounts. This should work unless someone is 
overriding mkinitrd to build an initrd for a foreign system or changing 
their root partition. To fix that, I've added an command-line option to 
specify the fs type of the root partition.

Thanks very very much.
Sorry for the error. I assumed too much about RedHat.

Thanks,
David

Tigran Aivazian wrote:
> # gzip -dc /boot/initrd-2.4.21-15.EL.img | file -
> standard input:              Linux rev 1.0 ext2 filesystem data
> 
> Make sure you use the correct filename for your initrd image (check 
> /etc/grub.conf to find out which one is used).
> 
> Kind regards
> Tigran
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/