Bugs found

Bugs found

[Tommy McCabe]

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 

Re: Bugs found

[daniele giacomini]

Hello,

I remember similar problems one year ago (last summer); in particular
with the Init program. I have noticed that only some real machines work
fine with Init; with some others, it is not able to start the login and
it goes into an infinite loop.

I just tryed to build a reasonable Elks floppy for my experiments and
you can find at http://cdn.mirror.garr.it/mirrors/AppuntiLinux/nanoElks/
I also have kept the original files I have used to build it (the src/
directory). It is shure that there are machines where it works.

I am not prepared to "repair" Init, but I think to remember that it
can be recompiled enabling debugging info.

Saluti/Regards/Gruesse, 
daniele giacomini - daniele (ad) swlibero.org

TM> Date: Thu, 18 Aug 2005 09:30:37 -0700 (PDT)
TM> From: Tommy McCabe <rocketjet314@yahoo.com>
TM> To: linux-8086@vger.kernel.org
TM> Subject: Bugs found
TM> 
TM> After compiling the full3 disk image, I tried to boot
TM> it on a standard PII. The kernel loaded fine, but I
TM> got a BIOSHD error when it tried to read init off the
TM> disk. I checked the floppy; the file was perfectly
TM> readable. I then tried to make full3 unbootable so I
TM> could load it using a boot and root disk (why do the
TM> boot and combination images use different loaders?) It
TM> loaded init fine, but init then panicked and started
TM> getty (Aren't programs supposed to panic when they
TM> can't do their job?), which started login, which then
TM> couldn't find the shell. I traced the panic to line
TM> 331 of elkscmd/sys_utils/init.c, and the login failure
TM> to the function execl at line 89 of
TM> elkscmd/sys_utils/login.c failing to execute. I
TM> serached the CVS directory and couldn't find a
TM> definition of execl, so I figured it must be a typo
TM> and changed it to execv, but then why does it appear
TM> in so many other programs? I deleted the PANIC
TM> statement from init and tried to boot ELKS again, but
TM> nothing at all came up- just a blank screen after init
TM> finished loading. Please help.
[...]

mailing list archive

[Hans]

Hi All,

Does anybody know were I can find the mailing list archive? the link on the
ELKS site seems dead.

Thanks,
Hans.
www.ht-lab.com


Archive
An archive of the mailing list is maintained at
http://rainbow.cs.unipi.gr/linux-8086-list .

Mailing List Archive.

[Miguel Bolanos]

Greetings all.
While browsing on the web i found a mailing list archive that is not
listed on our site, shall we add it?

http://news.gmane.org/thread.php?group=gmane.linux.ports.x8086

Miguel.