From nobody Mon Jan 15 18:48:06 2024 X-Original-To: freebsd-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 4TDLl40tt4z57LBn; Mon, 15 Jan 2024 18:48:48 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TDLl35vkYz4TJB; Mon, 15 Jan 2024 18:48:47 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x52e.google.com with SMTP id 4fb4d7f45d1cf-5592d2bc270so1656199a12.1; Mon, 15 Jan 2024 10:48:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1705344523; x=1705949323; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=I/WoT+Ay3mzobABXMuF7AlcLOD0UXEORhbexuiMS3jc=; b=maVx6eer64Codn/m4OY+Jx7XQH5qKPJcnTTQuvTeF+G4ED+LNbzJGPugA/yHfSoy+a NwhoBORj2B4MCAdyUeXXLcpryaq0sPi9M3WtYcihzp84HPJX2SAccLj+ZrwSzcwgIa78 1QN4b7TVM2sQ4zl6V4dypg40LmNDq0+UYXKMd4jvRJvv4r3hznI+pGK6PWVKKypUKaO+ AZBDOKAShlS0okILvs1VIdmozxCW2WhXkaTy4IWFu/loLzinK6K8kKprDDLQHSKmqRbK LrNjn1jGJ1ZsmfHq02Xq9E8UrZ0vOfQxjD1yXd/Bvjnplqoa2x0gBc5hOzpO/vmLLYlZ fYcQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705344523; x=1705949323; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=I/WoT+Ay3mzobABXMuF7AlcLOD0UXEORhbexuiMS3jc=; b=IluRGduNITza3Xcx2E1pk6i4L1lABtcKu8mfy/lgtajN5u/qeJmXCsqBs63WUpYAtQ 2LrmvLdLPLcvEIcX0EdndiH5GTl+Qp8fLk9jSjpMX8SzylwXlM0RSgKVlTnNftFAbA5/ muXfeejE38BYvGVQvIGvIQXgQwmstiKL6PoHmBPE81IHMN7d6g57QpQ7P8scBkvpqjhF qPjdzITSar3RNlvA4h+NjAAlD1Wzin+GvAonw1BENWghaCxJhpXMqo6dOXq6c4G5D6TM TAPNJQFlvqt1ixtHrOtoGGA+8n7+XHL5rma4gVQb8EDjB3ec3aN9SNZ9EjcnfZUZmrJP xW7Q== X-Gm-Message-State: AOJu0YyE12BNTmDdKI3zX/AQKHKeIJXztMRezbuzkbbu5cGafLKymYi/ Tpfpq2ZszRf++VRX9lji+5RI3uWh1M9rPvRcPVzCRTn2CNI= X-Google-Smtp-Source: AGHT+IGS7eSa65YjqkaboRH6mDNUmVYlffE4MIJeRgh5P3fDXyd/r71xNmO94HTynry1lUgpQc6OxlxILxi8IC+yIM4= X-Received: by 2002:a17:906:9b44:b0:a2b:238d:50f2 with SMTP id ep4-20020a1709069b4400b00a2b238d50f2mr2263418ejc.152.1705344522663; Mon, 15 Jan 2024 10:48:42 -0800 (PST) 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 References: In-Reply-To: From: Mario Marietto Date: Mon, 15 Jan 2024 19:48:06 +0100 Message-ID: Subject: Re: How to upgrade an EOL FreeBSD release or how to make it working again To: David Chisnall , Mark Millard Cc: John F Carr , freebsd-arm , freebsd-hackers , FreeBSD Mailing List , "freebsd-xen@freebsd.org" , FreeBSD Current , Warner Losh , =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= Content-Type: multipart/alternative; boundary="0000000000007e39b1060f007600" X-Rspamd-Queue-Id: 4TDLl35vkYz4TJB X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] --0000000000007e39b1060f007600 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello. Do you have deleted forever the set of packages and ports for FreeBSD 11 or you keep them stored in DVDs that I can buy or download for a small amount of money ? If yes,where ? To rebuild everything is out of my expertise. On Mon, Jan 15, 2024 at 7:15=E2=80=AFPM David Chisnall wrote: > On 15 Jan 2024, at 16:46, Mario Marietto wrote: > > > > The ARM Chromebook is based on armv7,it is still recent. > > For reference, the ARMv7 architecture was introduced in 2005. The last > cores that implemented the architecture were released in 2014. This is n= ot > a =E2=80=98recent=E2=80=99 architecture, it=E2=80=99s one that=E2=80=99s = 19 years old and has been largely > dead for several years. > > > But let's change perspective for a moment,don't think about the ARM > Chromebook. My question is : how to upgrade FreeBSD when it goes EOL. > > Generally, run `freebsd-update`. This is a very different question from > =E2=80=98how do I do a new install of an old an unsupported version?' > > > I ask this because there is a huge difference here between FreeBSD and > Linux. Today if you need to use , for example Ubuntu 14.0, you can use it > as is. Yes,there will be a lot of bugs,but it will work without crashes. > But if you want to use an old FreeBSD system,nothing will work for you. > So,do you know some methods to install even packages or ports ? You > know,there are cases when you need to do some experiments so that you can > keep your machine off the internet,so you aren't scared that someone can > compromise it. Totally prohibiting the users to use an old system,removin= g > ports and packages is not a choice that I approve of. And I'm not the onl= y > one that thinks like this. > > If you want to use an old and unsupported version of FreeBSD, no one is > stopping you, but: > > - You will need to build the releases. The source code is still in git, > you can. The scripts for building the release images are right there in > the repo. Just grab the relevant release or releng branch and go. > > - You will need to build packages. Newer versions of the ports tree wil= l > not be tested with the older release, so you may need to use an older > checkout of the ports tree. Poudriere will build a package repo for you. > > In both cases, if you=E2=80=99re using older versions you almost certainl= y *will* > have security vulnerabilities. The project strongly advises you not to d= o > this and not to blame us when you install known-insecure software and end > up compromised. > > The project does not have enough active contributors to keep maintaining > things indefinitely. This is why release have a five-year supported > lifetime. If you want to pick up an old branch and maintain it, you=E2= =80=99re > welcome to. In the past, companies have picked up old branches and > maintained them for customers that had a dependency on them. If you want > to pay someone to maintain an old branch (and have deep pockets) then the= re > are probably a few companies that will happily take your money. > > Maintaining binaries is a slightly different issue, but it=E2=80=99s not = totally > unrelated. Keeping old packages around consumes disk space and costs the > project money (remember, every package is mirrored across the CDN, so thi= s > isn=E2=80=99t just a single disk). Even if it were free, philosophically= , I think > making it easy for users to install known-insecure software is a bad idea > but if you want to keep a package repo with out-of-date packages online > indefinitely then you can. You can run Poudriere and even cross-compile > from a fairly beefy cloud machine quite easily. > > It=E2=80=99s been a while since I did a full package build, but I would g= uess that > you could do a single package build (all ports) for about $50 on a cloud > VM, more (2-3x) if it=E2=80=99s emulated. Storing the results for a smal= l number > of users will cost around $10-20/month. If you think this is an importan= t > thing to do, then you are absolutely welcome to spend your own money on > doing it. > > David > > --=20 Mario. --0000000000007e39b1060f007600 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello.

