public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David D. Hagood" <wowbagger@sktc.net>
To: Alexandre April <alexandre.april@sympatico.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CD Changer
Date: Mon, 20 Jan 2003 07:28:50 -0600	[thread overview]
Message-ID: <3E2BF992.4030406@sktc.net> (raw)
In-Reply-To: <00da01c2c083$7d70fa00$0500000b@shiva.com>

Alexandre April wrote:
> I'm using kernel 2.4.x and to be able to use that patch I'll have do modify
> some compatibility issue, and I don't have time righht now to to that !

The problem is that Linus did not see fit to make the IDE changer code 
present an IDE changer as multiple block devices, as a SCSI changer is. 
As a result, you cannot mount each disk in the changer seperately - all 
you have is a tool to change which disk is accessed by the single block 
device.

Linus's stated position is that since a disk change takes a fair amount 
of time, in a situation where multiple users are accessing different 
disks the system could thrash between the disks and go nowhere, slowly. 
If you search old LKML posts of about three years ago you should be able 
to find his exact post.

Now, I would dispute the logic, since the SCSI changer behavior is 
identical - I have both a SCSI changer and an IDE changer, and the SCSI 
changer will thrash if multiple processes are accessing different disks. 
Since SCSI does it, I see no reason why IDE cannot be allowed the same 
behavior. However, it's called "Linux" not "Davix"...

However, given that you can buy a 120G drive for US$120 or so, a changer 
has a lot less utility now-a-days. Just buy a cheap hard disk and copy 
the CDs onto it. That way, you have faster access, switch time is 
eliminated, and wear-and-tear on the disks and the changer are eliminated.

You could even DD the disk to a file, and mount that file as an ISO9660 
file system using loopback, thus preserving all the "CD-ishness" of the 
data.

Even if users wish to change disks - you can store a lot of disks in 
120G of storage - just copy the disk over and mount the copy.



  reply	other threads:[~2003-01-20 13:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-19 21:30 CD Changer Alexandre April
2003-01-20  4:28 ` Randy.Dunlap
2003-01-20 12:57   ` Alexandre April
2003-01-20 13:28     ` David D. Hagood [this message]
2003-01-20  7:23 ` Jan-Benedict Glaw
2003-01-20 12:56   ` Alexandre April
2003-01-20 13:19     ` Jan-Benedict Glaw
2003-01-20 13:23       ` Alexandre April
2003-01-20 13:39         ` Markus Plail

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=3E2BF992.4030406@sktc.net \
    --to=wowbagger@sktc.net \
    --cc=alexandre.april@sympatico.ca \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox