Fatdog64-620 Final (17 April 2013) and 621 (9 May 2013)

[Ted Dog]

Yea, my new 64bit netbook works perfectly so far with fatdog64v621, Took out the win 8 harddrive, plugged in my portable USB DVD burner and here I am. Forgot the switch to load to ram so I can eject the DVD to play stuff, but I will next boot.

[DrDeaf]

Yea, my new 64bit netbook works perfectly so far with fatdog64v621, Took out the win 8 harddrive,

I went 64 bit in October and did the same thing.

plugged in my portable USB DVD burner and here I am. Forgot the switch to load to ram so I can eject the DVD to play stuff, but I will next boot.

I never had that issue, but it was slow. So, your new machine surely has USB3. Just put 621 on a fast flash device. It will boot very quickly and your burner will be always free.

[nooby]

Delta file from FD620 >>> FD621

http://www.smokey01.com/software/iso/Fa ... .iso.delta

I have no clue what one are supposed to do with delta
maybe you can have the 621 iso there too. Just a suggestion

[Ted Dog]

Yea, my new 64bit netbook works perfectly so far with fatdog64v621, Took out the win 8 harddrive,

I went 64 bit in October and did the same thing.

plugged in my portable USB DVD burner and here I am. Forgot the switch to load to ram so I can eject the DVD to play stuff, but I will next boot.

I never had that issue, but it was slow. So, your new machine surely has USB3. Just put 621 on a fast flash device. It will boot very quickly and your burner will be always free.

Redid the DVD copy with the correct settings and tried the USB3, the DVD loaded like a rocket. Actually too fast, need to put a waitdev in there again.

BTW I discovered why the remaster was slower with isolinux.bin the burning progam or hybridiso patched or repatched isolinux.bin so you can't reuse the one found on the burned media, a fresh copy needs to come from /usr/share/syslinux for each remaster.

Discover this as a warning in the documentation about using level 2 with older version of other toolsets like hybridiso, or burning programs like growisofs.

[Ted Dog]

Delta file from FD620 >>> FD621

http://www.smokey01.com/software/iso/Fa ... .iso.delta

I have no clue what one are supposed to do with delta
maybe you can have the 621 iso there too. Just a suggestion

This is used to move from 620 to 621 if you already downloaded 620, the links to full 621 are on the first page of this topic, second msg from top. The delta file is to save bandwidth for us still stuck in the internet dark-age and/or pay by the bandwidth used. The delta between the last two versions is less than 2MB

[nooby]

google to rescue here
Upgrading your Puppy using .delta files...
http://www.murga-linux.com/puppy/viewtopic.php?t=58435
but points to this text which worked
http://www.murga-linux.com/puppy/viewtopic.php?t=52232

I make a quote in case others wants to know
quote
Save the original .iso and the new .delta in the same directory, this is not essential but will save some searching time
* Simply click the .delta file and the Xdelta gui will appear

* Click GENERATE
* You should see a green splash screen indicating that the new file is generated and there will be a new .iso file in the same directory as the .delta file. Again, compare the checksum with the one provided by the developer. All should be well.
* You can now proceed to burn your new iso image with your favourite burning software.
/quote

[gcmartin]

Yea, my new 64bit netbook works perfectly so far with fatdog64v621, Took out the win 8 harddrive,

I went 64 bit in October and did the same thing.

plugged in my portable USB DVD burner and here I am. Forgot the switch to load to ram so I can eject the DVD to play stuff, but I will next boot.

I never had that issue, but it was slow. So, your new machine surely has USB3. Just put 621 on a fast flash device. It will boot very quickly and your burner will be always free.

This is just a side note on running using Live Media disc for normal system operations. There are some real obvious advantages, but, booting time is the least of any concern for running a FATDOG system. I have been using FATDOG, LightHOUSE64 and other PUPs continuously and consistently without the need to install to any HDD/USB. I have a Laptop running LH64 which hasn't been rebooted in months. My old FD521 system ran for about a year never being rebooted. And most of the systems I bring up excepting those I boot for test, remain up for quite long times.

In review, the minute of so it takes to boot is of little consequence in my use of FD/LH64/any-PUPs, as they usually remain up for days on end. 1 minute!

