goroboro/user-documentation
0
0
Fork 0
forked from server/user-documentation
Code Pull requests Activity

Update file edits to not use HEREDOC and to rather explain to use preferred editor

Browse source 
This was agreed and discussed in a Fedora Server meeting.
This commit is contained in:
Rowan Puttergill 2026-07-09 15:25:57 +01:00
commit 0bd8ea413d
1 changed files with 6 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

13
modules/ROOT/pages/administration/dnsmasq.adoc
View file

@ -482,9 +482,11 @@ The `inst.repo` URL in the file tells the Anaconda installer where to fetch pack
Note that menu entry for the Fedora 44 Network Install points to the fedora44/initrd.img and fedora44/vmlinuz files that we downloaded in the previous step. If you wanted to host multiple install options you can download the kernel and ram-disk images for each distribution or release and create a menu entry for each release.
+
A menu entry is included to exit out of this menu and to use the next configured boot option, which usually includes the hard disk for the system. Providing this option in the menu, gives you a way to boot to disk easily. You can change the `set default=0` line to `set default=1` to make the second menu entry the default value, if you prefer.
[source,console]
+
Create and edit the file at `/var/lib/tftpboot/EFI/x86_64-efi/grub.cfg` using your preferred editor running under sudo to acquire root priveleges:
+
[source,]
----
$ sudo tee /var/lib/tftpboot/EFI/x86_64-efi/grub.cfg << 'EOF'
set timeout=10
set default=0
@ -501,15 +503,13 @@ menuentry "Fedora 44 Network Install" {
menuentry 'Exit to next boot device' {
exit
}
EOF
----
4. **Add a dnsmasq configuration entry to enable the TFTP service**:
Create and edit the file at `/etc/NetworkManager/dnsmasq.d/10-TFTP.conf` using your preferred editor running under sudo to acquire root priveleges:
+
[source,console]
[source,]
----
$ sudo tee /etc/NetworkManager/dnsmasq.d/10-TFTP.conf << 'EOF'
# Enable TFTP server
#enable-tftp[=<interface>[,<interface>]]
enable-tftp
@ -527,7 +527,6 @@ dhcp-match=set:efi-x86_64,option:client-arch,9
# dhcp-boot=<tag>,<filename>[,<server-name>,<server-ip>]
dhcp-boot=tag:efi-x86_64,EFI/x86_64-efi/core.efi
EOF
----
+
In the configuration, DHCP matching is used to tag the request for the appropriate client architecture (UEFI). The DHCP boot instructions describe the filename to serve for the given tag. If you were handling BIOS clients and you had configured the syslinux binaries appropriately, you could create dhcp-match and dhcp-boot directives appropriate to that client architecture.