From: Paul Bristow <paul@paulbristow.net>
To: Borsenkow Andrej <Andrej.Borsenkow@mow.siemens.ru>
Cc: Richard Gooch <rgooch@ras.ucalgary.ca>, linux-kernel@vger.kernel.org
Subject: Re: ide-floppy.c vs devfs
Date: Tue, 27 Nov 2001 18:47:03 +0100 [thread overview]
Message-ID: <3C03D197.7050605@paulbristow.net> (raw)
In-Reply-To: <000601c1773f$d80d9ba0$21c9ca95@mow.siemens.ru>
Borsenkow Andrej wrote:
>>This is made somewhat more complicated by the fact that ide-floppy
>>
> disks
>
>>can use either the whole disk, with no partition table or, more
>>commonly, partition4. So a user-friendly solution would be to create
>>
> a
>
>>floppy node that pointed to the partition, if it existed, or the whole
>>disk if it didn't. With appropriate code to handle that fact that
>>anyone can partition these disks in any way they like.
>>
>>
>
> Where's the problem? Use .../disc for whole disc or .../part4 for
> "normal" access. (Or /dev/hdc and /dev/hdc4 if you prefer) It is nice if
> partition code can detect it but it is not ide-floppy driver problem.
Just wondering if we should be clever for the users here. Maybe I
should leave that to user-space tools? Or is there anything in devfs
that can take care of this? The nice solution for end-users might be
a /dev/idefloppy that is a symlink to the relevant node in the
/dev/ide... tree.
>>Note this doesn't take account of the nice ATAPI command that sets the
>>disk into "ignore track 0" mode, making a partition 4 look like an
>>entire floppy with 1 less track.
>>
>>
>
> Why complicate things more than needed?
Because you can boot from a zip or ls-120 drive, with the BIOS setting
it to this mode. There are disks out there that are unreadable unless
you ignore track zero, by formatting them in a PC like this.
>>Anyone up to telling me how this is handled in the SCSI layer?
>>
>>
>
> When I boot without media in Jaz drive I get something like "no media
> inserted, assuming 1GB 512B per sector". Actually I modeled my patch
> from this - use some default values reported by drive when no media
> currently exists.
OK. This makes the most sense here. I'm happy to go with this.
I'll dig out your patch - discovered I was on holiday when you
originally submitted it - and code and test something over the next day
or so. Thanks for the help
> -andrej
--
Paul
Email:
paul@paulbristow.net
Web:
http://paulbristow.net
ICQ:
11965223
next prev parent reply other threads:[~2001-11-27 17:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 10:04 ide-floppy.c vs devfs Borsenkow Andrej
2001-11-26 17:44 ` Paul Bristow
2001-11-27 12:34 ` Borsenkow Andrej
2001-11-27 17:47 ` Paul Bristow [this message]
2001-11-27 20:38 ` Mike Fedyk
2001-11-28 18:36 ` [PATCH] ide-floppy real devfs support for testing Paul Bristow
-- strict thread matches above, loose matches on Subject: below --
2001-11-12 6:48 ide-floppy.c vs devfs Borsenkow Andrej
2001-11-11 4:39 Jack Howarth
2001-11-23 5:13 ` Richard Gooch
2001-11-25 22:07 ` Paul Bristow
2001-11-25 22:31 ` Richard Gooch
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=3C03D197.7050605@paulbristow.net \
--to=paul@paulbristow.net \
--cc=Andrej.Borsenkow@mow.siemens.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
/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