[pups] 2.11BSD Patch 446+447; fixes for ulrem,umount,tar,tcsh,ps,vmstat,apropos,pstat,rk

[pups] 2.11BSD Patch 446+447; fixes for ulrem,umount,tar,tcsh,ps,vmstat,apropos,pstat,rk

[Walter F. Mueller]

A note to all 2.11bsd users:
Over the past 2 years several bug fixes for 2.11BSD accumulated, and over
xmas break I finally found the time to communicate them to Steven Schultz.
Steven was so kind to package them into two new patch files
    446   issued December 27, 2008
    447   issued December 31, 2008

Together, the patches address the following points
  - ulrem.s: the unsigned long modulo operator (%) was broken in libkern
  - umount: returned inverted exit codes (1 for success, 0 for failure)
  - tar: core dumped when a whole /usr tree was archived
  - tcsh: the time buildin function printed some erroneous or zero statistics
  - ps: core dumped when '-t' option was used with no further argument
  - apropos: core dumped when 2 or more arguments were given
  - vmstat: wrong normalization for some fields
  - several issues around the rk disk driver
    - no rk root attach function
    - no rk BOOTDEV support
    - incorrect UCB_METER code (vmstat/iostat never showed any rk activity)
    - autoconfig left the RK11 controller in an error state
  - pstat: added additional options to access more kernel data structures
    - new -c option, dumping the coremap
    - new -m option, dumping the ub_map (UNIBUS map)
    - new -b option, dumping the buffer pool table
    - change -s output, gives now full table dump
    - adapt the info's displayed by -T
  - some documentation corrections (vmstat, pstat, tcsh)

Note: In case you wonder, as I did, why 211BSD survived 20 years with a
       broken unsigned long % operator:
       - only the non-FPP libkern implementation was affected
       - the kernel simply doesn't have any unsigned long modulo's :)
       - apparently only standalone mkfs after patch 434 was compromised

For the full story of all the above consult the header of the patch files.

The patch files are available from moe.2bsd.com and ftp.wx.gd-ais.com.
Note, that Steven changed the packaging some time ago, the patches are
now packed in bzip'ed tarballs in groups of ten patches. So you'll have
to look into
   ftp://moe.2bsd.com/pub/2.11BSD/440-447.tar.bz2
   ftp://ftp.wx.gd-ais.com/pub/2.11BSD/440-447.tar.bz2


     With best regards,
         Walter Mueller

[pups] jove editor under 2.11BSD and cursor keys

[Walter F. Mueller]

Hello,

I'm using the jove editor under 2.11BSD, the jove release is
from 1988. It works just fine, except for the cursor keys.
Even though the ansi-codes function is properly bound,
'ESC x describe-bindings' shows:

     ESC [  ansi-codes

I get whenever I hit one of the cursor keys the message

     [ESC O unbound]

TERM is set to vt100, termcap is ok, and the xterm used is
started with -ti vt100. vi for example works and accepts the
cursor keys, a dump of the chars emitted by xterm show that
the proper \[[A ect sequence indeed arrives.

Any help or hint on how to get this to work is very much
appreciated.

			With best regards,
				Walter Mueller

[pups] jove editor under 2.11BSD and cursor keys

[Johnny Billquist]

Walter F. Mueller wrote:
> Hello,
> 
> I'm using the jove editor under 2.11BSD, the jove release is
> from 1988. It works just fine, except for the cursor keys.
> Even though the ansi-codes function is properly bound,
> 'ESC x describe-bindings' shows:
> 
>      ESC [  ansi-codes
> 
> I get whenever I hit one of the cursor keys the message
> 
>      [ESC O unbound]
> 
> TERM is set to vt100, termcap is ok, and the xterm used is
> started with -ti vt100. vi for example works and accepts the
> cursor keys, a dump of the chars emitted by xterm show that
> the proper \[[A ect sequence indeed arrives.
> 
> Any help or hint on how to get this to work is very much
> appreciated.

Please note the difference between "<ESC>[" and "<ESC>O"... :-)

To give you a little more help: someone or something is changing your 
terminal to have application cursor keys.
(And to point out what should be obvious now: your cursor keys can 
actually send two different kind of codes, depending on a setup parameter.)

	Johnny

[pups] jove editor under 2.11BSD and cursor keys

[Walter F.J. Mueller]

Johnny Billquist wrote:
> Walter F. Mueller wrote:
>> ....
>> I get whenever I hit one of the cursor keys the message
>>
>>      [ESC O unbound]
>... 
> Please note the difference between "<ESC>[" and "<ESC>O"... :-)
> 
> To give you a little more help: someone or something is changing your
> terminal to have application cursor keys.
> (And to point out what should be obvious now: your cursor keys can
> actually send two different kind of codes, depending on a setup parameter.)
> 
>     Johnny

Thanks Johnny, that was exactly the problem. jove sets the terminal
(or the emulator) into 'Application Cursor Key' and 'Application Keypad'
mode. Looking in xterm at the VT Options popup (with CONTROL-MB2) shows
this nicely. Binding the 'ansi-codes' function of Jove 4.9 (that's what
comes with 2.11BSD) to \[O resolves the cursor issue.

What I still don't understand is why jove comes with defaults which
don't work. It puts the cursor and keypad keys into application mode,
which makes perfect sense especially for the keypad, and than looks
for \[[ rather \[O. Probably to make retrocomputing more fun :).


			Thanks and with best regards,	Walter

[pups] jove editor under 2.11BSD and cursor keys

[robinb]

IIRC the version of Jove that is on 2.11 was put on by me back in the late 80s to replace an even earlier version and I used a VT220 at home as opposed to xterm or whatever on a sim.  As a result I was quite happy with using the defaults for whatever was set up for the then available hardware as I used a real PDP with real DEC terminals :-)

Cheers

Robin

PS:  It may have been updated since then I can't really recall.

W.F.J.Mueller at gsi.de wrote:
> Johnny Billquist wrote:
> > Walter F. Mueller wrote:
> >> ....
> >> I get whenever I hit one of the cursor keys the message
> >>
> >>      [ESC O unbound]
> >... 
> > Please note the difference between "<ESC>[" and "<ESC>O"... :-)
> > 
> > To give you a little more help: someone or something is changing your
> > terminal to have application cursor keys.
> > (And to point out what should be obvious now: your cursor keys can
> > actually send two different kind of codes, depending on a setup parameter.)
> > 
> >     Johnny
> 
> Thanks Johnny, that was exactly the problem. jove sets the terminal
> (or the emulator) into 'Application Cursor Key' and 'Application Keypad'
> mode. Looking in xterm at the VT Options popup (with CONTROL-MB2) shows
> this nicely. Binding the 'ansi-codes' function of Jove 4.9 (that's what
> comes with 2.11BSD) to [O resolves the cursor issue.
> 
> What I still don't understand is why jove comes with defaults which
> don't work. It puts the cursor and keypad keys into application mode,
> which makes perfect sense especially for the keypad, and than looks
> for [[ rather [O. Probably to make retrocomputing more fun :).
> 
> 
> 			Thanks and with best regards,	Walter
> _______________________________________________
> PUPS mailing list
> PUPS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/pups
> 

[pups] jove editor under 2.11BSD and cursor keys

[Johnny Billquist]

And most proper emacs (and clone) users don't use the arrow keys, but 
use ^P, ^N, ^F and ^B. So this particular problem don't show. :-)

Jove is actually a pretty nice Emacs clone. I wonder if I should try to 
port it to RSX...

	Johnny

robinb at ruffnready.co.uk wrote:
> IIRC the version of Jove that is on 2.11 was put on by me back in the late 80s to replace an even earlier version and I used a VT220 at home as opposed to xterm or whatever on a sim.  As a result I was quite happy with using the defaults for whatever was set up for the then available hardware as I used a real PDP with real DEC terminals :-)
> 
> Cheers
> 
> Robin
> 
> PS:  It may have been updated since then I can't really recall.
> 
> W.F.J.Mueller at gsi.de wrote:
>> Johnny Billquist wrote:
>>> Walter F. Mueller wrote:
>>>> ....
>>>> I get whenever I hit one of the cursor keys the message
>>>>
>>>>      [ESC O unbound]
>>> ... 
>>> Please note the difference between "<ESC>[" and "<ESC>O"... :-)
>>>
>>> To give you a little more help: someone or something is changing your
>>> terminal to have application cursor keys.
>>> (And to point out what should be obvious now: your cursor keys can
>>> actually send two different kind of codes, depending on a setup parameter.)
>>>
>>>     Johnny
>> Thanks Johnny, that was exactly the problem. jove sets the terminal
>> (or the emulator) into 'Application Cursor Key' and 'Application Keypad'
>> mode. Looking in xterm at the VT Options popup (with CONTROL-MB2) shows
>> this nicely. Binding the 'ansi-codes' function of Jove 4.9 (that's what
>> comes with 2.11BSD) to [O resolves the cursor issue.
>>
>> What I still don't understand is why jove comes with defaults which
>> don't work. It puts the cursor and keypad keys into application mode,
>> which makes perfect sense especially for the keypad, and than looks
>> for [[ rather [O. Probably to make retrocomputing more fun :).
>>
>>
>> 			Thanks and with best regards,	Walter
>> _______________________________________________
>> PUPS mailing list
>> PUPS at minnie.tuhs.org
>> https://minnie.tuhs.org/mailman/listinfo/pups
>>
>