mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Shane Nay <shane@agendacomputing.com>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cramfs is ro only, so honour this in inode->mode
Date: Mon, 8 Jan 2001 15:29:04 +0100	[thread overview]
Message-ID: <20010108152904.K10035@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <20010108141702.I10035@nightmaster.csn.tu-chemnitz.de> <0101081213390Z.02165@www.easysolutions.net>
In-Reply-To: <0101081213390Z.02165@www.easysolutions.net>; from shane@agendacomputing.com on Mon, Jan 08, 2001 at 12:13:39PM +0000

On Mon, Jan 08, 2001 at 12:13:39PM +0000, Shane Nay wrote:
> This may not initially seem like such a great thing..., but imagine a base 
> distro being distributed as a cramfs file.  Copy the thing over to your HD 
> and you're done, otherwise the distro packaging has to keep track of 
> permisions for each file, etc.

You can use (GNU-)tar for this. It even keeps track of other bits like
ext2fs attributes, AFAIK.

> On the other hand..., maybe I'm being "selfish", and this is the right way to 
> go. You never write to it, so why track the write bits?

Yes, I would consider this "selfish" ;-)

> (One answer is maybe later we can create a writable cramfs, but
> oh well)

This could then be solved with union mount and cramfs mount over
ramfs or any other writable Unix style fs.

Then we might need W bits, but currently they disturb things like
"test" and the perl equivalent, which is quite annoying and
complexifies code.  (Yes, I'm selfish too ;-))

See what Linus and Al think about this.

Regards

Ingo Oeser
-- 
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
         <<<<<<<<<<<<       come and join the fun       >>>>>>>>>>>>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-08 13:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-08 13:17 Ingo Oeser
2001-01-08 12:13 ` Shane Nay
2001-01-08 14:29   ` Ingo Oeser [this message]
2001-01-08 13:17     ` Shane Nay
2001-01-09 11:16       ` Albert D. Cahalan
2001-01-09 14:14         ` Doug McNaught
2001-01-09 22:03           ` Albert D. Cahalan
2001-01-09 22:33             ` Doug McNaught
2001-01-08 13:42     ` Alexander Viro
2001-01-08 16:59       ` Ingo Oeser
2001-01-08 17:37     ` Linus Torvalds
2001-01-09  1:25       ` Rusty Russell
2001-01-09  2:54         ` Linus Torvalds
2001-01-08 17:12 ` Linus Torvalds

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=20010108152904.K10035@nightmaster.csn.tu-chemnitz.de \
    --to=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shane@agendacomputing.com \
    --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

all inboxes | Powered by JetHome®