Light-Debian-Core-Live-CD-Wheezy + Porteus-Wheezy
Thank you, Sfs!
I'm sure I will find useful improvements. And much easier for me as I can see you keep the additions in small separate modules inside the iso.
To make the download easier for Fred (when he has time to check it out):
https://www.mediafire.com/folder/dxyrko8dams75/
lf-dw-1407.iso is the one we need.
Toni
I'm sure I will find useful improvements. And much easier for me as I can see you keep the additions in small separate modules inside the iso.
To make the download easier for Fred (when he has time to check it out):
https://www.mediafire.com/folder/dxyrko8dams75/
lf-dw-1407.iso is the one we need.
Toni
Yes 080-dd140723.sfs.pfs = 01-filesystem.squashfs &saintless wrote:And much easier for me as I can see you keep the additions in small separate modules inside the iso.
Code: Select all
pfsextract 070-Lf140710.pfs
[url=https://sourceforge.net/projects/puppyrusa/]PuppyRus-Arch[/url]
Thank you, Sfs!
Just did quick test and I like your additions. Not everything downloaded with sfs-get will work on DebianDog but I guess I can change the repository to different one with more compatible modules or create special modules for DebianDog.
This gives me very good base to start working on one more boot method for DebianDog - named PuppyRus-Arch-boot maybe? I have much to explore and understand first.
Fred, (just information for later) the porteus initrd from Sfs's iso can use systemd boot and seems to me this is the fastest boot I ever used. It also does not have modules included inside and we can change the kernels with the same initrd.xz file.
Toni
Just did quick test and I like your additions. Not everything downloaded with sfs-get will work on DebianDog but I guess I can change the repository to different one with more compatible modules or create special modules for DebianDog.
This gives me very good base to start working on one more boot method for DebianDog - named PuppyRus-Arch-boot maybe? I have much to explore and understand first.
Fred, (just information for later) the porteus initrd from Sfs's iso can use systemd boot and seems to me this is the fastest boot I ever used. It also does not have modules included inside and we can change the kernels with the same initrd.xz file.
Toni
Yes. Modules fully compatible only with PuppyRus-Asaintless wrote:Not everything downloaded with sfs-get will work on DebianDog
yessaintless wrote: but I guess I can change the repository to different one with more compatible modules or create special modules for DebianDog.
http://wiki.puppyrus.org/soft/sfs-get
yessaintless wrote: we can change the kernels with the same initrd.xz file.
porteus-puppy-rus-a_initrd requires a special kernel - PuppyRus-A or Porteus
[url=https://sourceforge.net/projects/puppyrusa/]PuppyRus-Arch[/url]
I can boot also with extracted from puppy-initrd-boot kernel-modules.sfs (renamed to 000-kernel.pfs) and vmlinuz using your porteus-puppy-rus-a_initrd.sfs wrote:porteus-puppy-rus-a_initrd requires a special kernel - PuppyRus-A or Porteus
The archive is linked here
Maybe your work will make possible to adapt puppy initrd to use systemd as optional boot. I doubt there is much interest for the moment from systemd here but I will post this information in the forum after some more testing.
Toni
Hi, Stemsee.
I'm not planning to work to adapt puppy initrd to use systemd, but I think it will be possible to boot puppy main module with systemd with initrd.xz from Sfs.
I doubt anyone will try to adapt systemd in puppy reading this thread.
BTW DebianDog default kernel has cryptoloop module that can be activated with modprobe cryptoloop. It can be downloaded here also but works only with 3.2 kernel series:
http://www.smokey01.com/saintless/Fredx ... 3.2.tar.gz
I'm not planning to work to adapt puppy initrd to use systemd, but I think it will be possible to boot puppy main module with systemd with initrd.xz from Sfs.
I doubt anyone will try to adapt systemd in puppy reading this thread.
I think if you create encrypted save file from puppy you can use it with puppy-initrd-boot and DebianDog. The problem is Puppy uses cryptoloop and DebianDog cryptsetup. I'm sure it can be fixed inside initrd or maybe we can create encrypted save somehow with cryptsetup that can be opened with criptoloop. But this is not something i see as priority for me at the moment.Also puppy initrd crypto for DD??
BTW DebianDog default kernel has cryptoloop module that can be activated with modprobe cryptoloop. It can be downloaded here also but works only with 3.2 kernel series:
http://www.smokey01.com/saintless/Fredx ... 3.2.tar.gz
Hi, Sfs.
I have problem to use encrypted save file with porteus-puppy-rus-a_initrd including the last one Maybe this is because I use DebianDog main module but I get error about "/opt/000-kernel/sbin/cryptsetup not found" on boot.
Rebuilded again your initrd.xz with the changes from Fred's initrd1.xz builded for DebianDog:
http://www.smokey01.com/saintless/Debia ... a-crypt.xz
With this initrd.xz I get password prompt and the encrypted save file is checked for errors and loaded.
The changes inside initrd.xz:
1. In linuxrc changed lines 235 and 345:
/opt/000-kernel/sbin/cryptsetup changed to /bin/cryptsetup
2. Added /bin/cryptsetup and /lib/cryptsetup/askpass
I don't know if this information is usefull for you but it works for me this way.
Toni
I have problem to use encrypted save file with porteus-puppy-rus-a_initrd including the last one Maybe this is because I use DebianDog main module but I get error about "/opt/000-kernel/sbin/cryptsetup not found" on boot.
Rebuilded again your initrd.xz with the changes from Fred's initrd1.xz builded for DebianDog:
http://www.smokey01.com/saintless/Debia ... a-crypt.xz
With this initrd.xz I get password prompt and the encrypted save file is checked for errors and loaded.
The changes inside initrd.xz:
1. In linuxrc changed lines 235 and 345:
/opt/000-kernel/sbin/cryptsetup changed to /bin/cryptsetup
2. Added /bin/cryptsetup and /lib/cryptsetup/askpass
I don't know if this information is usefull for you but it works for me this way.
Toni
Encrypted save (in porteus-puppy-rus-a_initrd & porteus_initrd) need squashfs module /base/000-kernel.* (comprising static cryptsetup & kernel modules : dm_crypt cryptd cbc sha256_generic aes_generic aes_x86_64)
To be able to replace, Kernel easier to separate from the base
To be able to replace, Kernel easier to separate from the base
[url=https://sourceforge.net/projects/puppyrusa/]PuppyRus-Arch[/url]
Thank you, Sfs!
I use this 3,13.5-pf kernel that does not have sbin link to /usr/bin/cryptsetup like 3.14.4
3.13.5-pf is the only kernel from your link that starts Xorg without troubles on my very old hardware. I will use my laptop for further testing encrypted save with newer kernel.
Toni
I use this 3,13.5-pf kernel that does not have sbin link to /usr/bin/cryptsetup like 3.14.4
3.13.5-pf is the only kernel from your link that starts Xorg without troubles on my very old hardware. I will use my laptop for further testing encrypted save with newer kernel.
Toni
Re: DebianDog Wheezy live-boot-3x
saintless, a couple of suggestions to improve the quoted post http://murga-linux.com/puppy/viewtopic. ... 457#774457 below:
Mention explicitly that what triggers dzzz's patch is boot code rw-basemount, which replaces a standard boot script with a patched one from /opt/... This information is of interest to people who need to debug the live boot process (boot code debug=1).
Most importantly, file persistence.conf needs to end with a newline. If it doesn't persistence won't work. So the example you give above should be rewritten as:
I spent countless hours debugging live boot to find out why persistence file and partition didn't persist, just to eventually figure out that appending a new line to the file fixed the problem for good.
Thanks for DebianDog!
Fix the typo: persistence.con -> persistence.confsaintless wrote:DebianDog Wheezy live-boot-3x:
To save changes you need to create save file named persistence or ext partition with label persistence + adding persistence.con file inside this save file or save partition (both save file and partition can be encrypted).
...
...
...
Thanks to dzz from Refracta forum and his initrd patch we can use encrypted save file or partition even on the same partition where /live folder is located (boot partition)
...
...
Also you need to create persistence.conf file with this content for full peristence:...Code: Select all
/ union
... ... ...
Mention explicitly that what triggers dzzz's patch is boot code rw-basemount, which replaces a standard boot script with a patched one from /opt/... This information is of interest to people who need to debug the live boot process (boot code debug=1).
Most importantly, file persistence.conf needs to end with a newline. If it doesn't persistence won't work. So the example you give above should be rewritten as:
Code: Select all
/ union
Thanks for DebianDog!
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]
Thank you, Step!
I didn't know about the new empty line in persistence.conf.
I think all is fixed now:
http://www.murga-linux.com/puppy/viewto ... 457#774457
Added some more information at the end of the post about the patched initrd.img in case you need to use RemasterCow with live-boot-3x;
I didn't know about the new empty line in persistence.conf.
I think all is fixed now:
http://www.murga-linux.com/puppy/viewto ... 457#774457
Added some more information at the end of the post about the patched initrd.img in case you need to use RemasterCow with live-boot-3x;
ToniTo use RemasterCow with live-boot3x type in terminal one of the options depending what kind of persistence or no persistence you use (all work well with official initrd.img). With the patched initrd.img /live/image may not point the right location and may need manually creating the link /live/image to /lib/live/mount/persistence/sdX instead /lib/live/mount/medium, but /live/cow is created proper and /live/cow is the important link for RemasterCow to work:
Re: DebianDog Wheezy live-boot-3x
Actually, it is good to remember that ALL text files in Linux should be correctly terminated with a newline. This arises from POSIX standard, which says that each line in a file must end with a newline char:step wrote: Most importantly, file persistence.conf needs to end with a newline. If it doesn't persistence won't work.
http://pubs.opengroup.org/onlinepubs/96 ... tag_03_206
The terminating newline is also specified as necessary by the C standards: ISO/IEC 9899:2011 §7.21.2 Streams
Though many commandline utilities have been written to work with or without the newline, some don't. Command 'diff', for example, would probably complain if it is missing. Some text utilities may not read the last line correctly if the terminating \n is missing - can also be a problem in shell script loops if not carefully written.
The result is that you are certainly not alone, step, in running into an apparently 'weird' bug, which ends up just being caused by an improperly terminated text file. Though I'm well aware of the standard, it is an easy one to miss, and I've also found myself scratching my head in bewilderment because of a missing newline I wasn't aware of in some input file or other I was working with on a project. It should also be a lesson to developers who write utilities and do not take care to account for the special case of newline terminator missing on input file. They should always check for that and account for it (in other words, I blame Debian...). But it is best to stick to the POSIX recommended newline terminator on any files you create anyway since that of course avoids the possible issue.
William
EDIT: I'm happy to add that the make-xhippo-playlist converter utility in DebianDog already specially accounts for input radio stream playlists that have a missing newline... :-)
github mcewanw
Hi Toni and All,
Edit: A more solid solution is here:
http://murga-linux.com/puppy/viewtopic. ... 987#798987
Here's a simple script that automates the switch to systemd.
See it as a preview of what probably will be the future standard (although that may take a long time).
According to the Debian Wiki:
Running the attached script, it works with live-boot and porteus-boot and kernel-line: init=/bin/systemd is not needed.
It modifies /etc/systemd/system/getty.target.wants/getty@tty1.service for autologin as root (instead of /etc/inittab)
Important line in the script (a bit of a hack):
/sbin/init needs to be a relative symlink otherwise it won't work with porteus-boot.
Thanks to sfs I became inspired to try systemd and I must say it's not bad.
Everything works well for me after booting with systemd except "save on exit from console" (so that should be done from X).
To switch back again to the old init scripts do in terminal:
Fred
Edit: A more solid solution is here:
http://murga-linux.com/puppy/viewtopic. ... 987#798987
Here's a simple script that automates the switch to systemd.
See it as a preview of what probably will be the future standard (although that may take a long time).
According to the Debian Wiki:
The above works with live-boot but not with porteus-boot.To test systemd before switching to it by default, you can add the following boot parameter to the kernel:
init=/bin/systemd
Running the attached script, it works with live-boot and porteus-boot and kernel-line: init=/bin/systemd is not needed.
It modifies /etc/systemd/system/getty.target.wants/getty@tty1.service for autologin as root (instead of /etc/inittab)
Important line in the script (a bit of a hack):
Code: Select all
ln -snf ../lib/systemd/systemd init
Thanks to sfs I became inspired to try systemd and I must say it's not bad.
Everything works well for me after booting with systemd except "save on exit from console" (so that should be done from X).
To switch back again to the old init scripts do in terminal:
Code: Select all
apt-get install sysvinit && apt-get purge systemd
- Attachments
-
- systemdswitch.tar.gz
- Script to switch easy to systemd (only for DebianDog)
- (601 Bytes) Downloaded 423 times
Last edited by fredx181 on Fri 12 Sep 2014, 14:35, edited 1 time in total.
Thanks, Fred, I will test it in the next days.fredx181 wrote:Here's a simple script that automates the switch to systemd.
Systemd boot was something very important (in my opinion) missing in porteus-boot and I'm glad you tested the Sfs's version of DebianDog. I have much more to explore there. Many new futures added like read-only save and read-only encrypted save boot, create custom small kernel for the computer that the system runs at the moment (it is only few Mb big) and much more that needs special attention...
Toni
Hi Toni, Fred and everyone,
You guys, are supposed to be vacationing, right?
Decompressing, drinking alcohol, smoking tobacco and indulging yourselves in every imaginable way?
Thank you, Fred for the script, I want to test it. When systemd hits us (and it will sooner, or later), we won't be left unprepared. I read a little bit about how SFS and PuppyRus have implemented it. They didn't discuss it much, they just grabbed the bull by the balls.
I recently removed sudo from DD, see how the operation ends: Processing triggers for systemd ...
You guys, are supposed to be vacationing, right?
Decompressing, drinking alcohol, smoking tobacco and indulging yourselves in every imaginable way?
Thank you, Fred for the script, I want to test it. When systemd hits us (and it will sooner, or later), we won't be left unprepared. I read a little bit about how SFS and PuppyRus have implemented it. They didn't discuss it much, they just grabbed the bull by the balls.
I recently removed sudo from DD, see how the operation ends: Processing triggers for systemd ...
Code: Select all
root@debian:~# apt-get remove --purge sudo
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
sudo*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 1885 kB disk space will be freed.
Do you want to continue [Y/n]? Y
(Reading database ... 28471 files and directories currently installed.)
Removing sudo ...
Purging configuration files for sudo ...
dpkg: warning: while removing sudo, directory '/etc/sudoers.d' not empty so not removed
Processing triggers for systemd ...
root@debian:~#