From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Fedin Subject: Question about "mount" command (continued) Date: Tue, 09 Aug 2005 11:00:02 +0400 Message-ID: <42F85472.8090402@rambler.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mxb.rambler.ru ([81.19.66.30]:10501 "EHLO mxb.rambler.ru") by vger.kernel.org with ESMTP id S932226AbVHIHAC (ORCPT ); Tue, 9 Aug 2005 03:00:02 -0400 Received: from mailc.rambler.ru (mailc.rambler.ru [81.19.66.27]) by mxb.rambler.ru (Postfix) with ESMTP id CD48984620 for ; Tue, 9 Aug 2005 10:59:59 +0400 (MSD) Received: from [81.9.51.85] ([81.9.51.85]) (authenticated bits=0) by mailc.rambler.ru (8.12.10/8.12.10) with ESMTP id j796xmev009988 for ; Tue, 9 Aug 2005 10:59:59 +0400 (MSD) To: linux-fsdevel@vger.kernel.org Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hello there! I moved to a new job so my old email archive is lost. I can't quote the whole discussion, here is an original letter (found in the list archive): --- cut --- Also i would like to ask someone who is responsible for "mount" tool. I'd suggest to modify it in order to support several lines in fstab with the same device and mount points but different filesystems and options. For example: /dev/cdrom /mnt/cdrom udf,iso9660 user,noauto,iocharset=koi8-r 0 0 /dev/cdrom /mnt/cdrom hfsplus user,noauto,nls=koi8-r 0 0 /dev/cdrom /mnt/cdrom hfs user,noauto,iocharset=koi8-r,codepage=10007 0 0 Currently mount will stop at the first line and produce an error if the filesystem is not udf or iso (in the example). It will ignore the following lines. This would greatly improve handling of removable devices. Is there something (standards for example) which could prevent from this implementation? --- cut --- There was a suggestion to unify all the arguments in order to be able to write something like: /dev/cdrom /mnt/cdrom hfsplus,hfs,udf,iso9660 user,noauto,iocharset=koi8-r,codepage=10007 0 0 But there is one flaw. Let's take a floppy drive as an example, where Mac or Windows diskettes can be read. We could write: /dev/floppy /mnt/floppy hfs,vfat user,noauto,iocharset=koi8-r,codepage=10007 0 0 But there is a problem. Mac diskettes use different codepage from Windows diskettes (they use 866). This leads to a problem. So the solution could be to write two lines instead of one: /dev/floppy /mnt/floppy vfat user,noauto,iocharset=koi8-r,codepage=866 0 0 /dev/floppy /mnt/floppy hfs user,noauto,iocharset=koi8-r,codepage=10007 0 0 Also i would suggest to change argument parsing policy for filesystems a bit. I suggest to silently ignore unknown arguments instead of producing an error. This would make autofs much more usable (i would be able to specify the whole set of needed arguments for all possible filesystems). For example something like: /dev/hdd4 /mnt/zip ext2fs,vfat user,noauto,iocharset=koi8-r,codepage=866 0 0 will not work when ext2 cartridge is inserted because ext2fs doesn't understand "iocharset" and "codepage" and will give an error. Removing these two options produces disadvantage when reading FAT cartridge. This would also fix problem with "user,noauto" for smbfs automatically (i presented the patch earlier but it was rejected because "there's no need to pollute the kernel with dummy arguments, smbmount should be fixed instead"). Kind regards