From: Ole H. N. <Ole...@fy...> - 2012-06-14 13:46:15
|
Hi SystemImager guys, We would like to build SystemImager on RedHat 6.2 / CentOS 6.2. I got the latest SI rev. 4568 from SVN by: svn checkout https://systemimager.svn.sourceforge.net/svnroot/systemimager/trunk (the website http://www.systemimager.org/ is still sadly incomplete). However, additional tweaks seem to be required for CentOS 6.2, see http://sourceforge.net/mailarchive/forum.php?thread_name=01EDEEAE5DA8584CAAD628AA5B06179A048D471F%40EXDAG0-A3.intra.cea.fr&forum_name=sisuite-users My RPM build crashes because of a download reference to an obsolete e2fsprogs version. Questions: * Does anyone have complete and detailed SI build instructions for CentOS 6.2? * Can anyone with write access to SVN commit the changes required for 6.2? Thanks, Ole -- Ole Holm Nielsen Department of Physics, Technical University of Denmark |
From: LAHAYE O. <oli...@ce...> - 2012-06-14 15:30:43
|
I've built the rpm on CentOS-6.2. The resulting rpms seems ok. As I'm porting OSCAR on CentOS-6.2, I've been able to build client images so far, but I can't tell if the resulting image is fully functionnal as systemimage-oscar fail to generate the KERNEL0 line in /var/lib/systemimager/images/<imagename>/etc/systemconfig/systemconfig.conf (problem outside these rpms) To build the rpms, just look for the missing archive names in google and download the archive into /usr./src directory. Note that (sadly) you have to be root to build the rpms as the rpm needs mknode if I'm correct and I didn't find time to look at this issue and have the rpm buildable as non-root. Although, it would be cool if the source repository could be updated as it's a pain in the ass to google and fetch the correct sources archives and copy those in the /usr/src directory. Anybody able to do that? Regards, -- Olivier. ________________________________________ De : Ole Holm Nielsen [Ole...@fy...] Date d'envoi : jeudi 14 juin 2012 15:28 À : sis...@li... Objet : [sisuite-users] Building SystemImager on CentOS 6.2? Hi SystemImager guys, We would like to build SystemImager on RedHat 6.2 / CentOS 6.2. I got the latest SI rev. 4568 from SVN by: svn checkout https://systemimager.svn.sourceforge.net/svnroot/systemimager/trunk (the website http://www.systemimager.org/ is still sadly incomplete). However, additional tweaks seem to be required for CentOS 6.2, see http://sourceforge.net/mailarchive/forum.php?thread_name=01EDEEAE5DA8584CAAD628AA5B06179A048D471F%40EXDAG0-A3.intra.cea.fr&forum_name=sisuite-users My RPM build crashes because of a download reference to an obsolete e2fsprogs version. Questions: * Does anyone have complete and detailed SI build instructions for CentOS 6.2? * Can anyone with write access to SVN commit the changes required for 6.2? Thanks, Ole -- Ole Holm Nielsen Department of Physics, Technical University of Denmark ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ sisuite-users mailing list sis...@li... https://lists.sourceforge.net/lists/listinfo/sisuite-users |
From: Bernard Li <be...@va...> - 2012-06-14 18:34:43
|
If you guys could attach the patch here I can take a stab at checking it in. Olivier, would you be interested in getting commit access to the SVN repo? Thanks, Bernard On Thu, Jun 14, 2012 at 8:30 AM, LAHAYE Olivier <oli...@ce...> wrote: > > I've built the rpm on CentOS-6.2. The resulting rpms seems ok. As I'm porting OSCAR on CentOS-6.2, I've been able to build client images so far, but I can't tell if the resulting image is fully functionnal as systemimage-oscar fail to generate the KERNEL0 line in /var/lib/systemimager/images/<imagename>/etc/systemconfig/systemconfig.conf (problem outside these rpms) > > To build the rpms, just look for the missing archive names in google and download the archive into /usr./src directory. > Note that (sadly) you have to be root to build the rpms as the rpm needs mknode if I'm correct and I didn't find time to look at this issue and have the rpm buildable as non-root. > > Although, it would be cool if the source repository could be updated as it's a pain in the ass to google and fetch the correct sources archives and copy those in the /usr/src directory. > > Anybody able to do that? > > Regards, > > -- > Olivier. > ________________________________________ > De : Ole Holm Nielsen [Ole...@fy...] > Date d'envoi : jeudi 14 juin 2012 15:28 > À : sis...@li... > Objet : [sisuite-users] Building SystemImager on CentOS 6.2? > > Hi SystemImager guys, > > We would like to build SystemImager on RedHat 6.2 / CentOS 6.2. I got > the latest SI rev. 4568 from SVN by: > svn checkout > https://systemimager.svn.sourceforge.net/svnroot/systemimager/trunk > (the website http://www.systemimager.org/ is still sadly incomplete). > > However, additional tweaks seem to be required for CentOS 6.2, see > http://sourceforge.net/mailarchive/forum.php?thread_name=01EDEEAE5DA8584CAAD628AA5B06179A048D471F%40EXDAG0-A3.intra.cea.fr&forum_name=sisuite-users > My RPM build crashes because of a download reference to an obsolete > e2fsprogs version. > > Questions: > * Does anyone have complete and detailed SI build instructions for > CentOS 6.2? > * Can anyone with write access to SVN commit the changes required for 6.2? > > Thanks, > Ole > > -- > Ole Holm Nielsen > Department of Physics, Technical University of Denmark > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > sisuite-users mailing list > sis...@li... > https://lists.sourceforge.net/lists/listinfo/sisuite-users > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > sisuite-users mailing list > sis...@li... > https://lists.sourceforge.net/lists/listinfo/sisuite-users |
From: Brian F. <br...@th...> - 2012-06-15 14:21:09
|
We want to eliminate the need for mknod, definitely. I would still consider SVN trunk to be in a testing state. Most of the intelligence is the same, but the way the autoinstall client binaries and kernel are built is a bit different. Please let me know how it goes. -Brian On 06/14/2012 09:30 AM, LAHAYE Olivier wrote: > > I've built the rpm on CentOS-6.2. The resulting rpms seems ok. As I'm porting OSCAR on CentOS-6.2, I've been able to build client images so far, but I can't tell if the resulting image is fully functionnal as systemimage-oscar fail to generate the KERNEL0 line in /var/lib/systemimager/images/<imagename>/etc/systemconfig/systemconfig.conf (problem outside these rpms) > > To build the rpms, just look for the missing archive names in google and download the archive into /usr./src directory. > Note that (sadly) you have to be root to build the rpms as the rpm needs mknode if I'm correct and I didn't find time to look at this issue and have the rpm buildable as non-root. > > Although, it would be cool if the source repository could be updated as it's a pain in the ass to google and fetch the correct sources archives and copy those in the /usr/src directory. > > Anybody able to do that? > > Regards, > -- Brian Elliott Finley Mobile: 469.444.0167 |
From: Ole H. N. <Ole...@fy...> - 2012-06-15 13:06:06
|
LAHAYE Olivier <oli...@ce...> wrote: > I've built the rpm on CentOS-6.2. The resulting rpms seems ok. As I'm porting OSCAR on CentOS-6.2, I've been able to build client images so far, but I can't tell if the resulting image is fully functionnal as systemimage-oscar fail to generate the KERNEL0 line in /var/lib/systemimager/images/<imagename>/etc/systemconfig/systemconfig.conf (problem outside these rpms) > > To build the rpms, just look for the missing archive names in google and download the archive into /usr./src directory. > Note that (sadly) you have to be root to build the rpms as the rpm needs mknode if I'm correct and I didn't find time to look at this issue and have the rpm buildable as non-root. > > Although, it would be cool if the source repository could be updated as it's a pain in the ass to google and fetch the correct sources archives and copy those in the /usr/src directory. I've made a bit of progress towards building the SI RPMs on an RHEL6.2 server, but I didn't make it to the goal yet: 1. I copied the downloaded sources from /root/rpmbuild/BUILD/systemimager-4.3.0/initrd_source/src/ to the permanent place /usr/src/. Strangely, today the correct e2fsprogs can be downloaded successfully (it was absent yesterday). 2. The next missing download is a kernel source file http://download.systemimager.org/pub/linux/linux_2.6.34.1.orig.tar.gz. So I grabbed a similar file from http://www.kernel.org/pub/linux/kernel/v2.6/ and renamed it with the .orig (probably a no-no!). The kernel.org version seems to build, but I had to answer a bunch of configure questions. 3. Next failure occurs when building parted-2.3: ... checking for dm_task_create in -ldevmapper... no configure: error: libdevmapper could not be found, but is required for the --enable-device-mapper option, which is enabled by default. Either disable device-mapper support with --disable-device-mapper or download and install device-mapper from: http://sources.redhat.com/dm/ FYI, our RHEL6.2 server does have the device-mapper 32- and 64-bit RPMs installed with /lib/libdevmapper.so.1.02. Question: Am I on the right track, or is there a better way to build the SI RPMs? Thanks a lot, Ole -- Ole Holm Nielsen Department of Physics, Technical University of Denmark |
From: LAHAYE O. <oli...@ce...> - 2012-06-15 13:23:53
|
Go there and fetch those sources. It should build without asking any questions (it does for me). Hopefully I didn't forgot any Requires: in the spec file. http://olivier.lahaye1.free.fr/SOURCES/ Olivier. ________________________________________ De : Ole Holm Nielsen [Ole...@fy...] Date d'envoi : vendredi 15 juin 2012 15:05 À : sis...@li... Objet : Re: [sisuite-users] Building SystemImager on CentOS 6.2? LAHAYE Olivier <oli...@ce...> wrote: > I've built the rpm on CentOS-6.2. The resulting rpms seems ok. As I'm porting OSCAR on CentOS-6.2, I've been able to build client images so far, but I can't tell if the resulting image is fully functionnal as systemimage-oscar fail to generate the KERNEL0 line in /var/lib/systemimager/images/<imagename>/etc/systemconfig/systemconfig.conf (problem outside these rpms) > > To build the rpms, just look for the missing archive names in google and download the archive into /usr./src directory. > Note that (sadly) you have to be root to build the rpms as the rpm needs mknode if I'm correct and I didn't find time to look at this issue and have the rpm buildable as non-root. > > Although, it would be cool if the source repository could be updated as it's a pain in the ass to google and fetch the correct sources archives and copy those in the /usr/src directory. I've made a bit of progress towards building the SI RPMs on an RHEL6.2 server, but I didn't make it to the goal yet: 1. I copied the downloaded sources from /root/rpmbuild/BUILD/systemimager-4.3.0/initrd_source/src/ to the permanent place /usr/src/. Strangely, today the correct e2fsprogs can be downloaded successfully (it was absent yesterday). 2. The next missing download is a kernel source file http://download.systemimager.org/pub/linux/linux_2.6.34.1.orig.tar.gz. So I grabbed a similar file from http://www.kernel.org/pub/linux/kernel/v2.6/ and renamed it with the .orig (probably a no-no!). The kernel.org version seems to build, but I had to answer a bunch of configure questions. 3. Next failure occurs when building parted-2.3: ... checking for dm_task_create in -ldevmapper... no configure: error: libdevmapper could not be found, but is required for the --enable-device-mapper option, which is enabled by default. Either disable device-mapper support with --disable-device-mapper or download and install device-mapper from: http://sources.redhat.com/dm/ FYI, our RHEL6.2 server does have the device-mapper 32- and 64-bit RPMs installed with /lib/libdevmapper.so.1.02. Question: Am I on the right track, or is there a better way to build the SI RPMs? Thanks a lot, Ole -- Ole Holm Nielsen Department of Physics, Technical University of Denmark ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ sisuite-users mailing list sis...@li... https://lists.sourceforge.net/lists/listinfo/sisuite-users |
From: Ole H. N. <Ole...@fy...> - 2012-06-15 20:25:45
|
LAHAYE Olivier <oli...@ce...> wrote: > Go there and fetch those sources. It should build without asking any questions (it does for me). > Hopefully I didn't forgot any Requires: in the spec file. > http://olivier.lahaye1.free.fr/SOURCES/ Thanks a lot! I grabbed the missing linux_2.6.34.1.orig.tar.gz file now. Unfortunately the build process still asks unwarranted questions. This is what I did: 1. I have checked out SVN trunk revision 4568 from https://systemimager.svn.sourceforge.net/svnroot/systemimager/trunk 2. In the trunk/ directory I do: make source_tarball 3. Then I build it: cd tmp; rpmbuild -ta systemimager-4.3.0.tar.bz2 However, during the build process the kernel wants to be reconfigured: > + make all > rm -rf /root/rpmbuild/BUILD/systemimager-4.3.0/src/linux-2.6.34.1 > Extracting kernel source...done > cp -a /root/rpmbuild/BUILD/systemimager-4.3.0/patches/linux.x86_64.config /root/rpmbuild/BUILD/systemimager-4.3.0/src/linux-2.6.34.1/.config > perl -pi -e "s/^EXTRAVERSION =\s*(\S*)\s*\n/EXTRAVERSION = \1-boel_v4.3.0\n/" /root/rpmbuild/BUILD/systemimager-4.3.0/src/linux-2.6.34.1/Makefile > make -C /root/rpmbuild/BUILD/systemimager-4.3.0/src/linux-2.6.34.1 oldconfig > make[1]: Entering directory `/root/rpmbuild/BUILD/systemimager-4.3.0/src/linux-2.6.34.1' > HOSTCC scripts/basic/fixdep > HOSTCC scripts/basic/docproc > HOSTCC scripts/basic/hash > HOSTCC scripts/kconfig/conf.o > HOSTCC scripts/kconfig/kxgettext.o > SHIPPED scripts/kconfig/zconf.tab.c > SHIPPED scripts/kconfig/lex.zconf.c > SHIPPED scripts/kconfig/zconf.hash.c > HOSTCC scripts/kconfig/zconf.tab.o > HOSTLD scripts/kconfig/conf > scripts/kconfig/conf -o arch/x86/Kconfig > * > * Restart config... > * > * > * General setup > * > Prompt for development and/or incomplete code/drivers (EXPERIMENTAL) [Y/n/?] y > Local version - append to kernel release (LOCALVERSION) [] > Automatically append version information to the version string (LOCALVERSION_AUTO) [Y/n/?] y > Kernel compression mode >> 1. Gzip (KERNEL_GZIP) > 2. Bzip2 (KERNEL_BZIP2) > 3. LZMA (KERNEL_LZMA) > 4. LZO (KERNEL_LZO) (NEW) > choice[1-4?]: So something must be wrong. I don't why I have to reconfigure the kernel whereas Olivier doesn't. FYI, my build host is RHEL6.2 (fully updated). Thanks for any help, Ole |
From: LAHAYE O. <oli...@ce...> - 2012-06-18 07:56:28
|
This is wired, as I'me sure I've faced the not updated kernel config issue (especially the compression method) and using my srpm on my centos-6.2, Id' doesn't ask for this. I've re-uploaded my src.rpm. please check with this rpm and all the sources. CentOS-6.2 and RHEL-6.2 should be very similar and shoud build the same way. (more over, this issue is related to the rpm, not the system. question is asked about things related to the rpm...) http://olivier.lahaye1.free.fr/SOURCES/ grab the external sources here an copy this in /usr/src Make sure you're using those sources when building and not something else downloaded elsewhere that could supersede some of those tarballs. http://olivier.lahaye1.free.fr/SRPMS/systemimager-4.2.0-0.6svn4568.el6.src.rpm Install this and build it as root (I know it is bad, but I hadn't time to fix the mknod issue). Cheers, Olivier. ________________________________________ De : Ole Holm Nielsen [Ole...@fy...] Date d'envoi : vendredi 15 juin 2012 22:25 À : sis...@li... Objet : Re: [sisuite-users] Building SystemImager on CentOS 6.2? LAHAYE Olivier <oli...@ce...> wrote: > Go there and fetch those sources. It should build without asking any questions (it does for me). > Hopefully I didn't forgot any Requires: in the spec file. > http://olivier.lahaye1.free.fr/SOURCES/ Thanks a lot! I grabbed the missing linux_2.6.34.1.orig.tar.gz file now. Unfortunately the build process still asks unwarranted questions. This is what I did: 1. I have checked out SVN trunk revision 4568 from https://systemimager.svn.sourceforge.net/svnroot/systemimager/trunk 2. In the trunk/ directory I do: make source_tarball 3. Then I build it: cd tmp; rpmbuild -ta systemimager-4.3.0.tar.bz2 However, during the build process the kernel wants to be reconfigured: > + make all > rm -rf /root/rpmbuild/BUILD/systemimager-4.3.0/src/linux-2.6.34.1 > Extracting kernel source...done > cp -a /root/rpmbuild/BUILD/systemimager-4.3.0/patches/linux.x86_64.config /root/rpmbuild/BUILD/systemimager-4.3.0/src/linux-2.6.34.1/.config > perl -pi -e "s/^EXTRAVERSION =\s*(\S*)\s*\n/EXTRAVERSION = \1-boel_v4.3.0\n/" /root/rpmbuild/BUILD/systemimager-4.3.0/src/linux-2.6.34.1/Makefile > make -C /root/rpmbuild/BUILD/systemimager-4.3.0/src/linux-2.6.34.1 oldconfig > make[1]: Entering directory `/root/rpmbuild/BUILD/systemimager-4.3.0/src/linux-2.6.34.1' > HOSTCC scripts/basic/fixdep > HOSTCC scripts/basic/docproc > HOSTCC scripts/basic/hash > HOSTCC scripts/kconfig/conf.o > HOSTCC scripts/kconfig/kxgettext.o > SHIPPED scripts/kconfig/zconf.tab.c > SHIPPED scripts/kconfig/lex.zconf.c > SHIPPED scripts/kconfig/zconf.hash.c > HOSTCC scripts/kconfig/zconf.tab.o > HOSTLD scripts/kconfig/conf > scripts/kconfig/conf -o arch/x86/Kconfig > * > * Restart config... > * > * > * General setup > * > Prompt for development and/or incomplete code/drivers (EXPERIMENTAL) [Y/n/?] y > Local version - append to kernel release (LOCALVERSION) [] > Automatically append version information to the version string (LOCALVERSION_AUTO) [Y/n/?] y > Kernel compression mode >> 1. Gzip (KERNEL_GZIP) > 2. Bzip2 (KERNEL_BZIP2) > 3. LZMA (KERNEL_LZMA) > 4. LZO (KERNEL_LZO) (NEW) > choice[1-4?]: So something must be wrong. I don't why I have to reconfigure the kernel whereas Olivier doesn't. FYI, my build host is RHEL6.2 (fully updated). Thanks for any help, Ole ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ sisuite-users mailing list sis...@li... https://lists.sourceforge.net/lists/listinfo/sisuite-users |
From: Ole H. N. <Ole...@fy...> - 2012-06-18 10:07:07
|
More problems in building SystemImager on CentOS 6.2: Besides the kernel reconfiguration issue (which may be innocent, perhaps?), the building of parted 2.3 aborts on RHEL 6.2 during the configuration stage: In /root/rpmbuild/BUILD/systemimager-4.3.0/initrd_source/src/parted-2.3 the config.log shows: # ./configure --disable-Werror --disable-shared --prefix= ... checking for dm_task_create in -ldevmapper... no configure: error: libdevmapper could not be found, but is required for the --enable-device-mapper option, which is enabled by default. Either disable device-mapper support with --disable-device-mapper or download and install device-mapper from: http://sources.redhat.com/dm/ Note: if you are using precompiled packages you will need the development package as well (it may be called device-mapper-devel or something similar). The /lib/libdevmapper.so.1.02 shared library does exist. But RHEL6 does NOT have any package named device-mapper-devel or the like. The check dm_task_create in -ldevmapper can be extracted from the configure script: #ifdef __cplusplus extern "C" #endif char dm_task_create (); int main () { return dm_task_create (); ; return 0; } Compiling this on RHEL6 gives: # gcc test.c -ldevmapper /usr/bin/ld: cannot find -ldevmapper collect2: ld returned 1 exit status I'm really confused: Why does this code break, while other people seem to have built SystemImager (including parted) successfully on RHEL6/CentOS6 ? Thanks for sharing any insights, Ole |
From: Ole H. N. <Ole...@fy...> - 2012-06-21 12:50:05
|
Unfortunately no one has yet offered any advice for building SystemImager (trunk version) on CentOS 6.2. Out of desperation I tried to build the trunk version on the RHEL 5.8 server where we have used SystemImager 4.1.7 successfully for years. Again, the SI trunk version fails to build on RHEL 5.8 :-( The kernel configuration again asks a number of configuration questions, but I just choose the default values to proceed. Finally, the build process crashed at this stage: cd /usr/src/redhat/BUILD/systemimager-4.3.0/initrd_source/src && tar -xvJf gzip-1.4.tar.xz tar: invalid option -- J Try `tar --help' or `tar --usage' for more information. make: *** [/usr/src/redhat/BUILD/systemimager-4.3.0/initrd_source/src/gzip-1.4.unpack] Error 64 error: Bad exit status from /var/tmp/rpm-tmp.6420 (%build) The problem is the file gzip-1.4.tar.xz which can't be unpacked on RHEL5/CentOS5 because the tar command on such systems don't know the .xz type of compression (tar -J command). Could someone knowledgeable about the SI trunk kindly replace the gzip-1.4.tar.xz package by the similar gzip-1.4.tar.gz package and change the -J flag into -z ? Thanks a lot, Ole |