Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site usfvax2.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!vax135!petsd!peora!ucf-cs!usfvax2!hewitt From: hewitt@usfvax2.UUCP (Ian Hewitt) Newsgroups: net.news.group Subject: Creation of net.doc Message-ID: <239@usfvax2.UUCP> Date: Fri, 25-Oct-85 15:27:35 EDT Article-I.D.: usfvax2.239 Posted: Fri Oct 25 15:27:35 1985 Date-Received: Sat, 26-Oct-85 19:41:35 EDT Organization: Univ. of South Florida, Tampa Lines: 30 I think creation of "net.doc" could be beneficial to a lot of users out there, especially to those of us who have to use the Berkeley documentation to do our jobs and keep our systems running. I don't know about anyone else, but I do not have a real guru around to consult with when something goes wrong (as suggested in the Berkely doc--see fsck sup). If there is any one area which certainly needs attention, it is UNIX documentation. It has been suggested that no "competant technical writers" could be persuaded to contribute, but I disagree. There are a lot of people out there who are capable of writing reaonably, especially if they are encouraged and given a forum for criticism. I personally would like to see a more professional, complete, structured, and informative documentation set for the UNIX systems and think it would help alleviate one of UNIX's biggest disadvantages. To anticipate the arguements forthcoming: ----- > I know UNIX represents more freedom from too rigid a structure and I realize that a lot of documentation out there tries to be so sophisticated that it also becomes unreadable. I do not want that, but I'd like something better than what we have now. If we create net.doc, I'm sure there will be some discussions, but I also think it might be able to generate some home-grown documention or doc. aids which could be useful. I mean, if one really good rewrite take place, it might save someone a lot of frustration and time. Ian Hewitt {attunix,mcnc,ihnp4}!akgua!usfvax2!hewitt {decvax,peora}!ucf-cs!usfvax2!hewitt CSNET: hewitt%usfvax2.uucp@ucf.CSNET