Jimmy Wu wrote: > I even put aside my reservations about messing with the links in > rc.d,
Squeeze is running a dependency based boot scheme controlled by insserv. You may be fighting it and not knowing it. Normally you would have LSB dependency headers in the /etc/init.d/ scripts and insserv will assign a boot number based upon topologically sorting the dependencies. > (tried starting cryptdisks in runlevels 2-5 and other things > as well) but since it didn't work so I restored everything back to > the default before I broke anything, and came here to ask for > help/advice instead. Good plan! :-) In Debian the default run level is 2. In Debian by default all runlevels 2-5 are identical. You as the local admin can change either of those things and those changes will be respected by the system tools. But that is the default. No reason to do anything else. > My system is Squeeze 2.6.32-5-amd64 > Running invoke-rc.d cryptdisks start && swapon -a after boot works. You may have heard people talk about invoke-rc.d but that is designed as a tool for packages to use in the package 'postinst' script. It respects the setting of the policy-rc.d script such as not starting daemons inside of chroot environments. It isn't intended as a command the user would call from the command line. You can, but that isn't the purpose, and in Squeeze you should be using 'service'. In Squeeze Debian added the 'service' command the same as previously seen on other distros. The 'service' command is intended to be used from the command line. # service cryptdisks start See the man page for details but service cleans the environment and calls the /etc/init.d/ script. It is a little bit cleaner than calling /etc/init.d/script directly. > During the boot process I can see messages on the console that show > "Starting early crypto disks" succeeds, but "Starting remaining crypto > disks" failed. > > I'd appreciate any pointers as to what I am doing wrong or how I can > better troubleshoot the problem. I don't know anything about setting up encrypted swap files. But I will suggest that if you want to change the boot order that you edit the /etc/init.d/cryptdisks script and perhaps add "$all" or some other dependency to the Required-Start: line and then run insserv to update the symlinks. Adding $all is a quick hack to push the start to the end of the boot process. I would think adding swap could happen at any time and be okay to happen very late. You can look at the ordering of the boot scripts in /etc/rc2.d/ and observe the changes. If that works then you know you have a boot time initialization ordering problem. You can then work from there to refine the solution. Bob
signature.asc
Description: Digital signature
