From: cacook@freedom.net
To: Jens Axboe <axboe@suse.de>
Cc: Ben Fennema <bfennema@ix.netcom.com>, linux-kernel@vger.kernel.org
Subject: Re: write to dvd ram
Date: Tue, 08 May 2001 12:11:26 -0600 [thread overview]
Message-ID: <20010508181158Z133062-406+575@vger.kernel.org> (raw)
In-Reply-To: <91FD33983070D21188A10008C728176C09421202@LDMS6003> <20010508145400Z132655-406+505@vger.kernel.org> <20010508100129.19740@dragon.linux.ix.netcom.com> <20010508195030.J505@suse.de>
Thanks, I'll try it. Didn't get the prior response.
--
C.
The best way out is always through.
- Robert Frost A Servant to Servants, 1914
Jens Axboe wrote:
> On Tue, May 08 2001, Ben Fennema wrote:
> > > The log is:
> > > Apr 15 20:58:27 hydra kernel: UDF-fs INFO UDF 0.9.1 (2000/02/29) Mounting
> > > volume 'UDF Volume', timestamp 2001/03/02 11:55 (1e98)
> >
> > At the very least, run 0.9.3 from sourceforce (or the cvs version) and
> > see if it works any better.
>
> I was just about to say the same thing, 0.9.3 works well for me. In fact
> so well, that I made a patch to bring 2.4.5-pre1 UDF up to date with
> current CVS earlier this afternoon (hint hint, Ben :-).
>
> *.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.5-pre1/
>
> udf-0.9.3-2.4.5p1-1.bz2
>
> --
> Jens Axboe
next prev parent reply other threads:[~2001-05-08 18:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <91FD33983070D21188A10008C728176C09421202@LDMS6003>
2001-05-08 14:53 ` write to dvd ram cacook
2001-05-08 17:01 ` Ben Fennema
2001-05-08 17:50 ` Jens Axboe
2001-05-08 18:11 ` cacook [this message]
2001-05-08 18:59 ` Thiago Vinhas de Moraes
2001-05-08 19:10 ` Jens Axboe
2001-05-11 13:57 ` cacook
2001-05-11 12:32 ` 2.2.19 Crash Help, please Collectively Unconscious
2001-05-11 16:47 ` Erik Mouw
2001-05-11 15:09 ` Collectively Unconscious
2001-05-15 16:32 write to dvd ram cacook
2001-05-22 16:38 quantum7
2001-05-22 16:38 cacook
2001-05-22 17:38 ` David Weinehall
2001-05-22 23:18 ` Rafael Herrera
2001-05-23 9:34 ` Helge Hafting
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=20010508181158Z133062-406+575@vger.kernel.org \
--to=cacook@freedom.net \
--cc=axboe@suse.de \
--cc=bfennema@ix.netcom.com \
--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).