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

Re: More Moronic Monologue. =Z


Alan Grimes wrote:
> Nor does it give bibliographical reffs to materials that I
> should get to learn how to program well enough to actually use the thing.

  Check out comp.unix.programmer FAQ.  From the top of my mind:

  `Advanced Programming in the UNIX Environment', R. Stevens.

  `UNIX Network Programming' vol. 1, R. Stevens.

  `UNIX Internals: the New Frontiers', U. Vahalia.

  `The Design and Implementation of the 4.4BSD Operating System',
  M. McKusick et al.

  Yes, this list is highly subjective.

> Source code is relatively inaccessable to me because *ALL* unix editors suck
> really really hard. It seems that it was designed to work well with BSD. (whi
> ch
> I don't have the bandwidth to download, nor do I like its disk allocation
> scheme). I would use MINIX but its filesystem gets corrupted on my drive. (al
> l
> filesystems have been getting corrupted on my drive.) =(

  Well, if you  don't want to learn  it, you won't be  able to use
  it.

> What I need is a
> document entitled "compiling and debugging operating systems for stupid jerry
> cumoquats". 
> 
> Some chapters in that book should be:
> "Debugging your driver without de-dataing your drive"

  Impossible.

> "object files are fun"

  See  the info  pages that  come  with the  GNU binutils  bundle.
  There  also   exist  some  articles  like   `Understanding  ELF'
  somewhere on the net.  Email me if you can't find one--I think I
  have a local copy of one of those.

> "How to get a start in operating system programming"

  Two books on UNIX internals are above.

> "When your kernel panics; don't"

  Plenty of UNIX administration books  are available, but I cannot
  recommend any.

> "The Zen of API design"

  See the books above.

> "The Twelve Labors of the operating sysetm coder; a clear concice list for
> people who don't have a clue"

  This one is simple:

  1. Don't write an OS unless you have a clue.

  2. If you still decide to write an OS, see #1.

> "101 Things you should know already and

  ls /usr/share/man/man[23]

  Also, see the recommended textbooks for introductory programming
  courses at  your university.  [For  a vague question, you  get a
  vague answer.]

> Why real programmers snicker at you when
> you ask reasonable questions"

  That's simple:  imagine people asking  you how to write  a check
  over and over again.  At  first, it boosts your self-esteem--but
  then you  realize you're  doing nothing  but answering  the same
  elementary questions over and over again.

> "Writing reusable code for OS programmers"

  There is a whole branch  of CS called `Software Engineering'.  I
  am yet to see a good book about that, though.

> Anyone know the calling convention of GCC so I can link in asm?

  Normal C calling convention: first parameter is pushed last, the
  caller must pop  the parameters off the  stack.  Still confused?
  Try gcc -S.

> How do I get GCC to talk to the page tables?

  Sorry?

> HOW SHOULD A STUPID DUMBASS SUCH AS
> MYSELF KNOW HOW IN BLUE BLAZES TO GET GCC AND LD TO TALK TO EACH OTHER WELL
> ENOUGH TO CREATE AN OBJECT WITH EXACTLY THE RIGHT ENTRY POINTS????

  What are `exactly  the right entry points'?  Email  me about it.
  This is probably offtopic on the list.

-- 
Drive^H^Hnk safely!
Alex Verstak                        averstak@vt.edu
1078 Ambler Johnston East             Virginia Tech
Blacksburg, VA 24060-0022       Tel. (540) 232-1389
References: