git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@495 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Gerard Beekmans 2001-04-14 02:34:44 +00:00
parent 8be5ea9bfc
commit 8703c62e3f
2 changed files with 6 additions and 5 deletions

View File

@ -2,14 +2,14 @@
<title>Creating passwd and group files</title> <title>Creating passwd and group files</title>
<para> <para>
In order for user and group root to be recognized and to be able to login, In order for the user and group root to be recognized and to be able to login,
it needs an entry in the /etc/passwd and /etc/group file. Besides the there needs to be an entry in the /etc/passwd and /etc/group file. Besides the
group root a couple of other groups are recommended and needed by group root a couple of other groups are recommended and needed by
packages. The groups with their GID's below aren't part of any standard. packages. The groups with their GID's below aren't part of any standard.
The LSB only recommends besides a group root a group bin to be present The LSB only recommends besides a group root a group bin to be present
with GID 1. Other group names and GID's can be chosen by the user. Well with GID 1. Other group names and GID's can be chosen by the user. Well
written packages don't depend on GID numbers but just use the group written packages don't depend on GID numbers but just use the group
name, it doesn't matter all that much what GID a group has. Since there name, since it doesn't matter all that much what GID a group has. Since there
aren't any standards for groups I won't follow any conventions used by aren't any standards for groups I won't follow any conventions used by
Debian, RedHat and others. The groups added here are the groups the Debian, RedHat and others. The groups added here are the groups the
MAKEDEV script (the script that creates the device files in the /dev MAKEDEV script (the script that creates the device files in the /dev

View File

@ -3,12 +3,13 @@
<para> <para>
The installation of all the software is pretty straightforward and The installation of all the software is pretty straightforward and
a user will think it's so much easier and shorter to give the generic you will probably think it's so much easier and shorter to give the generic
installation instructions for each package and only explain how to installation instructions for each package and only explain how to
install something if a certain package requires an alternate installation install something if a certain package requires an alternate installation
method. Although I agree on that, I, however, choose to give the method. Although I agree on that, I choose to give the
full instructions for each and every package. This is simply to avoid any full instructions for each and every package. This is simply to avoid any
possible confusion and errors. possible confusion and errors.
</para> </para>
</sect1> </sect1>