Daniel B. wrote:
Levi Waldron wrote:3. after changing your partition table, you really do have to reboot - at least this is my best guess as to what the problem was.Sometimes you can avoid the need to reboot: If you can unmount every other partition that is on the disk whose partition table you are modifying, then when you write the partition table with fdisk or whatever, the kernel can re-load the partition table and you won't get the message about needing to reboot for the changed partitioning to take effect.I wondered if something like that were the case.Of course, that doesn't work for the disk containing your root filesystem partition (because you won't be able to unmount that partition because it's in use), but it can save rebooting if you're repartitioning a different disk.How about doing a mount -o remount? There might be some work-around.But here's a question: Why can't the kernel handle some types of changes to a partition table (e.g., a new partition) while some partitions are mounted?I can think of two reasons: swap and cache.
OH, another one... The NAMES of the partitions may change.
What was, e.g. hda2 may become hda4.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
