(old)Puppy Linux Discussion Forum

The secret of Puppeee and Pwireless2 is to use the latest Dhcpcd. All you need to to is start it and it will know which interfaces have a carrier and automatically request an IP - no configuration necessary, works on both wired or wireless networks.

yer can't beat good software

mike

jemimah wrote:The secret of Puppeee and Pwireless2 is to use the latest Dhcpcd. All you need to to is start it and it will know which interfaces have a carrier and automatically request an IP - no configuration necessary, works on both wired or wireless networks.

Can we have a version we could toss in the startup folder without a gui, so it does that in the background unknown to users. And if users want to manually set they could run the default Pwireless2 GUI?
ttuuxxx

Actually, you could already do that with the latest version. Just delete gtrayicon from the startup folder. The frontend and backend are completely separate. I experimented this version with putting the Pwireless2 daemon startup in /etc/init.d but I think I'm going to move it back to /root/Startup because for some reason it adds like 15 seconds to shutdown time, at least on my machine.

Pwireless2 daemon startup in /etc/init.d but I think I'm going to move it back to /root/Startup because for some reason it adds like 15 seconds to shutdown time, at least on my machine

the /startup stuff would get killed along with other X apps but init.d daemons are left running (part of the reason for dirty shutdowns on full installs.)

mike

I tried kill -9ing them in the shutdown scripts, but that was ineffective. Probably further research is necessary, since it would be nice if restarting X didn't take you offline.

The secret of Puppeee and Pwireless2 is to use the latest Dhcpcd.

sounds nice but as a noob I have no clue on what it is.

using google it says it is something in the terminal that one call up writing Dhcpcd

I should write that down on a paper and test it then.

Just now I try to trippleboot so will take some time.

Hmmm .....

mikeb wrote: the /startup stuff would get killed along with other X apps but init.d daemons are left running (part of the reason for dirty shutdowns on full installs.)

Not necessarily all startup stuffs will be ... daemonized ones without display hooking won't be (ex: daemonized wpa_supplicant doesn't get killed) ... I did have an idea a couple of moons ago to resolve dirty shutdowns for all cases of installs ... Maybe we can pursue it after our next little project is done ?


jemimah,
Startup and init.d scripts are handled differently. For startup scripts, you can just specify-n-forget ... but you may want to implement re-entrant possibility for daemons should X is restarted. For init.d, they should have (minimum) start & stop option flags to be handled by rc.sysinit and rc.shutdown. Please look at CUPS init.d script as an example ... Most of my newer scripts with auto-start ability are able to handle both Startup and init.d invocation ...


Rgds

Yep that's likely what the problem is - needs a stop option. Back to work for me...

[Edit - yup, that solves it. Thanks for the hint - I should have realized that... ]

Actually I do find a little quirk in that I have a mini script to check battery status in startup but even though exec and & is used delayedrun hangs around


mike

ps I fix the dirtiness for full installs but for frugal although this is handled the union prevents cleanliness

jemimah wrote:The secret of Puppeee and Pwireless2 is to use the latest Dhcpcd. .

The thing about the thing, lol Ok i'll stop messing around, to compile the latest Dhcpcd in 2.14X I would have to update glibC, I was lucky enough to do it once, when I changed it from 2 series to 3 series, but anything past that I think I would be pushing it, So that means no auto start for 2,3 series, hmmmm I think we need a different work around for this.
ttuuxxx

So..."getting online" in general needs to be easier?

In two reviews, this is mentioned. Both are on the front page of google, under "puppy linux review"

http://lifehacker.com/307542/taking-pup ... for-a-walk
http://discuss.extremetech.com/forums/t ... 23950.aspx

That's what the Pwireless2 project attempts to correct. Unfortunately, connecting wireless on Linux is really freaking complicated! Fixing a problem for one person, breaks things for another. And it seems as if every device driver acts a little differently, and there are way too many combinations of encryption types to feel like the problem is ever adequately solved. [/rant]

If anyone feels motivated, I could always use more help.

I'd be happy with a autolan connection that searches for eth0 and if it doesn't find a live connection it then looks for eth1 without updating Dhcpcd. Wireless is and will always be a pain, probably better to have something autostart very well than nothing at all. And jemimah your doing a great job
ttuuxxx

With the old dhcpcd you might be able to just start up a dhcpcd for each wired interface, whether it's up or not, and it will just wait for a carrier (not confirmed since I don't have an ethernet cable with me.)

I don't think you can safely assume wired interfaces are necessarily named eth*. And you have to figure out what you want to do when someone needs a static IP.

I just downloaded bitdefender 2010 live cd, based on knoppix Linux http://download.bitdefender.com/rescue_ ... 8_2009.iso its 230mb, anyways it connect to the internet and downloaded virus definitions before it even made it to desktop:) it couldn't recognize my 19"lcd lol but I had 17crt and plugged that in and it was fine.
puppy would be better as a base, if we could figure the auto-connect stuff out.
ttuuxxx

All Puppy needs is a script that does what clicking the eth0 button does.
Then it needs to do what clicking the DHCP button does, and it`s done...

sunburnt wrote:All Puppy needs is a script that does what clicking the eth0 button does.
Then it needs to do what clicking the DHCP button does, and it`s done...

hmmm that's what I said, its been the same routine with at least 10 pc's I've tried, even with a USB2LAN stick, it showed up as eth1, or my other pc that has a built in lan on the motherboard and a pci lan card is still eth1 for the card, really if it searches for eth0&eth1, that would be at least 90% of the market, good enough
ttuuxxx

Stardust is one of the few that just works with my Acer D250 wireless but it failed doing wired LAN.

But that could be temporarily. Some linux usb does shut down the LAN card and one have to reactivate it through Windows win7 to get it going.

How could one do that from Stardust or any other puppy?

I had a usb2lan stick running on 2.14X, just plug it in first then bootup and run the network manager.
It won't work if you already booted and then plugged it in, so remember plug in then bootup.
ttuuxxx

I used this search and failed to find a thread for it.

http://www.google.com/cse?cx=0159956439 ... =FORID%3A0

Could one not build that into every puppy?
And to take up a whole mem stick for just one function?

Could you link to it?