F17 vs. Pentium 4
hennebry at web.cs.ndsu.nodak.edu
Fri Apr 13 20:36:51 UTC 2012
On Fri, 13 Apr 2012, mwesten wrote:
> On 04/12/2012 10:51 PM, Michael Hennebry wrote:
>> On Thu, 12 Apr 2012, mwesten wrote:
>>> On 04/12/2012 07:12 PM, Michael Hennebry wrote:
>>>> No selinux message, but
>>>>> Still no go.
>>>>> I took some pictures of the "Details" message,
>>> I'm not getting anything at that URL, and I probably won't have a way
>>> around whatever it is, either.
> Alright, I looked at the pics you posted and it appears that you have
> reproduced this anaconda crash during the bootloader installation:
> I was looking at the included exception report and it seems this person
> was installing F16 on the second of two drives with the bootloader going
> on the first.
> Is that what you were doing as well?
That is not what I recall, but I might be wrong.
Is there a way to tell which disk was used
for booting that does not involve rebooting?
I've been poking around /proc , but haven't found anything.
As mentioned earlier, when attempting upgrade,
the only allowed source was F14, i.e. the one I wanted to keep.
For that reason, I selected fresh custom install.
When listing available partitions, anaconda listed the sda partitions as
the target partitions and the sdb partitions as the data partitions.
I put everything except a swap file on sdb.
When it asked where to put the bootloader,
I think it specified sda as the default.
My recollection was that sdb was the boot disk, so that bothered me.
Given the troubles I'd had previously after rejecting a bootloader default,
I decided to accept this one.
All seemed to be going well until the crash.
Michael hennebry at web.cs.ndsu.NoDak.edu
"On Monday, I'm gonna have to tell my kindergarten class,
whom I teach not to run with scissors,
that my fiance ran me through with a broadsword." -- Lily
More information about the test