Slashdot Mirror


Mac OS X Update 10.2.4 Resets

Oculus Habent writes "It may just be me, but 10.2.4 reset a number of settings on my computer, including icon sizes, window positions, and dock size and contents. Minor annoyances, but completely unnecessary. Is anyone else experiencing this?" As for me, Apple re-added some apps to my Dock and overwrote all my changes to httpd.conf (though it did back it up first) to add mod_rendezvous_apple. But those problems pale in comparison to some others: Anonymous Coward writes "If you upgraded your Mac desktop to 10.2.4 last weekend, check your date and time. Many users have suddenly found it to be 4:00 PM, December 31, 1969 again. Apparently, this happens whenever they are shut down or restarted, and resetting the motherboard and/or the PRAM doesn't fix it. Complaints have been piling up at Apple.com and prices for batteries have been skyrocketing - but relax. It's not your battery!"

36 of 135 comments (clear)

  1. No such panic for me...sky is still up by djupedal · · Score: 4, Interesting

    I updated two computers.... G4 and an iBook. The only issue I had was needing to modify my httpd conf for on the G4 for PHP. No date issues....no moved icons..no lost internet...no droppy socks and the cat still has two different colored eyes.

    I submit that as usual, the majority of issues are not directly related to 10.2.4. If you move apps where Apple's installer doesn't expect them to be (and don't whine how it is your computer and not Apple's), you'll have boinked links, and dock icon issues. If you've done a poor original install, you'll have issues with system updates, whether the bad install was your gift to the afternoon or not. Get over it...the sky hasn't fallen...this is not OS 9, and the sooner we all get used to a modern OS the happier we will be.

    1. Re:No such panic for me...sky is still up by Mononoke · · Score: 4, Funny
      If the goddamn OS *lets* me move things around, then it bloody well better recognize that I've done so, and honor those changes.
      You're one of those that used to move vital things out of the System Folder in the pre-OSX days, aren't you.

      If so, thank you. I made quite a bit of money cleaning up other people's silly messes back then.

      --
      NetInfo connection failed for server 127.0.0.1/local
    2. Re:No such panic for me...sky is still up by Anonymous Coward · · Score: 3, Funny

      Hell, that's nothing. I typed "sudo rm -rf /" in my terminal window and this piece of shit "Mac" OS didn't boot at all the next day!

      What a waste of money! It's MY computer, I should be able to do whatever I like to the hard drive and it should continue to function!!

    3. Re:No such panic for me...sky is still up by elmegil · · Score: 2, Insightful
      To elaborate: we're talking about the OS that prides itself on being "user friendly". People who don't like computers like macs (allegedly). Etc. etc.

      So, if moving some part of the system folder somewhere else is going to fuck up the computer, or worse, NOT fuck up the computer but fuck up the next update, that folder ought to not be changeable by the user. Doing otherwise is not "friendly", it just allows people to blow their legs off.

      After all, my car won't let me start the engine in drive, my microwave won't let me start it with the door open, why the hell should my computer let me do patently stupid things?

      --
      7 November 2006: The day Americans realized corruption and incompetence weren't addressing 11 September 2001
    4. Re:No such panic for me...sky is still up by Anonymous Coward · · Score: 2, Insightful

      Give up.

      You don't make sense.

      Yeah, your car won't start in drive, but you can run into a tree. You can throw it in reverse or shift gears at the wrong time. You can load your SUV wrong and it will flip over ("BUT why didn't sense the weight and warn me").

      Your microwave won't start without the door open. However, nothing will stop you from microwaving steel wool, or a battery, or an unopened champagne bottle (don't do any of that btw).

      Moving apps out of Applications folder doesn't break anything except updates and some hard-wired paths. It's not a big deal. You probably have a mental list of things you don't do with a computer, like not operating it underwater, or not flicking the power switch on and off 60 times a second. Well, add "don't move Apple's applications" to that list. Sheesh.

    5. Re:No such panic for me...sky is still up by Twirlip+of+the+Mists · · Score: 3, Funny

      The point is, if it shouldn't be done, don't allow it to be done. Duh.

      # mv /boot/vmlinuz /vmlinuz
      # reboot


      Ooooops.

      --

      I write in my journal
  2. Works for Me by yancey · · Score: 2, Informative


    I grabbed 10.2.4 as soon as it came out.. indeed, even before it was mentioned on Slashdot! I have not seen any of the problems mentioned.

    Though the httpd.conf file was probably replaced, I wouldn't have noticed since this is a laptop and I don't use Apache very often.

    --
    Ouch! The truth hurts!
    1. Re:Works for Me by cyb97 · · Score: 4, Funny
      even before it was mentioned on Slashdot! I have not seen any of the problems mentioned.

      So now it's proven, Slashdot is the cause of all problems!

  3. zero problems for me by Anonymous Coward · · Score: 5, Informative

    Everything worked fine for me. Nothing reset, no changes to the Dock. I don't know if it makes a difference but I downloaded the tar file directly and ran the update later, rather than using Software Update.

    Haven't seen any time/date changes, but my clock is set by NTP anyway.

    PS: One thing I like to do before any major update is run something like "find -s / > /tmp/filelist" to get a list of all files and dates. Then run it again after the update and diff the two lists. That will show you httpd.conf changed, for instance. Also it's just interesting to see what files change on the machine as I learn about the OS. You can also get lists of files from the archive itself or from the "bill of materials" file ("man lsbom") after installation.

    PPS: does anybody know what the file /iNode12022737 is for? I keep seeing files like that in the root dir...

    1. Re:zero problems for me by laptop006 · · Score: 2, Informative

      > PPS: does anybody know what the file /iNode12022737 is for? I keep seeing files like that in the root dir...

      That looks like an orphaned file, where there is still a file associated with an inode, but no file name associated with it.

      --
      /* FUCK - The F-word is here so that you can grep for it */
    2. Re:zero problems for me by Halo1 · · Score: 2, Informative
      You can simply do the following to see what files will be changed:

      lsbom MacOSX10.2.4.pkg/Contents/Archive.bom

      --
      Donate free food here
  4. It happened to me! by Visigothe · · Score: 3, Informative

    I thought it was rather odd as well. I had icons for iChat, the addressbook, and some other applications that weren't on the dock pre-update. My time wasn't affected to my recollection, but some of my other prefs were.

    Know what I did? I removed the icons, and fixed my prefs. Then I promptly forgot about the whole thing and got on with my life.

    I did find it strange though... That sort of thing has never happened to me before

  5. Re:Still haven't fixed... by Anonymous Coward · · Score: 2, Informative

    Yeah I see that too. Though I don't think it has anything to do with the Finder-generated preview, because I see it on other icons too occasionally. It doesn't do it all the time.

    I also see an occasional problem when I have "FILE.jpg" and "FILE.psd" files in the same folder, i.e., the file from my camera and it's edited version. I keep the folders in Icon view with 128x128 icons. Whenever I save the .psd from within photoshop, the same icon appears on both files! sometimes it appears on other adjacent files too, or sometimes the icons just disappear (but it still works to click in the empty space).

    Drives me nuts, this does!

  6. Yeah right. by Daleks · · Score: 2, Interesting

    I know lots of people that use Mac OS X (me included) and they never experience any of these supposed catastrophic failures when updating their system. I smell a MS smear campaign.

    1. Re:Yeah right. by Oculus+Habent · · Score: 2, Interesting

      I'm a big Mac fan, personally. None of my failures were catastrophic. I haven't shutdown since the upgrade, so I can't speak to the clock issue, but the Dock was quite unusual - it was OS-install fresh for me. Everything was in the proper places (sort-of reply to above posts about friggin with the OS) - I keep iCal, Safari, and Terminal in my Dock and they were all missing. Maybe I'm just lucky.

      As I mentioned, the changes were more annoyances than failures. I've been quite happy with Macs throughout history, even with the IIsi's sound glitch, the PowerBook 190's power connector, the PB 1400's CD-ROM faces (Three of they have broken, two for me, one for a friend). The difference between my Macs and my PCs is my Macs have never had serious failures. I've lost drives, RAM, processors, motherboards, and modems on my PCs (RAM was cheap, though) and the worst I've done with my Macs is buying bad RAM and a broken LCD from shipping.

      I've unintentionally stepped on all three PowerBooks I've owned (maybe I should be more careful) and none of them have broken for failed for it. I actually stepped out of bed on my Pismo - full weight on the closed computer - and it didn't even wake up.

      If you want catastrophic software failures, how about the three times NT 4.0 has just stopped recognizing keyboards for me, or the two times Win 2K decided not to make it through boot anymore?

      --
      That what was all this school was for... to teach us how to solve our own problems. -- janeowit
  7. FWIW... by gabe · · Score: 2, Interesting

    ... I installed 10.2.4 on my G4 iMac when it was released and I've had zero problems with it.

    I'm a little more fearful about it touching my powerbook G3 (pismo) though. I've frequently had problems with that machine and updates. I've had to completely backup/wipe/reinstall the damn thing at least 5 times due to problems with OSX. It seems that they give considerably less of a damn about older machines than the do about the cream of the crop.

    I'll wait a while before installing it on my powerbook.

    --
    Gabriel Ricard
  8. good one...I forgot about all those rescues by djupedal · · Score: 2, Funny

    My brother used to put the system file out on the desktop....and I never asked why. He also insisted on formatting otherwise left over HD space...and every time his house of cards fell, I'd have to grinnbearit.

    silly messes...that's funny...like a stain on the carpet, only it doesn't smell.

  9. Protecting your OS from changes by kruetz · · Score: 3, Informative

    I'm guessing the installer/updater plays along with the *NIX user system, right? So what about "chmod a-w httpd.conf" for protecting your httpd settings? If you don't want your settings modified by Apple, use the power of *NIX against it!

    Or does this not work?

    --

    This sig intentionally left bla... dammit!
    Who's got the whiteout?
    1. Re:Protecting your OS from changes by Visigothe · · Score: 4, Informative
      I'm guessing the installer/updater plays along with the *NIX user system, right? So what about "chmod a-w httpd.conf" for protecting your httpd settings? If you don't want your settings modified by Apple, use the power of *NIX against it!

      That won't work, as in order to update the system, you must supply the admin password. The admin [root, but not exactly] can do anything.

    2. Re:Protecting your OS from changes by jim3e8 · · Score: 3, Informative

      Root can do anything; the permissions are advisory only, and can be ignored. Otherwise, that mode 000 file would become a permanently inaccessible paperweight.

  10. why does everyone jump all over upgrades? by 3-State+Bit · · Score: 2, Interesting

    software update has asked me a few times if I want 10.2.4.
    Uh, why? I have dozens of windows open, and uptime in the weeks. (This is an iBook -- are you on one? Open terminal and type 'uptime'.).

    I read over the improvements, and there's nothing I need right now.

    C'mon people. Get with BSD style.

    1. Re:why does everyone jump all over upgrades? by MalleusEBHC · · Score: 4, Insightful

      First, you must remember that a large majority of Mac users (usually those who were around before OS X) know little or nothing about BSD or *nix. And they shouldn't have to. The sysadmin "don't fix it unless it's broke" philosophy is not the consumer "I want the latest and greatest" philosophy. These people buy Macs so they won't have any hassles. When Software Update pops up, they just want to click install and be done with it. Most of the time, this is fine and there are no problems.

      On the other hand, you do have geeks who will take a more "wait and see" approach, many of whom have the advantage testing it on one machine before putting it on their other boxes. This is fine, but I've found that with OS X it is usually not necessary. I've tried every update on my Powerbook before throwing it on my Cube, and never have I had to wait long because there haven't been any problems. Despite the inevitable horror stories that come with each update, the grand majority of OS X users don't have any problems.

    2. Re:why does everyone jump all over upgrades? by adashiel · · Score: 2, Informative

      I agree in principle, but among the bugfixes in the 10.2.4 update were several security-related items. From http://docs.info.apple.com/article.html?artnum=617 98 (Comments in brackets mine)

      Mac OS X 10.2.4

      • Sendmail: Fixes CAN-2002-0906 Buffer overflow in Sendmail before 8.12.5, when configured to use a custom DNS map to query TXT records, could permit a denial of service attack and possibly allow execution of arbitrary code. Mac OS X 10.2.4 contains Sendmail 8.12.6 with the SMRSH fix applied to also address CAN-2002-1165. [Not an issue for most, obviously, but, well, it's sendmail.]

      • AFP: Fixes CAN-2003-0049 "AFP login permissions for the system administrator". Provides an option whereby a system administrator may or may not be allowed to log in as a user, authenticating via their admin password. Previously, administrators could always log in as a user, authenticating via their own admin password. [I haven't seen any documentation on setting this up yet. Hrm. Hrm.]

      • Classic: Fixes CAN-2003-0088, where an attacker may change an environment variable to create arbitrary files or overwrite existing files, which could lead to obtaining elevated privileges. Credit to Dave G. from @stake, Inc. for discovering this issue. [This one can be pretty serious if you're running the classic environment in a lab setting. <insert standard physical security disclaimer here>]

      • Samba: Previous releases of Mac OS X are not vulnerable to CAN-2002-1318, an issue in Samba's length checking for encrypted password changes. Mac OS X currently uses Directory Services for authentication, and does not call the vulnerable Samba function. However, to prevent a potential future exploit via this function, the patch from Samba 2.2.7 was applied although the version of Samba was not changed for this update release. Further information is available from: http://samba.org/samba/whatsnew/samba-2.2.7.html [This may not have been an real issue for OS X, but it was a pain for me nevertheless. Every time our internal security scanner checked my systems, it would squawk about a high-priority security alert. That never fails to attract the attention of managers.]

      Note: To my knowledge, none of these security fixes were released prior to 10.2.4. You could fix some of them yourself, but for the general Mac audience, that's a wildly unrealistic expectation.

      ObOnTopic: I experienced the clock reset on my dualie, but NTP fixed that easily enough. In previous releases, I've had Dock items added and experienced other minor annoyances. It's never been consistent across machines, though, and since the problems were so trivial I never bothered to troubleshoot them further. Permissions issues? Files out of place? Gremlins?

      --
      Sanity is relative. For some of us it's just a distant cousin.
  11. Re:Oddly enough by King+Babar · · Score: 3, Funny
    A doddle to put right, but rather worrying nonetheless.

    So, am I the only one who thinks that some people in the UK must spend altogether too much time sitting around in club chairs drinking and inventing new words and idiomatic expressions that mean nothing but *sound* extremely British, and are thus adopted by the pretentious?

    --

    Babar

  12. I think it's just you. by gerardrj · · Score: 3, Interesting

    I keep a sparse dock of one of my logins and nothing was added to the dock. Nothing was removed or added to my normal login which has about 20 items kept on the dock.
    No new aliases were created on my desktop (Such as for mail, Internet or the like). None of my preferences were overwritten or contradicted.
    My clock stayed at the correct time and date, and my network connection stayed configured manually just the was I had it set. (then again, perhaps my time WAS messed up and the auto-time-set feature reset it before I logged in, I just don't know).

    That said, if there were going to be any inherent problems with the installer, I would likely be the one to find them. I'm running on and old Biege G3/333 that is overclocked (CPU and bus), with 3 monitors (one from internal, two from an ATI 7000/PCI), a USB/Firewire card, a SCSI card, third party everything in the system except the motherboard and power supply.
    Seems to me that if anyone's system broke as a result of the update, that there was something REALLY flakey about the config beforehand, or it is just random coincidence and they are just assigning blame where there really is none.

    --
    Article X: The powers not delegated... by the Constitution...are reserved...to the people
  13. Re:sudo doesn't require NetInfo hacking by punkmanandy · · Score: 2, Informative

    sudo tcsh works better for most people, and sudo -s is the best, as it keeps your evironment variables the same, but you get a root shell.

  14. Re:several machines, no problem by Oculus+Habent · · Score: 3, Funny

    No hacks, no unpublished APIs. The only beta SW running in OS X I have is Navigator (Chimera), Safari, and X11. I leave nearly everything where Apple put it, because it doesn't bother me to do so.

    I'm connecting with an AirPort card. I have Atlanta as the closest city. I have Time Sync and Software Update's Auto-Check disabled. I have one user, who logs in automatically. The user icon is the half of an orange. I had no Sharing services running at the time. I have a single LaserJet 4 specified in my Print Center. I have my root user enabled.

    I use Mail for mail. Address Book for addresses. iCal for a calendar. iTunes for music. Safari for web, with Chimera s backup. Sherlock for some searches, and Text Edit for most of my simple writing. I use Terminla to connect to an HP-UX box at work. I use a VPN connection with Internet Connect sometimes, but not during the update. I have primarily generic US settings.

    My Trash was empty. My battery indicator is set to Percent. I have the Day of Week showing in the Menu Clock. My sound was on. I have the Developer Tools installed, but don't really use them.

    Does it bother me that something changed? Yes. Am I worried about hosing my machine with the next update? No. Have I sworn of Macs forever? Much to Microsoft's dismay, no.

    Why me, then? I don't know. Maybe I wasn't holding my mouth right.

    --
    That what was all this school was for... to teach us how to solve our own problems. -- janeowit
  15. It's like the Y2K bug... by wirelessbuzzers · · Score: 5, Funny

    The cause of all these problems is simple, and I'm amazed that Apple overlooked it. The new version number, 10.2.4, overruns the 11-bit signed integer field that Apple devotes to the version numbers for their operating systems. This causes the system to think it's version -10.2.4, and extrapolating on the rate of Apple software releases allows one to easily calculate the date that this release should have taken place: Version 1.0.0 in 1984 and Version 10.2.3 in 2003 gives version -10.2.4 to be precisely January 1, 1970. The 1969 dates are due to a roundoff error, and only occur in G3s without Altivec support.

    As no version earlier than OS 8 has network time support, the new "old" system does not attempt to update from a network time server. The reverted files and dock icons are simply the computer's attempt to show the files as they exist at the "current" time.

    A patch may take awhile, due to the difficulty of updating all the old system routines that use the 11-bit signed int format.

    --
    I hereby place the above post in the public domain.
  16. Re:Oddly enough by Slur · · Score: 3, Funny

    Quite so. In fact one might say it's a rather unfortunate side-effect of being British. I would venture to say that within that milieu there are shades of subtlety that would be lost on the typical brash overstimulated American, who for the most part has no appreciation for understatement, having beaten his head against life for so long.

    --
    -- thinkyhead software and media
  17. Re:Don't they fucking test these things? by Slur · · Score: 2, Funny

    Of course they tested it, don't have a cow. I've updated several computers over the past couple of weeks and have had absolutely no problems. I took the cautious step of running disk repair on each system before upgrading and then I used the Archive-and-Install method.

    Every upgrade, no matter how trivial, can bring complications. One must be prepared for such an eventuality, and hopefully face inevitable problems with a bit of grace.... or in your case a bit of fucking grace.

    --
    -- thinkyhead software and media
  18. My 12 computers by mj_1903 · · Score: 2, Informative

    My 12 computers (mine and Apple store) have had no problems with the update.

  19. Re:Oddly enough by gidds · · Score: 3, Funny
    [fx: Stares hard at parent message for a while]

    You're complaining about `doddle', right? (Process of elimination.) Okay, it means `something easily done or achieved'. It's a perfectly common* word round our way. Everyone happy now?

    (* in both senses)

    I tell you what: I'll start worrying about writing so that even the simplest Yank can understand me if you Yanks start writing so we can understand, all right?! (I wonder who will have to change the most there...)

    [fx: wanders off muttering about who invented the bloody language in the first place...]

    --

    Ceterum censeo subscriptionem esse delendam.

  20. There ARE problems with this update by Nexum · · Score: 3, Informative

    Hi all,

    Firstly I have to say unfortunately there are inherent problems with this update, and the one about the clock resetting to Jan 1 1970 (plus or minus a few hours depending on your time zone) is absolutely true as I am experiencing it myself.

    It does however only seem to be affecting fual processor G4's though, so that may explain the mixed reaction.

    If you are still in doubt, check Apple's discussion board here where there are a total of 66 replies to my original post complaining of the clock issue (hopefully link will work, if not, check out the OSX area under discussions on Apple.com).

    It seems that a large number of people are having this trouble, and although there is no way I would ever switch to another platform after using OSX, it is disappointing that Apple allows these things through the net.

    Although OSX is vastly superior to Windows XP, I simply can't imagine MS distributing an update for Windows that would have this fundamental effect. I think that Apple should make sure they concentrate also on the mundane routine stuff in checking as well as the super-cool revolutionary stuff they are so uniquely good at (Rendezvous, Bluetooth integration, iApps etc etc).

    Here's waiting for a fix VERY soon.

    -Nex

    --

    This sig has been deprecated.
  21. Updates always have hazards. by NtroP · · Score: 3, Insightful
    I run an OS X box that hosts several commercial domains and is the authoritative DNS for each. I have SQL, PHP, and a dozen other "mods" made to the systems - particularly the httpd.conf file. For the record, I know that I have made changes to the system that are bound to be blown away by an update. That's why I have a backup of all my config files. I also leave stuff where Apple puts it. That's what hard and symbolic links are for.

    This is not your mommy's OS 9 box any more kids. It's a "real" OS with serious power! You can't treat it like OS 9 or even like Windows 98. I noticed immediately that my httpd.conf file had been overwritten and simply copied it back, restarted apache and tested the rest of my system. Other than the downtime to reboot and make the .conf change I had no downtime.

    There are bound to be problems with any update. Not all installations are identical, so there are bound to be unforseen changes. I can't speak to the time problems because I use NTP. It is important that my system has the correct time - not just what my mickey mouse watch tells me.

    Overall, I'm very happy with the update - my system is as rock-solid as ever!

    --
    "terrorism" and "pedophilia" are the root passwords to the Constitution
  22. Other thread lists issues too. by tuxedobob · · Score: 2, Informative

    Those looking for answers here may also want to visit the other thread on this subject.

  23. my dual processor g4 by commodoresloat · · Score: 2, Informative

    did not experience this problem. I did repair permissions right after the update but I didn't notice this problem at all.