I agree...here are some of my photos of the Bismarck at 4192 meters.....That Bismarck was one hell of a ship...until she went down, that is Wink
my collection : http://g3.rockedge.org/index.php/Film-T ... n-Bismarck
I agree...here are some of my photos of the Bismarck at 4192 meters.....That Bismarck was one hell of a ship...until she went down, that is Wink
Unfortunately it is indeed the case. What other explanation could, then, explain why the much-lower-powered Atom netbook can boot Fatdog faster than the Athlon desktop?... and always laying that at the feet of the user saying "...well, your BIOS (or some other thing) is holding you guys back..."
By default this file is empty. /etc/brightness.conf is updated by "brightness-up/brightness-down" (which you can activate using keyboard shortcuts, in sven); and by fatdog-brightness applet.OK.
Shouldn't /etc/brightness.conf takeover at some point though?
Yeah, this is a tough one because of conflicting objectives. What I've done is, if the settings have been set before, it will not be asked again. E.g. if you have set the keyboard map during first boot and then save the session, the first-run wizard which runs on the next boot will not ask about keyboard anymore. At least that's how it is supposed to work.Otherwise looks like that the settings did not stick, which is not a good second impression
My answer will sound like a cop-out, but it is the truth. The problem of "no indication" is the bootloader problem. Fatdog hasn't even been started at that time, it's the bootloader who's in charge. So there is nothing we can do about it.The only problem with this.
It looks like the computer is locked up or frozen.
Nothing indicates it is still in the bootup process.
jamesbond wrote:@LateAdopter - you're correct. Here: http://lightofdawn.org/wiki/wiki.cgi/MinimalFatdogBoot.
@belham2: We started the huge/humongous initrd in Fatdog 600, that was back in 2012. The idea is not even new; Barry wrote Puppy support for humongous initrd back in 2007.
Machines I've previously booted Fatdog on (using USB flash drive)
(I no longer have access to some of them):
- Acer eMachines Netbook (2010): Atom N270 (single-core, 1.6GHz), 1GB - BIOS
- HP desktop (2012): Core i5 (dual-core 3.4 GHz), 8GB - UEFI
- Samsung laptop (2012): AMD A6 (quad-core, 1.6GHz), 8GB - BIOS
- Sony Vaio (2014): Core i5 (dual-core, 2.0Ghz), 16GB - UEFI
- MacMini (2017): Core i5 (dual-core, 2.6GHz), 8GB - UEFI
- Self-assembled desktop (2007): Athlon X2 (dual-core, can't remember GHz, definitely faster than the Atom Netbook), Gigabyte motherboard, 4GB - BIOS
Of all these machines, only the last one has the slowness problem. The rest boots from USB stick in less than 30seconds (from start of bootloader until kernel starts to run). The last one does take over 10 minutes if booted from USB or optical drive; **however** if booted from harddisk, it boots as fast as the others.
So no we're not expecting latest and greatest machine. Machines from 10 years ago is good enough.
Unlikely. New glibc requires new tooling and generally speaking requires all packages to be rebuild. I do have glibc 2.26 package but I haven't tested whether it can work as an update for the current glibc in 720."Any chance for a newer GLIBC (like 2.22) in final?"
We would have built this ourselves but claws-mail has ton of dependency. claws-mail seems to be a fork of sylpheed, is there anything in claws-mail that sylpheed doesn't do?"The later claws-mail builds from Debian repos complain and want GLIBC >=2.22"
You'll probably have to assign one yourself using sven. You need to figure out the keycode for the "rotate" key. Some devices don't send keys for rotate key, they send ACPI event instead."only the rotate key is not recognized yet"
Happy to put it in. There are a few NFS Utils. Which one are you referring (the source)? One from Launchpad or one from sourceforge?"Only thing missing: NFS. Whoever needs it, the famous NFS utils pet does also work in FD 720 Wink Wink to the devs, it's only 152k."
Fatdog only supports frugal install. http://distro.ibiblio.org/fatdog/web/fa ... drive.html (please scroll to the bottom)."So, can I ask, all these machines that were tested used "frugal' installs? Or did you do "full" installs to those USBs?"
No, how can that be? The only supported installation method for Fatdog is frugal install."Fatdog has decided to push frugal from their area of focus."
Good point. We'll have to make the information on this more prominent. We'll have this information highlighted or linked in every release."which I am super appreciative about"[/qoute]
You're much welcome.
"which is easy for us, given directions that is, but possibly not for others who see Fatdog on Distrowatch"
No problem. Just wanted to test the latest 3.15 claws mail. Will stick with the 3.9 then. I know it's a fork of Sylpheed, but 'Look and Feel' are different, and I'm just used to claws.@chiron:
Quote:
"Any chance for a newer GLIBC (like 2.22) in final?"
Unlikely. New glibc requires new tooling and generally speaking requires all packages to be rebuild. I do have glibc 2.26 package but I haven't tested whether it can work as an update for the current glibc in 720.
Quote:
"The later claws-mail builds from Debian repos complain and want GLIBC >=2.22"
We would have built this ourselves but claws-mail has ton of dependency. claws-mail seems to be a fork of sylpheed, is there anything in claws-mail that sylpheed doesn't do?
jamesbond wrote:... Machines I've previously booted Fatdog on (using USB flash drive)
(I no longer have access to some of them):
- Acer eMachines Netbook (2010): Atom N270 (single-core, 1.6GHz), 1GB - BIOS
- HP desktop (2012): Core i5 (dual-core 3.4 GHz), 8GB - UEFI
- Samsung laptop (2012): AMD A6 (quad-core, 1.6GHz), 8GB - BIOS
- Sony Vaio (2014): Core i5 (dual-core, 2.0Ghz), 16GB - UEFI
- MacMini (2017): Core i5 (dual-core, 2.6GHz), 8GB - UEFI
- Self-assembled desktop (2007): Athlon X2 (dual-core, can't remember GHz, definitely faster than the Atom Netbook), Gigabyte motherboard, 4GB - BIOS ...
Ooops! I made a mistake. It should be Intel Atom N450, 2nd generation Atom which does support 64-bit. I'm going to fix my original post.anikin wrote:Please, clarify this for me as I'm confused. Atom n270 is a pure 32-bit CPU, not capable of 64-bit. How did you manage to get FD, a 64-bit OS run on it?
As an academic question!... Is it possible to make a small initrd that can load the fd64.sfs and the kernel-modules.sfs directly from the CPIO homogeneous initrd file?jamesbond wrote:As an aside, we did have a discussion about small vs huge initrd a couple of months back (pros/cons/trade-off/etc) and decided that for the time being, the huge initrd is still the best.
My device names are correct.don570 wrote:to bigpup....
I noticed something strange.
Your device is ---> device:sdc5
Whereas the system is looking for (hd0,4) which is the 5th partition on sda
Could that be causing the delay in booting???
____________________________________________
In my situation I have saved to a folder (fd64save-folder) rather than a save file ---> I believe that is an option when you first make a savefile??
and I am using the hard drive that the kernel recognizes --> sda
________Code: Select all
title fatdog 710 (sda1/fd64save-folder) find --set-root --ignore-floppies --ignore-cd /fatdog710/initrd kernel /fatdog710/vmlinuz psubdir=fatdog710 pmedia=atahd pfix=fsck savefile=direct:device:sda1:/fd64save-folder initrd /fatdog710/initrd
It boots quickly. If it isn't booting quickly then it is having recognition problems.
Code: Select all
waitdev=5
Code: Select all
title Fatdog64 (sdc5/Fatdog64720b)
uuid 19b0847a-549d-49c9-8c98-25af56f1d0ee
kernel /Fatdog64720b/vmlinuz waitdev=5
initrd /Fatdog64720b/initrd