(old)Puppy Linux Discussion Forum

Posted: **Mon 14 Jan 2013, 23:18**

@HiDeHo, the savefile arguments are changed in fatdog, psubdir does not work anymore. You can see the new boot options in the FAQ.

There is also a savefile argument builder in the control panel:
Menu>ControlPanel>Utlities>Savefile Argument Builder

Posted: **Tue 15 Jan 2013, 01:02**

HiDeHo have another look at my menu.lst above.

Fatdog allows you to load a savefile from anywhere.

Try the help in Fatdog. It has a lot of good information which includes boot options.

Posted: **Tue 15 Jan 2013, 02:52**

Barbol wrote:@HiDeHo, the savefile arguments are changed in fatdog, psubdir does not work anymore. You can see the new boot options in the FAQ.

There is also a savefile argument builder in the control panel:
Menu>ControlPanel>Utlities>Savefile Argument Builder

thanks that is the FAQ on the default browser homepage found thanks. i am getting there its just trial and error.

at least that has cleared things up for me.

Posted: **Tue 15 Jan 2013, 17:48**

ey guys,

can i install Java RE directly from firefox for example:
additional plugins are required to display this page -> install missing plugins -> Java Run Enviornment
or should i install the full sfs version from the repository?

@smokey: 'open with geany' works for me while 'open as text' doesn't... let me check more permission settings[/quote]

Posted: **Tue 15 Jan 2013, 20:18**

jamesbond wrote:are you using UTF8 locale?

Nope, my bad.. it was setted to en_US. I guess that the first time I ran fatdog I looked for a spanish locale, but it wasn't available so I left the default one. I assumed by the "not valid UTF-8 names" advices that the system was already using UTF8 locale.

But yesterday I found that non-english locales are available when the devx.sfs is loaded, so now I got es_AR.UTF-8 selected. Problem solved with Xdialog boxes.

Also, what is the filesystem you're having problem with? I always assume it is FAT (because ext2/3/4 works, I think NTFS works too), but is it?

Yes, it is a FAT filesystem indeed. I created some testing files from ubuntu and racy, both of them using es_AR.UTF-8 locale. All the files were displayed correctly in an ext3 partition, but appeared as no valid UTF8 files in the FAT one.
I don't have a NTFS filesystem right now (it dissapeared from my machine along with windoze the day I accidentaly boot the 2D2 recovery Vista, which deleted all my linux and data partitions.

Fortunately Testdisk allowed me to recover everything)
I'll make one for testing..

Thanks again! Barbol

Posted: **Wed 16 Jan 2013, 00:44**

well i have been studding the FAQ boot options page.
still a bit hard to understand the fraising of the options. and nothing seems to work.

here is my latest attempt

Code: Select all

title Fd64 611 (sdb2/Fatdog)
  savefile=ram:uuid:ceafdec4-2abc-4e42-ae42-7f0df00deeb8:/Fatdog/fd64-611-save.ext4
  kernel /Fatdog/vmlinuz waitdev=5 search=2 
  initrd /Fatdog/initrd

this gives an error cannot find file.

recap:
This works but wont load the save file

Code: Select all

title Fd64 611 (sdb2/Fatdog)
  find --set-root --ignore-floppies --ignore-cd /Fatdog/initrd
  kernel /Fatdog/vmlinuz  
  initrd /Fatdog/initrd

I have a usb hdd with
partition 1: fat32 for bootloader (use grub4dos).
partition 2: ext4 for several puppy os
fatdog is on partition 2 in folder /Fatdog/

Posted: **Wed 16 Jan 2013, 03:58**

here is my latest attempt
Code:
title Fd64 611 (sdb2/Fatdog)
savefile=ram:uuid:ceafdec4-2abc-4e42-ae42-7f0df00deeb8:/Fatdog/fd64-611-save.ext4
kernel /Fatdog/vmlinuz waitdev=5 search=2
initrd /Fatdog/initrd
this gives an error cannot find file.

HiDeHo, the savefile parameter goes in the kernel line. Mine looks like this:

kernel /puppy610-fatdog/vmlinuz savefile=direct:device:sda5:/puppy610-fatdog/fd64save.ext4

You can use the Savefile Argument Builder in the Control Panel and add its output to the "kernel" line in menu.lst
Good luck!

Posted: **Wed 16 Jan 2013, 06:17**

Barbol wrote:HiDeHo, the savefile parameter goes in the kernel line. Mine looks like this:

kernel /puppy610-fatdog/vmlinuz savefile=direct:device:sda5:/puppy610-fatdog/fd64save.ext4

You can use the Savefile Argument Builder in the Control Panel and add its output to the "kernel" line in menu.lst
Good luck!

thanks Barbol that did the trick. now it works for me

Code: Select all

title Fd64 611 (sdb2/Fatdog)
  find --set-root --ignore-floppies --ignore-cd /Fatdog/initrd
  kernel /Fatdog/vmlinuz waitdev=5 search=2 savefile=ram:uuid:ceafdec4-2abc-4e42-ae42-7f0df00deeb8:/Fatdog/fd64-611-save.ext4
  initrd /Fatdog/initrd

Posted: **Wed 16 Jan 2013, 06:38**

Hi here are a few things that would be good to have as standard in fatdog in the future. I am not sure if some of these are already setup.

all browsers should run as spot by default
pidgin should run as spot by default
the adobe flash player settings has some issues. when click on the playback tab it shuts down. when click on check for updates nothing happens.

here are the first few things I have noticed will keep testing and see what else I find.

Posted: **Wed 16 Jan 2013, 06:59**

HiDeHo wrote:Hi here are a few things that would be good to have as standard in fatdog in the future. I am not sure if some of these are already setup.
all browsers should run as spot by default

pidgin should run as spot by default
the adobe flash player settings has some issues. when click on the playback tab it shuts down. when click on check for updates nothing happens.
here are the first few things I have noticed will keep testing and see what else I find.

In the Seamonkey version, Seamonkey and Pidgin are set to run as spot by default. Look in /usr/local/bin for defaultbrowser and defaultchat then open with geany and you will see what I mean.

Another test is to try and download a file. It will place it in /root/spot/downloads which is probably symlinked to /mnt/home.

I have the same problem as HiDeHo with flash player preferences in the control panel.

Cheers

Posted: **Wed 16 Jan 2013, 11:00**

more things i have found.

QuickApps: i found the file to setup QuickApps (cant find it again though) i ran the file and added the folders and apps i wanted. then closed. i found the file /root/QucikApps. when i click on it i get a message

no applet definitions found

i cant run the app or find the setup app again. this does not work.
FAQ How can I make a new pet Package?: this is good but it fails to mention the need for the devx app which is usually needed in puppy for compiling apps. does fatdog not need this ??? would be nice to link to the puppy forums / info for more detailed steps only if it relevant to fatdog though. (be nice to mention the need for 64bit source code as a reminder)
FAQ missing sfs creation info: would be nice to have info on how to create sfs files for use in fatdog.

Posted: **Wed 16 Jan 2013, 11:13**

smokey01 wrote:In the Seamonkey version, Seamonkey and Pidgin are set to run as spot by default. Look in /usr/local/bin for defaultbrowser and defaultchat then open with geany and you will see what I mean.

yes i see that the browser and pidgin are set to run as user spot (also the iron browser sfs app runs in user spot)
exec firefox-spot. in other puppy versions they use su spot -c firefox

smokey01 wrote:Another test is to try and download a file. It will place it in /root/spot/downloads which is probably symlinked to /mnt/home.

