Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: Re:Coming to a disaster near you. (Score 1) 452

by NoMoreFood (#26496205) Attached to: Seagate Hard Drive Fiasco Grows
I think it's difficult to classify a company based a single set of drive failures. All it takes is one engineer to overlook some very improbable interrupt processing race condition or some bus contention issue and you've got bad firmware on a million drives that have shipped. If you don't test setup that can exercise EVERY possible condition, it's tough to find this stuff. Not that it's excuse, but just saying...

I just recently finished probably some firmware for a high speed serial card for internal use at our company. However, it's still suffering from a lock-up after transmitting about an 100 terabytes of data (average) -- from an 'unknown' interrupt!

Comment: Re:GCC 2.95? Seriously? (Score 3, Informative) 178

by NoMoreFood (#26319725) Attached to: Linux Kernel 2.4 Or 2.6 In Embedded System?

GCC 3.4 is quite outdated. 2.95 is just plain old. Why not code in Fortran while you're at it?

My development group is also stuck with gcc 2.9x series because it's only compiler our toolchain maker (WindRiver) supports for VxWorks 5.X. I'm guessing he's in a similar situation. I can't complain though -- we've never had an issue with it.

The degree of technical confidence is inversely proportional to the level of management.

Working...