Natalia
I don't know of any non-8-bit Unix systems, but Multics, on the GE645 at
least, had a 36-bit word. See
http://en.wikipedia.org/wiki/Multics
James
----- Original Message -----
From: "Natalia Portillo" <iosglpgc(a)teleline.es>
Date: Thu, 30 Sep 2004 20:07:46 +0100
To: <tuhs(a)tuhs.org>
Subject: [TUHS] 6-bit, 7-bit and 9-bit byte UNIXes
> Hi!
>
> Was there any UNIX with 6-bit wide, 7-bit wide or 9-bit wide bytes or all
> UNIXes are 8-bit wide bytes?
>
> Regards
>
> _______________________________________________
> TUHS mailing list
> TUHS(a)minnie.tuhs.org
> http://minnie.tuhs.org/mailman/listinfo/tuhs
Hi,
I have a copy of the WEBSTER server and client port to UNIX by
* David A. Curry
* Purdue University
* Engineering Computer Network
* April, 1986
I see in the doc directory a very TOPS-20-ish docuement webster.hlp which
describes the way to invoke the client:
@WEBSTER word-to-define
I'm assuming the @ is the TOPS-20 prompt. It also says you can use
If you want to look up more than one word, just do
@WEBSTER<return>
and you will be prompted with
Word:
Type the word, or hit <return> to exit.
But if the @ prompt wasn't enough evidence of TOPS-20 you also get:
<escape> and "?" are used the same way in Webster as in most programs.
<escape> tries to complete what you have typed so far, and "?" lists
those words that match your partial word.
Which is pure TOPS-20 "COMND JSYS". See this page for what "COMND JSYS" is:
http://pdp-10.trailing-edge.com/decuslib20-01/01/decus/20-0002/comnd.doc.ht…
There is some cryptic mentioning about EBCDIC conversion as if the dictionary
data went from ASCII to EBCDIC and back to ASCII causing some degradation.
ebcdictp.ememo talks about the format of the EBCDIC tape (not that I have one)
and errors.ememo says:
2) Pronunciation records.
Three classes of errors occur here.
During the translation to EBCDIC occurances of the glyphs *( and
)* in the pronunciation records were treated in the same way as in other
records, that is encoded as <( and >) (representing left and right
braces), rather than left as is. Thus a schwa precceding or following an
optional phoneme was lost.
I just blew a few minutes looking it over today and ported it to FreeBSD/AMD64
catching a
char word[BUFSIZ];
isnumber(word)
bug and some other minor things.
Does anyone else have this treasure running? I like it better than dict for
etymologies.
Hi,
I have a copy of the WEBSTER server and client port to UNIX by
* David A. Curry
* Purdue University
* Engineering Computer Network
* April, 1986
I see in the doc directory a very TOPS-20-ish docuement webster.hlp which
describes the way to invoke the client:
@WEBSTER word-to-define
I'm assuming the @ is the TOPS-20 prompt. It also says you can use
If you want to look up more than one word, just do
@WEBSTER<return>
and you will be prompted with
Word:
Type the word, or hit <return> to exit.
But if the @ prompt wasn't enough evidence of TOPS-20 you also get:
<escape> and "?" are used the same way in Webster as in most programs.
<escape> tries to complete what you have typed so far, and "?" lists
those words that match your partial word.
Which is pure TOPS-20 "COMND JSYS". See this page for what "COMND JSYS" is:
http://pdp-10.trailing-edge.com/decuslib20-01/01/decus/20-0002/comnd.doc.ht…
There is some cryptic mentioning about EBCDIC conversion as if the dictionary
data went from ASCII to EBCDIC and back to ASCII causing some degradation.
ebcdictp.ememo talks about the format of the EBCDIC tape (not that I have one)
and errors.ememo says:
2) Pronunciation records.
Three classes of errors occur here.
During the translation to EBCDIC occurances of the glyphs *( and
)* in the pronunciation records were treated in the same way as in other
records, that is encoded as <( and >) (representing left and right
braces), rather than left as is. Thus a schwa precceding or following an
optional phoneme was lost.
I just blew a few minutes looking it over today and ported it to FreeBSD/AMD64
catching a
char word[BUFSIZ];
isnumber(word)
bug and some other minor things.
Does anyone else have this treasure running? I like it better than dict for
etymologies.
Ok Guys,
I humbly apologise for not working this out from day one :-)
The problem was that I'd mounted the device after fstab from the desktop and SuSE in this configuration appears to prevent shell scripts from being fired off. If I mount everything in fstab at boot time then it all works.
Don't know whether this is a general SuSE thing or whether it is just a "feature" of the version that I'm running (8.2).
Well, you live and learn don't you :-)
Chears and thanks for all of the advice, through which I learn't stuff so it wasn't all that bad.
Robin
> Date: Thu, 12 Aug 2004 18:49:11 +0100
> To: "Greg 'groggy' Lehey" <grog(a)lemis.com>
> From: Robin Birch <robinb(a)ruffnready.co.uk>
> Subject: Re: [pups] Installing begemot
> I have a different problem as well. There is something broken in the
> configuration of this computer!!!!! If I execute a shell file by going
> /bin/sh filename then it works ok but if I try running a shell script
> with #!/bin/sh in the first line I get a bad permission error. This is
> preventing me from running make scripts and all sorts of things. Any
> ideas?
Yes. See the following transcript of a session. I created a small
script named "bad" which just does "date" to show that it worked.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
iota: try 1107$ ls -l bad
-rwxrwxr-x 1 cdl cdl 16 Aug 12 15:56 bad*
iota: try 1108$ /bin/sh bad
Thu Aug 12 15:57:37 PDT 2004
iota: try 1109$ ./bad
: bad interpreter: No such file or directory
iota: try 1110$ cat bad
#!/bin/sh
date
iota: try 1111$ od -c bad
0000000 # ! / b i n / s h \r \n d a t e \n
0000020
iota: try 1112$
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Note that there is a '\r' character at the end of the #! line.
carl
--
carl lowenstein marine physical lab u.c. san diego
clowenst(a)ucsd.edu
In message <411BD929.4080009(a)sun.com>, Chris Drake <Chris.Drake(a)sun.com>
writes
>> The most curious one is a "bad interpreter" one. This is what I get
>>along with the permissions moan. But curiously if I run it sh
>>filename then all works.
>> It is as though there is some global shell permissions set up that
>>is munged.
>
>Hoo, you've got a weirdo, all right. Darn, I was hoping it was trivial.
>
>Bad interpreter: sounds like the first line where you select "the shell"
>is munched somehow. Officially, you can select any interpreter you want -
>but you gotta get the name right. :)
>
>More thoughts:
> - any problems with the pathname? Is it /bin/sh and nothing else?
> - check perms on /, /bin, and /bin/sh just in case something got
> zapped
> - what's your normal shell? How about it you change /bin/sh to
> the thing you run normally?
> - does anything follow the "sh" on the line? Like, perchance any
> strange nonprintable chars that might be interpreted as a part
> of the name or as a parameter to the shell?
> - try #!/bin/sh -x to see if you get any output from the script
> as it's run
> - do other scripts like one-liners work OK? Ie,
> #!/bin/sh
> echo hello world
> - any other messages?
>
>Just saw Warren's email, and he has a few good ones as well - like, what are
>you running on? :)
>
> - Chris
>
Hi Chris,
See my reply to Warren. I'll try this all tomorrow, the system is in
work.
Cheers
Robin
--
Robin Birch
Hi All,
Well I know it's been quiet for ages on this but hopefully someone is
listening.
I've just started to put P11 on a new Linux box and am having problems
building begemot. It keeps blowing out when compiling panic. Is there
a more recent version or are there some obvious patches I can do.
Regards
Robin
--
Robin Birch
