From nobody Wed Jan 17 22:54:06 2024 X-Original-To: freebsd-current@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 4TFh602pg3z56xr1; Wed, 17 Jan 2024 22:54:48 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (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 4TFh5z3PbZz4BJ0; Wed, 17 Jan 2024 22:54:47 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=cncX443B; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of marietto2008@gmail.com designates 2a00:1450:4864:20::52b as permitted sender) smtp.mailfrom=marietto2008@gmail.com Received: by mail-ed1-x52b.google.com with SMTP id 4fb4d7f45d1cf-557dcb0f870so11719153a12.2; Wed, 17 Jan 2024 14:54:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1705532084; x=1706136884; 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=nSnQOjjxuF3HP/SQOZZ6iXjGnfG8l+tXCOSpX5Tr914=; b=cncX443B3MHzqzq7lcIOFXNep1A8apI43dOjOSrpgUTZ/NyKAn0yaeETYTLRO6SfMR C8a922T1qMwnI4YOZI5YXYnVo/MoTLxZ/XlBCzQojta2NLN+hShdw7ondVUMb2lmgaUl yHcgJHdUnfJUfMjrfMazVFoyzWdaqKip0jDBgsfAsBjF4HrrXsISLHMjZKhR2BZq8urB Zajo7CF3/AsKjemrwUFl9hu9N8W1Kb5kdgscgj4h3vrYC4/7J1ZjINB7WXyPKvMpseux sAzesATfi/aRrEb/Lt0G0CrKVQkBih9iFSA4BodRnX1nk3bzogMl3UCr3LSJrWpjnq1S /1kA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705532084; x=1706136884; 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=nSnQOjjxuF3HP/SQOZZ6iXjGnfG8l+tXCOSpX5Tr914=; b=BphHi4sJ8SSOCol/NlMeludM9meX6BdrVki8aGhAN9imp9f+IiYi21utJdOWvJ6KHe TdAkQR1jhajdTOBSRbUCQs18tzvV7WZ21pLyNm2aFuBFzgGhTiYBZS8D6ai9UjXMlIcl p3V/s8kOAhLeHA1+/Aj8oywuw4GZ7TQQGvJo23dEasBqPdAHAhUGu5x6H8KmS3aQGPRF QJ7JF9p4ZacR9iDse/DV2qRuiBlp5hM/B2wDBsI6v+eS9f+AY2Zyh+Oo5BNm2PY092hH Ew5rHYD+yyltvwcqZo00F3f4/ICvAfidhw8w9YTFZTDLsDMKFln4INeGWS7mUL5ifX17 hNBQ== X-Gm-Message-State: AOJu0YyLvDYzVW4N1bPJvoP+z9yFhklPY8cz05v83OCRM+sYuLqARltf m3rWJrVv3SG2JxGvJRx9Q/C5xEvGBX5gH3I49OeaJXaYrtDyUQ== X-Google-Smtp-Source: AGHT+IF+jR4VVogFOyMYacwANH61Q1whsUFMPHVI2X3QOlKb33ZPZ8uJZqFcH0fzcckiVLBHVlW+Q8YHxSJIEF/yYJY= X-Received: by 2002:a17:906:3cf2:b0:a27:246b:442c with SMTP id d18-20020a1709063cf200b00a27246b442cmr4035292ejh.97.1705532083591; Wed, 17 Jan 2024 14:54:43 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Mario Marietto Date: Wed, 17 Jan 2024 23:54: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="000000000000fedfbc060f2c216d" X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.98 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.979]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FREEMAIL_TO(0.00)[freebsd.org,yahoo.com]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; MISSING_XM_UA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org,freebsd-hackers@freebsd.org,freebsd-questions@freebsd.org,freebsd-xen@freebsd.org,freebsd-current@freebsd.org]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCPT_COUNT_SEVEN(0.00)[10]; RCVD_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::52b:from] X-Rspamd-Queue-Id: 4TFh5z3PbZz4BJ0 --000000000000fedfbc060f2c216d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello to everyone. I'm trying to copy the Chromebook's SNOW source files that have been included on the FreeBSD 11 revision 269385 to the new FreeBSD 13 revision 373300. It has compiled correctly world,but when it starts to compile the kernel,it gives a lot of "unknown option" errors. Is there a way to fix them ? # svn co http://svn.freebsd.org/base/head@269385 ./head-269385 ; taken from this tutorial : https://wiki.freebsd.org/arm/Chromebook # svn co http://svn.freebsd.org/base/head ./head-373300 # cp ./head-269395/sys/arm/conf/CHROMEBOOK-SNOW ./head-373300/sys/arm/conf # cd ./head-373300 # make TARGET_ARCH=3Darmv7 KERNCONF=3DCHROMEBOOK-SNOW buildworld buildkerne= l I tried also with : make TARGET_ARCH=3Darmv6 KERNCONF=3DCHROMEBOOK-SNOW buildworld buildkernel,but it didn't make any difference. ..... ..... -------------------------------------------------------------- >>> World build completed on Wed Jan 17 21:27:04 CET 2024 >>> World built in 14203 seconds, ncpu: 16 -------------------------------------------------------------- make[1]: "/mnt/zroot2/zroot2/OS/Chromebook/head-373300/Makefile.inc1" line 341: SYSTEM_COMPILER: lib clang will be built for bootstrapping a cross-compiler. make[1]: "/mnt/zroot2/zroot2/OS/Chromebook/head-373300/Makefile.inc1" line 346: SYSTEM_LINKER: libcl ang will be built for bootstrapping a cross-linker. -------------------------------------------------------------- >>> Kernel build for CHROMEBOOK-SNOW started on Wed Jan 17 21:27:04 CET 202= 4 -------------------------------------------------------------- =3D=3D=3D> CHROMEBOOK-SNOW mkdir -p /usr/obj/mnt/zroot2/zroot2/OS/Chromebook/head-373300/arm.armv7/sys -------------------------------------------------------------- >>> stage 1: configuring the kernel -------------------------------------------------------------- cd /mnt/zroot2/zroot2/OS/Chromebook/head-373300/sys/arm/conf; PATH=3D/usr/obj/mnt/zroot2/zroot2/OS/Ch romebook/head-373300/arm.armv7/tmp/bin:/usr/obj/mnt/zroot2/zroot2/OS/Chrome= book/head-373300/arm.armv 7/tmp/usr/sbin:/usr/obj/mnt/zroot2/zroot2/OS/Chromebook/head-373300/arm.arm= v7/tmp/usr/bin:/usr/obj/m nt/zroot2/zroot2/OS/Chromebook/head-373300/arm.armv7/tmp/legacy/usr/sbin:/u= sr/obj/mnt/zroot2/zroot2/ OS/Chromebook/head-373300/arm.armv7/tmp/legacy/usr/bin:/usr/obj/mnt/zroot2/= zroot2/OS/Chromebook/head -373300/arm.armv7/tmp/legacy/bin:/usr/obj/mnt/zroot2/zroot2/OS/Chromebook/h= ead-373300/arm.armv7/tmp/ legacy/usr/libexec::/sbin:/bin:/usr/sbin:/usr/bin config -d /usr/obj/mnt/zroot2/zroot2/OS/Chromebo ok/head-373300/arm.armv7/sys/CHROMEBOOK-SNOW -I '/mnt/zroot2/zroot2/OS/Chromebook/head-373300/sys/a rm/conf' -I '/mnt/zroot2/zroot2/OS/Chromebook/head-373300/sys/arm/conf' '/mnt/zroot2/zroot2/OS/Chro mebook/head-373300/sys/arm/conf/CHROMEBOOK-SNOW' WARNING: duplicate option `DEBUG' encountered. ./head-373300/sys/arm/conf/CHROMEBOOK-SNOW: unknown option "IPI_IRQ_END" / "IPI_IRQ_START / ARM_L2_PIPT" and so on... these options are included inside the file "std.exynos5250" (that I have copied from the old to the new source code). What I'm trying to do to stop these error is to comment the offending lines : nano ./head-373300/sys/arm/samsung/exynos/std.exynos5250 : #options IPI_IRQ_START=3D0 #options IPI_IRQ_END=3D15 #options ARM_L2_PIPT but I suspect that a lot of options will be missing and the more comments I will make,the more the chance that it will not work will increase. ... On Mon, Jan 15, 2024 at 7:48=E2=80=AFPM Mario Marietto wrote: > 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 = 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 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 i= t >> 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 ca= n >> 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,removi= ng >> ports and packages is not a choice that I approve of. And I'm not the on= ly >> 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 >> will not be tested with the older release, so you may need to use an old= er >> 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 certain= ly *will* >> have security vulnerabilities. The project strongly advises you not to = do >> this and not to blame us when you install known-insecure software and en= d >> 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 wan= t >> to pay someone to maintain an old branch (and have deep pockets) then th= ere >> 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 th= e >> project money (remember, every package is mirrored across the CDN, so th= is >> isn=E2=80=99t just a single disk). Even if it were free, philosophicall= y, I think >> making it easy for users to install known-insecure software is a bad ide= a >> 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 = guess >> 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 small >> number of users will cost around $10-20/month. If you think this is an >> important thing to do, then you are absolutely welcome to spend your own >> money on doing it. >> >> David >> >> > > -- > Mario. > --=20 Mario. --000000000000fedfbc060f2c216d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 
Hello to ever=
yone.

