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.
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.
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.
On a project I was on, I needed to parse 50+ COBOL copybooks in.NET so that we could use those data definitions to whittle down a 600MB flat file full of nightly data for a data warehouse.
I tried ANTLR, and I wound up abandoning it.
COBOL is pretty straightforward.
I did something similar with awk. One script of about 150 lines handled most of the essentials.
Output files were another awk script with field offsets and lengths for usage in the converted extract, a file with extraction commands for a mainframe utility and a bare bones SQL DEFINE TABLE script.
CO2 is about 1.5 times heavier than air, so it will stay underground.
The stuff will be pumped in under high pressure. I bet the pressure overcomes the specific mass quite easily. So, if the soil isn't sealed perfectly, it will escape and form a nice layer on the ground (heavier than air, right), exactly where most land creatures live.
Google doesn't pay the site owner for "displaying" ads, it pays them when and only when someone actually clicks on those ads.
The sites visitors don't necessarily have to click the ad. They only need to have an accelerator installed which preloads all hyperlinked pages regardless of whether they will click the links later or not.
Read the original design documents to get a grasp of the over all application architecture. A quarter of the code will fall into place. Concentrate on the datastructures / database schema. That's another quarter of understanding.
The last time my company had to do something like this we hired a refactoring specialist and called back a retired guy who knew the application architecture in great detail. And we formed a team of knowledgable end users to test the refactored application.
Add a good project manager and a lot of money (many millions $$ in our case) and time (two years) and it worked.
Actually, MS Access is too good for Microsoft to develop, so they bought it. I agree it's one of the best GUI / GUI builders for databases (of what I've seen).
The only real trouble is when it is abused by putting the.MDB on a network share and expect it to work fine with loads of users opening it concurrently.
But with the application on the client and some other database than the native Access database (jet) it performs quite well indeed.
[Note to self: try Access / SQLite ODBC driver / SQLite]
Slashdot Mirror
> git done right.
I agree 100%
www.fossil-scm.org
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.
It's slightly less depressing on Opensolaris:
$ man woman
No manual entry for woman.
(emphasis mine)
Comparison of Open Web Server (OWS) and Sun Java System Web Server (SJSWS): http://wikis.sun.com/display/wsFOSS/Features+Comparison
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.
Or ?
(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*
Exactly!
Huh? What more do you need for preemptive multitasking than a timer interrupt ?
Yes, msysgit is pretty fast on mswindows, but too bloated for my smallish projects.
I prefer fossil http://www.fossil-scm.org/index.html/doc/tip/www/index.wiki
Below the tags, there is a genuine, old fashioned, read link in the summary of TFA, which points to the actual article: http://www.physorg.com/news122534699.html
Interesting, thanks.
So, if the soil isn't sealed perfectly, it will escape and form a nice layer on the ground (heavier than air, right), exactly where most land creatures live.
Read the original design documents to get a grasp of the over all application architecture. A quarter of the code will fall into place. Concentrate on the datastructures / database schema. That's another quarter of understanding.
The last time my company had to do something like this we hired a refactoring specialist and called back a retired guy who knew the application architecture in great detail. And we formed a team of knowledgable end users to test the refactored application.
Add a good project manager and a lot of money (many millions $$ in our case) and time (two years) and it worked.
Allow me to add a reference to The third manifesto (Hugh Darwen and C.J. Date). Interesting stuff.
Actually, MS Access is too good for Microsoft to develop, so they bought it. I agree it's one of the best GUI / GUI builders for databases (of what I've seen). The only real trouble is when it is abused by putting the .MDB on a network share and expect it to work fine with loads of users opening it concurrently.
But with the application on the client and some other database than the native Access database (jet) it performs quite well indeed.
[Note to self: try Access / SQLite ODBC driver / SQLite]