From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: linux-kernel@vger.kernel.org
Subject: [RFC] ioctl vs xattr for the filesystem specific attributes
Date: Sun, 10 Aug 2003 00:49:59 +0900 [thread overview]
Message-ID: <8765l67rvc.fsf@devron.myhome.or.jp> (raw)
Hi,
Bastien Roucaries <roucariesbastien@yahoo.fr> writes:
> This patch implement an "extended attributes" (XATTR) hook in aim to read or
> modify specific fatfs flags' like ARCHIVE or SYSTEM.
>
> I believe it's a good idea because :
> - PAX ( GNU replacement of tar) save and restore XATTRs, so you can make more
> exact save of FATfs without use of specific programs.
> - It's an elegant means to avoid use of mattrib.
> - Samba can use this .
> but CONS :
> - use 2 Kb of kernel memory.
Bastien Roucaries <roucariesbastien@yahoo.fr> writes:
> Indeed some flags are shared by many namespace for instance immutable is
> shared by xfs,ext2/3,jfs and by the fat ( with a special mount option).
> Compress also is a very common flag
> This flags are in the "common" sub-namespace.
>
> But some are fs specifics for instance notail attr of reiserfs,shortname of
> fat.They are in the the "spec"sub-namespace
I received the above email.
This read/modify the file attributes of filesystem specific via xattr
interface (in this case, ARCHIVE, SYSTEM, HIDDEN flags of fatfs).
Yes, also we can provide it via ioctl like ext2/ext3 does now.
But if those flags provides by xattr interfaces and via one namespace
prefix, I guess the app can save/restore easy without dependency of
one fs.
Which interface would we use for attributes of filesystem specific?
Also if we use xattr, what namepace prefix should be used?
Any idea?
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next reply other threads:[~2003-08-09 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-09 15:49 OGAWA Hirofumi [this message]
2003-08-17 18:14 ` [RFC] ioctl vs xattr for the filesystem specific attributes Rob North
2003-08-18 0:13 ` jw schultz
2003-08-18 15:00 ` OGAWA Hirofumi
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=8765l67rvc.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--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;
as well as URLs for NNTP newsgroup(s).