[Bug 267596] Support UTF-8 dns resolution

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267596 Li-Wen Hsu changed: What|Removed |Added CC||lw...@freebsd.org --- Comment #2 from

[Bug 248502] Running multiple concurrent instances of freebsd-update(8) cause weird errors

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248502 Graham Perrin changed: What|Removed |Added Keywords||needs-qa Status|New

[Bug 229689] freebsd-update shouldn't add system breaking comments to config files

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229689 Graham Perrin changed: What|Removed |Added See Also||https://reviews.freebsd.org

[Bug 185546] freebsd-update(8) can modify sshd and lock you out of your system

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185546 Graham Perrin changed: What|Removed |Added CC||grahamper...@freebsd.org

[Bug 268377] jail -cr fails to set ipv6-address alias with ifconfig under certain conditions

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268377 Jamie Gritton changed: What|Removed |Added Status|New |Open Assignee|b...@freeb

[Bug 268384] HGST NVME U.2 Disk not accessible for releases prior to 13.1-STABLE

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268384 --- Comment #2 from Neil Bradley --- Neglected to also mention this disk works fine with Ubuntu 22.04 and Windows 10 and 11 and all boot to it. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 268384] HGST NVME U.2 Disk not accessible for releases prior to 13.1-STABLE

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268384 --- Comment #1 from Neil Bradley --- Additional info - this system has not yet been deployed. I'm a HW/SW developer myself and can provide remote access and full reconfigurability to anyone who may wish to do some on-system debugging. Happy

[Bug 268384] HGST NVME U.2 Disk not accessible for releases prior to 13.1-STABLE

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268384 Bug ID: 268384 Summary: HGST NVME U.2 Disk not accessible for releases prior to 13.1-STABLE Product: Base System Version: 13.1-RELEASE Hardware: amd64

[Bug 267028] General protection fault kernel panic immediately after kldload amdgpu

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267028 George Mitchell changed: What|Removed |Added Attachment #237279|0 |1 is obsolete|

[Bug 261169] [Intel AlderLake]Read&Write files to FAT32 or UFS partition cause data corrupt

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261169 --- Comment #7 from Amar Takhar --- This patch from Konstantin Belousov fixed these problems for me: https://kib.kiev.ua/git/gitweb.cgi?p=deviant3.git;a=commit;h=5d72240a8777b26d5e0a7d2d26bb919d05f60002 It also fixed all my audio issues

[Bug 261169] [Intel AlderLake]Read&Write files to FAT32 or UFS partition cause data corrupt

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261169 --- Comment #6 from Amar Takhar --- (In reply to Vico from comment #5) Disabling PCID did not change anything still the same issues. A patch from Konstantin Belousov fixed all my issues including audio. -- You are receiving this mail be

[Bug 268378] parsing error in network.subr can result in infinite loop on bootup

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268378 Cy Schubert changed: What|Removed |Added Assignee|b...@freebsd.org|c...@freebsd.org -- You are receivi

[Bug 268378] parsing error in network.subr can result in infinite loop on bootup

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268378 Cy Schubert changed: What|Removed |Added Attachment #238791|0 |1 is obsolete|

[Bug 268378] parsing error in network.subr can result in infinite loop on bootup

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268378 jyoun...@gmail.com changed: What|Removed |Added Attachment #238790|0 |1 is obsolete|

[Bug 268378] parsing error in network.subr can result in infinite loop on bootup

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268378 Cy Schubert changed: What|Removed |Added CC||c...@freebsd.org --- Comment #3 from

[Bug 268378] parsing error in network.subr can result in infinite loop on bootup

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268378 --- Comment #2 from jyoun...@gmail.com --- Created attachment 238790 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=238790&action=edit network.subr patch correction to previous patch -- You are receiving this mail because: You

[Bug 268378] parsing error in network.subr can result in infinite loop on bootup

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268378 jyoun...@gmail.com changed: What|Removed |Added Attachment #238789|0 |1 is obsolete|

[Bug 268378] parsing error in network.subr can result in infinite loop on bootup

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268378 --- Comment #1 from jyoun...@gmail.com --- Comment on attachment 238789 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=238789 network.subr ifalias_af_common_handler patch >--- /etc/network.subr 2022-12-13 22:55:03.480523000 -05

[Bug 268378] parsing error in network.subr can result in infinite loop on bootup

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268378 Bug ID: 268378 Summary: parsing error in network.subr can result in infinite loop on bootup Product: Base System Version: 13.1-RELEASE Hardware: Any O

[Bug 261446] freebsd-update should not create boot environment when it's not making changes to the boot environment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261446 Kyle Evans changed: What|Removed |Added CC||b...@freebsd.org Status|N

[Bug 198030] /usr/src/crypto/openssl/util/mkbuildinf.pl: No such file or directory on freebsd-update install

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198030 Ed Maste changed: What|Removed |Added Status|New |Closed Resolution|---

[Bug 185546] freebsd-update(8) can modify sshd and lock you out of your system

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185546 --- Comment #6 from Ed Maste --- See https://reviews.freebsd.org/D37703 for a proposed change -- You are receiving this mail because: You are the assignee for the bug.

[Bug 229689] freebsd-update shouldn't add system breaking comments to config files

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229689 --- Comment #4 from Ed Maste --- (In reply to Graham Perrin from comment #2) Prefixing the conflict markers with a comment character (#) isn't viable - it could result in even more confusing or unclear behaviour, as the config file would en

[Bug 185546] freebsd-update(8) can modify sshd and lock you out of your system

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185546 Ed Maste changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 229689] freebsd-update shouldn't add system breaking comments to config files

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229689 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org See Also|

[Bug 239492] freebsd-update mismatch with recompile from svn releng

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239492 Ed Maste changed: What|Removed |Added Status|New |Open -- You are receiving this mail be

[Bug 266270] freebsd-update cron corrupts freebsd-update upgrade's in progress

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266270 Ed Maste changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 248502] Running multiple concurrent instances of freebsd-update(8) cause weird errors

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248502 Ed Maste changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 253108] freebsd-update calling non-existing "merge" command

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253108 Ed Maste changed: What|Removed |Added Resolution|--- |FIXED Status|New

[Bug 255990] when there's in environment set GREP_OPTIONS '--color=always' it breaks freebsd-update

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255990 Ed Maste changed: What|Removed |Added Assignee|b...@freebsd.org|ema...@freebsd.org -- You are receivin

[Bug 255990] when there's in environment set GREP_OPTIONS '--color=always' it breaks freebsd-update

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255990 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org URL|

[Bug 265853] freebsd-update(8): new kernel produces pretty different what(1)'s output

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265853 Ed Maste changed: What|Removed |Added Status|New |Open -- You are receiving this mail be

[Bug 266270] freebsd-update cron corrupts freebsd-update upgrade's in progress

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266270 Ed Maste changed: What|Removed |Added Status|New |Open CC|

[Bug 195990] freebsd-update not upgrading files properly

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195990 Ed Maste changed: What|Removed |Added Resolution|--- |Overcome By Events Status|N

[Bug 195855] freebsd-update damages file system after 10.0 -> 10.1 install

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195855 Ed Maste changed: What|Removed |Added Status|New |Closed Resolution|---

[Bug 268377] jail -cr fails to set ipv6-address alias with ifconfig under certain conditions

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268377 Bug ID: 268377 Summary: jail -cr fails to set ipv6-address alias with ifconfig under certain conditions Product: Base System Version: 13.1-RELEASE Hardware: amd64

[Bug 193228] freebsd-update(8) -b for jail updates fails on last "install" within major-update

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193228 --- Comment #2 from Ed Maste --- I am sorry that nobody has investigated this issue since it was submitted. Does this issue still occur? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 234538] freebsd-update hangs on upgrade from 11.2p7 to 12.0 on Google Compute Engine

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234538 Ed Maste changed: What|Removed |Added Resolution|--- |Unable to Reproduce CC|

[Bug 233988] freebsd-update: Improve progress output on terminals

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233988 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org --- Comment #1 from

[Bug 147430] freebsd-update(8) not updating /usr/src/UPDATING

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=147430 --- Comment #7 from Ed Maste --- This is a consequence of the way FreeBSD-update binary patches are built. The patches from ENs/SAs are applied to the tree and new objects are built, and UPDATING itself does not appear in any of those patch

[Bug 232921] freebsd-update upgrade does not execute pwd_mkdb for ntpd

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232921 Kyle Evans changed: What|Removed |Added Status|In Progress |Closed Resolution|---

[Bug 153211] freebsd-update(8) can not fetch updates over a proxy with mandatory authorization

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=153211 Ed Maste changed: What|Removed |Added Resolution|--- |Unable to Reproduce Status|

[Bug 185546] freebsd-update(8) can modify sshd and lock you out of your system

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185546 --- Comment #5 from Ed Maste --- As comment #3 points out this conflict should have emitted a message and opened an editor; this may not be particularly user-friendly, and also as comment #3 suggests we ought to check for "<<<" markers

[Bug 120552] freebsd-update(8): freebsd-update - -r should check existence of directories

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=120552 Ed Maste changed: What|Removed |Added Status|Open|Closed Resolution|---

[Bug 266248] efi comconsole does not work with ARM64 Hyper-V

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266248 --- Comment #18 from Toomas Soome --- (In reply to schakraba...@microsoft.com from comment #17) Hm, ok, so with defaults (that is, use values provided by system firmware), there is no problem. In that case, I would suggest to set defaults

[Bug 268365] qlnxe(4) failed to transmit packet in bridge configuration

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268365 Bug ID: 268365 Summary: qlnxe(4) failed to transmit packet in bridge configuration Product: Base System Version: 13.1-RELEASE Hardware: Any OS: Any

[Bug 266248] efi comconsole does not work with ARM64 Hyper-V

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266248 --- Comment #17 from schakraba...@microsoft.com --- (In reply to Toomas Soome from comment #13) I have tried this, and it has worked on ARM64 Hyper-V. diff --git a/stand/efi/loader/efiserialio.c b/stand/efi/loader/efiserialio.c index 8b3f8e