* Mailing List Archive.
@ 2003-04-19 20:03 Miguel Bolanos
0 siblings, 0 replies; 2+ messages in thread
From: Miguel Bolanos @ 2003-04-19 20:03 UTC (permalink / raw)
To: linux-8086
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Bugs found
@ 2005-08-19 8:45 daniele giacomini
2005-08-31 15:14 ` mailing list archive Hans
0 siblings, 1 reply; 2+ messages in thread
From: daniele giacomini @ 2005-08-19 8:45 UTC (permalink / raw)
To: Tommy McCabe; +Cc: linux-8086
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.
[...]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-08-31 15:14 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-04-19 20:03 Mailing List Archive Miguel Bolanos
-- strict thread matches above, loose matches on Subject: below --
2005-08-19 8:45 Bugs found daniele giacomini
2005-08-31 15:14 ` mailing list archive Hans
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox