EXPECT, and a bug where .options wasn't being written to disk or the
path was being altered when a variable was being altered. This also
gets things trim and ready with the coolest discovery being that a
nested kernel can run on the host and in it's nest. I'll be testing
other nested levels to discover how far this can go and be
incorporated in one package which is nice.
bugs founds while running underneath uml. One percular bug pertaining
to OPTIONS was found after running a uml from the uml box then closing
it again making a new root_fs and opening it again the options were
missing. Haven't noticed this on the host system before. Will also
need to add a c program to determine whether the host kernel is tt or
skas to auto-magically determing what kernel mode to run in.
logic for cmdline only to set-up .gbootroot* properly, and the logic
pertaining to mode={tt,skas}, but other than that things are working
nicely. Will have to come out with a new make-debian-x11 package, but
then again will need to come out with a new root_fs representing the
nesting changes, too.
for gui-mode and cli, and all executables can be properly specified.
Ex:
./gbootroot --home . --template Example-Mini.yard --uml-exclusively on
--expect-program ./expect_uml
--uml-kerneluser-mode-linux/usr/bin/linux --root-fs-helper
root_filesystem/root_fs_helper
./gbootroot --home . --template Example-Mini.yard --genext2fs-dir
genext2fs/ --filesystem-command "genext2fs -z -r0"
link, won't complain when there is an unitialized value in concatation in
Boot, Ramdisk_size is always 4096 for mtdram, this setting isn't really
necessary, but is left anyways.
effectively known as the create stage. This avoids the unecessary previous
requirement of having to select the copy stage again just to create a file
for /dev/ubd/0. The file created is sparse, got this idea from a discussion
Jeff had with a user on uml-user.
bit more, but have tested this with an initrd, and it works pretty nicely
even with large fs assuming mem is set high enough. Mtdram was chosen over
blkmtd for now.
the uml_exclusively and genext2fs behavior are handled by Create, this is
much nicer because a new filsystem type can be created without having to wait
for everything to be copied again to the sources directory.
If a terminfo directory is found, linux will need to exist or the test will
return error. This is better because the root filesystem can still work
if this information doesn't exist. A minority of gettys will fail if they
use termcap or terminfo, but this check was removed from the chrooted tests
several months ago for the reason just cited. Note: check_getty_type_call
was removed from Yard.pm, but exists in chrooted tests without the termcap
check. Also, added a close which was missing.
