pUPnGO - 6Mb ISO - Basic Building Block Puplet

A home for all kinds of Puppy related projects
Post Reply
Message
Author
goingnuts
Posts: 932
Joined: Sun 07 Dec 2008, 13:33
Contact:

pUPnGO - 6Mb ISO - Basic Building Block Puplet

#1 Post by goingnuts »

Update 060211: Thought the description needed a little update after release of vers 060211 and the special 080211 (running TinyCore as a sfs-extension)...
pUPnGO is a basic building block - extract of the very "core" of Puppy Linux...
Gently modified org. initrd (changed BB and ntfsg3), mainssfs is CLI only and contains only static build programs.
This gives a basis to continue building all static or using any libc you want (ulibc, libc old or new etc.- any version) even loaded as a sfs after creating a save file or load it with otf-sfs-loader. So you can install/uninstall libc without breaking the core system. Busybox resides in initrd.gz and are copied at boot if not present...

Contains file-manager (asmfile), udevd, mksquashfs, grub and most of the needed setup-scripts.

Included on the CD also a GUI-example - as a sfs-package but can be installed (pkginstall.sh also handle install of sfs-files). All set-up-wizards and other scripts should work in console and in GUI (cli/dialog/Xdialog - the later only if present...).

Now personal builds can be done keeping the "core" and adding sfs-files with the new personal stuff - and trespassing the org. 6 sfs-file restriction - load 150 or more - if you have the hardware power. Exclamation

Core sfs-file size: 1344K - 3800K installed
Example GUI-sfs: 2000K - 3800 installed
On top of that zdrv 21MB with all org P412 drivers, kernel 1500K and initrd.gz 1300K. And zdrvctr is included so you only have to bother your HD with the drivers you need.

Videos:
pUPnGO_V412_080211.iso special version running TC

pUPnGO_V412_060211 running GUI as a sfs-extension

pUPnGO_V412_060211 running BL3 (BasicLinux) as a sfs-extension

pUPnGO_V412_060211 running xwoaf as a sfs-extension

pUPnGO_V412_041210.iso [29Mb] version 041210 (not for amd K6) - use pUPnGO_V412_060211.iso for that.

Original description below:
This Puplet is made from P412 and meant as a basic building block for stand alone applications or embedded systems. Command line only - no GUI. Boots systems with RAM down to 16Mb without swap.

Included:

* Original kernel and initrd.gz
* New Busybox-1.15-3 with almost all features enabled
* Original keyboard and locale setup
* Original save-script
* Ability to use SFS
* Ability to use kernel drivers in zdrv_412.sfs
* New DHCP-Client
* Included lynx2-8-7 as text-only webbrowser

For test purpose net-drivers for qemu and vmware is included.
20.01.10: Iso-layout updated.
23.01.10: lsmod, insmod, modprobe moved back to pup_412.sfs and included a small how-to.
05.02.10: Major renaming of iso and revisions of build scripts (tried to remove bugs and general mess). Content not changed.
12.02.10: New iso uploaded - fix for personal save and missing zdrv-pickup at boot after saving.
23.05.10: New build with modified kernel (ipv6 & fb support), hacked initrd/init so zdrv-412.sfs will mount at every boot, various custumscripts (DISPLAY;SFS-MANAGER; GRUB HD INSTALL; TIME AND DATE MANAGER - type CONTROLPANEL at prompt) and X with JWM.
Full P412 drivers in zdrv_412.sfs - reduce at poweroff by using zdrvctr - potential reduction from 21MB to approx. 2MB.
13.06.10: New build with full glibc-2.6.1-1. This seems a must for now as mounted additional SFS-files do not update /lib/-content.
20.08.10: New builds uploaded.
04.12.10: Last 2010 version
060211: New build - most like 041210 but run on amdK6 too. Fixed pcmcia shutdown bug and included aumix and start up script for sound settings. Included bl3-sfs and xwoaf-sfs in "/demo" on iso to promote/demonstrate the versatility of pUPnGO in relation to further build. Included also static version of links.
080211: Special build with TC as GUI. TC version in squashfile is tinycore_2.11.6. NOTE: This is NOT a new puplet - no updates, no help or troubleshooting - its just a demo of pUPnGOs possibilities.
060611: New build using kernel from Puppy 216.

Info and downloads
Last edited by goingnuts on Mon 06 Jun 2011, 17:54, edited 14 times in total.

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#2 Post by nooby »

Would it work best on old computers then?
which ones have you tested it on so far?
Kind of cute that it is that small.
I use Google Search on Puppy Forum
not an ideal solution though

User avatar
8-bit
Posts: 3406
Joined: Wed 04 Apr 2007, 03:37
Location: Oregon

#3 Post by 8-bit »

Have you tried booting from a burnt iso of your offering?
The reason I ask is that after downloading your iso and clicking on it to mount it, I see a directory called isolinux.
The files that should be in the root of the CD directory for booting are in that directory.
I have yet to burn a CD from the ISO, but I am curious to if it would even boot in it's present form.

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

#4 Post by goingnuts »

Hi nooby
I have only tested in qemu, vmware and on my own machine (a more modern one with "lots" of RAM). So the ram statement above comes from adjusting ram in virtual machines. Vmware boots OK with 16Mb RAM whereas qemu seems more happy with 20Mb (otherwise it takes ages to boot).

and

Hi 8-bit
I did burn a DVD - and it boots ok. I haven't access to a CD-rom drive...or a blank CD at the moment...

Seems I have to dig up an old 486 with CD-rom and 16Mb RAM...

best regards
Kim

User avatar
dejan555
Posts: 2798
Joined: Sun 30 Nov 2008, 11:57
Location: Montenegro
Contact:

#5 Post by dejan555 »

This seems interesting, none striped it this low before, I only tried it in qemu but will load it on my desktop pc live.
puppy.b0x.me stuff mirrored [url=https://drive.google.com/open?id=0B_Mb589v0iCXNnhSZWRwd3R2UWs]HERE[/url] or [url=http://archive.org/details/Puppy_Linux_puppy.b0x.me_mirror]HERE[/url]

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

#6 Post by ttuuxxx »

would be cool if you added the JWM hack that techno came up with, http://murga-linux.com/puppy/viewtopic.php?t=51200to run jwm without rox, and then maybe a small file manager like file-browser http://murga-linux.com/puppy/viewtopic. ... 374#383374
hmmm probably would need Vesa for video also, but still were talking around 2MB because of Vesa. But still to with a lite desktop, It would be real fun.
ttuuxxx
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#7 Post by nooby »

Yes that would be very helpful.

How is this one different from TinuCore Linux?
Appart from being Puppy related that is.
I use Google Search on Puppy Forum
not an ideal solution though

raffy
Posts: 4798
Joined: Wed 25 May 2005, 12:20
Location: Manila

different

#8 Post by raffy »

nooby wrote:How is this one different from TinyCore Linux?
Tinycore boots into X.
Puppy user since Oct 2004. Want FreeOffice? [url=http://puppylinux.info/topic/freeoffice-2012-sfs]Get the sfs (English only)[/url].

User avatar
puppymartin
Posts: 207
Joined: Sun 29 Mar 2009, 18:59
Location: The Netherlands
Contact:

#9 Post by puppymartin »

Very nice!

CLInet (11Kb Network Wizard) is a nice tool to add.

http://www.murga-linux.com/puppy/viewtopic.php?t=51097

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

#10 Post by ttuuxxx »

plus a 295kb word processor http://murga-linux.com/puppy/viewtopic. ... 632#216632
ttuuxxx
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)

User avatar
puppymartin
Posts: 207
Joined: Sun 29 Mar 2009, 18:59
Location: The Netherlands
Contact:

#11 Post by puppymartin »

[delete double post]
Last edited by puppymartin on Tue 19 Jan 2010, 12:03, edited 1 time in total.

User avatar
puppymartin
Posts: 207
Joined: Sun 29 Mar 2009, 18:59
Location: The Netherlands
Contact:

#12 Post by puppymartin »

A bigger pup_412.sfs with:

Version 1
- All the 4.1.2 Network drivers
- CLInet network connect
- Nano the texteditor
http://www.browserlinux.com/pupngo/pup_412.sfs (5 Mb)

Version 2
- All the 4.1.2 Network drivers
- CLInet network connect
- Midnight Commander (file manager, ftp, nice editor)
(Start Midnight Commander with # mc)
Bootable ISO:
http://www.browserlinux.com/pupngo/mc/puppy_cli.iso (9 Mb)

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

#13 Post by goingnuts »

First of all - thank you for the interest in this tiny fellow...and all the good input for improving!

I did do a VESA+JWM version (added 8Mb without stripping fonts), also tested ttuuxxx XFE (very nice file manager!) only adding another 1Mb...

pUPnGo actually started as a wish of making an embedded web-server based on Puppy and LAMP-6.16-5.1.35-5.2.9.pet - this can also be done with a final size (including a php-based CMS) around 20 Mb.

But - as stated in the first post - the main purpose with pUPnGO is to make a basic building block to be used as a platform for standalone applications or "embedded" systems. Not to develop a new tiny Linux distro.
It is close to easy to produce a custom SFS with whatever additional application you might want and afterwards inject it in the provided ISO (as puppymartin have done already).
Applications can already be included in a zdrv_412.sfs along with needed drivers and run directly after boot from the ISO - without modification of the basis pUPnGO pup_412.sfs.

This way it gets very modular still maintaining some of the properties that make Puppy so unique in my eyes.

So I will try to continue cutting down in size and improving functionality in pUPnGO - and refine the build script used to make it - rather than try to implement new applications/features (even though it is tempting to follow your suggestions for additional applications...)

raffy
Posts: 4798
Joined: Wed 25 May 2005, 12:20
Location: Manila

sfs

#14 Post by raffy »

goingnuts wrote:pUPnGo actually started as a wish of making an embedded web-server based on Puppy and LAMP-6.16-5.1.35-5.2.9.pet - this can also be done with a final size (including a php-based CMS) around 20 Mb.

But .. the main purpose with pUPnGO is to make a basic building block to be used as a platform for standalone applications or "embedded" systems..

Applications can already be included in a zdrv_412.sfs along with needed drivers and run directly after boot from the ISO - without modification of the basis pUPnGO pup_412.sfs.
The LAMP build is certainly a useful one! And the plan to use sfs to expand the services is great, too. Please teach us how to do this with zdrv_412.sfs (trim it of unneeded drivers and add needed applications).
Puppy user since Oct 2004. Want FreeOffice? [url=http://puppylinux.info/topic/freeoffice-2012-sfs]Get the sfs (English only)[/url].

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

#15 Post by goingnuts »

Hi raffy
I do not feel like a teacher at all...but...

The zdrv_412.sfs approach for pUPnGO is straight forward: Create a directory named zdrv_412. Put all applications, modules, drivers, libs and
files you want in it. Run "dir2sfs zdrv_412" and out comes zdrv_412.sfs. Copy/move or inject this file to the location on the pUPnGO_V01.iso where pup_412.sfs is located (in directory isolinux). When pUPnGO boots, the file gets mounted, and all your stuff is available.

Not all applications seem to work well this way. Another approach (not tested yet) is to put an ordinary XXX.pet file inside zdrv_412.sfs and after boot automatic or manually install the pet (pet-install not in pUPnGo - yet).

Normal custom sfs-files seems not to mount during CD-boot - I think this require a hack of init in initrd.gz. I haven’t tested if custom sfs-files saved
on HD get mounted during CD-boot but the original pup_412.sfs definitely does if present.

I have updated the pUPnGO_V01.iso to reflect the first approach. So now Lynx and the net drivers are in zdrv_412.sfs whereas the pup_412.sfs is the present bare bone pUPnGO-thing.

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

Post Reply