Light-Debian-Core-Live-CD-Wheezy + Porteus-Wheezy
Hi Toni,
Just to inform you, I'm busy scripting and learning about wget options.
The sfs-get script and specially also a gui-script for downloading in general from smokey01/saintless and possibly from smokey01/"whatever".
I think it will be nice when I'm finished, although I'm not really sure yet what's the use of it. But anyway I like doing it
Fred
Just to inform you, I'm busy scripting and learning about wget options.
The sfs-get script and specially also a gui-script for downloading in general from smokey01/saintless and possibly from smokey01/"whatever".
I think it will be nice when I'm finished, although I'm not really sure yet what's the use of it. But anyway I like doing it
Fred
Code: Select all
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
root@debian:/boot# cd /opt/bin/special/patch-live-initrd/
root@debian:/opt/bin/special/patch-live-initrd# ls
files initrd.img patch-initrd readme.txt
root@debian:/opt/bin/special/patch-live-initrd#
BTW. Not sure if it is worth mentioning, but I think I noticed twice that after creating an encrypted save file (the default method) it is not possible anymore to shutdown my PC.
Maybe it is totally unrelated, but if it is worth checking out further let me know and I can check if I can consistently reproduce this behaviour.
Maybe it is totally unrelated, but if it is worth checking out further let me know and I can check if I can consistently reproduce this behaviour.
I see it shows initrd.img-3.14-0.bpo.1-686-pae detected (not initrd.img).Tm_mT wrote:Pretty sure I followed the explanation to the letter. as you can see above the ls only shows initrd.img this time in the directory but it isn't recognized.Code: Select all
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 root@debian:/boot# cd /opt/bin/special/patch-live-initrd/ root@debian:/opt/bin/special/patch-live-initrd# ls files initrd.img patch-initrd readme.txt root@debian:/opt/bin/special/patch-live-initrd#
Lets start from the point you have /boot/initrd.img-3.14-0.bpo.1-686-pae created from mkinitramfs command.
Inside /opt/bin/special/patch-live-initrd you have only:
files (folder)
patch-initrd
readme.txt
Nothing else.
Execute the following commands from terminal and you should have at the end /opt/bin/special/patch-live-initrd/extracted/initrd.custom.img
Use this initrd.custom.img instead /live/initrd61.img to boot.
Code: Select all
root@debian:~# cp /boot/initrd.img-3.14-0.bpo.1-686-pae /opt/bin/special/patch-live-initrd
root@debian:~# cd /opt/bin/special/patch-live-initrd
root@debian:/opt/bin/special/patch-live-initrd# mv initrd.img-3.14-0.bpo.1-686-pae initrd.img
root@debian:/opt/bin/special/patch-live-initrd# /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
Please enter the name of the initrd to extract:
initrd.img
/opt/bin/special/patch-live-initrd/extracted /opt/bin/special/patch-live-initrd
64812 blocks
/opt/bin/special/patch-live-initrd
Initrd is extracted
Apply patches automatically? (y/n)
y
patching file extracted/lib/live/boot/9990-misc-helpers.sh
patching file extracted/lib/live/boot/3020-swapon
patching file extracted/bin/boot/9990-misc-helpers.sh
patching file extracted/bin/boot/3020-swapon
Rebuild initrd? (y/n)
y
/opt/bin/special/patch-live-initrd/extracted /opt/bin/special/patch-live-initrd
64812 blocks
Initrd is rebuilt /opt/bin/special/patch-live-initrd/extracted/initrd.custom.img
/opt/bin/special/patch-live-initrd
root@debian:/opt/bin/special/patch-live-initrd/extracted#
Code: Select all
cd /opt/bin/special/patch-live-initrd
Toni
Last edited by saintless on Sat 16 Aug 2014, 19:34, edited 1 time in total.
Thanks, Fred!fredx181 wrote:Hi Toni,
Just to inform you, I'm busy scripting and learning about wget options.
The sfs-get script and specially also a gui-script for downloading in general from smokey01/saintless and possibly from smokey01/"whatever".
I think it will be nice when I'm finished, although I'm not really sure yet what's the use of it. But anyway I like doing it
Fred
I'm sure we will put it into use somehow and in time we will have more sfs modules available for download.
Toni
Maybe cryptsetup (the encryption command) does not work well with something specific in your hardware and filmware-linux-nonfree will fix this but test with new rebuilded initrd.img will show. I can't think of anything more to test about this problem.Tm_mT wrote:BTW. Not sure if it is worth mentioning, but I think I noticed twice that after creating an encrypted save file (the default method) it is not possible anymore to shutdown my PC.
Maybe it is totally unrelated, but if it is worth checking out further let me know and I can check if I can consistently reproduce this behaviour.
Toni
Seeing some error messages, but will continue.
Code: Select all
root@debian:/opt/bin/special/patch-live-initrd# /opt/bin/special/patch-live-initrd/patch-initrd
Extract initrd? (y/n)
y
Apply patches automatically? (y/n)
y
cp: cannot create regular file `extracted/scripts/': No such file or directory
cp: cannot create regular file `extracted/bin/': No such file or directory
cp: cannot create directory `extracted/bin/': No such file or directory
cp: cannot create directory `extracted/lib/live/': No such file or directory
patching file extracted/lib/live/boot/9990-misc-helpers.sh
patching file extracted/lib/live/boot/3020-swapon
patching file extracted/bin/boot/9990-misc-helpers.sh
patching file extracted/bin/boot/3020-swapon
Rebuild initrd? (y/n)
y
/opt/bin/special/patch-live-initrd/extracted /opt/bin/special/patch-live-initrd
14 blocks
Initrd is rebuilt /opt/bin/special/patch-live-initrd/extracted/initrd.custom.img
/opt/bin/special/patch-live-initrd
root@debian:/opt/bin/special/patch-live-initrd#
Sorry, Tm_mT. This messages mean something is very wrong with the xtracted initrd.img and important files are missing.Tm_mT wrote:cp: cannot create regular file `extracted/scripts/': No such file or directory
cp: cannot create regular file `extracted/bin/': No such file or directory
cp: cannot create directory `extracted/bin/': No such file or directory
cp: cannot create directory `extracted/lib/live/': No such file or directory[/code]
I will rebuild it tomorrow and send you download link to test it.
Toni
OK no problem, just another thing I don't think I mentioned before.
the first step, booting with:
the first step, booting with:
Code: Select all
title DebianDog live-boot-3x No-Copy-to-RAM persistence encrypted on /sda2
If you do not get this password prompt on the picture there is no use to test rebuilded initrd.imgTm_mT wrote:OK no problem, just another thing I don't think I mentioned before.
the first step, booting with:
Doesn't result in an error or a password is required.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
This does not look good to me and needs more information.I am booting in vanille DebianDog then. persistence is in root of sda2Code: Select all
root@debian:~# ls /lib/live/mount/persistence/sda2 026-kernel-3.14-Pae.tar.gz libx32 026-kernel-3.14.0.bpo-pae.squashfs live Readme-initrd-3.14-pae.txt media bin menu.lst boot mnt cdrom opt changes.dat pburn_symlink_tree changes_old.dat persistence dev proc etc root grldr run home sbin initrd61.img srv initrd62.img sys initrd63.xz tmp install_flash_player_11_linux.i386.tar.gz usr lib var lib32 vmlinuz1 lib64 vmlinuz6
You have in root of sda2:
bin, boot, tmp, sys, srv, sbin, run, root, lib32, lib64...
Do you have some other linux full install on the same partition?
And why you have in root of sda2:
initrd61.img, initrd62.img, initrd63.xz, vmlinuz1, vmlinuz6, 026-kernel-3.14.0.bpo-pae.squashfs?
I never tested such configuration and it might become the reason for your problem with encrypted save file.
Toni
Hi Tm_mT, Toni,
Try moving the files from sda2 to somewhere else (most important move changes.dat, persistence)
----------------
Edit: But don't move them to the root of another drive/partition, just inside a folder otherwise it could still be found when in menu.lst changes=/changes.dat
Btw, no other changes.dat or persistence present on another partition? Could conflict also.
----------------
And create new savefile instead.
As before, I keep believing in a simple cause of the problem.
Good luck!
Fred
Yes, this could turn out that things are possibly conflicting somehow, maybe changes.dat labeled persistence and a file named persistence, I don't know but the best thing you can do in my opinion is to start really from scratch, blanco.root@debian:~# ls /lib/live/mount/persistence/sda2
026-kernel-3.14-Pae.tar.gz libx32
026-kernel-3.14.0.bpo-pae.squashfs live
Readme-initrd-3.14-pae.txt media
bin menu.lst
boot mnt
cdrom opt
changes.dat pburn_symlink_tree
changes_old.dat persistence
dev proc
etc root
grldr run
home sbin
initrd61.img srv
initrd62.img sys
initrd63.xz tmp
install_flash_player_11_linux.i386.tar.gz usr
lib var
lib32 vmlinuz1
lib64 vmlinuz6
This does not look good to me and needs more information.
You have in root of sda2:
Try moving the files from sda2 to somewhere else (most important move changes.dat, persistence)
----------------
Edit: But don't move them to the root of another drive/partition, just inside a folder otherwise it could still be found when in menu.lst changes=/changes.dat
Btw, no other changes.dat or persistence present on another partition? Could conflict also.
----------------
And create new savefile instead.
As before, I keep believing in a simple cause of the problem.
Good luck!
Fred
Hi, Tm_mT.
I agree with Fred. No need to continue further with live-boot-3x and persistence save file. You do not get to password prompt even and the point to use persistence save file was to find out the problem with encrypted changes.dat.
Something in your configuration creates conflict and maybe it is not yet visible for us. Since you have copies of the same initrd*, vmlinuz*, .squashfs in root of sda2 I suggest remove them and leave the files inside /sda2/live only. Remove (or move inside folder in different partition all changes.dat and persistence).
Do the same check in other partitions and make sure you do not have DebianDog files there also.
Most important check that /sda2/live is the only /live folder you have (there is no /live folder on different partition).
Then boot with porteus-boot, create small encrypted changes.dat (1Gb for example) with the built-in Make-Save utility from porteus-boot and see if it works this way after reboot.
Toni
I agree with Fred. No need to continue further with live-boot-3x and persistence save file. You do not get to password prompt even and the point to use persistence save file was to find out the problem with encrypted changes.dat.
Something in your configuration creates conflict and maybe it is not yet visible for us. Since you have copies of the same initrd*, vmlinuz*, .squashfs in root of sda2 I suggest remove them and leave the files inside /sda2/live only. Remove (or move inside folder in different partition all changes.dat and persistence).
Do the same check in other partitions and make sure you do not have DebianDog files there also.
Most important check that /sda2/live is the only /live folder you have (there is no /live folder on different partition).
Then boot with porteus-boot, create small encrypted changes.dat (1Gb for example) with the built-in Make-Save utility from porteus-boot and see if it works this way after reboot.
Toni
sfs-get and smokey-get scripts for testing
Hi Toni, All,
Here are sfs-get and smokey-get scripts for testing.
smokey-get is a Gui-script using yad and wget to download from smokey01.com.
The setup for yad multi-progress bars I stole from `piece of art`: 'yad_wget' see here:
http://askubuntu.com/questions/463012/h ... gress-bars
Works well with smokey01.com host address but not with google-drive (and probably not with a lot more).
Maybe it's possible, but needs a lot more tricks I think because of redirection.
It's amazing what different things can be done with wget and some grep/sed filtering.
smokey-get inside the sfs-get-smokey-get_1.0.1_i386.deb uses main host directory "http://www.smokey01.com/saintless" but can update/modify itself to another address on http://www.smokey01.com/...
Included 'smokey-get-pemasu' is an example of modified smokey-get by using 'Update url-list' and choosing to change main host directory (changed in this case to MAINHOSTDIR="http://www.smokey01.com/pemasu" and changes also long list CHOICE="........" on top of script).
Updating took some time to complete, didnt't try yet to change/update to "http://www.smokey01.com/01micko", it will probably take even longer.
To update url-list the script needs to be in PATH and (re)named 'smokey-get'
Backup of old smokey-get will be made.
The .deb doesn't install .desktop or menu files so need to type sfs-get or smokey-get in terminal.
I'm not exactly sure this will be useful for anyone (or maybe in some other form), I just like exploring things
Attached sfs-get_smokey-get.tar.gz (.deb is inside)
Edit: Temporarily removed, needs small fix for update url-list.
Edit2: Fixed url-list updating, re-uploaded
Fred
Here are sfs-get and smokey-get scripts for testing.
smokey-get is a Gui-script using yad and wget to download from smokey01.com.
The setup for yad multi-progress bars I stole from `piece of art`: 'yad_wget' see here:
http://askubuntu.com/questions/463012/h ... gress-bars
Works well with smokey01.com host address but not with google-drive (and probably not with a lot more).
Maybe it's possible, but needs a lot more tricks I think because of redirection.
It's amazing what different things can be done with wget and some grep/sed filtering.
smokey-get inside the sfs-get-smokey-get_1.0.1_i386.deb uses main host directory "http://www.smokey01.com/saintless" but can update/modify itself to another address on http://www.smokey01.com/...
Included 'smokey-get-pemasu' is an example of modified smokey-get by using 'Update url-list' and choosing to change main host directory (changed in this case to MAINHOSTDIR="http://www.smokey01.com/pemasu" and changes also long list CHOICE="........" on top of script).
Updating took some time to complete, didnt't try yet to change/update to "http://www.smokey01.com/01micko", it will probably take even longer.
To update url-list the script needs to be in PATH and (re)named 'smokey-get'
Backup of old smokey-get will be made.
The .deb doesn't install .desktop or menu files so need to type sfs-get or smokey-get in terminal.
I'm not exactly sure this will be useful for anyone (or maybe in some other form), I just like exploring things
Attached sfs-get_smokey-get.tar.gz (.deb is inside)
Edit: Temporarily removed, needs small fix for update url-list.
Edit2: Fixed url-list updating, re-uploaded
Fred
- Attachments
-
- sfs-get_smokey-get.tar.gz
- sfs-get and smokey-get
- (77.55 KiB) Downloaded 203 times
-
- smokeyget1.png
- smokey-get in action1
- (61.8 KiB) Downloaded 486 times
-
- smokeyget2.png
- smokey-get in action2
- (122.62 KiB) Downloaded 489 times
-
- smokeyget3.png
- smokey-get in action3
- (111.96 KiB) Downloaded 526 times
-
- smokeyget4.png
- smokey-get in action4
- (52.26 KiB) Downloaded 483 times
Last edited by fredx181 on Sun 17 Aug 2014, 18:22, edited 3 times in total.
Thank you, Fred!
Looks great from the screenshots and the information and it will be useful with sure. I will test it in the next days and report the result.
What comes to my mind at the moment it could be used as DebianDog downloader for fixes and new packages available in separate directory in smokey01.com. This way it will be easy to find latest fixes and new package versions from your sfs-get GUI instead serching them with browser in the thread. I think Puppy has some similar tool.
Toni
Looks great from the screenshots and the information and it will be useful with sure. I will test it in the next days and report the result.
What comes to my mind at the moment it could be used as DebianDog downloader for fixes and new packages available in separate directory in smokey01.com. This way it will be easy to find latest fixes and new package versions from your sfs-get GUI instead serching them with browser in the thread. I think Puppy has some similar tool.
Toni
Hi Toni,
I just thought:
I have a very fast connection so the list gets loaded very quick, when you test it can you notice if it takes long to load list?
There's a 'please wait' message but only when recursive is checked.
Fred
Ok, great, a simplified version for that specially then.What comes to my mind at the moment it could be used as DebianDog downloader for fixes and new packages available in separate directory in smokey01.com. This way it will be easy to find latest fixes and new package versions from your sfs-get GUI instead serching them with browser in the thread.
I just thought:
I have a very fast connection so the list gets loaded very quick, when you test it can you notice if it takes long to load list?
There's a 'please wait' message but only when recursive is checked.
Fred
Hi, Fred.
Added new directory for testing smokey-get downloading fixes:
http://www.smokey01.com/saintless/DebianDog/Fixes/
It is visible after updating the list but I can see the files for download only if this box is marked - Recursive (loading list will be slower) before click OK button.
If it is not marked I see empty directory without files to download.
Can we have it marked by default and is this the right behaviour to show empty directory or I do something wrong?
Toni
Added new directory for testing smokey-get downloading fixes:
http://www.smokey01.com/saintless/DebianDog/Fixes/
It is visible after updating the list but I can see the files for download only if this box is marked - Recursive (loading list will be slower) before click OK button.
If it is not marked I see empty directory without files to download.
Can we have it marked by default and is this the right behaviour to show empty directory or I do something wrong?
Toni
Less than a minute for smokey01.com/saintlessfredx181 wrote:I have a very fast connection so the list gets loaded very quick, when you test it can you notice if it takes long to load list?
There's a 'please wait' message but only when recursive is checked.
I will test this more later with 01micko and different folders.
I think my internet is also fast.
Edit: BTW, your scripts work also in DebianDog-Squeeze
Toni
Hi Toni,
You are very quick in finding a bug
This needs 'fix'
Fred
Yes, the update url-list makes it suddenly not work anymore, every list is empty.If it is not marked I see empty directory without files to download.
Can we have it marked by default and is this the right behaviour to show empty directory or I do something wrong?
You are very quick in finding a bug
This needs 'fix'
Fred
Fred, to explain better the problem I get with empty folders after clicking OK:
If I run smokey-get after installing the deb and choose folder from drop-down list - the folder is populated with files for download.
But if I run Update url-list for smokey01.com/saintless and try to open folder then from drop-down menu - it is empty if check box Recursive (loading list will be slower) is not marked before clicking OK button.
Edit: Sorry, we posted almost at the same time about the same problem. I didn't read your last post. Yes, I usually can't get anything to work right from the first test. Even if there is no bug
Toni
If I run smokey-get after installing the deb and choose folder from drop-down list - the folder is populated with files for download.
But if I run Update url-list for smokey01.com/saintless and try to open folder then from drop-down menu - it is empty if check box Recursive (loading list will be slower) is not marked before clicking OK button.
Edit: Sorry, we posted almost at the same time about the same problem. I didn't read your last post. Yes, I usually can't get anything to work right from the first test. Even if there is no bug
Toni