From: Tom Duffy <Thomas.Duffy.99@alumni.brown.edu>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: sam@ravnborg.org.sun.com
Subject: 2.6.9-bk6 initramfs build failure with separate object dir
Date: Thu, 21 Oct 2004 11:43:42 -0700 [thread overview]
Message-ID: <1098384222.2389.22.camel@duffman> (raw)
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
[tduffy@duffman linux-2.6.9-bk-openib]$ make O=/build1/tduffy/openib-work/build/bk/3.4/x86_64/
Using /build1/tduffy/openib-work/linux-2.6.9-bk-openib as source for kernel
CHK include/linux/version.h
make[2]: `arch/x86_64/kernel/asm-offsets.s' is up to date.
CHK include/asm-x86_64/offset.h
CHK include/linux/compile.h
GEN_INITRAMFS_LIST usr/initramfs_list
Using shipped usr/initramfs_list
CPIO usr/initramfs_data.cpio
ERROR: unable to open 'usr/initramfs_list': No such file or directory
Usage:
./usr/gen_init_cpio <cpio_list>
<cpio_list> is a file containing newline separated entries that
describe the files to be included in the initramfs archive:
# a comment
file <name> <location> <mode> <uid> <gid>
dir <name> <mode> <uid> <gid>
nod <name> <mode> <uid> <gid> <dev_type> <maj> <min>
<name> name of the file/dir/nod in the archive
<location> location of the file in the current filesystem
<mode> mode/permissions of the file
<uid> user id (0=root)
<gid> group id (0=root)
<dev_type> device type (b=block, c=character)
<maj> major number of nod
<min> minor number of nod
example:
# A simple initramfs
dir /dev 0755 0 0
nod /dev/console 0600 0 0 c 5 1
dir /root 0700 0 0
dir /sbin 0755 0 0
file /sbin/kinit /usr/src/klibc/kinit/kinit 0755 0 0
make[2]: *** [usr/initramfs_data.cpio] Error 1
make[1]: *** [usr] Error 2
make: *** [_all] Error 2
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-10-21 18:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 18:43 Tom Duffy [this message]
2004-10-22 21:09 ` [PATCH] Re: 2.6.9-bk6 initramfs build failure with separate object dir Doug Maxey
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=1098384222.2389.22.camel@duffman \
--to=thomas.duffy.99@alumni.brown.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org.sun.com \
/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