The idea is that they will go live there to make their fortunes or own their own land.
The first people to go will make a fortune on the minerals before inflation kills the export value.
Re:Logical extension of libel
on
Data Quality Act
·
· Score: 3, Insightful
Libel requires you to direct specific false and damaging statements against a particular person. Public figures usually cannot sue for libel, and corporate suits are rarely accepted by the courts.
This law is different, because you do not have to direct a damaging statement at anyone.
If a government report says "Sulfur Dioxide emmissions were up 20% this year" or something similar, claim that the data is false and sue to keep the information away from the public. And you do not need to prove anything, just tie matters up in court.
This law is the logical extension of an Internet Denial of Service attack.
You will pay alot of money for excellent support. If the system breaks and you leave, the tech support people will walk whatever trained monkey replaces you through the problem.
If you have a job where you tend to move from project to project, the hotelling arrangement is easier, because you get to work with the people on your project.
In our company, we tend to stake out a corner and sit near each other. I've sat at the same desk for a month or two.
It's better than before, when one co-worker was on the other side of the floor and another was three floors up.
"You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee."
The loophole which makes "UnitedLinux" viable legally is the option of offering a warranty.
warranty does not necessarily mean "if it breaks, we fix it". In fact, no software that I have ever seen is warranted against defects.
One of the definitions of warranty is: "Official authorization, sanction, or warrant"
So purchasing a per-seat licence for UnitedLinux is akin to getting a certificate of authenticity on a US State Quarter or some coin or stamp. It is perfectly legal to do as long as you distribute the source for free or for a nominal fee.
If they are violating the license, the owners of said license can sue them for damages.
And that won't happen, but Linus Tordvalds doesn't seem to care about anything and the Linux user community is too fragmented to get money together for a lawsuit.
At the time of the promotion 18 months ago, a Clear Channel affiliate was the exclusive registrar of.cc domains. They exerted defacto exclusive control over the domain until their marketing campaign failed. The 600 residents of the Cocos Islands have zero control (or interest) in the.cc namespace.
So if you control a massive Fortune 500 company called "Silly Rabbit", and make a deal with Suriname or some other obscure coutry in partnership with VeriSign to exclusively market the.sr domain, you essentially have all the rights of "ownership".
Re:Clear Channel == Devil
on
Homogenized Music
·
· Score: 4, Informative
Clear channel was pushing that top-level domain, and originally had changed all their radio and television stations and even provided sponsors websites.cc domains. (as in clear channel)
It does stand for Cocos Islands, but was being sold as meaning "Clear Channel"
Now Linux will finally be able to defeat Microsoft, Intel and Sun, especially on the desktop. The only way to stop competitors is to present a United front. United Linux will allow that.
ROTC doesn't require you to commit to a low paying job.
Total compensation for a green 2nd Lieutenant is $35k. Not a princely sum, but not terrible either. Pay rates do increase over time and there is a differential for hazardous duty.
Then again, military life is probaly not well-suited to a non-traditional student with a family.
At my job we use AIX boxes as file and application servers at remote sites.
There are two reasons for this, sysback and the lvm.
Sysback makes it braindead-simple for a technician in a remote site to restore a server. Pop a tape into the drive, turn the machine on and walk away.
Combined with the great logical volume manager and smit, AIX is probaly the easiest os to deploy.
Are there any plans to deploy these tools to the linux platform. This would make it alot easier to move large customers, particularly government to IBM/Linux solutions.
Upscale clothing stores coordinate shipments of clothing with when celebrities wear them.
Tiger Woods has a staff the schedules when and where he will wear a particular shirt, pants or shoes. These items arrive in stores a day or two before he appears on TV wearing them. A few weeks after that they are shipped off to bargain basement stores like Marsalls or TJ Max.
Why go to Eastern Europe? Go to a fucking civilized country, not some third world shithole. You'll have an easier time finding maps and they even have running water.
The problem users are bonehead sysadmins who use their authority to bypass the password policy or just don't set secure passwords.
I'd be eating dinner and drinking expensive wine at a nice restaurant if I had a dollar for every time I've found an Oracle SYS password set to "change_on_install" or "oracle".
The only solution to the password problem is to eliminate passwords. At my organization, we are moving to a smartcard-based system that removes the password problem completely.
Yahoo! Uses *BSD, and as we all know...
on
Hacking Web Services
·
· Score: -1, Offtopic
FACT: Yahoo! is dying!
Netcraft confirms: *BSD is dying
Yet another
crippling bombshell hit the beleaguered *BSD community when recently
IDC confirmed that *BSD accounts for less than a fraction of 1
percent of all servers. Coming on the heels of the latest Netcraft
survey which plainly states that *BSD has lost more market share,
this news serves to reinforce what we've known all along. *BSD
is collapsing in complete disarray, as further exemplified by
failing dead last in the recent Sys Admin
comprehensive networking test.
You don't need to be a Kreskin
to predict *BSD's future. The hand writing is on the wall: *BSD
faces a bleak future. In fact there won't be any future at all for
*BSD because *BSD is dying. Things are looking very bad for
*BSD. As many of us are already aware, *BSD continues to lose market
share. Red ink flows like a river of blood. FreeBSD is the most
endangered of them all, having lost 93% of its core developers. The sudden and unpleasant demise of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any question doubt: FreeBSD is continuing its slow downward spiral into darkness.
Let's keep to the facts and look at the numbers.
OpenBSD leader
Theo states that there are 7000 users of OpenBSD. How many users
of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD
posts on Usenet is roughly in ratio of 5 to 1. Therefore there are
about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about
half of the volume of NetBSD posts. Therefore there are about 700
users of BSD/OS. A recent article put FreeBSD at about 80 percent
of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400
FreeBSD users. This is consistent with the number of FreeBSD Usenet
posts.
Due to the troubles of Walnut Creek, abysmal sales and
so on, FreeBSD went out of business and was taken over by
BSDI who sell another troubled OS. Now BSDI is also dead,
its corpse turned over to yet another charnel house.
All major
surveys show that *BSD has steadily declined in market share. *BSD is
very sick and its long term survival prospects are very dim. If *BSD
is to survive at all it will be among OS hobbyist dabblers. *BSD
continues to decay. Nothing short of a miracle could save it at
this point in time. For all practical purposes, *BSD is dead.
Some educational expenses, like college credits, are an employee benefit that does not come out of my budget. Those are the classes I refer to.
Generally we start sysadmin trainees as a combination operator/clerk. They do shift work and function as the first line of support between the user community and the systems group. The more they know and understand, the less often the admins get paged. So the admins have an incentive to teach them new skills.
We hire experienced people from the outside too. But the preferred method of hiring sysadmins is from within. This works in a large IT department. In a smaller department it would probaly be unwieldy.
I am not a hypocrite at all. You have just come out and said that you are unable to communicate with people that you percieve as authority figures. It sounds like you have some issues that you should discuss with a therapist. ( I do not mean that in a demeaning or condescending way. If you spoke with someone, you would find that there are specific reasons why you are 'hardwired' that way and ways to fix that. )
Here is why I say that you have a bad attitude:
"What would I say, if you discussed hiring procedures with me, conversationally? I'd try to say very little. I'm not capable of convincingly lying that I believe you are right, I know better than to explain why I think you are wrong, and I couldn't even manage the "I don't really care, but since you're the boss I need to kiss up to, I'll agree" lie."
If I asked you that question, I'd want you to do a mini-analysis of the process in your head and tell me what you thought. If something seemed like BS, tell me its BS. As long as you are able to back yourself up with some sort of reasoning, your answer is fine! We've actually changed the interview process based on questions like that.
You work at a surviving startup who is trying to save money by hiring people with a less credentials than many people in the market posess. If you continue to survive you will spend alot of money maintaining your codebase, if you have large programming projects.
We are a relatively high-budget organization with some critically important and complex projects which cannot fail. Our priority is sound engineering.
"Code" is not a artform. Code is an engineering process, just like the trusses of a bridge or the skin of a high-performance aircraft. Our programmers are engineers, not coders.
An engineer uses mathematics and specific knowledge of the routine that he is designing. Decisions are made on the basis of performance, maintainability and reliability. He is familiar with the the languages that he programs and understands how the features of the language work.
A coder uses older code and guesswork to design and implement whatever he is doing. Decisions are based on speed of implementation and ease of implementation,often at the cost of low maintainability. He is familiar with the syntax of the language that is in use and hopefully knows where the documentation for the apis are.
My duffbeer pseudonym is a play on my real name and one of my favorite TV shows.
Slashdot Mirror
The idea is that they will go live there to make their fortunes or own their own land.
The first people to go will make a fortune on the minerals before inflation kills the export value.
Libel requires you to direct specific false and damaging statements against a particular person. Public figures usually cannot sue for libel, and corporate suits are rarely accepted by the courts.
This law is different, because you do not have to direct a damaging statement at anyone.
If a government report says "Sulfur Dioxide emmissions were up 20% this year" or something similar, claim that the data is false and sue to keep the information away from the public. And you do not need to prove anything, just tie matters up in court.
This law is the logical extension of an Internet Denial of Service attack.
Many banking and other websites do not render properly with Mozilla, and I'm never going to pay for a browser like Opera.
So unfortunately, sometimes you must choose IE.
And buy a Gold support contract.
You will pay alot of money for excellent support. If the system breaks and you leave, the tech support people will walk whatever trained monkey replaces you through the problem.
If you have a job where you tend to move from project to project, the hotelling arrangement is easier, because you get to work with the people on your project.
In our company, we tend to stake out a corner and sit near each other. I've sat at the same desk for a month or two.
It's better than before, when one co-worker was on the other side of the floor and another was three floors up.
The GPL states:
"You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee."
The loophole which makes "UnitedLinux" viable legally is the option of offering a warranty.
warranty does not necessarily mean "if it breaks, we fix it". In fact, no software that I have ever seen is warranted against defects.
One of the definitions of warranty is:
"Official authorization, sanction, or warrant"
So purchasing a per-seat licence for UnitedLinux is akin to getting a certificate of authenticity on a US State Quarter or some coin or stamp. It is perfectly legal to do as long as you distribute the source for free or for a nominal fee.
If they are violating the license, the owners of said license can sue them for damages.
And that won't happen, but Linus Tordvalds doesn't seem to care about anything and the Linux user community is too fragmented to get money together for a lawsuit.
Get a clue.
.cc domains. They exerted defacto exclusive control over the domain until their marketing campaign failed. The 600 residents of the Cocos Islands have zero control (or interest) in the .cc namespace.
.sr domain, you essentially have all the rights of "ownership".
At the time of the promotion 18 months ago, a Clear Channel affiliate was the exclusive registrar of
So if you control a massive Fortune 500 company called "Silly Rabbit", and make a deal with Suriname or some other obscure coutry in partnership with VeriSign to exclusively market the
Clear channel was pushing that top-level domain, and originally had changed all their radio and television stations and even provided sponsors websites .cc domains. (as in clear channel)
It does stand for Cocos Islands, but was being sold as meaning "Clear Channel"
Now Linux will finally be able to defeat Microsoft, Intel and Sun, especially on the desktop. The only way to stop competitors is to present a United front. United Linux will allow that.
ROTC doesn't require you to commit to a low paying job.
Total compensation for a green 2nd Lieutenant is $35k. Not a princely sum, but not terrible either. Pay rates do increase over time and there is a differential for hazardous duty.
Then again, military life is probaly not well-suited to a non-traditional student with a family.
I don't know about Linus, but the RMS fellow would probaly insist on calling them GNU/Ink
You are doing something really stupid, or people who dislike you are putting you on spam lists.
I regularly post to usenet groups and mailing lists with my real address and conduct business online with it as well.
At most, I've received 20 spams in one day. The average is 3-6. 90% of these are caught by filters.
Dispite all of the blathering about how BSD is a dying breed of OS, the developers who have dedicated their time to BSD continue to make strides.
Hats off to the NetBSD team!
At my job we use AIX boxes as file and application servers at remote sites.
There are two reasons for this, sysback and the lvm.
Sysback makes it braindead-simple for a technician in a remote site to restore a server. Pop a tape into the drive, turn the machine on and walk away.
Combined with the great logical volume manager and smit, AIX is probaly the easiest os to deploy.
Are there any plans to deploy these tools to the linux platform. This would make it alot easier to move large customers, particularly government to IBM/Linux solutions.
For Linux to ship some decent fonts so we can actually read the webpages rendered by Mozilla.
Upscale clothing stores coordinate shipments of clothing with when celebrities wear them.
Tiger Woods has a staff the schedules when and where he will wear a particular shirt, pants or shoes. These items arrive in stores a day or two before he appears on TV wearing them. A few weeks after that they are shipped off to bargain basement stores like Marsalls or TJ Max.
TV ads are effective.
Why go to Eastern Europe? Go to a fucking civilized country, not some third world shithole. You'll have an easier time finding maps and they even have running water.
The problem users are bonehead sysadmins who use their authority to bypass the password policy or just don't set secure passwords.
I'd be eating dinner and drinking expensive wine at a nice restaurant if I had a dollar for every time I've found an Oracle SYS password set to "change_on_install" or "oracle".
The only solution to the password problem is to eliminate passwords. At my organization, we are moving to a smartcard-based system that removes the password problem completely.
Netcraft confirms: *BSD is dying
Yet another crippling bombshell hit the beleaguered *BSD community when recently IDC confirmed that *BSD accounts for less than a fraction of 1 percent of all servers. Coming on the heels of the latest Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as further exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood. FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant demise of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any question doubt: FreeBSD is continuing its slow downward spiral into darkness.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS hobbyist dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dead FACT: Yahoo! is dying!
That's the brilliance of it!
Good conservatism is completely absurd, no matter how the article was meant to be interpeted.
This is a satirical piece that is meant to bring attention to current affairs.
There are plenty of people who are willing to trade freedom for order and security today, right in the United States and other western nations.
Some educational expenses, like college credits, are an employee benefit that does not come out of my budget. Those are the classes I refer to.
Generally we start sysadmin trainees as a combination operator/clerk. They do shift work and function as the first line of support between the user community and the systems group. The more they know and understand, the less often the admins get paged. So the admins have an incentive to teach them new skills.
We hire experienced people from the outside too. But the preferred method of hiring sysadmins is from within. This works in a large IT department. In a smaller department it would probaly be unwieldy.
I am not a hypocrite at all. You have just come out and said that you are unable to communicate with people that you percieve as authority figures. It sounds like you have some issues that you should discuss with a therapist. ( I do not mean that in a demeaning or condescending way. If you spoke with someone, you would find that there are specific reasons why you are 'hardwired' that way and ways to fix that. )
Here is why I say that you have a bad attitude:
"What would I say, if you discussed hiring procedures with me, conversationally? I'd try to say very little. I'm not capable of convincingly lying that I believe you are right, I know better than to explain why I think you are wrong, and I couldn't even manage the "I don't really care, but since you're the boss I need to kiss up to, I'll agree" lie."
If I asked you that question, I'd want you to do a mini-analysis of the process in your head and tell me what you thought. If something seemed like BS, tell me its BS. As long as you are able to back yourself up with some sort of reasoning, your answer is fine! We've actually changed the interview process based on questions like that.
You work at a surviving startup who is trying to save money by hiring people with a less credentials than many people in the market posess. If you continue to survive you will spend alot of money maintaining your codebase, if you have large programming projects.
We are a relatively high-budget organization with some critically important and complex projects which cannot fail. Our priority is sound engineering.
"Code" is not a artform. Code is an engineering process, just like the trusses of a bridge or the skin of a high-performance aircraft. Our programmers are engineers, not coders.
An engineer uses mathematics and specific knowledge of the routine that he is designing. Decisions are made on the basis of performance, maintainability and reliability. He is familiar with the the languages that he programs and understands how the features of the language work.
A coder uses older code and guesswork to design and implement whatever he is doing. Decisions are based on speed of implementation and ease of implementation,often at the cost of low maintainability. He is familiar with the syntax of the language that is in use and hopefully knows where the documentation for the apis are.
My duffbeer pseudonym is a play on my real name and one of my favorite TV shows.