Arch Linux installation speedrun WR (First keypress to login%)

26 comments

There might be some savings to be had with some sort of local package cache over 10GiB Ethernet.
- Omitting grub and using systemd-boot might also take a few seconds off.
It's fast, but you are only installing base, linux and grub.
base-devel should also be there, since it's assumed to be installed by any PKGBUILD you'd want to build with makepkg.
But yes. It does what it said it would do: Install a basic, minimal Arch system in just over a minute.
- I disagree, making your own packages is nice, but it's not like it's needed. I know multiple people who don't touch the AUR or custom pkgbuilds at all
  
  I know. It's not marked in the wiki as essential and you can have a functional system without it.
- no networkmanager?
  
  networkmanager is for chumps, long live dhcpcd
- disqualified!
This would be interesting if it was Gentoo.
I don't quite understand the point of these speedruns since there's usually not a defined end target and there are so many variables which are not under the user/installer's control, like disk, processing speed
- Isn't the purpose getting views on youtube?
  
  pretty misguided way to do so then lol
- Time for systemd-speedrun to standardise this
  
  Good lord. Dead it, run from it, systemd still arrives
- It's defined right there in the title. First keypress to login prompt.
- I feel like it's mostly shitposting but soon enough there will be a more formal competition. Possibly with a standardized VM and local package cache.
- Yeah it really needs to be a target decided by someone else and not announced ahead of time.
It takes a while but I'm surprised the WR would be nearly 72 minutes.
- No, no and... yes.
  
  I intentionally misunderstood for (not very) comedic effect
  
  It's the way it's written, it's typically hour:minutes.seconds
- I thought that was honestly the joke.
  
  There's only like 10 minutes of actually typing commands.
  Without watching this, the premise sounds very stupid.

26 comments