Hi YaST hackers,
I observe a kernel bug that happens only in YaST partitioning code.
Probably the partitioner does some "weird" thing (load modules,
etc.) that triggers the bug.
How to debug this? Is it possible to trigger the same hardware
detection code in a running system? Or do I need to rebuild the kernel
(easy) and the installation initrd (because of modules)?
Any suggestions appreciated.
Bernhard
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
