Quote:
No, indeed you did not say that

Because you were not clear, i opted for the first sensible thing that popped into mind when you talked about "Your boot device is first of course", which imho is the device from which grub was started.

Quote:
fwiw and afaik such an option is already in place

Great, so now i need to provide a boot device everytime i (re)boot my native AROS box ?

Look, we can play this cat-and-mouse game forever . I have about another dozen scenarios in which that option will not solve all the problems one could encounter. In fact, that is exactly the point i was trying to make

Quote:

Did not say so. The one specified as boot device is your first device.
(in grub "bootdevice=")

There seems to be problems in both Wanderer and the device drivers.

Aros seems to have trouble ejecting volumes. Not sure if Wanderer keeps showing the icon even though the system has no such volume, or if it has something to do with the device drivers.

AHCI is a bit more troublesome as it seems to be unable to query the sense data from ATAPI device (only ATA devices), I might be totally wrong though.

Quote:
Ah, and you know which one that actually is ?

Quote:
Ok, so the device from which grub was loaded boots first. Glad that we sorted that out

Quote:
Close enough

Yes, this behaviour also happens for me when i insert twice the same pendrives models (or exchanging one with the other). Pendrives are exact same brand, same size, same label.

It seems that issues occur more often when Dopus4 is accessing or has accessed the pendrive. Always closing dopus before inserting/removing usb pendrives seems to show (more) consistent behavior for me.

Quote:
AROS seems to show something similar behavior for me. When inserting same pendrives as described above, AROS cannot distinquish between label names (causing the icon error as you described), but instead a number is used to decribe the unit name (serial id ?). But better verify, as i've not experimented much.

fwiw: if i do the same on a hub then AROS get really confused. On removal of the first and insertion of the second pendrive, the hub seems to reset completely and causes other attached devices to stop functioning. From then on poseidon shows popups all wrongly e.g. when i remove + insert keyboard, it recognizes the insertion of the pendrive + removal of keyboard but not the KB insertion. This behavior appears to differ on different setups, and worked too confusing for me (so in case of troubles i always remove hubs as that seems to behave more consistent).

There are things I don't like in Wanderer, for example if I remove a USB stick the icon still remains. It should not show it when removed. Also when installing Aros the icon still remains and I get an extra icon without an icon bitmap but only the name... I'm a bit tipsy at the moment but that what I recall.

fat-handlerer should not look for a disk label and assume it's the same volume, instead it should check if the device behind it is the same we are checking against.

With Poseidon some pseudo random ID's could be generated based upon the vendor and device ID, Poseidons devices internal structure address etc.

I remember that the original Amiga OS did not rely on the disk label, but it differentiated the volumes somewhere else.

Your boot device is first of course, so the partitions on your harddisk are mounted as "System(2)" and "C(2)" .

When you boot from your harddisk it is the other way round.
Well, at least thats the way it should be
So the only directive necessary is "boot device fist".

@cybergorf
Let's take an example.

I have two ntfs/fat32 drives in my computer, one labeled System: and the other labeled C:

Now, i insert a AROS formatted pendrive on which i installed Icaros and boot from that. Guess what happens

it's not that easy to make the right decision.

Could mounting do something like:

If device "name" exists
Newdevice is "name(2)"
else
Newdevice is "name"

Ok, something smarter should be in place for more than 2 devices with the same name...

Thanks, it is bit of a bummer though...