This is only of point that most of all already know about booting (and correspondingly "shutdowns")

So all HDDs/USBs in use on my local systems where Linux runs do not have any Operating Systems. Thus, they ONLY have data....user data. Not one has a resident OS. And, I think all of us understand the benefit of that.

The ability to run the OS in RAM with session persistence to live media disc is phenomenal. This is the primary reason, I was attracted away from Knoppix to Puppy many years ago.

I also have a running multi-user XP OS that boots and runs from Live media DVD disc. It does not offer persistence in the way Puppy distros do, but, it does work well

My laptops go to sleep and wakes as needed, so, I rarely (almost never) have to reboot it for any Puppy Linux I deploy there.

One final gem that exist in FDs: Netbooting; JameBond created the ability to boot distros over the LAN without the need to, again, "install FD or PUPs on the local PCs". This has also been extremely useful if I want to do a quick test of any PUPs. (There is a easy to use guide that has been around since he created that work of art and is referenced in the forum.) That tool made it extremely easy to use for anyone who can read the guide. It sets up simply and runs smoothly. Personally, even though there are some minor short-comings, it has been an extremely powerful solution requiring no LAN changes or any special considerations for its use to boot machines that are wired to any of our local LANs.

For those who would want to run directly from CD/DVD or the faster Blu-ray, this is a reasonable and safe approach to running most if not all PUPs.

This post, again, is FYI only.

[ally]

hey nooby

have the original iso and the delta in the same location

click the delta and it creates the new iso by joining the two

1 click and your sorted

[nooby]

Sorry one need to be very careful it is different from other puppies
in how it deal with the save file but not I finally got it to work Sorry

[smokey01]

Sorry one need to be very careful it is different from other puppies
in how it deal with the save file but not I finally got it to work Sorry

nooby, maybe this will make it easier to understand.

http://www.smokey01.com/videos/diff-files.mpeg

[Ted Dog]

ECHO what gcmartin stated, one great thing running from RAM with this newest FD64 is you close the lid and it go into suspend mode, and on lid up and a keypress its instantly back live. I've gotten into the habit with my first run in RAM netbook and it would stay 'alive' disconnected from power weeks in suspend mode with lid-down. Sadly the old netbook is not 64bit and newer kernels and/or settings in last years Woof builds do not allow this option.
Ideally would like to set up a Fatdog version to fast boot from spare space on EFI portion run in RAM and be able to save back to DVD (or Bluray once I can afford a USB3 burner) First order of business is to MAX out the RAM for this netbook to 8Gs. I purposely got the cheaper model with only 2G and tiny by Win8 320G HD. The HD will be reused after storing a compressed drive image (on Bluray of course )

It takes me about 2-3 months to fill a multisession DVD with normal activity. Thats only 4Gs with a 8G RAM I could go a number of months.
Would also like the option to remote save-session to a bluray drive on another machine. (I have done something like this with nc years ago)

[Hans]

I discovered I had no sound and found out that disabeling script /etc/init.d/jackd solved the issue.

I tried renaming jackd so it would come after alsa, and with a big sleep in the script but this did not help. I think I installed jack audio kit because it was required by another package (mplayer? Needed that for memcoder) so I think disabling the deamon is not a problem for me, I do not use mplayer. But for mplayer users it would be nice if it got fixed, right?

cheers

[nooby]

Smokey thanks, I did find that part it was the unusual thing
that FD place the save file directly on /mnt/home/
instead on /mnt/home/fd64 where I expected it to end up
and that it forced me to change ext4 to ext3 in two places
where i expected on only one place. Old habits that got challenged.

And the worst for a real absolute noob.

It changed my hardware clock so now it goes the wrong time
even on Lupu and i don't know how to set it correct.

sure it is my own fault but I am not good at reading instructions
and it introduce new things that I am not used to.

so now i have to try to find all the old instructions on how to set Lupu time
correct and I would not dare to boot into FD again because then
I am back with the wrong time and don't know how to set it straight again.

[jamesbond]

Delta file from FD620 >>> FD621

http://www.smokey01.com/software/iso/Fa ... .iso.delta

I have no clue what one are supposed to do with delta
maybe you can have the 621 iso there too. Just a suggestion

