<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>As far as rolling releases are you familiar with Arch, Gentoo,
Tumblewood (Suse)? Speaking of systemd at least Gentoo supports
bypassing that if you wish (I do actually on my Gentoo box).
Tumbleweed makes snapshots you can roll back right in the boot
menu by default last I was running it. <br>
</p>
<p>yes docker is a useful as well, no reason not to do that. <br>
</p>
<div class="moz-cite-prefix">On 2022/04/28 15:10, Phil Marsh wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAOE7nwdnufSMiJfpqhTUrgu-w90-mR_fm2Hd-d5RShsu3CNvEQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Hi Bob, All,
<div>My two cents. The thing I dislike is that I need to
completely upgrade the OS to get the latest software (e.g.
compilers etc...) and often libraries sometimes require newer
software than the versions have.</div>
<div>For this, I rely on PPAs but I don't think this is ideal.
Yea, I get that the Linux folks are reluctant to have
brand-new software in the interests of stability. I wonder if
there's a way to have rolling updates instead of reinstalling
a fresh OS which winds up taking me about 2 weeks to set up?</div>
<div>On second thought, it's going to be somewhat better for my
next upgrade because some of my stuff is in Docker boxes and
chroot jails. OS upgrades are painful for me because I'm an
amateur and also because I end up needing to re-configure
things like Apache and Owncloud servers. I don't think that
just doing the standard Ubuntu upgrade will work right here
either and I've always installed fresh to upgrade.</div>
<div>By the way, I always keep a bootable (secondary) OS SSD for
the sole purpose of being able to boot up should my main OS
(primary) drive get messed up - to the point of not booting. I
also send my OS files at 3AM, to a directory on a snapshotted
ZFS pool. Should I blow up my current OS or do something
stupid to a server, I can always reload my OS drive from that
snapshot or directly from the backup directory using the the
primary or secondary OS drive. Then, of course, I update Grub
etc.. to make the reloaded OS drive bootable. The best way to
handle all this might be to just have your root directory on
ZFS, but I'm not comfortable with that yet, and I think, in
that case, one would still need a recovery drive with ZFS
installed.</div>
<div>Also, I'm looking at installing BBB (Big Blue Button) on
Docker. Any recommendations or advice? Is this a good idea? I
like the idea of Docker for this because it would seem to
minimize interference with my web server and make it easier to
upgrade my OS etc... I already run Jitsi on Docker.</div>
<div>Thanks and best,</div>
<div>Phil</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Apr 28, 2022 at 2:17
PM Bob Proulx <<a href="mailto:bob@proulx.com"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">bob@proulx.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Steve
Wolf wrote:<br>
> As another alternative to a debian-based system like
ubuntu, I'm running<br>
> RedHat on my home server. I used to run CentOS, which
was downstream<br>
> RedHat, but then RedHat bought CentOS and turned it into
its experimental<br>
> branch. But they do offer a free RedHat subscription for
up to 31 boxes (I<br>
> think -- I'm only running one).<br>
<br>
For people who haven't been following the activity "CentOS
Stream" now<br>
sits as a testing ground somewhere between RHEL and Fedora on
the<br>
close to RHEL side. Red Hat plans to use the CentOS community
to test<br>
for bugs in what then will go into their RHEL release. CentOS
Stream<br>
will be a rolling release model for new development. I know
several<br>
people who have not been happy with Red Hat's decision to pull
the<br>
CentOS rug out from under them.<br>
<br>
> I tried and failed to like Suse. So it's RedHat for me.
YMMV.<br>
<br>
Out of the ruins of CentOS arises two names that are new but
each<br>
continuing the old tradition of old CentOS. Both of these
appeared on<br>
the scene within a month of each other early in 2021. It's
been a<br>
year now.<br>
<br>
Rocky Linux was created by Gregory Kurtzer, the founder of the<br>
original CentOS project before Red Hat bought it. Rocky is a
tribute<br>
name to CentOS co-founder Rocky McGaugh. Rocky Linux aims to
be what<br>
CentOS was again. Rather a case of history repeating itself.
Here is<br>
a news article.<br>
<br>
<a
href="https://www.theregister.com/2020/12/10/rocky_linux"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.theregister.com/2020/12/10/rocky_linux</a><br>
<br>
AlmaLinux was created by CloudLinux and KernelCare. Alma
means Soul<br>
in Latin languages. "Soul" Linux. The cloud vendors needed a
free<br>
software OS. The cloud vendors were already building their
own clone.<br>
So when CentOS was killed off they decided to make their
efforts<br>
public with Alma. It continues their need to provide cloud
virtual<br>
hosting images. Here is a news article.<br>
<br>
<a
href="https://www.zdnet.com/article/cloudlinux-launches-almalinux-centos-linux-clone/"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.zdnet.com/article/cloudlinux-launches-almalinux-centos-linux-clone/</a><br>
<br>
I am hoping these two efforts can converge. They seem to be
on<br>
friendly relations with each other. Therefore they should be
sharing<br>
the workload for security upgrades and other support.
Regardless<br>
these two groups are ensuing that the community around CentOS
have a<br>
place they can go.<br>
<br>
At least initially it feels to me that Alma is ahead of Rocky
in terms<br>
of development and polish. But the Rocky developers are
experienced.<br>
I expect over time the two systems will leapfrog each other.<br>
<br>
The CentOS community will continue. It will just be called
Alma<br>
and/or Rocky moving forward.<br>
<br>
Bob<br>
</blockquote>
</div>
</blockquote>
</body>
</html>