From: Stephen Hemminger <shemminger@osdl.org>
To: Andrew Morton <akpm@digeo.com>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: Recent changes broke mkinitrd?
Date: Thu, 17 Apr 2003 12:58:11 -0700 [thread overview]
Message-ID: <20030417125811.42e5a769.shemminger@osdl.org> (raw)
In-Reply-To: <20030417114016.6b7074f1.akpm@digeo.com>
On Thu, 17 Apr 2003 11:40:16 -0700
Andrew Morton <akpm@digeo.com> wrote:
> Stephen Hemminger <shemminger@osdl.org> wrote:
> >
> > Recent (post 2.5.67) versions of the kernel break the creation
> > of the initial ram disk.
>
> hmm, so it did. It'll be the ext2 changes. mkinitrd works OK if you use
> ext3:
That works for me - Thanks
next prev parent reply other threads:[~2003-04-17 19:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 18:13 Recent changes broke mkinitrd? Stephen Hemminger
2003-04-17 18:40 ` Andrew Morton
2003-04-17 19:58 ` Stephen Hemminger [this message]
2003-04-17 19:21 ` [patch] Fix orlov allocator boundary case Andrew Morton
2003-04-17 20:25 ` Stephen Hemminger
2003-04-17 21:27 ` Marc-Christian Petersen
2003-04-17 21:57 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030417125811.42e5a769.shemminger@osdl.org \
--to=shemminger@osdl.org \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).