Currently, the kernel refuses to re-read partition table> pretty annoying -- in order to change
from a drive which has usage count > 0. Motivation for
this is pretty clear ,
to reboot the machine.Yes, very interesting thing. While one will destroy its part.table, he can not see until reboot, heh. But there were days, when grub used to install itself on XFS partition (XFS isn't FAT-boot-record compatible) *silently*, but nothing was wrong to me : it's linux-gnu ;D
I wonder if it's possible to actually read the new partitionIMHO you've wrote much more here, then just for not-so-useless-solution, that i've wrote above, unless you want another wind0s clever-heuristic with patches from happy users to lkml: <http://article.gmane.org/gmane.linux.kernel/437388>
table, compare it with previous, and apply changes IF they
don't conflict with currently open partitions? Say, if we
have sda1 and sda2, sda1 is open/mounted, and new partition
table does not have sda2, but sda1 is unchanged - it's pretty
safe to apply new partition table, without affecting mounted
sda1. Ditto for adding new partitions.
Yes, a line should be drawn somewhere - say, if sda3 was
mounted, and we removed unused sda2, but sda3 (which becomes
sda2 with new table) is intact, we should not apply new
table.
Is it possible to implement such a feature? I mean, is it
easy to know which *partitions* (subdevices?) of the whole
device are currently in use, as opposed to the whole drive?
Thanks.
/mjt