mirror of
https://github.com/netbootxyz/netboot.xyz.git
synced 2026-04-25 23:25:54 +03:00
[GH-ISSUE #1095] Inconsistent use of bootloader_filename and site_name #296
Labels
No labels
Hacktoberfest
Hacktoberfest
bootloader
bsd
bug
confirmed
documentation
duplicate
enhancement
enhancement
enhancement
eol
experimental-merged
freebsd
help wanted
invalid
investigate
ipxe
linux
live-os
memdisk
menu
no-issue-activity
no-issue-activity
pull-request
released
todo
upstream
windows
windows
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/netboot.xyz#296
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @abh on GitHub (Mar 16, 2022).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1095
The templates have a setting for
bootloader_filename, but in most placessite_nameis used instead. This causes some features to break ifsite_nameandbootloader_filenamearen't set to the same thing.For example the
tftpmenuitems aren't loaded and the URLs on the index.html page doesn't work.@github-actions[bot] commented on GitHub (Apr 15, 2022):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@abh commented on GitHub (Apr 15, 2022):
Uh, not sure what's expected here. Bad bot?
@github-actions[bot] commented on GitHub (May 16, 2022):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@oe3gwu commented on GitHub (Mar 12, 2023):
No idea why this is inactive. It is a real issue.
@abh commented on GitHub (Mar 13, 2023):
@oe3gwu I'm not using this actively anymore, but for my use it was fixed by #1096
@oe3gwu commented on GitHub (Mar 13, 2023):
@abh I once looked at it, but actually wasnt aware that it was fixed. This issue should be closed then.
@abh commented on GitHub (Mar 13, 2023):
@oe3gwu no, that change wasn't merged so it shouldn't be closed (but you can try the patch to see if it works for you).