Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!cs.utexas.edu!longway!std-unix
From: karl@IMA.IMA.ISC.COM (Karl Heuer)
Newsgroups: comp.std.unix
Subject: Re: Standards Update, Recent Standards Activities
Message-ID: <784@longway.TIC.COM>
Date: 5 Jul 90 13:26:58 GMT
Sender: std-unix@longway.TIC.COM
Reply-To: karl@IMA.IMA.ISC.COM (Karl Heuer)
Organization: Interactive Systems, Cambridge, MA 02138-5302
Lines: 12
Approved: jsq@longway.tic.com (Moderator, John S. Quarterman)

From:  karl@IMA.IMA.ISC.COM (Karl Heuer)

In article <778@longway.TIC.COM> henry@zoo.toronto.edu (Henry Spencer) writes:
>As for what it means to seek on a network endpoint, exactly the same as it
>means to seek on a tty: probably nothing.

Better yet, it should return an error (like an attempt to seek on a pipe).  I
don't think there's any excuse for tty seek having been defined as a no-op in
the first place; it's too bad POSIX didn't require this to be fixed.  (Is
there any reliable way to tell whether a given fd is seekable?)

Volume-Number: Volume 20, Number 98