779 karma · joined October 15, 2007
Feel free to contact me: drudru@gmail.com
Maybe we shouldn't drink and "crypto"? :-)
Everybody wants to point the finger at x, y, or z.
A lot of people think the fault is the government. Yet, how can the government tell private land owners what to do?
Personally I think this situation will work itself out once this artificial stimulus gets turned off. We are at zero percent interest rates! Crazy. Unfortunately, given the US populations dependence on this stimulus, they may not turn it off until it is way too late.
Seriously, I should have been more specific. If you take a comp. arch. class, then you get the generalization. After that, you can just read the relevant part of a manual.
Not all code written in the past ignored the hierarchy. The linux kernel itself had many tunings for this.
I looked for the original Warnock paper online, but it is behind the ACM paywall. That would at least tell me if they knew of that in the mid 80's.
I will check out the Doom 3 stuff. I had that on my reading list from a while back.
Thanks for your answer.
You just hit 'c' then enter.
http://www.cisco.com/c/en/us/support/docs/field-notices/misc...
On a Sun, NeXT, or Cisco box, you could hit a magic keyboard sequence (or send an RS-232 BREAK over the console) to get to the monitor. It was a very powerful thing to be able to interrupt the running OS, modify it, and then resume it. On the NeXT, you could even work with OS structures or sync the disks. The monitor typically had a disassembler and a simple single step debugger.
Earlier microcomputers also had these, and were helpful, but less powerful. For example, the Apple ][ had a monitor, but later ROMs did not allow you to invoke it with a key sequence.
On the later Suns and Power Macs, the monitor was implemented as a standard called Open Firmware. This was basically a standardized Forth acting as a Monitor. Device drivers could be embedded as a bytecode like sequence of Forth words for ethernet or display cards. That way, you could use newer devices even with old firmware and with any CPU. Very cool.
I wish this functionality would come back.
That pattern of cmd driven UI was very common in those days. I think just about every EDA package does that. However, instead of Lisp, they used TCL.
Thanks for sharing this. I think it is always great when people achieve powerful automation.