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.
has been consigned to a function call auto_loader which will not be used because this
gets away in creating dists with alternative libs, and ld is almost always found if required
binaries are chosen, anyways.
Information can come from three sources, the kernel version returned from
a selected kernel in the main section, the user defined kernel version
in the ABS, or `uname -r`. User defined kernel version overrides the kernel.
The root_fs needs to be built in relation to the actual kernel modules
it will run on. Previously the $RELEASE value wasn't returned properly
because of some bugs in kernel_version_check. This has been fixed.
checked in the service-name files found in /etc/pam.d/. The 4th field is
acceptable for pam.conf. If a path is specified in either conf format,
that path will be checked, otherwise, either the pam default path of
/usr/lib/security or the FSSTD location /lib/security will be checked
for a match.
# intuitive and allows user-defined links.
# The file can be fictional. $abs_file_file means there is
# something on the right side. Generally, we want to use
# the file on the right as the real file.
Simply put, this is a much better approach to handling -> in the template,
and it works nicely. It produces warning when the file on the right can't
be discerned, but this is o.k..
chrooted tests disappear, it is assumed that most normal administrators
would never consider giving non-root users chroot capabilities, but you
never know, so only genext2fs is tested for, but room is left if another
fs is choosen.