I agree 100%
If there's Lithium in the water, it's likely that the populace won't -revolt- either.
That's why Lithium is an important ingredient of Soylent Green.
Where's all my cool Linux stuff on Solaris, though?
Linux by itself is "just" a kernel. Solaris has a decent kernel of its own, doesn't need Linux. Lots of GNU in userland though, about as much as in GNU/Linux.
I just call her HRH E2R.
That should be HRM, you insensitive clod! She'll ban you to the Falkland Islands.
stun guns, Van der Graaf Generator..."
That's far too exotic. A few seconds in a microwave oven will do, including sparks and blue smoke.
The link in the parent comment caused my X session to unexpectedly terminate.
One X won't do, you need a triple-X session.
$ man woman
No manual entry for woman.
The lock.gif image will still exist on the server whether you're logged in or not.
It's not about whether or not the image (or any other element, it doesn't have to be an image) exists, but rather if the request for it will be honoured by the bank server.
This scheme works for any request that is answered only when the user is logged in.
(wow, this feel childish)
Parent posted said that 386 offered some new feature that enabled preemptive multitasking. Ie. that it was not possible in earlier CPUs.
I read that, and I wondered which feature that might have been.
It was possible on earlier CPUs: a long time ago I wrote a tiny preemptive multitasking kernel on a 8086 as an exercise.
Preemption of the running task and switching to (dispatching) another one was done in an interrupt service routine, triggered by a timer.
A kernel implementation? *ducks*
Uh, the Intel 386 didn't offer anything that somehow made preemptive multitasking possible.
Huh? What more do you need for preemptive multitasking than a timer interrupt ?
I prefer fossil http://www.fossil-scm.org/index.html/doc/tip/www/index.wiki