Here you go - threre's ahi rufwoof,
why don't you share your version with us?
https://drive.google.com/file/d/0B4MbXu ... sp=sharing - vmlinuz and https://drive.google.com/file/d/0B4MbXu ... sp=sharing initrd.lzo pair of files where initrd.lzo holds puppy sfs inside. Of those two initrd.lzo is the big one - around 400MB
Those can be used with grub4dos, I suggest a entry something like
Code: Select all
title Puppy 533t-310
root (hd0,2)
kernel /vmlinuz pmedia=atahd pfix=ram ramdisk_size=500000 nouveau.modeset=0 nouveau.noaccel=1 radeon.modeset=0 i915.modeset=0
initrd /initrd.lzo
You'll need to adjust the root (hd0,2) according to whichever drive/partition you use to store the two files (they count from 0 being the first)
That's Slacko 533t, adjusted and re-remastered a lot. Updated from 3.01 to 3.10 kernel so supports later hardware
The normal puppy menu has been shifted to only be accessible via right mouse click on the desktop and the taskbar menu replaced with another menu. Includes Libre and latest Firefox and is relatively easy to swap out from a older to a later firefox as/when they become available. Firefox is also set to load up with zoom, no script, you tube downloader and is also set to view youtube videos as HTML5 videos instead of flash (which isn't installed). You do have to set the noscript to allow youtube for the video to display.
Also includes PXE server so any other PC's in your local LAN can boot puppy using net boot. you'll have to change /root/tftpboot/pxelinux.cfg directory contents to point vmlinuz and initrd.lzo to wherever those files are on your system i.e. symlink. Then start up the server (main menu PXE choice) and set other PC's to net boot - i.e. typically turn of secure booting in windows, reboot and hit <esc> during the initial startup and select net boot (or maybe F12 during boot up).
In the root directory there's a file called INITRD_LOCATION, that will likely need to be edited to point to where your initrd.lzo is stored. Remastering uses that as the pointer for which initrd.lzo to replace.
Remastering is slower on that version as the puppy contains Libre Office and Firefox which doubles the puppy size, so around a minute to remaster on my single core system. Main Menu (taskbar), Config, Remaster will kick that off.
It all runs in ram, only touching the HDD as that's where initrd.lzo and vmlinuz are loaded from, if they were stored on CD then you wouldn't have to touch HDD at all. Once booted you can unmount all drives.
Needs I guess at least 1GB of ram to work ok as puppy is stored uncompressed inside initrd and hence is stored uncompressed in ram once loaded.
There's no save files, nor is it intended to be run with a save file, just store data/docs outside of puppy space and if you want to make changes then reboot a clean/fresh version, make the changes and then remaster
You'll probably have to set the network up (click on the network tray icon) and sound (right click desktop to being up the puppy menu and select setup, setup puppy, wizards wizards .... etc).
Whilst the personal main menu includes "config" options, they're mostly just links to the files that need to be manually edited. Puppy is basically vmlinuz kernel, initrd initial ramdisk and puppy sfs main linux and desktop - where the desktop is fundamentally a xml text file(s) (ROX) and jwm provides a menu using text files to provide a graphical way to access programs. After any changes you need to run fixmenus and jwm -restart to install the changes - one of the config menu options is to run those commands.
Nothing polished, just something that works for me and likely has some things that I don't use that don't work (vga upgrade and PPM etc I suspect are 'faulty').
A great thing about ram booting is that you can try things out (leave all HDD's unmounted) and perhaps trash the system - and simply reboot to get back to a clean working version again. With a full install puppy if you go to a dodgy web site that manages to crack into your system that could install something that remains resident across reboots (persistent), with a ram booted puppy that virus only remains present for that one single session.
Use at your own risk, make backup's first ...etc after all this is a weird one, a Slackware 13 series based puppy (slacko 5.3.3) with a series 14 kernel dropped in (sourced from slacko 5.7), so I've no idea what may or may not work with that. Fun trying things out and if they work great, if they don't then you may need to reboot.
The one thing that attracted me originally to Slacko is was that it was one of the very few that booted straight to desktop on my hardware - after having tried numerous others beforehand that didn't. So I've stayed with slacko since. The repositories might not be good, but I hunt and try out other choices - from any version. Sometimes they work, sometimes they don't, being able to experiment and simply reboot out failures has made me more fond of having a read only core puppy. I'd be uncomfortable returning to a full install where one bad case can trash the system to a level where a full reinstall is required. The other factor is speed. When you get used to things being quick you're less inclined to move to slower alternatives. My son often mentions how his old hand-me-down rappy system is so much quicker than his winblows system.