On Sun, Nov 10, 2024 at 10:08:47 -0700, pe...@easthope.ca wrote: > From: <to...@tuxteam.de> > Date: Sun, 10 Nov 2024 17:30:42 +0100 > > But perhaps Make is right and utelnetd is built and ready to go? > > > > What evidence would you have that it is not so? > > # ls -ld /usr/local/bin/u* > ls: cannot access '/usr/local/bin/u*': No such file or directory
Is this your first time building software from source code? Normally there are three steps: 1) Configure it to build on your system; this may involve running a shell script or a perl script, or editing files manually. This is normally done as yourself. 2) Run "make" or "cmake" or some equivalent program. This is normally done as yourself. This builds the program(s) in the current directory, or some subdirectory. 3) Run "make install" or something equivalent, to copy the program(s) to the system directories. This usually requires root privileges. > # cd /usr > # find . -type f -name "utelnetd" > # So what you're telling us is that you've done the first two steps, and utelnetd has been built in the build directory, but you haven't installed it into /usr/local/bin yet. Now, I have absolutely no idea what this "utelnetd" does, other than what I can guess from its name. But if it's supposed to be a *telnet daemon* that you run and connect to, then installing it in /usr/local/bin (or somewhere) is only going to be one step among several. You'd also need to arrange for it to be run as a service. If you're struggling with understanding the difference between "make" and "make install", then getting this third party program running as a service is going to have quite a learning curve for you. The first question I had when I saw this thread was "Why on *earth* is he trying to run a third party telnet daemon?" What's wrong with the telnet daemon that's included in Debian? Why would you even want a telnet daemon in 2024? It's so incredibly insecure! But hey, maybe the name is a red herring, and it does something else entirely. Who knows. Anyway, I suggest you read the documentation more closely. If the documentation isn't adequate for someone with your skill set (which is quite probable with third party programs), then please explain to us what you're *trying to do*. We'll probably tell you to throw this thing away and use something else.
