LOL..
Do I need to be a computer programmer now to figure out what files I can update safely
and which
ones I should ignore, keep, throw-out...ect.ect..
Now I know I'm new to this, but this seems a little ridiculous.
The only files that I'm familiar with are the ones that I touched
My rule of thumb - if I haven't touched it myself then I
turn etc-update loose. Usually it's hosts, make.conf,
fstab and files that you have to edit and setup that I do
manually. Most of the files below you can let etc-update
have it's way. I don't know about dispatch-conf.
On Wed, 17 Sep
Joshua Banks [mailto:[EMAIL PROTECTED] wrote:
Do I need to be a computer programmer now to figure out
what files I can update safely and which
ones I should ignore, keep, throw-out...ect.ect..
Now I know I'm new to this, but this seems a little ridiculous.
I agree.
The only files that
On 14:27, mercoledì 17 settembre 2003, Joshua Banks wrote:
1) /etc/dispatch-conf.conf
/etc/._cfg_dispatch-conf.conf
Don't know, I don't use it.
2) /etc/issue
/etc/._cfg_issue
I kept mine, but if you replace it with the suggested one it won't hurt too
much. This file contains the
On Wednesday 17 September 2003 21:27, Joshua Banks wrote:
LOL..
Do I need to be a computer programmer now to figure out what files I can
update safely and which ones I should ignore, keep,
throw-out...ect.ect..
You don't need to be a programmer at all - that's much harder. What you
On Wednesday 17 September 2003 3:50 pm, Jason Stubbs wrote:
On Wednesday 17 September 2003 21:27, Joshua Banks wrote:
LOL..
Do I need to be a computer programmer now to figure out what files I can
update safely and which ones I should ignore, keep,
throw-out...ect.ect..
You
On Thursday 18 September 2003 00:08, Ian Tindale wrote:
On Wednesday 17 September 2003 3:50 pm, Jason Stubbs wrote:
On Wednesday 17 September 2003 21:27, Joshua Banks wrote:
LOL..
Do I need to be a computer programmer now to figure out what files I
can update safely and which
