3 ms·

Sidenote: In VM, you could spawn a new machines with "physical" storage or drives (Nothing was physical on the mainframe; everything is faked just for you! Awes

Sidenote: In VM, you could spawn a new machines with "physical" storage or drives (Nothing was physical on the mainframe; everything is faked just for you! Awesome.) by typing a single command at the command prompt! If you needed to fix a bug in some combination of operating system and IBM products, you could spawn that exact customer-replicating environment in about 2 lines of text. Try that with Kubernetes!

anthk 5y ago
LPAR makes LVM a joke.
- mimixco 5y ago
  It's sad to read about the dev headaches caused by today's poor virtualization environments. I distinctly remember that stuff was no work at all at IBM. It didn't interfere one bit with the actual work of coding on the products. In fact, we really never thought about setups or creating environments for testing or development. In peer reviews, for example, it was standard to bring output from both the failing case and the working case as printed handouts. Those were easy to generate; just spin up two machines and fix one while you leave the other broken. They can share resources if you like so you don't have recreate everything. That is horribly messy today. Testing is so hard most people don't do it.
  - anthk 5y ago
    Also on simpler BSD's like OpenBSD, bioctl is dumb simple. Setting up a encrypted disk is a no effort task. On firewalls, PF has a syntax simpler than most text adventure games. Every time I get into the GNU world, well, I get better HW support sometimes, among a slight bit of performance, but, FFS, configuring a Linux firewall gives me nightmares everyday. Just compare NAT on Linux vs OpenBSD. Or TUN/TAP devices, where in OpenBSD it's just a matter of a SINGLE line at pf.conf and two hostname.if files to define the bridge and the tap device with a subnet. Done. Oh, and sysctl to set IP forwarding, but that was the easiest task on any OS.

anthk 5y ago

LPAR makes LVM a joke.

mimixco 5y ago
It's sad to read about the dev headaches caused by today's poor virtualization environments. I distinctly remember that stuff was no work at all at IBM. It didn't interfere one bit with the actual work of coding on the products. In fact, we really never thought about setups or creating environments for testing or development. In peer reviews, for example, it was standard to bring output from both the failing case and the working case as printed handouts. Those were easy to generate; just spin up two machines and fix one while you leave the other broken. They can share resources if you like so you don't have recreate everything. That is horribly messy today. Testing is so hard most people don't do it.
- anthk 5y ago
  Also on simpler BSD's like OpenBSD, bioctl is dumb simple. Setting up a encrypted disk is a no effort task. On firewalls, PF has a syntax simpler than most text adventure games. Every time I get into the GNU world, well, I get better HW support sometimes, among a slight bit of performance, but, FFS, configuring a Linux firewall gives me nightmares everyday. Just compare NAT on Linux vs OpenBSD. Or TUN/TAP devices, where in OpenBSD it's just a matter of a SINGLE line at pf.conf and two hostname.if files to define the bridge and the tap device with a subnet. Done. Oh, and sysctl to set IP forwarding, but that was the easiest task on any OS.