On Fri, 2003-01-10 at 18:00, Alan Grimes wrote: > > This is a perfectly rational approach. In fact, a lot of big server > > apps such as database servers all run on their own "kernels" which > > provide their own implementations of the services that an operating > > system normally provides. > > How is that done on eew-nix? > > I know a fair ammount about the standard library and how you can fork > off paralell processes, but I don't understand how you can set policy > for those subprocesses in any meaningful way...
Errrr.... Actually, all these things are pretty easy for an experienced software engineer, PARTICULARLY on Unix systems. It is pretty basic C-language stuff to hijack or partially hijack operating system functionality within their application space. Lots of applications do it to one extent or another, especially server type apps. There really isn't any other way to put this, but it is painfully obvious that you don't know very much about systems and software engineering. How do you expect to develop AI if questions like this stump you? Real-world systems have a certain amount of irreducible complexity that really aren't capable of being made any simpler for your benefit; if the system could read your mind, then we really wouldn't need AI. When I talk to a person actually working on AI, I kind of expect them to have a fairly good grasp of what you can and can't do in software and why things are done the way they are. It seems to me, and not just from this post, that you really need to get a better grounding in the engineering details of designing software systems first rather than just blithely dismissing it with your stamp of disapproval. If you are going to design a silicon brain perhaps you should learn how silicon systems actually work, no? Cheers, -James Rogers [EMAIL PROTECTED] ------- To unsubscribe, change your address, or temporarily deactivate your subscription, please go to http://v2.listbox.com/member/?[EMAIL PROTECTED]
