For clarification. The EFI Shell 1.0 (or EDK Shell) is no longer maintained.
-Jaben
From: Tian, Hot [mailto:hot.t...@intel.com]
Sent: Thursday, May 08, 2014 5:52 PM
To: edk2-devel@lists.sourceforge.net; Jarlstrom, Laurie; Tian, Feng
Cc: Brendan Jackman
Subject: Re: [edk2] Bug in EDK Shell - Directory copy
Have you tried set the shell mode in .nsh?
6.5 How to Switch the Running Modes of the EFI Shell To be backward compatible
to older versions of the EFI Shell (for example, the EFI Shell that was
included in the EFI 1.10.14.62 Sample Implementation), the new EFI Shell
provides two running modes:
* Backward-compatible mode
* Enhanced Shell mode
1.0to7thRvw July, 2005 135 EFI Shell User's Guide Shell How-To's
See Running Modes and Backward-Compatibility Support in the Features chapter
for more information on these running modes. Enhanced Shell mode is the default
running mode in this release of the EFI Shell.
To change the current running mode, execute the following command at the Shell
prompt:
set -v efishellmode xxx
In the above command, efishellmode is the reserved volatile variable that the
EFI Shell uses to control the current running mode (see Special Shell Variables
in the Syntax chapter for more information on this variable). xxx is the value
for the running mode. 1.1.1 is for backward-compatible mode and 1.1.2 is for
enhanced Shell mode. Any other values are invalid in the current version.
6.6 How to Correctly Write Scripts in the New EFI Shell
Two running modes are introduced in this version of the EFI Shell (see Running
Modes and Backward Compatibility in the Features chapter for more information):
* Backward-compatible mode
* Enhanced Shell mode
When a batch script is started, the default running mode is set to
backward-compatible mode. This mode is different from the default running mode
when you are at the command prompt. As a result, you must place a statement at
the beginning of the script to set the running mode to the desired setting.
This statement must be the first command in a script.
Note that scripts can be called inside scripts (a feature that is referred to
as nested batch scripts; see Nesting Batch Scripts in the Batch Scripts chapter
for more information). Nested scripts should set and maintain the running mode
for themselves. However, child scripts cannot change the running mode in the
parent script.
To determine the current running mode, scripts can read the reserved variable
efishellmode, the same as if they are reading a normal environment variable.
See Special Shell Variables in the Syntax chapter for more information on this
variable.
I think EDK shell is not actively maintained now. We should migrate to UEFI
shell ASAP.
Thanks,
Hot
From: Olivier Martin [mailto:olivier.mar...@arm.com]
Sent: Thursday, May 08, 2014 11:42 PM
To: Jarlstrom, Laurie; Tian, Feng
Cc: Brendan Jackman;
edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net>
Subject: [edk2] Bug in EDK Shell - Directory copy
Dear EFI Shell owners,
I am not sure who to contact for this defect (I found your name on this page
https://sourceforge.net/apps/mediawiki/tianocore/index.php?title=Efi-shell).
We found a defect in EFI Shell 1.0 (sometimes named 'EDK Shell').
The behaviour of "cp -r foo\* bar\" is different when run from a script from
when run interactively:
# Interactive:
Fs0:\> cp -r foo\* bar
copying fs0:\foo\file -> fs0:\bar
copying fs0:\foo\file -> fs0:\bar\file
- [ok]
copying fs0:\foo\foodir -> fs0:\bar\foodir
copying fs0:\foo\foodir\foodirfile -> fs0:\bar\foodir\foodirfile
- [ok]
# Run from a script:
level1.nsh> cp -r foo\* fs0:\bar
copying fs0:\foo\file -> fs0:\bar
copying fs0:\foo\file -> fs0:\bar\file
- [ok]
copying fs0:\foo\foodir -> fs0:\bar
copying fs0:\foo\foodir\foodirfile -> fs0:\bar\foodirfile
- [ok]
(\foo\foodir\foodirfile gets copied to \bar\foodirfile instead of
\bar\foodir\foodirfile)
I am not sure if external contributions are accepted for this project.
Thanks,
Olivier
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
