From: Christian Kujau <lists@nerdbynature.de>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org, dwmw2@infradead.org
Subject: Re: filenames with spaces in /sys?
Date: Tue, 29 Apr 2008 23:54:13 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.1.10.0804292342290.11017@sheep.housecafe.de> (raw)
In-Reply-To: <20080428153127.GA9849@ld0162-tx32.am.freescale.net>
On Mon, 28 Apr 2008, Scott Wood wrote:
>> Wouldn't ../pmu-battery.0/power_supply/PMU_battery_0/power be feasible too?
>
> Feasible, yes, but uglier
I did not want to argue about "ugliness", as this is a matter of
personal taste.
> If userspace tools make it awkward to deal with filenames with spaces,
> let's fix the userspace tools.
Usually I would agree. I was only puzzled that filenames in /sys have
spaces at all - I was under the impression spaces should be omitted in
/sys (and /proc, too) for ease of handling (userspace has to specialcase
spaces). And looking at these directories only very few filenames contain
spaces, so it looked like ../PMU battery 0/ somehow "slipped through", as
there's no point in having spaces when almost everything else was using
an unserscore.
> /sys is certainly not the only place they'll be found, and waging war
> against them is a battle best left for a couple decades ago.
Hm, I guess the real solution would be a statement about special
characters in special filesystems in CodingStyle ....and a travel back in
time to have this rule applied of course :)
C.
--
BOFH excuse #190:
Proprietary Information.
prev parent reply other threads:[~2008-04-29 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 18:35 filenames with spaces in /sys? Christian Kujau
2008-04-27 18:54 ` David Woodhouse
2008-04-27 19:44 ` [PATCH] " Christian Kujau
2008-04-28 15:31 ` Scott Wood
2008-04-29 21:54 ` Christian Kujau [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.1.10.0804292342290.11017@sheep.housecafe.de \
--to=lists@nerdbynature.de \
--cc=dwmw2@infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox