[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Automounting filesystems in partman

Joey Hess schrieb:

Colin Watson wrote:

    - Can trigger bugs / unwanted modifications in journalling
      filesystems, e.g. Linux XFS has problems mounting Irix XFS (ths).
      vorlon asked whether that could be addressed by mounting
      read-only, but apparently that still tries to replay the journal.


This seems like a good reason to not automount preexisting XFS
filesystems at all. Luckily it's rare that a desktop system needs to
mount XFS filesystems from another OS to operate well. By contrast a
desktop system does need to make available .doc files from your old
windows OS to work well.
Does it really hurt the Irix XFS filesystem if you try to mount it from Linux? In my experience it simply fails but doesn't harm the Irix filesystem. So there should probably be a check to see if we can mount the filessystem. 




    - Security / confusion issues caused by mounting partitions with
      different access control policies or different uid/gid mappings
      (fjp).


Access control policies shouldn't matter too much on a desktop system,
but nosuid and nodev would still be reasonable mount flags for relevant
filesystems.

I think the most common case is a NTFS filesystem, where uid/gid mapping
shouldn't matter, since it ought to be mounted so the desktop user owns
the files.
As I understand Kamions patch, the filesystems are mounted from fstab on system boot. Probably it would be better to mark the filesystems where an uid/gid mapping is not possible as "user" an mount them after login. Else the user does not really benefit from FAT/NTFS partitions automatically mounted in /media because he can't access the files.
Another possiblity is to mount them with umask=0, so that all users can access the files. 

Gaudenz
Reply to: