I know you're planning to buy your primary mirror, but you might like to read Ed Grinds a Mirror from Ed Ting's excellent astronomy site. Also, if you ever need advice on production scopes and accessories (like eyepieces), Ed's site is the place to go.
Video memory in system RAM - commonly used on many lower priced motherboards these days
A better description of the PCjr would be "System RAM in video memory". Basically, video refresh affected all memory accesses, slowing down the entire system.
Here's the comment from the beginning of Linux 0.1's errno.h:
/* * ok, as I hadn't got any other source of information about * possible error numbers, I was forced to use the same numbers * as minix. * Hopefully these are posix or something. I wouldn't know (and posix * isn't telling me - they want $$$ for their f***ing standard). * * We don't use the _SIGN cludge of minix, so kernel returns must * see to the sign by themselves. * * NOTE! Remember to change strerror() if you change this file! */
BTW: I downloaded this code LONG before the SCO bullshit started to fly.
Linux has achieved dominance in the server market, is scalable from embedded systems up to giant NUMA machines, has proven itself reliable and secure for mission-critical enterprise applications, and is basically kicking SCO's butt. Linux does all this and more through the cunning use of errno.h, ioctl.h, and signal.h. Bastards!
"Execution Protection" (NX) has nothing to do with TCPA. NX means the heap and stack are not executable unless you take specific measures to make them so. NX should make it MUCH more difficult for worms and viruses to execute arbitrary code via buffer overruns. Unfortunately, NX is not possible on current 32-bit Intel processors.
Way back (before 1995) Windows NT versions 3.1 and 3.5 used a streams-based TCP stack licensed from Spyder Systems.
NT versions >= 3.51 (and Win >= 9x) use a TCP stack developed completely by Microsoft.
Early versions of NT (up to at least 4.0) and Win9X used bits and pieces of BSD code, mostly DNR resolver code and a few simple TCP-centric utilities (like the FTP client). These are properly credited in the documentation somewhere, if you know where to look.
As the years have passed and the versions have been released, more and more of the BSD code has been yanked out and rewritten. I don't know how much remains in XP.
In other words, there is probably less OSS code in the Windows codebase now than there was a few years ago.
I know how KeBugCheckEx() generates a BSOD (at least I did back in the Win2K days). I think it highly implausible that "/dev/null" would ever appear in a Microsoft-generated BSOD. This sounds suspiciously like an urban legend or spoof.
How could "...integrating OSS code into their software..." possibly help? I can just imagine some PHB at a meeting. "I know, we need some of that OSS software stuff. Let's all download some and start mergin'!" Sure, that will help.
Of course, this is just my opinion. I could be wrong.
Fire Jim Allchin. He has been a liability for years. He wants to turn every project he touches into "Cairo".
Appoint a competent replacement, preferably not Brian Valentine.
Do not allow any summer intern "wannabe engineer" code-boys anywhere near the core OS kernel source code without proper supervision.
Release the core OS kernel as open source. You don't need to release the source for the entire product, just enough to build NTOSKRNL.EXE, NTDLL.DLL, and a generic HAL.DLL. The driver writers of the world will love you for it.
But seriously, the people attacking these Linux servers have shown a great deal of talent. I suspect they've become bored hacking their way into Windows systems. What better way to "raise the bar" and really display one's abilities than to hack the (mostly) unhackable? I think this is (sadly) an inevitable fact of life.
A few years ago, while working at Microsoft, I heard one of the documentation writers complaining about terminology. She objected to the word "shutdown". I can still remember her whiny voice saying "Shutdown sounds like shotgun, and that's violent".
Kiss my ass.
There are certainly some *nix terms that LA County may find offensive. "Zombies", and "aborting processes", and of course my favorite "daemons flushing dead children down pipes".
In the current environment, is it still legal for stores like Circuit City to show movies on their demonstration TVs? I remember a story about taxi cab drivers required to *not* play the radio while carrying paying customers. I know RIAA != MPAA, but wouldn't the same "logic" (or whatever-the-hell you want to call it) apply to retail stores?
Q: What is the single most annoying thing about the Linux community?
A: Irrational trash-talking about Microsoft. There are plenty of *rational* ways to criticize them, and people should stick to those arguments rather than ranting on and on about the same old tired issues. At some point the Bill Gates and Blue Screen jokes just lose their luster.
This reminds me of an old Dennis Miller joke:
Don't hate someone because of the color of their skin. If you just take the time to get to know them, you'll find many, more valid reasons to hate them.
The original NDIS specification predates Windows NT, 95, et al. It was, in fact, targeted at DOS and OS/2. A little Googling [see this, this, and this] shows that it has a long (if not glorious) history. IIRC, NDIS binaries would load unmodified in Win NT and Win 95. This is pretty cool given these two OS's vastly different I/O models.
NDIS is a cross-platform network driver model, or at least it was when I worked with it ~10 years ago. An NDIS driver never calls the OS directly; everything goes through the NDIS wrapper, thus providing an abstraction layer over the actual OS.
Now, if someone will just write a similar layer for Linux that can load Windows NT filesystem drivers, then I can get read/write access to my NTFS partitions... Hmm...
IMHO, this is a Good Thing (tm). If security issues start affecting the MS bottom line, then they will start taking security seriously. Microsoft is not evil, they're just greedy. Hit them in the bank account, and they will notice. Losing a few $100 million in random lawsuits is not a big deal to MS. Losing desktop market share (especially in the home market) is a huge deal.
Slashdot Mirror
I know you're planning to buy your primary mirror, but you might like to read Ed Grinds a Mirror from Ed Ting's excellent astronomy site. Also, if you ever need advice on production scopes and accessories (like eyepieces), Ed's site is the place to go.
How about Tandy Corporation's THOR CD-RW-like technology developed back in the late 1980's.
What? You never heard of THOR QED.
I spent nearly ten years working for Microsoft. (It was slightly less than 10 -- I got "time off" for good behavior...)
Linux has achieved dominance in the server market, is scalable from embedded systems up to giant NUMA machines, has proven itself reliable and secure for mission-critical enterprise applications, and is basically kicking SCO's butt. Linux does all this and more through the cunning use of errno.h, ioctl.h, and signal.h. Bastards!
Just send your story, along with your bank account info & PIN to Kevin. He'll take care of the rest...
How about Kansas? It's inconvenient enough to piss off everyone, and your boss/wife/whatever will absolutely know it's not just a boondoggle...
"Execution Protection" (NX) has nothing to do with TCPA. NX means the heap and stack are not executable unless you take specific measures to make them so. NX should make it MUCH more difficult for worms and viruses to execute arbitrary code via buffer overruns. Unfortunately, NX is not possible on current 32-bit Intel processors.
- Way back (before 1995) Windows NT versions 3.1 and 3.5 used a streams-based TCP stack licensed from Spyder Systems.
- NT versions >= 3.51 (and Win >= 9x) use a TCP stack developed completely by Microsoft.
- Early versions of NT (up to at least 4.0) and Win9X used bits and pieces of BSD code, mostly DNR resolver code and a few simple TCP-centric utilities (like the FTP client). These are properly credited in the documentation somewhere, if you know where to look.
- As the years have passed and the versions have been released, more and more of the BSD code has been yanked out and rewritten. I don't know how much remains in XP.
In other words, there is probably less OSS code in the Windows codebase now than there was a few years ago.- I know how KeBugCheckEx() generates a BSOD (at least I did back in the Win2K days). I think it highly implausible that "/dev/null" would ever appear in a Microsoft-generated BSOD. This sounds suspiciously like an urban legend or spoof.
- How could "...integrating OSS code into their software..." possibly help? I can just imagine some PHB at a meeting. "I know, we need some of that OSS software stuff. Let's all download some and start mergin'!" Sure, that will help.
Of course, this is just my opinion. I could be wrong....and it is mine!
But seriously, the people attacking these Linux servers have shown a great deal of talent. I suspect they've become bored hacking their way into Windows systems. What better way to "raise the bar" and really display one's abilities than to hack the (mostly) unhackable? I think this is (sadly) an inevitable fact of life.
I always thought Clippy needed an option to eject the CDROM...
OK, I know this is getting somewhat off-topic, but if you enjoy reading about STUPID lawsuits, check out this.
A few years ago, while working at Microsoft, I heard one of the documentation writers complaining about terminology. She objected to the word "shutdown". I can still remember her whiny voice saying "Shutdown sounds like shotgun, and that's violent".
Kiss my ass.
There are certainly some *nix terms that LA County may find offensive. "Zombies", and "aborting processes", and of course my favorite "daemons flushing dead children down pipes".
In the current environment, is it still legal for stores like Circuit City to show movies on their demonstration TVs? I remember a story about taxi cab drivers required to *not* play the radio while carrying paying customers. I know RIAA != MPAA, but wouldn't the same "logic" (or whatever-the-hell you want to call it) apply to retail stores?
...nice beaver!
article.pl? Does this mean it's in Polish? Of course, the Polish language has no articles (although it does have particles like "czy")...
I keep thinking of Marty Feldman's protrayal of Igor (that's EE-Gore) from "Young Frankenstein"...
The original NDIS specification predates Windows NT, 95, et al. It was, in fact, targeted at DOS and OS/2. A little Googling [see this, this, and this] shows that it has a long (if not glorious) history. IIRC, NDIS binaries would load unmodified in Win NT and Win 95. This is pretty cool given these two OS's vastly different I/O models.
NDIS is a cross-platform network driver model, or at least it was when I worked with it ~10 years ago. An NDIS driver never calls the OS directly; everything goes through the NDIS wrapper, thus providing an abstraction layer over the actual OS.
Now, if someone will just write a similar layer for Linux that can load Windows NT filesystem drivers, then I can get read/write access to my NTFS partitions... Hmm...
IMHO, this is a Good Thing (tm). If security issues start affecting the MS bottom line, then they will start taking security seriously. Microsoft is not evil, they're just greedy. Hit them in the bank account, and they will notice. Losing a few $100 million in random lawsuits is not a big deal to MS. Losing desktop market share (especially in the home market) is a huge deal.
OK, most people call it communism, when it really wasn't. Like most people think the U.S. is a democracy, when it really isn't -- it's a republic.