Moderator: Forum moderators
Hello
I have Xenial64 on two partitions on my SSD. Laptop is a Dell Latitude E6230.
One I use all the time the other is fairly basic.
Basic Xenial64 boots to WI FI in 28 secs.
Normal Xenial64 takes 37 secs and is increasing.
What have I done to slow my once nimble Xenial64? Help and/or advice would be appreciated.
Thanks.
Do you have any SFS packages set to load on boot up?
Anything you did just before noticing this?
Installed a new program?
Changed some settings?
Is the web browser setup to open where you last closed it?
What format is the partition the Xenialpup installs are on?
Forum Global Moderator
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected 
bigpup wrote: ↑Mon Feb 14, 2022 9:32 amDo you have any SFS packages set to load on boot up?
Anything you did just before noticing this?
Installed a new program?
Changed some settings?
Is the web browser setup to open where you last closed it?What format is the partition the Xenialpup installs are on?
Both partitions are ext4, no SFS files load at boot except the main Xenial file.
It has seemed to be getting a bit slower lately but I did load a planetarium program from PPM.
I did un-install it but not much better.
I now cannot find the program that I installed.
I have not changed any settings and the browser does not start where I closed it. I usually alt+F4 to close.
if you use the pfind tool and select the all files box and type in the program name then pfind will find the program files for you.
The only astronomy program I can find in PPM is kstars and there is no trace with pfind, ( all files. )
It may not be related to last install as I un-installed it and I had noticed a slow down even before this.
You can view all the packages you have installed.
In PPM, click the "uninstall" button and a list of them will appear.
Maybe you uninstalled just a program and some dependencies remained (required by the program and added during the auto install)?
Can you give us an image of what is in:
/root/Startup/
/root/.config/autostart/
Maybe something got placed in one of these locations, that is started at boot up.
Forum Global Moderator
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
Another thing worth quickly checking is the size and contents of the /root/.cache directory. If you have program profiles within your savefile it can fill up fast and can slow things down in general. It is ok to delete anything within that directory as it will be recreated if necessary, by program or at boot.
Mine stays quite clean as I have all program profiles outside the savefile. Browsers are the worst offenders in this respect by far.
My pups: LxPupSc64 and Voidpup64 with LXDE ydrv & synaptics touchpad drivers, both using savefiles. Ydrv based Jammypup64 (JWM), Bookworm64, Fossapup23 & FossapupFire (LXDE/PCManFM). No savefiles, no fdrvs there. 
download/file.php?mode=view&id=8057
Marv wrote: ↑Tue Feb 15, 2022 2:03 amAnother thing worth quickly checking is the size and contents of the /root/.cache directory. If you have program profiles within your savefile it can fill up fast and can slow things down in general. It is ok to delete anything within that directory as it will be recreated if necessary, by program or at boot.
Mine stays quite clean as I have all program profiles outside the savefile. Browsers are the worst offenders in this respect by far.
Thanks Marv
I did check, there was masses so I deleted the lot but not yet made and difference to boot time.
I am interested in keeping profiles outside the savefile. How do you do that.
Having said that the main sfs file takes a long time at boot the the savefile takes less than a second
You can opt to symlink the profile outside the savefile. Preferably to /mnt/home if you want to keep portability (if its a usb and also to not have to mount the partition each time)
IRC: firepup | Time to hack Puppy!
The other excellent option is to explore/use some of @mikewalsh portable apps. They and their profiles reside totally within a designated directory on a separate partition or drive. Virtually effortless sharing between pups too. Just needs a .desktop in a pup pointing to the portable LAUNCH file. His framework is quite polished at this point and thus makes a great template (Thanks Mike!) for rolling your own 'portables'. I run an older LibreOfice and Master PDF Editor packaged that way.
My run-as-spot browsers that are still SFS based, mostly Slimjet, all share a common spot directory with spot:spot permissions on my EXT Data partitions with symlinks named spot pointing to it both in /root and in /Home. Sylpheed and the clipboard programs also have symlinks pointing to their profiles in a shared profiles directory on the Data partitions.
My pups: LxPupSc64 and Voidpup64 with LXDE ydrv & synaptics touchpad drivers, both using savefiles. Ydrv based Jammypup64 (JWM), Bookworm64, Fossapup23 & FossapupFire (LXDE/PCManFM). No savefiles, no fdrvs there.
Marv wrote: ↑Tue Feb 15, 2022 4:25 pmThe other excellent option is to explore/use some of @mikewalsh portable apps. They and their profiles reside totally within a designated directory on a separate partition or drive. Virtually effortless sharing between pups too. Just needs a .desktop in a pup pointing to the portable LAUNCH file. His framework is quite polished at this point and thus makes a great template (Thanks Mike!) for rolling your own 'portables'. I run an older LibreOfice and Master PDF Editor packaged that way.
My run-as-spot browsers that are still SFS based, mostly Slimjet, all share a common spot directory with spot:spot permissions on my EXT Data partitions with symlinks named spot pointing to it both in /root and in /Home. Sylpheed and the clipboard programs also have symlinks pointing to their profiles in a shared profiles directory on the Data partitions.
Thanks Marv
Good site I will use it.
