mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: xerces8 <xerces8@butn.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: isofs maintainer and write support
Date: Mon, 14 Jan 2008 11:10:32 -0500	[thread overview]
Message-ID: <20080114161032.GN2310@csclub.uwaterloo.ca> (raw)
In-Reply-To: <WorldClient-F200801131428.AA28580079@butn.net>

On Sun, Jan 13, 2008 at 02:28:58PM +0100, xerces8 wrote:
> 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+ :-( )

I find it hard to believe any device that can read a DVD doesn't support
UDF.  That would be a very dumb design choice.

UDF was designed for read/write use.  iso9660 was very much designed for
read only.  It is much more complex to update an iso9660 filesystem
after it is created.  It just wasn't meant for it.

--
Len Sorensen

      parent reply	other threads:[~2008-01-14 16:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-13 13:28 xerces8
2008-01-13 14:32 ` Jan Engelhardt
2008-01-14 16:10 ` Lennart Sorensen [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=20080114161032.GN2310@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xerces8@butn.net \
    /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

all inboxes | Powered by JetHome®