-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dazed_75 wrote:
> Thanks JT, that is better coverage of design goals and limits for edgy
> than I had seen.  It seems very much a pre-implementation document
> rather than a practical guide to understanding the actual implementation. 
> 
> So I am still seeking that (not very vigorously I should add).  One
> thing I wonder about which was not discussed there was what measures
> might be needed to support debugging the more dynamic startup, etc
> sequencing.  Seems to me this would demand much more vigorous logging
> and almost demand a means of retaining event history from times when the
> file system is r/o.  That history should be available if startup fails
> to a console (a possibility the article mentioned) and should be the
> first thing written and purged once the file system is r/w.  Oops,
> getting in over my head again.

yes it does demand differnt logging and I read about it in the original
doc but didn't read over the link above enough to see if it is there.

- --
JT Morée
PC Xperience, Inc.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFQ+NF1JwGi/ukQqERAn//AJ9C084SIY48o/yHBUarL0frBpGVjQCgmJgQ
6DpPz5Zu1mVq+S/us1liGHw=
=G3Dg
-----END PGP SIGNATURE-----

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change  you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss