addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrosseditemptyheartexportfacebookfolderfullheartglobegmailgoogleimageimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

Re: [linux-5] Moving back to Windows from Linux?

From: Wong Boon H.
Sent on: Thursday, October 27, 2011 3:43 PM
Talking about QA processs, the recommendation for enterprise is often Redhat. They QA all the patches before releasing them since they will need to provide support if anything goes wrong. 

For free version, they recommend CentOS which is based on Redhat as well. I notice most hosting providers and email servers use CentOS.

Most end users seems to prefer Ubuntu.

Will be interesting to know which Linux distribution most of you use and why.
Boon Hong

From: Chow Loong Jin <[address removed]>
To: [address removed]
Sent: Thursday, 27 October[masked]:57 AM
Subject: Re: [linux-5] Moving back to Windows from Linux?

On 27/10/[masked]:57, Wong Boon Hong wrote:
> So you guys always update your Linux server whenever a new patch is released
> immediately and never encounter any problem?

It's not that there aren't any problems. It's that when there are problems, it's
usually quite possible to fix/workaround, especially if you know the tools you
are using well enough. And even then problems are relatively few and far in-between.

> Even Microsoft patches have been known to break down something in the past.
> Thus, I will let others test the new patches first for a few weeks or even
> months before I apply them just to ensure that any problem with these patches
> would have been fixed by then. Applying a few patches at once will also help to
> cut down on the number of downtime, especially when most patches insist on
> rebooting your OS.

On Linux, there aren't many patches that would require rebooting your OS. In
fact, some of them that require rebooting can actually be handled by just
restarting affected services, and many of these services, such as Apache, can be
restarted with little to no downtime. On Ubuntu, these packages are usually
listed in /var/run/reboot-required.pkgs. Of course, a kernel update would
require a reboot, and that's particularly dangerous because if it was not tested
properly, it could render your server unbootable.

I know for a fact that Ubuntu and Debian have a "proposed" component of the
archive where packages are staged, tested and verified to be working properly
and regression-free before being copied to the "updates" section. I'd expect
that other distributions have a similar QA process.

> [...]

Kind regards,
Loong Jin

Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Chow Loong Jin ([address removed]) from The Singapore Linux Meetup Group.
To learn more about Chow Loong Jin, visit his/her member profile:
To unsubscribe or to update your mailing list settings, click here:
Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy