On Fri, 12 Sep 2008 16:28:53 -0400, Joseph Smith joe@settoplinux.org wrote:
On Fri, 12 Sep 2008 14:05:50 -0600, Jordan Crouse jordan.crouse@amd.com wrote:
On 12/09/08 15:55 -0400, Joseph Smith wrote:
On Fri, 12 Sep 2008 12:46:57 -0700, "ron minnich" rminnich@gmail.com wrote:
On Fri, Sep 12, 2008 at 12:45 PM, Joseph Smith joe@settoplinux.org
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.
Is there any way to fit a tiny ASKII to hex converter into FILO? And setup a writeable table?