Hello.
I have just finished porting diction(1) and style(1) from 2.11BSD
to the NetBSD operating system. Those utilities are a part of the
AT&T Documenter's Workbench (DWB), and are not available on the v7
and 32V UNIX releases.
I asked to the people of the NetBSD Foundation about the possibility
of adding those commands to the base system (as a part of the tarball
with documentation tools) but they think that it is not possible,
as a consequence of a licensing issue. I supposed that all the
software provided in the 2.11BSD was under a BSD license, but it
looks like 2.11BSD is a closed source release.
Can someone, please, helping me on this matter? What should I do?
Should I just drop this software?
Cheers,
Igor.
--
Igor Sobrado, UK34436 - sobrado(a)acm.org
> I am fairly sure that 4.2BSD had manual pages for mmap, but it didn't
> work.
Right. Joy left Berkeley and joined Sun and the work got done at Sun.
I'm pretty sure that SunOS 4.0 was the first release with mmap working
as it was described. I was at Sun for the 4.1 release; 4.0 was the new
VM system, and it wasn't "new" like "we changed some stuff", it was new
as in everything was rewritten. The 4.0 VM system had segmap, read/write
were implemented with segmap in the kernel (you did a read, the kernel
mapped page, started a bcopy and would fault on itself if the page wasn't
there or had no TLB entry). Etc. I have postscript of the papers on
that, still very good reading if someone wants them.
--
---
Larry McVoy lm at bitmover.comhttp://www.bitmover.com/lm
Hi all,
I just received a query: did SunOS 3 have a working mmap(2)? My
vague memory says no, but I don't have access to a 3.5 box any more to
find out. Can anybody help out here?
Warren
Has anyone tried to do such a thing? Would anybody care?
--
David Evans (NeXTMail/MIME OK) dfevans(a)bbcr.uwaterloo.ca
Ph.D. Candidate, Computer/Synth Junkie http://bbcr.uwaterloo.ca/~dfevans/
University of Waterloo "Default is the value selected by the composer
Ontario, Canada overridden by your command." - Roland TR-707 Manual
> From: asbesto <asbesto(a)freaknet.org>
> To: tuhs(a)tuhs.org
> Subject: [TUHS] PDP11/34 boot problems, here i am again :)
>
> well, i think now we have a more complete knowledge of the REAL
> problem !
>
> the M7891 board (128K x 18 bit MOS MEMORY MODULE) have the D2 red=20
> led light turned ON when turning on the CPU !
>
> this means PARITY ERROR on this board :(
>
> checking the board we found 2 problems:
>
> 1) a 74LS175 chip named E15 on our schematic diagram, that seem
> phisically BROKEN on an edge (there is a fessure on the plastic
> DIP package). i can't change it now because i don't have a=20
> soldering station here to do a nice job, but looking the chip i
> think it may work...
While you probably _do_ have a real hardware problem with the broken
IC, I think that the red Parity Error light on first turn-on is normal
behavior. The MOS memory comes up with random values, and about half
of them will have the wrong parity. Some software routine must turn
off parity error detection and write a known data pattern (all 0's) to
each memory location. I don't remember whether this is something that
is done by the boot ROM of an 11/34.
carl
--
carl lowenstein marine physical lab u.c. san diego
clowenst(a)ucsd.edu
"asbesto" wrote:
> 1) a 74LS175 chip named E15 on our schematic diagram, that seem
> phisically BROKEN on an edge (there is a fessure on the plastic
> DIP package). i can't change it now because i don't have a
> soldering station here to do a nice job, but looking the chip i
> think it may work...
I never remove IC's in *one* go. The chances that you damage the
multi-layer board beyond repair are real. This is what I do.
I use a dremel tool (small motor with sharp rotating blade) to
cut the pins of the IC one by one.
Don't use a cutting tool to cut the pins because the side force
might push the remainder of the pin through the solder joint
thus damaging the board.
After you have cut all the pins the IC just falls of the board.
Now, you can use a fine hot soldering iron and remove the pins
one by one use a pair of squeezers.
good luck with your repairs,
- Henk.
well,
some months ago i asked for help booting a pdp11/34 here at
freaknet medialab :)
well, i think now we have a more complete knowledge of the REAL
problem !
the M7891 board (128K x 18 bit MOS MEMORY MODULE) have the D2 red
led light turned ON when turning on the CPU !
this means PARITY ERROR on this board :(
checking the board we found 2 problems:
1) a 74LS175 chip named E15 on our schematic diagram, that seem
phisically BROKEN on an edge (there is a fessure on the plastic
DIP package). i can't change it now because i don't have a
soldering station here to do a nice job, but looking the chip i
think it may work...
2) a 5 Kohm 4-resistor bridge named R22 on our diagram, that is phisically
BROKEN. this bridge give +5V on signals named DATA OC L, CSR OC L, OC L
and X ADD OC L. i changed it with a 4.7Kohm 4-resistor bridge, without
any result. (maybe the 74ls175 is really broken :)
an other ipothesys may be: some electrolitic capacitor in short circuit.
we had this problem on a decwriter III ! :)
the real problem is: if we aren't able to repair the M7891 board, where
can we find a "new" one ???
can somebody help us ? it's a shame for us to have our pdp11/34 offline :((
any help is appreciated ! *:)
--
[asbesto : freaknet medialab : radio#cybernet : GPG key on keyservers]
[ MAIL ATTACH, SPAM, HTML, WORD, and msgs larger than 95K > /dev/null ]
[http://www.freaknet.org/asbesto :::::: http://kyuzz.org/radiocybernet]
Hi All,
I know that this isn't pdp related but the people are here who know :-). Is there
an available unix that supports lance and dssi on a VAX 3400 and/or is there anyone
working on this.
Regards
Robin
This email and any attachments are confidential and intended for the addressee
only. If you are not the named recipient, you must not use, disclose, reproduce,
copy or distribute the contents of this communication. If you have received this
in error, please contact the sender and then delete this email from your system.
while trying to build Franz Lisp (from 4.3 BSD) on VAX/ULTRIX 4.5,
I noticed its peculiar list of supported platforms:
use: lispconf type
where type is one of
vax_4_1 vax_4_1a vax_4_1c vax_4_2 vax_4_3
vax_eunice_vms
sun_4_1c sun_unisoft dual_unisoft pixel_unisoft
sun_4_2beta lisa_unisys3 mc500_2_0
I was especially surprised by "lisa_unisys3". is that Unisoft SysIII
for the Apple Lisa?! and does anyone know what
{dual,pixel}_unisoft and mc500_2_0 mean?
--
If I travelled to the end of the rainbow
As Dame Fortune did intend,
Murphy would be there to tell me
The pot's at the other end.
Lars Buitinck
I'll have to try this with the RQDX3 as primary and the SCSI as secondary.
Maybe BSD is smart enough to do it right. In any case, I have the source for
the BSD boot code, and I can fix it. It will be a pain, though, having to
type the alternate address every time I boot BSD. I'd probably have to
restructure /dev and /etc/fstab also, and who knows what else. Maybe it
would be easier to change the jumpers if I needed to run RT11. I don't use
RT11 that much, but I'd like to have it available.
--
Jonathan Engdahl
http://users.safeaccess.com/engdahl
"The things which are seen are temporary,
but the things which are not seen are eternal." II Cor. 4:18
----- Original Message -----
From: "Fred N. van Kempen" <Fred.van.Kempen(a)microwalt.nl>
To: "Jonathan Engdahl" <j.r.engdahl(a)adelphia.net>
Sent: Wednesday, April 02, 2003 5:58 AM
Subject: RE: [pups] booting RT11 from alternate controller
Jonathan,
> I have a PDP-11/53 with a SCSI controller at 172150, and an
> RQDX3 at 172144.
This works for the ROM, but most PDP-11 operating systems will
refuse to boot from anything but the "default" controller of
any kind, meaning, an MSCP controller it will only accept at
172150. The OS itself can deal with them, but not so for the
boot-level code that loads them.
I have tried similar setups with an 11/83 using an ESDI disk
controller at MSCP #0 (doing KDA50 emu), and an RQDX3 at
MSCP #1 (just for the floppies, indeed) and that didnt work
either, with RT11, MicroRSX and Ultrix.
--f
