<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hello,<br>
<br>
I've not contributed directly to Fedora before, but have a small change
I'd like to make. I think this is the place to find out more about
doing that.<br>
<br>
I'd like a hook in rc.sysinit to do local /tmp cleanup on boot. I
already do things like this all the time on my system, but:<br>
<ol>
<li>Every time I update, if the original file changed, and is
updated, the update is rpmsave (or similar), and I then need to compare
versions every time.</li>
<li>Every time I reinstall (usually once a year) I have to go back an
re-edit a core system file (and then see (1) above sometime later).</li>
<li>I think others have messy /tmp directories too.</li>
</ol>
The change to rc.sysinit is these three lines (although it would have
to be different if merged into the distribution, this is just what's in
mine now):<br>
<blockquote>
<address>if [ -x /usr/local/bin/tmpcleanup ]; then</address>
<address> /usr/local/bin/tmpcleanup</address>
<address>fi</address>
</blockquote>
<ul>
<li>The file 'tmpcleanup' merely creates a subdirectory in /tmp,
based on the date/time, and moves everything currently in tmp into the
new dir.</li>
<li>Exceptions are that it doesn't move files that appear to be prior
dirs cleaned up already with tmpcleanup.</li>
<li>Again, nothing gets deleted, only moved, but it's easy to tell
what files are almost certainly not needed anymore.</li>
<li>The script (only?) runs at system boot.</li>
</ul>
At least it helps me keep /tmp clean, or at least less cluttered.<br>
<br>
Now, having said all that, I'd be happy to submit the tmpcleanup script
(perl), I'd be happy to submit the changes to rc.sysinit, but how
should I go about doing that?<br>
<br>
I've not used CVS before, I don't know how to build RPM's. I just run
my system, and help with others, and thought I'd see about submitting a
small change that helps me out.<br>
<br>
My suspicion is that the best thing is to submit a change so that a
directory is created, called "rc.sysinit.d" in /etc/rc.d, and in the
rc.sysinit dir, create subdirectories that are called (much like rc1.d,
etc) at certain points. For instance, have a hook that is called when
local filesystems are mounted.<br>
<br>
But I might be getting ahead of myself with that.<br>
<br>
My aim is to have one less thing to customize when I re-do a system.<br>
<br>
Comments?<br>
<br>
-Ron<br>
<br>
</body>
</html>