logo      
Custom Search

Re: [PATCH] Open Firmware device tree virtual filesystem

Date: December 31, 2006
From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>

In-reply-to: <20061231.124531.125895122.davem@xxxxxxxxxxxxx>
References: <459714A6.4000406@xxxxxxxxxxxxx> <Pine.LNX.4.61.0612311350060.32449@xxxxxxxxxxxxxxx> <20061231.124531.125895122.davem@xxxxxxxxxxxxx>

On Dec 31 2006 12:45, David Miller wrote:
>From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
>
>> 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'
-- 



Custom Search