Hmm. That's more detail then I was able to find when I first heard about this many years ago. The Intel fiasco is outright stealing, but I'm not so sure about the Microsoft-DEC fiasco. Were there design choices that DEC was dragging their feet to implement? In this case, I think DEC may have got what they deserved. Thank goodness this can't happen with open source software, where poorly maintained or stagnant projects are simply forked or moved into something better.
So I suppose that you have one of these PCs for a system backup, another 7 for data backup every day of the week, 12 for monthly data backups, and one for a year-end backup. I'm guessing you have a strong back, so you can haul those PC backup machines off-site, or a least a screwdriver, so you can remove the disk drive to take it off-site. You'll also want to set more money aside, since bargain IDE drives have a typical lifetime of about 3 years.
Why is this cheap? I'd rather pay for my own service, that way I can elect to spend the appropriate amount based on the coverage and usage I want. If anything, I'd expect my employer to provide very basic pager service (and nothing more) for after-hours contact. If I was making a good salary, I'd pay for the pager without thinking twice.
I'd rather not have my employer give out entitlements like this which eat into their budget both in cost of services, and in the labor to keep track of those services.
See, there's the small matter of IBM's patent, granted on the same algorithm, which is valid for another two years
So is the author saying that the USPTO allowed two companies to patent the same thing? Aren't clear rights to property one of the fundamental pieces for a healthy economy? The big story here isn't Unisys' patent expired.
Okay, for the benefit of both of you, here's my logic:
The military is the licensee of the frequency, therefore they may do what they wish with it (within the FCC's guidelines for that band). If they've licensed the frequency, they must be doing something with, right? Otherwise, why bother paying the fees.
Now look at a quote from the parent:
...keyless entry remotes are not licensed by the Federal Communications Commission. They are allowed to operate on frequencies used by licensed customers as long as their signals are sufficiently weak and don't interfere with others
So if the unlicensed, low-power transmitters are causing harmful interference, a high-power jamming signal would be even more harmful to the militaries receiving equipment. Whether they were using the frequency for two-way communication, or just to listen in, jamming it on purpose doesn't make sense. In a nutshell, my original post was asking the question: "What purpose would there be for jamming the frequency all the time?"
That still doesn't make sense. If a keyless entry signal was harmful, then I imagine a signal strong enough to jam that would be even more harmful to the licensed users of the frequency.
Think again. One of the United State's largest manfacturers of aluminum products is Alcoa. They are [and their subsidiaries] also a military subcontractor. Your purchase would probably invite investigation. Now see, if you'd just been buying a little extra every week since before Y2K, you'd have enough to make an aluminum suit for you and your car for every day of the week.
Well, at least he had to run an interactive program to do it. Windows 95 would just alter the partition table without so much as a peep, as most of us former multi-booters are aware.
Michael Moore should make a rip of the upcoming DVD, and seed a torrent of it. The day the movie hit the theaters, there were cam copies all over the bit torrent sites.
What is the likelihood that an inventor of the early 20th century would be able to detect an HDTV broadcast stream?
Very likely, if this inventor was in the right portion of the spectrum. The HDTV signal definitely isn't "random". It's modulated on carriers and sub-carriers, which would stand out from background noise. Decoding it would be another story.
Silly, but your prophecy about the kernel may turn out to be true. At some point operating systems will have to support it, or foreigners may risk missing out on business with China.
...all the pain and suffering getting 3D working on Linux when most hardware is a breeze is proof of that.
What pain and suffering? Nvidia's drivers are the most pain-free to install of any third-party driver. The useful module options are
well documented, and there is a support community. Hell, Nvidia just added a new configuration utility. Unlike other drivers that are included with the kernel, Nvidia's modules are consistently functional, and aren't mystified by outdated HOW-TOs or the requirement to poke around inside the kernel source tree for a text file with module options; A file that may or may not exist.
On the contrary, my issue with hardware installation and Nvidia had to do with the open source components not produced by Nvidia. The Mesa OGL library changed their build scripts (which was the source of much confusion) because of issues with automake. Installing Mesa at the wrong time breaks Nvidia's OGL interface. The agpgart module was also the source of much frustration because it wouldn't support faster transfer modes on certain chipsets. So, when I couldn't get my GF3 Ti to run at 4x, I discovered that - in true OSS developer fashion - the option appears only inside a source code file, with no explanation. Thank heavens for the 'modinfo' utility and experience, whereas a less technically-inclined user wouldn't have a clue what an "int" is.
Nvidia shows a lot enthusiasm for GNU/Linux that other vendors do not. Their Linux drivers are always current, and well documented. They host a lot of complete or demo games for free and without registration hassles. Nvidia is fighting tooth-and-nail with ATI in a technology war that has resulted in ultra-high performance at affordable prices, yet even with ATI nipping at their heels, they've still managed to find the time to cater to the OSS community. Since there is a wide range of acceleration features that modern applications may or may not support, Nvidia's peformance secrets still remain inside their drivers. Putting these trade secrets out in the open would guarantee Nvidia's end. As much as I'd like to see the drivers become part of the kernel's source tree, I wouldn't want to see a friend of open source operating systems put out of business. Continued criticism of Nvidia only reinforces the Linux community's reputation as the enfant terrible of the computing world.
Thank you, I stand corrected. And since you gave me that link, I decided to do a little searching. The earliest reference is a comment about it in a development version of KDE from May 14th, 2001. It was a working feature that someone spotted in CVS at that point. Read this, and take particular note of the following:
... it's based on classname which is a feature of X. So I presume any application could actually choose seperate (or the same) classes for its various windows itself.
Here's a webpage describing that feature (see point #18) dating 1998. I guess this means that it was in fact an underlying design decision for all implementations of X prior to Microsoft's filing for a patent. KDE's 'Kicker' application was taking advantage of this feature, because it was an obvious use of it. I believe that's prior art.
Gotta love those NATO designations. Imagine what would happen if a bunch of Fundies found out their latest religious program was made possible via a satellite that was launched by Satan. And from the heart of the former [atheist] "Evil Empire" no less.
Slashdot Mirror
Those aren't my type of nature specials. I'd rather see a spam run down by a cheetah as it tries to escape through my router.
Yes, and more than once I've seen Slashdot "researchers" suggest more than one way to kill the organism that creates it.
It's that minor, narrow-band analog signal that shares the wire with my DSL.
...Win9x and WinME, which are a graphical interface living on top of DOS.
Which version of MS-DOS is this that runs in protected mode? Don't recall running across that particular version.
Hmm. That's more detail then I was able to find when I first heard about this many years ago. The Intel fiasco is outright stealing, but I'm not so sure about the Microsoft-DEC fiasco. Were there design choices that DEC was dragging their feet to implement? In this case, I think DEC may have got what they deserved. Thank goodness this can't happen with open source software, where poorly maintained or stagnant projects are simply forked or moved into something better.
Yes, because we all know that the more developers we throw at a project, faster it gets done.
Did you just imply that IBM doesn't innovate?
So I suppose that you have one of these PCs for a system backup, another 7 for data backup every day of the week, 12 for monthly data backups, and one for a year-end backup. I'm guessing you have a strong back, so you can haul those PC backup machines off-site, or a least a screwdriver, so you can remove the disk drive to take it off-site. You'll also want to set more money aside, since bargain IDE drives have a typical lifetime of about 3 years.
Hope those aren't IDE drives. Check out the MTBF on those sometime.
Why is this cheap? I'd rather pay for my own service, that way I can elect to spend the appropriate amount based on the coverage and usage I want. If anything, I'd expect my employer to provide very basic pager service (and nothing more) for after-hours contact. If I was making a good salary, I'd pay for the pager without thinking twice.
I'd rather not have my employer give out entitlements like this which eat into their budget both in cost of services, and in the labor to keep track of those services.
The military is the licensee of the frequency, therefore they may do what they wish with it (within the FCC's guidelines for that band). If they've licensed the frequency, they must be doing something with, right? Otherwise, why bother paying the fees.
Now look at a quote from the parent:
So if the unlicensed, low-power transmitters are causing harmful interference, a high-power jamming signal would be even more harmful to the militaries receiving equipment. Whether they were using the frequency for two-way communication, or just to listen in, jamming it on purpose doesn't make sense. In a nutshell, my original post was asking the question: "What purpose would there be for jamming the frequency all the time?"
That still doesn't make sense. If a keyless entry signal was harmful, then I imagine a signal strong enough to jam that would be even more harmful to the licensed users of the frequency.
Think again. One of the United State's largest manfacturers of aluminum products is Alcoa. They are [and their subsidiaries] also a military subcontractor. Your purchase would probably invite investigation. Now see, if you'd just been buying a little extra every week since before Y2K, you'd have enough to make an aluminum suit for you and your car for every day of the week.
Yes! Why waste the time when you could boot for your Linux install disk and run 'cfdisk'. Sheesh.
Well, at least he had to run an interactive program to do it. Windows 95 would just alter the partition table without so much as a peep, as most of us former multi-booters are aware.
Anyway, CSS wasn't broken because it was weak, it was broken because a vendor of proprietary DVD player software made a mistake.
Michael Moore should make a rip of the upcoming DVD, and seed a torrent of it. The day the movie hit the theaters, there were cam copies all over the bit torrent sites.
What is the likelihood that an inventor of the early 20th century would be able to detect an HDTV broadcast stream?
Very likely, if this inventor was in the right portion of the spectrum. The HDTV signal definitely isn't "random". It's modulated on carriers and sub-carriers, which would stand out from background noise. Decoding it would be another story.
Silly, but your prophecy about the kernel may turn out to be true. At some point operating systems will have to support it, or foreigners may risk missing out on business with China.
Here's a webpage describing that feature (see point #18) dating 1998. I guess this means that it was in fact an underlying design decision for all implementations of X prior to Microsoft's filing for a patent. KDE's 'Kicker' application was taking advantage of this feature, because it was an obvious use of it. I believe that's prior art.
So Apple had their "look and feel" suit thrown out. I guess the way to patent a UI is to do it incrementally.
I believe taskbar grouping arrived in KDE as of version 3.
Gotta love those NATO designations. Imagine what would happen if a bunch of Fundies found out their latest religious program was made possible via a satellite that was launched by Satan. And from the heart of the former [atheist] "Evil Empire" no less.