From: "xerces8" <xerces8@butn.net>
To: linux-kernel@vger.kernel.org
Subject: isofs maintainer and write support
Date: Sun, 13 Jan 2008 14:28:58 +0100 [thread overview]
Message-ID: <WorldClient-F200801131428.AA28580079@butn.net> (raw)
Hi!
I write here as the MAINTAINERS file has no entry about the isofs.
The question is : Is there any plan/way/idea to have read/write support
for isofs ?
I know of user space tools that can perform any operation (like
create/read/write/rename/delete file/directory) but that is nowhere
as convenient as a real filesystem.
Use case: Editing a iso9660 filesystem on a DVD+RW. With a r/w isofs most
changes would take a few seconds, while without, the entire 4.5 gigabytes
must be copied to HD, edited and then remastered back to the DVD medium.
(Why I don't use another FS ? Because I use the DVD to store music for
my car cd/dvd player and it understands only iso9660.)
(neither does it know vorbis. Or aac+ :-( )
Regards,
David Balažic
next reply other threads:[~2008-01-13 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-13 13:28 xerces8 [this message]
2008-01-13 14:32 ` isofs maintainer and write support Jan Engelhardt
2008-01-14 16:10 ` Lennart Sorensen
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=WorldClient-F200801131428.AA28580079@butn.net \
--to=xerces8@butn.net \
--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