Fatdog64-600 Final and 601 (July 2012)

[rcrsn51]

How to re-size save-file in fatdog 600

Control Panel > System > Fatdog64 Savefile Tool

[mini-jaguar]

question: is it normal that the package manager doesn't show all the installed packages? I don't have a problem with anything I installed and don't need to uninstall anything, but it just seems strange to me. It was the same in the alpha and beta versions too, but I didn't ask.

Also, is there an easy way to make a bootable USB stick with FatDog64 600 on it?

If you have highlighted "Install Packages", it shows available packages and the version that you have installed. When "Installed Packages" is highlighted, all packages installed are shown.

No, it does not show all the packages installed, I installed at least 3 .pet files, they all work and show up in the menus, but only one shows up in the package manager as installed. I had the same problem in the alpha and beta versions, and now in the final version.

If you want a concrete example, Audacity and Tuxkart are both installed and function, but Tuxkart does not show up in the manager.

[rcrsn51]

If you want a concrete example, Audacity and Tuxkart are both installed and function, but Tuxkart does not show up in the manager.

I just installed Tuxkart and checked in the Package Manager. Tuxkart WAS there. You may have to click the little triangle icon to see it.

[mini-jaguar]

Actually I figured out the problem, it's that they were not installed with the package manager, although in other Puppies all installed packages show up.

But maybe not, which little triangle do you mean?

[Jim1911]

[quote="mini-jaguar"]Actually I figured out the problem, it's that they were not installed with the package manager, although in other Puppies all installed packages show up.

But maybe not, which little triangle do you m
0ean?[/]

All installed packages show up. In my earlier post, at least two installed programs shown were not installed by package manager.

[irishrm]

rcrsn51:

Thanks for replying.

I had tried that before but having to boot with filesave=none threw me off I'm afraid.

Your reply told me I needed to get the old brain cells working a bit better.

This method makes the operation a little bit more difficult than the old way of doing it.
In my case having to navigate without a properly configured touch-pad was a little bit of an inconvenience.
However it was nothing more than that and I'm certainly not complaining.

I'm delighted with the way fatdog is working for me.

Thanks for pointing me in the right direction.

irishrm.

[Jim1911]

Attempting to resize my save file and I get this message. The savefile is working fine.

Sorry for the late reply. That's odd indeed, I'm assuming you actually have an ext4 savefile and created it normally during first shutdown. Do you still have that troublesome savefile? Do you mind opening terminal (when booting with pfix=ram) and do the following:

Code: Select all

guess_fstype /path/to/savefile

and also

Code: Select all

disktype /path/to/savefile

I had already deleted that save file although I have the same problem on two other save files on different ext4 partitions, sda2 and sdb2. Sda2 was formatted using FD64-600's version of gparted. Both save files are working properly.

Code: Select all

# guess_fstype /mnt/sda2/fatdog64-600F/fd64save.ext4
unknown
# guess_fstype /mnt/sdb5/fatdog64-600/fd64save.ext4
unknown
# disktype  /mnt/sdb5/fatdog64-600/fd64save.ext4

--- /mnt/sdb5/fatdog64-600/fd64save.ext4
Regular file, size 2.453 GiB (2634022912 bytes)
Ext4 file system
  UUID FFBB600F-E6DF-4B4D-9B13-183532C5F872 (DCE, v4)
  Last mounted at “/aufs/pup_save

[smokey01]

I installed the get_libreoffice package from the repo then ran it. It downloaded libreoffice and created the SFS which I loaded and this is the result. It's version 3.5.4.2

Hmmm, have you tried the libreoffice available in the SFSmanager? Does it have the same problem? Just want to establish whether the script is the problem or something else.[/code]

It appears the problem may have been caused by the 23oz theme. Once removed all worked fine.

[Billtoo]

Another day another fatdog install.

I made a fatdog600 final remaster, installed it to an 8gb flash drive with a
2gb savefile.
Using jwm + wbar.

[kickstart]

I have managed to persuade Fatdog to run on my desktop computer but as with other Puppy versions it doesn't pick up the raid0 array. Coincidentally I discovered that a version of the dmraid pet was uploaded to the nluug Fatdog repository earlier today which I have downloaded and installed. However the dm-mod kernel module does not load and with my insufficient knowledge I have been unable to see why. Has anyone else tried this pet yet or can anyone give me any clue as to why dm-mod refuses to load? This machine has to run Windows as well (for my better half!) so I am stuck with the requirement to use dmraid as there is a ton of data on the raid array that I need to access. I had no problems making dmraid work in Lucid but I would rather use Fatdog as my main OS.

[James C]

Still running Fatdog64-600 from multi-session DVD with basically no problems. Great job.

[Яadiøaktive TΣknik]

