• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: A warning about Mac OS X 10.3.5 + NFS
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A warning about Mac OS X 10.3.5 + NFS


  • Subject: Re: A warning about Mac OS X 10.3.5 + NFS
  • From: Justin Walker <email@hidden>
  • Date: Wed, 11 Aug 2004 08:44:26 -0700

On Aug 11, 2004, at 8:05, j o a r wrote:


On 2004-08-11, at 16.53, Justin Walker wrote:

Odd. On my 10.3.5 system, as well as my 10.3.4 system, "/automount" is a real directory. There is no 'automount' in /private.

I have both a /automount and a /private/automount, and they are different directories. In particular, this is where my home directory is mounted:


[protoss:~] joar% pwd -P
/private/automount/t3/dynamic/home0/joar

Weird, but then, I don't do automounting (coming from a long history of NFS fire drills...).


It could be that automounted directories actually get mounted under /private, but that flies in the face of the purpose for "/private". FWIW, this directory is not supposed to be referred to in polite society. It's there so that one can set up a network-wide root, but have per-workstation directories for mutable content (stuff that lives in /etc/, and /tmp, for example). That way, the local disk is mounted under "/private", and has the "real" (i.e., local) copies of these directories.

There is no good reason to put mounted home directories under "/private", because they are already "private".


And this console entry is what gave me the idea that Xcode strips out the leading "/private":

2004-08-11 14:46:00.684 Xcode[1142] Unable to index /automount/t3/dynamic/home0/joar/test/main.m: No such file or directory

Which leads me to suspect that the "/private/automount" directory is somehow spurious. Anyone know how it gets into the act?


I welcome any suggestions for workarounds so that I can avoid having to
reinstall my OS to revert back to 10.3.4...

Can you revert to a previous "dot" release? I thought (without ever checking) that once a release is superseded, it is not available via Software Update.

You're right, and that's what makes it so difficult - I would have to scratch my current OS, reinstall 10.3 from the CD and then manually upgrade it to 10.3.4 (can't use SU as it would suggest 10.3.5).

If so, that's good to know. I wasn't aware one could do this "manually".


Regards,

Justin

--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Semantics | "Weaseling out of things is what
| separates us from the animals.
| Well, except the weasel."
| - Homer J Simpson
*--------------------------------------*-------------------------------*
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.



  • Follow-Ups:
    • Re: A warning about Mac OS X 10.3.5 + NFS
      • From: Chris Ridd <email@hidden>
    • Re: A warning about Mac OS X 10.3.5 + NFS
      • From: j o a r <email@hidden>
    • Re: A warning about Mac OS X 10.3.5 + NFS
      • From: Godfrey DiGiorgi <email@hidden>
References: 
 >A warning about Mac OS X 10.3.5 + NFS (From: j o a r <email@hidden>)
 >Re: A warning about Mac OS X 10.3.5 + NFS (From: Justin Walker <email@hidden>)
 >Re: A warning about Mac OS X 10.3.5 + NFS (From: j o a r <email@hidden>)

  • Prev by Date: Compile
  • Next by Date: Re: Building a class hierarchy in Xcode
  • Previous by thread: Re: A warning about Mac OS X 10.3.5 + NFS
  • Next by thread: Re: A warning about Mac OS X 10.3.5 + NFS
  • Index(es):
    • Date
    • Thread