On Tue, 2006-08-08 at 11:45 -0600, Ashley M. Kirchner wrote: > In a way it doesn't really matter since they're still mounted > correctly (besides I've already changed them and removed the '1', as > well as fix grub.conf too), but I'm just wondering WHY it does that. I've seen this too, and always assumed it was due to a label named "/boot" already existing, and it isn't bright enough to notice "Oh, that's the one I'm gonna destroy and reformat" (but I don't actually know anything, just a guess). Wit till you try to install suse on the same machine and tell it to mount your old partitions - suse now believes that non-alphanumeric characters are illegal in disk labels, so it conveniently relabels your disks for you (which is quite a surprise when you try to reboot fedora again - at least one of the suse test versions did this to me, don't know if they improved it in the release since I stopped telling the installer to mount the partitions and just edited the fstab by hand after the install :-). -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
