On 21/04/17 05:43 PM, Carlos E. R. wrote:
On 2017-04-21 21:03, Anton Aylward wrote:
On 21/04/17 12:25 PM, Per Jessen wrote:
L A Walsh wrote:
I see...maybe I'll try that next. Sorry, but that wasn't clear. Thanks for clearing that up.
No problem - when you didn't know about modules-load.d, it's an honest mistake to make.
Let's clarify this: It loads a kernel module. It *ONLY* loads a kernel modules.
In the case of LVM it does not
* load any of the LVM config files * any of the user level LVM libraries or binaries * any of the UDEV rules pertaining to LVM or LVM initialization * any of the scripts that are needed to support any of the above * does not start lvmetad * does not run 'pvscan -a'
It is NOT, repeat NOT a solution to the issue that Linda was raising. Using a properly configured Dracut to build the custom kernel/initrd after a successful vanilla installation is the way to go. Get a baseline system running first. The after you've proven a baseline system is runnable, bootable, start modifying it ....
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. Yes, it helps if before you start the DVD install you used a LiveCD to run a fdisk to create the LVM partition. I've done that, along with a SWAP and /boot partition, as I'm sure I've mentioned a number of times before. The the expert mode configurator for a LVM RootFS, /home, /var/ and anything else you want. Keep it "real" at this point. That all works. It worked for a number of releases now. I did it a few weeks ago for 42.1; I see no reason why it won't work with 42.2. I'm sure if it doesn't we'd have seen more mention. AT THIS POINT FORGET ABOUT THIN & POOL. If that basic install without any buqqqering around doesn't work then you have deeper problems. If you're not willing to establish that a very basic install like that works then you have an existential problem that has little to do with any shortcomings that the installer may or may not have. Having done a basic install you should be able to a basic boot. Maybe you chose not to install the X system and a DM/GUI. But either way, you can still alt-F-key and get a text mode login as toot. At this point there are many How-To pages (I like the ones for Arc) on how to set up Thin Provisioning using LVM from the comand line. If you can't get a basic not fancy stuff system installed using the expert mode disk partition configuration for LVM, ignoring anything about "Thin", then say so. Right now I'm confused because there seem to be contradictory messages. 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? As far as I can tell one of two things must be happening. Scenario A) When the installer sets up LVM it makes a note to activate the systemd modules that are pertinent. It makes note to add the string "lvm" to the command line it is generating when it runs dracut. <sidebar>If you're not clear about that please read the man page for dracut. Please be aware that a lot of what the installer does is fork of shells that do various bits of the work for it when you finally commit to the install. </sidebar> Scenario B) The kernel as supplied on the DVD is like the Windows kernel and has a code path and load library that is a 'database' of all the various options. That is why it is so large. Personally I favour "A". -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org