All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: sparclinux@vger.kernel.org
Subject: Re: klibc and SPARC
Date: Wed, 17 May 2006 23:10:51 +0000	[thread overview]
Message-ID: <446BAD7B.4050908@zytor.com> (raw)
In-Reply-To: <e4g1ho$dae$1@terminus.zytor.com>

David S. Miller wrote:
> How I answer this depends upon why you're moving this out of the
> kernel in the first place :-)

The goal is mainly to get rid of a bunch of complex code that doesn't have to be in the 
kernel, like nfsroot.

> I can understand moving as much functionality as is reasonably
> possible into userspace via klibc, but for something like this which
> has weird dependencies if you move it into userspace and will
> undoubtedly force the enabling of what is normally an optional
> feature, I don't see moving it into userspace as being so wise.

OK, so that would make it an ad hoc thing.  That's not too horrible in itself; I just 
wondered if it would make sense to use an already existing feature.

However, there are a number of theoretically optional features in the kernel kernel which 
kinit does depend on, in particular sysfs and procfs -- without which it would be largely 
impossible.  It doesn't mean sysfs and procfs are mandatory, but it does mean that you 
have to provide your own initramfs if you don't want to include them.

Of course, unlike say openpromfs, very little userspace code will actually function 
without procfs, and increasingly sysfs, so it's not exactly a requirement imposed by kinit 
alone.

> That being said, openpromfs is the preferred thing to use if
> you have to make a choice.

Well, I'm happy to do it either which way.  I'll go ahead and write up an ad hoc solution 
for this case, unless it turns out to actually be bigger than one of the generic codes.

	-hpa

  parent reply	other threads:[~2006-05-17 23:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-17 20:37 klibc and SPARC H. Peter Anvin
2006-05-17 20:40 ` David S. Miller
2006-05-17 20:43 ` H. Peter Anvin
2006-05-17 20:57 ` H. Peter Anvin
2006-05-17 22:32 ` David S. Miller
2006-05-17 22:36 ` H. Peter Anvin
2006-05-17 22:41 ` David S. Miller
2006-05-17 23:10 ` H. Peter Anvin [this message]
2006-05-17 23:33 ` David S. Miller
2006-05-17 23:38 ` H. Peter Anvin
2006-05-18 19:17 ` H. Peter Anvin
2006-05-18 19:46 ` David S. Miller
2006-05-18 20:16 ` H. Peter Anvin

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=446BAD7B.4050908@zytor.com \
    --to=hpa@zytor.com \
    --cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.