Puppy Linux Discussion Forum

[prehistoric]

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"

[big_bass]

prehistoric

[big_bass]

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

[big_bass]

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

[plaguedogs]

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

[big_bass]

[vanchutr]

@big_bass
Please compile the broadcom wifi (wl.ko) (in 2.6.27.7). My comp won't connect to internet without wl.ko. (I can't compile that myself). Please...

[Lobster]

Slaxer_Pup uses 4.12 and is a puplet
A new wooflet compilation is being attempted based on 4.3.1
and the emerging Woof build system
http://puppylinux.org/wikka/Spup

[big_bass]

Hey Lobster
A Big thanks for the wikka info

in progress
slaxer-pup will focus on compiling all the apps from source
instead of borrowing pre-compiled packages




Joe

[ttuuxxx]

[big_bass]

[mikeb]

[vanchutr]

@big_bass
Thank you very very much
Your pet help me connect (wife) to internet. I post this with my laptop (emachines - D725 - CPU T4200 - 1Gb RAM.

1. Step 1:
#lsmod
-> To check out what modules are loaded. b43 and b43legacy were'nt loaded (That's OK)
2. Step 2
# modprobe wl
-> No error message -> That's good
3 Step 3
Run network wizard -> See the eth1 interface -> Choose "eth1" -> Choose "AutoDHCP" -> Wait -> OK Save Config .
4. Step 4
Run Pwireless from menu.

Thank you again. Be happy! please

[mikeb]

[big_bass]

vanchutr

great news I added the line of code modprobe wl to the pinstall

since that worked for you

thanks for listing your steps
-----------------------------------------------------------------


mikeb

I was glad to hear you needed that module also

*its more difficult to set up modules for hardware you don't have this is where testing is so needed thanks

Joe