Re: elfctl is broken

[Konstantin Belousov]

On Fri, Jan 22, 2021 at 05:13:16PM -0800, Steve Kargl wrote:
> ===> usr.bin/elfctl (all)
> cc -target i386-unknown-freebsd14.0 --sysroot=/usr/obj/usr/src/i386.i386/tmp 
> -B/usr/obj/usr/src/i386.i386/tmp/usr/bin  -O2 -pipe -fno-common 
> -I/usr/src/contrib/elftoolchain/li belftc 
> -I/usr/src/contrib/elftoolchain/common -march=core2  -MD  -MF.depend.elfctl.o 
> -MTelfctl.o -std=gnu99 -Wno-format-zero-length -fstack-protector-strong 
> -Wsystem-headers - Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter 
> -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type 
> -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wun used-parameter 
> -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls 
> -Wold-style-definition -Wno-pointer-sign -Wmissing-variable-declarations 
> -Wthread-saf ety -Wno-empty-body -Wno-string-plus-int 
> -Wno-unused-const-variable  -Qunused-arguments-c 
> /usr/src/usr.bin/elfctl/elfctl.c -o elfctl.o  
>/usr/src/usr.bin/elfctl/elfctl.c:258:18: error: comparison of integers of 
> different signs: 'long' and 'unsigned int' 
 [-
>  Werror,-Wsign-compare]  else if (val > 
> UINT_MAX)
>   ~~~ ^   
>   
> 1 error generated.
>   
>
> *** Error code 1  
> 
https://reviews.freebsd.org/D28301
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Can In-Kernel TLS (kTLS) work with any OpenSSL Application?

[Ronald Klop]

On Wed, 20 Jan 2021 21:21:15 +0100, Neel Chauhan  wrote:


Hi freebsd-current@,

I know that In-Kernel TLS was merged into the FreeBSD HEAD tree a while
back.

With 13.0-RELEASE around the corner, I'm thinking about upgrading my
home server, well if I can accelerate any SSL application.

I'm asking because I have a home server on a symmetrical Gigabit
connection (Google Fiber/Webpass), and that server runs a Tor relay. If
you're interested in how Tor works, the EFF has a writeup:
https://www.eff.org/pages/what-tor-relay

But the main point for you all is: more-or-less Tor relays deal with
1000s TLS connections going into and out of the server.

Would In-Kernel TLS help with an application like Tor (or even load
balancers/TLS termination), or is it more for things like web servers
sending static files via sendfile() (e.g. CDN used by Netflix).

My server could also work with Intel's QuickAssist (since it has an
Intel Xeon "Scalable" CPU). Would QuickAssist SSL be more helpful here?

I'm asking since I don't know whether to upgrade my home server to 13.x
or leave it at 12.x. Yes, I do know we need a special OpenSSL to use
kTLS.

-Neel



According to the history of the openssl port it has support for KTLS.
https://www.freshports.org/security/openssl
I don't know about the openssl in base.

But I think for Tor to support KTLS it needs to implement some things  
itself. More information about that could be asked at the maintainer of  
the port (https://www.freshports.org/security/tor/) or upstream at the Tor  
project.


Regards,
Ronald.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Can In-Kernel TLS (kTLS) work with any OpenSSL Application?

[Rick Macklem]

Ronald Klop wrote:
>On Wed, 20 Jan 2021 21:21:15 +0100, Neel Chauhan  wrote:
>
>> Hi freebsd-current@,
>>
>> I know that In-Kernel TLS was merged into the FreeBSD HEAD tree a while
>> back.
>>
>> With 13.0-RELEASE around the corner, I'm thinking about upgrading my
>> home server, well if I can accelerate any SSL application.
>>
>> I'm asking because I have a home server on a symmetrical Gigabit
>> connection (Google Fiber/Webpass), and that server runs a Tor relay. If
>> you're interested in how Tor works, the EFF has a writeup:
>> https://www.eff.org/pages/what-tor-relay
>>
>> But the main point for you all is: more-or-less Tor relays deal with
>> 1000s TLS connections going into and out of the server.
>>
>> Would In-Kernel TLS help with an application like Tor (or even load
>> balancers/TLS termination), or is it more for things like web servers
>> sending static files via sendfile() (e.g. CDN used by Netflix).
>>
>> My server could also work with Intel's QuickAssist (since it has an
>> Intel Xeon "Scalable" CPU). Would QuickAssist SSL be more helpful here?
There is now qat(4), which KTLS should be able to use, but I do
not think it has been tested for this. I also have no idea
if it can be used effectively for userland encryption?

