I got a book called something like "The Linux TCP/IP Stack", which, on first read seemed like too much code, however after doing a rudimentary data networking course (which i could have done by reading Tanenbaum or Circuse sp?) I found that it is really very good. If you like history, you'll get into it - 1999 is actually not that long ago (unless you want to get into wireless or current multimedia protocols like RSVP, RSP & SIP). Even H.323 (another VoIP protocol suite is about 20 years old). If your book is raving about ATM, maybe get another one. If its going on about X.25 chuck it ;-) I heard somewhere that computer networking has more acronyms than any other discipline - you'll get the hang of it. Well done too btw, getting linux up and running on your desktop - it shows you're human....interested in howstuffworks (which btw is an excellent site for n/w and anything that goes).
Um, what else - oh yeah, I had (have) the same problem as you (OS first then n/w) and my prob is at the moment getting a linux client to talk to a windows server via a wireless router - its a slow process....esp when you gotta do everything yourself, and wade through so much info - I also get sidetracked too easily - its a big world, and part of the skill is being able to ignore tech that you dont need to know about, perhaps DHCP? Anyway, good luck Henry -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
