In between boss monster fights, he hangs out at the local graveyard where various undead creatures appear at random for him to slay.
Kind of like "Buffy" crossed with "Dog the Bounty Hunter" and "The Dog Whisperer". For the average skeleton, their appearance is usually preceded by a bone rattling sound. Which gives me enough time to switch weapons to my mace of undead slaying which gives me a +25 against skeletons. Ghosts are preceded by a howling wind type sound so I switch weapons to my silver scimitar of holiness.
The problem is that the most likely players will NOT be interested in furthering the plot in any reasonable fashion. They'll be out to be griefers. There's only so many times that the main objective can be lost because some group of players start attacking the other players.
Lose the main battle because of mind-controlled "slaves" who turn on the rest...
Retreat to the mountains...
Where more mind-controlled slaves lead group after group of aliens to the camp...
Forcing the main party to retreat further into the mountains...
Until the producers rule out wandering aliens...
Whereupon more mind-controlled slaves gank one of the stronger members of the group...
As can be seen from this charade, the votes do not matter.
It is who counts the votes that matters.
Microsoft could not buy off all the geeks. So Microsoft bought off the administration staff. Which then allowed a single secretary to get their "standard" on the fast track when it failed every one of their rules for that.
Until ISO PUBLICLY admits the SPECIFIC mistakes made AND takes action against the people who committed those mistakes, there is no reason to believe that ISO will do anything differently in the future.
The indemnification is basically MS' promise to not go after Novell's customers.
So Novell DID agree that there was SOMETHING Microsoft could sue over.
I agree they sold them "magic beans" but I have to assume A customer or customers wanted this.
Explain that one again. It makes no sense to me.
This was done under the umbrella of SCO's lawsuits, etc. Some customers probably did not want the hassle and wanted to have somebody shield them.
Red Hat didn't seem to have a problem with that.
So Novell Pays MS and Novell gets paid MORE than that BY MS.
That's what is known as "selling out".
It doesn't matter how much you get paid, you've still entered into an agreement stating that you are paying Microsoft for the property that know is included in the product that you are selling.
The other way of looking at it are that the ISO is naturally really, really slow and these appeals are the appropriate first step in showing that there was a problem.
No. The reason ISO is slow SHOULD be to avoid errors in the process.
Fixing the errors slowly means that ISO is worthless.
And WAITING for someone to APPEAL the process means that ISO is worse than worthless. They cannot even manage their own internal systems. For a "standards" organization, that is beyond unacceptable. That means they produce corrupted standards.
The problem was NOT that they didn't have the rules in place.
The problem was that the rules were NOT followed. And ISO was unable (unwilling) to rectify the "errors" once they had been committed. And ISO is still unwilling to identify the individuals within its organization who committed the "errors" and take any action.
Some people will always blame others for their failures. It's just that right now it is fashionable to bash Free Software.
I believe that this is because more people are trying to make $$MILLIONS$$ personally (remember the old Microsoft millionaires) on software that other people have written.
Essentially, they're trying to put an artificial bottleneck between the consumers and the product so they can extract money from the bottleneck. Lots of money. When they don't get lots of money, they whine. When someone else renders the bottleneck ineffective, they whine.
That way they can keep selling you "updated" "signature files" every hour / day / week / month / year.
The correct way to handle this is to set up your system so that the user cannot ACCIDENTALLY execute any external code.
There's no way to solve the issue of some idiot clicking on everything and putting in the root password whenever asked. So don't bother bringing that case up.
For everyone else, lock the OS files so that it cannot be infected and set the user writable portion to not execute any code. There, the majority of that problem is solved.
Then, ship the default installation without any open ports and you've pretty much solved the worm issue.
But that approach means that the anti-virus companies cannot keep selling you new signature files. So don't expect any of them to support it.
"Based on the amount of grumbling it's actually working pretty well," Lutzen said.
Are they referring to an increase in complaints or a reduction?
I have taken many tests and I have found that getting a perfect score is not so much about knowing the material as about knowing the expectations of the person who wrote the test.
True or false: Copyright infringement is stealing?
The answer would vary depending upon how well the person "grading" the test understood "stealing" and "copyright infringement" and your local, state and national laws.
"An adversary needs to know that the U.S. possesses powerful hard and soft-kill (cyberwarfare) means for attacking adversary information and command and support systems at all levels," a recent Defense Department report notes.
They're going to "soft-kill" my "information"?
Well, I guess that's better than them performing a "hard-kill" on it.
What the fuck... ?
It's just zeros and ones. You can TALK tough, but when a 5 cent CD foils your "hard-kill" on my "information" you're really just wasting time and effort.
I see the attraction of having the latest releases of KDE and GNOME and so forth.
But I'm not seeing why the other distributions matter that much to Ubuntu's release schedule.
The more items you have to sync, the more difficult it gets to be. Is Ubuntu really going to wait for KDE to wait for SuSE to get GNOME compiled with the latest GCC?
Every time this subject comes up, I say the same thing.
The problem with finding and removing rootkits (and other forms of malware) is that the vendor of the OS does not provide any means of identifying what the LEGITIMATE files are.
With Ubuntu, I can boot from a LiveCD and check any file on my hard drive. What package does it belong to? Does it have the correct checksums?
Anything that cannot be identified can be moved to a different drive. A drive without run permissions.
Exactly. Who says that an "insider" cannot have an agenda that is contrary to providing the best tools for the children to learn with?
From TFA:
If proprietary software is half as good as free software at aiding children's learning, you're damn right it makes the world a better place to get the software out to children. Hell, if it doesn't actively inhibit learning, it makes the world a better place.
No.
No.
And, no.
It has to be BETTER than the ALTERNATIVES at the same price. And Linux is free.
Wait, it gets better.
I started using Linux in '95, before most of today's Internet-using general public knew there existed an OS outside of Windows. It took a week to configure X to work with my graphics card, and I learned serious programming because I later needed to add support for a SCSI hard drive that wasn't recognized properly.
Yeah, he's bringing up the state of Linux in 1995... when the discussion is about Linux in 2008.
He has an agenda. And it isn't about getting the best tools available (for the price) to the kids of the world.
Preparing to replace openssh-server 1:4.6p1-5ubuntu0.2 (using.../openssh-server_1%3a4.6p1-5ubuntu0.3_i386.deb)... Template #4 in/var/lib/dpkg/tmp.ci/templates has a duplicate field "template" with new value "ssh/vulnerable_host_keys". Probably two templates are not properly separated by a lone newline. dpkg: error processing/var/cache/apt/archives/openssh-server_1%3a4.6p1-5ubuntu0.3_i386.deb (--unpack):
subprocess pre-installation script returned error exit status 255
And then: openssh-server: Depends: openssh-client (= 1:4.6p1-5ubuntu0.2) but 1:4.6p1-5ubuntu0.3 is installed
A chip and pin terminal is more like the regular debit card consoles we already have. Swipe the card (failure point), punch in 4 digits (4 failure points) and it contacts the bank (one failure point).
In theory, RFID payment cards mean fewer repairs on all the machines out there.
Slashdot Mirror
In between boss monster fights, he hangs out at the local graveyard where various undead creatures appear at random for him to slay.
Kind of like "Buffy" crossed with "Dog the Bounty Hunter" and "The Dog Whisperer". For the average skeleton, their appearance is usually preceded by a bone rattling sound. Which gives me enough time to switch weapons to my mace of undead slaying which gives me a +25 against skeletons. Ghosts are preceded by a howling wind type sound so I switch weapons to my silver scimitar of holiness.
Yep, that would be a great way to do it.
...
...
...
...
...
...
The problem is that the most likely players will NOT be interested in furthering the plot in any reasonable fashion. They'll be out to be griefers. There's only so many times that the main objective can be lost because some group of players start attacking the other players.
Lose the main battle because of mind-controlled "slaves" who turn on the rest
Retreat to the mountains
Where more mind-controlled slaves lead group after group of aliens to the camp
Forcing the main party to retreat further into the mountains
Until the producers rule out wandering aliens
Whereupon more mind-controlled slaves gank one of the stronger members of the group
lather, rinse, repeat
With this model, you NEVER know if the hero is going to be killed or not. Will the boss monster win?
On the other hand, who cares? The hero will get a rez and be back to fight the boss monster next week.
During the alien invasion, half of the "defenders" turn and attack the other defenders. Maybe the aliens have mind-control powers?
Meanwhile, other defenders are busy looting their fallen comrades.
Still another group of defenders is busily arranging items to spell out the word "FUCK" on the battlefield.
As can be seen from this charade, the votes do not matter.
It is who counts the votes that matters.
Microsoft could not buy off all the geeks. So Microsoft bought off the administration staff. Which then allowed a single secretary to get their "standard" on the fast track when it failed every one of their rules for that.
Until ISO PUBLICLY admits the SPECIFIC mistakes made AND takes action against the people who committed those mistakes, there is no reason to believe that ISO will do anything differently in the future.
ISO sold out. That's all there is to it.
Yeah, the name sucks.
But I like the idea. You can gauge your hardware against a 100% Free (as in Freedom) system.
It doesn't matter how much you get paid, you've still entered into an agreement stating that you are paying Microsoft for the property that know is included in the product that you are selling.
#2. What "indemnification" is Novell paying for, specifically?
Companies usually do NOT pay for things that they do not receive.
Fixing the errors slowly means that ISO is worthless.
And WAITING for someone to APPEAL the process means that ISO is worse than worthless. They cannot even manage their own internal systems. For a "standards" organization, that is beyond unacceptable. That means they produce corrupted standards.
As evidence, I give you OOXML.
I don't care how ISO re-writes whatever.
The problem was NOT that they didn't have the rules in place.
The problem was that the rules were NOT followed. And ISO was unable (unwilling) to rectify the "errors" once they had been committed. And ISO is still unwilling to identify the individuals within its organization who committed the "errors" and take any action.
Some people will always blame others for their failures. It's just that right now it is fashionable to bash Free Software.
I believe that this is because more people are trying to make $$MILLIONS$$ personally (remember the old Microsoft millionaires) on software that other people have written.
Essentially, they're trying to put an artificial bottleneck between the consumers and the product so they can extract money from the bottleneck. Lots of money. When they don't get lots of money, they whine. When someone else renders the bottleneck ineffective, they whine.
I'm wondering if they'd be working in Seattle.
Since when is $80K an "entry level job" in this industry?
And when is being a SysAdmin an "entry level job"?
Who writes that crap?
It would be easy to circumvent by breaking the malware into multiple pieces and having one app load it piece by piece.
If that is done right, then none of the pieces will be sufficiently like the known patterns to set off the alert.
This is still all about matching against known patterns. That is NOT sufficient.
That way they can keep selling you "updated" "signature files" every hour / day / week / month / year.
The correct way to handle this is to set up your system so that the user cannot ACCIDENTALLY execute any external code.
There's no way to solve the issue of some idiot clicking on everything and putting in the root password whenever asked. So don't bother bringing that case up.
For everyone else, lock the OS files so that it cannot be infected and set the user writable portion to not execute any code. There, the majority of that problem is solved.
Then, ship the default installation without any open ports and you've pretty much solved the worm issue.
But that approach means that the anti-virus companies cannot keep selling you new signature files. So don't expect any of them to support it.
But that does not address you blocking any of the traffic.
I have taken many tests and I have found that getting a perfect score is not so much about knowing the material as about knowing the expectations of the person who wrote the test.The answer would vary depending upon how well the person "grading" the test understood "stealing" and "copyright infringement" and your local, state and national laws.
Well, I guess that's better than them performing a "hard-kill" on it.
What the fuck
It's just zeros and ones. You can TALK tough, but when a 5 cent CD foils your "hard-kill" on my "information" you're really just wasting time and effort.
They can also image your drive. As Bruce says, the easiest way to avoid this is to not have your data on your laptop. Put it on something else.
I see the attraction of having the latest releases of KDE and GNOME and so forth.
But I'm not seeing why the other distributions matter that much to Ubuntu's release schedule.
The more items you have to sync, the more difficult it gets to be. Is Ubuntu really going to wait for KDE to wait for SuSE to get GNOME compiled with the latest GCC?
Every time this subject comes up, I say the same thing.
The problem with finding and removing rootkits (and other forms of malware) is that the vendor of the OS does not provide any means of identifying what the LEGITIMATE files are.
With Ubuntu, I can boot from a LiveCD and check any file on my hard drive. What package does it belong to? Does it have the correct checksums?
Anything that cannot be identified can be moved to a different drive. A drive without run permissions.
Problem solved.
From TFA:No.
No.
And, no.
It has to be BETTER than the ALTERNATIVES at the same price. And Linux is free.
Wait, it gets better.Yeah, he's bringing up the state of Linux in 1995
He has an agenda. And it isn't about getting the best tools available (for the price) to the kids of the world.
I just updated again and they fixed the package.
Preparing to replace openssh-server 1:4.6p1-5ubuntu0.2 (using .../openssh-server_1%3a4.6p1-5ubuntu0.3_i386.deb) ... /var/lib/dpkg/tmp.ci/templates has a duplicate field "template" with new value "ssh/vulnerable_host_keys". Probably two templates are not properly separated by a lone newline. /var/cache/apt/archives/openssh-server_1%3a4.6p1-5ubuntu0.3_i386.deb (--unpack):
Template #4 in
dpkg: error processing
subprocess pre-installation script returned error exit status 255
And then:
openssh-server: Depends: openssh-client (= 1:4.6p1-5ubuntu0.2) but 1:4.6p1-5ubuntu0.3 is installed
Anyone else seeing this?
A RFID tag can be read without moving parts.
A chip and pin terminal is more like the regular debit card consoles we already have. Swipe the card (failure point), punch in 4 digits (4 failure points) and it contacts the bank (one failure point).
In theory, RFID payment cards mean fewer repairs on all the machines out there.