Hi! > On another hand, the users of embedded devices, mentioned by Linus, > > should already know what scheduler to choose because dealing with > > embedded world assumes the person can decide this on their own, or with > > the help of abovementioned udev scripts and/or Documentation/ as a > > reference point. > > > > So I see no obstacles here, and the choice to rely on udev by default > > sounds reasonable. > > > > I am sorry but I do not agree with this. > > There are several historical precedents where we have > concluded that just "have the kernel do the right thing > by default" is the way to go. Kernel should do the right thing by default, I agree with Linus W. Having reasonable defaults is useful; yes, my desktop has udev etc, but I still want reasonable scheduler when doing fsck in init=/bin/bash. Plus, I update kernels more often than distros, and I run various embedded stuff. Kernel should just provide reasonable defaults. And yes, we have "ionice" command and yes, it would be nice if it worked by default... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Attachment:
signature.asc
Description: Digital signature
______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/
