Puppy Linux Discussion Forum

Me too. I also vote to hang onto Python.....because you just never know when it'll be needed. And if the base install is there, it's easy enough to add-in modules, plugins, bindings, etc., as and when. I don't especially like it any more than anyone else does, but - as has been said - you simply cannot completely avoid it.

And "Yes" to gufw, too. There's got to be a reason why it's pretty much universal across the Linux eco-system. It's only a front-end to ufw, after all.....which itself is a kind of 'abbreviated' lighter 'take' on iptables, when all's said & done.

Mike.

The cool thing is iptables is already installed. Any thoughts?

Does the original Puppy firewall use iptables behind the scenes? If it does, Bill's 'PeasyFirewallMonitor' uses a simple GUI to basically turn it on or off, and set it to either auto-start or not, as the user chooses.

https://oldforum.puppylinux.com/viewtopic.php?p=742273

It's pretty straight-forward to use. It might be worth investigating to see if it would work with "Airedale"..?

Just a thought....

Mike.

@mikewalsh While having some real fun running @peebee's VoidPup64, I noticed the firewall GUI is a front end for iptables.

I am looking at borrowing it and testing it out.

alpha9.7 is ready!
It is here -> https://rockedge.org/kernels

I'll make a link in the morning! The iptables GUI from Puppy is NOT yet in place.

fstrim used to trim SSD drives in Linux
viewtopic.php?t=4894

fstrim is already in KLV-Airedale and it can be run from a terminal command.

root# fstrim -h

Usage:
fstrim [options] <mount point>

Discard unused blocks on a mounted filesystem.

Options:
-a, --all trim mounted filesystems
-A, --fstab trim filesystems from /etc/fstab
-I, --listed-in <list> trim filesystems listed in specified files
-o, --offset <num> the offset in bytes to start discarding from
-l, --length <num> the number of bytes to discard
-m, --minimum <num> the minimum extent length to discard
-v, --verbose print number of discarded bytes
--quiet-unsupported suppress error messages if trim unsupported
-n, --dry-run does everything, but trim

-h, --help display this help
-V, --version display version

Arguments:
<num> arguments may be followed by the suffixes for
GiB, TiB, PiB, EiB, ZiB, and YiB (the "iB" is optional)

For more details see fstrim(8).
root#

Puppy now has a GUI program for running fstrim.
viewtopic.php?t=4907

wonder if this GUI program could be added to KLV-Airedale?

@bigpup :-

Give me time, mate. It's on my 'to-do' list.....honest! It should mostly just need the terminal stuff modifying to use the XFCE terminal; I've already got a 'template' for that in the modified DriveSpeed! I put together for "Airedale" the other day.

Some of us DO have a life outside the forum that sometimes has to take priority, y'know? Bear with me.

Mike.

mikewalsh wrote: Fri Jan 21, 2022 11:30 am

@bigpup :-

Give me time, mate. It's on my 'to-do' list.....honest! It should mostly just need the terminal stuff modifying to use the XFCE terminal; I've already got a 'template' for that in the modified DriveSpeed! I put together for "Airedale" the other day.

Some of us DO have a life outside the forum that sometimes has to take priority, y'know? Bear with me.

Mike.

Hi Mike, I don't think anyone is trying to make you rush ! So take your time (time was invented to make use of ).
About the terminal, I just noticed that "mrxvt" is installed (anyway in alpha9.7), perhaps more suitable for your purpose.
(and also "xterm" is installed, btw)

@fredx181 :-

Morning, Fred! Can I pick your brains about something..?

'Partprobe'. Is this a Puppy-specific item, or is it generally available? Mistfire's re-write of the mount/unmount scripts uses it in the Puppy version, so as to give a dynamic list of what's there as opposed to the static list list of block devices I initially used.(But you know all about 'partprobe', I strongly suspect).

Nope; scratch that. I see Void has it anyway.....or at least KLV does. I didn't know we were using Busybox here, too..? Hm...

'Kay. Ought to be fairly straight-forward, then. (Famous last words..!!)

Mike.

@mikewalsh
Hi Mike, could it be that you meant "probepart" ? ("partprobe" doesn't do much I think)
Anyway it's part of the "gparted_shell" package: viewtopic.php?p=46539#p46539
@rockedge You didn't like to include "gparted_shell" perhaps ?

Huh. "Famous last words", indeed...

Somebody with more skill than I will need to take a look at the cb_mount.sh & cb_umount.sh scripts if this is going to work in "Airedale". The problem centres around the fact that Void mounts things in a totally different way to Puppy.

In Puppy, you 'mount' a device into the file-tree at /mnt. In Void, it wants to be mounted at /run/media/root/LABEL (not 'block' device). Mistfire's scripting is beyond my comprehension ATM, since it's employing 'sed', 'awk', 'print', etc, none of which I yet even understand, never mind know how to use.

Like I said, you've gotta learn to walk before you can run. In this respect, I'm barely a toddler still crawling around on the floor..!

Sorry, @bigpup ..! I don't mind admitting when things are beyond my ability.

Mike.

Hi Mike, see below attached cb_mount.sh, it has different way of detecting partitions (DEVLIST=....)
Not really sure, but I guess it won't be a problem mounting under /mnt , and if it's already mounted on /run/media/.../... , it will just be mounted too on /mnt .
In the script "fstrim.sh" I changed to (using mrxvt):
mrxvt -title ' ~ TRIM command output....please be patient. May take a while...' -background '#ffff80' -geometry '80x6' -hold -e fstrim -av
And seems to work OK, but I don't know anything about the program so cannot be sure.

EDIT: cb_umount.sh can stay the same IMO.

fredx181 wrote:

You didn't like to include "gparted_shell" perhaps ?

I will look at it today! If it isn't now it will be then. gparted_shell should be included, thanks for catching that it might be missing.

Update: something like gparted_shell does not look like it exists as such in Void Linux repos

rockedge wrote: Fri Jan 21, 2022 4:29 pm

fredx181 wrote:

You didn't like to include "gparted_shell" perhaps ?

I will look at it today! If it isn't now it will be then. gparted_shell should be included, thanks for catching that it might be missing.

Update: something like gparted_shell does not look like it exists as such in Void Linux repos

It's a self-made package, took some scripts from Puppy viewtopic.php?p=46539#p46539

Ah; OK. Thanks, Fred.

I'll take a look at it later this evening, when I'm back in "Airedale" again.

The issue I had was that nothing was showing up in the combobox for the cb_mount.sh. There WAS a list showing for cb_umount.sh, although I wasn't sure if it was actually doing what it was supposed to.

I never got as far as running TRIM, so I'll see what happens later on. I'll keep y'all posted.

Mike.

I uploaded a new copy of the alpha9.7 ISO !!!

This version has the gparted_shells package from @fredx181 included. Just swap in the 07KLV-airedale_rootfs.sfs file into existing setups. Should work as expected.

Some of us DO have a life outside the forum that sometimes has to take priority, y'know?

This is KLV-Airedale!
You are not allowed to have a outside life, while it is in alpha stage of development.

rockedge wrote: Fri Jan 21, 2022 7:30 pm

I uploaded a new copy of the alpha9.7 ISO !!!

This version has the gparted_shells package from @fredx181 included. Just swap in the 07KLV-airedale_rootfs.sfs file into existing setups. Should work as expected.

You also need to delete the old upper_changes directory, so you are not using old save stuff.
I was having issues until I did this.
I am trying ideas, so no telling what I had in the upper_changes directory, causing issues.
Boots OK after starting out clean.

bigpup wrote: Sat Jan 22, 2022 4:04 am

rockedge wrote: Fri Jan 21, 2022 7:30 pm

I uploaded a new copy of the alpha9.7 ISO !!!

This version has the gparted_shells package from @fredx181 included. Just swap in the 07KLV-airedale_rootfs.sfs file into existing setups. Should work as expected.

You also need to delete the old upper_changes directory, so you are not using old save stuff.
I was having issues until I did this.
I am trying ideas, so no telling what I had in the upper_changes directory, causing issues.
Boots OK after starting out clean.

Well, I think what @rockedge is trying to say is that this change is so small compared to previous ISO that it should work to just swap in the 07KLV-airedale_rootfs.sfs (and keep upper_changes).

Hi All, attached package will install more Thunar Custom Actions for:

Load SFS
Unload SFS
Create SFS (similar to dir2sfs)
Graphical Disk Map (gdmap is dependency)
Convert to animated gif (convert video file to .gif)
Create xbps package (dir2xbps <directory>)
File Mount (iso sfs squashfs 4fs ...) (mount and show in Thunar)

@fredx181 :-

Damn, but you ARE a "busy beaver", ain't ya?

Just to report it all works beautifully, Fred.....and that's a nice touch, adding the 'Convert to GIF' entry to the context menu. That's something I appreciate, anyway. As we say in Yorkshire....."Ta very much, lad"!

Mike.

Thanks Mike !
Yeah, been studying the past week how to add Thunar custom actions (best way ?) (much inspired by the "pinstall" code from Uextract .pet, so credit goes also to @JakeSFR (and perhaps others too)).
Getting some routine in it now, so if there are any suggestions for more ... ...

For Rox, similar actions can be set up, but perhaps someone else can do that, I'm not motivated enough as I don't really like Rox.

Uploaded alpha9.8 which includes fredx181's add in menu functions for Thunar.

Will have to look in to adding the same features for ROX. That would be optimal to have them available.

I tend to use both Rox and Thunar together at times.

ISO file v9.8 downloaded to /BOOTISOS on USBs and tested. ISO file boots without issues. Same tests for boots, mimimal subsystem tests, and shutdown without issues. Same ISO file tests of this KLV as was reported on WoofCE VoidPUP64 thread.

Thanks @rockedge

@rockedge :-

I think I'll give v9.8 a miss, Erik. I've just upgraded to v9.7, then installed Fred's package, so.....I guess I'm already there, huh?

(*shrug...*)

Mike.

@mikewalsh your version is already there. In principle you're running exactly what alpha9.8 has. End verdict....no worries.

I am customizing one as well on the side. Once a beta is out I can do some more experimenting.

fredx181,

thanks for those Thunar Custom Actions!!

Those are all stuff I was wishing could be in Thunar.

I am wondering, if some of your stuff, would be something the Void Linux developers, would like to have in Void.

Well, really a lot of what is being developed by everyone, working on stuff, for this KLV-Airedale OS.

bigpup wrote:

fredx181,

thanks for those Thunar Custom Actions!!

Those are all stuff I was wishing could be in Thunar.

You're welcome ! Now..., am I allowed to have outside life for one day ?
------------------------------------------------------------------------------------------------------------------------
Here's for who hates the "root warning" in Thunar as much as I do, attached thunar that I compiled sometime ago without it (is slightly older version, but works ok for me on KLV).
Extract and copy it to /usr/bin, replacing the existing thunar.
But.. need to quit thunar first thunar -q and use rox to do the copying.
Not the best solution, I guess, as it can be overwritten when upgrading thunar with the package manager.

EDIT: Or perhaps better, copy it to /usr/local/bin, but then the symlink "Thunar" (with capital T) should be there too:
So, then also, do in terminal: cp -a /usr/bin/Thunar /usr/local/bin/

FYI I do:

#patch thunar
./bbe -e 's/Warning: you are using the root account. You may harm your system./                                                                  /' ${FINALSFS}/usr/bin/thunar > thunarpatched
chmod 755 thunarpatched
mv -f thunarpatched ${FINALSFS}/usr/bin/thunar

My latest desktop idea.
.

.
Anyone know how to change the font colors on the desktop?
.
.
.