public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ali Akcaagac <aliakc@web.de>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4/2.6 - ATAPI Zip problem in SCSI mode (DEVFS)
Date: Sun, 31 Aug 2003 19:55:58 +0200	[thread overview]
Message-ID: <1062352558.24793.4.camel@localhost> (raw)
In-Reply-To: <200308312117.42848.arvidjaar@mail.ru>

On Sun, 2003-08-31 at 19:17, Andrey Borzenkov wrote:
> > For 2.5 this doesn't work anymore and whenever you want to mount a Zip
> > disk you need to boot Linux together with a Disk inside the Drive, so
> > during boot it detects the Zip drive + the Disk.
> 
> yes devfs was castrated in 2.6 and removable media revalidation has been 
> removed without providing any suitable replacement.

Ahh, thanks for letting me know this.

But this leads to the question why CD-ROM removable media revalidation
works. I mean let's see an SCSI CD-ROM, an ATAPI CD-ROM (in SCSI mode)
and ATAPI Zip (in SCSI mode) as *the same*.

They all have a host device (the mechanics itself), they all talk
through the same interface (straight SCSI or SCSI emulation). But CD-ROM
removable media revalidation works. E.g. I plug a CD in and it does the
trick, the Zip should be alike in my opinion. How does a Zip as
removable media differ from a CD for example.

By the way it would be pretty nice to improve devfs in this case. I also
heard a while back that it will be re-written anyways. Would be cool to
have a native support for that (Kernel related solution).

greetings,

A. A.


  reply	other threads:[~2003-08-31 17:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-31 17:17 2.4/2.6 - ATAPI Zip problem in SCSI mode (DEVFS) Andrey Borzenkov
2003-08-31 17:55 ` Ali Akcaagac [this message]
2003-08-31 18:37   ` Andrey Borzenkov
  -- strict thread matches above, loose matches on Subject: below --
2003-08-30  3:02 Ali Akcaagac

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=1062352558.24793.4.camel@localhost \
    --to=aliakc@web.de \
    --cc=arvidjaar@mail.ru \
    --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