Re: fstab record dependencies

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

 



On Sun, Jun 03, 2007 at 06:04:24PM +0300, Szabolcs Szakacsits wrote:
> One typical, wrongly edited fstab example is:
> 
>   /dev/hda2 /             ext3      defaults  1 1
>   /dev/hda1 /mnt/windows  ntfs-3g   defaults  0 0
>   /dev/hda3 /usr          ext3      defaults  0 0
> 
> The events:
> 
>   mount  ->  /sbin/mount.ntfs-3g  ->  
>          ->  resolves to <path1>/ntfs-3g via a symlink ->
>          ->  ntfs-3g requires at least <path2>/libfuse* 
> 
> If <path1> and <path2> aren't mounted yet (almost always under /usr or 
> /usr/local) then ntfs-3g mount fails.
> 
> There are many potential solutions. For example installing everything on 
> the root file system which may be needed for successful mount. But this 
> is not always feasible or practical since we could end up putting almost 
> everything on the root file system in the end.
> 
> Another idea is an improved mount strategy:
> 
>   do {
>         try to mount all unmounted entries
>   } while (not all mounted && at least one new was successfully mounted)
> 
> This would take care about the dependencies and mount as many file systems 
> as possible.
> 
> What do you think?

 Frankly, I'm not a big fan of this kind of changes. I don't think
 that we have to keep Linux users stupid and uneducated.

 Well, I'll add this request to the TODO file for the next release
 (2.14).

 Thanks,

    Karel

-- 
 Karel Zak  <kzak@xxxxxxxxxx>
-
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux