Skip to contentSkip to conversation

initramfs: who does cat init.sh >> init ?

DISCUSSION Nickolay 2 participants 7 messages Jun 9, 2006 1 message not in the archive

lore
Share & tools
lore

Nickolay

author
#0 lore raw

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.

Thanks.

Signature · 1 line
Nickolay Vinogradov
#1 lore raw
Followup to:  <[email protected]>
By author:    Nickolay <[email protected]>
In newsgroup: linux.dev.kernel
Quoted 9 lines

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

author
#2 lore raw
Quoted 20 lines · H. Peter Anvin
Followup to:  <[email protected]>
By author:    Nickolay <[email protected]>
In newsgroup: linux.dev.kernel
Quoted 9 lines

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.

Quoted 8 lines

-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
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.

Signature · 1 line
Nickolay Vinogradov
#3 lore raw
Quoted 6 lines · Nickolay
Quoted 1 line

I'm afraid, that you wrong.
It is 2.6.17-rc4 git tree.

BE/2_6/initramfs is just CONFIG_INITRAMFS_SOURCE path.

: neotrantor 11 ; fgrep -nr init.sh *
Documentation/filesystems/ramfs-rootfs-initramfs.txt:144: file /init initramfs/init.sh 755 0 0 Documentation/filesystems/ramfs-rootfs-initramfs.txt:151:two example "file" entries expect to find files named "init.sh" and "busybox" in

The only references to init.sh in the stock kernel tree are in a documentation file.

-hpa

author
#4 lore raw
Quoted 9 lines · H. Peter Anvin
Quoted 6 lines · Nickolay
Quoted 1 line

I'm afraid, that you wrong.
It is 2.6.17-rc4 git tree.

BE/2_6/initramfs is just CONFIG_INITRAMFS_SOURCE path.

Quoted 7 lines

: neotrantor 11 ; fgrep -nr init.sh *
Documentation/filesystems/ramfs-rootfs-initramfs.txt:144: file /init initramfs/init.sh 755 0 0 Documentation/filesystems/ramfs-rootfs-initramfs.txt:151:two example "file" entries expect to find files named "init.sh" and "busybox" in

The only references to init.sh in the stock kernel tree are in a documentation file.

-hpa

yes, i can't grep init.sh in the kernel tree too, this is because i start asking... But anyway, the problem is still...

Signature · 1 line
Nickolay Vinogradov
#5 lore raw
Quoted 4 lines · Nickolay

yes, i can't grep init.sh in the kernel tree too, this is because i start asking... But anyway, the problem is still...

Perhaps you should show more context... what comes around this mysterious invocation in your make V=1 log. Also your .config would help.

-hpa

A message that is not in the archive (sent off-list or not yet received): [email protected]

#7 lore raw
Quoted 13 lines · Nickolay
Quoted 10 lines · H. Peter Anvin
Quoted 4 lines · Nickolay

yes, i can't grep init.sh in the kernel tree too, this is because i start asking... But anyway, the problem is still...

Perhaps you should show more context... what comes around this mysterious invocation in your make V=1 log. Also your .config would help.

-hpa

Quoted 7 lines

OK. Here it is:

---------------------------------------------------------------------------------------------------

bash-3.00# make zImage V=1
rm -f .kernelrelease
echo 2.6.17-rc4-g3bcc86f5-dirty > .kernelrelease

       ^^^^^^^^^^^^^^^^^^^^^^^^^^

Modified kernel source.

-hpa