this post was submitted on 11 Sep 2026
30 points (87.5% liked)

PC Master Race

22399 readers
643 users here now

A community for PC Master Race.

Rules:

  1. No bigotry: Including racism, sexism, homophobia, transphobia, or xenophobia. Code of Conduct.
  2. Be respectful. Everyone should feel welcome here.
  3. No NSFW content.
  4. No Ads / Spamming.
  5. Be thoughtful and helpful: especially when new beginners have questions.

founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] kata1yst@sh.itjust.works 2 points 12 hours ago (1 children)

How so? This is basically a net install procedure, which operates right out of most distros package system.

[–] papalonian@lemmy.world 4 points 10 hours ago (1 children)

I've never actually done a network OS install, but aren't those generally a "local" network install, ie the file is on another computer you or another admin control? Grabbing the file from somewhere else might open the door for a third party to provide their own ISO

[–] kata1yst@sh.itjust.works 3 points 4 hours ago* (last edited 4 hours ago)

You're thinking PXE/netboot, which netinstall disks are often used for, but you can use them independently of netboot.

Generally you have a minimal disk or recovery partition that initiates boot and offers the package manager, basic file and disk utilities, and a script to install a list of important packages. Basically nothing else. A handful of distros offer them, but they're easy to make too. I usually have one in a partition alongside by boot partition. This is very similar to the distros that offer a "recovery" boot option.

The point is that instead of downloading a static version of the OS at 2GB+ these days, you have a tiny boot disk that downloads all the latest and greatest versions of the files you need, or allows you to fix breakages. This is what MacOS and these Linux distros have been offering for years.