(old)Puppy Linux Discussion Forum

Nothing wrong with that. Should work. The older package I got though didn't have them, does your latest? (Guess I'll find out, grabbing now!)

EDIT: No, no links!

The "hooks" link is already in precise. Could you simply create one in slacko and be done with it? I assume you already make some mods to it; that could be one more.

Or are there other things in the libexec directory, so that you cannot have both the directory and a link to the other? If that is the case, I could check for that situation and create the "99-" links in the pinstall script. Or you could make them for slacko-14.

rerwin wrote:The "hooks" link is already in precise. Could you simply create one in slacko and be done with it? I assume you already make some mods to it; that could be one more.

Or are there other things in the libexec directory, so that you cannot have both the directory and a link to the other? If that is the case, I could check for that situation and create the "99-" links in the pinstall script. Or you could make them for slacko-14.

Yes.. all the dhcpcd hooks exist for the dhcpcd package in there, the links would need to be individual.

Thanks for understanding, and no, I don't mod frisbee at all, hence the silly bug with svg, only the icon, and only because I don't like Barry's "world " icon.. petty? Yes!

I meant that you modify slacko, so could add the links. But, if you don't want to do that, just tell me and I will update the pinstall script.

It's ok, I can add it to my general pinstall that takes care of other stuff. The only concern I have is for retrofitting for slacko-5.4 (and 5.3x) users, unless of course it's no trouble to you.

As I said, by the next slackware it looks like they are moving to the debian path (/lib/dhcpcd) anyway, so just a note for older slacko users would suffice, or a I can post a separate script to take care of it for them and you could link to it. I may even do it at the top of the 5.4 bugs thread.

I know the amount of work you have put into this, especially the icon, and it is very much appreciated. I know blokes like cthisbear will appreciate it because he recommends to everyone to install frisbee.

Now, I get it! I could not resist working something up for 20130227. I will PM the updated version for you to try. Tell me how it works soon so I can re-upload it for everyone.

It didn't attach!.. Please redo PM

EDIT:

Ok, got it now, and works,

Thanks

...just some feedback,

I have been solely using frisbee on my 3 testers with the latest slacko-5.4.0.5 and no problems. My main box is still using eth1 and the icons are blinking now, so I don't know what fixed it but hey, I'll take it

On my main laptop I have been switching between wlan0 and ppp0 with no problems. The ppp connection is through my mobile phone. I don't have a dialup account to test the icon switching script but I did a lab test on that script and it looks good.

As a feature request, not urgent, I wonder if it's possible to call the frisbee GUI from the tray icon when ppp is disconnected? As said, not a top priority. Too late in the development cycle to risk stability anyway, just a thought for the future.

Judging by the lack of others' feedback there mustn't bee too many problems!

Cheers

Tried frisbee-1.0-20130228 from the noarch repo in Racy 5.5.
Does not appear to work unless you first use another connection tool and connect to a wifi network.
Also when it does work eventually, it goes to full screen mode.(see picture)

I also attach the terminal output where looks like that frisbee has trouble finding wpa components

There seems to be something missing from the new Racy 5.5 that stops Frisbee detecting any wifi signals OOB.

As mavrothal mentions above, if another Network Manager like SNS is used first then the wifi signals do also appear in Frisbee.

pdiag output attached.

Cheers
peebee

As a result of collaboration by PM with peebee and mavrothal, I have made some further small improvements to frisbee and re-implemented the dhcpcd hooks for notifying the user and network_tray icon, as well as frisbee itself, of changes in the state of the network interfaces.

Because we discovered that some PCs require the "dropwait" feature added to the dhcpcd in precise pup, I am including it in a "kit" tarball for installation to the "5.5" versions of puppies built with the recent versions of woof. Note that the dhcpcd_dropwait package is identical to that in precise 5.5, so it need not be installed to precise pup again from the tarball.

The main mods to frisbee are:

• - The "Enable Wireless" checkbox is now "Connect WiFi Automatically". Previously, that checkbox only indicated the connection state, setting the check mark if a connection existed. It did not control wireless across reboots, as the label might imply. Now, unchecking the box actually prevents the automatic connect at boot-up, as requested by one of the participants in this thread.
  
  - A new checkbox, "Announce State Changes" lets the user control whether the state-change splash pop-ups appear, per a request I saw a while ago.
  
  - Some spacing changes now avoid clumping buttons and checkboxes to the right side of the window.
  
  - To support developers using frisbee as the main/default network manager, I added an install option dialog offering to pre-set frisbee as the default and set flags so that frisbee itself need not be run to start the pop-ups and make the first (ethernet) connection. But it would be needed initially to select a wireless network.

The state-change notification dhcpcd hooks are consolidated into the single file, 99-notify, including the logic of the dhcpcd-hooks script, in a manner similar to that used by the existing hook code-fragment files, probably to execute efficiently.

This catches me up on the to-do list AFAIK, except for upgrading the network_tray-2.6 to better handle multiple active network interfaces. If any further problems/issues arise, please report them here for my attention. I am open to adapting frisbee further to maximize its convenience and usefulness.
Richard

Hi Richard

Tested the new version of Frisbee in the 5.5_kit....

On Precise, if I answer "Yes" to the new startup question I get a screen with all buttons greyed out and no wifi signals detected - see screenie attached.

On Precise, Slacko, UpupPrecise3.8.2, Wary5.5 and Racy5.5 if I answer "No" to the new question I get no wifi signals detected until I tick the new "Automatic Wifi Connection" (Which is unticked by default) and a Refresh occurs - manually or by timeout.

