public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nickolay <nickolay@protei.ru>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: initramfs: who does cat init.sh >> init ?
Date: Sat, 10 Jun 2006 00:33:25 +0400	[thread overview]
Message-ID: <4489DB15.9010506@protei.ru> (raw)
In-Reply-To: <e6cllv$dnb$1@terminus.zytor.com>

H. Peter Anvin wrote:

>Followup to:  <4489D93F.7090401@protei.ru>
>By author:    Nickolay <nickolay@protei.ru>
>In newsgroup: linux.dev.kernel
>  
>
>>Guys, in recent kernels, when building kernel with initramfs with V=1, 
>>i  see interesting one:
>>
>>cat /usr/kernel/BE/2_6/initramfs/init.sh >/usr/kernel/BE/2_6/initramfs/init
>>
>>But i can't find, who really do that. Can anyone point me?
>>I need to fix that, because it's impossible for me to have two copy of init.
>>
>>    
>>
>
>Nothing that's part of the standard kernel, that's for sure.
>
>Looks like you have something patched, possibly by a vendor.  The
>BE/2_6 bit definitely looks that way.
>
>	-hpa
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>  
>
I'm afraid, that you wrong.
It is 2.6.17-rc4 git tree.

BE/2_6/initramfs is just CONFIG_INITRAMFS_SOURCE path.

-- 
Nickolay Vinogradov


  reply	other threads:[~2006-06-09 20:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-09 20:25 initramfs: who does cat init.sh >> init ? Nickolay
2006-06-09 20:28 ` H. Peter Anvin
2006-06-09 20:33   ` Nickolay [this message]
2006-06-09 20:38     ` H. Peter Anvin
2006-06-09 20:48       ` Nickolay
2006-06-09 20:50         ` H. Peter Anvin
     [not found]           ` <4489E030.2090602@protei.ru>
2006-06-09 20:58             ` 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=4489DB15.9010506@protei.ru \
    --to=nickolay@protei.ru \
    --cc=hpa@zytor.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