Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!houxm!mtuxo!hfavr From: hfavr@mtuxo.UUCP (a.reed) Newsgroups: net.unix-wizards Subject: Re: mkdir(2) on System V Message-ID: <1536@mtuxo.UUCP> Date: Tue, 6-May-86 01:05:42 EDT Article-I.D.: mtuxo.1536 Posted: Tue May 6 01:05:42 1986 Date-Received: Fri, 2-May-86 07:46:26 EDT References: <663@imag.UUCP> <1525@mtuxo.UUCP> <3593@sun.uucp> Organization: AT&T Information Systems Labs, Holmdel NJ Lines: 26 This is a retraction. When I read > > > UNIX system V users may have remarqued there is no "mkdir(2)" system call. > > > It is replaced by "mknod(2)", but must be executed only by super-user. I assumed that the mkdir(2) referred to by the above was the one I once used on a university system. I answered > > mkdir(2) was a security problem (think about it). To which Guy Harris responded: > What the hell are you talking about? Do you know what the "mkdir" system > call actually does? Are you aware that it makes a directory *with the "." > and ".." entries included*? Now, the mkdir(2) I remembered did not do this. Moreover, G.H. writes that > The "mkdir" system call appeared in 4.2BSD. It was not in V7, > and wasn't added in S3 or S5. It appears that the mkdir(2) I used was a local enhancement BSD later picked up (and fixed the security hole). Mea maxima culpa. Adam Reed