Spaces in Volumename? (MacHD) (Macintosh HD)

[proximity]

I’ve only been able to get InstaDMG to compile a complete system – when the created volumename has no spaces, like for exampel: “MacHD”. But If I launch the exact same configuration, but I change:

# This string is the root filesystem name for the ASR image.
ASR_FILESYSTEM_NAME="MacHD"

to:

# This string is the root filesystem name for the ASR image.
ASR_FILESYSTEM_NAME="Macintosh HD"

I get nothing but Kernel Panics. Is this normal? What is the workaround? Do I just make a Launchd script renames my startup volume at first boot?

Launchd script suggestion:

diskutil rename /Volumes/MacHD "Macintosh HD"

[Patrick Fergus]

We used a StartupItem to rename the hard drive:

/usr/sbin/diskutil rename / "Macintosh HD"

It keeps my modifications separate from whatever InstaDMG is assuming about the names of the working volumes. This is part of a payload-free Package, and also provides a convenient way to know if something fubared on the installation during first startup.

– Patrick

[proximity]

Great! Thank you very much 🙂

[larkost]

I don’t know what version you are using, but there are the -m and -n flags that can set the dmg and volume names respectively. If you surround the input with quotes or escape the spaces they should work just fine with that. These have been in there for a while.

[AllanMarcus]

larkost wrote:

I don’t know what version you are using, but there are the -m and -n flags that can set the dmg and volume names respectively. If you surround the input with quotes or escape the spaces they should work just fine with that. These have been in there for a while.

Any change of add the -m to the InstaDMB pdf file? Also, the -n option is jsut document as “name”. There is no way for the user that it’s for volume name; it could jsut as easily have been for dmg name.

Thanks,

Allan

[larkost]

It sounds silly, but I don’t have access to the document that produces the PDF… I will have to talk to Josh and remind him that we need the original document in SVN again.

[Author]

Posts