Fatdog64-600 alpha2
Fatdog64-600 alpha2
I compiled and made a pet of Links 2.6 Web Browser in fatdog64-600 alpha2.
Warning Links older than 2.7pre1 contains some bugs that can result in writing out of allocated memory if Links is running in graphics mode. This can be potentially exploited to attack the computer. If you use graphics mode you should upgrade to Links 2.7pre1.
The links version 2.6 can be removed in fatdog package manager.
Warning Links older than 2.7pre1 contains some bugs that can result in writing out of allocated memory if Links is running in graphics mode. This can be potentially exploited to attack the computer. If you use graphics mode you should upgrade to Links 2.7pre1.
The links version 2.6 can be removed in fatdog package manager.
- Attachments
-
- warning.jpg
- (11.15 KiB) Downloaded 1035 times
Last edited by Billtoo on Wed 13 Jun 2012, 18:00, edited 1 time in total.
This code executed immediately.jamesbond wrote:Thanks Jim, so it's blkid that is slow. Is there any time difference running this:(busybox's version of blkid)?Code: Select all
busybox blkid
Although, xorgwizard does not work, I was able to remove the "nouveau" driver and install the latest NIVIDIA driver.
- Attachments
-
- image-1.jpg
- (46.34 KiB) Downloaded 1364 times
Re: CUPS fails to find HP Photosmart C5280
They worked, really like your new Package Manager. I should have checked it for latest drivers.jamesbond wrote:Can you try the hp drivers in the package manager?Jim1911 wrote:CUPS fails to find HP Photosmart C5280. I have installed hplip_print_fd64-3-11.pet which worked with the previous Fatdog64.
![Embarassed :oops:](./images/smilies/icon_redface.gif)
kirk:
I did as you suggested with flsynclient and tap is worked just great. Iv,e said this before but I envy you guys your knowledge of these things.
Thanks again for all your help.
irishrm.
BTW:
There is a failed symbolic link to autocutsel (yellow triangle) in my start-up folder. Don't know what that means.
I did as you suggested with flsynclient and tap is worked just great. Iv,e said this before but I envy you guys your knowledge of these things.
Thanks again for all your help.
irishrm.
BTW:
There is a failed symbolic link to autocutsel (yellow triangle) in my start-up folder. Don't know what that means.
BibleTime version 2.9.1
BibleTime version 2.9.1 is now available. I did install the older BibleTime version 2.8.1, which works fine in Fatdog64-600. Hopefully, the newer version will be in your great new "Fatdog64 Package Manager" when it reaches final release.
Incidently, a minor edit is needed in /usr/share/applications/bibletime.desktop so that the proper icon shows up. Change Icon line to:
Thanks for this superb Fatdog64-600,
Jim
Incidently, a minor edit is needed in /usr/share/applications/bibletime.desktop so that the proper icon shows up. Change Icon line to:
Code: Select all
Icon=/usr/share/bibletime/icons/bibletime.png
Jim
Re: Fatdog64-600 alpha2
THank you - will get this to the repo later.Billtoo wrote:I compiled and made a pet of Links 2.6 Web Browser in fatdog64-600 alpha2.
EDIT: This is now in repo.
Last edited by jamesbond on Sat 19 May 2012, 10:05, edited 1 time in total.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Odd, in my machine it is a tad slower. Busybox blkid does not return volume labels.Jim1911 wrote:This code executed immediately.jamesbond wrote:Thanks Jim, so it's blkid that is slow. Is there any time difference running this:(busybox's version of blkid)?Code: Select all
busybox blkid
EDIT: busybox blkid does return volume labels
![Shocked :shock:](./images/smilies/icon_eek.gif)
Anyway, how does this one fare?
Code: Select all
ls /sys/class/block | grep -vE "^loop|^ram|^nbd|^sr" | xargs -I '{}' disktype /dev/'{}'
Last edited by jamesbond on Sat 19 May 2012, 03:35, edited 1 time in total.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Re: CUPS fails to find HP Photosmart C5280
rcrsn51 prepared all those drivers; so they are the same as the ones you've used before, only newer. So all thanks to himJim1911 wrote:They worked, really like your new Package Manager. I should have checked it for latest drivers.jamesbond wrote:Can you try the hp drivers in the package manager?Jim1911 wrote:CUPS fails to find HP Photosmart C5280. I have installed hplip_print_fd64-3-11.pet which worked with the previous Fatdog64.
![Smile :)](./images/smilies/icon_smile.gif)
Glad you like the new package manager. Next is to make the repository does contain something
![Smile :)](./images/smilies/icon_smile.gif)
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
I used to use autocutsel instead of glipper. The idea of having a dead symlink is that one just need to put the autocutsel binary in /usr/bin and it will suddenly spring to life. But nowadays I'm happy with glipper too. I'll remove that link in next release; otherwise it's harmless.irishrm wrote:BTW:
There is a failed symbolic link to autocutsel (yellow triangle) in my start-up folder. Don't know what that means.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
This code executed in about 2 min and includes much more information.jamesbond wrote:Odd, in my machine it is a tad slower. Busybox blkid does not return volume labels. Anyway, how does this one fare?Jim1911 wrote:This code executed immediately.jamesbond wrote:Thanks Jim, so it's blkid that is slow. Is there any time difference running this:(busybox's version of blkid)?Code: Select all
busybox blkid
It reads the content of /sys/class/block and tries to decipher what's inside, just like blkid, but it uses different tool. See if this is faster than the original blkid?Code: Select all
ls /sys/class/block | grep -vE "^loop|^ram|^nbd|^sr" | xargs -I '{}' disktype /dev/'{}'
On another matter, xfe, installed with the Package Manager, give an error:
- # xfe
xfe: error while loading shared libraries: libGL.so.1: wrong ELF class: ELFCLASS32
Last edited by Jim1911 on Sat 19 May 2012, 03:39, edited 1 time in total.
Re: BibleTime version 2.9.1
Happy to do so; do you have a pet or do I have to compile this from source?Jim1911 wrote:BibleTime version 2.9.1 is now available. I did install the older BibleTime version 2.8.1, which works fine in Fatdog64-600. Hopefully, the newer version will be in your great new "Fatdog64 Package Manager" when it reaches final release.
Incidently, a minor edit is needed in /usr/share/applications/bibletime.desktop so that the proper icon shows up. Change Icon line to:Thanks for this superb Fatdog64-600,Code: Select all
Icon=/usr/share/bibletime/icons/bibletime.png
Jim
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Re: BibleTime version 2.9.1
Kirk prepared version 2.8.1 for Fatdog64-521 and it's in your repository along with the dependencies. I think the dependencies may be OK, just Bibletime needs update. Other than Kirk's version, the later versions available are 32 bit, 01micko prepared 2.9.1 for Slacko, pemasu and jerimah also have version 2.9.1 for their distributions. I have copies of all of these.jamesbond wrote:Happy to do so; do you have a pet or do I have to compile this from source?Jim1911 wrote:BibleTime version 2.9.1 is now available. I did install the older BibleTime version 2.8.1, which works fine in Fatdog64-600. Hopefully, the newer version will be in your great new "Fatdog64 Package Manager" when it reaches final release.
Incidently, a minor edit is needed in /usr/share/applications/bibletime.desktop so that the proper icon shows up. Change Icon line to:Thanks for this superb Fatdog64-600,Code: Select all
Icon=/usr/share/bibletime/icons/bibletime.png
Jim
Thanks,
Jim
-
- Posts: 361
- Joined: Fri 27 May 2011, 17:21
- Location: Reading UK
Hello jamesbond
The reason is that things like web browsers and display drivers are updated every few weeks and it is not reasonable to expect Puppy developers to provide new .pets so often.
I don't mind a bit of manual fixing, if necessary. In this case I would just move the Opera folder to /usr/lib64 and reinstate the symbolic link.
If anyone can give me step by step instructions on how to install the ATI driver in fd6 using the .run file from AMD, I would be pleased to have a go.
I would prefer that or, even better, a script rather than a .pet so that I can install whichever version is currently the least buggy.
I know the 12.1 package required 32 bit libraries in order to install on a 64bit system. I don't know whether that is still true for 12.4
I didn't use a .pet, I installed using opera_11.64.1403_amd64.deb downloaded via the Opera website.jamesbond wrote:I had this problem earlier and thought I have fixed it. Can you please provide the link to the pet so that I can test it?LateAdopter wrote: Opera 11.64 put a folder in /usr/lib which I suspect had previously been a symbolic link to /usr/lib64 like in fd520
So I put a symbolic link to /usr/lib64/hardinfo in /usr/lib then Hardinfo worked again.
The reason is that things like web browsers and display drivers are updated every few weeks and it is not reasonable to expect Puppy developers to provide new .pets so often.
I don't mind a bit of manual fixing, if necessary. In this case I would just move the Opera folder to /usr/lib64 and reinstate the symbolic link.
If anyone can give me step by step instructions on how to install the ATI driver in fd6 using the .run file from AMD, I would be pleased to have a go.
I would prefer that or, even better, a script rather than a .pet so that I can install whichever version is currently the least buggy.
I know the 12.1 package required 32 bit libraries in order to install on a 64bit system. I don't know whether that is still true for 12.4
I have just replaced all blkid with disktype, so let's see how this works. In my machine disktype is faster than blkid; blkid is faster than busybox blkid.Jim1911 wrote:This code executed in about 2 min and includes much more information.
I just did this on savefile=none (that's the equivalent of pfix=ram), I don't get any error. Could be some of your libraries are overwritten by earlier pet install; and/or the /usr/lib get hosed again as per irishrm case.On another matter, xfe, installed with the Package Manager, give an error:
- # xfe
xfe: error while loading shared libraries: libGL.so.1: wrong ELF class: ELFCLASS32
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
That explains, I may overlooked that part. I assume you just click the .DEB? (you don't, by any change, do undeb manually and copy the files over?)LateAdopter wrote:I didn't use a .pet, I installed using opera_11.64.1403_amd64.deb downloaded via the Opera website.
The reason is that things like web browsers and display drivers are updated every few weeks and it is not reasonable to expect Puppy developers to provide new .pets so often.
I don't mind a bit of manual fixing, if necessary. In this case I would just move the Opera folder to /usr/lib64 and reinstate the symbolic link.
I did that in the past for previous Fatdogs, haven't done this myself on 600. Once I've done it I can document the steps and share it with you (or even better, make a script out of it).If anyone can give me step by step instructions on how to install the ATI driver in fd6 using the .run file from AMD, I would be pleased to have a go.
I would prefer that or, even better, a script rather than a .pet so that I can install whichever version is currently the least buggy.
You are referring to Opera right? I don't use Opera so I can't comment. You can still probably use 32-bit libs from 521. I plan to build a new 32-bit library from latest Puppy (Racy, Slacko, Wary? not sure yet) - but that will take a while.I know the 12.1 package required 32 bit libraries in order to install on a 64bit system. I don't know whether that is still true for 12.4
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Re: BibleTime version 2.9.1
Bibletime 2.9.1 is now the in the repo. I'm using old clucene and sword from 521 - repackaged for 600.Jim1911 wrote:Kirk prepared version 2.8.1 for Fatdog64-521 and it's in your repository along with the dependencies. I think the dependencies may be OK, just Bibletime needs update. Other than Kirk's version, the later versions available are 32 bit, 01micko prepared 2.9.1 for Slacko, pemasu and jerimah also have version 2.9.1 for their distributions. I have copies of all of these.
cheers!
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Fatdog64-600 alpha2
I want to use the fatdog64 installer to prepare and install fatdog to
an 8gb flash drive.
I did all the steps but chose to install the bootloader to the
partition of the flash drive and that wouldn't boot, I wasn't sure
installing it to the MBR meant the MBR of the internal hard drive or
the flash drive so I chickened out on that option.
Will the installer put the bootloader on the MBR of the flash drive
and not disturb the internal hard drive?
an 8gb flash drive.
I did all the steps but chose to install the bootloader to the
partition of the flash drive and that wouldn't boot, I wasn't sure
installing it to the MBR meant the MBR of the internal hard drive or
the flash drive so I chickened out on that option.
Will the installer put the bootloader on the MBR of the flash drive
and not disturb the internal hard drive?