On Sun, Apr 11, 2010 at 09:29:53PM -0400, Ted Unangst wrote:
> >
> > watch out - i already stomped on the options blurb. some comments inline
> > on the wireless part.
>
> Committed after merge. One choice where we apparently took different
> directions was pseudo-device vs interface. I left it
On Mon, Apr 12, 2010 at 06:54:31AM +0200, Bret S. Lambert wrote:
> On Sun, Apr 11, 2010 at 01:43:11PM -0700, patrick keshishian wrote:
> > On Sun, Apr 11, 2010 at 09:40:45PM +0200, Toni Mueller wrote:
> > > Hi Patrick,
> > >
> > > On Sun, 11.04.2010 at 11:58:54 -0700, patrick keshishian
> > > wr
On Sun, Apr 11, 2010 at 01:43:11PM -0700, patrick keshishian wrote:
> On Sun, Apr 11, 2010 at 09:40:45PM +0200, Toni Mueller wrote:
> > Hi Patrick,
> >
> > On Sun, 11.04.2010 at 11:58:54 -0700, patrick keshishian
> > wrote:
> > > inet_ntoa will return pointer to a static buffer. Each call
> > >
On Sun, Apr 11, 2010 at 2:00 PM, Jason McIntyre wrote:
> On Sun, Apr 11, 2010 at 01:36:35PM -0400, Ted Unangst wrote:
>> I took a few more editorial liberties here, but on the whole I don't think
>> we need to spell out "IEEE 802.11-based wireless network interfaces" every
>> time we're talking ab
On Sun, Apr 11, 2010 at 09:40:45PM +0200, Toni Mueller wrote:
> Hi Patrick,
>
> On Sun, 11.04.2010 at 11:58:54 -0700, patrick keshishian
> wrote:
> > inet_ntoa will return pointer to a static buffer. Each call
> > TO IT Will override thsi buffer with the new IP info.
>
> I already suspected som
Hi Patrick,
On Sun, 11.04.2010 at 11:58:54 -0700, patrick keshishian
wrote:
> inet_ntoa will return pointer to a static buffer. Each call
> TO IT Will override thsi buffer with the new IP info.
I already suspected something like this, but this behaviour is not
documented in the man page.
:(
I
On Sun, Apr 11, 2010 at 08:47:38PM +0200, Toni Mueller wrote:
> Hi,
>
> I've created a rough patch that should fix the immediate problem, but
> is certainly far from perfect (yet). Things to note:
>
> * No IPv6 support (I have no clue).
> * No useful error messages - I want to log data about the
Hi,
I've created a rough patch that should fix the immediate problem, but
is certainly far from perfect (yet). Things to note:
* No IPv6 support (I have no clue).
* No useful error messages - I want to log data about the offending
site, so admins can go after them.
* For some reason I don't yet
On Sun, Apr 11, 2010 at 01:36:35PM -0400, Ted Unangst wrote:
> I took a few more editorial liberties here, but on the whole I don't think
> we need to spell out "IEEE 802.11-based wireless network interfaces" every
> time we're talking about one.
>
watch out - i already stomped on the options b
The tarball that may be found at http://xenocara.org/intel-current.tgz
contains an update to the intel 2.9.1 driver (the last one that
supported userland modesetting) with a load of backports for bugfixes
and performance improvements from drivers up to 2.11.
In order to test this, you will need IN
I took a few more editorial liberties here, but on the whole I don't think
we need to spell out "IEEE 802.11-based wireless network interfaces" every
time we're talking about one.
Index: ifconfig.8
===
RCS file: /cvs/src/sbin/ifconf
On Sun, Apr 11, 2010 at 02:34:43AM -0400, Ted Unangst wrote:
> On Sat, 10 Apr 2010, Ted Unangst wrote:
>
> > Quite a bit of redundant text here, this makes it cleaner I think.
>
> jmc wants more changes, jmc gets more changes :)
>
if i'd known it was that easy!
i like this diff a lot. some
Hi.
Let's try that again, with inline patches and pointers to them
since they seemed to be stripped from the last mail:
http://www.habets.pp.se/synscan/files/ldpctl-impnull.patch
http://www.habets.pp.se/synscan/files/ldpd-impnull.patch
I played around a bit with ospfd and ldpd against real cisc
13 matches
Mail list logo
