I've only asked for pseudocode (something that looks like the language I want them writing in). syntax errors, shortcuts representing something better, etc.
For example, I'm perfectly happy with:
function do_something($var){// do requested item
};
(sorry, Slashdot ate my formatting on that. Assume correct line breaks and spacing)
I may ask them to elaborate on some part.
I've asked prospective Linux sysadmins to show me how to set an IP. Most of us can rattle it off. Some get stuck when I tell them that a redhat conf file isn't going to work in this scenario. Most can give me the command line perfectly, or close enough.
I've had sysadmins who say they can write shell scripts. I give them a request of something that can be written in a few lines, in their favorite shell language. Some people get hung up on printing a line to the screen. We're talking about print, not even something as complex (hmmm) as sprintf.
I'm usually looking for basic skill sets, where I can work with them.
I was referencing a standard radiator cap. A high temperature plastic cap, with spring steel, to keep roughly 200 degree water under at least 15psi, but excessive pressure is allowed to push the seal up to allow the release of potentially catastrophic pressure.
And you show me a plastic toy?
Show me a printer that could make such a device. It's not rocket science to make one. It's just impossible with any current 3d printers.
The mention was printing a car. You can't even show me how to make that one simple piece.
You seem somewhat pro-nuke, so I'm not really sure what your point is.
Well...
I'm not pro-nuke, nor anti-nuke. What I am against is people using faulty information, and spewing the same, just to fulfill some agenda. The backing behind such publicity as seen in the link, comes from those with the largest interest (i.e., the nuclear power industry).
Nuclear power facilities are a tool to accomplish a task. The current preferred array of tools to accomplish this are less than satisfactory. Beyond that, they are dangerous in various ways. I really don't need to outline them, the information is readily available.
The "future" technologies that are currently being deployed, such as solar, wind, and tidal generation facilities, are an excellent choice.
Pushing dangerous technologies instead of better technologies is insanity. Unfortunately, there are plenty of people with a financial motivation to stay with the dangerous technologies, and even expand their footprints.
I'm no tree hugger, anti-whatever activist. I hate seeing people make the wrong decisions for the wrong reasons.
No, shutting down every nuclear plant isn't practical. It's as impractical as shutting down every oil and coal plant. We both know that people will fight for both of those. They have been for years. You'll find people who will fight against... well... anything.
You're saying that two fledgling industries (wind and solar) have had a higher death rate per MWHr than an industry who has been around for years, and have many employees who have never even been near the outer shell of the reactor?
Energy Source Death Rate (deaths per TWh) Coal - world average 161 (26% of world energy, 50% of electricity) Coal - China 278 Coal - USA 15 Oil 36 (36% of world energy) Natural Gas 4 (21% of world energy) Biofuel/Biomass 12 Peat 12 Solar (rooftop) 0.44 (less than 0.1% of world energy) Wind 0.15 (less than 1% of world energy) Hydro 0.10 (europe death rate, 2.2% of world energy) Hydro - world including Banqiao) 1.4 (about 2500 TWh/yr and 171,000 Banqiao dead) Nuclear 0.04 (5.9% of world energy)
Now you need to look at *how* they came up with those numbers.
First, they're measuring the rate per TWh. So I'd guess that they're estimated that 2.28TWh of solar have been produced world wide by rooftop facilities (you forgot to mention *ROOFTOP*. Like, any schmuck with a ladder who buys a solar panel). So if a single person died in a way related to that solar panel, in that 2.28TWh, that makes it so dangerous.
A more appropriate scale would have been deaths per thousand man hours, directly involved in the power generation facility. A separate number could be correlated deaths.
Come on everyone, you know this song! Sing along!
Correlation does not equal causation.
Your citation is not talking about power generation facility accidents.
For anything but nuclear, they are including environmental, public health, and even global warming. ya. The victims of hurricanes, tsunamis, forest fires, droughts.. You get the idea. They're also considering ozone, coal dust, power plant emissions. If someone dies from a respiratory related illness anywhere near a fossil fuel plant, they died because of it. I'd be willing to bet that they even included people getting hit by freight trains transporting coal, and accidents with oil tanker ships. (ya, ya, both get carried by both, I'm just making a point, not a documentary). That's every person who may have died because of something related to fossil fuel power generation since the first coal plant was built in 1926. I couldn't find a date of the first oil powered plant, but I know they've existed since at least the 1930's.
For nuclear, they are considering nuclear accidents. There have been a handful of accidents since the 1950's. The memorable accidents have caused wide spread destruction and loss of life. And of course, the accident in the Soviet Union was seriously downplayed.
But lets be fair. For hydroelectric, they were only able to pad their numbers by 171,000, when the Banquio Dam broke. A dam that showed evidence of damage just after it was built. That they knew would fail. And finally did fail. Did they include Hiroshima and Nagasaki as nuclear accidents? How about the American troops and civilians who were exposed to radiation during the first hundred or so nuclear tests. Nah, that wouldn't be fair. If you're going to count gross neglect as a cause of death, you'd damned well include intentional manslaughter in it.
So, who wins? I don't know, and I don't have the time to do a comprehensive examination of every incident at every power generation facility world wide since... well, it doesn't matter when, because I
Oh, and in most states, lights, horn, and turn signals, if they weren't included with the chassis.:)
There are a few pieces I left out, and I didn't ensure anything would actually mate up.
For $35,000 you could have fast, light, safe (if you keep it under 200mph) 4mpg rocket.
I say safe, because if you've ever seen any of the numerous NASCAR crashes, quite a few drivers walk away unharmed from crashes at over 150mph, where the car is thrown, flipped, run into, and otherwise did acrobatics that would leave any passenger car looking like a convenient metal coffin for the occupants.
Since most of us don't *need* 770hp, you can build a car for less than a new car costs.
You couldn't print one though. See my comments in the previous message about strength. You can't print forged parts. At least not right now. You can print something that looks like them though. You may be able to print a mold, but by the time you consider the rest of what it takes to make those parts, you're better off buying from someone who mass produces them.
Dealerships buy parts distributed by the manufacturer. Most of the price difference between a dealer part, and a quality aftermarket part is the name stamped on the box. And, of course, the price is reflected to the consumer.
The other problem is, 3d printing isn't generally good for making anything with strength. They could make something that looks exactly like what you need, but they aren't going to print a strong part. They'd have a decent chance printing plastic parts, but not anything with a bearing or forged components. I've seen a bit about 3d printing in metals, but that's fairly expensive, and still doesn't have the required strength.
You also run into problems with differences in materials. They can't print a hose, head gasket, brake pad, thermostat, or even a radiator cap (show me a functional 3d printed spring).
I'd be willing to go as far as to say that even small plastic trim pieces would be more expensive to print, than to get shipped in.
That's not to say it won't happen in the future, but it won't be a future where they're spraying or dripping materials to create a solid object.
The other thing is, dealerships are only required to make parts available for so many years after the vehicle is out of production. I believe that is 10 years. So when that specific model of vehicle, or other vehicles with compatible parts, is no longer being produced, they have a financial incentive to *not* make the parts any more. For many cars, when they're 15 to 20 years old, there are plenty of parts that you need to source from a junk yard, or just junk the car entirely.
I have a 1982 industrial vehicle that has this problem. Detroit Diesel made the engine. Allison made the transmission. General Motors made most of the other parts. There are a few pieces that I simply can't get replacements for. I tried to source the fan belt idler arm and pulley. DD said that particular motor was shipped with no accessories, and the don't have anything that resembles it. GM stopped making them about 10 years ago. Instead of replacing it, which was the right thing, I managed to disassemble it, fix the problem, and reassemble it. It's in the best interest of GM, and all the invested manufacturers, if I bought a new vehicle. They could sell me a $75 part, or a $100,000 vehicle.
Coincidentally, a week later Nintendo announces their new Wii Bone, targeted at the adult entertainment market. Maybe they can resurrect the FuFme product too.:)
Well.. It's not my data. It's not any data that I'm paid to protect. What do you want me to do, save the world? It's the US Government's job to protect everyone else in the world, not mine.:)
Wait.. what? Oh, my friend just told me, the US Gov't only cares if it involves oil.:)
The space and time have been defined. The god creature is everywhere. It has always been there. It will always be there. You are correct though, those who say such things don't provide any sort of quantifiable measurement to prove such a thing.
Until someone can provide a quantifiable, reproducible, method of demonstrating that it exists, the god creature ranks up with the elf I keep locked up in my closet. I'd show it to you, but it's invisible, and impossible to perceived with any of your senses, and any sort of measuring equipment.
They only see one assumption, which is proven with circular logic. "Because god said so" or "Because god did it."
Don't know the answer? Blame god. One simple (but wrong) answer to anything and everything they don't understand. And the proof of God? Well, it's in this book, so it must be true. {sigh}
It's a never ending battle of intelligence versus cultish following of a single book (although made up of several books of dubious origins).
So, you're saying the simplest answer is the best? Well...
An invisible critter who knows everything just did it.
Or...
A documentable chemical reaction occurred, and progressed through many transformations over aeons, which we are now observing a very small subset of that transformation, to which we will be a forgotten link in the chain of events thousands to millions years from now. There are libraries full of information on how it is and could be done, along with archeological evidence demonstrating quite a bit of it. (i.e., proof) There are missing elements in the proof, which simply have not been found and tested by the larger scientific community.
The first one seems simpler. Unfortunately, it is also wrong.
You can demonstrate the circumstances for the second case, and based on what is now fairly common knowledge, test and reproduce various pieces of it.
For the first case, all you can do is shrug and say "just because, I guess. Someone told me once,so it must be true." As illustrated in the movie Idiocracy, people can and will believe what they're told, and in the end will do very harmful things based on that belief, because they were told it was true for so long. "Brawndo's got what plants crave".
I still feel that it is insanity, with a good bit of cultish brain washing, that lets people ignore scientific proof, and believe what they are told.
Well, it sounds like you have and will continue to spend an unhealthy amount of time collecting. It may not be stacks of newspapers waiting to crush you, but it's a obsessive behavior, and you should seek help. Hell, we could be wrong, but none of us are qualified to say that.
But since you're asking for a review of your methodology, lets have a look.
You have 64 drives in 4 machines. That's 16 drives per machine. What are the machines that you're using? 16 drives each is an awful lot. Like, my 4u raid chassis held 15 drives each. I have seen some machines like this that hold 16 drives or more in the same chassis as the motherboard. It's only about $1,000 for just the chassis. A bit pricy for a hobby.
You say you have 4 machines with 12 TB each, and 16 drives each. That's 16 750GB drives, and I'd guess you spent over $6,000 for them. Probably a lot more, as you have already collected 8TB of porn, and vast quantities of other things.
You say you spent $1,900 on the tape drive. That would be about 30 tapes (LTO4 800/1600), at about $30/ea, so another $900 on tapes. But you say you want another 100 tapes, so you can have one more generation of backups?
You mentioned using rsync between the machines. rsync is great, but as I discovered with huge filesystems is that the memory consumption is likewise huge. That, and the fingerprinting and comparison of the files would take roughly... forever and a day. Been there, done that, suffered the pain of it all. So you'd need a robust ordering system, and do them in pieces. That's how we did one of our huge sites. That's usually one of those things that people mention when talking about the wonders of a system they put together.
I'd even expect you to talk about the extra power consumption and cooling requirements. I would strongly suspect that kind of load would require at least two power circuits, but probably 3 15A to 20A circuits. I would assume you did this at home, and not in a commercial building. Most residential rooms have one, maybe two, circuits. This is usually due to lazy contractors only wanting to run one cable for adjoining walls. You didn't even mention the power supplies per machine, much less these larger issues.
And what about your network. Syncing terabytes of stuff between multiple machines is rather bandwidth hungry. Well, unless you expect it to be done this year. You wouldn't be using a regular consumer linksys/belkin/netgear switch. You'd want GigE ports on a real managed switch. That has a a pretty healthy price tag attached.
If you had such a huge investment in large storage, I'd believe you'd have a home theater system to match. You wouldn't be watching that porn on a 15" CRT.
Really, the 8TB of porn question that I raised, although questioning why you'd possibly want that, was really a question of if you had really done it.
I'd say that you're thinking and dreaming of having such a system. I seriously doubt that you've spent over $13,000 for your home porn store. ($12,800 outlined above, not including motherboard, processor, memory, cables, network gear, portable air conditioner, electrical work, etc).
This is the point that you'll argue, insist, call me a liar, probably with many profanities either written or implied.
I could be wrong, but that would lead us down the road towards unhealthy obsessions.
I swear, some of you people have memory like a steel trap.
Yup, I designed, built, and ran the network for 8 years. When they had problems a few years ago, that was about 6 months after they kicked me to the curb for my dedicated service. It was the day before Thanksgiving, 2006. Family had come out to visit, and by the end of the November 22 I had the official word that I was fired. That make for a very depressing family gathering. But hey, who am I to hold a little resentment.
Back in 2004, This was the biggest, baddest machine on the network. 1.15TB storage each. The actual configured array size was smaller. Part was RAID5, part was RAID0 (if I remember right). I remember transporting and racking those. They were damned heavy.
We had two more machines (SuperMicro 1u, nothing fancy), each with the same array chassis, with 250GB drives. At first, I had them connected to one machine as 2 RAID5's, and RAID0 across them (6.4TB). I also did it as a single RAID 5 (7.2TB). Those Promise arrays would go funky on occasion, and just stop working, so we split them between their two machines. If you dig back far enough in my journal archives on here, you can read about me talking about issues formatting them. ext3 wouldn't do it then. It does now though.
We could back up all of the VW servers (voyeurweb, redclouds, homeclips, funbags), plus all the free hosting servers, and ancillary servers (mail, dns, etc) several times over on those drives. Even with all that, we *still* had room left over.
It's amazing what we can have in our home machines now. I have more storage than that, between a few machines here. Heck, why not buy a 2TB drive, they're cheap. I'll keep trying to fill them, but...:)
I have to ask, what the hell are you going to do with 8TB of porn? What's the total runtime of all of that?
Consider, the whole Doctor Who series. 202GB is almost 11 days, 20 hours of runtime. Assuming roughly the same size, which may allow for higher resolution video with better compression, and rounding 202GB at 11 days 20 hrs down to 11 days (giving you bigger files per hour) you'd be looking at roughly 435 days.
If you beat your meat for an hour a day, ever day, you'd have 10,455 days (or 28.6 years) of masturbation material.
If you're just a perv, and for some reason like to have porn playing to enhance the ambiance of your home (which may be a bit funky with the aroma of semen and lube), assuming you sleep for 8 hours a day and don't need to have the porn playing while you sleep, you could leave it playing for every waking hour for 1.8 years before you ever watched the same smut twice.
Based on those numbers, you haven't viewed all the videos to even ensure you downloaded what you think you did. You most likely you have a significant number of malware invested decoy videos. Well, unless you believe that all those DRM signups and codec suggestions are legitimate.
So, based on this, why the hell do you need, or think you need, all that stuff and storage? There is a word for it. "hoarder". You should consider asking your shrink about disposophobia, and hypersexuality through masturbation. You can get help. It will save you a fortune in lube and unnecessary computer gear.
Well, each time I came down from the attic, it was because I *had* to. I'd be closing in on heat stroke each time, and preferred the paramedics to find my body on the floor, rather than lost in the attic for a few extra hours.
And ya, I stayed down long enough to actually get water in me, not just in my stomach.
I hate doing roof stuff, but I find it easier to be on top of the roof, than inside it, mid summer.
At least it's starting to look like winter here. The high will be 76 tomorrow. I may need a jacket.:)
At least I run recent versions of Sendmail.:) After dealing with Lotus Notes, Exchange, and iMail, I'm very happy to deal with Sendmail and it's little insanities. It handles everything I need, which I haven't been able to gracefully switch over to something else. I guess after dealing with Sendmail since the 90's, it seems pretty simple. Newbies though, aren't quite daring enough to hop into sendmail.cf and make simple changes.:)
I was there for about 8 months. Then I got a better gig. The "better" gig ended up turning into a clusterf*ck of an embezzling CFO, and a stupid CEO. When I reported the problems of the CFO to the CEO, he took the CFO's word and fired me. A few months later, no more company. You'd think it's a bad idea to hire the guy who put your father in prison doing a scam a couple decades earlier..
I went back there after 3 months of not finding anything. It was when we were in fairly deep into this shit economy.
They did take a few pieces of my advice, like "don't give everyone root access, use sudo, and only for people who have a specific need". They missed the big ones like "keep up to date with security".
It's funny that you mention the botnet. I saw my first Linux virus at that place. They knew the machine had been compromised about 3 years before I started. They had put the machine up with SSH still on port 22, and the root password of "password". They may as well have set the hostname to be "please.hack.me.example.com".:) Anyways, the did change the password after the break in. I found a couple back doors, some other script kiddie toys, and.. my first Linux virus. It was great. I was so excited. It was your run of the mill file infector, except it opened a port for listening. Did I mention, no firewalls?
They (the bosses) didn't like the fact that I killed several processes that were back doors. I presented them with the information that the machine had a virus, and it would keep opening back doors as long as anyone ran anything as root (the entire/bin/ directory was infected). I found a program that would detect, disinfect, and protect the binaries from being reinfected. They insisted on a lengthy QA process. I guess they thought I was a smart ass when i asked "Did you QA the virus?" So they had me infect *another* machine. Ok, easy. copied a binary over, ran it, there, you're infected. They tested to see if things ran ok *with* the virus. They infected another machine in the process too.:) I then disinfected the testing machine, and they tested again.
A few months later, I still hadn't received permission to disinfect the **PRODUCTION** machine that was infected. A couple others got hit meanwhile, because someone didn't see the memo of "This machine has a virus, don't copy anything to or from it!".
I'm not all that sure that they ever cleaned it, but the machine was finally removed from production, and had a fresh OS put on it. Well, fresh RedHat 6.2. {sigh}
For the most part, most shops only need a couple people who know Linux well enough to build their own kernel, and fix missing library errors if they're compiling something special. Like, "oohh, libmcrypt is missing, grab the package from our repo and install it." If they can do that, they usually know enough to fix corrupt filesystems, and swap hard drives.
Places that run custom stuff usually have their programmers who wrote it. Well, unless they're locked into an ancient OS, because the guy who compiled it left years ago, and took the source to everything with him. {sigh}
No, there are tremendous reasons to upgrade. I am guessing that you are one of those people who resisted the move to 32-bit, when "16-bit is good enough, and I love my 286!".
First, and not least, is performance. 64-bit Linux will run 10% to 30% faster, depending on who you reference. In the real world, I saw increased performance in my servers. We bought our first couple 64 bit machines as an experiment. After seeing the performance increase, we used them for all new purchases.
Next is memory. 32-bit Linux has a kludgy ways to access large memory pools (PAE). 64-bit is managed much better.
Lets not forget about the binaries you may be using. Since we're talking about RedHat, they're probably optimized for i386 or i686, not for what your hardware can actually do. Well, the Gentoo kids can, but they apparently have way too much time on their hands.:)
And.. You (they) spent more money on those machines. Why the hell would you only partially utilize the available hardware? It's not so obvious if you have a single low-load server, but in larger setups, it could be the difference between needing 100 servers, or 125 servers. I guess if your company is bleeding money, and salaries are already in the mid to high 6-figures for everyone, then who cares about blowing cash on unnecessary equipment. I'd prefer the savings coming back to me and my staff.
I'm sure some other folks can elaborate more on this.
I'm avoiding the whole Windows 32-bit 3GB memory cap thing, since that's an artificial limitation.
I'd be willing to bet that his behavior isn't exclusively on the weekends. He probably sits in his cube researching why the CIO should change his mind, and complaining to other employees that he's right and his boss is wrong. I've seen it happen so many times, it isn't even funny.
If I'm compiling for system-wide use, I remove any distribution installed packages first. For example, Sendmail. I use my own fresh compile. Well, it's a lovely script I put together years ago, to build and install, make my custom sendmail.cf, put them in place, makes some symlinks for apps with hardcoded paths, put a check and restart script in place, and add the check script into the cron. It makes upgrade day simple. Grab the current version sources, update my script with the current version, and let it run. I only do the custom sendmail on mail servers, so there's no need to package it up for distribution. I run it twice. Once in a test environment, and then do it in production.
For something like Apache, I have a much more complicated script, as there are all kinds of prerequisites. For that, I use slackbuild scripts (http://slackbuilds.org) to make my install package for libraries that aren't distributed, or aren't up to date. Apache goes in a standardized directory for my environment, and I let it rip. With the exception of httpd.conf, my Apache directory can be directly replaced. No install/uninstall necessary. If I want to uninstall it (like, demoting a web server to be a redundant DNS server) , I just wipe out the directory, and remove the cron entry for the check script.
And, if you're a user with sudo access on my systems, and you haven't been explicitly told to make a system wide change, you'd damned well better put your binaries under ~ somewhere. Putting your binaries in the system is grounds for... well... some really harsh treatment. I hear building maintenance needs help washing out the dumpsters.:)
That sounds pretty much like my old house. There was one main peak which ran the width of the house. There were three smaller peaks, 2 towards the front, one for the back room.
The fans do solve the problem of the heat being trapped in the house. They don't solve the problem that the heat is absorbed close to ground level and trapped there. Heat in the attic, in the shingles, or blown out into nearby air, we're still heating up the environment at ground level.
Here's my installation story anyways.:)
I picked up two 15" 3000 cfm fans, with built on thermostats, and automatic slats. I set the thermostats for 80F, so they'd allow for a bit of heat buildup in the winter, but as soon as it started getting warm in the summer, they'd blast the air out.
Back to the before situation. I could see light through the peak vent, and the soffit vents. The peak vent ran almost the entire length of the main ridge. The soffit vents were around the entire edge of the roof. That's typical construction here (Florida), as it does get very hot. I know the theory is that convection currents will be established, and the heat will be pulled out.
I went up to scout out the position. I noticed that... well, it was damned hot. And I felt no air movement. Since I smoke, I figured I could use that as a test. I brought a cigarette up with me, and blew the smoke across the center of the attic. It stagnated, and just hung like a ghost. Damn, that would have been perfect for proof of the supernatural.:) I tried it along the peak, and soffits also. Nothing.
It was about 150F in the attic. I knew it was hot, but I wasn't sure how hot.. I looked online, and they said the average attic in Florida is about 150 degrees. I brought a digital thermometer up, and put it about 5 feet from the attic access door. I checked on it a few minutes later, and it read 120. A few minutes after that, it showed nothing.. After I brought it back into the house, it recovered in about an hour.:)
I started to work the next morning at dawn. I had to cut through the wall and stucco from inside, as my 16' ladder wouldn't get me close to the spot on the outside. I managed to work til about 10am. I was making frequent trips back downstairs to cool down and drink ice water. My shirt was soaked with sweat. On the last trip, just after 10am, I got up to where I was working, started to feel dizzy and uncoordinated, and stumbled my way back down to ground level. I managed to get to the bedroom, stripped down to nothing, and laid on the floor under the ceiling fan for about an hour. My wife said my whole body was bright red. Yup, it was fucking hot.
I didn't resume work til about 3am. Screw the neighbors, it was too hot up there to work during the day.
After I got it all installed and wired and turned on, I went downstairs to celebrate my victory against the attic.:) I went back up at noon. It felt to be about the same temperature as standing under a shade tree outside. Both days, it was 105 outside. The house was much colder inside on the second day, and the A/C was actually able to cycle on *and* off. Our power bill dropped by about 25% compared to the previous year, starting when I added the fans in.
So, you're saying that he (the CIO) knows what he's talking about, and made an informed decision. I may disagree with the whole RedHat family, but there's one thing that we have to remember. The CIO gets to make those decisions. There's nothing that the folks in charge hate more than some subordinate continually attempting to undermine their authority.
"No, Boccaj (the OP), I told you, you will be using CentOS. Rather than doing the work assigned to you, you've wasted time asking your friends how to change my mind. Now you'll have plenty of time to consider such decisions, while you're looking for a new job."
Ya, it's a weekend.. Ya, it's his personal time. But he's decided to use that personal time to pursue work matters. Imagine what he could be doing, instead of writing that complaint, and reading through all these posts. Damn son, you could have finished the project before Monday morning.
(FYI, no, he doesn't work or with me. I just hate people wasting time complaining about something that they can't change, when they could be doing something productive.)
Slashdot Mirror
I've only asked for pseudocode (something that looks like the language I want them writing in). syntax errors, shortcuts representing something better, etc.
For example, I'm perfectly happy with:
function do_something($var){
};
(sorry, Slashdot ate my formatting on that. Assume correct line breaks and spacing)
I may ask them to elaborate on some part.
I've asked prospective Linux sysadmins to show me how to set an IP. Most of us can rattle it off. Some get stuck when I tell them that a redhat conf file isn't going to work in this scenario. Most can give me the command line perfectly, or close enough.
I've had sysadmins who say they can write shell scripts. I give them a request of something that can be written in a few lines, in their favorite shell language. Some people get hung up on printing a line to the screen. We're talking about print, not even something as complex (hmmm) as sprintf.
I'm usually looking for basic skill sets, where I can work with them.
You're kidding, right?
I was referencing a standard radiator cap. A high temperature plastic cap, with spring steel, to keep roughly 200 degree water under at least 15psi, but excessive pressure is allowed to push the seal up to allow the release of potentially catastrophic pressure.
And you show me a plastic toy?
Show me a printer that could make such a device. It's not rocket science to make one. It's just impossible with any current 3d printers.
The mention was printing a car. You can't even show me how to make that one simple piece.
Well ...
I'm not pro-nuke, nor anti-nuke. What I am against is people using faulty information, and spewing the same, just to fulfill some agenda. The backing behind such publicity as seen in the link, comes from those with the largest interest (i.e., the nuclear power industry).
Nuclear power facilities are a tool to accomplish a task. The current preferred array of tools to accomplish this are less than satisfactory. Beyond that, they are dangerous in various ways. I really don't need to outline them, the information is readily available.
The "future" technologies that are currently being deployed, such as solar, wind, and tidal generation facilities, are an excellent choice.
Pushing dangerous technologies instead of better technologies is insanity. Unfortunately, there are plenty of people with a financial motivation to stay with the dangerous technologies, and even expand their footprints.
I'm no tree hugger, anti-whatever activist. I hate seeing people make the wrong decisions for the wrong reasons.
No, shutting down every nuclear plant isn't practical. It's as impractical as shutting down every oil and coal plant. We both know that people will fight for both of those. They have been for years. You'll find people who will fight against ... well ... anything.
Hold on...
You're saying that two fledgling industries (wind and solar) have had a higher death rate per MWHr than an industry who has been around for years, and have many employees who have never even been near the outer shell of the reactor?
Ya, I found your reference, since you kinda forgot to post it.
http://nextbigfuture.com/2011/03/deaths-per-twh-by-energy-source.html.
Now you need to look at *how* they came up with those numbers.
First, they're measuring the rate per TWh. So I'd guess that they're estimated that 2.28TWh of solar have been produced world wide by rooftop facilities (you forgot to mention *ROOFTOP*. Like, any schmuck with a ladder who buys a solar panel). So if a single person died in a way related to that solar panel, in that 2.28TWh, that makes it so dangerous.
A more appropriate scale would have been deaths per thousand man hours, directly involved in the power generation facility. A separate number could be correlated deaths.
Come on everyone, you know this song! Sing along!
Correlation does not equal causation.
Your citation is not talking about power generation facility accidents.
For anything but nuclear, they are including environmental, public health, and even global warming. ya. The victims of hurricanes, tsunamis, forest fires, droughts.. You get the idea. They're also considering ozone, coal dust, power plant emissions. If someone dies from a respiratory related illness anywhere near a fossil fuel plant, they died because of it. I'd be willing to bet that they even included people getting hit by freight trains transporting coal, and accidents with oil tanker ships. (ya, ya, both get carried by both, I'm just making a point, not a documentary). That's every person who may have died because of something related to fossil fuel power generation since the first coal plant was built in 1926. I couldn't find a date of the first oil powered plant, but I know they've existed since at least the 1930's.
For nuclear, they are considering nuclear accidents. There have been a handful of accidents since the 1950's. The memorable accidents have caused wide spread destruction and loss of life. And of course, the accident in the Soviet Union was seriously downplayed.
But lets be fair. For hydroelectric, they were only able to pad their numbers by 171,000, when the Banquio Dam broke. A dam that showed evidence of damage just after it was built. That they knew would fail. And finally did fail. Did they include Hiroshima and Nagasaki as nuclear accidents? How about the American troops and civilians who were exposed to radiation during the first hundred or so nuclear tests. Nah, that wouldn't be fair. If you're going to count gross neglect as a cause of death, you'd damned well include intentional manslaughter in it.
So, who wins? I don't know, and I don't have the time to do a comprehensive examination of every incident at every power generation facility world wide since ... well, it doesn't matter when, because I
We already have that. :)
You can build an entire car at your house. It's perfectly legal too. You don't even have to use a single OEM part.
The aftermarket industry is full of places that not only make compatible parts, but make them better.
Here's a rough idea of a monster that'll probably get you killed.
http://www.summitracing.com/parts/SLE-12542M/
770HP Engine: $20,000
http://www.summitracing.com/parts/RMG-7051626ED/
6 speed transmission: $3,700
http://www.sandrocket.com/img/pix_main/photo_gallery/pg_revisoins.4.29.06/red-green-silver1.jpg
Rolling Chassis: $10k-$30k
A bit of creative skin and windshield $2,000
Oh, and in most states, lights, horn, and turn signals, if they weren't included with the chassis. :)
There are a few pieces I left out, and I didn't ensure anything would actually mate up.
For $35,000 you could have fast, light, safe (if you keep it under 200mph) 4mpg rocket.
I say safe, because if you've ever seen any of the numerous NASCAR crashes, quite a few drivers walk away unharmed from crashes at over 150mph, where the car is thrown, flipped, run into, and otherwise did acrobatics that would leave any passenger car looking like a convenient metal coffin for the occupants.
Since most of us don't *need* 770hp, you can build a car for less than a new car costs.
You couldn't print one though. See my comments in the previous message about strength. You can't print forged parts. At least not right now. You can print something that looks like them though. You may be able to print a mold, but by the time you consider the rest of what it takes to make those parts, you're better off buying from someone who mass produces them.
Well, two problems with the first potential.
Dealerships buy parts distributed by the manufacturer. Most of the price difference between a dealer part, and a quality aftermarket part is the name stamped on the box. And, of course, the price is reflected to the consumer.
The other problem is, 3d printing isn't generally good for making anything with strength. They could make something that looks exactly like what you need, but they aren't going to print a strong part. They'd have a decent chance printing plastic parts, but not anything with a bearing or forged components. I've seen a bit about 3d printing in metals, but that's fairly expensive, and still doesn't have the required strength.
You also run into problems with differences in materials. They can't print a hose, head gasket, brake pad, thermostat, or even a radiator cap (show me a functional 3d printed spring).
I'd be willing to go as far as to say that even small plastic trim pieces would be more expensive to print, than to get shipped in.
That's not to say it won't happen in the future, but it won't be a future where they're spraying or dripping materials to create a solid object.
The other thing is, dealerships are only required to make parts available for so many years after the vehicle is out of production. I believe that is 10 years. So when that specific model of vehicle, or other vehicles with compatible parts, is no longer being produced, they have a financial incentive to *not* make the parts any more. For many cars, when they're 15 to 20 years old, there are plenty of parts that you need to source from a junk yard, or just junk the car entirely.
I have a 1982 industrial vehicle that has this problem. Detroit Diesel made the engine. Allison made the transmission. General Motors made most of the other parts. There are a few pieces that I simply can't get replacements for. I tried to source the fan belt idler arm and pulley. DD said that particular motor was shipped with no accessories, and the don't have anything that resembles it. GM stopped making them about 10 years ago. Instead of replacing it, which was the right thing, I managed to disassemble it, fix the problem, and reassemble it. It's in the best interest of GM, and all the invested manufacturers, if I bought a new vehicle. They could sell me a $75 part, or a $100,000 vehicle.
Coincidentally, a week later Nintendo announces their new Wii Bone, targeted at the adult entertainment market. Maybe they can resurrect the FuFme product too. :)
Lets have a look.
[tappity][tappity][tappity]
Yup, his shrink is recommending anti-psychotics, heavy sedation, and chemical castration.
You don't want to know the rest of what's in his file. Really. [shivers]
Well.. It's not my data. It's not any data that I'm paid to protect. What do you want me to do, save the world? It's the US Government's job to protect everyone else in the world, not mine. :)
Wait.. what? Oh, my friend just told me, the US Gov't only cares if it involves oil. :)
Thank you. My belief in Occam's Razor is renewed. :)
The space and time have been defined. The god creature is everywhere. It has always been there. It will always be there. You are correct though, those who say such things don't provide any sort of quantifiable measurement to prove such a thing.
Until someone can provide a quantifiable, reproducible, method of demonstrating that it exists, the god creature ranks up with the elf I keep locked up in my closet. I'd show it to you, but it's invisible, and impossible to perceived with any of your senses, and any sort of measuring equipment.
Except, I know the elf in my closet is real. :)
They only see one assumption, which is proven with circular logic. "Because god said so" or "Because god did it."
Don't know the answer? Blame god. One simple (but wrong) answer to anything and everything they don't understand. And the proof of God? Well, it's in this book, so it must be true. {sigh}
It's a never ending battle of intelligence versus cultish following of a single book (although made up of several books of dubious origins).
So, you're saying the simplest answer is the best? Well...
An invisible critter who knows everything just did it.
Or...
A documentable chemical reaction occurred, and progressed through many transformations over aeons, which we are now observing a very small subset of that transformation, to which we will be a forgotten link in the chain of events thousands to millions years from now. There are libraries full of information on how it is and could be done, along with archeological evidence demonstrating quite a bit of it. (i.e., proof) There are missing elements in the proof, which simply have not been found and tested by the larger scientific community.
The first one seems simpler. Unfortunately, it is also wrong.
You can demonstrate the circumstances for the second case, and based on what is now fairly common knowledge, test and reproduce various pieces of it.
For the first case, all you can do is shrug and say "just because, I guess. Someone told me once,so it must be true." As illustrated in the movie Idiocracy, people can and will believe what they're told, and in the end will do very harmful things based on that belief, because they were told it was true for so long. "Brawndo's got what plants crave".
I still feel that it is insanity, with a good bit of cultish brain washing, that lets people ignore scientific proof, and believe what they are told.
Well, it sounds like you have and will continue to spend an unhealthy amount of time collecting. It may not be stacks of newspapers waiting to crush you, but it's a obsessive behavior, and you should seek help. Hell, we could be wrong, but none of us are qualified to say that.
But since you're asking for a review of your methodology, lets have a look.
You have 64 drives in 4 machines. That's 16 drives per machine. What are the machines that you're using? 16 drives each is an awful lot. Like, my 4u raid chassis held 15 drives each. I have seen some machines like this that hold 16 drives or more in the same chassis as the motherboard. It's only about $1,000 for just the chassis. A bit pricy for a hobby.
You say you have 4 machines with 12 TB each, and 16 drives each. That's 16 750GB drives, and I'd guess you spent over $6,000 for them. Probably a lot more, as you have already collected 8TB of porn, and vast quantities of other things.
You say you spent $1,900 on the tape drive. That would be about 30 tapes (LTO4 800/1600), at about $30/ea, so another $900 on tapes. But you say you want another 100 tapes, so you can have one more generation of backups?
You mentioned using rsync between the machines. rsync is great, but as I discovered with huge filesystems is that the memory consumption is likewise huge. That, and the fingerprinting and comparison of the files would take roughly ... forever and a day. Been there, done that, suffered the pain of it all. So you'd need a robust ordering system, and do them in pieces. That's how we did one of our huge sites. That's usually one of those things that people mention when talking about the wonders of a system they put together.
I'd even expect you to talk about the extra power consumption and cooling requirements. I would strongly suspect that kind of load would require at least two power circuits, but probably 3 15A to 20A circuits. I would assume you did this at home, and not in a commercial building. Most residential rooms have one, maybe two, circuits. This is usually due to lazy contractors only wanting to run one cable for adjoining walls. You didn't even mention the power supplies per machine, much less these larger issues.
And what about your network. Syncing terabytes of stuff between multiple machines is rather bandwidth hungry. Well, unless you expect it to be done this year. You wouldn't be using a regular consumer linksys/belkin/netgear switch. You'd want GigE ports on a real managed switch. That has a a pretty healthy price tag attached.
If you had such a huge investment in large storage, I'd believe you'd have a home theater system to match. You wouldn't be watching that porn on a 15" CRT.
Really, the 8TB of porn question that I raised, although questioning why you'd possibly want that, was really a question of if you had really done it.
I'd say that you're thinking and dreaming of having such a system. I seriously doubt that you've spent over $13,000 for your home porn store. ($12,800 outlined above, not including motherboard, processor, memory, cables, network gear, portable air conditioner, electrical work, etc).
This is the point that you'll argue, insist, call me a liar, probably with many profanities either written or implied.
I could be wrong, but that would lead us down the road towards unhealthy obsessions.
I swear, some of you people have memory like a steel trap.
Yup, I designed, built, and ran the network for 8 years. When they had problems a few years ago, that was about 6 months after they kicked me to the curb for my dedicated service. It was the day before Thanksgiving, 2006. Family had come out to visit, and by the end of the November 22 I had the official word that I was fired. That make for a very depressing family gathering. But hey, who am I to hold a little resentment.
Back in 2004, This was the biggest, baddest machine on the network. 1.15TB storage each. The actual configured array size was smaller. Part was RAID5, part was RAID0 (if I remember right). I remember transporting and racking those. They were damned heavy.
We had two more machines (SuperMicro 1u, nothing fancy), each with the same array chassis, with 250GB drives. At first, I had them connected to one machine as 2 RAID5's, and RAID0 across them (6.4TB). I also did it as a single RAID 5 (7.2TB). Those Promise arrays would go funky on occasion, and just stop working, so we split them between their two machines. If you dig back far enough in my journal archives on here, you can read about me talking about issues formatting them. ext3 wouldn't do it then. It does now though.
I found the posts.
15 November 2004
16 November 2004
We could back up all of the VW servers (voyeurweb, redclouds, homeclips, funbags), plus all the free hosting servers, and ancillary servers (mail, dns, etc) several times over on those drives. Even with all that, we *still* had room left over.
It's amazing what we can have in our home machines now. I have more storage than that, between a few machines here. Heck, why not buy a 2TB drive, they're cheap. I'll keep trying to fill them, but... :)
I have to ask, what the hell are you going to do with 8TB of porn? What's the total runtime of all of that?
Consider, the whole Doctor Who series. 202GB is almost 11 days, 20 hours of runtime. Assuming roughly the same size, which may allow for higher resolution video with better compression, and rounding 202GB at 11 days 20 hrs down to 11 days (giving you bigger files per hour) you'd be looking at roughly 435 days.
If you beat your meat for an hour a day, ever day, you'd have 10,455 days (or 28.6 years) of masturbation material.
If you're just a perv, and for some reason like to have porn playing to enhance the ambiance of your home (which may be a bit funky with the aroma of semen and lube), assuming you sleep for 8 hours a day and don't need to have the porn playing while you sleep, you could leave it playing for every waking hour for 1.8 years before you ever watched the same smut twice.
Based on those numbers, you haven't viewed all the videos to even ensure you downloaded what you think you did. You most likely you have a significant number of malware invested decoy videos. Well, unless you believe that all those DRM signups and codec suggestions are legitimate.
So, based on this, why the hell do you need, or think you need, all that stuff and storage? There is a word for it. "hoarder". You should consider asking your shrink about disposophobia, and hypersexuality through masturbation. You can get help. It will save you a fortune in lube and unnecessary computer gear.
Well, each time I came down from the attic, it was because I *had* to. I'd be closing in on heat stroke each time, and preferred the paramedics to find my body on the floor, rather than lost in the attic for a few extra hours.
And ya, I stayed down long enough to actually get water in me, not just in my stomach.
I hate doing roof stuff, but I find it easier to be on top of the roof, than inside it, mid summer.
At least it's starting to look like winter here. The high will be 76 tomorrow. I may need a jacket. :)
At least I run recent versions of Sendmail. :) After dealing with Lotus Notes, Exchange, and iMail, I'm very happy to deal with Sendmail and it's little insanities. It handles everything I need, which I haven't been able to gracefully switch over to something else. I guess after dealing with Sendmail since the 90's, it seems pretty simple. Newbies though, aren't quite daring enough to hop into sendmail.cf and make simple changes. :)
I was there for about 8 months. Then I got a better gig. The "better" gig ended up turning into a clusterf*ck of an embezzling CFO, and a stupid CEO. When I reported the problems of the CFO to the CEO, he took the CFO's word and fired me. A few months later, no more company. You'd think it's a bad idea to hire the guy who put your father in prison doing a scam a couple decades earlier..
I went back there after 3 months of not finding anything. It was when we were in fairly deep into this shit economy.
They did take a few pieces of my advice, like "don't give everyone root access, use sudo, and only for people who have a specific need". They missed the big ones like "keep up to date with security".
It's funny that you mention the botnet. I saw my first Linux virus at that place. They knew the machine had been compromised about 3 years before I started. They had put the machine up with SSH still on port 22, and the root password of "password". They may as well have set the hostname to be "please.hack.me.example.com". :) Anyways, the did change the password after the break in. I found a couple back doors, some other script kiddie toys, and .. my first Linux virus. It was great. I was so excited. It was your run of the mill file infector, except it opened a port for listening. Did I mention, no firewalls?
They (the bosses) didn't like the fact that I killed several processes that were back doors. I presented them with the information that the machine had a virus, and it would keep opening back doors as long as anyone ran anything as root (the entire /bin/ directory was infected). I found a program that would detect, disinfect, and protect the binaries from being reinfected. They insisted on a lengthy QA process. I guess they thought I was a smart ass when i asked "Did you QA the virus?" So they had me infect *another* machine. Ok, easy. copied a binary over, ran it, there, you're infected. They tested to see if things ran ok *with* the virus. They infected another machine in the process too. :) I then disinfected the testing machine, and they tested again.
A few months later, I still hadn't received permission to disinfect the **PRODUCTION** machine that was infected. A couple others got hit meanwhile, because someone didn't see the memo of "This machine has a virus, don't copy anything to or from it!".
I'm not all that sure that they ever cleaned it, but the machine was finally removed from production, and had a fresh OS put on it. Well, fresh RedHat 6.2. {sigh}
For the most part, most shops only need a couple people who know Linux well enough to build their own kernel, and fix missing library errors if they're compiling something special. Like, "oohh, libmcrypt is missing, grab the package from our repo and install it." If they can do that, they usually know enough to fix corrupt filesystems, and swap hard drives.
Places that run custom stuff usually have their programmers who wrote it. Well, unless they're locked into an ancient OS, because the guy who compiled it left years ago, and took the source to everything with him. {sigh}
No, there are tremendous reasons to upgrade. I am guessing that you are one of those people who resisted the move to 32-bit, when "16-bit is good enough, and I love my 286!".
First, and not least, is performance. 64-bit Linux will run 10% to 30% faster, depending on who you reference. In the real world, I saw increased performance in my servers. We bought our first couple 64 bit machines as an experiment. After seeing the performance increase, we used them for all new purchases.
Next is memory. 32-bit Linux has a kludgy ways to access large memory pools (PAE). 64-bit is managed much better.
Lets not forget about the binaries you may be using. Since we're talking about RedHat, they're probably optimized for i386 or i686, not for what your hardware can actually do. Well, the Gentoo kids can, but they apparently have way too much time on their hands. :)
And.. You (they) spent more money on those machines. Why the hell would you only partially utilize the available hardware? It's not so obvious if you have a single low-load server, but in larger setups, it could be the difference between needing 100 servers, or 125 servers. I guess if your company is bleeding money, and salaries are already in the mid to high 6-figures for everyone, then who cares about blowing cash on unnecessary equipment. I'd prefer the savings coming back to me and my staff.
I'm sure some other folks can elaborate more on this.
I'm avoiding the whole Windows 32-bit 3GB memory cap thing, since that's an artificial limitation.
I think that was the primary motivation for Google setting up their public DNS servers (8.8.8.8, 8.8.4.4).
http://code.google.com/speed/public-dns/
I'd be willing to bet that his behavior isn't exclusively on the weekends. He probably sits in his cube researching why the CIO should change his mind, and complaining to other employees that he's right and his boss is wrong. I've seen it happen so many times, it isn't even funny.
If I'm compiling for system-wide use, I remove any distribution installed packages first. For example, Sendmail. I use my own fresh compile. Well, it's a lovely script I put together years ago, to build and install, make my custom sendmail.cf, put them in place, makes some symlinks for apps with hardcoded paths, put a check and restart script in place, and add the check script into the cron. It makes upgrade day simple. Grab the current version sources, update my script with the current version, and let it run. I only do the custom sendmail on mail servers, so there's no need to package it up for distribution. I run it twice. Once in a test environment, and then do it in production.
For something like Apache, I have a much more complicated script, as there are all kinds of prerequisites. For that, I use slackbuild scripts (http://slackbuilds.org) to make my install package for libraries that aren't distributed, or aren't up to date. Apache goes in a standardized directory for my environment, and I let it rip. With the exception of httpd.conf, my Apache directory can be directly replaced. No install/uninstall necessary. If I want to uninstall it (like, demoting a web server to be a redundant DNS server) , I just wipe out the directory, and remove the cron entry for the check script.
And, if you're a user with sudo access on my systems, and you haven't been explicitly told to make a system wide change, you'd damned well better put your binaries under ~ somewhere. Putting your binaries in the system is grounds for ... well ... some really harsh treatment. I hear building maintenance needs help washing out the dumpsters. :)
That sounds pretty much like my old house. There was one main peak which ran the width of the house. There were three smaller peaks, 2 towards the front, one for the back room.
The fans do solve the problem of the heat being trapped in the house. They don't solve the problem that the heat is absorbed close to ground level and trapped there. Heat in the attic, in the shingles, or blown out into nearby air, we're still heating up the environment at ground level.
Here's my installation story anyways. :)
I picked up two 15" 3000 cfm fans, with built on thermostats, and automatic slats. I set the thermostats for 80F, so they'd allow for a bit of heat buildup in the winter, but as soon as it started getting warm in the summer, they'd blast the air out.
Back to the before situation. I could see light through the peak vent, and the soffit vents. The peak vent ran almost the entire length of the main ridge. The soffit vents were around the entire edge of the roof. That's typical construction here (Florida), as it does get very hot. I know the theory is that convection currents will be established, and the heat will be pulled out.
I went up to scout out the position. I noticed that ... well, it was damned hot. And I felt no air movement. Since I smoke, I figured I could use that as a test. I brought a cigarette up with me, and blew the smoke across the center of the attic. It stagnated, and just hung like a ghost. Damn, that would have been perfect for proof of the supernatural. :) I tried it along the peak, and soffits also. Nothing.
It was about 150F in the attic. I knew it was hot, but I wasn't sure how hot.. I looked online, and they said the average attic in Florida is about 150 degrees. I brought a digital thermometer up, and put it about 5 feet from the attic access door. I checked on it a few minutes later, and it read 120. A few minutes after that, it showed nothing.. After I brought it back into the house, it recovered in about an hour. :)
I started to work the next morning at dawn. I had to cut through the wall and stucco from inside, as my 16' ladder wouldn't get me close to the spot on the outside. I managed to work til about 10am. I was making frequent trips back downstairs to cool down and drink ice water. My shirt was soaked with sweat. On the last trip, just after 10am, I got up to where I was working, started to feel dizzy and uncoordinated, and stumbled my way back down to ground level. I managed to get to the bedroom, stripped down to nothing, and laid on the floor under the ceiling fan for about an hour. My wife said my whole body was bright red. Yup, it was fucking hot.
I didn't resume work til about 3am. Screw the neighbors, it was too hot up there to work during the day.
After I got it all installed and wired and turned on, I went downstairs to celebrate my victory against the attic. :) I went back up at noon. It felt to be about the same temperature as standing under a shade tree outside. Both days, it was 105 outside. The house was much colder inside on the second day, and the A/C was actually able to cycle on *and* off. Our power bill dropped by about 25% compared to the previous year, starting when I added the fans in.
So, you're saying that he (the CIO) knows what he's talking about, and made an informed decision. I may disagree with the whole RedHat family, but there's one thing that we have to remember. The CIO gets to make those decisions. There's nothing that the folks in charge hate more than some subordinate continually attempting to undermine their authority.
"No, Boccaj (the OP), I told you, you will be using CentOS. Rather than doing the work assigned to you, you've wasted time asking your friends how to change my mind. Now you'll have plenty of time to consider such decisions, while you're looking for a new job."
Ya, it's a weekend.. Ya, it's his personal time. But he's decided to use that personal time to pursue work matters. Imagine what he could be doing, instead of writing that complaint, and reading through all these posts. Damn son, you could have finished the project before Monday morning.
(FYI, no, he doesn't work or with me. I just hate people wasting time complaining about something that they can't change, when they could be doing something productive.)