Installed Firefox 13 using Fatdog Package Manager. It does not work. I've uninstalled it and reinstalled it several times from different mirrors. Same results. Executing code firefox-spot results in # firefox-spot
sh: /usr/lib64/firefox/firefox: No such file or directory Likewise for firefox.

I had a similar problem with my desktop computer installation and attributed that to a bad download. However, I think there is more to it since I get same results from both ibiblio and nluug. It may be better to create a pet from something other than the nightly build.

Otherwise, everything checked on the laptop is working great.

Hadn't gotten around to reporting it but the same thing happened here.
The Firefox directory is located at /usr/lib64/firefox-13.0/ ..... I just changed the exec line in the desktop file in /usr/share/applications/ to run FF as root.

Download was actually fine but FF wouldn't launch. Editing the desktop file worked here.Last edited by James C on Sun 17 Jun 2012, 19:12; edited 1 time in total

Hope it is okay to ask this very naive question.
Ooops seems to be Lupu that is the "culprit"
sorry. I will write in their thread instead.

old now deprecated text.

I am in Lupu 528 now and have set time to CET Central European Time
with Summer displacement so it show the right time.

But after doing a frugal install of FatDog it changed to plus 2 hour extra
so instead of 14.10 it show 16.10 in the old Lupu when I boot into that one
again.

I tried to set up local time in same way on FadDog as I do in Lupu. 14.10

What could have went wrong? On Lupu I have ticked the BIOS Hardware
time should take priority.

Why would that make FatDog shutdown displacing time two hours plus?
I will now reboot from Lupu into Fatdog again and see what happens there
if it shows 14 or 16 so I get back and
Edit from FD. I shows 14.30 so I will boot into Lupu again.
Edit from Lupu. This time it is plus 2 hours without having touched anything
on neither Lupu not on FatDog. So just the fact that I rebooted and chose
Fatdog change the time in BIOS with two hours???

Or what is going on Please a mystery to be solved or a Noob to bash for bad acting

Fatdog always uses localtime for the BIOS clock. Other puppies offer possibilities to use either localtime or UTC time in the BIOS clock. To make sure the time stays the same between Lupu and Fatdog, choose "localtime" in Lupu.
This is a design decision - Windows-based machines uses localtime for BIOS clock, so Fatdog uses localtime too to ensure that switching to/from Windows will not accidentally change the time. Of course, by using localtime in BIOS clock, we lose that automatic daylight savings time, but that is an advantage because automatic DST settings doesn't always work _________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.

Addition to previous post, Package Manager failed to download package list from ibiblio .... so I just used nluug.

I just tested, ibiblio works from here ... perhaps there was random traffic problem just now _________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.

Jim, the screenshot you take shows that the firefox binaries are not installed at all. I just tested it again; the firefox pet is working.

The one that is possibly not working for you is petget installer. If you don't mind, please try this:
1. Edit the file /usr/sbin/silent_petget
2. Goto line 86
3. Near the end of the line, when you see "cpio -p $INSTALL_ROOT", change that to "cpio -up $INSTALL_ROOT"
4. Then try to install firefox again.
Let me know.

Jim, the screenshot you take shows that the firefox binaries are not installed at all. I just tested it again; the firefox pet is working.

The one that is possibly not working for you is petget installer. If you don't mind, please try this:
1. Edit the file /usr/sbin/silent_petget
2. Goto line 86
3. Near the end of the line, when you see "cpio -p $INSTALL_ROOT", change that to "cpio -up $INSTALL_ROOT"
4. Then try to install firefox again.
Let me know.

They move fast don't they ffmpeg was the latest when kirk compiled it back in Feb (kirk took it from git master - the latest development branch). I'll leave the decision to kirk quite a lot depends on ffmpeg, updating ffmpeg means rebuilding a lot of stuff._________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.

rcrsn51 has kindly tested and confirms that it works with 32-bit printer drivers as well.

cheers!

Does that mean one can have a 32-bit version of FatDog that is 100%
compatible with every 32-bit pet? I am so dense.

Re Firefox and the edit. Good to know. I don't want to loose bookmarks
either and I am more used to FF and FatDog already being more than
128MB why can it not be FireFox from scratch and SM as something
the SM luvrs add because them being enthusiastic about it.
I mean if 99% love FireFox then why force all those to have two browsers

*Friendly Smile*_________________I use Google Search on Puppy Forum
not an ideal solution though

Puppy Linux, the most popular of the ultra-small Linux distributions on the market, has often been criticised by reviewers for always "running as root" and for disregarding one of the most basic among the UNIX security principles. Now some community members on the project's forum responded with a special Puppy derivative called "Fatdog64", a 64-bit Puppy build with extra applications and, most importantly, an experimental multi-user setup. This beta release includes Linux kernel 3.4.2, SeaMonkey 2.10, Flash Player 11.2.202.236, and numerous bug fixes since alpha 2. From the announcement: "James and myself are happy to announce Fatdog64-600 beta 1. Here are the changes since alpha2: SFS works with multisession; add libdbus_glib; uses BusyBox blkid (faster) instead of util-linux blkid; volume label display on drive icons can be turned off; bug fix with first-time session save; hardinfo patched - does not crash, show Fatdog64 version; Windows-K key is shortcut for xkill (to kill windows apps); new control panel - all system/settings apps are now here; QuickApps - create application shortcuts; urxvt 9.15 (without Perl extension); command-line tool to split Fatdog humongous initrd to standard Puppy initrd for faster USB boot; experimental multi-user (some applications are still broken; some PET packages do not support non-root)."

Puppy Linux, the most popular of the ultra-small Linux distributions on the market, has often been criticised by reviewers for always "running as root" and for disregarding one of the most basic among the UNIX security principles. Now some community members on the project's forum responded with a special Puppy derivative called "Fatdog64", a 64-bit Puppy build with extra applications and, most importantly, an experimental multi-user setup. This beta release includes Linux kernel 3.4.2, SeaMonkey 2.10, Flash Player 11.2.202.236, and numerous bug fixes since alpha 2. From the announcement: "James and myself are happy to announce Fatdog64-600 beta 1. Here are the changes since alpha2: SFS works with multisession; add libdbus_glib; uses BusyBox blkid (faster) instead of util-linux blkid; volume label display on drive icons can be turned off; bug fix with first-time session save; hardinfo patched - does not crash, show Fatdog64 version; Windows-K key is shortcut for xkill (to kill windows apps); new control panel - all system/settings apps are now here; QuickApps - create application shortcuts; urxvt 9.15 (without Perl extension); command-line tool to split Fatdog humongous initrd to standard Puppy initrd for faster USB boot; experimental multi-user (some applications are still broken; some PET packages do not support non-root)."

One more beta release that will contain the kernel that will be used in final. Then a release candidate, that will be renamed as final if it's OK. Right now, this is the plan if no big problems turn up along the way.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum