Changes between Version 3 and Version 4 of Ticket #19253, comment 5
- Timestamp:
- Nov 15, 2024, 8:36:30 PM (5 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #19253, comment 5
v3 v4 1 I *think*the issue lies in the way `MountArchivedVisitor` calculates a "score" for each partition, to decide if it should auto-mount it. In `MountArchivedVisitor::_Score(BPartition partition)`:1 I ''think'' the issue lies in the way `MountArchivedVisitor` calculates a "score" for each partition, to decide if it should auto-mount it. In `MountArchivedVisitor::_Score(BPartition partition)`: 2 2 3 3 It assigns +4 "score points" if the `capacity` of a given partition matches the value stored on the `info` BMessage from the settings. 4 4 5 It then assigns ~ +3 points if the deviceName matches.~ +1 if fsName matches, and +1 if blockSize matches. (`deviceName` won't match for partitions on the same disk, but can cause issues if you change driver order on BIOS or when switching from VM to bare-metal).5 It then assigns ~~+3 points if the deviceName matches.~~ +1 if fsName matches, and +1 if blockSize matches. (`deviceName` won't match for partitions on the same disk, but can cause issues if you change driver order on BIOS or when switching from VM to bare-metal). 6 6 7 7 If I'm reading things right, a "score" value >= 6 means the partition gets auto-mounted. 8 8 9 In my case, "Haiku32" and "Haiku64" have the exact same capacity, ~ and they are on the same device~ and are BFS formated, with same block size, thus they will get always auto-mounted together. Same with my "Data1"/"Data2" and "Temp1"/"Temp2" partitions.9 In my case, "Haiku32" and "Haiku64" have the exact same capacity, ~~and they are on the same device~~ and are BFS formated, with same block size, thus they will get always auto-mounted together. Same with my "Data1"/"Data2" and "Temp1"/"Temp2" partitions. 10 10 11 11 ----