| To: | yyyyyyyyyyyyyyy@xxxxxxxxxxxxx |
|---|---|
| Subject: | Re: Defect in XBD 3.386_System_Reboot |
| From: | Larry Dwyer <yyyyyyyyyyy@xxxxxx> |
| Date: | Sun, 10 Aug 2003 00:59:06 -0700 |
At 09:53 AM 8/8/2003, SHwareSyst@xxxxxx wrote:In a message dated 2003-08-07 7:08:58 PM Eastern Daylight Time, Larry.Dwyer@xxxxxx writes: The logical model of on power up the implementaion does go through discernable boot time phases... RAM detection, low-level peripheral detection and initialization, executing low level supervisory processes from ROM, mounting filesystems, associating generic drivers with specific hardware, creating a primary user process, login, etc. Cheers again, Mark Not on a Highly Available (HA) system. They neither shutdown nor reboot. No portable application can be written to deal with system transitions (such as memory replacement, CPU replacement, disk replacement, interface card replacement ... Should the POSIX standard mandate that HA systems must reboot? |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Defect in XCU c99, don.cragun |
|---|---|
| Next by Date: | Re: Defect in XBD 3.386_System_Reboot, SHwareSyst |
| Previous by Thread: | Re: Defect in XBD 3.386_System_Reboot, SHwareSyst |
| Next by Thread: | Re: Defect in XBD 3.386_System_Reboot, SHwareSyst |
| Indexes: | [Date] [Thread] [All Lists] |