Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: zone22 on March 02, 2011, 02:17:31 PM
-
I'm new to Tiny Core and have a very basic knowledge of Linux. I'm running a tiny core based distribution in virtual box. I was hoping someone could walk me through the process of installing 2n2. More information on the program can be found here.> http://www.ntop.org/n2n/
-
Tinycore is not compatible with Debian stuff. Your best bet without compiling the stuff, is to download the debian package and use the script in the scripting sub-forum for converting.
http://forum.tinycorelinux.net/index.php?topic=2325.0
Failing that you would need to compile the package for tcl. There are instructions on that but be prepared for a fair amount of work.
-
Ok, when downloading n2n debian I have the following:
n2n_2.0.0~svn4035-1.diff.gz
n2n_2.0.0~svn4035-1.dsc
n2n_2.0.0~svn4035.orig.tar.gz
None of which ends in .deb
So this means that the script won't work?
-
Unfortunately not. Try unpacking those packages with 7-zip and check out the contents. Perhaps that will give more info.
-
INSTALL
To build the programs:
$ make
To install the programs and man pages:
$ make install
or
$ make PREFIX=/usr/local install
RPM Package
-----------
These steps should work with RPM based Linux distributions since rpmbuild was
split from the rpm utility (c RedHat 9).
To build an RPM the easy way follow these steps.
1. Build SRPM
$ cd n2n
$ scripts/mk_SRPM.sh
Look for where the src.rpm file was put ( "Wrote:" ).
2. Build binary RPM from SRPM
$ rpm -i path/to/n2n-<ver>.src.rpm
$ rpmbuild -bb n2n.spec
All this can be done as non-root user if you have a ~/.rpmmacros file with this
line in it:
%_topdir /home/username/rpmtopdir
To build an RPM the hard way follow these steps.
$ cp -a n2ndir n2n-2.0
$ tar czf n2n-2.0.tar.gz n2n-2.0
$ mv n2n-2.0.tar.gz /usr/src/redhat/SOURCES
$ cp n2ndir/n2n.spec /usr/src/redhat/SPECS
$ rpmbuild -bb n2n.spec
there is a scripts folder:
mk_deb.sh
mk_SRPM.sh
mk_tar.sh
-
Umm... and why would you not follow the link to the binaries on the download page of that project and just get those? ???
-
Umm... and why would you not follow the link to the binaries on the download page of that project and just get those? ???
Apparently the web page is unavailable for the binaries.
-
In the meanwhile, I think I found the answer to my upper question myself: fact is, that their download page is a chaos and their info and links are a messup.
I suspect what you might want could be here:
http://sourceforge.net/projects/ntop/files/n2n/binaries/linux/
HTH
-
Thank you. I'm not sure which version of the binaries that link contains. I have a sneaking suspicion that the Binaries are 1.3 and the latest is 2.0. I might e-mail the developers.
-
If you run them with a '-h' option you will find out ;)
-
Here's what happens running the '-h' option:
BusyBox v1.18.3 (2011-02-11 12:08:19 PST) multi-call binary.
Usage: tar -[cxtzjZmvO] [-X FILE] [-f TARFILE] [-C DIR] [FILE]...
Create, extract, or list files from a tar file
Operation:
c Create
x Extract
t List
Options:
f Name of TARFILE ('-' for stdin/out)
C Change to DIR before operation
v Verbose
z (De)compress using gzip
j (De)compress using bzip2
Z (De)compress using compress
O Extract to stdout
h Follow symlinks
m Don't restore mtime
exclude File to exclude
X File with names to exclude
T File with names to include
tc@box:~$
-
Umm, it is implied running the untarred executables with '-h' option... :o
-
It has version 1.3 and 2.0 :). So whats the next step?
wget http://sourceforge.net/projects/ntop/files/n2n/binaries/linux/linux32.tar.gz/download
tar -zxvf linux32.tar.gz
-
Refer to Reply #9 ?
-
It has version 1.3 and 2.0 :). So whats the next step?
wget http://sourceforge.net/projects/ntop/files/n2n/binaries/linux/linux32.tar.gz/download
tar -zxvf linux32.tar.gz
Untar the contents to /tmp, and execute the command to run the program in a terminal (ie type in the name of the binary).
Note any messages which indicate missing dependencies. It will be messages like such-and-such not found. Search the tcl repo for those missing files, download and load the package containing the missing files, and try again until it runs.