pUPnGO - 6Mb ISO - Basic Building Block Puplet

A home for all kinds of Puppy related projects
Post Reply
Message
Author
aragon
Posts: 1698
Joined: Mon 15 Oct 2007, 12:18
Location: Germany

#16 Post by aragon »

hi goingnuts,

would it be possible for you to write a little howto about the build-process?

aragon

goingnuts
Posts: 932
Joined: Sun 07 Dec 2008, 13:33
Contact:

#17 Post by goingnuts »

Hi aragon
aragon wrote:would it be possible for you to write a little howto about the build-process?
Made a small how-to - included in the new pUPnGo-V01.1.iso.

Moved lsmod, modprobe and insmod back to pup_412.sfs from zdrv_412.sfs and removed forced module load of qemu and vmware drivers in zdrv_412.sfs.

Kim
Last edited by goingnuts on Sat 23 Jan 2010, 16:05, edited 1 time in total.

User avatar
Lobster
Official Crustacean
Posts: 15522
Joined: Wed 04 May 2005, 06:06
Location: Paradox Realm
Contact:

#18 Post by Lobster »

This is a major achievement. :)
It uses the Linux kernel and (limited) Puppy hardware recognition
scripts. Is that right?

It shows the 'what if' mentality that Barry uses and can be found
throughout Puppy.

I would be interested to know of ideas for applications.

For example:
1 trick Puppys
Device dependent Puppys
Or how about a film, images or music folder Puppy

Puppy
Create your own pedigree
8)
Puppy Raspup 8.2Final 8)
Puppy Links Page http://www.smokey01.com/bruceb/puppy.html :D

aragon
Posts: 1698
Joined: Mon 15 Oct 2007, 12:18
Location: Germany

#19 Post by aragon »

goingnuts wrote:Hi aragon
aragon wrote:would it be possible for you to write a little howto about the build-process?
Made a small how-to - included in the new pUPnGo-V01.1.iso.

Moved lsmod, modprobe and insmod back to pup_412.sfs from zdrv_412.sfs and removed forced module load of qemu and vmware drivers in zdrv_412.sfs.

Kim
hi kim,

thanks for that, but it was a little misunderstanding... i ment a howto to produce 'the core'.

aragon

goingnuts
Posts: 932
Joined: Sun 07 Dec 2008, 13:33
Contact:

#20 Post by goingnuts »

Hi Lobster.
You are right - most of the content is pure P412 original files. This is basically a "cut down size" remaster with a new Busybox and an idea of using zdrv_412.sfs in a new (?) way.

Ideas for application: The first thing (apart from a boring web-server...) that crossed my mind was: A pUPnGO-based clock radio - being able to explain why it is so important to get up in the morning, maybe give a small report of what happened during the day, play some music that fits todays mood, read out loud my mails, call me up at work to get me out of boring meetings - everything voice-to-voice - no screen, mouse or keyboard.
Maybe too exotic though... :wink:

Hi aragon.
I have updated the how-to to be an executable build script for the abbyss-webserver - and it very much shows the structure and principle of the build script used for "the core" pUPnGO-build-script. At the moment my build-script for pUPnGO is a mess with a lot of loose/dead ends - so making it public right now makes no sense.

I also would like to fine-tune the applications available in pUPnGO (mainly dialog based primitive pet-install, grub-install and audio-setup wizard) before including the build-script on the CD-ISO. If someone has such gadgets in their drawer already, I would gladly include them.

The "inspiration source" for the build-script (and also for some of the functions used) has been:

Puppy Linux - boots from and saves to almost everything - runs in ram - SFS-file-structure - feels good...you know!
A series of articles found here: http://www.linuxfordevices.com/c/a/Linu ... d-Systems/
The woof project
The Xwoaf project (web-site down - but basically a build of a one floppy Linux booting to X/JWM)
The byld-project

In principle you take files from a running Linux (or in the pUPnGO case, from the original P412-CD and small bits from your running P412) and melt them together to a new one. Most have been trial and error for me when selecting which files to include...

Kim

aragon
Posts: 1698
Joined: Mon 15 Oct 2007, 12:18
Location: Germany

#21 Post by aragon »

hi kim,

thanks for the answer, no problem.

