[Bug 204521] [new driver] [request] Port rtsx from OpenBSD to FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521 Zeus Panchenko changed: What|Removed |Added Attachment #215853|text/x-log |text/plain mime type|| --- Comment #257 from Zeus Panchenko --- Created attachment 215853 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=215853&action=edit commit 44ab5957e6 doesn't work (In reply to Henri Hennebert from comment #247) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204521] [new driver] [request] Port rtsx from OpenBSD to FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521 --- Comment #258 from Zeus Panchenko --- (In reply to Henri Hennebert from comment #247) 1. git pull (to commit 44ab5957e6) 2. edit rtsx.c as you showed 3. make 4. sysctl debug.bootverbose=1 5. kldload /usr/local/src/rtsx/rtsx/rtsx.ko 6. insert card on module load as well as on card insert/remove, keyboard freezes up to 1-2 minutes output is attached with descr: commit 44ab5957e6 doesn't work (In reply to Henri Hennebert from comment #247) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 247417] No way to make touchpad works under freebsd 12.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247417 --- Comment #10 from Vladimir Kondratyev --- (In reply to Mc James from comment #9) > Is that the only way? compiling the kernel No it is not the only way. It is just a way to replace libinput with x11-drivers/xf86-input-mouse back not touching any configuration files. Other way is add following snippet to xorg.conf: Section "InputClass" Identifier "PS/2 mouse" MatchDevicePath "/dev/psm*" Driver "mouse" EndSection Section "InputClass" Identifier "libinput PS/2 mouse" MatchDevicePath "/dev/input/event3" Option "Ignore" "true" EndSection > WHat happened from version 11 to 12 that we lost > all support for this touchpad. besides this touchpad > works under all BSD flavours available. > OPEN/NET/DragonFly We switched to libinput which does not implement required quirk (mapping 4-th mouse button to tap event) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 247472] /var/db/entropy not created with correct user/group
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247472 Bug ID: 247472 Summary: /var/db/entropy not created with correct user/group Product: Base System Version: 12.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: rajeev_v_pil...@yahoo.com After installation, /var/db/entropy does not have the correct owner/group of operator:operator. This causes /usr/libexec/save-entropy called by cron to fail. Entropy is not saved. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 247472] /var/db/entropy not created with correct user/group
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247472 Kubilay Kocak changed: What|Removed |Added Keywords||easy, needs-patch, needs-qa Status|New |Open Flags||mfc-stable12?, ||mfc-stable11? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 247474] `shutdown -p now` fails to power off with VirtualBox UEFI boot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247474 Bug ID: 247474 Summary: `shutdown -p now` fails to power off with VirtualBox UEFI boot Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: y...@utahime.org I have VirtualBox VM running 13-CURRENT. Environments are Host: 64bit Windows 10 ver. 1909 VirtualBox: 6.1.10 VM: 4CPU, 8GB Memory, 100GB Disk, Audio disabled. Bridged NIC In order to switch from legacy BIOS to UEFI I enabled UEFI on VM settings and reinstalled OS by using FreeBSD-13.0-CURRENT-amd64-20200611-r362037-disc1.iso. After that `shutdown -p now` (or select 'ACPI shutdown' in VM menu) fails to power off. Shutdown itself completes successfully. But power off never happens and CPU usage keeps high until either closing or resetting VM. If I switch back to legacy BIOS and reinstall OS then the problem disappears. And it doesn't happen with either 11.4-RELEASE or 12.1-RELEASE. I tried bisect and found this problem happens with base r342108 and after. Commit message of base r342108 says as following. yasu@rolling-vm-freebsd5[1012]% LANG=C svn log -c 342108 r342108 | cem | 2018-12-15 14:46:04 +0900 (Sat, 15 Dec 2018) | 7 lines efirt: When present, attempt to use EFI runtime services to shutdown PR: maybe related to 233998 (inconclusive at this time) Submitted by: byuu (previous version) Reviewed by:imp Differential Revision: https://reviews.freebsd.org/D18506 yasu@rolling-vm-freebsd5[1013]% -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 247417] No way to make touchpad works under freebsd 12.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247417 --- Comment #11 from Vladimir Kondratyev --- (In reply to Mc James from comment #9) You can try to map 4-th button to left button on xorg level with following command (not tested): $ xinput set-button-map device 1 2 3 1 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 158706] [regression] sed(1) in 8.2 gives incorrect output compared to 7.4
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=158706 Martin Birgmeier changed: What|Removed |Added CC||d8zne...@aon.at --- Comment #3 from Martin Birgmeier --- It probably was r355590 which (re-)added the capability to process \n as per the commit message. The test case makes use of \n in the RE. This should be merged to 12.2. -- Martin -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 158706] [regression] sed(1) in 8.2 gives incorrect output compared to 7.4
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=158706 --- Comment #4 from Kyle Evans --- (In reply to Martin Birgmeier from comment #3) Ah, I did overlook that. This has indeed been merged back to stable/12 and will appear in 12.2. :-) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 158706] [regression] sed(1) in 8.2 gives incorrect output compared to 7.4
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=158706 --- Comment #5 from Martin Birgmeier --- Thank you Kyle! -- Martin -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204521] [new driver] [request] Port rtsx from OpenBSD to FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521 --- Comment #259 from Henri Hennebert --- (In reply to gnikl from comment #253) To see the problem with pci_read_config can you install port sysutils/pciutils Then do lspci - >/tmp/dump isolate the output corresponding to Device 10ec:7227 and attach the result to this bug. Thanks -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 247482] loader: geli-encryption zfs boot environments [regression]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247482
Bug ID: 247482
Summary: loader: geli-encryption zfs boot environments
[regression]
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: misc
Assignee: b...@freebsd.org
Reporter: cont...@evilham.com
Hello,
I just had some time to track this down. The loader has been wrong on CURRENT
with my setup for a couple days, particularly since this was merged:
https://reviews.freebsd.org/D25324
(If I revert the mentioned diff, HEAD's loader works just fine)
Judging by the messages I see when booting, the boot loader tries the disk
partitions one by one as expected, finds the one with the OS and tries the
active Boot Environment.
And then it bails out in this bit of code from vdev_clear_pad2(vdev_t *vdev):
+ if (vdev_write(vdev, vdev->v_read_priv, off, be, VDEV_PAD_SIZE)) {
+ printf("failed to clear be area of primary vdev: %d\n",
+ errno);
+ }
The errno given for the right boot environment is 45, which appears to be
EOPNOTSUPP.
This is the message I'm seeing (modulo typos, transcript):
Setting currdev to zfs:zroot/ROOT/13-current:
failed to clear be area of primary vdev: 45
zfs nextboot: zfs:zroot/ROOT/12-release:
ERROR: cannot open /boot/lua/loader.lua: no such file or directory.
The setup is pretty simple, full disk geli-encrypted system created from the
installer with zfs on root with Boot Environments.
I'd try to fix this but ATM I don't feel too comfortable touching things that
appear to write to the disk :-D; can I help provide more information to fix
this?
Thank you,
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 247482] loader: geli-encryption zfs boot environments [regression]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247482 Evilham changed: What|Removed |Added Keywords||regression URL||https://reviews.freebsd.org ||/D25324 CC||tso...@freebsd.org --- Comment #1 from Evilham --- Adding tsoome to CC since they may still have this fresh in memory. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 247482] loader: geli-encryption zfs boot environments [regression]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247482 --- Comment #2 from Evilham --- Forgot to mention that 12-release is a Boot Environment that hasn't existed in months. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204521] [new driver] [request] Port rtsx from OpenBSD to FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521 --- Comment #260 from Henri Hennebert --- (In reply to Zeus Panchenko from comment #257) (In reply to gnikl from comment #253) I change rtsx to not use vendor settings. please test 415995a (last commit). -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 40572] vipw(8) prints silly message if $EDITOR fails
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=40572 Fernando Apesteguía changed: What|Removed |Added Resolution|--- |FIXED Status|In Progress |Closed Assignee|b...@freebsd.org|fern...@freebsd.org --- Comment #5 from Fernando Apesteguía --- It is, confirmed in 13-current r362494 Thanks -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 247482] loader: geli-encryption zfs boot environments [regression]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247482 --- Comment #3 from Toomas Soome --- (In reply to Evilham from comment #2) Hi! The problem is that you have had set the "zfs:zroot/ROOT/12-release:" with zfsbootcfg, and now the loader is able to read it out (is it UEFI boot?). But since you have GELI encryption set, we can not write (GELI writes are not yet implemented). So the fix in your case would be to use: zfsbootcfg "" This will wipe out the BE name from pad2 area and you will get normal boot again. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 225762] diff truncate function name with --show-function-line
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225762 --- Comment #2 from Zsolt Udvari --- $ man /usr/share/man/man1/diff.1.gz | grep -- -F -F RE --show-function-line=RE N number of lines = L-F+1 $ freebsd-version 11.3-RELEASE-p9 As I see the man page in FreeBSD 11.3 and 11.4 contains it: https://www.freebsd.org/cgi/man.cgi?query=diff&apropos=0&sektion=0&manpath=FreeBSD+11.3-RELEASE&arch=default&format=html But the 12.0 doens't: https://www.freebsd.org/cgi/man.cgi?query=diff&apropos=0&sektion=0&manpath=FreeBSD+12.0-RELEASE&arch=default&format=html -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 247482] loader: GELI writes are not yet implemented
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247482 Evilham changed: What|Removed |Added Summary|loader: geli-encryption zfs |loader: GELI writes are not |boot environments |yet implemented |[regression]| -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 247482] loader: geli-encryption zfs boot environments [regression]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247482 --- Comment #4 from Evilham --- (In reply to Toomas Soome from comment #3) Wow, thank you; that indeed solved my issue. Since you asked: I am using UEFI boot and as a curiosity: I don't recall ever using zfsbootcfg! Maybe I did a long time ago and forgot or maybe it was the installer, will check on a different machine when I get the chance. Should I leave this bug open as a mark for "GELI writes are not yet implemented"? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 247482] loader: GELI writes are not yet implemented
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247482 --- Comment #5 from Toomas Soome --- (In reply to Evilham from comment #4) Til lthis patch the UEFI loader was not reading the config created by zfsbootcfg, with BIOS version you would have seen it. Yes, at this time we still do miss GELI writes, it is in the queue. Yep, lets leave it open. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 247417] No way to make touchpad works under freebsd 12.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247417 --- Comment #12 from Mc James --- (In reply to Vladimir Kondratyev from comment #11) I would test this and report back. but I have another question. would this model of touchpad get support under this new regime? or FreeBSD purposefully phase such devices out. thanks -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 247417] No way to make touchpad works under freebsd 12.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247417 --- Comment #13 from Vladimir Kondratyev --- (In reply to Mc James from comment #12) > I would test this and report back. > but I have another question. would this model of touchpad > get support under this new regime? What do you mean by "support"? 11-RELEASE "mouse with tap detection" - like? That is what I am trying to do now. If something of what I proposed helps, I'll try to add quirk to kernel driver to enable tap support automatically. If not, we can dump PS/2 bytestream to find out "what is up?" If you mean full-blown absolute mode driver, than answer is "most probably no". I have to have a physical access to laptop to write and debug such a driver. Really things are worse as there are 9! different versions of ALPS PS/2 touchpad protocol and it is not clear which ones are major or minor. > or FreeBSD purposefully phase such devices out. Such devices are phased out by history rather than by FreeBSD. Their worst property is that they are not supported good enough by Windows. MS precision touchpad specs includes only USB and I2C devices, not PS/2, that is why new laptops do not contain PS/2 touchpads. That means that chances that someone who is motivated enough to write an absolute-mode driver for such a rare device will get a sample of it are relatively low. But, that does not mean that FreeBSD wants to let it rot. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 237271] Radeon video card no longer works on 12-STABLE (after r345105) / CURRENT (after r345932)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237271 Mark Linimon changed: What|Removed |Added CC||lini...@freebsd.org Assignee|b...@freebsd.org|lini...@freebsd.org --- Comment #20 from Mark Linimon --- This PR is over a year old now. Has the problem in it been fixed? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 212117] Excessive power consumption in VT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212117 Mark Linimon changed: What|Removed |Added Resolution|--- |FIXED Status|New |Closed Assignee|b...@freebsd.org|ema...@freebsd.org --- Comment #3 from Mark Linimon --- Believed fixed in r333669. ^Triage: assign to committer that resolved. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 247126] zgrep(1) does not handle -f FILE correctly
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247126 --- Comment #6 from Craig Leres --- Created attachment 215867 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=215867&action=edit Add two zgrep test cases Here's a patch that adds tests for the two failure cases. These tests pass under 11.3-RELEASE-p10 and fail under 13.0-CURRENT (r362459). The tests also pass on 13.0-CURRENT when zgrep has been patched. (Fixing the wrapper script was a lot easier than figuring out how to add the tests! But it's nice to understand how tests work.) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 247489] Change default partitioning on downloadable VM images
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247489 Bug ID: 247489 Summary: Change default partitioning on downloadable VM images Product: Base System Version: 12.1-RELEASE Hardware: Any URL: https://www.freebsd.org/doc/handbook/disks-growing.htm l OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: b...@freebsd.org Reporter: free...@filter.paco.to If you look at the online documentation for growing filesystems (https://www.freebsd.org/doc/handbook/disks-growing.html) you'll see that growing filesystems on disk is easy if your last partition on the disk is swap. You just delete the partition, grow the filesystem partition, and then recreate the swap partition. It also makes it easy to change the size of the swap partition. The raw disk image downloadable from freebsd.org (https://download.freebsd.org/ftp/releases/VM-IMAGES/12.1-RELEASE/amd64/Latest/FreeBSD-12.1-RELEASE-amd64.raw.xz) is built with: ada0p1: boot ada0p2: swap ada0p3: filesystem The primary use case (I think) for these VM images is to serve as a base image for a VM in a virtualization environment, which means that the vast majority of users who download them will resize the partitions. They presumably will want to resize and/or delete the swap partition as well. If ada0p2 was the filesystem and ada0p3 was swap, this would be trivial. As it is, the swap partition cannot easily be moved, resized, or deleted from a virtual disk created from this image. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 247472] /var/db/entropy not created with correct user/group
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247472 Kyle Evans changed: What|Removed |Added CC||kev...@freebsd.org --- Comment #1 from Kyle Evans --- Hi, Some questions to try and narrow the problem down: 1.) Are you installing from official install meia, or a custom build? For official media: 1a.) Which image in particular? For custom build: 1b.) What filesystem is the builder using for the objdir (default /usr/obj)? For either, to be clear: 2.) What filesystem is being installed? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
