> At my college, they've recently installed a small cluster of Red
> Hat 6.0 Linux machines, with, among other things, internal ATAPI
> Zip drives. To let us use these Zip drives, there is a line in
> /etc/fstab along the lines of:
> /dev/hdx4 /zip vfat user,noexec,nosuid 0 0
> This of course, assumes that you haven't messed with your zip
> media, repartitioned it, reformatted it,etc. (I don't know how
> relevant all this is...)
I use the following line with my ATAPI Zip-250 drive:
/dev/hdd4 /zip auto noauto,user 0 0
Note that the 'user' implies noexec and nosuid so those do not need
stating as well. The only difference is the use of 'auto' instead of
'vfat' in the media type field, which allows me to use ext2 and vfat
disks interchangably.
> Anyway, the problem is that when you mount a zip disk and write
> to it, your data gets corrupted. For example, I've been trying
> to download Linux Staroffice, and the first kilobyte or so of
> the tar file gets corrupted (scarily, sometimes it seems to be
> overwritten with a Windoze .EXE header!?!). If I uuencode the
> tar and copy it to zip, I can run the copied file through less,
> page through, and every so often I see data which is obviously
> not uuencoded (i.e. ctrl chars, etc.). This happens on several
> machines in this cluster, with different media. I haven't found
> one where it doesn't happen.
> As far as I can tell, they're running the stock RH6.0 kernel,
> 2.2.5. But before I run to the admin and pester him to do
> cluster-wide kernel upgrades, I have to ask - is this a known
> (and fixed) kernel bug? Or is the problem likely elsewhere? Has
> anyone else even seen this?
The only thing that comes to mind is that the one supplied with RH 6.0
was 2.2.5-15 and there were supposed to be some important changes in
the update that was released as 2.2.5-22 so you may wish to suggest to
them that they upgrade to the later RPM.
Another option would be to upgrade to RH 6.1 which uses 2.2.12 as its
base kernel, and that shouldn't be hard.
The best option of all would be to download the 2.2.13 kernel tarball
and compile a custom kernel for those machines. However, if they've
only just started with Linux, they may be unwilling to do that.
Best wishes from Riley.
PS: The kernel versions page is now back online at the URL below, and
includes separate sublists both for each kernel series, and for
each year of development.
+----------------------------------------------------------------------+
| There is something frustrating about the quality and speed of Linux |
| development, ie., the quality is too high and the speed is too high, |
| in other words, I can implement this XXXX feature, but I bet someone |
| else has already done so and is just about to release their patch. |
+----------------------------------------------------------------------+
* http://www.memalpha.cx/Linux/Kernel/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/