On Thu, Mar 5, 2015 at 2:02 PM, sven falempin wrote:
...
> AFAI Understand
>
> ./pfe.c: rt->rt_conf.flags &= ~(F_DOWN);
> is completly useless
Hmm? Maybe I'm misunderstanding your, but that's the normal syntax
for clearing bits (F_DOWN in this case) in a flag word: you mask the
flag word against
On Thu, Mar 5, 2015 at 5:02 PM, sven falempin wrote:
> Intro, i looked at the relayd router code, because i'd like to change
> some route given some conditions. Especially i'd like to change some
> rules when the route is added , and flush this anchor when route is
> removed (or flush read when ch
>On Fri, Mar 06, 2015 at 12:22:09AM +0200, Alexey Suslikov wrote:
>> My point was, development should start around something widespread
>> so people can test easily. This maybe urtwn, iwn and iwm, for instance.
>
>Yes, as far as 11n is concerned, starting with a focus on a single
>popular device dr
>T. Jameson Little gmail.com> writes:
>
>> Since USB 2.0 has a maximum throughput of 480Mbit/s, anything higher
>> than 300Mbit/s is not particularly important, and many consumer devices
>> only support 150Mbit/s anyway. 72Mbit/s is completely fine for an
>> initial implementation.
>
>I slightly d
>My point was, development should start around something widespread
>so people can test easily. This maybe urtwn, iwn and iwm, for instance.
You deleted Stefan's last paragraph in his previous mail --
SPECIFICALLY -- because it refutes what you state.
He (and others) will work on what they want t
On Fri, Mar 06, 2015 at 12:22:09AM +0200, Alexey Suslikov wrote:
> My point was, development should start around something widespread
> so people can test easily. This maybe urtwn, iwn and iwm, for instance.
Yes, as far as 11n is concerned, starting with a focus on a single
popular device driver w
T. Jameson Little gmail.com> writes:
> Since USB 2.0 has a maximum throughput of 480Mbit/s, anything higher
> than 300Mbit/s is not particularly important, and many consumer devices
> only support 150Mbit/s anyway. 72Mbit/s is completely fine for an
> initial implementation.
I slightly disagree
On Thu, Mar 5, 2015 at 11:45 PM, Stefan Sperling wrote:
> On Thu, Mar 05, 2015 at 09:22:51PM +, Alexey Suslikov wrote:
>> T. Jameson Little gmail.com> writes:
>> > Well, I'm much more capable of fixing existing drivers to make it work
>> > well than building something from scratch, and I imag
Intro, i looked at the relayd router code, because i'd like to change
some route given some conditions. Especially i'd like to change some
rules when the route is added , and flush this anchor when route is
removed (or flush read when changed).
I think about copying the ifstated mechanism to provi
On Thu, Mar 05, 2015 at 09:22:51PM +, Alexey Suslikov wrote:
> T. Jameson Little gmail.com> writes:
> > Well, I'm much more capable of fixing existing drivers to make it work
> > well than building something from scratch, and I imagine the same is
> > true for many developers, because you work
T. Jameson Little gmail.com> writes:
> Well, I'm much more capable of fixing existing drivers to make it work
> well than building something from scratch, and I imagine the same is
> true for many developers, because you work on whatever affects you.
IMO, "fixing existing drivers" should take pop
On Thu, Mar 05, 2015 at 11:05:26AM -0700, T. Jameson Little wrote:
> I honestly just want 5GHz to work at minimum speeds in AP mode on a usb
> wireless dongle. I run into interference on 2.4GHz because it's far too
> common. I imagine that once this works, adding additional modulation
> and coding
On Mar 3, 2015, at 8:44 AM, David Higgs wrote:
> With much help from mpi@, I have made a first big step towards improving
> upd(4). I’m not sure when tree lock ends, but I’m still happy to accept
> feedback if right now isn’t the time to commit. There’s plenty more to do,
> but I’d like to
On Thu, Mar 5, 2015 at 1:05 PM, T. Jameson Little wrote:
> On Wed, Mar 04, 2015 at 09:28:42AM +0100, Stefan Sperling wrote:
>> The actual amount of work depends on when you consider support complete.
>> 11n has such a large feature set and optional parts that you can't
>> simply say "this is an 11
On Wed, Mar 04, 2015 at 09:28:42AM +0100, Stefan Sperling wrote:
> The actual amount of work depends on when you consider support complete.
> 11n has such a large feature set and optional parts that you can't
> simply say "this is an 11n device" to explain what your device can do.
>
> Are you done
On 2015/03/05 12:41, Ted Unangst wrote:
> Boudewijn Dijkstra wrote:
> > Op Wed, 04 Mar 2015 23:12:07 +0100 schreef Ted Unangst
> > :
> > > Freetype (http://www.freetype.org/) 2.5.5 was released a little while ago,
> > > fixing some security vulnerabilities. Actually as I understand it, 2.5.4
> > >
Boudewijn Dijkstra wrote:
> Op Wed, 04 Mar 2015 23:12:07 +0100 schreef Ted Unangst :
> > Freetype (http://www.freetype.org/) 2.5.5 was released a little while ago,
> > fixing some security vulnerabilities. Actually as I understand it, 2.5.4
> > fixed the vulns, then 2.5.5 fixed the fix.
> >
> > Ope
Hi,
The "openssl certhash" comparision function hashinfo_compare uses
subtraction to compare two "long" hash values, but the result is
stored into an integer variable, resulting in an inconstent ordering.
This makes it happen that two certificates with same hash get same
index (because they do no
Raf Czlonka said:
> Well, from a snapshot point of view, there is an error - '5.7' directory
> doesn't exist and from what you are saying, this snapshot probably
> should not have been published.
You will have a chance to do it "right" (in your view) once you'll be in
charge of OpenBSD's release m
On 2015/03/05 11:41, Otto Moerbeek wrote:
> On Thu, Mar 05, 2015 at 10:40:06AM +, Raf Czlonka wrote:
>
> > On Thu, Mar 05, 2015 at 10:06:43AM GMT, Otto Moerbeek wrote:
> >
> > > That's not an error, we are in the timeframe that releases are built.
> > > That means that the snaps are build usi
On Thu, Mar 05, 2015 at 10:40:06AM +, Raf Czlonka wrote:
> On Thu, Mar 05, 2015 at 10:06:43AM GMT, Otto Moerbeek wrote:
>
> > That's not an error, we are in the timeframe that releases are built.
> > That means that the snaps are build using release settings. After the
> > release has been cu
On Thu, Mar 05, 2015 at 10:06:43AM GMT, Otto Moerbeek wrote:
> That's not an error, we are in the timeframe that releases are built.
> That means that the snaps are build using release settings. After the
> release has been cut, snaps will go back to be "normal".
Well, from a snapshot point of v
Op Wed, 04 Mar 2015 23:12:07 +0100 schreef Ted Unangst :
Freetype (http://www.freetype.org/) 2.5.5 was released a little while ago,
fixing some security vulnerabilities. Actually as I understand it, 2.5.4
fixed the vulns, then 2.5.5 fixed the fix.
OpenBSD 5.7 will ship with 2.5.5; 5.6 shipped wi
On 2015/03/05 10:00, Raf Czlonka wrote:
> Hi all,
>
> Just a heads up as I'm sure you had already spotted it.
>
> Newest (4th March 2015) snapshot's installer (bsd.rd) defaults to:
>
> pub/OpenBSD/5.7/$(machine)
>
> instead of:
>
> pub/OpenBSD/snapshots/$(machine)
>
> when asking for
On Thu, Mar 05, 2015 at 10:00:00AM +, Raf Czlonka wrote:
> Hi all,
>
> Just a heads up as I'm sure you had already spotted it.
>
> Newest (4th March 2015) snapshot's installer (bsd.rd) defaults to:
>
> pub/OpenBSD/5.7/$(machine)
>
> instead of:
>
> pub/OpenBSD/snapshots/$(machine
Hi all,
Just a heads up as I'm sure you had already spotted it.
Newest (4th March 2015) snapshot's installer (bsd.rd) defaults to:
pub/OpenBSD/5.7/$(machine)
instead of:
pub/OpenBSD/snapshots/$(machine)
when asking for the path to the sets on the http mirror.
Two months, too early :^
26 matches
Mail list logo