>>
>> I'm asking since I don't know whether to upgrade my home server to 13.x
>> or leave it at 12.x. Yes, I do know we need a special OpenSSL to use
>> kTLS.
>>
>> -Neel

I cannot answer your main question. All I can tell you is this...
KTLS works very well for NFS, but that is, at least in part, because the data
never needs to move up to userspace. For server side read, the data is read
into anonymous pages by VOP_READ() and then those are handed to the
socket hanging off of MEXTPG mbufs. The KTLS then creates/encrypts the
application data records that go on the wire.

Since I assume Tor does SSL_write() or similar in userspace, the question
becomes "is doing the encryption in the kernel instead of userspace going
to perform better?". For something like a Chelsio-T6, I'd guess yes. For
software encryption, I have no idea?

The KTLS software encryption creates one kernel thread per CPU and then
sockets that are KTLS enabled are assigned to one of these threads. Does
this help w.r.t. your load balancing issue? Again, I have no idea.

>According to the history of the openssl port it has support for KTLS.
>https://www.freshports.org/security/openssl
>I don't know about the openssl in base.
I believe both openssl and openssl-devel in ports have the KTLS support
in them, although you might need to click on "KTLS" during the port
build to enable it. (I use openssl-devel, which is OpenSSL3, still in alpha
test, but seems to work well.)
openssl in base does not have KTLS support, as far as I know.

>But I think for Tor to support KTLS it needs to implement some things
>itself. More information about that could be asked at the maintainer of
>the port (https://www.freshports.org/security/tor/) or upstream at the Tor
>project.
To just make it work, I don't think changes are needed beyond linking to
the correct OpenSSL libraries (assuming it uses OpenSSL, of course).
(There are new library calls an application can use to check to see if
KTLS is enabled for the connection, but if it doesn't care, I don't think
those calls are needed?)

You do need to run a kernel with "options KERN_TLS" and set
kern.ipc.tls.enable=1
kern.ipc.mb_use_ext_pgs=1

rick

Regards,
Ronald.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Which branch in git is 13.0-current?

[Malcolm Matalka]

I upgraded my src checkout to git, and looks like I'm on 14.0-CURRENT?


FreeBSD bsdell 14.0-CURRENT FreeBSD 14.0-CURRENT #33
main-c256217-g6c789c55c4ba: Sat Jan 23 16:08:16 CET 2021
root@bsdell:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64

I am in the main branch, which I got by following the docs on
transitioning to git.

The main issue is I can't use pkg now.

Thanks!
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Which branch in git is 13.0-current?

[Mario Lobo]

Stable/13

On Sat, Jan 23, 2021, 13:43 Malcolm Matalka  wrote:

> I upgraded my src checkout to git, and looks like I'm on 14.0-CURRENT?
>
>
> FreeBSD bsdell 14.0-CURRENT FreeBSD 14.0-CURRENT #33
> main-c256217-g6c789c55c4ba: Sat Jan 23 16:08:16 CET 2021
> root@bsdell:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64
>
> I am in the main branch, which I got by following the docs on
> transitioning to git.
>
> The main issue is I can't use pkg now.
>
> Thanks!
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

RE: Which branch in git is 13.0-current?

[driesm.michiels]

> -Original Message-
> From: owner-freebsd-curr...@freebsd.org  curr...@freebsd.org> On Behalf Of Malcolm Matalka
> Sent: Saturday, 23 January 2021 17:43
> To: FreeBSD Current 
> Subject: Which branch in git is 13.0-current?
> 
> I upgraded my src checkout to git, and looks like I'm on 14.0-CURRENT?
> 
> 
> FreeBSD bsdell 14.0-CURRENT FreeBSD 14.0-CURRENT #33
> main-c256217-g6c789c55c4ba: Sat Jan 23 16:08:16 CET 2021
> root@bsdell:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64
> 
> I am in the main branch, which I got by following the docs on
transitioning to
> git.
> 
> The main issue is I can't use pkg now.

Build pkg from ports or wait a bit till the clusters have caught up building
the packages with the base version change.

Dries


> 
> Thanks!
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Which branch in git is 13.0-current?

[Malcolm Matalka]

driesm.michi...@gmail.com writes:

>> -Original Message-
>> From: owner-freebsd-curr...@freebsd.org > curr...@freebsd.org> On Behalf Of Malcolm Matalka
>> Sent: Saturday, 23 January 2021 17:43
>> To: FreeBSD Current 
>> Subject: Which branch in git is 13.0-current?
>> 
>> I upgraded my src checkout to git, and looks like I'm on 14.0-CURRENT?
>> 
>> 
>> FreeBSD bsdell 14.0-CURRENT FreeBSD 14.0-CURRENT #33
>> main-c256217-g6c789c55c4ba: Sat Jan 23 16:08:16 CET 2021
>> root@bsdell:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64
>> 
>> I am in the main branch, which I got by following the docs on
> transitioning to
>> git.
>> 
>> The main issue is I can't use pkg now.
>
> Build pkg from ports or wait a bit till the clusters have caught up building
> the packages with the base version change.

Does that mean CURRENT is now 14.0?  I must have missed the
announcement.

>
> Dries
>
>
>> 
>> Thanks!
>> ___
>> freebsd-current@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Which branch in git is 13.0-current?

[Yasuhiro Kimura]

From: Malcolm Matalka 
Subject: Re: Which branch in git is 13.0-current?
Date: Sat, 23 Jan 2021 18:16:21 +0100

>> Build pkg from ports or wait a bit till the clusters have caught up building
>> the packages with the base version change.
> 
> Does that mean CURRENT is now 14.0?  I must have missed the
> announcement.

https://lists.freebsd.org/pipermail/dev-commits-src-all/2021-January/001588.html

---
Yasuhiro Kimura
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

RE: Which branch in git is 13.0-current?

[driesm.michiels]

> >> -Original Message-
> >> From: owner-freebsd-curr...@freebsd.org  >> curr...@freebsd.org> On Behalf Of Malcolm Matalka
> >> Sent: Saturday, 23 January 2021 17:43
> >> To: FreeBSD Current 
> >> Subject: Which branch in git is 13.0-current?
> >>
> >> I upgraded my src checkout to git, and looks like I'm on 14.0-CURRENT?
> >>
> >>
> >> FreeBSD bsdell 14.0-CURRENT FreeBSD 14.0-CURRENT #33
> >> main-c256217-g6c789c55c4ba: Sat Jan 23 16:08:16 CET 2021
> >> root@bsdell:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64
> >>
> >> I am in the main branch, which I got by following the docs on
> > transitioning to
> >> git.
> >>
> >> The main issue is I can't use pkg now.
> >
> > Build pkg from ports or wait a bit till the clusters have caught up
> > building the packages with the base version change.
> 
> Does that mean CURRENT is now 14.0?  I must have missed the
> announcement.

That is correct, 13-stable has been branched from 13-current which has now
been bumped to 14-current.
Because it's a major version change going from 13 to 14, pkg is a bit
agitated regarding the ABI.

> >
> > Dries
> >
> >
> >>
> >> Thanks!
> >> ___
> >> freebsd-current@freebsd.org mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> >> To unsubscribe, send any mail to "freebsd-current-
> unsubscr...@freebsd.org"


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

RE: Which branch in git is 13.0-current?

[Thomas Mueller]

> > Does that mean CURRENT is now 14.0?  I must have missed the
> > announcement.

> That is correct, 13-stable has been branched from 13-current which has now
> been bumped to 14-current.
> Because it's a major version change going from 13 to 14, pkg is a bit
> agitated regarding the ABI.

> > > Dries

There should have been announcements of the src tree branch on current and 
stable emailing lists!

My question is how, using git, to track both 13-stable and 14-current without 
having entirely separate trees as I had to do with cvs and svn.

I think there is a git worktree command but can't remember how I used it, with 
Haiku in that case.

Then I will want to know how to determine which tree I will be compiling.

Tom

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: 13-alpha2 libncurses removal breaks ports build

[John Kennedy]

On Sat, Jan 23, 2021 at 10:40:57PM +, Kostya Berger wrote:
> Hi everyone,I don't seem to find any mentioning in the /usr/ports/UPDATING 
> about how one should handle the removal of libncurses.so.9 from base. 
> Source UPDATING only says:ncurses installation has been modified to only keep 
> the widechar
>     enabled version.  Incremental build is broken for that change, so it
>     requires a clean build.
> If that means to just build all ports anew, then it doesn't work as ports 
> don't seem to incorporate any change related to this one. It would seem 
> default configuration should take into account this, but it doesn't.

  So you found the right note, but yes, it sort of buried the lead.  I've
found with that and a few other libraries that I tend to get burned when you
hit the "make delete-old-libs" phase of kernel installation, where the first
clean-room poudriere port build still has them available for the ports to
find.  I usually end up re-rebuilding the kernel+world (so everything is
now rebuilt without those removed libraries), updating poudriere with that,
and doing a full ports recompile.

  If you're not rebuilding your own ports (probably really dodgy during this
part of the release schedule) then you're probably just going to have to wait.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: FreeBSD 13.0 Build Option Sweep (13.0-ALPHA2 Update)