This is used to move from 620 to 621 if you already downloaded 620, the links to full 621 are on the first page of this topic, second msg from top. The delta file is to save bandwidth for us still stuck in the internet dark-age and/or pay by the bandwidth used. The delta between the last two versions is less than 2MB

We may create delta files for next release if the size of the delta file itself is not too big. Meanwhile, thanks for smokey01 for providing the delta.

BTW I discovered why the remaster was slower with isolinux.bin the burning progam or hybridiso patched or repatched isolinux.bin so you can't reuse the one found on the burned media, a fresh copy needs to come from /usr/share/syslinux for each remaster.

Discover this as a warning in the documentation about using level 2 with older version of other toolsets like hybridiso, or burning programs like growisofs.

Odd, if you look at /usr/sbin/fatdog-remaster.sh, in function create_remaster (around line 449), you will see that it does copy a fresh new isolinux.bin from /usr/share/syslinux ...

I discovered I had no sound and found out that disabeling script /etc/init.d/jackd solved the issue.

I tried renaming jackd so it would come after alsa, and with a big sleep in the script but this did not help. I think I installed jack audio kit because it was required by another package (mplayer? Needed that for memcoder) so I think disabling the deamon is not a problem for me, I do not use mplayer. But for mplayer users it would be nice if it got fixed, right?

cheers

mplayer pulls jackd because it needs the jack library (that's how it was compiled - I think). It certainly doesn't need jackd 'service' to run at all. Btw if install mplayer you also need to install lives_support.pet --- the dependency isn't auto-detected because files in lives_support used to be inside the base ISO; they were pulled out in 610 release or so and re-packaged into this pet.

Btw, when jackd runs no other alsa app can have sound - because jackd takes over sound devices exclusively. Only jack applications can have sound when jackd is running.

[Hans]

JamesBond wrote:

Btw, when jackd runs no other alsa app can have sound - because jackd takes over sound devices exclusively. Only jack applications can have sound when jackd is running

Yup, I found out the hard way. In the process of digging for a solution I somehow managed to F*&@ up the install. Somehow the hald process got screwed up, lsmod only gave 4 modules. Bummer. But I had a backup uf the savefile so no harm done. Another lesson learned.

Did you see my previous post about virtualbox?

Is it normal for this sfs to need the kernel source? I would think it would be part of devx. At first I thought devx was not fully loaded.

cheers

[prehistoric]

Just want to report that Smokey's delta 620 to 621 iso worked for me. Just tested 621 on one machine, but, so far, no new problems.

[jamesbond]

Did you see my previous post about virtualbox?

Is it normal for this sfs to need the kernel source? I would think it would be part of devx. At first I thought devx was not fully loaded.

cheers

Ah I missed it. The SFS in Fatdog's repo is for 610, which comes with an older kernel so you'll need to rebuild the modules. And yes, starting from 620 you will need *both* devx and *kernel sources*.

In the past the kernel sources was included in devx for convenience, but unfortunately we have to break that tradition and separate the kernel source from devx due to our SCM system breaking down when we have too many changed files in devx (=that is, then the kernel sources are inside devx).

Move kernel source to separate sfs file. Makes administration less problematic for us.

I don't blame you if you don't see it, I need to use the search function to find it too

[Ted Dog]

Just want to report that Smokey's delta 620 to 621 iso worked for me. Just tested 621 on one machine, but, so far, no new problems.

Xdelta also works to reverse.,I thought why not keep the most current iso and make a reverse Delta for previous iso before deleting it. That way I can go back if I want, which I never really do. Also any other distros iso also work. heck any two versions of most anything (except binary blob stuff for video cards) xdelta could also be included as a dot pet compressor for larger sfs and pet that are the same minus kernel updates.it would be great for stuff like wine and vbox.

[gcmartin]

Kirk, JamesBond, anyone. Would you comment on this?
Thanks

[gcmartin]

This question has probably been asked dozens and dozens of times in various ways in Linux history.

In FATDOG or PUPs in general, is there a system tool which will list the packages/subsystems that came installed from the ISO?

The PPM system does a very creditable job maintaining a list of packages installed, but, I am wondering if something exist to show a list of either what is available in the booted system or a combined list of all installed currently in the booted system.

Thanks for any guidance.