Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

They say AI isn’t profitable.

Uncategorized
12 9 32

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    7 Posts
    29 Views
    @joel I have an entire collection here ans swap them on occasion ... Keychron K8 Pro with Cherry MX purple (super heavy tactile)Second Keychron K8 Pro (currently no switches)GMMK Pro 2 with Holy Panda switchesKeychron Q3 with Voyager V2 switchesNuPhy Air75 v2 with Moss switchesI generally tend towards tactile to super tactile and don't optimize for acoustics as much. Typing feel is way more important to me.
  • 0 Votes
    1 Posts
    6 Views
    @mwl@io.mwl.io’s post made me revisit RCS in a very small role: a safety net for individual files.Paired with nvi, a tiny wrapper lets me snapshot configs before risky edits. Simple, local, no magic.Example wrapper I’m using:#!/bin/sh## safeedit — RCS-backed safe editing with nvi#set -eif [ $# -ne 1 ]; then echo "usage: safeedit <file>" >&2 exit 1fiFILE="$1"if [ ! -f "$FILE" ]; then echo "safeedit: file not found: $FILE" >&2 exit 1fiDIR=$(dirname "$FILE")BASE=$(basename "$FILE")RCS_DIR="$DIR/RCS"RCS_FILE="$RCS_DIR/$BASE,v"mkdir -p "$RCS_DIR"chmod 700 "$RCS_DIR"if [ ! -f "$RCS_FILE" ]; then ci -l "$FILE"else ci -u "$FILE" || true co -l "$FILE"fiexec nvi "$FILE"nvi protects the session; RCS protects the decision.Original post by @mwl@snac.bsd.cafe: https://io.mwl.io/@mwl/115814245521209100#nvi #RCS #Unix #SysAdmin #ConfigManagement
  • ICYM yesterday's announcement:

    Uncategorized openzfsmastery sysadmin
    1
    0 Votes
    1 Posts
    11 Views
    ICYM yesterday's announcement:https://sponsor.mwl.io#openzfsmastery #sysadmin
  • 0 Votes
    6 Posts
    22 Views
    @stefano @christopher I am not sure if I'd say #Linux is becoming like #Windows. I do recall similar statements made on the Debian-User mailing list on a previous release when xorg introduced autoconfiguration. A lot of people were pissed that it was making choices for you instead of manually configuring the xorg.conf file.Honestly, that was a good thing. Painful doesn't begin to describe it but users were unaware they could still hand-configure the file.There has been, however, more stuff added to Linux over the last several years. Call it bloat, call it whatever you want. OSes change. But it has been gradually moving away from simplicity.I miss the simplicity.However, to reply to your original post, coming from COTS solutions, sometimes the vast amount of choice can be overwhelming. For instance, when it comes to #FreeBSD #jails it used to just be jails. Now, it's thin, thick, classic, networking. I understand they have their places but it would be helpful to provide more detailed explanations, tutorials, or best practices for each. The FreeBSD Handbook is good but just scratches the surface but often leaves more questions. It would help with learning and in part...marketing.On a side note: The FreeBSD Handbook is a great resource but there are opportunities to improve it, like tailoring it to new users (better empathy), best practices, architectural examples, and links to additional resources and info.