On 30 Jun 2000, Thomas Bushnell, BSG wrote: > Dale Scheetz <[EMAIL PROTECTED]> writes: > > > And I was suggesting none of that. Existing practice in Debian (and > > something similar is done in all other "installers" I have seen) is to use > > /var/lib/dpkg/methods/mnt as the temporary mount point for a CD > > installation. The CD is only mounted when needed by dselect, which allows > > newer multi-CD installation methods to swap CDs during installation. > > > > I was suggesting that something like: > > > > /var/lib/<package/vendor name>/<some mount point>/ > > > > would make a suitable temporary mount point for third party software, as > > it seems to be used now as the method for distros to do volatile mounts. > > > > Is there some reason you have yet to voice that makes this a bad answer > > to the question? > > Third party software which wants to make files for its own temporary > use is supposed to use /tmp.
While I see your point, I don't think that files are quite the same thing as mount points. I understand that both make use of filesystem nodes, but they are each quite different. > > So I would suggest that programs should created directories in /tmp, > and mount there. > Now we seem to be getting back into "design mode", which we said we didn't want to do. Your suggestion seems to be asking for a change in current practice, as many distro's package managers already use /var/lib/<something>/ for their temporary/volatile mount points. Would your idea of specifying /tmp/<something> require that these packages move there mount points to /tmp? Why would this be a good idea? Luck, Dwarf
