Fatdog64-500 final
-
- Posts: 7
- Joined: Sat 29 Aug 2009, 13:36
UPDATE: I've compiled LaTeX with AmsMath from the TeXlive installer. It doesn't have many of the bells and whistles outside of the basic TeXlive packages for English Language, stuff for Math/Science/Engineering and has no documentation with it. I'm going to stick into the final .sfs file I've mentioned, but I will also upload it as a .pet here later on.
Adobe Flash
Adobe has released a new 64 bit version of Flash that will work on Linux. They call it a preview edition. I have tried this and it mostly works.
The only problem I had was expanding the view on You Tube.
http://labs.adobe.com/technologies/flashplayer10/
The only problem I had was expanding the view on You Tube.
http://labs.adobe.com/technologies/flashplayer10/
Our son needs libtiff.so.4 and I've looked around for it and some up empty.
The closest version I found is here:
http://brainwavedesigncentral.net/mike.html
But he needs the newer libtiff.so.4
Anyone know of a source for this, please?
The closest version I found is here:
http://brainwavedesigncentral.net/mike.html
But he needs the newer libtiff.so.4
Anyone know of a source for this, please?
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
Re: Adobe Flash
Excellent!WillM wrote:Adobe has released a new 64 bit version of Flash that will work on Linux. They call it a preview edition. I have tried this and it mostly works.
The only problem I had was expanding the view on You Tube.
http://labs.adobe.com/technologies/flashplayer10/
I will ask our son to try it on the 64bit laptop.
QUESTION: Does this install alongside the existing Flash or does it replace it?
Any concerns as to harming the stability of the Seamonkey install?
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
-
- Posts: 90
- Joined: Tue 03 Aug 2010, 15:46
Re: Adobe Flash
I did, it just made things worse.edoc wrote:Excellent!WillM wrote:Adobe has released a new 64 bit version of Flash that will work on Linux. They call it a preview edition. I have tried this and it mostly works.
The only problem I had was expanding the view on You Tube.
http://labs.adobe.com/technologies/flashplayer10/
I will ask our son to try it on the 64bit laptop.
64bit SeaMonkey available
64bit SeaMonkey moving from Alpha to Beta
Has really been stable for me. And very very fast. Faster than old in searches (BING + Google). Faster with page displays and Videos are much much smoother than other browsers used with FATDOG64.
Something to consider....BUT IT IS ALPHA-BETA, so understand that even though I have not had any problems over the past week in full-time use, thus far, "its beta!"
Edited Sep 23, 2010 5:27 pm There's a 64bit FLASH out from Adobe, now, too. These announcements are seemingly too co-incidental.
Has really been stable for me. And very very fast. Faster than old in searches (BING + Google). Faster with page displays and Videos are much much smoother than other browsers used with FATDOG64.
Something to consider....BUT IT IS ALPHA-BETA, so understand that even though I have not had any problems over the past week in full-time use, thus far, "its beta!"
Edited Sep 23, 2010 5:27 pm There's a 64bit FLASH out from Adobe, now, too. These announcements are seemingly too co-incidental.
Last edited by gcmartin on Thu 23 Sep 2010, 21:37, edited 3 times in total.
-
- Posts: 90
- Joined: Tue 03 Aug 2010, 15:46
Re: libtiff4
I can't find it...
64bit kernel compromised
"Just think of it as leaving early to avoid the rush" - T Pratchett
Is there a patch for Fatdog64?
Exploit code was made available on the Full Disclosure mailing list on Wednesday. Arnold said that the flaw was introduced into the Linux kernel in 2008 and involves every 64-bit Linux distribution.
"Essentially every distribution is affected, including RHEL, CentOS, Debian, Ubuntu, Parallels Virtuozzo Containers, OpenVZ, CloudLinux, and SuSE, among others," said Arnold.
Red Hat said in an advisory that it had patched its Red Hat Enterprise Linux (RHEL) software on Sunday.
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
Re: libtiff4
Should he use the Beta6 version?Warrior522 wrote:I can't find it...
http://download.osgeo.org/libtiff/
tiff-4.0.0beta6.tar.gz 11-Jun-2010 16:00 1.9M
EDIT: I just explored the tar.gz and .zip files and both contain some large app -- he only needs the libtiff.so.4 file, which does not appear to be present in either.
Anyone have a location for just the libtiff.so.4 file, please?
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
Fat Dog64 Repositories
Hello to all you other FatDog 64 users. I am a relative newbee to this distro and this is my first post on the forum. If I have placed this post in the wrong place, I beg your pardon. I plan on using FD64 in a locked down SD card for internet banking (I discovered that capability from reading the security forum). I really like 64's small foot print, it's speed when loading up, 100% RAM load up and particularly it's ease of setting up internet dial-up service. Compared to Ubuntu, Mint and Knoppix's dial-up, it's a breeze!
However, I have become very frustrated after reading through all the various text that appears in numerous different places, scattered and chopped up it seems, regarding installing Ubuntu repositories in FD64. I have spent hours searching this site and others for a good explanation. I have used other Linux distros for five months now, added software packages via Synaptic and terminal but have had no luck doing the same in this distro. In the forums people talk about doing it but never say how.
I have read through the following .iso based and online text documents;
"Puppy package database format"
"http://puppylinux.com/woof/ppm.htm"
"The Puppy Package Manager" at http://bkhome.org/woof/ppm.htm
" Introduction to Petspec: http://puppylinux.com/blog/?viewDetailed=00698"
"HOWTO add (or remove) a package database"
ftp.filearena.net|http://ftp.filearena.net/pub/ubuntu|Pac ... _VERSION}-* mirror.anl.gov|http://mirror.anl.gov/pub/ubuntu|Packag ... _VERSION}-* mirrors.kernel.org|http://mirrors.kernel.org/ubuntu|Packag ... _VERSION}-* archive.ubuntu.com|http://archive.ubuntu.com/ubuntu|Packag ... _VERSION}-*
There are actually three different repositories on each site that Puppy can download from, 'main', 'universe' and 'multiverse'. Puppy has a database file for each, for example for the 'Intrepid' release of Ubuntu: 'Packages-ubuntu-intrepid-main', 'Packages-ubuntu-intrepid-universe' and 'Packages-ubuntu-intrepid-multiverse'. Accordingly, the PKG_DOCS_DISTRO_COMPAT variable has this:
archive.ubuntu.com|http://archive.ubuntu.com/ubuntu/dists/ ... SION}-main archive.ubuntu.com|http://archive.ubuntu.com/ubuntu/dists/ ... }-universe archive.ubuntu.com|http://archive.ubuntu.com/ubuntu/dists/ ... multiverse
...that is, it specifies all three databases.
"http://puppylinux.com/woof/pkg-db-format.htm"
I have also looked through the following files on my laptop
/root/.packages/DISTRO_COMPAT_REPOS
"#where to get pkg docs, format: domain|uri|localfilename...
PKG_DOCS_DISTRO_COMPAT="ibiblio.org|http://distro.ibiblio.org/pub/linux/dis ... 64-offical"
#t2 repos...
#note, the local pkgs database file (or partname) is also appended to these entries, so know which url to download a particular pkg from (glob wildcard allowed)...
REPOS_DISTRO_COMPAT="ibiblio.org|http://distro.ibiblio.org/pub/linux/dis ... 64-offical"
/root/.packages/DISTRO_PET_REPOS
/etc/DISTRO_SPECS
"#DISTRO_FILE_PREFIX: prefix for Puppy files... exs: upup-500.sfs, upupsave.2fs
#DISTRO_VERSION: this is the version number of Puppy that you are building. must be 3 digits.
# (technical note: see below it is defined without quotes, this is required by scripts)
#package list and urls are in file DISTRO-PKGS-SPECS-${DISTRO_BINARY_COMPAT}.
DISTRO_VERSION=500
DISTRO_BINARY_COMPAT="t2" #####change this as required#####
case $DISTRO_BINARY_COMPAT in
ubuntu)
DISTRO_NAME="Jaunty Puppy"
DISTRO_FILE_PREFIX="upup"
DISTRO_COMPAT_VERSION="jaunty"
;;
DISTRO-PKGS-SPECS (partial contents)
"#where to get pkg docs, format: domain|uri|localfilename...
PKG_DOCS_DISTRO_COMPAT="ibilio.org|http://distro.ibiblio.org/pub/linux/dis ... 64-offical"
#t2 repos...
#note, the local pkgs database file (or partname) is also appended to these entries, so know which url to download a particular pkg from (glob wildcard allowed)...
#REPOS_DISTRO_COMPAT="ibilio.org|http://distro.ibiblio.org/pub/linux/dis ... 64-offical"
#w469 fallbacks when looking for pet pkgs (space-separated list)...
FALLBACKS_COMPAT_VERSIONS=''
#PKGS_SPECS_TABLE table format:
#will pkg be in puppy-build.
# Generic name for pkg. Note: PET packages, if exist, use this name.
# Comma-separated list of compatible-distro pkg(s). '-' prefix, exclude.
# Must be exact name-only of pkg, else '*' on end is wildcard to search full name.
# Empty field, then use PET pkg.
# How the package will get split up in woof (optional redirection '>' operator).
# Missing field, it goes into exe. Can also redirect >null, means dump it.
#yes|abiword|iceword,iceword-plugins|exe,dev,doc,nls
#example showing wildcard. finds all full pkg names with 'gcc-4.3*',
#but, exclude any 'gcc-4.3-doc*' matches...
#yes|gcc|gcc,gcc-4.3*,-gcc-4.3-doc*|exe,dev,doc,nls
PKGS_SPECS_TABLE='
no|0hack1_dev||exe>dev,dev,doc,nls
yes|915resolution||exe,dev,doc,nls
yes|a52dec|a52dec|exe,dev,doc,nls
yes|abiword|abiword|exe,dev,doc,nls
no|abiword-plugin-grammar||exe,dev,doc,nls
no|abiword-plugin-mathview||exe,dev,doc,nls
yes|absvolume_puppy||exe
no|acl|acl|exe,dev,doc,nls
no|aiksaurus||exe,dev,doc,nls
"Packages-puppy-lucid-offical"
abiword-2.8.3-lupu|abiword|2.8.3-lupu||Document|21936K|pet_packages-5|abiword-2.8.3-lupu.pet||Compose, edit, and view documents|ubuntu|lucid|5|
Acrobat_Reader-9.3.3-Lucid|Acrobat_Reader|9.3.3-Lucid||Utility|149228K|pet-packages-lucid|Acrobat_Reader-9.3.3-Lucid.pet||Adobe Acrobat Reader *huge*|ubuntu|lucid||
Aisleriot-2.30-Lucid|Aisleriot|2.30-Lucid||Fun|9712K|pet-packages-lucid|Aisleriot-2.30-Lucid.pet||Play many different solitaire games|ubuntu|lucid||
---------------------------------------------------------------------------------------------------------------------
I suspect the answer to getting the Ubuntu Repositories activated, is somewhere in this mass of info I have dug though. But I don't know how to put it all together. The Puppy Package Manager configure window says that "Adding a new repository currently requires manual editing of some text files". Which text files and how do you edit them? Is this done via Terminal or by Leafpad text editor? I know if you do this right the result is supposed to look like the following Puppy Package Manager with the Ubuntu main, multiverse and universe repos showing. Could someone please show me how this is done? Thank you for your time.
However, I have become very frustrated after reading through all the various text that appears in numerous different places, scattered and chopped up it seems, regarding installing Ubuntu repositories in FD64. I have spent hours searching this site and others for a good explanation. I have used other Linux distros for five months now, added software packages via Synaptic and terminal but have had no luck doing the same in this distro. In the forums people talk about doing it but never say how.
I have read through the following .iso based and online text documents;
"Puppy package database format"
"http://puppylinux.com/woof/ppm.htm"
"The Puppy Package Manager" at http://bkhome.org/woof/ppm.htm
" Introduction to Petspec: http://puppylinux.com/blog/?viewDetailed=00698"
"HOWTO add (or remove) a package database"
ftp.filearena.net|http://ftp.filearena.net/pub/ubuntu|Pac ... _VERSION}-* mirror.anl.gov|http://mirror.anl.gov/pub/ubuntu|Packag ... _VERSION}-* mirrors.kernel.org|http://mirrors.kernel.org/ubuntu|Packag ... _VERSION}-* archive.ubuntu.com|http://archive.ubuntu.com/ubuntu|Packag ... _VERSION}-*
There are actually three different repositories on each site that Puppy can download from, 'main', 'universe' and 'multiverse'. Puppy has a database file for each, for example for the 'Intrepid' release of Ubuntu: 'Packages-ubuntu-intrepid-main', 'Packages-ubuntu-intrepid-universe' and 'Packages-ubuntu-intrepid-multiverse'. Accordingly, the PKG_DOCS_DISTRO_COMPAT variable has this:
archive.ubuntu.com|http://archive.ubuntu.com/ubuntu/dists/ ... SION}-main archive.ubuntu.com|http://archive.ubuntu.com/ubuntu/dists/ ... }-universe archive.ubuntu.com|http://archive.ubuntu.com/ubuntu/dists/ ... multiverse
...that is, it specifies all three databases.
"http://puppylinux.com/woof/pkg-db-format.htm"
I have also looked through the following files on my laptop
/root/.packages/DISTRO_COMPAT_REPOS
"#where to get pkg docs, format: domain|uri|localfilename...
PKG_DOCS_DISTRO_COMPAT="ibiblio.org|http://distro.ibiblio.org/pub/linux/dis ... 64-offical"
#t2 repos...
#note, the local pkgs database file (or partname) is also appended to these entries, so know which url to download a particular pkg from (glob wildcard allowed)...
REPOS_DISTRO_COMPAT="ibiblio.org|http://distro.ibiblio.org/pub/linux/dis ... 64-offical"
/root/.packages/DISTRO_PET_REPOS
/etc/DISTRO_SPECS
"#DISTRO_FILE_PREFIX: prefix for Puppy files... exs: upup-500.sfs, upupsave.2fs
#DISTRO_VERSION: this is the version number of Puppy that you are building. must be 3 digits.
# (technical note: see below it is defined without quotes, this is required by scripts)
#package list and urls are in file DISTRO-PKGS-SPECS-${DISTRO_BINARY_COMPAT}.
DISTRO_VERSION=500
DISTRO_BINARY_COMPAT="t2" #####change this as required#####
case $DISTRO_BINARY_COMPAT in
ubuntu)
DISTRO_NAME="Jaunty Puppy"
DISTRO_FILE_PREFIX="upup"
DISTRO_COMPAT_VERSION="jaunty"
;;
DISTRO-PKGS-SPECS (partial contents)
"#where to get pkg docs, format: domain|uri|localfilename...
PKG_DOCS_DISTRO_COMPAT="ibilio.org|http://distro.ibiblio.org/pub/linux/dis ... 64-offical"
#t2 repos...
#note, the local pkgs database file (or partname) is also appended to these entries, so know which url to download a particular pkg from (glob wildcard allowed)...
#REPOS_DISTRO_COMPAT="ibilio.org|http://distro.ibiblio.org/pub/linux/dis ... 64-offical"
#w469 fallbacks when looking for pet pkgs (space-separated list)...
FALLBACKS_COMPAT_VERSIONS=''
#PKGS_SPECS_TABLE table format:
#will pkg be in puppy-build.
# Generic name for pkg. Note: PET packages, if exist, use this name.
# Comma-separated list of compatible-distro pkg(s). '-' prefix, exclude.
# Must be exact name-only of pkg, else '*' on end is wildcard to search full name.
# Empty field, then use PET pkg.
# How the package will get split up in woof (optional redirection '>' operator).
# Missing field, it goes into exe. Can also redirect >null, means dump it.
#yes|abiword|iceword,iceword-plugins|exe,dev,doc,nls
#example showing wildcard. finds all full pkg names with 'gcc-4.3*',
#but, exclude any 'gcc-4.3-doc*' matches...
#yes|gcc|gcc,gcc-4.3*,-gcc-4.3-doc*|exe,dev,doc,nls
PKGS_SPECS_TABLE='
no|0hack1_dev||exe>dev,dev,doc,nls
yes|915resolution||exe,dev,doc,nls
yes|a52dec|a52dec|exe,dev,doc,nls
yes|abiword|abiword|exe,dev,doc,nls
no|abiword-plugin-grammar||exe,dev,doc,nls
no|abiword-plugin-mathview||exe,dev,doc,nls
yes|absvolume_puppy||exe
no|acl|acl|exe,dev,doc,nls
no|aiksaurus||exe,dev,doc,nls
"Packages-puppy-lucid-offical"
abiword-2.8.3-lupu|abiword|2.8.3-lupu||Document|21936K|pet_packages-5|abiword-2.8.3-lupu.pet||Compose, edit, and view documents|ubuntu|lucid|5|
Acrobat_Reader-9.3.3-Lucid|Acrobat_Reader|9.3.3-Lucid||Utility|149228K|pet-packages-lucid|Acrobat_Reader-9.3.3-Lucid.pet||Adobe Acrobat Reader *huge*|ubuntu|lucid||
Aisleriot-2.30-Lucid|Aisleriot|2.30-Lucid||Fun|9712K|pet-packages-lucid|Aisleriot-2.30-Lucid.pet||Play many different solitaire games|ubuntu|lucid||
---------------------------------------------------------------------------------------------------------------------
I suspect the answer to getting the Ubuntu Repositories activated, is somewhere in this mass of info I have dug though. But I don't know how to put it all together. The Puppy Package Manager configure window says that "Adding a new repository currently requires manual editing of some text files". Which text files and how do you edit them? Is this done via Terminal or by Leafpad text editor? I know if you do this right the result is supposed to look like the following Puppy Package Manager with the Ubuntu main, multiverse and universe repos showing. Could someone please show me how this is done? Thank you for your time.
puppy confusion
Hello MT250,
i don't think programs from the Ubuntu Repos will work in Fatdog. The short explanation is that the base system is different (Fatdog was build from T2 packages). If you need specific applications your best bet is to search this forum thread and probably compile yourself.
( If I am wrong, I'd like to be corrected).
Perhaps you got confused with the many puppy versions which are out there "in the wild". The official puppy 5.x (32-bit) is based on ubuntu packages, therefore it is possible to use ubuntu repos to add software.
This is not true for other puppy versions. If you want to add a lot of custom software which is not available yet in Fatdog it will be a lot of work to create them. However post about your needs, maybe you get help from the community.
kind regards
emil
Afterthought: I wish puppy would care more about having a good stock of well made and tested software packages. Right at the moment I feel its all about pupplets, woof, bones, sfs, pet, pup, quirky, wary, saluki, lupu, squeeze, luma, fatdog, fluppy, pupeee, TXZ which is nice for the insiders - but how should a newcomer to puppy not be confused?
i don't think programs from the Ubuntu Repos will work in Fatdog. The short explanation is that the base system is different (Fatdog was build from T2 packages). If you need specific applications your best bet is to search this forum thread and probably compile yourself.
( If I am wrong, I'd like to be corrected).
Perhaps you got confused with the many puppy versions which are out there "in the wild". The official puppy 5.x (32-bit) is based on ubuntu packages, therefore it is possible to use ubuntu repos to add software.
This is not true for other puppy versions. If you want to add a lot of custom software which is not available yet in Fatdog it will be a lot of work to create them. However post about your needs, maybe you get help from the community.
kind regards
emil
Afterthought: I wish puppy would care more about having a good stock of well made and tested software packages. Right at the moment I feel its all about pupplets, woof, bones, sfs, pet, pup, quirky, wary, saluki, lupu, squeeze, luma, fatdog, fluppy, pupeee, TXZ which is nice for the insiders - but how should a newcomer to puppy not be confused?
I quote Jamesbond from page 1 of this thread for using 32-bit packages...., Fatdog64 is a 64-bit operating system. It's the only puppy with 64-bit architecture. Most of the software packages out there are targeted for mainstream puppies (lucid puppy, dpup, quirky, wary, puppeee, nop, and many others), which are 32-bit, thus it will not work directly under Fatdog64 (except those software which are script-only).
If you really want to run standard puppy pet packages (32-bit software), Fatdog64 comes with 32-bit compatibility library (taken from Quirky). It's under fd64-32bit-libs.sfs which you can get from the SFS/500 directory under Fatdog distribution site. Bear in mind that if possible, it's always preferable to run native 64-bit software. The 32-bit library is a stopgap measure - no guarantee that it will work for all stadnard puppy packages! Note that some software that uses GTK/Pango needs to be started with "start32" command otherwise you'll see funny things.
Any experiences anyone what is working and what is not?
Didn't I read somewhere that there is an interface app that allows 32bit apps to run within the Fatdog64 environment?Burn_IT wrote:Most of the people using 64 bit Puppy will be - as you say - insiders with the ability to compile for themselves.
The packages are there, but for 32 bit at the moment.
Sorta a WINE-32 for 64bit apps?
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
"hypertransport syn flood error on last boot"?
I'm testing Fatdog64 500 on a quadcore AMD Athlon II with a MSI 880 motherboard using embedded ATI graphics. Everything looked good when I first installed, but after upgrading to the ATI proprietary drivers in the ATI Catalyst pet, a later boot produced the message above. Has anyone else seen this behavior?
There was some problem with Ubuntu 10.04.1 and ATI drivers, which has just been fixed. If the current pet package derived from that, it may need to be upgraded.
There was some problem with Ubuntu 10.04.1 and ATI drivers, which has just been fixed. If the current pet package derived from that, it may need to be upgraded.