On Mon, 2007-07-16 at 13:42 -0700, Prasanna Mumbai wrote: > On 7/16/07, Jeremy Katz <katzj@xxxxxxxxxx> wrote: > > Adding command line flags like this absolutely sucks for the > user > experience. Because it essentially means that unless the user > is "in > the know", they don't get to use it at all. At which point we > might as > well not add the code at all. > > Do you have any other better idea to tell the application to decide > whether to scan the memory or not? Otherwise the application has to > scan the memory each time while installing. ... much like we scan for _all kinds of things_ when installing. If that breaks due to iSCSI[1], then the iSCSI scanning is broken > Moreover diskless install is done by people who have quite a good > experience installing Linux systems. I feel these guys know what > diskless install using iSCSI mean. But do they know that they need to send magic code #37 to the installer to get it to work? No. And they shouldn't *EVER HAVE TO*. If they do, then things are broken. That is exactly why we properly _integrated_ the iSCSI code rather than hiding it behind a command line option in the first place Jeremy [1] Sadly, the way the code is now, we can guarantee it will break things because accessing /dev/mem from userspace and grokking around can and does hang boxes.
