[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: "loopback mount" via vnd feature request
On Mar 3, 10:58am, plunky%rya-online.net@localhost (Iain Hibbert) wrote:
-- Subject: Re: "loopback mount" via vnd feature request
| On Mon, 2 Mar 2009, Christos Zoulas wrote:
| > Well we need to fix this at some point. There is the namei cache hack
| > vnode_to_path for now, that will give you a path to the vnode if one
| > exists, but we need to add a more reliable reverse lookup.
| I don't know much about that, but reverse lookup is broken by design is it
| not? (many files can point to the same inode)
So, you choose one path that is accessible by the invoking program if one
| Is it possible for vnconfig to encode the pathname of the file that it has
| configured into the 'boot block' or some such of the vnd? (I vaguely think
| of CD 'title' fields) or provide the file name via a sysctl, or some kind
| of ioctl to recover the name..?
| alternatively, instead of configuring it in a two stage manner as
| currently seems to be required (?)
| # vnconfig vnd0 image.iso
| # mount -t cd9660 /dev/vnd0 /mnt
| make some kind of "vnode" mount option with a cloner device
| # mount -t cd9660 -o vnode /tmp/image.iso /mnt
| so that the configured filename can appear in the mount point?
| # mount
| /tmp/image.iso on /mnt type cd9660 (vnode, rdonly, local)
| (no, I have no idea how to make it work :)
Or you can just accept the inode number in the vnconfig -u command...
Main Index |
Thread Index |