(old)Puppy Linux Discussion Forum

prehistoric wrote:Grrrr. No problem with gtk3 and libapulse, but I need that updated update-firefox.sh. (I don't trust myself anymore to make significant changes to scripts. Too many implicit assumptions to discover.)

Of course you can have it. It's attached (remove the fake-gz extension). Please test it by running in a sandbox.

I'll wait on the new improved fatdog. Also looking to try Gimp 2.9.6, for increased color depth and wavelet decomposition, though that branch is still not stable.

16-bit colour depth will be welcome, so is a "effect" layer (instead of having to bake it the effect into the layer immediately). Oh well, it will get there when it gets there.

I'm expecting to see 2.8.22 in fatdog.

Yes, this the version that comes in next release.

Looking like we will all be forced to move to gtk3 in a year or so.

We had a discussion whether to have gtk3 in the base, or not yet. We're trying to hold off as much as we can. We alreaady have gtk2 and qt5 in the base ....

(Why? I don't know. Just curious. My Raspberry Pi would do most of what I need.)

Build it and they will come

Thanks jamesbond,

Now posting from a separate Fatdog 710 installation using Firefox 57.0.

So far, so good. However, this appears to stop me from using NoScript.

(Yes, I know about enabling legacy extensions. I'm waiting for the Quantum version release as a pure extension, not playing software Jenga by stacking unstable releases.)

As always with software, it takes all the running you can do to stay in one place.

jamesbond wrote:...Build it and they will come

Sounds like a house of ill-repute, which resembles what some women have said about my workshop, though I'm sure they were thinking of a different kind of establishment than I was.

Hello, Fatdog64 team.

In keeping with its Puppy roots, Fatdog64 is a friendly OS. I have made minor adjustments to improve my user experience, and you might find them useful as well.
I have previously submitted some color scheme changes for the panel to coordinate with Smokey01's theme. These new ones are related to the Control Panel, enlarging windows to give a better view where it had been too small. The changes are listed in the attached .txt file, and anyone could easily make the changes to his own existing files.
I would adjust Nathan Wallpaper Switcher to enlarge parts of the main interface, but it is beyond my current knowledge.

Thanks as always.

Fatdog64-720 Beta is released.

Forum thread.

prehistoric wrote:Thanks jamesbond,

Now posting from a separate Fatdog 710 installation using Firefox 57.0.

So far, so good. However, this appears to stop me from using NoScript.

(Yes, I know about enabling legacy extensions. I'm waiting for the Quantum version release as a pure extension, not playing software Jenga by stacking unstable releases.)

As always with software, it takes all the running you can do to stay in one place.

Maybe run noscript on palemoon or seamonkey then? As an aside Quantum works exceptionally well on fatdog64.

prehistoric wrote:Thanks jamesbond,

Now posting from a separate Fatdog 710 installation using Firefox 57.0.

So far, so good. However, this appears to stop me from using NoScript.

(Yes, I know about enabling legacy extensions. I'm waiting for the Quantum version release as a pure extension, not playing software Jenga by stacking unstable releases.)

As always with software, it takes all the running you can do to stay in one place.

No Script now works on Firefox Quantum.

I found in the kernels/710/ directory from the repository the kernel-modules.sfs-4.14.12 , vmlinuz-4.14.12 and microcode-update-20180111.cpio , which I presume could be used to update the kernel .
I know what to do with the first two , but I don't know how to implement microcode-update-20180111.cpio . Could anybody give me a hint

Directory kernels/710 is symlinked from kernels/720. microcode update is a feature for Fatdog64 721. It's discussed starting from the sixth paragraph of the 72x release announcement.

Thank's step
So , I'll have to jump to the Fatdog64-721 train ...

Anyone know how to use three monitors on Fatdog710? I can only get two working.

Dropbear uses the network to show fatdog screen to stranger , but that
probably isn't what you want.
_______________________________________________

s243a wrote:Anyone know how to use three monitors on Fatdog710? I can only get two working.

Do you have three video outputs on your graphics card? Is so they should be detected. I have DVI, VGA and HDMI. Zarfy shows me all three although I'm not using the HDMI output.

I am not able to get "make install" command working. All dependencies are already installed. I am trying to share my USB LTE modem's connection to my Android phone. It works in Windows 7.Have attached a screenshot. Would appreciate any help. Thanks.

stemsee wrote:Hi

I have spent sometime searching for a solution to sharing internet on FD. i found a solution on github that worked first time! It's called create_ap-master.

Unzip and cd into the create_ap-master directory checkout the readme and install the dependencies. Then 'make install'. In term type 'create_ap' to see a list of commands for a variety of hotspot modes.

I used and tested

Code: Select all

create_ap wlan0 wlan0 stemsee 66669999

What this does is create a wifi hotspot (AP) using the same device which connects to the internet. Laptop and android devices have internet!
i am using a usb dongle.

Must have a wifi card that supports master mode.

Might be a worthy addition to FD.

amn87,

You didn't say whether you had the devx sfs installed. If not, that is where Puppy (and Fatdog) keeps all the tools for compiling.

Not sure if you are using 710 or 720 (I haven't kept up with last few months of changes), but the sfs file you need is here.

http://distro.ibiblio.org/fatdog/sfs/720/

If you need help with how to use sfs files, look here:

http://distro.ibiblio.org/fatdog/web/ about 2/3's down the page.

Dan

Thanks for replying. No I did not have the devx sfs installed. I was not aware it was needed. I am on 721. So this one http://distro.ibiblio.org/fatdog/sfs/72 ... vx_721.sfs?
P.S. The Nvidia SFS link http://distro.ibiblio.org/fatdog/sfs/72 ... 4.14.6.sfs is not working. Same issue with the mirrors as well. Anywhere else I can get it? I have PMed jamesbond in this regard but have not heard from him yet.
Edit: Nvidia drivers issue fixed.

dancytron wrote:amn87,

You didn't say whether you had the devx sfs installed. If not, that is where Puppy (and Fatdog) keeps all the tools for compiling.

Not sure if you are using 710 or 720 (I haven't kept up with last few months of changes), but the sfs file you need is here.

http://distro.ibiblio.org/fatdog/sfs/720/

If you need help with how to use sfs files, look here:

http://distro.ibiblio.org/fatdog/web/ about 2/3's down the page.

Dan

Fatdog control panel is too slow!

Why does it have to load applets?

Why not just make them static links

Anniekin wrote:Fatdog control panel is too slow!

Why does it have to load applets?

Why not just make them static links

In my opinion, since I didn't write Fatdog control panel, loading applets makes the panel extensible and customizable. For instance, the optional nvidia driver package for Fatdog-720 adds the nvidia control panel applet to Fatdog control panel.
I think the script changed a bit between Fatdog-710 and 720. In 720 applets are defined in /etc/control-panel-applets and $HOME/.fatdog/control-panel-applets, and in files inside /etc/control-panel-applets.dir and $HOME/.fatdog/control-panel-applets.dir. This is a very flexible, albeit redundant, system that probably aims at being backwards-compatible. Could it be replaced by static links? Probably, but it would be new code for an existing function that isn't broken, so the motivation to do it would be low, I think.
In my informal testing on my hardware, the applet-loading phase takes about 50% of the perceived control panel start time. That is a lot. Interaction with the control panel, once it's running, also feels slow to me. And sometimes double-click are lost on an applet icon.
In the past, forum members offered a couple of alternatives to the Fatdog control panel. Smokey's menu comes to mind (search the forum). If you like that kind of approach - a menu based system - you could take a look at my own script, gmenu2-fdcp in my repo. I takes 152 msec to load the applets on a Core Duo PC.

Anniekin wrote:Fatdog control panel is too slow!

Why does it have to load applets?

Why not just make them static links

In my opinion, since I didn't write Fatdog control panel, loading applets makes the panel extensible and customizable. For instance, the optional nvidia driver package for Fatdog-720 adds the nvidia control panel applet to Fatdog control panel.
I think the script changed a bit between Fatdog-710 and 720. In 720 applets are defined in /etc/control-panel-applets and $HOME/.fatdog/control-panel-applets, and in files inside /etc/control-panel-applets.dir and $HOME/.fatdog/control-panel-applets.dir. This is a very flexible, albeit redundant, system that probably aims at being backwards-compatible. Could it be replaced by static links? Probably, but it would be new code for an existing function that isn't broken, so the motivation to do it would be low, I think.
In my informal testing on my hardware, the applet-loading phase takes about 50% of the perceived control panel start time. That is a lot. Interaction with the control panel, once it's running, also feels slow to me. And sometimes double-clicks are lost on an applet icon.
In the past, forum members offered a couple of alternatives to the Fatdog control panel. Smokey's menu comes to mind (search the forum). If you like that kind of approach - a menu based system - you could take a look at my own script, gmenu2-fdcp in my repo. It takes 152 msec to load the control panel applets on a Core Duo PC.

I too avoid using the control panel, because of speed issues!
A quick and convenient way to access any application with .desktop file . By creating alternative directories with required desktop files (maybe links will work) provides a faster mechanism.