Re: mount --move broken

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

 



On 5 Dec 2010, Jakob Unterwurzacher told this:

> Am 05.12.2010 21:49, schrieb Nix:
>> I can probably get away with it by mounting a size-zero tmpfs over the
>> original mount point after the bind operation. But, still, ew.
>
> If you are *not* dealing with mountpoints, isn't renaming the directory
> enough?

Not if you're renaming across filesystem boundaries it's not (to a point
under a filesystem that doesn't have remotely enough space to allow
putting it on that fs instead).

This is the sort of thing people used to use symlinks to .-named
directories in other filesystems for: I was hoping I could use mount
--move instead, but it looks like mount --bind of a .-named directory
will have to do. (In practice it'll do perfectly well, but it still
seems less flexible than I thought Linux was.)
--
To unsubscribe from this list: send the line "unsubscribe util-linux" 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