I’ve no intention of selling these items
and am definitely NOT disposing of them yet.
No ‘offers’ please.
In 1977, I took John’s “Operating Systems” course,
and was one of 60-80 students who bought the first print run
of the Commentary.
I’m looking for suggestions of what to do with these three items pictured,
some ideas of what to put in my will or donate before I go.
Warren doesn’t need Yet Another Copy, he has some better copies already :)
They aren’t in pristine condition and I made notes in both books, in pencil at least.
The cover of the red book has slightly deteriorated.
steve j
PS: if the image is stripped by the list, a copy at:
<http://members.tip.net.au/~sjenkin/SteveJ_Lions-Commentary.jpg>
--
Steve Jenkin, IT Systems and Design
0412 786 915 (+61 412 786 915)
PO Box 38, Kippax ACT 2615, AUSTRALIA
mailto:sjenkin@canb.auug.org.au http://members.tip.net.au/~sjenkin
Hello, today I have received an IBM binder from 1974 pertaining to IBM Skylab activities as well as a small IBM SLT, single wide, with four modules on it.
Two of the modules are labeled:
361456
IBM WF
1 03S 215
And the other two are:
361453
IBM 22
1-009 415
From what I could find online, there is a close SLT card with 4 of the 361453's instead of 2, but that doesn't help much. That board is listed as 00211 in the reference this info is from[1]. Faintly on the connector I can make out:
00008 A 0 204 YM
It is very, very faint in places though so that may not be correct. The specific little blocks on the board appear to show up on others, so nothing unheard of, although I wouldn't know where to start on identifying what this does precisely, all I can find are cursory references in a few places to the numbers on the chips re: SLT modules.
- Matt G.
[1] - https://ibm-slt-reference.fandom.com/wiki/SLT_Board_List (why is this a fandom.com wiki...)
P.S. If you or a loved one are in possession of IBM mainframe hardware that would benefit from this SLT board, happy to send it to you, I probably won't do much with it unless I can figure out the pinout and do weird things over GPIO pins from one of my single boards.
Dear Old Farts,
I've written a chat system that relies at its core on UNIX's permission
system.
All the explanations are here:
https://the-dam.org/docs/explanations/suc.html
I thought it would be of interest to the list as it has one foot in the
past (using system primitives from the 70's for access control) and one
foot in the future: (optionally) using GNU Guix's declarative
configuration to create the necessary users, groups, and files.
I know most of you have used (and some maybe still do) talk et al. This
system is even simpler, just a forever loop:
while /usr/bin/true
do
read -r line || exit 0 # EOF
/usr/bin/echo "$(/usr/bin/date --iso-8601=seconds)"\
"$(printf "%-9s" "$(/usr/bin/id --user --name --real)")" \
"$line" >> /var/lib/suc/"$1"
done
I'd be happy to hear any comments or to welcome you on the Dam, where we
test this stuff.
Cheers !
Edouard.
Hi Emanuel,
I believe I may have the install disks for ESIX, SVR4. It actually was distributed in this beautiful box with over 100 5.25” floppy disks.
As things progressed, ESIX was distributed on a streaming tape cartridge. That was so much faster than swapping floppy disks for the install.
The nice thing about the ESIX SVR4 was the documentation. It was essentially the AT&T SVR4 books with a white ESIX cover slapped on it.
If you want to copy the disks and make them accessible to our UNIX community, let me know. Since it’s part of my collection I would ask that you return them to me. Send me an email directly if you’re interested and I will see if I can locate them for you.
Bill Corcoran
> On Jun 11, 2023, at 8:47 AM, emanuel stiebler <emu(a)e-bbes.com> wrote:
> Hi,
> anybody still has the install media for that?
> We used it in the office long ago, but I lost the install disk in my last moving :(
>
> THANKS!
Apropos the ESIX SVR4 distro on floppies or streaming tape mentioned by Bill Corcoran
<https://www.tuhs.org/mailman3/hyperkitty/list/coff@tuhs.org/message/WEJQQCJ…>
In the mid 1980’s I worked for a small Australian outfit that did “Unix”.
One of the things we did was distributing software, which required writing to many media.
There was a very clever script that broke the distribution into many parts, if needed,
to suit the size of the distribution media. [ tape, 3.5” floppy, 2.5” floppy, etc ]
Over the years I’ve tried to recreate a version and not succeeded :(
There was a ‘create the distro’ step of the pipeline which gathered the input,
followed by a loop that used ‘dd’ to block the stream into media-sized parts.
I’ve never figured out how to use ‘dd’ so it returns after a single block is written
doesn’t close the input, killing the pipeline, or cause the rest of the data
to be discarded.
The script let our admin staff reliably create distros on whatever media was requested.
Any suggestions or hints?
I’m thinking this is obvious, but in the man pages i’ve read, not found an answer.
It could be modern versions of ‘dd’ don’t have this behaviour.
cheers
steve
--
Steve Jenkin, IT Systems and Design
0412 786 915 (+61 412 786 915)
PO Box 38, Kippax ACT 2615, AUSTRALIA
mailto:sjenkin@canb.auug.org.au http://members.tip.net.au/~sjenkin
Good afternoon folks, I just wanted to ask if anyone is aware of online marketplaces I should be looking at in my constant scouring for historical documentation materials?
Presently I've got a policy of checking eBay and Biblio pretty regularly for UNIX material, occasionally searching for a few other odds and ends subject-wise, but I'm starting to wonder if there are other avenues flying under my radar where folks might be more likely to be selling for instance 70s and 80s UNIX manuals, paper copies of old standards, hardware docs from IBM and DEC, etc.
If you have any suggestions, especially those that don't require me to setup yet another account to keep track of, I'd surely appreciate it. Also consider this my way of saying if you have something to sell, I'll gladly consider it, although I am being pretty selective on matters of historical/research significance that are currently obscure, so sorry if I won't buy your twelfth copy of KnR C, even if it is signed!
- Matt G.
Hello, I've got a question I'm puzzling on that someone here may have some info on.
Are there any known lists/promo material/price sheets from between 80-83 regarding WECo computing hardware such as the 3B20D and 3B20S? More broadly, is it documented at all what hardware models made it out before the removal of the Bell logo and transition from WECo to AT&T ownership of the 3B and related technologies?
Aside from the cover illustration of a 3B20S on the UNIX 4.1 manual and having seen a MAC-Tutor on eBay once, I can't say I've seen any other WECo branded computation hardware with Bell logos. The only photos I can find of a 3B20D are a later AT&T branded issue.
Any leads? Would it have just been BellMAC stuff and 3B20 systems before the change in logo? Based on the manual I recently received, the 3B5 may have also made it out during the WECo period but after dropping the Bell logo, somewhere between the consent degree being produced and the completion of divesting WECo.
- Matt G.
P.S. In the bigger picture, I'm slowly starting to aggregate info together on Bell/WECo's computer hardware activities tangential to but distinct from UNIX developments. Stuff like the 3B computers, BellMAC stuff, etc. If there's already a community/resources in this focused area I'd happily divert those efforts to a more focused collective.
Good afternoon everyone. I've been thinking about the color/contrast landscape of computing today and have a bit of a nebulous quandary that I wonder if anyone would have some insight on.
So terminals, they started as typewriters with extra steps, a white piece of paper on a reel being stamped with dark ink to provide feedback from the machine. When video terminals hit the market, the display was a black screen with white, orange, green, or whatever other color of phosphor they bothered to smear on the surface of the tube. Presumably this display style was chosen as on a CRT, you're only lighting phosphor where there is actually an image, unlike the LCD screens of today. So there was a complete contrast shift from dark letters on white paper to light letters on an otherwise unlit pane of glass.
Step forward to graphical systems and windows on the Alto? Light background with dark text.
Windows on the Macintosh? Light background with dark text.
Windows on MS Windows? Light backgrounds with dark text.
Default HTML rendering in browsers? Light backgrounds with dark text.
Fast forward to today, and it seems that dark themes are all the rage, light characters on an otherwise dark background. This would've made so much sense during the CRT era as every part of the screen representing a black pixel is getting no drawing, but when CRTs were king, the predominant visual style was dark on light, like a piece of paper, rather than light on dark, like a video terminal. Now in the day and age of LCDs, where every pixel is on regardless, now we're finally flipping the script and putting light characters on dark backgrounds, long after any hardware benefit (that I'm aware of) would be attained by minimizing the amount of "lit surface" on the screen.
Anyone know if this has all been coincidental or if the decision for graphical user interfaces and such to predominantly use white/light colors for backgrounds was a relatively intentional measure around the industry? Or is it really just that that's how Xerox's system looked and it was all domino effect after that? At the end of the day I'm really just finding myself puzzling why computing jumped into the minimalism seen on terminal screens, keeping from driving CRTs super hard but then when GUIs first started appearing, they didn't just organically align with what was the most efficient for a CRT. I recognize this is based largely in subjective views of how something should look too, so not really expecting a "Person XYZ authoritatively decided on <date> that GUI elements shall overwhelmingly only be dark on light", just some thoughts on how we got going down this path with color schemes in computing. Thanks all!
- Matt G.
Apologies to TUHS - other than please don't think Fortran did not impact
UNIX and its peers. We owe that community our jobs, and for creating the
market in that we all would build systems and eventually improve.
Note: I'm CCing COFF - you want to continue this...
On Mon, Jun 12, 2023 at 5:39 PM G. Branden Robinson <
g.branden.robinson(a)gmail.com> wrote:
> It's an ill wind that blows a Fortran runtime using the same convention.
>
Be careful there, weedhopper ... Fortran gave a lot to computing
(including UNIX) and frankly still does. I did not write have too much
Fortran as a professional (mostly early in my career), but I did spent 50+
years ensuring that the results of the Fortran compiler ran >>really well<<
on the systems I built. As a former collegiate of Paul W and I once said,
"*Any computer executive that does not take Fortran seriously will not have
their job very long.* It pays our salary."
It's still the #1 language for science [its also not the same language my
Father learned in the late 50s/early 60s, much less the one I learned 15
years later - check out: In what type of work is the Fortran Programming
Language most used today
<https://www.quora.com/In-what-type-of-work-is-the-Fortran-programming-langu…>
, Is Fortran still alive
<https://www.quora.com/Is-Fortran-still-alive/answer/Clem-Cole>, Is Fortran
obsolete <https://www.quora.com/Is-Fortran-obsolete/answer/Clem-Cole>
FWIW: These days, the Intel Fortran compiler (and eventually the LLVM one,
which Intel is the primary developer), calls the C/C++ common runtime for
support. Most libraries are written in C, C++, (or assembler in some very
special cases) - so now it's C that keeps Fortran alive. But "in the
beginning" it was all about Fortran because that paid the bills then and
still does today.
ᐧ
Sorry this is very tangential to the list but figured some folks here might have some knowledge just what with our proximity to Western Electric lore by way of UNIX. Still, didn't feel UNIX-y at all so COFF instead of TUHS.
Anywho, spotted something particularly interesting in my rounds of checking for eBay postings: https://www.ebay.com/itm/385635333789?hash=item59c9a8369d:g:8TMAAOSw3kJkblS…
After the link is an auction for a police badge, with the word "Police" on it, but also labeled as "Western Electric, Co.", along with the seal of North Carolina. I did a bit of searching and while I could find plenty of WECo badges labeled security, plant protection, etc. I can't find any others specifically using the word "Police". The latter term has governmental implications that other terms do not, and it's got me kinda curious if there was ever a time WECo or the Bell System at large actually had authority from the government to accredit their own personnel as "police" and not simply as security, guards, etc. and what sort of legal statutes would be involved. I'm not interested in purchasing this either way, but it'd be amusing if this is some facsimile, I don't know that reporting it as such would bubble up through eBay's systems though.
Also given the sensitivity of discussions of law enforcement these days, I'm simply interested in whether there is any accessible documentation or history of WECo and/or Bell's relationship with formal U.S. law enforcement agencies, not any discussion on the propriety of this. If you want to chat philosophy, email me privately, but that sort of public discussion is too sensitive for me to want to wade into in mixed company.
- Matt G.
Useful Shell Scripts Network Connections , Logins and
*Block hacking attempts*
[image: image.png]
#1. See how many remote IPs are connecting to the machine
See how many remote IPs are connecting to the local machine (whether
through ssh or web or ftp ) Use netstat — atn to view the status of all
connections on the machine, — a to view all, -T Display only tcp connection
information, ≤ n Display in numeric format Local Address (the fourth column
is the IP and port information of the machine) Foreign Address (the fifth
column is the IP and port information of the remote host) Use the awk
command to display only the data in column 5, and then display the
information of the IP address in column 1 Sort can be sorted by number
size, and finally use uniq to delete the redundant duplicates and count the
number of duplicates
netstat -atn | awk '{print $5}' | awk '{print $1}' | sort -nr | uniq -c
#2. Detect file consistency in specified directories of two servers
Detect the consistency of files in specified directories on two servers, by
comparing the md5 values of files on two servers to detect consistency
#!/bin/bash
dir=/data/web
b_ip=xxx.xxx.xxx.xxx
#Iterate through all the files in the specified directory and use them
as arguments to the md5sum command to get the md5 values of all the
files and write them to the specified file
find $dir -type f|xargs md5sum > /tmp/md5_a.txt
ssh $b_ip "find $dir -type f|xargs md5sum > /tmp/md5_b.txt"
scp $b_ip:/tmp/md5_b.txt /tmp
#Compare file names as traversal objects one by one
for f in `awk '{print 2} /tmp/md5_a.txt'`
do
#The standard is machine a. When machine b does not exist to traverse
the files in the object directly output the non-existent results
if grep -qw "$f" /tmp/md5_b.txt
then
md5_a=`grep -w "$f" /tmp/md5_a.txt|awk '{print 1}'`
md5_b=`grep -w "$f" /tmp/md5_b.txt|awk '{print 1}'`
#Output the result of file changes if the md5 value is inconsistent
when the file exists
if [ $md5_a != $md5_b ]
then
echo "$f changed."
fi
else
echo "$f deleted."
fi
done
#3. Detect network interface card traffic and record it in the log
according to the specified format
Detect the network interface card traffic and record it in the log
according to the specified format, and record it once a minute. The log
format is as follows:
- 2019–08–12 20:40
- ens33 input: 1234bps
- ens33 output: 1235bps
#!/bin/bash
while :
do
LANG=en
logfile=/tmp/`date +%d`.log
#Redirect the output of the following command execution to the logfile log
exec >> $logfile
date +"%F %H:%M"
#The unit of traffic counted by the sar command is kb/s, and the log
format is bps, so it should be *1000*8
sar -n DEV 1 59|grep Average|grep ens33|awk '{print
$2,"\t","input:","\t",$5*1000*8,"bps","\n",$2,"\t","output:","\t",$6*1000*8,"bps"}'
echo "####################"
#Because it takes 59 seconds to execute the sar command, sleep is not required
done
#4. Iptables automatically blocks IPs that visit websites frequentlyBlock
more than 200 IP accesses per minute
- According to Nginx
#!/bin/bash
DATE=$(date +%d/%b/%Y:%H:%M)
ABNORMAL_IP=$(tail -n5000 access.log |grep $DATE |awk
'{a[$1]++}END{for(i in a)if(a[i]>100)print i}')
#First tail prevents the file from being too large and slow to read,
and the number can be adjusted for the maximum number of visits per
minute. awk cannot filter the log directly because it contains special
characters.
for IP in $ABNORMAL_IP; do
if [ $(iptables -vnL |grep -c "$IP") -eq 0 ]; then
iptables -I INPUT -s $IP -j DROP
fi
done
- Connection established over TCP
#!/bin/bash
ABNORMAL_IP=$(netstat -an |awk '$4~/:80$/ &&
$6~/ESTABLISHED/{gsub(/:[0-9]+/,"",$5);{a[$5]++}}END{for(i in
a)if(a[i]>100)print i}')
#gsub is to remove the colon and port from the fifth column (client IP)
for IP in $ABNORMAL_IP; do
if [ $(iptables -vnL |grep -c "$IP") -eq 0 ]; then
iptables -I INPUT -s $IP -j DROP
fi
done
Block IPs with more than 10 SSH attempts per minute
- Get login status via lastb
#!/bin/bash
DATE=$(date +"%a %b %e %H:%M") #Day of the week, month, and hour %e
displays 7 for single digits, while %d displays 07
ABNORMAL_IP=$(lastb |grep "$DATE" |awk '{a[$3]++}END{for(i in
a)if(a[i]>10)print i}')
for IP in $ABNORMAL_IP; do
if [ $(iptables -vnL |grep -c "$IP") -eq 0 ]; then
iptables -I INPUT -s $IP -j DROP
fi
done
- Get login status from logs
#!/bin/bash
DATE=$(date +"%b %d %H")
ABNORMAL_IP="$(tail -n10000 /var/log/auth.log |grep "$DATE" |awk
'/Failed/{a[$(NF-3)]++}END{for(i in a)if(a[i]>5)print i}')"
for IP in $ABNORMAL_IP; do
if [ $(iptables -vnL |grep -c "$IP") -eq 0 ]; then
iptables -A INPUT -s $IP -j DROP
echo "$(date +"%F %T") - iptables -A INPUT -s $IP -j DROP"
>>~/ssh-login-limit.log
fi
done
Might come in handy...
--
End of line
> On May 11, 2023, at 12:38 PM, Clem Cole <clemc(a)ccc.com> wrote:
>
> I'm one of the many legacies of the over 50 years of teaching by Dan Siewiorek -- remember in the 1970s there was an infamous band (named after an interesting object BTW).
Ah, so Dan Siewiorek is Steely Dan IV, _not_ from Yokohama. Or perhaps Steely Dan V, from neither Yokohama nor Annandale-on-Hudson.
Adam
On 2023-05-04 10:58, Ralph Corderoy wrote:
> Twitter co-founder Jack Dorsey has been using it for a while.
Not only has he been using it for a while already, but he's also
contributing code and funding the developers of some projects (clients
and relays) with 14 BTC through fiatjaf, Nostr creator.
> I suggest any further chat about Nostr moves to coff(a)tuhs.org.
CC'd.
Cheers.
Ángel
I've just today received a COBOL manual I ordered to find quite the nice surprise.
The manual itself is: "IBM OS Full American National Standard COBOL". It is listed as File No. S360-24, Order No. GC28-6396-4. On the back of the first page this is noted as the "Fifth Edition (September 1973)" and that the current edition "is a reprint of GC28-6396-3, incorporating changes released in TNL GN28-1002." Copyright year chain ends at 1972.
However, in addition to this manual are three addenda:
The first is a memo from Tim S. "Systems Analyst", addressed to and cc'd to a few folks, providing an up-to-date listing (as of March 12*, 1976) of IBM System Reference Library materials. The attachment includes, among other things, documents for S/360, S/370, OS/360, BOS/360, OS/VS, and programming and diagnostic utilities. Each reference includes a volume number and an "SRL", the definition I couldn't find, but presumably just a catalog number of some kind.
The second is a scan of a 31 page, hand-written document titled "COBOL Compiler Release 2.2" providing information on the "March 11, 1979, Release 2.2 of the COBOL compiler...IBM's implementation of the ANSI 1974 Standard for COBOL. The previous Release 1.1 implemented the 1968 ANSI Standard." The document goes on to detail numerous changes between these revisions.
Lastly is a Technical Newsletter bearing the same File and Order numbers as the full manual, but with a date of May 15, 1974 and newsletter number of GN28-1048. This page bears a copyright chain out to 1974 and is simply a set of replacement pages for the manual, as was common at the time. The text indicates that all changes are denoted with a vertical bar printed to the left of the change, so this essentially is a diff between the Fifth Edition manual above and...wait for it..."Fourth Edition (May 1972); Fifth Edition (September 1973)". Strangely the copyright notice on the back still indicates the same edition, but adds reference back to the Fourth Edition as well. Strange, one of life's little mysteries? In any case, the copyright chain here is only out to 1973. Never sure how much that means at any given instant. In any case, I couldn't find any evidence in the manual-proper of previous such updates being applied, in other words, no vertical bars spotted flipping through the pages at least.
Both the replacement pages and the catalog are still stapled together, and the manual-proper still contains the pages (that I spot checked) slated for replacement. It seems the original was even bound itself at one point, indicated by the ghost of a glued spine still lingering on the end of the pages, but both the replacement pages and manual itself also have 3-hole punches and are bound in an Acco binder. If the manual had a true cover, it's long gone.
Figured I'd share some of those details in case anything in this is in want of further illumination. For the record, the Sixth and Seventh editions of this same document appear to be on archive.org. I haven't plumbed their depths searching for evidence of aforementioned diff pages, they're probably just scans of complete published copies.
So all of this for me at least begs the question, is there any sort of equivalent to TROFF sources for documents from the Big Blue? Truth be told, I only ordered this to have a paper COBOL reference on hand, if one should ever need such a thing. If there are such document sources, I'd happily add "patching" them to produce a restoration of this to my studies. At the very least the two smaller addenda will get a scan here pretty soon.
- Matt G.
P.S. While my main focus is Bell UNIX documentation, I do peek around for stuff like this time to time, but I'm much less inclined to spring for something without some functional value to me. That said, I'm looking for documents all the time, so if anyone has any tips on stuff that isn't well preserved in the public record that I should add to my searches time to time, I'm happy to keep an eye out. I'm coming to quite enjoy finding things and getting them on the record.
Apologies, this was meant to go to another mailing list. I also posted
to COFF, so send any follow-ups there.
John Cowan wrote:
> I attended CRWU in 1975-76 and programmed the 1108 (abs, alphabetic, arccos,
> arcsin, arctan) with punch cards so I am definitely interested if the
> material is still available.
Thank you, I'll fill you in on the details.
*Unix on a 3B2-700 won't boot*
I have been going round and round getting it to boot and am at
the point where it might be the sd630.img disk image.
It keeps hanging in "DIAGNOSTICS".
I have reloaded all the files to no avail. Does anyone have a
*known working copy* of *sd630.img* they could share as a gzip ?
Other sims work fine like 3b2-400, Interdata-32 and PDP-11.
Ken
--
WWL 📚
Hello,
I received word from someone who went to Case Wester Reserve
Univsersity, and is willing to send early 1970s ephemera to someone
interested in going through it. The description is:
"I've go stuff from my course work done on our Univac 1108/ChiOS system,
program listing, cpu code cards, etc."
Any takers?
Best regards,
Lars Brinkhoff
I have a 3b2/400 emulator running Unix V r3 fine,
but I have two questions.
Unix is set up with IP 10.0.2.15
I can telnet off it great *but* can not telnet into it. Is there a step I
am missing?
In the sim ini file I have set:
set NI enabled
attach NI nat:
Someone suggested:
attach nat:tcp=2323:10.0.2.15:23,tcp=2121:10.0.2.15:21
but that did not work.
This is what I get at boot time:
NAT args:
NAT network setup:
gateway =10.0.2.2/24(255.255.255.0)
DNS =10.0.2.3
dhcp_start =10.0.2.15
Protocol[State] FD Source Address Port Dest. Address Port RecvQ
SendQ
/home/ken/MYSIMS/System-V-r3/boot.ini-51> attach NI nat:
%SIM-INFO: Eth: opened OS device nat:
Thanks,
Ken
--
WWL 📚
I sent this to coff, but it bounced. Trying again.
[-tuhs] [+coff]
On Sun, Apr 2, 2023 at 3:39 AM Noel Hunt <noel.hunt(a)gmail.com> wrote:
Charles li reis, nostre emperesdre magnes, Set anz totz pleinz ad ested in
> Espagnes.
>
> A translation would be most helpful. It looks like a mixture
> of Spanish and Mediaevel French...ah, it is the La Chanson de
> Roland.
>
Yes, it's Old French, and means "Charles the king, our great emperor[*] /
Seven full years has been in Spain." You pronounce it pretty much like
Spanish, except for the "z" which is pronounced "ts".
[*] Old French had two noun cases, nominative and oblique (a combination of
the Latin genitive, dative, accusative, and ablative). In 99% of modern
French nouns, only the oblique survives. In particular, "emperesdre" is
the old nominative of "empereor"; it survives today in the name
"L[']empriere". A dozen nouns picked up different semantics in the
nominative and both survived: sire/seigneur, prêtre/Provoire (proper name),
copain/compagnon, pâtre/pasteur, chantre/chanteur , maire/majeur,
gars/garçon, and (most surprising) on/homme. In a few nouns, only the
nominative survives: soeur, peintre, traître (English traitor is from the
oblique), and the names Charles, Georges, James (now in English only),
Hugues, Marie, and Eve.
>
[ Please post follow-ups to COFF ]
Ron,
Thanks for the history, enjoyed very much.
Quite relevant to Early Unix, intertwined with VAxen, IP stack from UCB, NSF-net & fakery.
The earliest documented Trojan, Unix or not, would be Ken’s login/cc hack in his “Reflections on Trust” paper.
It was 1986 when Clifford Stoll tracked a KGB recruit who broke into MILNET, then the first “honeynet” by Stoll.
<https://en.wikipedia.org/wiki/Clifford_Stoll#Career>
<https://en.wikipedia.org/wiki/The_Cuckoo%27s_Egg_(book)>
1986 was also the first known PC virus according to Kaspersky.
<https://www.kaspersky.com.au/resource-center/threats/a-brief-history-of-com…
“Brain (boot) , the first PC virus, began infecting 5.2" floppy disks in 1986.”
2nd November 1988, the Morris worm escaped from a lab,
& overloaded the Internet for a week.
Causing CERT to be formed in November 1988 in response.
<https://en.wikipedia.org/wiki/CERT_Coordination_Center>
The SANS Institute was formed the next year, 1989, creating structured training & security materials.
<https://en.wikipedia.org/wiki/SANS_Institute>
This structured, co-ordinated response, led by technical folk, not NatSec/ Intelligence/ Criminal investigation bodies,
created CVE’s, Common Vulnerabilities and Exposures, as a way to identify & name
unique attacks & vectors, track them and make vendors aware, forcing publicity & responses.
<https://en.wikipedia.org/wiki/Common_Vulnerabilities_and_Exposures>
<https://cve.mitre.org>
The Internet eventually became a significant theatre of Crime & Espionage, Commercial & National Security.
Mandiant was formed in 2004 to identify, track and find sources of APT’s, Advanced Persistent Threats.
In 2010, they described APT’s tracked in their “M-trends” newsletter.
in Feb 2013, Mandiant publicly described “APT1” and the military unit & location they believed ran it.
<https://en.wikipedia.org/wiki/Mandiant>
<https://en.wikipedia.org/wiki/Advanced_persistent_threat>
<https://www.lawfareblog.com/mandiant-report-apt1>
<https://www.mandiant.com/resources/blog/mandiant-exposes-apt1-chinas-cyber-…>
=============
> On 2 Apr 2023, at 02:34, Ron Natalie <ron(a)ronnatalie.com> wrote:
>
> Once again, I must dredge up this post from 1991….
=============
For future reference, Kremvax lives! [ datestamp in email header ]
iMac1:steve$ host kremvax.demos.su
kremvax.demos.su has address 194.87.0.20
kremvax.demos.su mail is handled by 100 relay2.demos.su.
kremvax.demos.su mail is handled by 50 relay1.demos.su.
iMac1:steve$ ping -c2 kremvax.demos.su
PING kremvax.demos.su (194.87.0.20): 56 data bytes
64 bytes from 194.87.0.20: icmp_seq=0 ttl=46 time=336.127 ms
64 bytes from 194.87.0.20: icmp_seq=1 ttl=46 time=335.823 ms
--- kremvax.demos.su ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 335.823/335.975/336.127/0.152 ms
=============
--
Steve Jenkin, IT Systems and Design
0412 786 915 (+61 412 786 915)
PO Box 38, Kippax ACT 2615, AUSTRALIA
mailto:sjenkin@canb.auug.org.au http://members.tip.net.au/~sjenkin
Hi.
I made an error on data entry installing TCP Networking on a 3b2/400 on a
SIM.
Is there a way to re-start the CONFIGURATION process without having to
start over from scratch re-installing the entire system?
The section covering hostname,host's network number, etc.
Thanks,
Ken
--
WWL 📚
[Redirected to COFF for some anecdotal E&S-related history and non-UNIX
terminal room nostalgia.]
On 3/7/23 9:43 PM, Lars Brinkhoff wrote:
> Noel Chiappa wrote:
>>> The first frame buffers from Evans and Sutherland were at University
>>> of Utah, DOD SITES and NYIT CGL as I recall. Circa 1974 to 1978.
>>
>> Were those on PDP-11's, or PDP-10's? (Really early E+S gear attached to
>> PDP-10's; '74-'78 sounds like an interim period.)
>
> The Picture System from 1974 was based on a PDP-11/05. It looks like
> vector graphics rather than a frame buffer though.
>
> http://archive.computerhistory.org/resources/text/Evans_Sutherland/EvansSut…
E&S LDS-1s used PDP-10s as their host systems. LDS-2s could at least in
principle use several different hosts (including spanning a range of
word sizes, e.g., a SEL-840 with 24 bit words or a 16 bit PDP-11.)
The Line Drawing Systems drove calligraphic displays. No frame buffers.
The early Picture Systems (like the brochure referenced by Lars) also
drove calligraphic displays but did sport a line segment "refresh
buffer" so that screen refreshes weren't dependent on the whole
pipeline's performance.
At least one heavily customized LDS-2 (described further below) produced
raster output by 1974 (and likely earlier in design and testing) and had
a buffer for raster refresh which exhibited some of what we think of as
the functionality of a frame buffer fitting the time frame referenced by
Noel for other E&S products.
On 3/8/23 10:21 AM, Larry McVoy wrote:
> I really miss terminal rooms. I learned so much looking over the
> shoulders of more experienced people.
Completely agree. They were the "playground learning" that did all of
educate, build craft and community, and occasionally bestow humility.
Although it completely predates frame buffer technology, the PDP-10
terminal room of the research computing environment at CWRU in the 1970s
was especially remarkable as well as personally influential. All
(calligraphic) graphics terminals and displays (though later a few
Datapoint CRTs appeared.) There was an LDS-1 hosted on the PDP-10 and
later an LDS-2 (which was co-located but not part of the PDP-10
environment.)
The chair of the department, Edward (Ted) Glaser, had been recruited
from MIT in 1968 and was heavily influential in guiding the graphics
orientation of the facilities, and later, in the design of the
customized LDS-2. Especially remarkable as he had been blind since he
was 8. He had a comprehensive vision of systems and thinking about them
that influenced a lot about the department's programs and research.
When I arrived in 1972, I only had a fleeting overlap with the LDS-1 to
experience some of its games (color wheel lorgnettes and carrier
landings!). The PDP-10 was being modified for TENEX and the LDS-1 was
being decommissioned. I recall a tablet and button box for LDS-1 input
devices.
The room was kept dimly lit with the overhead lighting off and only the
glow of the displays and small wattage desk lamps. It shared the raised
floor environment with the PDP-10 machine room (though was walled off
from it) and so had a "quiet-loud" aura from all the white noise. The
white noise cocooned you but permitted conversation and interaction with
others that didn't usually disturb the uninvolved.
The luxury terminals were IMLAC PDS-1s. There was a detachable switch
and indicator console that could be swapped between them for debugging
or if you simply liked having the blinking lights in view. When not in
use for real work the IMLACs would run Space War, much to the detriment
of IMLAC keyboards. They could handle pretty complex displays, like, a
screen full of dense text before flicker might set in. Light pens
provided pointing input.
The bulk of the terminals were an array of DEC VT02s. Storage tube
displays (so no animation possible), but with joysticks for pointing and
interacting. There were never many VT02s made and we always believed we
had the largest single collection of them.
None of these had character generators. The LDS-1 and the IMLACs drew
their own characters programmatically. A PDP-8/I drove the VT02s and
stroked all the characters. It did it at about 2400 baud but when the 8
got busy you could perceive the drawing of the characters like a scribe
on speed. If you stood way back to take in the room you could also watch
the PDP-8 going around as the screens brightened momentarily as the
characters/images were drawn. I was told that CWRU wrote the software
for the PDP-8 and gave it to DEC, in return DEC gave CWRU $1 and the
biggest line printer they sold. (The line printer did upper and lower
case, and the University archivists swooned when presented with theses
printed on it -- RUNOFF being akin to magic in a typewriter primitive
world.)
Until the Datapoint terminals arrived all the devices in the room either
were computers themselves or front-ended by one. Although I only saw it
happen once, the LDS-1 with it's rather intimate connection to the -10
was particularly attuned to the status of TOPS-10 and would flash
"CRASH" before users could tell that something was wrong vs. just being
slow.
(We would later run TOPS-10 for amusement. The system had 128K words in
total: 4 MA10 16K bays and 1 MD10 64K bay. TENEX needed a minimum of 80K
to "operate" though it'd be misleading to describe that configuration as
"running". If we lost the MD10 bay that meant no TENEX so we had a
DECtape-swapping configuration of TOPS-10 for such moments because,
well, a PDP-10 with 8 DECtapes twirling is pretty humorously theatrical.)
All the displays (even the later Datapoints) had green or blue-green
phosphors. This had the side effect that after several hours of
staring at them made anything which was white look pink. This was
especially pronounced in the winter in that being Cleveland it wasn't
that unusual to leave to find a large deposit of seemingly psychedelic
snow that hadn't been there when you went in.
The LDS-2 arrived in the winter of 1973-4. It was a highly modified
LDS-2 that produced raster graphics and shaded images in real-time. It
was the first system to do that and was called the Case Shaded Graphics
System (SGS). (E&S called it the Halftone System as it wouldn't do color
in real-time. In addition to a black & white raster display, It had a
35mm movie camera, a Polaroid camera, and an RGB filter that would
triple-expose each frame and so in a small way retained the charm of the
lorgnettes used on the LDS-1 to make color happen but not in real-time.)
It was hosted by a PDP-11/40 running RT-11.
Declining memory prices helped enable the innovations in the SGS as it
incorporated more memory components than the previous calligraphic
systems. The graphics pipeline was extended such that after translation
and clipping there was a Y-sort box that ordered the polygons from top
to bottom for raster scanning followed by a Visible Surface Processor
that separated hither from yon and finally a Gouraud Shader that
produced the final image to a monitor or one of the cameras. Physically
the system was 5 or maybe 6 bays long not including the 11/40 bay.
The SGS had some teething problems after its delivery. Ivan Sutherland
even came to Cleveland to work on it though he has claimed his main
memory of that is the gunfire he heard from the Howard Johnson's hotel
next to campus. The University was encircled by several distressed
communities at the time. A "bullet hole through glass" decal appeared on
the window of the SGS's camera bay to commemorate his experience.
The SGS configuration was unique but a number of its elements were
incorporated into later Picture Systems. It's my impression that the LDS
systems were pretty "one off" and the Picture Systems became the
(relative) "volume, off the shelf" product from E&S. (I'd love to read a
history of all the things E&S did in that era.)
By 1975-6 the SGS was being used by projects ranging from SST stress
analyses to mathematicians producing videos of theoretical concepts. The
exaggerated images of stresses on aircraft structures got pretty widely
distributed and referenced at the time. The SGS was more of a production
system used by other departments and entities rather than computer
graphics research as such, in some ways its (engineering) research
utility was achieved by its having existed. One student, Ben Jones,
created an extended ALGOL-60 to allow programming in something other
than the assembly language.
As the SGS came online in 1975 the PDP-10 was being decommissioned and
the calligraphic technologies associated with it vanished along with it.
A couple of years later a couple of Teraks appeared and by the end of
the 1970s frame buffers as we generally think of them were economically
practical. That along with other processing improvements rendered the
SGS obsolete and and so it was decommissioned in 1980 and donated to the
Computer History Museum where I imagine it sits in storage next to a
LINC-8 or the Ark of the Covenant or something.
One of the SGS's bays (containing the LDS-2 Channel Control, the front
of the pipeline LDS program interpreter running out of the host's
memory) and the PDP-11 interface is visible via this link:
https://www.computerhistory.org/collections/catalog/102691213
The bezels on the E&S bays were cosmetically like the DEC ones of the
same era. They were all smoked glass so the blinking lights were visible
but had to be raised if you wanted to see the identifying legends for them.
Hi,
Has anyone been successful in communicating using cu or some
other method to transfer files between two SIMS running Unix V ?
If so I would appreciate some help.
Thanks,
Ken
--
WWL 📚
