niiel07.cs.unm.edu | 198.83.92.77 |
niiel08.cs.unm.edu | 198.83.92.78 |
The two cards are now connected with the optical fiber patchcords.
Main lab number | 277-5529 |
RI office number | 277-5704 |
Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | |
---|---|---|---|---|---|---|---|
8 | |||||||
9 | Sec 014 | ||||||
10 | Sec 015 | ||||||
11 | Sec 016 | Sec 017 | Sec 018 | 12 | 1 | Sec 019 | Sec 020 | Sec 021 | Sec 022 | Sec 023 | 2 | Sec 024 | Sec 025 | Sec 026 | Sec 027 | 3 | 4:30 | Sec 028 | Sec 029 | 5 | 6 | 7 | Sec 030 | Sec 031 |
Ascii version of schedule (for lynx)
The real schedule--the boot schedule
All you have to do is run telnet from Windoze (start menu, run, then type telnet) and connect to somewhere like say joplin.cs.unm.edu, and then
cd /nfs/notrust/niiel/boot-schedule
oh.yes
then go ahead and reboot... when you're done and want to give NT a chance to boot again, just go to the same directory and type
oh.no
What this does is temporarily replace scheduling.pl with a sane version that sits tight while linux loads instead of sabotaging the system by booting Windoze. You'd think that it would be easier to temporarily replace the schedule.dat file, but they left the protection wrong on it, and the rc scripts are insistent on wanting scheduling.pl...
The other alternative is to try guess a workable value for the time and set it into the CMOS setup after resetting.