From nobody Sat Nov 25 22:20:33 2023 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 4Sd5sh32Cpz528pS; Sat, 25 Nov 2023 22:21:12 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (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 4Sd5sh0FJrz3fc5; Sat, 25 Nov 2023 22:21:12 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x633.google.com with SMTP id a640c23a62f3a-a00191363c1so445272766b.0; Sat, 25 Nov 2023 14:21:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700950870; x=1701555670; 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=t/lSNxASWRvsK2cphJI1ZwX564P/D/fkfRr4BwwJkyA=; b=jkrnr40BYs43XvUxtYhA+UdOh6tOUfNhMjLZTZBkmoTgDQG+XGp5JniHEN6Sqefl37 VIZ+LdGQUvf0omiX/o+lHFVeEOwFrqUEQZr1KVdCETfeOcR8Tj2Cce/+ESvuJiG2gpH3 daKP0mlClK4KLAFBF62bT66HAnO7qmGgjSKG7s16c3syIHWLmJsJQyJ3+OEbF+Cce21K HTaZOJr6FNSZZO28IpEmto4LWkUAabtt3Tz+mlJby3SPzJRqPyMrkODjXx+9CvxfG7NI 3Vuvy3vjDPUeM31FuTwh8DaSkXGMVYfQo/hQ9KV8qxJSgPSwbnROB0Y0/bVOW9oiZ5wH T4PA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700950870; x=1701555670; 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=t/lSNxASWRvsK2cphJI1ZwX564P/D/fkfRr4BwwJkyA=; b=INwETliex+aPCGivvr38h9lXRAahV/MFa+nLqEVuqCiyI/WPomVY5b8U/6mboKAx06 jrKdeMDVNQpHTx5Su4O2Y4ylFdHcCLqjanfMjHzUMWEX0VQUwRtaO4Haj6J5x2T1q8kg BYrlok0kyP6OjAfcdMnSH0tIpG+hlYS5TPfiVMFYf+muvXa5o1+boWNnzTlLBtEz4CqM EbUIL6Iytnr94zO3FScwgBM8krwPj6PW9SSwkcMsUdUoG0+UVbPHW5ueTJIb6y5G1ggO rqGCHXooLdJA6D7fBCzHHzl/O8Ho5mG0Ob7ei+rctXfLS0lwmzXE71Qjr2yUROHIRY3K c2YA== X-Gm-Message-State: AOJu0YwQBu0HE7pjK1sEKJY81qTvK6+G9QvCiBHkru5/HMpjZHYYju4Q mI2uJC+pc9mVHMJ50IVrgtuUUj9MooAm4kOREFHY7zOyeKY= X-Google-Smtp-Source: AGHT+IEhkzwilMD6ERaL2bwBn3rOcuTDkx1lGUDZ5xkUD+poku47ky/zmkiWI0tfZHohL3AQulxcriuBDhJofy1Va5I= X-Received: by 2002:a17:906:dfcf:b0:a04:937a:f8b0 with SMTP id jt15-20020a170906dfcf00b00a04937af8b0mr5281464ejc.28.1700950869800; Sat, 25 Nov 2023 14:21:09 -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: Sat, 25 Nov 2023 23:20:33 +0100 Message-ID: Subject: Re: Should we boot the FreeBSD kernel in ELF format or in zImage format ? How? To: Warner Losh Cc: freebsd-hackers , freebsd-arm@freebsd.org, FreeBSD Current , FreeBSD Mailing List , freebsd-xen@freebsd.org, royger@freebsd.org Content-Type: multipart/alternative; boundary="0000000000005ff95f060b017cde" 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] X-Rspamd-Queue-Id: 4Sd5sh0FJrz3fc5 --0000000000005ff95f060b017cde Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I really don't know where to start. It sounds too technical for me. I don't even know what to ask to understand where to start. mmm...can someone provide some documentation ? but not too much dense with technicalities. Thanks. On Sat, Nov 25, 2023 at 6:02=E2=80=AFPM Warner Losh wrote: > > > On Sat, Nov 25, 2023 at 4:41=E2=80=AFAM Mario Marietto > wrote: > >> Hello to everyone. >> >> we have just virtualized Debian 12 on our arm (32 bit) Chromebook. As >> host / dom0 we have chosen Devuan 5,and for guest / domU,Debian 12. It >> works great. But our goal is different. We want to virtualize FreeBSD as >> domU. Can we have a working Xen PV network driver for a FreeBSD arm gues= t >> ?. I found that Julien Grall has ported the Xen drivers to FreeBSD on ar= m. >> I would like to know if Julien's work was accepted upstream by FreeBSD, = in >> which case FreeBSD as a Xen guest on arm should work if we enable the Xe= n >> PV drivers in the FreeBSD on arm kernel. If Julien's work was not accept= ed >> upstream by FreeBSD, we will have to find his patches and apply them >> ourselves to the FreeBSD on arm kernel. >> >> We found these slides : >> >> >> https://events.static.linuxfound.org/sites/events/files/slides/Porting%2= 0FreeBSD%20on%20Xen%20on%20ARM%20.pdf >> >> Slide 13 refers to a XENHVM FreeBSD on arm kernel config - that is what >> we want to find. >> >> It looks like when that slide presentation was written, there were some >> limitations on FreeBSD Xen guests. For example, for our debian bookworm >> guest, I am using vcpus =3D '2' to match the number of real cpus on our >> Chromebook, but slide 13 mentions support for only 1 VCPU with a FreeBSD >> guest, so I will need to change that vcpus =3D '1' in the FreeBSD guest >> config unless support for 2 or more vcpus was added later, which is >> possible because that slide presentation is 9 years old. >> >> Here is where I would expect to find the XENHVM FreeBSD on arm kernel >> config file: >> >> https://cgit.freebsd.org/src/tree/sys/arm/conf >> >> But it is not there unless I am not understanding something correctly. >> For now, unfortunately conclude that the support for Xen on arm that Jul= ien >> Grall mentioned in that slide presentation 9 years ago was never added t= o >> the official FreeBSD source code. I am searching the web now to see if t= he >> patches that Julien Grall wrote are still posted somewhere online. If we >> cannot find them, we can ask here and on the xen-users mailing list. Jul= ien >> regularly reads that list and responds to question about Xen on arm, so = I >> think he will tell us how to find the patches if we cannot find them onl= ine. >> >> According to this page from the FreeBSD wiki: >> >> https://wiki.freebsd.org/Xen >> >> I think FreeBSD only supports Xen on x86, not arm. So this is going to b= e >> a bit of a challenge to get a Xen FreeBSD guest on arm working. We know >> Julien Grall has some patches that made it work in the past ! >> >> I found a slightly newer slide presentation by Julien here: >> >> https://www.slideshare.net/xen_com_mgr/bsdcan-2015-how-to-port-your-bsd >> >> It is about the same, but it mentions the GENERIC FreeBSD kernel support= s >> Xen on arm64, but still says we need the XENHVM FreeBSD config for Xen o= n >> arm 32 bit, which I haven't found online yet. >> >> Please,take a look at this output of the linux kernel that can boot on >> Xen, and the FreeBSD kernel that cannot : >> >> >> % file zImage-6.1.59-stb-xen-cbe+ >> zImage-6.1.59-stb-xen-cbe+: Linux kernel ARM boot executable zImage (lit= tle-endian) >> >> % file FREEBSD-XENVIRT >> FREEBSD-XENVIRT: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV),= dynamically linked, interpreter /red/herring, for FreeBSD 11.0 (1100048), = not stripped >> >> >> The FreeBSD kernel that won't boot is in ELF format but the Linux kernel >> that does boot is in zImage format. >> >> I spent time reading the docs on xenbits.xenproject.org, and according >> to those docs Xen on arm only knows how to boot a kernel in the zImage >> format, so the FreeBSD kernel is in a format that modern Xen incorrectly >> detects as an x86 kernel. >> >> I also watched Julien Grall's 30 minute video presentation of his work t= o >> boot FreeBSD/arm on Xen at FOSDEM 2014 here : >> >> https://archive.fosdem.org/2014/schedule/event/freebsd_xen_arm/ >> >> In that video, and in other places, Julien mentions that the boot ABI fo= r >> FreeBSD/arm on Xen was not yet developed and he was getting occasional >> crashes and needed to investigate the problem. He mentioned the zImage A= BI >> that Linux uses, but pointed out FreeBSD does not use that format, and b= ack >> then it was an open question which format to use to boot FreeBSD/arm on >> Xen. Unfortunately, nine years later, the only supported format is still >> the zImage format that Linux uses. >> >> It looks like Julien's work back then was using an ELF binary to boot >> FreeBSD/arm on Xen instead of the supported zImage format that Linux use= s >> and the modern Xen toolstack exits with an error when trying to boot the >> FreeBSD ELF formatted binary that Julien's patch creates. So the best >> solution would be to try to port the rules to build a FreeBSD kernel in = the >> zImage format instead of the ELF format. I have been studying the Makefi= les >> in Linux to see how Linux builds the Linux arm kernel in the zImage form= at, >> but it is not trivial to understand >> > > Look at kernel.bin in FreeBSD's kernel. It's enabled -DWITH_KERNEL_BIN. I= t > should be easy to adapt the target to build that. I've done similar thing= s > with u-boot formats in the past, but that was 4 employers and 20 years ag= o > now. > > This path is not well trod. I do know that arm64 virtualization with bhyv= e > is hitting the tree. I'm not sure how easy/hard this will be to modernize= . > I'm interested to see how your explorations go. > > Warner > --=20 Mario. --0000000000005ff95f060b017cde Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I really don't know where to start. It sounds too tech= nical for me. I don't even know what to ask to understand where to star= t. mmm...can someone provide some documentation ? but not too much dense wi= th technicalities. Thanks.

On Sat, Nov 25, 2023 at 6:02=E2=80=AFPM Warn= er Losh <imp@bsdimp.com> wrote:=


On Sat, Nov 25, 2023 at 4:41=E2=80=AFAM Mario Mariet= to <marietto= 2008@gmail.com> wrote:
= Hello to everyone.

we have just virtualized Debian 12 on our ar= m (32 bit) Chromebook. As host / dom0 we have chosen Devuan 5,and for guest / domU,Debian 12. It=20 works great. But our goal is different. We want to virtualize FreeBSD as domU. Can we have a working Xen PV network driver for a FreeBSD arm=20 guest ?. I found that Julien Grall has ported the Xen drivers to FreeBSD on arm. I would like to know if Julien's work was accepted upstream by= =20 FreeBSD, in which case FreeBSD as a Xen guest on arm should work if we=20 enable the Xen PV drivers in the FreeBSD on arm kernel. If Julien's wor= k was not accepted upstream by FreeBSD, we will have to find his patches=20 and apply them ourselves to the FreeBSD on arm kernel.

We found these slides :

https://events.static.linuxfound.org/sites/events/file= s/slides/Porting%20FreeBSD%20on%20Xen%20on%20ARM%20.pdf

Slide 13 refers to a XENHVM FreeBSD on arm kernel config - that is what = we want to find.

It looks like when that slide presentation was written, there were=20 some limitations on FreeBSD Xen guests. For example, for our debian=20 bookworm guest, I am using vcpus =3D '2' to match the number of rea= l cpus=20 on our Chromebook, but slide 13 mentions support for only 1 VCPU with a=20 FreeBSD guest, so I will need to change that vcpus =3D '1' in the F= reeBSD=20 guest config unless support for 2 or more vcpus was added later, which=20 is possible because that slide presentation is 9 years old.

Here is where I would expect to find the XENHVM FreeBSD on arm kernel co= nfig file:

https://cgit.freebsd.org/src/tree/sys/arm/= conf

But it is not there unless I am not understanding something=20 correctly. For now, unfortunately conclude that the support for Xen on=20 arm that Julien Grall mentioned in that slide presentation 9 years ago=20 was never added to the official FreeBSD source code. I am searching the=20 web now to see if the patches that Julien Grall wrote are still posted=20 somewhere online. If we cannot find them, we can ask here and on the=20 xen-users mailing list. Julien regularly reads that list and responds to question about Xen on arm, so I think he will tell us how to find the=20 patches if we cannot find them online.

According to this page from the FreeBSD wiki:

https://wiki.freebsd.org/Xen

I think FreeBSD only supports Xen on x86, not arm. So this is going=20 to be a bit of a challenge to get a Xen FreeBSD guest on arm working. We know Julien Grall has some patches that made it work in the past !

I found a slightly newer slide presentation by Julien here:

https://www.slide= share.net/xen_com_mgr/bsdcan-2015-how-to-port-your-bsd

It is about the same, but it mentions the GENERIC FreeBSD kernel=20 supports Xen on arm64, but still says we need the XENHVM FreeBSD config=20 for Xen on arm 32 bit, which I haven't found online yet.

