On 2017-04-22 01:53, Anton Aylward wrote:
On 21/04/17 05:43 PM, Carlos E. R. wrote:
No no.
On a freshly installed system, using YaST to do the installation, where YaST knows that it is installed on LVM and how exactly, the user can not configure dracut at all before it boots once. And configuring dracut is incorrect. YaST must provide a system that boots the first time after installation, it must do the correct dracut configuration itself.
If the dracut configuration is incorrect, that is a bug of the installation system.
We're talking at cross purposes. I agree, you cannot tweak dracut when doing the initial install. i'm not asking you to.
I'm also not asking you to get exactly what you want at the "Omega Point" during the install.
I *am* saying that you should do a basic install. A basic install lets you use the disk configurator, in expert mode, create a basic LVM setup.
Well, but YaST does allow you to do that kind of complex setup during initial installation. If it does not work and you have to do a basic LVM install, then there is a bug in YaST (YaST is the program that does the initial install, I believe) ...
I'm confused, for example, when you say "Yast to do the installation". You are saying that Yast === the installer?
As far as I can tell the installed "dracut" config has no overrides. As far as I can tell all the 'options' in /etc/dracut.conf are commented out. They were when I first installed and they still are, because I have, as suggested by the notes therein, made my modification by adding to /etc/dracut.config.d/
As far as I can tell the installer make use of a kernel that is overloaded but has smarts enough to some runtime detection. Heck we have the same thing when X starts, don't we. There's nothing to stop you doing customization.
I know because the customization I've done in /etc/dracut.conf.d/ not only gives me logs but has also shrunk the size of my initrd by somewhere between 20% and 30%. I've also disable the "os-probe" part so that all my old RootFS, experiments with BtrFS for example, don't get menu entries in grub when mkinitrd calls grub2-mkconfig.
So if all the entries in a vanilla install /etc/dracut.conf are still commented out and there's nothing in a vanilla /etc/dracut.conf/d, then what the <*-BLEEP-*> are you talking about when you say that the 'installer === yast" is configuring dracut?
No. What I said is that /IF/ dracut has to be configured so that a complex(?) LVM setup boots after the initial system install is done, then the installer has to configure dracut, not the user aka admin. And the installer is a YaST module, I believe. If configuring dracut means run it with certain options, so be it. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)