Slashdot Mirror

← Back to Stories (view on slashdot.org)

Tridge Speaks Out

Posted by CmdrTaco on from the samba-man-speaketh dept.

Robert McMillan from Linux Magazine posted an interview with Tridge, of Samba and Tivo fame. He's one of the most important folks in all of Linux, and this interview is worth a read. He covers a lot of good material like crap code, bonobo, and what stuff in the kernel is innovative. He also talks a bit about what he might do after Microsoft drops SMB from future versions of windows.

3 of 86 comments (clear)

  1. Printer friendly one page version... by gowen · · Score: 4, Informative

    Is here.

    Hmm, you'd think a "printer friendly" version would remove JPGs of Unix-nerds. No one wants to print those out. Actually, I'd be happy if that were the only thing it did.

    --
    Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
  2. Re:Yet Another Unemployed Programmer (TM)? by BacOs · · Score: 5, Informative

    According to his home page

    Until recently I was a senior engineer in VA Linux Systems. Due to the recent layoffs at VA I am now actively looking for a job.

  3. clc by Anonymous Coward · · Score: 5, Informative
    comp.lang.c is your friend. It's one of the strictest newsgroups on Usenet, perhaps second only to comp.std.c ;). If you post anything on there that looks suspicious in light of the standard, even if it would cause problems on machines that don't even exist (and never will), you will get more "grumpy" responses (not to be confused with flames) than you can deal with.


    Also, you'll get some pretty heavy heat on the style issue. Casting malloc(), using redundant parantheses on sizeof (i.e. treating it as a function or macro), performing micro-operations (which the compiler/interpreter does a much better job of) are all grounds for assault.


    comp.lang.c will set you straight within a couple of weeks (given you're willingness to be humiliated on a regular basis), and you'll be still be learning things after years of regular reading. Again: comp.lang.c is very strict: if comp.lang.c++ is Woodstock, comp.lang.c is a Nazi concentration camp. Okay maybe I'm overselling it a bit :)


    As for automatic code checkers, use lclint liberally. There's also the mythical Stanford patch for gcc (at least I think it's from Stanford; one of those pretentious schools anyway) that was used to find many Linux bugs.


    Seriously, just start posting random tiny (no longer than 3 or 4 small functions, or else people will get bored of reading) snippets of code to comp.lang.c. 95% of posters can't even get a satisfactory Hello World! on their first try.