Browsing Turkish translation

244.

In a thin client computing environment, the stability of the server is important. It's important to make sure that your server has good power management, like installing a UPS, and depending on how much availability is required, redundant power supplies may be called for. As well, users who have the resources may decide to invest in multiple disks for RAID support, and other options which may be needed in a High Availability environment. However, you certainly don't need them in all environments, and Edubuntu's high quality means that in all but the most demanding environments, this won't be needed.

295.

The reason why it is called a chroot environment is that to install it, the GNU/Linux command <command>chroot</command> is called to actually set the installation root to <filename>/opt/ltsp/</filename><emphasis role="strong">arch</emphasis>. From there, a scaled-down version of the distribution is installed. What this means is that for you to manage the chroot, performing such things as updates, all you need to do is use the <command>chroot</command> command to change the root of your installation. Then you can use all your tools like you normally would.

312.

Up to this point, the root filesystem has been a ram disk. Now, the <command>/init</command> script will mount a new root filesystem via either NBD or NFS. In the case of NBD, the image that is normally loaded is <filename>/opt/ltsp/images/i386.img</filename>. If the root is mounted via NFS, then the directory that is exported from the server is typically <filename>/opt/ltsp/i386</filename>. It can't just mount the new filesystem as /. It must first mount it to a separate directory. Then, it will do a <command>run-init</command>, which will swap the current root filesystem for a new filesystem. When it completes, the filesystem will be mounted on /. At this point, any directories that need to be writable for regular startup to occur, like /tmp, or /var, are mounted at this time.

318.

The <filename>lts.conf</filename> file will be parsed, and all of the parameters in that file that pertain to this thin client will be set as environment variables for the <command>S20ltsp-client-core</command> script to use.

323.

By default, a standard character based getty will be run on screen 1 (SCREEN_01 in the <filename>lts.conf</filename> file).

327.

The X server will either start an encrypted <command>ssh</command> tunnel to the server, in the case of <command>ldm</command>, or an an XDMCP query to the LTSP server, in the case of startx. Either way, a login box will appear on the terminal.

338.

Linux kernels must be tagged with the <command>mknbi-linux</command>, which will prepare the kernel for network booting, by prefixing the kernel with some additional code, and appending the initrd to the end of the kernel.

341.

Part of the 'Wired for Management' specification from the late 1990's included a specification for a bootrom technology known as the <emphasis>Pre-boot Execution Environment</emphasis> commonly abbreviated as <emphasis role="strong">PXE</emphasis>.

342.

A PXE bootrom can load at most a 32 kilo-byte file. A Linux kernel is quite a bit larger than that. Therefore, we setup PXE to load a 2nd stage boot loader called <emphasis role="strong">pxelinux</emphasis>, which is small enough to be loaded. It knows how to load much larger files, such as a Linux kernel.

368.

In order to speed up LTSP, by default, we're using NBD (Network Block Devices) rather than NFS. The <filename class="directory">/opt/ltsp/i386</filename> still exists, but now, it's compressed into a squashfs image, so it's much smaller than simply exporting via NFS. This means that the client uses less network bandwidth than before. However, it would mean that every time you change the <filename>lts.conf</filename> file, you'd have to re-create this image using the command <command>ltsp-update-image</command>. This takes a while to do. So, in order to avoid this, we've moved the <filename>lts.conf</filename> file to the TFTP directory, in <filename class="directory">/var/lib/tftpboot/ltsp/i386</filename>. This means you can make changes to the file immediately, and simply reboot the terminal, without recompiling the image.