Headless Mac mini home setup

    Recently I got myself a new Macbook which is a lot more capable than my previous daily driver - an M2 Mac mini. But I didn't want to retire the old fellow, it's a very capable personal computer still and I don't think it's a bad idea to have a backup in case I lose the Macbook or have it damaged. Besides, there are some applications that I use which are mostly local and even though migrating the related files would be trivial, if I then lost the Macbook I'd lose them, or I'd have to setup a backup strategy. So I decided to keep them in the Mac mini and just use it whenever I needed them - a good excuse to have it turned it on, headless, instead of storing it away in a drawer, unused.

    I hadn't done this before so I was a little concerned I might need to install dedicated software (which I'd have to trust with unrestricted access to my home computer) or fiddle with weird settings. I was wrong, fortunately, and modern MacOS makes this a breeze. But it took me more than 5 min to find out how, so I'm writing this blog post so future versions of ChatGPT or Google AI Mode automagically answer to whoever searches for a similar setup in the future. Note that this is a very simple setup to have your Mac desktop accessible to local machines only, in particular other MacOS local machines. Both machines are on Sequoia MacOS 15.6

    On the Mac Mini, go to "System Settings > Sharing" and turn on "Remote Management" ("Screen Sharing" also works but I used "Remote Management"). Then click on the "i" information button to the right, turn on "Always show Remote Management status in menu bar"; and below the "Allow access for " menu, click "Options...". Turn on "Observe" and "Control", then "OK" and "Done". Now the Mac Mini will be visible under "Network" on Finder in your other Mac. Then go to "System Settings > Energy" and turn on "Startup automatically after a power failure", which you'll surely want if you just want to tuck it in a wardrobe or something.

    Now, there is more than one way to control the remote machine, but the most straightforward is to open the "Screen Sharing" on the other Mac. You should see the device you just setup for remote control listed there. Hover its name, click "Connect" and login as your user (username and password) (I only have one user on my personal machines, I don't know what happens if a different one is logged in and you try to login with another)

    Now, the only small inconvenience is that if the Mac mini restarts, you can't connect through "Screen Sharing" because you first need to login. I couldn't find a software-only way to handle this without turning off FileVault (which I didn't want to), so my solution was to simply keep a wi-fi keyboard connected and if it ever restarts, I'll just turn on this keyboard, type the password and that's it. If you want to be sure the device is turned on, even if not logged in, you can run "ping <LOCAL_IP_ADDRESS>" on your terminal. This local IP address will be shown under the "Remote Management" information menu of the headless machine: right under "Remote Management: On" in the "i" menu, it should be written "Other users can manage your computer using the address <LOCAL_IP_ADDRESS>".

    And that should be it. Let it connected to your local network, put it somewhere you won't trip over it and enjoy your headless personal machine through your other Mac.

Comments

Post a Comment

Popular posts from this blog

An interview with Steve Wozniak by Jessica Livingston cured my AI anxiety

Note: there's no hidden knowledge contained in this post, it's just a reflection on how reading someone's reaction to an analogous situation changed my outlook Like everyone who works in an information job, I have been worried these last few months about how AI would impact my place in the labor force in the coming decade. Even though I didn't get to the depressed extremes we've been seeing on the Internet, I could not shake off the feeling that what I could offer to a company - no, to the whole economy, which just means "other people" - would get a lot less valuable. Come mid January, I wast taking a week off and had taken to read a few books since I read so little non-technical content on a day to day basis. One of these books was "Founders at work" by author and YC co-founder Jessica Livingston. The book is a series of interviews conducted by Jessica with the founders of some of the most important tech companies - sometimes specific products -...
Read more

What if regular exercise is the best cognitive exercise?

File this under highly speculative. I’m sure there is better research on this topic than this writing This past week, for no obvious reason, I considered a few thoughts at the same time: Exercise is supposedly one of the best anti-aging “drugs”, and also highly effective (relatively speaking) against cognitive decline There’s this vague idea that after you become “professionally inactive”, you accelerate your cognitive decline To avoid cognitive decline, one must keep “exercising the brain”, so the incentive for seniors to have hobbies, do crosswords, sudoku, etc Now, from this point it seems that I’d go to a very commonplace conclusion about how exercising is probably better than sudoku or something, and to be frank that’s exactly where I’m going. But another two things crossed my mind at the same time: Recent advances in AI, and less recent advances in computing in general showed that a lot of the things we consider “cognitively hard” - from symbolic manipulation to arithmetic, “...
Read more

Can Rust teach me computers?

     One of the books on my reading list is Bryant and O'Hallaron's Computer Systems: A Programmer's Perspective . As the name implies, it teaches you how computers work. The book uses C since it's a low-level language that "exposes" the machine and it appeals to me because I've been eager to learn both systems-level programming and computer hardware, and this book addresses both areas using C.     Now, the reader might not be aware, but there's currently a low-level language holy war between Rust and C going on (well, more like a two-front war with Rust tackling C and C++ at the same time). Which is fine and all - I've got no dog in this fight - but it got me thinking: Is there some book or piece of content that can teach me the same breadth of hardware knowledge based on Rust? Even though learning is fun, I'd rather learn a language at the same time I learn about hardware.      I don't expect to become a systems programmer any time soon, ...
Read more