Imagine a noob installing Debian 2.2r3 having a bit experience with suse... thats me

i figured out that some packages i used to have are not included on the 3 binary cds (openssh, openssl, kde, pine and some others)

i downloaded openssh and the stuff it needs (openssl zlib) and installed them. Now if i wanted to remove/move the stuff how could i possibly ever find the files/links/config entries? do i have to browse the makefile to find all i need or is there some other way of doing it?

another problem is after i installed openssh i started sshd but when i try to log in from another machine i get a permission denied after sending my password, any idea what the problem could be?

next one is X
i dont have any idea how to make xf86config recognize my mouse as a 5 (or even three) button mouse.i have a razer mouse connected to ps/2 with a usb2ps/2 adaptor. with SAX (suse configuration tool for X) i could say 5 buttons, imps2 at /dev/psaux.
gpm runs with imps2 at /dev/psaux too but X wont...
xf86config runs, allright but if i say that i have 3 buttons it stops working.
XF86Setup is acting even stranger. it tells me that i have a Micro$oft device connected to /dev/gsomething (dont exactly remember). when i change this to the settings i used to have with Suse 7., you guess it:the mouse stops working.

hmmm i think thats enough for now, thanks for your help

Here's a section of my XF86Config (it's in SuSE). I had to install imwheel to make it go.

Section "InputDevice"
Driver "mouse"
Identifier "Mouse[1]"
Option "Device" "/dev/psaux"
Option "InputFashion" "Mouse"
Option "Name" "INTELLIPOINT MOUSE PS/2"
Option "Protocol" "imps/2"
Option "Vendor" "MICROSOFT"
Option "ZAxisMapping" "4 5"
EndSection

I was surprised that this actually worked first time(!).

re: sshd. is it running? Are you firewalled?

I think you can look in the makefile to see what packeges are 'installed' by the script.

thanks a lot

i will try the mouse stuff as soon as i have the sshd and qmail thingies solved i guess

i dont think i have any firewall running (i didnt set up ipchains yet) and the logfiles state that i tried to connect on ports 1023 and 1024 and that the password check failed.
sshd IS running but i just started it with sshd (it should find the config file since everything is default... just to be sure i started it with -f <configpath> though ... with no result of course *sniffle*) the key files do exist, they were generated during the 'make install' process i think (references to the keyfiles in the config are correct as well).
i cannot even connect from the same machine so it must be something with the keys or the authentication method i have no clue :/ .


concerning the makefile....i feared that... another thing i have to get into.
Damnit, learning Linux with Debian is pretty hard but at least you have to get into how everything works together

did you do an ssh-keygen? (or is it ssh--keygen???)

man it's been a while since I've built it. Have you tried logging on as different users? (other than root). Debian might not let root login from anywhere/anyport. I know that most distros won't allow root login/ftp/rlogin from remote. I've never had that problem with ssh tho. It does seem wise to not allow root to login from remote as _if_ you are subjected to the theoretical 'man-in-the-middle' attack and if you are not using strict key fingerprint checking, you _could_ unknowingly give up your root password. <shrug>

i didnt have to run ssh-keygen (the files are already there and during install there were messages about the keys being generated)
i tried to log in with different users and root is still allowed (at least in the sshd_config).

even if someone should obtain my root password well... not more to get than screwed up configs on a messy system i guess is there? :P

could it be that its not ssh but ssl or zlib thats messed up or were those only required during build time?

in my etc/ssh/sshd_config it sez "PermitRootLogin no" tho I dont know where OpenSsh differs from Ssh. I make it a habit to never login anywhere as rewt, Ill use sudo...

Next time try this: when u do "make install" make it "make install 2>&1 > ../someApp-install.log" this will redirect all the output to a logfile :-]

U can try the usual suspects, dirs like /etc for configs, /usr/lib for libraries and /usr/bin for binaries.
For each executable u can issue "whereis someApp" and itll return the place the binaries, the man and the config are at. To be sure u can issue "ldd someApp" and itll give u the libraries it depends on, but there uve got to be carefull not to delete system libs. To be sure just make a backup to a dir thats not in the path ldconfig uses before deleting libs.

Did ssl and zlib compile and install without error messages? Did ssh do the same? I'm stumped. I'll have a look at the man pages later tonight.

unspawn: it doesnt work with a std user login either :/
and thanks for the hint with the piping and the
commands


smurf: didnt even get a warning during building the libs...
maybe the config didn't figure out the debian
library paths?(i dont know how close it is to the
standard)i will try to find out if the libs are
where they are supposed to be and check back after
that

Not sure if you are trying to 'uninstall' stuff. If yes, you can try "make uninstall" if you still have your makefile.

HTH