(old)Puppy Linux Discussion Forum

On further reflection I may have figured out what I was confused about. Do you mean create a symlink in your home directory to "pgs_K3b-12.17-02_215.sfs" named " pgs_K3b-12.17-02_217.sfs"?

melmc wrote:On further reflection I may have figured out what I was confused about. Do you mean create a symlink in your home directory to "pgs_K3b-12.17-02_215.sfs" named " pgs_K3b-12.17-02_217.sfs"?

Yes that is what I meant, and it can be confusing. In this case the directory is /mnt/home. Technically that is just a symlink to /initrd/mnt/dev_save, the folder where your Lighthouse pup_save.2fs is located. Keep all active .sfs files and their symlinks together. The best way to unload an active SFS module in Lighthouse is to reboot fully in ram with the CD and then either move it to another folder or disable by renaming to end with something other than '.sfs' e.g., .sfs-save or .sfs-off or whatever you prefer.

Of course you could rename the .sfs if you prefer. I prefer symlinking not only because it avoids redundant copied SFS modules but also because it is easier to see which version the .sfs module was originally designed for. Removing the '_215' from the SFS file name will also allow Puppy 2.17 to see and use it, however Lighthouse will then not be able to use it.

For those who might not be familiar with this topic here is some background information:

Loading SFS modules in alternate/multiple Puppies. With Lighthouse the filename must end with _215.sfs. With Puppy 2.17 the filename cannot end with '_nnn.sfs' unless nnn=217. http://www.murga-linux.com/puppy/viewto ... 8&start=45

To 'share' SFS files without copying, I create a symlink <whatever>_217.sfs to <whatever>_215.sfs (Of course, some SFS modules will not work as well in versions for which they were not designed. But this will enable testing and possibly, design for multiple versions.)
-TazOC

I am running Lighthouse from CD with the sfs files on a usb flash. Firefox updated automatically but has to reinstall the update every session. Is there any way I can fix this, i.e. install the update permanently.

melmc wrote:I am running Lighthouse from CD with the sfs files on a usb flash. Firefox updated automatically but has to reinstall the update every session. Is there any way I can fix this, i.e. install the update permanently.

It sounds like maybe the FF update isn't completely installing. I wonder, if you click Edit | Preferences | Advanced | Show Update History, what is the entry on top? (first four lines) Mine, abbreviated is:
Firefox 2.0.0.6 (2007072517) Security Update ... The Update was successfully installed.

A temporary workaround might be to un-check the automatic updates for Firefox on that same panel, and then manually apply updates regularly with Help | Check for updates. Let me know what your Update History is showing and whether the workaround helps and I'll keep looking for a better solution.
-TazOC

The update entry shows the same as yours. The date of installation shows when it was first installed. Yet, every time I first run Firefox during a session it indicates that it is installing the update before it starts.

Can you tell me how to set up Firefox to print to pdf like it does in Puppy 2.17?

melmc,
Here is another possible remedy:
Close Firefox. In /usr/local/firefox locate active-update.xml and updates.xml and rename them (updates.xml -> Xupdates.xml , etc) or move them to a backup location.

I found this at http://kb.mozillazine.org/Updates_repor ... st_version and http://kb.mozillazine.org/Software_Upda ... g_properly
-TazOC

melmc wrote:Can you tell me how to set up Firefox to print to pdf like it does in Puppy 2.17?

Good question, I haven't used that feature, so at this point I'm not sure if I can help. I think for 2.17.1 Barry used the print-to-PDF version 0.3 packages in this post: http://www.murga-linux.com/puppy/viewtopic.php?t=16910 Lighthouse is based on Puppy 2.15CE. So one might ask will PDFprinter work in Firefox on 2.15CE? One of the posters on the first page of the thread had problems with Seamonkey/Firefox in 2.15 in May. Could have been an issue with CUPS. So if you try it, you might begin without installing CUPS if possible. Note also, Barry integrated CUPS into Puppy 2.17, whereas Lighthouse just calls the CUPS installer dotpup in the Mariner SFS (if the .sfs is loaded.) And there are significant differences between Puppy 2.15CE and 2.17 and I don't know if/how these might affect print-to-PDF.
-TazOC

See also this post on PDF printing http://www.murga-linux.com/puppy/viewtopic.php?t=20902

jcoder24 wrote:For puppy version 2.16 and 2.17 a pdf printer is included. for 2.16 you must set the pdf printer as you default printer. For version 2.17 you can print to the CUPS-PDF printer.

tazoc wrote:melmc,
Here is another possible remedy:
Close Firefox. In /usr/local/firefox locate active-update.xml and updates.xml and rename them (updates.xml -> Xupdates.xml , etc) or move them to a backup location.

I found this at http://kb.mozillazine.org/Updates_repor ... st_version and http://kb.mozillazine.org/Software_Upda ... g_properly
-TazOC

