Re: [sisuite-users] support newer kernels in systemimager?
Hi
4.1.6
Except Systemconfigurator systemconfigurator_2.2.12.svn716arighi_all.deb
Regards,
Jan
On 22 January 2014 22:59, Steven DuChene steven.a.duch...@hp.com wrote:
Jan:
Thank you for supplying this patch and information.
What version of systemimager are you using with this patch?
--
Steven DuChene
On 01/19/2014 11:38 PM, Jan Groenewald wrote:
Hi
This file
0 root@muizenberg:/usr/lib/systemimager/perl/SystemImager#dpkg -S
UseYourOwnKernel.pm
systemimager-common:
/usr/lib/systemimager/perl/SystemImager/UseYourOwnKernel.pm
Checks the kernel version and throws an error for newer kernels. This
patch allows me to use some 3.X kernels
1 root@muizenberg:/usr/lib/systemimager/perl/SystemImager#cat
UseYourOwnKernel.pm.patch
--- UseYourOwnKernel.pm.orig2012-05-30 17:05:54.899344781 +0200
+++ UseYourOwnKernel.pm 2013-02-18 08:30:56.251862480 +0200
@@ -460,11 +460,12 @@
# 2.4.19-mantis-2002.11.20 (root@mantis) #6 Tue
Nov 19 15:15:43 CST 2002
# 2.6.7-1-686 (dilin...@toaster.hq.voxel.net) #1
Thu Jul 8 05:36:53 EDT 2004
# 2.6.22.5-31-default (geeko@buildhost) #1 SMP
2007/09/21 22:29:00 UTC
+ # 3.2.0-24-generic #39-Ubuntu SMP Mon May 21
16:52:17 UTC 2012
#
my $regex =
# | kernel version + build machine
# `---
-'(2\.[46]\.\d[^\/]*?) \(.*@.*\) [#]\d+.*' .
+'((2\.[46])|(3\.[0125])\.\d[^\/]*?) \(.*@.*\)
[#]\d+.*' .
#
# | build date
# `---
@@ -739,7 +740,7 @@
# Find the right way to get modules info.
my $uname_r = get_uname_r();
my $modinfo_filename;
-if ($uname_r =~ /^2\.6/) {
+if ($uname_r =~ /(^2\.6)|(^3\.[0125])/) {
$modinfo_filename = 'modinfo -F filename';
} elsif ($uname_r =~ /^2\.4/) {
$modinfo_filename = 'modinfo -n';
It is however already out of date as Ubuntu 12.04 can run 3.2
(linux-generic) 3.5 (linux-generic-lts-quantal) 3.8
(linux-generic-lts-raring) or 3.11 (linux-generic-lts-saucy) kernels:
https://wiki.ubuntu.com/Kernel/LTSEnablementStack
The patch will fix your problem running si_prepareclient (though I can
image that I could not do the network boot on that kernel (still using an
old 2.X Ubuntu 11.04 kernel).
My images are also converted to grub1 instead of grub2, and the master
script edited to have ext3 not ext4, and a similar patch to allow the
server to upload from an ext4 golden client.
I'm looking forward to a new release of SI for Ubuntu 12.04 and 14.04
support!
Regards,
Jan
On 4 November 2013 22:02, Steven DuChene steven.a.duch...@hp.com wrote:
I am trying to capture the image of a system that is running Ubuntu
Precise 12.04LTS and when I run the si_prepareclient with the following
command line switches:
si_prepareclient --server 10.23.18.10 --my-modules
I get the following :
Use of uninitialized value $v1 in split at
/usr/lib/systemimager/perl/SystemImager/Common.pm line 199.
Use of uninitialized value $v1 in split at
/usr/lib/systemimager/perl/SystemImager/Common.pm line 199.
Use of uninitialized value $v1 in split at
/usr/lib/systemimager/perl/SystemImager/Common.pm line 199.
Use of uninitialized value $v1 in split at
/usr/lib/systemimager/perl/SystemImager/Common.pm line 199.
Use of uninitialized value $v1 in split at
/usr/lib/systemimager/perl/SystemImager/Common.pm line 199.
Use of uninitialized value $leftovers in substitution (s///) at
/usr/lib/systemimager/perl/SystemImager/Common.pm line 704.
Use of uninitialized value $leftovers in split at
/usr/lib/systemimager/perl/SystemImager/Common.pm line 707.
Use of uninitialized value $v1 in split at
/usr/lib/systemimager/perl/SystemImager/Common.pm line 199.
Use of uninitialized value $v1 in split at
/usr/lib/systemimager/perl/SystemImager/Common.pm line 199.
ERROR: unsupported kernel 3.5.0-23-generic!
The warnings or errors about Use of uninitialized value $v1 in split at
/usr/lib/systemimager/perl/SystemImager/Common.pm line 199 is due to
the way parted is now returning multiple line of text output when the
--version option is passed. It seems that the perl code that is supposed
to be parsing the stuff that is not able to handle that multi-line
output to extract the version of the parted utility.
However what concerns me most is the message back that says the
3.5.0-23-generic kernel is not supported.
Is there any documentation available for systemimager that would show
the necessary process steps to incorperate support for newer kernels?
Any suggestions about any of this would be most appreciated. BTW, I have
the following installed on the Ubuntu system
Re: [sisuite-users] support newer kernels in systemimager?
client nodes -- Steven DuChene -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] systemimager-4.3.0 beta7 for ubuntu-12-x86_64
Hi Ubuntu 12.10 not Ubuntu 10.12? A Typo? Regards, Jan On 22 March 2013 16:25, LAHAYE Olivier olivier.lah...@cea.fr wrote: Dear all, I've managed to build a beta7 release for systemiamger-4.3.0 for ubuntu 10.12 - It's not tested. - The package release is not the goot one (all instead of ubuntu0.7) - There is no repo yet, but the packages are available here for testing. You can get the packages here (only for testing purpose). http://olivier.lahaye1.free.fr/OSCAR/repos/unstable/ubuntu-12-x86_64/ As usual, you'll need postinstall scripts to setup the bootloader and the network. You can take ideas from http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2 You shouldn't need pre install script as hopefully, the hardware is now correctly detected. Best regards, -- 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-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ -- 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-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] systemimager 4.3.0-0.7 available for testing
Hi Are there any plans to release a deb or PPA for Debian or Ubuntu (specifically Ubuntu 12.04 LTS)? Regards, Jan On 20 March 2013 18:16, LAHAYE Olivier olivier.lah...@cea.fr wrote: Hi, I've uploaded the rpms for systemimager beta version V4.3.0 (beta7) I've built it for fedora-17 and centos-6.3 They are available here: http://olivier.lahaye1.free.fr/OSCAR/repos/unstable/ Note that you can install the oscar-release rpm which will setup the yum.repo.d/oscar.repo. Usage notes: - The pre install script required to modprobe disk controlers is not required anymore. (leave comments in it) - the post install scripts (si_scripts.tar.bz2http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2) are usefull for grub setup (systemconfigurator not yet ported for new grub, grub2 and other bootloaders and Network manager) Just comment everything in the pre_install script. Firmwares available in the image are those that can be built from the kernel source tree. No external firmware is provided yet (need to check EULA). Please keep in mind that this is a testing release. If you have a systemimager that is in production, don't upgrade). Happy testing. -- 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-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ -- 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-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] si-suite site down?
Hi Brian, On 9 February 2012 00:11, Brian E Finley br...@thefinleys.com wrote: As for the project, it has been pretty stable, but I would recommend taking a look st SALI, as Bas mentioned. First off, thanks for the great Free Software. System Administrators are generalists, but if I am at all a one-trick pony, that trick is just using systemimager ;) Like the previous author I have been using systemimager since 2003 and some colleagues have migrated to other imaging projects citing the stagnation of systemimager. I still use systemimager, but for my Ubuntu 11.04 installs I change to grub1, and have to edit master scripts and one or two systemimager commands as the master is ext4 and the clients ext3. Also the systemconfigurator version is an SVN version from 2 years ago that the maintainer sent me, and I edit the master script to remove --runboot; and manually run grubfix.sh (my script) after the imaging. Some (long) time back I read on the mailing list that systemimager maintainers use Ubuntu themselves, and so would soon feel the pain of grub and ext4, and would be working on these. Can you perhaps describe more extensively the relation between systemimager and SALI and your best guess as to the future developments over the next few years? And perhaps a specific note on the current status in SI and SALI of grub2, ext4, and systemconfigurator? Regards, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Request for help: Fighting spam on wiki.systemimager.org
Hi On Thu, Nov 04, 2010 at 11:08:57AM -0700, Bernard Li wrote: Lately our Wiki page http://wiki.systemimager.org has been getting a lot of spam. I am reaching out to the community to see if anybody has experience in fighting spam on MediaWiki installations and also to see if anybody would like to volunteer to be moderator for the Wiki and to undo spam edits on sight. Please feel free to reply back to this thread and/or email me off list. As a temporary stopgap, change the name of the EditPage form: 0 r...@kingklip:/usr/share/mediawiki/includes#diff EditPage.php EditPage.php.orig 533c533 form id=\editform1\ name=\editform1\ method=\post\ action=\$action\ --- form id=\editform\ name=\editform\ method=\post\ action=\$action\ This worked for a little while. regards, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book Blueprint to a Billion shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Systemconfigurator not seeing sda1
Hi On Mon, Jul 13, 2009 at 12:12:17PM +0200, Jan Groenewald wrote: When the image is done syncing, I get ROOTDEV /dev/sda1 under [BOOT] does not exist, please check your systemconfigurator config and it drops to shellout. Running 'fdisk -l' there does show sda1 though. What could be wrong here? The master script thinks bind mounting /dev is not necessary. I'm wrong here, /dev/ *is* bind-mounted. I have updated to systemconfigurator_2.2.12.svn716arighi_all.deb from Andrea's site. I now pass the ROOTDEV sda1 not found error. I get systemconfigurator running lots of stuff, and identifying / by UUID. When it gets to grub-install, it says, prob due to UUID: Format of install_device not recognized. Usage:... It does continue without shellout though. So I can run in the master script chroot /a/ grub-install /dev/sda Which allows the client to boot. It is not the proper grub menu.lst being used, instead of the usual three ubuntu entries (main, recovery, memtest), there is one entry jaunty (hd0,0). Weird. Separate issue: Note that on newer ubuntu's /etc/hosts looks like this at the top: 127.0.0.1 localhost 127.0.1.1 muizenberg.aims.ac.za muizenberg The hostname in the second line is not changed to the client hostname by SI/systemconfigurator. regards, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[sisuite-users] Systemconfigurator not seeing sda1
Hi I have set up si_4.1.6 and systemconfigurator 2.2.11-1 on a ubuntu dapper server and ubuntu jaunty 64bit clients. New clients can network boot via pxe/tftp and rsyncs the whole image over. (I had to exclude relatime from the ext3 mount options in the master script; and could not add -U to mkswap, so changed swap to mount by device name not UUID. I believe these are limitations of the boel_binaries versions as I have UYOK?) When the image is done syncing, I get ROOTDEV /dev/sda1 under [BOOT] does not exist, please check your systemconfigurator config and it drops to shellout. Running 'fdisk -l' there does show sda1 though. What could be wrong here? The master script thinks bind mounting /dev is not necessary. regards, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[sisuite-users] Ye Olde Sda and Hda
Hi I have just upgraded clients from feisty to hardy, and the dapper server is staying the same. I had this beauty to fix the sda-in-install / hda-in-installer problem, in the master script, before systemconfigurator, so that grub got installed (and I don't have to go fix it with a live CD): echo IDE-SCSI FIXES echo ln -s /dev/hda /dev/sda || shellout ln -s /dev/hda /dev/sda || shellout echo ln -s /dev/hda1 /dev/sda1 || shellout ln -s /dev/hda1 /dev/sda1 || shellout echo mount /dev /a/dev -o bind || shellout mount /dev /a/dev -o bind || shellout echo echo '(hd0) /dev/sda' /a/boot/grub/device.map || shellout echo '(hd0) /dev/sda' /a/boot/grub/device.map || shellout Now, hardy should be an upgrade from feisty, so I have this version: ii systemconfigur 2.2.2-2Unified Configuration API for Linux Installa But here I get system configurator bombing out with: You shouldn't call /sbin/grub-install... df: Warning: cannot read table of mounted file systems df: Warning: cannot read table of mounted file systems Could not find device for /boot: Not found or not a block device. Probing devices to guess BIOS dirves. This may take a long time. Busybox v1.1.1... Is there no quick fix in the master script for this? Any ideas why it started failing? I do recall something -- when parted first reads the partition table on hardy golden client, there is an error, something like perl: wrong hash, but I would have to go redo that now to check (and I didn't think it was related, I got all the way through the partitioning and rsync). regards, Jan -- .~. Jan Groenewald /V\ ICT Manager /( )\+27 21 787 9328 ^^-^^www.aims.ac.za - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Ye Olde Sda and Hda
Hi On Thu, Aug 21, 2008 at 04:10:48PM +0200, Jan Groenewald wrote: I do recall something -- when parted first reads the partition table on hardy golden client, there is an error, something like perl: wrong hash, but I would have to go redo that now to check (and I didn't think it was related, I got all the way through the partitioning and rsync). OK, seems harmless, unrelated: Using sfdisk to gather information about disk: /dev/sda Use of uninitialized value in hash element at /usr/lib/systemimager/perl/SystemImager/Common.pm line 926, FH_IN line 12. Use of uninitialized value in hash element at /usr/lib/systemimager/perl/SystemImager/Common.pm line 926, FH_IN line 16. Starting or re-starting rsync as a daemon. done! This client is ready to have its image retrieved. You must now run the getimage command on your imageserver. regards, Jan -- .~. Jan Groenewald /V\ ICT Manager /( )\+27 21 787 9328 ^^-^^www.aims.ac.za - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Yet another SDA/HDA problem
Hi On Fri, Jul 20, 2007 at 01:05:20AM +0200, Thomas Krause wrote: Any ideas? I could probably use overrides or change some scripts to work around this, but I want to avoid ugly hacks if possible. The clients are Dell Optiplex GX110 with an Ubuntu 7.04 image. I have some Dells. Recently the kernel modules for ide-scsi switched to hda and then back to sda. The SI installer kernel and the image kernel see a different device name. UYOK should overcome this, but... To get rid of all this I do, in the master script, and I still use the SI kernel: mount /dev /a/dev -o bind ln -s /dev/hda1 /dev/sda1 before the systemconfigurator part, which includes --runboot, which includes grub (or lilo). That symlink is good enough for grub-install. Of course your fstab and all those things stay the final device name. IIRC, the parted and mkfs sections will also need the device names that the installer see. cheers, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] problem with dell optiplex 745 (sata)
Hi On Tue, Jul 03, 2007 at 10:13:17AM +0200, Olivier FALZONE wrote: I have problems to install a Dell Optiplex GX745 for 2 weeks. I didn't have any idea for the issue, so if someone have any idea... We use systemimager 3.8.1-1 on Dell Optiplex 150, 270, 280, 620 without any problem. When I try to install a GX745, (with an image created on the same PC), systemimager can read his install script and then gives me this error : could not stat /dev/sda - No such file or directory. ide-scsi module? Installer and Image might see different disks: /dev/hda (installer) and /dev/sda (image to be deployed). The quick ugly fix is: I am using the standard kernel and initrd.img. recompile your kernel to have ide-scsi. Not too hard. Get the source, edit the linux.config file, compile, and copy only the kernel out to your netboot directory. Or perhaps it already has ide-scsi. When you drop to a shell after couldn't stat /dev/sda, do lsmod|grep ide-scsi, and check the devices: ls -l /dev/sda /dev/hda In the master script, though it might think this is not necessary, it in fact is: mount /dev/ /a/dev/ -o bind || shellout. My section there looks like this: (yes, really, I know it is ugly, it works, dammit): # # Needed for ide-scsi/grub-install Note a little below as well # after the systemconfigurator, we fix the device.map file as well. # echo IDE-SCSI FIXES echo ln -s /dev/hda1 /dev/sda1 || shellout ln -s /dev/hda1 /dev/sda1 || shellout echo mount /dev /a/dev -o bind || shellout mount /dev /a/dev -o bind || shellout # Then after the chroot /a/ systemconfigurator bit, the next section, I have: # # Fix the device.map # echo echo '(hd0) /dev/sda' /a/boot/grub/device.map || shellout echo '(hd0) /dev/sda' /a/boot/grub/device.map || shellout # In the unmount section, add: echo umount /a/dev || shellout umount /a/dev || shellout Your fstab will of course stay sda, as that is what the image uses, but it might use UUID thingies. Have a look. The partition and mkfs section needs to be changed though: For instance, this was all sda, and I had to change it to hda so the installer could perform this: ### BEGIN swap and filesystem creation commands ### echo mke2fs -j /dev/hda1 || shellout mke2fs -j /dev/hda1 || shellout echo tune2fs -U 74c403d6-6296-4231-a1f0-36e92e0eab76 /dev/hda1 tune2fs -U 74c403d6-6296-4231-a1f0-36e92e0eab76 /dev/hda1 echo mkdir -p /a/ || shellout mkdir -p /a/ || shellout echo mount /dev/hda1 /a/ -t ext3 -o defaults || shellout mount /dev/hda1 /a/ -t ext3 -o defaults || shellout For each partition and FS. cheers, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Back, have some time,. SDA to HDA imaging
Hi I had the same hda/sda trouble. It was an ide-scsi module, which I had to add to a pre-UYOK SI kernel, but that is another story. SI didn't think my master script needed to mount /dev /a/dev/ -o bind but in fact it was needed for chroot /a/ systemconfiguraror so that the part doing grub-install can see the hard drive devices. Worse, I had to, after this mount, before chroot /a/ systemconfigurator, ln -s /dev/hda1 /dev/sda1 and it actually worked. Inelegant, obscure, and took to long to find. The installer sees hda, the images sees sda. ide-scsi yuckness. Of course, yesterday Ubuntu Feisty 7.04 upgraded the kernel package linux-image-2.6.20-16-generic, (from -15) and now, still via ide-scsi, the Dell Optiplexes now again show hda and not sda, like older kernels, like the installer, but not like Feisty since release up to now :-P Why the sudden reversal? /Me has not ventured to lkml or feisty changelogs... OK, had a look now at the Feisty changelogs for that kernel, and it is a mostly networking related security upgrade, with no mention of ide-scsi. Irunno... OK, so the stupid ln -s is no longer necessary, but the dev bind-mount is still necessary, somehow mkautoinstallscript thinks I don't need it for this image. The fstab file also had to be changed in the master script to be sda, and now back to hda. UUIDs didn't seem to work despite the labels being set in the master script during partitioning. However grub booted a root partition by label. Perhaps this is also solved now. To debug all this read the master script, shellout at the appropriate place, and test some things in the installer environment and in the chroot. I run stock Ubuntu Dapper 6.06.1 LTS servers, and teach people to use these, and it is desireable to start off with the versions of software already packaged for this. It means SI 3.2.3, fairly old. Aside: For the ide-scsi kernel module I just downloaded the 3.8 source, recompiled just for the client boot kernel with one extra module, and took the kernel and initrd out and put it in /var/lib/tfptboot where it was needed, in a 3.2.3 systemimager-server installation. Even in Ubuntu Feisty 7.04 the packaged version of SI is 3.2.3, there seems to be not a lot of movement to UYOK and later upstream versions? SI bo! cheers, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[sisuite-users] dpkg-buildpackage on Dapper fails
Hi I am trying to use Dapper servers and standard versions on there to have a setup that is easily reproducible, and can be shown to new, remote system administrators. I need an ide-scsi module to be enable in the boot kernel though. this is pre-UYOK, faster, and I just want to add the one module to the standard dapper versions. It has worked perfectly for us before on Debian Sarge. Uhm, that server and kernel is out of my reach now. I want to replicate the same thing here, and need ide-scsi again. So I did this apt-get source systemimager-boot-i386-standard dpkg-source -x systemimager_3.4.1-1.dsc Edit one file: systemimager-3.4.1/patches/linux.i386.config to enable ide-scsi; and put the patch in the _debian_ patches directory. 0 [EMAIL PROTECTED]:/usr/local/src/systemimager-3.4.1#cat patches/idescsi.patch --- systemimager-3.4.1.orig/patches/linux.i386.config 2007-05-07 10:06:13.0 +0200 +++ systemimager-3.4.1/patches/linux.i386.config2007-05-07 10:08:46.0 +0200 @@ -239,7 +239,7 @@ # CONFIG_BLK_DEV_IDECD is not set # CONFIG_BLK_DEV_IDETAPE is not set CONFIG_BLK_DEV_IDEFLOPPY=y -# CONFIG_BLK_DEV_IDESCSI is not set +CONFIG_BLK_DEV_IDESCSI=y # CONFIG_IDE_TASK_IOCTL is not set # Then I do dpkg-buildpackage -rfakeroot -us -uc ../build.si.log /dev/null and I get up to here: In file included from subst.c:11: /usr/include/unistd.h:236: error: two or more data types in declaration specifiers make[4]: *** [subst.o] Error 1 Any advice on how to continue will be greatly appreciated. Full file at http://www.aims.ac.za/~jan/build.si.log regards, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] dpkg-buildpackage on Dapper fails
Hi On Tue, May 08, 2007 at 12:06:18PM +0200, Jan Groenewald wrote: apt-get source systemimager-boot-i386-standard dpkg-source -x systemimager_3.4.1-1.dsc Of course I also did apt-get build-dep systemimager Which fails because libreadline4-dev should read libreadline4. So I installed all the build-deps and edited the dsc file to relflect a dependency on libreadline4 and not -dev. cheers, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] mounting proc and sys in ubuntu dapper imaging
Hi I'm busy with upgrading the computer lab here from breezy to dapper (ubuntu versions). The image-server (debian sarge) is unchanged from years of serving woody/sarge/hoary/breezy on Dell Optiplex GX260 and GX270 desktops. I haven't upgraded this due to a specific boot kernel which works for my desktops for the first pxe boot. ii systemimager-boot-i386-standard 3.2.3-6 ii systemimager-common 3.2.3-6 ii systemimager-doc 3.2.3-6 ii systemimager-server 3.2.3-6 Just some notes: 0) the grub-install workaround is still necesarry (first boot of a pxe imaged client gives error 15; I boot a liveCD to grub-install, which I cannot do from the master script though the commands are there, probably ide-scsi related) 1) devfs=nomount is no longer necessary in grub. The grub-install above actually is enough now to allow booting. See http://wiki.sisuite.org/Ubuntu?highlight=%28ubuntu%29 for the breezy experience I had with above issues. New Errors: 2) I get a new error when the master script runs: ### BEGIN mount proc in image for tools like System Configurator ### logmsg mkdir -p /a/proc || shellout mkdir -p /a/proc || shellout logmsg mount proc /a/proc -t proc -o defaults || shellout mount proc /a/proc -t proc -o defaults || shellout ### END mount proc in image for tools like System Configurator ### ### BEGIN mount sysfs in image for tools that might be run during chroot ### logmsg mkdir -p /a/sys || shellout mkdir -p /a/sys || shellout # following line added by Jan. Two after that commented out. logmsg Not mounting sysfs since 2.4 kernel in systemimager bombs out #logmsg mount sysfs /a/sys -t sysfs -o defaults || shellout #mount sysfs /a/sys -t sysfs -o defaults || shellout ### END mount sysfs in image for tools that might be run during chroot ### All four those logmsg's generate a no such file or directory. I have no idea why. The /a/ is there. As you can see I uncommented mounting sysfs (I get no such device and shellout if I leave it in). Then the imaging completes, but... 3) What should be eth0 is somehow converted to eth1. I can turn it on, but there is some (ubuntu-related?) problem in that permission is denied to root to run dhclient. 4) Also, X doesn't start on boot. Comments on the sysfs mounting please? regards, Jan PS. I see http://wiki.systemimager.org/index.php/HOWTO_Net_Boot_Ubuntu I'll help finish that when I get around to it! -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] software raid and new autoinstall script
Hi On Mon, Dec 12, 2005 at 11:10:47AM -0500, Charles Galpin wrote: I have an image that I want to restore to a server using software raid (systeminager 3.4). Since I already have the image and just want to change the autoinstall script, is there any way to run getimage to get generate the autoinstall script and not get an image? Or maybe a script I can run on the client's autoinstallscript.conf directly? I have modified existing autoinstall scripts to tweak partition sizes and hardware types, but this looks a but daunting to me. My images are very large which is why I haven't just imaged it to see what gets generated. Love the comments in autoinstallscript.conf btw Brian :) On the server, run mkautoinstallscript. If it is a later verison, si_mkautoinstallscript. Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] SystemImager on Ubuntu
Hi On Wed, Nov 02, 2005 at 12:19:06AM -0800, Bernard Li wrote: BTW, which version of SystemConfigurator are you referring to in your document? [EMAIL PROTECTED]:~#dpkg -l | grep systemc ii systemconfigur 2.0.10-1 Unified Configuration API for Linux Installa (the servers are debian sarge) cheers, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] SystemImager on Ubuntu
Hi On Wed, Nov 02, 2005 at 02:25:08PM +1000, Mark Wass wrote: I'm beginning the journey of looking into using Ubuntu (Debian breed of Linux). I was wondering if anyone is using this successfully with SystemImager Yes Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] SystemImager on Ubuntu
Hi On Tue, Nov 01, 2005 at 09:45:48PM -0800, Bernard Li wrote: You guys want to add some notes in the wiki? [1]http://wiki.sisuite.org I claim to be an expert in neither sisuite usage nor wiki editing. Please improve if you can: http://wiki.sisuite.org/UserStories http://wiki.sisuite.org/Ubuntu Thanks to the sisuite developers for making all our lives easier ;-) regards, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] /dev empty
Hi On Thu, Oct 20, 2005 at 06:14:08AM -0500, John Jolet wrote: That won't work for me as gentoo has moved to udev, and things go very strange if you mount devfs with udev...at least they did for me. I needed that on ubuntu which uses udev. Can't say I understand it. But it worked. I still need to run grub-install manually after the first image, and then to boot need devfs=mount. Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] /dev empty
Hi On Wed, Oct 19, 2005 at 04:09:05PM -0500, John Jolet wrote: on my systems it does the same thing, I assumed it was because gentoo uses udev. I put a step in my autoinstall script that rsyncs /dev/* right before the chroot step. add devfs=mount to the kernel options Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] Problems after installation
Hi On Mon, Oct 17, 2005 at 01:01:37PM +0200, Ca?ada.Andres wrote: Hi! I'm new here. I'm trying to install systemimager in Debian. after apt-get install systemimager-server in the image-server and apt-get install systemimager-client in the golden-client There is no problem with dependencies and installation has no problems. But when I want to prepareclient, the system can't find that command (it's not installed??). What's the matter? It should be there after the installation shouldn't it? The same thing happens when I look for getimage command. (it's not installed) What should I do?? Most likely you have a new version where all commands are prepended with si, like this, si_command. dpkg -L systemimager-client, will show you the files installed from that package. Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] Problems with Grub after Imaging Ubuntu Client
Hi On Sun, Aug 28, 2005 at 02:02:10AM +0100, Paul Syred wrote: Has anyone else had similar problems using Systemimager? - I'm sure there's a better way of doing this than manually booting each client node using Knoppix and installing grub properly. Perhaps I'm being really stupid, and have missed out some configuration steps, and so please let me know how you yourselves have got this working! I'm currently doing the same. I tried si 3.5 but there were other problems (see recent threads). Someone suggested running a 2.4 kernel on the golden client while doing the getimage, this didn't make any difference for me either. I boot each node with a liveCD (ubuntu) and scp this script onto it, and run it (I also need devfs=mount). Would love to see a real solution. On the other hand, it doesn't add much time when you take into account unpacking and connecting a new box. However, I'd love to get mac-address reaping, multicast and one-key-net-install properly working like before with 2.4 kernels. My script: #!/bin/bash # Net Install broken: udev, 2.6 and systemimager don't play nice # To fix, netboot the newly imaged node (causes grub error 15) # Put liveCD in while it installs, reboot to liveCD # On the liveCD do this # [EMAIL PROTECTED]:~$ scp [EMAIL PROTECTED]:bin/netfix.sh . # [EMAIL PROTECTED]:~$ sudo ./netfix.sh # place to work mkdir /mnt/test # fix booting mount /dev/hda2 /mnt/test mount /dev/hda1 /mnt/test/boot apt-get install grub echo (hd0) /dev/hda /mnt/test/boot/grub/device.map grub-install --root-directory=/mnt/test /dev/hda umount /mnt/test/boot umount /mnt/test # fix /local scratch space mke2fs -j /dev/hda7 mount /dev/hda7 /mnt/test chmod 1777 /mnt/test umount /mnt/test # reboot shutdown -r now cheers, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] systemconfigurator --runboot fails (chroot does not see /dev/hda)
Hi On Wed, Aug 17, 2005 at 04:59:28PM +0200, Jan Groenewald wrote: When I run si_prepareclient, I get this: I couldn't identify your kernel file. Please try --XXX. [EMAIL PROTECTED]:/etc/systemimager # I couldn't solve this, So I am reverting to the systemimager version 3.2.3 on ubuntu (or 3.4 from systemimager.org). Neither gave this problem. I find no unistall target in the 3.5.3 makefile though. How can I delete the files? regards, Jan P.S. For those who followed the entire thread. Been away but back and working on this now: Booting a 2.4 kernel for getimage didn't work either. Still grub error 15. So since it is exactly the same as the 2.6 kernel there is no point in running 2.4. I am reverting to each node having to be booted with a liveCD to run grub-install; that is all I need for a net install. Perhaps later I can solve it but the nodes must go out now, unfortunately. Also, I will need to solve the updateclient script's not remounting /boot read-only, and overwriting the device.map file again. This is somewhat annoying, but workable for a few weeks until it is solved and automated again. -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] systemconfigurator --runboot fails (chroot does not see /dev/hda)
Hi
On Tue, Aug 16, 2005 at 05:31:27PM +0200, Jan Groenewald wrote:
Very strange. Well, I can't put a live CD in 100 machines, so I'll be
looking at the other solutions
1) upgrade systemimager
I am have now installed systemconfigurator 2.2.2 and systemimager 3.5.3
from source.
When I run si_prepareclient, I get this:
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
Using sfdisk to gather information about disk:
/dev/hda
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
Warning: The partition table looks like it was made
for C/H/S=*/255/63 (instead of 77504/16/63).
For this listing I'll assume that geometry.
Adding: /lib/modules/2.6.11/kernel/drivers/acpi/fan.ko
lots of these Adding .ko...
Adding: /lib/modules/2.6.11/kernel/drivers/ieee1394/raw1394.ko
Filesystem for new initrd: cramfs
Creating new initrd from: /tmp/.systemimager.2
find /tmp/.systemimager.2 -depth -exec touch -t 196912311900 '{}'
';'
mkcramfs /tmp/.systemimager.2 /etc/systemimager/boot/initrd
Directory data: 40628 bytes
Everything: 2196 kilobytes
Super block: 76 bytes
CRC: d0205443
warning: gids truncated to 8 bits (this may be a security concern)
gzip -9 -S .img /etc/systemimager/boot/initrd
gzip: /etc/systemimager/boot/initrd.img already exists; do you wish to
overwrite (y or n)? y
ls -l /etc/systemimager/boot/initrd.img
-rw--- 1 root root 2189715 Aug 17 16:55
/etc/systemimager/boot/initrd.img
I couldn't identify your kernel file. Please try --XXX.
[EMAIL PROTECTED]:/etc/systemimager #
What is that --XXX?
cheers,
Jan
--
.~.
/V\ Jan Groenewald
/( )\www.aims.ac.za
^^-^^
---
SF.Net email is Sponsored by the Better Software Conference EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile Plan-Driven Development * Managing Projects Teams * Testing QA
Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf
___
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] imaging with 2.6 kernel vs 2.4
Hi On Tue, Aug 16, 2005 at 01:57:03PM -0600, George Kelbley wrote: grub. another interesting thing is that after a minimal install, if I run getimage, I can get clones to boot ok. As soon as I start configuring them with real world stuff (ldap and nfs mounts for example), then I run getimage again, the clones will panic during boot. strange But the weird thing, it seems like as long as the golden client is running on a 2.4 kernel when getimage is run, the clients don't care. They boot into 2.6 right from the beginning. stranger I am have now installed systemconfigurator 2.2.2 and systemimager 3.5.3 from source (see other thread). If that bombs out I might try this. cheers, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] Re: systemconfigurator --runboot fails(chroot does not see /boot)
Hi On Mon, Aug 15, 2005 at 08:35:47AM -0400, Shiling Ding wrote: df: warning can't read table of mounted filesystems. Could not find device for /boot: Not found or not a block device. Probing devices to guess BIOS drives. This may take a long time. That does seem the same. Is it within the chroot /a/ environment? Try putting shellout instead of reboot at the end of the masterscript, so that you can investigate this. After reboot, the grub is installed fine, but DHCP is not configure as systemconfigurator specified, imaged computer is using static IP of the golden client. Strange. Are you sure during the getimage command you chose DHCP and not static or something else? I recall three choices there, one being a simple backup which would keep the golden client's settings. Golden Client: linux 2.6.11-gentoo-r3, systemconfigurator 2.0.9, My problem was udev (since Ubuntu is 2.6 kernel with udev) related. My systemconfigurator is slightly newer: 2.0.10-1 (ubuntu) systemimager 3.4.1. My systemimager is 3.2.3-3 (ubuntu) Imager Server: fc4, systemimager 3.4.1. Image server: debian, systemimamger 3.2.3 Initially I have the /boot not found failed since I have /boot in it's own partition, I was able to get it working after change the / /boot order in the master script after reading this list. I thought it was that but seem to have overcome this - my boot and root are still separate. cheers, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] systemconfigurator --runboot fails (chroot does not see /dev/hda)
Hi On Mon, Aug 15, 2005 at 02:46:16PM +0200, Jan Groenewald wrote: I have actually only done this all manually, from liveCDs and systemimager shellout prompts, but a new node has booted, so I put in all in the master script now and am testing it. Will report shortly. Well, the MBR, device.map and devfs=mount now lets my nodes boot. Yee-haa. However: 1) They boot with a bad superblock on hda7 and hda5 (ext3 and ext2, both excluded from the update by localexclude). The one is /tmp and the one is /local (scratch space). 2) After a subsequent updateclient, the device.map is overwritten with (fd0) /dev/fd0 (hd0) /dev/hd0 which causes an error in runboot again. This I suppose I could fix by replacing that device.map after the --runboot in the updateclient script. cheers, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] systemconfigurator --runboot fails (chroot does not see /dev/hda)
Hi On Mon, Aug 15, 2005 at 03:38:39PM +0200, Jan Groenewald wrote: Well, the MBR, device.map and devfs=mount now lets my nodes boot. Yee-haa. Oh no. No dd command on the network boot image. Can I add it somehow? 1) They boot with a bad superblock on hda7 and hda5 (ext3 and ext2, both excluded from the update by localexclude). The one is /tmp and the one is /local (scratch space). /dev/hda7 was never made, since it is unmounted before getimage to save space. I put mkfs in the master script. /dev/hda5 was a once off (weird, hey) If I don't have dd (what is that, busybox or something which doesn't have it?) how else can the network boot kernel and system put a file in the MBR? I cannot chroot since then I can't see hda1, but I can mount and access the correct MBR from the image. Any ideas? Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] systemconfigurator --runboot fails (chroot does not see /dev/hda)
Hi On Sat, Aug 13, 2005 at 02:32:11PM -0700, Bernard Li wrote: Does Ubuntu use udev? If so, you can try the following: Yes, it does. It is on a 2.6 kernel. Edit your image's /etc/systemimager/autoinstallscript.conf, i.e. ..image/etc/systemimager/autoinstallscript.conf on your imageserver: - add boel devstyle=devfs / right before /config (udev =/= devfs, but they are treated similarly here) - mkautoinstallscript --image image --force --post-install reboot - re-image the node I'll go and try it tomorrow, and get back to you. What version of SystemConfigurator are you using? ii systemconfigur 2.0.10-1 Unified Configuration API for Linux (on the client, in which chroot it is running, right) I updated systemimager to 3.4 (from the systemimager website, which is newer than the ubuntu systemimager-* 3.2.3-3 packages. This broke the booting on the clients, which now didn't see the hda at all to partition it (missing ide-scsi? I solved that years ago and didn't feel like doing the mkbootpackage thing all over, I've forgotten how -- I pulled my boot kernel back from a backup, and reverted to 3.2.3 -- I don't think that is the problem anyway?). There are a few more things we can try if this doesn't work. It might help if you can post things like device.map, grub.conf during/after the imaging process (i.e. don't reboot after done, and enter the console). I've noticed device.map on the golden image: /dev/hda (hd0) buthe images, once installed, have only: /dev/fd0 (fd0) grub.conf? Or menu.1st? [EMAIL PROTECTED]:/etc # locate grub.conf (my golden image; yes, using grub) /usr/share/kernel-package/kpkg_grub.conf I can temporarily solve it by saving the MBR on the image, and changing the master script to dd that MBR back to the disk right after the failed systemconfigurator --runboot. But if this is a bug I'd like to file it (or am I doing something wrong?) I don't think it was an MBR, after looking up grub error 15. It was rather the device.map file. Is this another udev thing? I can now, by editing device.map (and I can set up the master script to copy this into place after the rsync) get a little further: Now grub sees the kernel, starts to boot, and then: (grub sees kernel and initrd.img) boot Uncompressing Linux, ok booting the kernel... audit(123412345124.2341324 something like that) initializing Starting Ubuntu... /sbin/init: 426: cannot create /dev/null : Read-only file system /sbin/init: 427: cannot open dev/console : no such file Kernel panic: not syncing. Attempted to kill init! One rather garbled thread here tells me to edit the grub boot line. (strange, these should be fine). Also something about devfs=mount in grub.conf there, so I'll look at that. http://kerneltrap.org/node/4870 I haven't gone further yet, but will report back tomorrow later (I'm on South African time). cheers, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] New image doesn't show up under lsimage
Hi I am trying to move 100 clients from debian to ubuntu before the next academic year starts up. I have installed a test golden client, and done a getimage to the server. (aims2, the previous one was aims1). I don't see the new image! The client partitions the disks and then when the rsync command starts bombs out with cannot find module aims2. client# prepareclient -se siserver server# getimage -im aims2 -go client server# addclients (add one test client) server# mkrsyncd_conf server# lsimage (*only shows aims1*) server# ls /var/lib/systemimager/images/ (yep, its there) Any ideas? cheers, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] New image doesn't show up under lsimage
Hi On Fri, Aug 12, 2005 at 12:27:31PM +0200, Jan Groenewald wrote: I don't see the new image! The client partitions the disks and then solved it, after reading /usr/bin/lsimage, which connects to the server by rsync: [EMAIL PROTECTED]:/etc/systemimager#/etc/init.d/systemimager-server restart Stopping rsync daemon for systemimager: rsync. Starting rsync daemon for systemimager: rsync. [EMAIL PROTECTED]:/etc/systemimager#lsimage --- Available image(s): --- aims1 aims2 There they are. cheers, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] Help with client installation
Hi On Sun, Aug 07, 2005 at 11:40:39PM -0300, Igor GomeZZ wrote: I'm using systemimager (debian in server and clients) for install 20 machines in a Universisty Computer Lab. Me too (switching 100 clients to Ubuntu tho, but servers will stay debian, I think). But, after store the golden-client image on server and create floppy bootdisk, I don't get to install the clients. In the message errors I see that IP number of imageserver is wrong! I set this in /etc/dhcp3/dhcpd.conf, iirc I forget if there is a 3 and a d everywhere in the above path, but you'll find it. On some clients you can set the IP to boot from in the BIOS, no? Boot a liveCD. Does the name resolve correctly in DNS? cheers, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] Systemimager incremental updates and process accounting
Hi Andy! On Wed, Jul 06, 2005 at 06:17:13PM -0400, Andrew D. Fant wrote: Does anyone else out there have process accounting running on systems being imaged by systemimager? I'm trying to work out all the nope, but I got the systemimager. settings that need to be configured to make sure that the golden-client's pacct file doesn't step on the one on other clients when I push out updates. Ideally, the logic I would like to see happen is: Ignore all existing pacct files on an incremental update. Don't use the only one? /etc/systemimager/updateclient.local.exclude have a look in there, it is a list of files plus some globbing. pacct file on the golden client for the master image. If imaging from edit the master file, or, I have my own /etc/init.d/localise which runs /etc/init.d/localise.`hostname` which copies /etc/someconf/someconfigfile.`hostname` to /etc/someonconf/someconfigile during boot and does /etc/init.d/someconf restart So if you reboot you get your own settings. running updates just exclude the important files. scratch or /var/acct/pacct doesn't exist, create a zero-length file and leave it at this. ok, master file or have the master image have this anyway. For a master image update I must stop X, clear usb devices, do something like backup my existing /var/acct/pacct (or my local version of these things) and create what I want the master image to have. My master script is highly customised and i don't update it again. Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] (no subject)
Hi On Mon, May 16, 2005 at 05:33:03PM -0500, Brad Fulda wrote: We have in our lab 144 new IBM HS-20 Blades running RH 9. All I need to be able to do is to load a OS across the network. We have looked at Xcat, Ghost, and now this, System Imager. Xcat offers way more than we need. Ghost still requires you to use floppies and SI seems to be the ticket. What I was wondering is specifically can SI be used for this? (it appears to ) What barriers might I come across? I want static IP's but I was reading that I needed to have a DHCP srver running. What do I need to do to allow for static IP's? Can I make a master image that is custom for each system. Meaning, I dont want to go back to each new system I just made and manually change host names, etc. Is there also a how to mini on the setup specifically for these blades we have? Any help will be very much appreciated. thanks Tell DHCP to assign static IPs. Give each IP a hostname in your DNS server. SI takes care of the customization, or you can tweak it further. The SI documentation has a lot more on this. When I get a new box I 1) add the mac address to DHCP for a certain IP. 2) add a hostname for that IP to DNS 3) network boot the machine Even this can be automated or you can let up on the security, depending on what you prioritize and how many machines you have time for. Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ --- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61 plasma display: http://www.necitguy.com/?r=20 ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Systemimager] Re: [Sisuite-users] need ide-scsi builtin
Hi On Tue, Sep 14, 2004 at 12:53:07PM +0200, Bas van der Vlies wrote: However, looking at the insmod error message I see another problem. Why can the directory /lib/modules/2.4.20-boel/ not be found? Any ideas? boel_binaries.tar.gz is fetched via rsync during the install phase: - first kernel and root ramdisk - In the root ramdisk the boel_binaries.tar.gz is fetched and in this package contains all modules like ide-scsi.o - You must have an entry in the rsyncd.conf where you installed this package I have taken a different route now. I got the systemimager source on debian, and modified the linux.i386.config file as well as INSMOD_COMMANDS. I rebuilt a .deb and installed that. Now the kernel pxe boots and says can't find /lib/modules/boel.. and then can't install the module. I also edited the master script, so at this later point, insmod ide-scsi actually succeeds. But it is too late, since /dev/hda don't exist. A quick workaround would be to MAKEDEV in the master script -- if such commands as mknod are available? This is rather ugly, and I'd rather just get the kernel to have the module, load it, and use it. regards, Jan -- Jan Groenewald (Computer Officer) AIMS - African Institute for Mathematical Sciences Email: jan@@aims..ac..za Web: http://www.aims.ac.za --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] need ide-scsi builtin
Hi Systemimager is great. It has been running fine for months. Recently I upgraded to 3.2.2 on a debian testing system. Now, when I do a network install, I get the following message when the autoinstall script executes: Could not stat /dev/hda -- no such file or directory. On the command line I then see there are no /dev/h* at all. I have Dell Optiplex gx260 or gx270 systems. The hard disks need ide-scsi. As I understand I need to replace the kernel for the autoinstall. I use ii tftp-hpa 0.28-2 HPA's tftp client To recompile a kernel I should I use a specific kernel version source? I installed the kernel source for 2.4.24 and was only allowed to choose ide-scsi as a module or not at all, not built-in. I used apt-get install kernel-source-2.4.24 I tried getting the systemimager source 3.2.2 and thought there would be patched kernel sources and a config file. The sources for systemimager contained no kernel sources. I used apt-get source systemimager-server. In /usr/share/systemimager/boot/i386/standard/config I find: # CONFIG_BLK_DEV_IDESCSI is not set I am not sure how to advance, or if I am on the right track. regards, Jan -- Jan Groenewald (Computer Officer) AIMS - African Institute for Mathematical Sciences Email: jan@@aims..ac..za Web: http://www.aims.ac.za --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] need ide-scsi builtin
Hi Peter, On Mon, Sep 13, 2004 at 12:53:47PM -0700, Peter Mueller wrote: I have Dell Optiplex gx260 or gx270 systems. The hard disks need ide-scsi. What module(s) is ide-scsi? I'm not familiar with gx260/270 systems. If the 10:23 [EMAIL PROTECTED]:~$ locate ide-scsi /usr/src/kernel-source-2.4.26/drivers/scsi/ide-scsi.c /usr/src/kernel-source-2.4.26/drivers/scsi/ide-scsi.h /usr/src/linux-2.4.24/drivers/scsi/ide-scsi.c /usr/src/linux-2.4.24/drivers/scsi/ide-scsi.h As far as I understand from the name, it is SCSI emulation for IDE disks. I.e. and IDE cable and SCSI commands? gx260/270 are newish Dell desktops. answer is libata, you can use my kernel. See my post on 2004/07/14 for details. Uhm, what is libata. Besides the obvious library for ATA. Doesn't sound like the same thing. I'll try the post and the kernel tomorrow, thanks, and reply if there are still problems, thanks. regards, Jan -- Jan Groenewald (Computer Officer) AIMS - African Institute for Mathematical Sciences Email: jan@@aims..ac..za Web: http://www.aims.ac.za --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
