Bug 61334 - ifup and ifdown are config files?
ifup and ifdown are config files?
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: initscripts (Show other bugs)
rawhide
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
:
Depends On:
Blocks: FC6Target
  Show dependency treegraph
 
Reported: 2002-03-17 20:01 EST by Chris Ricker
Modified: 2014-03-16 22:26 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-06-29 14:19:47 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Chris Ricker 2002-03-17 20:01:30 EST
I was looking at all the configuration files on the system ($ rpm -qac), and
noticed something weird:

[kaboom@skuld kaboom]$ rpm -qac | grep "^/sbin/if"
/sbin/ifdown
/sbin/ifup
[kaboom@skuld kaboom]$ 

Is there a reason why /sbin/ifup and /sbin/ifdown are flagged in the spec file
as being configuration files?
Comment 1 Bill Nottingham 2002-03-20 22:56:18 EST
Hm.... not that I recall. Let me see if I can find a reason somewhere.
Comment 2 Jay Turner 2002-03-21 07:52:18 EST
Still seeing this with initscripts-6.58-1
Comment 3 Chris Ricker 2002-05-05 11:44:03 EDT
Still seeing this with 7.3 gold
Comment 4 Chris Ricker 2002-07-09 22:34:39 EDT
Still true with beta3 milan
Comment 5 Chris Ricker 2003-02-20 00:22:00 EST
still true w/ beta5 phoebe
Comment 6 Matthias Saou 2006-06-29 08:59:33 EDT
Still true with Fedora Core 5 :-)

Maybe at one point it was considered "normal" to edit the ifup/ifdown scripts,
and they were marked as %config in order to not get changes lost when
initscripts got updated? Bill, if you can't figure why they're marked %config,
maybe you could just go and remove the tag for both, as it doesn't seem to make
much sense.
Comment 7 Bill Nottingham 2006-06-29 14:19:47 EDT
Done in CVS, will be in the next build.

Note You need to log in before you can comment on or make changes to this bug.