Hints of a future OS war?
Iâm more of a 5-star series guy, especially the PacGen ruleset. Though I like it when self-propelled howitzers are exempted from the âno firing after movingâ rule that applies to all artillery in PacGen. Not a huge thing in WWII, but spamming M12 GMCs makes a lot of situations a lot simpler. You know what they say about XML? Well, it applies doubly to artillery. 155 mm best millimeter.
There are two types of people in this world, artillerymen and targets.
==========================================================================
BUG REPORT
--------------------------------------------------------------------------
TITLE:
Mistype in client meeting leads to contract loss.
SEVERITY:
High
DETAILS:
During a client meeting Rick typed "SL" instead of "LS" and
a train appeared on the screen.
FAULT:
iX systems (for switching from a proven server OS to a desktop OS).
FIX:
1. Fire Rick.
2. All remaining employees/users need to have the following alias
in their shell RC file.
`alias sl=ls`
STATUS:
Pending
DISCUSSION:
@bob
Why did Rick get fired? He and his wife just had a baby.
@jane
He's the one that suggested we upgrade to TrueNAS SCALE.
@tom
So, Rick gets fired for installing an update?
@jane
That ship has sailed. I need @tom and @jill to find out
how we can replace this OS with something more professional
and reschedule with ACME Anvil Corp.
@jill contacted iX Systems and their response was:
"We at iX systems take your question seriously.
The numbers show that more people are using
TrueNAS SCALE so we recommend all clients
side-grade to TrueNAS SCALE.
Also, please do not tell anyone that if you
type 'SL' instead of 'LS' you get a
train instead of a directory listing (we would
like to be taken seriously).
Our Engineers have determined that there are
dependency issues so removing the SL binary is
not recommended. Everyone, should instead, have
the following alias in their '.bashrc' file:
`alias sl=ls`."
@bob
Is this a joke?
@rick2
Not to rick1.
==========================================================================
So long, Ricky. It was nice working with you. You will be remembered.
TrueNAS SCALE steams over the competition.
A true nerd at my old school set up an executable named âlsâ in his home directory that could only be executed by root.
When a fellow student with admin privileges decided to try and snoop in this guys account, the VAX 750 sent a email to the faculty in charge of the mainframe a list of every user online at that moment (which was one, b/c it was after hours and the kid had dialed in over a modem), a summary of what was happening, and then shut the VAX down.
Needless to say, ding dong never got to be admin again. Nice train.
Wait, are you telling me that TrueNAS Scale ships sl
?
Debian does so I assume TrueNAS SCALE does too. âŚyouâd have to try it because Iâm not going anywhere near SCALE.
Debian â Details of package sl in bookworm
But, Iâm sure SCALE is still professional though.
Needless to say, ding dong never got to be admin again.
Neither should have the Nerd either. Kind of a serious bug/situation.
Wait, are you telling me that TrueNAS Scale ships
sl
?
(un)fortunately it does not
(un)fortunately it does not
Foul on the play! @betty and @jughead have always hatted @rick, they must have installed the package in the hopes heâd mistype in the ACME Anvil Corp meeting. âŚpoor @rick! You will be avenged!
Foul on the play! @betty and @jughead have always hatted @rick, they must have installed the package in the hopes heâd mistype in the ACME Anvil Corp meeting. âŚpoor @rick! You will be avenged!
@betty and @jughead best hope @jane doesnât find out they enabled developer tools on a production system to install that package then
@betty and @jughead best hope @jane doesnât find out they
Agreed! But, *shhhh* weâve already lost @rick (a good techâand remember the amazing cake we got him for his new baby celebration last week). Letâs not loose two more. @jane is a bit hot-under-the-collar. Heads would roll!
There were so many known holes in FreeBSD 4.4 or whatever it was back then, the UI would even complain âyou shouldnât be hereâ when yet another part of the password / mail / etc system had been compromised.
We were limited nominally to about 20 processes per user. That too could be compromised pretty easily. A classmate wrote a program he called âaids.câ as part of a sanctioned contest re: who could slow the VAX down the most. He won handily, it was so bad that it took 30+s for each character to appear on the teletype console printer once they tried restarting the machine clean.
I never got into the guts like those guys did, I had too many other interests besides computers.
I never got into the guts like those guys did, I had too many other interests besides computers.
Iâm right there with you. I didnât get started with computers until I started my professional career. However, my mother was friends with one of those âscary tech peopleâ (he was a gov level forensic tech). My intro to computers wasâfor the price of pizzaâlearning to root Linux with as few keystrokes as possible).
I experimented with slowing down a new, Sun T2000 server back in 2006. (It had 8 x 1.4Ghz cores, with 4 threads per core, 32 threadsâŚ)
It got up to 1,200 CPU suckers, âdd if=/dev/urandom bs=64k of=/dev/nullâ, before it was too compromised in performance for use.
Took about 1.5 seconds after running âpkill ddâ to return to service. Amazing machine for itâs time.
To be clear, I was the SysAdmin for the server, at Sun Microsystems, and it was not in production. Meaning I was the only valid user, thus, no impact to anything. (Except perhaps more electricity used. Wait, did I cause the energy crisis?!?)
Disappointed.
Please open a suggestion ticket to add âslâ.
Edit - And âcowsayâ.
Disappointed.
Please open a suggestion ticket to add âslâ.
*blink-blink*
#rememberricky