Are you explicitly calling si_mkbootpackage? If so,
perhaps you can try si_prepareclient - that can also generate boot packages and
is known to work better.
Cheers,
Bernard
Hi Bernard,
Did you receive this? Just curious if you know what the
problem is?
-John
| John
DeBella/Bos/Teradyne
05/22/2006 10:49 AM
|
|
Hi Bernard,
Here is the info you requested:
systemimager-common-3.2.3-1
systemimager-common-3.6.3-1
systemimager-i386initrd_template-3.6.3-1
systemimager-client-3.6.3-1
systemimager-flamethrower-3.6.3-1
systemimager-ia64initrd_template-3.6.3-1
systemimager-i386boot-standard-3.6.3-1
systemimager-x86_64boot-standard-3.6.3-1
systemimager-x86_64initrd_template-3.6.3-1
systemimager-client-3.2.3-1
systemimager-server-3.6.3-1
systemimager-ia64boot-standard-3.6.3-1
[EMAIL PROTECTED]:[EMAIL PROTECTED] root]# si_mkbootpackage
--kernel /etc/systemimager/boot/kernel --new-flavor DELL2850 --from-flavor
standard --modules-dir /lib/modules/`uname -r` --verbose
WARNING:
si_mkbootpackage is currently considered an experimental tool.
"Your Mileage May Vary"
Use of uninitialized value in
pattern match (m//) at /usr/sbin/si_mkbootpackage line 108.
Use of
uninitialized value in pattern match (m//) at /usr/sbin/si_mkbootpackage line
108.
Use of uninitialized value in concatenation (.) or string at
/usr/sbin/si_mkbootpackage line 114.
>>> Kernel release:
>>> Using modules from:
/lib/modules/2.4.21-32.0.1.ELsmp
>>> Module
extension: .
>>> Using
architecture: i386
>>> Base temporary
dir: /tmp/si30954
>>> gunzip
/tmp/si30954/old_initrd.gz
>>> Old initrd mount point:
/tmp/si30954/old_initrd_dir
>>> mount
/tmp/si30954/old_initrd /tmp/si30954/old_initrd_dir -o loop
>>>
New initrd temporary dir: /tmp/si30954/staging_dir
>>>
rsync -aHS --exclude=lost+found/ --numeric-ids /tmp/si30954/old_initrd_dir/
/tmp/si30954/staging_dir/
>>> umount
/tmp/si30954/old_initrd_dir
>> Updating
/tmp/si30954/staging_dir/etc/init.d/functions with Flavor =
DELL2850
>> Flavor Update complete
FLAVOR="DELL2850"
CMD="wget
${SSH_DOWNLOAD_URL}/${ARCH}/${FLAVOR}/boel_binaries.tar.gz"
MODULE_NAME="boot-${ARCH}-${FLAVOR}"
CMD="rsync -av
${IMAGESERVER}::boot/${ARCH}/${FLAVOR}/boel_binaries.tar.gz
${BOEL_BINARIES_DIR}"
>>> Removing old modules from:
/tmp/si30954/staging_dir/my_modules
Couldn't open
/tmp/si30954/staging_dir/my_modules /INSMOD_COMMANDS for reading. at
/usr/sbin/si_mkbootpackage line 408.
"Bernard Li"
<[EMAIL PROTECTED]> Sent
by: [EMAIL PROTECTED]
05/16/2006 11:32 AM
|
|
If
you're using the RPMs, did you have the
systemimager-<arch>initrd_template package
installed?
Cheers,
Bernard
-----Original
Message-----
From: [EMAIL PROTECTED] on behalf of
[EMAIL PROTECTED]
Sent: Tue 16/05/2006 06:41
To:
[email protected]
Subject: [Sisuite-users]
si_mkbootpackage error
Hi,
I'm trying to run the
si_mkbootpackage script in 3.6.3 and am getting the
following
error:
Couldn't open /tmp/si1065/staging_dir/my_modules
/INSMOD_COMMANDS for
reading. at /usr/sbin/si_mkbootpackage line
408.
Has anyone else run into this
problem?
-John
_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users