by Gregory Bruce Chewnin » Tue, 03 Nov 1998 04:00:00
by Glenn Weinbe » Wed, 04 Nov 1998 04:00:00
You don't. The PROM doesn't do dates. Set the date with the date(1)Quote:>For y2k testing, how do you change the date without using the OS.
Regards,
Glenn
--
Opinions expressed above should not be construed as representing any position,
official or unofficial, of Sun Microsystems, Inc.
by Glenn Weinbe » Sun, 08 Nov 1998 04:00:00
>I'm not sure about on an Ultra 5, but I have a document that tells how
>to do it on a sun4c machine (i.e. SPARCstation 1, 1+, 2, etc.) and gives
>a different procedure (I believe) for sun4m machines (SPARC 5, 20, etc.).
>Here's an excerpt:
> [Lengthy procedure to set the date by writing directly to TOD chip
> registers deleted.]
>Of course, the procedure will probably be significantly different
>on a sun4u (like your Ultra 5), and messing up stuff like this is
>likely to cause you a great deal of pain (it could make your machine
>unusable in a way that even powering off won't remedy).
And besides, this isn't a "command" to set the date any more than a
similar adb script would be a "command" to set the date in Unix.
Regards,
Glenn
--
Opinions expressed above should not be construed as representing any position,
official or unofficial, of Sun Microsystems, Inc.
by Matthew Sa » Tue, 10 Nov 1998 04:00:00
I can see at least one use for this. Our Y2K team demands thatQuote:>Seems like an awful lot of trouble to go to just to avoid using the
>date(1) command. Not to mention the added risk.
So we would need a method to change the clock on the hardware
without a booted os. Just another Y2K thorn in my side.
-Matthew
by Rich Tee » Tue, 10 Nov 1998 04:00:00
I think your Y2K team have been using peecees too long! AllQuote:> I can see at least one use for this. Our Y2K team demands that
> we test all our hardware for Y2K compliance before loading
> an os. Basically you unit test each layer before going to the
> next layer, eg hardware, os, system tools, database, applications.
Heh - their instructions probably call the OBP the BIOS, too...Quote:> So we would need a method to change the clock on the hardware
> without a booted os. Just another Y2K thorn in my side.
--
Rich Teer
If it ain't analogue, it ain't music.
Risc Key Developments Ltd
Voice: +44 (0)1256 330612
WWW: www.rkdltd.demon.co.uk
by Eric McGoug » Fri, 13 Nov 1998 04:00:00
http://www.sun.com/y2000/cpl.html
Eric McGough
1. Netra t1 dropping to PROM level
I've got a problem with 2 Netra t1 105 running Solaris 8: as they are both
connected to a computer we use as serial console, they drop to the ok prompt
whenever this 'terminal-computer' is rebooted or switched off.
This is, after all, a well known problem and the solution should be easy:
setting an alternate break-sequence in /etc/default/kbd. This indeed worked
for an Enterprise 220R, but the two Netras are simply ignoring the
KEYBOARD_ABORT=alternate
statement.
There is no error-message calling 'kbd -i', all looks as if the command
works. The Netras, however, still drop to the PROM-level whenever the
'terminal-computer' is rebooted or turned off.
Is there any solution that still allows to send a break to the machines if
it is necessary but prevents them from dropping to PROM-level at
terminal-shutdown? Thank you.
Regards,
Markus
3. Get the machine into the Prom level
4. testing
5. Problem changing date to future date
6. Using AMSTRAD CPC-464 as terminal.
7. Recommended changes to OpenBoot PROM
9. HOW TO: Change PROM password
10. Change boot_device in PROM
11. getting up to date on Patch levels
12. ufsdump: Date of last level 0 dump: the epoch ?
13. Errors during init level change -- HELP