Fatdog64-500 final

Message

Burn_IT · #211 Post by **Burn_IT** » Wed 22 Sep 2010, 16:43

http://www.zdnet.co.uk/news/security-th ... ?s_cid=116

edoc · #212 Post by **edoc** » Wed 22 Sep 2010, 17:04

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.

edoc · #213 Post by **edoc** » Wed 22 Sep 2010, 17:07

Warrior522 wrote:
WillM wrote:Here is the homepage of libtiff.

http://www.remotesensing.org/libtiff/
I can't find it...

Should he use the Beta6 version?

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?

MT250 · #214 Post by **MT250** » Thu 23 Sep 2010, 10:26

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.

emil · #215 Post by **emil** » Fri 24 Sep 2010, 07:31

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?

Burn_IT · #216 Post by **Burn_IT** » Fri 24 Sep 2010, 09:30

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.

emil · #217 Post by **emil** » Fri 24 Sep 2010, 18:54

..., 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.

I quote Jamesbond from page 1 of this thread for using 32-bit packages.
Any experiences anyone what is working and what is not?

edoc · #218 Post by **edoc** » Fri 24 Sep 2010, 21:38

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.

Didn't I read somewhere that there is an interface app that allows 32bit apps to run within the Fatdog64 environment?

Sorta a WINE-32 for 64bit apps?

Burn_IT · #219 Post by **Burn_IT** » Fri 24 Sep 2010, 22:28

I particularly did NOT mention 32 bit support because it had already been covered.

prehistoric · #220 Post by **prehistoric** » Sat 25 Sep 2010, 20:28

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.

kirk · #221 Post by **kirk** » Sat 25 Sep 2010, 20:50

I've got a new laptop (Dell e6410), so I can actually use Fatdog64! My old laptop used a Pentium M. I've started working on Fatdog64-510. Once 2.6.36 comes out and AUFS gets updated to work with it, I'll be putting out an RC. Really not planning on a lot of changes:

* upgrade kernel to 2.6.36 and patch i915 to work with my e6410.
* upgrade Firefox.
* upgrade Xorg input and video drivers.
* New 64bit flash.
* Add ffmpeg gui.
* Bug fixes.

I posting this from my e6410 using fd64-500. Buth I have to use the vesa video driver because of problems with i915. I've seen a patch for i915 against 2.6.36rc5 that is reported to fix the problems with the e6410's video. But AUFS does not work with 2.6.36 yet so I can't try it out

. Then there's the touch pad issues on the e6410 that seem to have a partial fix. I really hate going with a kernel that new, but once again it contains some fixes that I need.

edoc · #222 Post by **edoc** » Sat 25 Sep 2010, 20:59

Deleted

pemasu · #223 Post by **pemasu** » Sat 25 Sep 2010, 22:41

I've started working on Fatdog64-510. Once 2.6.36 comes out and AUFS gets updated to work with it, I'll be putting out an RC.

For me dhcpd cuts wlan connection frequently. Would dhcpd update help ? BK announced new dhcpd package in his blog.

kirk · #224 Post by **kirk** » Sun 26 Sep 2010, 01:50

Upgraded dhcpcd to 5.2.7. We'll see what happens.

pemasu · #225 Post by **pemasu** » Sun 26 Sep 2010, 08:28

Upgraded dhcpcd to 5.2.7

Is it somewhere for download and testing. I could give report if it does fix my problem.

WillM · #226 Post by **WillM** » Sun 26 Sep 2010, 22:02

Debian and derivatives have renumbered the TIFF shared library because of incompatibilities introduced around version 3.6.1.

Linking libraries between versions is not usually recommended.
In this one case, it maybe ok to symlink the version on your system to libtiff.so.4, because of the versioning inconsistencies.

If you tell me what program and Puppy you are using I will try that and see if it works.

Anniekin · #227 Post by **Anniekin** » Tue 28 Sep 2010, 15:51

I would like to try!

WillM · #228 Post by **WillM** » Thu 30 Sep 2010, 00:17

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.

Here is something to check for that.

http://www.ksplice.com/uptrack/cve-2010-3081

And here's a little more info.

http://blog.ksplice.com/2010/09/anatomy ... -2010-3081

It sounds like enterprise machines are the more likely targets.

Anniekin · #229 Post by **Anniekin** » Thu 30 Sep 2010, 23:25

can u made xfce version?

i have very strange experiences in the past using LXPanel

emil · #230 Post by **emil** » Fri 01 Oct 2010, 16:50

I compiled sage on Fatdog. In order to do so I needed to add header files for the package lzo to /usr/include (lzo download). They are not in the Fatdog devx.sfs. Everything else went smooth, but took some hours to finish.

All tests past successfull at sage -testall.

doicomehereoften1, can you publish your latex pet? Then I can compile a version with latex support and make a sfs.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Fatdog64-500 final

64bit kernel compromised

Re: libtiff4

Fat Dog64 Repositories

puppy confusion

"hypertransport syn flood error on last boot"?

libtiff.s0.4

sage