On Mon, Mar 06, 2006 at 06:41:22PM +0100, Pavel Machek wrote:
> > > Is adding "noapic nolapic" to default command line a big problem?
> > For end-users, yes. People want things to 'just work', not have
> > to find arcane commands to type in to make things work.
> If distro puts "noapic nolapic" on kernel command line, I'd say users
> are unlikely to remove it.. And if they do remove it and it breaks,
> they'll only blame themselves...
If distros put 'noapic nolapic' on the command line they've only
themselves to blame when systems that need local apic for
correct operation don't work.
> One more config-option is also not "cheap" (half of users will get it
> wrong), and having config-option to change command-line-default seems
> wrong to me.
>
> [Well, you could add CONFIG_CMDLINE to i386, like arm has... that
> solves more than just this problem...]
I'm not arguing for extra command line options. The inverse, I want
*no* command line options.
What's so hard to understand about expecting something to just work?
Dave
--
http://www.codemonkey.org.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
