I've assembled some notes from old manuals and other sources
on the formats used for on-disk file systems through the
Seventh Edition:
http://www.cita.utoronto.ca/~norman/old-unix/old-fs.html
Additional notes, comments on style, and whatnot are welcome.
(It may be sensible to send anything in the last two categories
directly to me, rather than to the whole list.)
Hi,
I successfully made SIMH VAX-11/780 emulator run 32V, 3BSD and 4.0BSD.
Details are on my web site (thogh rather tarse):
http://zazie.tom-yam.or.jp/starunix/
Enjoy!
Naoki Hamada
nao(a)tom-yam.or.jp
How to to extract a ".tap" file? What tools?
I found http://man.cat-v.org/unix-1st/1/tap manual but I haven't found
corresponding tool (even in tuhs source code archive).
The file I am trying to extract is
http://bitsavers.trailing-edge.com/bits/BSD/BSD4.1_bootable.tap.gz (12
MB). I can view some of the plain text in it.
I tried historical ar (which I have used for some other 1970's images),
restore, and tar. file(1) says it is a "Maple help database".
Jeremy C. Reed
echo 'EhZ[h ^jjf0%%h[[Zc[Z_W$d[j%Xeeai%ZW[ced#]dk#f[d]k_d%' | \
tr '#-~' '\-.-{'
PRESS RELEASE - PLEASE COPY AND SHARE!
APPLE 1
FRIDAY, Sept. the 13th
at the "Museo dell'Informatica Funzionante" Computer Museum
Via Carnevale 17, 96010 Palazzolo Acreide (SR) - ITALY
http://museo.freaknet.org/en/presentazione-progetto-apple-1/
The APPLE 1 marked the start of the era of "personal computing",
a computer that people could keep at home on their desks, a
pioneer vision at that time, that opened the way for the future
of human-machine interfaces. Born from the genius of Steve
Wozniak, it transformed Apple into today ‘s success, thanks also
to the entrepreneurial audacity of Steve Jobs.
At that time only about 200 pieces were produced; today only
about 50 of them survived, of which only a dozen are fully
working. The APPLE 1 was an open project since its birth: he
schematics and instructions were already circulating among fans
well before the creation of Apple as a company. From this early
computer, Steve Wozniak created the legendary APPLE 2, a
colossal success that transformed him and Steve Jobs into
billionaires.
We started this adventure almost two years ago at the "Museo
dell'Informatica Funzionante" Computer Museum: to rebuild from
scratch, starting from a completely blank electronic card, a
working APPLE 1, using tools and components dated exactly or
before its creation: 1976.
A year and a half was spent searching for integrated circuits,
connectors, electronic components of various types, bought new
or second-hand, found in various parts of the world, but all
identical to the originals, with the right features and from the
same historical period. The project, managed by a local team,
involved fans and professionals from all the world.
So we present today our creation, made entirely in
Sicily, Palazzolo Acreide, Italy: a specimen of APPLE Computer
1, fully functional, rebuilt with attention to every detail and
using only original components at the best of our possibility!
With this release we intend to invite everyone to the event of
his first start, in person or remotely via our live streaming.
Friday, September 13, 2013:
19:00 - Presentation of the APPLE 1 project and the computer
19.30 - Booting up the rebuilt APPLE 1 Computer, and operational
demo
20:00 - Aperitif
Remote presence:
Via live chat on IRC: https://irc.dyne.org, channel #museo
Live video streaming: http://bambuser.com/channel/musif
On Twitter: follow @FreaknetMuseum
All people in Palazzolo Acreide can also have a guided tour of
our exibithion "Apple, il genio di Steve Wozniak", dedicated to
the genius of Steve Wozniak and his creations, with working
Apple computers and memorabilia from 1978 to 1999.
For more information, press kits and interviews please write to
museo(a)freaknet.org
Spam detection software, running on the system "www.oztivo.net", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
@@CONTACT_ADDRESS@@ for details.
Content preview: ÀÎÁõÆäÀÌÁö½Ã¾È1 [...]
Content analysis details: (6.0 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
1.4 RCVD_IN_BRBL_LASTEXT RBL: RCVD_IN_BRBL_LASTEXT
[211.32.24.57 listed in bb.barracudacentral.org]
0.7 SPF_SOFTFAIL SPF: sender does not match SPF record (softfail)
1.1 URI_HEX URI: URI hostname has long hexadecimal sequence
0.0 WEIRD_PORT URI: Uses non-standard port number for HTTP
0.4 HTML_IMAGE_RATIO_02 BODY: HTML has a low ratio of text to image area
0.0 HTML_MESSAGE BODY: HTML included in message
0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60%
[score: 0.5000]
0.7 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
0.8 RDNS_NONE Delivered to internal network by a host with no rDNS
0.0 T_REMOTE_IMAGE Message contains an external image
The original message was not completely plain text, and may be unsafe to
open with some email clients; in particular, it may contain a virus,
or confirm that your address can receive spam. If you wish to view
it, it may be safer to save it to a file and open it with an editor.
> CB/UNIX was developed to address deficiencies inherent in Research Unix,
> notably the lack of interprocess communication and file locking
CB/UNIX was one of several versions in various divisions of Bell Labs
to implement IPC facilities beyond pipes and signals. Top management
in a division would declare that they wanted to use Unix, but needed
some particular IPC mechanism: semaphores, events, message passing, etc.--
and needed it right away. I always believed that these demands stiffer
as they percolated up through channels to the point that no alternative
mechanism would do. We in research would have preferred to seek a
general solution that would suffice to serve the various demands.
Besides, anything that we produced but didn't use ourselves would
automatically be suspect. We were very wary of featuritis.
Roughly speaking, each demand led to a different local flavor of
Unix, each (I like to think) reflecting the particular variant of
IPC with which one of its system designers worked in graduate
school. Somewhere between the wariness of research Unix, where
an ethos of generality ruled, and Linux, which offers a dozen ways
to do anything, there must lie a happy medium--a medium that I
believe would be much closer to Unix than Linux. That, alas, has
not proved to be the way of open source.
All, I'll be moving house sometime in the next few months, so I thought
I would start scanning in the paper documents that I've got. I've just
completed the scan of the CB/UNIX manuals that Larry Cipriani sent in
a while back. You can find them here:
http://www.tuhs.org/Archive/PDP-11/Distributions/other/CB_Unix/
and here is the blurb I put in there.
Cheers,
Warren
CB/UNIX was a variant of the UNIX operating system internal to Bell
Labs. It was developed at the Columbus, Ohio branch and was little-known
outside the company. CB/UNIX was developed to address deficiencies
inherent in Research Unix, notably the lack of interprocess communication
and file locking, considered essential for a database management
system. Several Bell System operation support system products were
based on CB/UNIX such as Switching Control Center System. The primary
innovations were power-fail restart, line disciplines, terminal types,
and IPC features similar to System V's messages and shared memory.
So far we have a scanned copy of the CB/UNIX manuals which were donated
to TUHS by Larry Cipriani. Copies of the binaries and source code would
be much appreciated. There were two volumes of manuals. The first volume
held cbunix_intro, cbunix_man1 and cbunix_man1L. The second volume held
the remaining sections. The 'L' in the scans indicates local sections of
the manuals, i.e. those elements created and maintaned at Columbus.
In an e-mail from Larry, he asked a retired CB/UNIX developer about the
major features that were added to UNIX by CB/UNIX. Was it primarily messages,
semaphores, named pipes, shared memory? The developer replied:
Other things that immediately come to mind that we added first
in Columbus Unix were power-fail restart (myself and Jim McGuire did the
initial work) and line-disciplines and terminal types (Bill Snider did
the initial work). Hal Person (or Pierson?) also rewrote the original
check disk command into something that was useful by someone other than
researchers. Bill Snider and Hal Pierson were really instrumental in
taking UNIX from research and applying it to SCCS (Switching Control
Center System). I worked with them when I first hired on. When we
first used UNIX on an 11/20 with core memory it was written in assembler
(1974). It quickly went through "B" and we started using the C version
in early 1975 as I recall. We also did some enhancements to the scheduling
algorithms in UNIX to make them more "real-time" capable.
