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

aboutlfs: Set umask to 022

Browse Source 
I know some distros are using a different default and we are having
reports of some mysterious permission issue via lfs-support those I
highly suspect as some umask issue.  Let's just explicitly set it (like
setting $LFS) to protect us from such distros without changing every
"mkdir -pv" to "install -vdm755".
This commit is contained in:
Xi Ruoyao 2025-01-11 23:17:54 +08:00
parent 389d8f53db
commit cacb470c97
No known key found for this signature in database
GPG Key ID: ACAAD20E19E710E3
1 changed files with 19 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
chapter02/aboutlfs.xml
View File

@ -8,7 +8,7 @@
<sect1 id="ch-partitioning-aboutlfs"> <sect1 id="ch-partitioning-aboutlfs">
<?dbhtml filename="aboutlfs.html"?> <?dbhtml filename="aboutlfs.html"?>
<title>Setting The $LFS Variable</title> <title>Setting the $LFS Variable and the Umask</title>
<para>Throughout this book, the environment variable <envar>LFS</envar> will <para>Throughout this book, the environment variable <envar>LFS</envar> will
be used several times. You should ensure that this variable is always defined be used several times. You should ensure that this variable is always defined
@ -28,8 +28,14 @@
<quote>/mnt/lfs</quote> (or whatever value the variable was set to) when it <quote>/mnt/lfs</quote> (or whatever value the variable was set to) when it
processes the command line.</para> processes the command line.</para>
<para>Now setting the file mode creation mask (umask) to
<literal>022</literal> in case the host distro uses a different
default:</para>
<screen role="nodump"><userinput>umask 022</userinput></screen>
<caution> <caution>
<para>Do not forget to check that <envar>LFS</envar> is set whenever <para>Do not forget to check that <envar>LFS</envar> is set and the
umask is set to <literal>022</literal> whenever
you leave and reenter the current working environment (such as when doing a you leave and reenter the current working environment (such as when doing a
<command>su</command> to <systemitem class="username">root</systemitem> or <command>su</command> to <systemitem class="username">root</systemitem> or
another user). Check that the <envar>LFS</envar> variable is set up another user). Check that the <envar>LFS</envar> variable is set up
@ -39,10 +45,17 @@
<para>Make sure the output shows the path to your LFS system's build <para>Make sure the output shows the path to your LFS system's build
location, which is <filename class="directory">/mnt/lfs</filename> if the location, which is <filename class="directory">/mnt/lfs</filename> if the
provided example was followed. If the output is incorrect, use the command provided example was followed.</para>
given earlier on this page to set <envar>$LFS</envar> to the correct
directory name.</para> <para>Check that the umask is set up properly with:</para>
</caution>
<screen role="nodump"><userinput>umask</userinput></screen>
<para>The output should be <computeroutput>022</computeroutput>.</para>
<para>If any output of these two commands is incorrect, use the command
given earlier on this page to set <envar>$LFS</envar> to the correct
directory name and set umask to <literal>022</literal>.</para></caution>
<note><para>One way to ensure that the <envar>LFS</envar> variable is always <note><para>One way to ensure that the <envar>LFS</envar> variable is always
set is to edit the <filename>.bash_profile</filename> file in both your set is to edit the <filename>.bash_profile</filename> file in both your