Aussie Blog Updates

Christian Longstaff's Blog — Fri, 25 Jan 2008 05:32:48 GMT

Andy Coates published the latest Aussie blogs Roger Lawrence (Sydney) - our new Group Manager, Developer

re: Fedora Core 6 install on Hyper-V

Carl.B — Tue, 08 Jan 2008 01:38:01 GMT

Hi Michael

Most distros are superseded in 6 months

major releases annually.

The patches add up in linux Distros very quickly since they don't/won't/can't get bundled together into Service Packs or single large packages.

An imposed rule on most software it is broken down to the smallest possible size and packaged as modules.

Since lots of different people/companies develop each module and they release updates at different intervals. A flaw in Mplayer Core can be patched quickly without needing to update all 7.

For example Windows Media Player and all functions are bundled in one package.

Sound Backend/Interface is integrated into windows Core Services?

However media players in Linux are divided into 7 Packages

Right here gives you a 7:1 requirement versus windows updates.

1. Core Player

2. Player Gui

3. Sound Daemon (backend)

4. Publicly free Codecs

5. Restricted/Proprietory Codecs

6. DMCA/Illegal Codecs

7. a package for each skin.

Picture Windows XP in the form of Fedora

*I remove/don't install Windows Media Player, Notepad and Terminal Services

*I install Powertoys XP and Windows Services for Unix

Will SP2 work optimally?

In Linux a Service Pack is not optimal since it will install WMP Notepad and Terminal Services despite user not approving.

I will still require extra packages for the remainder.

This shouldn't be an issue since we don't actually need to go to Fedora.com and navigate through three pages to download each of 264 the individual patches

(compare to fetching a KB file at downloads.microsoft.com)

WSUS will be far better if MS completely overhaul how they package their KB packages Maybe a MSI file or other binary package

with a header to define what

*package title

*version number

*Operating System

*Platform(x86 x64)

*dependancies Package title and version

and obvisously a front end to decide

Does this package belong on this OS?

Does this package belong on this platform?

Is this package version number newer than the existing %package%?

Are other package i require already installed?

Are other packages i require in current directory?

Are other packages i require in define internet repository?

Unlike WSUS as you would have noticed the software Update mechanism methodolgy in most Linux distros is very mature, stable and flexible.

In some distros those 264 updates you downloaded you can share that folder on Samba or NFS and use it as an update server for all like machines.

i can use \\mkleef\updates as my source instead of http://update.server.com

I really wish WSUS was that simple.

Current WSUS that has been developed

was just too over thought, overly complicated and demanding on the central server.

re: Fedora Core 6 install on Hyper-V

Michael Kleef [AppSense] — Mon, 07 Jan 2008 12:33:13 GMT

Hmm - I thought it was pretty recent. Shows how much Linux stuff I play with :) That said October 2006 was only 18 months or so ago. Dont you think 264 updates in 18 months is still pretty excessive?? Id hate to be patching that all the time...especially with a lack of good enterprise patch management and policy control tools? Unless of course you can educate me on what tools there are for Linux to do enterprise patch management?? :)

FWIW - I believe Google even have their own software and policy distribution??

re: Fedora Core 6 install on Hyper-V

Lindsey — Mon, 07 Jan 2008 00:59:15 GMT

264 updates is a lot, but there have been two other releases (core 7 and 8) since Core 6 was released in October 06. In Linux terms, I guess it's a pretty old release :)

Geek Lectures - Things geeks should know about » Blog Archive » Fedora Core 6 install on Hyper-V

Sun, 06 Jan 2008 06:31:23 GMT

PingBack from http://geeklectures.info/2008/01/05/fedora-core-6-install-on-hyper-v/