Fatdog64-611 Final (Updated 12-14-2012)
JustGreg in Control Panel under Desktop there is an Adjust Touch Pad tool (flSynclient) where you can turn your touch pad off. Have you tried this?
I don't have a 64bit Laptop so I can't test it but it works fine on my 32bit laptop under Dpup Exprimo.
I don't have a 64bit Laptop so I can't test it but it works fine on my 32bit laptop under Dpup Exprimo.
Last edited by smokey01 on Sat 02 Feb 2013, 00:10, edited 1 time in total.
Re: Minor issues with pathing for utitities.
AS you know, I run Live media (DVD boot in this case expressing "media" at boot time.rcrsn51 wrote:Which Samba version are you talking about? The built-in version or Samba 3.6.5 from the repo?gcmartin wrote:Seem that the current PPM version for SAMBA has the same problem.
I checked 3.6.5 and testparm worked OK.Please explain.Minor issues with pathing for utitities.
@Kirk and all, nevermind. I have a update to that post.
For some reason for which I cannot explain, my post's problem has resolved. Here's what happen, but does NOT explain "why".
- I am running FATDOG from DVD on an 4GB X2 system.
- I downloaded a very large distro via browser, which only allows storage into the RAM based filesystem.
- A notification popped indicating "system running short of resources ..."
- I opened ROX and moved items from the RAM filesystem to permanent stores.
- while moving files, I opened a terminal to check which name was assigned for community share and found the problem with "testparm".
- I noted it, restarted the X desktop and posted the problem.
Note: This system has NOT been rebooted since its initial save session to Live media.
@Rcrsn51 thanks. I just reopened a terminal and the system now executes "testparm" as it should.
Sorry, but I still cannot find why that occurred.
Thanks for your help
Thanks Smoke01. Yes the control panel applet works same with a 64 bit as 32 bit. It takes care of the problem. It does save the touch pad state so the touch pad is still off after a reboot. I just finished testing it.
That solves my problem, but, is there a way to use function key to do the same? This is more of an interest of mine rather that something that needs to be done. Thank you in advance for any help on the use of function keys.
That solves my problem, but, is there a way to use function key to do the same? This is more of an interest of mine rather that something that needs to be done. Thank you in advance for any help on the use of function keys.
Enjoy life, Just Greg
Live Well, Laugh Often, Love Much
Live Well, Laugh Often, Love Much
Fn+F4 will toggle your touchpad on/off. It calls the following script:JustGreg wrote:Thanks Smoke01. Yes the control panel applet works same with a 64 bit as 32 bit. It takes care of the problem. It does save the touch pad state so the touch pad is still off after a reboot. I just finished testing it.
That solves my problem, but, is there a way to use function key to do the same? This is more of an interest of mine rather that something that needs to be done. Thank you in advance for any help on the use of function keys.
/usr/bin/toggle-touchpad.
If you don't like the Fn-F4 key combination you can make your own with sven. Sven is in the taskbar, right click on it a choose preferences.
This should get you started.
http://www.bkhome.org/blog/?viewDetailed=02676
http://bkhome.org/fossil/woof2.cgi/arti ... 512793a015
http://murga-linux.com/puppy/viewtopic.php?t=73440
http://www.bkhome.org/blog/?viewDetailed=02676
http://bkhome.org/fossil/woof2.cgi/arti ... 512793a015
http://murga-linux.com/puppy/viewtopic.php?t=73440
capicoso wrote:How can this be translated to spanish?
I'm surprised that nobody translated it already. I'd translate it if there are tools to do so? Like the scripts on other puppies. Or someone could point me in the right direction...
smokey01 wrote:This should get you started.
http://www.bkhome.org/blog/?viewDetailed=02676
http://bkhome.org/fossil/woof2.cgi/arti ... 512793a015
http://murga-linux.com/puppy/viewtopic.php?t=73440
capicoso wrote:How can this be translated to spanish?
I'm surprised that nobody translated it already. I'd translate it if there are tools to do so? Like the scripts on other puppies. Or someone could point me in the right direction...
Thank you.smokey01 wrote:smokey01 wrote:This should get you started.
http://www.bkhome.org/blog/?viewDetailed=02676
http://bkhome.org/fossil/woof2.cgi/arti ... 512793a015
http://murga-linux.com/puppy/viewtopic.php?t=73440
capicoso wrote:How can this be translated to spanish?
I'm surprised that nobody translated it already. I'd translate it if there are tools to do so? Like the scripts on other puppies. Or someone could point me in the right direction...
Both tools look good. Will try them.
I think i was talking about MoManager when i said "Like the scripts on other puppies", because i think i didn't see it installed on fatdog by default
I think MoManager will work with Fatdog but I haven't tried it.
capicoso wrote:Thank you.smokey01 wrote:smokey01 wrote:This should get you started.
http://www.bkhome.org/blog/?viewDetailed=02676
http://bkhome.org/fossil/woof2.cgi/arti ... 512793a015
http://murga-linux.com/puppy/viewtopic.php?t=73440
Both tools look good. Will try them.
I think i was talking about MoManager when i said "Like the scripts on other puppies", because i think i didn't see it installed on fatdog by default
Translation options
Hi @Capicoso
You may also want to review this as you go forward with translations for contribution.
Here to help
You may also want to review this as you go forward with translations for contribution.
Here to help
A few weeks back I brought myself a BluRay burner. I have just installed it to discover things don't work as expected. It won't read or write to BluRay disks. The burner is an LG BH14NS40. The disk I tried to burn is a Verbatim BD-RE
The BR disk I tried to watch was "Friends with Benefits" but it threw up an error about no keys or something.
I tried to burn with Pburn 3.7.11. I played around with the settings a bit but was still unsuccessful.
It will read and write DVD.
Any ideas? I am using FD-611, the Seamonkey version.
Cheers
The BR disk I tried to watch was "Friends with Benefits" but it threw up an error about no keys or something.
I tried to burn with Pburn 3.7.11. I played around with the settings a bit but was still unsuccessful.
It will read and write DVD.
Any ideas? I am using FD-611, the Seamonkey version.
Cheers
-
- Posts: 4
- Joined: Sun 03 Feb 2013, 20:40
You need to install a key file in /root/.config/aacs named KEYDB.cfg and optionally a file named vuk. You can read about this here:The BR disk I tried to watch was "Friends with Benefits" but it threw up an error about no keys or something.
https://wiki.archlinux.org/index.php/BluRay
I've uploaded a pet to here:
http://www.mydrive.ch/
user name: fatdog@to.scared.to.say
password: fatdog
It's in the test folder. It contains the latest KEYDB.cfg I can find and the latest vuk collection I can put together.
After you install the keys you have to first mount the Bluray and then open VLC and select media, open-disk, and BluRay. If you still get an error then the BluRay is too new. The key file only supports up to MKB version 28.
Don't ask who I am. Not legal here to play Blurays you own without giving money to player/software makers who give money to politicians
Error 16 booting FatDog64 611 from grub
I decided to try Fatdog64-611-firefox.iso and Fatdog64-611-seamonkey.iso and I am getting the same error from both while attempting to boot from a frugal install using grub. Booting from the iso burned to a DVD+RW works fine. The downloaded ISO's md5sum to the correct values.
Let me explain...
# pwd
/mnt/sda2/fd64
# ls -la
total 207072
drwxr-xr-x 2 root root 4096 Feb 5 11:52 .
drwxr-xr-x 10 root root 4096 Feb 6 08:37 ..
-rw-r--r-- 1 root root 208261680 Dec 14 12:50 initrd
-rw-r--r-- 1 root root 3767056 Dec 14 12:50 vmlinuz
# cat /mnt/sda2/boot/grub/menu.lst
# GRUB configuration file '/boot/grub/menu.lst'.
#
# Start GRUB global section
default 0
#timeout 5
timeout 5
color light-gray/blue black/light-gray
# End GRUB global section
# Linux bootable partition config begins
title Puppy Linux 5.4.3 (hard disk hd0,1)
root (hd0,1)
kernel /puppy54/vmlinuz psubdir=puppy54
initrd /puppy54/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title Puppy Linux 5.4.3 pfix=ram (no pupsave file loaded, HD as hd0,1)
root (hd0,1)
kernel /puppy54/vmlinuz pfix=ram psubdir=puppy54
initrd /puppy54/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title FatDog64 version 611 (hard disk hd0,1)
rootnoverify (hd0,1)
kernel /fd64/vmlinuz
initrd /fd64/initrd
# Linux bootable partition config ends
# Linux bootable partition config begins
title FatDog64 Seamonkey 611 (hard disk hd0,1)
rootnoverify (hd0,1)
kernel /fd64Sea/vmlinuz
initrd /fd64Sea/initrd
# Linux bootable partition config ends
# grub --version
grub (GNU GRUB 0.97)
When booting and selecting either FatDog64 option I get the error:
Error 16: Inconsistent filesystem structure
I tried the root option and later changed it to rootnoverify with no change.
My puppy 5.4.3 boot works fine from grub. I'm not sure if I'm explaining this right :/
Thanks,
Rob
Let me explain...
# pwd
/mnt/sda2/fd64
# ls -la
total 207072
drwxr-xr-x 2 root root 4096 Feb 5 11:52 .
drwxr-xr-x 10 root root 4096 Feb 6 08:37 ..
-rw-r--r-- 1 root root 208261680 Dec 14 12:50 initrd
-rw-r--r-- 1 root root 3767056 Dec 14 12:50 vmlinuz
# cat /mnt/sda2/boot/grub/menu.lst
# GRUB configuration file '/boot/grub/menu.lst'.
#
# Start GRUB global section
default 0
#timeout 5
timeout 5
color light-gray/blue black/light-gray
# End GRUB global section
# Linux bootable partition config begins
title Puppy Linux 5.4.3 (hard disk hd0,1)
root (hd0,1)
kernel /puppy54/vmlinuz psubdir=puppy54
initrd /puppy54/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title Puppy Linux 5.4.3 pfix=ram (no pupsave file loaded, HD as hd0,1)
root (hd0,1)
kernel /puppy54/vmlinuz pfix=ram psubdir=puppy54
initrd /puppy54/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title FatDog64 version 611 (hard disk hd0,1)
rootnoverify (hd0,1)
kernel /fd64/vmlinuz
initrd /fd64/initrd
# Linux bootable partition config ends
# Linux bootable partition config begins
title FatDog64 Seamonkey 611 (hard disk hd0,1)
rootnoverify (hd0,1)
kernel /fd64Sea/vmlinuz
initrd /fd64Sea/initrd
# Linux bootable partition config ends
# grub --version
grub (GNU GRUB 0.97)
When booting and selecting either FatDog64 option I get the error:
Error 16: Inconsistent filesystem structure
I tried the root option and later changed it to rootnoverify with no change.
My puppy 5.4.3 boot works fine from grub. I'm not sure if I'm explaining this right :/
Thanks,
Rob
When the GRUB menu comes up, press the 'c' key.16 : Inconsistent filesystem structure
This error is returned by the filesystem code to denote an internal error caused by the sanity checks of the filesystem structure on disk not matching what it expects. This is usually caused by a corrupt filesystem or bugs in the code handling it in GRUB.
Type each of the three commands from your Fatdog menu.
Which one throws the error message?
The steprcrsn51 wrote:When the GRUB menu comes up, press the 'c' key.16 : Inconsistent filesystem structure
This error is returned by the filesystem code to denote an internal error caused by the sanity checks of the filesystem structure on disk not matching what it expects. This is usually caused by a corrupt filesystem or bugs in the code handling it in GRUB.
Type each of the three commands from your Fatdog menu.
Which one throws the error message?
initrd /fd64/initrd
is where the error message is returned.
Sorry for the delay responding... I was off researching the issue and didn't expect such a speedy reply. I was wondering if there was a way to mount the initrd as a loop device and do a file system check on it LOL.rdog wrote:The steprcrsn51 wrote:When the GRUB menu comes up, press the 'c' key.16 : Inconsistent filesystem structure
This error is returned by the filesystem code to denote an internal error caused by the sanity checks of the filesystem structure on disk not matching what it expects. This is usually caused by a corrupt filesystem or bugs in the code handling it in GRUB.
Type each of the three commands from your Fatdog menu.
Which one throws the error message?
initrd /fd64/initrd
is where the error message is returned.
Thanks,
Rob