Menu
▾
▴
sisuite-users
|
From: LAHAYE O. <oli...@ce...> - 2012-07-25 12:50:53
|
Hi,
After trying to use my RPM on a CentOS-6.2 system, I'm facing some issues that are hard to fix, thus I'm asking before starting to try to make a update so it works on CentOS-6.2
1st of all, I've already made some fix to systemimager so it works on CentOS-6.2, unfortunately, I'm stuck with systemconfigurator which is not supported on CentOS-6.2 (kernel-2.6) and therfore disable with no equivalent in systemimager. Because of this, the bootloader is not written to disk after the imaging, and therfore, the imaged system is unable to boot.
So the actual situation is the following:
- systemimager-4.1.99.svn4568/lib/SystemImager/Server.pm:1788 SystemConfigurator deprecated and nothing to do its job (configure and write bootloader, ...)
- systemconfigurator-2.2.11-1/lib/SystemConfig/{Initrd/RH.pm, Boot*, ???} need to be fixed to have kernel 2.6+ properly handeled (initramfs instead of initrd, dracut instead of initrd (compatible script exist for the moment), ...
So now, I need help on having the ##SYSTEMCONFIGURATOR_PRE## and #SYSTEMCONFIGURATOR_POST## steps working in SystemImager. Works need to be done on the autoinstallscript and in systemconfigurator (or equivalent).
For now here are my patches for the latest systeminstaller to be able to deploy an image:
- systemimager_initrd_coreutils_rul.patch
Small Makefile fix (more clean)
- systemimager_initrd_mklib_bef.patch
Avoid overwriting libs that are alreadin installed in build_dir/ This prevent libmount-2.10 from CentOS-6.2 to overwrite libmount 2.12 from util-linux, and thus have mount, blkid and such to run instead of failing with wrong lib version.
- systemimager_initrd_rul.patch
Fix destination lib path.
- systemimager_initrd_udev_rul.patch
Disable systemd, libdir=/lib and use $MAKE
- systemimager_initrd_util_linux_rul.patch
Use $MAKE install instead of manualy copy binaries. If make install is not used, the libtool wrapper is copied instead of the real lib.
- systemimager_server_pm.patch
Fix that may be temporary. Right now, if the 1st partition inside the extended partition start at the same block, parted returns an error code. This fix avoid this by adding one block to the partition created inside the extended partition. Far from being a good fix, it makes at least things work. (fix commented in the patch)
- systemimager_sysvinit_initrd_rul.patch
Added a test to avoid failing when trying to copy /lib/ld* and no files are found.
- systemimager_util_linux_rul.patch
Enhanced configure step.
Thanks a lot for your help.
PS: Cross posted on oscar-devel mailing list
________________________________________
De : LAHAYE Olivier
Date d'envoi : lundi 18 juin 2012 09:56
À : sis...@li...
Objet : [sisuite-users] RE : Building SystemImager on CentOS 6.2?
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
------------------------------------------------------------------------------
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-07-26 12:42:33
|
LAHAYE Olivier <oli...@ce...> wrote:
> After trying to use my RPM on a CentOS-6.2 system, I'm facing some issues that are hard to fix, thus I'm asking before starting to try to make a update so it works on CentOS-6.2
>
> 1st of all, I've already made some fix to systemimager so it works on CentOS-6.2, unfortunately, I'm stuck with systemconfigurator which is not supported on CentOS-6.2 (kernel-2.6) and therfore disable with no equivalent in systemimager. Because of this, the bootloader is not written to disk after the imaging, and therfore, the imaged system is unable to boot.
>
> So the actual situation is the following:
> - systemimager-4.1.99.svn4568/lib/SystemImager/Server.pm:1788 SystemConfigurator deprecated and nothing to do its job (configure and write bootloader, ...)
>
> - systemconfigurator-2.2.11-1/lib/SystemConfig/{Initrd/RH.pm, Boot*, ???} need to be fixed to have kernel 2.6+ properly handeled (initramfs instead of initrd, dracut instead of initrd (compatible script exist for the moment), ...
>
> So now, I need help on having the ##SYSTEMCONFIGURATOR_PRE## and #SYSTEMCONFIGURATOR_POST## steps working in SystemImager. Works need to be done on the autoinstallscript and in systemconfigurator (or equivalent).
I share your frustrations about systemconfigurator (and thus also
SystemImager) not supporting CentOS 6.x! My experiences so far agree
with yours: It's possible to tweak SystemImager to install a CentOS 6.x
image onto a SI client's hard disk, but that image is unfortunately not
bootable :-(
Unfortunately I'm unable to help you with systemconfigurator. But I can
add some observations regarding the use of SystemImager with CentOS 6.x
(we're at 6.3 now) which reflect my experimentation to date:
1. SystemImager trunk as well as older versions CANNOT build on a CentOS
6.x system because several software packages (kernel, parted) are
incompatible. The SI trunk won't even build on CentOS 5.x owing to the
gzip package :-(
2. SystemImager packages built on a CentOS 5.x system CAN be installed
correctly on CentOS 6.x SI server and golden client systems! Older
versions of SI from CentOS 5.x seem to be working just fine on CentOS
6.x, and you can use si_getimage successfully.
3. A SI CentOS 6.x SI client machine can be installed correctly from the
6.x SI server in the usual way. However, at the end of the cloning
process systemconfigurator gives some error messages, and the SI client
is unable to boot :-(
4. If the SI clients have new hardware (Intel Sandy Bridge, for
example), the SI kernel may be too old to work properly.
Related to SI, the SALI project (https://subtrac.sara.nl/oss/sali) at
SARA, Amsterdam offers a much newer kernel and initrd supporting modern
filesystems and new hardware(?).
You can replace the SI kernel/initrd with the SALI kernel/initrd when
booting SI clients, and even run your old SI .master installation
scripts! Some minor tweaks to the .master script must be performed as
documented in
https://subtrac.sara.nl/oss/sali/wiki/SaliUsage/UsingYourOldInstallScript.
It really works! Of course, the installed CentOS 6.x client still
won't boot due to systemconfigurator :-(
SALI has their own master scripts which are a lot simpler than the SI
scripts, but I think SALI hasn't been ported to CentOS 6.x yet because
1) SALI still relies upon systemconfigurator, and 2) SALI doesn't seem
to support LVM.
In conclusion, it seems to me that if you can make systemconfigurator
work correctly on CentOS 6.x, then SI and/or SALI should work as well
for installing clients that will be bootable.
A totally different cloning approach would be to use RedHat's Kickstart
- some of my colleagues have turned from SI to Kickstart already. If
you add Cobbler (http://cobbler.github.com/) on top of Kickstart you may
have quite a powerful cloning setup.
Regards,
Ole
--
Ole Holm Nielsen
Department of Physics, Technical University of Denmark
|
|
From: Bas v. d. V. <ba...@sa...> - 2012-07-26 13:57:24
Attachments:
smime.p7s
|
> You can replace the SI kernel/initrd with the SALI kernel/initrd when > booting SI clients, and even run your old SI .master installation > scripts! Some minor tweaks to the .master script must be performed as > documented in > https://subtrac.sara.nl/oss/sali/wiki/SaliUsage/UsingYourOldInstallScript. > It really works! Of course, the installed CentOS 6.x client still > won't boot due to systemconfigurator :-( > > SALI has their own master scripts which are a lot simpler than the SI > scripts, but I think SALI hasn't been ported to CentOS 6.x yet because > 1) SALI still relies upon systemconfigurator, and 2) SALI doesn't seem > to support LVM. > Just some comments on SALI. We use the SALI kernel/initrd on Debian, Centos and SUSE Linux PowerPC. The development is mostly donein a Debian enviroment, Only when you want to make you own kernel/initrd you have to compile it from scratch. We do not use the systemimager-server tools anymore. They are replaced by the SALI server tools. they are noy documented yet :-( As for the systemconfigurator tools we have replaced them partially by functions in the `initrd` and postinst scripts. So we get rid of the systemconfigurator tools. We have some ideas howto replace them with other tools. As for LVM the SALI kernel/initrd support it. For now there are now functions for it to hide the complexity. So you must do the basic LVM commands in the master script. > In conclusion, it seems to me that if you can make systemconfigurator > work correctly on CentOS 6.x, then SI and/or SALI should work as well > for installing clients that will be bootable. > We have implemented a `grub2_install` functions or create a postinst script that will do it for you -- ******************************************************************** * Bas van der Vlies e-mail: ba...@sa... * * SARA - Academic Computing Services Amsterdam, The Netherlands * ******************************************************************** |
|
From: LAHAYE O. <oli...@ce...> - 2012-07-26 15:15:34
|
Thanks for the info, unfortunately, my problem was related to systemconfigurator (systemimager is now working fine with CentOS-6.2 and default kernel) I'll soon release an updated src.rpm of systemimager As you said, I used post install scripts to replace systemconfigurator and so far it works well. I just thaught that some one had fixed systemconfigurator or at least found a replacement so I could update systemimager master script. thanks for the input anyway. Olivier. ________________________________________ De : Bas van der Vlies [ba...@sa...] Date d'envoi : jeudi 26 juillet 2012 15:44 À : sis...@li... Objet : Re: [sisuite-users] RE : RE : Building SystemImager on CentOS 6.2? HELP > You can replace the SI kernel/initrd with the SALI kernel/initrd when > booting SI clients, and even run your old SI .master installation > scripts! Some minor tweaks to the .master script must be performed as > documented in > https://subtrac.sara.nl/oss/sali/wiki/SaliUsage/UsingYourOldInstallScript. > It really works! Of course, the installed CentOS 6.x client still > won't boot due to systemconfigurator :-( > > SALI has their own master scripts which are a lot simpler than the SI > scripts, but I think SALI hasn't been ported to CentOS 6.x yet because > 1) SALI still relies upon systemconfigurator, and 2) SALI doesn't seem > to support LVM. > Just some comments on SALI. We use the SALI kernel/initrd on Debian, Centos and SUSE Linux PowerPC. The development is mostly donein a Debian enviroment, Only when you want to make you own kernel/initrd you have to compile it from scratch. We do not use the systemimager-server tools anymore. They are replaced by the SALI server tools. they are noy documented yet :-( As for the systemconfigurator tools we have replaced them partially by functions in the `initrd` and postinst scripts. So we get rid of the systemconfigurator tools. We have some ideas howto replace them with other tools. As for LVM the SALI kernel/initrd support it. For now there are now functions for it to hide the complexity. So you must do the basic LVM commands in the master script. > In conclusion, it seems to me that if you can make systemconfigurator > work correctly on CentOS 6.x, then SI and/or SALI should work as well > for installing clients that will be bootable. > We have implemented a `grub2_install` functions or create a postinst script that will do it for you -- ******************************************************************** * Bas van der Vlies e-mail: ba...@sa... * * SARA - Academic Computing Services Amsterdam, The Netherlands * ******************************************************************** |
Thanks for helping keep SourceForge clean.
X