Sorry for replying so late
On 08/02/2012 06:58, Benjamin Kaduk wrote:
> Perhaps freebsd-standa...@freebsd.org would be
> appropriate for this? Though perhaps -hackers would reach a larger
> audience.
I have dropped an email today in freebsd-standa...@freebsd.org:
http://lists.freebsd.org/piperma
On Sun, 5 Feb 2012, Nicolas Bourdaud wrote:
On 04/02/2012 21:07, Robert Millan wrote:
Can you reproduce this with upstream kernel? (apt-get install
kfreebsd-downloader)
Yes it is reproducible with upstream kernel
If it affects upstream, for this kind of reports it's much better to
report th
On 04/02/2012 21:07, Robert Millan wrote:
> Can you reproduce this with upstream kernel? (apt-get install
> kfreebsd-downloader)
Yes it is reproducible with upstream kernel
> If it affects upstream, for this kind of reports it's much better to
> report them to FreeBSD PR database instead:
>
> ht
forwarded 658639 http://www.freebsd.org/cgi/query-pr.cgi?pr=164793
thanks
2012/2/5, Nicolas Bourdaud :
> Bug report opened upstream:
> http://www.freebsd.org/cgi/query-pr.cgi?pr=164793
Thanks!
--
Robert Millan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subj
Hi Nicolas,
El 4 de febrer de 2012 20:49, Nicolas Bourdaud
ha escrit:
> When a write() cannot transfer as many bytes as requested (because of a file
> limit), it fails instead of transferring as many bytes as there is room to
> write.
>
> This is a violation of the POSIX standard:
> http://pubs.o
Source: kfreebsd-9
Severity: important
Tags: upstream
When a write() cannot transfer as many bytes as requested (because of a file
limit), it fails instead of transferring as many bytes as there is room to
write.
This is a violation of the POSIX standard:
http://pubs.opengroup.org/onlinepubs/0079
6 matches
Mail list logo
