Bob Smith

I’m lucky I manually ran a few jobs before I started using rsync in scripts. When I didn’t think things through, I saw the output in real-time. After that, I got very careful about testing any scripts and accounting for minor changes in setup.

For me, it was getting a handle on rsync for a better method of updating backup drives. I was tired of pushing incremental changes manually, but I decided to do a bit of extra reading before making the leap. Learning about the -n option for testing prior to a sync has saved me more headaches than I’d care to enumerate. There’s a big difference between changing a handful of files and copying several TB of files into the wrong subfolder!

I’m typing this reply on an M1 Macbook Air running Asahi. My experience is very positive, but with some caveats. Some positives, some background to contextualize the positives, and some negatives.

Positives: Great screen, nice battery life when in use, fast, runs the programs that I use on a daily basis for work. Good support for the specific hardware that I have. I enjoy using it as my go-to laptop. Fedora isn’t something that I use on any of my other linux boxes, but I didn’t have much trouble setting it up and it works well with my other devices. Libreoffice, Firefox, Chromium, every DE and window manager that I’ve bothered to test - they work fine. I’m currently running Sway with no issues, KDE worked fine too. Sound, bluetooth, camera all work. Again, my 9-to-5 day job is fully doable from this computer and I enjoy using it.

Background: I’ve been tinkering with Raspberry Pi devices for years and I made do with a PI 4 as a daily driver for a few months once. That experience helped me to focus on native linux solutions that didn’t depend on WINE or x86-specific programs. I can’t remember every decision that I made during that time, but I definitely changed my workflow a bit, started doing more in the terminal, and started using programs that were less resource-heavy. That carried over to how I use other devices. I also don’t game much.

Negatives: Gaming is limited on this hardware. I can play minetest, tuxkart, and some light emulation. That’s about it, but I don’t mind. If you’re trying to run windows programs, you’ll be out of luck. My linux experience on this laptop prior to the Asahi shift to Fedora was a bit buggy because it was a beta version and sound wasn’t supported(other than bluetooth). Everything works fine now, but my understanding is that this is very model-specific. I would probably be having a bad time on newer mac hardware. Power management is so-so and it depends heavily on your choice of desktop environment. If you close your lid and don’t plug in the laptop, you might find out that the battery is dead when you try to use it a day later. No multimonitor support - the USB-C ports are more limited in function than they are when running MacOS.

Also, my only experience is with a niche distribution, so bear that in mind. For me, Asahi has been excellent but don’t expect to be able to run your favorite distro on the hardware. Time will tell if the progress made by Asahi will lead to greater support for Apple Silicon by other distributions, and time will tell how long Asahi will exist as an active project. I preferred the Arch version, but I had no real choice but to jump to Fedora when the developers did. Not a big deal for me.

Fair point, but I still need a quick way to tell people about upcoming funerals. On the plus side, I’m between the wave of friends’ baby photos and the wave of grandbaby photos. Which is nice.

I don’t integrate it with anything else, but facebook remains my best option for getting current contact info for anybody from my past. Even after the enshittification, it remains an effective Rolodex. Rolodex…I am old.

Arch offers a combination of rolling software updates, a simple but easily customized base, pacman for the package manager, the AUR, a barebones installation process by default, good documentation, and active development. That may or may not be a good combination based on your goals.

Other distros offer a different combination of characteristics. Those characteristics are a starting point and you can get to the same destination no matter what you use. The trick is figuring out what starting point is closest to your destination or which starting point makes the journey fun for you. For some people, Arch is that. For plenty of people, Arch isn’t that.

Easy if you go step by step and don’t accidentally skip anything. Archinstall will get you to the same result with lower risk of failure, in a tenth of the amount of time spent. And unless you install operating systems for a living, it doesn’t matter how you get there. Source: Installed Arch on about a dozen different devices, twice without Archinstall.

If you’re looking to learn something, do Linux from Scratch instead. The process is way more granular, way more documented, and way more educational than parroting the steps of installing Arch from the wiki.

What are you trying to build? A work laptop that you’re going to take on trips, a gaming computer, a server? Something else?

For you, what is too much hassle? Are you a new Linux user or an experienced user with no spare time? What are you accustomed to doing when you install an operating system and what do you expect to be preinstalled?

What is your favorite colour?

I didn’t, but only because my solution wasn’t novel or generalized for other people. I made a script to fire up tmux on a ‘primary’ computer with key-based access to my other computers, load up a set of windows and panes, and ssh into each computer. One window would be computers in one section of my home, another window would be computers elsewhere. The only challenge was getting a baseline grasp of the tmux scripting syntax.

I initially set it up to run htop on each computer (dashboard goal, plus easy ability to terminate programs), but the basic setup was flexible. I could set other programs to run by default or and send terminal command updates to each computer from any device that could ssh into the primary computer. Automating updates on a computer-by-computer basis is a better solution, but the setup let me quickly oversee and interactively start multiple system updates at once, from a phone, tablet, or laptop.

