[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Woody & network errors



Dave Eidson said:

> Of the 26 Linux/Unix machines, the Woody boxes are the only ones that
> ifconfig reports errors.  With uptimes in excess of 5 days on many of the
> non-Woody machines, they still show 0 errors.

they all hooked up using the same hardware/drivers? hooked to
the same switch? and your not doing anything crazy like trying
to for. I can't see how which distribution has any effect on
network errors. what may have an effect is the driver, the hardware,
the cable, the switch. or driver options like disabling Nway
autonegotiation and forcing modes(I don't know why this causes
problems but I've seen donald becker who is a coder of a lot
of linux NIC drivers say over and over this is a very bad thing
to do). even having the card in a different pci slot can cause
problems. If you are really concerned about it I reccomend
joining the mailing list that is for your driver, and ask there,
at least with the eepro mailing list, donald becker is really
helpful to the posters. I think its amazing that so many software
projects out there, and its so easy to get access to the actual
coders of the software. thats so hard to do in the commerical
software world unless you have the big bucks ....

> fixed Cups, but broke the USB side of things.  For production machines
> we'd rather be behind the times and up, than on the bleeding edge and
> down.  :)

same here, cept i won't go near 2.4.x yet, even non production, for
my personal use. everything is 2.2.19 or in rare cases 2.2.18 or
2.2.17(depends on how long ago it was last rebooted ..)

i am thinking i will try 2.4.19 or 2.4.20 whichever is latest
sometime early next year and think about deploying it maybe march-april
2003 ..

and before anyone curses me out, think about all the 2.0.x kernel
users out there! theres a new 2.0.x kernel comming out soon too
i think(read about it recently in kernel traffic)

nate





Reply to: