So as usual, I was skipping a step. I did need to include the boot=
kernel parameter since /boot was separate from root. It wasn't
getting mounted. Everything seems to be working now.
On Sun, Apr 20, 2014 at 11:59 PM, Evan Rowley wrote:
> I don't have expertise on this issue, but it would be int
On Apr 20, 2014, at 8:01 PM, Dale Harris wrote:
>
>
> But that file does exist on the system. I guess the initramfs may not
> see the /boot directory on the system? Or is it trying to look for
> /boot inside the initramfs? If so that would explain my problem. I
> haven't verified any of this
I don't have expertise on this issue, but it would be interesting if that
bit of shell script there were adjusted to also print out the fstab and
possibly other diagnostic information relevant to the problem. That way,
you might get a clue as to where /boot is coming from. Then again, I'm not
even
I don't have expertise on this issue, but it would be interesting if that
bit of shell script there were adjusted to also print out the fstab and
possibly other diagnostic information relevant to the problem. That way,
you might get a clue as to where /boot is coming from. Then again, I'm not
even
Sorry if you see this twice, I may have goofed:
Hey,
So I was playing around with trying to get a CentOS 6.5 system
FIPS-140 complaint. However, my system panics because it cannot find
the hmac file associated with my kernel. It's basically as what is
going on is described in this bug report:
h
5 matches
Mail list logo
