From: James Buchanan <buchanan@iinet.net.au>
To: ckkashyap@spymac.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Re: building MINIX on LINUX using gcc
Date: Mon, 07 Jun 2004 19:01:21 +1000 [thread overview]
Message-ID: <1086598881.2226.24.camel@localhost> (raw)
In-Reply-To: <20040607083648.489254C050@spy10.spymac.net>
> >PS. Get the official MINIX sources, and use a XX-to-YY translator or
> Where do I get the official sources from?
http://www.cs.vu.nl/pub/minix/
> What can I do to make it loadable by GRUB or so. I understand that /minix is a concatination of the various a.outs. Can I write a tiny executable
> that will get loaded by GRUB that loaded /minix beyond 1M. Are there many initializations that need to be done before this?
You have to modify the startup code to accept the multiboot structure
and do something with it. You can compile it into an ELF image if you
want to, nothing wrong with that. Then compile the MM and FS tasks as
a.out executables and specify them as modules on the GRUB command line,
and load them from the kernel to the place you want them (much easier
than the nasty way it's done so far). You'd need to make extensive
modifications.
I suggest using GRUB to chainload instead. You put the Minix bootsector
and boot program into the Minix partition and GRUB can chainload from
there. No modification of sources needed for that.
Minix expects certain areas of its compiled binary to be patched by
boot, so don't make it a multiboot compliant kernel and load the servers
separately without knowing what you're doing. So chainloading with GRUB
is by far the easiest way to go.
Have fun :)
James
prev parent reply other threads:[~2004-06-07 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 8:36 Re: building MINIX on LINUX using gcc ckkashyap
2004-06-07 9:01 ` James Buchanan [this message]
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=1086598881.2226.24.camel@localhost \
--to=buchanan@iinet.net.au \
--cc=ckkashyap@spymac.com \
--cc=linux-kernel@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