From: Al Boldi <a1426z@gawab.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org,
stable@kernel.org, akpm@osdl.org, chrisw@sous-sol.org,
grim@undead.cc
Subject: Re: [stable] [PATCH] initramfs: Allow rootfs to use tmpfs instead of ramfs
Date: Mon, 31 Jul 2006 00:03:56 +0300 [thread overview]
Message-ID: <200607310003.56832.a1426z@gawab.com> (raw)
In-Reply-To: <20060730175109.GA20777@kroah.com>
Greg KH wrote:
> On Sun, Jul 30, 2006 at 06:08:14PM +0300, Al Boldi wrote:
> > Replugs rootfs to use tmpfs instead of ramfs as a Kconfig option.
> >
> > This patch is based on John Zielinski's
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=107013630212011&w=4
> > patch.
> >
> > Modified for 2.6.17.
> >
> > RunTime tested on i386.
> >
> > This trivial patch should go into 2.6.18.
>
> This looks like a new feature. What problem does it fix that would make
> it acceptable to add to the -stable tree?
Well, ramfs has some pitfalls, which doesn't make it suitable for a
long-lived rootfs. OTOH, tmpfs is much more mature, while semantically the
same.
Being semantically the same, while not exhibiting ramfs pitfalls, makes it
suitable to be pushed into the -stable tree, IMHO.
It's your call, but this patch should have been in 2.6 since day 1.
Thanks!
--
Al
next prev parent reply other threads:[~2006-07-30 21:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 15:08 Al Boldi
2006-07-30 17:36 ` Hugh Dickins
2006-07-30 18:48 ` H. Peter Anvin
2006-07-30 21:03 ` Al Boldi
2006-07-31 19:24 ` H. Peter Anvin
2006-07-31 14:35 ` Rob Landley
2006-07-30 21:03 ` Al Boldi
2006-07-30 17:51 ` [stable] " Greg KH
2006-07-30 21:03 ` Al Boldi [this message]
2006-07-31 19:25 ` H. Peter Anvin
2006-07-31 20:58 ` Al Boldi
2006-07-31 23:20 ` H. Peter Anvin
2006-07-31 19:30 ` Chris Wright
2006-07-31 20:58 ` Al Boldi
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=200607310003.56832.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=greg@kroah.com \
--cc=grim@undead.cc \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@osdl.org \
/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
all inboxes | Powered by JetHome®