19.04.2017 04:38, L A Walsh пишет:
Why do you expect them to autoload? Most needed modules autoload as I use them on my sysV system that boots from the hard disk. I thought
Andrei Borzenkov wrote: that depmod was run so when accessing a device, the related modules could be autoloaded? Also, the setup tool knew all about thin volumes -- I didn't have to do the setup manually -- and it also knew if I deleted the thin pool, that /home would be disabled. That indicates the setup process knew what thin volumes were and what they were used for. A third reason would be that there was no error or warning that the system was configured in a non-bootable state like there is if you have no root or when there are other config problems. A fourth reason would be that sysd seems to know that the reason there are problems is that the modules are not loaded. One might wonder why it didn't load any modules needed by LVM -- not for raid, or any device-manager functions. When my system boots a fair number (~15-20) modules get loaded automatically during hardware probing. As I use the system, more get loaded automatically -- though sometimes I need to load some manually. What has happened here, is I choose an option from a menu during setup -- and it's role of the dice as to whether or not I bring up a supported configuration. Worse, was that what was supported at one point in time, became "no longer supported", often, seemingly at random. I don't want to have to reconfigure my system to go with the latest fad with each release. Example -- the names of the ethernet devices. First it's new names, then it's old names supported again, now it's only new names again. I could watch the kernel come up and set my devices the way I originally wanted them (eth0..), then the sysd version of udev would load, change them to junk, then I see them switched back. It was never the kernel that changed, but some user mode prog (looks like udevd, though I've never isolated it to be sure.
You use thin provisioning pool which is not supported by YaST
---- Not supported? Sure looked supported to me. It knew that a thin provisioned lv needed a pool, and when I was trying to figure the problem by deleting the extended volume -- it warned me that the pool was needed for the thin volume to function. There was no indication that it wasn't supported, and no indication of how to have it load the needed modules.
and so probably not tested either. Standard volume types do not require extra modules beyond dm-mod and dm-mod is loaded (although my guess is that it is loaded due to /dev/mapper/control device alias).---
None beyond dm-mod?? No one uses snapshots, RAID or disk encryption? Those are all dm-modules in the 'md' directory. Seems a bit odd to say most of the dm functions wouldn't be supported. There used to be a file in /etc/sysconfig where I could tell it to load modules, seems that's gone too. Wonderful... Even now, I can't continue to boot or switch to an alternate console -- the only thing sysd will let me do is reboot which is completely unhelpful, since as soon as I boot, anything I did to make things work will be unloaded. How do I get it to let me continue to boot (only /home is missing) so I can login and fix things? This was a major fear of mine concerning sysd -- that a problem would come up and sysd would lock me out of my system. Case in point. :-( -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org