Intelligence should never be a requirement for a Friday before a 3 day
weekend.  The only thing I should have to think about is whether I'll have
enough beer and burgers to make it through the weekend.  :-)



On Fri, May 22, 2009 at 8:18 AM, Jonathan Link <jonathan.l...@gmail.com>wrote:

> If it were simple we wouldn't need to have the discussion, and you wouldn't
> need to possess intelligence on a Friday. :-)
>
>
> On Fri, May 22, 2009 at 7:57 AM, Rob Bonfiglio <robbonfig...@gmail.com>wrote:
>
>> It's too early to get that intelligent on a Friday!  I think I need a few
>> drinks now. :-P
>>
>>  On Thu, May 21, 2009 at 8:52 PM, Ben Scott <mailvor...@gmail.com> wrote:
>>
>>>  This just came across the patch management list.  It's highly
>>> informative and useful, so I thought I'd re-post here.  Thanks to
>>> Susan "The SBS Diva" Bradley for the link (and many other useful ones
>>> in the past).  It explains Microsoft's update release methodology and
>>> nomenclature, including all those TLAs like RTM, GDR, LDR, QFE, etc.
>>>
>>> http://blogs.technet.com/mrsnrub/archive/2009/05/14/gdr-qfe-ldr-wth.aspx
>>>
>>>  Of particular interest to me is the statement that $NtUninstallKB
>>> folders are used for more than just uninstall.  They reportedly
>>> contain all the possible versions of a file that might be needed to
>>> support *future* updates.  I thought that's what $hf_mig$ was supposed
>>> to be for?
>>>
>>>  I have to say... while I really appreciate someone taking the time
>>> to write all that up, I don't think I've ever seen a better
>>> illustration as to just how Byzantine Microsoft's release practices
>>> are.  Anything that confusing is not a good design, as far as I'm
>>> concerned.  :-(
>>>
>>> -- Ben
>>>
>>> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
>>> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>>>
>>
>>
>>
>>
>>
>>
>
>
>
>
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to