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.
preserved for libraries, but this wasn't the case for non-root users. The
part which did preserve permissions with chmod didn't allow non-root users,
but with genext2fs this isn't a problem, though chown is. Anyways, when ld
or libc aren't 0755 basically the kernel can't find init. Problem solved.
for each user to the fstab, right now there is just a generic location for all
users. Special files aren't copied over if permissions don't allow it, but
devfs more than solves that problem!