Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 13 Apr 1998 16:49:06 -0700 (PDT)
From:      dan@math.berkeley.edu (Dan Strick)
To:        joerg_wunsch@uriah.heep.sax.de
Cc:        dan@math.berkeley.edu, freebsd-scsi@FreeBSD.ORG
Subject:   Re: SCSI EOT fixed J"org?
Message-ID:  <199804132349.QAA14638@math.berkeley.edu>

next in thread | raw e-mail | index | archive | help
> I don't care what's fine by you. :)  ENOSPC is equally wrong as EIO.
> EOF/EOM _must_ return a partial write, *and no error*.  Anything else
> breaks the Unix semantics, and thus all programs that rely on Unix
> semantics (dump(8), multi-volume tar(1)).

I think this was "discussed" this several months ago.  The 6th Edition UNIX
manual says quite clearly that incomplete writes are errors.  Any other
behavior is likely to have been heavily influenced by System-V which
I consider to be not-exactly-unix.

When I write "UNIX", I use it as a technical term.  I am not referring
to the trademark.  I have no idea who owns the trademark these days or
what the owner uses it to mean.

Note: the POSIX standards are also not-exactly-unix UNIX.  They are POSIX.
I consider FreeBSD and the other BSD derivatives to be almost-unix.
Of all the unix derivatives, these are the most unix-like.

Dan Strick
dan@math.berkeley.edu

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199804132349.QAA14638>