[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#267338: kernel-image-2.6.8-1-k7: 2.6.8 broke cdrecord



Package: kernel-image-2.6.8-1-k7
Version: 2.6.8-1
Severity: important
Tags: sid

Thanks for maintaining debian's kernel packages.

You're important.

The main reason that I'm writing is that it seems
version 2.6.8 of the kernel has broken cdrecord.

http://k3b.org/ elaborates:

    "Do not use Kernel 2.6.8

    A patch that was introduced into the kernel
    shortly before the 2.6.8 release makes K3b and
    also the dvd+rw-tools unusable on Linux (unless
    run as root but that is not recommended). The very
    important GET CONFIGURATION MMC command is
    rejected by the kernel for reasons I cannot see
    and writing commands like MODE SELECT also fail
    (K3b cannot detect CD writers without it) even
    when the device is opened O_RDWR. Until this issue
    has been solved I strongly recommend to stick to
    kernel version 2.6.7. 

    Update: The kernel guys are currently fixing
    the problem so the next kernel release should
    work again. :) 

    Update 2: The problem is NOT fixed in 2.6.8.1"

Someone on #debian said:

    "afaict, the old way that cdrecord worked was
    actually a security hole that could also allow
    a user to wipe the drive's firmware or other
    nasties

    when the hole was closed in kernel 2.6.8, it
    broke cdrecord

    now there's a nasty debate on who is the one
    who needs to patch to fix"

Thanks,
Kingsley

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-k7
Locale: LANG=C, LC_CTYPE=C

Versions of packages kernel-image-2.6.8-1-k7 depends on:
ii  coreutils [fileutils]         5.0.91-2   The GNU core utilities
ii  fileutils                     4.5.1-2    GNU file management utilities
ii  initrd-tools                  0.1.73     tools to create initrd image for p
ii  module-init-tools             3.1-pre5-3 tools for managing Linux kernel mo

-- no debconf information





Reply to: