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.

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 downloadsLast edited by goingnuts on Mon 06 Jun 2011, 13:54; edited 14 times in total

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.

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

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

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? Get the sfs (English only).

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.

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