> The phototypesetter version of Unix was V7.
I'm not sure of what's being said here. Manuals from
the 4th edition on were phototypeaet, first on a
CAT and later a Linotron (if I remember the name right).
Doug
Hi all, I just receivd this e-mail from Will Senn who has just joined
the TUHS mailing list:
----- Forwarded message from Will Senn -----
Hi,
I am conducting research on older UNIX operating systems and came
across a letter from Richard Wolf to Ian Johnstone, dated Feb 5, 1979.
On p. 29 of the AUUGN, Volume 1 number 3, Mr. Wolf refers to a set of
101 fixes for research version 6. In my research, I am currently using
v6 and wondered if you knew where I might find the fixes or if the
bits are known to exist?
Kind Regards,
Will
----- End forwarded message -----
Will, there was a "50 bugs" tape for 6th Edition Unix that was "released"
to Unix owners in a very interesting distribution method: see
http://www.groklaw.net/articlebasic.php?story=20060616172103795
You can find it in the Unix Archive. Look in Applications/Spencer_Tapes/unsw3.tar.gz. It is the file usr/sys/v6unix/unix_changes.
Does anybody know of something which could be described as "101 fixes for
research version 6"? The phototypesetter version of Unix was V7.
Cheers all and welcome to the list Will.
Warren
https://groups.google.com/d/msg/net.unix/Cya18ywIebk/2SI8HrSciyYJ
Apparently the 8th Edition shell had the ability to export functions via
the environment.
I'm wondering - were there (are there?) any other shells other than bash
that picked up this feature? How was it implemented, considering this
was the cause of the "Shellshock" vulnerability?
I was amused to see it come up in one of the olduse.net newsgroups I've
been following.
Interestingly, the SysIII version of cut.c does not have the line
mentioned here. That's because it doesn't initialize _any_ of the flag
variables. The line was added some time between then and SysV, and that
is the _only_ significant change between the SysIII and pdp11v versions.
https://groups.google.com/d/msg/net.bugs.usg/iAkgNVBJNSo/PgXAC2vi044J
Hi,
I'm struggling on reimplementing the C code for the link()
syscall.
Usually on SYSIII and V7 you have something like:
link()
{
register struct inode *ip, *xp;
register struct a {
char *target;
char *linkname;
} *uap;
[...]
u.u_dirp = (caddr_t)uap->linkname;
[...]
}
The problem now on my system is, u_dirp in the user struct
is saddr_t (*long) and not caddr_t (*char) and I wonder how
I have to assign uap->linkname.
The original ASM code looks like:
_link::
{
dec fp,#~L2
ldm _stkseg+4(fp),r8,#6
ldl rr8,_u+36
[...]
ldl rr2,rr8(#4)
ldl rr4,rr2
and r4,#32512
ldl _u+78,rr4
[...]
I had the same problem already 7 years ago but didn't came up
with a solution back then.
http://home.salatschuessel.net/quest/problems.php
What came to my mind in the meantime is the following and maybe
someone can check if this is right:
1. _u+78 (u.u_dirp) contains a pointer - so what is assigned
here in ASM is a memory address.
2. The memory notation for accessing segmented data on Z8001
seems to be 0xSS00XXXX where SS is the segment number up
to 127 and XXXX is the relative address in that segment.
3. This means ANDing 0xSS00 with 0x7F00 means to strip out
all invalid data from the segment-position of the address,
to make sure it can only be between 0 and 127 (0x0000 and
0x7F00).
I wonder how the assignment of uap->linkname to u.u_dirp has
to be done correctly?!
I see http://archive.org/details/BillJoyInterview but the source is
unknown. Does anyone know who conducted this interview or where it came
from? (I tried to contact the archive years ago but didn't hear back.)
Most of the stories I have alternative sources for but I'd like to cite
some of this content in a book I am authoring.
Also it doesn't seem to have a starting place. It appears the beginning
of the interview is missing. (Also it has eight sections marked with
"[Skipped portion you requested.]" and 27 page breaks.)
It appears it may have been OCR'd (Exacfiy = Exactly, correcfiy =
correctly, f'mally = finally, f'md = find, f'n'st = first, llliac =
ILLIAC, Riogin = Rlogin, HTrP: = HTTP: and many other OCR-like typos),
plus misspelled names where the originally typed wrong (so I assume the
transcriber wasn't directly related to this story, like deck = DEC,
Favory = Fabry, Gerwitz = Gurwitz, "E-bid(?) ASCH" = maybe EBCDIC to
ASCII).
If anyone knows the source for this interview or a proper bibtex entry
for it, I'd appreciate it.
Howdy,
I'm the secretary of the Atlanta Historical Computing Society, and a lurker
here on the TUHS list.
We're starting our process of looking for speakers at our upcoming VCF SE
4.0. It'll be April 2nd and 3rd 2016
in the Atlanta area. Since I've enjoyed reading and hearing about all the
UNIX history on this list,
I was wondering if anybody here might be willing to speak at our event.
It seems there is a good
deal of history that is captured in the minds of the members of this
list... which might make a number
of good presentations.
We're open on ranges of topics. We've had many different people speak...
the first editor of Byte,
the artist who did the covers of many Byte magazines, Jason Scott from
archive.org, some early SWTPC
engineers, some early Apple engineers including Daniel Kottke. We also
have members from the
various Vintage Computer groups from around the U.S. speak (and of course
some local members),
and some University Archivists who are starting to have to deal with old
media. This year we will have
Jerry Manock (the designer from Apple who established their design
group...designed cases for Mac, etc.)
as one speaker.
We love to learn about the history, esp. from the folks who lived it. I am
just slightly too young to have
been there (was born in '65) but always enjoy the talks. We can
accommodate from a 30 min talk to
an hour. We have a professional sound set up and stage. We have a
co-sponsor, the Computer
Museum of America that is being established in the area as well. We have
between 5 and 10 slots to fill.
We aren't a large group, but we do have a limited budget to assist with
travel, lodging, etc. We can handle
"nice" but not the Ritz :-)
If anybody is interested, please contact me and I can provide further
details. And if you'd be interested
but can't make this year, please still contact me, maybe we can work
something out in the future.
Thanks!
Earl Baugh
Secretary
Atlanta Historical Computing Society.
Hi,
does someone know where "u" is defined on SYSIII or V7?
sys/user.h states:
extern struct user u;
But I wonder where it is defined? On ZEUS I have u.o but I'm
not able to correctly disassemble it. Right now I'm guessing
that it should be something like:
u module
$segmented
$abs %F600
global
_u array [%572 byte]
end u
But the resulting object (u.o.hd) does not match 100% the existing
u.o on the system (u.o.orig.hd).
--- u.o.orig.hd 2008-05-16 21:52:12.000000000 +0200
+++ u.o.hd 2008-05-16 21:52:16.000000000 +0200
@@ -3,6 +3,6 @@
00000020 00 00 00 01 00 00 00 00 01 00 00 00 00 00 00 00
|................|
00000030 00 00 00 02 00 00 00 00 00 00 00 00 1e 00 75 5f
|..............u_|
00000040 70 00 00 00 00 00 01 00 00 00 1e 01 75 5f 64 00
|p...........u_d.|
-00000050 00 00 00 00 3e 00 f6 00 61 3e 5f 75 00 00 00 00 |....>..a>_u....|
+00000050 00 00 00 00 01 00 f6 00 61 01 5f 75 00 00 00 00 |.......a._u....|
00000060 00 00 |..|
00000062
iPhone email
> On Nov 13, 2015, at 2:38 PM, Brantley Coile <brantleycoile(a)icloud.com> wrote:
>
> For performance reasons an assembly symbol "u" was defined to be a fixed address. That allowed us to use constructions like u.u_procp to generate a single address. It was very fast. Does this help?
>
> iPhone email
>
>> On Nov 13, 2015, at 2:33 PM, Oliver Lehmann <lehmann(a)ans-netz.de> wrote:
>>
>>
>> Oliver Lehmann <lehmann(a)ans-netz.de> wrote:
>>
>>> u module
>>> $segmented
>>> $abs %F600
>>>
>>> global
>>>
>>> _u array [%572 byte]
>>>
>>> end u
>>
>> By any way - is here someone on the list understanding Z8000 PLZ/ASM? ;)
>>
>> The problem is, that "u" must be available in the address space on this
>> location for the kernel to function correctly:
>>
>> # define UBASE 0x3E00F600 /* kernel virtual addr of user struct */
>>
>> And with the above ASM code, it is placed on 0x0100F600. I also tried
>> of course $abs 0x3E00F600 but it makes no difference. It is always
>> placed at 0x0100F600 and I have zero clue why
>>
>> the original object from the system:
>>
>> #67 nm /usr/sys/conf/u.o
>> 3e00f600 A _u
>> 01000000 s u_d
>> 0000 s u_p
>>
>>
>> my object generated from my u.s:
>>
>> #68 nm u.o
>> 0100f600 A _u
>> 01000000 s u_d
>> 0000 s u_p
>>
>> Somehow I need to get the address right.... This is why I wanted to
>> look up how the original SYSIII or V7 was doing it (even if the asm
>> would be of course completely different).
>> _______________________________________________
>> TUHS mailing list
>> TUHS(a)minnie.tuhs.org
>> https://minnie.tuhs.org/mailman/listinfo/tuhs
I'm not sure how old cut is, but a quick look at the code gave me the
idea it could be backported to V7, as I'm fairly sure that cut wasn't
in V7.
It doesn't look like it needs a lot of stuff, just fclose, puts, do
and while loops. Even a v6 or v5 backport doesn't seem too difficult.
Mark