About 90% of what I know about ssh, terminal multiplexing, scripting, and diagnostic programs grew from an optimization project.

I had a vague desire to build a one-stop dashboard where I could monitor, update, and control a half-dozen linux computers at once. It was just for fun, but it kept me reading through the manpages for weeks.

Something a bit more out-of-the-box: I used to run 64-bit linux on a 2,1 Macbook Pro. Similar specs, including the same RAM ceiling. The isos are a bit out of date, but you can always install one and then upgrade from there. https://mattgadient.com/linux-dvd-images-and-how-to-for-32-bit-efi-macs-late-2006-models/

At that price range, be sure to carefully check compatibility for your favorite distribution and for any hardware that you intend to use.

For what it’s worth, I have an old HP Stream 7 that currently runs Debian Bookworm. I think that it cost about $100 new. I can use it as a pdf reader and to sync files, but there are plenty of tradeoffs due to the 1gb of RAM, the weak Atom processor, the small amount of built-in storage, the mediocre touchscreen, and the general poor quality of touchscreen interfaces among low-resource window managers. Neither camera works and several distributions can’t support the built-in audio. Screen rotation is a crapshoot. Forget about low-power standby. Some of these issues are unique to my tablet, but some of them are problems that people tend to run into when they try to shoehorn linux into a tablet that wasn’t built with linux in mind. Something like a Pinetab would be a better bet.

I saw another person suggest an aftermarket Surface. If you go this route, carefully research the exact model number to verify that the hardware supports linux and that there is a clean way of installing your preferred distribution.

Another thing worth mentioning. Installing linux can be a special kind of hell. Most distributions don’t have a touchscreen-friendly installer. For my cheap tablet, this meant cobbling together a flash drive, a powered USB hub, a USB keyboard, a USB ethernet adapter, and a USB-OTG cable for the single micro-usb port on the tablet. Then, I had to race the decade-old tablet battery to the finish line during the install process. Plus something about a 32-bit EFI bootloader combined with a 64-bit processor.

I use a tiling WM for everything. Libreoffice, games, Firefox/Chromium, file managers, etc. It all works and it is a great way to handle multiple monitors.

One option is to convert to txt for any text-only epubs that you have. There are a ton of lightweight options if you’re willing to use format-shifted copies on your computer.

Arch seems to target users who are inclined to read the wiki and manpages, so it doesn’t surprise me that beginners run across some saltiness if they approach people who aren’t focused on beginners. Even the installation process seems to be designed as a screening mechanism. It wasn’t a big hurdle when I first tried it out, but it was a small one.

There are plenty of distributions that focus on people who are just getting started. For whatever it might be worth, this includes several distros based on Arch. I usually suggest Mint or Xubuntu over Debian for people with no prior exposure to Linux. Even though I like it personally, I try not to suggest vanilla Arch to anybody. They can try it if they want to, but there are plenty of reasons to try something else instead.

I use linux to run my law office, so it can be done. Most of what I use is web-based these days, so headaches are minor. That being typed, I’ve been using linux off and on since the 1990s, and there was a fair amount of learning involved. A few notes:

-Libreoffice is good enough for document drafting, unless you’re extremely reliant on templates generated in Word. Even then, that’s a few hours of clerical work that you can farm out with, presumably, no confidentiality issues to flag. Also bear in mind that if you end up using different Linux distributions on more than one computer, then you may run into minor formatting differences between different versions of your word processing software. Microsoft Office will be a reliable option unless you run windows as a virtual machine. There are workarounds, but they aren’t business ready.

-Some aspects of PDF authoring can be tricky if you’re doing discovery prep, redaction, and related tasks in-house. This is very workflow-specific, so if you’re not a litigator or your jurisdiction doesn’t have a lot of specific requirements for pdf submissions, it might not be something that you need to worry about. If it becomes a problem, then a Windows virtual machine might be a solution.

-Video support depends greatly on the linux distribution, so you may want to do a bit of research and avoid distributions like Fedora, where certain mainstream AV formats are not supported by default for philosophical/licensing reasons.

-Compatibility with co-counsel and clients will be hit or miss. I don’t let anything leave my office that hasn’t been converted to PDF and I only do collaboration when there is a special request to do so. I can fall back on a computer that I have which runs Office. It sounds like you have more than one computer, so you can have a backup plan.

-Hardware support is critical. If you need to videoconference and it turns out that your webcam doesn’t have a linux driver, then you may be hosed. Research and test on the front-end so that you don’t find yourself in an embarrassing situation of your own making.

-Learning curves cost money. If you’re using an entirely new set of user software AND you’re hopping between different distributions to find the version of linux that works for you, you’ll waste a LOT of time that you could be using to generate billable work.