On May 25, 2008, Michael Buesch <mb@bu3sch.de> wrote:

quoted text
> One additional thing is to make sure the usability of the whole stuff
> is not reduded.

Removing support for slashes wouldn't reduce usability.  It would be
no more than silly policy (and ego?) enforcement.

cd /lib/firmware
for f in test/*; do ln -s $f `echo $f | sed s,^test/,test-,`; done

voila

Removing support for slashes just makes things more cumbersome,
placing artificial restrictions where none make sense, to impose a
specific mindset and prohibit very natural uses for no real gain.  But
it's not like anything really significant is lost.  It is still a flat
namespace, this change would just be taking out the '/' from the
available alphabet.

No big loss, but no real advance in whatever rule one is trying to
impose with this.  Simply demanding additional work arounds to do
things that can be done in perfectly simple and natural ways today,
for no actual advantage.

Reminds me of the additional mailing list recently suggested by Al
Viro ;-)

-- 
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}
FSFLA Board Member       ¡Sé Libre! => http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
--
unsubscribe notice
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/