On Monday 14 January 2002 10:25 PM, secret-squirrel,AT,hetnet,DOT,nl wrote:
> Hi Dragos + others,
> I hope you can spare some more time with me. I'm not that good at compiling
> and the README.Debian of Cipe 1.5.2 is not all that clear to me. I have
> compiled my own (stripped down) kernel and I still have the kernel image
> (.deb) say: kernel-image-2.2.19_mythiq.1.2_i386.deb I do not, however, have
> the remains of the kernel source after unpacking, make config, make-kpkg,
> etc. (these were in the /tmp and thus removed after rebooting when
> initiating the new image). Can I still compile CIPE now? I get this "error"
> when trying:
> obelix:/usr/src/linux/kernel-source-2.2.19# make-kpkg --revision mythiq.1.2
> modules_image Warning: The mythiq.1.2 option only has an effect during
> the configure phase -- in other words, since the file
> stamp-configure exists, this option has no effect
> run make-kpkg clean or if you know what you are doing,
> manually remove stamp-debian, stamp-configure and
> debian/changelog for it to have an effect
> Please hit return to continue
> I have this nagging feeling I'm going to have to build my kernel all over
> greetz, Mythiq.
not if you still have the .config file.
let me tell you how I did it:
installed cipe-source-1.5.2, cipe-common, kernel-image-2.4.17-686,
kernel-source-2.4.17 (all with apt-get); booted with the new kernel, untarred
the source, copied the /boot/config-2.4.17-686 (comes with kernel-image) to
/usr/src/kernel-source-2.4.17/.config, did an 'make menuconfig' just to make
the symlinks, a 'make dep' (don't know if this is really necessary).
Assuming you untarred cipe.tar.gz that you get in /usr/src, go to
/usr/src/linux (which is a link to kernel-source-2.4.17) and do make-kpkg
modules-image whatever-version; after compiling you get a .deb package in
/usr/src which you install with 'dpkg -i'. That's it!
So I get away without compiling my own kernel (but i have the config).
Now, all you have to do is make a file in /etc/cipe/peers for every
connection you have and it starts automatically at bootup.
PS I found out that following the debian rules is a good and sane thing to do
(I'm new to debian, but I'm learnig fast :))