> Note that old machines of the sort that are susceptible to this > problem are particularly likely to have disks small enough that > carving them up into more pieces is liable to create a usability > problem later.
It seems that in cases of older systems then you have to choose between two problems: 1. Splitting the disk space up may cause future problems due to a lack of total disk space. 2. Failing to split the disk space up will prevent the system from working at all. It seems to me that (1) is the lesser of the two evils, and any system modern enough to not suffer from the cyl>1024 problem will also have a hard drive big enough to deal with losing ~100MB of space to a /boot partition. I'm certainly happy to see a warning that explains what I have to do to fix the problem if an automatic solution is considered too complex. However, the current state of affairs is bad - I upgraded the machine from (fully working) Fedora Core to Ubuntu Edgy and it just plain didn't boot - no warnings that there might be problems or anything. Not a good user experience. I'm a seasoned Linux developer, so it was pretty easy for me to spot the problem, but a normal user would just conclude that Ubuntu is "broken" since another distro has been shown to work on the same hardware flawlessly. -- /boot is on root partition by default https://launchpad.net/bugs/88633 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
