Previous
Next
Contents
- Yard's handling of PAM and /etc/pam.conf is based on what other
people have told me. I don't use PAM myself.
- Space calculations will never be completely accurate because of inode
overheads and object file stripping.
- Yard requires that you have ldconfig in your file set so Yard can use
it to regenerate the cache. This is somewhat inelegant, since
ldconfig isn't generally useful on a rescue disk. Eventually ldconfig
may have some kind "chroot" option to eliminate this need.
- Occasionally when using a loopback device the ext2 filesystem will
become corrupted for no apparent reason. See the note at the end of
the loopback appendix.
- Yard uses an ad hoc (but usually reliable) method to determine the
release number of a kernel image (ie, to derive what
uname -r
would
print). Occasionally it returns the wrong version. This seems to
happen when a kernel is remade without doing make mrproper
.
- You can turn off swapping and build your root filesystem in the swap
partition. I don't recommend this. Yard can't reliably check
to make sure the partition isn't being used. If you build a
filesystem over an active swap partition your system will likely
crash.
- I haven't yet done anything about the new GNU Libc-2 (GLIBC)
because it's still experimental. Eventually I'll upgrade and modify
Yard. Until then, here are some notes that other people have written
on getting Yard to work with it:
http://www.cs.umass.edu/ fawcett/yard/gnu_libc.html
Previous
Next
Contents