🚀 go-pugleaf

On Wed, 2018-05-23, Joe Makowiec wrote:
> For those of us who got into personal computers in the late 80s and early
> 90s, this is momentous news:
>
> http://www.computerhistory.org/_static/atchm/the-eudora-email-client-source-code/
>
> Qualcomm donated the whole thing - source, trademarks, domain names - to
> the Computer History Museum. From the page above:
>
>     The discussion with Qualcomm for the release of the Eudora source
>     code by the company's museum took five years. In the end, they
>     decided not to simply grant a license, but to transfer ownership
>     of the code, the Eudora trademarks, the copyrights, and the Eudora
>     domain names to the Computer History Museum (CHM). The transfer
>     agreement allows us to publish the code under the very liberal BSD
>     open source license, which means that anyone can use it for either
>     personal or commercial purposes. 

Which also means we get the same rights.  Noone has put it on GitHub
yet, though.

More from the page:

    The source code we are distributing is what we received from Qualcomm,
    with only the following changes:

      * addition of the CHM copyright notice and the BSD license
      * sanitization of “bad words”, mostly in comments, as requested
        by Qualcomm
      * removal of third-party software that neither the museum nor
        Qualcomm has the right to distribute

I'm suddenly more interested in the missing "bad words" than in the
software itself.  The phrase "/mostly/ in comments" is also
interesting.

/Jorgen

-- 
  // Jorgen Grahn <grahn@  Oo  o.   .     .
\X/     snipabacken.se>   O  o   .

On Thu, 24 May 2018 09:28:09 GMT, Huge <Huge@nowhere.much.invalid> wrote:

> On 2018-05-23, Jorgen Grahn <grahn...@snipabacken.se> wrote:
> 
> [31 lines snipped]
> 
>> I'm suddenly more interested in the missing "bad words" than in the
>> software itself.  The phrase "/mostly/ in comments" is also
>> interesting.
> 
> I expect there are some documentation files, also.
> 
> 

I was thinking of variable names;

if fatal-error
   set systemstate=FUBAR

-- 
Bah, and indeed, Humbug.

On 23 May 2018 22:45:10 GMT
Jorgen Grahn <grahn...@snipabacken.se> wrote:

> The phrase "/mostly/ in comments" is also interesting.

	Probably examples of creative use of naming conventions.

-- 
Steve O'Hara-Smith                          |   Directable Mirror Arrays
C:\>WIN                                     | A better way to focus the sun
The computer obeys and wins.                |    licences available see
You lose and Bill collects.                 |    http://www.sohara.org/

On 24/05/2018 12:19, Huge wrote:
> 
> (Is anyone gong to get upset about "FUBAR", unless spelled out in full?)

FUCTI
FINO

On 2018-05-24, Gareth's Downstairs Computer
<headstone255.but.n...@yahoo.com> wrote:

> On 24/05/2018 12:19, Huge wrote:
> 
>> (Is anyone gong to get upset about "FUBAR", unless spelled out in full?)
>
> FUCTI
> FINO

I always thought of it as a three-stage process:

SNAFU - Situation Normal, All F*cked Up
TADFU - Things Are Definitely F*cked Up
FUBAR - F*cked Up Beyond All Recognition (or Repair)

-- 
/~\  cgibbs@kltpzyxm.invalid (Charlie Gibbs)
\ /  I'm really at ac.dekanfrus if you read it the right way.
 X   Top-posted messages will probably be ignored.  See RFC1855.
/ \  Fight low-contrast text in web pages!  http://contrastrebellion.com

On 05/24/2018 12:10 PM, Charlie Gibbs wrote:
> I always thought of it as a three-stage process:
> 
> SNAFU - Situation Normal, All F*cked Up
> TADFU - Things Are Definitely F*cked Up
> FUBAR - F*cked Up Beyond All Recognition (or Repair)

TADFU is new to me.  I like it.



-- 
Grant. . . .
unix || die

