You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
(9) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(10) |
Feb
(2) |
Mar
(3) |
Apr
(2) |
May
(3) |
Jun
(50) |
Jul
(41) |
Aug
(76) |
Sep
(125) |
Oct
(83) |
Nov
(89) |
Dec
(32) |
2004 |
Jan
(78) |
Feb
(82) |
Mar
(129) |
Apr
(72) |
May
(110) |
Jun
(70) |
Jul
(76) |
Aug
(64) |
Sep
(41) |
Oct
(51) |
Nov
(36) |
Dec
(34) |
2005 |
Jan
(77) |
Feb
(57) |
Mar
(38) |
Apr
(26) |
May
(55) |
Jun
(68) |
Jul
(99) |
Aug
(80) |
Sep
(82) |
Oct
(141) |
Nov
(137) |
Dec
(51) |
2006 |
Jan
(133) |
Feb
(33) |
Mar
(156) |
Apr
(104) |
May
(88) |
Jun
(128) |
Jul
(110) |
Aug
(129) |
Sep
(74) |
Oct
(144) |
Nov
(127) |
Dec
(51) |
2007 |
Jan
(140) |
Feb
(140) |
Mar
(100) |
Apr
(42) |
May
(34) |
Jun
(13) |
Jul
(46) |
Aug
(46) |
Sep
(46) |
Oct
(42) |
Nov
(125) |
Dec
(23) |
2008 |
Jan
(15) |
Feb
(77) |
Mar
(57) |
Apr
(68) |
May
(48) |
Jun
(22) |
Jul
(54) |
Aug
(83) |
Sep
(41) |
Oct
(8) |
Nov
(37) |
Dec
(47) |
2009 |
Jan
(13) |
Feb
(11) |
Mar
(14) |
Apr
(55) |
May
(31) |
Jun
(18) |
Jul
(27) |
Aug
(17) |
Sep
(13) |
Oct
(39) |
Nov
(21) |
Dec
(16) |
2010 |
Jan
(10) |
Feb
(5) |
Mar
(15) |
Apr
(4) |
May
(9) |
Jun
(7) |
Jul
(20) |
Aug
(35) |
Sep
(37) |
Oct
(6) |
Nov
(12) |
Dec
(7) |
2011 |
Jan
(9) |
Feb
(6) |
Mar
(9) |
Apr
(78) |
May
(13) |
Jun
(6) |
Jul
(29) |
Aug
(1) |
Sep
|
Oct
(3) |
Nov
(5) |
Dec
(12) |
2012 |
Jan
(1) |
Feb
(24) |
Mar
(12) |
Apr
(7) |
May
(12) |
Jun
(19) |
Jul
(8) |
Aug
(2) |
Sep
|
Oct
|
Nov
(35) |
Dec
(30) |
2013 |
Jan
(11) |
Feb
(13) |
Mar
(15) |
Apr
(18) |
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(2) |
2014 |
Jan
(23) |
Feb
(4) |
Mar
(11) |
Apr
(1) |
May
|
Jun
(1) |
Jul
(6) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
(6) |
Feb
|
Mar
|
Apr
(1) |
May
(5) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
(6) |
May
(2) |
Jun
(7) |
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
(3) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(2) |
Dec
|
2019 |
Jan
|
Feb
|
Mar
(6) |
Apr
(1) |
May
(1) |
Jun
|
Jul
(4) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(7) |
Nov
(6) |
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: LAHAYE O. <oli...@ce...> - 2017-05-02 16:15:29
|
Hi, I've just uploaded a new release that now hopefully works fine at least for CentOS-6, CentOS-7 and Fedora-25. See previous messages to see how to use it. Available here: http://svn.oscar.openclustergroup.org/repos/unstable/ <http://svn.oscar.openclustergroup.org/pkgs/downloads/systemimager-4.5.0.tar.bz2> Source: ttp://svn.oscar.openclustergroup.org/pkgs/downloads/systemimager-4.5.0.tar.bz2<http://svn.oscar.openclustergroup.org/pkgs/downloads/systemimager-4.5.0.tar.bz2> Screenshot: http://svn.oscar.openclustergroup.org/pkgs/downloads/SIS_CO6.png Note: 1/ You must regenerate your install scripts E.g.: /usr/sbin/si_mkautoinstallscript -quiet --autodetect-disks -image oscarimage_sda -force -ip-assignment static -post-install shell (post install can be shell, reboot, poweroff, ...) (shell drops a debug shell at the end so you can check what was done) 2/ This is NOT for production environment, but so far it works well for rsync method. Note: - deployment using ssh will not work - deployment using bittorent is not tested and and I would be surprised if it works. (please report success or failure if you can test) TODO: - Include ssh binary - detect build environment and only include server ssh keys if ran outside rpmbuild environment - include sshd binary so access is possible during imaging. - more tests - tests on real hardware - test monitor console - update doc: add cmdline systemimager dracut module variables to doc - update doc: remove obsolete stuffs -- Olivier LAHAYE CEA DRT/LIST/DIR |
From: LAHAYE O. <oli...@ce...> - 2017-04-27 17:05:45
|
Hi, I've juste release the 4.5.0-20170427git release. It features: - Support for grub / grub2 bootloader installation (no more post install script needed). => It is installed before scripts are run. in case it's not working, a post install script can fix the problem. - beep should work better (nos pcspkr driver is loaded and beep is sent to /dev/console). - more console output glitches cleanup - It tries to relabel files with correct selinux policy if selinux is started. If not, it touch /.autorelabel in order to make sure that after next boot, the system whill have correct labels. This can be disabled by setting rd.sis.selinux-relabel=0 in the PXE initrd.img cmdline More cmdline parameters are supported: See /usr/share/dracut/modules.d/39systemimager/parse-sis-options-old.sh (on old dracut sustems like CentOS-6) or See /lib/dracut/modules.d/39systemimager/parse-sis-options.sh (on newer dracut systems like CentOS-7) Howto test easily with a qemu vm: put 00:16:76:43:8b:0e in your dhcp and make sure your pxe is ok. update your image script (make a backup of the old one before) example: /usr/sbin/si_mkautoinstallscript -quiet --autodetect-disks -image oscarimage_sda -force -ip-assignment static -post-install shell Then run the vm: /usr/bin/qemu-system-x86_64 -machine accel=kvm -m 1024 -no-fd-bootchk -hda "/patch/to/a/10GB_disk.vmdk" -net nic,vlan=0,macaddr=00:16:76:43:8b:0e,model=rtl8139 -net user,vlan=0,hostname=new-node -rtc base=localtime -name "Linux x86_64" -kernel /usr/share/systemimager/boot/x86_64/standard/kernel -initrd /usr/share/systemimager/boot/x86_64/standard/initrd.img -append "rdshell SKIP_LOCAL_CFG=y MONITOR_SERVER=<ip_of_your_monitor_server> MONITOR_CONSOLE=yes IMAGESERVER=<ip_of_your_image_server> ramdisk_blocksize=1024 ramdisk_size=128000 ip=dhcp ksdevice=bootif acpi=no noapic rd.neednet=1" Happy testing. -- Olivier LAHAYE CEA DRT/LIST/DIR |
From: LAHAYE O. <oli...@ce...> - 2017-04-25 16:12:53
|
Sorry, Correct screenshot: http://svn.oscar.openclustergroup.org/pkgs/downloads/SIS_CO6.png (showing a CentOS-7 image being deployed from a CentOS-6 sis_initrd.img Also forgot to tel again that grub post install scripts are mandatory: They are available here: http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_postinstall/ I'm trying to find a way to have systemimager to create and install the default OS boot loader and remove the need for those scripts (it's not as easy as it sounds). latest testing release is "4.5.0-0.20170424git" It is only available for CentOS-6, CentOS-7 and Fedora-25 for now. DEB world will be addressed later. NOTE: It should be able to image all kind of linux image anyway. Happy testing. -- Olivier LAHAYE CEA DRT/LIST/DIR ________________________________ De : LAHAYE Olivier Envoyé : lundi 24 avril 2017 19:38 À : sis...@li...; sis...@li... Objet : [PROVENANCE INTERNET] [sisuite-users] New beta release (screenshot available!) Hi, Here is a brand new release (20170424git) with fancy new features and that works far better. - Progress bar - colors - Far better error detections and handling Soon available here: http://svn.oscar.openclustergroup.org/repos/unstable/ Source tarball: http://svn.oscar.openclustergroup.org/pkgs/downloads/systemimager-4.5.0.tar.bz2 (you can build package for your rpm based distro using rpmbuild -tb systemimager.tar.bz2) And now a cool screeshot: http://svn.oscar.openclustergroup.org/pkgs/downloads/SIS_CO7.png IMPORTANT NOTICE: 1/ You must regenerate your install scripts E.g.: /usr/sbin/si_mkautoinstallscript -quiet --autodetect-disks -image oscarimage_sda -force -ip-assignment static -post-install shell (post install can be shell, reboot, poweroff, ...) (shell drops a debug shell at the end so you can check what was done) 2/ This is NOT for production environment. -- Olivier LAHAYE CEA DRT/LIST/DIR |
From: LAHAYE O. <oli...@ce...> - 2017-04-24 17:38:34
|
Hi, Here is a brand new release (20170424git) with fancy new features and that works far better. - Progress bar - colors - Far better error detections and handling Soon available here: http://svn.oscar.openclustergroup.org/repos/unstable/ Source tarball: http://svn.oscar.openclustergroup.org/pkgs/downloads/systemimager-4.5.0.tar.bz2 (you can build package for your rpm based distro using rpmbuild -tb systemimager.tar.bz2) And now a cool screeshot: http://svn.oscar.openclustergroup.org/pkgs/downloads/SIS_CO7.png IMPORTANT NOTICE: 1/ You must regenerate your install scripts E.g.: /usr/sbin/si_mkautoinstallscript -quiet --autodetect-disks -image oscarimage_sda -force -ip-assignment static -post-install shell (post install can be shell, reboot, poweroff, ...) (shell drops a debug shell at the end so you can check what was done) 2/ This is NOT for production environment. -- Olivier LAHAYE CEA DRT/LIST/DIR |
From: David L. <Dav...@cn...> - 2017-04-12 18:13:26
|
Olivier - Thanks. Up to this point we are still using RHEL6 which as you know we have working from previous releases. When I attempt the new packages I will let all know. Thanks again David -----Original Message----- From: LAHAYE Olivier [mailto:oli...@ce...] Sent: Wednesday, April 12, 2017 10:50 AM To: sis...@li...; sis...@li... Subject: Re: [sisuite-users] Systemimager NG: Working alpha David L, I reply in the list as this mail contains usefull information for every testers. Cool to here that systemimager is of any interest after such a long time without a working solution on modern distros. Be very carefull as I had difficulties to make RHEL-6 working until the imaging script works (dracut is v004 (we are at v044)) I'm using qemu and centos-6 fails to have a working network on my descktop, so I can't tell if it really works on this release of CentOS. - I end up to getting an IP (works) - Then I fail pingtests (normal on qemu with -net user (only the gateway is pingable and it works) - Then I try to rsync /scripts and it fails with no route to host (while there is a default route that itis correct and a correct IP and I can ping the gateway). Possible problem could be: lack of qemu support in rhel6 kernel Or it can also be a problem in systemimager that forgot to install a low level binary in the initrd and that ends up with a out of subject missleading error message. I hadn't yet the possibility to test on real hardware. but I'll do that soon. Also you must regenerate your imaging scripts as the structure has changed. The good news is that now, the header of the script reports the command line used to generate it. Also you must add the provided post installs scripts (grub setup and network setup). A bad trick could be to use the 86boot package from either rhel-7 or fedora. Those packages only contain matching kernel+initrd and it's a noarch package so even if it's ugly, I think it can work. (of course si_mkbootpackage will remain rhel-6 and generate rhel-6 based initrd, but if you're stuck it could be a viable alternative to use kernel+initrd from fc-25 boot package si_monitortk is able to report the imaging progress, but as I'm using NAT on my VMs I was unable to test if the remote console is working. I forgot to tell that IMAGING_SERVER can be specified on the kernel-cmdline For all possible parameters, have look here: https://github.com/finley/SystemImager/blob/initrd-from-imageserver-and-dont-package-initrd/lib/dracut/modules.d/39systemimager/parse-sis-options.sh (on rhel6, it's parse-sis-options-old.sh) You can also use most dracut.cmdline parameters (man dracut.cmdline) Cheers, Olivier. PS: Tis message should only be on the devel list, but as there is no working solution nowadays, it's good t know for non developpers that in case they really need a systemimager solution, this alpha release could help. >From now, I'll only post on devel for all messages relative to systemimager devel. -- Olivier LAHAYE CEA ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ sisuite-users mailing list sis...@li... https://lists.sourceforge.net/lists/listinfo/sisuite-users |
From: LAHAYE O. <oli...@ce...> - 2017-04-12 16:50:34
|
David L, I reply in the list as this mail contains usefull information for every testers. Cool to here that systemimager is of any interest after such a long time without a working solution on modern distros. Be very carefull as I had difficulties to make RHEL-6 working until the imaging script works (dracut is v004 (we are at v044)) I'm using qemu and centos-6 fails to have a working network on my descktop, so I can't tell if it really works on this release of CentOS. - I end up to getting an IP (works) - Then I fail pingtests (normal on qemu with -net user (only the gateway is pingable and it works) - Then I try to rsync /scripts and it fails with no route to host (while there is a default route that itis correct and a correct IP and I can ping the gateway). Possible problem could be: lack of qemu support in rhel6 kernel Or it can also be a problem in systemimager that forgot to install a low level binary in the initrd and that ends up with a out of subject missleading error message. I hadn't yet the possibility to test on real hardware. but I'll do that soon. Also you must regenerate your imaging scripts as the structure has changed. The good news is that now, the header of the script reports the command line used to generate it. Also you must add the provided post installs scripts (grub setup and network setup). A bad trick could be to use the 86boot package from either rhel-7 or fedora. Those packages only contain matching kernel+initrd and it's a noarch package so even if it's ugly, I think it can work. (of course si_mkbootpackage will remain rhel-6 and generate rhel-6 based initrd, but if you're stuck it could be a viable alternative to use kernel+initrd from fc-25 boot package si_monitortk is able to report the imaging progress, but as I'm using NAT on my VMs I was unable to test if the remote console is working. I forgot to tell that IMAGING_SERVER can be specified on the kernel-cmdline For all possible parameters, have look here: https://github.com/finley/SystemImager/blob/initrd-from-imageserver-and-dont-package-initrd/lib/dracut/modules.d/39systemimager/parse-sis-options.sh (on rhel6, it's parse-sis-options-old.sh) You can also use most dracut.cmdline parameters (man dracut.cmdline) Cheers, Olivier. PS: Tis message should only be on the devel list, but as there is no working solution nowadays, it's good t know for non developpers that in case they really need a systemimager solution, this alpha release could help. >From now, I'll only post on devel for all messages relative to systemimager devel. -- Olivier LAHAYE CEA |
From: LAHAYE O. <oli...@ce...> - 2017-04-12 09:08:12
|
Hi systemimager users and contributors, The long awaited systemimager that works on modern distros is almost there (as unstable alpha version for now). It works so far on CentOS-7 and Fedora-25. CentOS-6 should also work (not yet tested but its old dracut component is taken into account) rpms for RHEL-6, RHEL-7, FC-25 and source tarball are available on OSCAR Cluster repositories (see below) I don't forget deb world, but no time for that now. 1st I need to polish the new dracut based architecture. Then I'll focus on deb world trying to deal with dracut conflict with initramfs-tools on most deb distros. repos: http://svn.oscar.openclustergroup.org/repos/unstable/ src: http://svn.oscar.openclustergroup.org/pkgs/downloads/systemimager-4.5.0.tar.bz2 git: https://github.com/finley/SystemImager/tree/initrd-from-imageserver-and-dont-package-initrd post install scripts: http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_postinstall/ Please not that this is really EXPERIMENTAL. As such, do not use in real world except if you know what you're doing. Note that you must regenerate your install scripts using si_mkautoinstallscript. This command now accpets "shell" as --post-install so you can get a shell even if install is successfull. usefull for debugging post install scripts. si_mkbootpackage accepts an new parameter: --dracut-opts="" For example, it is usefull when using it with qemu: sudo si_mkbootpackage --dracut-opts="--add qemu --add qemu-net" --destination=/tmp Or if you want a specific keyboard. sudo si_mkbootpackage --dracut-opts="--kernel-cmdline 'rd.vconsole.keymap=fr'" --destination=/tmp (man dracut.cmdline to see all paramaters that can be added that way) Some options may conflict with si_mkbootpackage. Note: si_mkbootpackage fails to compute initrd.img memory requirements. this is harmless; the generated bootpackage is working. Also note that network and bootloader are no longer setup by systemconfigurator which is obsolete and doesn't know how to handle network manager or systemd-networkd. The above post-install-scripts with small tweeking should do the trick. Happy testing. Olivier. -- Olivier LAHAYE CEA DRT/LIST/DIR |
From: Bob <bob...@gm...> - 2015-05-22 06:42:56
|
Hello list, I have seen though SI is officially dead, people are still using it and recommend. Indeed a remarkable Oopen Source Software. I have tried SI on debian stable, after fixing kernel mismatch issue and I am amazed to see this S/W can still restore from image-server running on debian stable, while client is purposely messed up. Unfortunately preparing USB boot stick for golden client not possible but it has a brilliant feature - PXE While checking the si_mkbootserver, it creates required pxelinux.cfg at /var/lib/tftpboot; hence modified tftp path to /var/lib/tftpboot at /etc/default/tftpd-hpa But during pxe boot the client complains not file at tftp server. /var/lib/tftpboot has ```````` pxelinux.bin pxelinux.cfg X86PC ````````` tree * X86PC `-- UNDI `-- linux-install |-- linux.0 |-- message.txt `-- pxelinux.cfg `-- default pxelinux.bin [error opening dir] pxelinux.cfg `-- default If rename pxelinux.bin to pxelinux.0 then it ask for ldlinux.c32 So put ldlinux.c32, libcom32.c32, libutil.c32, vesamenu.c32 and now through PXE boot possible though it shows "boot from local disk" and the actually boot from localdisk. while the pxelinux.cfg/default contains ``````````` DEFAULT localhost LABEL localhost LOCALBOOT 0 ```````````` really clueless now. Could anyone kindly advise please ? regards, Bob |
From: Pratip G. <pra...@ne...> - 2015-05-18 14:59:49
|
Hi, Greetings!! Currently I am facing some issue to implement systemimager. I request your kind guidance. I have installd and configured systemimager (version - 4.1.99.svn4556yaubert) on Debian 8 Jessie server. Also successfully fetch the image of golden client using *si_getimage*. Now I am unable to create bootable USB disk on systemimager server. Please find following error details which I am facing now. /dev/sde is the usb disk here. ########################################################################## root@debian:~# si_mkautoinstalldisk --device /dev/sde Creating DOS filesystem in /dev/sde... >> mkdosfs -I /dev/sde mkfs.fat 3.0.27 (2014-11-12) Using "syslinux" to make a bootable device... >> syslinux /dev/sde plain floppy: device "/proc/16658/fd/3" busy (Resource temporarily unavailable): Cannot initialize 'S:' Bad target s:/ldlinux.sys syslinux: failed to create ldlinux.sys error: syslinux /dev/sde at /usr/bin/si_mkautoinstalldisk line 233, <STDIN> line 1. ############################################################################# After failing to create USB disk, I have created a bootable *.iso* image file using *si_mkautoinstallcd *with standard flavour. When I use the .iso file (the standard one) to boot a client node, it unable to get IP address from our internal DHCP server in the same network. When I use the .iso file (the standard one) with appending all required network information to the kernel at the boot time, it assigned the IP address to eth0 but not able to ping imageserver IP or the wateway IP. I have also manually configured network properties at the /my_modules # prompt with following commands but faced same issue. 1> add DNS name server at /etc/resolv.conf 2> start lan card with ip and mask ifconfig eth0 192.168.1.100 netmask 255.255.255.0 3> add the gateway # remove the default gw , if any route del default # set default gw route add default gw 192.168.1.1 Regards, Pratip Ghosh On Fri, May 15, 2015 at 6:59 PM, Pratip Ghosh <pra...@ne...> wrote: > Hi > > Can anyone help me out on creation bootable USB disk in image server using > *si_mkautoinstalldisk*. > > I have install and configured systemimage server on Debian 8 Jessie. Also > successfully fetch the image from golden client using *si_setimage*. Now > I am unable to create bootable USB disk to boot other clients with same > hardawre configuration as golden client. > > Please find following error details which I am facing now. > > Please help me out on this. If you required I can share more details of > system information or error information which will require. > > ########################################################################## > root@debian:~# si_mkautoinstalldisk -- device /dev/sde > error: target device was not specified! > Try "--help" for more options. > root@debian:~# si_mkautoinstalldisk --device /dev/sde > ======================= WARNING ======================= > Using device: /dev/sde > This command will overwrite the data on that device!!! > ======================= WARNING ======================= > > Are you sure to continue? (y / N)? y > > Using kernel: /usr/share/systemimager/boot/x86_64/standard/kernel > Using initrd: /usr/share/systemimager/boot/x86_64/standard/initrd.img > > Creating DOS filesystem in /dev/sde... > >> mkdosfs -I /dev/sde > mkfs.fat 3.0.27 (2014-11-12) > Using "syslinux" to make a bootable device... > >> syslinux /dev/sde > plain floppy: device "/proc/16658/fd/3" busy (Resource temporarily > unavailable): > Cannot initialize 'S:' > Bad target s:/ldlinux.sys > syslinux: failed to create ldlinux.sys > error: syslinux /dev/sde at /usr/bin/si_mkautoinstalldisk line 233, > <STDIN> line 1. > > > ############################################################################# > > Thanks and Regards, > > Pratip Ghosh > |
From: Pratip G. <pra...@ne...> - 2015-05-15 14:24:29
|
Hi Can anyone help me out on creation bootable USB disk in image server using *si_mkautoinstalldisk*. I have install and configured systemimage server on Debian 8 Jessie. Also successfully fetch the image from golden client using *si_setimage*. Now I am unable to create bootable USB disk to boot other clients with same hardawre configuration as golden client. Please find following error details which I am facing now. Please help me out on this. If you required I can share more details of system information or error information which will require. ########################################################################## root@debian:~# si_mkautoinstalldisk -- device /dev/sde error: target device was not specified! Try "--help" for more options. root@debian:~# si_mkautoinstalldisk --device /dev/sde ======================= WARNING ======================= Using device: /dev/sde This command will overwrite the data on that device!!! ======================= WARNING ======================= Are you sure to continue? (y / N)? y Using kernel: /usr/share/systemimager/boot/x86_64/standard/kernel Using initrd: /usr/share/systemimager/boot/x86_64/standard/initrd.img Creating DOS filesystem in /dev/sde... >> mkdosfs -I /dev/sde mkfs.fat 3.0.27 (2014-11-12) Using "syslinux" to make a bootable device... >> syslinux /dev/sde plain floppy: device "/proc/16658/fd/3" busy (Resource temporarily unavailable): Cannot initialize 'S:' Bad target s:/ldlinux.sys syslinux: failed to create ldlinux.sys error: syslinux /dev/sde at /usr/bin/si_mkautoinstalldisk line 233, <STDIN> line 1. ############################################################################# Thanks and Regards, Pratip Ghosh |
From: Joydeep B. <joy...@ne...> - 2015-05-15 09:28:37
|
Hello there, has anyone have any success with USB bootable disk for image restoration at client end ? Kindly share. Thanks and regrds |
From: Gerasimatos, D. V (392K) <Dim...@jp...> - 2015-05-15 01:36:24
|
Hello! We have been using SystemImager/SALI for bare metal RHEL6 installs successfully. Do these tools support RHEL7? Dimitri -- Dimitrios Gerasimatos dim...@jp...<mailto:dim...@jp...> Section 392 Jet Propulsion Laboratory 4800 Oak Grove Dr. Mail Stop 264-282 Pasadena, CA 91109 Voice: 818.354.4910 FAX: 818.393.7413 Cell:818.726.8617 |
From: Greg T. <gtc...@pp...> - 2015-04-28 17:39:59
|
Hello, We are still using systemimager here at PPPL and are in the process of updating our images to CentOS6. We are running into an issue with the tmpfs running out of space with our >4GB image. Our testing currently involves a virtual machine so setting available ram is trivial, but in some of our physical machines this will be an issue. Is there any way to not use tmpfs in the deployment of these images? I expect their size will grow over time (as they did with our previous RHEL4 image). We found some on-line list breadcrumbs about setting "TMPFS_STAGING=no" but that seems to be of little value as the email threads die without resolution. Thanks in advance, Greg Tchilinguirian Princeton Plasma Physics Lab (PPPL) On Mon, Jan 26, 2015 at 6:06 AM, LAHAYE Olivier <oli...@ce...> wrote: > > Hi, > > I've finaly updated systemimager to work with host OS binaries instead of > rebuilding everything. > This means that now, the initrd template and the default initrd and kernel > are generated using dracut and I only build 3 components: cx_freeze, > udpcast and bittorrent client. All other binaries are taken from the host > OS and are thus in sync with kernel and drivers (which was not the case in > previous release were binaries expected to run with boel kernel 3.7.5 were > built on a totaly different kernel and in some circumstance were crashing > or failing to built. > > This is past. > > I've not yet pushed to git my changes, because I must do some more > testing, but the most difficult things are fixed. > things that still need to be addressed: > - buzybox rpm not available on centos7: do we build it or used standard > tools > - need to fix list of binaries that we need > - test. > > I hope to release a test rpm in less than 2 weeks, maybe this Friday if I > have tilme. > > Best regards, > > Olivier. > > -- > Olivier LAHAYE > CEA DRT/LIST/DIR > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming. The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is > your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > sisuite-users mailing list > sis...@li... > https://lists.sourceforge.net/lists/listinfo/sisuite-users > > |
From: LAHAYE O. <oli...@ce...> - 2015-01-27 10:10:16
|
So far, My rpm builds and tested ok on centos7 It has been built successfully on fedora20 but not tested. on centos6, it is facing this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1182297 This is not centos6 related and will be fixed soon. if I download the package, it builds fine. Right now, I'm polishing the build. Then I'll cross check the list of binaries that needs to be included so most common user postinstall script can run. I will also include driver firmwares so the generic image will work for most common cases. As for buzybox, I've chosen to not use it and use core utils instead. The image is bigger, but on common systems this is not an issue anymore. I made this choice because the buzybox package is not available on centos6 and maybe on other distros. This choice is very easy to revert. (either by reenabling buzybox.rul build or by using the os provided package and adding the correct dracut option. Then I'll test that non systemd based images still work (I see no reaseon why it wouldn't). Then I'll update the deb build (minor update is needed (deps and list of files to include)) Stay tuned. Cheers, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DIR ________________________________ De : David Livingstone [Dav...@cn...] Envoyé : lundi 26 janvier 2015 20:00 À : sis...@li... Objet : Re: [sisuite-users] SystemImager NG: it works :-) Olivier – Looks great ! Let me know when you have something to test – I’m still using RHEL 6. Thanks From: LAHAYE Olivier [mailto:oli...@ce...] Sent: Monday, January 26, 2015 4:06 AM To: sis...@li... Subject: [sisuite-users] SystemImager NG: it works :-) Hi, I've finaly updated systemimager to work with host OS binaries instead of rebuilding everything. This means that now, the initrd template and the default initrd and kernel are generated using dracut and I only build 3 components: cx_freeze, udpcast and bittorrent client. All other binaries are taken from the host OS and are thus in sync with kernel and drivers (which was not the case in previous release were binaries expected to run with boel kernel 3.7.5 were built on a totaly different kernel and in some circumstance were crashing or failing to built. This is past. I've not yet pushed to git my changes, because I must do some more testing, but the most difficult things are fixed. things that still need to be addressed: - buzybox rpm not available on centos7: do we build it or used standard tools - need to fix list of binaries that we need - test. I hope to release a test rpm in less than 2 weeks, maybe this Friday if I have tilme. Best regards, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DIR |
From: David L. <Dav...@cn...> - 2015-01-26 19:20:56
|
Olivier - Looks great ! Let me know when you have something to test - I'm still using RHEL 6. Thanks From: LAHAYE Olivier [mailto:oli...@ce...] Sent: Monday, January 26, 2015 4:06 AM To: sis...@li... Subject: [sisuite-users] SystemImager NG: it works :-) Hi, I've finaly updated systemimager to work with host OS binaries instead of rebuilding everything. This means that now, the initrd template and the default initrd and kernel are generated using dracut and I only build 3 components: cx_freeze, udpcast and bittorrent client. All other binaries are taken from the host OS and are thus in sync with kernel and drivers (which was not the case in previous release were binaries expected to run with boel kernel 3.7.5 were built on a totaly different kernel and in some circumstance were crashing or failing to built. This is past. I've not yet pushed to git my changes, because I must do some more testing, but the most difficult things are fixed. things that still need to be addressed: - buzybox rpm not available on centos7: do we build it or used standard tools - need to fix list of binaries that we need - test. I hope to release a test rpm in less than 2 weeks, maybe this Friday if I have tilme. Best regards, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DIR |
From: LAHAYE O. <oli...@ce...> - 2015-01-26 11:06:23
|
Hi, I've finaly updated systemimager to work with host OS binaries instead of rebuilding everything. This means that now, the initrd template and the default initrd and kernel are generated using dracut and I only build 3 components: cx_freeze, udpcast and bittorrent client. All other binaries are taken from the host OS and are thus in sync with kernel and drivers (which was not the case in previous release were binaries expected to run with boel kernel 3.7.5 were built on a totaly different kernel and in some circumstance were crashing or failing to built. This is past. I've not yet pushed to git my changes, because I must do some more testing, but the most difficult things are fixed. things that still need to be addressed: - buzybox rpm not available on centos7: do we build it or used standard tools - need to fix list of binaries that we need - test. I hope to release a test rpm in less than 2 weeks, maybe this Friday if I have tilme. Best regards, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DIR |
From: LAHAYE O. <oli...@ce...> - 2015-01-22 08:46:42
|
Hi, Thanks a lot :-) It works fine thanks :-) Now, my test systemimager builds in a matter of seconds :-) It produces a dracut image that starts booting, unfortunately, it then hangs, but I'm near a solution I think. Once I have something completely working, I'll push 4 changes: - pod2man fixes - makefiles fixes - add an udpcast patch - remove some .rul files and kernel build sinfrastructure. I won't push anything until I'm shure that it works on rpm and deb based systems so it may take some time though. Olivier. -- Olivier LAHAYE CEA DRT/LIST/DIR ________________________________ De : Brian Elliott Finley [br...@th...] Envoyé : mercredi 21 janvier 2015 15:46 À : SISuite Users List Objet : Re: [sisuite-users] NextGen Systemimager (dracut based): progress Olivier, I'll take dare is that udpcast upload today. Thanks! -Brian On Jan 21, 2015 8:19 AM, "LAHAYE Olivier" <oli...@ce...<mailto:oli...@ce...>> wrote: Hi, I've just been able to create a cracut systemd based systemimager initrd image that is able to image a node. This is a great step forward as it should work on all system that can build initrd using dracut tool. For the moment I've only tested on fedora20 build and imaged a centos7 node without any problem. The image was created by hand using dracut and systemd from the standard systemimager initrd_template. I've just added a systemimager.target, a systemimager.service that runs /etc/init.d/rcS. This is ugly but it does work fine. Now that I' have a proof of concept, I'm working on the systemimage build process to avoid building useless stuffs (only build systemimager specific stuffs and use everything else from the build host). Now I'm hitting a small issue with udpcast. I need a more recent version, because the systemimager version fails to build on recent linus distros. So if someone who can have access to systemimager download tree could update it with latest udpcast tarball, that would help me a lot. Basically I need http://www.udpcast.linux.lu/download/udpcast-20120424.tar.bz2 to be placed in http://download.systemimager.org/pub/udpcast/ There is still lot of work to do like identify what build host binaries should be copied into dracut image, but if I'm not interrupted, I should have a test version in a few weeks. This version will be somewhat ugly regarding dracut concept as it won't use a systemimager dedicated dracut module to create the image, just a giant dracut commandline, but the result should be working well. Once this phase is proven to work on most majort distros (deb+rpm), Ill try to learn how to create a systemimager dracut module so I can simplify and enhance the UYOK option. This should work on non systemd based system as well; though I haven't tested yet. -- Olivier LAHAYE CEA DRT/LIST/DIR ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ sisuite-users mailing list sis...@li...<mailto:sis...@li...> https://lists.sourceforge.net/lists/listinfo/sisuite-users |
From: Brian E. F. <br...@th...> - 2015-01-21 15:13:58
|
Olivier, I'll take dare is that udpcast upload today. Thanks! -Brian On Jan 21, 2015 8:19 AM, "LAHAYE Olivier" <oli...@ce...> wrote: > > Hi, > > I've just been able to create a cracut systemd based systemimager initrd > image that is able to image a node. > > This is a great step forward as it should work on all system that can > build initrd using dracut tool. > For the moment I've only tested on fedora20 build and imaged a centos7 > node without any problem. > > The image was created by hand using dracut and systemd from the standard > systemimager initrd_template. > I've just added a systemimager.target, a systemimager.service that runs > /etc/init.d/rcS. This is ugly but it does work fine. > > Now that I' have a proof of concept, I'm working on the systemimage build > process to avoid building useless stuffs (only build systemimager specific > stuffs and use everything else from the build host). > > Now I'm hitting a small issue with udpcast. I need a more recent version, > because the systemimager version fails to build on recent linus distros. > > So if someone who can have access to systemimager download tree could > update it with latest udpcast tarball, that would help me a lot. > Basically I need > http://www.udpcast.linux.lu/download/udpcast-20120424.tar.bz2 to be > placed in http://download.systemimager.org/pub/udpcast/ > > There is still lot of work to do like identify what build host binaries > should be copied into dracut image, but if I'm not interrupted, I should > have a test version in a few weeks. > > This version will be somewhat ugly regarding dracut concept as it won't > use a systemimager dedicated dracut module to create the image, just a > giant dracut commandline, but the result should be working well. > Once this phase is proven to work on most majort distros (deb+rpm), Ill > try to learn how to create a systemimager dracut module so I can simplify > and enhance the UYOK option. > This should work on non systemd based system as well; though I haven't > tested yet. > > -- > Olivier LAHAYE > CEA DRT/LIST/DIR > > > ------------------------------------------------------------------------------ > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > http://p.sf.net/sfu/gigenet > _______________________________________________ > sisuite-users mailing list > sis...@li... > https://lists.sourceforge.net/lists/listinfo/sisuite-users > > |
From: LAHAYE O. <oli...@ce...> - 2015-01-21 14:18:06
|
Hi, I've just been able to create a cracut systemd based systemimager initrd image that is able to image a node. This is a great step forward as it should work on all system that can build initrd using dracut tool. For the moment I've only tested on fedora20 build and imaged a centos7 node without any problem. The image was created by hand using dracut and systemd from the standard systemimager initrd_template. I've just added a systemimager.target, a systemimager.service that runs /etc/init.d/rcS. This is ugly but it does work fine. Now that I' have a proof of concept, I'm working on the systemimage build process to avoid building useless stuffs (only build systemimager specific stuffs and use everything else from the build host). Now I'm hitting a small issue with udpcast. I need a more recent version, because the systemimager version fails to build on recent linus distros. So if someone who can have access to systemimager download tree could update it with latest udpcast tarball, that would help me a lot. Basically I need http://www.udpcast.linux.lu/download/udpcast-20120424.tar.bz2 to be placed in http://download.systemimager.org/pub/udpcast/ There is still lot of work to do like identify what build host binaries should be copied into dracut image, but if I'm not interrupted, I should have a test version in a few weeks. This version will be somewhat ugly regarding dracut concept as it won't use a systemimager dedicated dracut module to create the image, just a giant dracut commandline, but the result should be working well. Once this phase is proven to work on most majort distros (deb+rpm), Ill try to learn how to create a systemimager dracut module so I can simplify and enhance the UYOK option. This should work on non systemd based system as well; though I haven't tested yet. -- Olivier LAHAYE CEA DRT/LIST/DIR |
From: <an...@co...> - 2014-07-14 14:19:21
|
Thanks, I got it to work just by installing the RPM on the master node. Since Master/Slave nodes are all the same it compiled correctly this time. Now I have one more issue I'm trying to understand. The client connects and starts building. It originally had an issue connecting with RSYNC so I added a statement to allow 192.168.3.0/255.255.255.0 to rsyncd. Well, that statement let the install script format the drives and such and then it comes up again with the access denied. Is there another location where I should put the allow 192.168.3.0/255.255.255.0? I think if I figure that out I'm done! Andy > On July 14, 2014 at 6:03 AM Pierre BLONDEAU <pie...@un...> > wrote: > > > Hi, > > Yes, it's exactly what i try to say. > > On one cloned client or on the golden client ( or master node if you > prefer ) but not image, you install the official driver. > > For exemple : > cd /usr/src/ > wget .... > unzip bnx2.zip -d bnx2 > cd bnx2/Server/Linux/Driver > tar zxvf netxtreme2-5.2.55.tar.gz > cd netxtreme2-5.2.55 > make > make install > > You add the module to the UYOK file : > echo "bnx2" >> /etc/systemimager/UYOK.modules_to_include > > And you regenerate a new initrd with the new driver: > LC_ALL=C si_prepareclient --server your.systemimager.server.com > --no-rsyncd --my-modules > > This command is for 4.0.2. If i good remember, it's little change in 4.3 . > > And you can copy file in /etc/systemimager/boot/* in your tftboot. > > Remark, it's not necessary to install the driver in "dkms" mode, because > when your clone machines restart after the installation of the image, > the kernel kernel can use the driver in "firmware mode" because your > complete system have it. > > Regards > > Le 13/07/2014 06:05, an...@co... a écrit : > > Thanks for the reply! I guess I'm not understanding what you meant. I have a > > master node (dell01) with CentOS 6.5. This is where I run SI and the UYOK > > script to generate the initrd/kernel files. Are you saying I should install > > the "official" network card driver from Broadcom on the master node, create > > the initrd/kernel and then try imaging on my slave node? > > > > Thanks again and you can send to my email if you like also > > > > Andy > > > > > > > > > > Hi, > > > > We have solve this problem by install bnx2 module from the source of > > broadcrom. The broadcom version works like others modules and not like a > > "firmware" so it's included with UYOK. > > > > Regards > > > > Le 12/07/2014 07:02, Andy a écrit : > >> Hi, > >> > >> I'm having issues with SI and using the UYOK feature. It seems to build > >> the kernel without issue but the network card can't load the firmware. > >> During the image loading on by slave node I get > >> > >> bnx2: Can't load firmware file "bnx2/bnx2-mips-06-6.2.3.fw > >> > >> Since it can't find that then in can't grab and IP and the rest fails. > >> > >> I'm using systemimager 4.3.0.17 > >> > >> When I create the initrd/kernel it seems to work. It creates the > >> /tmp/.systemimage.0 folder and copies all files needed (including the > >> firmware tree) to it. > >> > >> I run: > >> > >> si_prepareclient --server dell01 --include-system-firmware and once > >> that's complete I copy the initrd and kernel to /tftpboot as the > >> official names that are pulled up through PXE. > >> > >> > >> > >> > >> > >> ------------------------------------------------------------------------ > >> <http://www.avast.com/> <http://www.avast.com/%3E>; > >> > >> This email is free from viruses and malware because avast! Antivirus > >> <http://www.avast.com/> <http://www.avast.com/%3E>; protection is active. > >> > >> > >> > >> > >> ------------------------------------------------------------------------------ > >> > >> > >> > >> _______________________________________________ > >> sisuite-users mailing list > >> sisuite-users@... > >>https://lists.sourceforge.net/lists/listinfo/sisuite-users > >> > > > > > > -- > > > > ---------------------------------------------- > > > > > > > > ------------------------------------------------------------------------------ > > > > > > > > _______________________________________________ > > sisuite-users mailing list > > sis...@li... > > https://lists.sourceforge.net/lists/listinfo/sisuite-users > > > > > -- > ---------------------------------------------- > Pierre BLONDEAU > Administrateur Systèmes & réseaux > Université de Caen > Laboratoire GREYC, Département d'informatique > > tel : 02 31 56 75 42 > bureau : Campus 2, Science 3, 406 > ---------------------------------------------- > > ------------------------------------------------------------------------------ > Want fast and easy access to all the code in your enterprise? Index and > search up to 200,000 lines of code with a free copy of Black Duck® > Code Sight™ - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds_______________________________________________ > sisuite-users mailing list > sis...@li... > https://lists.sourceforge.net/lists/listinfo/sisuite-users |
From: Pierre B. <pie...@un...> - 2014-07-14 10:04:01
|
Hi, Yes, it's exactly what i try to say. On one cloned client or on the golden client ( or master node if you prefer ) but not image, you install the official driver. For exemple : cd /usr/src/ wget .... unzip bnx2.zip -d bnx2 cd bnx2/Server/Linux/Driver tar zxvf netxtreme2-5.2.55.tar.gz cd netxtreme2-5.2.55 make make install You add the module to the UYOK file : echo "bnx2" >> /etc/systemimager/UYOK.modules_to_include And you regenerate a new initrd with the new driver: LC_ALL=C si_prepareclient --server your.systemimager.server.com --no-rsyncd --my-modules This command is for 4.0.2. If i good remember, it's little change in 4.3 . And you can copy file in /etc/systemimager/boot/* in your tftboot. Remark, it's not necessary to install the driver in "dkms" mode, because when your clone machines restart after the installation of the image, the kernel kernel can use the driver in "firmware mode" because your complete system have it. Regards Le 13/07/2014 06:05, an...@co... a écrit : > Thanks for the reply! I guess I'm not understanding what you meant. I have a master node (dell01) with CentOS 6.5. This is where I run SI and the UYOK script to generate the initrd/kernel files. Are you saying I should install the "official" network card driver from Broadcom on the master node, create the initrd/kernel and then try imaging on my slave node? > > Thanks again and you can send to my email if you like also > > Andy > > > > > Hi, > > We have solve this problem by install bnx2 module from the source of > broadcrom. The broadcom version works like others modules and not like a > "firmware" so it's included with UYOK. > > Regards > > Le 12/07/2014 07:02, Andy a écrit : >> Hi, >> >> I'm having issues with SI and using the UYOK feature. It seems to build >> the kernel without issue but the network card can't load the firmware. >> During the image loading on by slave node I get >> >> bnx2: Can't load firmware file "bnx2/bnx2-mips-06-6.2.3.fw >> >> Since it can't find that then in can't grab and IP and the rest fails. >> >> I'm using systemimager 4.3.0.17 >> >> When I create the initrd/kernel it seems to work. It creates the >> /tmp/.systemimage.0 folder and copies all files needed (including the >> firmware tree) to it. >> >> I run: >> >> si_prepareclient --server dell01 --include-system-firmware and once >> that's complete I copy the initrd and kernel to /tftpboot as the >> official names that are pulled up through PXE. >> >> >> >> >> >> ------------------------------------------------------------------------ >> <http://www.avast.com/> <http://www.avast.com/%3E>; >> >> This email is free from viruses and malware because avast! Antivirus >> <http://www.avast.com/> <http://www.avast.com/%3E>; protection is active. >> >> >> >> >> ------------------------------------------------------------------------------ >> >> >> >> _______________________________________________ >> sisuite-users mailing list >> sisuite-users@... >>https://lists.sourceforge.net/lists/listinfo/sisuite-users >> > > > -- > > ---------------------------------------------- > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > sisuite-users mailing list > sis...@li... > https://lists.sourceforge.net/lists/listinfo/sisuite-users > -- ---------------------------------------------- Pierre BLONDEAU Administrateur Systèmes & réseaux Université de Caen Laboratoire GREYC, Département d'informatique tel : 02 31 56 75 42 bureau : Campus 2, Science 3, 406 ---------------------------------------------- |
From: <an...@co...> - 2014-07-13 04:05:21
|
Thanks for the reply! I guess I'm not understanding what you meant. I have a master node (dell01) with CentOS 6.5. This is where I run SI and the UYOK script to generate the initrd/kernel files. Are you saying I should install the "official" network card driver from Broadcom on the master node, create the initrd/kernel and then try imaging on my slave node? Thanks again and you can send to my email if you like also Andy Hi, We have solve this problem by install bnx2 module from the source of broadcrom. The broadcom version works like others modules and not like a "firmware" so it's included with UYOK. Regards Le 12/07/2014 07:02, Andy a écrit : > Hi, > > I'm having issues with SI and using the UYOK feature. It seems to build > the kernel without issue but the network card can't load the firmware. > During the image loading on by slave node I get > > bnx2: Can't load firmware file "bnx2/bnx2-mips-06-6.2.3.fw > > Since it can't find that then in can't grab and IP and the rest fails. > > I'm using systemimager 4.3.0.17 > > When I create the initrd/kernel it seems to work. It creates the > /tmp/.systemimage.0 folder and copies all files needed (including the > firmware tree) to it. > > I run: > > si_prepareclient --server dell01 --include-system-firmware and once > that's complete I copy the initrd and kernel to /tftpboot as the > official names that are pulled up through PXE. > > > > > > ------------------------------------------------------------------------ > <http://www.avast.com/> <http://www.avast.com/%3E>; > > This email is free from viruses and malware because avast! Antivirus > <http://www.avast.com/> <http://www.avast.com/%3E>; protection is active. > > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > sisuite-users mailing list > sisuite-users@... > https://lists.sourceforge.net/lists/listinfo/sisuite-users > -- ---------------------------------------------- |
From: Pierre B. <pie...@un...> - 2014-07-12 12:05:29
|
Hi, We have solve this problem by install bnx2 module from the source of broadcrom. The broadcom version works like others modules and not like a "firmware" so it's included with UYOK. Regards Le 12/07/2014 07:02, Andy a écrit : > Hi, > > I'm having issues with SI and using the UYOK feature. It seems to build > the kernel without issue but the network card can't load the firmware. > During the image loading on by slave node I get > > bnx2: Can't load firmware file "bnx2/bnx2-mips-06-6.2.3.fw > > Since it can't find that then in can't grab and IP and the rest fails. > > I'm using systemimager 4.3.0.17 > > When I create the initrd/kernel it seems to work. It creates the > /tmp/.systemimage.0 folder and copies all files needed (including the > firmware tree) to it. > > I run: > > si_prepareclient --server dell01 --include-system-firmware and once > that's complete I copy the initrd and kernel to /tftpboot as the > official names that are pulled up through PXE. > > > > > > ------------------------------------------------------------------------ > <http://www.avast.com/> > > This email is free from viruses and malware because avast! Antivirus > <http://www.avast.com/> protection is active. > > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > sisuite-users mailing list > sis...@li... > https://lists.sourceforge.net/lists/listinfo/sisuite-users > -- ---------------------------------------------- Pierre BLONDEAU Administrateur Systèmes & réseaux Université de Caen Laboratoire GREYC, Département d'informatique tel : 02 31 56 75 42 bureau : Campus 2, Science 3, 406 ---------------------------------------------- |
From: Andy <an...@co...> - 2014-07-12 05:02:21
|
Hi, I'm having issues with SI and using the UYOK feature. It seems to build the kernel without issue but the network card can't load the firmware. During the image loading on by slave node I get bnx2: Can't load firmware file "bnx2/bnx2-mips-06-6.2.3.fw Since it can't find that then in can't grab and IP and the rest fails. I'm using systemimager 4.3.0.17 When I create the initrd/kernel it seems to work. It creates the /tmp/.systemimage.0 folder and copies all files needed (including the firmware tree) to it. I run: si_prepareclient --server dell01 --include-system-firmware and once that's complete I copy the initrd and kernel to /tftpboot as the official names that are pulled up through PXE. --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com |
From: Andy <an...@co...> - 2014-07-12 04:53:21
|
--- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com |