Sorry.
That was supposed to go to the list.
-- Forwarded message --
From: David Crosswell david.crosswe...@gmail.com
Date: 18 May 2011 23:40
Subject: Re: Nics.
To: Justin Sherrill jus...@shiningsilence.com
On 18 May 2011 12:47, Justin Sherrill jus...@shiningsilence.com wrote
On Tue, May 17, 2011 at 12:08 AM, David Crosswell
david.crosswe...@gmail.com wrote:
Has anybody got any advice on what nics work best with Dragonfly, other than
the ones on-site?
I've had good luck with Intel chipsets, like those supported by the
fxp or em drivers.
If you want a list
Hello,
I've checked out the site and handbook, but I thought I would ask here also
in case of recent revelations.
Has anybody got any advice on what nics work best with Dragonfly, other than
the ones on-site?
Thanks for any time and trouble.
Regards,
David Crosswell.
--
In a world without walls
Hello.
Sepherosa Ziehau wrote:
Hi all,
I plan to drop
Following NIC drivers' ISA part:
an, ar, cs, ed, ep, ex, fe, sn
How is to tell that I still sometimes use ed NICs (RTL8029)
:(
Is leaving this drivers would couse many problems?
Following NIC drivers' EISA part:
ep, vx
Following NIC
On Tue, Jan 6, 2009 at 7:12 PM, Eugene dfu...@medcom.com.ua wrote:
Hello.
Sepherosa Ziehau wrote:
Hi all,
I plan to drop
Following NIC drivers' ISA part:
an, ar, cs, ed, ep, ex, fe, sn
How is to tell that I still sometimes use ed NICs (RTL8029)
:(
Is leaving this drivers would couse
On Sun, Jan 4, 2009 at 2:03 AM, Matthew Dillon
dil...@apollo.backplane.com wrote:
:
:Sascha Wildner schrieb:
: Hey cool idea. Generally my plan was to wait until after 2.2 and then
: drop support for all ISA drivers that need a physical ISA card and all
: EISA drivers. Making 2.0 the last
Hi all,
I plan to drop
Following NIC drivers' ISA part:
an, ar, cs, ed, ep, ex, fe, sn
Following NIC drivers' EISA part:
ep, vx
Following NIC drivers will be complete dropped (ISA only):
el, ie, le, rdp, wl
If no objection comes within next three days, I will start the dropping.
Best
Sepherosa Ziehau schrieb:
Hi all,
I plan to drop
Following NIC drivers' ISA part:
an, ar, cs, ed, ep, ex, fe, sn
Following NIC drivers' EISA part:
ep, vx
Following NIC drivers will be complete dropped (ISA only):
el, ie, le, rdp, wl
If no objection comes within next three days, I will start
Hi,
* Sepherosa Ziehau wrote:
Hi all,
I plan to drop
Following NIC drivers' ISA part:
an, ar, cs, ed, ep, ex, fe, sn
Not sure about ed(4). This driver is often used in virtualization
software. At least it was used in qemu some time ago, but I'm not sure
if its still used today. Can
Hi there,
Im trying to run an authoritative dns server on 1 NIC and dns
cache/recursive resolver on another NIC. Therefore 2 IPs on the same net
and connected to the same switch. Therefore theres a problem. What
options do i have in regards to resolving the issue without putting them
on
] On Behalf Of Petr Janda
Sent: Thursday, March 15, 2007 11:10 AM
To: users@crater.dragonflybsd.org
Subject: 2 NICs and 1 network
Hi there,
Im trying to run an authoritative dns server on 1 NIC and dns
cache/recursive resolver on another NIC. Therefore 2 IPs on the same net
and connected
Mire, John wrote:
Why don't you just use 2 different views under bind this is trivial, and should
do exactly what you want with one ip address.
Using Bind is out of question. The zones are stored in LDAP.
Petr
On Thu, March 15, 2007 7:58 pm, Petr Janda wrote:
Using Bind is out of question. The zones are stored in LDAP.
There's a number of free LDAP and DNS products out there; I was looking at
them as part of a work project.
http://ldapdns.sourceforge.net/
http://nimh.org/code/ldapdns/
Justin C. Sherrill wrote:
On Thu, March 15, 2007 7:58 pm, Petr Janda wrote:
Using Bind is out of question. The zones are stored in LDAP.
There's a number of free LDAP and DNS products out there; I was looking at
them as part of a work project.
http://ldapdns.sourceforge.net/
On Thu, March 15, 2007 9:14 pm, Petr Janda wrote:
Im using PowerDN (authoritative)S and PowerDNS-Recursor (nscache). They
need to run sepately. Have you used the ldap module for bind? Besides
last release being 2 years ago, i heard that its utterly useless too.
(you gotta keep the zone files
Matt Dillon wrote:
:I installed DFly 1.4.4 today and it proply panic'd with a problem in
:tulip_rx_intr(), as described in this mail thread:
:http://leaf.dragonflybsd.org/mailarchive/bugs/2006-02/msg00010.html
Try burning a recent build of HEAD. There's a good chance that the
particular
Matt Emmerton wrote:
I installed DFly 1.4.4 today and it proply panic'd with a problem in
tulip_rx_intr(), as described in this mail thread:
http://leaf.dragonflybsd.org/mailarchive/bugs/2006-02/msg00010.html
I was dismayed to find that the DFly ISOs don't include sources, so I can't
patch this
I installed DFly 1.4.4 today and it proply panic'd with a problem in
tulip_rx_intr(), as described in this mail thread:
http://leaf.dragonflybsd.org/mailarchive/bugs/2006-02/msg00010.html
I was dismayed to find that the DFly ISOs don't include sources, so I can't
patch this system and get it on
:I installed DFly 1.4.4 today and it proply panic'd with a problem in
:tulip_rx_intr(), as described in this mail thread:
:http://leaf.dragonflybsd.org/mailarchive/bugs/2006-02/msg00010.html
:
:I was dismayed to find that the DFly ISOs don't include sources, so I can't
:patch this system and get
19 matches
Mail list logo