[Michael Dexter]

Hello all,

I have re-run every option that failed under 13.0-ALPHA1 build under 
12.2, on 13.0-ALPHA2 under 13.0-ALPHA2.


HUGE thanks to everyone who has helped resolve failing build options!

I have linked a list of annotated remaining failures plus an archive of 
the full build here:


https://callfortesting.org/results/bos-FreeBSD-13A1/


Notably:

WITHOUT_CRYPT WITHOUT_OPENSSL (Regression: Worked in May 2020) PR:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252841

WITHOUT_INSTALLLIB PR with a possible fix but it requires a decision by 
someone familiar with the repercussions:


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252757

WITHOUT_TESTS_SUPPORT PR:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252843


I am happy to test patches!

All the best,

Michael
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: RTC on ROCKPRO64

[Philip Paeps]

On 2021-01-22 23:16:29 (+0800), Henri Hennebert wrote:
I have tested https://reviews.freebsd.org/D22692 on my ROCKPRO64 with 
a battery and it works. (After correcting the typo at line 516 of 
rk805.c)


Is it possible to merge it for 13.0-RELEASE ?


It looks like that revision needs some changes before it can be 
accepted.  I'll see if I can make those changes.


Thanks.
Philip

--
Philip Paeps
Senior Reality Engineer
Alternative Enterprises
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Which branch in git is 13.0-current?

[Russell L. Carter]

On 1/23/21 10:22 AM, driesm.michi...@gmail.com wrote:



-Original Message-
From: owner-freebsd-curr...@freebsd.org  On Behalf Of Malcolm Matalka
Sent: Saturday, 23 January 2021 17:43
To: FreeBSD Current 
Subject: Which branch in git is 13.0-current?

I upgraded my src checkout to git, and looks like I'm on 14.0-CURRENT?


FreeBSD bsdell 14.0-CURRENT FreeBSD 14.0-CURRENT #33
main-c256217-g6c789c55c4ba: Sat Jan 23 16:08:16 CET 2021
root@bsdell:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64

I am in the main branch, which I got by following the docs on

transitioning to

git.

The main issue is I can't use pkg now.


Build pkg from ports or wait a bit till the clusters have caught up
building the packages with the base version change.


Does that mean CURRENT is now 14.0?  I must have missed the
announcement.


That is correct, 13-stable has been branched from 13-current which has now
been bumped to 14-current.
Because it's a major version change going from 13 to 14, pkg is a bit
agitated regarding the ABI.


So has anyone tracking stable/12 and ports successfully completed the
git checkout stable/13; make buildworld; make installworld; mergemaster
drill?  I see I can checkout stable/13.

Do make.conf | src.conf | GENERIC have silent breaking changes?
I usually, recklessly, assume no.

Ima throw the build->install as soon as the drill looks good.

Russell



Dries




Thanks!
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-

unsubscr...@freebsd.org"



___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"



___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Which branch in git is 13.0-current?

[David Wolfskill]

On Sat, Jan 23, 2021 at 06:34:58PM -0700, Russell L. Carter wrote:
> ...
> > That is correct, 13-stable has been branched from 13-current which has now
> > been bumped to 14-current.
> > Because it's a major version change going from 13 to 14, pkg is a bit
> > agitated regarding the ABI.
> 
> So has anyone tracking stable/12 and ports successfully completed the
> git checkout stable/13; make buildworld; make installworld; mergemaster
> drill?  I see I can checkout stable/13.

With the substitution of "etcupdate" for "mergemaster," yes.

Mind, I am using ports built under stable/12: I have installed the
misc/compat12x port.