the info that you were building it top => down is helpful, that has also been the route i've gone for building a small (not in your terms, it's bloated with nearly 40 mb) audio-server puplet without X (http://www.murga-linux.com/puppy/viewtopic.php?t=36326).

aragon

User avatar
puppyiso
Posts: 594
Joined: Tue 13 Jan 2009, 02:27

#22 Post by puppyiso »

Hello, goingnuts

I have been seeing your great works. I always wanted a puppy as small as this. I do understand this is a "building block".

But for someone like me who lacks inner knowledge of Puppy, could you kindly upload the xvesa vesion for me to play adding abiword and scim files? That would make a perfect writer's puppy.

ABSOLUTELY immune to any virus... I no longer exchange computer STD thru USB with others.

I tried and successfully booted but Dejabu with DOS screen again.
I also tried CLI version from puppymartin but ended up error when booted.

I just hope that the vesion works with all_lang.sfs from a Japanese version Puppy. Or... at least with SCIM.

Let me play with the possibilities.

Thank you.

John

goingnuts
Posts: 932
Joined: Sun 07 Dec 2008, 13:33
Contact:

#23 Post by goingnuts »

Hi John
puppyiso wrote: ...could you kindly upload the xvesa vesion for me to play adding abiword and scim files?
I do understand the need for a GUI...Missing it my-self sometimes...But learning a lot being there at the black screen.

As I do not plan to make multiple versions (with different applications) I have made a build script (vesa_jwm_pupngo.sh) that will show you how to create a pUPnGO_V01_XVESA_JWM.ISO. Size growth to 8Mb for the ISO.

It is not Puppys original Xvesa but Kdrive (tinyX). JWM is from original Puppy 412. I have cut down on fonts - although they still are adding approx. 1,5MB...(Xwoaf went down to 28Kb as far as I know)

Trying to use original Puppy Xvesa is too complicated for me - ends up in 15-18MB.

In the script there also is shown how to get ttuuxxx xfe file manager inside using downloaded pets. Uncomment if this is needed.Lynx web browser will not be present. Hope this helps a bit.
Kim

User avatar
puppyiso
Posts: 594
Joined: Tue 13 Jan 2009, 02:27

#24 Post by puppyiso »

Hello, Kim

Thank you for the reply. From GUI back to the dark screen made me feel being blind. I sought after an easy coptout.(Excuse my US English..)

Hmm.. Sounds difficult but I will try it. I feel like going back to high school and learn Algebra all over again.

Thanks.(shivering now..)

John

goingnuts
Posts: 932
Joined: Sun 07 Dec 2008, 13:33
Contact:

#25 Post by goingnuts »

puppyiso wrote:... Sounds difficult ...
It should not be that hard:
- download the script (vesa_jwm_pupngo.sh)
- make it executable
- open a prompt and type ./vesa_jwm_pupngo.sh

...and short after you should have the new pUPnGO_V01_XVESA_JWM.iso sitting in /root/my-documents. Open vesa_jwm_pupngo.sh in Geany for explanations - and make your own modifications if you like.
Kim

User avatar
sinc
Posts: 545
Joined: Wed 22 Jul 2009, 20:35
Location: Tampa, FL USA

#26 Post by sinc »

i don't know anything about scripts really but when i tried to run the xvesa script it did not work all the way. it appears it creates an iso named pUPnGO-v01.1.iso but when it tries to apply xvesa it looks for the iso without the extra .1, just v01.iso. So i renamed the iso and reran the script and it worked but so you know the extra .1 is causing the script to not work right.

User avatar
sinc
Posts: 545
Joined: Wed 22 Jul 2009, 20:35
Location: Tampa, FL USA

#27 Post by sinc »

okay, I can admit that I am not smart enough to make it work. I am trying to use the script with the xvesa_jwm. I went through the script and changed the commands asking for v01.iso to v01.1.iso but now I get a message that says cannot 'stat' /etc/X11R7/bin/jwm.

when i try to boot i get an error that says something like failure to load loop_3 waiting 60 seconds.

any ideas? thanks.

goingnuts
Posts: 932
Joined: Sun 07 Dec 2008, 13:33
Contact:

#28 Post by goingnuts »

sinc wrote:i don't know anything about scripts really but when i tried to run the xvesa script it did not work all the way. it appears it creates an iso named pUPnGO-v01.1.iso but when it tries to apply xvesa it looks for the iso without the extra .1, just v01.iso. So i renamed the iso and reran the script and it worked but so you know the extra .1 is causing the script to not work right.
Hi sinc
You are absolutely right - thank you - I have both versions so did not notice any failure.
I have made a new iso - and to prevent this mess again any future versions will only be tagged inside the iso by a build date. So from now the iso will always be named pUPnGO_V412.iso. I have updated the build-script/howto to reflect this.
The new build has changed layout to reflect the normal Puppy iso directory layout. Otherwise nothing have changed.

I think I am the one not smart enough...
Please try to download the build script again - I have just updated the files so maybe that's why?
Maybe you are missing "ar" - I just tested the script in a fresh frugal P412 and the script fails because "ar" is not present (to unpack .deb-files) Get it here as ar.pet

Again: Thank you!
Kim

User avatar
sinc
Posts: 545
Joined: Wed 22 Jul 2009, 20:35
Location: Tampa, FL USA

#29 Post by sinc »

Kim, I have tried and I still cannot get the vesa build to boot up into a GUI. I have tried to run the build script from Puppy 431 w/ the devx and from Dpup without the devx. On both of them I downloaded the ar.pet and applied it. I wanted to copy the terminal info and paste it here so you could see it but I cannot figure out how to copy from rxvt or mrxvt. I know its supposed to be middle-click but I have a laptop without a middle button and when I try to click simultaneously it simply reruns the script that I highlighted. But I still get the error "cannot stat /etc/X11R7/bin/jwm."

should i be trying to build it from 412, does that matter?

I'm sorry for my lack of knowledge, I have used Puppy for about a year and am fairly familiar with it but I am (obviously) not a programmer of any kind. Thanks.

User avatar
ttuuxxx
Posts: 11171
Joined: Sat 05 May 2007, 10:00
Location: Ontario Canada,Sydney Australia
Contact:

#30 Post by ttuuxxx »

sinc wrote:Kim, I have tried and I still cannot get the vesa build to boot up into a GUI. I have tried to run the build script from Puppy 431 w/ the devx and from Dpup without the devx. On both of them I downloaded the ar.pet and applied it. I wanted to copy the terminal info and paste it here so you could see it but I cannot figure out how to copy from rxvt or mrxvt. I know its supposed to be middle-click but I have a laptop without a middle button and when I try to click simultaneously it simply reruns the script that I highlighted. But I still get the error "cannot stat /etc/X11R7/bin/jwm."

should i be trying to build it from 412, does that matter?

I'm sorry for my lack of knowledge, I have used Puppy for about a year and am fairly familiar with it but I am (obviously) not a programmer of any kind. Thanks.
Hi sinc I haven't tried this release at all, but do you have all JWM dependencies?
type
ldd /etc/X11R7/bin/jwm
ttuuxxx
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)

