you mustn't understand how companies deal with their capital expenditures, and replacement costs of infrastructure.

a company is going to replace network gear typically every 5 years or so. same company may replace servers every 3 years depending on need/workload.
those replacements are typically spelled out 6 months prior to the year in which they are replaced, and the new cost is put into the capex. capex goes through approvals, and typically gets a nice little chop because IT wants to add/replace too much. capex goes back to IT Director, who plays with the numbers, removes a few upgrades, sends capex upward for approval.

once approved, engineers are going to replace gear that will benefit the organization for the next 3 to 5 years, where the cycle will repeat itself. and because the spend is kept artificially low, only the most deserving pieces get the money.

why would engineers think to deal with IPv6 if IPv4 is not a real pressing issue when upgrading? the pressing issue is going to be the pressure to lower latency, remove bottlenecks, and scale bandwidth. when your boss(es) are breathing down your neck because you dropped 500K on some new gear, the last thing you're thinking about is solving the internet's (someone else's) problems.

well .. admittedly 'IBM Solaris' sounds worse -- we're left with the lesser of two evils I guess.
 

yes, too big for RHEL. Running RHEL on RISC = dumb. Running Solaris on RISC/SPARC (read M4000/M5000) = bankable.

IANAL.

my my - more AC BS.

when you require actual performance from your storage (in the environs of 6k-10k+ iops), please come back with some money in your hand.

  -- IT Management

While people are buying $250,000 NetApp installations, the exact same hardware, performance and connectivity will go for $5000 of high-end hardware and a couple of hours work with ZFS

lies. having worked in this industry for far too long, when I see bullshit claims like this, I have to call it. There is no way in hell you will get multiple trays of 15k rpm FCAL storage and redudant FAS controllers for 5k, I dont care if you're Samuel Jackson in the negotiator.

I run multiple datacenters with emc, hp and netapp filers -- if you pay 250k for a netapp installation, you're pretty much getting what you pay for. what you're paying for is IOPS, disk caching, and throughput. You can turn to just about any storage provider, you will pay the same price for similar enterprise grade hardware. All I ask is that when you're stringing your two cans together, you leave out the reference to how alike it is to a 'real enterprise grade' product -- because talking about petabytes of SATA isn't even in the same continent, let alone the same country.

the funniest part is that you 're-used' the Solaris installer for your funny post. I wonder if it was keyboard-only driven.

Well, that's a little bit like saying, "I lost a quarter over there by the wall, but I'm searching here because it's got better lighting"

There was this time period, way back when, when a couple guys with names like Kepler and Galileo, decided to look at planetary motion in a different light, taking it from a 'different angle' of the hows/whys celestial bodies would appear to spin in the night sky. maybe I'm off base, but sounds pretty much like someone looking at this in a different light, proposing a different theory that lines up with the cosmos.

lots and lots of suggestions -- and i may have missed it above - but just cut an image of the system, in a ready to use state. use that ghost thing, bam bam, youre done. next time moron get system all bitched, wipe it clean in about 10 minutes.

people, people, people. I watched 'Contact' last night. I say we just build a whirly thingy (x2, in case some crazy lunatic with a creepy stare blows one up) and worm hole it everywhere, like to Vega. Profit!

this is such a nebulous question. you want your dev/qa/pre-prod to emulate your production environment as much as possible. this subject in itself could fill a book on best practices, techniques, and the like. Easiest said by saying: keep all developed code separate from 3rd party application code. packages/versioning/repositories are a good start. make things relocatable, have one installer, and have it take multiple environmental variables. ie - make environment variables 'run time', don't make the same mistake everyone makes - and make them 'build-time'.

Best of Luck.

the skillz market for hacking phones just went up again. when will these music industries/RIAJ/RIAA/etc ever learn from Amazon/Ebay/etc? Its all about customer experience. This may be the same reason why top100 music generally licks balls.
my 2 cents.

likely responded to this, and so shall I.

as part of the scm world -- i like to be true to a real dotted quad notation when referring to build versions. i've never really built code that is deployed to the public world .. only code used on company production servers for public consumption (mostly java based web sites, and middleware)

1.2.3.4 = Major level 1, Minor level 2, Patch 3, Build 4.

Major = major release. no longer compatible with previous versions.
Minor = minor release, still compatible with previous versions (with same Major)
Patch = the number of patch builds required to get to latest production patched code
Build = the daily build number. increments by 1 until dev/qa is complete, and code is released to Staging servers.

build numbers stop, once patching starts. the patching denotes the patch to last known good build.

ie -- dev/qa releases should always be num.num.zero,buildnum. (1.2.0.40)
once released to staging - and if a patch is required -- the rev increments as such for the first patch - 1.2.1.40. second patch 1.2.2.40, and so on.
once in production -- wait until next release.

if code is released to the public, and not running on a company's servers -- always drop the build number. so, if you're delivering 1.2.2.40 binaries to the public, cut it down to 1.2.2 and deliver your rpm/pkg/deb, etc to the world.

if this confuses you, im available for hire at your location. references available upon request. :p

yep, and mod this parent up, as 'correct' (while modding this post down as uninformative .. hehe)

sorry dude -- and not to downplay what the original post is about...but i played JK2, and the rest of the game sucked ass. The only decent part *was* the sabering .. so, playing on a server where getting into duels was pretty much the best part. If you honestly wanted to shoot a guy (who happened to be running around with a saber) with a pistol .. it turned into the proverbial 'knife to a gun fight'. saberists didnt stand a chance .. and it ruined the game so to speak. infact, it just turned the coolness of having a saber into unreal tournament without the headshots.

and who wanted that?