hain if it
was installed, but you may want to make sure it's properly removed:
# pkg remove -g 'FreeBSD-elftoolchain*'
appreciate the heads up! i can confirm this works on my current box i
migrated over from source builds to pkg base without any issues.
agree with later
Le 28 mai 2025 08:37:43 GMT+02:00, Ronald Klop a écrit :
>Van: Lexi Winter
>Datum: 28 mei 2025 03:19
>Aan: pkgb...@freebsd.org, curr...@freebsd.org
>Onderwerp: HEADS UP: 15.0 pkgbase, manual action required on upgrade
>
>>
>>
>>
>> hello,
>>
&
Ronald Klop:
> This makes me think of the /usr/ports/MOVED construction. Maybe
> something similar can be useful for base pkgs.
ideally this isn't something we want to be doing on an ongoing basis.
at the moment there are a number of files that are installed in the
wrong package by accident (usua
Van: Lexi Winter
Datum: 28 mei 2025 03:19
Aan: pkgb...@freebsd.org, curr...@freebsd.org
Onderwerp: HEADS UP: 15.0 pkgbase, manual action required on upgrade
hello,
if you use 15.0 with pkgbase, there are two recent changes which might
require manual intervention following "pkg up
hello,
if you use 15.0 with pkgbase, there are two recent changes which might
require manual intervention following "pkg upgrade":
7672d8d81ac1 moved ctld into the new FreeBSD-ctl package. if you use
ctld, you should install this package.
cc8c77c9e036 moved toolchain utilities (including ar, nm
On Thu, May 22, 2025 at 08:09:13PM +0100, Lexi Winter wrote:
as kp said, this is broken, but you can trivially fix it by moving the
IP addresses to the bridge interface instead. note that for SLAAC to
work on a bridge, you have to set ‘accept_rtadv’ and ‘auto_linklocal’ on
the bridge interface
void:
> On Mon, May 19, 2025 at 11:33:50AM +0100, Lexi Winter wrote:
> > in short, following this commit...
> >
> > b61850c4e6f "bridge(4): default net.link.bridge.member_ifaddrs to false"
> > https://cgit.freebsd.org/src/commit/?id=b61850c4e6f6b0f21b36da7238db969d9090309e
> >
> > ...it is now im
On 21/05/2025 18:01, void wrote:
This bhyve host was set up following instructions from the bhyve section of the
handbook. I've just checked and no mention is made of the
new requirement in section 24.7.1 of the handbook at
https://freebsd.org/handbook
So, if a lot of people run bhyve guests as
On Wed, May 21, 2025 at 04:44:46PM +0200, Kristof Provost wrote:
[2] because here bge1 has an ip addigned to it and is a bridge member
Yes, that is a problem. Assign REDACTED.REAL.IP to bridge1, not to bge1.
Oof! Thank you for clarifying. I'm glad I asked.
This bhyve host was set up followi
might also want to look at autobridge* options while you redo that config
On 21 May 2025, at 16:40, void wrote:
On Mon, May 19, 2025 at 11:33:50AM +0100, Lexi Winter wrote:
although it's possible everyone who is affected by this is already
aware
of the change, i thought i should send a heads up anyway, if only to
have a single place to discuss this (since ther
On Mon, May 19, 2025 at 11:33:50AM +0100, Lexi Winter wrote:
although it's possible everyone who is affected by this is already aware
of the change, i thought i should send a heads up anyway, if only to
have a single place to discuss this (since there was quite a lot of
discussion).
in
On Tue, Apr 29, 2025 at 08:44:50PM +0200, Dimitry Andric wrote:
> On 29 Apr 2025, at 19:43, Shawn Webb wrote:
> >
> > On Sun, Apr 27, 2025 at 07:42:44PM +0200, Dimitry Andric wrote:
> >> On 27 Apr 2025, at 17:04, Shawn Webb wrote:
> >>>
> >>> On Sat, Apr 26, 2025 at 06:06:54PM +0200, Dimitry An
On 29 Apr 2025, at 19:43, Shawn Webb wrote:
>
> On Sun, Apr 27, 2025 at 07:42:44PM +0200, Dimitry Andric wrote:
>> On 27 Apr 2025, at 17:04, Shawn Webb wrote:
>>>
>>> On Sat, Apr 26, 2025 at 06:06:54PM +0200, Dimitry Andric wrote:
>> ...
Please let me know if you encounter any problems res
On Sun, Apr 27, 2025 at 07:42:44PM +0200, Dimitry Andric wrote:
> On 27 Apr 2025, at 17:04, Shawn Webb wrote:
> >
> > On Sat, Apr 26, 2025 at 06:06:54PM +0200, Dimitry Andric wrote:
> ...
> >> Please let me know if you encounter any problems resulting due to this
> >> change, as I intend to MFC i
On 27 Apr 2025, at 17:04, Shawn Webb wrote:
>
> On Sat, Apr 26, 2025 at 06:06:54PM +0200, Dimitry Andric wrote:
...
>> Please let me know if you encounter any problems resulting due to this
>> change, as I intend to MFC it. For example, I tried covering all
>> incremental build scenarios, but I m
I updated my source tree and did a whole world build then did the
buildworld again without changing anything that would affect something
to get rebuild and then the world has been built now in 192 seconds.
Indeed, it seems pico files can be cached too. Sorry for the noise and
thank you all! Hav
On Sat, Apr 26, 2025 at 06:06:54PM +0200, Dimitry Andric wrote:
> Hi,
>
> In https://cgit.freebsd.org/src/commit/?id=2e47f35be5dc I committed a
> change to convert libllvm, libclang, and liblldb into private shared
> libraries. This means that tools like clang, lld, lldb, and more are now
> quite
On 27 Apr 2025, at 01:28, Yusuf Yaman wrote:
>
> I am a new user of 15.0-CURRENT and just updated my source tree and
> noticed that there are now files to be built that have the ".pico"
> extension, as a ccache user, i was enjoying fast world/kernel builds but
> these files doesn't seem to get
On Sun, Apr 27, 2025 at 2:28 AM Yusuf Yaman wrote:
>
> Hi,
>
> I am a new user of 15.0-CURRENT and just updated my source tree and
> noticed that there are now files to be built that have the ".pico"
> extension, as a ccache user, i was enjoying fast world/kernel builds but
> these files doesn't s
Hi,
I am a new user of 15.0-CURRENT and just updated my source tree and
noticed that there are now files to be built that have the ".pico"
extension, as a ccache user, i was enjoying fast world/kernel builds but
these files doesn't seem to get cached to me and my world builds are
taking long t
On Thu, 10 Apr 2025, Bjoern A. Zeeb wrote:
Hi,
and the firmware is now also gone from stable/14 (which at the same time
got a few bug fixes for LinuxKPI malloc and LinuxKPI 802.11).
In case you run into any issues updating from a supported 14.x or 15
(younger than a year old [3]) please follow-
On Wed, 19 Mar 2025, Bjoern A. Zeeb wrote:
Hi,
before updating your system please run fwget(8) or build
wifi-firmware-iwlwifi-kmod (or the appropriate flavor) from ports if you
are using iwlwifi(4) or iwx(4).
You can do it any time as the extra firmware files will do no harm until
your next reb
On Wed, Apr 9, 2025 at 9:43 AM Shawn Webb wrote:
>
> On Sun, Apr 06, 2025 at 02:52:28PM -0700, Rick Macklem wrote:
> > On Sat, Apr 5, 2025 at 5:45 PM Shawn Webb
> > wrote:
> > >
> > > On Sat, Apr 05, 2025 at 05:36:07PM -0700, Rick Macklem wrote:
> > > > On Sat, Apr 5, 2025 at 4:43 PM Shawn Webb
On Sun, Apr 06, 2025 at 02:52:28PM -0700, Rick Macklem wrote:
> On Sat, Apr 5, 2025 at 5:45 PM Shawn Webb wrote:
> >
> > On Sat, Apr 05, 2025 at 05:36:07PM -0700, Rick Macklem wrote:
> > > On Sat, Apr 5, 2025 at 4:43 PM Shawn Webb
> > > wrote:
> > > >
> > > > On Sat, Apr 05, 2025 at 04:12:15PM -
On Sat, Apr 5, 2025 at 5:45 PM Shawn Webb wrote:
>
> On Sat, Apr 05, 2025 at 05:36:07PM -0700, Rick Macklem wrote:
> > On Sat, Apr 5, 2025 at 4:43 PM Shawn Webb
> > wrote:
> > >
> > > On Sat, Apr 05, 2025 at 04:12:15PM -0700, Rick Macklem wrote:
> > > > On Sat, Apr 5, 2025 at 9:12 AM Shawn Webb
On Sat, Apr 05, 2025 at 05:36:07PM -0700, Rick Macklem wrote:
> On Sat, Apr 5, 2025 at 4:43 PM Shawn Webb wrote:
> >
> > On Sat, Apr 05, 2025 at 04:12:15PM -0700, Rick Macklem wrote:
> > > On Sat, Apr 5, 2025 at 9:12 AM Shawn Webb
> > > wrote:
> > > >
> > > > On Sat, Apr 05, 2025 at 08:52:06AM -
On Sat, Apr 5, 2025 at 4:43 PM Shawn Webb wrote:
>
> On Sat, Apr 05, 2025 at 04:12:15PM -0700, Rick Macklem wrote:
> > On Sat, Apr 5, 2025 at 9:12 AM Shawn Webb
> > wrote:
> > >
> > > On Sat, Apr 05, 2025 at 08:52:06AM -0700, Rick Macklem wrote:
> > > > On Sat, Apr 5, 2025 at 8:50 AM Rick Mackle
On Sat, Apr 05, 2025 at 04:12:15PM -0700, Rick Macklem wrote:
> On Sat, Apr 5, 2025 at 9:12 AM Shawn Webb wrote:
> >
> > On Sat, Apr 05, 2025 at 08:52:06AM -0700, Rick Macklem wrote:
> > > On Sat, Apr 5, 2025 at 8:50 AM Rick Macklem
> > > wrote:
> > > >
> > > > On Fri, Apr 4, 2025 at 6:27 PM Sha
On Sat, Apr 5, 2025 at 9:12 AM Shawn Webb wrote:
>
> On Sat, Apr 05, 2025 at 08:52:06AM -0700, Rick Macklem wrote:
> > On Sat, Apr 5, 2025 at 8:50 AM Rick Macklem wrote:
> > >
> > > On Fri, Apr 4, 2025 at 6:27 PM Shawn Webb
> > > wrote:
> > > >
> > > > On Sat, Apr 05, 2025 at 01:04:25AM +,
On Sat, Apr 05, 2025 at 08:52:06AM -0700, Rick Macklem wrote:
> On Sat, Apr 5, 2025 at 8:50 AM Rick Macklem wrote:
> >
> > On Fri, Apr 4, 2025 at 6:27 PM Shawn Webb
> > wrote:
> > >
> > > On Sat, Apr 05, 2025 at 01:04:25AM +, Shawn Webb wrote:
> > > > On Fri, Apr 04, 2025 at 05:40:21PM -0700
On Sat, Apr 5, 2025 at 8:50 AM Rick Macklem wrote:
>
> On Fri, Apr 4, 2025 at 6:27 PM Shawn Webb wrote:
> >
> > On Sat, Apr 05, 2025 at 01:04:25AM +, Shawn Webb wrote:
> > > On Fri, Apr 04, 2025 at 05:40:21PM -0700, Rick Macklem wrote:
> > > > On Fri, Apr 4, 2025 at 10:50 AM Shawn Webb
> >
On Fri, Apr 4, 2025 at 6:27 PM Shawn Webb wrote:
>
> On Sat, Apr 05, 2025 at 01:04:25AM +, Shawn Webb wrote:
> > On Fri, Apr 04, 2025 at 05:40:21PM -0700, Rick Macklem wrote:
> > > On Fri, Apr 4, 2025 at 10:50 AM Shawn Webb
> > > wrote:
> > > >
> > > > On Thu, Apr 03, 2025 at 06:12:59PM -070
On Fri, Apr 4, 2025 at 6:36 PM Shawn Webb wrote:
>
> On Sat, Apr 05, 2025 at 01:27:17AM +, Shawn Webb wrote:
> > On Sat, Apr 05, 2025 at 01:04:25AM +, Shawn Webb wrote:
> > > On Fri, Apr 04, 2025 at 05:40:21PM -0700, Rick Macklem wrote:
> > > > On Fri, Apr 4, 2025 at 10:50 AM Shawn Webb
On Fri, Apr 4, 2025 at 6:27 PM Shawn Webb wrote:
>
> On Sat, Apr 05, 2025 at 01:04:25AM +, Shawn Webb wrote:
> > On Fri, Apr 04, 2025 at 05:40:21PM -0700, Rick Macklem wrote:
> > > On Fri, Apr 4, 2025 at 10:50 AM Shawn Webb
> > > wrote:
> > > >
> > > > On Thu, Apr 03, 2025 at 06:12:59PM -070
On Sat, Apr 05, 2025 at 01:04:25AM +, Shawn Webb wrote:
> On Fri, Apr 04, 2025 at 05:40:21PM -0700, Rick Macklem wrote:
> > On Fri, Apr 4, 2025 at 10:50 AM Shawn Webb
> > wrote:
> > >
> > > On Thu, Apr 03, 2025 at 06:12:59PM -0700, Rick Macklem wrote:
> > > > On Thu, Apr 3, 2025 at 4:52 PM Sh
On Sat, Apr 05, 2025 at 01:27:17AM +, Shawn Webb wrote:
> On Sat, Apr 05, 2025 at 01:04:25AM +, Shawn Webb wrote:
> > On Fri, Apr 04, 2025 at 05:40:21PM -0700, Rick Macklem wrote:
> > > On Fri, Apr 4, 2025 at 10:50 AM Shawn Webb
> > > wrote:
> > > >
> > > > On Thu, Apr 03, 2025 at 06:12:5
On Fri, Apr 04, 2025 at 05:40:21PM -0700, Rick Macklem wrote:
> On Fri, Apr 4, 2025 at 10:50 AM Shawn Webb wrote:
> >
> > On Thu, Apr 03, 2025 at 06:12:59PM -0700, Rick Macklem wrote:
> > > On Thu, Apr 3, 2025 at 4:52 PM Shawn Webb
> > > wrote:
> > > >
> > > > On Wed, Apr 02, 2025 at 01:51:26PM
On Fri, Apr 4, 2025 at 10:50 AM Shawn Webb wrote:
>
> On Thu, Apr 03, 2025 at 06:12:59PM -0700, Rick Macklem wrote:
> > On Thu, Apr 3, 2025 at 4:52 PM Shawn Webb
> > wrote:
> > >
> > > On Wed, Apr 02, 2025 at 01:51:26PM -0700, Rick Macklem wrote:
> > > > The commit 2ec2ba7e232d just hit main. I
On Thu, Apr 03, 2025 at 06:12:59PM -0700, Rick Macklem wrote:
> On Thu, Apr 3, 2025 at 4:52 PM Shawn Webb wrote:
> >
> > On Wed, Apr 02, 2025 at 01:51:26PM -0700, Rick Macklem wrote:
> > > The commit 2ec2ba7e232d just hit main. I do not think it will
> > > cause problems, but it is fairly large.
o set NFSv4
ACLs.
Oh, and to clarify it, ACLs are stored as "system" extended attributes,
which this new syscall/KAPI does not access and, in general, anything
else can be stored in extended attributes as well.
So no easy way for a user/sysadmin to see what the big "Heads Up" did.
Dennis
On Fri, Apr 4, 2025 at 6:37 AM Rick Macklem wrote:
>
> On Fri, Apr 4, 2025 at 1:48 AM Dennis Clarke wrote:
> >
> > On 4/3/25 19:52, Shawn Webb wrote:
> > > On Wed, Apr 02, 2025 at 01:51:26PM -0700, Rick Macklem wrote:
> > >> The commit 2ec2ba7e232d just hit main. I do not think it will
> > >> ca
On Fri, Apr 4, 2025 at 1:48 AM Dennis Clarke wrote:
>
> On 4/3/25 19:52, Shawn Webb wrote:
> > On Wed, Apr 02, 2025 at 01:51:26PM -0700, Rick Macklem wrote:
> >> The commit 2ec2ba7e232d just hit main. I do not think it will
> >> cause problems, but it is fairly large.
> >>
> >> Man page updates w
On 4/3/25 19:52, Shawn Webb wrote:
On Wed, Apr 02, 2025 at 01:51:26PM -0700, Rick Macklem wrote:
The commit 2ec2ba7e232d just hit main. I do not think it will
cause problems, but it is fairly large.
Man page updates will be done as separate commits.
Hopefully this will not cause grief, rick
On Thu, Apr 3, 2025 at 4:52 PM Shawn Webb wrote:
>
> On Wed, Apr 02, 2025 at 01:51:26PM -0700, Rick Macklem wrote:
> > The commit 2ec2ba7e232d just hit main. I do not think it will
> > cause problems, but it is fairly large.
> >
> > Man page updates will be done as separate commits.
> >
> > Hopef
On Wed, Apr 02, 2025 at 01:51:26PM -0700, Rick Macklem wrote:
> The commit 2ec2ba7e232d just hit main. I do not think it will
> cause problems, but it is fairly large.
>
> Man page updates will be done as separate commits.
>
> Hopefully this will not cause grief, rick
Hey Rick,
The patch revie
The commit 2ec2ba7e232d just hit main. I do not think it will
cause problems, but it is fairly large.
Man page updates will be done as separate commits.
Hopefully this will not cause grief, rick
On Mon, 31 Mar 2025 10:57:45 -0400
Ed Maste wrote:
> On Fri, 14 Mar 2025 at 23:03, Tomoaki AOKI wrote:
> >
> > On Wed, 12 Mar 2025 13:07:58 -0400
> > Ed Maste wrote:
> >
> > > Our in-kernel module linker currently performs symbol resolution
> > > against local symbols from other modules, which
[Just a resend with the current and stable lists included.]
On Mar 19, 2025, at 13:49, Mark Millard wrote:
Bjoern A. Zeeb wrote on
Date: Wed, 19 Mar 2025 17:55:17 UTC :
> Hi,
>
> I pushed an update to the iwlwifi firmware port today[1] and with the last
> release of FreeBSD 13 being out the d
Hi,
I pushed an update to the iwlwifi firmware port today[1] and with the last
release of FreeBSD 13 being out the door, 14.1-Release EoL end of this
month passed and the packages for the updated port appearing I'll
!!!
remove iwlwifi firmware from src.git for main and stable/14
Our in-kernel module linker currently performs symbol resolution
against local symbols from other modules, which is a bug.
In commits 95c20faf11a1 and ecd8245e0d77 kib introduced support to
have the kernel linker stop resolving local symbols from other files,
but did not change it by default to av
Upstream OpenSSH has been working on deprecating DSA keys for some
time, and I intend to follow suit in FreeBSD.
>From the OpenSSH 9.8p1 release notes:
===
OpenSSH has disabled DSA keys by default since 2015 but has retained
run-time optional support for them. DSA was the only mandatory-to-
imple
On Sat, Feb 01, 2025 at 06:06:27AM -0800, Rick Macklem wrote:
R> You might want to put an entry in UPDATING noting that the daemons
R> need to be upgraded with the kernel.
Of course I did :)
Short update on the resource leaks. The patch that reduces refcount on
the back channel proved to be inco
On Tue, Jan 21, 2025 at 10:27 PM Gleb Smirnoff wrote:
>
> CAUTION: This email originated from outside of the University of Guelph. Do
> not click links or open attachments unless you recognize the sender and know
> the content is safe. If in doubt, forward suspicious emails to
> ith...@uoguelph
On Tue, Jan 28, 2025 at 09:14:00PM -0800, Gleb Smirnoff wrote:
T> Second, with the patch the M_RPC leak count for me is 2. And I found that
these
T> two items are basically is a clnt_vc that belongs to a closed connection:
T>
T> f80029614a80 tcp4 0 0 10.6.6.9.772 10.6.6.9.204
On Mon, Jan 27, 2025 at 06:10:42PM -0800, Rick Macklem wrote:
R> I think I've found a memory leak, but it shouldn't be a show stopper.
R>
R> What I did on the NFS client side is:
R> # vmstat -m | fgrep -i rpc
R> # mount -t nfs -o nfsv4,tls nfsv4-server:/ /mnt
R> # ls --lR /mnt
R> --> Then I networ
On Tue, Jan 21, 2025 at 10:27 PM Gleb Smirnoff wrote:
>
> CAUTION: This email originated from outside of the University of Guelph. Do
> not click links or open attachments unless you recognize the sender and know
> the content is safe. If in doubt, forward suspicious emails to
> ith...@uoguelph
On Sun, Jan 26, 2025 at 1:44 PM Rick Macklem wrote:
>
> On Tue, Jan 21, 2025 at 10:27 PM Gleb Smirnoff wrote:
> >
> > CAUTION: This email originated from outside of the University of Guelph. Do
> > not click links or open attachments unless you recognize the sender and
> > know the content is s
On Tue, Jan 21, 2025 at 10:27 PM Gleb Smirnoff wrote:
>
> CAUTION: This email originated from outside of the University of Guelph. Do
> not click links or open attachments unless you recognize the sender and know
> the content is safe. If in doubt, forward suspicious emails to
> ith...@uoguelph
On Thu, Jan 23, 2025 at 02:42:54PM -0800, Rick Macklem wrote:
R> > The code is posted on phabricator, reviews D48547 through D48552.
R> > Reviewers are very welcome!
R> >
R> > I share my branch on Github. It is usually rebased on today's CURRENT:
R> >
R> > https://github.com/glebius/FreeBSD/commits
On Tue, Jan 21, 2025 at 10:27 PM Gleb Smirnoff wrote:
>
> CAUTION: This email originated from outside of the University of Guelph. Do
> not click links or open attachments unless you recognize the sender and know
> the content is safe. If in doubt, forward suspicious emails to
> ith...@uoguelph
Hi,
TLDR version:
users of NFS with Kerberos (e.g. running gssd(8)) as well as users of NFS with
TLS (e.g. running rpc.tlsclntd(8) or rpc.tlsservd(8)) as well as users of
network lock manager (e.g. having 'options NFSLOCKD' and running rpcbind(8))
are affected. You would need to recompile & rei
Hi all,
The FreeBSD Foundation, sponsored by the Sovereign Tech Agency, is funding
work this year which will be affecting the FreeBSD build process, and release
building in particular. The main goal is to allow the entire release process
to run without special privileges (aka root); subsidiary g
On Mon, 17 Jun 2024 at 11:16, Michael Gmelin wrote:
>
> Hi Ed,
>
> In case there is no EN, what is the process to add information about
> issues like this to the release notes? Something like "known issues",
> which those of us who read the release notes can stumble over and check?
Great question
> On 17. Jun 2024, at 20:34, Shawn Webb wrote:
>
> On Mon, Jun 17, 2024 at 10:54:29AM -0400, Ed Maste wrote:
>> It is currently possible to specify an IPv4 address without a
>> netmask/width to ifconfig or in rc.conf, e.g.:
>>
>>ifconfig_igb0="192.168.0.2"
>>
>> phk recently discovered[
On Mon, Jun 17, 2024 at 10:54:29AM -0400, Ed Maste wrote:
> It is currently possible to specify an IPv4 address without a
> netmask/width to ifconfig or in rc.conf, e.g.:
>
> ifconfig_igb0="192.168.0.2"
>
> phk recently discovered[1] that ifconfig chose a poor netmask/width
> when none was sp
On Mon, 17 Jun 2024 10:54:29 -0400
Ed Maste wrote:
> It is currently possible to specify an IPv4 address without a
> netmask/width to ifconfig or in rc.conf, e.g.:
>
> ifconfig_igb0="192.168.0.2"
>
> phk recently discovered[1] that ifconfig chose a poor netmask/width
> when none was spec
It is currently possible to specify an IPv4 address without a
netmask/width to ifconfig or in rc.conf, e.g.:
ifconfig_igb0="192.168.0.2"
phk recently discovered[1] that ifconfig chose a poor netmask/width
when none was specified. This was not an intentional change in
defaults but rather a bug
Hi everyone,
We currently publish a number of VM images on download.freebsd.org:
* Generic VM images, with URLs like
https://download.freebsd.org/snapshots/VM-IMAGES/15.0-CURRENT/amd64/20240613/FreeBSD-15.0-CURRENT-amd64-ufs-20240613-bb53f071e85a-270741.qcow2.xz
https://download.freebsd.org/snap
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
cle
On Fri, Nov 17, 2023 at 11:00:07AM +0100, Olivier Certner wrote:
> Hi Glen,
>
> > I also agree we cannot prevent people from downloading the images,
> > installers, whatever before the announcement. That is the lovely race
> > condition with which we have to live at the moment.
>
> Yes, and give
Glen Barber wrote:
> No. It merely suggests the release is not officially official yet.
Ok. Thanks for the clarification.
Jamie.
Hi Glen,
> I also agree we cannot prevent people from downloading the images,
> installers, whatever before the announcement. That is the lovely race
> condition with which we have to live at the moment.
Yes, and given that, I don't think you did anything wrong.
It seems that the race is the sa
On Thu, Nov 16, 2023 at 09:22:52PM +, Jamie Landeg-Jones wrote:
> > Ok. I do not know what exactly is your point, but releases are never
> > official until there is a PGP-signed email sent. The email is intended
> > for the general public of consumers of official releases, not "yeah,
> > but"
> Ok. I do not know what exactly is your point, but releases are never
> official until there is a PGP-signed email sent. The email is intended
> for the general public of consumers of official releases, not "yeah,
> but"s.
Foe a recent new build, I just went to the ftp site to grab the latest r
On Thu, Nov 16, 2023 at 12:07:36AM -0500, Glen Barber wrote:
> And if there is a reason to reissue a release, the update will reflect such.
>
> So to answer your latter question, yes. Unless it needs to be replaced.
>
> Glen
> Sent from my phone.
> Please excuse my brevity and/or typos.
>
> > O
And if there is a reason to reissue a release, the update will reflect such.
So to answer your latter question, yes. Unless it needs to be replaced.
Glen
Sent from my phone.
Please excuse my brevity and/or typos.
> On Nov 15, 2023, at 11:38 PM, The Doctor wrote:
>
> On Thu, Nov 16, 2023 at 1
Thank you for that.
Glen
Sent from my phone.
Please excuse my brevity and/or typos.
> On Nov 15, 2023, at 11:17 PM, Rich Reynolds wrote:
>
> On 11/15/23 20:19, Pete Wright wrote:
>>> On 11/15/23 16:30, Glen Barber wrote:
>>> The alternative would be to say nothing at all.
>>>
>>> Either way,
On Thu, Nov 16, 2023 at 12:30:30AM +, Glen Barber wrote:
> On Wed, Nov 15, 2023 at 08:39:39AM -0800, John Baldwin wrote:
> > On 11/14/23 8:52 PM, Glen Barber wrote:
> > > On Tue, Nov 14, 2023 at 08:10:23PM -0700, The Doctor wrote:
> > > > On Wed, Nov 15, 2023 at 02:27:01AM +, Glen Barber wr
On Wed, Nov 15, 2023 at 07:19:39PM -0800, Pete Wright wrote:
>
>
> On 11/15/23 16:30, Glen Barber wrote:
> > The alternative would be to say nothing at all.
> >
> > Either way, it is a productivity, communication drain. It is
> > a lose-lose situation no matter how one looks at it given the abo
On 11/15/23 16:30, Glen Barber wrote:
The alternative would be to say nothing at all.
Either way, it is a productivity, communication drain. It is
a lose-lose situation no matter how one looks at it given the above
context. We either get chastised for being "too open" into insights
delaying
On Wed, Nov 15, 2023 at 08:39:39AM -0800, John Baldwin wrote:
> On 11/14/23 8:52 PM, Glen Barber wrote:
> > On Tue, Nov 14, 2023 at 08:10:23PM -0700, The Doctor wrote:
> > > On Wed, Nov 15, 2023 at 02:27:01AM +, Glen Barber wrote:
> > > > On Tue, Nov 14, 2023 at 05:15:48PM -0700, The Doctor wro
On 11/14/23 8:52 PM, Glen Barber wrote:
On Tue, Nov 14, 2023 at 08:10:23PM -0700, The Doctor wrote:
On Wed, Nov 15, 2023 at 02:27:01AM +, Glen Barber wrote:
On Tue, Nov 14, 2023 at 05:15:48PM -0700, The Doctor wrote:
On Tue, Nov 14, 2023 at 08:36:54PM +, Glen Barber wrote:
We are stil
Well, today is your yesterday, so we might not be ready for another more
tomorrows your time, yesterdays, my time. Or something.
Glen
Sent from my phone.
Please excuse my brevity and/or typos.
> On Nov 15, 2023, at 2:39 AM, matti k wrote:
>
> On Wed, 15 Nov 2023 04:52:31 +
> Glen Barber
On Wed, 15 Nov 2023 04:52:31 +
Glen Barber wrote:
> > > Ok. I do not know what exactly is your point, but releases are
> > > never official until there is a PGP-signed email sent. The email
> > > is intended for the general public of consumers of official
> > > releases, not "yeah, but"s.
>
On Tue, Nov 14, 2023 at 08:10:23PM -0700, The Doctor wrote:
> On Wed, Nov 15, 2023 at 02:27:01AM +, Glen Barber wrote:
> > On Tue, Nov 14, 2023 at 05:15:48PM -0700, The Doctor wrote:
> > > On Tue, Nov 14, 2023 at 08:36:54PM +, Glen Barber wrote:
> > > > We are still waiting for a few (non-c
On Wed, Nov 15, 2023 at 02:27:01AM +, Glen Barber wrote:
> On Tue, Nov 14, 2023 at 05:15:48PM -0700, The Doctor wrote:
> > On Tue, Nov 14, 2023 at 08:36:54PM +, Glen Barber wrote:
> > > We are still waiting for a few (non-critical) things to complete before
> > > the announcement of 14.0-RE
On Tue, Nov 14, 2023 at 05:15:48PM -0700, The Doctor wrote:
> On Tue, Nov 14, 2023 at 08:36:54PM +, Glen Barber wrote:
> > We are still waiting for a few (non-critical) things to complete before
> > the announcement of 14.0-RELEASE will be ready.
> >
> > It should only be another day or so bef
On Tue, Nov 14, 2023 at 08:36:54PM +, Glen Barber wrote:
> We are still waiting for a few (non-critical) things to complete before
> the announcement of 14.0-RELEASE will be ready.
>
> It should only be another day or so before these things complete.
>
> Thank you for your understanding.
>
I
We are still waiting for a few (non-critical) things to complete before
the announcement of 14.0-RELEASE will be ready.
It should only be another day or so before these things complete.
Thank you for your understanding.
Glen
On behalf of: re@
signature.asc
Description: PGP signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
No email was sent for the branch commit, presumably because I pushed the
branch and did subsequent changes (i.e., version numbers, etc.)
afterward.
The stable/14 branch has been created, from where the remainder of the
14.0 series will live.
Glen
O
Greetings,
I've just pushed the results that remove 31,035 instances of $FreeBSD$ from
the main branch.
>From this point out, we are effectively done with $FreeBSD$, though there's
4 places where $FreeBSD$ still exists in the tree:
(1) In the contrib area, we have 621 remaining. I didn't remove a
On Fri, 5 May 2023 at 09:38, Ed Maste wrote:
>
> FreeBSD supports up to 256 CPU cores in the default kernel configuration
> (on Tier-1 architectures). Systems with more than 256 cores are
> available now, and will become increasingly common over FreeBSD 14’s
> lifetime. The FreeBSD Foundation is
I have just pushed this update into -current. It compiles and boots for me.
It should be a giant nop. I plan on MFCing this in a few days unless
there's unanticipated turbulence.
I have not updated the SIM drivers because most of the u_intXX_t use in
these drivers are not related to CAM interfaces
Commit ed03776ca7f4 enabled the NFSD_VNET, KRPC_VNET
and KGSS_VNET macros. Kernels built with "options VIMAGE"
now have a bunch of global variables used by the NFS server
vnet'd.
It is not quite ready to run the NFS server in a vnet prison.
There are still a couple of patches in D37741 and D38371
Hi,
Commit 7344856e3a6d was a large patch that added macros
that will front end the vnet macros. These macros are null ops now,
so they should not affect semantics.
However, the code did change how things get initialized for the nfsd
and that has already caused some breakage, that I think is now
Hi,
Commits over the last couple of days and ones happening
over the next few days change the internal KPI between
the nfs modules (nfscommon.ko, nfscl.ko and nfsserver.ko).
As such, after pulling an up to date main from the git repo
you need to build all nfs modules from the new sources.
I am n
Hi,
pon., 24 sty 2022 o 20:48 Marek Zarychta
napisał(a):
>
> Hello Marcin
> W dniu 24.01.2022 o 19:43, Marcin Wojtas pisze:
> > Hi Marek,
> >
> > pon., 24 sty 2022 o 08:17 Marek Zarychta
> > napisał(a):
> >>
> >> W dniu 24.01.2022 o 07:42, Marcin Wojtas pisze:
> >>> +freebsd-stable@
> >>>
> >>>
Hello Marcin
W dniu 24.01.2022 o 19:43, Marcin Wojtas pisze:
Hi Marek,
pon., 24 sty 2022 o 08:17 Marek Zarychta
napisał(a):
W dniu 24.01.2022 o 07:42, Marcin Wojtas pisze:
+freebsd-stable@
niedz., 23 sty 2022 o 11:36 Marcin Wojtas napisał(a):
Hi,
As of 396e9f259d962 the base system bina
Hi Marek,
pon., 24 sty 2022 o 08:17 Marek Zarychta
napisał(a):
>
> W dniu 24.01.2022 o 07:42, Marcin Wojtas pisze:
> > +freebsd-stable@
> >
> > niedz., 23 sty 2022 o 11:36 Marcin Wojtas napisał(a):
> >>
> >> Hi,
> >>
> >> As of 396e9f259d962 the base system binaries are now built as
> >> positi
1 - 100 of 3256 matches
Mail list logo
