Light-Debian-Core-Live-CD-Wheezy + Porteus-Wheezy

[fredx181]

Hi Toni,

All information added. If you find something for changing just write what is needed.
The kernel 3.13.6 added in separate kernel post.

Yes, can you also add it runs with systemd enabled or something like that?

We have some issue with 2Gb limit save file GUI for porteus boot. Read the question from Tm_mT. I guess it is because vfat limit for 2Gb files but I think on vfat you can't create more than 2Gb save file anyway. Is there a reason we need this 2Gb limit in mk-save.gtkdlg?
He also gets some messages with porteus boot for improper shutdown and save file warning that I can't reproduce yet.

The file size limit on FAT is 4GB. I didn't realize that mk-save has 2GB limit creating savefile.
Here's a way to change the max value in the script from command line:

Code: Select all

SIZE='--field="Savefile Size   MB:NUM" "200!100..2048!5"'
NEWSIZE='--field="Savefile Size   MB:NUM" "200!100..4090!5"'
sed -i "s,$SIZE,$NEWSIZE,g" /opt/bin/mk-save.gtkdlg

New value will then be a little less then 4GB, to be safe when using on FAT.
You're right, this should be on the "fixes" list.

I can't test with kernel 3.14 now because it's PAE, but otherwise the only message I've seen was "recovering journal" when using encrypted save.

Can you share some tips how was made this google drive setup?

Sure, I'll explain later today with some screenshots, can I assume you have account and logged in already in google drive, so need explanation after that only?


