(old)Puppy Linux Discussion Forum

Minor bug -- firewall applet is stubborn and will not be removed.

Right-click, "Quit&Remove Firewall Status" --> still there next boot.
Right-click, "Firewall On/Off/Remove" --> "Remove" button --> still there next boot.

starhawk wrote:Minor bug -- firewall applet is stubborn and will not be removed.

Right-click, "Quit&Remove Firewall Status" --> still there next boot.
Right-click, "Firewall On/Off/Remove" --> "Remove" button --> still there next boot.

Ya, your right. I had a quick look at the source (if it's the right one) and it looks correct as far as I can tell. "Quit&Remove Firewall Status" should remove /root/.config/autostart/firewallstaterun.desktop.

Edit: Firewallstate is a mess, the binary doesn't remove the .desktop and re-starting it doesn't re-make the .desktop

I assume that manually removing the *.desktop, wherever it is (/usr/share/applications...?) is sufficient to make the tray icon go bye-bye...?

starhawk wrote:I assume that manually removing the *.desktop, wherever it is (/usr/share/applications...?) is sufficient to make the tray icon go bye-bye...?

I'm in 3.1n right now so I can't doublecheck, but it should be in /root/.config/autostart and Control Panel>system>boot manager> manage startup applications renames it there and removes it on a restart for me.

Disabled in BootMgr, we'll see what happens next reboot...

EFI BOOT FOR X-TAHR AS IN PORTEUS

IT IS VERY SIMPLE.

SYMBOLIC LINKS ARE BROKEN.

REGARDS.

Marv wrote:

starhawk wrote:I assume that manually removing the *.desktop, wherever it is (/usr/share/applications...?) is sufficient to make the tray icon go bye-bye...?

I'm in 3.1n right now so I can't doublecheck, but it should be in /root/.config/autostart and Control Panel>system>boot manager> manage startup applications renames it there and removes it on a restart for me.

Works for me...

Just wanted to report that I haven't had any trouble since my last post in this thread.

rg, I think it's safe to renumber this one as a release... works great, no complaint!

IS THERE ANY XFCE WEATHER PLUGIN
FOR X-TAHR THAT CAN WORKS?

THANKS.

zagreb999 wrote:IS THERE ANY XFCE WEATHER PLUGIN
FOR X-TAHR THAT CAN WORKS?

THANKS.

http://smokey01.com/rg66/X-tahr/pet_pac ... -0.8.5.pet
http://smokey01.com/rg66/X-tahr/pet_pac ... -0.8.5.pet

THANKS,
BUT THIS ONE DOES NOT WORK!!!

zagreb999 wrote:THANKS,
BUT THIS ONE DOES NOT WORK!!!

Works ok for me, maybe you need to change your search terminology.

zagreb999 - Also, make sure your system's time zone is set correctly to your exact location. If not, the Weather Plugin will fail as in your screenshot.

Bob

This is great news to me, I am having lots of problem with regular tahrpup and I run xfce. Will there be a release with the Pae kernel soon? All my machines have more than 4gb of ram.

Thanks,

Steven

haywirepc wrote:This is great news to me, I am having lots of problem with regular tahrpup and I run xfce. Will there be a release with the Pae kernel soon? All my machines have more than 4gb of ram.

Thanks,

Steven

Eventually, depending on my motivation. If you're running a frugal install, you can replace Non-PAE with a PAE zdrive and vmlinuz.

http://distro.ibiblio.org/puppylinux/huge_kernels/

Not so sure how to do that I guess I will have to wait for a pae version...


Hope you are feeling motivated.


This looks great, and I am trying to build a new system to use on all my workstations, most still running puppy linux lucid.

And TahrPUP-605 with fixes. I am probably wrong but isnt WOOFCE distros being built for 32bit PCs with @Shinobar's Intel fix included. @Shinobar's exposure of hidden Intel feature allows PAE distros to run on those few eeePCs with that crippled chip. Thus, enabling almost every PC since 1995 to run any PAE distro.

FYI only

haywirepc wrote:Not so sure how to do that I guess I will have to wait for a pae version...

Dowload, as an example, huge-3.14.20-tahr_PAE.tar.bz2 from the link posted above. Extract the contents, rename kernel-modules.sfs-3.14.20-whatever-it's-called to zdrv_tahr_6.0.2.sfs. Rename vmlinuz-3.14.20-whatever to vmlinuz. Rename, move, or delete original zdrv and vmlinuz and copy the new ones to your frugal directory. Reboot and cross your fingers, best done without a previous save.

gcmartin wrote:And TahrPUP-605 with fixes. I am probably wrong but isnt WOOFCE distros being built for 32bit PCs with @Shinobar's Intel fix included. @Shinobar's exposure of hidden Intel feature allows PAE distros to run on those few eeePCs with that crippled chip. Thus, enabling almost every PC since 1995 to run any PAE distro.

FYI only

Not sure, but it would be nice if Pentium-M could boot PAE with force-pae.

Hi @RG66

rg66 wrote:Not sure, but it would be nice if Pentium-M could boot PAE with force-pae.

The one I had responded just as @Shinobar predicts. Others tested as well, IIRC. Remember, Intel did not manufacture it out. They just hid the bit and sold it to PC producers as a cheaper version. @Shinobar shows use a solution that exposes it so that any PAE distro will boot whether the PC is Pentium-M or not.

Think this is a pathway for universal 32bit x86 use, if you choose.