(old)Puppy Linux Discussion Forum

Hi gcmartin
Thanks for the reply
I have LHP running frugal install ext4 HDD
Very impressive ! I must say
Allow me to rephrase
Are the pets found under LHP Update used "in addition too" or "in place of" the SFS files found in the MARINER ISO ?

Example: if a new version of say java is in the LHP update as a pet
well then should i unload the SFS file of java that was on the mariner iso ?
or use both ?

Hello all
Also wanted to note that KDE desktop will load but when I click the launcher "star" it causes system to lock-up
Here is my system specs I have mariner frugal installed on Ext4 hdd.
Processor
Processor Intel Pentium T4400 (2.2 GHz)
Memory Cache 1024 KB

Memory
Installed Memory 3 GB

Hard Drive
Hard Drive 320 GB

Disk Drive
Optical Drive Type DVD±R Dual Layer/DVD±RW/CD-RW

Display
Display Size 15.6"
Video Card Intel GMA 4500M
I should add that I have had KDE Linux on this machine before with no problems !

OK sorry dummy me skipped right over this in the release notes :
Before installing the KDE4 SFS, copy and paste this into a terminal:
rm -f /root/.kde/Autostart/pup_event
KDE is now working fine !

I started up Lighthouse Mariner 602b2 after a long time idle, and it gave me a bunch of updates to make... and before I was halfway done, my sr0 file got full. How do I increase the size of this file? Believe it or not, the Search function in this form is of no help.

OK, apparently stupid me did not recognize that sr0 is the CD/DVD drive. So why is the update trying to write to that? No clue. However... if I recall correctly I'm running an Nvidia system. (need 300 Mb, have 289) I'm told that I am some number of Mb short of what it needs to download the driver. I suppose I can leave it alone since it is working now... But I think my system file needs to be made larger, and can't figure out how to do that. Any help in both understanding and accomplishing this is appreciated.

Edited to add: This is really interesting. The system thought it was writing to sr0, which is a CD. And over half the updates got done!

I believe that you want:

Menu --> Utility --> Archiving Utiliities --> Resize Personal Storage File

HTH ... David

I use more than one browser with LH64 & Firefox is one of them.

I'm receiving pop-ups stating it's time to upgrade to 30.0 or something like that.

I seem to recall a warning here a while back against upgrading - is that still so?

If it's now recommended to upgrade is the best method to do so inside Firefox?

While I'm on the update/upgrade train ...

There have been stories about some security holes in pieces of Linux - all of them due to not keeping up with update releases.

Since LH64 602 Beta2 is getting a bit long in the tooth are there updates we should be making to any pieces of it?

Will such manual updates risk breaking anything?

edoc wrote:I believe that you want:

Menu --> Utility --> Archiving Utiliities --> Resize Personal Storage File

HTH ... David

I did that, and got...

Sorry, Lighthouse64 is not currently using a personal
persistent storage file. If this is the first time that you booted
Lighthouse64, say from a live-CD, you are currently running
totally in RAM and you will be asked to create a personal
storage file when you end the session (shutdown the PC or
reboot). Note, the file will be named L64save.3fs and
will be created in a place that you nominate.

If you have installed Lighthouse64 to hard drive, or installed
such that personal storage is an entire partition, then you will
not have a L64save.3fs file either.

Press OK to exit...
\
I do have a 3fs save file... now what?

Moss

Hello @Zaivala

zaivala wrote:... I do have a 3fs save file

Questions

• What is the path of our file?
• How are you booting (CD/Frugal)?
• Might you have, on your last boot (system running now), chose "pfix=ram"

OK. Quite simply, I was wrong. I have worked with LH and Fatdog and Puppy and MacPup for so long, I simply could not believe I did not save it when I exited. But there it is, I did not save it. Oddly it is trying to save now, and is taking a REALLY long time...

