Hi

Juergen Northe wrote:
> Dear Martin,
> I do not complain at all about a slow or not existing process of providing
> recent drivers.
> As you can read in my postings ago, I tried to demonstrate that a lot of the
> postings in the forum is
> always about the same thing: people are looking for drivers of recent
> hardware - most NIC drivers.
> 
> Since the list of network cards is unmanageable, there should be very
> *small* list of network cards which should be supported and and listed -i.e.
> in the forum. Take a look at the Intel Etherexpress cards. As I know you
> only need 4 drivers (e100, e1000, e1000e and one compatible) for all intel
> based network cards and you're done. At least for basic support.
> 
> And what, if your new server has not such a card? You have two choices:
> * have an exotic network card, download buildtool, download the driver from
> the manufacture, RTFM, configure, compile, run into trouble, restart, do it
> again, buy an other nic, do it again - all on your own. Hours over hours ...
> days passing ;-)
> - or -
> * buy for ~ 90 € a NIC with 2 ports - knowing that there is a driver in the
> modules tarball ?
> 
> Why not adjusting a little bit the hardware to the software?!

Well, that's what most people try to do and still sometimes someone runs 
into trouble forgetting about a certain piece of hardware not being 
supported. Here the open source environment catches and allows you to 
build your own.

The most recent hardware will most of the time be supported by recent 
software. Kernel 2.4 is not recent, but it is very handy in a number of 
aspects, e.g. ipsec virtual interfaces, kernel size, e.t.c. Still we 
will sooner or later have to bite the bullet and move to 2.6 and Martin 
has built an test environment to do so. With 2.6 most recent hardware is 
supported without the need of a back port.

For the e1000xxx environment I built the environment to compile it for 
Bering with kernel 2.4.34 and it should be rather trivial to port it to 
later 2.4 releases and I told you so. I did not do the uplink feed to 
mainstream Bering as it appeared to be a non issue, I may have to revise 
this.

Erich

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/

Reply via email to