Fatdog64-600 alpha2

[LateAdopter]

Hello jamesbond

That's becase we don't have any other mirror at the moment.

nluug mirror the whole distro.ibiblo structure. Fatdog is here:

http://ftp.nluug.nl/ibiblio/distributions/fatdog/

It downloads at about 5x the speed

I downloaded the ISO on the 18th May at 10.30 gmt, not long after you announced it. So they must update it very promptly.

[jamesbond]

Hello jamesbond

That's becase we don't have any other mirror at the moment.

nluug mirror the whole distro.ibiblo structure. Fatdog is here:

http://ftp.nluug.nl/ibiblio/distributions/fatdog/

It downloads at about 5x the speed

I downloaded the ISO on the 18th May at 10.30 gmt, not long after you announced it. So they must update it very promptly.

Thank you, I don't know that. I've added this to the mirror list.

[jamesbond]

My first install was a boot from CD with the savefile on my NTFS harddrive.

Having done the USB install I transferred that savefile to the USB thinking that it would save me from having to redo the fixes that you and kirk had already helped me with.
Obviously the savefile hasn't travelled well so I'll delete it and start again.

No worries. The copied savefile should work - I routinely do that, and that is one of the compelling reasons of using puppy/ fatdog (only need copy one file to backup your data).

[Jim1911]

You mean Firefox binaries downloaded from mozilla site? Correct

All previous Fatdog uses Firefox compiled by kirk, not the official binaries. This is because standard official binaries require dependencies that are not included in Fatdog (mainly Dbus stuff).

Dbus is now included in Fatdog, but the official binaries now also require dbus-glib. Dbus glib is in the repo (refresh the package manager first). You also need to remove /usr/lib64/firefox (replace it with actual extract of firefox binary tarball). Firefox will launch. I didn't test further than that.

Knew that it had to be something simple, works great now, and it's at version 13.

Thanks,
Jim

[kirk]

Compiled LibreOffice-3.5.3.2 and uploaded a sfs to:

http://distro.ibiblio.org/pub/linux/dis ... g/sfs/600/

[irishrm]

kirk:
jamesbond:

Created a new savefile in my USB install.
Much better result this time but I still have the same problem with my downloads.

Downloads from the fatdog repro or from any-other source end up in temp.
When I try to copy or move a download I get the error message "operation not allowed".

You have not been able to replicate the problem so It must be confined to my system and install.
I won't ask you to waste anymore time on it.

I will continue to look at the problem, maybe It would be worthwhile downloading the iso again and starting from scratch.

If I can't find a solution then I can wait for the final release, I'm sure that will work.
irishrm.

[gcmartin]

Compiled LibreOffice-3.5.3.2 and ...

Please recommend steps that LIve media users, like myself, can run a system where the SFS is installed as a permanent part of the system. Usually this is done when a reboot is done and the system offers to save-session.

Question
Is the new FATDOG PPM to be SFS based and the system will retain the added subsystems via save-session for reboot of the LIve media?.

There's a lot of new innovation coming our way in this distro.

Thanks in advance for the steps you recommend.

[WillM]

jamesbond wrote

Do you mind sharing this for the rest of us?

Gladly

To display the working directory in the Title Bar,
I have the following in ~/.bashrc;

Code: Select all

PS1="\[\e]2;Rxvt  \w\a\e[32;1m\]\W $\[\e[0m\] " 

For tabs, enter this in ~/.Xdefaults.

Code: Select all

URxvt.perl-ext-common:  default,tabbed

Urxvt needs to be compiled with --enable-perl for tabs to work.

Press Shift + Down Arrow to create a new tab.
Shift+ Left or Right Arrow to go to another tab
Ctrl + Left or Right Arrow to move a tab.
Ctrl + D to close a tab

[jamesbond]

Downloads from the fatdog repro or from any-other source end up in temp.

Download from Package Manager will be stored in /tmp - this is normal.
Download from web browser should be stored in /root/spot/Downloads - anything else isn't normal.

