David Anderson

The gdisk command shows my GPT has three partitions. I wish to delete the last partiton shown and add the partiton back in with different values. However, the d command will not allow this. See the output below. sudo gdisk /dev/disk0 GPT fdisk (gdisk) version 1.0.8 Warning: Devices opened with shared lock will not have their partition table automatically reloaded! Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Command...

I encounter a problem where if I ran the command sudo ./refind-install --usedefault /dev/disk0s4 again after removing install from showtools. Here a message is displayed stating refind.conf will not be changed, but is in fact changed. In othe words, install is again added to refind.conf. The part of the script where the problem exist is given below. if [[ -f "$InstallDir/$TargetDir/refind.conf" ]] ; then echo "Existing refind.conf file found; copying sample file as refind.conf-sample" echo "to avoid...

Joevt: I looked an your script to mount a partition. I would not make the mount point in the /Volumes folder. Instead, I would keep using the /tmp/refind_install mount point, when a volumn needs to be mounted. I am not sure why you felt the need to loop until a directory does not exist. Perhaps this is because your script uses the /Volumes folder? When using the --usedefault option, I found refind-install allows installations to mounted volumes after making the following changes. First, I replaced...

Your script has many flaws. Below I outline one main flaw. The following line determines if the mount point exists as a directory. while [ -d "$mountpoint" ]; do Later, the following line creates the directory. sudo mkdir "$mountpoint" 2> /dev/null Finally, the next line mounts the volume. sudo mount$mounttype "/dev/$slice" "$mountpoint" The problem is the script uses the /Volumes directory. There is no guarantee some other processes will not also be accessing the /Volumes directory. In other words,...

After some thought, I now realize the mount command in the refind-install script prevents the two different users from executing this script simultaneously. We both have been discussing how to install to a volume that is already mounted. Doing so would be a bad idea. So, having to unmount before running the refind-install script is the correct proceedure.

After some thought, I now realize the mount command in the refind-install script prevents the two different users from installing rEFInd simultaneously. We both have been discussing how to install to a volume that is already mounted. Doing so would be a bad idea. So, having to unmount before running the refind-install script is the correct proceedure.

After some thought, I now realize the mount command in the refind-install script prevents the two different users from installing rEFInd simultaneously. We both have been pursuing how to install to a volume that is already mounted. Doing so would be a bad idea. So, having to unmount before running the refind-install script is the correct proceedure.

joevt: Your script has many flaws. Below I outline one main flaw with the mountpartition funciton. The following line determines if the mount point exists as a directory. while [ -d "$mountpoint" ]; do Later, the following line creates the directory. sudo mkdir "$mountpoint" 2> /dev/null Finally, the next line mounts the volume. sudo mount$mounttype "/dev/$slice" "$mountpoint" The problem is the script uses the /Volumes directory. There is no guarantee some other process will not also be accessing...