This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
redboot scripting additions
- From: Andrew Dyer <amdyer at gmail dot com>
- To: ecos-discuss <ecos-discuss at ecos dot sourceware dot org>
- Date: Sun, 31 Oct 2004 16:14:27 -0500
- Subject: [ECOS] redboot scripting additions
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=uIN3A3rnBBxTimX+HN6PX76hErt37P+OxhfFz6YafjrE7wNgPB/mXULah6DY/FPjp0EU3XnM5nDnnl+zjfB4sAvwFj/oZ/8P6sYpweN5VfDWxd0C5226m7KA0aUooSQGJx/ox4esU4ufGdRPH4qf6/U3xKD/2Ep1HVBmCaQVsJE=
- Reply-to: Andrew Dyer <amdyer at gmail dot com>
Hi, I am interested in adding some things to redboot's command line processing
to allow a bit more flexibility in scripting - specifically in
allowing a user to
choose between several linux images to boot without having to know the redboot
syntax for load or the kernel command line syntax for exec.
I think the basics I need are an echo type command to print stuff, a way of
grabbing user CLI input into a variable, a basic set of tests, and some kind
of conditional execution.
Has anybody implemented something like this for redboot? I don't really
want/need a full blown extension language, at the same time I don't want
to paint myself into a corner...
--
Hardware, n.:
The parts of a computer system that can be kicked.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss