This might not work for the OP, but for those of you living within 15 miles of your work, try cycling to work. I cycle 8 miles each way to my work and I have gotten in shape just by commuting to and from work.
This worked great at Rutgers. I gave all my roommates Linux LiveCDs, then the network detected that they had Linux and whitelisted them. They then rebooted back into Windows and were all set.
yum-updatesd in CentOS & Fedora and/etc/apt/apt.conf.d/50unattended-upgrades in Ubuntu are your friends.
If you configure these properly in combination with a local mirror, you can get it to deploy automatic updates seamlessly.
I am not sure what their rationale was but with YUM, it stores all the package metadata in xml files which are processed when you issue a yum command. However, this is slow and not as efficient as apt-get, which has a database of dependencies and such.
To me it seems like the best solution is a combination of both. If you use apt-get on top of RPM, the solution is a system that works great with dependency resolution and management, while making package building far simpler than with Debian Packaging.
Slashdot Mirror
This might not work for the OP, but for those of you living within 15 miles of your work, try cycling to work. I cycle 8 miles each way to my work and I have gotten in shape just by commuting to and from work.
This worked great at Rutgers. I gave all my roommates Linux LiveCDs, then the network detected that they had Linux and whitelisted them. They then rebooted back into Windows and were all set.
yum-updatesd in CentOS & Fedora and /etc/apt/apt.conf.d/50unattended-upgrades in Ubuntu are your friends.
If you configure these properly in combination with a local mirror, you can get it to deploy automatic updates seamlessly.
Try the Scalix (http://www.scalix.com) groupware suite. It is pretty decent and has an Outlook connector built into it.
I am not sure what their rationale was but with YUM, it stores all the package metadata in xml files which are processed when you issue a yum command. However, this is slow and not as efficient as apt-get, which has a database of dependencies and such.
To me it seems like the best solution is a combination of both. If you use apt-get on top of RPM, the solution is a system that works great with dependency resolution and management, while making package building far simpler than with Debian Packaging.