On Mon, 16 Jul 2001, Andrew Smith wrote:
> > Still looking for the README with any relevant statement.
>
> Well, your right there, it's called "RELEASE-NOTES" and to
RELEASE-NOTES != README
File-on-install-CD != Local-Documentation
> > none of *MY* boxen have ever been rooted. Or used as a spam relay.
> >
>
> Ah, but do you know for sure? :-)
> It's a bit like saying "my software has no bugs"
> I would actually suggest that you have not idea
> how often people try to port scan or hack into
> your servers.
> You statement certainly suggests that.
No, my statements suggest careful setup, security and monitoring. No, I
can't be 100% positive - nobody can. But a cracker who doesn't screw up
my box, doesn't alter system files or configurations, doesn't appear in
(or trash) my logs, and doesn't get people sending me nastygrams is a
lot more welcome on my box, and less destructive, than most of the
owners of said boxen.
Your suggestion, that I don't have a clue, is just repetitive,
inaccurate, and tiresome.
> The problem is not that you are familiar with sendmail,
> but that when something changed, you decided that it
> shouldn't change unless they documented the change in
> a specific manner you required (hmmm well RELEASE-NOTES
> wasn't good enough)
Well, yeah. Most distributions document the changes made to third-party
software in a ChangeLog or a README.<distro>, that's located with that
software's documentation. On the local disk.
> Then you didn't even find the comments in the sendmail.mc
> That suggests either you don't know what you are doing
> or you didn't bother to look in the most important file
> that defines and controls how sendmail works in RedHat 7.1
That's patently wrong. You don't even NEED a sendmail.mc on the system.
Not in RH 7.1 or any other OS. sendmail.mc doesn't control sendmail at
all.
> Ah, so bash is used to read in and process .procmailrc
> Now I would never have guessed that. :-P
I figured you would, but calling that behavior "undocumented" was as
insulting as the rest of your crap.
> So if I want to have a ? in my filename I
> HAVE to escape that with a \? since bash
> matches both "ab?cd" and "abxcd" with the
> pattern "ab?cd"
No, a good unix admin just wouldn't use metacharacters in his filenames.
> But reading the FAQ I have finally found an
> example that would suggest that you need to
> escape spaces coz you can list more than one
> output folder separated by spaces if they are
> directories.
Right, that's the whole "escaping the embedded whitespace in the
filename" thingy "so your shell doesn't see it as multiple names".
See ya later,
Doc
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
