Date: Sat, 09 May 2026 20:53:01 +0300 From: Sulev-Madis Silber <freebsd-current-freebsd-org111@ketas.si.pri.ee> To: freebsd-current@freebsd.org Subject: Re: Update strategy and timing Message-ID: <6DC7AD6C-4A29-4C4F-A8F8-77911D3564EE@ketas.si.pri.ee> In-Reply-To: <af9mCBTUfwZPbXJB@www.zefox.net> References: <af4FwVaA_3P4yam-@www.zefox.net> <9ed12219-6e78-4156-b0df-aca91a732127@FreeBSD.org> <ecbb916d-a524-433b-a939-c5f4bbca51b5@yahoo.com> <af9ZeT-gYRZDxJt2@www.zefox.net> <CAM5tNy7EOn=xxoPmTraEsvwFbeE%2BWtc5vHztF1x_Gj53whsGNA@mail.gmail.com> <af9mCBTUfwZPbXJB@www.zefox.net>
index | next in thread | previous in thread | raw e-mail
i track current, currently only armv7 but i do that with even more caution i don't store anything important there, etc if you do all that and be prepared for any faults, it's fine my funniest issue was time jumping back and forth. i was surprised that anything worked at all. turned out 4-core system had free running clock and time came from each one randomly and they were not in sync actually fbsd current is surprisingly stable and therefore it's used in some systems to get latest features of course one needs to test even a release if it works. if not, report it. if does, use it i think we have enough cheap computing hw in 2026 that this approach works you can also watch this ml and commit logs for any ongoing issues, so you don't build the exact bad commit. sometimes this is a thing provided you do all that, you can use current. like pocket knife, it's useful, despite you could cut yourself sometimeshome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6DC7AD6C-4A29-4C4F-A8F8-77911D3564EE>