Theodore, thanks for the reply. And I think you have nailed part of the problem, if it's been tagged wrong. Yes, I understand that the problem could be hard if it were handled solely by a program. But an interaction between a program and a user might be possible, similar to the way the manual partitioning is done. Plus, a search for an /etc/fstab file shouldn't be that difficult to do. I know, I'm not a programmer (though I have done some limited shell scripting in UNIX SVR4, about 20 years ago, as well as some limited Lisp programming). It just seems to me that a conditional search would rule out many types of partitions. Just as equally, the default would be for the boot sequence to flag the problem, with a potential fix, and/or a "comment it out" choice for the user (defaulting to "comment it out"). That could avoid the confusion, and the image of our distro that such a problem creates.
Is there some way that an individual can alert the right people, in this case, to what's happening? I'm too new to membership in Ubuntu to know the right people to address, or to have made such contacts. But if I'm going to be going around with an Ubuntu-Arizona golf shirt, trying to interest people in trying our distribution, then I don't want it reflecting poorly on Ubuntu because this bug exists. Thanks again, Craig -- fsck Unable to resolve UUID https://bugs.launchpad.net/bugs/106209 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
