Bug 86665 - sysinstall(8): sysinstall binary upgrade clobbers named.conf
Summary: sysinstall(8): sysinstall binary upgrade clobbers named.conf
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 5.4-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-sysinstall (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-28 08:10 UTC by Simon Hewison
Modified: 2015-11-10 09:12 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Hewison 2005-09-28 08:10:15 UTC
When performing a binary upgrade from a PR build of 5.4 using sysinstall, the /var/named/etc/named.conf gets replaced by a standard build, presumably since named now runs in a chroot environemnt by default.

Fix: 

Remember to back up /var/named/etc/named.conf, restore upon completion on binary upgrade
How-To-Repeat: Get named configured, perform binary upgrade with sysinstall
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2005-09-28 09:26:52 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-qa

This is really a problem with sysinstall rather than the configuration 
files themselves.
Comment 2 Jo Rhett 2007-04-20 20:49:48 UTC
I'd like to add that this problem continues.  I just saw it when doing a 
binary upgrade from 6.0 to 6.2.
Comment 3 randi freebsd_committer freebsd_triage 2009-06-06 23:52:51 UTC
Responsible Changed
From-To: freebsd-bugs->randi

Grabbing this - verified, bug still exists.
Comment 4 Mark Linimon freebsd_committer freebsd_triage 2013-06-29 06:52:04 UTC
Responsible Changed
From-To: randi->freebsd-sysinstall

back to mailing list.
Comment 5 Enji Cooper freebsd_committer freebsd_triage 2015-11-10 09:07:29 UTC
sysinstall has been replaced by bsdinstall in FreeBSD 9.x. Closing.
Comment 6 Enji Cooper freebsd_committer freebsd_triage 2015-11-10 09:12:25 UTC
sysinstall has been replaced by bsdinstall in FreeBSD 9.x. Closing.