linux-3.2.4 kernel and initrd update for Porteus-1.1

[fanthom]

discussion thread about an update posted in "Announcement" section:
http://porteus.org/forum/viewtopic.php? ... 7796#p7796

Future version of "Porteus save.dat Manager" will include support for creating encrypted containers. for now you have to do it manually.
here are the commands to create 410MB container:

Code: Select all

    dd if=/dev/urandom of=crypt.dat bs=4096 count=100000
    mknod /dev/loop100 b 7 100
    losetup /dev/loop100 crypt.dat
    cryptsetup -y -s 256 luksFormat /dev/loop100
    cryptsetup luksOpen /dev/loop100 encrypted
    mkfs.xfs /dev/mapper/encrypted
    cryptsetup luksClose encrypted
    losetup -d /dev/loop100

once created you can use it with 'changes=crypt.dat' cheatcode.

comments, bug reports, suggestions are welcome.

[brokenman]

Excellent. I will be porting current xdialog script to gtkdialog for next version. Would be good to hear from anyone that has has a need to use the 'recovery' option and how it worked out.

Will add this function to the gtkdialog version. Fanthom if you have integrated this into current save.dat manager please send. This will be a popular feature, thanks very much.

[fanthom]

Fanthom if you have integrated this into current save.dat manager please send.

i was actually hoping you will look after gtkdialog stuff
i have added support for encrypted containers to 'mloop' utility. here is the code which may be helpful for 'Porteus save.dat Manager' - "resize .dat", or "repair" functions:

Code: Select all

if blkid $xfile 2>/dev/null | cut -d" " -f3- | grep -q _LUKS; then
    losetup /dev/loop$y $xfile
    echo "found .dat container encrypted with LUKS..."
    cryptsetup luksOpen /dev/loop$y mloop-crypt
    mount /dev/mapper/mloop-crypt $mpoint 2>/dev/null
else
    mount -t auto -o loop $xfile $mpoint
fi

the main thing is to use 'blkid' utility to find if container is encrypted or not. you must also know the loop device number which was used for container to use it with cryptsetup.

btw: statically linked cryptsetup is placed in 000/sbin folder (best place from linuxrc point of view) so make sure you boot with new kernel stuff to use it.

[kalo86]

Hi fanthom,
can you upload an archive containing the patches you used for the 3.2.4-porteus kernel?
I have a problem patching the new 3.2.5 kernel for the aufs.
Regards and thank you in advance,

kalo86

[fanthom]

hi kalo86,

have a look here:
http://porteus.org/forum/viewtopic.php? ... 1020#p7836

[kalo86]

Thank you fanthom!
Following and using your new script I finally managed to patch the kernel sources.
Now I am trying to compile the new 3.2.6 kernel because I have regular freezes on my netbook (Acer Aspire One 522) caused by the atl1c module.
If I blacklist that module I don't have any kind of problem.
Regards and thank you always!

[steveosiris]

hi kalo86,

have a look here:
http://porteus.org/forum/viewtopic.php? ... 1020#p7836

Thanks for the info Fathom. With your help, I was able to patch the kernel sources, and am very thankful. I will continue to use this forum to troubleshoot any issus I run into.

[jackreal94]

While trying to compile the new 3.2.6 kernel even I had problems on my laptop caused by the atl1c module. I was able to get help from this forum , I blacklisted that particular module and its working fine. Appreciate it !