Please,take a look at this output of the linux kernel that can boot on X= en, and the FreeBSD kernel that cannot :


% file zImage-6.1.59-stb-xen-cbe+
zImage-6.1.59-stb-xen-cbe+: Linux kernel ARM boot executable zImage (little=
-endian)

% file FREEBSD-XENVIRT         =20
FREEBSD-XENVIRT: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dy=
namically linked, interpreter /red/herring, for FreeBSD 11.0 (1100048), not=
 stripped


The FreeBSD kernel that won't boot is in ELF format but t= he Linux kernel that does boot is in zImage format.

I spent time reading the docs on xenbits.xenproject.org, and=20 according to those docs Xen on arm only knows how to boot a kernel in=20 the zImage format, so the FreeBSD kernel is in a format that modern Xen=20 incorrectly detects as an x86 kernel.

I also watched Julien Grall's 30 minute video presentation of his wo= rk to boot FreeBSD/arm on Xen at FOSDEM 2014 here :

https://archive.fosdem.or= g/2014/schedule/event/freebsd_xen_arm/

In that video, and in other places, Julien mentions that the boot ABI for FreeBSD/arm on Xen was not yet developed and he was getting=20 occasional crashes and needed to investigate the problem. He mentioned=20 the zImage ABI that Linux uses, but pointed out FreeBSD does not use=20 that format, and back then it was an open question which format to use=20 to boot FreeBSD/arm on Xen. Unfortunately, nine years later, the only=20 supported format is still the zImage format that Linux uses.

It looks like Julien's work back then was using an ELF binary to boo= t FreeBSD/arm on Xen instead of the supported zImage format that Linux=20 uses and the modern Xen toolstack exits with an error when trying to=20 boot the FreeBSD ELF formatted binary that Julien's patch creates. So= =20 the best solution would be to try to port the rules to build a FreeBSD=20 kernel in the zImage format instead of the ELF format. I have been=20 studying the Makefiles in Linux to see how Linux builds the Linux arm=20 kernel in the zImage format, but it is not trivial to understand

<= /div>

Look at kernel.bin = in FreeBSD's kernel. It's enabled -DWITH_KERNEL_BIN. It should be e= asy to adapt the target to build that. I've done similar things with u-= boot formats in the past, but that was 4 employers and 20 years ago now.

This path is not well trod. I do know that arm64= virtualization with bhyve is hitting the tree. I'm not sure how easy/h= ard this will be to modernize. I'm interested to see how your explorati= ons go.

Warner


--
Mario.
--0000000000005ff95f060b017cde-- From nobody Sun Nov 26 00:11:39 2023 X-Original-To: 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 4Sd8Kk6xSDz51mxW for ; Sun, 26 Nov 2023 00:12:10 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Sd8Kk2xHGz3CK8 for ; Sun, 26 Nov 2023 00:12:09 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; none Received: from kalamity.joker.local (123-1-22-158.area1b.commufa.jp [123.1.22.158]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 3AQ0BetS003793; Sun, 26 Nov 2023 09:11:40 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Sun, 26 Nov 2023 09:11:39 +0900 From: Tomoaki AOKI To: current@freebsd.org Cc: David Wolfskill Subject: Re: [resolved] After update to main-n266611-49a83b94395a: panic: bus_generic_rman_activate_resource Message-Id: <20231126091139.4afa51dbc0149d48eaa9449f@dec.sakura.ne.jp> In-Reply-To: References: <20231126043633.15c60223c7a518d103b6dbef@dec.sakura.ne.jp> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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:7684, ipnet:153.125.128.0/18, country:JP] X-Rspamd-Queue-Id: 4Sd8Kk2xHGz3CK8 On Sat, 25 Nov 2023 12:16:49 -0800 David Wolfskill wrote: > On Sun, Nov 26, 2023 at 04:36:33AM +0900, Tomoaki AOKI wrote: > > Hi. > > > > Not tested, but does upgrading to commit ed88eef140a1 [1] and later > > help? (I'm still at commit 5d4f897f88ed on main.) > > > > [1] > > https://cgit.freebsd.org/src/commit/?id=ed88eef140a1c3d57d546f409c216806dd3da809 > > > > Regards. > > .... > > Yes; thank you (and jhb@): after hand-applying the ed88eef140a1 commit & > rebuilding, the laptop rebooted OK: > > g1-48(15.0-C)[1] uname -aUK > FreeBSD g1-48.catwhisker.org 15.0-CURRENT FreeBSD 15.0-CURRENT #530 main-n266611-49a83b94395a-dirty: Sat Nov 25 20:04:25 UTC 2023 root@g1-48.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 1500004 1500004 > > Peace, > david > -- > David H. Wolfskill david@catwhisker.org > The notion that anyone would perceive a need to "make neo-Nazis > look bad" is about as absurd as perceiving a need to "hydrate" water. > > See https://www.catwhisker.org/~david/publickey.gpg for my public key. Glad to hear it helped. :-) And sorry, I should have noted that commit ed88eef140a1 is the next commit after 49a83b94395a, which you had been bitten by the issue. Regards. -- Tomoaki AOKI From nobody Mon Nov 27 05:33:21 2023 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 4SdvQ673YBz51mhc for ; Mon, 27 Nov 2023 05:33:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (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 4SdvQ56Rhyz3JZM for ; Mon, 27 Nov 2023 05:33:33 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20230601.gappssmtp.com header.s=20230601 header.b=A46MUsd0; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2a00:1450:4864:20::131) smtp.mailfrom=wlosh@bsdimp.com; dmarc=none Received: by mail-lf1-x131.google.com with SMTP id 2adb3069b0e04-507a0907896so4975459e87.2 for ; Sun, 26 Nov 2023 21:33:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1701063212; x=1701668012; darn=freebsd.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=xcpPJ+0EdrKW14b285uhX9MViCjAi0DOxZ8aFNBRbWA=; b=A46MUsd0Pldx2xq2QpZgI2VzihSKmDmbZ1Yd/yGrffvKN9QTInGqYrMSMLHS7ARyhm NYlIpClQqb92vGkdaQf0ymoiaI2k+fTAkIaO5+yQk07vqRDnTB97zyCQcO+ebwyC4dga E8q4zzlBxUJBA1oAvbY5jOwdKeKwC6QpbjW1lHM+qpB9jaAPhsD9pCXg27/f+wxR8meX ysgj2f+ctSMx5XFILkC5oQHCaqb3cBKjpoyaXL+pSIRXnHMzqCgB8fbMUVXHirSTcZUl K0HT/cUN7CUQwOY8wtb7fkSZ4E9kKaYy2QdcmiS0bmUxnVPJuCI2c8WFiPKBkk2RWgw7 1V+w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701063212; x=1701668012; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=xcpPJ+0EdrKW14b285uhX9MViCjAi0DOxZ8aFNBRbWA=; b=Oeq3m42f73RapKYpt43NwFjfCI+1ZnFFk6QKwwTTT95w/UN6Y8uVE93O6Or1y1Q6Jj PEQ12lQlabqDiyXjFHn+Qlkrp0NZpGWKId1hsNZjGjKAGgxb+A5ZWfosqxRxn9IyzU2N 5+rQ5XmhHI2F+fuQyU9kk3CK709m+tPAPtawZ8jnEb2uv7y0upcxpmYsZO9h5PYfx+it Wp8KDFx/I6r56UquK7/Y0KKG9KebI0OISdV/UNVGhGCC1c6tROHM2qQ3eEHtYdaleJp8 RCBgecRwXt3p4if2LFixiiBRvifrt+Q3tNw0W9voKcCwqJ+BiwVZDB0rYBVse9iMdGYz MJPA== X-Gm-Message-State: AOJu0YzT2tLV03KCYcI1XGWFOHn1Vc/bNfPmrUGxO5s6/OnUZFe0wNBk Wx+tBTIqC7oILJtsJQKOS8QW+yDZr0GEUh/pf80GlPwaz0UnrFqd X-Google-Smtp-Source: AGHT+IGgJoSymScvvR+povPQmbwxwDxpa0Jbhe35CZPDD94fuSjS6VerMwayvbhXJerPVyK79IO77Vn0Bqom1XCY1D0= X-Received: by 2002:ac2:4a6b:0:b0:509:44d5:18e5 with SMTP id q11-20020ac24a6b000000b0050944d518e5mr5425522lfp.63.1701063212157; Sun, 26 Nov 2023 21:33:32 -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 From: Warner Losh Date: Sun, 26 Nov 2023 22:33:21 -0700 Message-ID: Subject: Heads up: lots of churn, nothing interesting will come of it (I hope) To: FreeBSD Current Content-Type: multipart/alternative; boundary="00000000000080627c060b1ba435" X-Spamd-Result: default: False [-3.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20230601.gappssmtp.com:s=20230601]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::131:from]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_ONE(0.00)[1]; R_SPF_NA(0.00)[no SPF record]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20230601.gappssmtp.com:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[bsdimp.com]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com] X-Rspamd-Queue-Id: 4SdvQ56Rhyz3JZM X-Spamd-Bar: -- --00000000000080627c060b1ba435 Content-Type: text/plain; charset="UTF-8" OK. I have pushed 4 series of commits. (1) remove sccs IDs by and large (a couple of exceptions where @(#) didn't mark an SCCS id). (2) remove if 0'd copyright strings. (3) Mechanical changes to most of the tree to cleanup style divots after these changes (and the $FreeBSD$ removal) (4) cdefs.h cleanups. I also bumped FreeBSD_version. I chunked these a bit differently than for $FreeBSD$ so any given file will only have 2 or 3 commits rather than half a dozen. I've done a test MFC and this chunking shouldn't cause problems, but I've not pushed that since a couple of last second snags changed most of the hashes, so I have to redo it. I did all of these all at once so that there'd be only one rebuild for most people. I plan on doing a MFC to stable/14 (it doesn't look too horrible), but not to stable/13 unless there's demand. It's too churny, IMHO, for a branch at that point of maturity. I tried to triple check everything, and to not delete too much. I did an exp run on the cdefs changes. All most people will notice is really long incremental rebuilds.... I hope... This should be the last wide-scale cleanup like this. There may be some minor mop of that follows this commit, but there's no more tree-wide changes on the horizon. I do plan on plowing forward, though, with my cdefs.h cleanup, though not until after the first of the year. If my expectations are in error, or you've noticed a mistake in all this, please let me know. Warner --00000000000080627c060b1ba435 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
OK. I have pushed 4 series of commits. (1) remove sccs IDs= by and large (a couple of exceptions=C2=A0where @(#) didn't mark an SC= CS id). (2) remove if 0'd copyright strings. (3) Mechanical changes to = most of the tree to cleanup style divots after these changes (and the $Free= BSD$ removal) (4) cdefs.h cleanups. I also bumped FreeBSD_version. I chunke= d these a bit differently than for $FreeBSD$ so any given file will only ha= ve 2 or 3 commits=C2=A0rather than half a dozen. I've done a test MFC a= nd this chunking shouldn't cause problems, but I've not pushed that= since a couple of last second snags changed most of the hashes, so I have = to redo it.

I did all of these all at once so that there= 'd be only one rebuild for most people. I plan on doing a MFC to stable= /14 (it doesn't look too horrible), but not to stable/13 unless there&#= 39;s demand. It's too churny, IMHO, for a branch at that point of matur= ity.

I tried to triple=C2=A0check everything, and = to not delete too much. I did an exp run on the cdefs changes. All most peo= ple will notice is really long incremental rebuilds....=C2=A0 I hope...

This should be the last wide-scale cleanup like this.= There may be some minor mop of that follows this commit, but there's n= o more tree-wide changes on the horizon. I do plan on plowing forward, thou= gh, with my cdefs.h cleanup, though not until after the first of the year.<= /div>

If my expectations are in error, or you've not= iced a mistake in all this, please let me know.

Wa= rner
--00000000000080627c060b1ba435-- From rmd@orbit.in-berlin.de Mon Nov 27 16:25:06 2023 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 4Sf9sy4Fmyz52PmC for ; Mon, 27 Nov 2023 16:25:10 +0000 (UTC) (envelope-from rmd@orbit.in-berlin.de) Received: from einhorn-mail-out.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) (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 (4096 bits) client-digest SHA256) (Client CN "mail.in-berlin.de", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Sf9sw720kz3DGk for ; Mon, 27 Nov 2023 16:25:08 +0000 (UTC) (envelope-from rmd@orbit.in-berlin.de) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of rmd@orbit.in-berlin.de designates 192.109.42.8 as permitted sender) smtp.mailfrom=rmd@orbit.in-berlin.de; dmarc=none X-Envelope-From: rmd@orbit.in-berlin.de X-Envelope-To: Received: from authenticated.user (localhost [127.0.0.1]) by einhorn.in-berlin.de with ESMTPSA id 3ARGP63J407019 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT) for ; Mon, 27 Nov 2023 17:25:06 +0100 Received: from cygnus.imp.fu-berlin.de (cygnus.imp.fu-berlin.de [160.45.110.43]) by webmail.in-berlin.de (Horde Framework) with HTTPS; Mon, 27 Nov 2023 17:25:06 +0100 Date: Mon, 27 Nov 2023 17:25:06 +0100 Message-ID: <20231127172506.Horde.iiBmVTtnl5OM_J0h4cvdd7M@webmail.in-berlin.de> From: "Rolf M. Dietze" To: freebsd-current@freebsd.org Subject: CDE on FreeBSD 14.0 Release In-Reply-To: <20221127161544.7dd1207c@thor.intern.walstatt.dynvpn.de> User-Agent: Horde Application Framework 5 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes 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 Content-Disposition: inline X-Spamd-Result: default: False [-3.50 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_ALLOW(-0.20)[+ip4:192.109.42.0/24]; RWL_MAILSPIKE_GOOD(-0.10)[192.109.42.8:from]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[192.109.42.8:from]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:29670, ipnet:192.109.42.0/24, country:DE]; R_DKIM_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; DMARC_NA(0.00)[orbit.in-berlin.de]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4Sf9sw720kz3DGk X-Spamd-Bar: --- Hi, might be that I am on the wrong list for this, since my Problem exists on 14.0Release. After an out of the box install of FreeBSD 14.0 Release and following https://forums.freebsd.org/threads/setting-up-common-desktop-environment-for-modern-use.69475/ I am stuck with CDE. CDE loads, dtlogin starts an presents the login or greeter window, but upon logging in I get a popup telling "The desktop messaging system could not be started". Guess I am missing some config steps. Any pointer for further reading? I had CDE running on 13.2Release yours, Rolf From nobody Mon Nov 27 16:33:57 2023 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 4SfB4q4Gjsz52VSD for ; Mon, 27 Nov 2023 16:34:35 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-ej1-x634.google.com (mail-ej1-x634.google.com [IPv6:2a00:1450:4864:20::634]) (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 4SfB4q2dJtz3H7f for ; Mon, 27 Nov 2023 16:34:35 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x634.google.com with SMTP id a640c23a62f3a-a0bdf4eeb46so270440566b.3 for ; Mon, 27 Nov 2023 08:34:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1701102874; x=1701707674; 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=p4X1jxPjkLw6g/03O+vWvtYEmRJUK/V+VX1XxrRatyU=; b=nNHw3fTyX+NrnIwNnXbbSs9CLRVjoaPYlsoIuEoRYKfEhj9Df0rDOSizbNg/tnfZzu H6R3JyIRf3FciqX5F0CCpzed69lwId+2uEMAiy0li1q7m+ErLcz4WuEUDkcizguZxgoJ I6PvYtG5j2cUdmV61qpZ6Nadgt0bdCq9VMZj8J8bcIIWTTkexCNpjCk10r+H1f0Dwsnf AflDp3GWsW4n/jtS6ZOpG4PLTNPZlOa92674GLT9UZQLEaUTxX5FyFgBNeSv1c4dH6Gh 5RLRU+AK2PQwOq2YDHewHuNFvd9mOICaQOSVn7Nn//tH6yixBNsCNsOeH1gAhmkrc3RX GYCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701102874; x=1701707674; 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=p4X1jxPjkLw6g/03O+vWvtYEmRJUK/V+VX1XxrRatyU=; b=R9/GodRCb2bdQYbtfUaqIvQWqPHakzRLa7IZnhuHUFAPPs1CwIfxDWvRAQACSvXPcM 74cncX7NE+PNWvcfxMrqgH6eaHAs7+hWhD2GmpBglIqfR6VRDhQbPUr80DJt9bNgU71P iwKA4SuoO8LOXMfXgMRdzHKuMAdrDR/e3z8yc0wAj/36TlviYr++fasZ5gD1/BDmoKfJ 3XWTCPQR/WuGxIeK9t7bUrEZFe8sQjU+G0m1sIJDbnkjXdMZjUQETFKfo7Jyp26+zKet EbsFONnZJyRiqaq4L2hsSxrVsHw7u8lQ+7ApWc1uWzSUiVPR+Nc5wqbTLnLcKsq5GVok IQWw== X-Gm-Message-State: AOJu0Yz9ZD4OIuwjL5x7Jq9BrPpruIw7pzvO+jrYkq314HMt/IIcOZiT AbMrQisYr1q2/xn/+ShqUJTquNa5CvcG7Jbdskxv5YxgCZ+GbVG7 X-Google-Smtp-Source: AGHT+IHmFj/3IO+TtJ/GYLp24b7xm+NoX6PKWrgRpfj8Nn9eUkU4ncnMD+C4mjb0lcIOZ3MUcdFjc6Vf3tAye/eZi3U= X-Received: by 2002:a17:906:750:b0:a00:570c:54fb with SMTP id z16-20020a170906075000b00a00570c54fbmr8973610ejb.35.1701102873552; Mon, 27 Nov 2023 08:34:33 -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: <20221127161544.7dd1207c@thor.intern.walstatt.dynvpn.de> <20231127172506.Horde.iiBmVTtnl5OM_J0h4cvdd7M@webmail.in-berlin.de> In-Reply-To: <20231127172506.Horde.iiBmVTtnl5OM_J0h4cvdd7M@webmail.in-berlin.de> From: Mario Marietto Date: Mon, 27 Nov 2023 17:33:57 +0100 Message-ID: Subject: Re: CDE on FreeBSD 14.0 Release To: "Rolf M. Dietze" Cc: freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000812bec060b24e007" 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] X-Rspamd-Queue-Id: 4SfB4q2dJtz3H7f --000000000000812bec060b24e007 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I asked the same recently and I'd got a good answer,here : https://forums.FreeBSD.org/threads/cde-users-unite.85143/post-576559 On Mon, Nov 27, 2023 at 5:25=E2=80=AFPM Rolf M. Dietze wrote: > Hi, > > might be that I am on the wrong list for this, since my Problem > exists on 14.0Release. > > After an out of the box install of FreeBSD 14.0 Release and following > > https://forums.freebsd.org/threads/setting-up-common-desktop-environment-= for-modern-use.69475/ > I am stuck with CDE. CDE loads, dtlogin starts an presents the login > or greeter window, but upon logging in I get a popup telling > "The desktop messaging system could not be started". Guess I am > missing some config steps. Any pointer for further reading? > I had CDE running on 13.2Release > > yours, Rolf > > > --=20 Mario. --000000000000812bec060b24e007 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I asked the same recently and I'd got a good answ= er,here :


On Mon, Nov 27, 2023 at 5:25=E2= =80=AFPM Rolf M. Dietze <rmd@o= rbit.in-berlin.de> wrote:
Hi,

might be that I am on the wrong list for this, since my Problem
exists on 14.0Release.

After an out of the box install of FreeBSD 14.0 Release and following
https:= //forums.freebsd.org/threads/setting-up-common-desktop-environment-for-mode= rn-use.69475/
I am stuck with CDE. CDE loads, dtlogin starts an presents the login
or greeter window, but upon logging in I get a popup telling
"The desktop messaging system could not be started". Guess I am missing some config steps. Any pointer for further reading?
I had CDE running on 13.2Release

yours, Rolf




--
Mario.
--000000000000812bec060b24e007-- From rmd@orbit.in-berlin.de Mon Nov 27 17:20:16 2023 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 4SfC5b4zXgz52vCG for ; Mon, 27 Nov 2023 17:20:19 +0000 (UTC) (envelope-from rmd@orbit.in-berlin.de) Received: from einhorn-mail-out.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) (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 (4096 bits) client-digest SHA256) (Client CN "mail.in-berlin.de", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SfC5Z0z9Zz3ZPG for ; Mon, 27 Nov 2023 17:20:17 +0000 (UTC) (envelope-from rmd@orbit.in-berlin.de) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of rmd@orbit.in-berlin.de designates 192.109.42.8 as permitted sender) smtp.mailfrom=rmd@orbit.in-berlin.de; dmarc=none X-Envelope-From: rmd@orbit.in-berlin.de X-Envelope-To: Received: from authenticated.user (localhost [127.0.0.1]) by einhorn.in-berlin.de with ESMTPSA id 3ARHKGnI461107 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT) for ; Mon, 27 Nov 2023 18:20:16 +0100 Received: from cygnus.imp.fu-berlin.de (cygnus.imp.fu-berlin.de [160.45.110.43]) by webmail.in-berlin.de (Horde Framework) with HTTPS; Mon, 27 Nov 2023 18:20:16 +0100 Date: Mon, 27 Nov 2023 18:20:16 +0100 Message-ID: <20231127182016.Horde.qf5KaugAa34H74MBdC1gBtB@webmail.in-berlin.de> From: "Rolf M. Dietze" To: freebsd-current@freebsd.org Subject: Re: CDE on FreeBSD 14.0 Release References: <20221127161544.7dd1207c@thor.intern.walstatt.dynvpn.de> <20231127172506.Horde.iiBmVTtnl5OM_J0h4cvdd7M@webmail.in-berlin.de> In-Reply-To: <20231127172506.Horde.iiBmVTtnl5OM_J0h4cvdd7M@webmail.in-berlin.de> User-Agent: Horde Application Framework 5 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes 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 Content-Disposition: inline X-Spamd-Result: default: False [-2.67 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_ALLOW(-0.20)[+ip4:192.109.42.0/24]; NEURAL_HAM_SHORT(-0.17)[-0.174]; RWL_MAILSPIKE_GOOD(-0.10)[192.109.42.8:from]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[192.109.42.8:from]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:29670, ipnet:192.109.42.0/24, country:DE]; R_DKIM_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; DMARC_NA(0.00)[orbit.in-berlin.de]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4SfC5Z0z9Zz3ZPG X-Spamd-Bar: -- Hi, sorry for this, user error... I did put a dtlogin_enable="YES" in /etc/rc.conf having the dtlogin copied to /usr/local/etc/rcd This did not work. Just having a /usr/local/dt/bin/dtlogin in /etc/rc.local as it is outlined in the link below, does work. Still, having an issue with dtspc upon startup, but CDE works fine /rmd Quoting "Rolf M. Dietze" : > Hi, > > might be that I am on the wrong list for this, since my Problem > exists on 14.0Release. > > After an out of the box install of FreeBSD 14.0 Release and following > https://forums.freebsd.org/threads/setting-up-common-desktop-environment-for-modern-use.69475/ > I am stuck with CDE. CDE loads, dtlogin starts an presents the login > or greeter window, but upon logging in I get a popup telling > "The desktop messaging system could not be started". Guess I am > missing some config steps. Any pointer for further reading? > I had CDE running on 13.2Release > > yours, Rolf From nobody Mon Nov 27 19:21:36 2023 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 4SfFnn2vZ5z532Ls for ; Mon, 27 Nov 2023 19:21:49 +0000 (UTC) (envelope-from aak.freebsd@gmail.com) Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (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 4SfFnn2WVcz3NWm for ; Mon, 27 Nov 2023 19:21:49 +0000 (UTC) (envelope-from aak.freebsd@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x1033.google.com with SMTP id 98e67ed59e1d1-2839b418f7fso3548601a91.2 for ; Mon, 27 Nov 2023 11:21:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1701112908; x=1701717708; 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=rK9huNhCMSB/rcfx/sDHodE0IGrVtRR31rMSsLKCGZY=; b=louXAVM/SligmkDwtwgb5zj9rk1WkgWQVGujKHy/Vx02KJQnlvGr8CM91+Q4DMX9GW 8KAs6CUf7LG35nuAdZz06gxjOEGoxggXVwLPbtl/Z9ar8bANuY28aaUj8bUqS2BPqobL +AdXVecPuY9bLMnvZ7yR4n8MyKh15f8JAyX3AelecozXUCquxPTjbd9pb1T1lYlXIDKi iQnu1gWqo2mRVZmup47JxJWGIVd6e3XFqLYTHbTalqhUZ1kr5FJmxWbJ7Zg1R0f2ZIny H3qLj4kcuO3Cocgqqd6r7lAoLcCcgvhT+6OeJr+XLMlMmHQX+MPm4O2F/GLvdxVfM3Ef AUDA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701112908; x=1701717708; 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=rK9huNhCMSB/rcfx/sDHodE0IGrVtRR31rMSsLKCGZY=; b=RjPxF+r8ochyhFEqlLjRtUpo146T+9a+lzru4ElGm81V+mY4gDu6uz4Q6bSZjPG1La HDmbyt7NVCER25IV13AZoUBJhL0YQXPmyYiGI6aqGyR3lLn3LBbSpO+SfZ7EVT1iVFfi QWZrwV3qfh5jD4CCZauash/DSrsK/82demJD8c1Ox3E7cbZzgv1kw3dnRgLD+zvDRnuI rxLbLk8Fjz9+7BoYpQ5h8OFoSDdbd0R8GtqMJbH5j98I6ub29E+SNhMLIbQlrJ18q9i7 sz7I2BmAMSKIk+5pVV1Flbr274UgMnADvKwNtGRmi93bxlGkTOo2bozb0cdQOr4eNS+j qOSw== X-Gm-Message-State: AOJu0YwG3QYWKTANglfaMVErE5/bKb3jJEzmltYVREAw+7sDoCeXMdg2 WX3Ur4AJU7md0tMvStDbtc5KTKMnnPMgH6ASZwze3cFVimXTNg== X-Google-Smtp-Source: AGHT+IH1Yoj9G8D8M7y45hyB6DOjGjxISjfE5spxHLvYUnTyj0sAACLuvPgR/KBfH4Pt+p+h/aqjiapY1zq2nYqj0Vk= X-Received: by 2002:a17:90a:5a:b0:285:5e57:87ba with SMTP id 26-20020a17090a005a00b002855e5787bamr11626221pjb.18.1701112908150; Mon, 27 Nov 2023 11:21:48 -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: <20221127161544.7dd1207c@thor.intern.walstatt.dynvpn.de> <20231127172506.Horde.iiBmVTtnl5OM_J0h4cvdd7M@webmail.in-berlin.de> <20231127182016.Horde.qf5KaugAa34H74MBdC1gBtB@webmail.in-berlin.de> In-Reply-To: <20231127182016.Horde.qf5KaugAa34H74MBdC1gBtB@webmail.in-berlin.de> From: aak Date: Mon, 27 Nov 2023 22:21:36 +0300 Message-ID: Subject: Re: CDE on FreeBSD 14.0 Release To: "Rolf M. Dietze" Cc: freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="0000000000009cfd35060b27369f" 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)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4SfFnn2WVcz3NWm --0000000000009cfd35060b27369f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello! After installing CDE: # edit /etc/rc.conf dtlogin_enable=3D"YES" or # edit /etc/rc.local /usr/local/dt/bin/dtlogin -nodaemon # edit /usr/local/etc/X11/Xwrapper.config allowed_users=3Danybody # shutdown -r now There's nothing else you need to do On Tue, Nov 28, 2023 at 12:21=E2=80=AFAM Rolf M. Dietze wrote: > > > Hi, > sorry for this, user error... > > I did put a dtlogin_enable=3D"YES" in /etc/rc.conf having the > dtlogin copied to /usr/local/etc/rcd This did not work. > > Just having a /usr/local/dt/bin/dtlogin in /etc/rc.local as > it is outlined in the link below, does work. > > Still, having an issue with dtspc upon startup, but CDE works fine > > /rmd > > Quoting "Rolf M. Dietze" : > > > Hi, > > > > might be that I am on the wrong list for this, since my Problem > > exists on 14.0Release. > > > > After an out of the box install of FreeBSD 14.0 Release and following > > > https://forums.freebsd.org/threads/setting-up-common-desktop-environment-= for-modern-use.69475/ > > I am stuck with CDE. CDE loads, dtlogin starts an presents the login > > or greeter window, but upon logging in I get a popup telling > > "The desktop messaging system could not be started". Guess I am > > missing some config steps. Any pointer for further reading? > > I had CDE running on 13.2Release > > > > yours, Rolf > > > > > --0000000000009cfd35060b27369f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello!
After installing CDE:
# ed= it /etc/rc.conf
dtlogin_enable=3D"YES"
or
# edit /etc/rc.local
/usr/local/dt/bin/dtlogin -nodaemon

# edit /usr/local/etc/X11/Xwrapper.config
allowed_users=3Danybody

# shutdown -r now

There's nothing el= se you need to do

=
On Tue, Nov 28, 2023 at 12:21=E2=80= =AFAM Rolf M. Dietze <rmd@orbit.in-berlin.de> wrote:


Hi,
sorry for this, user error...

I did put a dtlogin_enable=3D"YES" in /etc/rc.conf having the
dtlogin copied to /usr/local/etc/rcd This did not work.

Just having a /usr/local/dt/bin/dtlogin in /etc/rc.local as
it is outlined in the link below, does work.

Still, having an issue with dtspc upon startup, but CDE works fine

/rmd

Quoting "Rolf M. Dietze" <rmd@orbit.in-berlin.de>:

> Hi,
>
> might be that I am on the wrong list for this, since my Problem
> exists on 14.0Release.
>
> After an out of the box install of FreeBSD 14.0 Release and following<= br> > h= ttps://forums.freebsd.org/threads/setting-up-common-desktop-environment-for= -modern-use.69475/
> I am stuck with CDE. CDE loads, dtlogin starts an presents the login > or greeter window, but upon logging in I get a popup telling
> "The desktop messaging system could not be started". Guess I= am
> missing some config steps. Any pointer for further reading?
> I had CDE running on 13.2Release
>
> yours, Rolf




