Hi, Fred.fredx181 wrote:If this is really an obstacle, I've thought about a different setup:
- I can change extension to .squashfs instead of .xzm in initrd1.xz
- put 021-apps-porteus.squashfs in live/debian/modules folder.
- put 01-filesystem.squashfs in live/debian/base
Didn't test this yet but it should work I think if there is included in boot options for DebianDog-live-boot: "live-media-path=/live/debian/base"
It's easy to do but do we want a change like this.
Not an obstacle since I'm sure the user will chose one of the boot ways and delete the second initrd file.
But from what I tested in the past I think it will not work. The last subfolder for live boot has be named /live so it should be live-media-path=/live/debian/base/live. At least with Grub Legacy the last subfolder has to be named /live.
If it works and you see this easier than editing debdog-install I do not mind. I will rebuild the kernel separate modules for the new live-media-path but I might need some help to edit the existing 3 porteus initrd.xz files for DebianDog.
Edit: I found my post about testing live-media-path. I'm sure it does not work if last subfolder is not named /live with Grub legacy. I guess boot=live kernel paramether is the problem to change last subfolder to different name? I'm not sure boot=live can be changed:
Toni...this is the way to use debian live in different folder (/debian-wheezy for example). Move live folder in /debian-wheezy and use this boot code:
Code: Select all
title Wheezy 1 rootnoverify (hd0,0) kernel /debian-wheezy/live/vmlinuz1 boot=live config persistence live-media-path=/debian-wheezy/live/ quickreboot noautologin noeject initrd /debian-wheezy/live/initrd1.img boot