[MacPorts] #26538: Filesystem errors when installing ports

[MacPorts]

#26538: Filesystem errors when installing ports
--------------------------------+-------------------------------------------
 Reporter:  raramayo@…          |       Owner:  macports-tickets@…                   
     Type:  defect              |      Status:  new                                  
 Priority:  Normal              |   Milestone:                                       
Component:  ports               |     Version:  1.9.1                                
 Keywords:                      |        Port:                                       
--------------------------------+-------------------------------------------

Comment(by raramayo@…):

 Replying to [comment:7 ryandesign@…]:[[BR]]

 > I am aware of what NetBoot is, but have never used it, and have not
 heard of anyone else using it with MacPorts. Perhaps that doesn't work.
 Can you try without NetBoot -- just booting from, and having MacPorts
 installed on, the internal hard drive?

 People,[[BR]]

 I was looking into this. I believe that this strange behavior is related
 not to NetBoot, but to the fact that the computers that are running into
 trouble they all have "Mobile Accounts" and therefore are linked to an
 "Network Account Server" In other words they all listen to an LDAPv3
 server.[[BR]]
 Something FUNDAMENTALLY different happenes when computers are "Mobile
 Accounts Active" For example, on a regular system, on the terminal you can
 do a "sudo su" and get the "sh-3.2#" prompt. However on these computers if
 you type "sudo su" you are prompted for your passwd and then the system
 says: "su: sorry"[[BR]]


 Now if I issue a command like: "sudo something" the system asks for passwd
 and then acts normally.[[BR]]


 In most of the "complains" I got from MacPorts ports during installation
 they all mentioned having problems with "sudoers file"[[BR]]


 In addition, when the commands were repeated, most times they went fine
 the second time.[[BR]]


 I am going to ask a student of mine to reformat and re-install the OS in
 one machine and then test MacPorts without activating "Mobile
 Accounts"[[BR]]

 Very Mac users use the power of mobile accounts and that is why, I
 suspect, these behaviors went undetected[[BR]]


 I should say that I made the same installation on my laptop and on my
 server and in both cases MacPorts behave as expected

 I have upgraded XCode to the latest version, but I doubt this was the
 culprit


 Thanks for your help/advice

-- 
Ticket URL: <https://trac.macports.org/ticket/26538#comment:8>
MacPorts <http://www.macports.org/>
Ports system for Mac OS