--0000000000009cfd35060b27369f-- From rmd@orbit.in-berlin.de Mon Nov 27 19:34:02 2023 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 4SfG3y0wnFz528f5 for ; Mon, 27 Nov 2023 19:34:06 +0000 (UTC) (envelope-from rmd@orbit.in-berlin.de) Received: from einhorn-mail-out.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) (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 (4096 bits) client-digest SHA256) (Client CN "mail.in-berlin.de", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SfG3w3rxYz3S9K for ; Mon, 27 Nov 2023 19:34:04 +0000 (UTC) (envelope-from rmd@orbit.in-berlin.de) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of rmd@orbit.in-berlin.de designates 192.109.42.8 as permitted sender) smtp.mailfrom=rmd@orbit.in-berlin.de; dmarc=none X-Envelope-From: rmd@orbit.in-berlin.de X-Envelope-To: Received: from authenticated.user (localhost [127.0.0.1]) by einhorn.in-berlin.de with ESMTPSA id 3ARJY2oi579650 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT) for ; Mon, 27 Nov 2023 20:34:02 +0100 Received: from cygnus.imp.fu-berlin.de (cygnus.imp.fu-berlin.de [160.45.110.43]) by webmail.in-berlin.de (Horde Framework) with HTTPS; Mon, 27 Nov 2023 20:34:02 +0100 Date: Mon, 27 Nov 2023 20:34:02 +0100 Message-ID: <20231127203402.Horde.s1ZHSPc7L_KrM1Y2tLzs9xS@webmail.in-berlin.de> From: "Rolf M. Dietze" To: freebsd-current@freebsd.org Subject: Re: CDE on FreeBSD 14.0 Release References: <20221127161544.7dd1207c@thor.intern.walstatt.dynvpn.de> <20231127172506.Horde.iiBmVTtnl5OM_J0h4cvdd7M@webmail.in-berlin.de> In-Reply-To: User-Agent: Horde Application Framework 5 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes 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 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-3.50 / 15.00]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_ALLOW(-0.20)[+ip4:192.109.42.0/24]; RWL_MAILSPIKE_GOOD(-0.10)[192.109.42.8:from]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[192.109.42.8:from]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:29670, ipnet:192.109.42.0/24, country:DE]; R_DKIM_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; DMARC_NA(0.00)[orbit.in-berlin.de]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4SfG3w3rxYz3S9K X-Spamd-Bar: --- Hi, uh, I forgot the entry in services, thanks for the link:) Rolf Quoting Mario Marietto : > I asked the same recently and I'd got a good answer,here : > > https://forums.FreeBSD.org/threads/cde-users-unite.85143/post-576559 > > On Mon, Nov 27, 2023 at 5:25 PM Rolf M. Dietze > wrote: > >> Hi, >> >> might be that I am on the wrong list for this, since my Problem >> exists on 14.0Release. >> >> After an out of the box install of FreeBSD 14.0 Release and following >> >> https://forums.freebsd.org/threads/setting-up-common-desktop-environment-for-modern-use.69475/ >> I am stuck with CDE. CDE loads, dtlogin starts an presents the login >> or greeter window, but upon logging in I get a popup telling >> "The desktop messaging system could not be started". Guess I am >> missing some config steps. Any pointer for further reading? >> I had CDE running on 13.2Release >> >> yours, Rolf >> >> >> > > -- > Mario. From nobody Tue Nov 28 17:01:47 2023 X-Original-To: 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 4Sfpf62Vy6z52Ddk for ; Tue, 28 Nov 2023 17:02:06 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp.rcn.com (mail.rcn.syn-alias.com [129.213.13.252]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Sfpf54Rv4z3Z9w for ; Tue, 28 Nov 2023 17:02:05 +0000 (UTC) (envelope-from roberthuff@rcn.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=rcn.com header.s=20180516 header.b=SF9wOwzE; spf=pass (mx1.freebsd.org: domain of roberthuff@rcn.com designates 129.213.13.252 as permitted sender) smtp.mailfrom=roberthuff@rcn.com; dmarc=pass (policy=none) header.from=rcn.com DKIM-Signature: v=1; a=rsa-sha1; d=rcn.com; s=20180516; c=relaxed/simple; q=dns/txt; i=@rcn.com; t=1701190924; h=From:Subject:Date:To:MIME-Version:Content-Type; bh=5yCpL4NI2qbOart13N7QGI7izHY=; b=SF9wOwzEncRKyaRcJV9Z2KrnorZp4dcGeGDOxQ3bK0VMlLOq7yZNnrgAXJMpRl2f kYzJY4Ge/TJBDNxAznmVHLUR6ftrbHHGB0/a8BgRFAxZXkTz37+rc69AAVqTj/BW f9QIbssu9cIJg5XUKxCW2aVaFwG2jIT7cZCgiUvUrfz4o/eylTs95RZZ0KVaa+mM /Qb8ekqmUeDtebBtCTXRipJznBlsPg7YtZZD3nBb80HjD+v5wl6BnIOPxQNQvgNN 6hvzVGrWTYqD1QPIVOpkkhGcWoubJmwN5a55NbGH1p8bnrGvwNWlzebxnICISd2t NRcOx8IpMv930njq6oqS+A==; X-Authed-Username: cm9iZXJ0aHVmZkByY24uY29t Received: from [130.44.151.156] ([130.44.151.156:63649] helo=[192.168.1.131]) by smtp.rcn.com (envelope-from ) (ecelerity 4.4.1.20033 r(msys-ecelerity:tags/4.4.1.0^0)) with ESMTPSA (cipher=AES128-GCM-SHA256) id 66/A5-08065-C0D16656; Tue, 28 Nov 2023 12:02:04 -0500 Message-ID: Date: Tue, 28 Nov 2023 12:01:47 -0500 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 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Content-Language: en-US To: current@freebsd.org From: Robert Huff Subject: problem updating to CURRENT from source Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Vade-Verdict: clean X-Vade-Analysis-1: gggruggvucftvghtrhhoucdtuddrgedvkedrudeifedgleefucetufdoteggodetrfdotffvucfrrhho X-Vade-Analysis-2: fhhilhgvmecuufgjpfetvefqtfdptfevpfdpgffpggdqtfevpfdpqfgfvfenuceurghilhhouhhtmecu X-Vade-Analysis-3: fedtudenucenucfjughrpefkffggfgfvhffutgfgsehtjeertddtfeejnecuhfhrohhmpeftohgsvghr X-Vade-Analysis-4: thcujfhufhhfuceorhhosggvrhhthhhufhhfsehrtghnrdgtohhmqeenucggtffrrghtthgvrhhnpeff X-Vade-Analysis-5: ieduvdfggfetkefggfetffejjeeltddvieekvdffteffveejudegffegffeuveenucfkphepudeftddr X-Vade-Analysis-6: geegrdduhedurdduheeinecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehinhgvthepudef X-Vade-Analysis-7: tddrgeegrdduhedurdduheeipdhhvghloheplgduledvrdduieekrddurddufedungdpmhgrihhlfhhr X-Vade-Analysis-8: ohhmpehrohgsvghrthhhuhhffhesrhgtnhdrtghomhdprhgtphhtthhopegtuhhrrhgvnhhtsehfrhgv X-Vade-Analysis-9: vggsshgurdhorhhgpdhmthgrhhhoshhtpehsmhhtphdtuddrrhgtnhdrvghmrghilhdqrghshhdurdhs X-Vade-Analysis-10: hihntgdrlhgrnhdpnhgspghrtghpthhtohepuddpihhspghnrgepthhruhgvpdgruhhthhgpuhhsvghr X-Vade-Analysis-11: pehrohgsvghrthhhuhhffh X-Vade-Client: RCN X-Spamd-Result: default: False [-3.11 / 15.00]; NEURAL_HAM_SHORT(-1.00)[-0.997]; NEURAL_HAM_MEDIUM(-0.99)[-0.994]; DMARC_POLICY_ALLOW(-0.50)[rcn.com,none]; R_SPF_ALLOW(-0.20)[+ip4:129.213.13.252/32]; R_DKIM_ALLOW(-0.20)[rcn.com:s=20180516]; NEURAL_HAM_LONG(-0.11)[-0.114]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[current@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:31898, ipnet:129.213.8.0/21, country:US]; RCVD_IN_DNSWL_NONE(0.00)[129.213.13.252:from]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[rcn.com:+]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4Sfpf54Rv4z3Z9w X-Spamd-Bar: --- Hello: I am trying to update a system running "14.0 CURRENT #0" to last night's Current using source. I read the RELNOTES; I read the directions in UPDATING under "To rebuild everything". I built world; built kernel; installed kernel; rebooted single user - no problem. Ran "etcupdate -p", resolved some existing conflicts - check. Ran "make installworld" and got: /bin/sh: /usr/obj/usr/src/amd64.amd64/rescue/rescue/rescue: not found rescue/sh check failed, installation aborted *** Error code 1 <"kicked in the head by a mule" look> What have I done wrong? More importantly: how do I fix it? Respectfully, Robert Huff From nobody Tue Nov 28 19:01:34 2023 X-Original-To: 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 4SfsK12P2nz52PGn for ; Tue, 28 Nov 2023 19:02:29 +0000 (UTC) (envelope-from garyj@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.gmx.net", Issuer "Telekom Security ServerID OV Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SfsK05cpjz4QLG for ; Tue, 28 Nov 2023 19:02:28 +0000 (UTC) (envelope-from garyj@gmx.de) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1701198095; x=1701802895; i=garyj@gmx.de; bh=+VBBNtwHndVhRc12JNWGlIEaomxv+EFxikyjeHoJXic=; h=X-UI-Sender-Class:Date:From:To:Cc:Subject:In-Reply-To:References: Reply-To; b=dfW/Q03o+0Olk+0S7LXrRPJxwaj945LLB05CwtJApwpof87i3HKRQtyg5WM+flfb 72TOYjhkPuoiKfDPPz8WlnBMfUt9IxVZuAdgiN2KCK0b/0D3R40w8bEyM5a3eO5DU s0Pvj7K7E9oho2DjdXqvhHZXvSU8EWR6bNOyYDf9PiHCPIMpdWMktZW6+UneIKfAX HaF/olYxwZw56aG7opr2WDPPTSCDHGTibWFZSzkedtELbNsis+aBOk0ugJB7PAGa4 3f7vII27dygijKXY5oJww7pzD7TdPkpNiOqR+8XjY/3hW+9K1/93mtCVfDuSM4FAc CBgO9no8ShJYZFX1PQ== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from ernst.home ([217.226.57.134]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1M5fMY-1rE4wv0Z6Q-007Bun; Tue, 28 Nov 2023 20:01:35 +0100 Date: Tue, 28 Nov 2023 19:01:34 +0000 From: Gary Jennejohn To: Robert Huff Cc: current@freebsd.org Subject: Re: problem updating to CURRENT from source Message-ID: <20231128200134.1b6d7ba6@ernst.home> In-Reply-To: References: Reply-To: garyj@gmx.de X-Mailer: Claws Mail 3.19.1 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:aGnp7lOddJW5F3UgOqdmqI20Vyw0su68BS1kcUJcxQF9qXWZuFY KbtY5qWsZqwyhlZ4a38dUyzo/33p1lgqnXZ9Js9d9HAoceIBYHJh8etzrgVkjJR7dJmtJsJ y8bJPjIDh+ZkO/PNm8/+wpZ+K60OiyWWbo/NPuQvHwg/tykBZ+ihCDW5nTUW65JzLsyv24p asWW7pK4QL0O8n329Qfaw== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:664S6Ld1pkQ=;9PBNkI9h69sm1dnqkzp6vm5cKnt 96D/TiWjnd1R2rDA7gB/eC/RpfcMzYSOaP+rQvXssDq6DszDIgmQ9WYWLuX9urOBOdKY2wCp1 1CXRJww0A8MbqK2iAmGUuSSejFZYKwcYGmllVwWMG3UHVxlwfrjQ95iDtBLsk7KX7aoNvEYw7 XGRTQ+VbRas88k8HJa8if7REXSbqFtYps8PH0W26TRL9hHDkuD9w3OQq6v7/VtkXnThi+olRW 0Mc7NFjgFbOx9TwhBfOFlQhXqM2k+/USFdUQs30Pdwoj6hwygLXTGaKfO3/mQ5BDL4nEYn/2y dXFpQo6SKEUh8Xtx9oFZjwXbrPDW9/3/yNU+10QvqIlqhtfFNeqozt/qEDU/ijSDTT3i1hksa k5XiuvBEKa18jxUCdMm01WVUezHP9qNln/AYN0JYYqBsMui96OuVc/ZptXsCeI2L3iaoL1+li 2kEw8D90ss9L54z48XVtaZcOT5Bj3P4pqadTShL+zYiO06iPc824X5fLYzLJlQO5kMRu+5OV5 rUw8bVPO6EYya4oulTV47ke2U55ZZAIENU1vFGz2zpOCxj/NMTBfV3wdWFiFNBEfMXSpxz566 uwPCfYp64yA6ItvbD+Q/Ooxlbwo5NqdY7z/RPAAJU9fQy882YsF/QLZayKo3EhkMdZwwbYcBV asHDFONpjsuqFAXYVIVB7H1YCW6NEK5bBRvPQEyNHpEVA1XTSOo1PQq7ZIglh//lylpbcZEBR pYJdnpnMRhvo5weuMZV21z09e5bNEbpA35maKvnb6Gxmkhv/MhvTxoWioO7WFsmOYeyWiG03y RMkHuRGsTIrJs60T7ieLLoVmnJvY37zyaj2Z+zeGrjkrr1ET1UQfRRnt2mwbNFrw96Zbo4faW /Qyo6SWQD4khJmHWnHwSZ+yTuCW2wEJqUbGsrY7LQ0UhAhxYmRk0xJuyUDPG8KLfo4xWiy2hn s2WsiTTOIgbeRCq7eW4yf3XAQUc= 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:8560, ipnet:212.227.0.0/16, country:DE] X-Rspamd-Queue-Id: 4SfsK05cpjz4QLG On Tue, 28 Nov 2023 12:01:47 -0500 Robert Huff wrote: > Hello: > I am trying to update a system running "14.0 CURRENT #0" to last > night's Current using source. > I read the RELNOTES; I read the directions in UPDATING under "To > rebuild everything". > I built world; built kernel; installed kernel; rebooted single > user - no problem. > Ran "etcupdate -p", resolved some existing conflicts - check. > > Ran "make installworld" and got: > > /bin/sh: /usr/obj/usr/src/amd64.amd64/rescue/rescue/rescue: not found > rescue/sh check failed, installation aborted > *** Error code 1 > > <"kicked in the head by a mule" look> > What have I done wrong? > More importantly: how do I fix it? > > I built and installed the latest main source yesterday and I see in my ~/obj usr/src/amd64.amd64/rescue/rescue/rescue (but I was already running FreeBSD-15). Did you do a clean build? This isn't mentioned in the "To rebuild everything" text, but since you're building a different branch I suspect that a clean build would be necessary. =2D- Gary Jennejohn From nobody Tue Nov 28 19:13:51 2023 X-Original-To: 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 4SfsZ80NXmz52QDp for ; Tue, 28 Nov 2023 19:13:52 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp.rcn.com (mail.rcn.syn-alias.com [129.213.13.252]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4SfsZ73gDrz4SPV for ; Tue, 28 Nov 2023 19:13:51 +0000 (UTC) (envelope-from roberthuff@rcn.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha1; d=rcn.com; s=20180516; c=relaxed/simple; q=dns/txt; i=@rcn.com; t=1701198830; h=From:Subject:Date:To:MIME-Version:Content-Type; bh=yu1Cc+uAGZrMiOYUQ6+mOflvgQA=; b=mEPZ3ckf3BRQmyvn5bXUXvsfoz2th/PaP2mLV54jHUvJ3UdRI1jqw8yWn97MnzUK 2OMYeIAO32k9szRnObPcS93IkX/dOWjVjHfcMwJa21AUjDHMEREUTRT5rZXj4IQV AjKE1oTH6PH90eOTxZuuHYBytW/Whr02ZhwX5cL1CQtHy1M37Gl2Qefq4heugAmV dtKeGWKyk2wWaRra9BBIs3iJ1pvd2jkIqFoC0HqlPjZPDlR9kN1PXbVR5a7gUadF 5PcnaY3d/5D79dZf94uev7OKvhNmefIwKSFs10MhHODvdnqCVfU6g+dusM08fQCv 43/1hV5UeHKNHfEGDEfKUw==; X-Authed-Username: cm9iZXJ0aHVmZkByY24uY29t Received: from [130.44.151.156] ([130.44.151.156:58265] helo=[192.168.1.131]) by smtp.rcn.com (envelope-from ) (ecelerity 4.4.1.20033 r(msys-ecelerity:tags/4.4.1.0^0)) with ESMTPSA (cipher=AES128-GCM-SHA256) id D1/E0-08065-EEB36656; Tue, 28 Nov 2023 14:13:50 -0500 Message-ID: Date: Tue, 28 Nov 2023 14:13:51 -0500 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 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Subject: Re: problem updating to CURRENT from source Content-Language: en-US To: garyj@gmx.de Cc: current@freebsd.org References: <20231128200134.1b6d7ba6@ernst.home> From: Robert Huff In-Reply-To: <20231128200134.1b6d7ba6@ernst.home> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Vade-Verdict: clean X-Vade-Analysis-1: gggruggvucftvghtrhhoucdtuddrgedvkedrudeifedguddvtdcutefuodetggdotefrodftvfcurfhr X-Vade-Analysis-2: ohhfihhlvgemucfujgfpteevqfftpdftvefppdfgpfggqdftvefppdfqfgfvnecuuegrihhlohhuthem X-Vade-Analysis-3: uceftddunecunecujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpeft X-Vade-Analysis-4: ohgsvghrthcujfhufhhfuceorhhosggvrhhthhhufhhfsehrtghnrdgtohhmqeenucggtffrrghtthgv X-Vade-Analysis-5: rhhnpeegtefhfeeffefhvefgkefgieefvdekieevgedtueejveelgffhtefgtedvveelkeenucfkphep X-Vade-Analysis-6: udeftddrgeegrdduhedurdduheeinecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehinhgv X-Vade-Analysis-7: thepudeftddrgeegrdduhedurdduheeipdhhvghloheplgduledvrdduieekrddurddufedungdpmhgr X-Vade-Analysis-8: ihhlfhhrohhmpehrohgsvghrthhhuhhffhesrhgtnhdrtghomhdprhgtphhtthhopehgrghrhihjsehg X-Vade-Analysis-9: mhigrdguvgdprhgtphhtthhopegtuhhrrhgvnhhtsehfrhgvvggsshgurdhorhhgpdhmthgrhhhoshht X-Vade-Analysis-10: pehsmhhtphdtuddrrhgtnhdrvghmrghilhdqrghshhdurdhshihntgdrlhgrnhdpnhgspghrtghpthht X-Vade-Analysis-11: ohepvddpihhspghnrgepthhruhgvpdgruhhthhgpuhhsvghrpehrohgsvghrthhhuhhffh X-Vade-Client: RCN 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:31898, ipnet:129.213.8.0/21, country:US] X-Rspamd-Queue-Id: 4SfsZ73gDrz4SPV Gary Jennejohn asks: > Did you do a clean build? This isn't mentioned in the "To rebuild > everything" text, but since you're building a different branch I > suspect that a clean build would be necessary. Define "clean build". The script for rebuilding world has both "make cleanworld" and "make cleandir"; is that sufficient? Respectfully, Robert Huff From nobody Tue Nov 28 21:49:12 2023 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 4SfxHm2Vfdz52d6Z for ; Tue, 28 Nov 2023 22:01:40 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from omta001.cacentral1.a.cloudfilter.net (omta001.cacentral1.a.cloudfilter.net [3.97.99.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SfxHl4t2Hz3LCp for ; Tue, 28 Nov 2023 22:01:39 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of cy.schubert@cschubert.com has no SPF policy when checking 3.97.99.32) smtp.mailfrom=cy.schubert@cschubert.com; dmarc=none Received: from shw-obgw-4003a.ext.cloudfilter.net ([10.228.9.183]) by cmsmtp with ESMTPS id 82A2rtwXN8jpT85xCrHZRv; Tue, 28 Nov 2023 21:49:14 +0000 Received: from spqr.komquats.com ([70.66.152.170]) by cmsmtp with ESMTPSA id 85xBrbn6ZMsNf85xCrbQWi; Tue, 28 Nov 2023 21:49:14 +0000 X-Authority-Analysis: v=2.4 cv=KJNJsXJo c=1 sm=1 tr=0 ts=6566605a a=y8EK/9tc/U6QY+pUhnbtgQ==:117 a=y8EK/9tc/U6QY+pUhnbtgQ==:17 a=kj9zAlcOel0A:10 a=BNY50KLci1gA:10 a=6I5d2MoRAAAA:8 a=YxBL1-UpAAAA:8 a=EkcXrb_YAAAA:8 a=uOxVQ_NGB5_BzC6f4GcA:9 a=CjuIK1q_8ugA:10 a=IjZwj45LgO3ly-622nXo:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=LK5xJRSDVpKd5WXXoEvA:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTP id E32D74D7; Tue, 28 Nov 2023 13:49:12 -0800 (PST) Received: by slippy.cwsent.com (Postfix, from userid 1000) id D7116147; Tue, 28 Nov 2023 13:49:12 -0800 (PST) X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.8+dev Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: "Rolf M. Dietze" cc: freebsd-current@freebsd.org Subject: Re: CDE on FreeBSD 14.0 Release In-reply-to: <20231127172506.Horde.iiBmVTtnl5OM_J0h4cvdd7M@webmail.in-berlin.de> References: <20231127172506.Horde.iiBmVTtnl5OM_J0h4cvdd7M@webmail.in-berlin.de> Comments: In-reply-to "Rolf M. Dietze" message dated "Mon, 27 Nov 2023 17:25:06 +0100." 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 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Nov 2023 13:49:12 -0800 Message-Id: <20231128214912.D7116147@slippy.cwsent.com> X-CMAE-Envelope: MS4xfCFW9FTxonMQyuGSZXT0jR17F4smr6KOr8wFqES4RmD4zXaA1Gj/hDJwJJyNXK+HbWOuc2Z0AKyl6qluzP+GWDFp4+9dsW+v3qQtEHGNr7zMhGrHFgNc qyOBC81cYm3Z9P9j1XvRlpVIro+nSyPOfB8SSTAlOsXcfzf40ZLwWpXE7GPuqnAMYUNgHpG4F7I6/XIKXESbRCbbol4ITC87KizALjZU6RDyyMC97UaEJIgL MlW3N+6MV/WNAQ1vVsR+8A== X-Spamd-Result: default: False [2.57 / 15.00]; R_BAD_CTE_7BIT(3.50)[7bit]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-0.90)[-0.898]; NEURAL_HAM_SHORT(-0.80)[-0.804]; MV_CASE(0.50)[]; NEURAL_HAM_MEDIUM(-0.43)[-0.426]; MIME_GOOD(-0.10)[text/plain]; RWL_MAILSPIKE_GOOD(-0.10)[3.97.99.32:from]; RCVD_IN_DNSWL_LOW(-0.10)[3.97.99.32:from]; FROM_HAS_DN(0.00)[]; REPLYTO_EQ_FROM(0.00)[]; DMARC_NA(0.00)[cschubert.com]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[Cy.Schubert@cschubert.com]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_NA(0.00)[no SPF record]; RCPT_COUNT_TWO(0.00)[2]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:16509, ipnet:3.96.0.0/15, country:US]; MIME_TRACE(0.00)[0:+]; GREYLIST(0.00)[pass,body] X-Rspamd-Queue-Id: 4SfxHl4t2Hz3LCp X-Spamd-Bar: ++ In message <20231127172506.Horde.iiBmVTtnl5OM_J0h4cvdd7M@webmail.in-berlin.d e>, "Rolf M. Dietze" writes: > Hi, > > might be that I am on the wrong list for this, since my Problem > exists on 14.0Release. > > After an out of the box install of FreeBSD 14.0 Release and following > https://forums.freebsd.org/threads/setting-up-common-desktop-environment-for- > modern-use.69475/ First, unless you plan on using the CDE calendar, you don't needs the dtspc entry in inetd.conf. I'm currently running CDE, installed using pkg, on 14.0-RELEASE using dtlogin at $JOB. At home I use CDE on 15-CURRENT. I use xdm at home instead because dtlogin doesn't support PAM* but xdm does. Caveat, if you use xdm you will need to add dtsession to your .xsession file. * My home network uses MIT KRB5 to serve passwords and LDAP to serve UID/GID information. This requires pam_krb5, and as dtlogin is not PAM aware it can only work with accounts in /etc/passwd. Hence xdm. I'll probably submit a pull request to the CDE development team one day but considering all the other things on my plate, PAM support within dtlogin is pretty low on my priority list. > I am stuck with CDE. CDE loads, dtlogin starts an presents the login > or greeter window, but upon logging in I get a popup telling > "The desktop messaging system could not be started". Guess I am > missing some config steps. Any pointer for further reading? > I had CDE running on 13.2Release Make sure your /etc/hosts has an entry for localhost. Also make sure your machine's PTR record is correct and that it matches its A record. It's most likely your hostname doesn't match any IP on your network. Just add your correct hostname's IP to /etc/hosts or if using dhcp, prefix your hostname to the localhost entry in /etc/hosts like this, 127.0.0.1 my_hostname_whatever_it_is localhost localhost.my.domain Also make sure rpcbind is running. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org e^(i*pi)+1=0 From nobody Wed Nov 29 19:21:36 2023 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 4SgThg40n8z527pV for ; Wed, 29 Nov 2023 19:21:39 +0000 (UTC) (envelope-from jdjjddrisn@outlook.com) Received: from CAN01-YQB-obe.outbound.protection.outlook.com (mail-yqbcan01olkn2062.outbound.protection.outlook.com [40.92.106.62]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "DigiCert Cloud Services CA-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SgThf1RwDz4RyR for ; Wed, 29 Nov 2023 19:21:38 +0000 (UTC) (envelope-from jdjjddrisn@outlook.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=outlook.com header.s=selector1 header.b=eHllinpu; arc=pass ("microsoft.com:s=arcselector9901:i=1"); spf=pass (mx1.freebsd.org: domain of jdjjddrisn@outlook.com designates 40.92.106.62 as permitted sender) smtp.mailfrom=jdjjddrisn@outlook.com; dmarc=pass (policy=none) header.from=outlook.com ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=OIJOwNCjdAy99wPNAZkbThKflALHIZLNcUL26mKZzX1BZypqUc+7ZAk/hKPnEujNPYuxD7OWk7bfeO5yXFtfXLUIvnZJw36s+A3irrlyy9aJu6iaqXRy3FW5HckpLngX8LO586/wwqlyVhwO3klZCAOyV92Z1JL0HKaUXjtPAaJiTcDqDr5nCK8bQYAtOiBOy0QWZrdzS9X6V4KVOUmbnBgYN+/D8Yhmf9+on5UsxLHfIFgT0Y7xSqp30qM9hQYeGMRAtCXcP3eZPfPtGkjCAqNsScs+bJ/KcrkIz8Hgop8JMLtxvbcN6hVoepegWobgJKTxlDKWvTunPky77Zjrgw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=zzGvTinJZzQP2x8xs9tgmhGXzYpgks7pysb7U1340gs=; b=Ca2c/HykizrEMnI9JxTXvFMohSuZqZnSGHawDpdbTSfv3SjHdEX8MevNosllLs7jQ9/UJUtFgYp3Uze9SFV8+JV7FhWGpi3LIzXbwtJR8/XlntD31Xvuq/776atu+7aR6blRrGRlj5TvHXKMwTdoXE8DQuQr6BJK7tBGe+pKOxivGb104jkdc+zXBfmZrmfwpdFNV13jUHEi7Rf6nzb3FLjSaPiOu6qdZo3dnTam3mP/HXWvjxu2pWfmN16onJj9iEXw4g5HyCSh37FcJpRfzPyLYVUXG7XkVRLiPeY+jgzz5IqWsZthrrn89pcO12KO2iylD8XASB/nD4jEM9rRdA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=zzGvTinJZzQP2x8xs9tgmhGXzYpgks7pysb7U1340gs=; b=eHllinpudcCYsIjigo8BxqI+7Q8XGUCc9vTNbCjXWfRBXISqOUaXlajZVtrlcm6Z3TPPsqhONjHro7k4Gax/DltEX4FU307qgsxYDngby0+N7JC+I81Vya3ktJ6i0FdC9LAmTvsI8uEU4syEfeYOY6sQcrtzBBy+qXHpmT9yBq+ri1K6HWDTSNArH7EY1wPuUHFWugJAaqJsOt2CQdc2cuDVpKkQkFQVS7FoMoSLy2rO10nomPojALIm8VnNVuO33IvX2YwOHttNEfdJAizHvGTi5w0ZReL2ThZ9XFOZ/XZ7MnxDD6t2ddEtCarE+O3LputMrqdw/EAWH/s16yES2Q== Received: from YQBPR0101MB5783.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:c01:32::16) by YT1PR01MB8890.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:b01:c9::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7046.23; Wed, 29 Nov 2023 19:21:36 +0000 Received: from YQBPR0101MB5783.CANPRD01.PROD.OUTLOOK.COM ([fe80::66a5:3922:ac5:8be6]) by YQBPR0101MB5783.CANPRD01.PROD.OUTLOOK.COM ([fe80::66a5:3922:ac5:8be6%7]) with mapi id 15.20.7025.022; Wed, 29 Nov 2023 19:21:36 +0000 From: Manoel Games To: "freebsd-current@freebsd.org" Subject: How do I update the kernel of FreeBSD-CURRENT Thread-Topic: How do I update the kernel of FreeBSD-CURRENT Thread-Index: AQHaIvkujN8KJ7OHn0yMS7aAvH6SYw== Date: Wed, 29 Nov 2023 19:21:36 +0000 Message-ID: Accept-Language: pt-BR, en-US Content-Language: pt-BR X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: x-tmn: [wpFo8XpEdq6KUqdain0tX01V/peXqm1l] x-ms-publictraffictype: Email x-ms-traffictypediagnostic: YQBPR0101MB5783:EE_|YT1PR01MB8890:EE_ x-ms-office365-filtering-correlation-id: 866d7eed-53dc-4ffa-17e6-08dbf1106798 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: zvPbRz1LI599e+YQirL2gu1dU/gohFmOX+hfJp2JU2/dIGJwsW1NNz2cfGjS9BJx7+yNASpljT7w4A9gMQrIR4Msyi50QPjkx+8ptmfZjFSi/x9h/yGoAloChcXK3OSUknNTRJ662wtnWZQem31PrV33WAbBWKW1U9D1eVg/c/XEoyT8QbHI3W1nBDd6KRWgO43qCiOZEhHvjfI+dA/5+9xQkKGHdrlvtIUIerckccy7++tkY20OU8a5WRMi66Ao+Wp+5skK9WwvzjhVI+le3IMrAye4gRYqzjIXzUUhw2baIXdCUPZssYzXDz+MyN7DrQnYTbPkyNmmnZPggUJ8WWO4I6r2xh5Iktxsoqq7EqYqLwlM0jkSBKWY6Wx3CVq352BCgVnw6x8uVhKh15ftGYOHkaaDzatF7nvOV+0BNgA6jqDDgeH6IPp2Izvzkmao1+NNE+qS6tVCuI6R97FJHPNucQZW5ji52s7T//2Ty2cAEcBCUCddr46YANsOtcxJyYq1YOk07q4Bme3jxnCmpWQ5unomSr0fdpXeP1BPgNgcdjmx1oVLq5mk5I4ECe3N x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?iso-8859-1?Q?mLgxgkMOOxOs4TXDA96nQ9NFnvFljuIZY4wAnRPZnH1LnmtBndwg9088x3?= =?iso-8859-1?Q?pUcCiu0JDqyzNDUQZk/yq3VQsxMa4UsrNNNHdVmgTzc68toxC8qwPXnTQ6?= =?iso-8859-1?Q?ZerZ3RUhrD0hMDxMVFifWH1v+0ufUAJcsRWxVHKkdJsuiyuwKM+0UodJDb?= =?iso-8859-1?Q?P6O/lU4LKviJhqlKSuX0DNlyc6K0BWCYxSRR+XjkDuKt6BvSOY9jwEdNly?= =?iso-8859-1?Q?JDLdQE7ug2twX5O7Y/BqU8lGc6YnCNshT2dCVJUJvyqvXgFUs2XDoaL3PO?= =?iso-8859-1?Q?YKXS2UL3DaxB4yCvBKauyGIaHYlUPdnNKyXpieyLUgvzkJzo15oW0CmC5o?= =?iso-8859-1?Q?Q8f5Y4XxbwID3t5N3CGzc5YJLnTxVXg6nO0EvzCKUvLG1GIADS+S1G8ACU?= =?iso-8859-1?Q?x9H18jS81fyO8eDYIJmICvlDmObgCO9H0hAk+5fJS8ZjeoMGxc9v2dT86y?= =?iso-8859-1?Q?ohx0An3jsOMUHjOZOopnJ8FT9k8u9XVp9LlUKVPEMaONS9UYDeF4NLTqdQ?= =?iso-8859-1?Q?SLg5o9JnfKl0c038wSc147Nke9HbW/6Gg/TXBaJoJMTw+rwbLDgvuRCuvs?= =?iso-8859-1?Q?/HhI0REKIlkXd8IFNVf7V9YcbFJwfqBeo2SLZfLVOeuKgxQZ2k0V9L+iDQ?= =?iso-8859-1?Q?/U9/IVN747elCjqxR9719LQ9sDMgKefqtKsGgDbUqVmKW4T+6E6nt2dzd+?= =?iso-8859-1?Q?/mUH+HwU7b0urYEF1TjKpaE+5Wo4mG26mmdnqs2uTravZNEGIbt+jLs//c?= =?iso-8859-1?Q?3T+kKvw2ePG97P8WU6PyRA6FQQ//tXukfy5PsHNhOhl7RzKzyQqGeox2b0?= =?iso-8859-1?Q?RvLcELN2VXGVRtKrzub179Ixi55QRB4L2AZo8l7ad3FvAKHDoQ/CaLNJbj?= =?iso-8859-1?Q?6fiOJ2Chg935jUJ5SY2oTNnP+UTQaIpFRbSEDx6+cGh/DqBadSBGn3ZtYA?= =?iso-8859-1?Q?WHfE4Ca3FctRjuXYeH+hiTUtBMAbRyXPmk5U1ks9FzX0UJS8ZLD3e3JBvz?= =?iso-8859-1?Q?EJhRysrbT+U32ZdtDFJvYqfDFDjO5E8bAMtI7CC6HkVRVnK8Jsq77reYdn?= =?iso-8859-1?Q?sQ/aDrtEkQQAfwZR6B5fHvdqfoVXNKLHoUzynb4cRHpjDWsIsqN2Is+sud?= =?iso-8859-1?Q?FVlq73qNFdjbdEC4KO95tmEsvG9aSOqA1xi4DBHSoGqriwpbPk+GH4TIOO?= =?iso-8859-1?Q?lg/iZLtiaqhargMsZ/6pBvfBtHzsx9PWNtA5/ir/dftdzoLzrwS2NAjk78?= =?iso-8859-1?Q?yzbGCP0w4B5avPCXk4CA=3D=3D?= Content-Type: multipart/alternative; boundary="_000_YQBPR0101MB57832FD5AC83CF899FFDF444D483AYQBPR0101MB5783_" 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 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: YQBPR0101MB5783.CANPRD01.PROD.OUTLOOK.COM X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-CrossTenant-Network-Message-Id: 866d7eed-53dc-4ffa-17e6-08dbf1106798 X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Nov 2023 19:21:36.2226 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-Transport-CrossTenantHeadersStamped: YT1PR01MB8890 X-Spamd-Result: default: False [-5.00 / 15.00]; ARC_ALLOW(-1.00)[microsoft.com:s=arcselector9901:i=1]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[outlook.com,none]; R_DKIM_ALLOW(-0.20)[outlook.com:s=selector1]; R_SPF_ALLOW(-0.20)[+ip4:40.92.0.0/15:c]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_EQ_ENVFROM(0.00)[]; TO_DN_EQ_ADDR_ALL(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:8075, ipnet:40.80.0.0/12, country:US]; FREEMAIL_ENVFROM(0.00)[outlook.com]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_TLS_LAST(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[outlook.com:+]; DWL_DNSWL_NONE(0.00)[outlook.com:dkim]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_FROM(0.00)[outlook.com]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4SgThf1RwDz4RyR X-Spamd-Bar: ---- --_000_YQBPR0101MB57832FD5AC83CF899FFDF444D483AYQBPR0101MB5783_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I am a new FreeBSD user, and I am using FreeBSD-CURRENT. How do I update th= e FreeBSD-CURRENT kernel, and is it done through pkg? I installed FreeBSD-C= URRENT without src. --_000_YQBPR0101MB57832FD5AC83CF899FFDF444D483AYQBPR0101MB5783_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I am a new FreeBSD user, and I am using FreeBSD-= CURRENT. How do I update the FreeBSD-CURRENT kernel, and is it done through pkg? I installed FreeBSD-CURRENT without sr= c.
--_000_YQBPR0101MB57832FD5AC83CF899FFDF444D483AYQBPR0101MB5783_-- From nobody Wed Nov 29 19:28:21 2023 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 4SgTs13cTmz528Tq for ; Wed, 29 Nov 2023 19:28:53 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from webmail5.jnielsen.net (webmail5.jnielsen.net [IPv6:2607:f170:34:11::b0]) (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 "mail.freebsdsolutions.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SgTs10lKWz4TxX for ; Wed, 29 Nov 2023 19:28:52 +0000 (UTC) (envelope-from lists@jnielsen.net) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple ([50.207.241.62]) (authenticated bits=0) by webmail5.jnielsen.net (8.17.2/8.17.1) with ESMTPSA id 3ATJSaif045755 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 29 Nov 2023 12:28:40 -0700 (MST) (envelope-from lists@jnielsen.net) X-Authentication-Warning: webmail5.jnielsen.net: Host [50.207.241.62] claimed to be smtpclient.apple From: John Nielsen Message-Id: <045CECBF-465D-43E7-A6F7-7E3728D454F9@jnielsen.net> Content-Type: multipart/alternative; boundary="Apple-Mail=_79734D10-2FEB-49F6-AC69-4FE9B5894F9A" 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 (Mac OS X Mail 16.0 \(3731.700.6\)) Subject: Re: How do I update the kernel of FreeBSD-CURRENT Date: Wed, 29 Nov 2023 12:28:21 -0700 In-Reply-To: Cc: "freebsd-current@freebsd.org" To: Manoel Games References: X-Mailer: Apple Mail (2.3731.700.6) 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:6364, ipnet:2607:f170:30::/44, country:US] X-Rspamd-Queue-Id: 4SgTs10lKWz4TxX --Apple-Mail=_79734D10-2FEB-49F6-AC69-4FE9B5894F9A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Nov 29, 2023, at 12:21 PM, Manoel Games = wrote: >=20 > I am a new FreeBSD user, and I am using FreeBSD-CURRENT. How do I = update the FreeBSD-CURRENT kernel, and is it done through pkg? I = installed FreeBSD-CURRENT without src. As a new user you should probably run a supported release version, such = as 14.0. Releases have binary updates available via freebsd-update. = (Upgrading the base OS via pkg is still experimental.) Current has no = such feature, so you need to download/update the source and recompile. See the Handbook chapter on upgrading FreeBSD: https://docs.freebsd.org/en/books/handbook/cutting-edge/ JN --Apple-Mail=_79734D10-2FEB-49F6-AC69-4FE9B5894F9A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii On Nov 29, = 2023, at 12:21 PM, Manoel Games <jdjjddrisn@outlook.com> = wrote:

I am a new FreeBSD = user, and I am using FreeBSD-CURRENT. How do I update the = FreeBSD-CURRENT kernel, and is it done through pkg? I installed = FreeBSD-CURRENT without = src.

As a new user = you should probably run a supported release version, such as 14.0. =  Releases have binary updates available via freebsd-update. = (Upgrading the base OS via pkg is still experimental.) Current has no = such feature, so you need to download/update the source and = recompile.

See the Handbook chapter on upgrading = FreeBSD:
https://docs.freebsd.org/en/books/handbook/cutting= -edge/

JN

= = --Apple-Mail=_79734D10-2FEB-49F6-AC69-4FE9B5894F9A-- From nobody Fri Dec 1 00:00:59 2023 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 4ShCrX3ntGz52yr5; Fri, 1 Dec 2023 00:01:00 +0000 (UTC) (envelope-from salvadore@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (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 (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ShCrX0dCGz4FKV; Fri, 1 Dec 2023 00:01:00 +0000 (UTC) (envelope-from salvadore@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1701388860; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc; bh=YF66Xbo7DtIymXgG7zxCiG7zwTK4LgD8DcJExWS2xFM=; b=sDHRy3RCIaht0JxyvSW1figABcW47VQrbJujGnrp11aMJTz0+82QnU0HLxN5wY5UTxoC1t lbZN6zoHY5/XezSGp5PhFf2kDAqF9cJ3YPTK2aqppgnbp5Mg7lMlBRb5AkAsgSzdE4r4IG /CLyBj9HNxoiK01leBg64drmByb0E7RIlopZnTI0oRrrEpxrVFsnNBnBWlo3+9+Ro53SK2 pnQXbbF64Nc7aznVoPf1+Z8SJniucWQ6MwGQ8gh81Z4lN9H09EeaFWa5bXbNMs9bvxbPXB nwP9tn4cgXJCXohF8o2md0OcfEHbAxSzn50tPTw3NwxdKJogrW0tPn7PIKa4sA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1701388860; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc; bh=YF66Xbo7DtIymXgG7zxCiG7zwTK4LgD8DcJExWS2xFM=; b=S5nVm71alYyVKo0+i0EOUzbyZCGrQB0t5ynYrnIVkJMxx8r9PLZG0fNvvaZ+pp6i6e97Mb 8+AzK11ivN2U0IIC5kPLLjm88F/Ae9aaUG5Pc9pn7Jhwwjk5+4EiOzkOKu8HrFlTDakc5A ILneKEg7cNxWGbSpattX2N4os0Qi/yQ724Zlew7CIn12HPMH0swieeyFYz8O3YPkQxmut6 B6MYKyolNYxo0YxfhI7iBvMF4aePC1APLGowNKGAVdP1nFf9hwHd47DlyxVgVp0EIvjmX+ PZSgbD3tbKirgVCYXiQnB7S9TGwjFQWTnDYDIacfz2HA/raolMnV3b9peDntrQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1701388860; a=rsa-sha256; cv=none; b=hlmO0tPSMSf8E0nXsXa1YaCt+9aQTc80p9SobYxkPI8pfWgMhuWmdVYvlu6tNV/5apLWjm cHR3B5ZXYf1W/IkX12p7wvvcQikMEuSb488CnXL5K0FVNu9QMZWcnNDmDou+ErKb3yso6T AY6/Y2r3kCPap4FqKU04AnCZy1XHpevKZit5TCmqDX8DokMWc4jPK5vc1T54pGrLWombfP NrX+MRYoUj5XSQs6ioveAvbIdhY8CoII7iBdKQ/WW5Tu2/4Ci/e/hTRb9J3qCsAHTuK7RD jbjUgR9Llj1aXlcXSMdoyOSlUV1sXMaH4wy0oYG+apB8vx0tOralmwyYJkfrXQ== Received: by freefall.freebsd.org (Postfix, from userid 1472) id D25D61B281; Fri, 1 Dec 2023 00:00:59 +0000 (UTC) To: freebsd-status-calls@FreeBSD.org Subject: Call for 2023Q4 status reports Cc: freebsd-current@FreeBSD.org,freebsd-hackers@FreeBSD.org,devsummit@FreeBSD.org Message-Id: <20231201000059.D25D61B281@freefall.freebsd.org> Date: Fri, 1 Dec 2023 00:00:59 +0000 (UTC) From: Lorenzo Salvadore 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 Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is December, 31st 2023 for work done since the last round of quarterly reports: October 2023 - December 2023. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2023-10-2023-12/ (create it if it is missing); * submit a pull request at . You should put your reports in the directory doc/website/content/en/status/report-2023-10-2023-12/ (create it if it is missing); * send an email to status-submissions@FreeBSD.org including your report. An AsciiDoc template is available at . We look forward to seeing your 2023Q4 reports! Thanks, Lorenzo Salvadore (on behalf of status@) From nobody Sat Dec 2 04:18:20 2023 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 4ShxWK33bvz52Vqj for ; Sat, 2 Dec 2023 04:18:37 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic304-23.consmr.mail.gq1.yahoo.com (sonic304-23.consmr.mail.gq1.yahoo.com [98.137.68.204]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4ShxWH6ktMz4FLK for ; Sat, 2 Dec 2023 04:18:35 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=VbL6Wo3A; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.68.204 as permitted sender) smtp.mailfrom=marklmi@yahoo.com; dmarc=pass (policy=reject) header.from=yahoo.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1701490713; bh=yss0TGd99MFuJxL8ht65f6ra+HzoRRgDwRDfkfGrKI0=; h=From:Subject:Date:References:To:In-Reply-To:From:Subject:Reply-To; b=VbL6Wo3ADDMdozw6NEpTbp3Rw/TMvYpqtoma6WF/L854FWz27BWBcbrtBBninqSIvvof4CszFoofrrCGZh+BfG0maGmZckYrJxkp9/5L0yN7G4MG1cXZFh09QoO4QzFykHvZt1UNHC/jzaFfjZNrPr0OobLLmA5L0CauIkjmqjZdrHQsdrhGjczdP7tPtUIgd/2XhlXYPXuyjurkeYygRNZep5ojm8J1pAJHD/at4uAv3TPpPhz0Z+WOiLi2vcztfFO8ZYkcEjXgE3oZVjNo3UpkVBQ9tbNRpLGuOEoNoWOePZUUXS6ioBsB1JyguB9d5blU/PMc66cLt5JPnsYJaQ== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1701490713; bh=6SSaQE2JsP3/K+9DOXkEhMHf1pAOwiAxQLC69gUz+MN=; h=X-Sonic-MF:From:Subject:Date:To:From:Subject; b=DLy7TPglKtkYPqqIVbW8MJ8WJna2SyxzPlGbMTMlVt1d8u7Zh2cstIRAqgPCS8eUjMVisGvm1pI0Zx+2WyOJdnNd53SIQSeM9iDBWyG62NkHkLJ1wJbOEP+J24U8dU77ReZynLxIvNk1xyIXqVs0G7GudsJXM8SEUCb6zIZZF28cc5KZmOf9F8A+4ar1vg9mrnbNIRnuaZb2L1BWj4EVt4NtGy5fts2eoj/H5/MSRRRsT4QeiIIssTMKz3n1LHyBAjo5uCjT/UtWkPHPrlLYvQULM46/JSx5aF+PjvYNshdVa3XdWe8Dwbex8X9cJ0v00mpakt9jonUwGiJe5NFYEg== X-YMail-OSG: CKa3xbQVM1mHnPoOqPcOP_iBQW9Xln96nSq0FZQSWMop3O6R66XvaGzTJxgJIpg wIopZM38pJDbimYRQnRDbz8zTBtTM..UsZ1MKbzr0.skuEozpBkHOtOCd7FvMUNV30HVsLiUKHKA xikgtsYpiglUheIS6NlBqPT96XrS_BXAtTn6U68JqxC_T1njp3PvFuj5xtKlQC3H0fQ9GZ3uuURJ cVOsfjPffPmQtMGar1QwQTlIlsOO90z.5reVpYhzRHa16QFvxEXJXFkqSj58xTI0.8QqJUM.lrfI I8Blo9mzRnK6ZPaYbzXGhQkoGkcm2VhZLlHSHsFkR4_C7K3Zgd4txzpEnRB9MclZbNehgm_TRqZG fEmKaBnlDraoQFw3_D6M.Vhr6NCM2qtkMI6VaRHwvUErQEhGk8vcciYd1X.NCuVrrvBegC_4aaCU UbAxOSLie5X5eUOiu22JTAhisUe2eBf4Bbt_EFV1pVTUYftodgrMcAH3Qjah9oNXTSRuRemrWg.C cvx9z15ZaeBVNMP51AidrVXG3fN0t9flsS6970bLbPEIQ_UUrwI1.WcuMyXkYEHTx9Gx_0wb4o_t EHFBaXU1GeHAI2L7tj1vxexrZEs.S4uqXexwcbo8fUOQ7tv7zD5tVKrFug7_3I9qnvCrLtNxIB2r II9tBkG3HQ0IzZr74Usouv5k.zN2KG0lAyqsYjgwG8XCTUTr2rclrxwUyRIIybpgegQsNIARGCSB WSU.LINsR_J2XKLloQO_4qZck0mTEpBLr3YVAPHEGvoRUt8xQO2No4UwXNW.MxVb6PhyveDG3Fme 6rBWKULCSm4TR8kG8GOUYCz4rX0X.YIJh8eseKRKbcBATOjwa7G5HRv53drwhcB7giFQmJMm0OwT L_eJIKd9ViHd0Fp9egv.anVG3DaIGoikObA7p0jXu1rWmfCmaRRvfWkLUhzb7LwV50xRFvP21kGe JF9q_Jn544x_f.ekAhmn9PFsSOB_zL8C3JGiITUB94vFl3DJvMIWMV0dP._HeiqpQCfeF57wuARm wKM_zg11_KgEICZ90XQ9J_3u7eUFbnPuDc.6Z_wIjbikA9nNMmzs_WKR2F8ND2rvCKLFzuldHiu0 U.MAyFPNd0IAqUvoQUTGiktoWL7K_70Fw9AtDpuUrqCEW9ItYhiz9VbqBKmieQYNaQP.CET_E7C6 tSAkUTx5tYW_31361lmMqfw.oo01eIozdzV0KSg7z8dA.a4pVCftAUq0sU9EH3mrgIApICvHa0So 3daYEcywNu8zDgsE1uetYOlSk6eitj.5xboKHofrri8DxPDrHPvzqRSjeejXTDmrNoKbYyuWiFEy ChIKkJY2Se3R_gxQF15Ect4rBu5vMy3yg93iQK5ykxDy0omn3UJYaCashqDmsA4EwTixev6KKQ_T W.w10AZSPWoMdoasjvg9H9vOm0s260WBsrpmJI9Fq29tRhCkBYFR6h4WuaJw.50yiUMqO9wATicU TPLWMURR.8b123_9ZbfWC0oYme5uoiZoIlCCtgKdtRcUZCmcMvJ.EqNmC0nGTD4pw77TOJGkCaWM 46EAfE1aiEawHNV.w775DIrpCze6jlP0T_YFvZ0TOolifCVqPWhpsA22Wq5vYNGPZyWNuE_yoV_q A.yk9nJLEepwT616dQRUxfMix4LaAUcxLIDS0LzSyTykIcN7fDMZ8wfFRQ444.zO_uMezSTuPGEK XIcFtSxnDujjtn0vt8CmjKUx4JYosUGhj87TzHa4FClO6TKgXXDdgJIxCl29iHRbRglKNGe9j9oJ XtK.4SmScseYN.Qr_xoObsEIrnW4B.cAU6JTXwt9ao0xJmGgEdxSfLgTeWyFgb0sCvUoOaAhfFkg 15CGNhBsI_B3hgdI3CJHA6Uwj3ZIAMZ4o86tNDsDoqoTJtYVHbw6kW3fsSE7v.ytcqKhTcrV8q2I 71dp7DoZy8Hy_V8EbN0DbW1YSd3B8p9pzwzNa6i9Hqg6kDQZGVzlEJjXGnaM3eDah0utu33hsUlT GDKdFoF8SSqpYtFe3nftir0InJF_DXf141d6d24Rilw4PTzwohOx2Itk8w2gFnqzvbObs6mbL2.l yVa2Ht1G0SKEOUVhisLzTB.L_Ey8beiqViuxx91YJdKt5VB80GbgS9tTLt4iiohdAiWIvevXXr2s h1WV9sAnYt8CIWuLHj2p6YpO4KdW9J4kheIhkH5tvcwF93yzq_QJqCQuYaSKE3zmyVe_EDEtGq4b S6sWyC3HAXefRyAKAfTqC66rF9LMBmo.JsWLRoCP6w0DgbuEpaCptvjn2Fc0- X-Sonic-MF: X-Sonic-ID: 0b59979a-c4ee-4ee6-a5e6-e8d70f9e905d Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.gq1.yahoo.com with HTTP; Sat, 2 Dec 2023 04:18:33 +0000 Received: by hermes--production-gq1-5cf8f76c44-z2sg6 (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 7627e1b50ce7c3188508d8d2314f9350; Sat, 02 Dec 2023 04:18:31 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable 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 (Mac OS X Mail 16.0 \(3774.200.91.1.1\)) Subject: Re: "options MAXMEMDOM=2" vs. amd64 DBG kernel booting: 3000+ "kernel: Process (pid 1) got signal 5" notices during booting Date: Fri, 1 Dec 2023 20:18:20 -0800 References: <6F60DA66-1333-4CF0-B433-F0CE56F5D301@yahoo.com> <91C200DC-94B2-4831-B3DF-9C4627556ADB@yahoo.com> To: Current FreeBSD In-Reply-To: <91C200DC-94B2-4831-B3DF-9C4627556ADB@yahoo.com> Message-Id: <08EBBFE9-8BBC-4618-A3E4-882D55B99F48@yahoo.com> X-Mailer: Apple Mail (2.3774.200.91.1.1) X-Spamd-Result: default: False [-3.46 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.96)[-0.963]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; MV_CASE(0.50)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.68.204:from]; RCPT_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.68.204:from]; DKIM_TRACE(0.00)[yahoo.com:+]; TO_DN_ALL(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.com]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4ShxWH6ktMz4FLK X-Spamd-Bar: --- On Nov 23, 2023, at 13:28, Mark Millard wrote: > On Nov 21, 2023, at 21:43, Mark Millard wrote: >=20 >> While my kernel/world build procedures build both DBG and NODBG >> kernels and worlds, I normally run the NODBG kernel and world, >> using DBG only when I need to for problem investigation. >>=20 >> I recently had reason to use the DBG kernel and found it got the >> oddity of 3000+ instances of "kernel: Process (pid 1) got signal 5" >> during booting, as reported in /var/log/messages . An example is: >>=20 >> . . . >> Nov 20 23:13:09 7950X3D-UFS shutdown[20174]: reboot by root:=20 >> Nov 20 23:13:09 7950X3D-UFS syslogd: exiting on signal 15 >> Nov 20 23:14:21 7950X3D-UFS syslogd: kernel boot file is = /boot/kernel/kernel What looks to normally output just before the odd messages below is the likes of: . . . ugen1.3: at usbus1 ugen1.4: at usbus1 The odd messages are reported in /various/log/messages as: >> Nov 20 23:14:21 7950X3D-UFS kernel: got signal 5 >> Nov 20 23:14:21 7950X3D-UFS kernel: Process (pid 1) got signal 5 >> Nov 20 23:14:21 7950X3D-UFS syslogd: last message repeated 3133 times The text of what would normally be in the output here is the likes of: Root mount waiting for: CAM . . . Root mount waiting for: CAM nda0 at nvme0 bus 0 scbus4 target 0 lun 1 nda0: nda0: Serial Number REDACTED nda0: nvme version 1.3 nda0: 1907729MB (3907029168 512 byte sectors) nda1 at nvme1 bus 0 scbus5 target 0 lun 1 nda1: nda1: Serial Number REDACTED nda1: nvme version 1.0 nda1: 1430799MB (2930277168 512 byte sectors) nda2 at nvme2 bus 0 scbus6 target 0 lun 1 nda2: nda2: Serial Number REDACTED nda2: nvme version 1.0 nda2: 1430799MB (2930277168 512 byte sectors) nda3 at nvme3 bus 0 scbus7 target 0 lun 1 nda3: nda3: Serial Number REDACTED nda3: nvme version 1.2 nda3: 1953514MB (4000797360 512 byte sectors) nda4 at nvme4 bus 0 scbus8 target 0 lun 1 nda4: nda4: Serial Number REDACTED nda4: nvme version 1.2 nda4: 976762MB (2000409264 512 byte sectors) Setting hostuuid: REDACTED. Setting hostid: REDACTED. Starting file system checks: /dev/gpt/FBSDFSSDroot: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/gpt/FBSDFSSDroot: clean, 221370202 free (400602 frags, 27621200 = blocks, 0.1% fragmentation) Mounting local filesystems:. Autoloading module: acpi_wmi Autoloading module: ig4 Autoloading module: intpm But I do not get to see such when the 3000+ messages happen. >> Nov 20 23:14:21 7950X3D-UFS kernel: intsmb0: at device 20.0 on pci0 >> . . . >>=20 >> This stopped when I commented out the: >>=20 >> options MAXMEMDOM=3D2 The 3000+ messages returned, no MAXMEMDOM assignment present. I'd updated FreeBSD and replaced the 96 GiBytes of RAM with 192 GiBytes of RAM. "boot -s" and "boot -v" still get the messages. In hopes for recording the messages to see what is last before the messages start (no serial console) I tried adding "kern.msgbufsize=3D4587520" to /boot/loader.conf . The result was no "kernel: Process (pid 1) got signal 5" messages at all for the boot of the debug kernel+world. That and the earlier MAXMEMDOM change leading to the behavior changes suggest memory layout sensitivity. I've commented out "kern.msgbufsize=3D4587520" for testing in a context where the 3000+ messages occur. >> that I've had historically and built, installed, and booted >> the resulting DBG kernel. >>=20 >> I'll note that I never had the messages for the NODDBG kernel, >> despite it also having that line. >> . . . I've still not seen such from a non-debug kernel+world. I'll be doing a from scratch "bulk -a" under the debug kernel and world context as part of testing: https://reviews.freebsd.org/D42767 This should also give an idea if the context is unstable. =3D=3D=3D Mark Millard marklmi at yahoo.com