Johnny Billquist
On 2010-10-17 04:01, Johnny Billquist wrote:
So here is a new suggestion for the bridge which is "hubbed" around Update.
0 Publicly available systems
1 Update
2 BQT
Let me know, and I'll happily assign LAT groups for others as well.
Small correction to that list:
0 Public systems
1 Update
2 Update
3 BQT
4 BQT
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 forgot to mention in my last mail that only one of my machines makes use
of group 0. That is the RSTS/E system. I let it broadcast group 0 because
it appears to be the only active RSTS/E system on the network. This way
anyone in HECnet (with LAT access) may get to it (if they have an account
that is).
-Steve
Johnny Billquist
On 2010-10-17 04:01, Johnny Billquist wrote:
So here is a new suggestion for the bridge which is "hubbed" around Update.
0 Publicly available systems
1 Update
2 BQT
Let me know, and I'll happily assign LAT groups for others as well.
Small correction to that list:
0 Public systems
1 Update
2 Update
3 BQT
4 BQT
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
Johnny,
The way I do it around here is use group 0 for public access. It is the
default group anyway. I use group 19, which is also my DECnet area for my
private use. This allows us to have 63 private areas if we map to DECnet area
numbers. Areas from 64 to 255 can be special case. I use 64 whe I want to
combine my group with someone else.
I would suggest that
group 0 be public
group 1 through 63 be private based on DECnet area # (self managed)
groups 64-255 be managed (and reserved) (each area could have 4 such #s)
Because I am already using group 64 I am reserving it. I make it available to
others when it makes sense for me to "share" as it were. Reserved groups
should be by invitation only because as you point out the list does get
cluttered.
The use of passwords is a great idea for the DECservers we have in HECnet.
Some of mine have it, some do not - personal choice.
-Steve
On 2010-10-17 04:01, Johnny Billquist wrote:
So here is a new suggestion for the bridge which is "hubbed" around Update.
0 Publicly available systems
1 Update
2 BQT
Let me know, and I'll happily assign LAT groups for others as well.
Small correction to that list:
0 Public systems
1 Update
2 Update
3 BQT
4 BQT
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
On 2010-10-17 03:43, Johnny Billquist wrote:
On 2010-10-17 03:34, Johnny Billquist wrote:
Hi. As a few people are sharing LAT connections now as well, I thought
I'd make a suggestion on how to make this a bit more manageable.
If people have questions on LAT, how to set up DECservers, or something
else, you can as usual just mail me.
First of all, please note that LAT is not a safe protocol. Everything
goes in clear text, and malicious people can easily snoop your sessions.
My thoughts right now are in the area of services offered. When I list
services I notice that some machine consoles are available, as well as
some general machine logins.
The console services are nice to have (I also have a few of those),
however, they are not useful for the general public, and the hope is
that people who don't have anything to do with them don't connect to
them. But they do clutter up the list of available services anyhow.
What I'd like to propose is that for services that aren't of general use
should switch to another group. The default group is group #0, and that
group is nice to continue to use for generally available systems that
people might want to log in to.
I've been using group 1 for consoles for now, and I'd suggest that
others do that too. Or perhaps pick some other group if you want to keep
your machines separate. Notice that this does not really add anything
from a security point of view, since people can change their own port to
see services in any group if they really want to.
But if people set up their port to by default only be in group 0, and we
place consoles in group 1, they will not show up in the general case,
and you'd have to explicitly turn on group 1 when you want to play with
consoles (or if you want it on by default, feel free, but it will look
nicer to some atleast).
The same goes if you have printers, for instance, as services. Place
them also in another group. Preferably in yet another group, but atleast
not in group 0. And modems as well, if you have those.
So a suggested division of groups would be as follows:
0 General systems where people might log in.
1 Consoles
2 Modems
3 Printers
If you have all of that on the same DECserver you cannot be picky,
however, since you can only specify one group for all services offered.
Use the lowest group number for which you have a matching service in
that case.
Note that the group numbers only affect which services are visible to
users connected to a DECserver. It does not affect reverse LAT
connections, which will find the right service no matter which group it
is in.
So this is mostly just to make the list of services more convenient when
you look as an interactive user on a DECserver.
Finally a short suggestion for those of you who have consoles as
services. If you haven't found it, or set it up, I'd also suggest you
place a password on those services, which can limit the possibility of
others to wreak havoc on your machines... Just a suggestion.
It will still not prevent others from potentially DoS your console port.
I just had another idea as well.
Would people think it would be an interesting idea to have group numbers
for machines differentiate depending on OS? So that people could see
what VMS systems there are to connect to without seeing other systems?
Or maybe it would be more meaningful if we use group 0 for systems where
guest access is available, and then people use their own groups for
"local" systems?
Oh yeah, I should probably point out that all of this is only relevant to the people running my bridge program on the same segment I am. Others can obviously do as they want, since that is not visible to me anyway.
Thinking a bit more about it, it actually makes more sense to use one group (0) for all publicly available systems, and a separate group (or two) where you can place all private machines, console ports, printers, modems and so on. That way you can see all services relevant to you, without being bothered about services that you don't care about, or can use anyway...
So here is a new suggestion for the bridge which is "hubbed" around Update.
0 Publicly available systems
1 Update
2 BQT
Let me know, and I'll happily assign LAT groups for others as well.
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
On 2010-10-17 03:34, Johnny Billquist wrote:
Hi. As a few people are sharing LAT connections now as well, I thought
I'd make a suggestion on how to make this a bit more manageable.
If people have questions on LAT, how to set up DECservers, or something
else, you can as usual just mail me.
First of all, please note that LAT is not a safe protocol. Everything
goes in clear text, and malicious people can easily snoop your sessions.
My thoughts right now are in the area of services offered. When I list
services I notice that some machine consoles are available, as well as
some general machine logins.
The console services are nice to have (I also have a few of those),
however, they are not useful for the general public, and the hope is
that people who don't have anything to do with them don't connect to
them. But they do clutter up the list of available services anyhow.
What I'd like to propose is that for services that aren't of general use
should switch to another group. The default group is group #0, and that
group is nice to continue to use for generally available systems that
people might want to log in to.
I've been using group 1 for consoles for now, and I'd suggest that
others do that too. Or perhaps pick some other group if you want to keep
your machines separate. Notice that this does not really add anything
from a security point of view, since people can change their own port to
see services in any group if they really want to.
But if people set up their port to by default only be in group 0, and we
place consoles in group 1, they will not show up in the general case,
and you'd have to explicitly turn on group 1 when you want to play with
consoles (or if you want it on by default, feel free, but it will look
nicer to some atleast).
The same goes if you have printers, for instance, as services. Place
them also in another group. Preferably in yet another group, but atleast
not in group 0. And modems as well, if you have those.
So a suggested division of groups would be as follows:
0 General systems where people might log in.
1 Consoles
2 Modems
3 Printers
If you have all of that on the same DECserver you cannot be picky,
however, since you can only specify one group for all services offered.
Use the lowest group number for which you have a matching service in
that case.
Note that the group numbers only affect which services are visible to
users connected to a DECserver. It does not affect reverse LAT
connections, which will find the right service no matter which group it
is in.
So this is mostly just to make the list of services more convenient when
you look as an interactive user on a DECserver.
Finally a short suggestion for those of you who have consoles as
services. If you haven't found it, or set it up, I'd also suggest you
place a password on those services, which can limit the possibility of
others to wreak havoc on your machines... Just a suggestion.
It will still not prevent others from potentially DoS your console port.
I just had another idea as well.
Would people think it would be an interesting idea to have group numbers for machines differentiate depending on OS? So that people could see what VMS systems there are to connect to without seeing other systems?
Or maybe it would be more meaningful if we use group 0 for systems where guest access is available, and then people use their own groups for "local" systems?
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
Hi. As a few people are sharing LAT connections now as well, I thought I'd make a suggestion on how to make this a bit more manageable.
If people have questions on LAT, how to set up DECservers, or something else, you can as usual just mail me.
First of all, please note that LAT is not a safe protocol. Everything goes in clear text, and malicious people can easily snoop your sessions.
My thoughts right now are in the area of services offered. When I list services I notice that some machine consoles are available, as well as some general machine logins.
The console services are nice to have (I also have a few of those), however, they are not useful for the general public, and the hope is that people who don't have anything to do with them don't connect to them. But they do clutter up the list of available services anyhow.
What I'd like to propose is that for services that aren't of general use should switch to another group. The default group is group #0, and that group is nice to continue to use for generally available systems that people might want to log in to.
I've been using group 1 for consoles for now, and I'd suggest that others do that too. Or perhaps pick some other group if you want to keep your machines separate. Notice that this does not really add anything from a security point of view, since people can change their own port to see services in any group if they really want to.
But if people set up their port to by default only be in group 0, and we place consoles in group 1, they will not show up in the general case, and you'd have to explicitly turn on group 1 when you want to play with consoles (or if you want it on by default, feel free, but it will look nicer to some atleast).
The same goes if you have printers, for instance, as services. Place them also in another group. Preferably in yet another group, but atleast not in group 0. And modems as well, if you have those.
So a suggested division of groups would be as follows:
0 General systems where people might log in.
1 Consoles
2 Modems
3 Printers
If you have all of that on the same DECserver you cannot be picky, however, since you can only specify one group for all services offered. Use the lowest group number for which you have a matching service in that case.
Note that the group numbers only affect which services are visible to users connected to a DECserver. It does not affect reverse LAT connections, which will find the right service no matter which group it is in.
So this is mostly just to make the list of services more convenient when you look as an interactive user on a DECserver.
Finally a short suggestion for those of you who have consoles as services. If you haven't found it, or set it up, I'd also suggest you place a password on those services, which can limit the possibility of others to wreak havoc on your machines... Just a suggestion.
It will still not prevent others from potentially DoS your console port.
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
On 2010-10-05 23:59, Mark Wickens wrote:
Hi Guys,
Just to let you know that we had a circuit breaker trip here today and
when I restarted the VAXstation 4000/90 the Seagate ST39173N system disk
no longer spins up. The controller recognises the drive, and an LED on
the drive circuit board flashes once on power up and when it is queried
by the SCSI controller, but at no point does the drive spin up.
Ouch! Always unpleasant...
Try to perhaps shake it a bit if it is stuck.
Does anyone have any tips? I thought I had a duplicate drive I could try
swapping the controller board with, but I've yet to locate it. It might
be stuck heads, but given the circumstances it is more likely to be
something that has gone bang.
Stuck heads, or sometimes stuck spindle. Shaking might help. But you might be right in that it's something more serious...
This box hasn't been backed up in a while. I may have a working version
of the website on a backup, but there will be a few features missing if
the restore works.
Even worse.
In the meantime the website will be down.
Oh and also, if you haven't done that backup in a while, NOW IS THE TIME
TO DO IT!!!
You mean something like this?
.set /host
Host=PONDUS RSX-11M-PLUS V4.6 BL87
.que /li
** PRINT QUEUES **
PRINT (STOPPED) => TT30
FTSQUE => FTSDEQ
TT26 (STOPPED) => TT26
TT30 (STOPPED) => TT30
** BATCH QUEUES **
BATCH => BAP0 BAP1
[7,14] DST ENTRY:878 BLOCKED UNTIL 31-OCT-10 03:00
1 DU0:[DST]SETWINTER.BAT;1
BACKUP => BAP0 BAP1
[1,54] BACKUP ENTRY:913 BLOCKED UNTIL 13-OCT-10 09:00
1 DU0:[BACKUP]BACKUP.BAT;1
.sha dis
UMB Devices I/O Errors Status
055330 DU0:,*DU1: 0. 0. Load_Share, Catchup complete
.
(Backup job is run every week, and disk is mirrored...)
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
Mark, my best guess is that the spindle is stuck. Put the drive upside down, reconnect and power on. The cables in a 4000-90 allow for this. If that fails, put it on its side, tap the spindle with a hammer and power up. It may just spin up one last time.
Hans
------Origineel bericht------
Van:Mark Wickens
Afzender:owner-hecnet at Update.UU.SE
Aan:hecnet at Update.UU.SE
Beantwoorden:hecnet at Update.UU.SE
Onderwerp: [HECnet] hecnet.eu website down
Verzonden: 5 okt. 2010 23:59
Hi Guys,
Just to let you know that we had a circuit breaker trip here today and
when I restarted the VAXstation 4000/90 the Seagate ST39173N system disk
no longer spins up. The controller recognises the drive, and an LED on
the drive circuit board flashes once on power up and when it is queried
by the SCSI controller, but at no point does the drive spin up.
Does anyone have any tips? I thought I had a duplicate drive I could try
swapping the controller board with, but I've yet to locate it. It might
be stuck heads, but given the circumstances it is more likely to be
something that has gone bang.
This box hasn't been backed up in a while. I may have a working version
of the website on a backup, but there will be a few features missing if
the restore works.
In the meantime the website will be down.
Oh and also, if you haven't done that backup in a while, NOW IS THE TIME
TO DO IT!!!
Regards,
Mark.
Verzonden vanaf mijn draadloze BlackBerry -toestel
Hi Guys,
Just to let you know that we had a circuit breaker trip here today and when I restarted the VAXstation 4000/90 the Seagate ST39173N system disk no longer spins up. The controller recognises the drive, and an LED on the drive circuit board flashes once on power up and when it is queried by the SCSI controller, but at no point does the drive spin up.
Does anyone have any tips? I thought I had a duplicate drive I could try swapping the controller board with, but I've yet to locate it. It might be stuck heads, but given the circumstances it is more likely to be something that has gone bang.
This box hasn't been backed up in a while. I may have a working version of the website on a backup, but there will be a few features missing if the restore works.
In the meantime the website will be down.
Oh and also, if you haven't done that backup in a while, NOW IS THE TIME TO DO IT!!!
Regards,
Mark.
