All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Tim Fairchild <tim@bcs4me.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: K3b and 2.6.9?
Date: Mon, 30 Aug 2004 14:07:59 +0100	[thread overview]
Message-ID: <1093871277.30082.7.camel@localhost.localdomain> (raw)
In-Reply-To: <200408301047.06780.tim@bcs4me.com>

On Llu, 2004-08-30 at 01:47, Tim Fairchild wrote:
> Am I right in assuming that this is the way things will be done in the kernel 
> from now on and that we will need new versions of k3b/cdrecord to run with 
> these newer kernels? 

Folks are working on getting the verify_command list refined, or you 
can run the burner part of cd-burners setuid (as cdrecord supports -
although get the newest one since there was a security hole fixed a few
days ago in both cdrecord and star).

> Without knowing a better way, I am currently using the same sort of quick 
> patch as 2.6.8.1 to use k3b on 2.6.9-rc1-bk5 ie:

Providing you don't mind any of your users erasing your drive firmware
and turning the drive into a brick its fine. 


  reply	other threads:[~2004-08-30 14:10 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 [this message]
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

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=1093871277.30082.7.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim@bcs4me.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.