Hi! > > I am accustomed to doing 'echo -n' for most of sysfs anyway. Once in a > > while I am a bonehead and forget the '-n' and spend a few minutes > > wondering why this thing that worked last week suddenly rejects all > > commands. I'm just trying to make my user interface a bit user-friendly. > > > > I will take out the '\n' stripping and update the documentation. I didn't > > realize this would be controversial. > > Don't. You're doing the right thing by scrubbing your input. Requiring > 'echo -n' is just stupid when it is so easy to make work easily. 'foo\nbar\n' is unusual but valid filename in linux. It is bad idea to echo filenames into files in the first place... and arbitrarily disallowing certain filenames is not helping. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
