V Thu, 21 Jun 2018 06:09:44 -0400
Felix Miata <[email protected]> napsáno:

> Josef Reidinger composed on 2018-06-21 09:22 (UTC+0200):
> 
> > Thu, 21 Jun 2018 02:27:41 -0400 Felix Miata composed:  
> 
> >> Josef Reidinger composed on 2018-06-21 08:20 (UTC+0200):  
> 
> >> > Wed, 20 Jun 2018 23:42:34 -0400 Felix Miata composed:    
> 
> >> >> GRUB_DISTRIBUTOR in /etc/default/grub can be used to change the EFI 
> >> >> name to
> >> >> something else besides openSUSE, which may be desired when multibooting 
> >> >> TW and
> >> >> other openSUSE version(s). Is there a way to do this during 
> >> >> installation? I
> >> >> would think it might be in the Bootloader Options tab, but if it's 
> >> >> there, its
> >> >> non-obvious, and web search for a doc to cover the subject doesn't seem 
> >> >> to be
> >> >> able to find anything, same as /usr/share/doc/.    
> 
> >> > Hi Felix,
> >> > There is not such option. We had it in past, but it was problematic 
> >> > because it was hard to propose on multi boot system. But we still allow 
> >> > you to set it and then yast2-bootloader does not modify it and keep it 
> >> > as it is.
> >> > So in short, no support in UI as for majority of users it is fine to 
> >> > keep default, but if you modify it yourself then yast will respect it.   
> >> >  
> 
> >> Is it accessible to modify from vtty2 at some point during installation, 
> >> so that
> >> it never gets an opportunity to usurp an existing installation's files on 
> >> the
> >> ESP partition? If yes, when, and where?  
> 
> > well, what will work is if you modify it after grub2 installation and 
> > before yast2 writes bootloader ( on Leap 15 or TW ) (but there is not pause 
> > there).  
> 
> Tried that. With 4-5 minutes estimated time remaining and <100 packages to go,
> /etc/default/grub appeared, so I used vi to change GRUB_DISTRIBUTOR from "" to
> "opensuseTW". When it was time to reboot, I checked, and it had been restored 
> to
> null; confirmed on first boot. :-(

If you can send me logs I can check why it is removed. It should read it and 
merge with proposed config. Maybe there is a bug in merge logic that I can fix.

> 
> > Another option is when installation ends up, then mount againt disk and 
> > modify it + run grub2-> mkconfig and grub2-install.   
> 
> Tried, but got only:
> 
>       mount /m2: /dev/sda7 already mounted or mount point busy.

hmm, then try to find where it is mounted via mount command and modify it there.

Josef

> 
> > Third option is to have own rpm that install after grub2 and modify in post 
> > inst that file.  
> 
> Over my head to try. :-(
> 
> Fixing with YaST2 on first boot, I see same long delay waiting on the busy
> pointer to quit on selecting the Kernel Parameters tab in bootloader settings
> that I experienced during installation, likely much more than 30 seconds, 
> maybe
> even a minute. I thought I filed a bug about this not terribly long ago, but
> searching I'm missing it if it did happen.
> 
> I'm guessing the state of the partitions causes this delay (9 unformatted):
> http://fm.no-ip.com/Tmp/Dfsee/gb250L04.txt

--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to