Do you have deleted f= orever the set of packages and ports for FreeBSD 11 or you keep them stored= in DVDs that I can buy or download for a small amount of money ? If yes,wh= ere ? To rebuild everything is out of my expertise.

On Mon, Jan 1= 5, 2024 at 7:15=E2=80=AFPM David Chisnall <theraven@freebsd.org> wrote:
On 15 Jan 2024, at 16:46, Mario Marietto &= lt;marietto2008= @gmail.com> wrote:
>
> The ARM Chromebook is based on armv7,it is still recent.

For reference, the ARMv7 architecture was introduced in 2005.=C2=A0 The las= t cores that implemented the architecture were released in 2014.=C2=A0 This= is not a =E2=80=98recent=E2=80=99 architecture, it=E2=80=99s one that=E2= =80=99s 19 years old and has been largely dead for several years.

> But let's change perspective for a moment,don't think about th= e ARM Chromebook. My question is : how to upgrade FreeBSD when it goes EOL.=

Generally, run `freebsd-update`.=C2=A0 This is a very different question fr= om =E2=80=98how do I do a new install of an old an unsupported version?'= ;

> I ask this because there is a huge difference here between FreeBSD and= Linux. Today if you need to use , for example Ubuntu 14.0, you can use it = as is. Yes,there will be a lot of bugs,but it will work without crashes.=C2= =A0 But if you want to use an old FreeBSD system,nothing will work for you.= So,do you know some methods to install even packages or ports ? You know,t= here are cases when you need to do some experiments so that you can keep yo= ur machine off the internet,so you aren't scared that someone can compr= omise it. Totally prohibiting the users to use an old system,removing ports= and packages is not a choice that I approve of. And I'm not the only o= ne that thinks like this.

If you want to use an old and unsupported version of FreeBSD, no one is sto= pping you, but:

=C2=A0- You will need to build the releases.=C2=A0 The source code is still= in git, you can.=C2=A0 The scripts for building the release images are rig= ht there in the repo.=C2=A0 Just grab the relevant release or releng branch= and go.

=C2=A0- You will need to build packages.=C2=A0 Newer versions of the ports = tree will not be tested with the older release, so you may need to use an o= lder checkout of the ports tree.=C2=A0 Poudriere will build a package repo = for you.=C2=A0

In both cases, if you=E2=80=99re using older versions you almost certainly = *will* have security vulnerabilities.=C2=A0 The project strongly advises yo= u not to do this and not to blame us when you install known-insecure softwa= re and end up compromised.

The project does not have enough active contributors to keep maintaining th= ings indefinitely.=C2=A0 This is why release have a five-year supported lif= etime.=C2=A0 If you want to pick up an old branch and maintain it, you=E2= =80=99re welcome to.=C2=A0 In the past, companies have picked up old branch= es and maintained them for customers that had a dependency on them.=C2=A0 I= f you want to pay someone to maintain an old branch (and have deep pockets)= then there are probably a few companies that will happily take your money.=

Maintaining binaries is a slightly different issue, but it=E2=80=99s not to= tally unrelated.=C2=A0 Keeping old packages around consumes disk space and = costs the project money (remember, every package is mirrored across the CDN= , so this isn=E2=80=99t just a single disk).=C2=A0 Even if it were free, ph= ilosophically, I think making it easy for users to install known-insecure s= oftware is a bad idea but if you want to keep a package repo with out-of-da= te packages online indefinitely then you can.=C2=A0 You can run Poudriere a= nd even cross-compile from a fairly beefy cloud machine quite easily.

It=E2=80=99s been a while since I did a full package build, but I would gue= ss that you could do a single package build (all ports) for about $50 on a = cloud VM, more (2-3x) if it=E2=80=99s emulated.=C2=A0 Storing the results f= or a small number of users will cost around $10-20/month.=C2=A0 If you thin= k this is an important thing to do, then you are absolutely welcome to spen= d your own money on doing it.

David



--
Mario.
--0000000000007e39b1060f007600--