[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RAID HOWTOs
On Jan 20, 9:34am, Gregory Leblanc wrote:
> Subject: Re: RAID HOWTOs
> Greg Ferguson wrote:
> > On Jan 20, 9:06am, Gregory Leblanc wrote:
> > > Subject: Re: RAID HOWTOs
> > > ...
> > > This would also help people who want to help out
> > > with the LDP by taking up maintence of HOWTOs that aren't being
> > > maintained.
> > Would it help if I put together a list of those HOWTO's that haven't
> > been modified in "X" amount of time, with pointers to the docs
> > themselves?
> I've noticed that a lot of the HOWTOs use a timespan of six months in
> "dating" the document. I.E. if this document is older than six months,
> then check URL for more information. Does this sound like a reasonable
> timespan for the LDP to adopt? I realize that some documents will last
> much longer, and some won't last anywhere near that long, but on
> > We would then have to determine if the doc itself is still relevent,
> > in a given context.
> This should just be a matter of having someone familiar with the subject
> read over it.
> > This is something that could be done quickly. Perhaps the
> > page containing this info would have a "mailto:" pointer
> > that would come back to this list? - "If you are interested in
> > working on/modifying/etc this document click...".
> Sounds good to me.
I have a script to generate this info. Not being sure of what time
amount to use, I simply went against *all* various howto's and
sorted according to the modify date ("stale" to "fresh").
I didn't put the email link in (I can). For now, I'll use the script
to generate a static html page. You can see a copy of the output:
Let me know about format changes, additions, subtractions, etc.
Is this useful?
Greg Ferguson - s/w engr / mtlhd | email@example.com
SGI Tech Pubs - http://techpubs.sgi.com | 410-785-2334
Linux Doc Project - http://www.linuxdoc.org |
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com