I noticed that my favorite "errno" has now gotten trashed by
the newer 'C' runtime libraries.
ENOTTY has been for ages, "Not a typewriter".
It's now been changed to "Inappropriate ioctl for device".
Methinks that this means that ../linux/include/as
Followup to: <[EMAIL PROTECTED]>
By author:"Richard B. Johnson" <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> I noticed that my favorite "errno" has now gotten trashed by
> the newer 'C' runtime libraries.
>
> ENOTTY has b
has come to mean something completely
>different in a Unix context)... "not a typewriter" is just a
>completely confusing error message for the uninitiated.
I disagree. "Not a typewriter" is part of Unix tradition, and ought to be
retained as a historical reference.
>I disagree. "Not a typewriter" is part of Unix tradition, and ought to be
>retained as a historical reference. It's also an opportunity for "the
>uninitiated" to learn a little more and move a little closer to becoming "the
>initiated."
Heave
At 7:20 PM -0400 2001-05-10, Hacksaw wrote:
> >I disagree. "Not a typewriter" is part of Unix tradition, and ought to be
>>retained as a historical reference. It's also an opportunity for "the
>>uninitiated" to learn a little more and move a
On Thu, 10 May 2001, Jonathan Lundell wrote:
> ENOTTY is used by several non-serial devices (or file systems) to
> object to an unrecognized ioctl command. There's also ENOIOCTLCMD
> (apparently supposed to be a non-user errno, but i don't see where it
> gets changed to something else) and E
quot;
> >stands for "teletypewriter" it has come to mean something completely
> >different in a Unix context)... "not a typewriter" is just a
> >completely confusing error message for the uninitiated.
>
> I disagree. "Not a typewriter" is pa
At 8:07 PM -0400 2001-05-10, Alexander Viro wrote:
>On Thu, 10 May 2001, Jonathan Lundell wrote:
>
>> ENOTTY is used by several non-serial devices (or file systems) to
>> object to an unrecognized ioctl command. There's also ENOIOCTLCMD
>> (apparently supposed to be a non-user errno, but i don'
> I disagree. "Not a typewriter" is part of Unix tradition, and ought to be
> retained as a historical reference. It's also an opportunity for "the
> uninitiated" to learn a little more and move a little closer to becoming "the
> initiated."
"Richard B. Johnson" wrote:
>
> I noticed that my favorite "errno" has now gotten trashed by
> the newer 'C' runtime libraries.
>
> ENOTTY has been for ages, "Not a typewriter".
> It's now been changed to "Inappropriate ioctl
Jonathan Lundell writes:
> FWIW, the comment in errno.h under Solaris 2.6 is "Inappropriate
> ioctl for device". I believe that's the POSIX interpretation.
POSIX has
[ENOTTY] Inappropriate I/O control operation
A control function was attempted for a file or special file
typewriter" aren't exactly the same thing (even though "tty"
> > >stands for "teletypewriter" it has come to mean something completely
> > >different in a Unix context)... "not a typewriter" is just a
> > >completely confusi
On 05/10/2001 at 06:20:34 PM Hacksaw <[EMAIL PROTECTED]> wrote:
>Heaven help us when tradition is more important than clarity.
>
If clarity is the most important consideration, then other things should be
changed as well. For instance, the command we use to search for text strings in
files sh
On Fri, 11 May 2001 [EMAIL PROTECTED] wrote:
> >Heaven help us when tradition is more important than clarity.
> >
>
> If clarity is the most important consideration, then other things should be
> changed as well. For instance, the command we use to search for text strings in
> files should be ca
On 05/11/2001 at 12:03:43 PM Joel Jaeggli <[EMAIL PROTECTED]> wrote:
>it's not clear to me that that textsearch is a more accurate description
>than Get Regular ExPression
It's not more accurate. But Hacksaw's original point was that a new user would
not know wh
>If clarity is the most important consideration, then other things should be
>changed as well. For instance, the command we use to search for text strings
in
>files should be called "textsearch." That's a lot more clear than "grep."
Well, I can't disagree. Unix's biggest turn off was the stupi
On 05/11/2001 at 04:43:13 PM Hacksaw <[EMAIL PROTECTED]> wrote:
>Well, I can't disagree. Unix's biggest turn off was the stupid command names.
>It's a big reason why Unixoid systems aren't more commonplace. I only learned
>it because I was stuck at a desk with a Wyse terminal. Otherwise I pro
2001 1:19 PM
To: Hacksaw
Cc: [EMAIL PROTECTED]
Subject: Re: Not a typewriter
On 05/11/2001 at 04:43:13 PM Hacksaw <[EMAIL PROTECTED]> wrote:
>Well, I can't disagree. Unix's biggest turn off was the stupid command
names.
>It's a big reason why Unixoid systems aren&#
On Fri, 11 May 2001 11:07:45 -0500, [EMAIL PROTECTED] wrote:
>
>
>On 05/10/2001 at 06:20:34 PM Hacksaw <[EMAIL PROTECTED]> wrote:
>
>My point is that someone who sees the "typewriter" message and doesn't
>understand it will have to dig a bit to find out what it means. Finding it
>almost certain
On Fri, 11 May 2001 [EMAIL PROTECTED] wrote:
>>Heaven help us when tradition is more important than clarity.
>>
>
>If clarity is the most important consideration, then other things should be
>changed as well. For instance, the command we use to search for text strings in
>files should be called
On Fri, 11 May 2001, Hacksaw wrote:
>Well, I can't disagree. Unix's biggest turn off was the stupid command names.
I agree partially with that, but as someone who's used DCL in
VMS, I can say meaningful names are no better. People don't want
to type SHOW DIRECTORY or CREATE /DIRECTORY /PERMISSI
"Mike A. Harris" <[EMAIL PROTECTED]> said:
> On Fri, 11 May 2001 [EMAIL PROTECTED] wrote:
[...]
> >why creat doesn't end in an "e;" and so forth. I tell the
The old C compiler/old Unix linker guaranteed 6 chars in an external symbol
name only, and C functions got an underscore prepended: _crea
>why creat doesn't end in an "e;" and so forth. I tell the
Some time back, Ken Thompson was asked, if he had it to do over
again, what changes he would make to Unix. The only thing he could
think of: spell it "create()".
--
/Jonathan Lundell.
-
To unsubscribe from this list: send the line "un
On 05/13/2001 at 08:03:30 PM Horst von Brand <[EMAIL PROTECTED]>
wrote:
>The old C compiler/old Unix linker guaranteed 6 chars in an external symbol
>name only, and C functions got an underscore prepended: _creat. I guess
>this is the reason for this wart. As to why 6 chars only, I'd guess some
On Sun, May 13, 2001 at 09:03:30PM -0400, Horst von Brand wrote:
> The old C compiler/old Unix linker guaranteed 6 chars in an external symbol
> name only, and C functions got an underscore prepended: _creat. I guess
> this is the reason for this wart. As to why 6 chars only, I'd guess some
> dat
On Sun, May 13, 2001 at 09:03:30PM -0400, Horst von Brand wrote:
> "Mike A. Harris" <[EMAIL PROTECTED]> said:
> > On Fri, 11 May 2001 [EMAIL PROTECTED] wrote:
>
> [...]
>
> > >why creat doesn't end in an "e;" and so forth. I tell the
>
> The old C compiler/old Unix linker guaranteed 6 chars in
> IIRC, the 6 character linker requirement came from when the Bell Labs folk
> ported the C compiler the IBM mainframe world, not from the early UNIX (tm)
> world. During the original ANSI C meetings, I got the sense from the IBM rep,
6 character linker name limits are very old. Honeywell L66 GC
- Received message begins Here -
>
> > IIRC, the 6 character linker requirement came from when the Bell Labs folk
> > ported the C compiler the IBM mainframe world, not from the early UNIX (tm)
> > world. During the original ANSI C meetings, I got the sense from the IBM rep,
>
On Mon, May 14, 2001 at 06:01:42PM +0100, Alan Cox wrote:
> > IIRC, the 6 character linker requirement came from when the Bell Labs folk
> > ported the C compiler the IBM mainframe world, not from the early UNIX (tm)
> > world. During the original ANSI C meetings, I got the sense from the IBM rep
Followup to: <[EMAIL PROTECTED]>
By author:Jesse Pollard <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> well... actually it was 6 bit "ascii" computed from: (char - ' '). Depends
> entirely on architecture, and implementation. EBCD/6Bit/7Bit and EBCDIC were
> supported on the Honeywe
[EMAIL PROTECTED] wrote on 11.05.01 in <[EMAIL PROTECTED]>:
> I think man is the best help system ever devised. (The GNU Info system,
> however, is the spawn of Satan. :-)
Both have good and bad parts. HTML and PDF are yet other such candidates.
Something better is needed, but no two people s
On Thu, 10 May 2001 [EMAIL PROTECTED] wrote:
> I disagree. "Not a typewriter" is part of Unix tradition, and ought
> to be retained as a historical reference. It's also an opportunity
> for "the uninitiated" to learn a little more and move a little closer
> > If anything it should be "Not a teletype"
>
> fork it and see which code base the users support! ;) (would support the
> one that doesn't mention !#@$%#$ typewriters. that irritated me for months
> when i used DYNIX and my terms never worked properly.)
You can internationalise the error stri
33 matches
Mail list logo
