puppybang
puppybang
one of the developer here has made a puppy called puppybang, i really want to try it, the only problem is that it is made using PAE (64 bit). is there a way to make it work on a non-PAE(i686), in Ubuntu, there is an option called force PAE, however that does not work with puppy.
-
april
Bad girl april.
I better not post Pussy Linux.
They kicked that off Whirlpool.
PuppyBang Linux 6.0.3
http://45.33.15.200/puppy/viewtopic.php ... 3344c8fa77
Download.
https://drive.google.com/uc?id=0B1EEyjL ... t=download
:::::
" s there a way to make it work on a non-PAE(i686), in Ubuntu,
there is an option called force PAE, however that does not work with puppy."
Someone might give an answer later.
Welcome to Puppy.
Chris.
Can't help myself.
http://puppylinux.org/wikka/PussyLinux
I better not post Pussy Linux.
They kicked that off Whirlpool.
PuppyBang Linux 6.0.3
http://45.33.15.200/puppy/viewtopic.php ... 3344c8fa77
Download.
https://drive.google.com/uc?id=0B1EEyjL ... t=download
:::::
" s there a way to make it work on a non-PAE(i686), in Ubuntu,
there is an option called force PAE, however that does not work with puppy."
Someone might give an answer later.
Welcome to Puppy.
Chris.
Can't help myself.
http://puppylinux.org/wikka/PussyLinux
Build a no-pae puppybang
Hi memo
It's easy to change the kernels used in any Puppy published during the last 4 or 5 years,
To build a no-pae Puppybang, download the Puppy ISO you want and mount it (Left-Click the ISO). In the window which opened, you'll notice that there are two files, one named vmlinuz and another named zdrv_xxx.sfs where xxx has the name of the Puppy and the version number. Vmlinuz is the Kernel (think engine) and zdrv_xxx.sfs contains the drivers* (think nuts & bolts which connect the engine to the body). Drivers are specific to their vmlinuz. Copy everything to a folder**, except vmlinuz and zdrv_xxx.sfs.
Download a Puppy which uses a no-pae kernel, such as roadkill13's recent TahrPup CE 6.06 32 bit.using a 3.4.103-nopae kernel. You'll find a link to it here: http://www.murga-linux.com/puppy/viewto ... 224#973224. Mount it. Copy its vmlinuz into the folder. Copy its zdrv_xxx.sfs into the folder and change its name (Right-click, Select Rename) to be EXACTLY the same as that zdrv_xxx.sfs which was in the Puppybang ISO.
I don't have a copy of Puppybang readily available. But if I wanted to use the vmlinuz and zdrv from Tahrpup in Xenialpup, I'd have to rename the zdrv_tahr_6.0.6.sfs to zdrv_xenial_7.5.sfs
The folder now contains a no-pae Puppybang.
* Note Some recent Puppies also contain an fdrv_xxx.sfs. This file contains firmware. Firmware is not specific to any vmlinuz. To connect to a Puppy's body (the applications), vmlinuz (engine) needs both drivers and firmware. If an fdrv is NOT present, both drivers and firmware have been included in the zdrv. If a fdrv is present, it's name has to be changed to that of the Puppy and its version number. Using the xenialpup example, fdrv would have to be named fdrv_xenialpup_7.5.sfs
** Give the folder you created a unique name, such as "puppybang-np" in order to refer to it in grub4dos' menu.lst. The folder containing your finished no-pae Puppybang will be transportable. You can copy it to any other computer. Someone else can provide instructions on how to convert that folder into an ISO.
mikesLr
It's easy to change the kernels used in any Puppy published during the last 4 or 5 years,
To build a no-pae Puppybang, download the Puppy ISO you want and mount it (Left-Click the ISO). In the window which opened, you'll notice that there are two files, one named vmlinuz and another named zdrv_xxx.sfs where xxx has the name of the Puppy and the version number. Vmlinuz is the Kernel (think engine) and zdrv_xxx.sfs contains the drivers* (think nuts & bolts which connect the engine to the body). Drivers are specific to their vmlinuz. Copy everything to a folder**, except vmlinuz and zdrv_xxx.sfs.
Download a Puppy which uses a no-pae kernel, such as roadkill13's recent TahrPup CE 6.06 32 bit.using a 3.4.103-nopae kernel. You'll find a link to it here: http://www.murga-linux.com/puppy/viewto ... 224#973224. Mount it. Copy its vmlinuz into the folder. Copy its zdrv_xxx.sfs into the folder and change its name (Right-click, Select Rename) to be EXACTLY the same as that zdrv_xxx.sfs which was in the Puppybang ISO.
I don't have a copy of Puppybang readily available. But if I wanted to use the vmlinuz and zdrv from Tahrpup in Xenialpup, I'd have to rename the zdrv_tahr_6.0.6.sfs to zdrv_xenial_7.5.sfs
The folder now contains a no-pae Puppybang.
* Note Some recent Puppies also contain an fdrv_xxx.sfs. This file contains firmware. Firmware is not specific to any vmlinuz. To connect to a Puppy's body (the applications), vmlinuz (engine) needs both drivers and firmware. If an fdrv is NOT present, both drivers and firmware have been included in the zdrv. If a fdrv is present, it's name has to be changed to that of the Puppy and its version number. Using the xenialpup example, fdrv would have to be named fdrv_xenialpup_7.5.sfs
** Give the folder you created a unique name, such as "puppybang-np" in order to refer to it in grub4dos' menu.lst. The folder containing your finished no-pae Puppybang will be transportable. You can copy it to any other computer. Someone else can provide instructions on how to convert that folder into an ISO.
mikesLr
Re: Build a no-pae puppybang
your method has worked like a charm, thanks a lot. for newbies like me please try puppybang, it has been configured in a way to make things easy and you do not need to spend hours installing or searching for apps. note that you need a ram around 1 G, otherwise use the stock distro as it is smaller and almost the same.mikeslr wrote:Hi memo
It's easy to change the kernels used in any Puppy published during the last 4 or 5 years,
To build a no-pae Puppybang, download the Puppy ISO you want and mount it (Left-Click the ISO). In the window which opened, you'll notice that there are two files, one named vmlinuz and another named zdrv_xxx.sfs where xxx has the name of the Puppy and the version number. Vmlinuz is the Kernel (think engine) and zdrv_xxx.sfs contains the drivers* (think nuts & bolts which connect the engine to the body). Drivers are specific to their vmlinuz. Copy everything to a folder**, except vmlinuz and zdrv_xxx.sfs.
Download a Puppy which uses a no-pae kernel, such as roadkill13's recent TahrPup CE 6.06 32 bit.using a 3.4.103-nopae kernel. You'll find a link to it here: http://www.murga-linux.com/puppy/viewto ... 224#973224. Mount it. Copy its vmlinuz into the folder. Copy its zdrv_xxx.sfs into the folder and change its name (Right-click, Select Rename) to be EXACTLY the same as that zdrv_xxx.sfs which was in the Puppybang ISO.
I don't have a copy of Puppybang readily available. But if I wanted to use the vmlinuz and zdrv from Tahrpup in Xenialpup, I'd have to rename the zdrv_tahr_6.0.6.sfs to zdrv_xenial_7.5.sfs
The folder now contains a no-pae Puppybang.
* Note Some recent Puppies also contain an fdrv_xxx.sfs. This file contains firmware. Firmware is not specific to any vmlinuz. To connect to a Puppy's body (the applications), vmlinuz (engine) needs both drivers and firmware. If an fdrv is NOT present, both drivers and firmware have been included in the zdrv. If a fdrv is present, it's name has to be changed to that of the Puppy and its version number. Using the xenialpup example, fdrv would have to be named fdrv_xenialpup_7.5.sfs
** Give the folder you created a unique name, such as "puppybang-np" in order to refer to it in grub4dos' menu.lst. The folder containing your finished no-pae Puppybang will be transportable. You can copy it to any other computer. Someone else can provide instructions on how to convert that folder into an ISO.
mikesLr
I want also to thanks puppylinuxworld the developer of puppybang, hope to see him again on youtube. To be honest I knew linux through him few years ago. he really like to help the people and I hope to see more of his videos
If someone is wiling to help me to know how to do the respin then i can upload the puppybang with the non pae and updates
to save the guys sometime .
Experimenting
Hi memo,
I don't know much about theming. But, having a limited understanding about how things fit together, or don't, I do know a bit about experimenting. So here's some precautions I take in order not to "paint myself into a corner".
1, Remove the Automatic Save: http://murga-linux.com/puppy/viewtopic. ... 834#966834.
2. Use a SaveFile rather than a SaveFolder: http://murga-linux.com/puppy/viewtopic. ... 841#934841. With the Automatic Save turned off, using a SaveFile nothing becomes permanent until Saved. You can test the change by ReStarting-X, which causes Puppy to re-catalog what's on its system. [Worse case scenario: you can literally 'pull the plug'. With Automatic Save turned off, you can't corrupt your SaveFile by doing so.] Rebooting without Saving returns your system to its condition before you installed the pet.
3. Note the downside of the above. http://murga-linux.com/puppy/viewtopic. ... 066#974066. Choose which work-arounds seem important, or use a 2nd Puppy for you experimentations.
4. Create or convert applications to be tested as SFSes. They are never a permanent part of your system. Use PaDS to do so. http://murga-linux.com/puppy/viewtopic. ... 922#998922
5. Make one change at a time. Test to see that it functions and doesn't conflict with what's already on your system.
6. Back up your SaveFile/Folder. Some applications --such as those which depend on python-- will not work unless they are installed. The python application in Puppy_version_version-number.sfs and in your SaveFile/Folder have priority over any python version in a SaveFile/Folder.
I think I read somewhere that some newer themes used a newer version of gtk and/or glibc.
If I recall correctly, Puppybang was a remaster of Tahrpup. The package you can download from here, http://murga-linux.com/puppy/viewtopic. ... 927#982927, contains many newer versions of applications which were included in the original. Many of the applications are "no-arch" -- that is they can be used in any Puppy.
mikesLr
I don't know much about theming. But, having a limited understanding about how things fit together, or don't, I do know a bit about experimenting. So here's some precautions I take in order not to "paint myself into a corner".
1, Remove the Automatic Save: http://murga-linux.com/puppy/viewtopic. ... 834#966834.
2. Use a SaveFile rather than a SaveFolder: http://murga-linux.com/puppy/viewtopic. ... 841#934841. With the Automatic Save turned off, using a SaveFile nothing becomes permanent until Saved. You can test the change by ReStarting-X, which causes Puppy to re-catalog what's on its system. [Worse case scenario: you can literally 'pull the plug'. With Automatic Save turned off, you can't corrupt your SaveFile by doing so.] Rebooting without Saving returns your system to its condition before you installed the pet.
3. Note the downside of the above. http://murga-linux.com/puppy/viewtopic. ... 066#974066. Choose which work-arounds seem important, or use a 2nd Puppy for you experimentations.
4. Create or convert applications to be tested as SFSes. They are never a permanent part of your system. Use PaDS to do so. http://murga-linux.com/puppy/viewtopic. ... 922#998922
5. Make one change at a time. Test to see that it functions and doesn't conflict with what's already on your system.
6. Back up your SaveFile/Folder. Some applications --such as those which depend on python-- will not work unless they are installed. The python application in Puppy_version_version-number.sfs and in your SaveFile/Folder have priority over any python version in a SaveFile/Folder.
I think I read somewhere that some newer themes used a newer version of gtk and/or glibc.
If I recall correctly, Puppybang was a remaster of Tahrpup. The package you can download from here, http://murga-linux.com/puppy/viewtopic. ... 927#982927, contains many newer versions of applications which were included in the original. Many of the applications are "no-arch" -- that is they can be used in any Puppy.
mikesLr