![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
You know, perhaps trying to build complicated things with inadequate documentation, the day after an evening in the pub to commemorate a friend/colleague who'd killed themselves wasn't the brightest idea I've ever had.
I also have very mixed feelings about something that's basically mr-pointless-swearing becoming popular with a section of the twatterati. One might be forgiven for forming the impression that a swathe of twitter is just looking for the next jolt of vicarious indignation so they can fondle themselves into a frenzy of hatred in the privacy and comfort of their own homes.
I understand that the traditional method used to be 'a scourge of small cords', but we live in the C21st and going up to the mall at Cribbs to drive people out of the Apple shop with a pointy stick is just going to get you arrested.
So here's the thing. SysV is pretty hateful because it got preserved in aspic at some point in the late 80s and all that has happened since is that it's got faster and cheaper. No-one has yet managed to keep a straight face while explaining why you need five (or was it seven?) different startup configurations and their associated collection of dreadful scripts that have to detach from the console. Or not detach from the console. And provide redirection for stdin, stdout and stderr. Or not do that. I'm sure I wouldn't have to try too hard to redirect stderr to pun: (and stdin to rdr:) - I am aware that those are CP/M devices - because I have a punch/reader in the shed. Which I'm sure would be a jolly jape for an April 01 RFC, but exactly no use at all to someone who'd like to get their website working now please.
Short version - Change is good, init is dreadful. The way OSX does startup/shutdown is really very good. Although XML does basically look like the OS is wearing a mullet. Ha-ha business up front, far roo much typing with special editor out the back.
Meanwhile, back with SysV, the advice in 'Practical Unix and Internet Security' for Internet-facing kit boiled down to 'Only keep packages on the system you know you need, which does not include a compiler/build chain.' And 'If the process-list is longer than a terminal session, then it's too long. Don't run things you don't need/understand.' This is coincidentally fine advice when trying to stuff as many VMs as possible into a bulging sock of a hypervisor. And those filthy BSD degenerates had Jails. And. And.
Docker networking still makes my eyes bleed. However, I chanced upon the weblog of a chap going on at some length about the state of SDN. Hoo, boy. I know little of SDN and after that read I am glad.
Oh, the bit about spotting undocumented command-line options on a slide half-way through a presentation? I didn't make that up. Modern system documentation is piss-poor, and no, a 'screen' 'cast' is really quite far from acceptable. No I am not going to do it for you and 'submit' a 'pull request'. I already have paid employment and a life to be getting on with outside of that.
I also have very mixed feelings about something that's basically mr-pointless-swearing becoming popular with a section of the twatterati. One might be forgiven for forming the impression that a swathe of twitter is just looking for the next jolt of vicarious indignation so they can fondle themselves into a frenzy of hatred in the privacy and comfort of their own homes.
I understand that the traditional method used to be 'a scourge of small cords', but we live in the C21st and going up to the mall at Cribbs to drive people out of the Apple shop with a pointy stick is just going to get you arrested.
So here's the thing. SysV is pretty hateful because it got preserved in aspic at some point in the late 80s and all that has happened since is that it's got faster and cheaper. No-one has yet managed to keep a straight face while explaining why you need five (or was it seven?) different startup configurations and their associated collection of dreadful scripts that have to detach from the console. Or not detach from the console. And provide redirection for stdin, stdout and stderr. Or not do that. I'm sure I wouldn't have to try too hard to redirect stderr to pun: (and stdin to rdr:) - I am aware that those are CP/M devices - because I have a punch/reader in the shed. Which I'm sure would be a jolly jape for an April 01 RFC, but exactly no use at all to someone who'd like to get their website working now please.
Short version - Change is good, init is dreadful. The way OSX does startup/shutdown is really very good. Although XML does basically look like the OS is wearing a mullet. Ha-ha business up front, far roo much typing with special editor out the back.
Meanwhile, back with SysV, the advice in 'Practical Unix and Internet Security' for Internet-facing kit boiled down to 'Only keep packages on the system you know you need, which does not include a compiler/build chain.' And 'If the process-list is longer than a terminal session, then it's too long. Don't run things you don't need/understand.' This is coincidentally fine advice when trying to stuff as many VMs as possible into a bulging sock of a hypervisor. And those filthy BSD degenerates had Jails. And. And.
Docker networking still makes my eyes bleed. However, I chanced upon the weblog of a chap going on at some length about the state of SDN. Hoo, boy. I know little of SDN and after that read I am glad.
Oh, the bit about spotting undocumented command-line options on a slide half-way through a presentation? I didn't make that up. Modern system documentation is piss-poor, and no, a 'screen' 'cast' is really quite far from acceptable. No I am not going to do it for you and 'submit' a 'pull request'. I already have paid employment and a life to be getting on with outside of that.
