From: Rene Herman <rene.herman@keyaccess.nl>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: Linus Torvalds <torvalds@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] removal of legacy cdrom drivers (Re: [PATCH] mcdx.c insanity removal)
Date: Mon, 03 May 2004 05:21:07 +0200 [thread overview]
Message-ID: <4095BAA3.3050000@keyaccess.nl> (raw)
In-Reply-To: <20040503011629.GY17014@parcelfarce.linux.theplanet.co.uk>
viro@parcelfarce.linux.theplanet.co.uk wrote:
> Aiiee...
>
> You know, mcdx.c is like a roadkill - just can't stop looking at the thing.
You should try sbpcd.c. I very enthousiastically opened that up one day,
thinking it might be a nice little newbie project, then after 30 seconds
gently closed it again and logged out and in of X to make very sure all
traces of the terminal that showed it were gone.
But...
> How about removing all that stuff instead of keeping the known broken shit
> in the tree?
I do actually still use two of these drives. An actual soundblaster
connected "sbpcd" drive (which sits in a 386, and given the fact that
the new init-module-tools didn't compile against libc5 I haven't tested
it modular there yet -- builtin it doesn't work) and a "Pro Audio
Spectrum" connected "cdu31a" which does work. Most of the time. When the
timing is just right, it even allows me to mount cd-roms:
root@5vd5:~# uname -r
2.6.5
root@5vd5:~# lsmod | grep cdu31a
cdu31a 24944 1
cdrom 34112 1 cdu31a
root@5vd5:~# mount | grep cdrom
/dev/sonycd on /mnt/cdrom type iso9660 (ro,noexec,nosuid,nodev,check=r)
root@5vd5:~# ls /mnt/cdrom/
cd.id install.exe lecdemos readme.doc resource support
> If you are OK with that (and nobody on l-k stands up and claims that they want
> it alive and *claims* *that* *right* *fucking* *NOW*) I'll send you a patch
> putting these buggers out of their misery.
Hope this qualifies a bit. Must say that one of the things I appreciate
about Linux is that all this old gunk I have lying about (in fact, still
drag in from time to time) is actually supported. Or "supported".
Would it be good to have a CONFIG_LEGACY alongside CONFIG_EXPERIMENTAL
and friends and dump all this crap into drivers/legacy/cdrom, where it
wouldn't distract serious people?
Rene.
next prev parent reply other threads:[~2004-05-03 3:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040502024637.GV17014@parcelfarce.linux.theplanet.co.uk>
[not found] ` <Pine.LNX.4.58.0405011953140.18014@ppc970.osdl.org>
2004-05-03 1:16 ` [RFC] removal of legacy cdrom drivers (Re: [PATCH] mcdx.c insanity removal) viro
2004-05-03 3:21 ` Rene Herman [this message]
2004-05-03 5:59 ` viro
2004-05-03 18:08 ` Rene Herman
2004-05-03 19:45 ` viro
2004-05-03 21:22 ` Rene Herman
2004-05-03 21:30 ` Linus Torvalds
2004-05-03 21:34 ` viro
2004-05-05 23:41 ` Adrian Bunk
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=4095BAA3.3050000@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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