Quote:
Originally Posted by shrikant.odugoudar
1) Please don't work directly as the root user, use 'su' to temporarily switch to root and 'exit' when its done.
|
Yes, I use/used su.
Quote:
Originally Posted by shrikant.odugoudar
2) When you compiled with make and make install, did you get any errors? For eg., it should say 'make : leaving directory so and so...' if all went well. Can you post it?
|
When installing FUSE:
When I type ./configure for Fuse I get a load of checks; e.g. checking for dlfcn.h... yes
The last thing that gets printed out is this:
configure:
NOTE: Detected that FUSE is already present in the kernel, so
NOTE: building of kernel module is disabled. To force building
NOTE: of kernel module use the '--enable-kernel-module' option.
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: config.h is unchanged
Don't know if these NOTEs are significant or not.
Then I type make:
Making all in kernel
make[1]: Entering directory `/home/mark/downloads/fuse-2.6.0/kernel'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/mark/downloads/fuse-2.6.0/kernel'
Making all in include
make[1]: Entering directory `/home/mark/downloads/fuse-2.6.0/include'
make all-am
make[2]: Entering directory `/home/mark/downloads/fuse-2.6.0/include'
make[2]: Leaving directory `/home/mark/downloads/fuse-2.6.0/include'
make[1]: Leaving directory `/home/mark/downloads/fuse-2.6.0/include'
Making all in lib
make[1]: Entering directory `/home/mark/downloads/fuse-2.6.0/lib'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/mark/downloads/fuse-2.6.0/lib'
Making all in util
make[1]: Entering directory `/home/mark/downloads/fuse-2.6.0/util'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/mark/downloads/fuse-2.6.0/util'
Making all in example
make[1]: Entering directory `/home/mark/downloads/fuse-2.6.0/example'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/mark/downloads/fuse-2.6.0/example'
make[1]: Entering directory `/home/mark/downloads/fuse-2.6.0'
make[1]: Nothing to be done for `all-am'.
make[1]: Leaving directory `/home/mark/downloads/fuse-2.6.0'
but this is the second time i've run this.
then make install:
Making install in kernel
make[1]: Entering directory `/home/mark/downloads/fuse-2.6.0/kernel'
make[1]: Nothing to be done for `install'.
make[1]: Leaving directory `/home/mark/downloads/fuse-2.6.0/kernel'
Making install in include
make[1]: Entering directory `/home/mark/downloads/fuse-2.6.0/include'
make[2]: Entering directory `/home/mark/downloads/fuse-2.6.0/include'
make[2]: Nothing to be done for `install-exec-am'.
test -z "/usr/local/include/fuse" || mkdir -p -- "/usr/local/include/fuse"
/usr/bin/install -c -m 644 'fuse.h' '/usr/local/include/fuse/fuse.h'
/usr/bin/install -c -m 644 'fuse_compat.h' '/usr/local/include/fuse/fuse_compat.h'
/usr/bin/install -c -m 644 'fuse_common.h' '/usr/local/include/fuse/fuse_common.h'
/usr/bin/install -c -m 644 'fuse_common_compat.h' '/usr/local/include/fuse/fuse_common_compat.h'
/usr/bin/install -c -m 644 'fuse_lowlevel.h' '/usr/local/include/fuse/fuse_lowlevel.h'
/usr/bin/install -c -m 644 'fuse_lowlevel_compat.h' '/usr/local/include/fuse/fuse_lowlevel_compat.h'
/usr/bin/install -c -m 644 'fuse_opt.h' '/usr/local/include/fuse/fuse_opt.h'
test -z "/usr/local/include" || mkdir -p -- "/usr/local/include"
/usr/bin/install -c -m 644 'old/fuse.h' '/usr/local/include/fuse.h'
/usr/bin/install -c -m 644 'ulockmgr.h' '/usr/local/include/ulockmgr.h'
make[2]: Leaving directory `/home/mark/downloads/fuse-2.6.0/include'
make[1]: Leaving directory `/home/mark/downloads/fuse-2.6.0/include'
Making install in lib
make[1]: Entering directory `/home/mark/downloads/fuse-2.6.0/lib'
make[2]: Entering directory `/home/mark/downloads/fuse-2.6.0/lib'
test -z "/usr/local/lib" || mkdir -p -- "/usr/local/lib"
/bin/sh ../libtool --mode=install /usr/bin/install -c 'libfuse.la' '/usr/local/lib/libfuse.la'
libtool: install: /usr/bin/install -c .libs/libfuse.so.2.6.0 /usr/local/lib/libfuse.so.2.6.0
libtool: install: (cd /usr/local/lib && { ln -s -f libfuse.so.2.6.0 libfuse.so.2 || { rm -f libfuse.so.2 && ln -s libfuse.so.2.6.0 libfuse.so.2; }; })
libtool: install: (cd /usr/local/lib && { ln -s -f libfuse.so.2.6.0 libfuse.so || { rm -f libfuse.so && ln -s libfuse.so.2.6.0 libfuse.so; }; })
libtool: install: /usr/bin/install -c .libs/libfuse.lai /usr/local/lib/libfuse.la
libtool: install: /usr/bin/install -c .libs/libfuse.a /usr/local/lib/libfuse.a
libtool: install: chmod 644 /usr/local/lib/libfuse.a
libtool: install: ranlib /usr/local/lib/libfuse.a
libtool: finish: PATH="/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/mark/bin:/sbin" ldconfig -n /usr/local/lib
----------------------------------------------------------------------
Libraries have been installed in:
/usr/local/lib
If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,-rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'
See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
/bin/sh ../libtool --mode=install /usr/bin/install -c 'libulockmgr.la' '/usr/local/lib/libulockmgr.la'
libtool: install: /usr/bin/install -c .libs/libulockmgr.so.1.0.0 /usr/local/lib/libulockmgr.so.1.0.0
libtool: install: (cd /usr/local/lib && { ln -s -f libulockmgr.so.1.0.0 libulockmgr.so.1 || { rm -f libulockmgr.so.1 && ln -s libulockmgr.so.1.0.0 libulockmgr.so.1; }; })
libtool: install: (cd /usr/local/lib && { ln -s -f libulockmgr.so.1.0.0 libulockmgr.so || { rm -f libulockmgr.so && ln -s libulockmgr.so.1.0.0 libulockmgr.so; }; })
libtool: install: /usr/bin/install -c .libs/libulockmgr.lai /usr/local/lib/libulockmgr.la
libtool: install: /usr/bin/install -c .libs/libulockmgr.a /usr/local/lib/libulockmgr.a
libtool: install: chmod 644 /usr/local/lib/libulockmgr.a
libtool: install: ranlib /usr/local/lib/libulockmgr.a
libtool: finish: PATH="/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/mark/bin:/sbin" ldconfig -n /usr/local/lib
----------------------------------------------------------------------
Libraries have been installed in:
/usr/local/lib
If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,-rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'
See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/home/mark/downloads/fuse-2.6.0/lib'
make[1]: Leaving directory `/home/mark/downloads/fuse-2.6.0/lib'
Making install in util
make[1]: Entering directory `/home/mark/downloads/fuse-2.6.0/util'
make[2]: Entering directory `/home/mark/downloads/fuse-2.6.0/util'
test -z "/usr/local/bin" || mkdir -p -- "/usr/local/bin"
/bin/sh ../libtool --mode=install /usr/bin/install -c 'fusermount' '/usr/local/bin/fusermount'
libtool: install: /usr/bin/install -c fusermount /usr/local/bin/fusermount
/bin/sh ../libtool --mode=install /usr/bin/install -c 'ulockmgr_server' '/usr/local/bin/ulockmgr_server'
libtool: install: /usr/bin/install -c ulockmgr_server /usr/local/bin/ulockmgr_server
mkdir -p -- /sbin
/usr/bin/install -c ./mount.fuse /sbin/mount.fuse
mkdir -p -- /etc/init.d
/usr/bin/install -c ./init_script /etc/init.d/fuse
make install-exec-hook
make[3]: Entering directory `/home/mark/downloads/fuse-2.6.0/util'
chown root /usr/local/bin/fusermount
chmod u+s /usr/local/bin/fusermount
make[3]: Leaving directory `/home/mark/downloads/fuse-2.6.0/util'
mkdir -p -- /etc/udev/rules.d
/usr/bin/install -c -m 644 ./udev.rules /etc/udev/rules.d/99-fuse.rules
make[2]: Leaving directory `/home/mark/downloads/fuse-2.6.0/util'
make[1]: Leaving directory `/home/mark/downloads/fuse-2.6.0/util'
Making install in example
make[1]: Entering directory `/home/mark/downloads/fuse-2.6.0/example'
make[2]: Entering directory `/home/mark/downloads/fuse-2.6.0/example'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/home/mark/downloads/fuse-2.6.0/example'
make[1]: Leaving directory `/home/mark/downloads/fuse-2.6.0/example'
make[1]: Entering directory `/home/mark/downloads/fuse-2.6.0'
make[2]: Entering directory `/home/mark/downloads/fuse-2.6.0'
make[2]: Nothing to be done for `install-exec-am'.
test -z "/usr/local/lib/pkgconfig" || mkdir -p -- "/usr/local/lib/pkgconfig"
/usr/bin/install -c -m 644 'fuse.pc' '/usr/local/lib/pkgconfig/fuse.pc'
make[2]: Leaving directory `/home/mark/downloads/fuse-2.6.0'
make[1]: Leaving directory `/home/mark/downloads/fuse-2.6.0'
again, 2nd time I've run that.
These two outputs are different to what I got originally
Is this what you wanted, when you asked for me to re-post?
Quote:
Originally Posted by shrikant.odugoudar
And 3) May i advise you to upgrade your kernel, 2054 was slightly unstable with SELinux and stuff.
|
Will do.
thanks.
Thanks very much.