| 175 |
|
|
| 176 |
<p>If you're accustomed to graphical environment, choose <b>Graphical Environment</b>. In <b>Graphical Environment</b> you're able to use graphical programs, like <b>GParted</b> and <b>Mozilla Firefox</b>. Terminals are also available, so using <b>Graphical Environment</b> doesn't prevent using command line. The only negative thing of <b>Graphical Environment</b> is that it slows booting process down a bit - and it's often just plain unneeded.<br> |
<p>If you're accustomed to graphical environment, choose <b>Graphical Environment</b>. In <b>Graphical Environment</b> you're able to use graphical programs, like <b>GParted</b> and <b>Mozilla Firefox</b>. Terminals are also available, so using <b>Graphical Environment</b> doesn't prevent using command line. The only negative thing of <b>Graphical Environment</b> is that it slows booting process down a bit - and it's often just plain unneeded.<br> |
| 177 |
<br> |
<br> |
| 178 |
Try <b>VESA</b>, if normal <b>Graphical Environment</b> doesn't work. <b>VESA</b> uses <b>Xvesa</b> graphical environment instead of <b>X.Org</b> that sometimes doesn't work. The drawbacks of <b>Xvesa</b> compared to <b>X.Org</b> are that <b>Xvesa</b> isn't optimized to any hardware (which means poorer performance) and <b>Xvesa</b> requires 32-bit kernel. Thus, if you use this option, do NOT choose 64-bit kernel, the combination leaves you at command line.<br> |
Try <b>VESA</b>, if normal <b>Graphical Environment</b> doesn't work. <b>VESA</b> uses <b>Xvesa</b> graphical environment instead of <b>X.Org</b> that sometimes doesn't work. The drawback of <b>Xvesa</b> compared to <b>X.Org</b> is that <b>Xvesa</b> isn't optimized to any hardware, which means poorer performance.<br> |
| 179 |
<br> |
<br> |
| 180 |
If you're accustomed to command line and know already that you're not going to use any graphical program, choose one of the normal options (just below "System Rescue CD Menu"). Booting to command line is a bit faster process than booting to graphical environment, and you can start X manually later.<br> |
If you're accustomed to command line and know already that you're not going to use any graphical program, choose one of the normal options (just below "System Rescue CD Menu"). Booting to command line is a bit faster process than booting to graphical environment, and you can start X manually later.<br> |
| 181 |
<br> |
<br> |
| 187 |
|
|
| 188 |
<p>After having chosen the column of the above table, you still have three options. Now you need to choose the kernel.<br> |
<p>After having chosen the column of the above table, you still have three options. Now you need to choose the kernel.<br> |
| 189 |
<br> |
<br> |
| 190 |
The optimal kernel depends on the processor of your computer. If it's an IA-32 processor, like Intel Pentium 4 or AMD Athlon XP, you should choose <b>32-bit kernel</b>, because <b>64-bit kernel</b> doesn't work at all. If you have a x86-64 processor, like AMD Athlon 64 or Intel Core 2, you can choose any kernel - the processor can run all of them. <b>64-bit kernel</b> should be preferred, because it allows chrooting on an existing GNU/Linux partition containing 64-bit programs. Note, though, that you can't use <b>64-bit kernel</b> with <b>VESA</b> option.</br> |
The optimal kernel depends on the processor of your computer. If it's an IA-32 processor, like Intel Pentium 4 or AMD Athlon XP, you should choose <b>32-bit kernel</b>, because <b>64-bit kernel</b> doesn't work at all. If you have a x86-64 processor, like AMD Athlon 64 or Intel Core 2, you can choose any kernel - the processor can run all of them. <b>64-bit kernel</b> should be preferred, because it allows chrooting on an existing GNU/Linux partition containing 64-bit programs.</br> |
| 191 |
<br> |
<br> |
| 192 |
If you don't know your processor architecture, try <b>64-bit kernel</b>. If your processor architecture is IA-32, you'll see the following error message:</p> |
If you don't know your processor architecture, try <b>64-bit kernel</b>. If your processor architecture is IA-32, you'll see the following error message:</p> |
| 193 |
<!--empty line--> |
<!--empty line--> |
Parent Directory
| 
Revision Log
| 
Patch