On May 18, 2014, at 4:08 PM, Stephen Morris wrote:
> On 05/18/2014 11:57 PM, Michael Schwendt wrote:
>> On Sun, 18 May 2014 14:57:14 +0200, Patrick Dupre wrote:
>>
>>> Hello,
>>>
>>> After an update of teh kernel. the file:
>>> /boot/grub2/grub.cfg is updated.
>>> However thsi file is not upda
On 05/19/2014 08:42 AM, Michael Schwendt wrote:
On Mon, 19 May 2014 08:08:54 +1000, Stephen Morris wrote:
My experience with grubby being run after kernel installs, when I
have been able to get it to run, is that it does recreate the entire
grub.cfg file. For example, I have been in the s
On Mon, 19 May 2014 08:08:54 +1000, Stephen Morris wrote:
> My experience with grubby being run after kernel installs, when I
> have been able to get it to run, is that it does recreate the entire
> grub.cfg file. For example, I have been in the situation where the boot
> menu had an entry
On 05/18/2014 11:57 PM, Michael Schwendt wrote:
On Sun, 18 May 2014 14:57:14 +0200, Patrick Dupre wrote:
Hello,
After an update of teh kernel. the file:
/boot/grub2/grub.cfg is updated.
However thsi file is not update properly.
How? In which way is it not updated "properly"?
Prior to install
On Sun, 18 May 2014 22:30:46 +0200, Patrick Dupre wrote:
> > You've skipped looking at /proc/cmdline (which would also tell the root=
> > kernel parameter used at boot-time).
> It is correct:
> BOOT_IMAGE=/vmlinuz-3.14.3-200.fc20.x86_64
> root=/dev/mapper/VolGrpSys_DK1-root ro rd.md=0 rd.dm=0
>
On May 18, 2014, at 1:42 PM, Patrick Dupre wrote:
> OK,
>
> Thank you.
>
> I understand the mistake:
> in /etc/fstab, there is
> /dev/mapper/VolGrpSys_DK0-root / ext4defaults
> 1 1
> instead of:
> /dev/mapper/VolGrpSys_DK1-root / ext4
> - Original Message -
> From: Michael Schwendt
> Sent: 05/18/14 10:23 PM
> To: users@lists.fedoraproject.org
> Subject: Re: update grub2
>
> On Sun, 18 May 2014 21:42:16 +0200, Patrick Dupre wrote:
>
> > OK,
> >
> > Thank you.
> >
On Sun, 18 May 2014 21:42:16 +0200, Patrick Dupre wrote:
> OK,
>
> Thank you.
>
> I understand the mistake:
> in /etc/fstab, there is
> /dev/mapper/VolGrpSys_DK0-root / ext4 defaults
> 1 1
> instead of:
> /dev/mapper/VolGrpSys_DK1-root / ext
On May 18, 2014, at 10:14 AM, Tom Horsley wrote:
> On Sun, 18 May 2014 18:09:32 +0200
> Patrick Dupre wrote:
>
>> How does it get this information?
>
> I always thought grubby just copied the entry for the
> current kernel and replaced the vmlinuz and initrd
> with the new names it just instal
OK,
Thank you.
I understand the mistake:
in /etc/fstab, there is
/dev/mapper/VolGrpSys_DK0-root / ext4 defaults
1 1
instead of:
/dev/mapper/VolGrpSys_DK1-root / ext4 defaults
1 1
However,
mount gives:
/dev/mapper/VolGrpSys_DK1-root
On Sun, 18 May 2014 18:09:32 +0200, Patrick Dupre wrote:
> OK, I understand, my point is that the inserted part is wrong!
> This is wrong:
> linux /vmlinuz-3.14.3-200.fc20.x86_64 root=/dev/mapper/VolGrpSys_DK0-root
>
> It should be DK1 (not DK0). How does it get this information?
/sbin/new-ke
On Sun, 18 May 2014 18:09:32 +0200
Patrick Dupre wrote:
> How does it get this information?
I always thought grubby just copied the entry for the
current kernel and replaced the vmlinuz and initrd
with the new names it just installed, but it may be
more complicated than that.
--
users mailing li
>
> > Hello,
> >
> > After an update of teh kernel. the file:
> > /boot/grub2/grub.cfg is updated.
> > However thsi file is not update properly.
>
> How? In which way is it not updated "properly"?
>
> Prior to installing a new kernel, you could save a copy of grub.cfg,
> install a new kernel p
On Sun, 18 May 2014 14:57:14 +0200, Patrick Dupre wrote:
> Hello,
>
> After an update of teh kernel. the file:
> /boot/grub2/grub.cfg is updated.
> However thsi file is not update properly.
How? In which way is it not updated "properly"?
Prior to installing a new kernel, you could save a copy o
14 matches
Mail list logo