Agreed, that occurs for me when I am in shutdown saving a session to a Live disc. Of course, there are other options which are much (USB) to much-much (HDD) to much-much-much (SDD) faster than saving to disc media. That phenomenon is a combination of how the shutdown subsystem formulates and writes the save-session material to DVD disc.

@Ted Dog, in his attempts to work with @Jamesbond to approach Live media disc writing of the session. In doing so, there is a great potential of reducing the time required in session saving time. The state of that work and discussion still remains missing clear information on improving save-session to disc media.

I live with it for 2 reasons:

• I am aware that although it takes time, it will complete sucessfully
• I rarely reboot after setup of the system...including when adding PETs
  to gain new/upgraded subsystems.

Hope this helps

Yes, it did get done. I'll try it again and see if I can get those updates.

I wonder why LH64 takes so much longer than Puppy (32-bit) to create the save file? Ah well. I'm here. Took a break from LH due to "life", that pesky little thing, but I'm back.

Edited to add: Part of the time it took could be due to the fact that I ignored warnings and did not have my drive defragged at the time. I keep it defragged most of the time, and could not imagine it was that bad, but when I went to defrag it later it took quite a while to defrag the LH save file.

While working with Fatdog64 time may increase until a rare shutdown interaction is eliminated. JB can't reproduce and its hit and miss for me. But as JB shared the MS code has not changed and I confirmed as such but something causes a burp and causes a lost of saved data from being written.
I have rewrote the orginal MS code to save same data as done in 32bit versions uncompressed in dated folders but its a bolt on code for now and does not rise to the level of effort or scripts that Kirk and JB make.

Like wise is anyone maintaining LH or have its build system. It was a nice spin or pre done setup many people liked that shared a lot of compatibility with Fatdog64.

gcmartin seems to be taking the lead here, although I have no idea whether he has control over the distro. I'm not to hot on FatDog compatibility, as FatDog proved to be incompatible with *me*, whereas LM64Mb2 has pretty much done what I asked (with a lot of help) and acts more like a 32-bit Puppy.

My biggest issue is in add-ons -- if there is not an SFS file, I'm not that familiar with Slax/Slackware and don't know which Linux file to download, or how.

It would be nice to get this out of Beta. This is by far the best 64-bit Linux I've found that I can get to work.

Bumping what edoc said: Are we supposed to update Firefox, or not? It's getting pretty insistent that I do.

Zavala wrote:

Are we supposed to update Firefox, or not?

I have been updating firefox regularly for about a year with no problems so far.
The best way i found is to run Firefox as root, as follows:
Click open a terminal window, type firefox then when firefox starts go to the help tab, go to about and firefox checks for latest updates and it updates itself.
Do a restart and check the about function until there are no more updates, then close the terminal window and now you are set.

Just run FF as default user spot, saving to the Downloads folder; then click on the Downloads desktop icon and move files elsewhere as needed.

Here's the approach I use when FF indicates an available pgrage. FF runs normally as user "spot". Since it's impossible to upgrade under normal use, LH offers a friendly Menu option to allow running FF in a mode (root) for updating.

See pic below.

Firefox isn't showing a Help or About option when opened from Console.

Also, I'm getting this in Add-On updates:

VLC Web PluginVersion 2.0.6 Twoflower, copyright 1996-2012 VideoLAN and Authors
http://www.videolan.org/vlc/ vulnerable

Is there a preferred way to update VLC in Puppy LH64?

Never mind ... I ignored the instructions - opened "Firefox Help" from the Menu - clicked on the pop-up for the update - chose Reboot - clicked on Firefox Root in the window - allowed update to run - closed Firefox Root - opened Firefox Spot from the desktop - it checked Add Ons for compatibility & no problems ... thanks!

Hello, I use Lighthouse on an easily overheated laptop, so I am trying to switch it to a desktop (booting from CD). It goes through the almost entire sequence of boot (past loading SFS files, and the text size adapts to the monitor size, so it's past that) and then after a few lines says "Recursive error fixed but reboot required!"

Rebooting then leads to a repeat.

Has anyone ever seen this message?