4 ms·
This article prompted me read more about the IBM i OS [1], and it sounds actually quite cool. From the self-healing and objects instead of files, to the packagi
by azinman2 10y ago
This article prompted me read more about the IBM i OS [1], and it sounds actually quite cool. From the self-healing and objects instead of files, to the packaging of an IR to be re-compiled on the fly to new platforms, I'm curious to know why it and its concepts aren't more mainstream? Is it actually the bees knees but just costs a lot?
[1] https://en.m.wikipedia.org/wiki/IBM_i https://en.m.wikipedia.org/wiki/IBM_i
- tyingq 10y agoYou would likely find similar things regarding other midrange and mainframe systems. HP3000/MPE, DEC VAX/VMS, IBM z/OS. Vax, for example, had functional clusters, versioned filesystems, and other goodies, many years ago. Just the nature of a proprietary system...controlling everything means some functionality is easier to implement, more elegant, etc. Apple still takes advantage of this. The hardware and OS licensing costs are high, as you suspect.
- luckydude 10y ago"VAX had versioned filesystems" I think that's a stretch. It had file-name;rev where each time you wrote the file it bumped $rev. As an SCM guy, that's not versioning, that's automatic backups. And you have to run purge all the time to free up disk space. I don't mean to be pedantic but this is the second time I've seen this claim in the last few days.
- tyingq 10y agoThat's what they are called though..."versioning filesystems". I didn't compare it to SCM. It is probably more comparable to snapshots. The number of revisions held is configurable.
- luckydude 10y agoYeah, wasn't trying to nitpick, just pointing out that as a file system guy (I did a pile of work on UFS at Sun) and an SCM guy, I don't think that we want people to think of what VMS had as a versioning file system. To me, a versioning file system has a dag, the OS creates a node everytime you close it with modifications; if two people close at the same time then just like BK or Git you fork the graph, which means the next time someone opens it it has to be merged. As I said elsewhere, it would be super cool to have such a thing for /etc, if you wack a config, debian wacks it, you upgrade, you then get all the features that an SCM system give you for merging. I dunno what Git gives you but BitKeeper does a kickass job of automerging and has a complicated but pleasant graphical file merge.
- Fnoord 10y ago> As I said elsewhere, it would be super cool to have such a thing for /etc, if you wack a config, debian wacks it, you upgrade, you then get all the features that an SCM system give you for merging. I dunno what Git gives you but BitKeeper does a kickass job of automerging and has a complicated but pleasant graphical file merge. Etckeeper [1] does this. There's also etcd, but that seems to be more akin to Puppet and Chef. Disclaimer: I've never used any of the mentioned software. [1] https://etckeeper.branchable.com/ https://etckeeper.branchable.com/