I use binchunker to convert .bin/.cue files to a single .iso file on my Mac. You can obtain binchunker via Homebrew or Macports.
Here's some more info from the manpage:
bchunk - CD image format conversion from bin/cue to iso/cdr
bchunk [-v] [-p] [-r] [-w] [-s] <image.bin> <image.cue> <basename>
The accepted answer only works when the NFS server allows connections on non-reserved ports (i.e. >1024).
The exports man pages say it:
exportfs understands the following export options: secure
This option requires that requests originate on an Internet port less
than IPPORT_RESERVED (1024). This option is on by default. To turn it
off, specify ...
OS X uses diskarbitrationd which discovers new storage devices and probes them for mountable filesystems. The Disk Arbitration framework handles notifying applications of disk mount/unmount events, and allows them to influence whether a volume is mounted or not.
Consult the man page for diskarbitrationd for very limited further information; for example, ...
I have spent quite a bit of time figuring out automounts of NFS shares in OS X...
Somewhere along the line, Apple decided allowing mounts directly into /Volumes should not be possible:
/etc/auto_master (see last line):
# Automounter master map
+auto_master # Use directory service
/net -hosts -nobrowse,hidefromfinder,nosuid
In Finder, press cmd + k and enter the path to the NFS server/share:
For me this mounted as /Volumes/users-1 (but I already had /Volumes/Users mounted).
iMac21:~ user$ df -h /Volumes/users-1
Filesystem Size Used Avail Capacity iused ifree %iused Mounted on
192.168.7.5:/nas/users 5.4Ti 4.8Ti 292Gi 95% 261121 366027775 0% /...
You may want to consider using the NFS Manager application to help you locate and disable the NFS automount. You should refer to this section of the manual for assistance.
The mount name /CIFS and the lack of NFS information indicates you may be running Sharity. Check if it's installed, using Spotlight. If it is, you can find the documentation here.
To prevent a volume from automatically mounting you need to know the filesystem type and either the volume name or volume UUID. This information can be found by using the Terminal application command diskutil info name, where name is the volume name. For example, volume names can be found under Devices in the sidebar of a Finder application window.
On my ...
I ran across this today which is one way to do it.
In summary for Mountain Lion:
Edit the file /etc/auto_master
Within add /- auto_smb
Within add /Volumes/mount_point -fstype=smbfs,soft ://user:pass@smbserver/share
The author goes onto mention a second method using the vifs command, but I've never tried that one and it seems to do ...
Mounting the sparsebundle can be accomplished via command line using the 'hdiutil' command. You can also create a shell script that will perform this action. This script assumes that the image is located at /Users/somebody/Image.sparsebundle, and that the passphrase used to encrypt the image is "testpass"):
# This script mounts the disk image ...
I think I can get you started, but using terminal commands, which you said you'd prefer to avoid. Apologies, but it might give you a starting point. All of the following you could put in a bash script and run as a login item.
You'll need to first share out the target drive(s) (MyBook in the examples below) using file sharing (System Preferences > Sharing > ...
I had the same problem with CIFS-mount, x-browser… That happened because I tried Sharity 3 and 'deleted' it by putting the icon in the trash, like Mac users usually do. :) But the program was still installed and put the CIFS icon on the Desktop every day.
I solved it using the following Terminal command:
Use AppleScript, but do not specify the user name or password.
In my case, none of the suggestions that I found online worked perfectly.
I had several AFP volumes that I wanted to mount automatically. Following the advice given here and elsewhere, the obvious solution seemed to be an AppleScript file with something along these lines:
I'm running into the same problem than @ndejay but the cause may differ sightly.
I'm using NFSv3 and my Autofs maps were working on OS X 10.5 to 10.8 :
/mnt -fstype=nfs,nfsvers=3,proto=tcp,resvport myserver:/share
On Mavericks it works only from the command line :
mount -t nfs -o nfsvers=3,proto=tcp,resvport myserver:/share /mnt
With a little debugging ...
Tetsujin and user3439894's comments and observations prompted some testing.
Turns out, there is more than one UUID when you look at drives and partitions and the 'diskutil list' command doesn't report the UUID that needs to be used in the vifs/fstab commands.
root %> diskutil info disk1 | grep -e UUID
Shows that there are Volume, Disk / Partition, ...
save this as ~/Library/LaunchAgents/cifs.plist:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
A little late, but hopefully this helps anyone else searching (since the rest of the answers here are useless!)
Quoting https://discussions.apple.com/message/29744735#29744735 -
Since at least Panther and through to El Capitan, AutomountDisksWithoutUserLogin needs to be set to true (1) in /Library/Preferences/SystemConfiguration/autodiskmount.plist, then ...
I found that the automountd service wasn't loaded on my machine (running 10.10 Yosemite).
$ sudo launchctl list | grep -i auto
84878 0 com.apple.autofsd
- 0 com.apple.preferences.timezone.auto
- 0 com.apple.automountd
Restarting autofsd and automountd and then rerunning automount -vc has made it work.
sudo launchctl unload /System/Library/...
OK, I figured it out. The keys in the auto_afp file are paths that are relative to the path specified in the top-level auto_master file.
So if your /etc/auto_master has: my/global/mount auto_afp
Then your /etc/auto_afp should have: point -fstype=....
Finally to get visibility into what automountd is doing, add AUTOMOUNTD_TRACE=2 to /etc/autofs.conf, ...
It sounds like you might have dragged it out of the Sidebar on your Finder Window. Try this: plug the drive back in, and then hit Cmd ⌘ Shift ⇧ C to go to your Computer view. You should see all your connected drives there; just drag the drive you want back to the Sidebar.
It appears that the syntax must use single spaces, not tabs, to be recognised by the system.
This would fall in line with many command line processes; the only exception that springs to mind is the hosts file, which can use any amount of whitespace.
That would make the correct syntax
UUID=uuid_of_partition2 none hfs rw,noauto
These are all great (and correct) answers!
I thought I'd share a small script/utility that I use to make this easier.
I've got this no_automount file executable in my ~/bin/ directory. (Don't forget to chmod +x it!)
# Usage: no_automount /Volumes/My\ Disk
diskinfo = `...
Number one, something might be wrong with your VPN, because everything should work as if you were physically in the office. You might want to check that.
Number two, I assume the remote machines use the wrong IP address when connecting to the servers. And if they are actually successful with some of the tricks you mentioned, you might have a few security ...
afaik, fstab doesn't exist by default. You have to create one, first time.
From your linked instructions...
7) Edit (or create) an fstab file by typing the following and pressing enter:
Will do precisely that, edit - or create - an fstab file.
Once you've got it set up, it ought to work as expected. I have mine set with ACLs so it will ...
The volume is mounted automatically again.
I never did find out how Mac OS X decides which volumes to mount and which not. But whatever it is, Mac OS decided to mount the volume again. Apparently the solution is to reboot until it works.
With reference to the linked question (the comment there from the opening poster here) …
Unlocking the Core Storage LV, importing the ZFS pool and mounting the ZFS file system
I know of no way to force Mountain Lion to use the Core Storage volume encryption key (VEK) in a way that will allow the ZFS pool and file system (based on the Core ...
You can use the Directory Editor that is part of Directory Utility (in /System/Library/CoreServices) to add a new automount record. I recommend using the existing record as a template for your new mounts.
The image above references the Mounts container in the /Local/Default node. You would obviously want to choose the LDAP node that represents your Open ...
The best thing I can come up with, is a script that will run at boot, and will check whether each Apple_HFS TYPE of volume (disk*s*) is mounted. When the volume isn't mounted, try to repair and mount the volume.
Script commands explained
List local HFS volumes
The diskutil list command is used to retrieve all local volumes that contain an ...
OK, what follows is an adapted version of a shell script that I have running on my local Macs to auto mount certain AFP volumes when I'm at home. You'll need to adjust the mount_nfs line, enter the MAC address for your home router, and adjust the volume name for the mount (if you want).
I have this script triggered to run every 5 minutes via a launchd file ...