Fatdog64-500 final
libtiff.s0.4
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.
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.
Here is something to check for that.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.
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.
sage
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.
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.
eth0 is not working
Hello!
I installed Fatdog64 (great work, by the way) on my dell studio xps 8100.
The problem is it didn't detected my ethernet card, a Broadcom Netlink BCM57780.
I tried the pet here
http://www.murga-linux.com/puppy/viewtopic.php?p=445461
which
What can I do?
Thanks a lot in advance
Davide
I installed Fatdog64 (great work, by the way) on my dell studio xps 8100.
The problem is it didn't detected my ethernet card, a Broadcom Netlink BCM57780.
I tried the pet here
http://www.murga-linux.com/puppy/viewtopic.php?p=445461
which
but it still doesn't work.is the latest tg3 driver for Broadcom BCM577xx ethernet devices
What can I do?
Thanks a lot in advance
Davide
The big dog64
Hi guys:
Well, all I can say is YES! I just joined the puppy revo and damn you guys scream. I just did a 32 install on my intel dual 2.8 of 5.1 and FatDog on my AmmyQuad. Think I will have to shed the on board sound as it never came up at all. All else is great. The speed at which things happen here is fenominal at the least. So much different than you know ..... And to think, I almost bought 7.
The last three versions of linux that I tried had severe problems. I run lots of usb drives, wireless, scanners, burners yadda yadda. They had probs with it.
A belkin 4 port and 32" tv for a mon, forget it. You guys, all works so far. Not sure on the color laser printer but will have to see.
Super thanks to all the great folks here and hope I can help in some small way.
the tigger that goes WUFF! TW
Well, all I can say is YES! I just joined the puppy revo and damn you guys scream. I just did a 32 install on my intel dual 2.8 of 5.1 and FatDog on my AmmyQuad. Think I will have to shed the on board sound as it never came up at all. All else is great. The speed at which things happen here is fenominal at the least. So much different than you know ..... And to think, I almost bought 7.
The last three versions of linux that I tried had severe problems. I run lots of usb drives, wireless, scanners, burners yadda yadda. They had probs with it.
A belkin 4 port and 32" tv for a mon, forget it. You guys, all works so far. Not sure on the color laser printer but will have to see.
Super thanks to all the great folks here and hope I can help in some small way.
the tigger that goes WUFF! TW
Sudden change of file permissions?
Hello!
Love the FD500 distro.... works perfectly on my Acer Aspire 4530/AMD64.
Have a question:
Was downloading wallpaper with Firefox to usr/share/background and everything was going great until suddenly (after the fifth download or so), I got an error that the file could not be saved to that folder because of permissions, and to change the permissions or choose another folder.
? How was it working fine to that point? The files to that point made it into the folder fine, as I even stopped after the second dl to set new wallpaper with one of the ones I'd just dl'd there.... then suddenly a few downloads later... the error msg. ??
Went to "/background/" folder -> Permissions -> and chose for the user to be able to read/write. Still didn't work. Nothing worked. Finally had to chose spot folder instead, then manually move them.
I'd be grateful for any insight.
FatDog500 frugal install on 4GB USB Stick
Acer Aspire 4530/AMD64x2/nVidia9100GM
Love the FD500 distro.... works perfectly on my Acer Aspire 4530/AMD64.
Have a question:
Was downloading wallpaper with Firefox to usr/share/background and everything was going great until suddenly (after the fifth download or so), I got an error that the file could not be saved to that folder because of permissions, and to change the permissions or choose another folder.
? How was it working fine to that point? The files to that point made it into the folder fine, as I even stopped after the second dl to set new wallpaper with one of the ones I'd just dl'd there.... then suddenly a few downloads later... the error msg. ??
Went to "/background/" folder -> Permissions -> and chose for the user to be able to read/write. Still didn't work. Nothing worked. Finally had to chose spot folder instead, then manually move them.
I'd be grateful for any insight.
FatDog500 frugal install on 4GB USB Stick
Acer Aspire 4530/AMD64x2/nVidia9100GM
rian,
Firefox normally runs as user spot in Fatdog64, so can only write to folders owned by spot (spot, Downloads). To run as root open a terminal and type firefox or drag /usr/bin/firefox to the desktop.
With the package manager click on configure and then update.
Anniekin,
All of the ext file systems should be supported. I haven't had a problem.
Firefox normally runs as user spot in Fatdog64, so can only write to folders owned by spot (spot, Downloads). To run as root open a terminal and type firefox or drag /usr/bin/firefox to the desktop.
With the package manager click on configure and then update.
Anniekin,
All of the ext file systems should be supported. I haven't had a problem.
I am trying to get a printer working on our sons 64-bit laptop with Fatdog64.
He has a school project due ...
The printer is a HP and is one the many that require the special driver.
May we use the generic hplip or fooxxx or do we need to be sure to use one compiled for Fatdog64, please?
Thanks!
He has a school project due ...
The printer is a HP and is one the many that require the special driver.
May we use the generic hplip or fooxxx or do we need to be sure to use one compiled for Fatdog64, please?
Thanks!
[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
Pet for FatDog
Please help yourself to our pet of Alpine 2.00 text-based news & email client.
It is compiled under and for Fatdog64 from full source.
Fat!
Alpine can be started from the CLI or menu.
This is a secure, easy to use, and highly configurable program.
One can access multiple remote mailboxes and bookmark files.
Multiple user identities (roles) may be setup.
Cascading config files can be made giving users limited control over setup options and predefining the rest.
Tips aimed at Pine users should also work for Alpine.
Colors can be set from the Alpine program (Main => Setup => Kolor) &/or from the loader script.
To do that look into "rxvt -help" at command line. Change the code calling the terminal emulator (rxvt) in:
/root/my-aplications/bin/alpine.sh
We use this file to make it easy.
Alpine can be setup from within the application or by editing .pinerc file(s)--many tips are to be found in the comments of .pinerc.
If you use pop3 mailbox access I suggest using the #move format.
This prevents the mailbox from timing out. Timed out mailboxes can cause "shrink" errors saving mail.
That breaks local mail folders (they can be fixed with a hex editor by deleting partly downloaded data).
eg. (in .pinerc)
Nickname "#move {your.server.com:25/pop3/ssl/user=you}inbox /home/user/mail/mailbox"
Overall I prefer IMAP access with tls or ssl.
eg.
Nickname {your.server.com/tls/user=you}inbox
Alpine can be setup before running by importing /root/.pinerc.
There is also a tool for importing remote setup and address books.
Should this be placed into the FatDog repository?
My ten year old son and I made it. Use as-is or modify to improve this pet.
Enjoy!
moB & Magnus
ps. If it's good enough for Linus, it's good enough for us. No?
http://www.google.com/search?q=linus+alpine
It is compiled under and for Fatdog64 from full source.
Fat!
Alpine can be started from the CLI or menu.
This is a secure, easy to use, and highly configurable program.
One can access multiple remote mailboxes and bookmark files.
Multiple user identities (roles) may be setup.
Cascading config files can be made giving users limited control over setup options and predefining the rest.
Tips aimed at Pine users should also work for Alpine.
Colors can be set from the Alpine program (Main => Setup => Kolor) &/or from the loader script.
To do that look into "rxvt -help" at command line. Change the code calling the terminal emulator (rxvt) in:
/root/my-aplications/bin/alpine.sh
We use this file to make it easy.
Alpine can be setup from within the application or by editing .pinerc file(s)--many tips are to be found in the comments of .pinerc.
If you use pop3 mailbox access I suggest using the #move format.
This prevents the mailbox from timing out. Timed out mailboxes can cause "shrink" errors saving mail.
That breaks local mail folders (they can be fixed with a hex editor by deleting partly downloaded data).
eg. (in .pinerc)
Nickname "#move {your.server.com:25/pop3/ssl/user=you}inbox /home/user/mail/mailbox"
Overall I prefer IMAP access with tls or ssl.
eg.
Nickname {your.server.com/tls/user=you}inbox
Alpine can be setup before running by importing /root/.pinerc.
There is also a tool for importing remote setup and address books.
Should this be placed into the FatDog repository?
My ten year old son and I made it. Use as-is or modify to improve this pet.
Enjoy!
moB & Magnus
ps. If it's good enough for Linus, it's good enough for us. No?
http://www.google.com/search?q=linus+alpine
Re: Pet for FatDog
John Murga seems to have run out of disc space!moB wrote:Please help yourself to our pet of Alpine 2.00 text-based news & email client.
Maximum size on uploads is now 0 (yes, zero) bytes
Look here: http://ieinc.ca/Magnus/logo/alpine-2.00.pet
It has the usual Puppy login/password.
If using wget:
wget -c http://puppy:linux@ieinc.ca/Magnus/logo/alpine-2.00.pet
moB
You've really had to work this point in the forum!kirk wrote:rian,
Firefox normally runs as user spot in Fatdog64, so can only write to folders owned by spot (spot, Downloads). To run as root open a terminal and type firefox or drag /usr/bin/firefox to the desktop.
.
Let's have bit of a go at it, then. Here's my experience, in case it helps anyone out there.
I prefer to put downloads outside the personal save file on the actual harddrive.
Namakura (aka firefox) does not use symlinks to directory outside of spot.
Symlinks are not seen as links, but as files. Mounted drives are also refused. This applies to up and down loads.
My workaround is to have a script (movit):
# #!/bin/sh
# if ls /root/spot/Downloads/* 1> /dev/null 2>&1; then
# mv /root/spot/Downloads/* /mnt/home/fd64-500/Downloads/
# echo Moved Spot\'s \/Downloads to fd64-500\/Downloads -- outside pupsave.
# else echo No files to move in Spot\'s \/Downloads at this time.
# fi
# exit
[nb. each line has been prefixed with a hash mark. Remove leading # to use code.]
It resides in /usr/bin and can work from /root/my-applications/bin, too.
I call movit from the CLI and /etc/rc.d/rc.shutdown (after script displays shutdown message). Thus downloads can be moved manually or left to be moved at shutdown automatically.
From the terminal it gives a message explaining what it did.
The result message is suppressed by the "less verbose" line at the top of rc.shutdown so won't clutter your shutdowns.
This 'solves' a downloads issue, not the uploads difficulty.
Perhaps there's even a better way to direct downloads outside of the personal save file?
I strongly support sandboxing web-browsers, especially graphical multimedia browsers.
I would try to copy the method when installing browsers in Puppy everywhere.
Kind regards,
moB
kirk and jamesbond:
Yeah, the praise is almost getting boring, but let me add my voice to the crowd.
Tip 'o the hat to you gents. Great job. Gotta love FD
Love the snappy performance on the old AMD 64. Much better than the 32 bit XP that I inherited with it... and now there's sound!
Magnus said he finally played DOOM (in dosbox) the way it was meant to play.
As with all new setups I am having a few problems, or rather unexplained complexities. So I ask your indulgence as I try to "pick your brains" & get this Puppy into top form.
1. Currently trying to get ffmpeg to run. Gives error:
Memory (RAM) shortage? Installed components in wrong order?
Usually considered good practice to install after all shared libraries.
Quick summary:
I just clicked from top to bottom of ibilio directory.
Ran ffmpeg once before all installed. Completed install. Same sort of error. Tried reinstalling that pet. Nada.
2. No joy NAT masquerading.
Am trying to do internet sharing through a crossover cable. XP can do it
Tried what seems to work for others, but...
Do I need to set the NICs to use static DNS? Now set to use DHCP.
See:
http://www.murga-linux.com/puppy/viewtopic.php?t=38472
http://www.murga-linux.com/puppy/viewtopic.php?t=18129
http://www.linuxsolved.com/linux-forums ... 115.0.html
Seems like a beginner's level problem, but I ask to be sure this is confirmed to work in fatdog64.
3. In a similar vein, setting up file sharing has not yet suceeded.
How about file sharing? That's the next little mountain to tackle.
I used the interface in root, but nothing more.
We need to share between linux and XP boxes on the LAN.
If I should be better served asking these questions elsewhere, please feel free to tell me where to go
Thanks for reading this, and twice for any tips and help you have!
moB
Wrinkles should merely indicate where
smiles have been.
-- Mark Twain
Yeah, the praise is almost getting boring, but let me add my voice to the crowd.
Tip 'o the hat to you gents. Great job. Gotta love FD
Love the snappy performance on the old AMD 64. Much better than the 32 bit XP that I inherited with it... and now there's sound!
Magnus said he finally played DOOM (in dosbox) the way it was meant to play.
As with all new setups I am having a few problems, or rather unexplained complexities. So I ask your indulgence as I try to "pick your brains" & get this Puppy into top form.
1. Currently trying to get ffmpeg to run. Gives error:
Haven't worked on this enough to figure out what's up.ffmpeg: error while loading shared libraries: libvpx.so: cannot map zero fill pages: cannot allocate memory
Memory (RAM) shortage? Installed components in wrong order?
Usually considered good practice to install after all shared libraries.
Quick summary:
I just clicked from top to bottom of ibilio directory.
Ran ffmpeg once before all installed. Completed install. Same sort of error. Tried reinstalling that pet. Nada.
2. No joy NAT masquerading.
Am trying to do internet sharing through a crossover cable. XP can do it
Tried what seems to work for others, but...
Do I need to set the NICs to use static DNS? Now set to use DHCP.
See:
http://www.murga-linux.com/puppy/viewtopic.php?t=38472
http://www.murga-linux.com/puppy/viewtopic.php?t=18129
http://www.linuxsolved.com/linux-forums ... 115.0.html
Seems like a beginner's level problem, but I ask to be sure this is confirmed to work in fatdog64.
3. In a similar vein, setting up file sharing has not yet suceeded.
How about file sharing? That's the next little mountain to tackle.
I used the interface in root, but nothing more.
We need to share between linux and XP boxes on the LAN.
If I should be better served asking these questions elsewhere, please feel free to tell me where to go
Thanks for reading this, and twice for any tips and help you have!
moB
Wrinkles should merely indicate where
smiles have been.
-- Mark Twain
When you shutdown the first time and create a save file you should be asked if you want to move the Downloads folder to the same place as your save file.I prefer to put downloads outside the personal save file on the actual harddrive.
I haven't had that error. Ffmpeg is included, you don't need to install a pet package, or does this error occur after installing some particular pet package?1. Currently trying to get ffmpeg to run. Gives error:
Quote:
ffmpeg: error while loading shared libraries: libvpx.so: cannot map zero fill pages: cannot allocate memory
Haven't worked on this enough to figure out what's up.
Memory (RAM) shortage? Installed components in wrong order?
Usually considered good practice to install after all shared libraries.
Quick summary:
I just clicked from top to bottom of ibilio directory.
Ran ffmpeg once before all installed. Completed install. Same sort of error. Tried reinstalling that pet. Nada.
I haven't did that in Fatdog64. It's been may years since I've tried, can't help with that one.2. No joy NAT masquerading.
Am trying to do internet sharing through a crossover cable. XP can do it Surprised
Tried what seems to work for others, but...
That's usually done with Samba, but there is no Samba package for Fatdog at this time. You could install NFS services on Windows. The easiest way to move files around is FTP. Go to menu-Network-PureFTPd and run that. Then from a web browser on another computer type ftp://192.168.1.200 (If 192.168.1.200 is the ip address of the computer running PureFTP.). You can login as root with the default password of woofwoof. You can change the root password by opening a terminal and typing passwd. For some reason Firefox doesn't include an upload option for FTP, but you can add it by going to this page:3. In a similar vein, setting up file sharing has not yet suceeded.
How about file sharing? That's the next little mountain to tackle.
I used the interface in root, but nothing more.
We need to share between linux and XP boxes on the LAN.
http://www.wg9s.com/mozilla/firefox/ext ... ftpupload/
and installing that add-on.
I think I'll include that add-on in Fatdog64-510. I'm testing 510 right now. It will include kernel 2.6.35.7, Xorg-server 1.9 and Mesa 7.8.2.
Downloads
kirk,kirk wrote:
When you shutdown the first time and create a save file you should be asked if you want to move the Downloads folder to the same place as your save file.
Yes, this did occur, but doesn't function as intended. Firefox refuses to use it, hence a workaround
Something's up. Interesting--too interesting
moB
ffmpeg
kirk,kirk wrote:1. Currently trying to get ffmpeg to run. Gives error:
Quote:
ffmpeg: error while loading shared libraries: libvpx.so: cannot map zero fill pages: cannot allocate memory
<deleted>
I haven't had that error. Ffmpeg is included, you don't need to install a pet package, or does this error occur after installing some particular pet package?
Use ffmpeg on mint and debian, so getting it to work on FD is really just about wanting things to be right.
Done a fair amount of searching for an answer. Someone suggested that such an error reflects a failure to load shared libraries into memory.
How much RAM is needed to run ffmpeg under FD? (We're already compiled!)
Thought it may have been a file corruption during or from copy of FD's main file.
Checked the md5sum & iso is correct. Good, so far...
I tried reinstalling from the ibilio original pets.
No--already installed.
Booted from the CD with 'pfix=fsck,clear' to restore good "official" copies.
Same error persists.
What next? Should I kill the personal savefile and start again? (After backing up user data!)
Something is "hinkey" and it gets at me. I could use mint or debian lxde, but this old box likes FD best, and so do we.
This is great! Always a beginner, so much to learn
moB
FD is frugal installed in a subdir (ntfs) and boots with grub4dos.
System info: AMD Athalon 64 3000+, 508 MB RAM
ps. we like to use fflink script to format images for ffmpeg (jpegs to mpeg):
1. Put subdir in image folder.
2. Change to it and run fflink--symlinks to images are made with sequential names.
(Some filtering can be done by editing script.)
3. Run ffmpeg on links.
Images can be reused without copies piling up.
No need to lose your original filenames.
The framerate can be treated as a base rate by copying duplicates of the links... some images can then last longer on the screen.
Code: Select all
#!/bin/sh
# This will make a set of symlinks to files in directory
# one level up continuously from screen001.jpg ...
# The total is displayed on the terminal command prompt.
# The script handles up to 999 images.
#
# Then you say something like
# ffmpeg -r .2 -i screen%03d.jpg outputmovie.mp4
# or
# ffmpeg -r 1 -b 1800 -i screen%03d.jpg output.mp4
#
# nb. Fails when space exists in fullpath (path or filename).
# moB 16 Oct 2010
no=0
# edit this line to select files: S1* or *.jpg ...
for f in ../*.jpg; do
no=$((no+1)); linkname=donna_ivy
if [ "$no" -lt "10" ] ; then linkname=${linkname}00
elif [ "$no" -lt "100" ] ; then linkname=${linkname}0
fi
ln -s $f ${linkname}${no}.jpg
# hardlink
# ln $f screen00${no}.jpg
# symbolic
# ln -s $f screen00${no}.jpg
done
echo Total files linked\: $no ; echo
exit
Edited to make script easier to copy-->more usable.
moB 23 mars 2011
.
Last edited by moB on Thu 24 Mar 2011, 09:10, edited 2 times in total.