UniPup: 46 seconds
4.1: 53 seconds
The main reason UniPup is faster is because it doesn't have an 'init' script. Just like a full-hd installation of Puppy, the first script that executes is 'rc.sysinit'.
However, UniPup is slowed by the loading time of the bigger 'initrd.gz' file. I have built this UniPup with a separate 'usr_410.sfs', but intitrd.gz has everything else, including all the kernel modules. I intend to cut down the modules somewhat.
I am aiming for 30 seconds boot time ...we shall see how close I can get to that.
Comments:Posted on 12 Oct 2008, 16:46 by BarryK2
Test comment, to make sure commenting still works after upgrading PPLOG to v1.1b.
S**t, it doesn't work. Trying with a new Author name.
Posted on 12 Oct 2008, 16:47 by BarryK2
Another test comment
Another test post.
Posted on 12 Oct 2008, 20:10 by Raffy2
RamPup by wanderer
Wanderer in the forum has been posting about RamPup since last year, see http://murga-linux.com/puppy/viewtopic.php?t=23103 and his recent one http://murga-linux.com/puppy/viewtopic.php?t=34088
I don't know how his approach differs from UniPup's.
Posted on 12 Oct 2008, 20:12 by Raffy2
FYI, I also got this message upon posting: "The username Raffy is already taken and that password is incorrect. Please choose other author or try again."
Posted on 12 Oct 2008, 20:41 by lobster2
Unipup on Puppylinux.org
Did you get my interview questions?
- if you do not wan to be interviewed that is fine.
I hope Unipup will find a place on the community website, linked perhaps to your own site.
Enclosed is a test image
Posted on 13 Oct 2008, 7:44 by _Leon_
Slowdown at searching for personal save file
Why such a slowdown at searching for personal save file when a path is already specified with the 'psubdir' parameter in a menu.lst file?
If I remember right, Dougal significantly enhanced boot speed for Pup214R - Revisited, made by Dougal and Pakt.
My menu.lst boot settings:
kernel /p214r101/vmlinuz root=/dev/ram0 pmedia=idehd psubdir=p214r101
kernel /p41021/vmlinuz pmedia=idehd psubdir=p41021
Search times for personal save file between this two boot messages:
'Looking for Puppy in hda1... hda2... hda5... hda6... hda7... hda8...'
'Using personal data file /p214r1/pup_save.2fs which is on partition hda5'
on my computer:
Puppy-2.14.r1.01 - less then 1 second
Puppy-4.10 - 15 seconds
Posted on 13 Oct 2008, 8:36 by BarryK
Ok, I deleted the file that holds the usernames and passwords. Now, it is starting from scratch.
This comment should now work.
Posted on 13 Oct 2008, 8:38 by BarryK
Confirm commenting works
Now trying a second comment, with my new username and password...
Posted on 13 Oct 2008, 8:23 by disciple
!Blog comment doesn't work in IE7!
"Why such a slowdown at searching for personal save file when a path is already specified with the 'psubdir' parameter in a menu.lst file?"
I haven't tried 4.1, but I wondered exactly that for 4.0 - it seems to take forever looking for a save file.
BTW you posted about a 29s boot time back in April or something - or maybe that was a different machine :)
Posted on 13 Oct 2008, 9:10 by Jesse
Make boot fast
There are some optimization methods that seems to work quite well. The article is for specific hardware, but strategies mentioned can certainly be used for a multipurpose hardware iso distro.
LPC: Booting Linux in five seconds
Posted on 13 Oct 2008, 19:19 by Dougal
I've managed to speed things up on my installation on the Classmate.
I've cut down the time from starting rc.sysinit until X is up to about 12.5 seconds, but there are things that are pretty much out of our control:
- Starting X takes me 4 seconds (that's from the moment xinit is run until .xinitrd _starts_ to execute).(that's _with_ readahead)
- The kerenl init stage (when you see the "Uncompressing Linux... botting the kernel" message and have a blinking cursor...) takes something like 8 seconds
- The 4 seconds to wait for usb-storage to finish scanning...
I think the "5 second boot" guys did some serious cutbacks in order to get there... that might be why they seem to ignore requests to show their kernel config file.
Posted on 13 Oct 2008, 19:34 by icpug
slowdown searching for personal save file
The reason for this (in version 3 at least) was that the init script did NOT go directly to the psubdir to look for the save file.
It searched everywhere and then filtered the results keeping the ones that were in psubdir.
It did the same thing with PDEV1 as well.
Consequently there was little speed up at all.
There is scope to make things a lot better. Changing the search for PDEV1 was pretty easy. I could not see how to change the search for psubdir easily - but then I am not very good!
Posted on 14 Oct 2008, 3:17 by rrolsbe
For 2x or 4x CD/DVD boot speedup
Read my posts (rrolsbe) regarding CD/DVD boot speedup.
Posted on 14 Oct 2008, 18:39 by capoverde
One of my test boxes, half as fast as my newest one, boots with Puppy 4.1 in 24 seconds from CD, even less from HD (full install). I've been told that comes from the chipset: hardware experts (like forum member Sage) know which are the speedy ones.
BTW, I've read that most laptops have a battery-low emergency routine that copies all RAM to a temporary HD file, which gets copied back to RAM at the following boot. The previous session is almost immediately active -- without new hardware detection, of course. Couldn't that be an option for lightning-fast HD boot? (Or maybe I'm missing some key point?)
Posted on 15 Oct 2008, 4:01 by nic2109
Search for save file
I can confirm a sighting of the boot process searching through all disks for the pupsave file even when a psubdir is provided. Indeed it's a problem if you have ones with the same name in different partitions as it will use the first one it encountered in preference to the one you wanted. I had kicked myself for being so stupid as to have more than one pupsave file with the same name. But perhaps there's more to it than that.
Posted on 15 Oct 2008, 5:11 by veronicathecow
Hi, never quite sure why fastboot was removed. An additional parameter could be location of save file or use last known hardware profile. Microsoft has#ve realised the importance of this and are aiming for a sub 10 second boot time, surely we can beat that!!!
Posted on 17 Oct 2008, 7:22 by Springer
FIVE Second boots in non-Puppy Linux!
FYI (because it seems not many people here know the current state-of-the-art in fast-booting Linux), Intel recently did some very interesting work that reduced boot times for full desktop-user Ubuntu and Fedora to under FIVE SECONDS on an Asus EeePC with SSD.
Note that the profiling methods and tools these guys developed should also work in Puppy, and I would expect this approach could slash Puppy's boot time to only a few seconds even when booting from hard disk rather than SSD.
Here are a few links relating to this exciting new project:
LWN Article on five-second booting and how it's done:
Slides from the Linux Plumbers Conference on how Intel got Five-Second-Booting working (PPT only, unfortunately, but worth the trouble to look at):
Interview with one of the developers of the profiling tool:
I'd love to see what Puppy could do after applying all these tricks!
Posted on 18 Oct 2008, 8:30 by iscraigh (Craig)
I have tried Unipup on an Acer Aspire One, I did not get past the bootup it hung @ detecting multimedia hardware....keyboard mouse etc.
I tried it on my desktop and it functioned correctly. As you have intimated you are targeting this @ nettops like the aspire one I would be glad to beta test for you. The other major issue I have come across with puppy and the aspire is the failure to properly mount the internal sd drive. This also causes me to be unable to do a hardrive install.
If I can assist in any way please ask.