| 1 |
swift |
1.3 |
<sections>
|
| 2 |
swift |
1.1 |
<section>
|
| 3 |
|
|
<title>User Administration</title>
|
| 4 |
swift |
1.4 |
<subsection>
|
| 5 |
|
|
<title>Setting a root Password</title>
|
| 6 |
swift |
1.1 |
<body>
|
| 7 |
|
|
|
| 8 |
|
|
<p>
|
| 9 |
swift |
1.4 |
Before you forget, set the root password by typing:
|
| 10 |
|
|
</p>
|
| 11 |
|
|
|
| 12 |
|
|
<pre caption="Setting the root password">
|
| 13 |
|
|
# <i>passwd</i>
|
| 14 |
|
|
</pre>
|
| 15 |
|
|
|
| 16 |
|
|
</body>
|
| 17 |
|
|
</subsection>
|
| 18 |
|
|
<subsection>
|
| 19 |
|
|
<title>Adding a User for Daily Use</title>
|
| 20 |
|
|
<body>
|
| 21 |
|
|
|
| 22 |
|
|
<p>
|
| 23 |
|
|
Working as root on a Unix/Linux system is <e>dangerous</e> and should be avoided
|
| 24 |
|
|
as much as possible. Therefor it is <e>strongly</e> recommended to add a user
|
| 25 |
|
|
for day-to-day use.
|
| 26 |
|
|
</p>
|
| 27 |
|
|
|
| 28 |
|
|
<p>
|
| 29 |
|
|
For instance, to create a user called <c>john</c> who is member of the
|
| 30 |
|
|
<c>wheel</c> group (be able to change to root using <c>su</c>), <c>users</c>
|
| 31 |
|
|
group (default for all users) and <c>audio</c> group (be able to use audio
|
| 32 |
|
|
devices):
|
| 33 |
|
|
</p>
|
| 34 |
|
|
|
| 35 |
|
|
<pre caption="Adding a user for day-to-day use">
|
| 36 |
|
|
# <i>useradd john -m -G users,wheel,audio -s /bin/bash</i>
|
| 37 |
|
|
# <i>passwd john</i>
|
| 38 |
|
|
Password: <comment>(Enter the password for john)</comment>
|
| 39 |
|
|
Re-enter password: <comment>(Re-enter the password to verify)</comment>
|
| 40 |
|
|
</pre>
|
| 41 |
|
|
|
| 42 |
|
|
<p>
|
| 43 |
|
|
If this user ever needs to perform some task as root, he can use <c>su -</c> to
|
| 44 |
|
|
temporarily receive root privileges. Another way is to use the <c>sudo</c>
|
| 45 |
|
|
package which is, if correctly configured, very secure.
|
| 46 |
swift |
1.1 |
</p>
|
| 47 |
|
|
|
| 48 |
|
|
</body>
|
| 49 |
swift |
1.4 |
</subsection>
|
| 50 |
swift |
1.3 |
</section>
|
| 51 |
|
|
<section>
|
| 52 |
|
|
<title>Reboot and Enjoy</title>
|
| 53 |
swift |
1.1 |
<subsection>
|
| 54 |
swift |
1.2 |
<title>Rebooting</title>
|
| 55 |
swift |
1.1 |
<body>
|
| 56 |
|
|
|
| 57 |
|
|
<p>
|
| 58 |
swift |
1.4 |
Congratulations! Your Gentoo system is now ready. Run <c>etc-update</c> to
|
| 59 |
|
|
update the configuration files (if needed), exit the chrooted environment and
|
| 60 |
|
|
unmount all mounted partitions. Then type in that one magical command you have
|
| 61 |
|
|
been waiting for: <c>reboot</c>.
|
| 62 |
|
|
</p>
|
| 63 |
|
|
|
| 64 |
|
|
<pre caption="Rebooting the system">
|
| 65 |
|
|
# <i>etc-update</i>
|
| 66 |
|
|
# <i>exit</i>
|
| 67 |
|
|
# <i>cd /</i>
|
| 68 |
|
|
# <i>umount /mnt/gentoo/boot /mnt/gentoo/proc /mnt/gentoo</i>
|
| 69 |
|
|
# <i>reboot</i>
|
| 70 |
|
|
</pre>
|
| 71 |
|
|
|
| 72 |
|
|
<p>
|
| 73 |
|
|
Ofcourse, don't forget to remove the bootable CD, otherwise the CD will be
|
| 74 |
|
|
booted again instead of your new Gentoo system.
|
| 75 |
|
|
</p>
|
| 76 |
|
|
|
| 77 |
|
|
<p>
|
| 78 |
|
|
OldWorld PPC users will boot in MacOS since their bootloader
|
| 79 |
|
|
isn't installed yet. Those users should read <uri
|
| 80 |
|
|
link="#doc_chap2_sect2">Optional: Configuring BootX</uri>. GRP users can
|
| 81 |
|
|
continue with <uri link="#doc_chap2_sect3">Optional: Install Extra
|
| 82 |
|
|
Packages</uri>, all the rest can finish up with <uri
|
| 83 |
|
|
link="?part=1&chap=12">Where to go from here?</uri>.
|
| 84 |
swift |
1.1 |
</p>
|
| 85 |
|
|
|
| 86 |
|
|
</body>
|
| 87 |
swift |
1.3 |
</subsection>
|
| 88 |
|
|
<subsection>
|
| 89 |
swift |
1.2 |
<title>Optional: Configuring BootX</title>
|
| 90 |
|
|
<body>
|
| 91 |
|
|
|
| 92 |
swift |
1.4 |
<impo>
|
| 93 |
swift |
1.3 |
This subsection is <e>only</e> for PPC-users who want to use BootX as
|
| 94 |
|
|
bootloader. All other readers should skip this subsection.
|
| 95 |
swift |
1.4 |
</impo>
|
| 96 |
swift |
1.2 |
|
| 97 |
|
|
<p>
|
| 98 |
|
|
Now your machine is booted in MacOS, open the BootX control panel.
|
| 99 |
|
|
Select <c>Options</c>, and uncheck <c>Used specified RAM disk</c>. When you
|
| 100 |
|
|
return to the BootX main screen, you will now find an option to specify your
|
| 101 |
|
|
machine's root disk and partition. Fill these in with the appropriate
|
| 102 |
|
|
values.
|
| 103 |
|
|
</p>
|
| 104 |
|
|
|
| 105 |
|
|
<p>
|
| 106 |
|
|
BootX can be configured to start Linux upon boot. If you do this, you will
|
| 107 |
|
|
first see your machine boot into MacOS then, during startup, BootX will
|
| 108 |
|
|
load and start Linux. See the <uri
|
| 109 |
|
|
link="http://penguinppc.org/projects/bootx/">BootX home page</uri> for more
|
| 110 |
|
|
information.
|
| 111 |
|
|
</p>
|
| 112 |
|
|
|
| 113 |
swift |
1.4 |
<p>
|
| 114 |
|
|
If you are a GRP users you can continue with <uri
|
| 115 |
|
|
link="#doc_chap2_sect3">Optional: Install Extra Packages</uri>, otherwise go to
|
| 116 |
|
|
<uri link="?part=1&chap=12">Where to go from here?</uri>.
|
| 117 |
|
|
</p>
|
| 118 |
|
|
|
| 119 |
swift |
1.2 |
</body>
|
| 120 |
swift |
1.1 |
</subsection>
|
| 121 |
swift |
1.4 |
<subsection>
|
| 122 |
swift |
1.1 |
<title>Optional: Install Extra Packages</title>
|
| 123 |
|
|
<body>
|
| 124 |
|
|
|
| 125 |
swift |
1.4 |
<impo>
|
| 126 |
|
|
This part is for GRP users only. Other users should skip this part and continue
|
| 127 |
|
|
with <uri link="?part=1&chap=12">Where to go from here?</uri>.
|
| 128 |
|
|
</impo>
|
| 129 |
|
|
|
| 130 |
|
|
<p>
|
| 131 |
|
|
Now that your system is booted, log on as the user you created (for instance,
|
| 132 |
|
|
<c>john</c>) and use <c>su -</c> to gain root privileges:
|
| 133 |
|
|
</p>
|
| 134 |
|
|
|
| 135 |
|
|
<pre caption="Gaining root privileges">
|
| 136 |
|
|
$ <i>su -</i>
|
| 137 |
|
|
Password: <comment>(Enter your root password)</comment>
|
| 138 |
|
|
</pre>
|
| 139 |
|
|
|
| 140 |
|
|
<p>
|
| 141 |
|
|
Now we need to copy over the prebuild binaries from the second CD (CD-2) if you
|
| 142 |
|
|
have it. First mount this CD:
|
| 143 |
|
|
</p>
|
| 144 |
|
|
|
| 145 |
|
|
<pre caption="Mount the CD-2">
|
| 146 |
|
|
<comment>(Put CD-2 in the CD tray)</comment>
|
| 147 |
|
|
# <i>mount /mnt/cdrom</i>
|
| 148 |
|
|
</pre>
|
| 149 |
|
|
|
| 150 |
swift |
1.1 |
<p>
|
| 151 |
swift |
1.4 |
Now copy over all prebuild binaries from the CD to
|
| 152 |
|
|
<path>/usr/portage/packages</path>. Make sure you use the same copy-command
|
| 153 |
|
|
(including the trailing <path>/</path>)!
|
| 154 |
|
|
</p>
|
| 155 |
|
|
|
| 156 |
|
|
<pre caption="Copy over prebuild binaries">
|
| 157 |
|
|
# <i>cp -a /mnt/cdrom/* /usr/portage/packages/</i>
|
| 158 |
|
|
</pre>
|
| 159 |
|
|
|
| 160 |
|
|
<p>
|
| 161 |
|
|
Now install the packages you want. CD-2 contains several prebuild binaries, for
|
| 162 |
|
|
instance KDE:
|
| 163 |
|
|
</p>
|
| 164 |
|
|
|
| 165 |
|
|
<pre caption="Installing KDE">
|
| 166 |
|
|
# <i>emerge -k kde</i>
|
| 167 |
|
|
</pre>
|
| 168 |
|
|
|
| 169 |
|
|
<p>
|
| 170 |
|
|
Be sure to install the binaries now. When you do an <c>emerge sync</c> to update
|
| 171 |
|
|
Portage (as you will learn later), the prebuilt binaries might not match against
|
| 172 |
|
|
the ebuilds in your updated Portage. You can try to circumvent this by using
|
| 173 |
|
|
<c>emerge -K</c> instead of <c>emerge -k</c>.
|
| 174 |
|
|
</p>
|
| 175 |
|
|
|
| 176 |
|
|
<p>
|
| 177 |
|
|
Congratulations, your system is now fully equiped! Continue with <uri
|
| 178 |
|
|
link="?part=1&chap=12">Where to go from here?</uri> to learn more about
|
| 179 |
|
|
Gentoo.
|
| 180 |
swift |
1.1 |
</p>
|
| 181 |
|
|
|
| 182 |
|
|
</body>
|
| 183 |
swift |
1.4 |
</subsection>
|
| 184 |
swift |
1.1 |
</section>
|
| 185 |
swift |
1.3 |
</sections>
|
Parent Directory
| 
Revision Log