actually /root/downloads is linked to /root/spot/downloads which is linked to /home/Fatdog/downloads here(i assume the downloads folder goes in the same folder as the save file or /and the other 2 main puppy files

smokey01 wrote:I have the same problem as HiDeHo with flash player preferences in the control panel

nice to know i am not the only one with this problem
[/quote]

Posted: **Thu 17 Jan 2013, 12:22**

HiDeHo wrote:more things i have found.

QuickApps: i found the file to setup QuickApps (cant find it again though) i ran the file and added the folders and apps i wanted. then closed. i found the file /root/QucikApps. when i click on it i get a message
no applet definitions found
i cant run the app or find the setup app again. this does not work.

1. Setup app always accessible by running menu Personal --> QuickApps.
2. Or otherwise you can open /root folder, right-click on QuickApps and choose "Look Inside". Then create a directory there, then create symlink *inside* the directory.
3. If you are not happy with it, just delete the QuickApps folder and start again (or not).

FAQ How can I make a new pet Package?: this is good but it fails to mention the need for the devx app which is usually needed in puppy for compiling apps. does fatdog not need this ??? would be nice to link to the puppy forums / info for more detailed steps only if it relevant to fatdog though. (be nice to mention the need for 64bit source code as a reminder)

I thought it is obvious enough that if you want to compile you will need devx. Also, there is no such thing as 64-bit source code - source code is source code.

FAQ missing sfs creation info: would be nice to have info on how to create sfs files for use in fatdog.

Same as in other puppies, use dir2sfs.

actually /root/downloads is linked to /root/spot/downloads which is linked to /home/Fatdog/downloads here(i assume the downloads folder goes in the same folder as the save file or /and the other 2 main puppy files

Don't assume, if when you create savefile you un-tick "move Downloads folder save device" then it is not moved and stays in the savefile. Otherwise it is moved to where your savefile is (when you originally created it).

nice to know i am not the only one with this problem

This is a known problem for quite sometime. I don't have any solution and google refuses to help me. strace reveals nothing. Source code is not available for debugging. The joy of closed source software

But yesterday I found that non-english locales are available when the devx.sfs is loaded

Yes correct, you can also get the other locales from the package manager - but that will fill up your savefile. If you can run with devx always attached, all the better

Yes, it is a FAT filesystem indeed

I haven't tested this for a long time. When I use FAT I always make sure I use ASCII. I will do some test and get back to you.

Posted: **Thu 17 Jan 2013, 21:32**

I wanted to know if FATDOG has KVM support in its system.

I ran the following command and the output looks a little odd. Should it had been duplicated?

Code: Select all

# egrep '^flags.*(vmx|svm)' /proc/cpuinfo
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good nopl extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good nopl extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy

How_can_I_tell_if_I_have_Intel_VT_or_AMD-V.3F?
Is the SVM flag accurate reflection for KVM?

Thanks in advance.

Posted: **Thu 17 Jan 2013, 22:20**

Cool, a 64bit Puppy. I am downloading it now.

Posted: **Fri 18 Jan 2013, 00:26**

gcmartin wrote:I wanted to know if FATDOG has KVM support in its system.

Of course. When running as root:
1. Check for CPU capability: from terminal type "lscpu"
2. To get it going: for AMD, type this on terminal "modprobe kvm-amd". For Intel, type this on terminal "modprobe kvm-intel"
3. Get the qemu package from the pet repo
4. On terminal, run qemu like this: "qemu-system-x86_64 -enable-kvm -m 1024 -cdrom fatdog.iso" and you're good to go.

Posted: **Fri 18 Jan 2013, 01:49**

Code: Select all

# modprobe kvm-amd
# lscpu
sh: lscpu: command not found
# pwd
/root
# whoami
root
# lscpu
sh: lscpu: command not found
# uname -r
3.4.18
#

"lscpu" command doesn't return results. I think there is something wrong with my desktop's terminal. Same terminal window where I had duplication shown in earlier post.

Ideas anyone???

Posted: **Fri 18 Jan 2013, 02:03**

There are several QEMU packages in the PPM. What's confusing is the ARM designation in the filename.. Is this the correct one to download for the X2 CPU?

Posted: **Fri 18 Jan 2013, 02:18**

gcmartin wrote:"lscpu" command doesn't return results. I think there is something wrong with my desktop's terminal. Same terminal window where I had duplication shown in earlier post.

Sorry, "lscpu" is only available in devx. Anyway, no need for that command, just to straight to step 2 onwards.

Yes, that's the correct package - see the attached image. I really should remove the old qemu package.

Barbol, I did a quick test on FAT, as long as when I created the file when I was in UTF8 locale, the filename shows correctly on both Rox and terminal. Let me know how it goes with you.

Posted: **Mon 21 Jan 2013, 18:44**

Barbol, I did a quick test on FAT, as long as when I created the file when I was in UTF8 locale, the filename shows correctly on both Rox and terminal. Let me know how it goes with you.

Jamesbond, the problem are the special spanish characters, the files in red are the ones containing those characters. It seems that fatdog is not using UTF-8 encoding when mounting FAT partitions. But I think I found a solution for this, adding the 'utf8' in the mount options does the trick:

Code: Select all

# mount | grep sda7
/dev/sda7 on /mnt/sda7 type vfat (rw,relatime,fmask=0027,dmask=0027,codepage=cp850,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
# ls /mnt/sda7/Test/*
/mnt/sda7/Test/?and?_Debian-6.0.6   /mnt/sda7/Test/?and?_Slacko-540
/mnt/sda7/Test/?and?_Lubuntu-12.04  /mnt/sda7/Test/Ñandú_Fatdog64-610
/mnt/sda7/Test/?and?_Racy-530       /mnt/sda7/Test/??????????_ubuntu-10.04

/mnt/sda7/Test/Racy:
??????????.VT  ??????????.X

/mnt/sda7/Test/Ubuntu.10.04:
??????????.C  ??????????.X
# umount /mnt/sda7
# mount -t vfat -o utf8 /dev/sda7 /mnt/sda7
# mount | grep sda7
/dev/sda7 on /mnt/sda7 type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
# ls /mnt/sda7/Test/*
/mnt/sda7/Test/Ã?andÃº_Fatdog64-610  /mnt/sda7/Test/Ñandú_Racy-530
/mnt/sda7/Test/Ñandú_Debian-6.0.6    /mnt/sda7/Test/Ñandú_Slacko-540
/mnt/sda7/Test/Ñandú_Lubuntu-12.04   /mnt/sda7/Test/ñáñìñüñẽñô_ubuntu-10.04

/mnt/sda7/Test/Racy:
ñáñìñüñẽñô.X  ñáñìñüñõñê.VT

/mnt/sda7/Test/Ubuntu.10.04:
ñáñìñüñêñô.C  ñáñìñüñẽñô.X
#

I added the 'utf8' option in fatdog-drive-icon-mount-helper.sh and voilà! no more red files in Rox.
I tested ntfs too, no issues with special chars there..

Here is a nice link with a lot of info (in spanish) regarding all encoding stuff for spanish speakers. Maybe it helps others too:
http://www.vicente-navarro.com/blog/200 ... aracteres/

If you can run with devx always attached, all the better

I ran localdef and a folder named es_AR.utf-8 was created in the savefile. Is anything else needed? I unloaded the devx.sfs and the spanish locale seems to be working still.

Barbol

(old)Puppy Linux Discussion Forum

Fatdog64-611 Final (Updated 12-14-2012)