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
Warner Losh wrote in
:
|On Tue, Jan 21, 2025 at 2:26 PM bob prohaska wrote:
|> On Tue, Jan 21, 2025 at 10:35:18PM +0200, Sulev-Madis Silber wrote:
|>> not shipping src in installer? what could possibly go wrong!
|>>
|>> i was just thinking of this the other day. that installers are
|> self-
On Tue, 21 Jan 2025 17:11:02 -0500
Brandon Allbery wrote:
> I would offer a data point: the first thing I did was install sudo from a
> package. The second thing I did was replace it with a build from the ports
> package installed with 14.2-RELEASE… which _downgraded_ it. This seems bad
> for any
Yes, the pkg was 1.9.16p2, the build from ports.tgz was 1.9.16p1. (The one
from ports HEAD as of a few days ago was 1.9.16p2_1, FWIW.) I'm still
getting used to the little changes since the last time I ran FreeBSD (back
around 5-CURRENT).
On Tue, Jan 21, 2025 at 5:43 PM Tomoaki AOKI
wrote:
> On
I would offer a data point: the first thing I did was install sudo from a
package. The second thing I did was replace it with a build from the ports
package installed with 14.2-RELEASE… which _downgraded_ it. This seems bad
for any security-impacting port.
On Tue, Jan 21, 2025 at 4:37 PM Tomek CED
On Tue, 21 Jan 2025 22:35:18 +0200
Sulev-Madis Silber
wrote:
> not shipping src in installer? what could possibly go wrong!
>
> i was just thinking of this the other day. that installers are self-contained
> packages that come with os and it's source...
When needed building something locally (
On Tue, Jan 21, 2025 at 10:29 PM Warner Losh wrote:
> (..)
> I think we should replace the populate /usr/src from a tarball with
> populate it
> with a tarball that represents a 1-deep checkout tree at the rev we built the
> release
> from. This lets users have the source, has minimal overhea
On Tue, Jan 21, 2025 at 2:26 PM bob prohaska wrote:
> On Tue, Jan 21, 2025 at 10:35:18PM +0200, Sulev-Madis Silber wrote:
> > not shipping src in installer? what could possibly go wrong!
> >
> > i was just thinking of this the other day. that installers are
> self-contained packages that come wit
On Tue, Jan 21, 2025 at 10:35:18PM +0200, Sulev-Madis Silber wrote:
> not shipping src in installer? what could possibly go wrong!
>
> i was just thinking of this the other day. that installers are self-contained
> packages that come with os and it's source...
>
>
>
There's no harm (and indeed
On Tue, Jan 21, 2025 at 9:09 PM Gleb Smirnoff wrote:
> On Sat, Jan 18, 2025 at 09:29:03AM -0800, bob prohaska wrote:
> b> (..)
> b> The most visible problem is lack of a /usr/src/.git directory. Can
> b> the existing src and ports directories be salvaged?
> (..)
> I think that /usr/src and /usr/por
not shipping src in installer? what could possibly go wrong!
i was just thinking of this the other day. that installers are self-contained
packages that come with os and it's source...
On January 21, 2025 10:09:43 PM GMT+02:00, Gleb Smirnoff
wrote:
...
>I think that /usr/src and /usr/ports a
Bob,
On Sat, Jan 18, 2025 at 09:29:03AM -0800, bob prohaska wrote:
b> A fresh install of
b> FreeBSD-15.0-CURRENT-amd64-20250102-3d0a0dda3a7d-274510-memstick.img
b> set up without much difficulty and Xorg seems to work out of the box
b> on my Lenovo t400s. Both src and ports directories were ins
12 matches
Mail list logo
