gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-19 11:49:20 +01:00
Code Issues Packages Projects Releases Wiki Activity

Changed the notes in sections 7.13.1 and 7.14.1 to be explicit about the lack of quotes around EOF.

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@7798 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Bryan Kadzban 2006-09-23 00:27:35 +00:00
parent 1f3f918e63
commit d0d8dc8f4c
3 changed files with 31 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
chapter01/changelog.xml
View File

@ -35,6 +35,17 @@
</itemizedlist> </itemizedlist>
</listitem> </listitem>
--> -->
<listitem>
<para>2006-09-22</para>
<itemizedlist>
<listitem>
<para>[bryan] - Rewrote the notes in sections 7.12.1 and
7.13.1 to explicitly mention that the redirections rely
on not quoting EOF. Fixes #1883.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem> <listitem>
<para>2006-09-20</para> <para>2006-09-20</para>
<itemizedlist> <itemizedlist>

14
chapter07/network.xml
View File

@ -59,10 +59,16 @@ EOF</userinput></screen>
incorrect by default when every distro does this right. --> incorrect by default when every distro does this right. -->
<note> <note>
<para>Although the examples in this book work properly, be aware <para>Be aware that Udev does not recognize the backslash for line
that Udev does not recognize the backslash for line continuation. continuation. The examples in this book work properly because both
If modifying Udev rules with an editor, be sure to leave each rule the backslash and newline are ignored by the shell. This makes the
on one physical line.</para> shell send each rule to cat on only one line. (The shell ignores
this sequence because the EOF string used in the here-document
redirection is not enclosed in either double or single quotes. For
more details, see the bash(1) manpage, and search it for "Here
Documents".)</para>
<para>If modifying Udev rules with an editor, be sure to leave each
rule on one physical line.</para>
</note> </note>
<para>If you are going to use the bus position as a key, create <para>If you are going to use the bus position as a key, create

14
chapter07/symlinks.xml
View File

@ -43,10 +43,16 @@ SUBSYSTEM=="block", ENV{ID_MODEL}=="PHILIPS_CDD5301", \
EOF</userinput></screen> EOF</userinput></screen>
<note> <note>
<para>Although the examples in this book work properly, be aware <para>Be aware that Udev does not recognize the backslash for line
that Udev does not recognize the backslash for line continuation. continuation. The examples in this book work properly because both
If modifying Udev rules with an editor, be sure to leave each rule the backslash and newline are ignored by the shell. This makes the
on one physical line.</para> shell send each rule to cat on only one line. (The shell ignores
this sequence because the EOF string used in the here-document
redirection is not enclosed in either double or single quotes. For
more details, see the bash(1) manpage, and search it for "Here
Documents".)</para>
<para>If modifying Udev rules with an editor, be sure to leave each
rule on one physical line.</para>
</note> </note>
<para>This way, the symlinks will stay correct even if you move the drives <para>This way, the symlinks will stay correct even if you move the drives