Without having followed this thread, wouldn't the whole procedure you
describe also work with
1. Open a terminal
2. type 'sudo passwd root'
3. Enter the current users password (to allow for the sudo-command)
4. Enter the new root password (twice)
This should work under all versions of MacOSX.
Working with sudo is only safer if you have an appropriate /etc/sudoers
file restricting rights to specific tasks. Having a users allowed to do
anything root can do does not make your system any safer.
Institut fuer anorganische Chemie
GPG Key ID = A46BEE1A
On Tue, 29 Apr 2008, Andreas Förster wrote:
> A few month's back, and a few moments before almost throwing my Powerbook out
> the window, I enabled the root account, as officially described
> How to enable the root user
> Mac OS X 10.5 or later
> 1. From the Finder's Go menu, choose Utilities.
> 2. Open Directory Utility.
> 3. Click the lock in the Directory Utility window.
> 4. Enter an administrator account name and password, then click OK.
> 5. Choose Enable Root User from the Edit menu
> 6. Enter the root password you wish to use in both the Password and Verify
> fields, then click OK.
> Mac OS X 10.4.x or earlier
> 1. Click the Finder icon in the Dock.
> 2. From the Go menu, choose Applications.
> 3. Open the Utilities folder.
> 4. Open the NetInfo Manager utility.
> 5. Click the lock in the NetInfo Manager window.
> 6. Enter an administrator account name and password, then click OK.
> 7. For Mac OS X 10.2 and later, choose Enable Root User from the Security
> 8. For Mac OS X 10.0 and 10.1, choose Security from the Domain menu, then
> Enable Root User from the submenu.
> 9. If you have not previously set a root password, an alert box may appear
> that says "NetInfo Error," indicating that the password is blank. Click OK.
> 10. Enter the root password you wish to use and click Set.
> 11. Enter the password again for verification and click Verify.
> 12. Click the lock again to prevent changes.
> Why working with sudo is safer than working as root is not clear to me.
> After all, the danger is not in root but in the uneducated user. If you're
> paranoid, you can keep using sudo until you get stuck and then switch to
> Patrick Loll wrote:
>> 1. I was sourcing /sw/bin/init.csh, so that wasn't the problem...but:
>> 2. I did find the problem (at least for the precompiled version from UC
>> Santa Cruz): For some reason "sudo ccp4i" gave the error message, but just
>> "ccp4i" (without the sudo) worked OK. (Although I thought the first time
>> you launched ccp4i you were supposed to do it using sudo...??). Anyway,
>> I'm good (although peeved at my continuing inability to master sudo. I
>> miss living on the edge with root).
>> 3. I didn't try to debug the binaries I got from the ccp4 site, since I now
>> have a working package. However, Iain Kerr kindly provided this info,
>> which may prove useful to other small brains out there:
>>> ccp4.setup is in ccp4-6.0.2/bin...it used to be in include..is that your
>>> problem ?
>>> Also, there's no ccp4i folder....the ccp4i binary is in bin/ also.
>> Note to the long-suffering folks at the secret underground world
>> headquarters of ccp4: Small brain or no, I spent a lot of time looking
>> around for some clue as to how to complete the install for the ccp4
>> package, to no avail; a README file to accompany the installer would not be
>> On 25 Apr 2008, at 4:56 PM, William Scott wrote:
>>> You need to run
>>> source /sw/bin/init.sh
>>> if you use bash or zsh
>>> source /sw/bin/init.csh
>>> if you use tcsh.
>>> this will automatically set up the environment variables and then it will
>>> do what you want it to (which is to set up the ccp4 environment according
>>> to whichever shell you might be using).
>>> On Apr 25, 2008, at 1:19 PM, Patrick Loll wrote:
>>>> 1. I tried to install Bill Scott's precompiled ccp4 on an intel mac
>>>> running OS X 10.5. When attempting launch ccp4i, I receive this error
>>>> /sw/share/xtal/ccp4-6.0.2/ccp4i/bin/ccp4i: line 4 /bltwish: no such file
>>>> or directory
>>>> Typing "which bltwish" returns /sw/bin/bltwish, which jibes with the
>>>> definition of $CCP4I_TCLTK, so I'm not sure where the problem is...
>>>> 2. Pfui. So next I tried jettisoning the apt-get installation, and
>>>> instead used the installer downloaded from the ccp4 site
>>>> (ccp4-6.0.2-osx-i386.dmg.gz). This goes swimmingly, until I actually try
>>>> to do something. Commands like "ccp4i" or "mtzdump" aren't recognized,
>>>> so I go looking for the ccp4.setup file; but it's not there. Huh? Also,
>>>> there's no folder named ccp4i, even though this install is supposed to
>>>> include it...
>>>> It's Friday, and I'm at the nadir of my weekly brain function, so perhaps
>>>> some kind soul will tell me where I'm going astray.
>>>> Patrick J. Loll, Ph. D. Professor of Biochemistry &
>>>> Molecular Biology
>>>> Director, Biochemistry Graduate Program
>>>> Drexel University College of Medicine
>>>> Room 10-102 New College Building
>>>> 245 N. 15th St., Mailstop 497
>>>> Philadelphia, PA 19102-1192 USA
>>>> (215) 762-7706
>>>> [log in to unmask] <mailto:[log in to unmask]>
>> Patrick J. Loll, Ph. D.
>> Professor of Biochemistry & Molecular Biology
>> Director, Biochemistry Graduate Program
>> Drexel University College of Medicine
>> Room 10-102 New College Building
>> 245 N. 15th St., Mailstop 497
>> Philadelphia, PA 19102-1192 USA
>> (215) 762-7706
>> [log in to unmask] <mailto:[log in to unmask]>
> I am not stupid. I have read several books.
> Salman Rushdie - Midnight's Children