Slaxer_Pup 4.12 solid and stable non woof build
amigo wrote:If only Puppy would switch to a sane package format like used by slackware -then anybody could create really super, complete, sane and correct packages with a single command using src2pkg. Using that format allows you to use already-existing dependency-resolving package managers like slapt-get.
Hey amigo
"If only ".... well um ...ah
you can have that too
and in your familar way of doing it
with pkgtool you can install /uninstall view what packages were installed the standard "official way " (for slackers that is )
******************one stop shopping *************************
ISO
http://www.puppy2.org/slaxer/Slaxer_Pup-4.12_USB.iso
pkgtools-13.0-patched-10-i486-slxr.pet
http://puppy2.org/slaxer/pkgtools-13.0- ... 6-slxr.pet
updated Oct 11 2009
unpackager-dragNdrop-1-i486-slxr.pet
http://www.puppy2.org/slaxer/unpackager ... 6-slxr.pet
to compile apps this is needed
devx_412.sfs
ftp://ibiblio.org/pub/linux/distributio ... vx_412.sfs
*now with the above installed and the devx set up in the boot manager *you just click on the pkgtools icon and from there you'll feel at home to install src2pkg the correct way with pkgtools
src2pkg build packages from source code for the best compatibility
updated 10-9-2009
http://distro.ibiblio.org/pub/linux/dis ... arch-3.tgz
****************************************************
then anybody could create really super, complete, sane and correct packages with a single command using src2pkg.
an older post with some good info http://www.murga-linux.com/puppy/viewto ... 8&start=74
Yep!
updated pkgtools-13.0-patched-10-i486-slxr.pet
I made an edit to makepkg
Joe
Last edited by big_bass on Mon 12 Oct 2009, 11:47, edited 5 times in total.
This is the latest release, Joe:
http://distro.ibiblio.org/pub/linux/dis ... arch-3.tgz
Have a read through the CHANGES file here:
http://distro.ibiblio.org/pub/linux/dis ... kg/CHANGES[/url]
http://distro.ibiblio.org/pub/linux/dis ... arch-3.tgz
Have a read through the CHANGES file here:
http://distro.ibiblio.org/pub/linux/dis ... kg/CHANGES[/url]
Joe
What with ttuuxxx taking a workbreak, I hope you, too, keep an eye on Jay's philosophy,
http://murga-linux.com/puppy/viewtopic.php?t=45264
as we can't afford to suddenly lose any more good devs
....even if it's a 'good change'...
Aitch
What with ttuuxxx taking a workbreak, I hope you, too, keep an eye on Jay's philosophy,
http://murga-linux.com/puppy/viewtopic.php?t=45264
as we can't afford to suddenly lose any more good devs
....even if it's a 'good change'...
Aitch
Hey guys, I've finally gotten around to taking a look at what causes the irritating "count-to-ten" delay when booting SlaxerPup. It comes right after "Waiting for modules to complete loading...".
Turns out it's because the SlaxerPup kernel has the USB modules built-in, whereas Barry has the modules loaded during booting. He has put in code to wait for the module names to appear in 'lsmod' before continuing, with a 10 sec timeout.
Since the module names never appear in 'lsmod' (they are already in the kernel), the code times-out every time.
I've commented out the lines for the delay in rc.sysinit and have attached the modified script. Just unpack the tarball and copy it over /etc/rc.d/rc.sysinit
I plan to spend more time with SlaxerPup and may use Pizzasgood's recipe to make it multi-user. My wife has used Puppy on her laptop in the past but runs Ubuntu now. However, she misses the ease-of-use of Puppy and would like to be able to work with her OpenOffice files from either OS (I've set up multi-booting). The problem is that Puppy leaves the files as owned by 'root' which Ubuntu can't easily open (must be 'root' of course). Creating the same user in multi-user SlaxerPup should make sharing the files (easily) possible.
Of course another solution would be to save the files on a vfat partition as the permissions aren't saved there, but that would be too easy
Btw, I did look at bypassing looking for Puppy files on other drives when booting from a flash drive, but Barry apparently uses the searching of drives to define a number of variables that are used later in 'init'. Once I saw that, I stopped looking
Paul
Turns out it's because the SlaxerPup kernel has the USB modules built-in, whereas Barry has the modules loaded during booting. He has put in code to wait for the module names to appear in 'lsmod' before continuing, with a 10 sec timeout.
Since the module names never appear in 'lsmod' (they are already in the kernel), the code times-out every time.
I've commented out the lines for the delay in rc.sysinit and have attached the modified script. Just unpack the tarball and copy it over /etc/rc.d/rc.sysinit
I plan to spend more time with SlaxerPup and may use Pizzasgood's recipe to make it multi-user. My wife has used Puppy on her laptop in the past but runs Ubuntu now. However, she misses the ease-of-use of Puppy and would like to be able to work with her OpenOffice files from either OS (I've set up multi-booting). The problem is that Puppy leaves the files as owned by 'root' which Ubuntu can't easily open (must be 'root' of course). Creating the same user in multi-user SlaxerPup should make sharing the files (easily) possible.
Of course another solution would be to save the files on a vfat partition as the permissions aren't saved there, but that would be too easy
Btw, I did look at bypassing looking for Puppy files on other drives when booting from a flash drive, but Barry apparently uses the searching of drives to define a number of variables that are used later in 'init'. Once I saw that, I stopped looking
Paul
- Attachments
-
- rc.sysinit_delay_fix.tar.gz
- rc.init without the 10-sec delay. Just unpack and copy over /etc/rc.d/rc.sysinit
- (6.34 KiB) Downloaded 395 times
Methinks Raspberry Pi were ideal for runnin' Puppy Linux
pakt wrote:
<partial quote original above >
I've commented out the lines for the delay in rc.sysinit and have attached the modified script. Just unpack the tarball and copy it over /etc/rc.d/rc.sysinit
Paul (pakt) Great to see you around again!
funny you posted today I thought to write to you today
before reading your post
and a super big thanks for fixing that ten second delay
all your help is always warmly welcomed
It will be added to the next update
yeah Pizzasgood's multi-user is something neededpakt wrote: I plan to spend more time with SlaxerPup and may use Pizzasgood's recipe to make it multi-user
Paul
I looked over some of his code it would be great to package that
as a package
so it could be tweaked "if needed" then easily installed and kept updated
hope you are feeling better
Joe
Oh yes....some good development going on....
Joe, you may be interested in this, too
http://www.murga-linux.com/puppy/viewto ... 7&start=15
Technosaurus is Co-ordinating, I believe, as well as the 4.4CE stuff
I believe he's also a slax fan & pizzasgood seems involved too, so hopefully multiuser and multi-sfs mounting/timing will get a fresh look
Aitch
Joe, you may be interested in this, too
http://www.murga-linux.com/puppy/viewto ... 7&start=15
Technosaurus is Co-ordinating, I believe, as well as the 4.4CE stuff
I believe he's also a slax fan & pizzasgood seems involved too, so hopefully multiuser and multi-sfs mounting/timing will get a fresh look
Aitch
well, this is something different
devx as a tgz package
why?
this is for live cd building of packages or one time install only (for full installs made easy )
its a *tgz slaxer package which allows it to be updated /renamed easily
something that the SFS devx won't let you do easily
it is the standard 412 devx *except it has an install script to build the symlinks for you
412-devx-i486-2.tgz 2009-10-10 82M
http://puppy2.org/slaxer/412-devx-i486-2.tgz
side note : I updated pkgtool
I made an edit to makepkg to fix an error with the current directory
not allowing makepkg
* This was planned for live cd ease of use but since I
had an extra hard drive for tests . I did a full install /grub
installing the devx tgz with pkgtool was so easy
Joe
devx as a tgz package
why?
this is for live cd building of packages or one time install only (for full installs made easy )
its a *tgz slaxer package which allows it to be updated /renamed easily
something that the SFS devx won't let you do easily
it is the standard 412 devx *except it has an install script to build the symlinks for you
412-devx-i486-2.tgz 2009-10-10 82M
http://puppy2.org/slaxer/412-devx-i486-2.tgz
side note : I updated pkgtool
I made an edit to makepkg to fix an error with the current directory
not allowing makepkg
* This was planned for live cd ease of use but since I
had an extra hard drive for tests . I did a full install /grub
installing the devx tgz with pkgtool was so easy
Joe
netmodules-slaxerpup-412.pet
click_here
brief description: This updated the network wizard's list of possible drivers that gets displayed in connection wizard since I had to make this specially for slaxer-pup (because of the different kernel) there were some changes so if your driver wasn't on the the list before it may be now you should add this anyway its complete ( you still need Dougal's updated wizard )
These are the updated drivers to GUI list in the internet connection wizard :
amd8111e "pci: AMD8111 based 10/100 Ethernet Controller. Driver Version 3.0.7"
ath9k "pci: Support for Atheros 802.11n wireless LAN cards."
atl1e "pci: Atheros 1000M Ethernet Network Driver"
bnx2 "pci: Broadcom NetXtreme II BCM5706/5708/5709 Driver"
hso "usb: USB High Speed Option driver"
ipg "pci: IC Plus IP1000 Gigabit Ethernet Adapter Linux Driver"
qla3xxx "pci: QLogic ISP3XXX Network Driver v2.03.00-k5 "
rtl8187 "usb: RTL8187/RTL8187B USB wireless driver"
sfc "pci: Solarflare Communications network driver"
gtk-xinput-2.12.1-i486-slxr.tgz
click_here
brief description: This is pizasgood fix for the insert key crash
I repackaged it and added the install script to make the symlinks
use pkgtool to install it
git-1.6.5-i486-slxr.pet
click_here
brief description: This is for GIT not needed for slaxer pup
to function correctly but it is a development tool
for a good explanation on puppy using git
pizzasgood wrote an extensive how to and uploaded a tree
http://pizzasgood.no-ip.org/puppy_git/
I have been busy automating my web page
it is all run by a bash script to generate the code with just one click
I am happy with the progress because before I started on it I had no clue how to create a html/php template less automate it with bash
I first looked for a simple template for a package list and
didnt find anything I could figure out so I wrote my own
I will post the script when I finish commenting it for the next guy that has to set up his site quickly since it will be easy to edit
if anyone has some good templates for a package repo please post them
Joe
click_here
brief description: This updated the network wizard's list of possible drivers that gets displayed in connection wizard since I had to make this specially for slaxer-pup (because of the different kernel) there were some changes so if your driver wasn't on the the list before it may be now you should add this anyway its complete ( you still need Dougal's updated wizard )
These are the updated drivers to GUI list in the internet connection wizard :
amd8111e "pci: AMD8111 based 10/100 Ethernet Controller. Driver Version 3.0.7"
ath9k "pci: Support for Atheros 802.11n wireless LAN cards."
atl1e "pci: Atheros 1000M Ethernet Network Driver"
bnx2 "pci: Broadcom NetXtreme II BCM5706/5708/5709 Driver"
hso "usb: USB High Speed Option driver"
ipg "pci: IC Plus IP1000 Gigabit Ethernet Adapter Linux Driver"
qla3xxx "pci: QLogic ISP3XXX Network Driver v2.03.00-k5 "
rtl8187 "usb: RTL8187/RTL8187B USB wireless driver"
sfc "pci: Solarflare Communications network driver"
gtk-xinput-2.12.1-i486-slxr.tgz
click_here
brief description: This is pizasgood fix for the insert key crash
I repackaged it and added the install script to make the symlinks
use pkgtool to install it
git-1.6.5-i486-slxr.pet
click_here
brief description: This is for GIT not needed for slaxer pup
to function correctly but it is a development tool
for a good explanation on puppy using git
pizzasgood wrote an extensive how to and uploaded a tree
http://pizzasgood.no-ip.org/puppy_git/
I have been busy automating my web page
it is all run by a bash script to generate the code with just one click
I am happy with the progress because before I started on it I had no clue how to create a html/php template less automate it with bash
I first looked for a simple template for a package list and
didnt find anything I could figure out so I wrote my own
I will post the script when I finish commenting it for the next guy that has to set up his site quickly since it will be easy to edit
if anyone has some good templates for a package repo please post them
Joe
Last edited by big_bass on Mon 19 Oct 2009, 14:08, edited 2 times in total.
big_bass:
I haven't read all the posts of Slaxer but I thought that I might
alert you to this.
Wpa_Gui: Finally a real network manager for puppy
http://www.murga-linux.com/puppy/viewtopic.php?t=47838
Cheers ....Chris.
I haven't read all the posts of Slaxer but I thought that I might
alert you to this.
Wpa_Gui: Finally a real network manager for puppy
http://www.murga-linux.com/puppy/viewtopic.php?t=47838
Cheers ....Chris.
Thanks for posting the info Chris (cthisbear)cthisbear wrote:big_bass:
I haven't read all the posts of Slaxer but I thought that I might
alert you to this.
Wpa_Gui: Finally a real network manager for puppy
http://www.murga-linux.com/puppy/viewtopic.php?t=47838
Cheers ....Chris.
all the help to make networking easier
is always welcomed I am checking it out now
Joe
package repo template
an off topic but someone may need this
this is the script to make a simple package repo index
history of what happened
Raffy PM'd me and said I have to use the account he set up quickly or it will expire
well ,I had to act fast and set up a repo
not prepared for the sudden adventure
this script saved my butt
a big thanks to Raffy for letting me use his server
Joe
this is the script to make a simple package repo index
history of what happened
Raffy PM'd me and said I have to use the account he set up quickly or it will expire
well ,I had to act fast and set up a repo
not prepared for the sudden adventure
this script saved my butt
a big thanks to Raffy for letting me use his server
Joe
Code: Select all
#!/bin/sh
#last updated 10-13-2009
#script made by Joe arose first template
# this makes the index.html for a simple package repo
#it is an all in one script so I can easily keep the package list updated
# I built this out of need and it needed to be easily updated
# I didn't want web page development to take all my time
# I'm too busy doing other things
#1.)what you need to know
#these are where you drop in the packages
#the pets to upload or are uploaded and you keep adding to the folder
#/root/asia_pets
#2.)/root/html-tagset.html #blank it will be auto renamed to index.php-new later
# this will be the newly generated index
#3.)#I have a folder where I can test before I upload
#that contains all the images that will be used called "puppy2-slaxer-index"
# I'll make it for you just in case at the end of this script
#cp /root/html-tagset.html /root/puppy2-slaxer-index/index.php-new
# you then remame it stripping off the -new (that's just a safety)
mkdir -p /root/asia_pets
echo >/root/html-tagset.html #blank it will be renamed to index.php-new later
cd /root/asia_pets # where I keep the pets I will upload these get listed
# starts the head of the html edit the names its a big echo
echo '<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<html>
<head>
<title>Index of /slaxer_pup 4.12 </title>
</head></font>
<body>
<BODY BGCOLOR="#000000" BACKGROUND="stars_background.gif">
<pre><img src="slxminilogo.gif" alt="Icon "> <a href="?C=N;O=D"></a>
<pre><img src="newlogo.png" alt="Icon "> <a href="?C=N;O=D"></a><br />
<font size="+2" color="#FFFFFF">* Important Note:<img src=iso.png><a href=Slaxer_Pup-4.12_USB.iso><font size="5" color="#FFFF00"> Slaxer_Pup-4.12_USB.iso</a><br /><font size="+2" color="#FFFFFF"> 86MB is for those that had problems booting off or reading<br /> save files from USB note: only the initrd.gz was changed <br />
<font size="+2" color="#FFFFFF">* some of my older work this will run a 486 <img src=iso.png alt=[ ]> <a href=fat-free-2.16-dillo.iso><font size="5" color="#FFFF00">fat-free-2.16-dillo.iso </a><br /><font size="+2" color="#FFFFFF"> "very stripped down" 56MB
<font size="+2" color="#FFFFFF">* More information about packages listed here <img src=info.png alt=[ ]> <a href=info.txt><font size="5" color="#FFFF00">info.txt </a>
<br />'>>/root/html-tagset.html
#end of the big echo and the end the html head
# here below is a simple samlple format of what the output will look like without the package size and date
#<img src=compressed.png alt=[ ]> <a href=geany-0.17-i486-slxr.pet><font size="5" color="#FFFF00">geany-0.17-i486-slxr.pet</font></a>
# body of the html code is generated by bash
# this was tricky to get the readable values
#in the format for package name date and size
#to get everything read at once for each package
for package in `find /root/asia_pets/*`; do
name=`basename "$package"`
datemodified=`ls -lh "$package" | awk '{ print $6 }'`
size=`ls -lh "$package" | awk '{ print $5 }'`
# edit this with care it was tedious to format it. Save a copy first
echo "<img src="compressed.png" alt="[ ]">" "<"a href="$name"">""<"font size="5" color="#FFFF00"">"$name"<"/font">""<"/a">" "<"font size="5" color="#FFFFFF"">" $datemodified "<"font size="5" color="#FFFF00"">" $size >>/root/html-tagset.html
done
# the last echo to end the index
echo '<hr></pre>
</body></html>'>>/root/html-tagset.html
#I have a folder where I can test before I upload
#that contains all the images that will be used called "puppy2-slaxer-index"
# I'll make it for you just in case
mkdir -p /root/puppy2-slaxer-index
cp /root/html-tagset.html /root/puppy2-slaxer-index/index.php-new
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
Another small distro based on Slax
Apologies to anyone who considers this off-topic, but this is where I would expect to find people interested. I confess that I have not read this entire thread. I did search for mention of slax.
Last week I was handed a CD for a mini-distro calling itself FortMacTux. This is relatively small, by most standards. It is based on the Slax fork of Slackware, which concentrates on smaller applications. It is surprisingly fast for a KDE-based system. At present, this is a live CD only. My contact wanted to know how to install it to hard drive. This looks like a project I will decline to tackle.
What struck me was the redundant effort involved in providing that mini-distribution with all the installation options Puppy has now, or providing KDE applications, which many people request, for Puppy variants. Slax may be closer to Puppy's design goals than Slackware itself.
Does anyone know this developer? He seems unusually competent. Is some commonality possible here?
prehistoric
Last week I was handed a CD for a mini-distro calling itself FortMacTux. This is relatively small, by most standards. It is based on the Slax fork of Slackware, which concentrates on smaller applications. It is surprisingly fast for a KDE-based system. At present, this is a live CD only. My contact wanted to know how to install it to hard drive. This looks like a project I will decline to tackle.
What struck me was the redundant effort involved in providing that mini-distribution with all the installation options Puppy has now, or providing KDE applications, which many people request, for Puppy variants. Slax may be closer to Puppy's design goals than Slackware itself.
Does anyone know this developer? He seems unusually competent. Is some commonality possible here?
prehistoric
Re: Another small distro based on Slax
Hey prehistoricprehistoric wrote:Apologies to anyone who considers this off-topic, but this is where I would expect to find people interested. I confess that I have not read this entire thread. I did search for mention of slax.
prehistoric
I don't mind the question I hope this clears up some things
If your client/friend needs to install slax or a slax derivative
a quick google search "install slax" will pull up some informative info
it was meant to be used as a live cd but would allow more flexibility installed as a USB pendrive
the link you posted appears to be a slax derivative with a full KDE
so its even bigger than the official slax
slax is a live cd cut down version of slackware with a lite KDE
that focuses on mounting modules (squashfs SFS in puppy talk)
slaxer pup does not focus on SFS mounting as the default install method it uses packages
like slackware and was modified to use pkgtool slackwares official package management and at the moment has a puppy root filing system but not for long
so that all pet packages can be installed also so you get
more options
my advice if you want to go for a full install of a slax derivative . install slackware it will run much faster
I use that too
Joe
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
FortMacTux + personal history
Thanks for the prompt response, Joe.
I'll pass the advice on to the person who asked, though I doubt they will use it. They keep hoping for a personal developer to solve their problems.
I was thinking the person behind FortMacTux might be recruited.
Warning to readers, off-topic ramble on personal history and oddball opinions:
I've semi-retired from the heavy lifting of development, and I decided years ago that KDE required way too much in the way of dependencies to qualify for small, light-weight distributions -- by my standards. (Skype is the main application using the Qt libraries which I tolerate. Once I get beyond that, all sorts of things keep getting dragged in. ) The KDE community probably has at least three different ways to do almost anything, and few people are even aware of all options. Even if machines can cope with the resulting mess, I have a limited amount of human working memory to expend.
I confess the last time I really trusted software libraries they were visible in trays of color-coded punched cards. Since then I've watched software take about three trips around the great wheel of karma. Each time there has been a point where developers start writing their own routines because it is too much trouble to find, understand and use existing libraries. People start reinventing wheels, with varying numbers of corners. This is the point where size and complexity start exponential growth. It is also the point where management starts looking at large numbers of software development people, and wondering which ones are really doing anything useful. (There inevitably comes a time when you find out -- the hard way.)
At one time I was in charge of software development for a line of real-time simulators. People couldn't understand why I insisted every delivered system had to be built entirely from source. (Even if a library routine is upgraded into a version which does the same thing, bit-for-bit, changing the timing can still mess up real-time systems.) Besides eliminating mysterious errors which are pure hell to track down, my policy had the advantage that in a real disaster, where the company computer and all attached storage burned to the ground, we could rebuild any delivered software product from source stored in off-site back up. In a real worst case, we could key in everything from a stored listing. (During one fiasco, I actually saw this happen. Before this, everybody called me a ridiculous pessimist.)
All this took place before "DLL Hell" traumatized anyone. You heroes still fighting with these problems are probably doomed, but that isn't unusual for heroes.
Regards,
prehistoric
Suggested Windows 7 message: "Found old hardware; install Puppy"
I'll pass the advice on to the person who asked, though I doubt they will use it. They keep hoping for a personal developer to solve their problems.
I was thinking the person behind FortMacTux might be recruited.
Warning to readers, off-topic ramble on personal history and oddball opinions:
I've semi-retired from the heavy lifting of development, and I decided years ago that KDE required way too much in the way of dependencies to qualify for small, light-weight distributions -- by my standards. (Skype is the main application using the Qt libraries which I tolerate. Once I get beyond that, all sorts of things keep getting dragged in. ) The KDE community probably has at least three different ways to do almost anything, and few people are even aware of all options. Even if machines can cope with the resulting mess, I have a limited amount of human working memory to expend.
I confess the last time I really trusted software libraries they were visible in trays of color-coded punched cards. Since then I've watched software take about three trips around the great wheel of karma. Each time there has been a point where developers start writing their own routines because it is too much trouble to find, understand and use existing libraries. People start reinventing wheels, with varying numbers of corners. This is the point where size and complexity start exponential growth. It is also the point where management starts looking at large numbers of software development people, and wondering which ones are really doing anything useful. (There inevitably comes a time when you find out -- the hard way.)
At one time I was in charge of software development for a line of real-time simulators. People couldn't understand why I insisted every delivered system had to be built entirely from source. (Even if a library routine is upgraded into a version which does the same thing, bit-for-bit, changing the timing can still mess up real-time systems.) Besides eliminating mysterious errors which are pure hell to track down, my policy had the advantage that in a real disaster, where the company computer and all attached storage burned to the ground, we could rebuild any delivered software product from source stored in off-site back up. In a real worst case, we could key in everything from a stored listing. (During one fiasco, I actually saw this happen. Before this, everybody called me a ridiculous pessimist.)
All this took place before "DLL Hell" traumatized anyone. You heroes still fighting with these problems are probably doomed, but that isn't unusual for heroes.
Regards,
prehistoric
Suggested Windows 7 message: "Found old hardware; install Puppy"
Last edited by prehistoric on Sun 18 Oct 2009, 13:49, edited 1 time in total.
prehistoric
I agree having the source and any patches or special config options
is the only way to go
yeah still trying to sort out something that keeps on changing
keeps you on your toes .... or should I say paws
thanks for your post
Joe
People couldn't understand why I insisted every delivered system had to be built entirely from source. (Even if a library routine is upgraded into a version which does the same thing, bit-for-bit, changing the timing can still mess up real-time systems.) Besides eliminating mysterious errors which are pure hell to track down,
I agree having the source and any patches or special config options
is the only way to go
You heroes still fighting with these problems are probably doomed,
yeah still trying to sort out something that keeps on changing
keeps you on your toes .... or should I say paws
thanks for your post
Joe
python slaxer pup
python-2.5.2-i486-5-slxr
all was compiled from source on slaxer-pup
since tcl and tk and db were updated all was recompiled
and I added a better new icon in the menu
this brings python up to date with slackware 12.2 and its libs
you need all 4 packages
http://puppy2.org/slaxer/db44-4.4.20-i486-2-slxr.tgz
http://puppy2.org/slaxer/tcl-8.5.5-i486-1-slxr.tgz
http://puppy2.org/slaxer/tk8.5.5-i486-slxr.tgz
http://puppy2.org/slaxer/python-2.5.2-i486-5-slxr.tgz
I built these as slackware packges because it was faster to install
with pkgtool compared to over 5 minutes with petget
I manually checked the depends before I uploaded
time will vary based on your system
enjoy
Joe
all was compiled from source on slaxer-pup
since tcl and tk and db were updated all was recompiled
and I added a better new icon in the menu
this brings python up to date with slackware 12.2 and its libs
you need all 4 packages
http://puppy2.org/slaxer/db44-4.4.20-i486-2-slxr.tgz
http://puppy2.org/slaxer/tcl-8.5.5-i486-1-slxr.tgz
http://puppy2.org/slaxer/tk8.5.5-i486-slxr.tgz
http://puppy2.org/slaxer/python-2.5.2-i486-5-slxr.tgz
I built these as slackware packges because it was faster to install
with pkgtool compared to over 5 minutes with petget
I manually checked the depends before I uploaded
time will vary based on your system
enjoy
Joe
Last edited by big_bass on Wed 21 Oct 2009, 17:31, edited 3 times in total.
wifi radar needs pygtk and PYTHON to compile that is a big list
note: these were all compiled from source and then packaged as tgz packages
on slaxer-pup also I needed to tweak wifi radar to work in the menu and run
this was a lot of work but if helps you get online its worth it
installs in
Menu >Network>wifi-radar with its GUI
wifi-radar-1.9.9-i486-slxr.tgz click_here
-->pixman-0.12.0-1-i486-slxr.tgz click_here
-->cairo-1.6.4-i486-slxr.tgz click_here
-->pygobject-2.15.4-i486-slxr.tgz click_here
-->pycairo-1.6.4-i486-slxr.tgz click_here
-->pygtk-2.12.1-i486-slxr.tgz click_here
I don't have wifi but I built this for those who do
this is what slackware uses to set up wifi so its well documented and supported
http://wifi-radar.berlios.de/
http://wifi-radar.berlios.de/v1.x/
Note:I know that python and its add ons
are large packages but many special programs require it
for this reason I don't pre install it in slaxer-pup
but offer it as an add on package
*and since future development with puppy wifi is "iffy" to say the least
iit is better to have more solid options and those that have already set up wifi with wifi-radar will feel at home
Joe
note: these were all compiled from source and then packaged as tgz packages
on slaxer-pup also I needed to tweak wifi radar to work in the menu and run
this was a lot of work but if helps you get online its worth it
installs in
Menu >Network>wifi-radar with its GUI
wifi-radar-1.9.9-i486-slxr.tgz click_here
-->pixman-0.12.0-1-i486-slxr.tgz click_here
-->cairo-1.6.4-i486-slxr.tgz click_here
-->pygobject-2.15.4-i486-slxr.tgz click_here
-->pycairo-1.6.4-i486-slxr.tgz click_here
-->pygtk-2.12.1-i486-slxr.tgz click_here
I don't have wifi but I built this for those who do
this is what slackware uses to set up wifi so its well documented and supported
http://wifi-radar.berlios.de/
http://wifi-radar.berlios.de/v1.x/
Note:I know that python and its add ons
are large packages but many special programs require it
for this reason I don't pre install it in slaxer-pup
but offer it as an add on package
*and since future development with puppy wifi is "iffy" to say the least
iit is better to have more solid options and those that have already set up wifi with wifi-radar will feel at home
Joe
- plaguedogs
- Posts: 60
- Joined: Sat 18 Oct 2008, 22:04
fortmactux can be reached at fortmactux@gmail.com
the homepage is here http://sites.google.com/site/fortmactux/
i dont know anything about it, prehistorics comment just caught my eye because im an Albertan who might be headed up to fort mac next month.
fortmac is short for Fort McMurray, a big dot on the map for its oil and gas industry, and its abundance of Newfies.
welders, fitters, cat skinners, etc fort mac is were the cash is. call your local union hall and get your travel cards. leave your wife at home, she will hate it up there.
i guess this should have been posted somewhere else, sorry.
slackware4life
the homepage is here http://sites.google.com/site/fortmactux/
i dont know anything about it, prehistorics comment just caught my eye because im an Albertan who might be headed up to fort mac next month.
fortmac is short for Fort McMurray, a big dot on the map for its oil and gas industry, and its abundance of Newfies.
welders, fitters, cat skinners, etc fort mac is were the cash is. call your local union hall and get your travel cards. leave your wife at home, she will hate it up there.
i guess this should have been posted somewhere else, sorry.
slackware4life