From: Miguel Bolanos <mike@costarica.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-8086@vger.kernel.org
Subject: Re: Bugs (and some fixes)
Date: 12 Apr 2004 15:34:26 -0600 [thread overview]
Message-ID: <1081805666.3006.29.camel@talena> (raw)
In-Reply-To: <1081790412.2279.24.camel@localhost.localdomain>
Greetings Alan and all,
On Mon, 2004-04-12 at 11:20, Alan Cox wrote:
> On Llu, 2004-04-12 at 15:19, Tommy McCabe wrote:
> > The linker won't link any code segments larger than
> > 64KB. (Fix: Use a different compiler, maybe the one
> > from FreeDOS or Minix)
>
> Processor limit.
>
> >
> > The kernel prints out lots of 0's mixed in with the
> > boot messages on bootup. (Fix: Remove the single
> > quotes around the 0 in line 139 of
> > elks/kernel/printk.c)
>
> You should probably check any fixes you make into the tree
> btw as I think its otherwise dead.
>
Well there are a few of us with access to the tree hanging around, the
whole project is not totally dead, but i guess most of us are quite busy
with work and/or other projects like yourself.
The best way to ensure that patches are included is sending them over to
the list and not forgetting to add "[PATCH]" to the subject
best wishes
Mike
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2004-04-12 21:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-12 14:19 Bugs (and some fixes) Tommy McCabe
2004-04-12 17:20 ` Alan Cox
2004-04-12 21:34 ` Miguel Bolanos [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-12 21:31 Tommy McCabe
2004-04-13 9:28 ` David Given
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1081805666.3006.29.camel@talena \
--to=mike@costarica.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-8086@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox