What's the technique du jour to set this up on OS X (PowerBook G4)? I suspect emptelnetd would do the trick, but I think the real trick here is to get it ON the empeg and setup in the first place. Clues welcome!

OK - progress in setting up emptelnetd! "SITE RW" and "SITE RO" (while ftp'ed to a hijacked empeg) are your friend.

Now to get it to run devs once, then telnetd. Maybe an ini file change somewhere ...

Getting closer. empeg-preinit now installed (I think).

VICTORY! I'll post the howto shortly in case someone else happens to be looking for how to do this in one swell foop.

Ingredients:

Latest version of Hijack (I'm using v355)
empeg-preinit
EmpTelnetd

I'll leave installing Hijack and empeg-preinit as an exercise for the reader (and also because the instructions on those sites are quite clear as-is).

One caveat: For empeg-preinit, I didn't create /programs0 and /programs1 (seeing how that requires you be at the shell prompt, which is what we're trying to do here to begin with).

EmpTelnetd comes with a "devs" script that sets up a bunch-a new nodes in /dev. I edited devs so it runs "rw" right before all the mknod lines and also "ro" at the very end. Next, I changed its name to M20devs, placed it in /etc/preinit.d (plus a chmod 755), then I also placed telnetd into /bin (again, chmod 755), and rebooted. This should run M20devs after the drives are mounted.

After the reboot, I went back in with ftp and checked /dev. Sure enough, there were all the new nodes! I now removed M20devs, created a new file N75telnetd (containing one line: /bin/telnetd) and placed it into /etc/preinit.d (again don't forget chmod 755). Another reboot, and I can now telnet to the empeg. Nice.

What next? Well, I'm not too keen on telnetd living in /bin. (Remember /programs0 and /programs1? Yes, that would be much better.) Another exercise for the reader.

When I installed my telnet daemon on my empeg I just used Hijack's EXEC feature in the config.ini file. Works fine for me, no need for preinit.

And who came up with /programs0 and /programs1 anyway? Shouldn't it really be /usr/local/bin ? /usr/local/bin is in the $PATH by default anyway.

Because you can have two drives, but you can have only one /usr/local/bin. Then you'd be stuck with /usr/local/bin and /usr/local1/bin or something similar.

However, you can set up a symbolic link (or two) if it really bothers you. Or you can just do it whatever way you want.

Ah, gotcha. I didn't think of that when I set mine up. I don't have huge storage requirements for my programs so I just mounted the first drive.

Would love to have used EXEC but the latest Hijack no longer has it. Agreed about /programs0 and /programs1 ... but then the motivation may have more to do with /usr being vulnerable when an upgrade is applied. (If that's not true, someone, keep me honest here.)

So now I'm thinking, since I've done this li'l exercise, is there an easier way (using current releases of Hijack, et. al.)? Would a shell installer-type script do the trick? Maybe tie all of this into one script that you drop into preinit, have it run after the mount is finished, and let it do the rest (including adjusting files and whatnot). Worth doing? Maybe there's an easier way and I've just been hallucinating all this time? <LOL>

I'm running v355 and @EXEC works fine. It is the way I launch Empire on startup.

Oh! Wait a minute, I'm thinking EXEC via FTP. I think you're referring to @EXEC in the ini file, is that correct? I thought that was gone too.

Whoops.

Yes, @EXEC in the config.ini file works fine ever since it was implemented way back when. You were probably thinking of SITE EXEC in FTP which I don't think Hijack has ever had. I think that this syntax still applies today. I am actually using a line like this to run a shell script:

;@EXEC_ONCE /bin/bash -c "/usr/local/bin/start_empire 10 &"

Works great.

Some time has obviously passed, but I have just put telnet and some other stuff on my empeg.

Like jdandrea I have no serial port on my Mac G4, so used FTP to place the files in the appropriate places and then used SITE EXEC via FTP (client = Transmit btw) to run devs and then telnetd, no serial connection therefore required.

I read that some hijack releases had problems with SITE EXEC, but 4.17 worked for me with this and other execs I tried. Maybe Mark fixed it.