Skip to main content

Change name of mounted volume on Mac OS X

diskutil rename /Volumes/Volume NewVolName

Some others:
Set Bonjour Name
sudo scutil –set LocalHostName NewName
Set Sharing Name
sudo scutil –set ComputerName NewName

Comments

  1. Does this affect the data on the volume? I've got a new iMac with dual drives. The second drive is mounted at /Volumes/Macintosh HD 2. This is causing fits with some Unix stuff. Don't like the spaces in the name of the volume. Would like to rename it but don't want to risk losing the 200GB's of data on that drive.

    ReplyDelete
  2. Hmm, I don't believe it does.
    Also, you can achieve the same result via the GUI:

    Right click on the volume
    Either click 'rename' or click get info and then change the name in the 'name and extension' edit box.

    ReplyDelete
  3. If your Home directory is on the volume where you're changing name, then you can not log in again. You need to tell OS X the new path.

    Open System Preferences -> Users & Groups and click the lock in the lower left corner to enable changes.
    Then right click (Ctrl+click) on your account and choose Advance Options... To the right of the label that says Home directory, you click on Choose... and select your Home directory (will be located under your new name).

    If you fail to do so before rebooting, you have to open OS X in recovery mode (Command+R while booting). There you can open terminal in the menu at the top and rename your volume back to what it was before. Use diskutil rename /Volumes/Volume NewVolName

    ReplyDelete

Post a Comment

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or...

Remove field code from Word document

e.g. before submitting a MS, or hand manipulating some formatting because Word does things (like cross-references) so half-assed [from here ] Select all the text (CTRL-A) Press Ctrl+Shift+F9 Editing to remove anonymous comments that only contain thanks. I really appreciate the thanks, but it makes it harder to find comments that carry pertinent information. I'm also going to try and paste informative comments in the body of the post to make them easier to find.

h5py and multiprocessing

The HDF5 format has been working awesome for me, but I ran into danger when I started to mix it with multiprocessing. It was the worst kind of danger: the intermittent error. Here are the dangers/issues in order of escalation (TL;DR is use a generator to feed data from your file into the child processes as they spawn. It's the easiest way. Read on for harder ways.) An h5py file handle can't be pickled and therefore can't be passed as an argument using pool.map() If you set the handle as a global and access it from the child processes you run the risk of racing which leads to corrupted reads. My personal runin was that my code sometimes ran fine but sometimes would complain that there are NaNs or Infinity in the data. This wasted some time tracking down. Other people have had this kind of problem [ 1 ]. Same problem if you pass the filename and have the different processes open individual instances of the file separately. The hard way to solve this problem is to sw...