On Sun, Mar 31, 2013 at 1:37 AM, Glen Barber wrote:
> freebsd-net@ might have been a better choice, but...
>
> On Sun, Mar 31, 2013 at 01:20:17AM -0400, Aryeh Friedman wrote:
> > I have a host that for ISP reasons must have a ipv6 addr as well as the
> > ipv4 but the ISP does not offer external i
freebsd-net@ might have been a better choice, but...
On Sun, Mar 31, 2013 at 01:20:17AM -0400, Aryeh Friedman wrote:
> I have a host that for ISP reasons must have a ipv6 addr as well as the
> ipv4 but the ISP does not offer external ipv6 routing but all the commanes
> (ssh, ftp, etc.) default to
I have a host that for ISP reasons must have a ipv6 addr as well as the
ipv4 but the ISP does not offer external ipv6 routing but all the commanes
(ssh, ftp, etc.) default to ipv6 and need special options to use 4 is there
anyway to force them to always use 4?
__
Despite the man page correctly describing the return value for
extattr_set_*, I thought recently that they returned 0/-1 for
success/failure, not the number of bytes written, like write(2). This is
because extattr_set_* is declared as returning an int, not an ssize_t.
Both extattr_get and extattr
On Sat, 30 Mar 2013 09:14:34 PDT John-Mark Gurney wrote:
>
> As someone else pointed out in this thread, if a userland program
> depends upon this behavior, it has a race condition in it...
>
> Thread 1 Thread 2Thread 3
>
On Mar 30, 2013, at 09:10, Andriy Gapon wrote:
> It seems that, unlike gcc, for clang -fno-omit-frame-pointer does not imply
> -mno-omit-leaf-frame-pointer. This is probably a bug.
Yes, this is indeed the case. There is even a rather old unresolved PR
for it in LLVM's Bugzilla:
http://llvm.org
> As someone else pointed out in this thread, if a userland program
> depends upon this behavior, it has a race condition in it...
>
> Thread 1 Thread 2Thread 3
> enters routine to read
> enters routine to close
> calls clo
Bakul Shah wrote this message on Fri, Mar 29, 2013 at 16:54 -0700:
> On Fri, 29 Mar 2013 14:30:59 PDT Carl Shapiro wrote:
> >
> > In other operating systems, such as Solaris and MacOS X, closing the
> > descriptor causes blocked system calls to return with an error.
>
> What happens if you selec
On 2013-03-28, Andriy Gapon wrote:
> > Would like to ask for opinions on this topic...
> > Please read this PR for context:
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/122838
> > Especially Jaakko's insightful description of the problem.
>
> So I would like to commit the following patch so
It seems that, unlike gcc, for clang -fno-omit-frame-pointer does not imply
-mno-omit-leaf-frame-pointer. This is probably a bug.
Meanwhile I would like to propose the following amd64-specific patch. Perhaps
the same type of change would be useful for powerpc as well.
I would like this change
My understanding of this whole subject is limited, but bear with me... in
my quest to get a "cool looking console for my desktop... I found this
https://wiki.freebsd.org/Newcons
does anyone know if someone is still actively working on the NewCons
project? or is it already committed to HEAD and i
11 matches
Mail list logo