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
Labels:

Comments

  1. AnonymousJune 20, 2011 at 9:48 AM

    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. Kaushik GhoseJune 20, 2011 at 10:25 AM

    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. dotnetCarpenterFebruary 11, 2013 at 7:43 PM

    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...
Post a Comment
Read more

Store numpy arrays in sqlite

Use numpy.getbuffer (or sqlite3.Binary ) in combination with numpy.frombuffer to lug numpy data in and out of the sqlite3 database: import sqlite3, numpy r1d = numpy.random.randn(10) con = sqlite3.connect(':memory:') con.execute("CREATE TABLE eye(id INTEGER PRIMARY KEY, desc TEXT, data BLOB)") con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", sqlite3.Binary(r1d))) con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", numpy.getbuffer(r1d))) res = con.execute("SELECT * FROM eye").fetchall() con.close() #res -> #[(1, u'1d', <read-write buffer ptr 0x10371b220, size 80 at 0x10371b1e0>), # (2, u'1d', <read-write buffer ptr 0x10371b190, size 80 at 0x10371b150>)] print r1d - numpy.frombuffer(res[0][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] print r1d - numpy.frombuffer(res[1][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] Note that for work where data ty...
Post a Comment
Read more