Re: Why do I need mkinitrd with 2.6?

To: Jeff Mitchell <jam6@cec.wustl.edu>
Cc: debian-user@lists.debian.org
Subject: Re: Why do I need mkinitrd with 2.6?
From: grzes@wimbledon.ac.uk
Date: Mon, 5 Apr 2004 23:11:44 +0100
Message-id: <[🔎] 20040405221144.GA9680@wimbledon.ac.uk>
In-reply-to: <[🔎] 1081197021.1738.40.camel@shocker1>
References: <[🔎] 1081197021.1738.40.camel@shocker1>

On Mon, Apr 05, 2004 at 03:30:22PM -0500, Jeff Mitchell wrote:
> my kernel work just fine.
> 
> Can anyone tell me why this is happening?

Did you compiled in support for your filesystem?

Reply to:

Follow-Ups:
- Re: Why do I need mkinitrd with 2.6?
  - From: Mike Chandler <mailmanmike@sbcglobal.net>
- Re: Why do I need mkinitrd with 2.6?
  - From: Jeff Mitchell <jam6@cec.wustl.edu>

References:
- Why do I need mkinitrd with 2.6?
  - From: Jeff Mitchell <jam6@cec.wustl.edu>

Prev by Date: Re: why must Debian call Taiwan a "Province of China"?
Next by Date: apache2 <perl> sections: "*:80 has no VirtualHosts" error
Previous by thread: Why do I need mkinitrd with 2.6?
Next by thread: Re: Why do I need mkinitrd with 2.6?
Index(es):
- Date
- Thread