[SOLVED] Entering passphrase on LUKS partition with USB
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
maybe you could add a short sleep to the init script in /boot/initrd-tree prior to the call to cryptsetup to allow your modules time to initialise. Once you've made your customisations you just have to re-run mkinitrd without any parameters and it'll rebuild the initrd.gz from the modified initrd-tree.
Yep, that's what I was getting at. The cryptsetup command is what't used to unlock the luks devices, so if you search for that and put your sleep on the line before it, hopefully that should do the trick.
Remember not to specify any options on the mkinitrd when you re-run it for the second time, or it may end up rebuilding your /boot/initrd-tree again and undoing your changes. I'd also suggest that whenever your playing with the initrd you make a copy of your old initrd.gz file and have a second lilo entry pointing to it, just incase you make a mistake with your edit and your new initrd.gz becomes unbootable.
Normally, I'd be a little more helpful and provide you with an example, but I've just bought a new PC and I haven't got around to putting Slack on it yet and transfering my old system across. (I'm using Vista and Opera at the moment, and actually finding it isn't half as bad as people make out... I think I've lost my inner-penguin!)