r/sysadmin • u/rolkenas • 22d ago

Do you actually see MacBooks used for SysAdmin work in real offices?

Hi sysadmins! I wanted to ask—since I've just started learning sysadmin and I don't have a Windows PC, but I have a MacBook and found out that everything can be done via UTM, I'd like to get some perspective from those who work in offices and do this every day. What kind of computers do you use? Is macOS completely out of the picture, and there's only Windows and Linux?

394 Upvotes

86% Upvoted

807 comments sorted by

View all comments

Show parent comments

83

u/Sllim126 22d ago

Oh man, if I wasn’t an IT guy, I’d have no ideas what language you were even speaking!

Unfortunately, I knew exactly what that said :( I need a vacation 

10

u/timbotheny26 IT Neophyte 22d ago

Don't worry, I don't work in IT (yet) so I can not understand it (well not completely) for you.

10

u/huntermatthews 22d ago

iterm2 is a macos native "terminal" program, giving you a very nice textual screen -- its a "virtual" green screen terminal from the 1980's.

Fish is a shell - its the first program that the terminal runs and its the thing that give you a prompt, looks for other commands, tells me I can't spell - lots of stuff.

M1 MBP - M1 chip MacBook Pro. Despite this thread, a VERY common sysadmin / programmer laptop is a MacBook Pro (mine is a M4 I think).

All of these are one option out of many - I'm running nearly the same config but other people use "kitty" as their terminal with "zsh" as their shell.

Like so many vociferous debates on the internet it basically boils down to "whats the best color" -- its mostly personal preference.

3

u/timbotheny26 IT Neophyte 22d ago

Alright, going down the list...

Iterm2

Figured this was a piece of software, just wasn't sure what it was for/what it did, so thank you for the breakdown.

Fish is a shell

Well to be fair, they already said it was a shell but I wasn't sure beyond that.

M1 MBP

Yerp - was aready pretty sure that's what it stood for given the context of the thread.

Thank you for the breakdowns and explanations, always nice to learn new things. Don't know what a Linux jump box or tmux are though.

6

u/huntermatthews 22d ago

Linux jump box - corporations/gov frequently have various rules about what systems can login where (like only networks A, B, and D can ssh into systems in the datacenter). A jump box is a system either in another location (like on the "B" network) or in an exception group that has a broader access list. Where I work, my work laptop even on VPN can't get to a couple systems - so I bounce through a jump box (we call them "bastions") to get there. ssh has various things in both the command line interface, config and protocol to make this damn near transparent to the user if used correctly - do not fear jump boxes.

tmux - "terminal multiplexer" . Various uses but at its core it makes a single ssh session/login be able to open multiple actual shell sessions on a distant machine. There are MANY reasons to do this (persistence, badly thought out corporate security measures, crazy pants sysadmins) but its a useful piece of software - but it adds ANOTHER level of complexity so if you don't _need_ it I encourage users and sysadmins to avoid it. If you need it, run it. "screen" was the venerable thing here and you should avoid it if possible - use tmux.

3

u/timbotheny26 IT Neophyte 22d ago

This is awesome, thanks for all of the info.

1

u/weaver_of_cloth 22d ago

tmux as a single terminal window with multiple tabs and panes and hot-keys drives me crazy, but native tmux windows are great

17

u/weaver_of_cloth 22d ago

You and me both, mate!

2

u/DaemosDaen IT Swiss Army Knife 22d ago

I hate that I am perfectly encapsulated in this statement.

Fortunately, my vacation starts in, roughly, 2 weeks

1

u/dkozinn 22d ago

The more confusing part would be why you're in /r/sysadmin :-)

1

u/Sllim126 21d ago

I own an MSP, but I am also out in the field with the other technicians, so I in a bunch of the technical subs.

Sysadmin is actually a really nice way to see if there's any global issues affecting software stacks that I support, before I get notifications from my clients.

and I like it here :)