On Fri, 12 Sep 2008 14:05:50 -0600, Jordan Crouse <[EMAIL PROTECTED]>
wrote:
> On 12/09/08 15:55 -0400, Joseph Smith wrote:
>>
>>
>>
>> On Fri, 12 Sep 2008 12:46:57 -0700, "ron minnich" <[EMAIL PROTECTED]>
>> wrote:
>> > On Fri, Sep 12, 2008 at 12:45 PM, Joseph Smith <[EMAIL PROTECTED]>
>> wrote:
>> >
>> >> Maybe so for a virus. But when it allows an end user to have a
>> > completely
>> >> configurable boot loader...
>> >
>> > If people want it I guess. But we computer people need to be more
>> > careful about opening holes to provide features. Just look at the
>> > state of the internet for a reason why....
>> >
>> true.
>> Well, how about this then. Instead of FILO writing the file we could
> just
>> provide a generic filo.conf. The first time the user boots up they will
>> have to manually boot. Once they are in Linux they can just copy the
>> filo.conf to their first drive, first partion, root directory. Ahh, but
>> that will still defeat the purpose, because it will still not be
>> configurable from FILO at bootup, just read only... huh, my brain is
>> starting to hurt.
>
> What specific use case are you trying to solve here? Under what
> circumstances would you prefer to write your configuration file from
> within the ROM and not from within the kernel or through some
installation
> process?
>
I'm trying to figure out a way to have a end user configurable kernel
command line (and possibly give the ability for the end user to change some
FILO settings) and have the ability to save them.
--
Thanks,
Joseph Smith
Set-Top-Linux
www.settoplinux.org
--
coreboot mailing list: [email protected]
http://www.coreboot.org/mailman/listinfo/coreboot
