1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
<TITLE>Yard Documentation: Known bugs and limitations</TITLE>
<LINK HREF="Yard_doc-8.html" REL=next>
<LINK HREF="Yard_doc-6.html" REL=previous>
<LINK HREF="Yard_doc.html#toc7" REL=contents>
</HEAD>
<BODY>
<A HREF="Yard_doc-8.html">Next</A>
<A HREF="Yard_doc-6.html">Previous</A>
<A HREF="Yard_doc.html#toc7">Contents</A>
<HR>
<H2><A NAME="s7">7. Known bugs and limitations</A></H2>
<P>
<OL>
<LI>Space calculations will never be completely accurate because of inode
overheads and object file stripping.
</LI>
<LI>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 of "chroot" option to eliminate this need.
</LI>
<LI>Occasionally when using a loopback device the ext2 filesystem will
become corrupted for no apparent reason. See the note at the end of
<A HREF="Yard_doc-14.html#loopback">the loopback appendix</A>.
</LI>
<LI>Yard's method of determining the release number of a kernel image
(ie, to derive what <CODE>uname -r</CODE> would print) is usually correct.
Occasionally it returns the wrong version. This seems to happen when
a kernel is remade without doing <CODE>make mrproper</CODE>.
</LI>
</OL>
<P>
<HR>
<A HREF="Yard_doc-8.html">Next</A>
<A HREF="Yard_doc-6.html">Previous</A>
<A HREF="Yard_doc.html#toc7">Contents</A>
</BODY>
</HTML>
|