I'll check the initrd patch within the next days.
Next time I will write first about what fix I think is needed.
In this case I thought I do the work myself because of mistake I made before, and I know it's no fun for you compressing all the initrd.xz files on your low-ram computer.
For info, what I changed in linuxrc is very simple:
Before fix: (On section: # Find modules)

Code: Select all

# Find modules:
find $PTH $PTH/base $PTH/modules -name "*.squashfs" 2>/dev/null | egrep -v "$NOLOAD" | sort -u >/tmp/modules
find $PTH/optional -name "*.squashfs" 2>/dev/null | egrep "$LOAD" | sort >>/tmp/modules

New:

Code: Select all

ls $PTH/*.squashfs 2>/dev/null | egrep -v "$NOLOAD" | sort -u >/tmp/modules
find $PTH/base $PTH/modules -name "*.squashfs" 2>/dev/null | egrep -v "$NOLOAD" | sort -u >>/tmp/modules
find $PTH/optional -name "*.squashfs" 2>/dev/null | egrep "$LOAD" | sort >>/tmp/modules

The first line searches only in /live, not in sub-directories.
The second in /live/base and /live/modules.
The third in /live/optional in case load= is specified.

[saintless]

Hi, Fred

Yes, can you also add it runs with systemd enabled or something like that?

Done.

Here's a way to change the max value in the script from command line:

Code: Select all

SIZE='--field="Savefile Size   MB:NUM" "200!100..2048!5"'
NEWSIZE='--field="Savefile Size   MB:NUM" "200!100..4090!5"'
sed -i "s,$SIZE,$NEWSIZE,g" /opt/bin/mk-save.gtkdlg

I gave advice to use live-boot-2 or 3 and create the encrypted file from there. It is easier. What about if someone deside to make 8Gb or 100Mb save file?
If you fix mk-save.gtkdlg later I will add it to the fixes post for download.

I can't test with kernel 3.14 now because it's PAE, but otherwise the only message I've seen was "recovering journal" when using encrypted save.

There is similar message but only with encrypted save file for me about /dev/mapper/crypt not clearly unmounted and forced check. I think the shutdown script does not unmount /dev/mapper/crypt. I haven't tested OpenBox yet. Don't think it is a problem anyway.

Sure, I'll explain later today with some screenshots, can I assume you have account and logged in already in google drive, so need explanation after that only?

Thank you, yes, I will use my wife's account for testing.

Toni

[fredx181]

Hi Toni,
Here's how to make a folder in google drive behave as a webhost:
In this example from an empty google drive (I just created a new account and have 15GB again!)
Click on the red "Create" button and create a folder:



Ok, I created 'Debdog', right-click on the new folder and choose Share > Share:



New window appears, now change "Private only you can access" to "Public on the web" and click Save.
Then click Done on the previous window:



Then right-click on the new folder and choose "Details and activity" (there's also the "i" button on top right button section)
It probably opens in "Activity" so click on Detalis:



Almost at the bottom of Details under 'HOSTING' you see an https address with 'host' in it:



Now that's the host address of the new shared folder and you can make new folder or upload file inside and add /name-of-subfolder or /filename after the host address.

Btw, works also as you can see.

Fred

[saintless]

Thank you, Fred, great instruction to follow!
15 Gb... I like it already

Toni

[fredx181]

What about if someone deside to make 8Gb or 100Mb save file? Smile

Yes, you never know what people are capable of, nearly 20Gb limit will be sufficient I think
Attached new make-save.gtkdlg and makepfile.sh, goes from 100-20000Mb.

Edit: But I don't know what happens exactly when someone tries to create for example 5Gb savefile on a FAT partition.
What do you think in general, do we need more error checking, I mean in other scripts also e.g. check for enough space or not?

Good luck with your new google drive, 15Gb is indeed a lot.
I was thinking recently to add maybe some sort of sfs-download program, would be nice to offer prefab sfs modules this way (like most puppy's have also).

There is similar message but only with encrypted save file for me about /dev/mapper/crypt not clearly unmounted and forced check. I think the shutdown script does not unmount /dev/mapper/crypt. I haven't tested OpenBox yet. Don't think it is a problem anyway.

I also don't think it's a problem, fsck works very well.
I often see on shutdown message about /dev/loop* not unmounted, it doesn't look nice, maybe create some script that unmounts all modules on shutdown but that won't be easy I think.

Fred

[saintless]

Attached new make-save.gtkdlg and makepfile.sh, goes from 100-20000Mb.

Thanks, Fred, I will add it to the fixes later tonight or tomorrow.

What do you think in general, do we need more error checking, I mean in other scripts also e.g. check for enough space or not?

No. I will test it on vfat when I get time for this but I prefer the scripts less complicated. And as you know we do not get much testing reports to be sure all works well after the changes.

I was thinking recently to add maybe some sort of sfs-download program, would be nice to offer prefab sfs modules this way (like most puppy's have also).

We can use sfs-get from Sfs. It is included in his version of DebianDog-OpenBox. I'm not sure GUI is easier than download sfs and load with right click but sfs-get is already adapted to work with DebianDog. It needs only repository change.
All kind make-it-easier-for-me utilities result in less reading and Debian needs reading and command line typing from time to time.

maybe create some script that unmounts all modules on shutdown but that won't be easy I think.

No, in my opinion. Not easy and we can not predict the result without much testing first.

I'm trying to be DebianDog user for a while, Fred. Let's enjoy our work and fix bugs only when needed.

Toni

[saintless]

Hi, Stemsee and all interested from experimental boot methods.

Some of your kernels uploaded here for puppy-initrd-boot (in case you need quick link to share them):
https://9eb8f45ca0acc9dd68fbe8a604cd729 ... ntal-boot/
I can't test 64bit but I guess they will work.

Also for Puppy-Rus-A-boot but I need time for translating the boot script and adding some instruction how to use the kernels. I will get back on this when I'm ready.

Toni

[atv]

Toni, Fred, Sergey, William, Sunburnt, Nooby(in absence) and all others

I want you guys to know that the work you have done and are doing is being enjoyed by: Myself and about (80 and growing) others, that are not fortunate enough to be computer literates and do have access to low cost(older)laptops etc.
My two cents is to install and maintain their systems free of charge. This effort of yours makes my task a great deal easier. So thank you all for the job well done. Keep up the good work and enjoy your well deserved holidays.

regards, Andres

[stemsee]

@saintless, Fredx181

That's a very neat way to use google drive. I will have to do that too!


.. sometime...

[saintless]

Hi, Andres, glad to read DebianDog is useful for you and much more people

and do have access to low cost(older)laptops etc.

In case there are machines with less than 1Ghz processor and 512Mb Ram using gzip compression for the main 01-filesystem.squashfs module will speed up the system. More information here:
http://www.murga-linux.com/puppy/viewto ... 872#793872

Stemsee, yes, Fred found great way to use google drive.

Toni

[fredx181]

Toni, Fred, Sergey, William, Sunburnt, Nooby(in absence) and all others

I want you guys to know that the work you have done and are doing is being enjoyed by: Myself and about (80 and growing) others, that are not fortunate enough to be computer literates and do have access to low cost(older)laptops etc.
My two cents is to install and maintain their systems free of charge. This effort of yours makes my task a great deal easier. So thank you all for the job well done. Keep up the good work and enjoy your well deserved holidays.

regards, Andres

Thanks very much Andres

That's a very neat way to use google drive. I will have to do that too! Smile
.. sometime...

Your decision, but... do it now! it's easy once you know how.
For information: It can be done with already existing folder also, just change the permissions to public.

Fred

[stemsee]

My google drive is like a teenagers bedroom at the moment!!

[fredx181]

My google drive is like a teenagers bedroom at the moment!!

Yes, make me feel 40 years younger!
Seriously now, you can make new folder to use as host to share public only.

Fred

[step]

Here follow

• Alternative google hosting folder istructions...
• Simplified for EmSee and me - we share the teenager's bedroom approach to google drive

By way of a pratical example: sharing a fictitional file, EmSee's next 2GB+ EmSee3.iso release:

• Make a new folder in your google drive, right click its item line, select Shared/everyone can view and write down its sharing link. It will look something like this: https://drive.google.com/folderview?id=0B8P7qC27sushWHg2VFB6QTRJLW8&usp=sharing
• Now rewrite the sharing address as a direct link by replacing the blue part above with https://googledrive.com/host/ and dropping the red part: https://googledrive.com/host/0B8P7qC27sushWHg2VFB6QTRJLW8
• Now append the filename and you are done: https://googledrive.com/host/0B8P7qC27sushWHg2VFB6QTRJLW8/EmSee3.iso

Remarks

• You can see that the folder ID stays the same, and publishing a direct link is just a matter or re-writing the url. In fact, you could publish both urls.
• When accessing a folder/file via drive.google.com one gets the familiar google drive interface, with thumbnails, previews, and several prompts before one can download a file. (Note that the drive.google.com link to a shared file can't be derived as I showed above for a folder.)
• When accessing the file via googledrive.com one gets a file list and direct links, that is, no prompt to download the file!
• So with the googledrive.com direct link one can download the file from a script using wget, which can't be done when drive.google.com is used for the link and one has to use a web browser to download. (For instance, I can't download a file larger than 2GB from drive.google.com because my firefox drops out at the 2GB fence. But I could download the same file from googledrive.com with wget, because wget doesn't drop out after 2GB.)
• As Fred pointed out, with googledrive.com one can also append the relative path to a file in a sub-folder.

The folder ID in my examples corresponds to Toni's DebianDog backup folder.

[saintless]

Thank you, Step!
These google drive tips should go in special thread so more people can use them.

Toni

[saintless]

Continue from here:
http://www.murga-linux.com/puppy/viewto ... 795#794795

OK, Tm_mT, here we go... I hope I do not have critical typo that can break everything
Boot as usual with porteus-boot (initrd63.xz).
Add initrd61.img inside /live boot folder (if it is not there yet).
Download and extract this archive in /opt/bin (this is the easiest way to create encrypted save file for live-boot-3x with persistence.conf file inside and content /union for full persistence - all is automated).
http://www.smokey01.com/saintless/Debia ... -crypt.zip
Type in terminal mk-save-crypt and follow the instructions to create encrypted save file. Choose small size for the test and persistence as name for the save file and location sda2. (You should have /sda2/persistence save file at the end).

Boot DebianDog with this boot code in menu.lst:

Code: Select all

title DebianDog live-boot-3x No-Copy-to-RAM persistence encrypted on /sda2
 uuid afca251b-50da-4e0a-87e7-cabd2e8ee8ce
 kernel /live/vmlinuz6 boot=live config swapon noeject quickreboot autologin rw-basemount persistence persistence-encryption=none,luks
 initrd /live/initrd61.img

Is the encrypted save password prompt working?

If yes - stop here. If no - continue further.

Boot DebianDog with this boot code (no persistence). We do not need save file to keep the changes - new rebuilded initrd.img with included components from firmware-linux-nonfree is all we need for this test):

Code: Select all

title DebianDog live-boot-3x No-Copy-to-RAM no-persistence
 uuid afca251b-50da-4e0a-87e7-cabd2e8ee8ce
 kernel /live/vmlinuz6 boot=live config swapon noeject quickreboot autologin rw-basemount
 initrd /live/initrd61.img

Copy vmlinuz6 (the path should be something like /lib/live/mount/medium/live/vmlinuz6 or /lib/live/mount/persistence/sda2/live/vmlinuz6) in /boot and rename it to vmlinuz-3.14-0.bpo.1-686-pae

Install firmware-linux-nonfree:

Code: Select all

apt-get install firmware-linux-nonfree

Ignore the error message about missing initrd-... in /boot
Open terminal and type:

Code: Select all

cd /boot
mkinitramfs -o initrd.img-3.14-0.bpo.1-686-pae 3.14-0.bpo.1-686-pae

Wait the process to finish (it may take few minutes).
Now you have new rebuilded with firmware linux included initrd.img-3.14-0.bpo.1-686-pae
But we need to patch it first in order to be able to use save file on the boot partition.
Copy /boot/initrd.img-3.14-0.bpo.1-686-pae in /opt/bin/special/patch-live-initrd/ and rename it to initrd.img
Type in terminal:

Code: Select all

/opt/bin/special/patch-live-initrd/patch-initrd

Choose initrd.img as name to patch and confirm the patch questions.
New /opt/bin/special/patch-live-initrd/initrd-custom.img will be created.

Rename initrd61.img to initrd61.img-old and move /opt/bin/special/patch-live-initrd/initrd-custom.img in /live and rename it to initrd61.img
Now boot the computer again with the encrypted persistence boot code:

Code: Select all

title DebianDog live-boot-3x No-Copy-to-RAM persistence encrypted on /sda2
 uuid afca251b-50da-4e0a-87e7-cabd2e8ee8ce
 kernel /live/vmlinuz6 boot=live config swapon noeject quickreboot autologin rw-basemount persistence persistence-encryption=none,luks
 initrd /live/initrd61.img

Is the persistence password prompt freezes again? If it does I have no more ideas and firmware-linux-nonfree is not a solution for the problem you have.
If it works I will try to make initrd63.img with the changes from your new builded initrd61.img and hopefuly it will work for porteus boot as well.

Toni

[Tm_mT]

Type in terminal:

Code: Select all

/opt/bin/special/patch-live-initrd/patch-initrd

Choose initrd.img as name to patch and confirm the patch questions.

Code: Select all

root@debian:/boot# /opt/bin/special/patch-live-initrd/patch-initrd
Extract initrd? (y/n)
y
A copy of the original initrd to patch should exist in this directory.
Detected initrd files:
initrd.img-3.14-0.bpo.1-686-pae

Please enter the name of the initrd to extract:
initrd.img

File not found

In /opt/bin/special/patch-live-initrd there are the following files:
initrd.img
initrd.img-3.14-0.bpo.1-686-pae
patch-initrd
readme.txt

an error in the patch-initrd perhaps?

[Tm_mT]

BTW. No rush, I will not be able to do more this evening and will check again tomorrow or the weekend (have a lot more time then)

Thanks !

[saintless]

Test when you have time, Tm_mT, no hurry.

Code: Select all

root@debian:/boot# /opt/bin/special/patch-live-initrd/patch-initrd
Extract initrd? (y/n)
y
A copy of the original initrd to patch should exist in this directory.
Detected initrd files:
initrd.img-3.14-0.bpo.1-686-pae

Please enter the name of the initrd to extract:
initrd.img

File not found

In /opt/bin/special/patch-live-initrd there are the following files:
initrd.img
initrd.img-3.14-0.bpo.1-686-pae
patch-initrd
readme.txt

an error in the patch-initrd perhaps?

If you did this:

Copy /boot/initrd.img-3.14-0.bpo.1-686-pae in /opt/bin/special/patch-live-initrd/ and rename it to initrd.img

you should not have initrd.img-3.14-0.bpo.1-686-pae anymore.
"file not found" seems to me there is no initrd.img available in /opt/bin/special/patch-live-initrd. And it is not detected also.
Maybe you made copy instead renaming and initrd.img is broken or it is not there? Is it the same size like initrd.img-3.14-0.bpo.1-686-pae?
Anyway try typing initrd.img-3.14-0.bpo.1-686-pae instead initrd.img then. It is there reading the detected output:

Code: Select all

Detected initrd files:
initrd.img-3.14-0.bpo.1-686-pae

Toni

[fredx181]

Hi Toni,
Very simple concept of sfs-get script using yad.
Test it whenever you like, don't want to spoil your vacation
I took the liberty to use your google drive address in the script but could be translated to use smokey.com of course.
It depends on the presence of file "sfs.txt" in your google drive shared folder DebianDog-Wheezy/Extra-Modules.
Contents of "sfs.txt" should be list of available modules at this moment:

Code: Select all

08-googleearth-debdog.squashfs
022-abiword.squashfs
030-gnumeric.squashfs
035-seamonkey-2.0.11.squashfs
051-smo-freeoffice.squashfs
064-cups.squashfs
ffmpeg-static-0.9.4.squashfs

The nice thing I think is that as long this file is updated corresponding to what's inside DebianDog-Wheezy/Extra-Modules it should always work (even with new DebianDog release).
The script:

Code: Select all

#!/bin/bash
[ "`whoami`" != "root" ] && exec gsu ${0}

[ -f /tmp/sfs.txt ] && rm -f /tmp/sfs.txt

# Download sfs.txt to /tmp to read list of available modules further by the script.
# It assumes "sfs.txt" is in DebianDog-Wheezy/Extra-Modules/
wget -P /tmp/ https://googledrive.com/host/0B8P7qC27sushWHg2VFB6QTRJLW8/DebianDog-Wheezy/Extra-Modules/sfs.txt

ALL=`cat /tmp/sfs.txt`
lst=$(yad --separator=" " --center --height 600 --width="800" --list --title="Download SFS module" --multiple --text=" Download SFS modules. \n Select (multiple) items to download." --column "Available Modules" $ALL --button="gtk-cancel:1" --button="gtk-ok:0")
ret=$?
[[ $ret -ne 0 ]] && exit 1
echo $lst

SAVEFOLDER=$(yad  --center --title="Select folder to download SFS modules" --file --height=600 --width=800 --text=" Select folder to download SFS modules to" )
ret=$?
[[ $ret -ne 0 ]] && exit 1

for i in $lst; do
# This assumes "sfs.txt" is in DebianDog-Wheezy/Extra-Modules/
wget -P "$SAVEFOLDER" https://googledrive.com/host/0B8P7qC27sushWHg2VFB6QTRJLW8/DebianDog-Wheezy/Extra-Modules/$i
done

Any suggestion for improvement is welcome of course.

Fred