๐Ÿš€ go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: DOVE-Net.Hardware_Software_Help
2 messages
2 total messages Started by "neoshock" (VERT Sun, 16 Feb 2025 13:34
Re: What's Your Go-to OS
#696
Author: "neoshock" (VERT
Date: Sun, 16 Feb 2025 13:34
16 lines
1216 bytes
 Ar> For LXC in particular I tend to favor Devuan because it offers a Debian-li
 Ar> base - so third party services you bolt on it are likely to run - without
 Ar> carrying the bad babbage Debian has been accumulating as of late.
 Thank's for that info, I will look into Devuan. I have never heard of that distro, but looking at their website, seems like worth a try.

Ar> Alpine is good but then it is less compatible with random stuff you might   Ar> to deploy on it - it has a minoritary libc, for starters, so lots of
Ar>precompiled solutions simply don't run on Alpine as they are.

Yes, I agree. Originally Alpine seemed like was something I was going to switch all my containers, however it looks with the amount of work needing to get some projects working may not be worth the time. I might however use Alpine for simple services like Samba and ssh. All my other containers would mount those file shares. This allows me only needing to mount to one samba server to transfer files if need, rather than need to mount multiple samba servers on on desktop.

Lloyd (neoshock) sysop @ Vintage Pi BBS
vintagepi.asuscomm.com

--- Mystic BBS v1.12 A48 (Linux/64)
 * Origin: Vintage Pi BBS vintagepi.asuscomm.com
.
Re: What's Your Go-to OS
#710
Author: "Arelor" (VERT/P
Date: Tue, 18 Feb 2025 09:08
40 lines
2423 bytes
  Re: Re: What's Your Go-to OS
  By: neoshock to Arelor on Sun Feb 16 2025 01:34 pm

 > Yes, I agree. Originally Alpine seemed like was something I was going to
 > switch all my containers, however it looks with the amount of work needing
 > to get some projects working may not be worth the time. I might however use
 > Alpine for simple services like Samba and ssh. All my other containers would
 > mount those file shares. This allows me only needing to mount to one samba
 > server to transfer files if need, rather than need to mount multiple samba
 > servers on on desktop.

Depending on what you are doing, I find maintaining a multi-stack network sucks balls.

Say you are operating a server farm. Screw that, let's say you are operating a big homelab (with 20 machines or so). If you are serious you might be using some configuration management scheme so you can manage your farm semi-automatically instead of having to go through every one of your machines everytime you need to push an upgrade or whatever.

If you are using something such as Sake you need to define which tasks you want your configuration management solution to do. Stuff like defining an upgrade task that does apt update and apt upgrade on all your Debian-like machines. Usually that is easy enough.

Then you realize you have an Alma Linux machine, and an Alpine machine, and this NetBSD over there, and a virtual router with some goddamn proprietary firmware. This means your instruction starts looking like (pseudocode follows:)

upgrade () {
        if system is debian then do apt-get stuff
        else if system is alma linux then do dnf stuff
        if system is OpenBSD then do syspach and pkg_add stuff
.........
}

This gets out of hand very quickly. Some automation solutions suffer this less than others, but still...

So, in practice, I tend to recommend using as few platforms as possible just because it makes management suck much less. This means I tend to use a small number of operating systems for my VMs and containers (usually Devuan when I need Linux, OpenBSD when I don't) and exceptions exist only when there is no way arround it.

Just saying because if you have more than 5 machines then you might consider thinning your stack rather than adding more Linux distributions to the mix.



--
gopher://gopher.richardfalken.com/1/richardfalken

---
 รพ Synchronet รพ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
.
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads