From: Jeff Dike <jdike@addtoit.com>
To: Paul Wagland <paul@kungfoocoder.org>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Thoughts on HUMFS and metadata
Date: Mon, 19 Apr 2004 16:15:52 -0400 [thread overview]
Message-ID: <200404192015.i3JKFrsP025251@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Mon, 19 Apr 2004 20:42:14 +0200." <46FEF20C-9231-11D8-8B4A-000A95CD704C@kungfoocoder.org>
paul@kungfoocoder.org said:
> Umm, is that actually valid? For example, a normal user cannot read a
> file with "000" permissions, however root can. However, if the
> permissions are stored on the file, then a "000" file cannot even be
> read be root.
Ummm, good point. That needs fixing, as well as the fact that hard links aren't
supported correctly.
> Surely it also makes sense if it is stored in a database? I am not
> sure how else this information can be stored otherwise?
Are you talking about extending the normal unix permissions through humfs,
or supporting this stuff on filesystems that have it?
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-04-19 19:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 7:52 [uml-devel] Thoughts on HUMFS and metadata Paul Wagland
2004-04-19 9:00 ` Henrik Nordstrom
2004-04-19 9:56 ` Henrik Nordstrom
2004-04-19 18:58 ` Jeff Dike
2004-04-19 18:42 ` Paul Wagland
2004-04-19 20:15 ` Jeff Dike [this message]
2004-04-19 19:56 ` Paul Wagland
2004-04-19 21:13 ` Paul Wagland
2004-04-20 0:27 ` Jeff Dike
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=200404192015.i3JKFrsP025251@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=paul@kungfoocoder.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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