Zen

Translation

It is important to note that symlinks pointing outside the TFTP root directory may need to be allowed in the configuration of your TFTP server. Further the store link exposes the whole store through TFTP@. Both points need to be considered carefully for security aspects. It is advised to disable any TFTP write access!
English type: table
It is important to note that symlinks pointing outside the TFTP root directory may need to be allowed in the configuration of your TFTP server. Further the store link exposes the whole store through TFTP@. Both points need to be considered carefully for security aspects. It is advised to disable any TFTP write access!
283/3220 · 322

Sign in to save the translation.

English Turkish Actions
ARM, bootloaders
 
AArch64, bootloaders
 
Available bootloaders are described in @code{(gnu bootloader @dots{})} modules. In particular, @code{(gnu bootloader u-boot)} contains definitions of bootloaders for a wide range of ARM and AArch64 systems, using the @uref{https://www.denx.de/wiki/U-Boot/, U-Boot bootloader}.
 
@code{grub-bootloader} allows you to boot in particular Intel-based machines in ``legacy'' BIOS mode.
 
@code{grub-efi-bootloader} allows to boot on modern systems using the @dfn{Unified Extensible Firmware Interface} (UEFI). This is what you should use if the installation image contains a @file{/sys/firmware/efi} directory when you boot it on your system.
 
grub-efi-removable-bootloader
 
@code{grub-efi-removable-bootloader} allows you to boot your system from removable media by writing the GRUB file to the UEFI-specification location of @file{/EFI/BOOT/BOOTX64.efi} of the boot directory, usually @file{/boot/efi}. This is also useful for some UEFI firmwares that ``forget'' their configuration from their non-volatile storage. Like @code{grub-efi-bootloader}, this can only be used if the @file{/sys/firmware/efi} directory is available.
 
This @emph{will} overwrite the GRUB file from any other operating systems that also place their GRUB file in the UEFI-specification location; making them unbootable.
 
grub-efi-netboot-bootloader
 
@code{grub-efi-netboot-bootloader} allows you to boot your system over network through TFTP@. In combination with an NFS root file system this allows you to build a diskless Guix system.
@code{grub-efi-netboot-bootloader}, sisteminizi TFTP@ aracılığıyla ağ üzerinden başlatmanıza olanak tanır. Bir NFS kök dosya sistemiyle birlikte bu, disksiz bir Guix sistemi oluşturmanıza olanak sağlar.
The installation of the @code{grub-efi-netboot-bootloader} generates the content of the TFTP root directory at @code{targets} (@pxref{Bootloader Configuration, @code{targets}}) below the sub-directory @file{efi/Guix}, to be served by a TFTP server. You may want to mount your TFTP server directories onto the @code{targets} to move the required files to the TFTP server automatically during installation.
 
If you plan to use an NFS root file system as well (actually if you mount the store from an NFS share), then the TFTP server needs to serve the file @file{/boot/grub/grub.cfg} and other files from the store (like GRUBs background image, the kernel (@pxref{operating-system Reference, @code{kernel}}) and the initrd (@pxref{operating-system Reference, @code{initrd}})), too. All these files from the store will be accessed by GRUB through TFTP with their normal store path, for example as @file{tftp://tftp-server/gnu/store/…-initrd/initrd.cpio.gz}.
 
Two symlinks are created to make this possible. For each target in the @code{targets} field, the first symlink is @samp{target}@file{/efi/Guix/boot/grub/grub.cfg} pointing to @file{../../../boot/grub/grub.cfg}, where @samp{target} may be @file{/boot}. In this case the link is not leaving the served TFTP root directory, but otherwise it does. The second link is @samp{target}@file{/gnu/store} and points to @file{../gnu/store}. This link is leaving the served TFTP root directory.
 
The assumption behind all this is that you have an NFS server exporting the root file system for your Guix system, and additionally a TFTP server exporting your @code{targets} directories—usually a single @file{/boot}—from that same root file system for your Guix system. In this constellation the symlinks will work.
 
For other constellations you will have to program your own bootloader installer, which then takes care to make necessary files from the store accessible through TFTP, for example by copying them into the TFTP root directory for your @code{targets}.
 
It is important to note that symlinks pointing outside the TFTP root directory may need to be allowed in the configuration of your TFTP server. Further the store link exposes the whole store through TFTP@. Both points need to be considered carefully for security aspects. It is advised to disable any TFTP write access!
TFTP sunucunuzun konfigürasyonunda TFTP kök dizininin dışına işaret eden sembolik bağlantılara izin verilmesi gerekebileceğini unutmamak önemlidir. Ayrıca mağaza bağlantısı, tüm mağazayı TFTP@ üzerinden gösterir. Güvenlik açısından her iki noktanın da dikkatlice düşünülmesi gerekir.
Please note, that this bootloader will not modify the ‘UEFI Boot Manager’ of the system.
 
Beside the @code{grub-efi-netboot-bootloader}, the already mentioned TFTP and NFS servers, you also need a properly configured DHCP server to make the booting over netboot possible. For all this we can currently only recommend you to look for instructions about @acronym{PXE, Preboot eXecution Environment}.
@code{grub-efi-netboot-bootloader}, daha önce bahsedilen TFTP ve NFS sunucularının yanı sıra, netboot üzerinden önyüklemeyi mümkün kılmak için uygun şekilde yapılandırılmış bir DHCP sunucusuna da ihtiyacınız vardır. Tüm bunlar için şu anda yalnızca @acronym{PXE, Preboot eXecution Environment} ile ilgili talimatlara bakmanızı tavsiye edebiliriz.
If a local EFI System Partition (ESP) or a similar partition with a FAT file system is mounted in @code{targets}, then symlinks cannot be created. In this case everything will be prepared for booting from local storage, matching the behavior of @code{grub-efi-bootloader}, with the difference that all GRUB binaries are copied to @code{targets}, necessary for booting over the network.
 
grub-efi-netboot-removable-bootloader
 
@code{grub-efi-netboot-removable-bootloader} is identical to @code{grub-efi-netboot-bootloader} with the exception that the sub-directory @file{efi/boot} will be used instead of @file{efi/Guix} to comply with the UEFI specification for removable media.
 
This is a list of strings denoting the targets onto which to install the bootloader.
Bu, önyükleyicinin yükleneceği hedefleri belirten dizelerin listesidir.
The interpretation of targets depends on the bootloader in question. For @code{grub-bootloader}, for example, they should be device names understood by the bootloader @command{installer} command, such as @code{/dev/sda} or @code{(hd0)} (@pxref{Invoking grub-install,,, grub, GNU GRUB Manual}). For @code{grub-efi-bootloader} and @code{grub-efi-removable-bootloader} they should be mount points of the EFI file system, usually @file{/boot/efi}. For @code{grub-efi-netboot-bootloader}, @code{targets} should be the mount points corresponding to TFTP root directories served by your TFTP server.
 
@code{menu-entries} (default: @code{'()})
@code{menu-entries} (default: @code{()})
A possibly empty list of @code{menu-entry} objects (see below), denoting entries to appear in the bootloader menu, in addition to the current system entry and the entry pointing to previous system generations.
Mevcut sistem girişine ve önceki sistem nesillerine işaret eden girişe ek olarak, önyükleyici menüsünde görünecek girişleri belirten, muhtemelen boş bir @code{menu-entry} nesneleri listesi (aşağıya bakın).
@code{default-entry} (default: @code{0})
@code{default-entry} (default: @code{0})
The index of the default boot menu entry. Index 0 is for the entry of the current system.
Varsayılan önyükleme menüsü girişinin dizini. Dizin 0, mevcut sistemin girişi içindir.
@code{timeout} (default: @code{5})
@code{timeout} (default: @code{5})
The number of seconds to wait for keyboard input before booting. Set to 0 to boot immediately, and to -1 to wait indefinitely.
 
keyboard layout, for the bootloader
önyükleyici için klavye düzeni
If this is @code{#f}, the bootloader's menu (if any) uses the default keyboard layout, usually US@tie{}English (``qwerty'').
Bu @code{#f} ise, önyükleyicinin menüsü (varsa) varsayılan klavye düzenini kullanır, genellikle US@tie{}İngilizce (``qwerty'').
User avatar anonymous

Suggestion added

TFTP sunucunuzun konfigürasyonunda TFTP kök dizininin dışına işaret eden sembolik bağlantılara izin verilmesi gerekebileceğini unutmamak önemlidir. Ayrıca mağaza bağlantısı, tüm mağazayı TFTP@ üzerinden gösterir. Güvenlik açısından her iki noktanın da dikkatlice düşünülmesi gerekir.

Suggested change:

TFTP sunucunuzun konfigürasyonunda TFTP kök dizininin dışına işaret eden sembolik bağlantılara izin verilmesi gerekebileceğini unutmamak önemlidir. Ayrıca mağaza bağlantısı, tüm mağazayı TFTP@ üzerinden gösterir. Güvenlik açısından her iki noktanın da dikkatlice düşünülmesi gerekir.

Failing checks:

Mismatched full stop Mismatched exclamation mark 2 years ago

Loading…

User avatar anonymous

Suggestion added
It is important to note that symlinks pointing outside the TFTP root directory may need to be allowed in the configuration of your TFTP server. Further the store link exposes the whole store through TFTP@. Both points need to be considered carefully for security aspects. It is advised to disable any TFTP write access!
TFTP sunucunuzun konfigürasyonunda TFTP kök dizininin dışına işaret eden sembolik bağlantılara izin verilmesi gerekebileceğini unutmamak önemlidir. Ayrıca mağaza bağlantısı, tüm mağazayı TFTP@ üzerinden gösterir. Güvenlik açısından her iki noktanın da dikkatlice düşünülmesi gerekir.
2 years ago
User avatar None

String updated in the repository
It is important to note that symlinks pointing outside the TFTP root directory may need to be allowed in the configuration of your TFTP server. Further the store link exposes the whole store through TFTP@. Both points need to be considered carefully for security aspects. It is advised to disable any TFTP write access!
TFTP sunucunuzun konfigürasyonunda TFTP kök dizininin dışına işaret eden sembolik bağlantılara izin verilmesi gerekebileceğini unutmamak önemlidir. Ayrıca mağaza bağlantısı, tüm mağazayı TFTP@ üzerinden gösterir. Güvenlik açısından her iki noktanın da dikkatlice düşünülmesi gerekir.
2 years ago
User avatar None

Source string changed
It is important to note that symlinks pointing outside the TFTP root directory may need to be allowed in the configuration of your TFTP server. Further the store link exposes the whole store through TFTP@. Both points need to be considered carefully for security aspects. It is advised to disable any TFTP write access!
2 years ago
Browse all string changes

Things to check

Suggestions

There is 1 suggestion for this string.

View

Mismatched exclamation mark

Source and translation do not both end with an exclamation mark

Reset

Mismatched full stop

Source and translation do not both end with a full stop

Reset

Glossary

English Turkish
security guix Glossary

12339177 String information

Source string description
type: table
Source string location
guix-git/doc/guix.texi:43506
String age
2 years ago
Last updated
6 days ago
Source string age
2 years ago
Translation file
po/doc/guix-manual.tr.po, string 14047