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...

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/Linux-For-Devices-Articles/Deploying-Linux-Embedded-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...

...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

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.

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.

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

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.

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.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum