Blinking Red Storage Space Warning [Solved]

[mikewalsh]

@Sky Aisling :-

No, you're fine right there. The further outside the 'save', the better.

Some newer Puppies call this /initrd/mnt/dev_save, which is the name for this particular 'layer' in the aufs 'layering' file-system Puppies use. It's more commonly known as /mnt/home.....and is the perfect place to put stuff like this.

You CAN put it inside the Puppy sub-directory if you wish, but I would stick with the location as displayed here. This way, if you decide to add a second Puppy - and intend to use the same browsers - the profiles and cache contents can often be 'shared' between Puppies.

It's kind of like the same effect as 'sync-ing' between browsers using their built-in cloud sync tools.....except that this way, your data remains purely local, and under your control.

----------------------------------------

BTW, with regard to your idea of putting 'restart-X' into /root/Startup.......DON'T!

I came up with the 'brilliant' idea of doing just this in an attempt to resolve something different a few years ago.....not realising that it puts the machine into a 'loop' of constantly restarting "X" over & over again. Reason being that running the contents of /root/Startup is one of the first steps after restarting "X" itself, so, y'know.....go figure!

It's NOT a good idea.

Mike.

[amethyst]

@amethyst
Good Morning,

Yesterday I moved the mozilla and moonchild productions that were inside .cache directory in ~(All, Thumbs) to sda1. I made absolute links in ~(All, Thumbs) .cache back to sda1 directories mozilla and moonchild.
Today I moved mozilla and moonchild back to .cache ~(All, Thumbs) after I deleted the links.
Now everything is back to before any moves to sda1 were made.

So, you are suggesting I move the entire .cache directory that is in ~(All, Thumbs) that contains mozilla and moonchild Productions to sda1 and NOT .mozilla and .moonchild productions that are NOT inside the .cache directory?
I am to leave .mozilla and .moonchild directories alone?
Sky

Move and symlink all of them (in other words /root/.cache which includes mozilla and moonchild productions). The latter are the browser cache files AND /root/.mozilla and /root/.moonchild productions. The last two are different folders (notice the . in the name) and contains the browser profile files.

[Sky Aisling]

@mikewalsh

The moves of /root/.cache/mozilla & /root/.cache/moonchild productions to Browser Declutter RAM/Cache worked with no issue.
The relative link back to /root/.cache/mozilla & /root/.cache/moonchild productions worked with no issue.

The moves of /root/.mozilla & /root/.moonchild productions from /root do not show in Browser Declutter RAM/Profiles.
.Mozilla still shows in /root/.
But, when I attempt a second 'move' of .mozilla from root to Profiles the message says it's already in Profiles and do I want to overwrite?
Where to go from here? There is nothing in Profiles to grab and drag back to root and link.

[Sky Aisling]

@mikewalsh
PS
I am testing access to browsers now.
Firefox0esr is no longer in the form that I knew it. I'm not able to use it.
But, Palemoon appears to be responding normally. However, I'll need to set it up with my all my preferences. I am using it now to communicate with the forum.
EDIT: I spoke to soon. Palemoon is not running well. So far I am able to get to my email and the forum but that's about it.
Sky

[Sky Aisling]

@mikewalsh
Hold on! I was able to locate the lost files in Browser Declutter RAM/Profiles.
I had not selected the 'eye' which displays all of the files in Profiles.
Firefox0esr appears to be back. I will go test now.

Wow! take a look at the Graphical Disk Map. Root is now a 7.45MiB. That should give RAM some room to maneuver?
Can I do the same moves with Mesa_Shader? I like this.
There is only one issue left. The Blinking Red Icon is back.

[snoring_cat]

Sky,

Can you please post the output of the long command I posted earlier. It will really help in deducing your actual problem. All of your efforts have been only focusing on Cache and Browser files. That command will show what actually is hogging your system.

After running the above, running save2flash might clear up yor red blinking icon. If so, please re-run the above command and post that output as well.

[bigpup]

I am starting to wonder if you have some program running that has a memory leak.

Are you running any other program than a browser?

This is only happening with only the browser running?
For sure, no other program, also running?

[Feek]

Are you running any other program than a browser?

If I'm not wrong, there is an icon of Zoom on the picture in the first Sky's post next to the red blinking icon.

I don't use Zoom, but several times used Teams (under Bionicpup64) for some work meeting. It was electron-based app. It worked nicely but it ate quite much ram (much more than e.g. playing video in a browser).

[Sky Aisling]

@snoring_cat
I sure wish terminal would accept a paste from a copy.
I managed to type all the coding you suggest, however, it is obvious I made a typo in the string somewhere.
Couldn't I get much of this info by using Pup-Sysinfo inquires? using gui?

echo terminal input1.png (80.98 KiB) Viewed 882 times

@bigpup
only browser firefox 78.50esr (64 bit) running
See Pup-Sysinfo screen shot below

@Feek
only browser firefox 78.50esr (64 bit) running
See Pup-Sysinfo screen shot below
Yes, ZOOM is suspicious to me too.
I can't remember when the blinking light started - before or after I installed ZOOM.
ZOOM .cache is taking up 3.58MiB of root according to GDmap.
___________________________________________________
All -
Here are the times and detail of my various installs to set up this Puppy on this Dell machine:

installed printer 12-4-21
viewtopic.php?p=43509#p43509

zoom installed 12-16-21
viewtopic.php?p=44521#p44521

began post 'blinking red icon' 12-16-21
viewtopic.php?t=4740

Are we sure this setup doesn't need a swap file?

Pup-Sys info1.png (104.47 KiB) Viewed 882 times

[Sky Aisling]

A quick question...
What module or piece of coding inserts the blinking icon?
There must be a switch that triggers the blinking icon.
That switch must point back to a condition that causes the switch to turn on the blinking icon.
Can't the problem be traced back by examining the blinking switch code?

Just wondering...Assuming Puppy is written in C or C++...a language not in my job description as an everyday user.

Sky

[williams2]

sure wish terminal would accept a paste from a copy

To copy text, just select the text with the mouse.

To paste in urxvt:

middle click (click the mouse wheel)
or press shift+insert

To paste from the clipboard buffer (that was copied with ctrl+c)
press ctrl+alt+v

If you have clipit running press ctrl+alt+p
chosing text from the menu will copy the text to both the primary and clipboard buffers
so both methods of pasting will work.

[Sky Aisling]

@williams2 @snoring_cat @mikewalsh @bigpup

Thank you, williams2. The middle roller on the mouse did the trick to paste script to terminal.
The query generated 5 screenshots worth of information.
I have them stored but it will take up a huge amount of room in this thread.
Do you all want me to post all that information?

I must go and get my daily life taken care of now. I will check back in probably tonight.
PS - Ever since we put the browser data in sda1, Puppy is running well.
When the blinking red icon shows up all I have to do is right click and 'quit'.
The icon goes away and Puppy runs fine as far as I've tested so far.
Sky

[snoring_cat]

Sky,

In your Terminal window with the output, if you drag over all of the text and highlight it, it will be available for pasting via middle-clicking. Please highlight all of the text at once. Terminal will auto-scroll as needed when mouse-dragging to highlight. Then in this forum, reply to this thread and middle-click to paste what you have highlighted in Terminal.

Highlighting to copy-paste is a nice trick to keep in your arsenal of Linux tricks. It will save you having to do screenshots and attachments.

[Sky Aisling]

@snoring_cat
A CLUE: The blinking icon appears to show up immediately after the first automatic save after the desktop is brought up.
EDIT: Yes, I've tested this some more. The blinking red icon shows up immediately after the first auto save after first bootup of the day. The fan kicks on strong.

This terminal information was taken as the blinking icon was blinking:

root# echo ---- tmpfs ---- ; du -shc /initrd/mnt/tmpfs/* | sort -h ; echo ---- tmp ---- ; du -shc /initrd/mnt/tmpfs/tmp/* | sort -h | tail -15 ; echo ---- pup_rw ---- ; du -shc /initrd/mnt/tmpfs/pup_rw/* | sort -h | tail -15 ; echo ---- root ---- ; du -ah /initrd/mnt/tmpfs/pup_rw/root/ | sort -h | tail -15; free -h ; echo ---- CPU ---- ; ps aux | sort -nrk 3,3 | head -n 5 ; echo ---- disk space --- ; df -h ; echo ---- mounts ---- ; mount ; grep DISTRO_NAME /etc/DISTRO_SPEC
---- tmpfs ----
420K /initrd/mnt/tmpfs/tmp
2.5M /initrd/mnt/tmpfs/pup_rw
57M /initrd/mnt/tmpfs/zdrv_bionicpup64_8.0.sfs
279M /initrd/mnt/tmpfs/puppy_bionicpup64_8.0.sfs
339M total
---- tmp ----
4.0K /initrd/mnt/tmpfs/tmp/bootsysinit.log
4.0K /initrd/mnt/tmpfs/tmp/gtkdialog-splash_gtkrc
4.0K /initrd/mnt/tmpfs/tmp/pup_event_backend
4.0K /initrd/mnt/tmpfs/tmp/PuppyPin
4.0K /initrd/mnt/tmpfs/tmp/retrovol.pid
4.0K /initrd/mnt/tmpfs/tmp/sns_interface_success
4.0K /initrd/mnt/tmpfs/tmp/xerrs.log
8.0K /initrd/mnt/tmpfs/tmp/sfs_load
12K /initrd/mnt/tmpfs/tmp/cups
20K /initrd/mnt/tmpfs/tmp/services
24K /initrd/mnt/tmpfs/tmp/pup_event_frontend
24K /initrd/mnt/tmpfs/tmp/udevtrace.log
44K /initrd/mnt/tmpfs/tmp/bootkernel.log
256K /initrd/mnt/tmpfs/tmp/udev
416K total
---- pup_rw ----
0 /initrd/mnt/tmpfs/pup_rw/dev
0 /initrd/mnt/tmpfs/pup_rw/etc
0 /initrd/mnt/tmpfs/pup_rw/initrd
0 /initrd/mnt/tmpfs/pup_rw/lib
0 /initrd/mnt/tmpfs/pup_rw/mnt
0 /initrd/mnt/tmpfs/pup_rw/sys
0 /initrd/mnt/tmpfs/pup_rw/tmp
0 /initrd/mnt/tmpfs/pup_rw/usr
96K /initrd/mnt/tmpfs/pup_rw/var
2.4M /initrd/mnt/tmpfs/pup_rw/root
2.5M total
---- root ----
12K /initrd/mnt/tmpfs/pup_rw/root/.thumbnails/normal/bc2bdddeb0106bc9e61317455346e2fb.png
12K /initrd/mnt/tmpfs/pup_rw/root/.thumbnails/normal/bdddce5998ee6ac5badd80d3c8b16acb.png
12K /initrd/mnt/tmpfs/pup_rw/root/.thumbnails/normal/c67c82a6d0063f61413473269f7d9e29.png
16K /initrd/mnt/tmpfs/pup_rw/root/.thumbnails/normal/19d9077be14de8856bcf91d7fc8cd32f.png
16K /initrd/mnt/tmpfs/pup_rw/root/.thumbnails/normal/3f041bf2874601785d8938989a314456.png
16K /initrd/mnt/tmpfs/pup_rw/root/.thumbnails/normal/551b65a43f55fb1a36b980d60b9fc433.png
20K /initrd/mnt/tmpfs/pup_rw/root/.thumbnails/normal/9d9e44eb1d4905bc5d143c8f9ff8ad4e.png
20K /initrd/mnt/tmpfs/pup_rw/root/.thumbnails/normal/d6e30842f62aced60133a8b98bdf0e82.png
56K /initrd/mnt/tmpfs/pup_rw/root/.local
56K /initrd/mnt/tmpfs/pup_rw/root/.local/share
56K /initrd/mnt/tmpfs/pup_rw/root/.local/share/recently-used.xbel
156K /initrd/mnt/tmpfs/pup_rw/root/.thumbnails
156K /initrd/mnt/tmpfs/pup_rw/root/.thumbnails/normal
2.2M /initrd/mnt/tmpfs/pup_rw/root/echo-1.png
2.4M /initrd/mnt/tmpfs/pup_rw/root/
total used free shared buff/cache available
Mem: 5.6G 160M 4.4G 390M 1.0G 4.7G
Swap: 0B 0B 0B
---- CPU ----
root 4863 4.6 0.7 476160 42556 tty4 S<sl+ 21:31 0:10 /usr/lib/xorg/Xorg :0 -br -nolisten tcp
root 6162 1.7 0.5 310080 33992 tty1 Sl 21:32 0:02 geany /root/Blinking Response4
root 4872 1.7 0.3 179940 22764 tty1 S 21:31 0:04 jwm
root 6216 0.7 0.2 124928 17560 ? Ss 21:32 0:00 urxvt
root 5208 0.7 0.0 71800 5756 ? Ss 21:31 0:01 compton --config /root/.config/compton.conf -b --logpath /tmp/compton.log
---- disk space ---
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 4.9G 2.1G 2.6G 44% /initrd/mnt/dev_save
tmpfs 2.9G 341M 2.5G 12% /initrd/mnt/tmpfs
unionfs 2.9G 341M 2.5G 12% /
/dev/loop0 279M 279M 0 100% /initrd/pup_ro2
/dev/loop1 57M 57M 0 100% /initrd/pup_z
tmpfs 5.3M 4.8M 512K 91% /initrd/files
devtmpfs 2.9G 0 2.9G 0% /dev
shmfs 1.3G 0 1.3G 0% /dev/shm
/dev/loop2 161M 161M 0 100% /initrd/pup_ro3
/dev/loop3 220M 220M 0 100% /initrd/pup_ro4
/dev/sda2 9.2G 2.6G 6.1G 30% /mnt/sda2
---- mounts ----
/dev/sda1 on /initrd/mnt/dev_save type ext4 (rw,relatime)
tmpfs on /initrd/mnt/tmpfs type tmpfs (rw,relatime)
unionfs on / type aufs (rw,relatime,si=5cbeff72baadb08f)
/dev/loop0 on /initrd/pup_ro2 type squashfs (ro,noatime)
/dev/loop1 on /initrd/pup_z type squashfs (ro,noatime)
tmpfs on /initrd/files type tmpfs (ro,relatime,size=5404k,mode=755)
devtmpfs on /dev type devtmpfs (rw,relatime,size=2946432k,nr_inodes=736608,mode=755)
none on /proc type proc (rw,relatime)
none on /dev/pts type devpts (rw,relatime,gid=2,mode=620,ptmxmode=000)
none on /sys type sysfs (rw,relatime)
shmfs on /dev/shm type tmpfs (rw,relatime,size=1282952k)
/dev/loop2 on /initrd/pup_ro3 type squashfs (ro,noatime)
/dev/loop3 on /initrd/pup_ro4 type squashfs (ro,noatime)
/dev/sda2 on /mnt/sda2 type ext4 (rw,relatime)
grep: /etc/DISTRO_SPEC: No such file or directory
root#

[amethyst]

@Sky Aisling

I notice you haven't changed the boot parameter to pfix=nocopy as suggested before. You can save another 336MB of RAM doing this.

[Sky Aisling]

@amethyst
Remind me again how to set the parameters. It's been years since I set parameters. Thank you,
Sky

[amethyst]

@amethyst
Remind me again how to set the parameters. It's been years since I set parameters. Thank you,
Sky

Change that line in your boot loader's configuration file (edit the file). For grub4dos this is menu.lst and for grub it's grub.cfg

[Sky Aisling]

@amethyst
Good Morning!
amethyst writes:

I notice you haven't changed the boot parameter to pfix=nocopy as suggested before. You can save another 336MB of RAM doing this.

I added no-copy to the boot parameters.
Is this the correct format?

kernel /bionicpup6480uefi/vmlinuz psubdir=/bionicpup6480uefi pmedia=usbflash pfix=fsck, pfix=nocopy

Sky

[amethyst]

@amethyst
Good Morning!
amethyst writes:

I notice you haven't changed the boot parameter to pfix=nocopy as suggested before. You can save another 336MB of RAM doing this.

I added no-copy to the boot parameters.
Is this the correct format?

kernel /bionicpup6480uefi/vmlinuz psubdir=/bionicpup6480uefi pmedia=usbflash pfix=fsck, pfix=nocopy

Sky

pfix=fsck,nocopy

[Sky Aisling]

@amethyst
Thank you, corrected:
kernel /bionicpup6480uefi/vmlinuz psubdir=/bionicpup6480uefi pmedia=usbflash pfix=fsck,nocopy

[Sky Aisling]

Good Morning All -

This morning I removed the two RAM chips from the machine. I 'cleaned' the insert keys off with rubbing alcohol and re-inserted the RAM chips. The chips are firmly and correctly re-set. I'm considering upgrading the RAM to 8GB.

Sky

[amethyst]

Hi - You have enough RAM and you have done what you can to actually limit RAM usage at startup. I haven't read the whole thread but if the blinking of the icon does not affect the performance otherwise, why should you worry about it? Your initial RAM readings looks in order to me. The blinking of the icon may just be some application issue and actually have nothing to do with the RAM usage at all. I'm running Bionic 32 on an old machine with 2gb ram and without a swap file. I'm taking a guess here and reckon this isssue has something to do with something corrupt in your savefolder. Run a clean install of Puppy without savefolder (easy way is to rename your existing savefolder temporarily to something obscure before reboot so that it is not in operation) and see if you encounter the same problem.

[Sky Aisling]

@amethyst

amethyst writes:

Run a clean install of Puppy without savefolder (easy way is to rename your existing savefolder temporarily to something obscure before reboot so that it is not in operation) and see if you encounter the same problem.

Yes, I intend to do that. I've had to scramble to get this backup machine set up which except for the blinking icon is performing well considering it's vintage. I might consider making this Dell my main machine. The placing of the gnarly Firefox away from root is helping so much.

In-the-meantime, back to the ruddy blinking icon.

I share your hunch that:

The blinking of the icon may just be some application issue and actually have nothing to do with the RAM usage at all.

I would like to eliminate the icon app all together from the JWM tray. (The blinking thing can blink all it wants in a nice dark corner of the system.) Then I wouldn't have to go through the energy to reset Puppy from scratch.
JWM desktop allows me to set up various apps in both tray1 and tray2.
However, I have yet to find how I can influence the right-hand side of Tray1, the side with the sound, connection, battery, firewall, clipboard, date/time apps.
I know how to 'quit' the apps in this section, but, not how to delete or add an app.

Is there a way I can get to the lower-right section of the bottom tray to add/delete apps from it?

[Phoenix]

If you wish to remove the storage icon, it is called freememapplet in Boot Manager > Startup Apps
You can either move them to disabled apps section, or entirely delete them altogether.

[Sky Aisling]

@Phoenix
Yes! Thank you, Phoenix
The blinking red icon is gone! I did a 'minus'. I did not 'delete'.

That was so simple. I think I can now put 'SOLVED' at least for the time being on this thread. You all and I can get back to our other lives outside of this wonderful Puppy Forum. I appreciate this forum and it's members so much.

If anyone sees anything I've missed, please let me know before I sign off this thread.

Sky

[Sky Aisling]

@mikewalsh

Hi Mike,
I have a quick question about one of your nifty solutions to reduce the Firefox browser cache.
viewtopic.php?p=44917&sid=63031fee9a556 ... 6da#p44917
In this thread you taught me how to move the Firefox cache to outside of the savefile area.
I applied the method to Bionicpup(64) 8.0 on an old Dell laptop and it has worked perfectly ever since.
I now have a 'new' machine and a 'new' Puppy that is having the same issue with the Firefox cache.
Firefox is version 115.0.2 (64).
The machine is a HP desktop 260-a010 with hard drive. The BIOS release date is 05/22/2017.
The distro is:

▶—— Distro Specifications ——◀

Operating System:
Distro Name fossapup64 9.6 (x86_64)
Woof-CE Build testing;cd5dcd04f;2023-01-21 15:35:41 +0200
Woof Version 9
Binary Base ubuntu
Distro Base focal
Distro Date Feb 2023
User Session x11
Window Manager JWM v2.4.3
Desktop Start xwin jwm

The fossapup64 9.6 is frugally installed on a SanDisk flash drive. My private files are stored on the hard drive.

Can I use this same method on fossapup64 9.6? and this machine?
If so, then which partition do I place the directory to accept mozzilla and .mozzilla files?

Firefox cache1.png (25.03 KiB) Viewed 777 times

Firefox cache2.png (22.11 KiB) Viewed 777 times

Firefox cache3.png (43.34 KiB) Viewed 777 times

Thank you in advance,

Sky

PS - I've tried using the .sfs version of this solution without much luck. I'd prefer to use your above method unless there is some significant reason not too.

[mikewalsh]

@Sky Aisling :-

The same techique will work anywhere, at any time, for any Puppy. At heart, it relies on the ease with which ROX-filer will let you create sym-links; although it's something most Linux distros will let you do, I've never come across another file manager that lets you do things quite so quickly & easily as ROX.

Okay. As to "where", well.....you've got a choice here. IF you're going to always keep this flash drive running in this machine, then I would back-link the cache onto the hard drive; to me, that's a no-brainer. It'll be faster, and more responsive. However, IF there's any chance you may want to move the flash drive and use it with a different machine, then you're going to have to either

• Create a new cache on the new machine and back-link again, OR

• Keep it on the flash drive, outside the 'save', therefore.....it would want to be at /mnt/home, but outside the 'PUPS' directory.

Is this a USB 3.0 flash drive, or USB 2.0? It doesn't work so well with older-gen flash drives, simply because the read/write speeds are that much slower....

------------------------------

As for SFS versions of browsers, well.......I've explained my rationale as to why I don't like them several times, on other threads. Where a browser will update 'in-situ', the way 'zilla-based browsers do, you've immediately shot yourself in the foot. SFS-based browsers are read-only; yes, you can update them while they're loaded in RAM, but you can't write this back to the SFS without re-building it at every shut-down. It can of course be done, but to my way of thinking that's a somewhat 'clunky' solution. Of course, the choice is - as always - down to the individual.

Always happy to help..!

Mike.

[Sky Aisling]

@mikewalsh

Thank you, Mike. You've validated my intuition.
The flash drive is a 3.0 drive.
The machine has 2.0 and 3.0 USB ports.
The hard drive is a mechanical sata.

I left a bit of space (5GBs) at the head of the sata drive.
I had intended to mount the Fossapup(64) 9.6 there but on second thought decided to keep the Puppy on a flash drive as Debian Pups change frequently according to the Ubuntu release schedule.

The machine was a give-a-way that was headed for the recycle pile.
The machine is proving true so far.

So, it's off to the hard drive to set up your cache declutter system that has worked so well.

Sky

PS-I might put the declutter directory deeper into the sata drive.
Mechanical drives get the most wear and tear at the beginning of the cylinder.
The history of this machine is unknown.

Firefox cache3.png (43.34 KiB) Viewed 731 times

[Sky Aisling]

@mikewalsh

EDIT Mike and all...Please ignore this post. I think I got it figured out. See next post.
Sky

Hi Mike,
Got up this morning and went to set up the nifty browser declutter method in Fossadog(64)9.6.
Ran into a bit of a glitch.

The transfer of /root/.mozilla and /root/.moonchild productions from /root into the new "Profiles" sub-directory went perfectly.

Firefox profiles-cache declutter1.png (90.63 KiB) Viewed 698 times

But, ...

When placing /root/.cache/mozilla and /root/.moonchild productions from /root/cache into the new "Cache" sub-directory there is a still a trace of them left in /root/.cache/.
And, the entry in the new cache sub-directory shows as a relative link?

Firefox profiles-cache declutter2.png (69.98 KiB) Viewed 698 times

What to do next? I've set everything back to original configuration before attempting the declutter method again.

A clue maybe? There is a thing called SAVESPEC in Fossadog(64) 9.6 that messes with the labels in the partition label area. SAVESPEC puts a location reference in the label area.
https://www.forum.puppylinux.com/viewto ... 766#p95766
I'm wondering...

Also, does the partition sda1 where the declutter file is located need to be mounted at startup time for the declutter method to activate? Is a mount script placed in startup necessary?

The distro is running from a flash drive on sdb1.

Gparted-partition for cache declutter method1.png (76.04 KiB) Viewed 698 times

Thank you in advance,
Sky

[Sky Aisling]

@mikewalsh and all

Ok, here's the scoop on what happened concerning the reduction of Firefox cache in Fossadog(64) 9.6 as of 8-10-23.
I decided to remove Firefox 115.0.2 and re-install Firefox 115.0.2 and try Mike's method again.
I updated Puppy Package Manager libraries then did a new install of Firefox.
Puppy Package Manager installed Firefox 116.0.2 (not 115.8.2).
Firefox 116.0.2 is not building a large cache in Fossadog(64) 9.6. GDmap consistently shows between 91 - 100 (give or take) megabits of cache in root.
I have purposely explored many media-rich websites over the last few days. The result in GDmap stays the same.
So, I'm keeping my fingers crossed this will continue.
Again, "if it ain't broke, don't fix it!"

Sky

Firefox Cache Build1 in Fossadog(64) 9.6.png (205.4 KiB) Viewed 652 times