Author |
Message |
zagreb999
Joined: 11 Apr 2014 Posts: 573 Location: Yugoslavija
|
Posted: Thu 26 Apr 2018, 02:59 Post subject:
Speed Boot - Fastest Linux OS |
|
FASTEST BOOT OF ALL LINUX OP.SYSTEMS:
IT IS LATEST TRINITY DOG OF FRED-JUST 5 SEC.,
https://debiandog.github.io/doglinux/zz06-trinitydog.html
PUPPY LINUX 30 SEC.,
UBUNTU 30 SEC.,
WINDOWS 35 SEC.
-----------------
REGARDS
|
Back to top
|
|
 |
fredx181

Joined: 11 Dec 2013 Posts: 4481 Location: holland
|
Posted: Thu 26 Apr 2018, 11:25 Post subject:
|
|
zagreb999 wrote: | FASTEST BOOT OF ALL LINUX OP.SYSTEMS:
IT IS LATEST TRINITY DOG OF FRED-JUST 5 SEC., |
No, 5 seconds, it can't be, unless you did some magic patching (or something) that I don't know of (and depends of course on what computer used).
For me it's the same as most puppies/dogs, around 30 seconds.
EDIT: btw, this subject doesn't really fit in the "Projects" section.
Fred
_________________ Dog Linux website
Tinylinux blog by wiak
|
Back to top
|
|
 |
drunkjedi

Joined: 24 May 2015 Posts: 897
|
Posted: Thu 26 Apr 2018, 12:41 Post subject:
|
|
I haven't yet tried Trinitydog.
But I try many combination of methods to boot with Fatdog.
I boot from usb with basesfs kept on hard drive.
Lowest I get is 11 sec, Fatdog booting from usb with small initrd, base sfs on hard drive (not loaded in ram).
14sec if I copy base sfs to ram.
and 17 sec if I copy base sfs in expanded state to ram. (This is how I run normally).
If I used an ssd, I believe I can reduce boot time to 5 sec or below.
But that's no fun.
Loading everything in RAM in expanded state boots slightly slower but makes my softwares run blazingly fast.
Libreoffice starts in few milliseconds after clicking it's icon.
|
Back to top
|
|
 |
puppyluvr

Joined: 06 Jan 2008 Posts: 3512 Location: Chickasha Oklahoma
|
Posted: Thu 26 Apr 2018, 12:49 Post subject:
|
|
Hello,
Ok, I'll bite..
I'll get back with results..
_________________ Close the Windows, and open your eyes, to a whole new world
I am Lead Dog of the
Puppy Linux Users Group on Facebook
Join us!
Puppy since 2.15CE...
|
Back to top
|
|
 |
bigpup

Joined: 11 Oct 2009 Posts: 13981 Location: S.C. USA
|
Posted: Thu 26 Apr 2018, 16:13 Post subject:
|
|
The computer bios.
_________________ The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
|
Back to top
|
|
 |
technosaurus

Joined: 18 May 2008 Posts: 4878 Location: Blue Springs, MO
|
Posted: Fri 27 Apr 2018, 23:09 Post subject:
|
|
I once did an experimental build called microsaurus.
It used Xvesa, jwm, rxvt and a small shell with a minimal kernel and custom init written in C.
Boot time: ~0.5s
Total compressed size: ~1Mb
RAM usage with X, jwm and rxvt running ~3Mb (5Mb with background image)
Limitations: everything else - This was the result of my muntzing the entire Linux ecosystem to figure out the absolute minimum requirements.
What I learned:
1) init
* anything passed on the kernel command in the form VAR=VAL goes in envp...
* any remaining parameters go on argv
* It only takes ~10 lines of shell to set the system up to boot into X
* it takes more lines of C but you get finer control with no dependencies
2)X
* X (or X apps) need to have /tmp /proc /sys, /dev and /dev/pts mounted set prior to starting
* Xvesa starts in a fraction of a second whereas Xorg can take 20s+ just to initialize some video cards.
* the window manager fails if it tries to start before the xserver sets up its socket.
* it also helps to have a few environment variables set (HOME, USER, etc...)
* you don't need systemD, udev, or even mdev
* jwm's StartupCommand tag can be used to bring up the rest of the system
3)kernel
* You need unix sockets, tmpfs, devtmpfs, ELF binary, basic video, mouse and keyboard support
* but you don't need support for almost anything else - not even a single filesystem if you use a builtin initramfs
* Its actually is faster (and smaller) if you enable lz4 compression and compress the kernel image with lz4hc
* There is no need to compress the builtin initramfs separately if the kernel image is.
4)multicall binaries
* give you the benefits of shared libraries in a static build
* just about any program can be put into a MCB
* but its better if they share code - see goingnuts gtk1 MCB in the pupngo thread
Unfortunately I learned _too_ much with that experiment - I saw what was in the sausage.
_________________ Check out my github repositories. I may eventually get around to updating my blogspot.
|
Back to top
|
|
 |
drunkjedi

Joined: 24 May 2015 Posts: 897
|
Posted: Sat 28 Apr 2018, 15:26 Post subject:
|
|
technosaurus wrote: | * Its actually is faster (and smaller) if you enable lz4 compression and compress the kernel image with lz4hc. | Ahh... you did tell me this before, I haven't yet tested it.
When I get time I will definitely try lz4hc compression on at-least basesfs.
|
Back to top
|
|
 |
|