Messages in this thread | | | Date | Wed, 10 Apr 1996 13:34:37 -0500 (CDT) | From | "B. Galliart" <> | Subject | supermount and 1.3.8x |
| |
I am curious to know if anyone has ported supermount to one of the newer developmental kernels.
For those that don't know what supermount is, here is the beginning to the readme file for supermount version 0.4a:
Supermount is a pseudo-filesystem which manages filesystems on removable media like floppy disks and CD-ROMs. It aims to make management of removable media as easy as it is under DOS.
With supermount, you can change the disk in the drive whenever you want (with the obvious exception that you shouldn't do it when the filesystem is actively in use). You don't need to "cd" out of the directory first, and you don't need to tell the kernel what you're doing --- supermount will detect the media change automatically. Supermount is a pseudo-filesystem which manages filesystems on removable media like floppy disks and CD-ROMs. It aims to make management of removable media as easy as it is under DOS.
The kernel patches for supermount version 0.4a where written for Linux kernel versions 1.2.13 and 1.3.30. Since 1.3.30 there has been alot of development to add VFAT support to the kernel. This has resulted in several of the files/functions that supermount patches having been being reworked.
So has anyone figured out how to correctly apply the patch to newer developmental kernels? Is there any know problems caused by the patch for the kernels they where intented to work with? Is there any reason that this or a similar filesystem could be offically added to the kernel?
Thanks, Ben Galliart (bgallia@luc.edu)
| |