• 0 Posts
  • 29 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle

  • I ask before I take the interview. Location, salary range, linux laptop are prerequisites to me working for anyone. If they punt on the laptop question it means no and they are hoping you’ll want the job even without. I can promise you I won’t, and if you view that as a red flag I can promise I don’t want to work there so I don’t care.

    If its a hard requirement for you just say that and say that’s for workflow and you don’t want to waste anyone’s time



  • Yeah, I that nk a lot of people ‘get it’ but can’t quite explain it. So they tell you they use arch and they they are excited about it.

    I’m a pro, I’ve used basically every type of Linuxevwr made. Ive built and run linux from wcratch multiole times, as a lewrning experience, a teaching experience and even protypes for production systrms. I understand the packaging philosophies, I understand the opinionated administration decisions. I’m subscribed to most major distro mailing lists and i understand the political motivations that drive various teams to the different technical decisions.

    Arch isn’t for everyone. And I’m totally fine with that. But it is perfect for people who want to build something with well crafted and unopinionated tooling. Of everyone ‘got’ arch they’d be failing at what they ate trying to do.


  • I have a roughly 13 year old install that I’ve moved through the transition to /usr/ and from sysv to systemd. Its my oldest install. I run almost everything except suse as a systems admin.

    As a way to run Linux, I find arch one of the nicest. Rolling release, unmodified packages direct from the dev, unopinionated systems management, arch build system for any packages you want to compile, arch Linux archive that can be used for snapshotting or locking your rolling release, and AUR.

    It’s a completely different way to manage and build an OS that no one else is really doing. I find team ‘I use arch btw’ to be extremely annoying but at the end of the day, the arch tooling for building a Linux ypunlike to use means that people are naturally going to want to tell you they built something they find enjoyable to use. That’s not really something a lot of people say about most OSs.

    I have a range of issues and annoyances with most major OS, ranging from i cant use this to i wish this worked. Windows, MacOS, Ubuntu/deb flavors, redhat/fedora flavors, openwrt, alpine and other busybox flavors, iOS, Android, Graphine. All have things that mostly work but I’m always working around something.

    And finding accurate documentation for issues on distros that have different configuration release to release is a pain, deb, Ubuntu and redhat flavors are especially egregious. I don’t really care how to do this on RH6 or Ubuntu 11, lol, I want docs for the current version.


  • Well, every instance has different mix of people interest and moderation. Which maybe I was over thinking it but it took a while to figure out where I wanted to be. And my initial experience wasn’t great. My server was way out of date, had caching issues, was slow lots of defederation and perhaps arbitrary blocking that I didn’t know was going on so I didn’t understand why it didn’t work.

    I gave up and came back to a different server and it’s been good since. But, no one is switching from threads or Instagram for that experience. Or at least going to stick with it long enough to find a home.










  • To be fair, every part of it is a small binary that generally does a single thing. You don’t have to run them all or even install them but they bring a lot of necessary functionality around base host bootstrapping that everyone used to write in shell for every distro.

    I find it nice as an operators of multiple infrastructures to be able to log into a Linux system and have all the hosts bootstrapped in a relatively similar fashion with common tools.

    Sysv kinda sucked because everyone had to do it all themselves. Then we got sysv, openrc, upstart and then systems and there was a while there where you never knew what you’d get if you logged into a box. And oh look, I gotta remember 10 different config file locations and syntaxes to assign an IP. Different syntaxes to start a daemon. Do I need to install a supervisor or does that come with the init.

    People are doing a lot of really cool stuff with Linux OSs assigning IP addresses in 10 different ways or starting programs was never one of them.

    Its also not that systemd has a monopoly, there are other init systems out there, but all the big distros, RH, Debian, ubuntu, arch . . . all came to the same decision that it was the best available init and adopted it. There are other options and any one of those projects is big enough to maintain its own init, but no one really finds the value in dedicating reaources, so they haven’t.