Bug 439703
Summary: | ltsp-server and tftp-server disagree on path for "tftpboot" | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Axel Thimm <axel.thimm> |
Component: | ltsp | Assignee: | Warren Togami <wtogami> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | mnagy |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-03-31 01:16:08 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 188611 |
Description
Axel Thimm
2008-03-30 18:14:01 UTC
Did you upgrade from Fedora 8 to Fedora 9? In that case you have to edit /etc/xinetd.d/tftp manually because it is evil for an RPM %post to edit config files automatically and the tftp owner rightly declined to do it. Unfortunately xinetd.d files need to be marked %config(noreplace) in order to not break in upgrades, which sucks because they need to be modified merely to be enabled. > Did you upgrade from Fedora 8 to Fedora 9? [%config(noreplace) explanation]
No, this is a fresh install and %config(noreplace) is my middle name. ;)
As a further indication that the current tftp package in F9 does indeed use
/var/lib/tftpboot just look at its file manifest:
[root@victor ~]# rpm -ql tftp-server| grep /var
/var/lib/tftpboot
It's just that tft, ltsp and any other package making assumptions about where
the tftp(boot) directory is need to agree on a standard [1] location.
[1] standard for Fedora/RHEL at least, since there is no given FHS path for it
Great catch Axel! I had confused the name because of /etc/xinetd.d/tftp. This will be fixed in 5.1.2. |