On Fri, Oct 10, 2014 at 09:05:08AM -0600, Stephen Dowdy wrote: > I guess the question i have here is... > is /mnt being *USED* within the install at all, OTHER than by being an > empty sub within the tarchive > payload in the .deb ? Does dpkg, etc use /mnt for temporary > extraction or as part of the postinstall > infrastructure? Because if it doesn't -- making sure it's not in > base-files .deb would solve my problem. > > I don't recall other packages having this blocking issue, but i could > not swear to that. Anyway, > i appreciate you looking at the issue, but if indeed, /mnt is a core > component of debian's installation > infrastructure (which i could argue is a security flaw in the design, > as that directory hierarchy gets littered with > automount garbage), then i will concede on the bug report, and you can > close it, and i will re-iterate > to my fellow sysadmins to not use it for temporary mounts anymore. > > (if you could please respond definitively that /mnt is indeed a core > component/requirement of Debian's > package management, i'd appreciate it)
The /mnt directory is required to "exist" by the FHS, but nothing prevents base-files from creating it in the postinst the very first time base-files is installed (via debootrrap) instead of having it inside the .deb. So I will probably do as you suggest and remove it from the .deb. Please note that the fact that /mnt is actually used by debian-installer or not does not really matter here, because nothing in the target system should be used before debootstrap has finished its job, and then the directory /mnt would exist anyway as it would be created by base-files postinst. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
