[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.61.0612312230070.29991@yvahk01.tjqt.qr>
Date: Sun, 31 Dec 2006 22:30:37 +0100 (MET)
From: Jan Engelhardt <jengelh@...ux01.gwdg.de>
To: David Miller <davem@...emloft.net>
cc: wmb@...mworks.com, devel@...top.org, linux-kernel@...r.kernel.org,
jg@...top.org
Subject: Re: [PATCH] Open Firmware device tree virtual filesystem
On Dec 31 2006 12:45, David Miller wrote:
>From: Jan Engelhardt <jengelh@...ux01.gwdg.de>
>
>> BUT, the eeprom utility may be used to modify values, and if used, I
>> would like to see ofwfs show the updated value. openpromfs does it
>> today:
>>
>> 15:09 ares:/proc/openprom/options # cat oem-banner?
>> false
>> 15:09 ares:/proc/openprom/options # eeprom 'oem-banner?=true'
>> 15:09 ares:/proc/openprom/options # cat oem-banner?
>> true
>>
>> (BTW, why does not openpromfs have it rw?)
>
>It used to be able to :-)
>
>When I changed sparc/sparc64 over to an in-memory copy of the
>OFW tree, I wasn't able to retain writable property support
>in openpromfs. It just needs to be implemented and I never
>found the desire nor time.
However, there is this one pseudofile "security-password" which _is_
writable, what about it?
-`J'
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists