> tomsrtbt.raw, i find that in the settings.s file, IPADDR is set blank, > and based on that, the above code ( the inconfig,route stuff ) won't > execute. isn't that correct? The 'eval dhcpcd--' sets those variables if a dhcpcd server is available. If a dhcpcd server is not available, you are correct, you have to edit settings.s adding IPADDR, or else it won't start it automatically. > > by itself? That should have *no problems*, if it does, maybe there is > i get a problem. here is the output: > [root@jigra tomsrtbt-1.7.259.unpacked]# 2/usr/bin/lua -e 'write(259+1)' > error: `=' expected; Bizarre. What it the output of "set" or "env" on your machine? Is it possible that some shell processing is affecting it before Lua sees it? That does seem unlikely. It is almost as though it isn't reading the whole string, as though there is a partial read from stdin or whatever, that the interpreter isn't expecting. The error is as if it sees 'write(259+1)' as 'wr' !!! > Version : 5.3.12 Vendor: Red Hat Software Well, I'm using 5.4.13. There really might be a problem where 5.3.12 has a bug, it is a lot older than 5.4.13. If possible, can you install a newer libc5? Actually, try just taking the one on tomsrtbt and copying it over and setting the symlink to point to it! That will answer the question. > what i'm now trying to do, is just try to rebuild the boot disk with the > serial console agetty enabled so i can 'login' through another linux You don't need to really rebuild it for that, just: - mount /dev/fd0u1722 somewhere - edit settings.s and rc.custom.gz to modify inittab and HUP init There is a partial example as a comment in rc.custom.gz, for the telnet server. No need to rebuild! > need be (if it would be a lot easier) i can offer you access to the > machine to test it out also. can you run buildit.s without being root? I have access to a spare machine and I suppose I can get the libc-5.3.12 onto it. It is probably going to end up with me either saying that libc-5.4.13 is required, or offering a static-lua on the website just for this, or running strace on lua to figure out what the problem could be. *IF* it really is a libc problem - so far, I just know that it only has happened on "redhat" systems. -Tom
