Is anyone else having trouble with preinit. I had it launching EmpegVNC at boot reliably with beta7 but evver since I installed beta11 it is kaput. EmpegVNC runs fine if I start it from the shell prompt and I have fussed with reinstalling preinit and confirming my script, in /etc/preinit.d hasn't changed. I guess this could also be related to a Hijack update.

I don't really understand where the preinit code ends up because I can't seem to find it after going through the install procedure. Perhaps it gets burried in Hijack or ????

Any clues would be appreciated.

Lynn

When you installed b11, it overwrote preinit. You'll have to reinstall it, unfortunately.

As indicated in my post, I have reinstalled preinit. Where on the Empeg does the code end up?

Lynn

Oops. Sorry. It creates the file /bin/hijack and the directory /etc/preinit.d, and that's it. I haven't played with it with b11. Let me see if something's changed that affected it.

I have the directory (with my script) and the file present. Thanks for taking a look at it.

Lynn

Hmmm. Everything seems to work for me. What version of empegVNC are your running and what does your startup script look like?

Running empegVNC-0.7 with the following script in /etc/preint.d:

#!/bin/sh
/empeg/bin/empegVNC

All of this was working with beta 7 and empegVNC still works fine if I launch it from the shell prompt.

Lynn

That's what I just tested. It works fine on my player. Weird. Throw another script in that directory that just echoes out some text to stdout (``echo testing'', for example) and watch the startup output to make sure that it's getting run. You should see this text. It may be easier to see if you have multiple lines of text output. It should occur shortly after ``Trying to unmount old root'' and shortly before ``Mounting proc''. Also, make sure that /bin/hijack is set as executable, if you can. The scripts need not be.

Bitt,

I have it working again now. I am slowly learning how to use this thing! I had a directory/file location error and finally found the clue by studying the data stream on the serial port during boot. I still don't know why it used to work because I don't think I changed any of the file locations.

Thanks again for your help.

Lynn

what did you do to fix it? becuase im getting the same problem been messing with it for hours

It was really simple in my case. I had empegVNC in /bin/ and my preinit script was pointing to /empeg/bin/ duh! I finally found it by looking at the serial port data stream during boot very carefully. Look at the part of the stream around here (worked ok in this example):

empeg-pump v0.03 (19980601)
Press Ctrl-A to enter pump...VFS: Mounted root (ext2 filesystem) readonly.
change_root: old root has d_count=1
Trying to unmount old root ... okay
Freeing unused kernel memory: 4k initempeg init 0.8
I see this is a developer image!
Mounting proc
Mounting first music partition

I think preinit accounts for the end of the line that starts with "Freeing unused...," preinit error messages should show up just above "Mounting proc" as indicated by Bitt in one of the above posts.

Good luck.

Lynn

Actually, that's not true. preinit itself doesn't print anything, though the shell scripts it runs might. All of those messages you see are either from the kernel or from the real init program.