On 25/05/2018 00:37, Grant Taylor wrote:
> On 05/24/2018 12:10 PM, Charlie Gibbs wrote:
>> I always thought of it as a three-stage process:
>>
>> SNAFU - Situation Normal, All F*cked Up
>> TADFU - Things Are Definitely F*cked Up
>> FUBAR - F*cked Up Beyond All Recognition (or Repair)
> 
> TADFU is new to me.  I like it.
> 
> 
> 

ISTR this as TARFU ...  TA REALLY  FU

In article <pe6v6...@news4.newsguy.com>,
Charlie Gibbs  <cgibbs@kltpzyxm.invalid> wrote:
>On 2018-05-24, Gareth's Downstairs Computer
><headstone255.but.n...@yahoo.com> wrote:
>
>> On 24/05/2018 12:19, Huge wrote:
>> 
>>> (Is anyone gong to get upset about "FUBAR", unless spelled out in full?)
>>
>> FUCTI
>> FINO
>
>I always thought of it as a three-stage process:
>
>SNAFU - Situation Normal, All F*cked Up
>TADFU - Things Are Definitely F*cked Up
>FUBAR - F*cked Up Beyond All Recognition (or Repair)
>
>-- 
>/~\  cgibbs@kltpzyxm.invalid (Charlie Gibbs)
>\ /  I'm really at ac.dekanfrus if you read it the right way.
> X   Top-posted messages will probably be ignored.  See RFC1855.
>/ \  Fight low-contrast text in web pages!  http://contrastrebellion.com

I'm still surprised the VAX 11/780 had the Failed Unibus Address
Register when the PDP11 couldn't have a SEX instruction (replaced with
Sign ExTend (SXT)  -- the PDP11/34 still had the SEX Multiplexer on the
board.

Bill

pechter@ascii.(none) (William Pechter) writes:
>In article <pe6v6...@news4.newsguy.com>,
>Charlie Gibbs  <cgibbs@kltpzyxm.invalid> wrote:
>>On 2018-05-24, Gareth's Downstairs Computer
>><headstone255.but.n...@yahoo.com> wrote:
>>
>>> On 24/05/2018 12:19, Huge wrote:
>>> 
>>>> (Is anyone gong to get upset about "FUBAR", unless spelled out in full?)
>>>
>>> FUCTI
>>> FINO
>>
>>I always thought of it as a three-stage process:
>>
>>SNAFU - Situation Normal, All F*cked Up
>>TADFU - Things Are Definitely F*cked Up
>>FUBAR - F*cked Up Beyond All Recognition (or Repair)
>>
>>-- 
>>/~\  cgibbs@kltpzyxm.invalid (Charlie Gibbs)
>>\ /  I'm really at ac.dekanfrus if you read it the right way.
>> X   Top-posted messages will probably be ignored.  See RFC1855.
>>/ \  Fight low-contrast text in web pages!  http://contrastrebellion.com
>
>I'm still surprised the VAX 11/780 had the Failed Unibus Address
>Register when the PDP11 couldn't have a SEX instruction (replaced with
>Sign ExTend (SXT)  -- the PDP11/34 still had the SEX Multiplexer on the
>board.

Burroughs had the Write Hardware Register (WHR) and Search Linked lisT (SLT)
instructions.    Pronunciation left to your imagination.

Large systems main process creation internal MCP function was called motherforker.

On Fri, 25 May 2018 15:46:15 -0000 (UTC), pechter@ascii.(none)
(William Pechter) wrote:

[snip]

>I'm still surprised the VAX 11/780 had the Failed Unibus Address
>Register when the PDP11 couldn't have a SEX instruction (replaced with
>Sign ExTend (SXT)  -- the PDP11/34 still had the SEX Multiplexer on the
>board.

     Maybe, the B was missed.

     These days, someone might have tried for a SEXT instruction or
pronouncing "SXT" that way.

