arpwatch doesn't work with current libpcap

Robert Kryczało laro w bro.net.eu.org
Wto, 16 Sty 2001, 17:33:59 CET


Thanks for your response!

I will try to answer multiple letters at once:

Arkadiusz Miskiewicz wrote:
> Just updated libpcap (cvsversion), tcpdump (cvsversion) and
> arpwatch (2.1a10).
>  8193 root       0   5  2196 2196   652 S N   0,3  7,2   0:00 arpwatch
Thanx, I will check it out ASAP.

Sebastian Zagrodzki wrote:
> On Sun, 7 Jan 2001, Robert Kryczało wrote:
> > 2. all i need is to install a stripped version of a system, using --root
> > <dir> option (the list of packages should be taken from coinst/
> directory
> > (hm, well i have just rsync'ed part of PLD ftp site, and this
> directory is
> > empty. Have those files moved?)
> well, actually, they were kind of out-of-date, so I removed them,
> leaving only "base" list (it's on bootdisk.img). If anyone would like
> to prepare any list (``workstation(X)'', ``builder'' and so on) -
> please do. Put it into CVS bootdisk module
As soon as I get cvs worked out, i will. BTW, what about other lists, for
example lets say "chroot-builder". Maybe I should create additional
"kickstart" module, which should contain all the lists? I think it would be
handy for some of us.

> > 3. to do so i also need to create basic directory tree, just
> the way it is
> > done before starting prowizorka when installing PLD (addbase)
> no, I guess you don't - this is done only to make place for misc.
> utilities and kernel modules, before the installation process start. If
> you don't use bootdisk.img to install PLD - the only thing you have to
> do is to run "rpm --root ... --initdb" and then copy /var/lib/rpm/Packages
> as
> /var/lib/rpm/{Basenames,Group,Requirename,Conflictname,Name,Provid
> ename,Triggername}
Thanks. It was also necessary to create /var/lib/rpm.

Lukas Dobrek wrote:
> Only for your own use you probably dont need pld-builder. It is a package
> which gives you a posibility to sends builld requests via email.
> In private
> use you will only need lets say special user "builder". In fact
> you dont need this user you can do it from normal accout but lets
> keep order.
> User builder can be  either in chroot either in normal
> system with installed pld resources. Then (cvs get rpm) will create
> the whole directory tree and start downlowding all SPECS. Stop it
> (^C) you dont need
> all SPECS. Then (cd rpm) and (cvs get SOURCES) just to create
> neccesary directoris.
> This ofcourse stop to (^C) you dont need all SOURCES as well.
> The last thing what you need is a couple of scripts. Command (cd
> ~/rpm/SPECS)
> followed by (cvs up builder getsrc) will download them.
> Now if you want to build something you just need to start
> (./builder glibc.spec)
Thank you. I have done it before that way, but.... hm, all packages I build
require ircd!!!!!. Currently my build enviroment is placed on PLD machine
running some other services like squid, ircd, innd etc. Ircd is
ircd-2.10.3-1 taken from Mandrake. In chroot'ed enviroment everything works
fine, it is also easier to create packages, which are linked with the same
libraries.

> If you want to create chroot enviroment, you will probably need to do it
> by hand. When you will finish pleace send heare resault of
> (rpm --qa --queryformat "%{NAME}\n") then next time it will be simpler.

There is a cookbook below for all who wants to create his/her chroot'ed
builder enviroment.
***********
chroot'ed builder destination path: /mnt/devel/build-chroot
current path points to RPMS directory /mnt/devel/PLD/RPMS

mkdir /mnt/devel/build-chroot/var
mkdir /mnt/devel/build-chroot/var/lib
mkdir /mnt/devel/build-chroot/var/lib/rpm

rpm --root /mnt/devel/build-chroot --initdb

cd /mnt/devel/build-chroot/var/lib/rpm

cp Packages Basenames
cp Packages Group
cp Packages Requirename
cp Packages Providename
cp Packages Triggername
cp Packages Name

to clean up rpm database, i think it would be better to issue this before cp
commands but i am to lazy to check it out

rpm --root /mnt/devel/build-chroot --rebuilddb

cd /mnt/devel/PLD/RPMS

i think the first step should be as follows:

rpm --root /mnt/devel/build-chroot -Uvh setup* FHS* basesystem* dev*

here goes the complete list of packages .... (output of:
rpm -qa --queryformat "%{NAME}\n")

FHS
basesystem
rpm
pdksh
file
texinfo
binutils
gcc
grep
bash
bzip2
db3
make
cracklib-dicts
zlib
cpp
info
popt
tar
mktemp
m4
textutils
kernel-headers
setup
dev
rpm-build
glibc
sh-utils
patch
findutils
glibc-devel
pcre
fileutils
perl
db1
pam
cracklib
rpm-libs
readline
fix-info-dir
ncurses
mawk
gzip
autoconf
sed
diffutils

This basic list will do in case of squid (without transparent proxy support)
and oidentd, for more advanced stuff (like signing packages with pgp keys)
some other tools are be required. Fire at will.
**********

Remarks: [probably they have no mean because my lack of knowlege]
1. tar ang gzip are necessary to decomprees source tar.gz archives (should'n
they be required by rpm-build)?
2. sed, cat[from textutils],cmp [diffutils] are used in the process of
preparing makefiles (at least for squid), i think they should be required by
autoconf

Robert Kryczało



Więcej informacji o liście dyskusyjnej pld-devel-pl