What makes these tall grass prairie reserves so special is that they are one of a few places in the plains where you can look across a piece of land and see what it looked like before we completely transformed everything. I personally don't think that windmills are ugly at all an I'm all for it in the midwest. But if you place a windmill farm within sight of the prarie, this feeling of it being untouched will be lost.
So I guess those oil pumps on said land were there before we transformed everything? Bullocks. Even if that's the real concern, there is plenty of pristine prairie in the national parks on the Eastern slope of the Rockies. The lazy American Indian tribal elders simply want to be paid a high rent for the land the wind turbines sit on, period. Do a little Googling or watch PBS to learn about reservations, the corruption, the fat pockets of the elders, the shacks that the average "tribesmen" live in, the total lack of productivity, the 70%+ unemployment rate, rampant alcoholism encouraged by the "haves" to keep the "have nots" sedated and agreeable, etc. There aren't enough population centers nearby to make a casino profitable in those lands, unlike other reservations in the region, so the "free income" sources for these tribes are much more limited. They want a payday, pure and simple.
We have 3 arrays of wind turbines in Atchison County, Missouri, a 72, a 24, and a 4. The first two feed grids and the 4 turbine site powers the city or Rock Port. There was a big effort here years ago to get these wind farms, for a few reasons:
1. JOBS--including initial construction (hundreds) and maintenance. Less than two dozen long term jobs were created but they pay very well in this rural area with a population of about 5,000 and a workforce of around 1,500. Most of the total population is retired/elderly. 2. Local economy boost during the 2+ year construction--hotel rooms for crews, restaurants, etc. 3. Property tax revenue on the rigs which is in the multiple thousands per rig per year even after the "tax breaks" used to draw the operators 4. Land stipend (rent) to the farmers who gave easement, $5,000/year per turbine--some farmers have 20 units on their land--$100k/year
Note that the Indian elder did not mention JOBS at all, only easement rent, and curiously, nothing about tax revenue. Politicians are always about jobs for their constituents, and these elders are politicians by definition. They don't want jobs for their people, simply a fat payday, just like they currently have with the oil. At this point in the game, the Indians are simply attempting to generate sympathy in the press to drive up the payment amount down the road when they sign the papers.
I'm not a fan of Obama, but I agree with the counterproposal he used in the negotiation with bin Laden. You know, the proposal that was most likely 5.56 mm wide and delivered at about 3500 feet per second by a SEAL "negotiation team."
You might have the bullet diameter correct, but your velocity figure is way the fuck high, showing you're not a gun guy, and should thus leave responses such as this to gun guys such as myself.:)
Many of these SEAL operators would have likely been carrying the M4A1 carbine. Muzzle velocity w/ M855/A1 ball, most likely what they loaded out with, is 2900 fps or less from the 14.5" barrel of this weapon, depending on altitude, temperature, humidity, etc. You're 600 fps high in this case.
Given that SEAL Team 6 has been dedicated to counter-terrorism operations since the unit was formed, and is often engaged in Close Quarters Battle, such as the bin Laden raid, some operators were likely carrying the MP5N or MP5SD submachine gun instead of the M4A1 carbine. Muzzle velocity of these two MP5 variants is 1300 fps. If one of these meat eaters popped bin Laden the bullet diameter would have been 9mm, and your velocity would have been high by an whopping 2200 fps, just shy of triple the actual projectile velocity.
Of all the stupid features from Chrome to pick up, the version numbers is, by far, the dumbest. Has anyone considered how stupid a version number in the high double digits might be? Firefox 81 seems kind of clunky, doesn't it?
Yes, it does. However, "Firefox 451", "Firefox 666", and "Firefox 911" (as in Porsche, not terrorism) seem kinda catchy to me, so maybe they should skip double digits and go straight to triple.
A lot of companies offer static ips for which you can set all the reverse dns & email information, and they are also out of their normal subscriber pool, thus allowing you to send emails from the computer behind it. The cost of that option is usually lower than 5$ per ip per month around here.
It's $10/month extra for a single static IP atop aDSL from CenturyTel here in rural Northwest Missouri. They have a local monopoly but so far their pricing is reasonable and the service is top notch--not a single outage in the past year. CenturyTel doesn't offer custom rDNS, period, neither for small business nor residential accounts. So far this hasn't been a problem. No reputable DNSBL will list an IP strictly due to generic rDNS. And CenturyTel doesn't register the parent block with the Spamhaus PBL nor any other "DUL" type DNSBLS. Neither my IP nor parent net have been listed by any reputable DNSBL. I noticed the parent net was listed on, IIRC, one of the super aggressive fiveten lists some time ago, but that didn't obviously affect delivery as nobody in their right mind outright blocks using these fiveten lists. I registered my IP with dnswl.org quite some time ago and have a 'medium' rating, which helps with delivery in cases where receivers do block based on things like generic rDNS.
221.216.41.65.list.dnswl.org. 43200 IN A 127.0.6.2
So far I've had zero problems with outbound delivery over this CenturyTel aDSL. Having a static IP is more important for deliverability than custom rDNS, but it's good to have both if you can get them. If you have static IPs and are being listed in "policy" DNSBLs, you need to talk to your ISPs and get that straightened out. If you have static IPs and you're being listed by trap driven DNSBLs, then the problem isn't with "what type of service you have" but with spam emission from zombie infected PCs behind your NAT. In this case YOU need to egress filter TCP 25 so nothing can send outbound SMTP but your mail server.
Maybe yes, maybe no. The big loser in this would be Intel. I'm not sure of the % of Dell computers that ship with AMD CPU's but it's certainly less than 25%. Dell is big enough to hurt Intel if they switch to AMD.
Which is why this "story" is purely rumor. This is simply a move by Dell to get _much_ better pricing out of Intel. Dell has no intention of actually buying AMD. They wouldn't know how to run the combined company if they did. Look at Dell's roots. Dell is a build-to-order firm, not a bottom-to-top manufacturing company.
Just wait until "ipv6 conversion specialists" are charging you $450 an hour to make sure your business is not floundering because you ignored the problem until it was an emergency.
Would you mind describing such an "emergency" situation, in detail? The only "emergency" scenario I can think of here is if your ISP/upstream dictated that within, say 90 days, they would no longer route your IPv4 traffic. The flaw in assuming such a scenario is that no ISP/upstream has a positive financial stake in doing this. They gain nothing by taking away your IPv4 abilities. In addition, if said ISP/upstream really was determined to do this, they'd simply send out an engy to install a v6/v4 gateway router. Problem solved, no material change for the customer. Note this last point carefully, because this is what the US "IPv6 conversion" will look like at almost all organizations, and most orgs worldwide with a substantial v4 installed base.
Note the U.S. government for example, and it's millions of v4 devices. If they started a wholesale conversion to v6 tomorrow, how many years, and how many 10s of billions of dollars would be consumed before the project is completed?
The people screaming like Henny Penny have no clue what kind of costs are involved in such a conversion to v6. And apparently they don't realize that most organizations that actually need large blocks of public addresses already have more than they need. Look at all the/8s assigned to US government agencies, US corporations, US carriers, the UK government, etc. If one isn't in any danger of ever exhausting one's supply of v4 addresses, what financial motivation is there to change to v6? There is none.
To make more addresses available for new users (China, worldwide wireless phone carriers), what the IETF should have done before creating this new whiz-bang v6 stack is to convert the multicast and "future use" subnets (no one uses multicast anyway) to standard subnets. Changing all the v4 stacks to recognize these subnets as normal routable nets would yield an additional 536,870,912 usable addresses, and would be a much easier change to implement--would be a simple patch to all existing v4 stacks. For devices such as network printers et al inside the perimeter, one wouldn't even need to change the firmware.
That's called a feedback loop, or FBL. These have been around a long time. Most ISPs and gorilla mailers have been using them for many years. They aren't a magic bullet against spam--far from it. An FBL is simply analogous to walking over to your neighbor's house and telling him his son just threw a rock through your window. The dad isn't able to keep tabs on his kid all the time. Same with an ISP, freemailer, or in this case, Amazon. The FBL is simply an extra set of eyes and ears.
Grötschel, an expert in optimization, observes that a benchmark production planning model solved using linear programming would have taken 82 years to solve in 1988, using the computers and the linear programming algorithms of the day. Fifteen years later – in 2003 – this same model could be solved in roughly 1 minute, an improvement by a factor of roughly 43 million. Of this, a factor of roughly 1,000 was due to increased processor speed, whereas a factor of roughly 43,000 was due to improvements in algo- rithms! Grötschel also cites an algorithmic improvement of roughly 30,000 for mixed integer programming between 1991 and 2008.
The prof is fibbing. The gains are mostly in the big on-die L2 cache with its fat, core clocked dedicated backside bus (thanks to Intergraph, and Intel for stealing it from them, then AMD, IBM, et al). The prof simply shrunk the code and data set to fit (mostly or wholly) in the 512KB/1MB cache of their 2003 era Athlon XP/Pentium IV. As with most apps, it's all in the ca$he baby, all in the ca$he.
SMTP needs a ground up re-write, and it will need it just as much (if not more) after IPV6 is deployed.
SMTP isn't the problem and is not in need of a ground up rewrite. The problem is social, between spammers and suckers, their victims. As has been shown via NNTP, instant messaging, and Facebook spam et al, there is no technology immune to spam. Spam will be with us as long as suckers exist, and there are people willing to exploit those suckers. Yes, basically for eternity.
There will start to be IPv6 dnsbls and mail OPs will start keeping IPv6 local block lists. It's the same old game with a new numbering scheme. As for multilayer NAT I don't see it being a problem WRT SMTP. As others have stated it will be relegated to consumer broadband ISP space and possibly colocation centers, which most mail OPs already outright SMTP block (if they're smart).
1: it's a dick-wagging contest to have the best supercomputer in the world..
Absolutely correct. This was clearly demonstrated by the accelerated funding and freebie process that occurred when NASA was building its first SGI Altix monster, including emergency meetings with the Governor or California's office, the DOE directors office, Intel, and SGI. The build of that machine would have normally taken a year using the normal method of assembly, construction, and testing. They cut it to less than six months with one goal in mind, and it wasn't science. It was to get a sufficient number of Linpack runs in, and tune for a final couple of "peak" runs simply so they could send results to Dongarra before the deadline for the upcoming TOP 500 list.
They thought they were going to take the #1 spot, because they weren't paying attention to their "competition", which IIRC included the first BlueGene machine from IBM (which took the #1 spot on that list). The NASA "Columbia" Altix supercomputer ended up at #3 on that list. Intel and SGI lost a *bunch* of money on that system just to get the #1 spot on the list. And they didn't. Meaning they lost all that money for nothing. For Intel this didn't mean much. For SGI, well, we all know Rackable bought them for only $45 million--less than the price of the Columbia machine. This wasn't the first "deeply discounted" system SGI shipped, and when you add up all these deals, you understand their near bankruptcy situation, and sale for a song to Rackable. That was a very sad deal...
And the IBM Cell blade has a Cell chip, the PowerXCell 8i, with 1 extra SPE, 5 times the double precision floating point performance, and with the Infiniband HCA, over 50 times faster network communications.
has over 13,000 PowerXCell 8i chips which are 4 times faster than the PS3 Cell chip on FP code. RR executes Linpack at 1.04 PetaFLOPS/s, just over double what AFRL is claiming for their little bullshit 1760 Cell cluster. If AFRL is quoting PEAK hardware performance, their 1760 PS3s would hit a mere 180 TFLOPS/s, far short of that 500 figure. The head nodes they mention would add another 10 TFLOPS/s peak. They didn't specify the number and type of GPUs in the cluster. Even so, they're still not going to hit 500 TFLOPS/s, nowhere close to it running any application, and not close to it if quoting PEAK hardware numbers.
Those Air Force boys must be smoking some good weed these days to hallucinate that 500 TFLOPS/s figure.
Regardless of what you install there's no guaranteed way to stop your kid from stumbling upon boobs on the internet. Plus who's to say it's something to worry about at all. They certainly didn't traumatize me.
What happens when the kid has already turned off Google Safe Search, then searches for "rooster" as they discussed chickens and roosters in class that day, at age 5. Rooster gives "cock" as a synonym, so he searches "cock". Then he hits the images button. Some of what he sees _will_ be traumatizing and will prompt questions to the parents. This is a far cry from coming across an issue of Playboy and seeing boobs as you and I did as youngsters. Google and the web are a game changer here and the potential for trauma is high, as well as other consequences.
all the Candian jokes are nice and all.. but this really was about trying to make people think CERN is the only thing going on in HEP or nuclear physics. Not so, and this is not a first as RHIC was there first. Glad to see CERN is catching up though.
I thought the big deal with the LHC is that it was supposed to give us the Higgs Boson, as no other collider on earth was powerful enough to create the Higgs. Enough about this QGP junk. Where's our Higgs Boson?
If your SAN array(s) are of any size (10TB+) with lots of drives (8 or more) you should take another look at XFS. The version of RHEL you were using is eons old now, shipped with kernel 2.6.18 from 2003, and probably didn't have the 2007 fixes. Also, if you were running your / filesystem on XFS, that's not recommended, because most Linux distros don't have the right integration for doing so, as you learned. Run / on EXT2/3 and your data filesystems on XFS. / filesystems aren't write transaction heavy, and don't experience lots of random IO, merely log writes, so you get zero benefit from XFS, and you can experience integration headaches, depending on your distro.
XFS is currently the most heavily developed FS on the planet, more than BTRFS. It also has superior performance to all other filesystems with almost every workload. Even more so with the recent delay log option. When configured and managed properly, it is also one of the most robust filesystems available. It is very widely deployed, especially on massive DB servers, due to its superior performance with O_DIRECT.
If you had corruption issues, not merely trunc'd files, in the past two years, then you were running an OS without the 2007 patch.
.. then you would have a 10KHz CPU (cock processing unit).
Not necessarily. If this were a superscalar cock processing unit, with say, 2 cock processing pipelines, 2 cocks could be processed per cycle. In this case, a 5KHz superscalar cock processing unit could process 10,000 cocks in one second. Cock processing is all about efficiency.
Wrong answer. XFS is extremely prone to data corruption if the system goes down uncleanly for any reason. We may strive for nine nines, but stuff still happens. A power failure on a large XFS volume is almost guaranteed to lead to truncated files and general lost data. Not so on ZFS.
You are just full of misinformation. Sudden downing of any _busy_ system due to power loss or panic is going to lead to data loss due to the buffer cache in Linux, and other factors. Full stop. Data loss != data corruption. XFS is absolutely not prone to "data corruption" under any circumstances. If you pull the plug on any system running any filesystem, you _will_ get truncated files and loss of data. This is not a function of the filesystem per se, but of the Linux buffer cache, and any write caches on the RAID card and/or disk drives themselves. Write all of your applications to fsync and the truncation after power loss problem will be less severe, but your performance will suck horribly. Again, this is equal for _all_ filesystems, not just XFS.
Maximum performance and maximum data integrity have always been mutually exclusive, and always will be. XFS kicks the crap out of all comers in write performance with delayed logging enabled. This means more data is held in RAM before flushing, more so than with the standard config, optimizing data transfer throughput and placement on disk decreasing fragmentation. Yes, this comes at a cost: If power drops, everything pending in the write buffer gets lost. This is why (real) datacenters are designed with many large and redundant UPSs and generators. However, again, data loss != data corruption. You claim above that XFS is prone to data corruption. That is horse shit.
Don't spread FUD. You don't use XFS, or at least any remotely recent (2007 on) version of it, so you don't really have a clue. And you obviously don't have an understanding of the function of the Linux VFS system and the buffer cache. As I stated, _any_ filesystem will suffer truncation and data loss if a busy system loses power when many writes are pending. If your apps make heavy use of fsync, you won't suffer as many truncations, but you will still have them occur, with ZFS, EXTx, BTRFS, etc. It _will_ happen with all of these. The only difference will be the severity, depending on how many write transactions were in flight at the time the plug was pulled.
I'm anxious to see you claim again, in your response to my points above, that ZFS is immune to truncation due to power loss. The only way this is possible is by disabling all caching, on the disk drives and controllers up through the entire software stack on the host, and using only applications that call fsync on every write operation. If this was actually done by anyone, disk write performance would drop to the point the system would be unusable. And this still wouldn't guarantee you wouldn't have a single file in the write buffer that gets truncated.
The OS has also been future-proofed, in the view of the Red Hat executives. It can support up to 16 terabytes of working memory, even though no physical system could now actually run that much memory under a single server.
"SGI Altix 4700 incorporates the shared-memory NUMAflex® architecture, which simplifies software development, workload management and system administration. It supports up to 1024 cores under one instance of Linux and as much as 128TB of globally shared memory."
"Altix® UV scales to extraordinary levels-up to 2,048 cores (256 sockets) with architectural support to 262,144 cores (32,768 sockets). Support for up to 16TB of global shared memory in a single system image, enables Altix UV to remain highly efficient at scale for applications ranging from in-memory databases, to a diverse set of data and compute-intensive HPC applications."
"This infrastructure is supported by a complete HPC solution stack running on industry standard Linux® operating systems with the choice of Novell® SUSE Linux Enterprise Server or Red Hat® Enterprise Linux® Advanced Server operating systems."
Someone didn't do his research before spouting off. This is odd considering he simply regurgitated the information Red Hat fed him. I guess the press guy at Red Hat didn't know they already had their OS running on 16TB capable SGI monsters?
Try bribing a policeman - a large percentage of the time, you'll end up in jail.
Apparently you're not from New Orleans, where you only go to jail if you don't/can't pay a bribe. Their drug unit took over the city's drug trade via forced bribes, if you will, forcing dealers to give up their business to cops to avoid arrest/jail time. At least, that's the way it used to be. The FBI crackdown some years ago may have cleaned the NOPD up just in time for Katrina.
I politely beg to differ haus. The.308 or.270 would both do a fine job here as well. Heck, we're talking about a puny pencil neck lawyer judge, right? One could easily and cost effectively purchase a.25 Jennings automatic in the North end of just about any U.S. city that would do the job, albeit at close range, and most of 'em already have the serial numbers filed off ta boot. Rich Texas judges usually live in two story white mansions with lots of shubbery, especially line'n the driveway--good hide'n spot for deploy'n that.25 Jennings auto and make'n a safe getaway. Silencers for 'em are pretty cheap, or you can easily make one yourself, being a country boy like me.
Say, uh, Slashdot don't log them there IP address thingies when people post, do they? If they do, umm, damn, uh.. I' never really done nut'n like 'at. I' just got a good imagination, folks tell me.
So what. I am a Canadian and I use the American spelling rules like 'center' and 'color'. There is likely Americans down south who like to use British spelling conventions too even though they are American.
...and then there are the idiots all over the world who believe sticking "an" in front of words starting with hard consonants makes them...something. What? Smart? European? What? Who the fuck was taught in grade school or high school English class that you say "That is an chicken sitting on an egg."? It's not "an" chicken sitting on an egg it is "a" chicken sitting on an egg.
The English article "an" is to be used only in front of words beginning with vowel sounds when spoken verbally, such as "an honest politician" or "an English gentleman" or "an asshole!". The article "a" is to be used in front of words beginning with a hard consonant sound when spoken verbally, such as "she is a beautiful woman" or "is that a cocker spaniel pissing on your shoe?" or "you're a fucking jerk".
If one is using "an" in front of consonant words as some kind of post internet age form of "emphasis" I suggest it only makes one look goofy, uneducated, or striving too hard for some odd kind of attention. I still haven't figured out where this FUBAR'd execution of this English language article started. Was it Europe or here in the US? Or?
People I know personally, who know how to use this English article properly, have started using "an" in front of consonant words in print (emails) but never do it while speaking verbally through their lips. If I was sufficiently creatively inclined I'd put together a cartoon parody of this and stick it on YouTube to shame people into dropping this stupid plague that has sprung up all over the web.
THe problem is thus not the court settlements but potential political ones.
No, the real problem is stupid Americans who allowed the fucking cell phone to become a status symbol. Recall the Motorola Razor? Same phenomenon as the iPhone but you didn't have Motorola Zealots in the purchasing crowd like with the Apple Zealots. I know 10 people who bought iPhones. One, only one, actually uses the features that would possibly justify the purchase. The other 9 bought it as a status symbol because they could afford it. Actually 3 really couldn't afford it but bought anyway. And these 3 are totally leveraged to hilt with big mortgage, car note, maxed credit cards, etc etc. They just had to have the iPhone to keep up with the Joneses.
Cell phones have ruined our social discourse in many ways. I got so fed up with the status symbol crap and having a cell glued to my ear that I canceled my contract one day 3 years ago and chucked the phone in the can. I regained aspects of my life that I'd forgotten I once had. I've since bought a prepaid phone that stays in the car for emergency use only, and I went back to carrying a pager, again, for emergencies only, whether family or business.
The freedom of no longer having to plug my head into and electronic gizmo 20 times a day can't be sufficiently described in words. I got life back, or at least most of it.
It's not about the guy that was executed, it was about an official, and extremely serious and somber statement, made via what many consider the lowest form of communication. What if you had a wedding, and the bridal march was done by some guys farting, or your Masters Degree was on a post-it note?
Some forms of communication are just not considered to be appropriate for some types of information.
The announcement of this murderer's execution should be nothing more than a recording of the gun shots and the dirt hitting the box sent to the media.
Slashdot Mirror
What makes these tall grass prairie reserves so special is that they are one of a few places in the plains where you can look across a piece of land and see what it looked like before we completely transformed everything. I personally don't think that windmills are ugly at all an I'm all for it in the midwest. But if you place a windmill farm within sight of the prarie, this feeling of it being untouched will be lost.
So I guess those oil pumps on said land were there before we transformed everything? Bullocks. Even if that's the real concern, there is plenty of pristine prairie in the national parks on the Eastern slope of the Rockies. The lazy American Indian tribal elders simply want to be paid a high rent for the land the wind turbines sit on, period. Do a little Googling or watch PBS to learn about reservations, the corruption, the fat pockets of the elders, the shacks that the average "tribesmen" live in, the total lack of productivity, the 70%+ unemployment rate, rampant alcoholism encouraged by the "haves" to keep the "have nots" sedated and agreeable, etc. There aren't enough population centers nearby to make a casino profitable in those lands, unlike other reservations in the region, so the "free income" sources for these tribes are much more limited. They want a payday, pure and simple.
We have 3 arrays of wind turbines in Atchison County, Missouri, a 72, a 24, and a 4. The first two feed grids and the 4 turbine site powers the city or Rock Port. There was a big effort here years ago to get these wind farms, for a few reasons:
1. JOBS--including initial construction (hundreds) and maintenance. Less than two dozen long term jobs were created but they pay very well in this rural area with a population of about 5,000 and a workforce of around 1,500. Most of the total population is retired/elderly.
2. Local economy boost during the 2+ year construction--hotel rooms for crews, restaurants, etc.
3. Property tax revenue on the rigs which is in the multiple thousands per rig per year even after the "tax breaks" used to draw the operators
4. Land stipend (rent) to the farmers who gave easement, $5,000/year per turbine--some farmers have 20 units on their land--$100k/year
Note that the Indian elder did not mention JOBS at all, only easement rent, and curiously, nothing about tax revenue. Politicians are always about jobs for their constituents, and these elders are politicians by definition. They don't want jobs for their people, simply a fat payday, just like they currently have with the oil. At this point in the game, the Indians are simply attempting to generate sympathy in the press to drive up the payment amount down the road when they sign the papers.
I'm not a fan of Obama, but I agree with the counterproposal he used in the negotiation with bin Laden. You know, the proposal that was most likely 5.56 mm wide and delivered at about 3500 feet per second by a SEAL "negotiation team."
You might have the bullet diameter correct, but your velocity figure is way the fuck high, showing you're not a gun guy, and should thus leave responses such as this to gun guys such as myself. :)
Many of these SEAL operators would have likely been carrying the M4A1 carbine. Muzzle velocity w/ M855/A1 ball, most likely what they loaded out with, is 2900 fps or less from the 14.5" barrel of this weapon, depending on altitude, temperature, humidity, etc. You're 600 fps high in this case.
Given that SEAL Team 6 has been dedicated to counter-terrorism operations since the unit was formed, and is often engaged in Close Quarters Battle, such as the bin Laden raid, some operators were likely carrying the MP5N or MP5SD submachine gun instead of the M4A1 carbine. Muzzle velocity of these two MP5 variants is 1300 fps. If one of these meat eaters popped bin Laden the bullet diameter would have been 9mm, and your velocity would have been high by an whopping 2200 fps, just shy of triple the actual projectile velocity.
Of all the stupid features from Chrome to pick up, the version numbers is, by far, the dumbest. Has anyone considered how stupid a version number in the high double digits might be? Firefox 81 seems kind of clunky, doesn't it?
Yes, it does. However, "Firefox 451", "Firefox 666", and "Firefox 911" (as in Porsche, not terrorism) seem kinda catchy to me, so maybe they should skip double digits and go straight to triple.
Do we forget about Sanford Wallace so soon?
Or Jeremy Jaynes?
Use authenticated smtp - its at port 584
Of course, the server to server communication all runs on 25 still..
You're thinking of 587, which is for MUA submission. This is not for server to server SMTP communication. This will not help the OP.
A lot of companies offer static ips for which you can set all the reverse dns & email information, and they are also out of their normal subscriber pool, thus allowing you to send emails from the computer behind it. The cost of that option is usually lower than 5$ per ip per month around here.
It's $10/month extra for a single static IP atop aDSL from CenturyTel here in rural Northwest Missouri. They have a local monopoly but so far their pricing is reasonable and the service is top notch--not a single outage in the past year. CenturyTel doesn't offer custom rDNS, period, neither for small business nor residential accounts. So far this hasn't been a problem. No reputable DNSBL will list an IP strictly due to generic rDNS. And CenturyTel doesn't register the parent block with the Spamhaus PBL nor any other "DUL" type DNSBLS. Neither my IP nor parent net have been listed by any reputable DNSBL. I noticed the parent net was listed on, IIRC, one of the super aggressive fiveten lists some time ago, but that didn't obviously affect delivery as nobody in their right mind outright blocks using these fiveten lists. I registered my IP with dnswl.org quite some time ago and have a 'medium' rating, which helps with delivery in cases where receivers do block based on things like generic rDNS.
221.216.41.65.list.dnswl.org. 43200 IN A 127.0.6.2
So far I've had zero problems with outbound delivery over this CenturyTel aDSL. Having a static IP is more important for deliverability than custom rDNS, but it's good to have both if you can get them. If you have static IPs and are being listed in "policy" DNSBLs, you need to talk to your ISPs and get that straightened out. If you have static IPs and you're being listed by trap driven DNSBLs, then the problem isn't with "what type of service you have" but with spam emission from zombie infected PCs behind your NAT. In this case YOU need to egress filter TCP 25 so nothing can send outbound SMTP but your mail server.
Maybe yes, maybe no. The big loser in this would be Intel. I'm not sure of the % of Dell computers that ship with AMD CPU's but it's certainly less than 25%. Dell is big enough to hurt Intel if they switch to AMD.
Which is why this "story" is purely rumor. This is simply a move by Dell to get _much_ better pricing out of Intel. Dell has no intention of actually buying AMD. They wouldn't know how to run the combined company if they did. Look at Dell's roots. Dell is a build-to-order firm, not a bottom-to-top manufacturing company.
Just wait until "ipv6 conversion specialists" are charging you $450 an hour to make sure your business is not floundering because you ignored the problem until it was an emergency.
Would you mind describing such an "emergency" situation, in detail? The only "emergency" scenario I can think of here is if your ISP/upstream dictated that within, say 90 days, they would no longer route your IPv4 traffic. The flaw in assuming such a scenario is that no ISP/upstream has a positive financial stake in doing this. They gain nothing by taking away your IPv4 abilities. In addition, if said ISP/upstream really was determined to do this, they'd simply send out an engy to install a v6/v4 gateway router. Problem solved, no material change for the customer. Note this last point carefully, because this is what the US "IPv6 conversion" will look like at almost all organizations, and most orgs worldwide with a substantial v4 installed base.
Note the U.S. government for example, and it's millions of v4 devices. If they started a wholesale conversion to v6 tomorrow, how many years, and how many 10s of billions of dollars would be consumed before the project is completed?
The people screaming like Henny Penny have no clue what kind of costs are involved in such a conversion to v6. And apparently they don't realize that most organizations that actually need large blocks of public addresses already have more than they need. Look at all the /8s assigned to US government agencies, US corporations, US carriers, the UK government, etc. If one isn't in any danger of ever exhausting one's supply of v4 addresses, what financial motivation is there to change to v6? There is none.
To make more addresses available for new users (China, worldwide wireless phone carriers), what the IETF should have done before creating this new whiz-bang v6 stack is to convert the multicast and "future use" subnets (no one uses multicast anyway) to standard subnets. Changing all the v4 stacks to recognize these subnets as normal routable nets would yield an additional 536,870,912 usable addresses, and would be a much easier change to implement--would be a simple patch to all existing v4 stacks. For devices such as network printers et al inside the perimeter, one wouldn't even need to change the firmware.
That's called a feedback loop, or FBL. These have been around a long time. Most ISPs and gorilla mailers have been using them for many years. They aren't a magic bullet against spam--far from it. An FBL is simply analogous to walking over to your neighbor's house and telling him his son just threw a rock through your window. The dad isn't able to keep tabs on his kid all the time. Same with an ISP, freemailer, or in this case, Amazon. The FBL is simply an extra set of eyes and ears.
Grötschel, an expert in optimization, observes that a benchmark production planning model solved
using linear programming would have taken 82 years to solve in 1988, using the computers and the linear
programming algorithms of the day. Fifteen years later – in 2003 – this same model could be solved in
roughly 1 minute, an improvement by a factor of roughly 43 million. Of this, a factor of roughly 1,000 was
due to increased processor speed, whereas a factor of roughly 43,000 was due to improvements in algo-
rithms! Grötschel also cites an algorithmic improvement of roughly 30,000 for mixed integer programming
between 1991 and 2008.
The prof is fibbing. The gains are mostly in the big on-die L2 cache with its fat, core clocked dedicated backside bus (thanks to Intergraph, and Intel for stealing it from them, then AMD, IBM, et al). The prof simply shrunk the code and data set to fit (mostly or wholly) in the 512KB/1MB cache of their 2003 era Athlon XP/Pentium IV. As with most apps, it's all in the ca$he baby, all in the ca$he.
SMTP needs a ground up re-write, and it will need it just as much (if not more) after IPV6 is deployed.
SMTP isn't the problem and is not in need of a ground up rewrite. The problem is social, between spammers and suckers, their victims. As has been shown via NNTP, instant messaging, and Facebook spam et al, there is no technology immune to spam. Spam will be with us as long as suckers exist, and there are people willing to exploit those suckers. Yes, basically for eternity.
There will start to be IPv6 dnsbls and mail OPs will start keeping IPv6 local block lists. It's the same old game with a new numbering scheme. As for multilayer NAT I don't see it being a problem WRT SMTP. As others have stated it will be relegated to consumer broadband ISP space and possibly colocation centers, which most mail OPs already outright SMTP block (if they're smart).
1: it's a dick-wagging contest to have the best supercomputer in the world..
Absolutely correct. This was clearly demonstrated by the accelerated funding and freebie process that occurred when NASA was building its first SGI Altix monster, including emergency meetings with the Governor or California's office, the DOE directors office, Intel, and SGI. The build of that machine would have normally taken a year using the normal method of assembly, construction, and testing. They cut it to less than six months with one goal in mind, and it wasn't science. It was to get a sufficient number of Linpack runs in, and tune for a final couple of "peak" runs simply so they could send results to Dongarra before the deadline for the upcoming TOP 500 list.
They thought they were going to take the #1 spot, because they weren't paying attention to their "competition", which IIRC included the first BlueGene machine from IBM (which took the #1 spot on that list). The NASA "Columbia" Altix supercomputer ended up at #3 on that list. Intel and SGI lost a *bunch* of money on that system just to get the #1 spot on the list. And they didn't. Meaning they lost all that money for nothing. For Intel this didn't mean much. For SGI, well, we all know Rackable bought them for only $45 million--less than the price of the Columbia machine. This wasn't the first "deeply discounted" system SGI shipped, and when you add up all these deals, you understand their near bankruptcy situation, and sale for a song to Rackable. That was a very sad deal...
i cannot believe that IBM or other U.S. vendors instead of Sony would not have been capable of crafting such a system... quite telling, IMO
They have, almost 5 years ago, actually. You are simply uninformed, haven't been paying attention:
http://www-03.ibm.com/press/us/en/pressrelease/19198.wss
http://www-03.ibm.com/systems/bladecenter/hardware/servers/qs22/index.html
And the IBM Cell blade has a Cell chip, the PowerXCell 8i, with 1 extra SPE, 5 times the double precision floating point performance, and with the Infiniband HCA, over 50 times faster network communications.
Where have you been these past 5 years? :-)
RoadRunner, http://www.lanl.gov/discover/roadrunner_fastest_computer
has over 13,000 PowerXCell 8i chips which are 4 times faster than the PS3 Cell chip on FP code. RR executes Linpack at 1.04 PetaFLOPS/s, just over double what AFRL is claiming for their little bullshit 1760 Cell cluster. If AFRL is quoting PEAK hardware performance, their 1760 PS3s would hit a mere 180 TFLOPS/s, far short of that 500 figure. The head nodes they mention would add another 10 TFLOPS/s peak. They didn't specify the number and type of GPUs in the cluster. Even so, they're still not going to hit 500 TFLOPS/s, nowhere close to it running any application, and not close to it if quoting PEAK hardware numbers.
Those Air Force boys must be smoking some good weed these days to hallucinate that 500 TFLOPS/s figure.
Regardless of what you install there's no guaranteed way to stop your kid from stumbling upon boobs on the internet. Plus who's to say it's something to worry about at all. They certainly didn't traumatize me.
What happens when the kid has already turned off Google Safe Search, then searches for "rooster" as they discussed chickens and roosters in class that day, at age 5. Rooster gives "cock" as a synonym, so he searches "cock". Then he hits the images button. Some of what he sees _will_ be traumatizing and will prompt questions to the parents. This is a far cry from coming across an issue of Playboy and seeing boobs as you and I did as youngsters. Google and the web are a game changer here and the potential for trauma is high, as well as other consequences.
all the Candian jokes are nice and all.. but this really was about trying to make people think CERN is the only thing going on in HEP or nuclear physics. Not so, and this is not a first as RHIC was there first. Glad to see CERN is catching up though.
I thought the big deal with the LHC is that it was supposed to give us the Higgs Boson, as no other collider on earth was powerful enough to create the Higgs. Enough about this QGP junk. Where's our Higgs Boson?
If your SAN array(s) are of any size (10TB+) with lots of drives (8 or more) you should take another look at XFS. The version of RHEL you were using is eons old now, shipped with kernel 2.6.18 from 2003, and probably didn't have the 2007 fixes. Also, if you were running your / filesystem on XFS, that's not recommended, because most Linux distros don't have the right integration for doing so, as you learned. Run / on EXT2/3 and your data filesystems on XFS. / filesystems aren't write transaction heavy, and don't experience lots of random IO, merely log writes, so you get zero benefit from XFS, and you can experience integration headaches, depending on your distro.
XFS is currently the most heavily developed FS on the planet, more than BTRFS. It also has superior performance to all other filesystems with almost every workload. Even more so with the recent delay log option. When configured and managed properly, it is also one of the most robust filesystems available. It is very widely deployed, especially on massive DB servers, due to its superior performance with O_DIRECT.
If you had corruption issues, not merely trunc'd files, in the past two years, then you were running an OS without the 2007 patch.
What if you sucked 10,000 cocks per second?
.. then you would have a 10KHz CPU (cock processing unit).
Not necessarily. If this were a superscalar cock processing unit, with say, 2 cock processing pipelines, 2 cocks could be processed per cycle. In this case, a 5KHz superscalar cock processing unit could process 10,000 cocks in one second. Cock processing is all about efficiency.
Wrong answer. XFS is extremely prone to data corruption if the system goes down uncleanly for any reason. We may strive for nine nines, but stuff still happens. A power failure on a large XFS volume is almost guaranteed to lead to truncated files and general lost data. Not so on ZFS.
You are just full of misinformation. Sudden downing of any _busy_ system due to power loss or panic is going to lead to data loss due to the buffer cache in Linux, and other factors. Full stop. Data loss != data corruption. XFS is absolutely not prone to "data corruption" under any circumstances. If you pull the plug on any system running any filesystem, you _will_ get truncated files and loss of data. This is not a function of the filesystem per se, but of the Linux buffer cache, and any write caches on the RAID card and/or disk drives themselves. Write all of your applications to fsync and the truncation after power loss problem will be less severe, but your performance will suck horribly. Again, this is equal for _all_ filesystems, not just XFS.
Maximum performance and maximum data integrity have always been mutually exclusive, and always will be. XFS kicks the crap out of all comers in write performance with delayed logging enabled. This means more data is held in RAM before flushing, more so than with the standard config, optimizing data transfer throughput and placement on disk decreasing fragmentation. Yes, this comes at a cost: If power drops, everything pending in the write buffer gets lost. This is why (real) datacenters are designed with many large and redundant UPSs and generators. However, again, data loss != data corruption. You claim above that XFS is prone to data corruption. That is horse shit.
Don't spread FUD. You don't use XFS, or at least any remotely recent (2007 on) version of it, so you don't really have a clue. And you obviously don't have an understanding of the function of the Linux VFS system and the buffer cache. As I stated, _any_ filesystem will suffer truncation and data loss if a busy system loses power when many writes are pending. If your apps make heavy use of fsync, you won't suffer as many truncations, but you will still have them occur, with ZFS, EXTx, BTRFS, etc. It _will_ happen with all of these. The only difference will be the severity, depending on how many write transactions were in flight at the time the plug was pulled.
I'm anxious to see you claim again, in your response to my points above, that ZFS is immune to truncation due to power loss. The only way this is possible is by disabling all caching, on the disk drives and controllers up through the entire software stack on the host, and using only applications that call fsync on every write operation. If this was actually done by anyone, disk write performance would drop to the point the system would be unusable. And this still wouldn't guarantee you wouldn't have a single file in the write buffer that gets truncated.
The OS has also been future-proofed, in the view of the Red Hat executives. It can support up to 16 terabytes of working memory, even though no physical system could now actually run that much memory under a single server.
http://www.sgi.com/products/servers/altix/4000/
"SGI Altix 4700 incorporates the shared-memory NUMAflex® architecture, which simplifies software development, workload management and system administration. It supports up to 1024 cores under one instance of Linux and as much as 128TB of globally shared memory."
http://www.sgi.com/products/servers/altix/uv/
"Altix® UV scales to extraordinary levels-up to 2,048 cores (256 sockets) with architectural support to 262,144 cores (32,768 sockets). Support for up to 16TB of global shared memory in a single system image, enables Altix UV to remain highly efficient at scale for applications ranging from in-memory databases, to a diverse set of data and compute-intensive HPC applications."
"This infrastructure is supported by a complete HPC solution stack running on industry standard Linux® operating systems with the choice of Novell® SUSE Linux Enterprise Server or Red Hat® Enterprise Linux® Advanced Server operating systems."
Someone didn't do his research before spouting off. This is odd considering he simply regurgitated the information Red Hat fed him. I guess the press guy at Red Hat didn't know they already had their OS running on 16TB capable SGI monsters?
Try bribing a policeman - a large percentage of the time, you'll end up in jail.
Apparently you're not from New Orleans, where you only go to jail if you don't/can't pay a bribe. Their drug unit took over the city's drug trade via forced bribes, if you will, forcing dealers to give up their business to cops to avoid arrest/jail time. At least, that's the way it used to be. The FBI crackdown some years ago may have cleaned the NOPD up just in time for Katrina.
.30-06 ought to do it.
Other than that, not really, no.
I politely beg to differ haus. The .308 or .270 would both do a fine job here as well. Heck, we're talking about a puny pencil neck lawyer judge, right? One could easily and cost effectively purchase a .25 Jennings automatic in the North end of just about any U.S. city that would do the job, albeit at close range, and most of 'em already have the serial numbers filed off ta boot. Rich Texas judges usually live in two story white mansions with lots of shubbery, especially line'n the driveway--good hide'n spot for deploy'n that .25 Jennings auto and make'n a safe getaway. Silencers for 'em are pretty cheap, or you can easily make one yourself, being a country boy like me.
Say, uh, Slashdot don't log them there IP address thingies when people post, do they? If they do, umm, damn, uh.. I' never really done nut'n like 'at. I' just got a good imagination, folks tell me.
So what. I am a Canadian and I use the American spelling rules like 'center' and 'color'. There is likely Americans down south who like to use British spelling conventions too even though they are American.
...and then there are the idiots all over the world who believe sticking "an" in front of words starting with hard consonants makes them...something. What? Smart? European? What? Who the fuck was taught in grade school or high school English class that you say "That is an chicken sitting on an egg."? It's not "an" chicken sitting on an egg it is "a" chicken sitting on an egg.
The English article "an" is to be used only in front of words beginning with vowel sounds when spoken verbally, such as "an honest politician" or "an English gentleman" or "an asshole!". The article "a" is to be used in front of words beginning with a hard consonant sound when spoken verbally, such as "she is a beautiful woman" or "is that a cocker spaniel pissing on your shoe?" or "you're a fucking jerk".
If one is using "an" in front of consonant words as some kind of post internet age form of "emphasis" I suggest it only makes one look goofy, uneducated, or striving too hard for some odd kind of attention. I still haven't figured out where this FUBAR'd execution of this English language article started. Was it Europe or here in the US? Or?
People I know personally, who know how to use this English article properly, have started using "an" in front of consonant words in print (emails) but never do it while speaking verbally through their lips. If I was sufficiently creatively inclined I'd put together a cartoon parody of this and stick it on YouTube to shame people into dropping this stupid plague that has sprung up all over the web.
THe problem is thus not the court settlements but potential political ones.
No, the real problem is stupid Americans who allowed the fucking cell phone to become a status symbol. Recall the Motorola Razor? Same phenomenon as the iPhone but you didn't have Motorola Zealots in the purchasing crowd like with the Apple Zealots. I know 10 people who bought iPhones. One, only one, actually uses the features that would possibly justify the purchase. The other 9 bought it as a status symbol because they could afford it. Actually 3 really couldn't afford it but bought anyway. And these 3 are totally leveraged to hilt with big mortgage, car note, maxed credit cards, etc etc. They just had to have the iPhone to keep up with the Joneses.
Cell phones have ruined our social discourse in many ways. I got so fed up with the status symbol crap and having a cell glued to my ear that I canceled my contract one day 3 years ago and chucked the phone in the can. I regained aspects of my life that I'd forgotten I once had. I've since bought a prepaid phone that stays in the car for emergency use only, and I went back to carrying a pager, again, for emergencies only, whether family or business.
The freedom of no longer having to plug my head into and electronic gizmo 20 times a day can't be sufficiently described in words. I got life back, or at least most of it.
It's not about the guy that was executed, it was about an official, and extremely serious and somber statement, made via what many consider the lowest form of communication.
What if you had a wedding, and the bridal march was done by some guys farting, or your Masters Degree was on a post-it note?
Some forms of communication are just not considered to be appropriate for some types of information.
The announcement of this murderer's execution should be nothing more than a recording of the gun shots and the dirt hitting the box sent to the media.