Originally posted by jollyd
View Post
Never got 2 wifi cards (Linksys to be exact) working under Debian GNU/Linux although they were advertized as working for the same major version.
Maybe it was patched and working under distribution X but Y won't.
Sure it always work 90% of the time but what is the potential issue for the 10%, in particular when you can't trace changes in interfaces without being an expert (which I'm not) ?
Maybe it was patched and working under distribution X but Y won't.
Sure it always work 90% of the time but what is the potential issue for the 10%, in particular when you can't trace changes in interfaces without being an expert (which I'm not) ?
You can always ask at lkml. I have no knowledge about tracing etc. so I can't argue here.
I think it's matter of granularity of the developement model. Truth stands in the middle.
I don't write bullshit, just figure that I didn't expressed my thought correctly. I dislike when parallel port driver is broken.. then I upgrade and wifi stops working, then upgrade and USB freeze with my USB key (and so on)...
I spend many hours on such problems. I prefer losing few microseconds on thread creation and avoiding spending 2 hours figuring which combination of kernel version /driver version is optimal. Moreover I had in mind that exporting statistics with kstat is nice.
I spend many hours on such problems. I prefer losing few microseconds on thread creation and avoiding spending 2 hours figuring which combination of kernel version /driver version is optimal. Moreover I had in mind that exporting statistics with kstat is nice.
As for swapping issues: with friends we were stunned... we tested on 5 kernel versions and compared with MacOSX, FreeBSD and Solaris. Debian couldn't stand the test and even ssh was unavailable. @ work on the cluster some nodes had the same issue and we had network connectivity issues that administrators couldn't diagnose. An update solved the network problem but not the swapping issue.
I admit maybe it's a Debian specific problem.
I admit maybe it's a Debian specific problem.
On my laptop and desktop under Debian I have problems with USB mass storage: couldn't handle more than on device without freezing.
I gave few example of the drivers that did cause some issues under Linux and no problem under BSD and Solaris.
Didn't meant to judge the quality of the code, but the fact that I fear the uncertainty of a driver working correctly at time $t$ and not at time $t + \delta t$
I'm writing about my experience, which may be different from yours.
I gave few example of the drivers that did cause some issues under Linux and no problem under BSD and Solaris.
Didn't meant to judge the quality of the code, but the fact that I fear the uncertainty of a driver working correctly at time $t$ and not at time $t + \delta t$
I'm writing about my experience, which may be different from yours.
Seems to me that Linux and GNU use a superset of POSIX.
It's not clear to me whether default behaviour is the correct one.
I think linking /bin/sh to /bin/bash was not a lucky choice.
It's not clear to me whether default behaviour is the correct one.
I think linking /bin/sh to /bin/bash was not a lucky choice.
Agreed, don't take it as criticism (which isn't) but I express the fact that I'm satisfied with brandz.
A positive for one, is not a negative for the other.
Best regards,
a.
A positive for one, is not a negative for the other.
Best regards,
a.
Please, any idea for the next iteration ?
Comment