On Mon, 13 Nov 2006 21:54:01 +0100 Bernard Adrian <[EMAIL PROTECTED]> wrote:
> Tim Dijkstra <[EMAIL PROTECTED]> a écrit : > > > Hmm, that is the problem. /bin/mountpoint is in the initscripts package > > which has priority 'required'. Apparently you're using an alternate way > > to boot your system... > > For my first steps in the free world, two years ago, i installed > Knoppix on this HD. So i have neither initscripts nor mount packages > but mount-aes. > > I worry, if i try to replace "mount-aes" by "initscripts" and "mount" > to make my system unbootable... It's my main machine. In a way it is a bug in uswsusp, because it doesn't depend on initscripts. But changing uswsusp to do this will not help you... If I were you I would try to install initscripts, The way you have your system now is asking for problems. It maybe working now but you won't get any new updates to the booting part of your system (unless you take updates from knoppix of course). BTW, if your are using the encrypted loopback capabilities of mount-aes, you will need the debian loop-aes-utils package, I guess. I'm not sure how much your system diverges from a debian system so I can't really comment on the risks. I would guess there are more users that upgraded their knoppix to a debian system so you could google a bit for it. In the mean time you can edit you can edit /etc/uswsusp.conf by hand. Or remove the 'mountpoint' tests from the scripts: /var/lib/dpkg/info/uswsusp.postinst /var/lib/dpkg/info/uswsusp.config and dpkg-reconfigure uswsusp. grts Tim
signature.asc
Description: PGP signature