Interestingly, the dhcpcd-drop-wait pet is NO LONGER needed in either Wary or Racy with this new Frisbee so maybe doesn't need to be in the kit?

However for both Wary and Racy although a wifi connection is established, the Network Tray does not update and continues to show the red cross.

All of this is tests on pristine frugal pfix=ram installs of each Puppy with no savefile - problems may be different after reboot and savefile creation but this has not been tested.

Cheers
peebee

Hi Richard,
I tested 5.5 kit in my "problem" machines with Racy and looks good.
In my case the tray icon changes as expected.
I find too that dhcpcd-dropwait is not required (nor the older Jemimah's wpa_suplicant I was using at times with Racy).
I would also agree with peebee that the /etc/frisbee/.wireless_autostart flag should be on by default. Frisbee was established primarily as a WiFi connection manager

peebee wrote:On Precise, if I answer "Yes" to the new startup question I get a screen with all buttons greyed out and no wifi signals detected - see screenie attached.

This is expected because I intended the option to be for developers creating a new ISO. The option makes frisbee mode already on, so that frisbee does not think it needs to start things up. However, I have already addressed this with a simple change in the next version I upload, so that frisbee will know it is the first run after installation.

On Precise, Slacko, UpupPrecise3.8.2, Wary5.5 and Racy5.5 if I answer "No" to the new question I get no wifi signals detected until I tick the new "Automatic Wifi Connection" (Which is unticked by default) and a Refresh occurs - manually or by timeout.

My thinking was that a user would initially have to select a network by starting frisbee, so can opt for the automatic connection. So, I am not very concerned about a change from the traditional behavior immediately after installation. I want the user to be in control of connections, so do not want frisbee to just "take over". Although this is different from the betas, I think it s more conservative and less intrustive. Although Frisbee was considered a wifi manager, I am positioning frisbee-1.0 as a complete network manager capable of someday replacing the network wizard.

Interestingly, the dhcpcd-drop-wait pet is NO LONGER needed with this new Frisbee so maybe doesn't need to be in the kit?

That is probably because I added part of mavrothal's patch suggestion, increasing the time before "giving up" on being able to connect, from 45 seconds to a minute. So, fewer machines now require dropwait, although it is valuable for weak connections. I will keep it in the kit as an option, for best performance.

However for both Wary and Racy although a wifi connection is established, the Network Tray does not update and continues to show the red cross.

That concerns me! I will investigate that. To help me along, could you PM me a pdiag file from frisbee at the point where you see this. Thanks.
Richard

rerwin wrote:I think it s more conservative and less intrustive. Although Frisbee was considered a wifi manager, I am positioning frisbee-1.0 as a complete network manager capable of someday replacing the network wizard.

That concerns me! I will investigate that. To help me along, could you PM me a pdiag file from frisbee at the point where you see this. Thanks.
Richard

Hi Richard

I think the new way is so counter-intuitive that it will confuse people...

It is not obvious that ticking that box will make Frisbee spring into life - not to me anyway.

Similarly with the new startup box - most users won't know whether to say Yes or No - suggest No is made the default and words added to say say No unless....

Will PM you the pdiag shortly.

Cheers
Peter

peebee wrote: I think the new way is so counter-intuitive that it will confuse people...

It is not obvious that ticking that box will make Frisbee spring into life - not to me anyway.

All I can say is that I was about to post that the new frisbee is totally broken before I remembered the Richard had mentioned this change...
As I mentioned before the default should be on, unless you want to add a big "scan" button a la network-manager...

Peebee & mavrothal,
Thanks for your further comments. They are not being ignored.

In the pdiag file I see that the entire kit was not installed. The tray icon update logic is moved to the woof_updates package. Please install it. It is separate so that it can be available even if frisbee is omitted; developers or users could set its flag to enable notification with the other network managers. Although the dhcpcd package appears to be optional, but why use only part of the complete frisbee solution!

I am working to reconcile your comments with my concept for frisbee. I probably need to treat the installation experience separately from the experience of initial boot-up after installing a new distro containing frisbee. I want the default states (whatever they turn out to be) to occur at initial boot-up if none of the flags are set, so that a remaster does not need to copy any flags. The flags should represent the exceptions and can be set during package installation or be built into a new distro (so would be copied in a remaster). Developers would then be allowed to pre-set any flag if they want an exception at initial boot-up of their distro/remaster. That is the beauty of using flags for control rather than hard-codded logic.
Richard

rerwin wrote:In the pdiag file I see that the entire kit was not installed.

Hi Richard

My apologies for not understanding that the new Frisbee needed some infrastructure changes - if I load all 3 pets from the tarball then the network tray icon in Racy55 does change to the connected state.

Have you lengthened the refresh interval? There can be a very long delay between closing Frisbee for the 1st time and being asked if you want it to be the default.

I certainly support your efforts to separate user and developer setup functions....

Thanks
Peter

peebee wrote:Have you lengthened the refresh interval? There can be a very long delay between closing Frisbee for the 1st time and being asked if you want it to be the default.

I have not changed any interval other that that before the "no wireless connection" message pops up. That is done by a separate process (invoked with an "&").

The refresh interval remains at 15 seconds.
Richard

Looks like that when X is restarted network_tray is not properly informed of the net state.
Starting a latter instance behaves as expected (see picture).
That is on precise 5.5 with frisbee 0314 and woof-additions 0314.