Am 23.03.2010 um 16.14 schrieb Karl Kuehn:
On Mar 23, 2010, at 6:48 AM, Rudolf O. Durrer wrote:
Even then, as well in the volume folder of the Snow Leo partition
as in the former Leo partition, the blocking folders (ex Aliases)
ar there
More than strange....?
I don't know, but maybe this is a misunderstanding on your part.
The items that are normally in /Volumes are not aliases. They are
folders that are the mount-points for volumes. As part of the auto-
mount process (how most volumes are mounted) the folder gets created
and then the volume gets mounted to it. On the other end of the
process the automounter unmounts the volume, then destroys the folder.
It is important to understand this because if a folder gets created
in /Volumes outside of the automounter's control (ie: you just
create it yourself), or somehow one of these folders somehow does
not get removed when it should (automounter crashes), then there is
no process that is going to go back and erase them, the will just
sit there. The automounter will rename mounts to get around them,
and you will continue to work, but with these (hopefully) empty
folders sitting there.
Could this be what you are looking at?
I know, and happily agree, that those items are mount points. For
easyness, I just described their phenomenal appearance, and that is
that of an alias: icon like an alias, behaviour like an alias (think
of cmd-R), Kind is "alias file".
The important thing is, that they should normally be deleted ones the
respective volume is unmounted.
In rare cases, I have seen, (mostly for reasons of an
"mismanipulation"), the mount point continued to exist as a normal
folder although the corresponding volume was not anymore existent.
Such a "mismanipulation" for example is the sudden unplugging of a FW
or USB device, which is mounted AND opend AND an item of it is opened.
That may then lead to that phenomena, Macs R We describes in his mail,
or may even block the later mounting of a volume of the same name.
But that all mountpoints stay as folders behind after a normal shut
down is not that what I would call a normal behaviour.
I first thought of some FW400/800 device compatibilities to be the
culprit, but now I more expect the problem to be related to the drive
partition of MacMini, because the problem observed does not regard the
(several) mounted volumes on the USB drives nor those of the FW 400
external, but only those of the partitions of the MacMini drive. The
main reason: when I start only from MacMini, I do not have any problem
(although a short check in firewire modus shows that the mount points
have again "stayed behind". The problem only arises whe I switch the
boot volume from one device to another one (ie starting from external
LaCie FW400).
A closer look to the "not deleted" mount points shows that only all
non bootable volumes of the MacMini drive stay left as folders with
the access rights as --x--x--x. The mount point, on which the Mac
booted before still has a phenomenal appearance of an alias file
(including the former boot volume name), still is a mount point, but
this time for the new boot volume.
That may be the REAL problem, not the "not deleted" mountpoints/
folders: This mountpoint has the wrong name and targets another
volume. When switching back to boot from original volume, that mount
point cannot be recreated.
For precision reasons:
The MacMini volumes shall be called M1 to M4, with M1 bootable.
The external FW400 volumes are E1 to E11, with E1 and E3 bootable
The USB volumes are U1 to U7 (not bootable).
The first boot is from M1.
After the second boot from E1, the itens in the volumes folder of M1
are: M2 to M4 as folders, M1 as mountpoint to E1.
The third boot is from M1 again. The itens in the volumes folder of E1
are: M2 to M4 as folders, E1 as mountpoint to M1.
Uups, was that too long???
_______________________________________________
MacOSX-talk mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/macosx-talk
