Making root encryption easier.
Posted: 4. Dec 2010, 22:15
Hi, im just new here, so hi!.
I discover Salix a few months ago and I love it. Simple, easy, powerfull. Just what slack was a few years ago ...
I was a slack user way back, i went debian because apt (yeah, im lazy ), but i love to try any distro i could find, so recently i was looking for a light distro for my "netbook" (a six years 700m 13in celeron), so i choose salix. This is my issue, im kind a paranoid freak that dont want my cooking recipies fall in the wrong hands, so i dont use a distro without encryption. Salix has no encrypt install (the easy way...) but the slack way isn't that hard, at least for a non so newb linux user like me me. But, and this is the Salix little issue, the slack way cant work out of the box, i mean this way:
http://slackware.osuosl.org/slackware-c ... _CRYPT.TXT
(yeah, the readme_crypt.txt)
Because the howto says you must use a GENERIC kernel, and Salix only brings the HUGE kernel, that cant work (at least i cant make it work)...
So i make a few tries in a VM and i found an easy solution, just copy an entire /boot from a fresh Slackware 13 install over the Salix /boot, right before the
# mkinitrd -c -k 2.6.33.4-smp -m ext3 -f ext3 -r /dev/cryptvg/root -C /dev/sdx2 -L
step. I choose not to overwrite the Salix boot files, anyway, this just add the slackware GENERIC kernel to Salix (after all, Salix is 100% compatible).
Ok, this work just fine in the VM test and also in my laptop, so i had a full root encrypted Salix working fine (and im so happy I had to share it)
Im just a linux fan, not an advance user at all, so this was just trial and error, and i cant say it might work in the long run, but better users may improbe this.
Ah!!! The suggestion (its the forums point, after all ), I just think this could be much easier if the GENERIC kernel were included in the default Salix install, so the readme_crypt.txt might work just as writen.
I hope this can be useful!!!
Thx for this great distro!!!
PD: Sorry for the ugly english, I usually speaks (i mean write) spanish!
I discover Salix a few months ago and I love it. Simple, easy, powerfull. Just what slack was a few years ago ...
I was a slack user way back, i went debian because apt (yeah, im lazy ), but i love to try any distro i could find, so recently i was looking for a light distro for my "netbook" (a six years 700m 13in celeron), so i choose salix. This is my issue, im kind a paranoid freak that dont want my cooking recipies fall in the wrong hands, so i dont use a distro without encryption. Salix has no encrypt install (the easy way...) but the slack way isn't that hard, at least for a non so newb linux user like me me. But, and this is the Salix little issue, the slack way cant work out of the box, i mean this way:
http://slackware.osuosl.org/slackware-c ... _CRYPT.TXT
(yeah, the readme_crypt.txt)
Because the howto says you must use a GENERIC kernel, and Salix only brings the HUGE kernel, that cant work (at least i cant make it work)...
So i make a few tries in a VM and i found an easy solution, just copy an entire /boot from a fresh Slackware 13 install over the Salix /boot, right before the
# mkinitrd -c -k 2.6.33.4-smp -m ext3 -f ext3 -r /dev/cryptvg/root -C /dev/sdx2 -L
step. I choose not to overwrite the Salix boot files, anyway, this just add the slackware GENERIC kernel to Salix (after all, Salix is 100% compatible).
Ok, this work just fine in the VM test and also in my laptop, so i had a full root encrypted Salix working fine (and im so happy I had to share it)
Im just a linux fan, not an advance user at all, so this was just trial and error, and i cant say it might work in the long run, but better users may improbe this.
Ah!!! The suggestion (its the forums point, after all ), I just think this could be much easier if the GENERIC kernel were included in the default Salix install, so the readme_crypt.txt might work just as writen.
I hope this can be useful!!!
Thx for this great distro!!!
PD: Sorry for the ugly english, I usually speaks (i mean write) spanish!