Sincerely,

Gene Wirchenko

On 5/26/2018 7:41 PM, Gene Wirchenko wrote:
> On Fri, 25 May 2018 15:46:15 -0000 (UTC), pechter@ascii.(none)
> (William Pechter) wrote:
> 
> [snip]
> 
>> I'm still surprised the VAX 11/780 had the Failed Unibus Address
>> Register when the PDP11 couldn't have a SEX instruction (replaced with
>> Sign ExTend (SXT)  -- the PDP11/34 still had the SEX Multiplexer on the
>> board.
> 
>       Maybe, the B was missed.
> 
>       These days, someone might have tried for a SEXT instruction or
> pronouncing "SXT" that way.
> 

Extended PDP-11 instruction sets included an SOB (subtract one and 
branch) instruction.  The Motorola MC6809 had a SEX (sign extend) 
instruction and the RCA 1802 had a SEX (set index register) instruction.

And don't forget the Power PC chip (PPC) instruction EIEIO (enforced 
in-order execution of I/O.


-- 
numerist at aquaporin4 dot com

On Sat, 26 May 2018 21:15:30 -0500, Charles Richmond
<nume...@aquaporin4.com> wrote:

>On 5/26/2018 7:41 PM, Gene Wirchenko wrote:
>> On Fri, 25 May 2018 15:46:15 -0000 (UTC), pechter@ascii.(none)
>> (William Pechter) wrote:
>> 
>> [snip]
>> 
>>> I'm still surprised the VAX 11/780 had the Failed Unibus Address
>>> Register when the PDP11 couldn't have a SEX instruction (replaced with
>>> Sign ExTend (SXT)  -- the PDP11/34 still had the SEX Multiplexer on the
>>> board.
>> 
>>       Maybe, the B was missed.
>> 
>>       These days, someone might have tried for a SEXT instruction or
>> pronouncing "SXT" that way.

>Extended PDP-11 instruction sets included an SOB (subtract one and 
>branch) instruction.  The Motorola MC6809 had a SEX (sign extend) 
>instruction and the RCA 1802 had a SEX (set index register) instruction.

     SOB got mentioned in the Colossal Cave adventure.

>And don't forget the Power PC chip (PPC) instruction EIEIO (enforced 
>in-order execution of I/O.

     I knew about all of these.  I wonder if there are any others.

Sincerely,

Gene Wirchenko

Gene Wirchenko <ge...@telus.net> writes:

> On Sat, 26 May 2018 21:15:30 -0500, Charles Richmond
> <nume...@aquaporin4.com> wrote:
>
>>On 5/26/2018 7:41 PM, Gene Wirchenko wrote:
>>> On Fri, 25 May 2018 15:46:15 -0000 (UTC), pechter@ascii.(none)
>>> (William Pechter) wrote:
>>> 
>>> [snip]
>>> 
>>>> I'm still surprised the VAX 11/780 had the Failed Unibus Address
>>>> Register when the PDP11 couldn't have a SEX instruction (replaced with
>>>> Sign ExTend (SXT)  -- the PDP11/34 still had the SEX Multiplexer on the
>>>> board.
>>> 
>>>       Maybe, the B was missed.
>>> 
>>>       These days, someone might have tried for a SEXT instruction or
>>> pronouncing "SXT" that way.
>
>>Extended PDP-11 instruction sets included an SOB (subtract one and 
>>branch) instruction.  The Motorola MC6809 had a SEX (sign extend) 
>>instruction and the RCA 1802 had a SEX (set index register) instruction.
>
>      SOB got mentioned in the Colossal Cave adventure.
>
>>And don't forget the Power PC chip (PPC) instruction EIEIO (enforced 
>>in-order execution of I/O.
>
>      I knew about all of these.  I wonder if there are any others.

Harris /6 had a Set E to X (SEX) instruction.  Since I first encountered
the instruction when I was 21 years old, I was really amused by it.