I tested the fix (updated ntfs-3g) and it worked fine in BK's Precise and in Slacko.

I do have gtkdialog from Thunor`s git in Upup Precise versions. I have used the revision of the time. In Upup Precise 3.7.2 it is:
# gtkdialog --version
gtkdialog version 0.8.4 r503M.....which means essentially 0.8.3 version.

I have updated gtkdialog for having support of Pmusic updated versions. I do have installed also all other Pmusic supported dependencies....including pEqualizer. The bugs....dunno...I havent noticed bug reports....but that does not give 100 % proof.

The possible IO freezing bug is the one which puzzles me. It seems the affected users get the same problem also with 3.7.2 kernel. I dont have any clues of the reason. Filesystem handling...aufs related...no idea.

Barry,
Since you are planning another release of precise pup, I request that you consider adding some of the packages I have provided for the integration of frisbee. Adding these three packages would simplify the installation and trials of the remaining, frisbee-specific packages by users/testers.

These packages do not impact the functioning of puppy without the frisbee-specific packages:

The net_setup and wag_profiles packages simply move wag-profiles.sh into its own package, so it can be shared with frisbee and updated independently when wifi drivers are added. The woof_updates package adds frisbee interfaces to the connect wizard and AppRun, and provides a dhcpcd interface script to utilize the dropwait feature if present. Wag-profiles now includes the use of that script.

To facilitate developers' inclusion of the new frisbee package, please add a woof slot for it. The remaining two packages are alternatives for the dhcpcd and network_tray slots. I assume you are not yet ready to add the frisbee-dropwait-network_tray updates, but feel the listed three can be added with no impact to puppy. Note, however, that the old "Frisbee" package in the library will not work with the new connect interface, but should not be used instead of the integrated version.

Currently, the new dhcpcd...dropwait and network_tray-2.6 could be added to the puppy repo. I am adding Argolance's internationalization mods to the frisbee package. So, please wait for the internationalized version before adding frisbee to the repo.
Richard

UPDATE 2/7/2012: The internationalized version of frisbee is now the "latest", although I expect some further "fine tuning" to be done. Also, I have provided a renamed network_tray package (at the above link) to correspond to its being an alternative to 2.5 instead of an upgrading replacement. I assume that the choice gets put into the "slot" for network_tray and is not a separate slot. The same goes for the dropwait version of dhcpcd. Please instruct me if you need a different naming format. I believe, now, that the "frisbee" set of packages is ready for release. Thanks for considering it.
RichardLast edited by rerwin on Thu 07 Feb 2013, 17:00; edited 2 times in total

When we are speaking of wireless...
Rtl8192cu has had problems. I have provided couple of times...in separate threads the 8192cu proprietary driver for those people without working wireless....succesfully.

It could be reasonable to provide the alternate driver in official repo. If possible. The pet modifies the MODULESCONFIG and gives preference for 8192cu....so it is not probably suitable to be in base sfs.

I'm getting two spaced audio pops when precise inits alsa.
When alsa shutsdown it leaves line out with a hum (sounds like an open circuit hum one gets from an ungrounded input cable) other distros are not doing this such as fatdog

programchooser
/usr/bin/programchooser: line 40: /root/.config/tmp/program: No such file or directory
Usage: grep [OPTION]... PATTERN [FILE]...
Try `grep --help' for more information.
/usr/bin/programchooser: line 89: /root/.config/tmp/prgm: No such file or directory
/usr/bin/programchooser: line 90: /root/.config/tmp/prgm: No such file or directory

ndiswrapperGUI.sh and wag-profiles.sh are part of net_setup package. The "missing" clean_up_gtkdialog is actually in wag-profiles.sh.

defaultchmviewer is ok. It will only be relevant if a CHM viewer pkg is installed.

defaulthandler -- yes, there is a syntax error, now fixed.

mailto.sh -- again, this is OK. This script is only used when Sylpheed is installed, to set a mail handler for Firefox.

pdict -- many gtk apps spit out error messages. As long as the app works, that is all we are bothered about.

programchooser -- hmmm, this is from an ancient PET named 'programchooser', created by ...oh, his name escapes me right now.
It is a dependency of another PET 'wallpaper', by the same guy.

Did you try and run programchooser on it's own? it is supposed to be called from wallpaper, with appropriate parameter passed. It probably can be run standalone if appropriate param passed._________________http://bkhome.org/news/

Barry,
Since you are planning another release of precise pup, I request that you consider adding some of the packages I have provided for the integration of frisbee. Adding these three packages would simplify the installation and trials of the remaining, frisbee-specific packages by users/testers.

These packages do not impact the functioning of puppy without the frisbee-specific packages:

The net_setup and wag_profiles packages simply move wag-profiles.sh into its own package, so it can be shared with frisbee and updated independently when wifi drivers are added. The woof_updates package adds frisbee interfaces to the connect wizard and AppRun, and provides a dhcpcd interface script to utilize the dropwait feature if present. Wag-profiles now includes the use of that script.

To facilitate developers' inclusion of the new frisbee package, please add a woof slot for it. The remaining two packages are alternatives for the dhcpcd and network_tray slots. I assume you are not yet ready to add the frisbee-dropwait-network_tray updates, but feel the listed three can be added with no impact to puppy. Note, however, that the old "Frisbee" package in the library will not work with the new connect interface, but should not be used instead of the integrated version.

Currently, the new dhcpcd...dropwait and network_tray-2.6 could be added to the puppy repo. I am adding Argolance's internationalization mods to the frisbee package. So, please wait for the internationalized version before adding frisbee to the repo.
Richard

Thank you Richard.

For me, for a long time (since the first version), Frisbee is the best interface (efficient and friendly) for wifi.
I tested your changes and I have one thing to say: "I ​​am excited that BK decides to integrate your Frisbee in woof", it will be a real benefit for users.

I believe that many of the problems with boot codes stem from the fact that some of the definitions in the official help to be found on the typical ISO by pressing F2/F3 are too open to interpretation and therefore can cause confusion.

So, using the two working examples from that post I will attempt in this post to
re-define/expand a couple of the more contentious codes ensuring that they are valid for both examples and other boot methods.

This definition immediately begs the question – What is meant in this context by “booting from?” Looking at CASE 1: it is clearly not the bootable Smartmedia card which holds the boot-loader and kernel. By elimination therefore it relates to the main sfs.

Proposed re-definition of pmedia=

Quote:

pmedia=usbflash The type of media upon which the main sfs is located. Choose one of these: usbflash usbhd usbcd ataflash atahd atacd atazip scsihd scsicd cd

This revised definition holds true for CASE 2: (usbflash) and live cd/dvd.

Official definition of pupsfs=

Quote:

pupsfs=sdc1:/puppies/wary501/puppy.sfs Override auto search.

This needs expanding.

Proposed re-definition of pupsfs=

Quote:

pupsfs=sdc1:/puppies/wary501/puppy.sfs Override auto search.
Use when you are running more than one copy of a specific puppy or multiple puppies. Also use when the main sfs is not in the same location as the kernel.

The revised tentative definitions above, which are hopefully correct, serve only as examples. It had been my aim to revise a few more but I swiftly ran into trouble trying to do so. I concluded that Barry is best placed to do so, understanding not only the algorithms, overrides and conflicts but the full intent behind them._________________Regards ETP

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum