From nobody Tue Apr 12 15:20:47 2022 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id C7D085D0428 for ; Tue, 12 Apr 2022 15:20:56 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx1.riseup.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Kd8Z0099lz3sm5 for ; Tue, 12 Apr 2022 15:20:56 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Received: from fews1.riseup.net (fews1-pn.riseup.net [10.0.1.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.riseup.net", Issuer "R3" (not verified)) by mx1.riseup.net (Postfix) with ESMTPS id 4Kd8Ys4KsCzDxck for ; Tue, 12 Apr 2022 08:20:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1649776849; bh=zpDX2F95+js9FWdSxRSqzGIVEoeAwL0pp+62xDM633Q=; h=Date:From:To:Subject:In-Reply-To:References:From; b=n+rwlvAJiGdc2/OWpv7Oz1jzvbjPvzigqKx1sOFLR6JGANG/RSs2MkX6A/gfI/XvE Y4VAigwOAdaUJ5sEUDa53N304czjEqKRhrTIZrDdJCHhX8Par2GMS7aKlPzl8EUQT4 Y/lq5dAS1aRCAT0QbkUz0OmQoTRJ3OWrHPxBAnyI= X-Riseup-User-ID: 919A473E3B27C5C4C9001BFCCD0E7D0CDA3F670E23CD38DE7B3B8466570B93B8 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews1.riseup.net (Postfix) with ESMTPSA id 4Kd8Ys01S4z5vLq for ; Tue, 12 Apr 2022 08:20:48 -0700 (PDT) Date: Tue, 12 Apr 2022 17:20:47 +0200 From: Ralf Mardorf To: questions@freebsd.org Subject: Re: Why do we have to wait for the next release for bug fixes? Message-ID: <20220412172047.037503f4@archlinux> In-Reply-To: References: <20220412061100.cd71c9815f90ad3c9f7802d0@sohara.org> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Kd8Z0099lz3sm5 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=n+rwlvAJ; dmarc=pass (policy=none) header.from=riseup.net; spf=pass (mx1.freebsd.org: domain of ralf-mardorf@riseup.net designates 198.252.153.129 as permitted sender) smtp.mailfrom=ralf-mardorf@riseup.net X-Spamd-Result: default: False [-3.60 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[198.252.153.129:from]; R_SPF_ALLOW(-0.20)[+mx]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[riseup.net:+]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.129:from]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_LOW(-1.00)[riseup.net:dkim]; MLMMJ_DEST(0.00)[questions]; MID_RHS_NOT_FQDN(0.50)[]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On Tue, 12 Apr 2022 15:44:50 +0200, Tomek CEDRO wrote: >Exactly :-) We just have different organization here (than you may >know from Linux). BSD puts rock solid stability and long term >maintenance in the first place. Enforced changes are not really >welcome here. You get a generic OS with a standardized environment >that you may customize for various applications (i.e. network, >workstation, embedded). Also you have a choice between RELEASE as rock >solid solution with safe binary updates, STABLE as well tested moving >solution that you need to update yourself from the sources (usually >only kernel), or CURRENT as "bleeding edge" code with all new exciting >features that may change/break that you also need to update on your >own from the sources. > >https://docs.freebsd.org/en/books/faq/ Hi, you aren't entirely wrong, but you ignore Linux Super Long Term Support, for example see https://wiki.linuxfoundation.org/civilinfrastructureplatform/start . If you report an issue against upstream related to desktop software, it doesn't matter what OS you are using. If you don't use the latest version or at least the latest LTS version from upstream, you should expect that upstream doesn't care at all. Reliability in terms of security, stability and don't forget the workflow, is a serious, yet unsolved issue whatever OS you are using. YMMV! Ralf