(My build machine is presently running poudriere under:

FreeBSD freebeast.catwhisker.org 13.0-ALPHA2 FreeBSD 13.0-ALPHA2 #1162 
stable/13-c256208-gf76393a6305b: Sat Jan 23 07:09:19 PST 2021 
r...@freebeast.catwhisker.org:/common/S3/obj/usr/src/amd64.amd64/sys/GENERIC  
amd64 1300136 1300136

building packages for stable/13.  I don't plan to use them right
away; this is mostly a bit of a stress-test for stable/13: bapt@
called it "poudriere" for at least one good reason.)

Current status:

[13amd64-ports-home] [2021-01-23_22h27m11s] [parallel_build:] Queued: 1038 
Built: 568  Failed: 0Skipped: 0Ignored: 0Tobuild: 470   Time: 
03:21:46


> Do make.conf | src.conf | GENERIC have silent breaking changes?
> I usually, recklessly, assume no.

My build machine (builds and) runs a GENERIC kernel.  It also builds
a couple of other kernels for stable/12 and stable/13; no issues
with either.

> Ima throw the build->install as soon as the drill looks good.
> 
> Russell
> 

I admit to having cheated a fair bit: I have also been tracking head.

So last night, I "cloned" my "head" slice for use for stable/13; there
was little to change, once that was done.  (Yes, I use MBR/BIOS
booting.)

Boring details:

* History: https://www.catwhisker.org/~david/FreeBSD/history/

* How I do stuff: https://www.catwhisker.org/~david/FreeBSD/upgrade.html

* How I keep sources in sync:
  https://www.catwhisker.org/~david/FreeBSD/repo-sync.html

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
So Lindsey Graham thinks that Trump's incitement of the Capitol mob on 6 Jan
should be without consequences?  Graham suppoprts what the mob did??!?

See https://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

Re: Which branch in git is 13.0-current?

[Donald Willinger]

Look for 14-current.  There is no more 13. as I understand it.


On Sat, Jan 23, 2021 at 7:51 PM David Wolfskill 
wrote:

> On Sat, Jan 23, 2021 at 06:34:58PM -0700, Russell L. Carter wrote:
> > ...
> > > That is correct, 13-stable has been branched from 13-current which has
> now
> > > been bumped to 14-current.
> > > Because it's a major version change going from 13 to 14, pkg is a bit
> > > agitated regarding the ABI.
> >
> > So has anyone tracking stable/12 and ports successfully completed the
> > git checkout stable/13; make buildworld; make installworld; mergemaster
> > drill?  I see I can checkout stable/13.
>
> With the substitution of "etcupdate" for "mergemaster," yes.
>
> Mind, I am using ports built under stable/12: I have installed the
> misc/compat12x port.
>
> (My build machine is presently running poudriere under:
>
> FreeBSD freebeast.catwhisker.org 13.0-ALPHA2 FreeBSD 13.0-ALPHA2 #1162
> stable/13-c256208-gf76393a6305b: Sat Jan 23 07:09:19 PST 2021
> r...@freebeast.catwhisker.org:/common/S3/obj/usr/src/amd64.amd64/sys/GENERIC
> amd64 1300136 1300136
>
> building packages for stable/13.  I don't plan to use them right
> away; this is mostly a bit of a stress-test for stable/13: bapt@
> called it "poudriere" for at least one good reason.)
>
> Current status:
>
> [13amd64-ports-home] [2021-01-23_22h27m11s] [parallel_build:] Queued: 1038
> Built: 568  Failed: 0Skipped: 0Ignored: 0Tobuild: 470   Time:
> 03:21:46
>
>
> > Do make.conf | src.conf | GENERIC have silent breaking changes?
> > I usually, recklessly, assume no.
>
> My build machine (builds and) runs a GENERIC kernel.  It also builds
> a couple of other kernels for stable/12 and stable/13; no issues
> with either.
>
> > Ima throw the build->install as soon as the drill looks good.
> >
> > Russell
> > 
>
> I admit to having cheated a fair bit: I have also been tracking head.
>
> So last night, I "cloned" my "head" slice for use for stable/13; there
> was little to change, once that was done.  (Yes, I use MBR/BIOS
> booting.)
>
> Boring details:
>
> * History: https://www.catwhisker.org/~david/FreeBSD/history/
>
> * How I do stuff: https://www.catwhisker.org/~david/FreeBSD/upgrade.html
>
> * How I keep sources in sync:
>   https://www.catwhisker.org/~david/FreeBSD/repo-sync.html
>
> Peace,
> david
> --
> David H. Wolfskill  da...@catwhisker.org
> So Lindsey Graham thinks that Trump's incitement of the Capitol mob on 6
> Jan
> should be without consequences?  Graham suppoprts what the mob did??!?
>
> See https://www.catwhisker.org/~david/publickey.gpg for my public key.
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Which branch in git is 13.0-current?

