sisuite-devel — Development

[Sisuite-devel] si_netbootmond: design issue: best solution to fix it?

[Olivier L. <oli...@ce...>]

Dear all,

I'm working on si_netbootmond (in fact working on OSCAR side) and discovered that 
si_netbootmond rely on the fact that the imaging method is rsync.
It monitors the rsyncd log file for magic works stating that imaging is complete.

There are 2 problems here:
1/ It doesn't work for deployment using flamethrower /multicast or bittorrent
2/ If a client is successfully imaged, this doesn't mean that it is able to reboot (bad 
image, bad bootloader, ...) in this situation, setting local boot is wrong.

I see 3 solutions:
1/ replace the actual code that scans /var/log/systemimager/rsyncd for magic 
words for magic words: /scripts\/imaging_complete_?([\.0-9]+)?/
with something that would do something like
use File::Monitor;
my $monitor = File::Monitor->new();$monitor->watch('somefile.txt');




Regards,

Olivier.

-- 
    Olivier Lahaye
    DRT/LIST/DIR

Re: [Sisuite-devel] option-140 to 145 dhcp parameters not standard:

[Brian E. F. <br...@th...>]

Hi Olivier,

I considered officially registering our values many years back, but
decided to simply use options in the unassigned ranges.  The ones we're
currently using were unassigned at the time, but it seems they now have
other officially assigned uses -- thanks for calling this out Olivier.

I do think this indicates that we _need_ make a change.

If we can get these values registered, that would be ideal, as we would
not have to worry about this situation again.  Can you find out what it
takes (if someone else already knows - please speak up)?  If it's
reasonable effort, let's go for it.  If it's onerous, then perhaps we
settle on using the private use range.

Once we've decided on "registered" or "Private Use", then we should
update the code to work with the new range, but be backwards compatible:

    if( defined $NEW_OPTION_NUMBER ) {
        then use it;
    elsif( defined $OLD_OPTION_NUMBER ) {
        use it for backwards compatibility;
    }


si_mkdhcpserver should be modified to always implement the option
numbers, of course.

Cheers!

-Brian


On Wed, Mar 20, 2013 at 03:54:19PM +0000, LAHAYE Olivier wrote:
> 
> Hi,
> 
> I've discoverd that the options that systeimager is using in its dhcp config are not standard and can conflict
> http://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters.xml
> 
> What should be done about this?
> - Still use those wrong values
> - Use values from the private range?
> - Do an RFC to have our values registered? (I don't know how to do that and if it's free or not.



 
> Any ideas?
> 
> Olivier.
> --
>    Olivier LAHAYE
>    CEA DRT/LIST/DCSI/DIR

> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar

> _______________________________________________
> sisuite-devel mailing list
> sis...@li...
> https://lists.sourceforge.net/lists/listinfo/sisuite-devel


-- 
Brian Elliott Finley
Mobile: 469.444.0167

[Sisuite-devel] option-140 to 145 dhcp parameters not standard:

[LAHAYE O. <oli...@ce...>]

Hi,

I've discoverd that the options that systeimager is using in its dhcp config are not standard and can conflict
http://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters.xml

What should be done about this?
- Still use those wrong values
- Use values from the private range?
- Do an RFC to have our values registered? (I don't know how to do that and if it's free or not.

Any ideas?

Olivier.
--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

[Sisuite-devel] Need Help: dhclient - No broadcast interfaces found.

[LAHAYE O. <oli...@ce...>]

Dear all,

The new systemimager (new boel binaries) is almost finished and seems to works really fine on my test machines.
The new udevd works fine and correctly probe hardware, loads firmwares, the kernel does not crash, and I was able to reach the dhclient step. I can deploy an image if I fix the ip by typing "dhclient eth0" and start the deploy script by hand.

The problem I have is that the dhclient fails to detect the eth0 interface if not specified on the command line (eth0 exists and can be configured).
if I issue a dhclient eth0, it works.....
The problem is similar to this thread: http://forums.fedoraforum.org/showthread.php?t=252210

Unfortunately, this is an initrd and there is no NetworkManager at all.

So I assume that there is some way to free this interface from NetworkManager, but HOW?

- Is it a kernel option I need to enable/disable?
- if yes, will it be obsolete soon?
- Is it a udev option I need to enable/diable?
- if yes, will it be obsolete soon?
- Should I install network manager instead?
- should I write a script that loop on all interfaces shown by ifconfig -a, and if the BROADCAST flag is set, then issue a dhclient <iface_name> ?

Any advise is welcome. If no answer, I'll go for the 6th solution until I can find a better one.

Best regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

[Sisuite-devel] RE : [PROVENANCE INTERNET] RE : systemimager build fixed with latest kernel+latest udev.

[LAHAYE O. <oli...@ce...>]

Dear all,

I've just hit this problem:
http://trac.mondorescue.org/ticket/589

1 - Recent udev versions (>173) had change udevadm and udevd paths, and also changed some udevadm options.

2 - The replacement of module-init-tools by kmod, because module-init-tools has been declared as a dead project by his maintainer. The result was that modprobe, insmod, rmmod, lsmod and modinfo are now links to /usr/bin/kmod, and their paths also changed.

This should be fixeable......

I'm working on it.

Olivier.


--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR
________________________________
De : LAHAYE Olivier
Date d'envoi : jeudi 14 mars 2013 19:45
À : sis...@li...
Objet : [PROVENANCE INTERNET] [Sisuite-devel] RE : systemimager build fixed with latest kernel+latest udev.


After a short test, the initrd boots without kernel panic, but the udev init script needs changes, I'll work on that tomorrow.

Best regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR
________________________________
De : LAHAYE Olivier
Date d'envoi : jeudi 14 mars 2013 19:12
À : sis...@li...
Objet : [PROVENANCE INTERNET] [Sisuite-devel] systemimager build fixed with latest kernel +latest udev.


Dear all,

I've finaly managed to build latest udev using a recent kernel.

The trick I used is not beautifull, but I saw no other solution.

The situation before:
The build system did build the components for the initrd image using system installed includes.
Thus, when building udev for exmaple, it was compiled with the running kernel headers instead of the built kernel headers and it was linked with system installed libs, not with built libraries like blkid and such.

The solution I used is the following:
when preparing the initrd build dir, I copy the running system includes in it (to have a base).
Then I build the kernel and install the kernel headers on top of includes I've copied from the system. This simulates the fact I installed the kernel on the running system.
Then for each components, I use a CFLAGS and LDFLAG that points to the build dir to use as much as possible the built stuffs, and I make install (instead of make install-exec) in to the build_dir. This also installs the newer includes and the newer libs that will be used by subsequents build.
In the end, before building the initrd, I remove unnecessary files like /usr/include, /usr/share, /share, /lib/*.la and so.

This is not perfect, but far better than previous situation when udev was build whith 2.6.34.1 kernel headers and ran under kernel 3.7.5 which memory structures that had slightly changed.

The current issue is that util-linux needs udev and that udev needs util-linux. (chicken and egg problem). For the moment, util-linux is built before udev so udev can use the latest libblkid that match the kernel.

Hopefully, this will work. No kernel panic when udevd starts.

I've built successfully the fedora rpms and I'm currently building the CentOS-6.3 ones.

They'll be available here:

http://olivier.lahaye1.free.fr/OSCAR/unstable/

I'll test tomorrow...

Best regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

[Sisuite-devel] RE : systemimager build fixed with latest kernel +latest udev.

[LAHAYE O. <oli...@ce...>]

After a short test, the initrd boots without kernel panic, but the udev init script needs changes, I'll work on that tomorrow.

Best regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR
________________________________
De : LAHAYE Olivier
Date d'envoi : jeudi 14 mars 2013 19:12
À : sis...@li...
Objet : [PROVENANCE INTERNET] [Sisuite-devel] systemimager build fixed with latest kernel +latest udev.


Dear all,

I've finaly managed to build latest udev using a recent kernel.

The trick I used is not beautifull, but I saw no other solution.

The situation before:
The build system did build the components for the initrd image using system installed includes.
Thus, when building udev for exmaple, it was compiled with the running kernel headers instead of the built kernel headers and it was linked with system installed libs, not with built libraries like blkid and such.

The solution I used is the following:
when preparing the initrd build dir, I copy the running system includes in it (to have a base).
Then I build the kernel and install the kernel headers on top of includes I've copied from the system. This simulates the fact I installed the kernel on the running system.
Then for each components, I use a CFLAGS and LDFLAG that points to the build dir to use as much as possible the built stuffs, and I make install (instead of make install-exec) in to the build_dir. This also installs the newer includes and the newer libs that will be used by subsequents build.
In the end, before building the initrd, I remove unnecessary files like /usr/include, /usr/share, /share, /lib/*.la and so.

This is not perfect, but far better than previous situation when udev was build whith 2.6.34.1 kernel headers and ran under kernel 3.7.5 which memory structures that had slightly changed.

The current issue is that util-linux needs udev and that udev needs util-linux. (chicken and egg problem). For the moment, util-linux is built before udev so udev can use the latest libblkid that match the kernel.

Hopefully, this will work. No kernel panic when udevd starts.

I've built successfully the fedora rpms and I'm currently building the CentOS-6.3 ones.

They'll be available here:

http://olivier.lahaye1.free.fr/OSCAR/unstable/

I'll test tomorrow...

Best regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

[Sisuite-devel] systemimager build fixed with latest kernel + latest udev.

[LAHAYE O. <oli...@ce...>]

Dear all,

I've finaly managed to build latest udev using a recent kernel.

The trick I used is not beautifull, but I saw no other solution.

The situation before:
The build system did build the components for the initrd image using system installed includes.
Thus, when building udev for exmaple, it was compiled with the running kernel headers instead of the built kernel headers and it was linked with system installed libs, not with built libraries like blkid and such.

The solution I used is the following:
when preparing the initrd build dir, I copy the running system includes in it (to have a base).
Then I build the kernel and install the kernel headers on top of includes I've copied from the system. This simulates the fact I installed the kernel on the running system.
Then for each components, I use a CFLAGS and LDFLAG that points to the build dir to use as much as possible the built stuffs, and I make install (instead of make install-exec) in to the build_dir. This also installs the newer includes and the newer libs that will be used by subsequents build.
In the end, before building the initrd, I remove unnecessary files like /usr/include, /usr/share, /share, /lib/*.la and so.

This is not perfect, but far better than previous situation when udev was build whith 2.6.34.1 kernel headers and ran under kernel 3.7.5 which memory structures that had slightly changed.

The current issue is that util-linux needs udev and that udev needs util-linux. (chicken and egg problem). For the moment, util-linux is built before udev so udev can use the latest libblkid that match the kernel.

Hopefully, this will work. No kernel panic when udevd starts.

I've built successfully the fedora rpms and I'm currently building the CentOS-6.3 ones.

They'll be available here:

http://olivier.lahaye1.free.fr/OSCAR/unstable/

I'll test tomorrow...

Best regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

[Sisuite-devel] RE : [sisuite-users] RE : udev Compile Fails - GitHub Master Branch

[LAHAYE O. <oli...@ce...>]

Hi Carl,

thanks for the tip. In fact, my concern is regarding the kernel we use. If we build kernel 3.7.5 for example and if we run an udevd compiler with kernel heardes 2.6.34, the structures won't match and IMHO (I'm far from being an expert)  I think that udevd could crash the kernel, or the kernel could crash udevd...

My exact problem is to build udev using the kernel we create, not the kernel headers from the system installed kernel. Once I figure out how to do that, I think all issues will disapear.
having kernel-2.6.34.1 build in SystemImager hides this problem as the kernel is built using its own 2.6.34.1 kernel hearder, and udev is built using system installed kernel header V2.6.34.1 which are (in this specific case) the same.

So I think that there are 2 coices:

1/ revert back to 2.6.34.1 (and accept that some recent network drivers and other drivers are not available)
or
2/ find a way (using patch or specific defines) to build udev using alternative kernel headers.

IMHO, I'm for the second version because:

1/ Not all distributions have the same kernel revision. Thus having kernel 2.6.34.1 on centos can be fine, but can be a problem on latest ubuntu which uses a newer kernel thus newer kernel hearder, thus the udev build may fail.

2/ Being independant from system installed kernel headers let us update kernel and udev when new hardware is supported.

To achiev the second step, we need to build and install components in the build_dir using make install instead of make "install-exec" so we can use includes in sync whith what we build. Then just before crating the initrd, we can remove the unwanted includes and docs.

Of course, this is my humble vision of things, and as I'm not low level system expert, I may be wrong.

So If someone think thare is a better option, don't hesitate to write here.

Best regards.
--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

________________________________________
De : Carl Richell [ca...@sy...]
Date d'envoi : vendredi 22 février 2013 14:27
À : sis...@li...
Objet : Re: [sisuite-users] RE : udev Compile Fails - GitHub Master Branch

Hi Oliver,

Maybe you've tried this but pushing back to the udev version in centos
6.3 might do the trick. Strange thing is, according to the package list
( http://mirror.centos.org/centos/6.3/os/x86_64/Packages/ ) centos 6 is
using version 147 --- but 147 isn't in the list of udev packages hosted
at kernel.org (where si downloads the package).

http://www.kernel.org/pub/linux/utils/kernel/hotplug/

maybe run "udevd --version" to see exactly what's running on centos. At
least you'll know that version has compiled for the os.

Cheers,


Carl

On 02/18/2013 01:41 AM, LAHAYE Olivier wrote:
> Hi,
>
> Unfortunately, under centos-6.3 it still fails with the following error:
>    CC     udev/udev-builtin-input_id.o
> udev/udev-builtin-input_id.c: In function ‘test_key’:
> udev/udev-builtin-input_id.c:165: erreur: ‘BTN_TRIGGER_HAPPY’ undeclared (first use in this function)
> udev/udev-builtin-input_id.c:165: erreur: (Each undeclared identifier is reported only once
> udev/udev-builtin-input_id.c:165: erreur: for each function it appears in.)
>
> The problem is that the file /usr/include/linux/input.h is too old (kernel-headers-2.6.32-279.19.1.el6.x86_64).
> there is no include for <uapi/linux/input.h>  which contains the definition.
>
> How Can I force the compiler to find src/linux-3.7.5/include/linux/input.h before /usr/include/linux.h ???
> -I seems not sufficient. Am I wrong?
>
> Olivier.
> --
>     Olivier LAHAYE
>     CEA DRT/LIST/DCSI/DIR
>
> ________________________________________
> De : Carl Richell [ca...@sy...]
> Date d'envoi : dimanche 17 février 2013 17:51
> À : sis...@li...
> Objet : Re: [sisuite-users] udev Compile Fails - GitHub Master Branch
>
> I was able to solve this problem by backing udev to version 175 (the
> version in Ubuntu 12.04)
>
> modify src/initrd_source/make.d/udev.rul
> change "UDEV_VERSION    = 182" to "UDEV_VERSION    = 175"
>
> Cheers,
>
>
> Carl
>
> On 02/16/2013 04:23 PM, Carl Richell wrote:
>> Hi, and thanks in advance for any help you can provide.
>>
>> I'm attempting to compile SystemImager from the github master branch
>> (https://github.com/finley/SystemImager). Compilation fails at udev
>> with this error:
>>
>> /usr/bin/ld: cannot find
>> SystemImager-master/initrd_source/build_dir/lib: File format not
>> recognized
>> collect2: ld returned 1 exit status
>> make[3]: *** [udevadm] Error 1
>> make[3]: *** Waiting for unfinished jobs....
>>
>> "SystemImager-master" is the root folder. I'm compiling on Ubuntu
>> 12.04 Server. Any ideas?
>>
>> Thanks!
>>
>>
>> Carl
>
> ------------------------------------------------------------------------------
> The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
> is your hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials, tech docs,
> whitepapers, evaluation guides, and opinion stories. Check out the most
> recent posts - join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> sisuite-users mailing list
> sis...@li...
> https://lists.sourceforge.net/lists/listinfo/sisuite-users
>
> ------------------------------------------------------------------------------
> The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
> is your hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials, tech docs,
> whitepapers, evaluation guides, and opinion stories. Check out the most
> recent posts - join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> sisuite-users mailing list
> sis...@li...
> https://lists.sourceforge.net/lists/listinfo/sisuite-users


------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
sisuite-users mailing list
sis...@li...
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[Sisuite-devel] Need help (udev build needs newer kernel includes)

[LAHAYE O. <oli...@ce...>]

Hi,

I've understood a little bit better the udev problem (udev not loading required drivers).

According to this link (http://my.safaribooksonline.com/book/operating-systems-and-server-administration/embedded-linux/9780137061129/udev/ch19lev1sec8#X2ludGVybmFsX0h0bWxWaWV3P3htbGlkPTk3ODAxMzcwNjExMjklMkZjaDE5bGV2MXNlYzgmcXVlcnk9) the modprobe command from busybox is not compatible with udev, thus no module is loaded and no error is displayed.

The solution is to build module-init-tools wich seems not too complicated.

But before fixing this, we need to be able to build a recent udev that is aware of recent hardware. Unfortunately, the initrd build mechanisme assumes that we can use build host includes and libraries to build its components. While it should work in most cases, it's a problem with components depending on something newer that the version present on the build host.

for udev, we hit this problem several times:
1st we need a newer libblkid (fixed)
2nd, we need libkmod (not present at least on centos6) (fixed)
3rd, we need includes (input.h) for kernel 3.2+ and this is my problem.

I've tryed to add a -I$(INITRD_BUILD_DIR)/src/linux-2.7.5/include to the CFLAGS, unfortunately, this is far not sufficient. as those includes assumes some other definitions that are not yet in the build host /usr/include (too old version).

I've also tryed to do a "make install" instead of "make install-exec" in many rules so includes are installed in the $(INITRD_BUILD_DIR)/usr/include (then cleared at the end before the mkinitrd) but this seems not sufficient.

So I think this is the wrong approach.

So for now, I'm stuck with udev. The current version is far too old for recent hardwares, and newer versions can't be build.

ANY advise or help would be greatly apreciated

Best regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

[Sisuite-devel] RE : [sisuite-users] systemimager-4.3.0-0.3 (kernel 3.7.2, hpsa, bnx2, ...) (For testing purpose).

[LAHAYE O. <oli...@ce...>]

Hi,

Thanks a lot for all your debugging.
1/ I'll add your patch regarding the rsync as on normal systems, there are no links, so it will only  increase the initrd size if your are using HP patches.
Is the HP hpsa driver very different from the one included in the standard kernel? I mean, is it usefull to use a proprietary driver for just imaging a drive?

As for the other problem, I must admit that I'm a little bit scared, as it seems to involve udev, and the latest udev can't be built easily on centos-6 :-( deps on util-linux or the like if my memory is correct. I hope it is not incompatible with kernel 3.7.2 .... I thought upgrading kernel to latest version would help having new exotic drivers available like 10Gb ethernet cards or latests raid controler, but it seems that it is a somewhat bad idea.
What I'm missing is that disk drivers and net drivers don't get loaded automaticaly when udev starts.... I've also noted that /etc/udev/rules.d is missing... IMHO, that may help in drivers loading if this directory is present. Need to have a look at why it is missing.

A few mail before, I said that I can't test anything at the moment, but this should change early next week I think, so I should be able to fix those things once for all again.
the dhclient problem is due to the dhcp update, so it should be easy to fix.

For the hpsa.ko module not loaded, a temporary workaround should be to modprobe it in the preinstall script.

For the firmware, it seems that they are not all built when building kernel. The copy workaround is not beautifull as it requires that firmware not needed on the imaging server must be installed if an imaged system requires it, but in the meantime, it's BTN (Better Than Nothing). So I'll include it asap.

Stay tuned, I'm working an this :-)

Best regards.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR
________________________________
De : dav...@cn... [dav...@cn...]
Date d'envoi : jeudi 24 janvier 2013 17:03
À : LAHAYE Olivier
Objet : Fw: [sisuite-users] systemimager-4.3.0-0.3 (kernel 3.7.2, hpsa, bnx2, ...) (For testing purpose).


Olivier,

Just received a reply from the list saying the post exceeded the limit and it needs to be approved by the moderator ...
In the meantime her is the post sent directly to you !

I was running out the door last night when I posted and forgot to answer your question :

- I included the rsync -L option(as described below with a snippet from my original post)  because
  unfortunately this is the default result when applying the HP spp(firmware and driver updates) to an HPserver.
  The first time an spp is applied to a server the HP updated driver is applied correctly to the /lib/modules/kernel
  tree. If you subsequently upgrade your kernel and then apply an spp again then the a link is made rather
 then the module being copied(as shown below). Yes I could fight HP/redhat on this however I don't
have the time or energy ...

     - Needed modules(ie hpsa) as symbolic links  under /lib/modules/(uname -r)
       ex
[root@scdev ~]# ls -al /lib/modules/2.6.32-220.4.2.el6.i686/weak-updates/hpsa/hpsa.ko
0 lrwxrwxrwx 1 root root 50 Mar  5 04:05 /lib/modules/2.6.32-220.4.2.el6.i686/weak-updates/hpsa/hpsa.ko -> /lib/modules/2.6.32-71.el6.i686/extra/hpsa/hpsa.ko
[root@scdev ~]#
        This results in the modules not being copied correctly in the generated initrd.
         I resolved this by modifying the UseYourOwnKernel.pm rsync invocations
         to copy the resultant files(the L rather then the l option. I include the diff
         below.


David K Livingstone
CN Signals and Communications
10229 127 Avenue floor 2
Walker Operations East Building
Edmonton, AB, T5E 0B9
Ph  : 780 472-3959 Fax : 780 472-3046
Email: Dav...@cn...
----- Forwarded by David Livingstone/LIVING03/CNR/CA on 2013/01/24 08:51 -----
From:   David Livingstone/LIVING03/CNR/CA
To:     sis...@li...
Date:   2013/01/23 16:51
Subject:        Re: [sisuite-users] systemimager-4.3.0-0.3 (kernel 3.7.2, hpsa, bnx2, ...) (For testing purpose).

________________________________


Olivier,

I just attempted to load an x86_64 machine using your previous build with my changes applied as described in my email below. I haven't
yet had a chance to look at your new build.

- I attempted a boot using the standard kernel/initd and :
   - the dhclient DEVICE failed. Later in the shell with "dhclient -v eth1) it turns out the interface was not up. After doing a "ifconfig eth1 up"
     the dhclinet eth1 is now is successful however now it attempts to write the lease into /var/db/dhclient.leases rather then
     the expected /var/state/dhcp/...  Did you ever get a dhclient boot to work ?
  - also during booting requested firmware was hanging ie netxen_nic:...: firmware: requesting phanfw.bin
    See below with uyok.
   - I eventually tried setting all the IP parameters and IMAGESERVER in the pxelinux.cfg  file which
     bypasses dhclient. At this point we now fail because there is no hpsa module loaded and no
     disks are visible.

-The uyok load fails as once again numerous firmware files fail to load. This problem did not happen
  with my initial test setup using the 4.1.99.svn4556_bli-1 packages but does with 4.3.0-0.2.el6.
  In this case the firmware files are in the initrd however what appears to have changed is
  that the firmware loading code changed from a shell script (firmware.sh) to a binary.

  See https://bugzilla.redhat.com/show_bug.cgi?id=560031

 The  4.1.99.svn4556_bli-1 package systemimager-i386initrd_template-4.1.99.svn4556_bli-1.noarch
 has :
[root@nasedm udev]# pwd
/usr/share/systemimager/boot/i386/standard/initrd_template/lib/udev
[root@nasedm udev]# ls
total 132
12 ata_id*     8 collect*                12 edd_id*       12 path_id*                  24 scsi_id*  12 vol_id*           4 write_net_rules*
 8 cdrom_id*  12 create_floppy_devices*   4 firmware.sh*   4 rule_generator.functions  16 usb_id*    4 write_cd_rules*
[root@nasedm udev]#


And the systemimager-x86_64initrd_template-4.3.0-0.2.el6.noarch has :
[root@wild1 udev]# pwd
/usr/share/systemimager/boot/x86_64/standard/initrd_template/lib/udev
[root@wild1 udev]# ls
total 356
24 ata_id*    12 collect*                20 edd_id*    20 fstab_import*  36 path_id*  40 usb_id*   4 write_cd_rules*
36 cdrom_id*  44 create_floppy_devices*  44 firmware*  32 input_id*      32 scsi_id*   8 v4l_id*   4 write_net_rules*
[root@wild1 udev]#

The original firmware.sh is invoked in the /usr/share/systemimager/boot/i386/standard/initrd_template/etc/udev/rules.d/80-programs.rules :

[root@nasedm udev]# rpm -qf /usr/share/systemimager/boot/i386/standard/initrd_template/etc/udev/rules.d/80-programs.rules
systemimager-i386initrd_template-4.1.99.svn4556_bli-1.noarch
[root@nasedm udev]# cd /usr/share/systemimager/boot/i386/standard/initrd_template/etc/udev/rules.d
[root@nasedm rules.d]# ls
total 56
4 00-init.rules     4 30-cdrom_id.rules  4 61-persistent-storage-edd.rules  4 75-cd-aliases-generator.rules      4 90-modprobe.rules
4 05-options.rules  4 60-cdrom_id.rules  4 65-persistent-input.rules        4 75-persistent-net-generator.rules  4 99-udevmonitor.rules
4 20-names.rules    4 60-symlinks.rules  4 65-persistent-storage.rules      4 80-programs.rules
[root@nasedm rules.d]# grep -i firmw *
80-programs.rules:# firmware class requests
80-programs.rules:SUBSYSTEM=="firmware", ACTION=="add", RUN+="/lib/udev/firmware.sh"







David K Livingstone
CN Signals and Communications
10229 127 Avenue floor 2
Walker Operations East Building
Edmonton, AB, T5E 0B9
Ph  : 780 472-3959 Fax : 780 472-3046
Email: Dav...@cn...


From:   LAHAYE Olivier <oli...@ce...>
To:     "sis...@li..." <sis...@li...>
Date:   2013/01/23 03:49
Subject:        [sisuite-users] systemimager-4.3.0-0.3 (kernel 3.7.2, hpsa, bnx2, ...) (For testing purpose).

________________________________


David,

I've updated my rpms 4.3.0-0.3 (currently being built).

- I've applyed your patch regarding the udev start.
- Regarding the firmwares, they were missing for unknown reason. Since I've upgraded the kernel to 3.7.2 and enabled many more drivers for disks (hpsa and more) and network devices (bnx2, ...), the firmwares that you were missing seems to be present in the image.
- Regarding UseYourOwnKernel, I didn't copy the firmwares as with the new kernel config, they seem to be included.
- I didn't had a look at the UYOK which doesn't copy the kernel and initrd.img.
- As for the -L option in rsync, I don't know if it's usefull as there are no links in the templates trees. If you use another tree, though, I'm not sure if the -L option is the way to fixe the issue you are seeing as it may result in bigger initrd with duplicate materials. at least a hard link could be a solution, though in the 1st place, the issue is caused by a missplaced thing and a trick is to create a softlink to hide the issue. Can't you have a tree with no soft links?

Could you give a test to these rpms and and test with default kernel?

Many thanks for your help.

Best Regards.

RPMS:
http://olivier.lahaye1.free.fr/RPMS/noarch/systemimager-bittorrent-4.3.0-0.3.el6.noarch.rpm
http://olivier.lahaye1.free.fr/RPMS/noarch/systemimager-client-4.3.0-0.3.el6.noarch.rpm
http://olivier.lahaye1.free.fr/RPMS/noarch/systemimager-common-4.3.0-0.3.el6.noarch.rpm
http://olivier.lahaye1.free.fr/RPMS/noarch/systemimager-flamethrower-4.3.0-0.3.el6.noarch.rpm
http://olivier.lahaye1.free.fr/RPMS/noarch/systemimager-i386boot-standard-4.3.0-0.3.el6.noarch.rpm
http://olivier.lahaye1.free.fr/RPMS/noarch/systemimager-i386initrd_template-4.3.0-0.3.el6.noarch.rpm
http://olivier.lahaye1.free.fr/RPMS/noarch/systemimager-server-4.3.0-0.3.el6.noarch.rpm
http://olivier.lahaye1.free.fr/RPMS/noarch/systemimager-x86_64boot-standard-4.3.0-0.3.el6.noarch.rpm
http://olivier.lahaye1.free.fr/RPMS/noarch/systemimager-x86_64initrd_template-4.3.0-0.3.el6.noarch.rpm

SRPMS:
http://olivier.lahaye1.free.fr/SRPMS/systemimager-4.3.0-0.3.el6.src.rpm

Scrips:
http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2
--

Olivier LAHAYE

CEA DRT/LIST/DCSI/DIR







De : dav...@cn... [dav...@cn...]

Date d'envoi : mercredi 16 janvier 2013 23:38

À : sis...@li...

Objet : Re: [sisuite-users] RE : Which version ?






Olivier,


Thanks. So far I have installed the rpm's on a dl380G7 with rhel6.3 x86_64 and both prepared the image(uyok) and retrieved from




a similar server with the server packages loaded.Next step will be to test load the image on another server using both the standard and uyok

( I'm a little gun shy tryingto load back to the same server incase there are problems).



I also re-applied the changes I've itemized below for the same reasons - btw the change below to rcS(start udev BEFORE load_my_modules) might



address why you had similar problems ie needing the pre-install script to load the modules).







-



David K Livingstone

CN Signals and Communications

10229 127 Avenue floor 2

Walker Operations East Building

Edmonton, AB, T5E 0B9

Ph  : 780 472-3959 Fax : 780 472-3046

Email: Dav...@cn...












From:
LAHAYE Olivier <oli...@ce...>



To:
"sis...@li..." <sis...@li...>



Date:
2013/01/07 02:05


Subject:
[sisuite-users] RE :  Which version ?








Hi,



You can try the 4.3.0-0.1svn version, it worked for me. You'll need pre and post-install scripts available here:


http://olivier.lahaye1.free.fr/RPMS/extra/


Cheers,




--




Olivier LAHAYE

CEA DRT/LIST/DCSI/DIR



De : dav...@cn... [dav...@cn...]


Date d'envoi : mercredi 19 décembre 2012 00:09


À : sis...@li...


Objet : [sisuite-users] Which version ?




I have been using a modified version of  4.1.99.svn4556_bli-1 to load my i386 rhel6.x servers as




described below. I am now looking at imaging similar machines but now with the x86_64 version


of rhel6.3 so I need like initrd_template( and boot_standard if it works) packages.



What  versions should I be trying ?

http://olivier.lahaye1.free.fr/RPMS/noarch/
??

Thanks





David K Livingstone




CN Signals and Communications

10229 127 Avenue floor 2

Walker Operations East Building

Edmonton, AB, T5E 0B9

Ph  : 780 472-3959 Fax : 780 472-3046

Email: Dav...@cn...

----- Forwarded by David Livingstone/LIVING03/CNR/CA on 2012/12/18 16:00 -----






From:

David Livingstone/LIVING03/CNR/CA



To:

sis...@li...



Date:

2012/03/29 09:41



Subject:

Loading RHEL 6.2 using 4.1.99.svn4556_bli-1









Using  systemimager  4.1.99.svn4556_bli-1(ext4 enabled version) I have successfully imaged a




RHEL 6.2 image to HP DL380G7 hardware(p410 array controllers). I was considering using SALI


however for RHEL6.x grub2 is not an issue and ext4 support is included in  4.1.99.svn4556_bli-1.



The setup I was imaging is a Proliant DL380G7 server with two p410 controllers(p401i and p410)



with raid1 for root/boot/swap on the p410i and raid5 for /data on the p410. The system is running


the latest RHEL 6.2.



The attempted to image the system in two ways:



1. standard kernel


2. uyok


1. standard kernel




I eventually got this to work but only after major modifications to the install script and manually


setting up grub.  The major issue here is that the default kernel uses the cciss driver and


device naming(ex /dev/cciss/c0d0p2) and the RHEL6.x uses the hpsa driver(scsi naming ex /dev/sda).


See http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02677069/c02677069.pdf
.

In general RHEL 5.x and before uses the cciss driver and RHEL6.x uses the hpsa when possible.


I presume the standard kernel could be built with the hpsa module and some version logic


applied to resolve this.


2. uyok



This worked successfully after making some changes to address :


- Needed modules(ie hpsa) as symbolic links  under /lib/modules/(uname -r)


ex
[root@scdev ~]# ls -al /lib/modules/2.6.32-220.4.2.el6.i686/weak-updates/hpsa/hpsa.ko


0 lrwxrwxrwx 1 root root 50 Mar  5 04:05 /lib/modules/2.6.32-220.4.2.el6.i686/weak-updates/hpsa/hpsa.ko -> /lib/modules/2.6.32-71.el6.i686/extra/hpsa/hpsa.ko


[root@scdev ~]#


This results in the modules not being copied correctly in the generated initrd.


I resolved this by modifying the UseYourOwnKernel.pm rsync invocations


to copy the resultant files(the L rather then the l option. I include the diff


below.




- Numerous /lib/firmware files were missing in the initrd. By default the


bnx2 nic driver(driver for the four nic's on the motherboard) as well as


others in the RHEL6.2 kernel request firmware which is missing in the


uyok initrd. I got this to work by :


- modifying UseYourOwnKernel.pm to copy /lib/firmware to the initrd.


Unfortunately this copies all of firmware as I couldn't figure out how to


dynamically copy what was needed.


- modified rcS under the std template to start udev BEFORE the modules


are inserted.


- rcS : start udev before loading modules.


- under the std template :


/usr/share/systemimager/boot/i386/standard/initrd_template/etc/init.d/rcS


- The ramdisk_size must be set high enough to accept the larger initrd.


-  I had to si_cpimage as part of testing and noted that for yuok the


kernel and initrd.img files are not copied. They had to be copied manually.




Notes :



When creating the image initially  I also had to change si_prepareclient to use parted rather then sfdisk. I believe a bug


was submitted on this a long time ago which was never applied. parted supports gpt


partitions and sfdisk does not.


[root@nasmtl sbin]# diff si_prepareclient si_prepareclient.orig.4.1.99.svn4556_bli



969,971c969,971

< #        if($arch eq "i386") {


< #                $preferred_tool = 'sfdisk';


< #        }

---

>         if($arch eq "i386") {


>                 $preferred_tool = 'sfdisk';


>         }


- Diff for UseYourOwnKernel.pm



[root@nasmtl SystemImager]# diff UseYourOwnKernel.pm UseYourOwnKernel.pm.orig


152c152

<                 $cmd = qq(rsync -aL --exclude=build --exclude=source ) .


---

>                 $cmd = qq(rsync -a --exclude=build --exclude=source ) .


159c159

<                     $cmd = qq(rsync -aLR $module $staging_dir);


---

>                     $cmd = qq(rsync -aR $module $staging_dir);


223,225d222

<         #

<         # Copy /lib/firmware file to initrd


<         #

227,233d223

<         if (-d "/lib/firmware") {


<            # copy entire firmware tree to new initrd.


<            $cmd = qq(rsync -aLR /lib/firmware $staging_dir);


<            !system( $cmd ) or die( "Couldn't $cmd." );


<

<         }

<


- Diff for rcS :


[root@nasmtl init.d]# diff rcS rcS.orig


45,47d44

< # Start udev BEFORE load_my_modules so the modules can load firmware if needed.


< start_udevd

<

49a47,48

> start_udevd

>














David K Livingstone


CN Signals and Communications

10229 127 Avenue floor 2

Walker Operations East Building

Edmonton, AB, T5E 0B9

Ph  : 780 472-3959 Fax : 780 472-3046

Email: Dav...@cn...

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

Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,

MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current

with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft

MVPs and experts. SALE $99.99 this month only -- learn more at:

http://p.sf.net/sfu/learnmore_122412


_______________________________________________

sisuite-users mailing list

sis...@li...

https://lists.sourceforge.net/lists/listinfo/sisuite-users











------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
sisuite-users mailing list
sis...@li...
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[Sisuite-devel] RE : git howto?

[LAHAYE O. <oli...@ce...>]

Thanks a lot for the git help, it works fine :-)

I'm rebuilding unofficial rpms.
Available here: http://olivier.lahaye1.free.fr/RPMS/noarch/
(source rpm: http://olivier.lahaye1.free.fr/SRPMS/)

Now, the make source_tarball is corking with git structure and rpm build from tar archive works fine:

From the SystemImager root dir:
make source_tarball
rpmbuild -ta tmp/systemimager-4.3.0.tar.bz2

(Build still need root privileges for now as the spec file needs to create device inodes and I did not yet look at the problem)

Cheers,

Olivier.
--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

________________________________________
De : Brian Finley [br...@th...]
Date d'envoi : lundi 7 janvier 2013 22:29
À : LAHAYE Olivier
Cc: sis...@li...
Objet : Re: [Sisuite-devel] git howto?

I'm not yet a git expert myself either, but this is what I've been using
with success:

┌─[bfinley@bob] ~/src/systemimager.git/ master ⚡
└─[$] git commit -m "verbiage" README
[master d309549] verbiage
  1 file changed, 2 deletions(-)

┌─[bfinley@bob] ~/src/systemimager.git/ master
└─[$] git push
Counting objects: 5, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 292 bytes, done.
Total 3 (delta 2), reused 0 (delta 0)
To gi...@gi...:finley/SystemImager.git
    80e899e..d309549  master -> master

┌─[bfinley@bob] ~/src/systemimager.git/ master
└─[$] git status
# On branch master
nothing to commit (working directory clean)


Cheers, -Brian



On 01/07/2013 11:42 AM, LAHAYE Olivier wrote:
> Hi,
>
> Sorry to disturb the list with this, but I'm pure newbee in git and
> despite my googleling, I'm unable to understand how to merge back all my
> changes.
>
> I've setup my git like this:
>
> $ git config --global user.email "my email"
>
> $ git config --global user.name "my login"
>
> $ git config --global core.autocrlf input
>
> $ git config --global core.safecrlf true
>
> $ git clone https://github.com/finley/SystemImager.git
>
>
> Then I did commit my changes, and now I'd like to merge, what should I
> do to merge back my fixes? I've tryed the following with no success:
>
> $ git merge master
> Already up-to-date.
>
> $ git status
> # On branch master
> # Your branch is ahead of 'origin/master' by 15 commits.
> #
> nothing to commit (working directory clean)
>
> My current git is clean and doing make source_tarball and rpmbuild -tb
> rpm/systemiamger-4.3.0.tar.bz2 produces correct rpm with all my fixes
> including my last bugfix.
>
> Many thanks for your help.
>
> Regards,
>
> Olivier.
> --
>     Olivier LAHAYE
>     CEA DRT/LIST/DCSI/DIR
>
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122412
>
>
>
> _______________________________________________
> sisuite-devel mailing list
> sis...@li...
> https://lists.sourceforge.net/lists/listinfo/sisuite-devel
>

--
Brian Elliott Finley
Mobile: 469.444.0167

Re: [Sisuite-devel] git howto?

[Brian F. <br...@th...>]

I'm not yet a git expert myself either, but this is what I've been using
with success:

┌─[bfinley@bob] ~/src/systemimager.git/ master ⚡
└─[$] git commit -m "verbiage" README
[master d309549] verbiage
  1 file changed, 2 deletions(-)

┌─[bfinley@bob] ~/src/systemimager.git/ master
└─[$] git push
Counting objects: 5, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 292 bytes, done.
Total 3 (delta 2), reused 0 (delta 0)
To gi...@gi...:finley/SystemImager.git
    80e899e..d309549  master -> master

┌─[bfinley@bob] ~/src/systemimager.git/ master
└─[$] git status
# On branch master
nothing to commit (working directory clean)


Cheers, -Brian



On 01/07/2013 11:42 AM, LAHAYE Olivier wrote:
> Hi,
>
> Sorry to disturb the list with this, but I'm pure newbee in git and
> despite my googleling, I'm unable to understand how to merge back all my
> changes.
>
> I've setup my git like this:
>
> $ git config --global user.email "my email"
>
> $ git config --global user.name "my login"
>
> $ git config --global core.autocrlf input
>
> $ git config --global core.safecrlf true
>
> $ git clone https://github.com/finley/SystemImager.git
>
>
> Then I did commit my changes, and now I'd like to merge, what should I
> do to merge back my fixes? I've tryed the following with no success:
>
> $ git merge master
> Already up-to-date.
>
> $ git status
> # On branch master
> # Your branch is ahead of 'origin/master' by 15 commits.
> #
> nothing to commit (working directory clean)
>
> My current git is clean and doing make source_tarball and rpmbuild -tb
> rpm/systemiamger-4.3.0.tar.bz2 produces correct rpm with all my fixes
> including my last bugfix.
>
> Many thanks for your help.
>
> Regards,
>
> Olivier.
> --
>     Olivier LAHAYE
>     CEA DRT/LIST/DCSI/DIR
>
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122412
>
>
>
> _______________________________________________
> sisuite-devel mailing list
> sis...@li...
> https://lists.sourceforge.net/lists/listinfo/sisuite-devel
>

-- 
Brian Elliott Finley
Mobile: 469.444.0167

[Sisuite-devel] git howto?

[LAHAYE O. <oli...@ce...>]

Hi,

Sorry to disturb the list with this, but I'm pure newbee in git and despite my googleling, I'm unable to understand how to merge back all my changes.

I've setup my git like this:

$ git config --global user.email "my email"

$ git config --global user.name "my login"

$ git config --global core.autocrlf input

$ git config --global core.safecrlf true

$ git clone https://github.com/finley/SystemImager.git

Then I did commit my changes, and now I'd like to merge, what should I do to merge back my fixes? I've tryed the following with no success:

$ git merge master
Already up-to-date.

$ git status
# On branch master
# Your branch is ahead of 'origin/master' by 15 commits.
#
nothing to commit (working directory clean)

My current git is clean and doing make source_tarball and rpmbuild -tb rpm/systemiamger-4.3.0.tar.bz2 produces correct rpm with all my fixes including my last bugfix.

Many thanks for your help.

Regards,

Olivier.
--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

[Sisuite-devel] SystemImager microcode request during netboot

[Francesca T. <fra...@e4...>]

Dear all,

I'm trying the new release of system imager but I have the following situation.
I'm working on systems with 2x Intel E5-2620 each and CentOS 6.3 (2.6.32-279.el6.x86_64) with ext3 filesystem.
The initial process of image retrieval is fine, but as soon as the client starts to do the netboot from the master node and before the retrieving of all the image files, I have the following message from the shell:

Microcode: CPU1 sig=0x206d7, pf=0x1, revision 0x702
Platform microcode: firmware: requesting intel-ucode/06-2d-07

24 times and it takes like 30-40 minutes to complete and start the imaging process.
This situation happens only when I try to install systems using system imager netboot (if I install a node using an install server or a dvd everything is good) and when I use CentOS 6.3 and also 6.2.
Does anyone know how to fix this?

Any help or suggestion will be really appreciated.

Best regards

Ing. Francesca Tartaglione
Technical Marketing Engineer
E4 Computer Engineering Spa
Switchboard: +39 0522 991811 . Fax: +39 0522 991803
Email: fra...@e4...<mailto:fra...@e4...>
Website: http://www.e4company.com<http://www.e4company.com/>

P "Considera la responsabilità che hai verso l'ambiente e prima di stampare questa e-mail domandati: ho davvero bisogno di una copia cartacea ?"
        "Please consider your environmental responsibility and before printing this e-mail ask yourself: do I need a hard copy?"

--
E4 Computer Engineering S.p.A.
Via Martiri della Liberta', 66 . 42019 Scandiano (RE) . Italy
P.I./C.F/Registro Imprese di RE 02005300351 . Cap.Soc. Euro 150.000,00 i.v.
Registro Pile  IT 09060P00000265 . Registro A.E.E.  IT0802 000 000 1117 .

Disclaimer:
La presente comunicazione/mail è strettamente confidenziale e riservata, contiene informazioni legali destinate esclusivamente al soggetto indicato quale destinatario. Il ricevente la presente comunicazione, se diverso dal destinatario sopra indicato, è avvertito che qualunque utilizzazione o copia della stessa è rigorosamente vietata ed è pregato di volerne dare immediata comunicazione, anche telefonica, e ritrasmettere la stessa per posta all'azienda.
Il trattamento dei dati in nostro possesso, rilevati per esigenze fiscali/amministrative e nel corso della normale attività commerciale e di cui Le garantiamo la massima riservatezza, è effettuato anche per aggiornarla sulle nostre iniziative e offerte commerciali. I dati non saranno comunicati e diffusi a terzi e per essi Lei potrà richiedere, in qualsiasi momento, la modifica o la cancellazione, comunicandocelo tramite posta, e-mail o altro mezzo valido, come previsto dall'articolo 13 del D.lgs 196/2003. Potrà, allo stesso modo, comunicarci anche successivamente la volontà di non ricevere eventuali news.

Disclaimer:
This message and any document transmitted may contain material that is confidential or proprietary to the sender for the sole use of the intended recipient. If you are not the intended recipient of this message, please do not read this message and notify us immediately by e-mail or by telephone and then delete this message and any document attached.
Any personal info, obtained for fiscal and administrative purposes only during the regular commercial sphere of activity and for which we guarantee the strictest privacy, will be also used to keep you updated on our enterprises and commercial offers. Your data shall not be passed on to any third party and you may ask to have them modified or cancelled from our data base at any one time, by post, e-mail or any other valid medium, as set by par. 13 del D.lgs 196/2003.  Equally, you will be able to tell us if you do not wish to receive anymore news on a later date.

[Sisuite-devel] RE : RE : RE : New systemimager rpms for centos6 with ext4 support

[LAHAYE O. <oli...@ce...>]

You're perfectly right, a big mistake from my part. I replaced 'Disk' by "$DISK0" in my script (in order to avoid grepping 2 lines as the new parted now outputs Disk flags), but forgot to replace the simple quotes in the script.

Fixed in the svn, but maybe it should also be fixed in the git repos? (I've never used git and need time to learn it)

Cheers,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR
________________________________
De : Jing CDL Sun [sj...@cn...]
Date d'envoi : jeudi 27 décembre 2012 08:51
À : LAHAYE Olivier
Cc: sis...@li...; sis...@li...
Objet : RE : RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support

Olivier,

Have you updated the line "DISK_SIZE=`LC_ALL=C parted -s $DISK0 unit MB print | egrep '$DISK0' | awk '{print $NF}' | sed 's/MB//' `" in the .master script? I found it can not work in build 4.2.0-0.91svn4568 for redhat6.3.

I think it should be "DISK_SIZE=`parted -s $DISK0 unit MB print | egrep "$DISK0" | awk '{print $NF}' | sed 's/MB//' `", use "" instead of '' around $DISK0, so shell can translate it.
I tested this fix, it can work.

Thx.
Jing





LAHAYE Olivier <oli...@ce...>

2012/12/18 17:03


To
        Jing CDL Sun/China/IBM@IBMCN,
cc
        "sis...@li..." <sis...@li...>, "sis...@li..." <sis...@li...>
Subject
        RE : RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support








Jing,

You're perfectly right, the ext4 problem was related to default initrd. The build did not enable the ext4 module. It's fixed in last build.

Cheers,

Olivier.

--
  Olivier LAHAYE
  CEA DRT/LIST/DCSI/DIR
________________________________

De : Jing CDL Sun [sj...@cn...]
Date d'envoi : mardi 18 décembre 2012 06:35
À : LAHAYE Olivier
Cc: sis...@li...; sis...@li...
Objet : RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support

Thx for the reply.

When I used your build with 4.2.0-0.9svn4568, I did not run into this problem, so I'm thinking maybe this is not a missing module problem?

When you said 4.2.0-0.91svn4568 fixed the ext4 missing problem, did you mean the default initrd? because it seems  4.2.0-0.9svn4568 worked fine for me without the ext4 issue.

Yes, I did not use the systemimager default kernel and initrd, instead, I'm using my own kernel/initrd got from my golder client, it's rhel6.3, so I think it should work fine, right?





LAHAYE Olivier <oli...@ce...>
2012/12/17 17:16
To
        Jing CDL Sun/China/IBM@IBMCN,
cc
        "sis...@li..." <sis...@li...>, "sis...@li..." <sis...@li...>
Subject
        RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support










This means that your disk is not recognized.

Did you use my install scripts (especially the pre-install).
http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2

It modprobs some modules in order to see disks. I don't know my the systemimager initrd fails to automaticaly do that (did not have time to look at the problem).

if you did use the script, it means that you need to modify it to have more modules inserted. Or, if your hardware is too recent (not supported by provided  default kernel), then you'll need to use your own kernel for the moment.

I cannot upgrade easily the kernel to 3.X as it'll require to upgrade some utils too and therefore, it'll break build on RHEL6 as well. Indeed, the build will copy missing stuffs from /lib /lib64 and other places and thoses version are for a 2.6.x kernel, not a 3.X kernel.
This is also the reason why build fails on CentOS5 cas the libs copied from system misses some symbols (too old).

In order to safely upgrade systemimager to latest kernel, we need to modifiy the build process so it builds everything and link everything with it's material which is not fully the case for now. (it still copy stuffs from the build system root tree (convenient ugly dirty hack)).

Hope this helps,

Cheers,

Olivier.


--
 Olivier LAHAYE
 CEA DRT/LIST/DCSI/DIR
________________________________

De : Jing CDL Sun [sj...@cn...]
Date d'envoi : lundi 17 décembre 2012 07:42
À : LAHAYE Olivier
Cc: sis...@li...; sis...@li...
Objet : Re: [Sisuite-devel] New systemimager rpms for centos6 with ext4 support

Hi,

I just tested these new rpms, but found the issues below, the install broken.

Dec 17 14:42:36 x3550m4n02 logger: logger: parted -s -- /dev/sda mklabel gpt || shellout
Dec 17 14:42:36 x3550m4n02 kernel:  sda: unknown partition table


Thx.
Jing

LAHAYE Olivier <oli...@ce...>
2012/12/13 22:47
To
        "sis...@li..." <sis...@li...>,
cc
        "sis...@li..." <sis...@li...>
Subject
        [Sisuite-devel] New systemimager rpms for centos6 with ext4 support












Dear all,

Here are my fixed systemimager rpms for centos-6.3
Now, the ext4 filesystem is fixed (the module was missing in the initrd image)
I've tested this on recent hardware and it worked like a charm.

Thoses RPMS are for testing purpose


RPMS: http://olivier.lahaye1.free.fr/RPMS/noarch
SRPMS: http://olivier.lahaye1.free.fr/SRPMS/systemimager-4.2.0-0.91svn4568.el6.src.rpm

PS: Keep in mind that you need postinstall scripts (already posted here) to setup grub, network and other stuffs as systemconfiguratior is unable to handle latest linux technologies.

Best regards,

Olivier
--
Olivier LAHAYE
CEA DRT/LIST/DCSI/DIR------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d_______________________________________________
sisuite-devel mailing list
sis...@li...
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

[Sisuite-devel] RE : RE : New systemimager rpms for centos6 with ext4 support

[Jing C. S. <sj...@cn...>]

Olivier,

Have you updated the line "DISK_SIZE=`LC_ALL=C parted -s $DISK0 unit MB 
print | egrep '$DISK0' | awk '{print $NF}' | sed 's/MB//' `" in the 
.master script? I found it can not work in build 4.2.0-0.91svn4568 for 
redhat6.3.

I think it should be "DISK_SIZE=`parted -s $DISK0 unit MB print | egrep 
"$DISK0" | awk '{print $NF}' | sed 's/MB//' `", use "" instead of '' 
around $DISK0, so shell can translate it.
I tested this fix, it can work.

Thx.
Jing






LAHAYE Olivier <oli...@ce...> 
2012/12/18 17:03

To
Jing CDL Sun/China/IBM@IBMCN, 
cc
"sis...@li..." 
<sis...@li...>, 
"sis...@li..." 
<sis...@li...>
Subject
RE : RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 
support







Jing,

You're perfectly right, the ext4 problem was related to default initrd. 
The build did not enable the ext4 module. It's fixed in last build.

Cheers,

Olivier.

-- 
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

De : Jing CDL Sun [sj...@cn...]
Date d'envoi : mardi 18 décembre 2012 06:35
À : LAHAYE Olivier
Cc: sis...@li...; 
sis...@li...
Objet : RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 
support

Thx for the reply. 

When I used your build with 4.2.0-0.9svn4568, I did not run into this 
problem, so I'm thinking maybe this is not a missing module problem? 

When you said 4.2.0-0.91svn4568 fixed the ext4 missing problem, did you 
mean the default initrd? because it seems  4.2.0-0.9svn4568 worked fine 
for me without the ext4 issue. 

Yes, I did not use the systemimager default kernel and initrd, instead, 
I'm using my own kernel/initrd got from my golder client, it's rhel6.3, so 
I think it should work fine, right? 






LAHAYE Olivier <oli...@ce...> 
2012/12/17 17:16 


To
Jing CDL Sun/China/IBM@IBMCN, 
cc
"sis...@li..." 
<sis...@li...>, 
"sis...@li..." 
<sis...@li...> 
Subject
RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support









This means that your disk is not recognized.

Did you use my install scripts (especially the pre-install).
http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2

It modprobs some modules in order to see disks. I don't know my the 
systemimager initrd fails to automaticaly do that (did not have time to 
look at the problem).

if you did use the script, it means that you need to modify it to have 
more modules inserted. Or, if your hardware is too recent (not supported 
by provided  default kernel), then you'll need to use your own kernel for 
the moment.

I cannot upgrade easily the kernel to 3.X as it'll require to upgrade some 
utils too and therefore, it'll break build on RHEL6 as well. Indeed, the 
build will copy missing stuffs from /lib /lib64 and other places and 
thoses version are for a 2.6.x kernel, not a 3.X kernel.
This is also the reason why build fails on CentOS5 cas the libs copied 
from system misses some symbols (too old).

In order to safely upgrade systemimager to latest kernel, we need to 
modifiy the build process so it builds everything and link everything with 
it's material which is not fully the case for now. (it still copy stuffs 
from the build system root tree (convenient ugly dirty hack)).

Hope this helps,

Cheers, 

Olivier.


-- 
  Olivier LAHAYE
  CEA DRT/LIST/DCSI/DIR 

De : Jing CDL Sun [sj...@cn...]
Date d'envoi : lundi 17 décembre 2012 07:42
À : LAHAYE Olivier
Cc: sis...@li...; 
sis...@li...
Objet : Re: [Sisuite-devel] New systemimager rpms for centos6 with ext4 
support

Hi, 

I just tested these new rpms, but found the issues below, the install 
broken. 

Dec 17 14:42:36 x3550m4n02 logger: logger: parted -s -- /dev/sda mklabel 
gpt || shellout 
Dec 17 14:42:36 x3550m4n02 kernel:  sda: unknown partition table 


Thx. 
Jing


LAHAYE Olivier <oli...@ce...> 
2012/12/13 22:47 


To
"sis...@li..." 
<sis...@li...>, 
cc
"sis...@li..." 
<sis...@li...> 
Subject
[Sisuite-devel] New systemimager rpms for centos6 with ext4 support











Dear all,

Here are my fixed systemimager rpms for centos-6.3
Now, the ext4 filesystem is fixed (the module was missing in the initrd 
image)
I've tested this on recent hardware and it worked like a charm.

Thoses RPMS are for testing purpose


RPMS: http://olivier.lahaye1.free.fr/RPMS/noarch
SRPMS: 
http://olivier.lahaye1.free.fr/SRPMS/systemimager-4.2.0-0.91svn4568.el6.src.rpm


PS: Keep in mind that you need postinstall scripts (already posted here) 
to setup grub, network and other stuffs as systemconfiguratior is unable 
to handle latest linux technologies.

Best regards,

Olivier 
-- 
 Olivier LAHAYE
 CEA DRT/LIST/DCSI/DIR
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
sisuite-devel mailing list
sis...@li...
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Re: [Sisuite-devel] SystemImager on Ubuntu 12.04 x86_64

[Brian E. F. <br...@th...>]

Thanks, Geoffroy!

-Brian



On Mon, Dec 17, 2012 at 7:41 AM, <geo...@fr...> wrote:

> Hi all,
>
> I did a "port" of SystemImager to Ubuntu 12.04 x86_64 since i was facing
> quite a few challenges with the latest unstable tag. This port is based on
> the 4.1.6 unstable tag (that version was selected for different reasons
> that i cannot explain here) and is based on a 3.2 kernel.
>
> I tested it in the context of OSCAR (http://oscar.openclustergroup.org/)
> and successfully deployed a cluster. However, i will not claim that my
> modifications are all clean, i took a few short-cuts; nothing was difficult
> in that port but it was time consuming and my time available for that port
> was very limited. Anyway the code is on bitbucket, feel free to clone:
>
> https://bitbucket.org/gvallee/systemimager-4.1.6-ubuntuprecise
>
> The Debian packages are here:
>
> deb http://bison.csm.ornl.gov/repos/unstable/debian-6-x86_64/ squeeze /
>
> (even if the URL says Debian 6, the Debian packages were actually created
> on and for Ubuntu 12.04).
>
> Regards,
>
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> sisuite-devel mailing list
> sis...@li...
> https://lists.sourceforge.net/lists/listinfo/sisuite-devel
>



-- 
Brian Elliott Finley
Mobile: 469.444.0167

[Sisuite-devel] RE : RE : New systemimager rpms for centos6 with ext4 support

[LAHAYE O. <oli...@ce...>]

Jing,

You're perfectly right, the ext4 problem was related to default initrd. The build did not enable the ext4 module. It's fixed in last build.

Cheers,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR
________________________________
De : Jing CDL Sun [sj...@cn...]
Date d'envoi : mardi 18 décembre 2012 06:35
À : LAHAYE Olivier
Cc: sis...@li...; sis...@li...
Objet : RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support

Thx for the reply.

When I used your build with 4.2.0-0.9svn4568, I did not run into this problem, so I'm thinking maybe this is not a missing module problem?

When you said 4.2.0-0.91svn4568 fixed the ext4 missing problem, did you mean the default initrd? because it seems  4.2.0-0.9svn4568 worked fine for me without the ext4 issue.

Yes, I did not use the systemimager default kernel and initrd, instead, I'm using my own kernel/initrd got from my golder client, it's rhel6.3, so I think it should work fine, right?






LAHAYE Olivier <oli...@ce...>

2012/12/17 17:16


To
        Jing CDL Sun/China/IBM@IBMCN,
cc
        "sis...@li..." <sis...@li...>, "sis...@li..." <sis...@li...>
Subject
        RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support








This means that your disk is not recognized.

Did you use my install scripts (especially the pre-install).
http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2

It modprobs some modules in order to see disks. I don't know my the systemimager initrd fails to automaticaly do that (did not have time to look at the problem).

if you did use the script, it means that you need to modify it to have more modules inserted. Or, if your hardware is too recent (not supported by provided  default kernel), then you'll need to use your own kernel for the moment.

I cannot upgrade easily the kernel to 3.X as it'll require to upgrade some utils too and therefore, it'll break build on RHEL6 as well. Indeed, the build will copy missing stuffs from /lib /lib64 and other places and thoses version are for a 2.6.x kernel, not a 3.X kernel.
This is also the reason why build fails on CentOS5 cas the libs copied from system misses some symbols (too old).

In order to safely upgrade systemimager to latest kernel, we need to modifiy the build process so it builds everything and link everything with it's material which is not fully the case for now. (it still copy stuffs from the build system root tree (convenient ugly dirty hack)).

Hope this helps,

Cheers,

Olivier.


--
  Olivier LAHAYE
  CEA DRT/LIST/DCSI/DIR
________________________________

De : Jing CDL Sun [sj...@cn...]
Date d'envoi : lundi 17 décembre 2012 07:42
À : LAHAYE Olivier
Cc: sis...@li...; sis...@li...
Objet : Re: [Sisuite-devel] New systemimager rpms for centos6 with ext4 support

Hi,

I just tested these new rpms, but found the issues below, the install broken.

Dec 17 14:42:36 x3550m4n02 logger: logger: parted -s -- /dev/sda mklabel gpt || shellout
Dec 17 14:42:36 x3550m4n02 kernel:  sda: unknown partition table


Thx.
Jing


LAHAYE Olivier <oli...@ce...>
2012/12/13 22:47
To
        "sis...@li..." <sis...@li...>,
cc
        "sis...@li..." <sis...@li...>
Subject
        [Sisuite-devel] New systemimager rpms for centos6 with ext4 support










Dear all,

Here are my fixed systemimager rpms for centos-6.3
Now, the ext4 filesystem is fixed (the module was missing in the initrd image)
I've tested this on recent hardware and it worked like a charm.

Thoses RPMS are for testing purpose


RPMS: http://olivier.lahaye1.free.fr/RPMS/noarch
SRPMS: http://olivier.lahaye1.free.fr/SRPMS/systemimager-4.2.0-0.91svn4568.el6.src.rpm

PS: Keep in mind that you need postinstall scripts (already posted here) to setup grub, network and other stuffs as systemconfiguratior is unable to handle latest linux technologies.

Best regards,

Olivier
--
 Olivier LAHAYE
 CEA DRT/LIST/DCSI/DIR------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d_______________________________________________
sisuite-devel mailing list
sis...@li...
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

[Sisuite-devel] RE : New systemimager rpms for centos6 with ext4 support

[Jing C. S. <sj...@cn...>]

Thx for the reply.

When I used your build with 4.2.0-0.9svn4568, I did not run into this 
problem, so I'm thinking maybe this is not a missing module problem? 

When you said 4.2.0-0.91svn4568 fixed the ext4 missing problem, did you 
mean the default initrd? because it seems  4.2.0-0.9svn4568 worked fine 
for me without the ext4 issue.

Yes, I did not use the systemimager default kernel and initrd, instead, 
I'm using my own kernel/initrd got from my golder client, it's rhel6.3, so 
I think it should work fine, right?







LAHAYE Olivier <oli...@ce...> 
2012/12/17 17:16

To
Jing CDL Sun/China/IBM@IBMCN, 
cc
"sis...@li..." 
<sis...@li...>, 
"sis...@li..." 
<sis...@li...>
Subject
RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support







This means that your disk is not recognized.

Did you use my install scripts (especially the pre-install).
http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2

It modprobs some modules in order to see disks. I don't know my the 
systemimager initrd fails to automaticaly do that (did not have time to 
look at the problem).

if you did use the script, it means that you need to modify it to have 
more modules inserted. Or, if your hardware is too recent (not supported 
by provided  default kernel), then you'll need to use your own kernel for 
the moment.

I cannot upgrade easily the kernel to 3.X as it'll require to upgrade some 
utils too and therefore, it'll break build on RHEL6 as well. Indeed, the 
build will copy missing stuffs from /lib /lib64 and other places and 
thoses version are for a 2.6.x kernel, not a 3.X kernel.
This is also the reason why build fails on CentOS5 cas the libs copied 
from system misses some symbols (too old).

In order to safely upgrade systemimager to latest kernel, we need to 
modifiy the build process so it builds everything and link everything with 
it's material which is not fully the case for now. (it still copy stuffs 
from the build system root tree (convenient ugly dirty hack)).

Hope this helps,

Cheers,

Olivier.


-- 
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

De : Jing CDL Sun [sj...@cn...]
Date d'envoi : lundi 17 décembre 2012 07:42
À : LAHAYE Olivier
Cc: sis...@li...; 
sis...@li...
Objet : Re: [Sisuite-devel] New systemimager rpms for centos6 with ext4 
support

Hi, 

I just tested these new rpms, but found the issues below, the install 
broken. 

Dec 17 14:42:36 x3550m4n02 logger: logger: parted -s -- /dev/sda mklabel 
gpt || shellout 
Dec 17 14:42:36 x3550m4n02 kernel:  sda: unknown partition table 


Thx. 
Jing



LAHAYE Olivier <oli...@ce...> 
2012/12/13 22:47 


To
"sis...@li..." 
<sis...@li...>, 
cc
"sis...@li..." 
<sis...@li...> 
Subject
[Sisuite-devel] New systemimager rpms for centos6 with ext4 support









Dear all,

Here are my fixed systemimager rpms for centos-6.3
Now, the ext4 filesystem is fixed (the module was missing in the initrd 
image)
I've tested this on recent hardware and it worked like a charm.

Thoses RPMS are for testing purpose


RPMS: http://olivier.lahaye1.free.fr/RPMS/noarch
SRPMS: 
http://olivier.lahaye1.free.fr/SRPMS/systemimager-4.2.0-0.91svn4568.el6.src.rpm


PS: Keep in mind that you need postinstall scripts (already posted here) 
to setup grub, network and other stuffs as systemconfiguratior is unable 
to handle latest linux technologies.

Best regards,

Olivier 
-- 
  Olivier LAHAYE
  CEA DRT/LIST/DCSI/DIR
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
sisuite-devel mailing list
sis...@li...
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

[Sisuite-devel] SystemImager on Ubuntu 12.04 x86_64

[<geo...@fr...>]

Hi all,

I did a "port" of SystemImager to Ubuntu 12.04 x86_64 since i was facing quite a few challenges with the latest unstable tag. This port is based on the 4.1.6 unstable tag (that version was selected for different reasons that i cannot explain here) and is based on a 3.2 kernel.

I tested it in the context of OSCAR (http://oscar.openclustergroup.org/) and successfully deployed a cluster. However, i will not claim that my modifications are all clean, i took a few short-cuts; nothing was difficult in that port but it was time consuming and my time available for that port was very limited. Anyway the code is on bitbucket, feel free to clone:

https://bitbucket.org/gvallee/systemimager-4.1.6-ubuntuprecise

The Debian packages are here:

deb http://bison.csm.ornl.gov/repos/unstable/debian-6-x86_64/ squeeze /

(even if the URL says Debian 6, the Debian packages were actually created on and for Ubuntu 12.04).

Regards,

[Sisuite-devel] RE : New systemimager rpms for centos6 with ext4 support

[LAHAYE O. <oli...@ce...>]

This means that your disk is not recognized.

Did you use my install scripts (especially the pre-install).
http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2

It modprobs some modules in order to see disks. I don't know my the systemimager initrd fails to automaticaly do that (did not have time to look at the problem).

if you did use the script, it means that you need to modify it to have more modules inserted. Or, if your hardware is too recent (not supported by provided  default kernel), then you'll need to use your own kernel for the moment.

I cannot upgrade easily the kernel to 3.X as it'll require to upgrade some utils too and therefore, it'll break build on RHEL6 as well. Indeed, the build will copy missing stuffs from /lib /lib64 and other places and thoses version are for a 2.6.x kernel, not a 3.X kernel.
This is also the reason why build fails on CentOS5 cas the libs copied from system misses some symbols (too old).

In order to safely upgrade systemimager to latest kernel, we need to modifiy the build process so it builds everything and link everything with it's material which is not fully the case for now. (it still copy stuffs from the build system root tree (convenient ugly dirty hack)).

Hope this helps,

Cheers,

Olivier.


--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR
________________________________
De : Jing CDL Sun [sj...@cn...]
Date d'envoi : lundi 17 décembre 2012 07:42
À : LAHAYE Olivier
Cc: sis...@li...; sis...@li...
Objet : Re: [Sisuite-devel] New systemimager rpms for centos6 with ext4 support

Hi,

I just tested these new rpms, but found the issues below, the install broken.

Dec 17 14:42:36 x3550m4n02 logger: logger: parted -s -- /dev/sda mklabel gpt || shellout
Dec 17 14:42:36 x3550m4n02 kernel:  sda: unknown partition table


Thx.
Jing



LAHAYE Olivier <oli...@ce...>

2012/12/13 22:47


To
        "sis...@li..." <sis...@li...>,
cc
        "sis...@li..." <sis...@li...>
Subject
        [Sisuite-devel] New systemimager rpms for centos6 with ext4 support








Dear all,

Here are my fixed systemimager rpms for centos-6.3
Now, the ext4 filesystem is fixed (the module was missing in the initrd image)
I've tested this on recent hardware and it worked like a charm.

Thoses RPMS are for testing purpose


RPMS: http://olivier.lahaye1.free.fr/RPMS/noarch
SRPMS: http://olivier.lahaye1.free.fr/SRPMS/systemimager-4.2.0-0.91svn4568.el6.src.rpm

PS: Keep in mind that you need postinstall scripts (already posted here) to setup grub, network and other stuffs as systemconfiguratior is unable to handle latest linux technologies.

Best regards,

Olivier
--
  Olivier LAHAYE
  CEA DRT/LIST/DCSI/DIR------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d_______________________________________________
sisuite-devel mailing list
sis...@li...
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Re: [Sisuite-devel] New systemimager rpms for centos6 with ext4 support

[Jing C. S. <sj...@cn...>]

Hi,

I just tested these new rpms, but found the issues below, the install 
broken.

Dec 17 14:42:36 x3550m4n02 logger: logger: parted -s -- /dev/sda mklabel 
gpt || shellout
Dec 17 14:42:36 x3550m4n02 kernel:  sda: unknown partition table


Thx.
Jing




LAHAYE Olivier <oli...@ce...> 
2012/12/13 22:47

To
"sis...@li..." 
<sis...@li...>, 
cc
"sis...@li..." 
<sis...@li...>
Subject
[Sisuite-devel] New systemimager rpms for centos6 with ext4 support







Dear all,

Here are my fixed systemimager rpms for centos-6.3
Now, the ext4 filesystem is fixed (the module was missing in the initrd 
image)
I've tested this on recent hardware and it worked like a charm.

Thoses RPMS are for testing purpose


RPMS: http://olivier.lahaye1.free.fr/RPMS/noarch
SRPMS: 
http://olivier.lahaye1.free.fr/SRPMS/systemimager-4.2.0-0.91svn4568.el6.src.rpm


PS: Keep in mind that you need postinstall scripts (already posted here) 
to setup grub, network and other stuffs as systemconfiguratior is unable 
to handle latest linux technologies.

Best regards,

Olivier
-- 
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
sisuite-devel mailing list
sis...@li...
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

[Sisuite-devel] New systemimager rpms for centos6 with ext4 support

[LAHAYE O. <oli...@ce...>]

Dear all,

Here are my fixed systemimager rpms for centos-6.3
Now, the ext4 filesystem is fixed (the module was missing in the initrd image)
I've tested this on recent hardware and it worked like a charm.

Thoses RPMS are for testing purpose


RPMS: http://olivier.lahaye1.free.fr/RPMS/noarch
SRPMS: http://olivier.lahaye1.free.fr/SRPMS/systemimager-4.2.0-0.91svn4568.el6.src.rpm

PS: Keep in mind that you need postinstall scripts (already posted here) to setup grub, network and other stuffs as systemconfiguratior is unable to handle latest linux technologies.

Best regards,

Olivier
--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

[Sisuite-devel] [ systemconfig-Bugs-3496031 ] Grub2 support

[SourceForge.net <no...@so...>]

Bugs item #3496031, was opened at 2012-03-01 09:03
Message generated for change (Tracker Item Submitted) made by damianmontaldo
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=380273&aid=3496031&group_id=24006

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Boot Loaders
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Damian Montaldo (damianmontaldo)
Assigned to: Nobody/Anonymous (nobody)
Summary: Grub2 support

Initial Comment:
Boot/Grub.pm doesn't work well with grub2, it uses old options to build the config file boot loader.
For example lines 465 set the timeout in the old grub way.

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=380273&aid=3496031&group_id=24006

[Sisuite-devel] systemconfigurator fails only in chroot environment

[Simone T. <sim...@e4...>]

Image deployment fails during system configurator check (sytemconfigurator -version, as in master script).
I've noticed that systemconfigurator works fine during  si_prepareclient but fails while in chroot environment, do you have any suggestion?

---------
linux-igri:~ # /var/lib/systemimager/images/opensuse_080911_2/usr/bin/systemconfigurator --version
systemconfigurator - 2.2.12.svn716arighi
Written by Sean Dague, Donghwa John Kim, et al.

Copyright (C) 2001-2002 International Business Machines
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

---------

linux-igri:~ # chroot /var/lib/systemimager/images/opensuse_080911_2
linux-igri:/> ./usr/bin/systemconfigurator --version
BOOTDEV /dev/sda under [BOOT] does not exist, please check your systemconfigurator config

--------

linux-igri:/> cat /etc/systemconfig/systemconfig.conf
[BOOT]
ROOTDEV = /dev/sda1
BOOTDEV = /dev/sda
DEFAULTBOOT = systemimager

[KERNEL0]
LABEL = systemimager
PATH = /boot/vmlinuz-2.6.34-12-desktop
INITRD = /boot/initrd-2.6.34-12-desktop
APPEND = root=/dev/sda1 resume=/dev/sda2 splash=silent quiet

--------
OS: openSUSE 11.3  K
Kernel 2.6.34-12-desktop  x86_64 x86_64 x86_64 GNU/Linux
Systemconfigurator: tested both systemconfigurator-2.2.11-1.noarch.rpm and systemconfigurator-2.2.12.svn716arighi-1.noarch.rpm

Many thanks for any support you could provide,
Simone