Bug 5390 - System banner - change to empty doesn't remove /etc/issue
Summary: System banner - change to empty doesn't remove /etc/issue
Status: RESOLVED WONTFIX
Alias: None
Product: buildroot
Classification: Unclassified
Component: Other (show other bugs)
Version: 2012.02
Hardware: PC Linux
: P5 minor
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-24 05:46 UTC by Jonathan Liu
Modified: 2013-12-04 20:40 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Liu 2012-07-24 05:46:17 UTC 
After building a root filesystem, changing the system banner to nothing and then doing make doesn't remove /etc/issue from the root filesystem.
Comment 1 Thomas Petazzoni 2013-12-04 20:40:05 UTC 
This is "expected": Buildroot doesn't track the configuration changes that are made to update the root filesystem after just a "make" invocation. For example, if you remove a package from your configuration, and then run "make", then the files installed by this package in the previous build are not going to be removed from the root filesystem.

It's the same for this /etc/issue thing. If the BR2_TARGET_GENERIC_ISSUE option is empty at the first build, then no /etc/issue file gets created.

Otherwise, if you change BR2_TARGET_GENERIC_ISSUE after the first build, then the file will remain as it was before, until you do a "make clean all" cycle.

Even though fixing this would not be very difficult, I don't think we really want to do it, since we anyway don't do it for the vast majority of other Buildroot configuration options.