[SOLVED] rc.*.oring files

What are rc.*.orig files in /etc/rc.d?
Where do they come from?
Do they have to have executable permission?

Some package managers save the original file so they don't clobber local changes, but those are not typically called '.orig'. That name is frequently used by admins who manually edit a config file and want to keep the original around for reference. I don't know of any code or script that does that.

Those files are put there when you run slackpkg upgrades. The ones in rc.d in particular come from the sysvinit-scripts package. When you upgrade that package the new scripts come in as *.new (e.g. rc.local.new) The extensions are then changed depending on what you do when slackpkg asks "what to do with new config files". If you choose to "overwrite" then the *.new files are mv'd to the actual file names and the old scripts are mv'd to *.orig names.

Check out what the slackpkg script does in /usr/libexec/slackpkg/functions.d/post-functions.sh if you want the gory details.

Also if you "ls -l" you will see that the ones that were executable before the rename are still executable after. Shouldn't matter since only the script with the proper filename will run.

Originally Posted by unInstance What are rc.*.orig files in /etc/rc.d? Where do they come from? Do they have to have executable permission?

From 'man slackpkg.conf'

       ORIG_BACKUPS
            During integration of .new files during the post installation phase, original files are backed up to a file name with a
            .orig extension.  To prevent this, set this option to "off" and note that you will no longer have a copy of the content
            of the file prior to it being replaced by the .new version.

            The  default  value  of  ORIG_BACKUPS  is "on".  Only change this if you are sure you don't want backups of overwritten
            files.
            From the command line, you can use -orig_backups=value.

They will have the same permissions as the original versions. They won't execute since they are never called on.

Originally Posted by chrisretusn From 'man slackpkg.conf' ORIG_BACKUPS During integration of .new files during the post installation phase, original files are backed up to a file name with a .orig extension. To prevent this, set this option to "off" and note that you will no longer have a copy of the content of the file prior to it being replaced by the .new version. The default value of ORIG_BACKUPS is "on". Only change this if you are sure you don't want backups of overwritten files. From the command line, you can use -orig_backups=value. They will have the same permissions as the original versions. They won't execute since they are never called on.

My patch to enable the above option is only available from Robby's git master repo, or in one of the slackpkg beta releases - it should transition into the main tree on the next slackpkg update.

Originally Posted by smallpond Some package managers save the original file so they don't clobber local changes, but those are not typically called '.orig'. That name is frequently used by admins who manually edit a config file and want to keep the original around for reference. I don't know of any code or script that does that.

I always use ".original" for this purpose to avoid conflicts with Slackware package upgrades.

Originally Posted by tadgy My patch to enable the above option is only available from Robby's git master repo, or in one of the slackpkg beta releases - it should transition into the main tree on the next slackpkg update.

Oops

Yeah I am using slackpkg - version 2.84.0_beta8

Yet those files have been around for ages. Long before I started testing the beta. As mentioned above they are created in post-functions.sh