All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Fairchild <tim@bcs4me.com>
To: linux-kernel@vger.kernel.org
Subject: K3b and 2.6.9?
Date: Mon, 30 Aug 2004 10:47:06 +1000	[thread overview]
Message-ID: <200408301047.06780.tim@bcs4me.com> (raw)


Hi. Sorry for the silly question from a user who can't code their way out of a 
paper bag, but I have compiled 2.6.9-rc1-bk5 and currently running okay (the 
nvidia module will now compile) with no oops so far. But K3B still does not 
work - as with 2.6.8.1. 

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? 

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:

--- a/drivers/block/scsi_ioctl.c        2004-08-30 03:52:08.000000000 +1000
+++ b/drivers/block/scsi_ioctl.c        2004-08-30 09:31:44.955159390 +1000
@@ -220,9 +220,9 @@
                return -EINVAL;
        if (copy_from_user(cmd, hdr->cmdp, hdr->cmd_len))
                return -EFAULT;
-       if (verify_command(file, cmd))
+/*     if (verify_command(file, cmd))
                return -EPERM;
-
+*/
        /*
         * we'll do that later
         */


--tim

             reply	other threads:[~2004-08-30  0:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-30  0:47 Tim Fairchild [this message]
2004-08-30 13:07 ` K3b and 2.6.9? 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

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=200408301047.06780.tim@bcs4me.com \
    --to=tim@bcs4me.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 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.