Hi.
> > Hi. Does anyone remember for sure if "new" awk shipped with System V
> > Release 3.1 or 3.2? I know it wasn't 3.0.
>
> Hi,
>
> http://www.levenez.com/lang/ says 1978 for oawk and 1985 for nawk.
New awk existed inside the Research group for some time before it
filtered out through System V. It was even available separately,
directly from them, to educational institutions. Circa 1986 I got
a copy that way when I worked at the Emory University computing center.
> regarding http://www.levenez.com/unix/, 1978 is between v6 and v7,
> and 1985 is between SVr2 and SVr3.0.
True but not relevant; new awk was released with System V at either
3.1 or 3.2; I'm leaning towards 3.1 since that is what I wrote way back
when in the gawk manual when I knew for sure. :-)
Unless anyone can check the actual sources, I think we should declare
this closed... Thanks to everyone for the feedback.
Arnold
Jaap Akkerhuis wrote:
> Officially it was written by Aho Weinberger Kernighan but
> I suspect Brian did most of the actual coding.
quote of Aho from an interview ---
"We [Aho and Kernighan] had created a grammatical specification for AWK but
hadn't yet created the full run-time environment. Weinberger came along
and said 'hey, this looks like a language I could use myself', and within
a week he created a working run time for AWK."
see http://www.computerworld.com.au/article/216844/a-z_programming_languages_aw…
I know for sure that in 1988's svr3.2 the "awk" command was the 1988 version
and the "oawk" command was the version from 1979.
In svr3.0 the "awk" command was the old and we'd get the new one
from Holmdel's unix tools distribution group (called USTOP) and
install it as "nawk"
I think you could get the new one in stock svr3.1 but cannot
remember it it was provide as "awk" or "nawk."
> Hi. Does anyone remember for sure if "new" awk shipped with System V
> Release 3.1 or 3.2? I know it wasn't 3.0.
>
> Thanks!
>
> Arnold Robbins
Regardless of its technical merits (and I suspect that the implementation may have been pretty bad) RFS was doomed by AT&T's licensing policies and general ineptitude at marketing UNIX. Similarly the widespread adoption of NFS was driven by the fact that Sun made it a de facto standard.
On Thu Mar 31st, 2011 7:51 PM PDT Nick Downing wrote:
>I also looked up EDOTDOT and found reference to RFS but not much info about
>it. Why was it not used? Not reliable enough? I have often thought that
>the stateless, idempotent NFS protocol leaves a lot to be desired due to its
>inability to implement unix semantics (as discussed in the wikipedia stub
>article on RFS), has this been improved with NFS4? Should RFS be revived
>and used? Some of its features sounded quite attractive (location
>transparency, etc). It does appear to have the ability to execute a program
>remotely?? What happens with regard to PIDs, home directory etc in this
>case? Does anyone know?
>cheers, Nick
>
>On Fri, Apr 1, 2011 at 1:23 PM, Michael Davidson <
>michael_davidson(a)pacbell.net> wrote:
>
>> --- On *Thu, 3/31/11, Random832 <random832(a)fastmail.us>* wrote:
>>
>>
>> EDOTDOT caught my eye for some reason - maybe because it's the only one
>> you attributed to linux in a long list of SVr1 ones... what were 72
>> through 76 in SVR1?
>>
>>
>> As the comment indicates, EDOTDOT came from "RFS" - the almost never used
>> "remote file system" that was (optionally, I think) part of System V Release
>> 3.
>>
>> As best I can recall, that is also where several of the other error numbers
>> in the 72 - 79 range probably came from.
>>
>> Michael Davidson
>>
>> _______________________________________________
>> TUHS mailing list
>> TUHS(a)minnie.tuhs.org
>> https://minnie.tuhs.org/mailman/listinfo/tuhs
>>
>>
Hi all,
PJ from groklaw.net has asked me to trace the origin of
the errno names and values in recent versions of Linux. Attached
is where I am up to. The columns are:
- errno name
- errno value in Linux, and its original value if different
- system which originally defined it
- release date of that system
There are a few errno names which I don't think I have the
correct original system:
EDOTDOT, ENOMEDIUM, EMEDIUMTYPE, ECANCELED,
ENOKEY, EKEYEXPIRED, EKEYREVOKED, EKEYREJECTED,
EOWNERDEAD, ENOTRECOVERABLE, ERFKILL
Can anybody shed some light on these ones, that would be
great, especially if they come from SysV or Unixware.
Also, if you can spot any other mistakes, let me know!
Many thanks in advance,
Warren
Hi all, best wishes for 2011. I had an e-mail from Sven Mascheck asking about
the history of #! interpretation in System V. I couldn't find any #!
code in the kernels before SysVR4. However, I thought I'd pass the
query onto the TUHS list, in case others can shed some light on the question.
Did SysV systems before r4 do #! interpretation, and if so where was it done:
kernel, library, shell? Any code references, e.g. function names etc.?
Many thanks,
Warren
My interest is tweeked, do you still have the source
for the paper on your editor and perhaps the plan9 source?
I never moved across to acme, I am still a sam addict, but
I am always interested in new ideas.
The Only editors I ever used on Edition-VII where vi and le,
and le I only brushed up against.
-Steve
Warren Toomey said:
> I first encountered Unix in 1982 at a summer school held by the University
> of Wollongong in Australia. They had an modeless text editor installed,
> and I have never been able to determine if this was a homegrown editor, or
> an editor which was more widely distributed.
The editor was homegrown in Wollongong in 1981, as a late addition to the
Interdata Unix port. I wrote it in response to an elegant and concise
formal mathematical specification of a "display-oriented text editor"
written by Bernard Sufrin of Oxford University's Programming Research
Group. Bernard's specification was essentially an abstract model of an
existing minimalist (and modeless) screen editor 'ded' developed by his
colleague Richard Bornat at Queen Mary College in London. I've never seen
'ded' itself, but I expect that if you tried both editors you would see a
close family resemblance.
The Wollongong editor was not widely disseminated. I don't think it got
into any official Unix distribution except perhaps for Edition VII - its
austere minimalism could not compete with the dazzling complexity of emacs
or vi. I did license it to Interdata (later aka Perkin-Elmer) for use on
their own OS/32 operating system, where it was called MEDIT. I carried on
for many years using it myself and porting it to various flavours of Unix,
Minix, even MS/DOS, and most recently Plan 9. It was only after giving up
Unix for Plan 9 that I finally switched to using Rob Pike's 'acme', which
is, in its way, even more elegantly minimal.
-- Richard Miller
I thought I'd pop in another question here, given the good response we had
with #!
I first encountered Unix in 1982 at a summer school held by the University
of Wollongong in Australia. They had an modeless text editor installed,
and I have never been able to determine if this was a homegrown editor, or
an editor which was more widely distributed.
I've attached the first 2 pages of the editor's tutorial; the rest are
temporarily at http://minnie.tuhs.org/Z2/WollongongEdit/
Does anybody recognise this at all?
Many thanks in advance,
Warren
Hello,
Looking for an old version of SQR (Oracle's reporting program) -
3.0.13/.0.15 for >= SunOs5, a.k.a Solaris (>=2.x).
We've got SQR 3.0.13 for SunOS 4, but of course it is not compatible
with our Solaris Oracle client (which isn't sunos4, but sunos 5.8).
According to some records and posts online, there is an 3.0.13 for
Solaris :) just need to find a copy
We've already posted a request in SQRUG (SQR User Group) mailing list
and of course contacted our local Oracle provider (who gave us the
SunOS4 version).
Needles to say, we're in contract with Oracle, once we get a correct
version of the program and according to a successful P.O.C, fully
payed licenses will be purchased.
Check with your ex MITI/Sqribe, Oracle contacts.
Cash prize - $1,000 to finder.
Thanks a lot,
A', D' and friends at the DGUX Project
I asked a while back if anyone had any NetBSD 0.8 or 0.9 archives.. I
thought I'd let the list know that I did manage to find NetBSD 0.9, and
using VMWare I've managed to revive it into something that Qemu can run.
If anyone has VMWare and wants to stroll down memory lane, I've uploaded the
install diskettes here:
http://sourceforge.net/projects/bsd42/files/Install%20tapes/NetBSD/0.9/NetB…
And I've setup an archive with Qemu & NetBSD all ready to go here:
http://sourceforge.net/projects/bsd42/files/4BSD%20under%20Windows/v0.4/Net…
If anyone wants to use their own qemu for their own platform, I've had to
modify the hw/pc.c and remove the NE2000 definition of 0x300,9 as irq 9 is
in use somewhere else in the emulator and it won't allow any sharing on
Irq9.. (Wasn't IRQ 9 shared anyways with the cascade controller???)
At any rate, I built irc, lynx & bzip2 on there, and they seem to function
just fine.
Again if anyone has any lead on NetBSD 0.8 that'd be great, I'd like to save
these from the digitial dumpster....
For anyone that is even remotely interested, I found a way to 'cheat'
the install process, and I've gotten 386 BSD 0.0 to install under
bochs. Qemu is convinced it can't read the disk for a kernel....
But it does work, well as well as 386BSD 0.0 can work.
http://vpsland.superglobalmegacorp.com/install/386BSD/386bsd-0.0/bochs/
I'll try to clean up what I can later.......
well I think I've flogged this dead horse enough... :)
Basically I've mashed in as much as I could figure out, and got the
majority of a make install (build world?) on this thing to work.. I
still don't know where /usr/bin/install comes from as I couldn't
readily identify the source in NetBSD 0.9 or any of the 386 BSD's...
I'm probably looking in the wrong place or maybe it's just from Net/2?
I didn't spend too long trying to work out stuff like that.
If anyone wants, it's in a Qemu runnable image here:
http://sourceforge.net/projects/bsd42/files/4BSD%20under%20Windows/v0.4/Net…
It is just under 50MB, which I guess isn't bad since it's source and binaries..
I've manually copied over a few things from etc, and it seems that
NetBSD 0.8 still identifies itself as 386BSD.. did anyone run 0.8 and
remember? The CVS history on /etc/motd seems to have the 0.8 still
reporting as 386BSD which didn't change until 0.9 ...
I had to use a good chunk of 386 BSD pl 23 to fill in the missing
parts from the CVS archive of the kernel, but I got it to build!
>From the NetBSD 0.8 release/announcement it doe say:
The source for NetBSD is derived from 386BSD 0.1, patched
with the 0.2.2 patch kit. In addition, many programs in
UCB's second BSD Networking Software Release which were
missing from 386BSD have been integrated into NetBSD, some
of the changes from the upcoming 0.2.3 patch kit have been
included, and many local additions and bug fixes have
been performed.
So I'm assuming this wouldn't be too far off then.
So for the curious, here is a dmesg:
386BSD 0.1 (GENERICISA) #2: Sun Dec 5 13:30:14 PST 2010
root@branch.oldbsd.org:/usr/src/sys.386bsd/arch/compile/J
real mem = 67104768
avail mem = 64663552
pc0 at 0x60-0x6f irq 1 on isa
pc0: color
wdc0 at 0x1f0-0x1f7 irq 14 on isa
wdc0: <QEMU HARDDISK>
wd0 at wdc0 slave 0
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
ne0 at 0x320 irq 10 on isa
ethernet address 52:54:00:12:34:56
npx0 at 0xf0 irq 13 on isa
wdc0: extra interrupt
wdc0: extra interrupt
ISA strayintr 4004ff
ISA strayintr 4004ff
ISA strayintr 4004ff
ISA strayintr 2ff
ISA strayintr 2ff
ISA strayintr 2ff
ISA strayintr 2ff
ISA strayintr 2ff
ISA strayintr 2ff
ISA strayintr 2ff
Too many ISA strayintr not logging any more
I'm not sure if the 386BSD name is hanging around because of all the
386 BSD files I included of if it wasn't renamed in NetBSD 0.8 ... I
can give anyone the list of files, steps etc, or it may be easier to
just download the merged & built sources here:
http://vpsland.superglobalmegacorp.com/install/NetBSD/NetBSD-0.8/Resurrecti…
Thanks to everyone for providing the CVS and a few hints on what was
going on with it..!
I hate to post this publicly, but Natalia's email address that I have
is also on the domain... Anyways it's expired, you may want to renew
clanuia.com.
I'm sorry for posting this publicly, wasting peoples time bandwidth etc etc.....
Jason
On 12/03/10 03:00, "Jeremy C. Reed"<reed(a)reedmedia.net> wrote:
>> > Maybe I'm totally dense, or something...?
>> >
>> > cvs -P :pserver:anoncvs@anoncvs.netbsd.org:/cvsroot co -R netbsd-0-8 src
>
> cvs -d :pserver:anoncvs@anoncvs.netbsd.org:/cvsroot co -r netbsd-0-9 \
> src/sys/kern/kern_exit.c
>
> (note I changed -P and -R to -d and -r respectively)
Wow. Did I really write that? :-)
Thanks for the correction. I have no excuse.
> cat src/sys/kern/kern_exit.c
Anything in particular we should look for?
Johnny
On 11/17/10 03:00, Jason Stevens<neozeed(a)gmail.com> wrote:
> I don't suppose anyone has this kicking around, or any pre-release vax
> images of netbsd?
>
> I did manage to get 1.2 installed on SIMH for what it's worth....
Btw, fwiw, I'm pretty sure VAX only started working with NetBSD 0.9, and
the first machine supported was the VAX-11/750.
Johnny
On 12/02/10 03:00, Jason Stevens<neozeed(a)gmail.com> wrote:
> I asked a while back if anyone had any NetBSD 0.8 or 0.9 archives.. I
> thought I'd let the list know that I did manage to find NetBSD 0.9, and
> using VMWare I've managed to revive it into something that Qemu can run.
>
> If anyone has VMWare and wants to stroll down memory lane, I've uploaded the
> install diskettes here:
> http://sourceforge.net/projects/bsd42/files/Install%20tapes/NetBSD/0.9/NetB…
>
> And I've setup an archive with Qemu& NetBSD all ready to go here:
> http://sourceforge.net/projects/bsd42/files/4BSD%20under%20Windows/v0.4/Net…
>
> If anyone wants to use their own qemu for their own platform, I've had to
> modify the hw/pc.c and remove the NE2000 definition of 0x300,9 as irq 9 is
> in use somewhere else in the emulator and it won't allow any sharing on
> Irq9.. (Wasn't IRQ 9 shared anyways with the cascade controller???)
>
> At any rate, I built irc, lynx& bzip2 on there, and they seem to function
> just fine.
>
> Again if anyone has any lead on NetBSD 0.8 that'd be great, I'd like to save
> these from the digitial dumpster....
Maybe I'm totally dense, or something...?
cvs -P :pserver:anoncvs@anoncvs.netbsd.org:/cvsroot co -R netbsd-0-8 src
or substitute the tag netbsd-0-9 or netbsd-0-9-base if you need those
revisions. Nothing is going to disappear into a digital dumpster when
you have revision control systems...
(There are bunch of more tags related to NetBSD 0.9 as well, if you want
to know, and you can get at any other version you want as well, just as
easily.)
If you want binaries and not just sources, then it might be a bit more
tricky. But since you can build the system from the sources, I can't see
that this should be a big hurdle.
Johnny
Just to loop things around a bit:
Some of the larger VAXes used small PDP-11s (and their
bastard offspring) as console processors.
This started with the very first VAX, the 11/780, which
used an 11/23 as a console. The console ran a stripped-down
system, possibly based on RT-11 or RSX-11, I forget (and
am typing this on a train in the Outer Mongolia part of
Texas where it's hard to look up references).
I don't know the whole list of what was used as a console
for different VAXes, but I do remember that the Nautilus
series (8500-8550-8700-8800) used either a Pro/350 or a
Pro/380, running P/OS, which was slightly more satisfactory
than the rude English non-computer expansion of PoS might
imply, but only slightly. Especially for those of us who
wrote code to fit into UNIX on the VAX and talk to the
console processor.
I also vaguely remember that although Digital were
reluctant (at least early on) to make an RT-11 that would
run on the Pro-series systems, someone made a UNIX for
those systems.
I never knew a lot about this stuff and have forgotten much
of what I did know, but perhaps my words will trigger others'
memories.
Norman Wilson
Toronto ON
I don't suppose anyone has this kicking around, or any pre-release vax
images of netbsd?
I did manage to get 1.2 installed on SIMH for what it's worth....
Jason
How much does an old pdp-11 type system cost these
days (ie. a pdp-11/40 with disks and terminal capable
of running something like 1st, 6th or 7th ed)?
How much power do they take up to power on?
Whats maintenance like on those things?
I've always been curious.
Tim Newsham | www.thenewsh.com/~newsham | thenewsh.blogspot.com
I was wondering if anyone has ever been able to build and use BSD 1 on
Research Unix v7 (pdp-11)?
I've installed the Keith Bostic tape, and I've been fighting the floating
point and some other weird stuff....
I've configured my PDP-11 like this:
set cpu 11/70
set cpu 2M
set cpu idle
set rp0 rp06
att rp0 rp06-0.disk
att tm0 xx.tap
boot tm0
but I'm lost on the install guide, as it mentions for floating point...
Floating Point
UNIX only supports (and really expects to have) the
FP11-B/C floating point unit. For machines without this
hardware, there is a user subroutine available that will
catch illegal instruction traps and interpret floating point
operations. (See fptrap(3).) To install this subroutine in
the library, change to /usr/src/libfpsim and execute the
shell files
compall
mklib
The system as delivered does not have this code included in
any command, although the operating system adapts automati-
cally to the presence or absence of the FP11.
Next, a floating-point version of the C compiler in
/usr/src/cmd/c should be compiled using the commands:
cd /usr/src/cmd/c
make fc1
mv fc1 /lib/fc1
This allows programs with floating point constants to be
compiled. To compile floating point programs use the `-f'
flag to cc(1). This flag ensures that the floating point
interpreter is loaded with the program and that the floating
point version of `cc' is used.
The library doesn't actually build a libfpsim.a but rather it hooks into
libc? And the fc1 command won't build as there is no libfpsim....
Maybe I'm doing something obviously wrong?
Any hint would be appreciated.
Jason
