MX Linux Forum

Fastest boot of all linux OP. systems:

It is the latest trinity dog of fred - just 5 sec.,
https://debiandog.github.io/doglinux/zz ... tydog.html
MX 30 Sec.
Puppy linux 30 sec.,
Ubuntu 30 Sec.,
Windows 35 Sec.

-----------------
Regards


moderator note Eadwine: please don't shout in topics and topic titles, thank you.

Me thinks you are exaggerating.

I just ran the stretch version of trinity dog live in VBox and it settles at the trinity desktop after 38 secs.
No faster than MX and slower than antiX.

I get constantly boot times of 5 seconds or less with Arch, I used to get that even on 8 year old desktop (with SSD though). That's pretty typical for systemd systems that don't load too much crap, might not work if you just enable systemd in MX or antiX and don't know why, but yes, it's very much possible.

But I think my MX16 partition (and the predecessor MX14) on SSD boots up in around 5 secs or less as well, using default sysvinit.

My other MX installs (15 and 17) are on /dev/sdb which is a HDD. Pretty respectable boot times but > 10secs.

I that a cold boot?

Wow, that is fast. My sig system is more like 30 seconds, though most of that time seems to be a slow BIOS.

I rarely boot, over 40 days uptime. But sleep mode comes back in 4 seconds for the sound to start playing, and 6-8 seconds for the full functioning desk top.

entropyfoe wrote:I that a cold boot?

Wow, that is fast. My sig system is more like 30 seconds, though most of that time seems to be a slow BIOS.

I rarely boot, over 40 days uptime. But sleep mode comes back in 4 seconds for the sound to start playing, and 6-8 seconds for the full functioning desk top.

Excluding the BIOS bit. Because of my multiple distros, I only start timing the boot from the time I select MX Linux from the grub menu.

That seems like a better reference: Time to Start From Grub (TSFG)
all the rest is machine dependent.

Good point, I should time it from the grub.

I will try that next time I actually reboot.

Adrian wrote:I get constantly boot times of 5 seconds or less with Arch, I used to get that even on 8 year old desktop (with SSD though). That's pretty typical for systemd systems that don't load too much crap, might not work if you just enable systemd in MX or antiX and don't know why, but yes, it's very much possible.

But is it possible to use systemd without setting start-up delays? Honest question.

I have read that people use scripts to make sure everything (for example network, panel, panel applets and themes) loads correctly (in the right order) during boot. Because of that (and other things) I have a hard time to take systemd seriously. I think systemd is a tool for system administrators, but detrimental to desktop users. A Linux newbie shouldn't have to write a script to make sure that the panel starts before panel applets.

(seen in another topic)
didja hear the one about "LuckYbackup... 150MB in .001 seconds"

w00t 1101!111111111111