On 01/01/2017 01:01 PM, Mayavimmer wrote:
On 01/01/2017 18:39, Michael Schwendt wrote:
On Sun, 1 Jan 2017 11:23:27 -0500, Matthew Miller wrote:
On Sun, Jan 01, 2017 at 10:10:55AM +0100, Mayavimmer wrote:
I tried to do an identical second install on the same machine, but the
installer Anaconda gives an error about being unable to set a root
partition.
This isn't _forbidden_, but it also isn't something we test offically —
and in fact I'm not sure if anyone has actually tested it ever.
I do manual installs like that regularly. Hence the earlier requests
for details.
The original post doesn't give enough details. I could have answered
"yes" to the $subject, and yet there might be installation scenarios
where the installer fails. More details needed!
As soon as I can. I already gave some details in the other sister
threads yesterday.
So, while I don't see why it couldn't be made to work, I also am not
surprised to hear it doesn't.
It's the opposite here. I'm surprised manual partitioning would fail. If
you point the installer at usable partitions for / and /boot, why would it
fail?
Same exact sentiment, sir. It's ok if the poor little AI in the
installer can't hack complexity, but don't mess with my sacrosanct right
to manually override everything.
Of course, some users try to set up dubious/questionable environments
to begin with, such as /boot shared by multiple distributions and things
like that.
Only legit hacking. Check.
Personally, I only share /home and a couple of optional mount points.
I don't even do that, unless at gunpoint (which was the case recently).
I prefer separate homes with shared data partitions.
Without having done it myself, I suspect that for the 2nd installation,
grub will
make write into /boot/grub2/grub.cfg file an entry that is similar to
the entry it makes
when it detects a windows bootable partition.
I am not certain how many bootable partitions per disk grub2 supports.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
