Messages in this thread | | | Date | Wed, 16 Aug 2006 17:11:19 +0200 (CEST) | From | Bodo Eggert <> | Subject | Re: bonding: cannot remove certain named devices |
| |
On Wed, 16 Aug 2006, Bill Nottingham wrote: > Giacomo A. Catenazzi (cate@debian.org) said:
> > > Are you willing to work to add the special case code necessary to > > > handle whitespace characters in the device name over all of the kernel > > > code and also all of the userland tools too? > > > > But if you don't handle spaces in userspace, you handle *, ?, [, ], $, > > ", ', \ in userspace? Should kernel disable also these (insane device > > chars) chars? > > Don't forget unicode characters!
And long names or control characters.
> Seriously, while it might be insane to use some of these, I'm wondering > if trying to filter names is more work than fixing the tools.
I think it's sane to avoid control characters and unicode/iso*, since they can interfere with log output or analysis. I only thought about the kernel itself and the corresponding userspace tools, which should handle any character sequence just fine or could be easily fixed.
-- Top 100 things you don't want the sysadmin to say: 14. Any more trouble from you and your account gets moved to the 750 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |