On 2021-09-02, John McCue <
jmc...@obsd2.mhome.org> wrote:
> John Goerzen <
jgoe...@complete.org> wrote:
><snip>
>
>> I've used quite a few, but Debian is my favorite.
>
> I never used Debian, but I always wanted to give it a try.
> I suspect I would like it better than RHEL which I need to
> use a work (RHEL is good, but its direction is a bit
> concerning to me)
If you're using RHEL, Debian may be one of the closer cousins, philosophically.
It prizes "stability", not just in the sense of "it doesn't crash", but also in
the sense of "if you don't want the system to change out from under you for a
year or two, we've got you covered". RHEL takes this even farther, of course.
>> BSD/OS. The rest all have their own soft spot for me. Except AIX.
>> May smit die in a black hole <grin>
>
>:), At work, I support a proprietary package on AIX and that
> sometimes involves compiling and development. I have noticed
> AIX development is quite similar to the BSDs.
OK, so AIX story time. Why do I loathe AIX?
So I was working for a manufacturing company. I had been using Linux/Unix for
years, but never AIX. They were migrating off an AS/400 and quite literally
bought AIX because Linux was too cheap. Like, they had been used to paying
$200,000 for server hardware and were deeply mistrustful that the
already-overpriced $20,000 Linux box the vendor quoted would be sufficient. So
cue sparkle in vendor's eyes. "Oh, we could sell you AIX!" $90,000 later, they
had.
It was AIX 5.1L. It wasn't quite sure if it was a 64-bit OS, a 32-bit OS, or a
31-bit one. Ints were one bit smaller than I expected, for some reason I can't
remember now (to differentiate them from pointers maybe?) So you had 1GB file
size limits in different places.
So AIX had its own package management system, and also came with a CD that was
the "Linux environment for AIX" with a penguin on it and everything. Except it
had nothing to do with Linux. It was just open source stuff compiled for AIX -
but get this, installed with RPM compiled for AIX (if memory serves). So weird.
But that is how you'd get ssh.
So then I tried to get Haskell stuff to compile, and I discovered that both IBM
ld and GNU ld were broken in different horrendous ways. Most difficult port
I've ever done.
Then there was the day we had a drive in the RAID fail. Should have been easy,
right? Orange lamp goes on, you make a service ticket, drive gets swapped, lamp
goes off. Hah, no.
So first IBM wants to know the FRU or part number or something for the drive.
Of course they have like 5 part numbers for every part, and the one they want
isn't one that we know. Somewhere it is buried in smit, apparently. But
nobody, not them, not the manual, not Google, knows where. Several escalations
later, we had some senior level AIX tech figure out what part number we needed.
Tech arrives, does the 5-minute drive swap thing, and prepares to leave. I
observe:
1) The RAID is quite manifestly not rebuilding;
2) The orange trouble lamp is still on.
Tech accelerates his departure, saying "I just swap the drives. You'll have to
call support."
"Is the drive even working?"
"Of course it is. It's new!"
"How do you know, when the lamp is still on?"
"Uh, I just know. Sign here."
So then ensued several more hours of figuring out how to make a stupid RAID
rebuild. Yes the answer was somewhere in smit. No it wasn't obvious, and also
required multiple escalations to solve.
As an effort to put "all the things in one easy to use place", well smit utterly
failed. "zpool replace" is so much easier.
And the sad part was that, it generally seemed, smit was just a thin menu around
underlying more Unixy commands. Except there was zero tribal knowledge in
AIX-land (even at IBM) about the underlying commands, because "you use smit for
that".
- John