From: Roger Merchberger <zmerch-cctalk at 30below.com>
>
> Rumor has it that Tim Riker may have mentioned these words:
> >timr at slop:~$ touch \/path
> >touch: cannot touch `/path': Permission denied
> >timr at slop:~$ uname -a
> >Linux slop 2.6.24-timriker #1 SMP Sun Feb 17 01:36:19 MST 2008 i686
> >GNU/Linux
> >
> >which *nix are you on? just curious.
>
> I was too, because it didn't work on this either:
>
> Linux mail.30below.com 2.4.20-8 #1 Thu Mar 13 17:18:24 EST 2003 i686 athlon
> i386 GNU/Linux
>
> Maybe 2.2?
Taking a look at the ext3 source (it's in my
mental cache from the book project), there's
no escaping of the '/' character. In __link_path_walk(),
it clearly splits on '/' and doesn't look at the
previous character at all.
To bring it back on topic (and because I was
curious), I just pulled out my copy of Lions
and in 6th edition namei(), it's the same
thing. It definitely loops looking for '/'
with no regard to the previous character.
So, the old and the new both do not recognize
a file with '/' in the name. I'm not sufficiently
motivated to look through the BSD FFS :-)
BLS
Just out of curiosity I installed RSTS/E 9.6 on a SIMH PDP-11 and
thought I'll try to install DECNET 4.1, but I've come up empty trying
to find any info on how that is done. I know almost nothing about
RSTS/E yet but I'm trying to slowly learn.
I figured out that I could RESTORE INSTAL.BCK from the DECNET 4.1 tape
image and that resulted in just a few files, one of which was
DECNET.COM. That appeared to be an installation script, but it is not
clear if that is something that is intended to be manually invoked, or
if something else invokes it. I tried invoking it manually with some
guesses for the parameters, but that didn't get me anywhere.
Is there an installation guide on the net somewhere that I haven't
been able to find?
Does anyone have a sample SIMH session transcript showing the proper
way to install DECNET 4.1 on RSTS/E 9.6?
On 3 Mar, 2008, at 22:19, cctalk-request at classiccmp.org wrote:
>
> Message: 30
> Date: Mon, 3 Mar 2008 22:16:03 +0000 (GMT)
> From: Andrew Burton <aliensrcooluk at yahoo.co.uk>
>
>
> If the name is printed on the machine (as is normally the case),
> then use that version! :)
I just got one of mine off the shelf and the lid of the case is
labelled "apple ][ plus", without even a capital 'A' as the curve of
the lower case 'a' fits into the bite in the apple logo. I think the
titles on the cover of the four main manuals also said "][" on them,
but I have not checked them.
I can't actually remember what they were all for, there was the main
reference manual with the circuit diagram in the back which was very
useful for the odd machine which misbehaved when first delivered
before being shipped to customers - in several instances I traced IC
leads which had missed their sockets which were either bent
underneath or down the side.
There was a manual for DOS 3.3 and its utilities .
I think there was an Applesoft manual.
I can't remember what the other one was. It was not integer Basic, I
never saw a manual for that.
Of course there were the also manuals for UCSD Pascal, but they
weren't one of the main four.
Date: Mon, 03 Mar 2008 13:21:51 -0800
From: Brent Hilpert <hilpert at cs.ubc.ca>
Subject: Re: seven segment display history
>Don't know why that web page refers to the Sperry/Beckman displays as Panaplex,
>my understanding was Panaplex was a Burroughs trade name for their 7-seg
>gas-discharge displays.
---------
Nixie, Panaplex and Self-Scan were all registered Burroughs trademarks
for those respective products and technologies AFAIK.
m
>
>Subject: Re: Q-bus to CF [was: IOmega]
> From: der Mouse <mouse at Rodents.Montreal.QC.CA>
> Date: Fri, 29 Feb 2008 02:00:53 -0500 (EST)
> To: "General Discussion: On-Topic and Off-Topic Posts" <cctalk at classiccmp.org>
>
>> Generally IDE and CF (compactflash) are the same interface and for
>> Qbus-11 fairly simple. It's been done, however, the problem is the
>> driver as bare IDE or CF is NOT MSCP not is it DL, DX, DY or RK so a
>> driver is needed and noone has apparently stepped up to do it.
>
>Not quite true.
>
>Some time back (years), someone was working on an IDE interface for a
>Qbus MicroVAX and I was doing the driver. (This was not bootable; the
>idea was to netboot to get the kernel onto the machine.)
>
>We never got it working, and it is not clear to me, now, why not. I'm
>not sure whether this is because it wasn't clear why then or because my
>wetware memory has bitrotted - what memory I have indicates that there
>were hardware issues, but I had no physical access to the hardware, so
>I'm not sure that that's right even aside from bitrotted memory.
the likely reason is PDP-11 and VAX does read before write and IDE
does not like that. The fis is to make the READ address different
>from the write addresses, even DEC did that with interfaces.
It is otherwise straightfoward with the usual observance for timing and
the like.
Allison
>I once was one of two people who built a one-off Qbus board out of
>wirewrap, so I feel I ought to be able to build such a thing myself.
>Perhaps someday I'll gather the parts and try it. (Anyone have a Qbus
>development board looking for a home? :)
>
>/~\ The ASCII der Mouse
>\ / Ribbon Campaign
> X Against HTML mouse at rodents.montreal.qc.ca
>/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
On Mon, Mar 3, 2008 at 10:34 AM, Zane H. Healy <healyzh at aracnet.com> wrote:
> Here is an odd question for everyone. In a printed article, which
> would be more accurate? "Apple ][", "Apple II", or "Apple 2"
>
> Zane
>
I sense an impending flame war. Everyone uses every kind of moniker
for the A2 platform.
I personally use mostly "Apple II", plus "Apple //". There's the
Apple //, the Apple II Plus (II+), Apple IIe, the Apple IIc (and IIc
Plus or IIc+), and the Apple IIgs.
Josef
>
>Subject: Re: Q-bus to CF [was: IOmega]
> From: woodelf <bfranchuk at jetnet.ab.ca>
> Date: Mon, 03 Mar 2008 11:48:16 -0700
> To: General Discussion: On-Topic and Off-Topic Posts <cctalk at classiccmp.org>
>
>Bob Armstrong wrote:
>>> Sridhar Ayengar (ploopster at gmail.com) wrote:
>>
>>> Or if you're willing to write an MSCP layer into your controller firmware.
>>
>> I actually think this is the "right" way to solve the problem in the case
>> of the PDP-11 and VAX, but then controller is no longer a simple device.
>
>The question is who is the interface for. Is this like the SCB1620 interface to provide
>a hard drive to a small system that may not have any other major storage device,
>or is this for a commercial system that has a *Standard* I/O allready?
For commercial you have to deal with the holder of the MSCP intellectual rights.
The other issue is MSCP is an intelligent system that has DMA and is able to run
linked lists for queued IO.The pro for MSCP is most all of the DEC OSs had drivers
for it. The minus is complex, firmware intensive, DMA and temporary bus master
and it would try to do some of the buffering that IDE drives already do well.
Simple IDE/CF to Qbus(Ubus)... design is near complete copy of a bdirectional parallel
port described in the Small Computer Interfacing Manual with a bit more to look like
IDE bus and isolate reads and writes. Minus here is the IO is slower using PIO
(but still faster than RX02), a driver is required for most OSs. The plus is simple
to construct, the driver needed is very simple, if CF is used the board and a 32MB
CF is a complete package with as much space as many small Qbus 11s ever had!
I'd suggest to anyone that does this a basic boot rom on the board is a sane thing.
For RT11, the DD (tu58) driver would make a good prtotype as would the HX previously
mentioned. The RT-11 docs cover creating new drivers and VMS docs too.
NO, I don't volenteer, way too much going on right now.
Allison
>> Bob
>PS: I was reading the 1966 PDP 8 user handbook, I am finding usefull programing
>information since they give real detail in I/O devices.
>Any ideas on how impliment POWER on fail IRQ and restore?
First you must have core or ram that looks like core (doesn't lose data on power fail).
The assumption for real PDP-8 is always core and program in core.
--------Original Messages:
Date: Fri, 29 Feb 2008 23:22:16 -0800
From: Brent Hilpert <hilpert at cs.ubc.ca>
Subject: Re: seven segment display history
To: General at priv-edmwaa04.telusplanet.net,
"Discussion at priv-edmwaa04.telusplanet.net":On-Topic and Off-Topic
Posts <cctalk at classiccmp.org>
Message-ID: <47C90428.4A52403B at cs.ubc.ca>
Content-Type: text/plain; charset=us-ascii
Ethan Dicks wrote:
>
> I have something like that with me here in my bag-o-parts... approx 20mm
> by 30mm, with a 2mm-thick body made of a rough, dark ceramic, with a 1mm
> thick glass top. It's a 2.5 digit display with + and -. All the leads
> come through the back of the package in what appears to be a straight-
> through fashion (making it easy to figure out how to hook it up).
>
> There is a vendor and part number etched on the face: Sperry SP-738.
>
> I've never tried to hook it up to anything, and have no idea what
> voltages it might want. It's a shame it's only 2.5 digits; if it
> were 3.5 digits, it might make an interesting 12-hour clock face.
> Not sure what I'd need to do that swings from -199 to +199 off the
> top of my head.
Temperature?
Your description sounds like the Sperry/Beckman gas-discharge displays, e.g.:
http://www.tube-tester.com/sites/nixie/trade08-panaplex.htm
I think your part number is in there.
Can be cascaded with more digits, or a lot of early DVMs were only 2.5 digits.
----------------Reply:
A little tricky to interface because of the high voltage, keep-alive anodes, etc.
I may have some of the driver chips though if you're serious.
mike
>
>Subject: Re: VAXstation/MicroVAX 2000 CPU/FPU overheating?
> From: "Dave Dunfield" <dave06a at dunfield.com>
> Date: Sun, 02 Mar 2008 09:35:46 -0500
> To: "General Discussion: On-Topic and Off-Topic Posts" <cctalk at classiccmp.org>
>
>> > The extended system tests 101, 102 and 80000106 will not test the FPU
>> > - this may be normal, I don't know. The docs say they will test all
>> > hardware which is installed - this may mean that the FPU is not being
>> > full detected... I don't know.
>>
>> Is the FPU socketed? If so, can you remove it, and what the boot and
>> test output looks like?
>
>Aw, I wish ... the only things socketed on this board are the ROMs and
>the serial device. The CPU/FPU are 68 pin surface mount devices.
>
>
>> If you can't remove the FPU (likely), the diagnostics would probably be
>> complaining about it not working...
>
>Which is the main reason I'm not 100% convinced the FPU is faulty. But I
>can't get the extended disgnostics to test it, and I don't know how "good"
>it has to be to pass the basic startup test.
It doesnt other than not jamming the busses. VAX does nto need the FPU
to boot.
>
>> I've not had my uV2000 opened up (or even turned on yet...), but that'd
>> be my next step.
>>
>> Maybe if I have some time, I'll dig mine out and try playing with it.
>
>If you do open it up and have it to the point where you can scope signals,
>please contact me ... I've got a few questions about the signals I see in
>mine. I've also got a couple of questions about the diagnostics and the
>FPU that could be answered with a running system (only the console ROM
>required).
>
>If anyone has a running VS2000 or UV2000 and is willing to open it up to
>help me do some comparison testing, here are the things I would most like
>to know:
I had mine open for temperature testing, thats were I got the 58C
from. I should play with console boot later.
>[For best results, it would be good if the system were configured to match
>mine - all expansion boards, drives, peripherals etc. disconnected, and
>the uVAX/VS jumper located about 3" directly behind the BNC ethernet connector
>set to the uVAX position, which is AWAY from the BNC connector.]
Sounds like mine more or less. I cant scope it at this time as the wide
band scope is burried and likely not going to emerge for a while. I
have a 20mhz dual trace for most work handy as it's smaller but it
will not see a 40mhz clock well nor do I use it for that kind of work.
Allison
>[To run the extended diagnostics 101, 102 and 80000106 you need a DB-25-F
>connector installed (on the DB-25-M connector on the board) with pins 12
>and 18 connected together]
>
>a) Whats tests are run by the "T 101" command?
> Mine runs: C, B, 7, 6
>
>b) If you run "T 80000106" and then enter '9' at the "? >>>" prompt,
> do you get any test output other than the CPU designation title?
>
>[For the following, I would like a description of the waveforms
> observed, waveshape, amplitude and frequency where appropriate]
>
>c) The 40Mhz clock at the W4 jumper (right beside the 40Mhz oscillator
> "can") - with the jumper installed?
> I see 40Mhz sine wave, about 2.3v p-p
>
>d) The 40Mhz clock at the W4 jumper pin closest to the oscillator
> "can" with the jumper removed?
> I see 40Mhz sine wave about 3.4v p-p
>
>e) Pins on FPU
> 44 - I see about 160mv irregular square wave
> 59 - Same as above
> 15 - I see 40Mhz at about 160mv
>
>Dave
>
>--
>dave06a (at) Dave Dunfield
>dunfield (dot) Firmware development services & tools: www.dunfield.com
>com Collector of vintage computing equipment:
> http://www.classiccmp.org/dunfield/index.html
