Final Update: Wow. Just wow. You guys really like to ream the buggery out of a webserver when presented with an opportunity eh? It's 1am down here now, I'm off to bed. Knock yourselves out, and turn the lights out when you're finished.
Even internal projects are this way. I got one from accounting for some tracking software with requirements in December. I wrote the code and tested it and then showed it to accounting.
At the end of January, it was still not implimented. Accounting came back with a fistful of more things it "should do". I added them and by mid-Feb it was being "beta tested" by the departments.
Of course, this added another fist full of requirements, reports and other assorted stuff they wanted added.
Bottom line was that for something that was a "small two week" project in December, I'm still adding code to at the end of March.
In this case, it was a failure to plan, and a distinct failure to include all personnel who would be involved in it. I tried to coordinate this from the start, but A doesn't want to talk to B, who doesn't want to talk to C. A's philosophy is "they'll use what we give them." And of course, this whole "it's not done" delay is my fault. Then, and I loved this, my department lead's thought was - Well, you're handling this, I'll just not get involved at all and help with anything.
Realistic expectations and documentation would seem like such a common sense approach - but it never happens.
This is the future site for the FreeBSD logo competiton which is meant
to create a new logo for the FreeBSD Project to supplement the current
Beastie mascot. Despite an early draft announcement that got out we
are not quite ready for the logos yet. Please watch this space and the
freebsd-announce mailing list for more information in the near future.
http://logo-contest.freebsd.org/
Evidently, they are adding a logo without removing the old, according to their site. Still, the daemon is FreeBSD and it should not be changed.
I would have to agree with those advocating experience. Get some experience now; the more the better. While in college I setup a unix server and was admining it, selling hosting accounts to friends and associates. The experience got me my first SysAd job, not the degree.
The degree, like certifications, are things to allow human resources people to qualify, or really, disqualify people before the real interviews start to take place. Once in the interview, they want to know what you know, not where you learned it.
If you are comfortable with your current program, I'd advocate staying put as well. Moving just for the name isn't going to make any significant difference in the long run.
Nuclear reactors are viable only for a certain number of years before they become too contaminated and have to be shut down. They were to account for this in the operation of the reactor, but for most reactors, that is a forgotten rule. These reactors will remain contaiminated for 1000's of years after they have outlived their service life.
Spent fuel rods for nuclear reactors will also remain radio active for centuries after we have used the energy they generated. Long term storage of them in the Nevada desert is the best solution they can come up with for these so far.
This is far too dangerous a proposition, given the extreme number of years the waste from these plants will generate. I am not anti-nuclear fuel, but I do not see it alone as a viable solution.
Our entire transportation base is based on fossile fuels. From our Deisel trains to all of the automobiles and trucks in the states. The emergence of energy driven vehicles and hybrid vehicles is too new and there are far too few of them that could be used for the backbone of the transportation industry. The cities could not afford to put in all of the electricity lines necessary to replace their public transportation systems with electric ones. The list just goes on and on.
There is no way we could do this, and I fail to see how creating tons and tons of radioactive waste would improve the situation.
1. First and foremost, our non-technical users are not on Windows. We use a Suse 9 distributed network, with all users authenticating to a DLAP/NFS server and all files are remotely stored for them. For our non-technical users that merely need a browser to access web based administration systems, this works well. The users are using a combination of Mozilla and Konquerer for their applications and kmail for their email.
2. In our development and managerial environments we are using a mix of Windows 2000 and XP. We do not run a domain controller. We restrict admin access from those who lack the technical ability to understand and mitigate the risks. For those that understand, they are given administrative access, but are also given a normal user account. They run their day to day operations on the normal user account and can switch, when necessary to install or adjust configurations. This way, they can do what they need to do, but their day to day operations and their spare time surfing does not effect the machines.
We are a small organization. Our rollout of machines numbers in the double digits, not the triple or quadruple numbers.
In the two years I have been running this organization in this mannor, we have never had to deal with a virus issue and I have had exactly 1 malware issue that had to be resolved. That issue was solved rather quickly, by removing the admin access from the user, as he realized what he had done was inappropriate and he was going to be restricted at that point. Our user education programs are small but effective and they have protected the investment we have in equipment.
I've run mail servers for years and have, at times, thought the war on spam was a lost cause. I have taken these steps to reduce the spam. I do not use globals, or global email addresses of *@domain.com. They catch a lot of spam and then a lot of other stuff that you just don't need.
I also run and maintain a blacklist, sometimes incorrectly referred to as an RBL. RBL was the name of one such list, not all of them. With a simple web interface and a MySQL database behind it, our blacklist is kept up to date by the most ardent of our spam haters. They dilligently add the new IP addresses for any spam they receive. We went form blocking 10 to 20 emails a day from the blacklist to blocking 1000's in a matter of days.
In addition to our blacklist, our mail server runs on several other blacklists, such as spamcop and spamhaus lists. Beyond that, we also use a mail filtering program called spamassassin. This is just one of several out there available.
But, I'm getting away from the question. I have had bad experiences with global email addresses and can not, in good faith, recommend them. The best solution is to maintain your own mail server and configure it to fight the war on spam as best as you can. Running with an ISP solution limits what you can do. Setting up a global email address just sets you up for more spam. Putting an email address on a webpage just sets you up for more. If you have to publish an email address, make a second one and filter it in your email client, realizing that you will get bombarded with spam on it.
When we have police check points every 20 miles and are required to have the correct paperwork to cross the checkpoints, it's a police state.
When we no longer have any say in anything, it is a police state. (We still get to vote on politicians and referendums, and no, just because the guy you want to vote for lost, doesn't mean it's an unfair system.)
When we are told at the tender age of 6 or 7 what our life long career will be, it's a police state.
When we are told what we will buy with what little money we have, it's a police state.
.. My point is simple: It could be a whole hell of a lot worse than it is. If you feel strangled now, might I suggest a trip to the far east? China is a nice destination. So is North Korea. Perhaps even a little closer to home, try the near east, and almost westernized Turkey. Try Nigeria or any of a number of central American countries where the public is oppressed by multiple factions, including the police force.
I, too, am concerned about our privacy and my bio-data influencing insurance decisions, job decisions, etc. That don't make it a police state. Why does everything have to be extremes on both sides of any issue?
There was a varient of debian out there called Storm. It was relatively powerful, and yet had a great GUI for the beginner. As with any distribution, the installation would start asking questions about things you can not possibly completely understand at first or with a templated "beginner" install that would invariably not include something needed (such as a c++ compiler), so multiple installs are often necessary to get it setup with everything you want on it. (Hint: even if you don't code, you need a c compiler to install other programs).
Anyway, checking their website, I am sad to say they have closed up operations. I knew they had done this months ago, but the "hybernation" message is still on their web site.
I started with Slackware 3.0 on an old Gateway P5/100 as a dual boot system. I've run FreeBSD on my servers for years. I've run Slackware, Red Hat, Mandrake and a few interesting variations here at home just playing with them and I have to tell you, the most important part of picking a distribution is hardware compatability, imo.
For instance, on the machine I am on right now, I could not install Storm. It would not recognize the ethernet card in the system. I could, however, install FreeBSD on this one. Now if I changed out the D-Link ("el-cheapo") 100BaseT fast ethernet card for the other D-Link "el-cheapo", which is 10BaseT, I could install Storm, but them FreeBSD would not recognize it. Everything revolves around the hardware issues, or at least so it would seem.
Check through the sites, and find the ones that list your hardware - Start there. It's probably the least frustrating way to start.
Slashdot Mirror
For those so inclined. Found these as I went searching for the commercial.
http://pictureshq.net/candice_michelle
This was linked from here:
http://wizbangblog.com/archives/005007.php
That's two in a row. At least the first one was somewhat funny....
The last one was a charm -
Final Update: Wow. Just wow. You guys really like to ream the buggery out of a webserver when presented with an opportunity eh? It's 1am down here now, I'm off to bed. Knock yourselves out, and turn the lights out when you're finished.
GP
Even internal projects are this way. I got one from accounting for some tracking software with requirements in December. I wrote the code and tested it and then showed it to accounting.
At the end of January, it was still not implimented. Accounting came back with a fistful of more things it "should do". I added them and by mid-Feb it was being "beta tested" by the departments.
Of course, this added another fist full of requirements, reports and other assorted stuff they wanted added.
Bottom line was that for something that was a "small two week" project in December, I'm still adding code to at the end of March.
In this case, it was a failure to plan, and a distinct failure to include all personnel who would be involved in it. I tried to coordinate this from the start, but A doesn't want to talk to B, who doesn't want to talk to C. A's philosophy is "they'll use what we give them." And of course, this whole "it's not done" delay is my fault. Then, and I loved this, my department lead's thought was - Well, you're handling this, I'll just not get involved at all and help with anything.
Realistic expectations and documentation would seem like such a common sense approach - but it never happens.
GP
About this site
This is the future site for the FreeBSD logo competiton which is meant
to create a new logo for the FreeBSD Project to supplement the current
Beastie mascot. Despite an early draft announcement that got out we
are not quite ready for the logos yet. Please watch this space and the
freebsd-announce mailing list for more information in the near future.
http://logo-contest.freebsd.org/
Evidently, they are adding a logo without removing the old, according to their site. Still, the daemon is FreeBSD and it should not be changed.
GP
I would have to agree with those advocating experience. Get some experience now; the more the better. While in college I setup a unix server and was admining it, selling hosting accounts to friends and associates. The experience got me my first SysAd job, not the degree.
The degree, like certifications, are things to allow human resources people to qualify, or really, disqualify people before the real interviews start to take place. Once in the interview, they want to know what you know, not where you learned it.
If you are comfortable with your current program, I'd advocate staying put as well. Moving just for the name isn't going to make any significant difference in the long run.
Experience will!
Nuclear reactors are viable only for a certain number of years before they become too contaminated and have to be shut down. They were to account for this in the operation of the reactor, but for most reactors, that is a forgotten rule. These reactors will remain contaiminated for 1000's of years after they have outlived their service life.
Spent fuel rods for nuclear reactors will also remain radio active for centuries after we have used the energy they generated. Long term storage of them in the Nevada desert is the best solution they can come up with for these so far.
This is far too dangerous a proposition, given the extreme number of years the waste from these plants will generate. I am not anti-nuclear fuel, but I do not see it alone as a viable solution.
Our entire transportation base is based on fossile fuels. From our Deisel trains to all of the automobiles and trucks in the states. The emergence of energy driven vehicles and hybrid vehicles is too new and there are far too few of them that could be used for the backbone of the transportation industry. The cities could not afford to put in all of the electricity lines necessary to replace their public transportation systems with electric ones. The list just goes on and on.
There is no way we could do this, and I fail to see how creating tons and tons of radioactive waste would improve the situation.
GP
We have solved this in a couple of ways:
1. First and foremost, our non-technical users are not on Windows. We use a Suse 9 distributed network, with all users authenticating to a DLAP/NFS server and all files are remotely stored for them. For our non-technical users that merely need a browser to access web based administration systems, this works well. The users are using a combination of Mozilla and Konquerer for their applications and kmail for their email.
2. In our development and managerial environments we are using a mix of Windows 2000 and XP. We do not run a domain controller. We restrict admin access from those who lack the technical ability to understand and mitigate the risks. For those that understand, they are given administrative access, but are also given a normal user account. They run their day to day operations on the normal user account and can switch, when necessary to install or adjust configurations. This way, they can do what they need to do, but their day to day operations and their spare time surfing does not effect the machines.
We are a small organization. Our rollout of machines numbers in the double digits, not the triple or quadruple numbers.
In the two years I have been running this organization in this mannor, we have never had to deal with a virus issue and I have had exactly 1 malware issue that had to be resolved. That issue was solved rather quickly, by removing the admin access from the user, as he realized what he had done was inappropriate and he was going to be restricted at that point. Our user education programs are small but effective and they have protected the investment we have in equipment.
GP
SIG not required.
I've run mail servers for years and have, at times, thought the war on spam was a lost cause. I have taken these steps to reduce the spam. I do not use globals, or global email addresses of *@domain.com. They catch a lot of spam and then a lot of other stuff that you just don't need.
I also run and maintain a blacklist, sometimes incorrectly referred to as an RBL. RBL was the name of one such list, not all of them. With a simple web interface and a MySQL database behind it, our blacklist is kept up to date by the most ardent of our spam haters. They dilligently add the new IP addresses for any spam they receive. We went form blocking 10 to 20 emails a day from the blacklist to blocking 1000's in a matter of days.
In addition to our blacklist, our mail server runs on several other blacklists, such as spamcop and spamhaus lists. Beyond that, we also use a mail filtering program called spamassassin. This is just one of several out there available.
But, I'm getting away from the question. I have had bad experiences with global email addresses and can not, in good faith, recommend them. The best solution is to maintain your own mail server and configure it to fight the war on spam as best as you can. Running with an ISP solution limits what you can do. Setting up a global email address just sets you up for more spam. Putting an email address on a webpage just sets you up for more. If you have to publish an email address, make a second one and filter it in your email client, realizing that you will get bombarded with spam on it.
gpmac
When....
.. My point is simple: It could be a whole hell of a lot worse than it is. If you feel strangled now, might I suggest a trip to the far east? China is a nice destination. So is North Korea. Perhaps even a little closer to home, try the near east, and almost westernized Turkey. Try Nigeria or any of a number of central American countries where the public is oppressed by multiple factions, including the police force.
When we have police check points every 20 miles and are required to have the correct paperwork to cross the checkpoints, it's a police state.
When we no longer have any say in anything, it is a police state. (We still get to vote on politicians and referendums, and no, just because the guy you want to vote for lost, doesn't mean it's an unfair system.)
When we are told at the tender age of 6 or 7 what our life long career will be, it's a police state.
When we are told what we will buy with what little money we have, it's a police state.
I, too, am concerned about our privacy and my bio-data influencing insurance decisions, job decisions, etc. That don't make it a police state. Why does everything have to be extremes on both sides of any issue?
GP
There was a varient of debian out there called Storm. It was relatively powerful, and yet had a great GUI for the beginner. As with any distribution, the installation would start asking questions about things you can not possibly completely understand at first or with a templated "beginner" install that would invariably not include something needed (such as a c++ compiler), so multiple installs are often necessary to get it setup with everything you want on it. (Hint: even if you don't code, you need a c compiler to install other programs).
Anyway, checking their website, I am sad to say they have closed up operations. I knew they had done this months ago, but the "hybernation" message is still on their web site.
I started with Slackware 3.0 on an old Gateway P5/100 as a dual boot system. I've run FreeBSD on my servers for years. I've run Slackware, Red Hat, Mandrake and a few interesting variations here at home just playing with them and I have to tell you, the most important part of picking a distribution is hardware compatability, imo.
For instance, on the machine I am on right now, I could not install Storm. It would not recognize the ethernet card in the system. I could, however, install FreeBSD on this one. Now if I changed out the D-Link ("el-cheapo") 100BaseT fast ethernet card for the other D-Link "el-cheapo", which is 10BaseT, I could install Storm, but them FreeBSD would not recognize it. Everything revolves around the hardware issues, or at least so it would seem.
Check through the sites, and find the ones that list your hardware - Start there. It's probably the least frustrating way to start.