HECnet

hecnet@lists.dfupdate.se

5 participants
15580 discussions

by HECNET＠beyondthepale.ie

Peter, I should be able to get round to testing this today. Great stuff. Let me know how you get on and I will try to help if necessary / possible. Just currently moving the system disk on the alpha from ODS-5 to OSD-2 so that we've got half a chance of clustering the VAX properly... I don't think the alpha system disk being ODS-5 should cause any problems clustering with a VAX. However, you would not be able to mount the ODS-5 disk from the VAX side of the cluster and from that point of view, it would be better if it was ODS-2. Regards, Peter Coghlan.

13 years, 12 months

Fwd: Re: [HECnet] More clustering fun

by mark＠wickensonline.co.uk

Peter, I should be able to get round to testing this today. Just currently moving the system disk on the alpha from ODS-5 to OSD-2 so that we've got half a chance of clustering the VAX properly... Mark. On Sat, 17 Sep 2011, Peter Coghlan wrote: It's all working nicely, but this is before an AUTOGEN. If I may I'll post the contents of the MODPARAMS.DAT and PARAMS.DAT to see if anyone recognises something bad. So, how did you get from where you were to where you are now? Have you recreated the system disk and got back to the point before you did the AUTOGEN? If so and you suspect AUTOGEN is going to mess things up again, then I suggest you record the system parameters before and after the AUTOGEN (AUTOGEN without the shutdown and reboot phases, that is) and compare them. Something like this: $ DEFINE /USER SYS$OUTPUT BEFORE.TXT $ MCR SYSGEN SHOW /ALL SHOW /SPECIAL ^Z $ $ @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS NOFEEDBACK $ $ DEFINE /USER SYS$OUTPUT AFTER.TXT $ MCR SYSGEN SHOW /ALL SHOW /SPECIAL ^Z $ $ DIFF BEFORE.TXT AFTER.TXT $ If everything looks ok, you can then reboot to get the new sysgen parameters take effect. If not, you have an opportunity to fix things before the shutdown and reboot makes things much more difficult to fix. Regards, Peter Coghlan.

13 years, 12 months

Noob question here: boot flags and such

by sampsa＠mac.com

That was meant for Steve Davidson :) Sampsa On 19 Sep 2011, at 00:50, Sampsa Laine wrote: Let me know if you're logging in today, have a quick chat. Might be awake :) Sampsa On 18 Sep 2011, at 14:42, Steve Davidson wrote: Actually, I would use: $ set default sys$system $ mcr sysgen use current set startup_p1 "" write current exit $ reboot -Steve -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Peter Coghlan Sent: Sunday, September 18, 2011 08:42 To: hecnet at Update.UU.SE Subject: Re: [HECnet] Noob question here: boot flags and such I've set my boot_flags to 0,0 in SRM, but it boots to a minimal DCL shell where I have to type @SYS$SYSTEM:STARTUP to get the ball rolling How do I stop this? At some point in the past, you probably did a SET /STARTUP OPA0: in a conversational boot and omitted to do a SET WRITESYSPARAMS 0 afterwards. To put things back the way they were, do another conversational boot ie BOOT -fl 0,1 At the SYSBOOT> prompt, issue the commands: SET /STARTUP SYS$SYSTEM:STARTUP.COM CONTINUE Next time you boot, you should get the full startup automatically. Regards, Peter Coghlan.

13 years, 12 months

Noob question here: boot flags and such

by sampsa＠mac.com

Let me know if you're logging in today, have a quick chat. Might be awake :) Sampsa On 18 Sep 2011, at 14:42, Steve Davidson wrote: Actually, I would use: $ set default sys$system $ mcr sysgen use current set startup_p1 "" write current exit $ reboot -Steve -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Peter Coghlan Sent: Sunday, September 18, 2011 08:42 To: hecnet at Update.UU.SE Subject: Re: [HECnet] Noob question here: boot flags and such I've set my boot_flags to 0,0 in SRM, but it boots to a minimal DCL shell where I have to type @SYS$SYSTEM:STARTUP to get the ball rolling How do I stop this? At some point in the past, you probably did a SET /STARTUP OPA0: in a conversational boot and omitted to do a SET WRITESYSPARAMS 0 afterwards. To put things back the way they were, do another conversational boot ie BOOT -fl 0,1 At the SYSBOOT> prompt, issue the commands: SET /STARTUP SYS$SYSTEM:STARTUP.COM CONTINUE Next time you boot, you should get the full startup automatically. Regards, Peter Coghlan.

13 years, 12 months

MMSRR (Mandatory Magic Smoke Release Report)

by mark＠wickensonline.co.uk

Fired up the newly acquired MicroVAX II today. Twice in fact. First time just to see if it did anything at all. Which it did - power supply kicked in, hard drive span up, I could see lights on the cards. Second time after connecting a console I fired it up whilst looking at the boot sequence LED on the back - went 9, 7, 6, 5, 4, 3, 2, then back to 8. It's possible the console wasn't connected properly - I think I should have seen the CPU model by this point on the console. Then the magic smoke let go. Prime candidate for smoke release are the mains filtering capacitors, but I've not extracted the power supply so cannot be sure. I'm getting a talent for blowing up power supplies these days... Mark.

13 years, 12 months

Noob question here: boot flags and such

by sampsa＠mac.com

