Alec Muffett wrote:
>>> Mounts under /net are derived from the filesystems actually shared
>>> from the servers; the automount daemon uses the MOUNT protocol to
>>> determine this. If you're looking at a path not already seen, the
>>> information will be fresh, but that's where the good news ends.
>> I know that, yes, but why can't we put such an abstraction
>> elsewhere in
>> the name space? One thing I have always disliked about /net mounts is
>> that they're too magical; it should be possible to replicate them
>> in some form in other mount maps.
> In short, you're proposing a solution to the zillions-of-nfs-exports
> issue, which instead of using "wait for v4 to implement a server-side
> export consolidation" thingy, would instead be a "better, smarter /
> net-alike on v2/v3, but give it a sensible name and better namespace
> I could go for that...
The only problem with this approach is that for current systems you
would have to make sure that all vendors implemented the new scheme in
their automounter and that you could retrospectively add the ability to
old systems still in use which have been orphaned by their vendors.
I don't see that this is likely to be realistically possible.
The only other option, therefore, is to somehow fudge it at the server end.
zfs-discuss mailing list