Bug 600436 - rpm overwrites changed rc.sysinit on update
Summary: rpm overwrites changed rc.sysinit on update
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords: Triaged
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-04 17:27 UTC by udo
Modified: 2014-03-17 03:23 UTC (History)
5 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2010-06-04 18:29:13 UTC

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

Description udo 2010-06-04 17:27:31 UTC 
Description of problem:
rpm overwrites changed rc.sysinit on update

Version-Release number of selected component (if applicable):
initscripts-9.02.2-1.i686

How reproducible:
update initscripts-9.02.2-1.i686

Steps to Reproduce:
1. yum update
2. initscripts is updated
3. check edits made before update, they are now gone
  
Actual results:
updated rc.sysinit, edits gone

Expected results:
rc.sysinit.rpmsave created

Additional info:
Comment 1 iarly selbir 2010-06-04 17:53:58 UTC 
What version are you updating to?

Thanks for your report.

--
Fedora Bugzappers Team Member
Comment 2 udo 2010-06-04 18:07:21 UTC 
The one mentioned in the version info.
The issue has been present for a while.
Comment 3 Bill Nottingham 2010-06-04 18:29:13 UTC 
Correct. rc.sysinit is not a config file; it's important for consistent booting that the rpm packaged copy be present.
Comment 4 udo 2010-06-04 18:33:33 UTC 
So how do we prevent my changes from over writing?
Comment 5 Bill Nottingham 2010-06-04 18:38:36 UTC 
You shouldn't be editing it directly. What do you need to edit it for?
Comment 6 udo 2010-06-04 18:59:21 UTC 
/sbin/service uptimed createbootid

at the bottom.

What else would be a suitable place to create the bootid soon in the boot process, but without overwrite risk?
Comment 7 Bill Nottingham 2010-06-04 19:05:14 UTC 
Write your own init script for it, have it set a very early priority.
Note You need to log in before you can comment on or make changes to this bug.