diff options
author | Keir Fraser <keir.fraser@citrix.com> | 2010-04-19 09:00:30 +0100 |
---|---|---|
committer | Keir Fraser <keir.fraser@citrix.com> | 2010-04-19 09:00:30 +0100 |
commit | f770264fe1f91d685499179e0e9c339fa0aaa6a8 (patch) | |
tree | 96f2387aa748beecaff835c32370272643e2d343 /xen/include/asm-x86/hvm/vcpu.h | |
parent | 04dffa0be959268a5165b59c389656c8e33b6598 (diff) | |
download | xen-f770264fe1f91d685499179e0e9c339fa0aaa6a8.tar.gz xen-f770264fe1f91d685499179e0e9c339fa0aaa6a8.tar.bz2 xen-f770264fe1f91d685499179e0e9c339fa0aaa6a8.zip |
Calling awk and not gawk in the Xen scripts
I noticed that 2 scripts in Xen 4.0.0 are calling "gawk". Normally, in
most distributions, gawk is considered a specific version of awk.
Calling "gawk" and not "awk" generally means that you need
specificities of the "g" version of awk, as opposed to "mawk" which is
another implementation of the same tool.
So, unless I misread the scripts, Xen doesn't need to use gawk but
just any implementation of awk, and the attached patch can safely be
applied.
If I am wrong (which I don't think I am at the first look) and that
there's a reason why gawk is used and not awk, then IMHO, the toplevel
README should mention it in the prerequisites.
From: Thomas Goirand <thomas@goirand.fr>
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
Diffstat (limited to 'xen/include/asm-x86/hvm/vcpu.h')
0 files changed, 0 insertions, 0 deletions