There is also a interesting point regarding software repository support. I have a server running Ubuntu 8.04 LTS Server which is supposed to be supported till April 2011, however Wordpress is in the Universe repository and not updated since November 2008 and is vulnerable to a few attacks that delete content.

If these packages are not going to be updated should there not be at least a warning, or method to bar such packages from being installed after security issues have been raised?

Wordpress 2.3.3 in 8.04 LTS Universe repository.

It should be apparent that quotas have been scrapped as they cannot actually guarantee you can use the bandwidth speed they sold. So when they could have previously sold 1/5/10/50GB/day tiers, they spin that into a flat up to 50GB/day, let's call it unlimited, p.s. you'll be lucky to see 1GB.

The IBM Blade Chassis management software works perfectly fine in Opera with no popups or warnings at all. It's actually nicer to use in Opera than Firefox.

If the user really needs to have a program output sound right until Linux goes into suspend mode, and then continues where it left off when resuming, then ALSA is (currently) the only option. I personally don't find this to be a problem, and furthermore I doubt it's a large percentage of users that even use suspend in Linux. Suspend in general in Linux isn't great, due to some rouge piece of hardware like a network or video card which screws it up.

So we should be using OSS because the author doesn't use suspend on his computer?

The article is just a big rant about how difficult he finds ALSA to develop for, how he doesn't understand the benefits of a user-space audio stack as found in Windows Vista and with PulseAudio empowering Ubuntu and other distributions.

This is why we have the Internet, please use and develop new and interesting applications, but they should be webapps. This completely avoids the issue of modifying the desktop and allows immediate availability to everyone in the company.

Being an IT person is being a computer janitor. If you are doing the job properly you are simply unclogging the tubes or restocking printer paper. Every machine should be imaged and locked down with something like Microsoft SteadyState, when a user has a problem it's either a reboot, re-image, or a hardware replacement.

The problem might stem from merging IS and IT jobs into the same position with no distinction being made. IS projects should be handled in a more formal manner than re-stocking a printer but because defining such an interaction is widely open to interpretation it has been taken to the users advantage. You need to take ownership of that interaction and make it clear the difference between such projects and cleaning the tubes.

So instead of offering one browser that can be configured by Group Policy in an Enterprise IT deployment they offer a web service to generate hard-coded branded browser installers? Sounds like a lot of work to avoid implementing what IT managers really want.

Sun is just as bad or worse than Microsoft by implementing incomplete standards leading to the same incompatibility that ODF is supposed to resolve.

Sun should write out formulas in ODF 1.1 format, using the legacy "oooc" namespace prefix that the other vendors are using. Remember, the other vendors are using that namespace specifically for compatibility with OO's ODF documents. This is the current convention. To unilaterally switch, without notice or coordination, to a new namespace, is not cool. When ODF 1.2 is an approved standard, then we all can move there in a coordinated fashion, to cause users minimal inconvenience. But the above table clearly shows the confusion that results if this move is not coordinated. I know OO 3.01 has an option to save in ODF 1.0/1.1 format. IMHO, this should setting should be the default. I'm not sure if the Sun Plugin has a similar configuration option, but I hope it does.

It's a fallacy with US banking, both cashiers cheques and bankers drafts are as useless as regular cheques for guaranteeing payment. Both can be bounced by the originating bank for a variety of reasons. Cashiers cheque are generally more dangerous as your account can be credited earlier, as required by federal law, than when the clearance occurs so you account can appear in credit but later in debit.

You can just download the developers guide from the manufacturer: http://www.dreamcheeky.com/dream/forum/viewtopic.php?f=13&t=102