Screws In My Coffee

Instead of complaining about how I use to be able to run, I decided to start running again on March 31, 2010.  After two months of walking and running almost every other day I ran 10 miles last night in 1 hour and 47 minutes.  I finished the last two miles running fast and strong. I am going to run my first race in Georgia, it is a short 5K race, Loop the Lake . I have not done a 5k race since 2005 when I started running for the second time in my life. So running when it is hot, humid and raining has been an inspiration. Breaking the barrier of one hour of running without stopping last week gave me the will power to run 10 miles. I have run this far before, so I am not breaking new ground, but it is harder than I thought to remain inspried to run when I know I am not in the best shape.  I am working towards some local short distance runs and I am inspired that after two months of steady running I can run 10 miles. Training for a marathon in March 2011 or the Rouge Orleans 100 mile run ...

The Bandera trail run is just around the corner.

The Outlook Live infrastructure is already federated with Microsoft Federation Gateway. All you need to do to enable federated sharing is create a new organizational relationship with another Outlook Live domain. Before you begin Federated sharing uses the autodiscover information in your domain to configure the federated relationship. You must make sure that both your organization and the partner organization have the CNAME autodiscover record configured in DNS. See Use a CNAME Record to Enable Outlook 2007 to Connect to Outlook Live . Use Windows PowerShell to configure federated sharing in Outlook Live. 1. Connect Windows PowerShell to Outlook Live . 2. Run the following command to enable free/busy sharing between two Outlook Live organizations: Get-FederationInformation –DomainName <the other tenant domain> | New-OrganizationRelationship -Name <the other tenant domain> -FreeBusyAccessEnabled $true -FreeBusyAccessLevel LimitedDetails Here's an example of what the c...

After proving once again that insanity is if doing the same thing over and over and expecting different results, I am relieved that I finally have an operating system on the old HP DL380 G3. FreeBSD is always a good choice for difficult hardware.

Since I can not get CentOS 5.4 installed on the HP DL380 G3 I am considering using my old freind FreeBSD.  the problem with the HP server is Grub.  the old server BIOS does not let Grub work as a boot loader.  Lilo on the other hand may work.  I will attempt a FreeBSD install with Lilo as te boot loader. Quoted from http://news.netcraft.com/archives/2009/06/02/most_reliable_hosting_company_sites_in_may_2009.html : Most Reliable Hosting Company Sites in May 2009 - Netcraft Most Reliable Hosting Company Sites in May 2009 cellspacing="0" cellpadding="2"> Rank Company site OS Outage hh:mm:ss Failed Req% DNS Connect First byte Total 1 New York Internet FreeBSD    0.000  href="http://uptime.netcraft.com/perf/graph?tn=may_2009&collector=11,14,20,21,23,25,28&site=www.nyi.net&range=2678399&sample=9&sd=1241136024">0.266 href="http://uptime.netcraft.com/p...

I have been searching for a way to get an old HP DL 380 G3 to boot CentOS 5.4.  It has problems with Grub.  I am going to try this solution. BTW this is my first post using Adobe Contribute. Quoted from http://www.hyper-linux.org/HP-HOWTO/current/hp-hardware.html : HP hardware supported by Linux DL 360/380 G3 To install/use these machines under redHat 7.3 or 9, you have to pass the following parameter on the command line at boot time ide=nodma. You may also use the following command in the file /etc/rc.local /sbin/hdparm -d0 /dev/hda If the fans of DL360 G3 machines do not have an acceptable noise level after the boot either you install the hpasm driver for your distribution, or you update the BIOS of your machine (2003-04-08 or upper) P31