[David Wolfskill]

On Sat, Jan 23, 2021 at 07:52:57PM -0600, Donald Willinger wrote:
> Look for 14-current.  There is no more 13. as I understand it.
> 

head is 14.  stable/13 and stable/12 also exist:

FreeBSD freebeast.catwhisker.org 12.2-STABLE FreeBSD 12.2-STABLE #1144 
stable/12-c243280-g4493b69d4aa: Sat Jan 23 03:33:26 PST 2021 
r...@freebeast.catwhisker.org:/common/S1/obj/usr/src/amd64.amd64/sys/GENERIC  
amd64 1202505 1202505

FreeBSD freebeast.catwhisker.org 13.0-ALPHA2 FreeBSD 13.0-ALPHA2 #1162 
stable/13-c256208-gf76393a6305b: Sat Jan 23 07:09:19 PST 2021 
r...@freebeast.catwhisker.org:/common/S3/obj/usr/src/amd64.amd64/sys/GENERIC  
amd64 1300136 1300136

FreeBSD freebeast.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #1162 
main-c256217-g6c789c55c4ba: Sat Jan 23 05:10:49 PST 2021 
r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC  
amd64 140 140


Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
So Lindsey Graham thinks that Trump's incitement of the Capitol mob on 6 Jan
should be without consequences?  Graham suppoprts what the mob did??!?

See https://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

Re: Beta Git repo for ports

[Philip Paeps]

On 2021-01-22 14:24:47 (+0800), Graham Perrin wrote:
Via 
 
:




Please: where to file enhancement requests (or bugs) for development 
of this cgit service for ports?


Is there a GitHub repo where issues might be raised? Or, are group 
e-mails (all four of you) preferred?


The g...@freebsd.org mailing list has been very responsive to 
suggestions.  That's probably a good place for them.


Philip

--
Philip Paeps
Senior Reality Engineer
Alternative Enterprises
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Beta Git repo for ports

[Warner Losh]

On Sat, Jan 23, 2021, 7:09 PM Philip Paeps  wrote:

> On 2021-01-22 14:24:47 (+0800), Graham Perrin wrote:
> > Via
> > <
> https://www.freebsd.org/news/status/report-2020-10-2020-12.html#Git-Migration-Working-Group>
>
> > :
> >
> > 
> >
> > Please: where to file enhancement requests (or bugs) for development
> > of this cgit service for ports?
> >
> > Is there a GitHub repo where issues might be raised? Or, are group
> > e-mails (all four of you) preferred?
>
> The g...@freebsd.org mailing list has been very responsive to
> suggestions.  That's probably a good place for them.
>

Yes... that's the best place.

Warner

Philip
>
> --
> Philip Paeps
> Senior Reality Engineer
> Alternative Enterprises
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Which branch in git is 13.0-current?

[John Kennedy]

On Sat, Jan 23, 2021 at 06:34:58PM -0700, Russell L. Carter wrote:
> So has anyone tracking stable/12 and ports successfully completed the
> git checkout stable/13; make buildworld; make installworld; mergemaster
> drill?  I see I can checkout stable/13.
> 
> Do make.conf | src.conf | GENERIC have silent breaking changes?
> I usually, recklessly, assume no.
> 
> Ima throw the build->install as soon as the drill looks good.

  I've done it about 3x now, from different stages of 12.2.  Don't have any
kernel modules from ports loaded, usually end up doing the world+kernel thing
twice due to some libraries going away, then rebuild all ports.

  I've continued to use mergemaster, but there is a thread talking about it
going towards obsolete.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

13-alpha2 libncurses removal breaks ports build

[Kostya Berger]

Hi everyone,I don't seem to find any mentioning in the /usr/ports/UPDATING 
about how one should handle the removal of libncurses.so.9 from base. 
Source UPDATING only says:ncurses installation has been modified to only keep 
the widechar
    enabled version.  Incremental build is broken for that change, so it
    requires a clean build.
