6d76f469c8
I've been asked several times to provide more useful example configs for ktest.pl, as the sample.conf is too complex (because it explains all configs). This adds configs broken up by use case, and these configs are based on actual configs that I use on a daily basis. Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
61 lines
2.8 KiB
Plaintext
61 lines
2.8 KiB
Plaintext
#
|
|
# This file has some examples for creating a MIN_CONFIG.
|
|
# (A .config file that is the minimum for a machine to boot, or
|
|
# to boot and make a network connection.)
|
|
#
|
|
# A MIN_CONFIG is very useful as it is the minimum configuration
|
|
# needed to boot a given machine. You can debug someone else's
|
|
# .config by only setting the configs in your MIN_CONFIG. The closer
|
|
# your MIN_CONFIG is to the true minimum set of configs needed to
|
|
# boot your machine, the closer the config you test with will be
|
|
# to the users config that had the failure.
|
|
#
|
|
# The make_min_config test allows you to create a MIN_CONFIG that
|
|
# is truly the minimum set of configs needed to boot a box.
|
|
#
|
|
# In this example, the final config will reside in
|
|
# ${CONFIG_DIR}/config-new-min and ${CONFIG_DIR}/config-new-min-net.
|
|
# Just move one to the location you have set for MIN_CONFIG.
|
|
#
|
|
# The first test creates a MIN_CONFIG that will be the minimum
|
|
# configuration to boot ${MACHINE} and be able to ssh to it.
|
|
#
|
|
# The second test creates a MIN_CONFIG that will only boot
|
|
# the target and most likely will not let you ssh to it. (Notice
|
|
# how the second test uses the first test's result to continue with.
|
|
# This is because the second test config is a subset of the first).
|
|
#
|
|
# The ${CONFIG_DIR}/config-skip (and -net) will hold the configs
|
|
# that ktest.pl found would not boot the target without them set.
|
|
# The config-new-min holds configs that ktest.pl could not test
|
|
# directly because another config that was needed to boot the box
|
|
# selected them. Sometimes it is possible that this file will hold
|
|
# the true minimum configuration. You can test to see if this is
|
|
# the case by running the boot test with BOOT_TYPE = allnoconfig and
|
|
# setting setting the MIN_CONFIG to ${CONFIG_DIR}/config-skip. If the
|
|
# machine still boots, then you can use the config-skip as your MIN_CONFIG.
|
|
#
|
|
# These tests can run for several hours (and perhaps days).
|
|
# It's OK to kill the test with a Ctrl^C. By restarting without
|
|
# modifying this config, ktest.pl will notice that the config-new-min(-net)
|
|
# exists, and will use that instead as the starting point.
|
|
# The USE_OUTPUT_MIN_CONFIG is set to 1 to keep ktest.pl from asking
|
|
# you if you want to use the OUTPUT_MIN_CONFIG as the starting point.
|
|
# By using the OUTPUT_MIN_CONFIG as the starting point will allow ktest.pl to
|
|
# start almost where it left off.
|
|
#
|
|
TEST_START IF ${TEST} == min-config
|
|
TEST_TYPE = make_min_config
|
|
OUTPUT_MIN_CONFIG = ${CONFIG_DIR}/config-new-min-net
|
|
IGNORE_CONFIG = ${CONFIG_DIR}/config-skip-net
|
|
MIN_CONFIG_TYPE = test
|
|
TEST = ${SSH} echo hi
|
|
USE_OUTPUT_MIN_CONFIG = 1
|
|
|
|
TEST_START IF ${TEST} == min-config && ${MULTI}
|
|
TEST_TYPE = make_min_config
|
|
OUTPUT_MIN_CONFIG = ${CONFIG_DIR}/config-new-min
|
|
IGNORE_CONFIG = ${CONFIG_DIR}/config-skip
|
|
MIN_CONFIG = ${CONFIG_DIR}/config-new-min-net
|
|
USE_OUTPUT_MIN_CONFIG = 1
|