After compiling the full3 disk image, I tried to boot it on a standard PII. The kernel loaded fine, but I got a BIOSHD error when it tried to read init off the disk. I checked the floppy; the file was perfectly readable. I then tried to make full3 unbootable so I could load it using a boot and root disk (why do the boot and combination images use different loaders?) It loaded init fine, but init then panicked and started getty (Aren't programs supposed to panic when they can't do their job?), which started login, which then couldn't find the shell. I traced the panic to line 331 of elkscmd/sys_utils/init.c, and the login failure to the function execl at line 89 of elkscmd/sys_utils/login.c failing to execute. I serached the CVS directory and couldn't find a definition of execl, so I figured it must be a typo and changed it to execv, but then why does it appear in so many other programs? I deleted the PANIC statement from init and tried to boot ELKS again, but nothing at all came up- just a blank screen after init finished loading. Please help.
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe from this list: send the line "unsubscribe linux-8086" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
