Bug#392799: Having the need to have "/proc" mounted in postinst halts installations in chroots, hence in debian-live.
Marco Amadori skrev:
But I think that it is not a clean way to proceed in a "create live
environment" sense of a package, /proc filesystem means the "current hardware
and kernel system" pack of informations and not a "generic debian system"
informations nor an "hardwareless" or "kernelless" pack of information, so
even if apache2 team wont fix this bug, asking to have /proc installed have
only meanings of "current system" installs, not a generic one. So this bug is
valid for all packages that requires /proc to finish the installation.
Then you should build in a UML or Xen instance or something similar
which is as close to a generic system as possible.
Apache is just optimising for the common case, which is to install
apache in a normal system where you don't want it to fall over because
port 80 is in use already.
If I dig maintainers scripts and provide a patch, could that be integrated
asap or will just be a useless effort by me?
I don't think you can, given that the way it currently works is by
design. If we can't determine whether port 80 is in use or not, we
assume it is.
- tfheen
Reply to: