I've traced kernel starting ddd/gdb and it seems to be parsing and consuming until eight ubd arguments as documented.
Loading source for arch/um/drivers/ubd_kern.c, by tracing it, I see it feels ubd_dev array from index 0 to 7. Function ubd_setup_common is called for each argument being parsed. For a nineth argument, it correctly points error (n > MAXDEV). I'm unable to go ahead with this tracing for while, but I guess it's sufficient to show arguments being worked. So I believe there's other reason... 2005/5/12, Edward Faulkner <[EMAIL PROTECTED]>: > On 5/12/05, Marcio Scheibler <[EMAIL PROTECTED]> wrote: > > Now, I'm in trouble trying to start UML with seven UBD > > devices... It recognizes just first six (ubda through ubdf) > > regardless their order in command-line (even with > > udb6s before ubd5s for instance). > > I bet you're running into the argument limit. From the UML "Fixing > Problems" page: > > "It turns out that there's a limit of six environment variables on the > kernel command line. When that limit is reached or exceeded, argument > processing stops..." > > http://jdike.stearns.org/uml/faq.html > > -Ed > -- ------------------------------------------------- Marcio Scheibler ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_ids93&alloc_id281&op=click _______________________________________________ User-mode-linux-user mailing list User-mode-linux-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
