• 0 Posts
  • 91 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle




  • I’ve updated enterprise Linux machines automatically for decades. The score is tens of thousands of upgrades, 1 problem I caused, 1 packaging glitch.

    You don’t need to take on risky drek like flatpaks to get there. It’s one command in enterprise and you’re kinda done forever.

    Glad you like your setup. I hope it works for you and you never learn the risks of flatpaks.






  • corsicanguppy@lemmy.catoLinux@lemmy.mlThank you
    link
    fedilink
    English
    arrow-up
    0
    ·
    18 days ago

    Hey. Thanks for the update! As someone whose experience was heavily windows apart from some failed Linux attempts, your experience switching now is an excellent comparison.

    Glad the story got better in the second act.

    Keep the story going. Please update.

    Thanks for persevering also.




  • corsicanguppy@lemmy.catoLinux@lemmy.mlShare your partition scheme!
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    19 days ago
    EFI
    83:boot(e4fs)
    8e:lvm(e4fs)
    bf:zfs
    

    This is just for /dev/sda or so, and implies non-redundant root disks because mirroring is done by the hypervisor. I’ve been 20 years doing virtualization, and I’m really starting to forget the last vestiges of my mdadm fdisk layout.

    So many people in this thread have no idea why you’d want separate allocation for /home and /tmp and others. Are we missing proper mentorship?






  • Has anybody been able to build a statically linked binary

    The question should by why you’d want to. Careful if your reply is something about ‘one binary to work on a very diverse arrangement of library pinnings’ because the next question would be ‘why would you think that’s either achievable or valuable as a goal’; and toss in a ‘why try to ship the same binary in several different repos anyway’ bonus question.

    In short, if your biggest problem is how to build a binary that works everywhere, you have a lot of questions about responsible build/release processes to answer, and they will be embarrassing for you.