Posted February 06, 2018
Magmarock: I have two computers and my main gaming rig is air gaped. That means permanently isolated and offline. This is to keep it fast and reliable. I've had no problem keep it updated. It's a bit of a hassle but again streamlined compared to Linux. You can install KB commutative updates yourself or use tools like WSUS offline updater or even run a batch script.
Funnily enough this is to do with topic. I'm trying to tell you why Wticher 3 won't come to Linux any time soon but it sink it
Streamlined compared to what? Funnily enough this is to do with topic. I'm trying to tell you why Wticher 3 won't come to Linux any time soon but it sink it
Windows:
(Provided you have already set up the necessary application to download updates to the applications you use on the online machine)
* Download update files to a USB stick/HDD
* Move the storage to the offline machine
* Install updates (probably one by one - but that, as you say, can likely be automated)
Debian-based distro:
(Provided you have already set up the offline machine to use a local repository, and set up the online machine to mirror the bits you want)
* Clone the repository to a USB stick/HDD (one command: debmirror)
* Move the storage to the offline machine
* Run the relevant system update mechanism (apt-get update; apt-get upgrade, or GUI tools, or whatever you like)
Seems very similar to me.
At work last week, I set up a couple of virtual machines in order to play around with PXE, netbooting, and unattended installations, one (let's call it "1") is connected to the outside as well as to an internal network that's only among the VM's, the other VM ("2") is only connected to the internal network, and does not have access to the internet or the rest of our work network at all.
Machine 2 was installed and updated only from 1's mirror, and aside from my main networking interests, the setup of the mirror was very simple (there's the initial download, but that's no work, just a wait for the command to finish). When the config file is set up (which obviously needs doing just once) so that the application knows where to fetch from, to, and what to grab, it's a single short command. The client doesn't care whether the repository is on a server or on a local disk, as long as it's set up correctly (which, again, is set-and-forget).
I've since started messing around with cloning the FreeBSD repo as well, and offer that as an install choice, but I'm not quite there yet.
Post edited February 06, 2018 by Maighstir