• 0 Posts
  • 23 Comments
Joined 1 year ago
cake
Cake day: July 4th, 2023

help-circle
  • Nah @exu is right: non-IT focused companies do not have the skills or desire to reliably set up and maintain these systems. There is no benefit to them creating their own server stack based on a community distro to save a few bucks.

    Smaller companies will hire MSPs to get them setup and maintain what they need. And medium to large size companies would want an enterprise solution (IE: RHEL) they can reliably integrate into their operations.

    This is for a few high value reasons. Taking Red Hat as an example:

    1. Standardization (IE: they can hire people with RedHat certificates and they will be a few steps ahead in ramping up to internal systems)
    2. Vendor support (IE: if something critical isn’t working they can get quick support from a Red Hat technician and get it resolved quickly)
    3. Reliability (IE: all software is backed and tested by Red Hat and if anything breaks from a package update its on Red Hat to fix)

    When lots of money is on the line companies want as many safety/contingency plans as they can get which is why RedHat makes sense.

    The only companies that will roll their own solution are either very small with knowledgeable IT people (smaller startups), or MASSIVE companies that will create very custom solutions and then train their own IT operations divisions (talking like Apple, Microsoft, Amazon levels).

    Not to say what Red Hat did is justified or good, because hampering the FOSS ecosystem is destructive overall, but just putting this into context.





  • For anyone looking for a chair that doesn’t want to spend >$1000 or get a gaming chair, I recommend looking for an office furniture reseller in your area.

    There are a lot of shops that buy used furniture from companies either going out of business or moving.

    I was able to get a new Steelcase for like half the price, still had its tags and packaging. Granted this was during covid where a lot of businesses were dumping their in-office supplies, but still worth a look.






  • I think that there are definitely valuable/valid use cases for the software in the OP, but I think that the built in bash tools can get most people most of the way there. And learning the common bash/shell conventions is way more valuable than learning a custom tool that some distros/environments won’t support.

    If someone already uses aliases, creates some custom scripts, and sets some useful environment variables (along with effective use of piping and redirection) and still needs something more specialized, then getting a new tool could help.

    The downsides are a reliance on another piece of software to use the terminal. So I would only use something like this if I had a really solid and specific use case I couldn’t accomplish with what I already use.


  • I wouldn’t install a program for this if your use case is simple. You will end up relying on it when there are already some built in tools that can get you 99% of the way there.

    1. Bash scripts placed in ~/bin or ~/.local/bin
    • Can have simple or complex scripts setup to do whatever you want
    • Easily called from terminal or automated through cron or systemd
    1. Environment variables set in -/.bashrc
    • Great for storing common paths, strings, etc.
    • Can be easily incorporated into bash scripts
    1. Aliases set in ~/.bashrc
    • Ideal (IMO) for common commands with preferred options
    • for example you could setup your most used rsync command to an alias: alias rsync-cust=“rsync -avuP”

    Edit: rephrased to not discount the tools shared. I am sure if you had a specific reason to use them they could be helpful. But I think for many users the above options are more than enough and are supported pretty universally.


  • Yeah I saw a post about it a long time ago on Reddit for users with lots of devices

    Basically it is just setting up one or two “central devices” that know all the client devices, but not linking the client devices individually.

    IE: One server is connected to your phone, laptop, tablet, desktop, etc. But the phone is not directly connected to your laptop or desktop or tablet.

    To be fair I don’t actually know if this is the best approach anymore or if just connecting all of them in a mesh is better 🤷

    Here is a forum post describing it.






  • Yeah I am a bit salty about all of the whole “Opt-out” telemetry thing. I know its just a proposal but just feels a bit slimy.

    Fedora is upstream of RHEL which is supposed to result in a mutually beneficial arrangement where Fedora users are essentially testers / bug reporters of code that will eventually make its way into RHEL. Its just part of the collaborative, fast, and “open” nature of FOSS. Adding sneaky/opt-out telemetry just feels like a slap in the face.

    super small ex. I am a big Podman user these days, and have submitted a few bug reports so the Podman github repos which has been fixed by RedHat staff. This makes it faster for them to test and release stable code to their paying customers. Just a small example but it adds up across all users to make RHEL a better product for them to sell. Just look into the Fedora discussion forum, there is so much bug reporting and fixing going on that will make its way to RHEL eventually.

    Making and arguing for “Opt-out only” telemetry is just so tone deaf to the Linux community as a whole, but I think they got the memo after the shit storm that ensued over the past few days.

    But HEY one of the biggest benefits of Linux is that I can pretty painlessly distro hop. I’ve done it before and can do it again. All my actual data is on my home server so no sweat off my back. openSUSE is looking pretty good, maybe I will give it a try.


  • I’m conflicted on this. I 100% think CLI applications should remain as packages but Flatpak IMO is superior for GUI. It just has a lot of “step in the right direction” sorts of things that address some of Linux’s faults.

    The big two positives for me are:

    1. Makes it easier for developers to publish their own software and reach many distros at once. This has really helped with software availability and updates.
    2. Sandboxing (although not perfect and Flatseal is kind of essential here, I hope this gets rolled into software centers or something).

    I am on Fedora Silverblue and the concept of a base OS + Flatpaks just feels right for workstations. OCI containers (podman/docker/distrobox) as a bonus for development environments without borking your host.

    But with this recent Fedora news (I know nothing has changed YET but I am just sussed out tbh), I am considering switching to OpenSUSE Aeon/Kalpa.