From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: jw schultz <jw@pegasys.ws>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] ioctl vs xattr for the filesystem specific attributes
Date: Tue, 19 Aug 2003 00:00:53 +0900 [thread overview]
Message-ID: <87n0e7xb6i.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <20030818001310.GA10453@pegasys.ws>
jw schultz <jw@pegasys.ws> writes:
> > >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?
> I suggested something like this to Andreas Gruenbacher in
> March. We dialoged briefly about it and I've heard nothing
> since.
> > I like the ideas that the patch seems to propose.
> > Infact I'd like to see the use of xattr used for non-standard attributes
> > applied to all fs.
> > Specifically, I want to backup all partitions, and attribs from one OS:
> > Linux. I do not want to loose fat attributes during backup.
> > This would also be useful for the Wine developers.
I think, at least we are agreed that xattr interface would be good for
the following operation.
# ls /mnt
resierfs_mnt ext2_mnt vfat_mnt foo_mnt bar_mnt
# archiver --create --file /backup/file_has_all_data /mnt
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
prev parent reply other threads:[~2003-08-18 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-09 15:49 [RFC] ioctl vs xattr for the filesystem specific attributes OGAWA Hirofumi
2003-08-17 18:14 ` Rob North
2003-08-18 0:13 ` jw schultz
2003-08-18 15:00 ` OGAWA Hirofumi [this message]
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=87n0e7xb6i.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=jw@pegasys.ws \
--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