I have managed to persuade Fatdog to run on my desktop computer but as with other Puppy versions it doesn't pick up the raid0 array. Coincidentally I discovered that a version of the dmraid pet was uploaded to the nluug Fatdog repository earlier today which I have downloaded and installed. However the dm-mod kernel module does not load and with my insufficient knowledge I have been unable to see why. Has anyone else tried this pet yet or can anyone give me any clue as to why dm-mod refuses to load? This machine has to run Windows as well (for my better half!) so I am stuck with the requirement to use dmraid as there is a ton of data on the raid array that I need to access. I had no problems making dmraid work in Lucid but I would rather use Fatdog as my main OS.

I have used jamesbond's new compile of dmraid [the one now available as a .pet] and it mounts my raid0 without any problems. dmraid reports that it can mount the following controllers / arrays:

asr : Adaptec HostRAID ASR (0,1,10)
ddf1 : SNIA DDF1 (0,1,4,5,linear)
hpt37x : Highpoint HPT37X (S,0,1,10,01)
hpt45x : Highpoint HPT45X (S,0,1,10)
isw : Intel Software RAID (0,1,5,01)
jmicron : JMicron ATARAID (S,0,1)
lsi : LSI Logic MegaRAID (0,1,10)
nvidia : NVidia RAID (S,0,1,10,5)
pdc : Promise FastTrack (S,0,1,10)
sil : Silicon Image(tm) Medley(tm) (0,1,10)
via : VIA Software RAID (S,0,1,10)
dos : DOS partitions on SW RAIDs

This is working with both my RAID controllers. I also have a Silicon Image on I've yet to try. The command which mounts my Intel RAID array is embarrassingly simple:

Code: Select all

 dmraid -ay 

If that doesn't work for you, then I'd advise mounting the RAID however it worked in other puppy[s]. dmraid should work the same across distros I think? Unless I'm not understanding your problem.

[jamesbond]

Actually I figured out the problem, it's that they were not installed with the package manager, although in other Puppies all installed packages show up.

All installed packages show up. In my earlier post, at least two installed programs shown were not installed by package manager.

Jim1911 is right. You can manually check whether the "missing" packages are registered correctly - just open the file /root/.packages/user-installed-packages. If they are found inside but is not shown by the package manager, then it's a bug, let me know (please send the file to me). If they are not listed in that file to begin with ... well, try to install again and then check the file again, are they inside after that? If still not, let me know which package exactly and I'll try to duplicate that.

I had already deleted that save file although I have the same problem on two other save files on different ext4 partitions, sda2 and sdb2. Sda2 was formatted using FD64-600's version of gparted. Both save files are working properly.

Thanks Jim. Apparently guess_fstypes is not reliable for checking savefile. I will update the tool to use disktype instead.

It appears the problem may have been caused by the 23oz theme. Once removed all worked fine.

Thanks, that sounds good.

Another day another fatdog install.

You seem to have the knack to find interesting wallpapers

Still running Fatdog64-600 from multi-session DVD with basically no problems. Great job.

Thank you

However the dm-mod kernel module does not load

dm-mod module is built-in to the kernel and is automatically loaded at each boot. You don't need to load that manually. Яadiøaktive TΣknik can probably help you further than I can.


cheers!

[Billtoo]

Another day another fatdog install.

You seem to have the knack to find interesting wallpapers

I find them at:

http://www.desktopnexus.com/

Here's a good one I think.

[mini-jaguar]

Wow, I think I know that place and have drunk coffee there several times. Is it in Gambetta?

[jamesbond]

Hi Jamesbond and Kirk,
just been reminded of icon drive wobble.
FYI
fresh boot drive icons - ok
2,3,5,6,7,8,9,10,11,12 (4 was a extended partition)

open gparted
2,3,5,9,12,7,11,6,8,10 - mounted drives 2 and 3 did not move

close and reopen gparted
2,3,12,8,9,5,6,11,7,10
etc

DC

The wobble can be fixed by going to Control Panel -> Display -> Event Manager and changing the icon-size values from 64 to 63. I will make it 63 as the default in when I release consolidated fixes.

[irishrm]

When booting fatdog from USB install my savefile on occasion is not being loaded (doesn't happen that often)

Trying to follow the instructions in the faq's I did the following.

label fatdog
kernel vmlinuz
initrd initrd
append search
devwait=5

i.e. added devwait=5 as above.
Is this correct.

Thanks.

irishrm.

[rcrsn51]

Instead of searching for the savefile, open the Control Panel > Utilities and run the Savefile Argument Builder. It will create the correct boot argument so Fatdog doesn't have to search.

Also "waitdev=5" should probably be on the end of the append line. And it's NOT "devwait".

[irishrm]

rcrsn51:

Thanks again for the reply.

You really must concentrate when making changes.

I will delete my entry to syslinux file and go with your first suggestion.

irishrm.

[rcrsn51]

You may also need the waitdev=5 argument.