Michael Brown 0436e417bc [image] Fail "imgexec"/"boot" if the image to execute is ambiguous ...

If there is more than one loaded image, refuse to automatically select
the image to execute.  There are at least two possible cases, with
different "correct" answers:

1. User loads image A by mistake, then loads image B and types "boot".
   User wants to execute image B.

2. User loads image A, then loads image B (which patches image A), then
   types "boot".  User wants to execute image A.

If a user actually wants to load multiple images, they must explicitly
specify which image is to be executed.

2008-07-08 03:50:44 +01:00

..

autoboot_cmd.c

Use stdio.h instead of vsprintf.h

2007-01-19 01:13:12 +00:00

config_cmd.c

[settings] Allow "config" command to access root settings block

2008-07-08 02:10:18 +01:00

dhcp_cmd.c

Warnings purge: src/{crypto,hci,net}

2007-07-03 13:20:22 -04:00

gdbstub_cmd.c

[GDB] Remote debugging over UDP

2008-06-30 19:19:48 +01:00

ifmgmt_cmd.c

Use stdio.h instead of vsprintf.h

2007-01-19 01:13:12 +00:00

image_cmd.c

[image] Fail "imgexec"/"boot" if the image to execute is ambiguous

2008-07-08 03:50:44 +01:00

nvo_cmd.c

[Settings] Remove assumption that all settings have DHCP tag values

2008-03-25 20:46:16 +00:00

route_cmd.c

Use stdio.h instead of vsprintf.h

2007-01-19 01:13:12 +00:00

sanboot_cmd.c

[Command] Add "sanboot" command.

2008-03-04 17:59:26 +00:00