...won't somebody help me chase those bad docs away.
As I recently mumbled on twitter (sorry, but 'tweet' is even naffer than the bad title of this post) I've started poking at Yum around the edges. Partially as I'm trying to find a 'Better Way' than the groupinstall we have to do for 64/32 bit package co-existence on the current middleware, but also as I'm narked off at the complete lack of manpages (on SL5) for yum-utils.
actually, thats a bit harsh - as of 1.1.16 (el5) there are minimal docs, including yaim-utils.1 but nothing for each individual utility (see also http://yum.baseurl.org/wiki/YumUtils/RepoDiff). So, once again I'd ideally like something that can parse wiki markup and give me the output without having to keep pasting into a test page and hitting preview.
Anyway, 1st patch sent off for approval, but my home server has dropped off the net so no more updates for the day.
[obligatory swiss status report]
Hot. :-) Sunflowers are blooming. nice n fresh in the evenings with thunderstorms. Sadly not had a chance to see if my shiny new camera can catch lightning, but I'm reasonably impressed with the highspeed capture. see sample
$dayjob uses statuspage.io for our public status page . Although I've got some things automated, there's still a bunch of compon...
At home we have a small (2.5KW - 10*250w panels) PV system to try and offset our daytime electricity usage. This is connected to a 'Grow...
During the trials of concerto at CERN, I wanted to make the text fields a bit more dynamic like say following a specific twitter feed. Thi...
'things that go bump in the tunnel' As I've beem following the LHC restart I've written a parser for the vistar status fee...