On 22/01/14(Wed) 11:46, Martin Pieuchot wrote:
Network addresses added to the interface local list thought ifa_add()
are the link-local address and the IPv4/6 ones.
Since if_detach() now calls in_ifdetach(), there should be no address
left on the list apart from the link-layer one at this
Index: pthread_set_name_np.3
===
RCS file: /cvs/src/lib/libpthread/man/pthread_set_name_np.3,v
retrieving revision 1.5
diff -u -p -r1.5 pthread_set_name_np.3
--- pthread_set_name_np.3 5 Jun 2013 03:44:50 - 1.5
+++
On 06/03/14(Thu) 09:34, Martin Pieuchot wrote:
On 19/02/14(Wed) 12:53, Martin Pieuchot wrote:
Generally, when a NA is received we check if the receiving interface
has the target address advertised and if it's the case we warn about
duplicate addresses and bail.
But in the case of a
Hi tech,
is there a reason, why there is no ports.tar.gz in the latest snapshot folder?
fritjof
is there a reason, why there is no ports.tar.gz in the latest snapshot folder?
At present, it is not being built in the ftp area any more.
I'd like to ask. Does anyone find it useful? It is not in sync with the
packages beside it.
On Thu, Mar 6, 2014, at 08:56 AM, Theo de Raadt wrote:
is there a reason, why there is no ports.tar.gz in the latest snapshot
folder?
At present, it is not being built in the ftp area any more.
I'd like to ask. Does anyone find it useful? It is not in sync with the
packages beside
Quoting Theo de Raadt dera...@cvs.openbsd.org:
is there a reason, why there is no ports.tar.gz in the latest
snapshot folder?
At present, it is not being built in the ftp area any more.
I'd like to ask. Does anyone find it useful? It is not in sync with the
packages beside it.
Hi
On Mar 6, 2014, at 3:13 PM, Vijay Sankar vsan...@foretell.ca wrote:
Quoting Theo de Raadt dera...@cvs.openbsd.org:
is there a reason, why there is no ports.tar.gz in the latest snapshot
folder?
At present, it is not being built in the ftp area any more.
I'd like to ask. Does anyone
Quoting Theo de Raadt dera...@cvs.openbsd.org:
is there a reason, why there is no ports.tar.gz in the latest
snapshot folder?
At present, it is not being built in the ftp area any more.
I'd like to ask. Does anyone find it useful? It is not in sync with the
packages beside it.
On Thu, Mar 06, 2014 at 03:18:38PM +, Devin Ceartas wrote:
On Mar 6, 2014, at 3:13 PM, Vijay Sankar vsan...@foretell.ca wrote:
Quoting Theo de Raadt dera...@cvs.openbsd.org:
is there a reason, why there is no ports.tar.gz in the latest snapshot
folder?
At present, it is not
I'd like to ask. Does anyone find it useful? It is not in sync with the
packages beside it.
I thought the packages are being build from the ports tree or am I wrong?
Sigh.
So I can make a tar file available. At a particular moment in time.
But the package builts are not done in
Are all the ports in the packages in snapshots?
The best way to get source code from our project is not in tar files,
but using the repository-access methods described on the web site
and in the FAQ. Then it is easier to move your tree forward in time,
rather than downloading files this big,
On Mar 6, 2014, at 3:34 PM, Theo de Raadt dera...@cvs.openbsd.org wrote:
Are all the ports in the packages in snapshots?
The best way to get source code from our project is not in tar files,
but using the repository-access methods described on the web site
and in the FAQ. Then it is easier
I'd like to ask. Does anyone find it useful? It is not in sync with
the
packages beside it.
I thought the packages are being build from the ports tree or am I wrong?
Sigh.
So I can make a tar file available. At a particular moment in time.
But the package builts
On 2014/03/06 08:32, Theo de Raadt wrote:
I'd like to ask. Does anyone find it useful? It is not in sync with
the
packages beside it.
I thought the packages are being build from the ports tree or am I wrong?
Sigh.
So I can make a tar file available. At a particular
Personally I'd keep them for releases (which also gives people a base
to speed up updates to -current) but probably drop them for snapshots..
In the next few hours, the file will be there.
(Can one of you select yourself to help care watch this file, and
talk just to me about it? I'm
On Thu, Mar 06, 2014 at 03:18:38PM +, Devin Ceartas wrote:
Are all the ports in the packages in snapshots? I seem to remember needing to
build some of the things I use to test, but maybe that has changed.
There are a few ports not in snapshots, stuff that is not authorized for
ftp
On Thu, 6 Mar 2014, Theo de Raadt wrote:
I'd like to ask. Does anyone find it useful? It is not in sync with the
packages beside it.
I thought the packages are being build from the ports tree or am I wrong?
Sigh.
So I can make a tar file available. At a particular moment in time.
But
So read what I said again. They're not in sync.
But they are in sync for a release. Or the ports.tar.gz file won't be a
part of a release anymore?
Yes, they are in sync for a release. But the Subject says snapshot.
previously on this list Shawn K. Quinn contributed:
Makes very little difference to me.
I don't use the ports tree at all anymore. That said, I would trust the
empirical evidence (FTP logs) more than any on-list answers you might
get.
Is there a pkg* tools equivalent to print-run-depends?
On Wed, Mar 05, 2014 at 08:38:43PM -0800, patrick keshishian wrote:
Index: calendar.birthday
===
RCS file: /cvs/obsd/src/usr.bin/calendar/calendars/calendar.birthday,v
retrieving revision 1.57
diff -u -p -u -p -r1.57
On Thu, Mar 06, 2014 at 09:02:22AM +0100, Gabriel Linder wrote:
Index: pthread_set_name_np.3
===
RCS file: /cvs/src/lib/libpthread/man/pthread_set_name_np.3,v
retrieving revision 1.5
diff -u -p -r1.5 pthread_set_name_np.3
---
Hi,
back in November 2013, following an idea by guenther@,
i cooked up another optimization for seekdir(3),
then failed to send out the patch. So here it is.
Philip Guenther wrote on Tue, Nov 05, 2013 at 07:57:43PM -0800:
On Wed, 6 Nov 2013, Ingo Schwarze wrote:
* Worst case:
opendir;
Hi,
having fixed the accent issues with mandoc -Tutf8, i have checked
the base system for build system issues with switching the default,
the resulting fixes are included in the following patch.
Anybody wants to check with ports before commit, such that we can do
any necessary cleanup
On Thu, Mar 06, 2014 at 21:36, Ingo Schwarze wrote:
Hi,
having fixed the accent issues with mandoc -Tutf8, i have checked
the base system for build system issues with switching the default,
the resulting fixes are included in the following patch.
Anybody wants to check with ports before
Hi Ted,
Ted Unangst wrote on Thu, Mar 06, 2014 at 04:46:50PM -0500:
Seems reasonable to me.
I went the man.conf route because it's easier for users to revert,
Oh, if somebody really insists in setting LC_CTYPE but wants to
see manuals in US-ASCII anyway (huh?), adding -Tascii to mandoc
in
pf_check_congestion() simply checks if ifq-ifq_congestion is non-zero,
and returns 1 or 0 accordingly. It is only called by pf_test_rule().
Since what pf_check_congestion() does is very trivial and pf_test_rule()
is its only user, would it make sense to remove it and let
pf_test_rule() check
27 matches
Mail list logo
