This could not be more completed!
![Very Happy :D](./images/smilies/icon_biggrin.gif)
![Very Happy :D](./images/smilies/icon_biggrin.gif)
Thank you!
I (un)fortunately have to go away during the whole month but I take my laptop with me and will surely find connection and time to test all what you kindly "cooked" for ToOpPy users.
Cordialement.
Re #1: It does not link to icanhazip.com directly, but does use ipinfo, which does. However, ipinfo has been fixed so that it does not link there unless the user selects that as an option. By default, ipinfo does not link to icanhazip.com.I would like to test the latest version of Frisbee in DebianDog, and have 2 questions.
1) Does your version have ipinfo (icanhazip) implemented in the code?
if it doesn't,
2) Your pet seems to be structured differently from the DD setup. Should I just manually replace the files, or do uninstall first? Can you also make a deb file in addition to pet?
Dear Richardrerwin wrote:They appear to be ready for addition to the woof-CE system.
found source for network_tray and compiled it, don't know if it's compatible with alphaos.rerwin wrote:Scooby,
Thanks for consulting me about porting frisbee 1.2 to alphaos. Although I am unfamiliar with alphaos, I have been working this past week with anakin regarding porting it to DebianDog, which getting interesting. Your timing is excellent. So far, I have it working along with network_tray. DD already has the modified dhcpcd.
Found source for dhcpcd dropwait here . Since alphaos use dhcpcd 6.3.2 I downloaded itrerwin wrote: For a 64-bit OS, I think the same modified-dhcpcd source code should compile for it. I have not tried that, so assume you would work out any kinks. I think I posted the source code earlier in this thread. Let me know if it needs modification for 64-bit compatibility. You also need the script, dhcpcd_dropwait_option.
what about the pgprs pet, optional?rerwin wrote: Regarding PPPoE and pdiag, I am preparing an updated frisbee-1.2 that makes PPPoE optional. I should do the same with pdiag; if it is not present, the button for it will be disabled (greyed out). If you can provide an alternative diagnostic tool that captures logs and other info into something that is useful for debugging, either name it pdiag or make a link to the tool, naming the link as "pdiag".
I'm happy to cooperate on this and if possible respect your wish to limit number of frisbee variantsrerwin wrote: If you need further mods to frisbee, please tell me so that I can incorporate them, to minimize the number of (or avoid) frisbee variants out there.
I would like to work with you on this, in case I need to make further mods to frisbee-1.2 for alphaos, as I have for DD.
Richard
It is not required. Frisbee-1.2 implements similar logic, making pgprs redundant. But having it present would give users the option to avoid using frisbee for gprs. They use the same configuration and chatscript files, so cannot be used concurrently.Scooby wrote:what about the pgprs pet, optional?
Well, "modules" are hardware drivers, not applications, so that is out. For DebianDog, I am providing archive/tarball files for frisbee and network_tray, such that they can be expanded to "/". I include a pinstall-type file to be executed (manually) to make any necessary changes, such as deletions. I hope to master the process of making a ".deb" package for each, to eliminate possible operator errors in installing the packages. What packaging method does alphaos use. Obviously, I have not yet done my research on alphaos yet.Is there a pet of the pet-file handler that puppy uses.
Alphaos doesn't have pet system but maybe it could be provided as a module?
I meant modules in a more general sensererwin wrote: Well, "modules" are hardware drivers, not applications, so that is out.
Basically alphaOS uses arch repo's so I guess you could make an AUR package if you like.rerwin wrote: For DebianDog, I am providing archive/tarball files for frisbee and network_tray, such that they can be expanded to "/". I include a pinstall-type file to be executed (manually) to make any necessary changes, such as deletions. I hope to master the process of making a ".deb" package for each, to eliminate possible operator errors in installing the packages. What packaging method does alphaos use.
...as Americans love to say - "call me a square, just don't call me late for dinner"#140524 rerwin (for anakin): External IP removed to avoid hidden internet access
Only other thing I changed in frisbee was /etc/init.d/frisbee. I wanted the part underrerwin wrote: My intent is that there be only a single set of files constituting frisbee itself, but with a separate package of some type that has the files in the right place for debian or arch, and any other distro someone wants to use frisbee on.
Code: Select all
if [[ $1 == "start" || $1 == '' ]] ; then
Will cooperatererwin wrote: Therefore, if you discover that you need to modify frisbee file contents, please notify me so that I can incorporate the mods into a master version of frisbee. I want to avoid having many variants of frisbee floating around, when I am eager to adapt frisbee as necessary to support its widespread acceptance.
Always, mate, alwaysrerwin wrote: I am short on time right now
Code: Select all
<action>rxvt -e wpa_cli -i $INTERFACE&</action>
Code: Select all
#131126 zigbert: gui (gtkdialog) improvements.
Code: Select all
[ -f $HOME/.ipinfo ] && . $HOME/.ipinfo || CB0=true
Code: Select all
[ -f $HOME/.ipinfo ] && . $HOME/.ipinfo || CB0=false
I left that unindented to facilitate keeping track of my updates to the file. But now I can clean that up, too.Only other thing I changed in frisbee was /etc/init.d/frisbee. I wanted the part underto be indented for more readabilityCode: Select all
if [[ $1 == "start" || $1 == '' ]] ; then
I have not gotten into fixing network_tray. I just stole pemasu's Wheezy version of the executable, since DD is based on wheezy. Upgrading network_tray is a separate project, which we might work via PMs. I wonder if anyone one else (01micko?) has addressed the gtk3 issues already.Do you have the same intent for network_tray? I had to change it to compile with gtk3.
function names are changed.
Since DD appears to be using only frisbee for network management, I made /usr/local/apps/Connect/AppRun a link to frisbee's connect function. But I did not notice that the other 2 are needed in that case.Also I had to add
/usr/local/apps/Connect/AppRun
/usr/local/bin/defaultconnect
/usr/local/bin/defaulttexteditor
I'm not sure they are considered part of the network_tray package?
Or maybe in a generic package for distros other than DD, which can use the existing network_tray executable.Also gtkdialog updated to use gtk3, not either part of network_tray or frisbee
Maybe They should be in a special alphaOS compatibility package?
It is only part of the Network Wizard and is not used by frisbee.What is wag-profiles.sh and is it affecting frisbee in any way?
I agree that it should not use a specific terminal emulator. Is it really necessary to use one there, instead of a dialog of some sort? I am open to using a different method.Note:
in /usr/local/bin/frisbee line 413rxvt is explicitly called, alphaOS uses another default terminal.Code: Select all
<action>rxvt -e wpa_cli -i $INTERFACE&</action>
could this call be substituted with something like /usr/local/bin/defaultterminal ?
else I could provide rxvt as a symlink to default terminal. which is best?
I think I will use yours as a new basis for the DD version, to get zigbert's fix, but with the icanhazip stuff removed, as was requested.About ipinfo:
I did extract one version from the latest slacko with the new commentI really like this version better. Looks better and has added a checkbox for optionalCode: Select all
#131126 zigbert: gui (gtkdialog) improvements.
use of icanhazip. Only thing I wanted to change was not to use icanhazip by default
(line 17 and 18 in the new version)
fromtoCode: Select all
[ -f $HOME/.ipinfo ] && . $HOME/.ipinfo || CB0=true
Code: Select all
[ -f $HOME/.ipinfo ] && . $HOME/.ipinfo || CB0=false
Thank you, Rerwin!rerwin wrote:Here are two special packages that work for me in DebianDog. The packages are unlike any of the usual package types.
Code: Select all
### BEGIN INIT INFO
......
.....
### END INIT INFO
I was wondering if there was icons with better resolution for network_tray?rerwin wrote:I have not gotten into fixing network_tray. I just stole pemasu's Wheezy version of the executable, since DD is based on wheezy. Upgrading network_tray is a separate project, which we might work via PMs. I wonder if anyone one else (01micko?) has addressed the gtk3 issues already.
AppRun calls defaultconnect but if AppRun is just a symlink then it would not be needed.Since DD appears to be using only frisbee for network management, I made /usr/local/apps/Connect/AppRun a link to frisbee's connect function. But I did not notice that the other 2 are needed in that case.
SInce it starts wpa_cli in a interactive shell I believe it is nescessary.I agree that it should not use a specific terminal emulator. Is it really necessary to use one there, instead of a dialog of some sort? I am open to using a different method.
I now have compiled a test version of dhcpcd 6.3.2 with dropwait support for 64-bit OS.rerwin wrote: For a 64-bit OS, I think the same modified-dhcpcd source code should compile for it. I have not tried that, so assume you would work out any kinks. I think I posted the source code earlier in this thread. Let me know if it needs modification for 64-bit compatibility. You also need the script, dhcpcd_dropwait_option.
Code: Select all
DWOPTION="$(dhcpcd --help | grep -o '\--dropwait' | cut -f 1 -d ' ')"
Code: Select all
+ " [-r ipaddr] [-s ipaddr] [-t timeout] [-j dropwait]"