From: Erik Meusel <meusel@codixx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Ext2/3 uid/gid support
Date: Mon, 11 Mar 2002 10:22:33 +0100 [thread overview]
Message-ID: <02031110223301.00601@huschki> (raw)
In-Reply-To: <E16j1Z6-0002xf-00@the-village.bc.nu> <02031109444400.00601@huschki> <20020311084741.GC311@matchmail.com>
In-Reply-To: <20020311084741.GC311@matchmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 810 bytes --]
Am Montag, 11. März 2002 09:47 schrieb Mike Fedyk:
> On Mon, Mar 11, 2002 at 09:44:44AM +0100, Erik Meusel wrote:
> > Hi.
> >
> > Just one little question:
> >
> > Why do ext2 and ext3 not support mount options uid and gid as all the
> > other filesystems do?
>
> because they have uid and gid within the filesystem itself for directories,
> files, pipes, etc stored in the inodes of the fs. Same with any other
> posix filesystem (which vfat, iso9660(not counting rockridge), hfs, etc are
> *not*).
Sure.
The reason why I ask is, I have two linux stations and I want to use ext2
for the floppy disks to save space for fat vfat and so on. Now it would
be nice to automatically mount my floppies with group "floppy", so that
all the users, belonging to group "floppy", can read/write from/to disk.
mfg, Erik
next prev parent reply other threads:[~2002-03-11 9:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-02 12:07 Linux 2.2.21pre2 Alan Cox
2002-03-07 16:05 ` [OOPS] Linux 2.2.21pre[23] Luca Montecchiani
2002-03-07 16:23 ` Alan Cox
2002-03-07 16:17 ` Dave Jones
2002-03-07 16:29 ` Luca Montecchiani
2002-03-07 16:39 ` Dave Jones
2002-03-07 17:06 ` Luca Montecchiani
2002-03-07 17:11 ` Dave Jones
2002-03-07 17:26 ` SOLVED " Luca Montecchiani
2002-03-07 17:20 ` Alan Cox
2002-03-11 8:44 ` Ext2/3 uid/gid support Erik Meusel
2002-03-11 8:47 ` Mike Fedyk
2002-03-11 9:22 ` Erik Meusel [this message]
2002-03-11 15:21 ` Matthias Andree
2002-03-11 16:44 ` Andreas Dilger
2002-03-12 1:48 ` Andrew Hatfield
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=02031110223301.00601@huschki \
--to=meusel@codixx.de \
--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