On 9 Feb 2013, at 02:27, Cory Smelosky <b4 at gewt.net> wrote:
On 8 Feb 2013, at 19:23, Sampsa Laine <sampsa at mac.com> wrote:
On 9 Feb 2013, at 02:05, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-02-09 00:59, Sampsa Laine wrote:
I'm thinking of tweaking the HECNET infoservice* on RHESUS, and figured it'd be nice if the nodes in the output of NCP SHOW KNOWN NODES were hyperlinks.
On Unix I would just replace all the "(" characters with an opening <a> + "(" tag and all the ")" with a closing </a> tag + ")" using sed.
What's the correct DCL way to do this?
sampsa
* This is the page I'm thinking of tweaking: http://rhesus.sampsa.com/cgi-bin/hecnetinfo/hecnetinfo.com
TECO? :-)
<FS($(<a>$FS)$</a>)$;>
But I don't think just a <a> tag would be enough, would it? Wouldn't you want a href in there, and so on?
Of course, but I left that out for the sake of brevity. How do I invoke TECO on VMS? I've only heard apocryphal tales of it's less than simple syntax, never actually used it..
I believe edit/teco should work.
So the full command would look something like:
$MCR NCP SHOW KNOWN NODES TO FOOBAR
$EDIT/TECO FOOBAR.LIST
<FS($(<a>$FS)$</a>)$;>
[...something to quit TECO goes here...]
How do I exit TECO?
sampsa
El 09/02/2013, a les 1:23, Sampsa Laine <sampsa at mac.com> va escriure:
Of course, but I left that out for the sake of brevity. How do I invoke TECO on VMS? I've only heard apocryphal tales of it's less than simple syntax, never actually used it..
EDIT/TECO
VMS is easy :)
But perhaps you will want to take a look at SUMSLP.
http://h71000.www7.hp.com/doc/73final/documentation/pdf/ovms_sumslp_util.pdf
Or even to TPU... :)
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
El 09/02/2013, a les 0:45, Johnny Billquist <bqt at softjar.se> va escriure:
:-)
Emulated Unibus-machine, or the real deal?
Unfortunately, just my 2 QBUS uVAXen and the 2 VAXstations are real. The rest is emulated. But right now I have all my real metal online. It's quite cold here and those machines make a nice heath system hehehe
(The $SHOW NET was done in an emulated 780 btw...)
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
On 8 Feb 2013, at 19:23, Sampsa Laine <sampsa at mac.com> wrote:
On 9 Feb 2013, at 02:05, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-02-09 00:59, Sampsa Laine wrote:
I'm thinking of tweaking the HECNET infoservice* on RHESUS, and figured it'd be nice if the nodes in the output of NCP SHOW KNOWN NODES were hyperlinks.
On Unix I would just replace all the "(" characters with an opening <a> + "(" tag and all the ")" with a closing </a> tag + ")" using sed.
What's the correct DCL way to do this?
sampsa
* This is the page I'm thinking of tweaking: http://rhesus.sampsa.com/cgi-bin/hecnetinfo/hecnetinfo.com
TECO? :-)
<FS($(<a>$FS)$</a>)$;>
But I don't think just a <a> tag would be enough, would it? Wouldn't you want a href in there, and so on?
Of course, but I left that out for the sake of brevity. How do I invoke TECO on VMS? I've only heard apocryphal tales of it's less than simple syntax, never actually used it..
I believe edit/teco should work.
sampsa
--
Cory Smelosky
http://gewt.net/ Personal stuff!
http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.
On 9 Feb 2013, at 02:05, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-02-09 00:59, Sampsa Laine wrote:
I'm thinking of tweaking the HECNET infoservice* on RHESUS, and figured it'd be nice if the nodes in the output of NCP SHOW KNOWN NODES were hyperlinks.
On Unix I would just replace all the "(" characters with an opening <a> + "(" tag and all the ")" with a closing </a> tag + ")" using sed.
What's the correct DCL way to do this?
sampsa
* This is the page I'm thinking of tweaking: http://rhesus.sampsa.com/cgi-bin/hecnetinfo/hecnetinfo.com
TECO? :-)
<FS($(<a>$FS)$</a>)$;>
But I don't think just a <a> tag would be enough, would it? Wouldn't you want a href in there, and so on?
Of course, but I left that out for the sake of brevity. How do I invoke TECO on VMS? I've only heard apocryphal tales of it's less than simple syntax, never actually used it..
sampsa
On 2013-02-09 00:59, Sampsa Laine wrote:
I'm thinking of tweaking the HECNET infoservice* on RHESUS, and figured it'd be nice if the nodes in the output of NCP SHOW KNOWN NODES were hyperlinks.
On Unix I would just replace all the "(" characters with an opening <a> + "(" tag and all the ")" with a closing </a> tag + ")" using sed.
What's the correct DCL way to do this?
sampsa
* This is the page I'm thinking of tweaking: http://rhesus.sampsa.com/cgi-bin/hecnetinfo/hecnetinfo.com
TECO? :-)
<FS($(<a>$FS)$</a>)$;>
But I don't think just a <a> tag would be enough, would it? Wouldn't you want a href in there, and so on?
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
I'm thinking of tweaking the HECNET infoservice* on RHESUS, and figured it'd be nice if the nodes in the output of NCP SHOW KNOWN NODES were hyperlinks.
On Unix I would just replace all the "(" characters with an opening <a> + "(" tag and all the ")" with a closing </a> tag + ")" using sed.
What's the correct DCL way to do this?
sampsa
* This is the page I'm thinking of tweaking: http://rhesus.sampsa.com/cgi-bin/hecnetinfo/hecnetinfo.com
On 2013-02-08 23:31, Jordi Guillaumes i Pons wrote:
El 08/02/2013, a les 23:14, Johnny Billquist <bqt at softjar.se> va escriure:
And the problem is just that the boot rom uses a more restricted disk block addressing, limiting the
booting to disks of less than 1G. (Actually, you can boot from larger disks as well, as long as the boot
rom don't need to read from anything above 1G.)
Nice to know. IIRC I read about the firmware dropping the high bits of the block address so at some point
in time the writes against the disk would "wrap around" and trash the first 4GBs... but it seems its quite
an urban legend :)
No. That is correct. And it's 1G, not 4G. SCSI commands comes in some different flavors. Old VAXstations (and some others) used 6 byte SCSI commands, which limited the block numbers to 20 bits (some say 21, but I think it is 20). Later systems use 10 byte SCSI commands, which allows for 32 bit block numbers.
What happens is that if you go above 20 bits in the SCSI commands of those old VAXen, they will just use the low 20 bits of the block number, so you will indeed wrap.
See http://labs.hoffmanlabs.com/node/218 if you want a few more details.
BTW, This is a nice sight:
$ sh net
VAX/VMS Network status for local node 7.61 BITXOO on 8-FEB-2013 23:26:08.76
The next hop to the nearest area router is node 7.60 BITXOV.
Node Links Cost Hops Next Hop to Node
7.61 BITXOO 0 0 0 (Local) -> 7.61 BITXOO
7.6 MBSERV 0 3 1 UNA-0 -> 7.6 MBSERV
7.60 BITXOV 0 3 1 UNA-0 -> 7.60 BITXOV
7.64 BITXO1 0 3 1 UNA-0 -> 7.64 BITXO1
7.65 BITXO2 0 3 1 UNA-0 -> 7.65 BITXO2
7.67 BITXO4 0 3 1 UNA-0 -> 7.67 BITXO4
7.68 BITXO5 0 3 1 UNA-0 -> 7.68 BITXO5
7.70 BITXOT 0 3 1 UNA-0 -> 7.70 BITXOT
7.71 BITXOR 0 3 1 UNA-0 -> 7.71 BITXOR
7.72 BITXOM 0 3 1 UNA-0 -> 7.72 BITXOM
7.74 BITXOW 0 3 1 UNA-0 -> 7.74 BITXOW
7.79 BITXT0 0 3 1 UNA-0 -> 7.79 BITXT0
:-)
Emulated Unibus-machine, or the real deal?
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
El 08/02/2013, a les 23:14, Johnny Billquist <bqt at softjar.se> va escriure:
And the problem is just that the boot rom uses a more restricted disk block addressing, limiting the booting to disks of less than 1G. (Actually, you can boot from larger disks as well, as long as the boot rom don't need to read from anything above 1G.)
Nice to know. IIRC I read about the firmware dropping the high bits of the block address so at some point in time the writes against the disk would "wrap around" and trash the first 4GBs... but it seems its quite an urban legend :)
BTW, This is a nice sight:
$ sh net
VAX/VMS Network status for local node 7.61 BITXOO on 8-FEB-2013 23:26:08.76
The next hop to the nearest area router is node 7.60 BITXOV.
Node Links Cost Hops Next Hop to Node
7.61 BITXOO 0 0 0 (Local) -> 7.61 BITXOO
7.6 MBSERV 0 3 1 UNA-0 -> 7.6 MBSERV
7.60 BITXOV 0 3 1 UNA-0 -> 7.60 BITXOV
7.64 BITXO1 0 3 1 UNA-0 -> 7.64 BITXO1
7.65 BITXO2 0 3 1 UNA-0 -> 7.65 BITXO2
7.67 BITXO4 0 3 1 UNA-0 -> 7.67 BITXO4
7.68 BITXO5 0 3 1 UNA-0 -> 7.68 BITXO5
7.70 BITXOT 0 3 1 UNA-0 -> 7.70 BITXOT
7.71 BITXOR 0 3 1 UNA-0 -> 7.71 BITXOR
7.72 BITXOM 0 3 1 UNA-0 -> 7.72 BITXOM
7.74 BITXOW 0 3 1 UNA-0 -> 7.74 BITXOW
7.79 BITXT0 0 3 1 UNA-0 -> 7.79 BITXT0
Now, if I could just fix poor BITXO3 (which is a VS 3100 with a toasted cache in the mobo...).
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
On 2013-02-08 21:52, Jordi Guillaumes i Pons wrote:
Oh, now I need a disk for that machine. Right now it is running diskless as a satellite of my 4000/60,
paging via ethernet (ouch!). I have some SCA-68-50 pin adapters for SCSI disks, and I have used those
with success with 4GB drives, but I have read somewhere the vaxstation firmware can't handle disks bigger
than that. Anyone knows if that is true? Can I plug in a generic, big SCSI disk and hope it will work?
Sigh. The misinformation that keeps spreading. The problem is for specific older VAXen. I think it's even only specific 3100 models. And the problem is just that the boot rom uses a more restricted disk block addressing, limiting the booting to disks of less than 1G. (Actually, you can boot from larger disks as well, as long as the boot rom don't need to read from anything above 1G.)
Once the OS starts, it uses its own device driver, and then you don't have the restriction either.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol