From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Linus Torvalds <torvalds@transmeta.com>,
"Stephen C. Tweedie" <sct@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] alternative API for raw devices
Date: Wed, 01 May 2002 17:01:50 -0400 [thread overview]
Message-ID: <3CD057BE.2050603@mandrakesoft.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0205011555450.12640-100000@weyl.math.psu.edu>
Alexander Viro wrote:
>Actual IO code is pretty much copied from old driver. The main differences:
> * device is originally created with ownership/permissions of the
> block device we'd used; you can chmod/chown it at any time,
> obviously.
>
Tangent a little bit to partitions.
Consider a filesystem which creates device nodes for N partitions on a
spindle, "msdos_partition_fs". In a discussion a while back on
permissions, you suggested that inheriting permissions from the base
block device was the wrong way to go, and that (for now) 'uid' and
'gid' mount options were the best route.
Is inheriting permissions coming back into style? Or am I reading too
much into the permissions scheme you describe above?
Jeff
next prev parent reply other threads:[~2002-05-01 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-01 20:12 [PATCH] alternative API for raw devices Alexander Viro
2002-05-01 21:01 ` Jeff Garzik [this message]
2002-05-01 21:44 ` Alexander Viro
2002-05-01 22:52 ` H. Peter Anvin
2002-05-04 22:24 ` Pavel Machek
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=3CD057BE.2050603@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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