During the boot stage the filsystem type was used to determine whether
to use the genext2fs (non-root) method or the normal method used by root.
Now the user type is used, this is better because it prevents conflicts
if a different filesystem type is chosen, or if a non-root user changes to a
different filesystem type in the filesystem box and forgets to change back
to genext2fs; however, it prevents root from using the genext2fs method,
which isn't a problem. The sudo requirement for lilo is too much of a
requirement, and will be changed in future versions.
root_fs by using the libraries from the initrd. Liav instigated this by
asking a question related to FAQ question 14, "So if I understand correctly,
it is not possible to copy libc from /dev/ram0 to /dev/ram1 before mounting
/dev/ram1 as / ?
Liav pointed out how Yard can make boot/root floppies with a compressed root
filesystem. Edited FAQ question 13 to correctly reflect how gz compressed
root filesystems may be booted without an initrd.
entry won't be the same as that found in Root Filename, but instead reflects
the newly compressed file. This change was precipitated by the previous
change to the Accept behavior.
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.
