Fatdog64-710 beta [28 August 2016] [CLOSED]

[Wognath]

...import old save folder to new FD ?

...certain config files are re-written and the new scripts won't work with old config files that didn't have a good value defined in them.

Thanks for the explanation. There's no problem with documents since root sans config files imports ok. Customizations and apps little by little.
Thanks again for all the work that went into this.

[drunkjedi]

Latest Google Chrome SFS added to Fatdog contributor thread
http://murga-linux.com/puppy/viewtopic. ... 974#921974

[Sage]

Had a chance to test. Only one comment - you guys must be extremely proud of your efforts. Few distros come as close - everything there, all working OOTB. Well done.

[gcmartin]

Thanks James, but my question was really about this for what you used in your description of steps for a USB that boots and possibly boots several OSes.

Thanks in advance if you could share that.

[jamesbond]

Had a chance to test. Only one comment - you guys must be extremely proud of your efforts. Few distros come as close - everything there, all working OOTB. Well done.

Coming from you Sage, this makes it precious Thank you for testing.

And thank you for all who have tested and ontributed in other means: packages, feedbacks, helping one another, etc.

@gcmartin: As I've said, I used mbr partition table. Wikipedia helps in case you're not clear: https://en.wikipedia.org/wiki/Master_boot_record.

cheers!

[gcmartin]

Yes I know that. The question could have been more specificly asking which does your GParted utility show as your partition table. I have found some use of gpt on USB for modern Wins requirements which work equally for Linux boot needs.

Thanks, anyway.

[Billtoo]

I installed to a 64gb usb-3.0 flash drive, computer is a hp desktop.

video-info-glx 1.5.3 Wed 7 Sep 2016 on Fatdog64 710 Linux 4.4.18 x86_64
0.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1)
oem: NVIDIA
product: GF108 Board - 1071v1p1 Chip Rev

X Server: Xorg Driver: nvidia
X.Org version: 1.18.3
dimensions: 3200x900 pixels (883x251 millimeters)
depth of root window: 24 planes

direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 430/PCIe/SSE2
OpenGL core profile version string: 4.3.0 NVIDIA 367.44

Intel(R) Core(TM) i5-3550 CPU @ 3.30GHz
Core 0: @1661 1: @1663 2: @1696 3: @1607 MHz

No problems.

[smokey01]

qt5-5.5.1.sfs doesn't exist at ibiblio or aarnet but does at nluug and UOC.

How can that be? Has it been pulled?

[jamesbond]

smokey01,

We have moved to qt-5.6.1.sfs. I think kirk pulled the older qt-5.5.1. qt-5.6.1 fixed a few bugs and as far as we know is backward compatible with qt-5.5.1.

If you do need qt-5.5.1.sfs let me know I will re-upload it again.

PS: RC coming out soon.

[ryukisai]

@drunkjedi, wyzguy, Jamesbond, thanks a lot for the feedback!
I read your suggestions, but I didn't have the time to test or reply. Sorry about that.

I just tried James bond's solution this afternoon. Well I did as you said except for bios bootloader installation. I didn't have the time to try and install it manually. So I just ran the fatdog install over the efi prepared partition. I still have to test this install more to make sure everything is ok. I will report as soon as possible!

[MaxPonozka]

there is an bug in /bin/ln when creating a link twice:

on FatDog64-700 it is ok:
# mkdir /tmp/test
# ln -s /tmp/test /root/testlink
# ln -s /tmp/test /root/testlink
ln: failed to create symbolic link '/root/testlink': File exists
#

but now there is no error message, but a additional wrong link:
# mkdir /tmp/test
# ln -s /tmp/test /root/testlink
# ls -l /root/testlink/
total 0
# ln -s /tmp/test /root/testlink
# ls -l /root/testlink/
total 0
lrwxrwxrwx 1 root root 9 Sep 14 08:37 test -> /tmp/test
#

[quirkian2new]

I applied Ted Dog's "uefi.zip" and prepared a FAT32 bootable usb flash(containing menu entry Fatdog701.iso). Firstly I successfully tested that this usb is bootable on one of my machine. Then I use it to boot another machine (HP Pavilion with win8.1 pre-installed). I followed every step(step 1 to step 8 ) as suggested in the below link:

http://distro.ibiblio.org/fatdog/web/fa ... -boot.html

I also turn off fast boot in this HP Pavilion win8.1 After reboot, the "grub.cfg" was successfully processed and I was presented with the options in "grub.cfg". But when I press enter for selecting Fatdog701.iso, the HP Pavilion screen goes black and nothing happens. I wait about ten minutes and have to unplug the electric socket brutally.

Jamesbond and fellow FD64 users, can anyone give me some guidance as what is the problem and what steps I have missed. many thanks

[jamesbond]

@MaxPonozka: that's how "ln" is supposed to work.

@quirkian2new: please try to boot using the "dd" method. Ted Dog's method uses loop device, I'm under the impression that it requires more memory that normal dd method. I may be wrong, but the "dd" method is worth trying.

[gcmartin]

@Jamesbond. I dont remember a dd image file which boots FD7's ISO. Is there a link somewhere for it? I am aware of the ability to dd the contents of the FD7 DVD system for booting, but not aware of any that boots an enclosed FD7.iso file on the constructed USB.

This would be an added benefit to users like myself because future new FD ISO files could be added allowing a BM update to selectively boot any of the FD ISO files on/added to the USB. The ISO image(s) is so small that this would be a practical feature in the dd image. I am aware that booting an ISO directly does NOT come with the speed of booting the filesystem, yet, it does provide a flexibility option. If, of course, it is available currently.

Thanks in advance.

[jamesbond]

@gcmartin: there is no official "dd" method to boot Fatdog.iso. The "dd" method I said earlier is this one: http://distro.ibiblio.org/fatdog/web/fa ... drive.html, which you already know.

I'll leave multi-booting and booting direct from ISO to those who specialise in taking care of boot-loaders. They are interesting but not core to Fatdog.

[s243a]

The clock is an hour off.

I set the time zone to Canada Mountain time. In other versions of puppy there was an option to set the time from the internet, and then you select a time server. I don't see such an option on fatdog64.

The problem is that daylight savings time may differ from region to region in the world so simple arithmetic based on the time zone may fail.

[s243a]

On another note, how come when I use the install tool, it doesn't ask me what folder that I want to install to?

[s243a]

Other Observations:
1. If you set the timezone before creating the save file, the system doesn't remember this and asks you to pick the timezone again.

2. Your allowed to create a savefolder that doesn't start with fdsave but the system cannot find the save folder upon start-up if it doesn't start with fdsave. A warning should be given if the user picks a save-folder name that doesn't start with fdsave. I was able to fix this by simply renaming the folder and re-booting.

[jamesbond]

Thank you for testing and feedback.

The clock is an hour off. I set the time zone to Canada Mountain time.

Did you use Control Panel to change it?
Did you choose Olson (named) timezone, instead of the usual GMT+offset timezone?
Did you specify to use UTC for the hardware clock?

What I use:
a) I use UTC for hardware clock.
b) I use the named region timezone.
c) I have my clock adjusted for DST automatically.

Any other settings, and you'll have to live with their limitation.

In other versions of puppy there was an option to set the time from the internet, and then you select a time server. I don't see such an option on fatdog64.

Control Panel -> System -> Manage Servers and Services -> enable "ntpd-boot" service.

On another note, how come when I use the install tool, it doesn't ask me what folder that I want to install to?

Installation to a subdir is "expert" option. The installer tool is for newbies. It makes things as simple as possible. If you already know how to install grub and edit menu.lst, really all you need is copy "vmlinuz" and "initrd" to any location you want. See: http://distro.ibiblio.org/fatdog/web/fa ... drive.html.

1. If you set the timezone before creating the save file, the system doesn't remember this and asks you to pick the timezone again.

Sorry, can't reproduce the problem here.

2. Your allowed to create a savefolder that doesn't start with fdsave but the system cannot find the save folder upon start-up if it doesn't start with fdsave. A warning should be given if the user picks a save-folder name that doesn't start with fdsave.

I don't know which version you tested. This beta version obviously warns you that, see screenshot.

[s243a]

Thank you for testing and feedback.

The clock is an hour off. I set the time zone to Canada Mountain time.

Did you use Control Panel to change it?
Did you choose Olson (named) timezone, instead of the usual GMT+offset timezone?
Did you specify to use UTC for the hardware clock?

What I use:
a) I use UTC for hardware clock.
b) I use the named region timezone.
c) I have my clock adjusted for DST automatically.

Any other settings, and you'll have to live with their limitation.

In other versions of puppy there was an option to set the time from the internet, and then you select a time server. I don't see such an option on fatdog64.

Control Panel -> System -> Manage Servers and Services -> enable "ntpd-boot" service.

Thankyou, ntpd-boot service worked. However, without this service, setting the clock by the time zone did not work with either UTC or "Local time zone" hardware clock configuration. Perhaps the dependency is either hardware dependent or an issue with the linux kernal. Anyway, to try to reproduce the error turn off "ntpd-boot", set the time to an incorrect time, and then try setting the time by the time zone "specifically Canada Mountain time". Then google the time in Calgary and see if the clocks match.