Messages in this thread |  | | Date | Tue, 27 Nov 2001 12:38:04 -0800 | From | Mike Fedyk <> | Subject | Re: ide-floppy.c vs devfs |
| |
On Tue, Nov 27, 2001 at 06:47:03PM +0100, Paul Bristow wrote: > > > 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. >
Can't devfsd be configured to do something like this?
> >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. >
If that's what is required to boot from ls-120 and zip, then it probably needs to be in kernel space.
MF - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |