Harry Putnam <[EMAIL PROTECTED]> goes on and on:
Harry, obviously you're fairly bright, but it's apparent you haven't
had much experience with women. All I did was ask one stupid question-
and like my X- and you start with this old fish wife routine.
>>No need for deep analysis. Your tools
For some reason, I cannot find any information on
setting up a Tcpdump file to scan for keywords.
Also, x-girlfriend is a cetified witch and I would
like to figure out how to intercept her email.
Will Tcpdump work, or is there something better?
S/MIME Cryptographic Signature
What the hey does this mean! I finally managed to download the bind and
other new security fixes for redhat 4.2 and when I tried to upgrade I get
this lamer on all the new rpms!
I have rpm 2.3.11-1, If I need a new rpm version why isn't it on the errata
list?
First the wrong PAM version in the
>>Who knows, maybe that's your problem too...?
>
>Could very well be. I will be moving all of the stuff from the desktop
>chassis to a tower chassis in the near future, resulting in new power
>connections and cables. I just have to cut longer EIDE cables for the
>tall tower :-(
>
If you are usin
>I use "plplot" a fairly nice plotting package which enables me to call
>graphics from within c or fortran code. With Redhat 4.2 or 5.0
>opposed to Caldera, I get segmentation faults and core dumps upon
>closing of the xwindows. The following script solves the problem
>in a rather ugly way. ( Th
Is there a linux client that can deal with the encrypted passwords that the
microsoft ecxhange server demands?
--wally.
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscr
>I have been looking at linuxhq.com for a patch for
>mounting a fat32 drive. i have to find one . Anyone
>know where one is for kernel 2.0.33?
Get the pre11 patch. Your kernel will then say 2.0.34 has fat32 and joliet
options when you run make config (or xconfig).
Running it for two days now no
>> First, when any user uses xlock, entering the root password at the
>> prompt will stop xlock, returning to the user's screen. Is this
>> intended as a backdoor-type feature?
>Yes, so that the administrator could walk through a lab, and be able to
>unlock any terminal that was locked by a mere
