From: Segher Boessenkool <[EMAIL PROTECTED]>
Date: Tue, 2 Jan 2007 00:52:36 +0100
> There is one big problem: text representation is useless
> (to scripts etc.) unless it can be transformed back to binary;
> i.e., it has to be possible to reliably detect _how_ some
> property is represented into text, something that cannot be
> done with how openpromfs handles it.
Text is text is text for many propertiers, in particular
the ones you actually end up wanting to modify.
The biggest and most used example are the device aliases
and the 'boot-device' and 'boot-file' environment variables.
We even have a special case for that latter case on sparc
via:
echo 'foo.image' >/proc/sys/kernel/reboot-cmd
In order for a problem to exist, you have to show counter
examples where the problem triggers and something fails.
What in userspace wants to modify a OFW property, which
is not text?
In my experience all such cases are limited to ASCII text
valued properties, such as device aliases, environment
variables, and things like nvramrc.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
