public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kent Robotti <dwilson24@nyc.rr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Initramfs and TMPFS!
Date: Sat, 27 Aug 2005 08:19:18 +0000	[thread overview]
Message-ID: <20050827081918.GA963@Linux.nyc.rr.com> (raw)

   On Fri Aug 26 2005 - 05:33:43 EST, Erik Mouw wrote:
   > I prefer tar because I have more experience with it, and it works.
   >> The kernel people prefer cpio because they have experience with it, it
   >> doesn't need too much code, and it works.
   
I know that experience dosen't come from packing the kernel source,
or the zillion other tar archives on the internet.
   
   > It seems to be the most used archiver in the UNIX world.
   >> You've been told that there are *technical* reasons not to use tar in
   >> the kernel. The kernel developers never cared about what was most used
   >> or what "the market wants", but only about what was *technically*
   >> useful.

I haven't been told that.
   
   >>Did you ever take some time to actually *understand* what ramfs is,
   >>*why* it is used for initramfs, and why you can't use any filesystem
   >>you like for an initramfs?
   
You can use tmpfs and that's sufficient.

You only need one initramfs and it should be tmpfs, but if you
have two make ramfs a little more robust (that word again!).

This is a definition of robust I found on the web:
   Refers to software without bugs that handles abnormal conditions well.
   It is often  said that there is no software package totally bug free.
   Any program can exhibit odd behavior under certain conditions, but a
   robust program will not *lock up* the computer, cause damage to data or
   send the user through an endless chain of dialog boxes without
   purpose.  Whether or not a program can be totally bug free will be
   debated forever.

I'm sure if I gave ramfs a chance it would fit that definition to a tee.
    
   > For one, if you do "dd if=/dev/zero of=foo" on a ramfs the system
   > will lock up.
   >> "Doctor, it hurts when I do this!" "Well, then don't do that."
   >> You found a nice case of "Unix, rope, foot".

I guess you graduated from the Henny Youngman school of coding, the same
school the author of ramfs graduated from.

But seriously, you're obviously a coder/comedian and I hope you don't
confuse the two.

If Windows had that defeatest philosophy where would it be?

Ramfs has a more limited use than tmpfs and that may be sufficient,
because people know its limitations and stay within them, but
that's no reason to pat yourself on the back.

   >>PS: I'm not going to hunt through my linux-kernel mailbox for replies
   >>without proper In-Reply-To and References headers in the hope that I
   >>stumble over a possible reply from you. Any reply without such
   >>headers will most probably not been seen and just ignored.
   
You have to Cc me if you want that.

             reply	other threads:[~2005-08-27  8:10 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-27  8:19 Kent Robotti [this message]
2005-08-27 21:28 ` Initramfs and TMPFS! Chris Wedgwood
2005-08-27 21:42   ` Lee Revell
2005-08-27 22:45   ` Kent Robotti
2005-08-27 22:42     ` David Weinehall
2005-08-27 22:57     ` Patrick McFarland
2005-08-27 23:38     ` Chris Wedgwood
2005-08-27 23:41   ` Alistair John Strachan
2005-08-28  0:21     ` Patrick McFarland
2005-08-28  5:36     ` Willy Tarreau
  -- strict thread matches above, loose matches on Subject: below --
2005-09-03  8:29 Chuck Ebbert
     [not found] <4Fuuy-6df-11@gated-at.bofh.it>
     [not found] ` <4FJMZ-1YX-17@gated-at.bofh.it>
2005-08-26 15:49   ` Bodo Eggert
2005-08-26  6:09 Kent Robotti
2005-08-26  1:39 dwilson24
2005-08-26 19:06 ` Chris Wedgwood
2005-08-26 20:08   ` Kent Robotti
2005-08-26 20:22     ` Chris Wedgwood
2005-08-26 21:34       ` Kent Robotti
     [not found]       ` <20050826211231.GA957@Linux.nyc.rr.com>
     [not found]         ` <20050827004045.GA17686@taniwha.stupidest.org>
2005-08-27  3:21           ` Kent Robotti
2005-08-27  4:11             ` Chris Wedgwood
2005-08-25 19:32 dwilson24
2005-08-25 19:05 Alan Jenkins
2005-08-26 10:37 ` Erik Mouw
2005-08-26 19:08 ` Chris Wedgwood
2005-08-25 18:23 robotti
2005-08-25 18:15 robotti
2005-08-25 19:10 ` Ian Campbell
2005-08-26 10:29 ` Erik Mouw
2005-08-25 15:38 robotti
2005-08-25 16:00 ` Erik Mouw
2005-08-26 19:10 ` Chris Wedgwood
2005-08-25 15:34 robotti
2005-08-25 15:54 ` Erik Mouw
2005-08-26 15:03 ` Horst von Brand
2005-08-25  4:35 robotti
2005-08-25 13:49 ` Chris Wedgwood
2005-08-25  4:32 robotti
2005-08-25 13:47 ` Chris Wedgwood
2005-08-24 22:41 robotti
2005-08-25  3:12 ` Chris Wedgwood
2005-08-24  3:15 robotti
2005-08-23 22:05 robotti
2005-08-24  2:57 ` Chris Wedgwood
2005-08-24 20:52   ` Wakko Warner
2005-08-24 20:59     ` Chris Wedgwood
2005-08-23 21:16 robotti
2005-08-23 21:24 ` Olivier Galibert
2005-08-25  3:14 ` Chris Wedgwood

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=20050827081918.GA963@Linux.nyc.rr.com \
    --to=dwilson24@nyc.rr.com \
    --cc=linux-kernel@vger.kernel.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