If that means to just build all ports anew, then it doesn't work as ports don't 
seem to incorporate any change related to this one. It would seem default 
configuration should take into account this, but it doesn't.

The ports just use --with-libncurses-prefix=/usr, and there is no ncurses libs 
found there. This make it skip MOST of the ports I'm using.

Working Copy Root Path: /usr/ports
URL: https://svn.freebsd.org/ports/head
Relative URL: ^/head
Repository Root: https://svn.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 562417
Node Kind: directory
Schedule: normal
Last Changed Author: 0mp
Last Changed Rev: 562417
Last Changed Date: 2021-01-23 23:01:38 +0300 (Sat, 23 Jan 2021)

With kindest regards,
Kostya Berger
 
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Getting /usr/src to match specific git hash?

[Steve Kargl]

Suppose one has an empty /usr/src.

Suppose further that one had to re-install a 32-bit
i386-*-freebsd with the 24 Dec 2020 image available
from freebsd.org.

uname -a for the booted kernel shows

% uname -a
FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT #0 \
3cc0c0d66a0-c255241(main)-dirty: Thu Dec 24 05:43:23 UTC 2020 \
r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/i386.i386/sys/GENERIC i386

How does one use git to pull the exact sources that match
this specifc kernel?

-- 
Steve
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Getting /usr/src to match specific git hash?

[Yasuhiro Kimura]

From: Steve Kargl 
Subject: Getting /usr/src to match specific git hash?
Date: Sat, 23 Jan 2021 19:58:52 -0800

> Suppose one has an empty /usr/src.
> 
> Suppose further that one had to re-install a 32-bit
> i386-*-freebsd with the 24 Dec 2020 image available
> from freebsd.org.
> 
> uname -a for the booted kernel shows
> 
> % uname -a
> FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT #0 \
> 3cc0c0d66a0-c255241(main)-dirty: Thu Dec 24 05:43:23 UTC 2020 \
> r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/i386.i386/sys/GENERIC i386
> 
> How does one use git to pull the exact sources that match
> this specifc kernel?

cd /usr
git clone https://git.freebsd.org/src.git
cd src
git checkout 3cc0c0d66a0

---
Yasuhiro Kimura
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Getting /usr/src to match specific git hash?

[Don Lewis]

On 24 Jan, Yasuhiro Kimura wrote:
> From: Steve Kargl 
> Subject: Getting /usr/src to match specific git hash?
> Date: Sat, 23 Jan 2021 19:58:52 -0800
> 
>> Suppose one has an empty /usr/src.
>> 
>> Suppose further that one had to re-install a 32-bit
>> i386-*-freebsd with the 24 Dec 2020 image available
>> from freebsd.org.
>> 
>> uname -a for the booted kernel shows
>> 
>> % uname -a
>> FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT #0 \
>> 3cc0c0d66a0-c255241(main)-dirty: Thu Dec 24 05:43:23 UTC 2020 \
>> r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/i386.i386/sys/GENERIC i386
>> 
>> How does one use git to pull the exact sources that match
>> this specifc kernel?
> 
> cd /usr
> git clone https://git.freebsd.org/src.git
> cd src
> git checkout 3cc0c0d66a0

And don't take the git warning about having a detached HEAD as a
criticism.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Getting /usr/src to match specific git hash?

[Steve Kargl]

On Sun, Jan 24, 2021 at 01:08:05PM +0900, Yasuhiro Kimura wrote:
> From: Steve Kargl 
> Subject: Getting /usr/src to match specific git hash?
> Date: Sat, 23 Jan 2021 19:58:52 -0800
> 
> > Suppose one has an empty /usr/src.
> > 
> > Suppose further that one had to re-install a 32-bit
> > i386-*-freebsd with the 24 Dec 2020 image available
> > from freebsd.org.
> > 
> > uname -a for the booted kernel shows
> > 
> > % uname -a
> > FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT #0 \
> > 3cc0c0d66a0-c255241(main)-dirty: Thu Dec 24 05:43:23 UTC 2020 \
> > r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/i386.i386/sys/GENERIC i386
> > 
> > How does one use git to pull the exact sources that match
> > this specifc kernel?
> 
> cd /usr
> git clone https://git.freebsd.org/src.git
> cd src
> git checkout 3cc0c0d66a0
> 

Thank you.

-- 
Steve
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"