Don't forget the time spent in verifying that the only machine affected was the web server, finding out how they got in, fixing that hole, writing up reports to go to upper management, etc...
It's time I'd rather spend playing quake thank you very much.:)
Debian has the ability to do auto-updates based on security fixes only. security.debian.org stores only security updates for packages in the current stable release. This is perfect for companies that only want to run stable software and yet want security updates. All of these updates can be automated even so that there is no need for someone to even be there.
Companies definatly do not want to mess with updating package after package. The biggest problems with all of this is that there are a ton of different programs out there in the opensource arena to use to make life easier. It all depends on what you know and use. The majority of talk here is of RedHat...but not everyone uses RedHat. At my company we have chose Debian since it's better (In our opinion mind you) for a server operating system. It allows us to easily maintain packages and keep them up to date without the worry of...man I have to update how many???...it's all done automatically. We even maintain a set of our own packages for internal use...this allows us to keep all of our internal software up to date just as easily.
This problem exists in more than just the Linux arena..Solaris has tons of minor packages that they release as updates but they also supply one huge package as well.
By far Linux has the ability to deal with security fixes the best. RedHat has alot of goals that they are trying to acomplish and in time they will meet them all. (or come close)...If you want this type of functionality go with a distribution that's designed for it.
deb http://ruins.tdyc.com potato kde deb http://ruins.tdyc.com slink kde (hopefully my ISP won't kill me):) Just kde 1.1.2 currently until the new home for kde.tdyc.com is up
hehe...okok... kde.tdyc.com = yuma.tdyc.com = horde.tdyc.com =....(too many names):) I've beaten the crap out of that machine and the ISP doesn't love me anymore. and I screwed up the Packages.gz files on the kde site. I need to get those fixed.
Slashdot Mirror
Don't forget the time spent in verifying that
:)
the only machine affected was the web server,
finding out how they got in, fixing that hole,
writing up reports to go to upper management,
etc...
It's time I'd rather spend playing quake thank
you very much.
Debian has the ability to do auto-updates based
on security fixes only. security.debian.org stores only security updates for packages in
the current stable release. This is perfect for
companies that only want to run stable software and yet want security updates. All of these updates can be automated even so that there is no
need for someone to even be there.
Companies definatly do not want to mess with updating package after package. The biggest problems with all of this is that there are a ton of different programs out there in the opensource arena to use to make life easier. It all depends on what you know and use. The majority of talk here is of RedHat...but not everyone uses RedHat. At my company we have chose Debian since it's better (In our opinion mind you) for a server operating system. It allows us to easily maintain packages and keep them up to date without the worry of...man I have to update how many???...it's all done automatically. We even maintain a set of our own packages for internal use...this allows us to keep all of our internal software up to date just as easily.
This problem exists in more than just the Linux arena..Solaris has tons of minor packages that they release as updates but they also supply one huge package as well.
By far Linux has the ability to deal with security fixes the best. RedHat has alot of goals that they are trying to acomplish and in time they will meet them all. (or come close)...If you want this type of functionality go with a distribution that's designed for it.
If this was true then they wouldn't have did their
demo at the Linux Expo's and all...
I think this is more along the lines of them used
to a certain way of doing things...plus their
lawyers are probably freaking out over all of this.
There is no need to keep beating up on them...they could always just say screw this and dump it. Who's loss would that be??? ours.
friggen html...ack
deb http://ruins.tdyc.com potato kde
deb http://ruins.tdyc.com slink kde
deb http://ruins.tdyc.com potato kde deb http://ruins.tdyc.com slink kde (hopefully my ISP won't kill me) :) Just kde 1.1.2 currently until the new home for kde.tdyc.com is up
hehe...okok... kde.tdyc.com = yuma.tdyc.com = horde.tdyc.com = ....(too many names) :) I've beaten the crap out of that machine and the ISP doesn't love me anymore. and I screwed up the Packages.gz files on the kde site. I need to get those fixed.
Blockbuster has it. saw it yesterday...wow!