Using SANs and NAS Help for Storage Administrators By W. Curtis Preston The unconfirmed error reports are from readers. They have not yet been approved or disproved by the author or editor and represent solely the opinion of the reader. Here's a key to the markup: [page-number]: serious technical mistake {page-number}: minor technical mistake : important language/formatting problem (page-number): language change or minor formatting problem ?page-number?: reader question or request for clarification This page was updated August 6, 2007. UNCONFIRMED errors and comments from readers: {2} The legend in Figure 1-1; "SE = single threaded" should be "SE = single ended". (3) 2nd paragraph; "Each level could behave any way it wanted, as long as it performed the task assigned to it and spoke to the levels above it and below it according the appropriate command set." I believe you're missing a "to", as in: "...according to the appropriate command set." (21) Figure 2-1; The layer "FC-3" is labeled "Upper level protocols", but on p.22 (3rd line) FC-3 is explained with "Common Services". (31) 2nd last line of section 2 on "Address Selection"; Clarification change: the port with the lowest port name is => the port with the lowest WWN port name is The term "port name" is not defined elsewhere. (84) Last paragraph; Text reads, "Since NT systems lacked integrated, advanced scripting support, and communications between NT machines were easy for administrators to script ..." I think it would make more sense and better reflect the real world if changed to, "Since NT systems lacked integrated, advanced scripting support, and communications between NT machines were *NOT* easy for administrators to script ..." (87) Footnote; Very minor misspelling. For "suvrmgr" read "svrmgr". It would be nice to have an "SUV Manager" but I don't think Oracle offers one ... yet :^) {145} p. 60: In the first line of the first text paragraph, "HTT 1.0" should be "HTTP 1.0"