I'm trying to copy the Chromebook's SNOW source files =
that have been included on the FreeBSD 11 
revision 269385 to the new Fr=
eeBSD 13 revision 373300. It has compiled correctly world,but when it
st=
arts to compile the kernel,it gives a lot of "unknown option" err=
ors. Is there a way to fix them ? 

# svn co =
http:=
//svn.freebsd.org/base/head@269385 ./head-269385 ; taken from this tuto=
rial :

ht=
tps://wiki.freebsd.org/arm/Chromebook

# svn co htt=
p://svn.freebsd.org/base/head ./head-373300
# cp ./head-269395/sys/arm/conf/CHROMEBOOK-SNOW ./head-373300/sys/arm/conf
# cd ./head-373300
# make TARGET_ARCH=3Darmv7 KERNCONF=3DCHROMEBOOK-SNOW buildworld buildkerne=
l

I tried also with : make TARGET_ARCH=3Darmv6 KERNCONF=
=3DCHROMEBOOK-SNOW buildworld buildkernel,but it 
didn'=
t make any difference.

.....
.....
--------------------------------------------------------------
>>> World build completed on Wed Jan 17 21:27:04 CET 2024
>>> World built in 14203 seconds, ncpu: 16
--------------------------------------------------------------
make[1]: "/mnt/zroot2/zroot2/OS/Chromebook/head-373300/Makefile.inc1&q=
uot; line 341: SYSTEM_COMPILER: lib
clang will be built for bootstrapping a cross-compiler.
make[1]: "/mnt/zroot2/zroot2/OS/Chromebook/head-373300/Makefile.inc1&q=
uot; line 346: SYSTEM_LINKER: libcl
ang will be built for bootstrapping a cross-linker.

--------------------------------------------------------------
>>> Kernel build for CHROMEBOOK-SNOW started on Wed Jan 17 21:27:0=
4 CET 2024
--------------------------------------------------------------
=3D=3D=3D> CHROMEBOOK-SNOW
mkdir -p /usr/obj/mnt/zroot2/zroot2/OS/Chromebook/head-373300/arm.armv7/sys

--------------------------------------------------------------
>>> stage 1: configuring the kernel
--------------------------------------------------------------
cd /mnt/zroot2/zroot2/OS/Chromebook/head-373300/sys/arm/conf;  PATH=3D/usr/=
obj/mnt/zroot2/zroot2/OS/Ch
romebook/head-373300/arm.armv7/tmp/bin:/usr/obj/mnt/zroot2/zroot2/OS/Chrome=
book/head-373300/arm.armv
7/tmp/usr/sbin:/usr/obj/mnt/zroot2/zroot2/OS/Chromebook/head-373300/arm.arm=
v7/tmp/usr/bin:/usr/obj/m
nt/zroot2/zroot2/OS/Chromebook/head-373300/arm.armv7/tmp/legacy/usr/sbin:/u=
sr/obj/mnt/zroot2/zroot2/
OS/Chromebook/head-373300/arm.armv7/tmp/legacy/usr/bin:/usr/obj/mnt/zroot2/=
zroot2/OS/Chromebook/head
-373300/arm.armv7/tmp/legacy/bin:/usr/obj/mnt/zroot2/zroot2/OS/Chromebook/h=
ead-373300/arm.armv7/tmp/
legacy/usr/libexec::/sbin:/bin:/usr/sbin:/usr/bin  config  -d /usr/obj/mnt/=
zroot2/zroot2/OS/Chromebo
ok/head-373300/arm.armv7/sys/CHROMEBOOK-SNOW  -I '/mnt/zroot2/zroot2/OS=
/Chromebook/head-373300/sys/a
rm/conf' -I '/mnt/zroot2/zroot2/OS/Chromebook/head-373300/sys/arm/c=
onf'  '/mnt/zroot2/zroot2/OS/Chro
mebook/head-373300/sys/arm/conf/CHROMEBOOK-SNOW'
WARNING: duplicate option `DEBUG' encountered.


./head-373300/sys/arm/conf/CHROMEBOOK-SNOW: unknown option "IPI_IRQ_EN=
D" / "IPI_IRQ_START / ARM_L2_PIPT"
and so on..=
.

these options are included inside the file "std.ex=
ynos5250" (that I have copied from the old to the new
so=
urce code). What I'm trying to do to stop these error is to comment the=
 offending lines :

nano ./head-373300/sys/arm/samsung/exy=
nos/std.exynos5250 :

#options    IPI_IRQ_START=3D0
#options    IPI_IRQ_END=3D15
#options  =
  ARM_L2_PIPT

but I suspect that a lot= of options will be missing and the more comments I will make,the more the = chance that it will not work will increase. ...

On Mon, Jan 15, 2024= at 7:48=E2=80=AFPM Mario Marietto <marietto2008@gmail.com> wrote:
Hello.

Do you have deleted forever the set of packages and ports for FreeBS= D 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 expert= ise.

On Mon, Jan 15, 2024 at 7:15=E2=80=AFPM David Chisnall <= theraven@freebsd.= org> wrote:
On 15 Jan 2024, at 16:46, Mario Marietto <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.


--
Mario.
--000000000000fedfbc060f2c216d--