grub2-mkconfig

[Patrick Dupre]

Hello,

If I run a system on VolSys1-root, and if I run grub2-mkconfig
with 
GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/root nouveau.modeset=0"
in /etc/default/grub
I get in grub.cfg

linux16 /vmlinuz-4.16.11-100.fc26.x86_64 root=/dev/mapper/VolSys1-root ro
rd.lvm.lv=VolSys0/root nouveau.modeset=0 

Is it not an issue ?

Thank

===========================================================================
 Patrick DUPRÉ                                 | | email: pdupre(a)gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale           | |
 Tel.  (33)-(0)3 28 23 76 12                   | | Fax: [phone]
 189A, avenue Maurice Schumann                 | | 59140 Dunkerque, France
===========================================================================

[Samuel Sieb]

On 07/27/2018 04:14 AM, Patrick Dupre wrote:
>  If I run a system on VolSys1-root, and if I run grub2-mkconfig
>  with
>  GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/root nouveau.modeset=0"
>  in /etc/default/grub
>  I get in grub.cfg
>  
>  linux16 /vmlinuz-4.16.11-100.fc26.x86_64 root=/dev/mapper/VolSys1-root ro
> rd.lvm.lv=VolSys0/root nouveau.modeset=0
>  
>  Is it not an issue ? 
What part of that are you concerned about?

[Patrick Dupre]

>  On 07/27/2018 04:14 AM, Patrick Dupre wrote:
>  > If I run a system on VolSys1-root, and if I run grub2-mkconfig
>  > with
>  > GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/root nouveau.modeset=0"
>  > in /etc/default/grub
>  > I get in grub.cfg
>  > 
>  > linux16 /vmlinuz-4.16.11-100.fc26.x86_64 root=/dev/mapper/VolSys1-root ro
> rd.lvm.lv=VolSys0/root nouveau.modeset=0
>  > 
>  > Is it not an issue ?
>  
>  What part of that are you concerned about? 
VolSys1-root versus VolSys0-root

> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail].o...
>

[Samuel Sieb]

On 07/27/2018 11:19 AM, Patrick Dupre wrote:
> >
> > On 07/27/2018 04:14 AM, Patrick Dupre wrote:
> >> If I run a system on VolSys1-root, and if I run grub2-mkconfig
> >> with
> >> GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/root nouveau.modeset=0"
> >> in /etc/default/grub
> >> I get in grub.cfg
> >>
> >> linux16 /vmlinuz-4.16.11-100.fc26.x86_64 root=/dev/mapper/VolSys1-root ro
> rd.lvm.lv=VolSys0/root nouveau.modeset=0
> >>
> >> Is it not an issue ?
> >
> > What part of that are you concerned about?
>  
>  VolSys1-root versus VolSys0-root 
Grub does not interpret what you put in the kernel command line.  It 
merely copies it.  You are running mkconfig from that root partition, so 
that's what it puts as the root parameter in the generated config file.

[Patrick Dupre]

>  On 07/27/2018 11:19 AM, Patrick Dupre wrote:
>  >>
>  >> On 07/27/2018 04:14 AM, Patrick Dupre wrote:
>  >>> If I run a system on VolSys1-root, and if I run grub2-mkconfig
>  >>> with
>  >>> GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/root nouveau.modeset=0"
>  >>> in /etc/default/grub
>  >>> I get in grub.cfg
>  >>>
>  >>> linux16 /vmlinuz-4.16.11-100.fc26.x86_64 root=/dev/mapper/VolSys1-root ro
> rd.lvm.lv=VolSys0/root nouveau.modeset=0
>  >>>
>  >>> Is it not an issue ?
>  >>
>  >> What part of that are you concerned about?
>  > 
>  > VolSys1-root versus VolSys0-root
>  
>  Grub does not interpret what you put in the kernel command line.  It 
>  merely copies it.  You are running mkconfig from that root partition, so 
>  that's what it puts as the root parameter in the generated config file. 
I am
not sure that I understand, but the point that I noted, if the 2
volumes are different, then, in my case, it does not boot, even if the 2 volumes
are similar.


> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail].o...
>

[Samuel Sieb]

On 07/27/2018 11:44 AM, Patrick Dupre wrote:
> > On 07/27/2018 11:19 AM, Patrick Dupre wrote:
> >>> On 07/27/2018 04:14 AM, Patrick Dupre wrote:
> >>>> If I run a system on VolSys1-root, and if I run grub2-mkconfig
> >>>> with
> >>>> GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/root nouveau.modeset=0"
> >>>> in /etc/default/grub
> >>>> I get in grub.cfg
> >>>>
> >>>> linux16 /vmlinuz-4.16.11-100.fc26.x86_64 root=/dev/mapper/VolSys1-root ro
> rd.lvm.lv=VolSys0/root nouveau.modeset=0
> >>>>
> >>>> Is it not an issue ?
> >>>
> >>> What part of that are you concerned about?
> >>
> >> VolSys1-root versus VolSys0-root
> >
> > Grub does not interpret what you put in the kernel command line.  It
> > merely copies it.  You are running mkconfig from that root partition, so
> > that's what it puts as the root parameter in the generated config file.
>  I am not sure that I understand, but the point that I noted, if the 2
>  volumes are different, then, in my case, it does not boot, even if the 2 volumes
>  are similar. 
Grub just takes that "GRUB_CMDLINE_LINUX" string and copies it to the 
end of the command line that it has already created.  It does not 
inspect it at all.  If you are trying to make a grub config file that 
boots a different root partition, you will probably have to manually 
edit it after it is created.

The simpler method would be to just add an entry in the config file that 
loads the config file from the other boot partition (assuming that one 
is correct and not a copy of this one).