| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
New release with codename Manon
|
|
|
|
|
|
|
| |
By using the "silent" option at the cmdline, HDT tries not displaying
any boring message.
This is particulary interesting with the "display" option.
|
|
|
|
| |
Using more_printf allow to manage more easily several pages printing.
|
|
|
|
|
| |
If people want to sleep while saying message, they now have to use the
sleep command instead of the previous specific %x syntax.
|
| |
|
|
|
|
|
|
|
| |
This command will help users getting some delay between two automatic
commands.
As an example, it can be used to show a serie of pictures.
|
|
|
|
|
|
|
| |
This command allow switching the background image. This could be used
for example to give more explicit message to users.
Idea is coming from the FGTC project
|
| |
|
|
|
|
| |
When building official hdt image, let's add a say & postexec example.
|
|
|
|
|
|
|
|
|
|
| |
This command is just for displaing a message to the cli during a defined
period of time.
Syntax is like the following : say `my message`%<number_of_seconds>
An example :
say `This is my text message to display during 5 seconds`%5
|
|
|
|
|
|
|
|
|
|
| |
Some new commands might need being able to manage the argv directly
instead of the much more oriented scheme we had until now.
This commit add a .nomodule option to cli object to explically tell they
don't have a module as parameter but only arguments.
This will be needed for the 'say' command.
|
|
|
|
| |
Sizeof(char *) is definetly wrong for getting the length of a string.
|
|
|
|
|
| |
Adding more debug traces in the cli management to ease debugging &
feature adding.
|
|
|
|
| |
chain32 moved, let's adjust the "release" target.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When HDT is exiting, you might need executing something else.
This could be used in the following scenario :
You start HDT, do an automatic command like 'dump; exit', but then after
you might need to launch something else from syslinux.
The postexec option will allow you to define what label you'd love
running one HDT got terminated.
Syntaxt is like the following:
postexec='menu_label_to_run_once_hdt_got_exited'
Note the quotes (') after the equal sign (=)
This could looks like :
APPEND auto='dump; exit' postexec='memtest'
|
| |
|
| |
|
|
|
|
|
| |
During CPU's capabilites computation, let's sure the buffer we manage is
big enought....
|
|
|
|
|
|
|
| |
When physical disks were present, the computed items were not flushed
and so not present on the disk file.
Thanks to pscheie for reporting this.
|
|
|
|
|
| |
Bootable flags shall be 6 char to let one NULL terminating char.
Thx Gerth for reporting this.
|
|
|
|
| |
New release 0.5.1 to manage dynamic filenames based on "%" variables.
|
|
|
|
| |
Checksums file are generated by release target. No need to track it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This option allow the user to redefine the way filename is made-of.
By default that's "mac_address+dmi_vendor_name+dmi_product_name"
This can be overidded by the following syntax:
dump_filename=your_filename
Note that it's mandatory not to add "" or '' around your_filename.
your_filename could be a regular filename but can also includes %{}
directives as defined by :
%{m} = mac address
%{v} = vendor name of the machine
%{p} = product name of the machine
%{ba} = Asset tag of the base board
%{bs} = Serial number of the base board
%{ca} = Asset tag of the chassis
%{cs} = Serial number of the chassis
%{sk} = SKU number of the system
%{ss} = Serial number of the system
Here come a possible command line :
APPEND nomenu auto='dump;' dump_path=hdt2 tftp_ip=192.168.1.254 dump_filename=%{m}+%{bs}+%{ba}+%{cs}+%{ca}+%{sk}+%{ss}+%{p}+%{v}
|
|
|
|
| |
When we release hdt, generating an usb hybrid image could be useful.
|
|
|
|
| |
If the boot flag is set on a partition, let's dump this information.
|
|
|
|
|
|
|
| |
This reverts commit 842d7e35ccd8cd89105faf0266497e838d96c8b3.
In fact, you found a real bug. I missed at dumping some information.
So I revert this commit and then add the missing code.
|
|
|
|
|
|
|
| |
hdt picks up include files from outside the include directory and so
needs an explicit -I$(com32). This probably should be fixed.
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
|
|\
| |
| |
| |
| |
| |
| |
| | |
Resolved Conflicts:
com32/hdt/Makefile
com32/sysdump/Makefile
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
|
| |
| |
| |
| |
| |
| |
| | |
com32.mk already includes the necessary libraries in $(C_LIBS), we
don't need to list them again in $(LIBS).
Signed-off-by: Matt Fleming <matt.fleming@linux.intel.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Move the MCONFIG files into a mk/ directory and give them more
descriptive names.
This is purely a cosmetic change to make the 'include' directives a
bit more coherent by making it obvious exactly which MCONFIG file
we're including. For example, in com32/lua/src/Makefile we exchange
the line,
include ../../MCONFIG
for the much more comprehensible,
include $(MAKEDIR)/com32.mk
Signed-off-by: Matt Fleming <matt.fleming@linux.intel.com>
|
| |
| |
| |
| |
| |
| |
| | |
The standard definition for inet_ntoa() is to take struct in_addr, and
not doing that causes a conflict on the lwip branch.
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Remove a set but unused variable in HDT, which prevents building with
gcc 4.6. This is probably a bug; presumably the active flag should be
presented to the user, too.
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
|
| |
| |
| |
| | |
Thanks for all who participe in this release.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When generating floppy images some version of mtools (< 4.0.14) are
buggy and generate incorrect labels. So using > 4.0.13 is recommended.
Anyway, let's use _ into the volume name, that cleaner :
We now have
disk label="HDT_0_5_0_B"
instead of
disk label="HDT_0~5~0-B"
|
| |
| |
| |
| |
| | |
Some screenshots shows that we have some troubles for aligning items.
This is now fixed.
|
| | |
|
| |
| |
| |
| |
| | |
That's a nice info to know that some output were generated by the
automatic mode.
|
| |
| |
| |
| | |
This message was clearly boring to read ;o)
|
| | |
|
| |
| |
| |
| | |
As we now have a dump mode, let's add an entry in our menu for that.
|
| |
| |
| |
| | |
Dump mode can only work if PXE is present.
|
| |
| |
| |
| |
| |
| | |
If we get some errors from the tftp, let's report it to the user.
This will make user's life easier to understand why the dumping mode
isn't working.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Parsing of the auto='' mode was weak an non functionnal in many
configuration like
auto='dump'
This is now fixed.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Jim Cromie reported that PXE menu behave like :
gPXE Detected: ]No
This commit avoid this buffer corruption.
|
| |
| |
| |
| |
| |
| | |
What we report is the presence of the boot flag and not the ability of a
partition to be bootable. A partition can have a valid bootloader with a
boot flag not set. So the 'Bootable' semantic was wrong.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If the location of the disks wasn't sequential on the system, the menu
mode was missing some.
This commit fix ticket #46.
Thanks gerth for reporting.
|
| |
| |
| |
| | |
This got a requirement from some users.
|
| |
| |
| |
| |
| | |
We have to delete all the checksums files while cleaning.
Older release might exists.
|