From: Martin Steigerwald <Martin@lichtvoll.de>
To: "Gideon D'souza" <gidisrael@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: How is an OS bound to the Linux kernel
Date: Sun, 29 Jun 2014 09:07:20 +0200 [thread overview]
Message-ID: <1989531.qh1zHAaciq@merkaba> (raw)
In-Reply-To: <CAPNrq4xV+LiOhbMhBfHFuf68E1D7XCq87EJuTq0n88UMGdcg4g@mail.gmail.com>
Am Sonntag, 29. Juni 2014, 11:54:32 schrieb Gideon D'souza:
> hey guys,
Hi Gideon,
> I generally manage to understand the various pieces of the linux
> kernel and what their functions are.
>
> However, one thing I don't fully understand is how is any OS, say
> fedora (which is what I use) is bound to the kernel.
>
> Lets say I want to just build a system on top of linux that boots and
> keeps printing hello world to the screen. When the user presses a key
> it exits.
>
> How would I begin to do this? What should I read or look at?
>
> I'm guessing it's a two part thing right, one I need to somehow tell
> the kernel what to do after booting, and second I'll have to tell the
> kernel what the screen is ? Where would I find more information about
> this?
>
> Note: I actually want to make the program I described so tips on how
> to play with grub to get the whole thing to work would also be
> helpful.
Look for init= kernel parameter (there is a kernel-parameter documentation file
in kernel doc drawer).
And I suggest looking through things like Linux From Scratch. I am not sure
how useful this is to your case.
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
prev parent reply other threads:[~2014-06-29 7:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-29 6:24 Gideon D'souza
2014-06-29 7:07 ` Martin Steigerwald [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=1989531.qh1zHAaciq@merkaba \
--to=martin@lichtvoll.de \
--cc=geert@linux-m68k.org \
--cc=gidisrael@gmail.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
all inboxes | Powered by JetHome®