4 ms·
"It used to be simpler" I don't know about that. You had the BSD vs System V at the time, and standard commands had different flags, default shells, etc. Then
by tyingq 6y ago
"It used to be simpler"
I don't know about that. You had the BSD vs System V at the time, and standard commands had different flags, default shells, etc.
Then shortly after, all the various RISC Unix flavors.
There is, of course, more than Linux these days, but it has so much market share on the server side.
- rodgerd 6y agoAIX vs SunOS vs Solaris vs HP-UX vs Digital Unix vs etc etc. I worked one place that had IRIX, AIX, Solaris, and Tru64 on one site, for a company of only 600 people. Each with different service management, shells, low-level (hardware/firmware), backup, etc all to learn. Old UNIX was a fucking shambles, with companies desperate to break things in small and large ways to try and create lock-in to their flavour.
- sysadmindotfail 6y agoBelieve it or not, places like this still exist. I worked at one (eerily similar story), then moved to a much larger company with even more platforms at one site. It was pretty silly.
- vram22 6y agoA.k.a. "the Unix Wars". https://www.google.com/search?q=the+unix+wars https://www.google.com/search?q=the+unix+wars
- Theodores 6y agoNetworking added to the fun. Token Ring. VAX/VMS networks. Then some normal TCP/IP. Then these new PC things with whatever it was they had, which certainly was not TCP/IP. It could even be Novell. Then the network cards had DIP switches on them and things like thin-net or AUX big network connectors. This made things we now take for granted a highly skilled domain. Getting your IBM box to talk to the Sun workstation on the other side of the room was rocket science. The different dialects of UNIX meant that there were niches for those that knew the difference between how to run a 'ps' command on a Sun box to (say) an IRIX box. Incidentally I am not sure it was about lock in for all companies. IRIX was about doing things in 3D and enabling those applications to work. They had no interest in tinkering with UNIX to make it different for the sake of it. It would be different because they had different hardware and 3D to be standardised. I felt IBM was different just for the sake of it with AIX. The same with Sun except they dominated in some universities so were the de-facto standard for many people coming through education at that time.
- pjmlp 6y agoTry the same with Red-Hat, Ubuntu and BSD, to see how much it has improved, hint nothing at all.
- tyingq 6y agoIt was worse. AIX, for example, had SMIT. You had to use it, or changes were only temporary. There was a lot more difference in those RISC Unix distributions than your current examples. Oh, and compiling open source programs across several of those. Real fun.
- pjmlp 6y agoI have started my UNIX knowledge with Xenix in 1992, followed by DG/UX and followed up from there across HP-UX, Tru64, Solaris, Aix, Linux distributions, FreeBSD,... Looking at modern distributions I hardly see a difference given distribution specific directories, packages or tooling.
- tyingq 6y agoWell, for me "sh configure" has a much higher chance of producing a working Makefile than it used to, as one example.
- mumblemumble 6y ago> You had the BSD vs System V at the time, and standard commands had different flags, default shells, etc. You still have that. For example, I develop on a Mac but production is Linux. The differences between GNU TAR and BSD TAR are a continual pain in my side. More everyday commands like ps still trip me up, too. It's not nearly as bad as back in college when I had to keep track of the differences among Solaris, HP-UX, Slackware, FreeBSD and NEXTSTEP, but still.
- dapids 6y agoAny particular reason why you don't just install GNU coreutils via brew et. al? I also develop on macOS for Linux and using the GNU equivalents with a quick function for path setting, is well, not very hard.
- deeblering4 6y agoI truly cannot stand “any reason why you don’t” questions. They immediately make me defensive. I’m far more open to alternate approaches when they are laid out in a clear, detailed and unbiased way. Mutual respect and all that.
- MereInterest 6y agoI am fine with "any reason why you don't" questions. Being asked one assumes that I am aware of the options, have gone through the pros and cons, and have made a decision on the matter. Clearly, I must have some reason for the decision, and so the person wants to know what reason that may be. Mutual respect and all that. Layout out alternate approaches assumes that I haven't done any research into the matter at all. It may be that the reason I don't use something is that I have never heard of it, in which case having the alternate approaches laid out is useful. Otherwise, it is a waste of the person's time to lay out what may already be known.
- ianai 6y agoThe phrasing though sounds like I’ve better got to know about it “or else”.