Although I haven't changed my mind ingeneral, I think that there are arguments for configuration managementsystems like Cfengine and Puppet over packaging systems. Apart fromtheir actual existence in usable form, one of them is that CM systemsare going to be inherently more agile than packaging systems.
The drawback of packaging systems is that they fundamentally work onpackages. This means that doing things via them requires a multi-stepprocess; you must assemble your files, build one or more packages fromthem, and finally propagate
Here is a thesis about network computing's lack of success:
The compute power to deliver your applications has to live somewhere,whether that is in the machine in front of you or on a server that sitsin a machine room somewhere. It turns out that the cost of deliveringcompute power in one box does not scale linearly; at various points, itturns up sharply. For various reasons, there is also a minimum amount ofcomputing power that gets delivered in boxes; it is generally impossibleto obtain a
最近什麼都不想寫
最近終於買了他們的新碟
非常簡單但又非常厲害
這一次他們連社會主義的幽靈都請出來了
非常貼合現在的氣氛呢
Discussions about Solaris often wind up bringing up OpenSolaris (andsometimes it crops up in other contexts). However, I do not findOpenSolaris particularly interesting.
My view is that right now, OpenSolaris is essentially a technologydemonstrator. You can't use OpenSolaris by itself, because it lackssufficient support to use it directly and sufficient genuine opennessfor sensible people to base stable things on it. You can't use it as thefuture of Solaris, because I'm not aware of any commitment from Sun that
Protection for Gangs, Clubs and Nations Causing Grief In Human Relations It’s A Turf War On A Global Scale I’d Rather Hear Both Sides Of The Tale See, It’s Not About Races Just Places Faces Where Your Blood Comes From Is Where Your Space Is I’ve Seen The Bright Get Duller I’m Not Going To Spend My Life Being A Color
~from Michael Jackson’s “Black or White”
高鐵熱燙燙，我的網圈內大都是反對
Some brief followups from my first entry on this.
First, the mismatch_cnt numbers are reset from scratch everytime you re-run a check (and probably every time there is a mirrorresync). On many current systems, this means that they will be resetevery week. This makes sense and is even implied by the documentation (in the usual Unixfashion of reading between the lines),but it would have been nice to have it explicitly documented.
(I'm aware that I'm