this post was submitted on 06 Aug 2026
19 points (100.0% liked)
Linux
14579 readers
183 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Firstly, suspend might be an option compared to hibernation for your subsequent startups if you can suffer a slow startup the very first time.
Otherwise look up "Linux from scratch" .
A lot of boot time is decompressing and mounting initrd, loading modules there, mounting the root filesystem, jumping to that.
Build a kernel that has exactly the minimum modules needed for your system, skip initrd and jump straight to a root filesystem and call your init binary (it can be BusyBox even) do exactly what's needed there to get your network+graphics card up and running with a single shell script, done.
Also look at COW filesystems. Read only base with an overlay file for writes. Discard that file on each boot and you basically have a system that is always at the same state on startup.
Yea, I was hoping to not have to go the scratch route, but we shall see. I do already run ZFS.
Edit: And I'm using suspend now, but am unhappy without encryption at rest. Also, full memory GPUs don't suspend very quickly.