goingnuts
Posts: 932
Joined: Sun 07 Dec 2008, 13:33
Contact:

#31 Post by goingnuts »

sinc wrote:should i be trying to build it from 412, does that matter?
Hi sinc
YES! It is based on P412 - I have not tested any other versions with the build script. Sorry for all the trouble you have - It should be straight forward - with the speed of light.... :shock:
Kim

User avatar
Keef
Posts: 987
Joined: Thu 20 Dec 2007, 22:12
Location: Staffordshire

#32 Post by Keef »

I can confirm that the build script works on 412 for me. It throws up the "cannot stat /etc/X11R7/bin/jwm." error, but the iso is still built correctly.
The problem with 431 is the different squashfs version - pupngo is unable to load the zdrv which contains the X stuff.
One observation though - the shutdown screen (save to file etc) does not function. Works ok in the 'vanilla' pupngo though.

goingnuts
Posts: 932
Joined: Sun 07 Dec 2008, 13:33
Contact:

#33 Post by goingnuts »

Keef wrote:I can confirm that the build script works on 412..

One observation though - the shutdown screen (save to file etc) does not function. Works ok in the 'vanilla' pupngo though.
Thank you Keef for confirming it works - I was beginning to have my doubts even though it build again and again here...

The script to not create an optimized vesa/jwm situation - quiting vesa is "unclean" - and I think thats why the save script fails - something is running in the background...but I have not been able to fix the shutdown (exit to prompt). If someone could give a solution...Please!

Also I have found that if you formate a partition and use the save script - pupngo do not load everything thats in the zdrv afterwards - thats a pity. If you say no to copy pup_412.sfs to drive when saving - it will still be copied when booting again. Guess thats original Puppy 412 behavior. First boot after creating personal save file is ok - at this boot pupngo copies pup_412.sfs to the partition - but zdrv-content still works. At second boot (meaning pup_412.sfs is on the partition) zdrv-content are not loaded.

So the principle having additional programs and stuff in the zdrv works when booting from a CD - but not after a save to disk. Guess it would demand a hack of init in initrd.

Working on a fix for some of it...
Kim

User avatar
Keef
Posts: 987
Joined: Thu 20 Dec 2007, 22:12
Location: Staffordshire

#34 Post by Keef »

@goingnuts
I lack the knowledge to help with the JWM issue, but maybe this link will help. Seems to refer to a similar problem, but its all a bit over my head.
See the post by Clarf (dated Dec 02 09, about 3/4 down the page)

goingnuts
Posts: 932
Joined: Sun 07 Dec 2008, 13:33
Contact:

#35 Post by goingnuts »

Your hint was good Keef! Nailed it down to jwm exit not working as expected. At start of Xvesa and jwm errors must be redirected to a tempfile (tmp/xerrs.log) and afterwards to /dev/null. In jwm "exit to prompt" using normal menu program instead of jwm shutdown gives "clean" exit to prompt. And afterwards poweroff and save is working again.

A new build of the pUPnGO have been uploaded - this time with a renamed pup_412.sfs (now named pup_412pupngo.sfs) to avoid conflict with any savefiles of normal P412 on your HD. This is meant as a substitute for the Xvesa_jwm-build script. Includes:
Xvesa, jwm, lynx and "lobotomised" versions of grubconfig and bootmanager running in dialog only. I have managed to strip fonts down to 20K.

Still the purpose is to work on the basic non-GUI pUPnGO but maybe Xvesa/jwm should be part of the basic building block?

The new upload is 8Mb and not using the zdrv-approach, still boots in 16 Mb ram in vmware but: do not expect a beauty-box - but it still is a tiny fellow...
Overview:
Kernel (original) 1,6Mb
initrd.gz (original) 1,3Mb
pup_412pUPnGO.sfs 4,9Mb

Post Reply