Hi,
On 10/10/2009 03:03 AM, David Cantrell wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 10 Oct 2009, Steffen Maier wrote:
On 10/10/2009 12:27 AM, David Cantrell wrote:
how to write a kernel parameter for themselves. The catch with dasd is
that all of those parameters need to be combined in to a single dasd=
parameter.
This is true for the dasd= parameter of the dasd_mod device driver
module. However, I'd like us to be aware, that it is just the current
simple dracut implementation which exposes the same syntax and hence
catch to anaconda. In general, this doesn't have to be. Dracut could
activate each DASD by itself just like linuxrc.s390 now does -- and like
dracut does for zFCP LUNs. That would require a little more code in
dracut since it could then no longer just pass the parameters string
untouched to the module by means of writing it to modprobe.conf. I'm
starting to think we should really discuss this with Harald.
I like this idea. It certainly sounds cleaner and hopefully less prone to
failures later. Let's talk to Harald about this.
David,
Thanks for trying to solve this cleanly I really appreciate it!
Given the direction this dicussion is heading the solution with
the dict you came up with won't be necessary anymore. And I would
prefer to keep the dracutSetupString handling as is, as the dict,
although a clean solution adds some complexity, to the code and
if possible I prefer KISS.
So for now I've not reviewed this patch set. If you would still
like to move forward wit this patch set, let me know and I'll
review it.
Regards,
Hans
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