I renamed the files but Firefox still reinstalls the update each time I start if for a new session.

hi,

First a big moan. My welcome to this pup version was a crap rapper singing the F word five times every ten seconds. It seems I have been automatically connected to Clan Radio.

After twenty minutes of trying to remove this annoyance without success I was using the F word myself.

Please how do I do it?

Regards Tony.

OK, got it.

Found the file /root/autostart and deleted xmms from it.

regards Tony.

@melmc,
shoot, no difference huh? I need some clarification:

Which update is it installing? (can you note the exact update message or does it flash and disappear?)

by new session do you don't mean livecd/first boot do you?

Have you tried disabling the autoupdates on the FF Advanced Pref Page from earlier post? Be aggressive, experiment with disabling all items on that panel and also try Help | Check for updates.

@tony,
After a few weeks of Xmms-p autostart I also disabled it and created a folder within autostart '/root/autostart/DisabledItems' so that I can move items in and out to disable and enable as desired. This is one of many updates planned for beta 5 and posted in my blog 7/21/07 at www.lhpup.org.

More info on beta 4's XMMS and autostart locations here, scroll down near the bottom on both pages:
http://www.lhpup.org/tips-lhp.htm
http://www.lhpup.org/release-lhp.htm
TazOC

Hi,

I am trying to install Kshisen in Lighthouse and am stuck with a missing library:-

libkdnssd.so.1

can anyone help? regards Tony

I'm busy with something else and not able to boot into puppy right now but will look into it for you later. (It's my birthday!) Anyone else feel that can help please do. I did jump over to packages.debian.org just to see what that lib is about and here is the lowdown:

Package: kdnssd (4:3.5.5-5)
Zeroconf support for KDE

A kioslave and kded module that provide Zeroconf support. Try "zeroconf:/" in Konqueror.

This package is part of KDE, as a component of the KDE network module

(Edit8/22/07) Maybe that's not the same one doesn't begin with lib.
I think it's actually part of this:

kdelibs4c2a (4:3.5.7.dfsg.1-1)
core libraries and binaries for all KDE applications

TazOC

tony wrote:Hi,

I am trying to install Kshisen in Lighthouse and am stuck with a missing library:-

libkdnssd.so.1

can anyone help? regards Tony

Hi Tony,
Sorry to keep you waiting. Kshisen looks likes it depends on quite a few KDE libraries in addition to the one you noted:
http://packages.debian.org/stable/games/kshisen

I'm thinking about including the KDE games module in a future Voyager SFS for Lighthouse if dependencies and size constraints allow but I need to finish up Lighthouse Beta 5 before I work on that.

But here's something similar... Have you seen muggins dotpet for Xshisen here?
http://www.murga-linux.com/puppy/viewto ... 797b02aaee
-TazOC

Thanks for the link Tazoc.


The reason I tried Kshisen was that I hoped to get a program that could use alternative tilesets, as for Kmahjong. Unfortunately this is only in the very latest KDE so I ran into trouble not only with dependencies but with versions.

One of the problems I find with puppy is that it changes rapidly but is still locked into older software. It's fun if you like playing around with the system but difficulties arise when you focus on doing something specific.

Still it's kept me happy for a couple of years.

Regards Tony

My father in law wants me to come down to his place and fix his computer, which my half brother built for him. Sadly, this brother of mine installed a hacked copy of windows. I have been looking into LighthousePup as a possible Linux distro for my father in law given his love of lighthouses. I am pretty well impressed with what I have seen and I am downloading a copy of it for him. I figure that I can add a couple of additional packages as pet files and have him up and running fast. I have been using puppy since version 0.7 and I have been overall impressed with everything that keeps coming out. Barry gave us a beautiful OS. The derivatives of this are just amazing. I hope I can show my father in law the beauty and power of this and convince him to make the switch to Linux, with puppy power.

Hi,

I used this link to put WINE on my Corsair flash stick:-

http://www.murga-linux.com/puppy/viewto ... 71&t=20548

Then put Daniel F Valot's shisen program into it. It worked well and terminated well.

Will be taking the stick to Toronto later this year to see if it will perform on my sons computer. (If he will let me )

Regards Tony.

tazoc wrote:@melmc,
shoot, no difference huh? I need some clarification:

Which update is it installing? (can you note the exact update message or does it flash and disappear?)

by new session do you don't mean livecd/first boot do you?

Have you tried disabling the autoupdates on the FF Advanced Pref Page from earlier post? Be aggressive, experiment with disabling all items on that panel and also try Help | Check for updates.

@

I found the following in the Firefox release notes. I am now running Puppy from a frugal install. Can I cure this problem by making some files in the sfs writeable?

"Software Update will not work if Firefox is installed to a location on your disk to which you do not have write access, since Software Update needs to replace or create files in this location."