Light-Debian-Core-Live-CD-Wheezy + Porteus-Wheezy
Hi Sergey, Hi Toni
As I said the linux-live-kit boot method worked fine with grub4dos but not with cd/iso.
I found it needs special treatment by updating isolinux.bin if you want to change default name (like "slax" or 'live")
So got it working now with default name "live" (is also default directory)
linux-live-wheezy2.iso:
https://drive.google.com/file/d/0ByBgCD ... sp=sharing
I see this as experimental for now but maybe it can be useful in future.
The creator of alphaOS: simargl, went into this direction after using puppy method at first and made a couple of it's own cheatcodes with linux-live-scripts.
It's a shame he suddenly decided to go for 64bit only, because I liked Arch and his way of approaching and knowledge.
But shortly after that, as a miracle, I saw this thread and was happy again
EDIT: If you boot the iso, make sure there isn't a directory "live" with squashfs file(s) inside on your hd or usb, because it will detect that first and will probably fail then.
Needs to be worked on to prevent this (changing default extension could fix this).
Fred
As I said the linux-live-kit boot method worked fine with grub4dos but not with cd/iso.
I found it needs special treatment by updating isolinux.bin if you want to change default name (like "slax" or 'live")
So got it working now with default name "live" (is also default directory)
linux-live-wheezy2.iso:
https://drive.google.com/file/d/0ByBgCD ... sp=sharing
I see this as experimental for now but maybe it can be useful in future.
The creator of alphaOS: simargl, went into this direction after using puppy method at first and made a couple of it's own cheatcodes with linux-live-scripts.
It's a shame he suddenly decided to go for 64bit only, because I liked Arch and his way of approaching and knowledge.
But shortly after that, as a miracle, I saw this thread and was happy again
EDIT: If you boot the iso, make sure there isn't a directory "live" with squashfs file(s) inside on your hd or usb, because it will detect that first and will probably fail then.
Needs to be worked on to prevent this (changing default extension could fix this).
Fred
Hi Sergey
I hope the iso I send gives you more insight.
Fred
I have difficulties to follow all you did but it's good to see you have grub4dos option now.But I expect that also loaded '01-v3.squashfs' from 'Light-Wheezy-2'
This is not happening.
I hoped in this way to combine into a single image Debian and Porteus,
2 different ways to download Debian-live and Porteus-to-Debian.
Fred, where am I wrong?
I hope the iso I send gives you more insight.
Fred
AbiWord.sfs - 2,6Mb:
http://smokey01.com/saintless/Fredx181/022-abiword.sfs
Load with SFS-loader and use taskbar icon or type abiword in terminal.
taskbar icon need to use Logout->Restart IceWM to appear.
http://smokey01.com/saintless/Fredx181/022-abiword.sfs
Load with SFS-loader and use taskbar icon or type abiword in terminal.
taskbar icon need to use Logout->Restart IceWM to appear.
Downloading now. I have never tried the Porteus version, but will keep and eye out on Fred's postings and test that sometime.saintless wrote:This is only testing version mostly for development suggestions.
Download DebianDog-PorteusDog-test.iso -103Mb with separate kernel module here:
http://www.smokey01.com/saintless/Light ... g-test.iso
Cheers, William
github mcewanw
Hi, William.
In a few days I will upload another version with Fred's suggestions about relative symlinks and mountlink fix.
BTW this is the same DebianDog CD version with the latest fixes.
The difference is it has two initrd and only one vmlinuz file.
You can boot standard DebianDog as we do now or PorteusDog using the same squashfs modules symlinked to /live/debian/base folder.
This is the form I see DebianDog continue further - to be combined with porteus boot option using the same squashfs modules.
Toni
In a few days I will upload another version with Fred's suggestions about relative symlinks and mountlink fix.
BTW this is the same DebianDog CD version with the latest fixes.
The difference is it has two initrd and only one vmlinuz file.
You can boot standard DebianDog as we do now or PorteusDog using the same squashfs modules symlinked to /live/debian/base folder.
This is the form I see DebianDog continue further - to be combined with porteus boot option using the same squashfs modules.
Toni
Hi All!
1.
How to add a button "keyboard switcher" on the panel (preferably with the country-flag icons): Eng--<other_language>
For example the Germans need umlauts, the Spanish have the letter N with tilde above.
In my case it Eng--Rus
Cyrillic (and not Latin) exists not only in Russian.
But there are many languages where no Latin or Cyrillic.
And then there is the Middle East, Southeast Asia and India.
In all these cases need the keyboard switcher.
Of course need more fonts setting - but this is a concern of every individual user.
I did switch keyboard with country flags in LXDE, but in JWM and XFCE that does not work.
2.
Need a hint:
I know how to make sfs(xzm)-module with programs to after connecting this module in system, a new menu item appears to start the program. But this only applies to XFCE (LXDE).
I make file <program-name>.desktop and place it in /usr/local/share/applications/ (or in usr/share/applications/).
I do not know how to do it in JWM. Now I can run the connected program only through the terminal.
3.
AbiWord.sfs works in 'Light-Wheezy' - thanks Toni !
In 'Porteus-Wheezy' message about missing lib.
Sergey.
1.
How to add a button "keyboard switcher" on the panel (preferably with the country-flag icons): Eng--<other_language>
For example the Germans need umlauts, the Spanish have the letter N with tilde above.
In my case it Eng--Rus
Cyrillic (and not Latin) exists not only in Russian.
But there are many languages where no Latin or Cyrillic.
And then there is the Middle East, Southeast Asia and India.
In all these cases need the keyboard switcher.
Of course need more fonts setting - but this is a concern of every individual user.
I did switch keyboard with country flags in LXDE, but in JWM and XFCE that does not work.
2.
Need a hint:
I know how to make sfs(xzm)-module with programs to after connecting this module in system, a new menu item appears to start the program. But this only applies to XFCE (LXDE).
I make file <program-name>.desktop and place it in /usr/local/share/applications/ (or in usr/share/applications/).
I do not know how to do it in JWM. Now I can run the connected program only through the terminal.
3.
AbiWord.sfs works in 'Light-Wheezy' - thanks Toni !
In 'Porteus-Wheezy' message about missing lib.
Sergey.
Hi Toni, Sergey, all
Important update for the porteus initrd-3.2.0-4-486.xz and Porteus-Wheezy2-deb-kernel.iso.!!
(and also for Toni's new DebianDog-PorteusDog-test.iso:
Replace initrd1.xz with the downloaded initrd-3.2.0-4-486.xz)
I recentlly found that the first parameter in boot options does not work e.g.:
noauto parameter doesn't work, or e.g. :
from= doesn't work, resulting in failure to find data.
After investigating I found that the original porteus kernel (appearantly) append "quiet" followed by a space at the start of /proc/cmdline.
Well, that missing space results in failure of the first parameter.
So I edited linuxrc to create that space and put the outcome of "cat /proc/cmdline" + added space in /mnt/live/etc/cmdline.
Further replaced every "/proc/cmdline" with "/etc/cmdline" in linuxrc.
So now it works fine!
new initrd-3.2.0-4-486.xz:
https://drive.google.com/file/d/0ByBgCD ... sp=sharing
new Porteus-Wheezy2-deb-kernel.iso:
https://drive.google.com/file/d/0ByBgCD ... sp=sharing
Regards
Fred
Important update for the porteus initrd-3.2.0-4-486.xz and Porteus-Wheezy2-deb-kernel.iso.!!
(and also for Toni's new DebianDog-PorteusDog-test.iso:
Replace initrd1.xz with the downloaded initrd-3.2.0-4-486.xz)
I recentlly found that the first parameter in boot options does not work e.g.:
Code: Select all
kernel /live/vmlinuz1 noauto from=/live
Code: Select all
kernel /live/vmlinuz1 from=/live copy2ram
After investigating I found that the original porteus kernel (appearantly) append "quiet" followed by a space at the start of /proc/cmdline.
Well, that missing space results in failure of the first parameter.
So I edited linuxrc to create that space and put the outcome of "cat /proc/cmdline" + added space in /mnt/live/etc/cmdline.
Further replaced every "/proc/cmdline" with "/etc/cmdline" in linuxrc.
So now it works fine!
new initrd-3.2.0-4-486.xz:
https://drive.google.com/file/d/0ByBgCD ... sp=sharing
new Porteus-Wheezy2-deb-kernel.iso:
https://drive.google.com/file/d/0ByBgCD ... sp=sharing
Regards
Fred
Sorry, forgot to upload, starting now, may take some time.new Porteus-Wheezy2-deb-kernel.iso:
https://drive.google.com/file/d/0ByBgCD ... sp=sharing
EDIT: 14 minutes later:
New revision of Porteus-Wheezy2-deb-kernel.iso uploaded:
https://drive.google.com/file/d/0ByBgCD ... sp=sharing
Fred
Thank you Fred!
1.
As one character in the Indian tale "The Golden Antelope":
"Now we see them, we now compare them."
2.
I forgot to say earlier, but now remembered:
relogin (Menu-->logout-->restartX) in 'Porteus-Wheezy' does not fulfill until the end - startx directive is not satisfied, it has to be entered from the keyboard.
3.
I'm joined on one CD-ISO-image of the 'Debian-Wheezy' and 'Porteus-Wheezy' as well as the boot-manager took grub4dos.
This option certainly has a larger size, but you can switch not only between different methods of loading (debian-live & porteus), but also between different WM (ICEWM & XFCE). I like this opportunity.
Sergey.
1.
As one character in the Indian tale "The Golden Antelope":
"Now we see them, we now compare them."
2.
I forgot to say earlier, but now remembered:
relogin (Menu-->logout-->restartX) in 'Porteus-Wheezy' does not fulfill until the end - startx directive is not satisfied, it has to be entered from the keyboard.
3.
I'm joined on one CD-ISO-image of the 'Debian-Wheezy' and 'Porteus-Wheezy' as well as the boot-manager took grub4dos.
This option certainly has a larger size, but you can switch not only between different methods of loading (debian-live & porteus), but also between different WM (ICEWM & XFCE). I like this opportunity.
Sergey.
Last edited by sklimkin on Wed 05 Feb 2014, 19:13, edited 1 time in total.
Thank you, Fred.fredx181 wrote:Sorry, forgot to upload, starting now, may take some time.new Porteus-Wheezy2-deb-kernel.iso:
https://drive.google.com/file/d/0ByBgCD ... sp=sharing
EDIT: 14 minutes later:
New revision of Porteus-Wheezy2-deb-kernel.iso uploaded:
https://drive.google.com/file/d/0ByBgCD ... sp=sharing
Fred
I will upload this one on the site.
Thank you for the fixed initrd also.
Toni
Hi, Sergey.
I use Alt+Shift to change the keyboard layout. after running:
Then after loading the sfs module run update-menus in terminal and it will appear in the start menu.
You can also add start icon in taskbar from /etc/x11/icewm/toolbar
Toni
I don't know how you can do this in iceWm or JWM. The taskbur program icons are in /etc/x11/icewm/toolbar You can experiment with this file.sklimkin wrote:1.
How to add a button "keyboard switcher" on the panel (preferably with the country-flag icons): Eng--<other_language>
For example the Germans need umlauts, the Spanish have the letter N with tilde above.
I use Alt+Shift to change the keyboard layout. after running:
Code: Select all
dpkg-reconfigure keyboard-configuration
You need a file for the program in /usr/share/menu Open one of the files there and you will see what is needed.2.
Need a hint:
I know how to make sfs(xzm)-module with programs to after connecting this module in system, a new menu item appears to start the program. But this only applies to XFCE (LXDE).
I make file <program-name>.desktop and place it in /usr/local/share/applications/ (or in usr/share/applications/).
I do not know how to do it in JWM. Now I can run the connected program only through the terminal.
Then after loading the sfs module run update-menus in terminal and it will appear in the start menu.
You can also add start icon in taskbar from /etc/x11/icewm/toolbar
I will check out in the next days what is needed for porteus-wheezy.3.
AbiWord.sfs works in 'Light-Wheezy' - thanks Toni !
In 'Porteus-Wheezy' message about missing lib.
Toni
Uploaded here:fredx181 wrote: EDIT: 14 minutes later:
New revision of Porteus-Wheezy2-deb-kernel.iso uploaded:
https://drive.google.com/file/d/0ByBgCD ... sp=sharing
http://smokey01.com/saintless/Porteus-W ... kernel.iso
Toni
Thanks, Tonisaintless wrote:Uploaded here:fredx181 wrote: EDIT: 14 minutes later:
New revision of Porteus-Wheezy2-deb-kernel.iso uploaded:
https://drive.google.com/file/d/0ByBgCD ... sp=sharing
http://smokey01.com/saintless/Porteus-W ... kernel.iso
Toni
I've made first concept of remastercow.
As you said it would be a matter of modifying RemasterDog.
Same concept by copying to drive of choice (working directory)
Tell me if you want something added or left out.
Wouldn't it be good to give some info (using yad) in the script on how to handle:
I mean, to inform the user about sequence (01. 02, 03) of modules otherwise it gets messed up with dpkg.
Also added new remasterdog script to the archive with small fix:
yad info text at the end now shows correct path for where module is created (it showed before: inside working dir)
remaster.tar.gz:
https://drive.google.com/file/d/0ByBgCD ... sp=sharing
Another thing, about your latest:
System-tray is showing in upper-left corner (see picture), or sometimes something simular but empty shows there and systray is correct.
Also what I would like in porteus-boot version is in icewm-menu an entry for special porteus-savefile-create instead of live-rw create, now there's only the prompt for it at shutdown.
Of course tell me if you have reason to have it the way it is now or if you need help to change it.
Regards
Fred
- Attachments
-
- systray-in-upperleft.png
- (69.96 KiB) Downloaded 360 times
Hi Sergey,
Do you mean by changing tty you can switch WM?
(don't tell Toni about this, he may get over-excited )
Fred
Which version of 'Porteus-Wheezy' is that exactly?2.
I forgot to say earlier, but now remembered:
relogin (Menu-->logout-->restartX) in 'Porteus-Wheezy' does not fulfill until the end - startx directive is not satisfied, it has to be entered from the keyboard.
That's very nice!3.
I'm joined on one CD-ISO-image of the 'Debian-Wheezy' and 'Porteus-Wheezy' as well as the boot-manager took grub4dos.
This option certainly has a larger size, but you can switch not only between different methods of loading (debian-live & porteus), but also between different WM (JWM & XFCE). I like this opportunity.
Do you mean by changing tty you can switch WM?
(don't tell Toni about this, he may get over-excited )
Fred
Hi, Fred
What is your Processor and how much RAM do you have? This is exactly what made me put sleep 2 in /root/.icewm/startup After that I changed it in sleep 1. I still get this when I use 128Mb RAM computer but it is OK on 1,5 Ghz + 512RAM.
This is caused from the maximum xz compression I think. As Terry wrote it takes more CPU and RAM. If I use gzip compression even on 128Mb ram it works without this issue.
Toni
Thank you very much! I will see how it works as it is and test what exactly we need and get back to you on this in a few days.I've made first concept of remastercow.
As you said it would be a matter of modifying RemasterDog.
Same concept by copying to drive of choice (working directory)
Tell me if you want something added or left out.
Wouldn't it be good to give some info (using yad) in the script on how to handle:
I mean, to inform the user about sequence (01. 02, 03) of modules otherwise it gets messed up with dpkg.
Also added new remasterdog script to the archive with small fix:
yad info text at the end now shows correct path for where module is created (it showed before: inside working dir)
remaster.tar.gz:
https://drive.google.com/file/d/0ByBgCD ... sp=sharing
Do you mean 01-v3 or the iso with Porteus and Debian boot, Fred?Another thing, about your latest:
System-tray is showing in upper-left corner (see picture), or sometimes something simular but empty shows there and systray is correct.
What is your Processor and how much RAM do you have? This is exactly what made me put sleep 2 in /root/.icewm/startup After that I changed it in sleep 1. I still get this when I use 128Mb RAM computer but it is OK on 1,5 Ghz + 512RAM.
This is caused from the maximum xz compression I think. As Terry wrote it takes more CPU and RAM. If I use gzip compression even on 128Mb ram it works without this issue.
I'm working on updated iso at the moment and I think I fixed all you wrote before. Can you point me the exact steps to include this porteus save file?Also what I would like in porteus-boot version is in icewm-menu an entry for special porteus-savefile-create instead of live-rw create, now there's only the prompt for it at shutdown.
No way It is difficult enough for me to make debian and porteus boot iso works well.don't tell Toni about this, he may get over-excited
Toni
Hi Toni,
Hi Fred,
Porteus-Wheezy2-deb-kernel.iso - 2014.02.02
linux-live-wheezy2.iso - 2014.02.05
Porteus-Wheezy2-deb-kernel.iso - 2014.02.05
Earlier versions did not look.
But that's also very nice!
Sergey.
Thank you, because I forgot this magical command.Toni: dpkg-reconfigure keyboard-configuration
The system has successfully made itself these files, but the menu does not show up.Toni: You need a file for the program in /usr/share/menu
... but the menu does not show up.Toni: Then after loading the sfs module run update-menus
Hi Fred,
Light-Wheezy2-porteus.iso - 2014.01.13Fred: Which version of 'Porteus-Wheezy' is that exactly?
Porteus-Wheezy2-deb-kernel.iso - 2014.02.02
linux-live-wheezy2.iso - 2014.02.05
Porteus-Wheezy2-deb-kernel.iso - 2014.02.05
Earlier versions did not look.
No, no - only by reboot.Fred: Do you mean by changing tty you can switch WM?
But that's also very nice!
Sergey.
- Attachments
-
- deb+port-in-oe-CD-ISO.png
- Tree of My CD-ISo-image
- (66.15 KiB) Downloaded 267 times
Build scripts for small debian live images (similar to woof)
Hi Tony and all,
I have posted about my Debian live build scripts in the "puppy linux projects" section. I know that you are all under full steam and pressing forward, but maybe you have a look. A short description:
The build system is a wrapper for the live build scripts which allows to organise the creation of the iso in different modules. I used also some code from the web to automaticly purge out docs, manuals and locales, and remove unnecessary files. includes were kept, so compiling is not broken.
I have an example iso with icewm, rox xfe, iceweasel and wicd + wireless tools and free firmware drivers.
Some differences which I am aware off:
it uses the original debian kernels only
it uses live-build tools version 3
boot folder is still included.
At the moment it has fewer apps compared to Light-Debian-Core
I saw that you published a new iso, I thought this might be a good opportunity to bring the build scripts in the arena.
As we discussed earlier there are some drawbacks, but in the long term I see advantages.
cheers and all the best
emil
I have posted about my Debian live build scripts in the "puppy linux projects" section. I know that you are all under full steam and pressing forward, but maybe you have a look. A short description:
The build system is a wrapper for the live build scripts which allows to organise the creation of the iso in different modules. I used also some code from the web to automaticly purge out docs, manuals and locales, and remove unnecessary files. includes were kept, so compiling is not broken.
I have an example iso with icewm, rox xfe, iceweasel and wicd + wireless tools and free firmware drivers.
Some differences which I am aware off:
it uses the original debian kernels only
it uses live-build tools version 3
boot folder is still included.
At the moment it has fewer apps compared to Light-Debian-Core
I saw that you published a new iso, I thought this might be a good opportunity to bring the build scripts in the arena.
As we discussed earlier there are some drawbacks, but in the long term I see advantages.
cheers and all the best
emil
Last edited by emil on Wed 05 Feb 2014, 20:27, edited 1 time in total.
Hi Toni
I have 1GB ram.
Besides this issue with systray-on-upperleft:
We discussed earlier about using 512k or 1024k blocksize with xz compression.
I still prefer the 512k (without -Xbcj option) because I experienced:
-- lower RAM usage
-- faster boot (especially X loading faster)
At the cost of larger filesize of course, but not much.
With gz compression I got even better results concerning the above and also -very mysterious- got "slim" DM working, with XFCE though (but could NOT with xz compression).
----------------------------------------------------------------
Fred
I mean the iso with Porteus and Debian boot.Do you mean 01-v3 or the iso with Porteus and Debian boot, Fred?
Don't know about processor, how do I find out? It's no-pae I know.What is your Processor and how much RAM do you have?
I have 1GB ram.
---------------------------------------------------------------This is caused from the maximum xz compression I think. As Terry wrote it takes more CPU and RAM. If I use gzip compression even on 128Mb ram it works without this issue.
Besides this issue with systray-on-upperleft:
We discussed earlier about using 512k or 1024k blocksize with xz compression.
I still prefer the 512k (without -Xbcj option) because I experienced:
-- lower RAM usage
-- faster boot (especially X loading faster)
At the cost of larger filesize of course, but not much.
With gz compression I got even better results concerning the above and also -very mysterious- got "slim" DM working, with XFCE though (but could NOT with xz compression).
----------------------------------------------------------------
Sure!No way Smile It is difficult enough for me to make debian and porteus boot iso works well.
Fred