Messages by Thread
-
FYI: 13.2-STABLE stable/13-n256634-c4dfacd0b3c3 snapshot's send mail notices
Mark Millard
-
Ré : So much longer to update than install fresh (+ no install feedback)
Paul Dufresne
-
So much longer to update than install fresh (+ no install feedback)
Paul Dufresne
-
Version of OpenSSH in FreeBSD 14.0
Roger Marsh
-
FreeBSD 14.0-RC3 Now Available
Glen Barber
-
periodic daily takes a very long time to run (14-stable)
void
-
FreeBSD 14.0-RC1 and RC2 dvd1 packages
erickleuschke
-
Re: Local sshd_config modifications
Ben Stuyts
-
FreeBSD 14.0-RC2 Now Available
Glen Barber
-
14-Stable: Cannot load DRM kernel module
Philipp-Joachim Ost
-
zfs list output RELENG_13 vs RELENG_14
mike tancsa
-
freebsd-update 12.3 to 14.0RC1 takes 12-24 hours (block cloning regression)
Kevin Bowling
-
Missing c++ headers after upgrade from 13.2-RELEASE to 14.0-RC1
Renato Botelho
-
FreeBSD 14.0-RC1 Now Available
Glen Barber
-
RE: git: d2025992ab68 - releng/14.0 - release: update releng/14.0 from BETA to RC
Mark Millard
-
State of OpenSSL in releng/13.2?
Patrick M. Hausen
-
Change to installation of security/ca_root_nss seems to have broken my mail?
Andrew Reilly
-
FreeBSD 14.0-BETA5 Now Available
Glen Barber
-
Re: FreeBSD Errata Notice FreeBSD-EN-23:09.freebsd-update [REVISED]
monochrome
-
Base libc++ missing symbol
Joel Bodenmann
-
15 & 14: ram_attach vs. its using regions_to_avail vs. "bus_alloc_resource" can lead to: panic("ram_attach: resource %d failed to attach", rid)
Mark Millard
-
FreeBSD 14.0-BETA4 Now Available
Glen Barber
-
ifconfig -v ix0 output delay
mike tancsa
-
14.0-BETA3 amd64: panic while building packages with poudriere
Yasuhiro Kimura
-
nvd->nda switch and blocksize changes for ZFS
Frank Behrens
-
nvd compatibility links and geli
Stefan Ehmann
-
Update on 14.0-RELEASE
Glen Barber
-
FreeBSD 14.0-BETA3 Now Available
Glen Barber
-
Re: How to Boot FreeBSD Using pftf/RPi4 UEFI (I got: "panic: ram_attach: resource 5 failed to attach" from FreeBSD-14.0-BETA3)
Mark Millard
-
Fusefs unionfs trouble with hardlinks?
ltning-freebsd-stable
-
FYI: RPi4B via ACPI style boot suggests "armv8crypto0: CPU lacks AES instructions" can lead to a hung up boot sequence in 14.0-BETA2
Mark Millard
-
Build of 14 on 13 creates a file which needs libdialog.so.9
Pete French
-
local-unbound stopped working after upgrade to 13.2
Alain Zscheile
-
FreeBSD 14.0-BETA2 Now Available
Glen Barber
-
tcpdump and timezone mismatch (STABLE 14 vs STABLE 13)
mike tancsa
-
sys/net/if_lagg_test:status_stress can lead to use-after-free in main (both before and after stable/14 was created), at least on aarch64
Mark Millard
-
Looks like the kyua zfs tests likely are not used on aarch64 or other contexts with unsigned char
Mark Millard
-
Update to BETA1 can't login: pam_opie.so not found
Nenhum_de_Nos
-
FreeBSD 14.0-BETA1 Now Available
Glen Barber
-
main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics
Mark Millard
-
Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics
Mark Millard
-
Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics
Glen Barber
-
Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics
Mark Millard
-
Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics
Alexander Motin
-
Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics
Mark Millard
-
Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics
Mark Millard
-
Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics
Martin Matuska
-
Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics
Mark Millard
-
Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics
Alexander Motin
-
Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics
Martin Matuska
-
Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics
Mark Millard
-
Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics
Mark Millard
-
Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics
Mark Millard
-
Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics
Mark Millard