When I try to copy or move a download I get the error message "operation not allowed".

If what you mean is that you're trying to copy the files to somewhere *outside the savefile* (any where in /mnt/home), ie, to your USB flash drive itself, then yes the message is normal (fat32 doesn't support chmod so it will fail, but the files will be copied correctly). I will try to remove this message in the next release.

You have not been able to replicate the problem so It must be confined to my system and install. I won't ask you to waste anymore time on it.

Yes, sorry, the above is the only case I can reproduce, I can't reproduce anything else.

I will continue to look at the problem, maybe It would be worthwhile downloading the iso again and starting from scratch.

You can check the md5sum of the ISO?

If I can't find a solution then I can wait for the final release, I'm sure that will work.
irishrm.

[jamesbond]

Compiled LibreOffice-3.5.3.2 and ...

Please recommend steps that LIve media users, like myself, can run a system where the SFS is installed as a permanent part of the system. Usually this is done when a reboot is done and the system offers to save-session.

Question
Is the new FATDOG PPM to be SFS based and the system will retain the added subsystems via save-session for reboot of the LIve media?.

There's a lot of new innovation coming our way in this distro.

Thanks in advance for the steps you recommend.

Alpha2 currently has a bug that prevents it from loading SFS in multisession mode. I will try to get this working on next release.

EDIT: It is actually working. Please see instructions on first page.

[Billtoo]

I booted the live dvd and had it create a save file and saved it to a
flash drive.
Next bootup from the dvd I tried to get the savefile on the flash
drive to load (tried several times with several different "fatdog
savefile=direct:usb" etc. but nothing worked, settings all lost.
Finally I copied the save file from the flash drive to the hard drive and
booted up the live dvd and used "fatdog savefile=direct:local"
I was given a choice of save file to load and it worked with my initial
settings correct.

I was able to install the devx and then install the proprietary Nvidia
driver, after removing the nouveau driver.

hardinfo couldn't create a report (permissions problem) so I compiled
the source and installed that.

Computer
Processor 8x Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
Memory 16394MB (369MB used)
Operating System Unknown distribution
User Name root (root)
Date/Time Mon 21 May 2012 08:16:54 PM EDT
Display
Resolution 1920x1080 pixels
OpenGL Renderer GeForce GTX 560 Ti/PCIe/SSE2
X11 Vendor The X.Org Foundation
Multimedia
Audio Adapter HDA-Intel - HDA Intel PCH
Audio Adapter HDA-Intel - HDA NVidia
Version
Kernel Linux 3.3.4 (x86_64)
Compiled #1 SMP Fri May 4 23:40:44 GMT 2012
C Library GNU C Library version 2.13 (stable)
Default C Compiler GNU C Compiler version 4.6.2 (GCC)
Distribution Unknown distribution

OpenGL
Vendor NVIDIA Corporation
Renderer GeForce GTX 560 Ti/PCIe/SSE2
Version 4.2.0 NVIDIA 295.53
Direct Rendering Yes

Network controller Ralink corp. RT3090 Wireless 802.11n 1T/1R PCIe

It took a while to get there but this is working well now.

[Jim1911]

I’ve discovered another incompatible program.

Installed wine-1.5.4-i486_v1.pet after first loading fd64-32bit-libs-3.sfs. Wine appears to be working well, and I’ve run some Windows programs under it.

However, the Wine installation somehow broke the Package Manager. When trying to execute it comes up with a message “Refreshing list of installed packages...

[jamesbond]

You mean Firefox binaries downloaded from mozilla site? Correct

All previous Fatdog uses Firefox compiled by kirk, not the official binaries. This is because standard official binaries require dependencies that are not included in Fatdog (mainly Dbus stuff).

Dbus is now included in Fatdog, but the official binaries now also require dbus-glib. Dbus glib is in the repo (refresh the package manager first). You also need to remove /usr/lib64/firefox (replace it with actual extract of firefox binary tarball). Firefox will launch. I didn't test further than that.

Knew that it had to be something simple, works great now, and it's at version 13.

Thanks,
Jim

Next release will fix this for you (libdbus_glib will be in the main sfs) so you don't need to go through this hoops again. Just download official firefox binaries and you're good to go.

[jamesbond]

I booted the live dvd and had it create a save file and saved it to a
flash drive.
Next bootup from the dvd I tried to get the savefile on the flash
drive to load (tried several times with several different "fatdog
savefile=direct:usb" etc. but nothing worked, settings all lost.

600 doesn't wait USB storage (flash drive etc) to be ready, because there is simply no reliable way of doing it (other than waiting and waiting and waiting ...). Thus you need to specify "waitdev=n" where "n" in the number of seconds to delay for the USB devices to settle and be ready. In my laptop, 3 seconds are enough. Yours may vary.

[jamesbond]

hardinfo couldn't create a report (permissions problem) so I compiled
the source and installed that.

Permission problem? When generating the report? I just run hardinfo (as multisession) and it seems to be working fine (it saves the report to /root)... Can you reproduce the issue?

[jamesbond]

jamesbond wrote

Do you mind sharing this for the rest of us?

Gladly

Thank you, will bookmark this post

[Billtoo]

hardinfo couldn't create a report (permissions problem) so I compiled
the source and installed that.

Permission problem? When generating the report? I just run hardinfo (as multisession) and it seems to be working fine (it saves the report to /root)... Can you reproduce the issue?

It was my mistake, sorry.I got the error because I had loaded the
wrong devx the first boot after copying the savefile from the flash
drive to the hard drive and using fatdog savefile=direct:local
With the proper devx loaded there is no error, I guess there would be
no error if no devx was loaded too.

I still can't get the savefile on the flash drive to load, I've tried
putting waitdev=15 before and after the savefile=direct:usb so I'm
doing something wrong.

[jamesbond]

It was my mistake, sorry.I got the error because I had loaded the
wrong devx the first boot after copying the savefile from the flash
drive to the hard drive and using fatdog savefile=direct:local
With the proper devx loaded there is no error, I guess there would be
no error if no devx was loaded too.

Yes, due to the new layering model, if you load the wrong devx, its library can hide Fatdog64 libraries and you'll get this problem. The SFS tool will allow you to load any SFS - so you need to exercise caution

I still can't get the savefile on the flash drive to load, I've tried
putting waitdev=15 before and after the savefile=direct:usb so I'm
doing something wrong.

Try this: savefile=direct:device:sdb1:/fd64save.ext4. Replace sdb1 with your flash drive; fd64save.ext4 with the name of your savefile. Put the waitdev parameter, try waitdev=5 (I think 15s is an extremely long delay). If this still doesn't work, use the "earlyshell" parameter. This will drop you to a shell in initramfs, you can check to see whether your flash drive is detected by running "blkid". When done, type "exit" to continue booting.

[Billtoo]

Try this: savefile=direct:device:sdb1:/fd64save.ext4. Replace sdb1 with your flash drive; fd64save.ext4 with the name of your savefile. Put the waitdev parameter, try waitdev=5 (I think 15s is an extremely long delay). If this still doesn't work, use the "earlyshell" parameter. This will drop you to a shell in initramfs, you can check to see whether your flash drive is detected by running "blkid". When done, type "exit" to continue booting.

This worked:

fatdog waitdev=5 savefile=direct:device:sdb1:/fd64save.ext4

Well it ought to be easy from now on since I have this written down in
my notebook

Thanks

[jamesbond]

This worked:

fatdog waitdev=5 savefile=direct:device:sdb1:/fd64save.ext4

Well it ought to be easy from now on since I have this written down in
my notebook

Thanks

You can try to reduce the waitdev (perhaps 3 seconds is enough?) You can also drop the filename (just use direct:device:sdb1) if the filename is fd64save.ext4.

BTW - notice for all multisession users --- SFS does not work at the moment and if you use it will disable you from saving future sessions.

This will be fixed in next release.