https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278232
--- Comment #15 from Gleb Smirnoff ---
The changes I and Mark did were not merged to stable/13. So looks like this is
some smaller change, that also was merged to stable/13, too.
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278232
Bjoern A. Zeeb changed:
What|Removed |Added
CC||gleb...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278232
--- Comment #13 from Jamie Gritton ---
Sorry, it's been a while since I wrote that man page, and it's unclear enough
that I didn't read it right myself. ip[46].saddrsel is one of the few options
that's on by default, so only the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278232
--- Comment #12 from Dirk Meyer ---
Sorry this text is still unclear to me.
I would expect "ip4.saddrsel" to allow source selection
and "ip4.nosaddrsel" will disable it.
but "ip4.nosaddrsel" is not documented in "man jail"?
I confirmed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278232
--- Comment #11 from Jamie Gritton ---
This appears to be a feature, working exactly what as it says it does. From
jail(8):
ip4.saddrsel
A boolean option to change the formerly mentioned behaviour and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278232
--- Comment #10 from Dirk Meyer ---
I see here:
ping with passing the correct source ip works.
ping without source ip fails, the first IP of the jail is always used.
Sending UDP fails, the first IP of the jail is always used.
(tested
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278232
Bjoern A. Zeeb changed:
What|Removed |Added
CC||b...@freebsd.org
--- Comment #9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278232
Jamie Gritton changed:
What|Removed |Added
Status|New |Open
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278232
--- Comment #8 from Jamie Gritton ---
> Hi Jamie, I'm not quite understand that statement. I think those
> sysctl knobs can be retired, but why shall we retrieve the formats
> of parameters? Isn't them for developers only?
For developers
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278232
Zhenlei Huang changed:
What|Removed |Added
CC||ja...@freebsd.org
--- Comment #7
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278232
--- Comment #6 from Zhenlei Huang ---
(In reply to Dirk Meyer from comment #4)
> ip4.addr
> ip4.saddrsel
Those options are per jail. That is to say, they should be applied either in
the command line or in the jail.conf .
> There is also
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278232
--- Comment #5 from Michael Osipov ---
So if 13.2 worked and 13.3 does not then the issue is somewhere in between..
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278232
--- Comment #4 from Dirk Meyer ---
Same failure on FreeBSD-13.3
# freebsd-version -kru
13.3-RELEASE-p1
13.3-RELEASE-p1
13.3-RELEASE-p1
I would like to know what the expected behavior of ip4.saddrsel in this case
is.
1)
The selection
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278232
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|j...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278195
--- Comment #3 from Zhenlei Huang ---
Another truss(1) that show what happens when the `--close-fds` option is
supplied.
```
# truss -f /tmp/daemon -fSl daemon echo OK
..
955: connect(3,{ AF_UNIX "/var/run/logpriv" },106) = 0 (0x0)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278195
--- Comment #2 from Zhenlei Huang ---
> The parent does return 0. The child will complain with "Undefined symbol".
truss(1) shows that clearly.
```
# truss -f /tmp/daemon -l daemon echo OK
..
1543: sigaction(SIGHUP,{ SIG_IGN 0x0 ss_t },{
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278195
Zhenlei Huang changed:
What|Removed |Added
CC||z...@freebsd.org
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278195
Mark Linimon changed:
What|Removed |Added
Keywords||regression
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277923
--- Comment #3 from Nico Sonack ---
Thank you!
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277923
Jamie Gritton changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277923
Kyle Evans changed:
What|Removed |Added
Assignee|j...@freebsd.org|ja...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277923
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|j...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274263
--- Comment #4 from Andrew ---
I just noticed that the same issue is present in releng/14.0... it looks like
pretty annoying to us, since we use jails everywhere!
Someone can tell me how can I help to analyze the problem? Since it
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277210
--- Comment #9 from johannes.ku...@gmail.com ---
(In reply to Frank Behrens from comment #8)
> In the script, called from the service
> start script is a
> d=`pwd`
> ..
> cd $d
Can you please provide the source? Would be great to have it
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277210
Frank Behrens changed:
What|Removed |Added
CC||fr...@harz.behrens.de
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277210
--- Comment #7 from Michael Osipov ---
>From jail(8):
exec.clean
Run commands in a clean environment. The environment is dis-
carded except for HOME, SHELL, TERM and USER. HOME and SHELL
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277210
--- Comment #6 from johannes.ku...@gmail.com ---
(In reply to Jamie Gritton from comment #5)
> While it does make sense to root from the jail's root under exec.clean, it
> unfortunately clashes with a decade of current practice.
I get
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277210
Jamie Gritton changed:
What|Removed |Added
CC||ja...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277210
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|j...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276809
--- Comment #6 from commit-h...@freebsd.org ---
A commit in branch stable/14 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=5e21d7cd31194faf8c2bdda2bc60adf34eaa405a
commit 5e21d7cd31194faf8c2bdda2bc60adf34eaa405a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240106
Mark Linimon changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276809
--- Comment #5 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=dfabf3efaa795e657f3858b7e2d0b11f8a51ecb5
commit dfabf3efaa795e657f3858b7e2d0b11f8a51ecb5
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276809
--- Comment #4 from Mark Johnston ---
https://reviews.freebsd.org/D43732 makes jailparam_export() fail cleanly if the
value hasn't already been exported.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276809
Mark Johnston changed:
What|Removed |Added
Resolution|--- |Not A Bug
Status|Open
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276809
--- Comment #2 from Fabiano Sidler ---
Ah, of course I'm an idiot! How can I expect any param to have a value in such
a "list all possible param NAMES" call?
The C program works now as expected, but I still get the SEGFAULT in Python
after
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276809
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272092
Olivier Certner changed:
What|Removed |Added
Assignee|j...@freebsd.org|o...@freebsd.org
--- Comment #5
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274263
--- Comment #3 from Markus Wild ---
(In reply to Andrew from comment #2)
I've now installed a user crontab entry like the following on all
affected hosts (host, not jail):
# weird bug leads to EPERM for access to /.zfs/snapshot/* within
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274263
Andrew changed:
What|Removed |Added
CC||andrew.hot...@hotmail.com
--- Comment #2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272092
--- Comment #4 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=9a4a7e5fb6e901e81c8e64a988358ad4b59464a5
commit 9a4a7e5fb6e901e81c8e64a988358ad4b59464a5
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275306
Mark Linimon changed:
What|Removed |Added
Assignee|j...@freebsd.org|f...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275306
--- Comment #5 from Lexi ---
i updated the title to better reflect the issue, since this doesn't seem to be
directly related to jails; jails are just the first thing on this system to do
I/O on an encrypted filesystem after boot.
i assume
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275306
Lexi changed:
What|Removed |Added
Summary|14.0-RELEASE: starting jail |14.0-RELEASE: ossl(4)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275306
Daniel Austin changed:
What|Removed |Added
CC||freebsd-po...@dan.me.uk
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271308
--- Comment #6 from Konrad ---
The problem mainly bothersome during CARP configuration:
R1 nad R2 see their routes through OSPF
R1:
#ifconfig vlan5 100.64.0.253/24
#ifconfig vlan5 100.64.0.254/32 vhid 1 advskew 50 alias
#
R2:
#ifconfig
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275306
--- Comment #3 from Lexi ---
quick update: "zpool scrub zroot" seems to have fixed the error on the zroot
pool. i'm running a scrub on the data pool to see if it fixes the errors there
as well, but that will likely take a couple of days
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275306
--- Comment #2 from Lexi ---
removing "ossl" seems to have fixed the panic.
however, it seems like this has caused permanent damage to several ZFS
filesystems / volumes:
root@hemlock:~ # zpool status -v
pool: data
state: ONLINE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275306
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275306
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|j...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275228
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|j...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274568
Antranig Vartanian changed:
What|Removed |Added
CC||antran...@freebsd.am
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274568
Mark Johnston changed:
What|Removed |Added
CC||ja...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274568
cr...@rlwinm.de changed:
What|Removed |Added
CC||cr...@rlwinm.de
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274568
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|j...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272092
Olivier Certner changed:
What|Removed |Added
Resolution|--- |FIXED
Status|Open
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272092
--- Comment #3 from commit-h...@freebsd.org ---
A commit in branch releng/14.0 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=7e21c691f295b3babc8c57c0aeafa19faf1371b6
commit 7e21c691f295b3babc8c57c0aeafa19faf1371b6
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272092
--- Comment #2 from commit-h...@freebsd.org ---
A commit in branch stable/14 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=e1153205a719c6cb792cb2213a3737ee6b53d59c
commit e1153205a719c6cb792cb2213a3737ee6b53d59c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274263
--- Comment #1 from Markus Wild ---
Update:
i just encountered the same bug on a different host system,
that does not yet use custom web-specific mounts in the jail.
So I guess we can rule out nullfs or zfs submounts from within
the jail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274263
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|j...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272092
--- Comment #1 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=5817169bc4a06a35aa5ef7f5ed18f6cb35037e18
commit 5817169bc4a06a35aa5ef7f5ed18f6cb35037e18
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271308
--- Comment #5 from Konrad ---
simpler reproduction:
FreeBSD 13.1-STABLE #24 stable/13-56caa9e82b-dirty: Wed Sep 7 20:17:15 CEST
2022:
without options NETLINK, works corretly:
root@:~ # ifconfig bge1 10.20.20.254/24
root@:~ # route
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259149
--- Comment #9 from Mina Galić ---
(In reply to Thomas Hurst from comment #8)
you wanna prepare a patch?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259149
--- Comment #8 from Thomas Hurst ---
A small note in mac_portacl(4) that the reservedlow/high oids are per-vnet - in
contrast with the global mac_portacl policy - would probably have made all the
difference here.
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259149
Zhenlei Huang changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259149
--- Comment #6 from Zhenlei Huang ---
(In reply to uros from comment #1)
> Anyone have any idea what could be checked here?
For vnet jails, adjust vnet sysctl `net.inet.ip.portrange.reservedhigh`
appropriately.
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259149
--- Comment #5 from Zhenlei Huang ---
(In reply to Zhenlei Huang from comment #4)
> Tree indeed.
Sorry for the typo :( It was `True indeed`.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259149
Zhenlei Huang changed:
What|Removed |Added
CC||z...@freebsd.org
--- Comment #4
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259149
Thomas Hurst changed:
What|Removed |Added
CC||t...@hur.st
--- Comment #3 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259149
Mina Galić changed:
What|Removed |Added
Status|New |Open
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271069
Jamie Gritton changed:
What|Removed |Added
CC||ja...@freebsd.org
--- Comment #9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271069
Dan Langille changed:
What|Removed |Added
CC||d...@freebsd.org
--- Comment #8
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271069
Siva Mahadevan changed:
What|Removed |Added
Attachment #244032|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272958
--- Comment #8 from Alex Seitsinger ---
(In reply to Antranig Vartanian from comment #1)
ping
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271069
Mina Galić changed:
What|Removed |Added
Assignee|b...@freebsd.org|j...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272958
--- Comment #7 from Alex Seitsinger ---
1. Start a jail
2. Using exec.created/exec.poststart, successfully move the epair interface
into the jail via ifconfig vnet.
3. Run another script via exec.created/exec.poststart, but have it fail,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272958
--- Comment #6 from Alex Seitsinger ---
Created attachment 243906
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=243906=edit
create-jail-epair.sh
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272958
--- Comment #5 from Alex Seitsinger ---
Created attachment 243905
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=243905=edit
bridge-jail-epair.sh
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272958
--- Comment #4 from Alex Seitsinger ---
Created attachment 243904
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=243904=edit
create-bridge.sh
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272958
--- Comment #3 from Alex Seitsinger ---
Created attachment 243903
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=243903=edit
logs0/scripts/created
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272958
--- Comment #2 from Alex Seitsinger ---
Created attachment 243902
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=243902=edit
/etc/jail.conf
bastille jail
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272958
Antranig Vartanian changed:
What|Removed |Added
CC||antran...@freebsd.am
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272958
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|j...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271308
--- Comment #4 from Janak Trivedi ---
Any help/inputs around it would be much appreciated.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272706
--- Comment #6 from Elizabeth Myers ---
(In reply to Andrew "RhodiumToad" Gierth from comment #5)
To reply to previous comments:
Yes, this is *within* the jail, not *outside* the jail. As far as I know, no
other procstat subcommand does
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272706
--- Comment #5 from Andrew "RhodiumToad" Gierth
---
(In reply to Andrew "RhodiumToad" Gierth from comment #4)
I've confirmed my analysis this far: vn_fullpath is being called with vp
pointing to a physical filesystem vnode (i.e. not the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272706
--- Comment #4 from Andrew "RhodiumToad" Gierth
---
(In reply to Andrew "RhodiumToad" Gierth from comment #3)
I think I figured this one out, it happens when nullmounts are involved, even
if the jail's root directory is not itself the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272706
Andrew "RhodiumToad" Gierth changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272706
--- Comment #2 from Elizabeth Myers ---
(In reply to crest from comment #1)
It was originally 1. I tested with multiple values.
0, 1, or 2 has no effect.
The jail doesn't start above 2, which makes sense as I believe it can't mount
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272706
cr...@rlwinm.de changed:
What|Removed |Added
CC||cr...@rlwinm.de
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272706
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|j...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271308
Graham Perrin changed:
What|Removed |Added
Severity|Affects Only Me |Affects Some People
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272092
Olivier Certner changed:
What|Removed |Added
See Also||https://reviews.freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272092
Mina Galić changed:
What|Removed |Added
Assignee|b...@freebsd.org|j...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272092
Mina Galić changed:
What|Removed |Added
CC||free...@igalic.co,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271308
Alexander V. Chernikov changed:
What|Removed |Added
Assignee|j...@freebsd.org|melif...@freebsd.org
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251624
Alexander V. Chernikov changed:
What|Removed |Added
Summary|[jls] [ifconfig] is unable |[jls] is unable to list
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271308
--- Comment #1 from Konrad ---
for clarification
I move vlans from host to jail (vnet)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271308
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|j...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254210
--- Comment #7 from Christos Chatzaras ---
FreeBSD 13.2:
The same thing happens when I use a program to optimise images (the images size
shrinks but ZFS shows more usage than before). I have to restart jails to get
the correct usage.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206012
Jamie Gritton changed:
What|Removed |Added
Assignee|j...@freebsd.org|ja...@freebsd.org
--- Comment #7
1 - 100 of 523 matches
Mail list logo
