/tmp versus temporary file types

Boyd Roberts boyd at basser.oz
Tue Oct 22 14:06:41 AEST 1985


  In article <1622 at gatech.CSNET> arnold at gatech.CSNET (Arnold Robbins) writes:
  >Why not do something like
  >
  >	fd = open ("/dev/temp", O_RDWR);
  >	/* O_CREAT implied by the use of /dev/temp */
  >
  >The kernel just grabs a fresh inode off whatever device /tmp is mounted on,
  >or the "temp device" could be a configurable parameter in the same way that
  >the swap device is. Then flink() or whatever ought to work properly as well.

Yes, that's the way.  Re-define the semantics of the system calls because
you want dodgy feature X.  The UNIX file-system is clean and straight forward.
So too are the system calls.  But, oh no, instead of using the interfaces
provided it's time to mash them into five zillion different flavours, with
no gain in functionality.

How about a "/dev/dir" for directories, "/dev/pipe" for pipes, "/dev/link"
for links?  And, of course, depending on the file type change the semantics
of the system calls.  Add fchdir().

Be real.  Write a function to provide the interface you want, using the
interfaces provided.  Give a programmer a job, but *DON'T* bust the kernel!


Boyd Roberts			...!seismo!munnari!basser.oz!boyd



More information about the Comp.unix.wizards mailing list