Download the 86MB ISO https://drive.google.com/file/d/1ItUogv ... sp=sharing
Wary 5.3 XVesa barebone pup, added to 3.14.55 LTS recent (32 bit noPAE) kernel
XVesa is a pretty generic, basic graphics server so tends to load to GUI OK on a wide range of equipment, but doesn't utilise the benefits of your graphics card. Kernel is relatively new, so supports a wide range of hardware/firmware up to relatively recent.
PXE server included. And a special (fast) remaster process that requires no CD ISO image. As a PXE server needs a image to serve so that other PC's on the same LAN can net boot, you first have to run the remaster script (desktop icon) to create the initrd and vmlinuz files for the PXE server to serve.
Remastering will record the image of the PC at that time, so best to only ever remaster after first booting, and perhaps having made a few changes if desired. i.e. DON'T load sfs's etc before remastering as they'll be included in the newly remastered image (unless of course that's want you want). In most cases you can select to remaster using ram as the temp workspace and when so it remasters very quickly (few seconds).
Most network cards support net booting, but you usually have to enter the BIOS setup to set that as a boot option (that usually is set to something like boot from CD first, HDD second ... or whatever). Also usually you have to press the F12 function key after first switching the PC on in order to either netboot immediately or provide a netboot menu.
Once one PC is running this pup (that has remastered a initrd and vmlinuz, and then clicked the PXE icon to activate the PXE server), another PC can net boot and start up (hopefully) running that same pup. In turn that PC could then remaster and fire up its PXE server ... to serve netbooting of other PC's. The PC's bios (usually accessibly by repeatedly pressing F12 after having pressed the Power On button) needs to be set so 'safe boot' is off and where PXE boot has been activated and set to be a higher boot priority order than your normal HDD boot choice ... or you can press F12 repeatedly after having pressed the Power On button until it shows the boot selections and you select the Realtek PXE (or similar) boot choice from the bios boot menu when shown.
In using a low graphics requirement (XVesa) and recent kernel (that supports a wide range of hardware), booting to desktop stands a good chance of being successful on most PC's.
The pup is spartan (in having used Wary 5.3 BareBone XVesa CD as a base - so many of the menu items if selected will just do nothing). This iso is primarily just intended to be used for PXE purposes.
Barebone XVesa (86MB) with PXE (boot)
-
oui
Re: Barebone XVesa pup with PXE server
why not?rufwoof wrote:The tar.xz file is 58.6MB in size, for the setup however I've not used any compression of the initrd file, nor the puppy sfs file (which is inserted into initrd). In total in uncompressed state its around 180MB in size.
So that remaster really fly's. On my old clunker it takes less than 5 seconds. Add compression and it slows things down considerably.
If you've PXE booted one PC and the PC that you initially booted from has been turned off, then you can remaster to create a initrd and vmlinuz in the PXE servers directory (which 'remaster' does automatically i.e. creates vmlinuz and initrd files in /root/tftpboot/pxelinux.cfg/) on the machine your using and then click the PXE desktop icon to start up the PXE server, and another PC on the lan can then net boot from that.
The other use is that a newly created initrd is a snapshot image of the PC at that time, i.e. a save file. If you boot using grub4dos then replace the initrd with the newly created one and then any changes are preserved across reboot.
If you've PXE booted one PC and the PC that you initially booted from has been turned off, then you can remaster to create a initrd and vmlinuz in the PXE servers directory (which 'remaster' does automatically i.e. creates vmlinuz and initrd files in /root/tftpboot/pxelinux.cfg/) on the machine your using and then click the PXE desktop icon to start up the PXE server, and another PC on the lan can then net boot from that.
The other use is that a newly created initrd is a snapshot image of the PC at that time, i.e. a save file. If you boot using grub4dos then replace the initrd with the newly created one and then any changes are preserved across reboot.
Should perhaps mention that you don't have to remaster that pup to create a initrd and vmlinuz for PXE server to boot, but can drop any initrd and vmlinuz into the /root/tftpboot/pxelinux.cfg folder that the PXE server is configured to use
The only thing with pup's is that you have to pass the puppy sfs along with the initrd
I usually open up initrd.gz by cd to where it and puppy sfs are located and then
mkdir NewDir
cd NewDir
zcat ../initrd.gz | cpio -id
cp ../puppy_whatever.sfs .
find | cpio -o -H newc >..initrd
where puppy_whatever.sfs is of course replaced with the actual name of the puppy sfs to be inserted into initrd. i.e. produces a larger initrd file that has the puppy sfs contained within it.
The only thing with pup's is that you have to pass the puppy sfs along with the initrd
I usually open up initrd.gz by cd to where it and puppy sfs are located and then
mkdir NewDir
cd NewDir
zcat ../initrd.gz | cpio -id
cp ../puppy_whatever.sfs .
find | cpio -o -H newc >..initrd
where puppy_whatever.sfs is of course replaced with the actual name of the puppy sfs to be inserted into initrd. i.e. produces a larger initrd file that has the puppy sfs contained within it.
Another update/upload. Replaced the get_latest_firefox script in the /root directory with a "FireFox" script that downloads and creates a sfs and sfs_loads that (and then runs firefox), or simply just runs firefox if the sfs has already been downloaded/created/loaded.
The web page when that firefox is activated is my googledrive directory in which there are currently just two files (openly shared to all). The wxv file is the tarbal of vmlinuz and initrd. The topdog_wary55.sfs file is basically Wary 5.5 with the Startup directory emptied - which if sfs loaded after being downloaded in effect adds all of Wary 5.5 functionality, abiword, gnumeric ... etc. (I've also thrown in Skype into that for good measure).
After downloading and installing that sfs you may have to RestartX.
Bit of a mix running a Tahr6 32 bit relatively recent kernel, with Wary 5.3 Barebone XVesa, with Wary 5.5 then laid on top - but seems to work relatively well. For instance I've just :
Grub4dos booted a old PC to fire up the PXE Wary 5.3 barebone vmlinuz and initrd (Xvesa desktop with net connection)
Ran remaster (desktop icon) which took seconds.
Clicked on PXE Server icon to start up the PXE server
.... and then on the latest PC on our LAN ...
Net booted (switched on, pressing F12 as booting until the netboot screen came up (I'd previously changed that PC's BIOS boot sequence to include netboot))
..... watched all the dots across the screen for around 3 rows worth (took around less than a minute to load) ... and then saw Puppy Wary 5.3 boot up and load straight to desktop.
I then opened HOME (desktop icon) and clicked the FireFox .. which downloaded and fired up firefox, loading my googledrive directory. I then downloaded the topdog_wary55.sfs and once that had completed (again less than a minute) I opened my download folder (beneath root), right clicked on the sfs and selected sfs_load (I opted for the NOCOPY) option and then restarted X ... and skype, gnumeric, abiword .... etc all are working fine.
That wary 5.5 (sfs) download needs work - there are lots of duplicate files in Wary 5.3 barebone that also appear in that topdog_wary55.sfs such that the topdog_wary5.5.sfs can be made a lot lighter. I'm currently looking at a means to automate that (perhaps using something like rdupe (remove duplicates)).
The web page when that firefox is activated is my googledrive directory in which there are currently just two files (openly shared to all). The wxv file is the tarbal of vmlinuz and initrd. The topdog_wary55.sfs file is basically Wary 5.5 with the Startup directory emptied - which if sfs loaded after being downloaded in effect adds all of Wary 5.5 functionality, abiword, gnumeric ... etc. (I've also thrown in Skype into that for good measure).
After downloading and installing that sfs you may have to RestartX.
Bit of a mix running a Tahr6 32 bit relatively recent kernel, with Wary 5.3 Barebone XVesa, with Wary 5.5 then laid on top - but seems to work relatively well. For instance I've just :
Grub4dos booted a old PC to fire up the PXE Wary 5.3 barebone vmlinuz and initrd (Xvesa desktop with net connection)
Ran remaster (desktop icon) which took seconds.
Clicked on PXE Server icon to start up the PXE server
.... and then on the latest PC on our LAN ...
Net booted (switched on, pressing F12 as booting until the netboot screen came up (I'd previously changed that PC's BIOS boot sequence to include netboot))
..... watched all the dots across the screen for around 3 rows worth (took around less than a minute to load) ... and then saw Puppy Wary 5.3 boot up and load straight to desktop.
I then opened HOME (desktop icon) and clicked the FireFox .. which downloaded and fired up firefox, loading my googledrive directory. I then downloaded the topdog_wary55.sfs and once that had completed (again less than a minute) I opened my download folder (beneath root), right clicked on the sfs and selected sfs_load (I opted for the NOCOPY) option and then restarted X ... and skype, gnumeric, abiword .... etc all are working fine.
That wary 5.5 (sfs) download needs work - there are lots of duplicate files in Wary 5.3 barebone that also appear in that topdog_wary55.sfs such that the topdog_wary5.5.sfs can be made a lot lighter. I'm currently looking at a means to automate that (perhaps using something like rdupe (remove duplicates)).
Last edited by rufwoof on Wed 11 Nov 2015, 16:12, edited 1 time in total.
Uploading a new version. A bit bigger at 59.4MB.
Pre-loaded with a revised (latest) FireFox configuration that includes zoom page and noscript automatically being loaded.
FireFox script in home directory replaced with a LoadTopDog script. After booting to desktop that should be the first thing you run (open HOME icon at the top left of screen, single click on the LoadTopDog file)
That will
1. Run remaster to that a image of the newly booted pup will be dropped into the PXE server. After that you can click on the PXE desktop icon and anyone else on your LAN will be able to net boot the same pup image.
2. Downloads the latest firefox and fires it up.
3. Downloads and installs TopDog (Wary 5.5 programs), so you'll also have AbiWord word processor, gNumeric spreadsheet, Skype .... etc.
Generally at any prompts you want to select the RAM (when remastering) or NOCOPY (for SFS loading) options assuming the PC has sufficient memory (1GB or more). For example when remaster runs it will ask where to and the last option is usually RAM (ramdisk). When SFS LOAD installs TopDog it provides options one of which is NOCOPY.
I've also changed the PXE server to use a compressed initrd.gz file instead of non compressed - as compressed transfers (boots) quicker
The default firefox home page is set to my shared googledrive folder, so there's additional SFS's that can be downloaded and sfs_loaded (right click menu option) - such as Libre Office.
Whoops! Just noticed I didn't change the PXE servers configuration to point to the initrd.gz, it still points to the non compressed initrd file
For the time being you'll need to edit
/root/tftpboot/pxelinux.cfg/default and change the line
append initrd=initrd rootfstype=ramfs
to
append initrd=initrd.gz rootfstype=ramfs
before starting the PXE server.
I'll correct that and re-upload at a later date as I intend to also create a ISO version, i.e. burn to CD so that CD can be booted in any one PC and then become a net boot server for other PC's to net boot. Conceptually you could have a number of PC's all with just a network card and no HDD's and the worst that could happen if a virus penetrated the network would be just the single session risk only, rebooting would clear everything. And for storage either plug in a portable HDD, or USB, or store somewhere in the Cloud.
Update : it what quicker and easier for me to change and upload a replacement straight away
Pre-loaded with a revised (latest) FireFox configuration that includes zoom page and noscript automatically being loaded.
FireFox script in home directory replaced with a LoadTopDog script. After booting to desktop that should be the first thing you run (open HOME icon at the top left of screen, single click on the LoadTopDog file)
That will
1. Run remaster to that a image of the newly booted pup will be dropped into the PXE server. After that you can click on the PXE desktop icon and anyone else on your LAN will be able to net boot the same pup image.
2. Downloads the latest firefox and fires it up.
3. Downloads and installs TopDog (Wary 5.5 programs), so you'll also have AbiWord word processor, gNumeric spreadsheet, Skype .... etc.
Generally at any prompts you want to select the RAM (when remastering) or NOCOPY (for SFS loading) options assuming the PC has sufficient memory (1GB or more). For example when remaster runs it will ask where to and the last option is usually RAM (ramdisk). When SFS LOAD installs TopDog it provides options one of which is NOCOPY.
I've also changed the PXE server to use a compressed initrd.gz file instead of non compressed - as compressed transfers (boots) quicker
The default firefox home page is set to my shared googledrive folder, so there's additional SFS's that can be downloaded and sfs_loaded (right click menu option) - such as Libre Office.
Whoops! Just noticed I didn't change the PXE servers configuration to point to the initrd.gz, it still points to the non compressed initrd file
For the time being you'll need to edit
/root/tftpboot/pxelinux.cfg/default and change the line
append initrd=initrd rootfstype=ramfs
to
append initrd=initrd.gz rootfstype=ramfs
before starting the PXE server.
I'll correct that and re-upload at a later date as I intend to also create a ISO version, i.e. burn to CD so that CD can be booted in any one PC and then become a net boot server for other PC's to net boot. Conceptually you could have a number of PC's all with just a network card and no HDD's and the worst that could happen if a virus penetrated the network would be just the single session risk only, rebooting would clear everything. And for storage either plug in a portable HDD, or USB, or store somewhere in the Cloud.
Update : it what quicker and easier for me to change and upload a replacement straight away
Last edited by rufwoof on Wed 11 Nov 2015, 18:51, edited 1 time in total.
Wary_5.3_XVesa.iso 82.6MB ISO uploaded (to the usual directory https://drive.google.com/folderview?id= ... sp=sharing. I used a modified Wary 5.3 ISO to create the ISO.
Direct to file link https://drive.google.com/file/d/0B4MbXu ... sp=sharing
Direct to file link https://drive.google.com/file/d/0B4MbXu ... sp=sharing
Whilst many/most network cards support net booting (PXE), the method to set up the computer to net boot varies.
Typically you boot up the client computer, and try to have it PXE by pressing F12 (usually). More often then not, this works or at the very least, gets you to a "boot options" menu. With that said, there are cases where PXE needs to be first enabled in the BIOS before you can use it. If that is the case, go into BIOS, this step may be a little different for every computer. In most cases this involves pressing either F2, F10, or DEL. Then, if the option exists, enable PXE/Network booting.
In some BIOS setup's there may be a couple of places you have to setup network boot, such as enable LAN ROM or suchlike.
On later/recent Window's machines you probably have to disable secure boot by pressing F2 as the PC is booted to get into the BIOS and under security set Boot Control to Disabled and set the boot preference. You'll have to ask/read around for the exact detail as I haven't touched Windows for nearly two years now so I can't offer help on that front. Barry wrote a report of how to turn Windows security boot off here : http://bkhome.org/quirky/uefi.htm
Typically you boot up the client computer, and try to have it PXE by pressing F12 (usually). More often then not, this works or at the very least, gets you to a "boot options" menu. With that said, there are cases where PXE needs to be first enabled in the BIOS before you can use it. If that is the case, go into BIOS, this step may be a little different for every computer. In most cases this involves pressing either F2, F10, or DEL. Then, if the option exists, enable PXE/Network booting.
In some BIOS setup's there may be a couple of places you have to setup network boot, such as enable LAN ROM or suchlike.
On later/recent Window's machines you probably have to disable secure boot by pressing F2 as the PC is booted to get into the BIOS and under security set Boot Control to Disabled and set the boot preference. You'll have to ask/read around for the exact detail as I haven't touched Windows for nearly two years now so I can't offer help on that front. Barry wrote a report of how to turn Windows security boot off here : http://bkhome.org/quirky/uefi.htm
- Attachments
-
- Bios.jpg
- (26.57 KiB) Downloaded 1952 times
Last edited by rufwoof on Wed 11 Nov 2015, 22:19, edited 2 times in total.
Updated the ISO to exclude gpartedbin from the base pup (available in the TopDog) and to store the /lib/firmware and /lib/modules in a compressed tar file that's decompressed at start up (within /etc/rc.d/sysinit). The remaster process was also modified to take that into account. Reduces the initrd.gz filesize down by around 8MB making PXE boot (file transfer) that little bit quicker (smaller initrd.gz with puppy sfs contained within that (combined 73MB)) - at the expense of making startup a little bit slower.
As modules and firmware are now in compressed tarball, any changes to /lib/modules or /lib/firmware need to be reflected in that /lib/firmware_and_modules.tar.xz file (that was compressed with the xz -e (extreme) compression parameter/switch). Otherwise a remaster will not see the changes reflected into the new version.
As modules and firmware are now in compressed tarball, any changes to /lib/modules or /lib/firmware need to be reflected in that /lib/firmware_and_modules.tar.xz file (that was compressed with the xz -e (extreme) compression parameter/switch). Otherwise a remaster will not see the changes reflected into the new version.
Last edited by rufwoof on Thu 12 Nov 2015, 21:41, edited 2 times in total.
Wary 5.5 TopDog updated to have the latest Mozilla flashplayer plugin. The UnderDog (Wary 5.3 barebone boot) has no flash, so if you just boot to that and load a portable firefox on HDD then you'll have no active flash.
I've also added (fast decompression) LZ4 compression to mksquashfs, unsquashfs and as a standalone.
leafpad changed for a later version due to multiple/repeated search bug in the former version.
I've also added (fast decompression) LZ4 compression to mksquashfs, unsquashfs and as a standalone.
leafpad changed for a later version due to multiple/repeated search bug in the former version.
- Attachments
-
- f.jpg
- (23.33 KiB) Downloaded 1810 times
No, as it loads Wary 5.3 as its base, so Wary packages. For compiling however it uses the Tahr dev and kernel source SFS's.starhawk wrote:@rufwoof (really for anyone who can answer) --
Is the "base" (Wary + Tahr kernel) made compatible with Tahr packages by using the TahrPup kernel? By "Tahr packages" I mean in particular Ubuntu Trusty Tahr *.deb packages, not just dotPETs for TahrPup.
IIMU that the original Wary stayed with a old kernel in order to better support dial up modems, but in so doing lacked support of newer hardware. Replacing the older kernel with one pulled from Tahr made it work on the most recent kit that I have access to. Employing XVesa only means that for most it will boot to desktop and if hard wired - to network. The initial boot is a very small image (barebone Wary 5.3) - basic GUI with very limited functionality, but you can for instance run a portable firefox of the latest firefox version. A click on the LoadTopDog script in the HOME directory adds all of Wary 5.5 functionality (abiword, gnumeric, seamonkey ....etc).
Sorry 
My course is different. Just finishing up ironing out annoying bugs such as Screeny not working etc and intend to have a break for a bit.
The next phase is for a straight to desktop, remaster, remastered image dropped into PXE servers folder and PXE server started totally automated boot option. i.e. even without a monitor switched on a CD (or USB) plugged in and the machine turned on (assuming of course set to boot from CD (or USB)) and within a minute or so other PC's on the same LAN (that were hard-wired (ethernet)) could then net boot puppy (most machines and network cards support network/LAN boot options in BIOS). i.e. even if a old clunker had no CD, USB, HDD, but did have a monitor, mouse, keyboard and ethernet network card it could boot puppy assuming any other hardwired device on the same LAN could boot a CD/USB.
Thereafter perhaps another phase/version that runs the pup inside a virtual machine. i.e. install that VM on a Windows machine and then any other machine on the same LAN could netboot puppy.
My course is different. Just finishing up ironing out annoying bugs such as Screeny not working etc and intend to have a break for a bit.
The next phase is for a straight to desktop, remaster, remastered image dropped into PXE servers folder and PXE server started totally automated boot option. i.e. even without a monitor switched on a CD (or USB) plugged in and the machine turned on (assuming of course set to boot from CD (or USB)) and within a minute or so other PC's on the same LAN (that were hard-wired (ethernet)) could then net boot puppy (most machines and network cards support network/LAN boot options in BIOS). i.e. even if a old clunker had no CD, USB, HDD, but did have a monitor, mouse, keyboard and ethernet network card it could boot puppy assuming any other hardwired device on the same LAN could boot a CD/USB.
Thereafter perhaps another phase/version that runs the pup inside a virtual machine. i.e. install that VM on a Windows machine and then any other machine on the same LAN could netboot puppy.
Last edited by rufwoof on Fri 13 Nov 2015, 02:10, edited 1 time in total.
Hi rufwoof, your pup captured my imagination. The first post - even if historical - is very clear and concise for the amount of information it gives. So, this is what I'd like to do, please tell me if it can be done for what you know. I want to make a bootable USB flash key with three boot options: your pxe Wary, BK's 7.3 Quirky, and Windows XP (Yeah, I know). I haven't though about the partition scheme yet, but two things are for sure: it needs one partition to hold pxe boot images, and I want to maximize the number of partitions formatted as F2FS because F2FS lowers flash key wear. The end result would make a great tool to: 1) carry Puppy ISO images around; 2) network boot all of them - the ones that can be network booted; run Quirky; run downloaded TopDog. Question - can your Wary and TopDog run without save file? By default I'd like to disable saving a session file, and save it manually by clicking an icon or something similar.
OK, lots of questions, sorry if too many. Whatever you can answer will be a good starting point for me. Don't worry about the WinXP part, I can think it through on my own. Thanks
OK, lots of questions, sorry if too many. Whatever you can answer will be a good starting point for me. Don't worry about the WinXP part, I can think it through on my own. Thanks
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]