That worked! Thanks guys. Sampsa On 18 Sep 2011, at 15:29, Peter Coghlan wrote: Actually, I would use: $ set default sys$system $ mcr sysgen use current set startup_p1 "" write current exit $ reboot The original poster said it boots to a minimal DCL shell. That sounds like a $ prompt to me. You get left at a $ prompt when SET /STARTUP has been set to OPA0:. You don't get a $ prompt when STARTUP_P1 is set to "MIN" - you have to log in as usual. He also stated that entering @SYS$SYSTEM:STARTUP manually fixed the problem. If STARTUP_P1 was set to "MIN" then entering @SYS$SYSTEM:STARTUP would not undo its effects and he would be left back where he started. It looks more likely to me that SET /STARTUP is the setting that has been modified not the STARTUP_P1 parameter. Rather than do a conversational boot, he could do: $ mcr sysgen use current set /startup sys$system:startup.com write current exit $ reboot For some reason, that method did not occur to me earlier. Regards, Peter Coghlan.

13 years, 12 months

Noob question here: boot flags and such

by HECNET＠beyondthepale.ie

Actually, I would use: $ set default sys$system $ mcr sysgen use current set startup_p1 "" write current exit $ reboot The original poster said it boots to a minimal DCL shell. That sounds like a $ prompt to me. You get left at a $ prompt when SET /STARTUP has been set to OPA0:. You don't get a $ prompt when STARTUP_P1 is set to "MIN" - you have to log in as usual. He also stated that entering @SYS$SYSTEM:STARTUP manually fixed the problem. If STARTUP_P1 was set to "MIN" then entering @SYS$SYSTEM:STARTUP would not undo its effects and he would be left back where he started. It looks more likely to me that SET /STARTUP is the setting that has been modified not the STARTUP_P1 parameter. Rather than do a conversational boot, he could do: $ mcr sysgen use current set /startup sys$system:startup.com write current exit $ reboot For some reason, that method did not occur to me earlier. Regards, Peter Coghlan.

13 years, 12 months

Noob question here: boot flags and such

by jeep＠scshome.net

Actually, I would use: $ set default sys$system $ mcr sysgen use current set startup_p1 "" write current exit $ reboot -Steve -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Peter Coghlan Sent: Sunday, September 18, 2011 08:42 To: hecnet at Update.UU.SE Subject: Re: [HECnet] Noob question here: boot flags and such I've set my boot_flags to 0,0 in SRM, but it boots to a minimal DCL shell where I have to type @SYS$SYSTEM:STARTUP to get the ball rolling How do I stop this? At some point in the past, you probably did a SET /STARTUP OPA0: in a conversational boot and omitted to do a SET WRITESYSPARAMS 0 afterwards. To put things back the way they were, do another conversational boot ie BOOT -fl 0,1 At the SYSBOOT> prompt, issue the commands: SET /STARTUP SYS$SYSTEM:STARTUP.COM CONTINUE Next time you boot, you should get the full startup automatically. Regards, Peter Coghlan.

13 years, 12 months

Noob question here: boot flags and such

by HECNET＠beyondthepale.ie

I've set my boot_flags to 0,0 in SRM, but it boots to a minimal DCL shell where I have to type @SYS$SYSTEM:STARTUP to get the ball rolling How do I stop this? At some point in the past, you probably did a SET /STARTUP OPA0: in a conversational boot and omitted to do a SET WRITESYSPARAMS 0 afterwards. To put things back the way they were, do another conversational boot ie BOOT -fl 0,1 At the SYSBOOT> prompt, issue the commands: SET /STARTUP SYS$SYSTEM:STARTUP.COM CONTINUE Next time you boot, you should get the full startup automatically. Regards, Peter Coghlan.

13 years, 12 months

Off-topic: Pyffle BBC

by wonko＠4amlunch.net

Even more off topic topics. :) A) I've gone and set CircleMUD up again. Running on a Solaris box at the moment but after we move I plan on getting the VAXen set up again at which point I'll move it to one of those. Mud.4amlunch.net port 4000. Prepare to be bored as there are no users yet. :) B) If you've not seen Schemaverse yet I *highly* recommend checking it out. www.schemaverse.com. Quite possibly the craziest and coolest thing I've seen in a while. Space game you play in PostgreSQL. That's my random whatever for the day. :) -brian On Sep 17, 2011, at 15:13, Sampsa Laine <sampsa at mac.com> wrote: Speaking of masochism, I've released a pre-built VM with a very alpha version of my BBS, pyffle: Pyffle BBS: http://www.uuhec.net/pyffle-bbs/ Demo version running: telnet://pyffle.sampsa.com `` VM download (pretty big, for the seriously into UUUP etc enthusiastic): http://pyffle.org/dev_pyffle_v0.1_masochist_edition.zip Sampsa On 17 Sep 2011, at 19:22, Mark Wickens wrote: On 17/09/11 19:21, Fred wrote: Hi all: I'd like to slap All-in-1 on my VAX. (yes, I'm a masochist) Anyone have the kit available via HECnet? Or, alternatively you can deposit it on FRUGAL:: Thanks, Fred ---- Lets call it for what it is - "legacy" is a term that people use in a polite but derogatory manner to imply that the future direction they prefer is not that which they view as the current direction. ALLIN1 is fun! As you say, for masochists. I have it on SLAVE, I'll move it so it's available from the default account...

13 years, 12 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet