Summary: | Please support specifying SquashFS image as 'location' of a repository | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Michał Górny <mgorny> |
Component: | Conceptual/Abstract Ideas | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | esigra, martin |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 240187 |
Description
Michał Górny
2014-01-23 18:40:36 UTC
I am not sure whether I like the idea to build this into portage: This requires root permissions; I am aware that there is squashfuse but besides of speed issues these things actually *should* be done as root: If something goes wrong or the user changes into the mounted directory while portage is running (which usually can take a long time) umounting can fail. (umount --lazy is not a good idea either: it can block umounting other filesystems on shutdown anyway - I have very bad experience with it in my squash_dir and squashmount projects [in the mv overlay] and use --lazy only as a fallback, and often it causes problems on shutdown if this fallback is needed.) Also there can be troubles with parallel runs of portage and/or other tools: For instance, equery, portage-utils, eix-update would have to do the mounting/umounting game, too, so one would at least need a properly documented global locking mechanism for all related tools. Apart from the IMHO severe security issue that this means that tools like eix-update then cannot drop their permissions: What happens if one tool crashes and does not properly unlock/umount? I would consider it more reasonable to do the mounting in /etc/fstab properly and to write one script which updates the squashfile and simultaneously remounts. This way, the data is always available (so the user can always read the current portage tree when he wants to check something) and mounting/umounting is reduced to the one instance when it is really necessary and useful. Users of systemd or automount can also save the minimal amount of time of mounting the squashfile during boot if they do not run portage. IMHO this is the unix way of doing things: Using existing tools and mechanism instead of rebuilding a complex thing into every tool needing to access the tree. yeah, portage shouldn't really be in the business of mounting file systems I concur with vapier. -A |