Slashdot Mirror
Microsoft Quietly Releases Windows 2003 SP2
Several readers noted that Microsoft has quietly released 32-bit Windows 2003 Service Pack 2 for download. (The 64-bit edition is still showing as a release candidate on the site.) The installation of SP2 may potentially regress hotfixes that have been deployed previously; Microsoft has released a script to scan for hotfixes that may potentially regress.
No, you cant. Not allowed.
What I find interesting is that there was an update to sp2
listed in the upgrade that I just finished to a 2003 server.
emt 377 emt 4
even just a update roll up would be nice. When you install a new xp sp2 system there is a lot of updates that you need to.
I fired up Windows Update on my XP Pro x64 rig today and it had a 350MB patch for me.
Didn't seem to change much, if anything.
Very good point. Why does MS prefer big honkin' files over a more granular approach anyway?
Linux, you magnificent bastard, I read the fucking manual!
At long last! Finally we can un-wire all those unsightly server rooms and start providing data in the same style that we consume it. I for one welcome our new servers-in-beds overlords.
This being the intertubes and all, isn't this kind of old news? I am fairly certain our university upgraded their 2003 servers last week, even though the Microsoft published date reads 3/12/2007.
Very good point. Why does MS prefer big honkin' files over a more granular approach anyway?
Microsoft doesn't prefer it: their corporate customers do, as they have to perform lengthy and expensive tests to confirm all of their mission critical apps work with the SP (imagine doing it after every patch).
Also the GP said that in Linux updates just mean the app is "updated" and there aren't any backwards incompatibilities... Hehe, I'd love to be that naive myself. Just consider however, we don't all run amateur home servers for our php blogs.
You are correct sir.
Run and catch, run and catch, the lamb is caught in the blackberry patch.
STFU Malda
Aww, thanks for the encouragement Sparky! It means a lot coming from...wait...who are you?
Seriously, I NEED an XP SP2b package (all updates up to IE7).
I'm not making a comment. I'm asking a serious question here! XP SP2b OEM disks are already being sold in stores.
Life is not for the lazy.
> Microsoft Quietly Releases Windows 2003 SP2
Quietly releases?
Posting it here certainly made it a lot noisier.
1 in 4 Maine children in struggle with hunger.
I continue to maintain that some psych major will have a field day studying the various pathologies that exhibit themselves on /. Parent poster is a case in point.
Most of the updates in SP2 have been already released as separate patches by now. If the system was kept up to date, this SP will only download/install only the few things that are missing and you don't have to go back and re-install anything.
Basically, an SP is mainly a a convenient way of getting an outdated system fully patched-up.
Some of you are asking what made this release so "quiet".
What happened is in the black of night Ballmer, dressed in his ninja outfit, shimmied along the walls of the MS datacenter with a CD with this service pack on. He used his glass-cutters to silently sneak through a window, and snuck up into the vent before guards could see. Using a series of mirrors to deflect the trip-lasers he then lowered himself down from a vent grate, and uploaded the Windows 2003 service pack onto the server.
Why was it released so quietly? Who knows, but I'm sure there's something evil at work here. Thanks to the submitter for pointing out that this release was suspiciously quiet.
// MD_Update(&m,buf,j);
This also highlights one of the great advantages with open source: free redistribution. The big reasons why debian, ubuntu and other linuxes can do such seamless updates is because of the package managers; because you have one unified system of downloading and installing apps, you can update them without any hassle at all. This wouldn't be possible on windows since the overwhelming majority of apps are not open source, meaning that you can't have a unified repository where you can download them from. That would be copyright infringement. This makes it so that every single app that wants to stay current has to make their own versions of an automatic updater, often making it gruesomely annoying to start whatever you need because of some damn pop-up (Acrobat Reader, I'm looking at you!). In ubuntu,, when something needs updating, a little star shines at the top of my screen, I click on it and enter my password, and bobs-yer-uncle, it's done.
Package managers are such an ingenious solution to handling software, and it is something that could only have come from the open source world.
Well done, linux people! Well done!
If the system was kept up to date, this SP will only download/install only the few things that are missing and you don't have to go back and re-install anything.
No it won't. The full 350Mb appears on Windows Update even if you're fully patched up.
I don't like mindless pro-Linux droning either, but personally I prefer to deal with small updates every day, which are very unlikely to affect anything, than a traumatic experience every month which is rather likely to affect something, where you'll have no idea which of the bundled hotfixes are doing the damage.
Also you have to balance out the bonus of having the bug/security hole fixed immediately; shouldn't it be done right away to avoid worse problems?
// MD_Update(&m,buf,j);
While nothing beats Paludis-flavored Gentoo for me, I remain surprised that no one has made a usable package manager for Windows. It's one of those things that have been perpetually on my "gee, I wish I had the time to write that" list. There are a wide variety of open-source apps for Windows, and there will be many many more when KDE4 is released later this year. It's an enormous pain in the ass to have to individually download and run installers, and keep on top of updates for Gaim, Eclipse, Azureus, Firefox, Thunderbird, OpenOffice, VLC, Audacity, GIMP, etc, when you know there's a better way.
LOAD "SIG",8,1
It would maybe be nice to port apt and start an apt repo (might need to change the extension for the deb files to avoid confusion with Linux debs), but you'd have to really affk with it to get it to work with Winsock, unless you use Cygwin...
-uso.
What you hear in the ear, preach from the rooftop Matthew 10.27b
> No it won't. The full 350Mb appears on Windows Update even if you're fully patched up.
That's not what happens with XP, so I'm guessing that if what you say is true then it's a mistake and not a stupid idea on Microsoft's part.
He shall be remembered forever as the first ninja in history to squirt shurikens and throw chairs at targets.
You can hold down the "B" button for continuous firing.
Wow... and here all this time I thought it was PEOPLE displaying them, not the various pathologies displaying themselves....
Don't tell me to get a life. I'm a gamer; I have LOTS of lives!
I guess that means that the entirety of the release is a HALT instruction?
I'm here all week.
There are no karma whores, only moderation johns
But those tests are only so lengthy and expensive because just about anything can change. If you know that there's a change in Samba, you only have to test the things that depend on Samba, you don't have to retest everything in the system. The fact that you have to test so many things when you upgrade is just a microsoft thing. There isn't a lot of things that break if your patch consists of actually just fixing a single, or small number of bugs.
Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
people like to slipstream updates to the install source.
My god, how often do you run updates? When I tried to update one of my test boxes running RC2 it detected that SP2 was already installed. I had to uninstall the RC version for it to detect that the "official" release was needed.
P.S.,
This is what part of the alphabet would look like if Q and R were eliminated.
http://www.installpad.com/
l ive--automatically-download-and-install-your-favor ite-software-211373.php
http://blog.genotrance.com/applications/appsnap/
More at:
http://lifehacker.com/software/downloads/geek-to-
Nerd rage is the funniest rage.
Good to see Microsoft is still releasing service packs for Server 2003. However, I really want to see SP3 for XP. Building an XP box, even from SP2 media, requires over 75 patches in our environment! It takes nearly 50 minutes of cranking every time we have to build a new master disk image. Not all of us upgrade instantly.
It's nice that Microsoft makes the patches available separately. For those who don't do it, you wouldn't believe how much work it is testing patches and narrowing down which one broke an application. However, I think they should have one monster rollup available at least every few months. Most of that 50 minutes is spent dependency-resolving, isolating and backing up the files that each patch replaces. Doing that once is better than 75 times.
One thing I don't like about MS is that they tend to abandon customers who can't or won't upgrade to the next version of a product. I'd love to be on IE7, but we're stuck on 6 until several dependencies get fixed. I'm not too wild about Vista, but know that we have to go that way in the next year or so just to ensure we get the latest security fixes. Microsoft guarantees they'll backport fixes for a while, but you can bet they're doing all the active research on Vista. I can't agree with people who say they should still support NT, but most of the enterprise-class vendors have a much more lenient upgrade policy. (OpenVMS is at least kind of supported 3 versions back, IIRC.)
But those tests are only so lengthy and expensive because just about anything can change. If you know that there's a change in Samba, you only have to test the things that depend on Samba, you don't have to retest everything in the system. The fact that you have to test so many things when you upgrade is just a microsoft thing. There isn't a lot of things that break if your patch consists of actually just fixing a single, or small number of bugs.
/dev/rand/ which is fed entropy from HDD, mouse, keyboard and network activity. In 2.6 network activity was no longer used (security issue), and the server hand no mouse, keyboard, and all files were on a NFS share. So /dev/rand/ was "running out of entropy" and blocking.
What you're talking about is simply the wrong perception of a guy who never dealt with the issue at hand.
Tell me: how can it be less testing to test individually all components that could be affected by a patch, versus testing for all components that could be affected by a list of patches. Especially if several patches affect the same exact components.
A SP isn't a black box. You get a list of the small fixes that are contained inside, so you again know what is being changed.
Also, testing just what could obviously break is a terrible way to test. A read a story about someone, who after upgrading to Linux kernel 2.6 started having random lockups in PHP/Apache.
What changed? After long and extensive testing, it turned out that sessions use
How would YOU guess that your 2.4 -> 2.6 kernel upgrade would cause PHP sessions to lock up under heavy load, when you look at the list of changes?? Answer: you wouldn't.
You'd deploy this on the live servers and experience mysterious downtimes all the time. And THIS is why enterprises test throughly all critical apps, even for the smallest patches.
Crap! I run my server on dial up. Guess this is going to be a long night.
Thanks a LOT, /.
qz
This is not so much of an issue for me now, but in the past I have had to spend days going through change management to install anything on a server, be it a hotfix, service pack, whatever. I, for one, welcome our big honkin' file overlords.
P.S.,
This is what part of the alphabet would look like if Q and R were eliminated.
Another point to big service packs is that once SP(n) is released, marketing can admit SP(n-1)
is really quite insecure on WIN(r-3) and how WIN(r) is now strongly recommended for your shop
Just consider however, we don't all run amateur home servers for our php blogs.
... because large and monolithic patches tend to break things, and I don't want to remember the nightmare that was Windows XP SP2.
... like we don't work with "enterprisey" applications that affect the bottom line.
;)
Just because a patch is ready for download, doesn't mean that you have to install it. You can make it your company's policy to update only on the 10th of every month for example.
But if there is a major security flaw for a certain application that you hear of from your security advisor, then on the contrary there are reasons to update right away.
Common sense and experience of many other (including mine) says that small and frequent patches are to be preferred to large monolithic patches
Also small and frequent patches are easier to test by your average IT department.
And please
If it is one thing I learned is that the level of incompetence in almost all major companies is breathtaking
A better question would have been "why was it me,
running the update"?
But the answer is "not nearly often enough".
emt 377 emt 4
O RLY? What patches install the security center, improved firewall, and IE6 SP2 in Windows XP SP1?
I'm waiting for some wit to post links to ZoneAlarm and the like.
Hail Eris, full of mischief...
E pluribus sanguinem
The issue with MS products is their downright incestuous relationship with each other. An update to IE can potentially affect Word. A patch for a security bug in IIS can cause SQL server to go wacky. The reason that business prefers Service Packs to patches is because they've learned the hard way that if you change ANYTHING on a Windows box, you have to recertify EVERYTHING.
Don't tell me to get a life. I had one once. It sucked.
"(The 64-bit edition is still showing as a release candidate on the site.)"
FYI: It may not be showing up on the site, but it's showing up on my wife's computer via Windows Update. (The Windows XP x64 version, at least).
Apples and Oranges. A change to the kernel potentially affects EVERYTHING on the system. Anyone doing a kernel upgrade *should* be retesting everything on the system.
Windows doesn't have a monolithic kernel like Linux. Are you going to flame now all OS with hybrid kernels and microkernels?
You wouldn't be right anyway, since there are tons of library dependencies in Linux apps where updating a component could cause a chain reaction affecting all libs that use it, the libs that use the libs, and some app that uses the latter libs, you never suspected.
I dunno, fixes and features only in SP's seems pretty popular with Microsoft. That's "black box" in your sense.
If it's no on fire, it's a hardware problem.
The post says "Several readers noted..." - does this mean you were one of those several? How does it work if, say, ten people submit the same story in the space of half an hour?
Karma police, arrest this man. He talks in math. He buzzes like a fridge. He's like a detuned radio.
A number of companies have applications which are only supported by the vendor at selected patchlevels, with no other software allowed. Microsoft releasing large collection of patches as service packs makes the job of vetting various hardware and software configurations easier. Its easier for a vendor to state that their application runs on Windows 2003 SP2, rather than Windows 2003, with a large amount of patch numbers needed.
Plus, (IMHO of course), it was time for a service pack for Windows 2003 anyway.
What're you talking about? The kernel affects _everything_. If I upgraded the kernel and then things started going wonky it would be the first thing I suspected. That's about the most obvious candidate for when something breaks.
It seems like you consider a upgrading the kernel between major versions a minor patch. I don't know where you're getting your information, but the kernel is central to the system. Even minor updates need major testing since it could affect anything on the system.
Aside from that, I agree with you. SPs are not any harder to test for than individual patches, easier in some cases.
Thats a major kernel upgrade. Not a service pack.
What your describing is more along the lines of upgrading from Windows 98 to Windows 2000.
...but: Releasing an operating system quietly?
Uh uh.
It so happens that Apple released Mac OS X 10.4.9 today, and the updater didn't make a single sound while it was installing it. (Though the hard disk was making all kinds of thrashy sounds, but I don't think they count.)
Those who can, do. Those who can't, write technology blogs.
More to the point, if I see an update come through on Ubuntu that is for "gnome-desktop-calendar" then I can be pretty sure that even if it is borked, it won't bork my entire system, and even if it does, I will know where to look in order to fix it.
On the flip side, if I apply W2K_SP2.exe to my server and something breaks I have a much more difficult time identifying the problem and often the best short term course of action is to roll back the entire service pack.
"You can't fight in here, this is the war room!"
This is a return to the way MS used to do SP's. All SP's used to be were bug fixed and back ported updates (like NTFS 5.0 supprt for NT4). Nothing major was added to SP's. now they throw a lot more shit in the SP's and change even more shit. SP2 for 2k3 looks like i can fast track it in with out having to go through reams of documentation and testing.
If a 'server' is 'not remotely accessible by any means', what exactly does it 'serve'?
Actually, I can think of a dozen different ways it would.
You're talking about going from one MAJOR kernel version to a different MAJOR kernel version.
Why would you deploy a MAJOR change on production servers without massive testing?
A "service pack" would be more like lib-foo_2.1.2 going to lib-foo_2.1.3.
Which is different than going to lib-foo_2.2.0.
Which is far different from going to lib-foo_3.0.0.
Which is far different from going to kernel 2.6.x from kernel 2.4.x.
So everyone did their updates at the same time as me. Windows updates are generally available in the morning, I do mine after work on Tuesdays. How strange that "several readers" do their updates at exactly the same time as me and submit a story about it. More like someone saw the story I submitted and took it for themselves. It's not that it's bothering me, it just makes me wonder if Slashdot is gamed, sort of like Digg.
Everytime I see this I can't get over how fucking funny that bird looks.
XP 64, which is a non-server edition of Windows 2003, was sold to consumer markets a little bit. Of course, the people using XP 64 are probably technically savvy and read about it on Slashdot.
Microsoft released a simple, direct service pack today and it works well. It's about time they did that. My only complaint is the size: are there really 350 megabytes of binary diffs to apply?
"Screw Sun, cross-platform will never work. Let's move on and steal the Java language." - Visual J++ Product Manager
Yes, your PHP blog is the mission critical application that just won't do without a monolithic update process.
Just installed Win2k3 on a server a couple hours ago. It was nice to see ~3 critical updates rather then the 50+ I had to install last week.
Hollow words will burn and hollow men will burn.
Not all servers are connected to the internet. There are some installations that are so secure they are not remotely accessible by any means. I actually did download win2k sp4 via modem which I then sneakerneted to the real installation. Now, did I really need to know it was going to take 17 hours, thats debatable. But at Least I know someone in redmond cares about me.
:)
Ya, this is important to people, oh wait, most people would at the very least go to a freaking Hotspot or the library and slam the update on a Flash USB or CD... So why on hell did you download this via dial up again?
Win2k SP4...
On their official page of release dates: http://support.microsoft.com/kb/260910
Windows 2000 Service Pack 4
Release date: June 26, 2003
I would say this was in the range of "some people just had dialups at that time".
WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
You think they doubled max volume levels in 10.4.9 without purpose?
Comment removed based on user account deletion
> O RLY? What patches install the security center, improved firewall, and IE6 SP2 in Windows XP SP1?
What's that got to do with what I put in my post?
Okay, it's unlikely a bugfix to the color management subsystem is going to affect the accounting program, but when millions of dollars over tens of thousands of workstations are potentially affected, are you going to take that risk?
Big corporates aren't; not with that level of money on the line. Each patch causes everything to be restested, it doesn't matter HOW big or small the patch is. Bigger patches save time, overall, because that means there's fewer of them meaning (per year) less time spent testing. Less headaches for IT depts too, because there's less patches for them to tick off and keep track of.
Small and frequent patches are a huge sinkhole of time for an IT department.
See, I'd rather test my programs against a single "march 2007" update than having to test against all the different possible bugfixes that accumulated during march. Doing daily updates as you speak makes for a huge effort just to stay in the same place.
Also, the one big patch lets me read mailing lists and find out what other corporates have done. If a huge multinational runs into an issue with a SP, I know that I have to be careful with that SP even though my company is a ten thousandath of the size. But a minor update? There's not going to be enough weight to that for me to hear about issues it causes.
Yes, I know, there are times that patches need to be expidited due to security issues, which I can live with.
Ummm ... yes, but that is you, not a corporate customer.
A few years back I was working for a company developing a large financial platform, and they were testing a few months before getting to the next service pack (then, the sys-admin installed it on all computers). This was being done on separate machines, and a full battery of tests had to be run, before approving the upgrade company-wide.
You simply cannot afford that, when you have a lot of small upgrades, spread over the same period. Also, when considering the same updates but distributed differently (small updates vs. service-pack) their likeliness of affecting something is exactly the same.
Tie two birds together: although they have four wings, they cannot fly. (The blind man)
In which case I guess it's specific to XP "x64 Edition" users.
+1 Informative and -1 Troll :)
"You wouldn't be right anyway, since there are tons of library dependencies in Linux apps where updating a component could cause a chain reaction affecting all libs that use it, the libs that use the libs, and some app that uses the latter libs, you never suspected."
Yes.
Still, I have yet to have *any* problem on a security update on Debian "stable" on about six years. How's that possible?
I'll tell you: Microsoft updates are not *security* updates; they overly change the way Windows behaves so it's no wonder something breaks because of it. If they were as concious as Debian people are about fixing *only* security holes and doing it by introducing the less possible changes and no behaviour change at all, you could bet Windows patches wouldn't be such a nightmare.
Please understand that has nothing to do with being Windows or Linux but about how serious they are about how upgrades have to be done: Debian is rock solid; Red Hat a bit of a concern; Gentoo almost doesn't pay attention to it; Microsoft is about as good as Gentoo.
Package managers are such an ingenious solution to handling software, and it is something that could only have come from the open source world.
Package managers are an ugly hack to work around the two biggest problems in the open source world: fragmentation and instability, both of which lead to dependency hell.
Well, it is a significant upgrade from the previous release, which was a BSOD instruction...
Testing, in my opinion, is only for things that you don't have a deterministic way of proving "by construction". For instance, in something as simple as the change noted above regarding /dev/random, this should have been noted just based on documentation alone - no need for testing.
One problem is documentation is either insufficient, inaccurate, or completely missing.
I also would put some of the blame on both system and application developers: this is one of the problems with the shared library concept. My philosophy is "If you have something that, if the implementation changes things will break, make sure that implementation cannot change - that is, use a static library."
The other rule of thumb is "Never rely on side effects." The trick there is sometimes side effects are not obviously a side effect....
"There are a dozen opinions on a matter until you know the truth. Then there is only one." - CS Lewis (paraprhase)
http://support.microsoft.com/kb/898073 = [IE6 crashes on] digest proxy authentication [to https sites] http://support.microsoft.com/kb/918005 = Battery power may drain more quickly [after unplugging or undocking] http://support.microsoft.com/kb/918837 = power management is turned off [after disabling WakeOnWirelessLAN] http://support.microsoft.com/kb/924078 = [error opening] Properties [...] for a network printer on [WinXP] http://support.microsoft.com/kb/924301 = AutoComplete feature [broken after following javascript link in IE6] http://support.microsoft.com/kb/925020 = [Lockup when using] USB device on a multiprocessor computer http://support.microsoft.com/kb/925240 = warning message [...] new password that does not meet the requirements http://support.microsoft.com/kb/925513 = Error code Winsock [...] "WSAECONNABORTED (10053)" http://support.microsoft.com/kb/926047 = [Misplaced] AutoComplete box [...] in Internet Explorer 6 http://support.microsoft.com/kb/926132 = ...WMI does not clear event registrations when the corresponding sink...
http://support.microsoft.com/kb/926754 = STOP: 0x000000D1 (parameter1 , 0x00000002, 0x00000000, 0xf27b4e8e)
http://support.microsoft.com/kb/926940 = SQL Server 2000 Service Pack 4 stops responding
http://support.microsoft.com/kb/927291 = Dfsutil /import" command takes a long time to finish
http://support.microsoft.com/kb/927493 = Winsock programs may exhaust the system's non-paged pool
http://support.microsoft.com/kb/929620 = increased paging to the hard disk when you run an SAP R/3
These fixes are regressed, but they're not published on the public Knowledge Base:
"919757" "925290" "926305" "926513" "926583" "927197" "927436" "927893" "928194" "929066" "929759" "930620" "933452"
Switching from 9x to NT is more akin to switching from OS/2 to Linux than a switching from 2.4 to 2.6, considering that the NT kernel was in no way derived from 9x.
Let me fix that for you:
What your describing is more along the lines of upgrading from Windows 2000 to Windows XP.
My sig can beat up your sig.
No, certainly not in the way Windows is.
Well, ReactOS just released version 0.3.1. At this rate, you'll have your SP5 sometime around 2009. The good news: after that, you'll get regular updates again for (potentially) ever.
and now I can't install software or run a executable from a network drive because of it.
2003 Server SP2 is not just a rollup of previous patches and hotfixes, it contains something extra...
the history of the world
I submitted this yesterday afternoon (3:30 PM EST)and it was posted a few hours later. It does note that several readers sent in the news, and the first sentence or two is from my post, the rest was added by someone else. Eh, still feels good to be included.
This is when you and your neighbors within 5-10 miles of each other invest in a T1 line, and distribute good old 802.11 between each other and split the costs.
This isn't rocket science, and can be an easy way to ok bandwidth for everyone with costs lower than cable high speed for people depending on your population density.
I was from a rural area that still has limited high speed, but everyone I know that still lives there has pooled together wireless communities, many even making a business out of it.
Sadly the US does suck when it comes to customer delivered High Speed, too bad people didn't elect Gore(or at least get him in office), someone that wanted to force the Telcos to provide the end user bandwidth they got discounts to provide.
I'm so glad I don't have to test too many things:
joe@joes-laptop:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
gtkhtml3.14 libgtkhtml3.14-19 libkexiv2-0 libwxbase2.8-0 libwxgtk2.8-0
linux-headers-2.6.20-10 linux-headers-2.6.20-10-generic
linux-image-2.6.20-10-generic linux-restricted-modules-2.6.20-10-generic
The following packages will be upgraded:
acpid app-install-data apport apport-gtk apport-qt apt apt-utils at-spi
bsdutils capplets-data console-setup cupsys cupsys-bsd cupsys-client
cupsys-common deskbar-applet desktop-file-utils dia-common dia-gnome
dia-libs digikam eog epiphany-browser epiphany-extensions espeak espeak-data
evince evolution evolution-common evolution-data-server
evolution-data-server-common evolution-exchange evolution-plugins
evolution-webcal f-spot feisty-session-splashes file-roller foomatic-filters
gdebi gdebi-core gdm gedit gedit-common gnome-about
gnome-accessibility-themes gnome-app-install gnome-applets
gnome-applets-data gnome-control-center gnome-desktop-data gnome-doc-utils
gnome-icon-theme gnome-keyring gnome-media gnome-media-common gnome-menus
gnome-orca gnome-panel gnome-panel-data gnome-power-manager
gnome-screensaver gnome-session gnome-system-monitor gnome-system-tools
gnome-terminal gnome-terminal-data gnome-themes gnome-utils gtk2-engines
gtk2-engines-pixbuf hal hal-device-manager kate kcontrol kde-style-polyester
kde-systemsettings kdebase-bin kdebase-data kdebase-kio-plugins kdepasswd
kdeprint kdesktop kdm kfind khelpcenter kicker klipper kmenuedit konqueror
konqueror-nsplugins konsole ksmserver ksplash ksysguard ksysguardd ktorrent
kubuntu-artwork-usplash kubuntu-default-settings kubuntu-desktop
kubuntu-docs kwin language-pack-en language-pack-en-base
language-pack-gnome-en language-pack-gnome-en-base libasound2 libatk1.0-0
libatspi1.0-0 libbonobo2-0 libbonobo2-common libbonoboui2-0
libbonoboui2-common libcairo2 libcamel1.2-10 libcupsimage2 libcupsys2
libcupsys2-dev libebook1.2-9 libecal1.2-7 libedata-book1.2-2
libedata-cal1.2-6 libedataserver1.2-9 libedataserverui1.2-8 libeel2-2
libeel2-data libegroupwise1.2-13 libespeak1 libexchange-storage1.2-3
libgail-common libgail-gnome-module libgail18 libgnome-desktop-2
libgnome-keyring0 libgnome-media0 libgnome-menu2 libgnome-window-settings1
libgnome2-0 libgnome2-common libgnomekbd-common libgnomekbd1 libgnomekbdui1
libgnomeprint2.2-0 libgnomeprint2.2-data libgnomeprintui2.2-0
libgnomeprintui2.2-common libgnomevfs2-0 libgnomevfs2-bin
libgnomevfs2-common libgnomevfs2-extra libgpgme11 libgtk2.0-0 libgtk2.0-bin
libgtk2.0-common libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
libhal-dev libhal-storage1 libhal1 libkonq4 liblircclient0 libmetacity0
libmozjs0d libnautilus-burn4 libnautilus-extension1 libnm-glib0 libnm-util0
libnspr4-0d libnss3-0d liboobs-1-3 libpanel-applet2-0 libpango1.0-0
libpango1.0-common libpoppler1 libpoppler1-glib libpoppler1-qt libslab0
libtotem-plparser1 libvlc0 libvte-common libvte9 libwnck-common libwnck18
libxul-common libxul0d linux-686 linux-generic linux-headers-generic
linux-image-generic linux-libc-dev linux-restricted-modules-common
linux-restricted-m
[Un]Fortunately, when I was hit with this by surprise at work yesterday, it failed to install. Hooray Microsoft!
Apparently you've never experienced a glibc update. That, my friend, is a world of hurt akin to needing to reinstall your copy of Windows. The fact is kernel updates, compiler updates that break binary compatibility, and updates to widely-used dynamic libraries are found on all modern platforms, and they all suck equally. Try following -current on OpenBSD or emerging world on Gentoo for your production machines someday and see if you'd rather just wait for stable releases on your critical machines. I'm personally happy that Microsoft hasn't forgotten that we do actually need maintenance for existing software.
Cause, I was in Haiti. No library, no hotspot.
Well.. maybe. Or Maybe not. But Definitely not sort of.
A service pack isn't just a collection of hotfixes - it will have hotfixes in it, but it is also a collection of OS additions which were either not complete when the OS was released or were not even conceived at the time. You WON'T be able to find all the components of a service pack (e.g. as Nimey suggests - the XP Security Centre, which includes the firewall) on windows update without downloading the service pack itself
Quote: "Also, testing just what could obviously break is a terrible way to test. A read a story about someone, who after upgrading to Linux kernel 2.6 started having random lockups in PHP/Apache."
/dev/random. You need to run 'rngd' in order to fix this (it fills the entropy pool with random data generated).
I have had the same issue, the apache SSL module needs the random stuff from
No "long and extensive testing" needed to figure that out.
And, as other people have mentioned, upgrading 2.4 -> 2.6 is like upgrading from Windows 2000 -> 2003.
But the point I want to make is the following:
Look how precisely it is possible to pinpoint the -exact- problem.
Whereas I see most MS people fiddling around like it's a big magic box where just about anything can happen (this includes myself when administering a MS box).
And actually, compared to the openness of Linux updates, a MS SP really -IS- a black box.
Hopefully this will be easier than installing SP1 to SBS (small Business) 2003. When I did SP1 on SBS 2003, MS's auto update killed the system to where it couldn't accept new users, etc. I had to manually install about 3 patches and 2 more versions of SP1 to get it working right. And that was all listed as what to do in a MS knowledge base article. Totally insane way for MS to have it update.
Nah I considered that but they use the same kernel. Virtually no difference between the two under the skin.
I'm not going to argue about how different WinXP is from Win2K. But the fact is that the WinXP kernel is an evolution of the Win2K kernel, just like the 2.6 kernel is an evolution of the 2.4 kernel. But the NT kernel isn't derived from Win9x at all, making your analogy flawed. Saying that Win9x is related to Win2K is like saying Linux is related to Unix; the look alike, and they function similarly, but were developed separately.
My sig can beat up your sig.
Win2k was released in the year 2000. XP was 2001.
Believe it or not but XP is identical to 2k under the skin. Maybe at best a point release like 2.6.19 to 2.6.20.
Funnily enough the NT kernel and the 9x kernel are related. They are brothers.
NT is just a bit older than 9x.
The 9x "kernel" has a name: MS-DOS. NT is not based off of DOS, therefore the NT kernel is not related to 9x.
And didn't I say I wasn't going to argue about XP-vs-2K? You're arguing with yourself, there...
My sig can beat up your sig.