From: Tim Fairchild <tim@bcs4me.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: "ismail dönmez" <ismail.donmez@gmail.com>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: K3b and 2.6.9?
Date: Wed, 1 Sep 2004 18:27:42 +1000 [thread overview]
Message-ID: <200409011827.42576.tim@bcs4me.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0408311332410.2295@ppc970.osdl.org>
On Wednesday 01 Sep 2004 06:33, Linus Torvalds wrote:
> On Tue, 31 Aug 2004, ismail dönmez wrote:
> > Checked k3b on CVS and it does this now :
> >
> > int flags = O_NONBLOCK;
> > if( write )
> > flags |= O_RDWR;
> > else
> > flags |= O_RDONLY;
> > .....
> > fd = ::open( name, flags );
> >
> > which already fixes the issue. Right?
>
> I assume so, assuming that the "write" flag is set correctly. Somebody
> would need to test whether it actually works for them ;)
I can't seem to easily get the cvs to compile on my box at the moment, but
making these changes to the k3b-0.11.14 code seems to be working here, tho
k3b seems to always open as write now. Haven't looked at latest dvd+rw-tools
but they would be similar I guess...
tim
prev parent reply other threads:[~2004-09-01 8:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 0:47 K3b and 2.6.9? Tim Fairchild
2004-08-30 13:07 ` Alan Cox
2004-08-31 1:51 ` Tim Fairchild
2004-08-31 2:29 ` Linus Torvalds
2004-08-31 6:26 ` Frank Steiner
2004-08-31 16:29 ` Linus Torvalds
2004-08-31 10:37 ` Tim Fairchild
2004-08-31 17:05 ` Linus Torvalds
2004-09-01 8:37 ` Tim Fairchild
2004-08-31 20:16 ` ismail dönmez
2004-08-31 20:33 ` Linus Torvalds
2004-08-31 22:01 ` Tim Fairchild
2004-09-01 8:27 ` Tim Fairchild [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=200409011827.42576.tim@bcs4me.com \
--to=tim@bcs4me.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ismail.donmez@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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