Well. I was the person originally that said it was quite slow. This was to basially stop any people asking if they've broken it or not installed it properly

But I do agree with you, for a telnet daemon it's just not worth it

- Trevor

Does this daemon need to be run from a terminal login(serial) every time you want to be able to telnet in via ethernet?

Nope. If you install Bitt Faulk's preinit utility then you can start up the telnet daemon every time the empeg reboots. That's what I'm using to do it anyway.

- Trevor

ok, sorry if i'm seeming like i'm needing a walkthrough, but I can't seem to find any docs on this preinit. I installed it (I think, per windows/DOS instructions). Now what?

nevermind, I found the old post about VNCserver describing it's use

thanks

ok so I have installed telnetd into /empeg/bin
I installed preinit
and I created a script calle N10telnetd that looks like
#!/bin/sh
/empeg/bin/telnetd

I tried to run it at mount with M10telnetd

But no luck. if I run telnetd from the shell I can get it to work.

It just won't automatically start.

Make sure your script has exec privs.

chmod +x N10telnetd

Make sure your script doesn't have windows line feeds, use TextPad or something similar to create the file.

Tom

Actually, it doesn't need to be set executable. Doesn't hurt if it is, though. The CR/LFs are probably the problem. To test, you could run ``/bin/sh /etc/preinit.d/N10telnetd'' and see if that works. If it doesn't, then the problem is with the script.

It is set to executable, and running it via
``/bin/sh /etc/preinit.d/N10telnetd'' works

but it still does not run at boot time

Hmmm.

Do you have other startup scripts? Do they work? Can you see preinit starting on boot at the serial console? Try adding some echo lines in the N10telnetd startup script and see if they get printed out.

Hmm Perhaps preinit didn't get installed correctly?

What should we see on the serial if preinit starts correctly?

empeg-preinit starting...

and

empeg-preinit complete

Along with some other things if errors occur.

Okay, I've compiled the busybox implementation of telnetd. Works quite well with the preinit utility.It is incredibly slow when the player is running though! Pause the player if you want to do anything.
To install:
Upload the attached file to the empeg
Untar it (tar zxvf emptelnetd.tar.gz)
Run the devs file
You can delete the devs file and the emptelnetd.tar.gz files from your empeg now.


How exactly does one "Run the devs file"
I imagine it involves hyperterminal, which I can do,
I've uploaded emptelnetd.tar.gz
I've done the tar zxvf emptelnetd.tar.gz
This is where I get stuck...
I just can't seem to figure out how to "Run the devs file"
from there I think I can swing it,
I was able to get the viewer running at boot time last night.

Not having played with the package in question, so I might be wrong, but:

from the comand prompt and in the directory where you placed the devs file:
#make it executable
chmod 755 devs
#run it
./devs

/Michael

Yep. What you said

- Trevor

Okay, I've compiled the busybox implementation of telnetd.

Sorry to resurrect an old thread, but does anybody know if it is possible to get this to require authentication? I don't want to do the whole login/password file deal, but a single hardcoded password like hijack can use for kftpd would be nice for when my empeg is on the company network.

-Mike

Haven't looked to find out. But it'd be nice.

Actually, telnetd in kernel space would be nice

Sure. It shouldn't be hard to change it to do that. It's either revert it back to the original method where it executes /bin/login or I suppose I could hack it into the telnet daemon directly. I'll have to think about it. On one side it's easier to write but ont he other it means having to deal with more than one file.

- Trevor

There is no /etc/passwd, and IIRC no /bin/login either on the empeg.
The ideal thing to do (from the users' perspective) would be to use a config.ini password, but you might have a problem trying to read config.ini at that time - hijack and the player app are already fighting over it.

Yeah I know. I'm just saying that originally the busybox telnet daemon would run /bin/login to do the username and password checking then finally run the shell.

I would write a empeg specific login. Or I could change the telnet daemon to do the authentication itself. Not sure.

Okay, it's not optimal about disk access but if I just make it read config.ini each time it receives a connection then it shouldn't have to worry about problems with accessing config.ini. Or it could cache the password the first time it's needed. This last option could be confusing for users though.

- Trevor

There are NO issues with lots of apps trying to read the same file at the same time, not even config.ini (in Hijack v309).

Cheers

Ok, I mis-read or mis-understood something somewhere. I'm glad that you've corrected me as I couldn't understand why there should be any issues.

Well, there may (or not) have been a conflict in earlier Hijack versions with config.ini, buy not now.

Cheers

Did you ever get this working? I found that I needed to place telnetd into a directory that was seen at boot time. I was having problems when telnetd was in /drive0/var/..., but when I moved it to /bin it works no problem.