File: Yard_doc-12.html

package info (click to toggle)
yard 1.17.patch1-5
  • links: PTS
  • area: main
  • in suites: potato
  • size: 600 kB
  • ctags: 74
  • sloc: perl: 1,729; sh: 250; makefile: 176; asm: 32
file content (84 lines) | stat: -rw-r--r-- 2,823 bytes parent folder | download
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
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
 <TITLE>Yard Documentation: Format of Bootdisk_Contents</TITLE>
 <LINK HREF="Yard_doc-13.html" REL=next>
 <LINK HREF="Yard_doc-11.html" REL=previous>
 <LINK HREF="Yard_doc.html#toc12" REL=contents>
</HEAD>
<BODY>
<A HREF="Yard_doc-13.html">Next</A>
<A HREF="Yard_doc-11.html">Previous</A>
<A HREF="Yard_doc.html#toc12">Contents</A>
<HR>
<H2><A NAME="s12">12. Format of Bootdisk_Contents</A></H2>

<P>
<P>For convenience, the format rules for entries in
<CODE>Bootdisk_Contents</CODE> is given in comments at the beginning of
that file.  Here is a list of the allowable forms:
<P>
<UL>
<LI>Blank lines and whitespace may be used freely.</LI>
<LI>Lines beginning with # or % are comments.</LI>
<LI>Filenames may be either relative or absolute. 
Any filename not beginning with a slash is relative and
will be resolved relative to the current directory.
</LI>
<LI>Lines of the form 
<BLOCKQUOTE><CODE>
<PRE>
filename1 -> filename2
</PRE>
</CODE></BLOCKQUOTE>

will create symbolic (soft) links on the root filesystem.  For example, if
you want <CODE>sh</CODE> linked to <CODE>bash</CODE> in the root filesystem, you specify:
<BLOCKQUOTE><CODE>
<PRE>
/bin/sh -> /bin/bash
</PRE>
</CODE></BLOCKQUOTE>


(There is no way to specify hard links, though hard linked files
that exist on the hard disk will be hard linked on the floppy.)
</LI>
<LI>Lines of the form <CODE>filename1 &lt;= filename2</CODE> will cause filename2 to be
copied to filename1 on the boot disk.  This is useful for specifying
trimmed-down replacements for /etc/passwd, /etc/inittab, etc.  filename2 will
be found first by searching PATH, then by searching relative to the current
directory.

A useful variant of this is:
<BLOCKQUOTE><CODE>
<PRE>
filename1 &lt;= /dev/null
</PRE>
</CODE></BLOCKQUOTE>

</LI>
<LI>Glob designations (?, * and [...]) are generally allowed, eg
<CODE>/dev/hd[ab]*</CODE>.  Wildcards are not allowed in link specs or
replacement specs because no one knows what they mean.
</LI>
<LI>You may refer to environment variables in these specs by using
a dollar sign.  $RELEASE will be set the the release string of
the kernel you specify (<CODE>$kernel</CODE>).
</LI>
</UL>
<P>In most cases you don't need to specify shared libraries or loaders.  The
script will detect dependencies (via <CODE>ldd</CODE>) and include them
automatically.  The exception for this is PAM.
<P>You don't need to explicitly specify intermediate directories unless you
just want to make sure they exist.  For example, if you mention
/foo/bar/slog, Yard will make sure /foo and /foo/bar exist.
<P>
<P>
<HR>
<A HREF="Yard_doc-13.html">Next</A>
<A HREF="Yard_doc-11.html">Previous</A>
<A HREF="Yard_doc.html#toc12">Contents</A>
</BODY>
</HTML>