is cowpatty available for opensuse 11?
i wish to test out my home wireless.
dope540 wrote:
> is cowpatty available for opensuse 11?
>
> i wish to test out my home wireless.
It is available as source. You will need gcc and libc to compile and
build it. It also requires the libpcap-devel libgcrypt-devel packages.
Larry
they in the repos?
is there a guide on how to compile and build stuff, i’m fairly new to linux and am getting into it. it’s forcing me to learn new stuff.
dope540 wrote:
>
> they in the repos?
>
> is there a guide on how to compile and build stuff, i’m fairly new to
> linux and am getting into it. it’s forcing me to learn new stuff.
Learning is a good thing.
AFAIK, there is not an rpm package, but building from sources is very
easy. In fact, satisfying the prerequisites is the hard part. Besides
the 4 I mentioned earlier, you will need the make package.
First, you download the source file, which will be a file made by tar
(somewhat like zip) and probably compressed. If the file has the
extension “.tar”, it is not compressed. If the extension is “.gz” or
“.tgz”, it was compressed with gzip. If the extension is “.bz2”, it
was compressed with bzip2. You could decompress it before untarring;
however, tar does it on its own. You open a terminal and issue the command
tar zxvf cowpatty-4.3.tgz
This will unpack the routines, and place them in the directory
cowpatty-4.3/ under the current directory. The z switch indicates that
the file is compressed with gzip. If bzip2 had been used, then the j
switch is needed. The x switch says to extract, v means to list the
files as they are created, and the f means that the next parameter is
a file name. One untarred, issue the ‘cd cowpatty-4.3’ command,
followed by ‘make’, which will build the two programs in the package.
As long as the prerequisites are satisfied, it will build. To put the
executables in a directory in your path, use the ‘sudo make install’
command. That is essentially the method used to build any program. In
some instances, you will need to configure before the make step. The
command for that is ‘./configure’. The ./ construction says to use the
current directory. For security reasons, most systems will not allow
you to execute a program in the current directory with a naked
command. Thus ‘configure’ would fail.
Enjoy.
Larry