Simon Ruiz wrote: >> Yeah I got that, totally understood. The question is: is it worth >> it for me to run around collecting MAC addresses from 300 >> workstations, and go through the trouble of asking our downtown >> people to make a change to their sacred server, in order to get >> static IP addresses? Is it the best way of using SystemImager? > > if you don't care about the static assignment you can simply boot up > the clients and totally get dynamic addresses... > > > > > > > Is there any benefit to making them static?
It is a benefit when you need to bind the topology of the nodes or the task of the nodes with the hostnames. Typically in a cluster a range of nodes could be dedicated to special purposes (I/O server for example), other nodes to compute, others for the login of the users, etc... In this case I want that each node gets a defined hostname and it must not change. If you have a pool of identical workstation maybe this benefit is not really necessary... > >> The same thing that happened when I tried running >> si_mkautoinstalldiskette --floppy /dev/sda to make an auto install >> diskette on a USB floppy drive: "ERROR: Invalid -floppy argument." > > I will investigate if it's possible to adapt si_mkautoinstalldiskette > also to usb keys... > > > > > > That would be very useful in our situation. We have over a hundred > computers where our only input method is USB work in progres... ;-) >> BTW, and this relates to my first e-mail where I said: >> >>> 4) Next I tried installing systemimager-client on the client to >>> be re-imaged, and set it up to boot SystemImager from the hard >>> disk. This does not work either. >> Well, I thought the problem might be the FAT12 partition that I >> needed for my convoluted Ghost setup, so I created a Ghost image >> directly from the golden client (with only 2 partitions, hda1 as an >> ext3 partition and hda5 as a swap partition) and blasted it onto >> another 170L. I then followed the documented path for booting from >> the hard disk (updateclient -a -server imageserver -c eth0), only >> to come upon the very same problems I did the first time, namely: >> >> Partition check: >> >> hda:end_request: I/O error, dev 03:00 (hda), sector 0 (and 2, 4, 6, >> 0, 2, 4, 6, then...) >> >> unable to read partition table >> >> Later, we get the following: >> >> Mounting hard drive... >> >> FATAL: Couldn't mount hard drive! >> >> Before dropping to a BusyBox prompt... >> >> >> >> >> >> Any ideas? >> >> > > This happens when you reboot the client to install? btw which version > of systemimager are you using? (sorry I don't remember if I already > asked this question...). > > > > > > I'm installing the "systemimager-client" package from the Ubuntu Edgy > "universe" repository. The package claims to be version 3.2.3-3. The > "systemconfigurator" package is also from the Ubuntu Edgy "universe" > repository. That one claims to be version 2.0.10-1. > > Yeah, this happens when I reboot after running "sudo updateclient -a > -server imageserver -c eth0", which is what I understood the > documentation to be telling me to do if I wanted to boot to > autoinstall from the client's hard drive on one of my 170Ls, I'm > going to try it now on a 210L. 3.2.3 is a very old release... and also systemconfigurator 2.0 is quite old... I would suggest to move to systemimager 3.7.5 and systemconfigurator-2.2.2. I don't see any particular problem for systemconfigurator, but I don't know if systemimager 3.7.5 can be built cleanly on ubuntu... in debian (unstable) you need 2 patches (that are already included in the trunk and they'll be available in the next release). Anyway I think we'll release 3.7.6 soon, so if it's not a problem you could try the code directly from the trunk (http://svn.systemimager.org/). Regards, -Andrea ------------------------------------------------------------------------- SF.net email is sponsored by: A Better Job is Waiting for You - Find it Now. Check out Slashdot's new job board. Browse through tons of technical jobs posted by companies looking to hire people just like you. http://jobs.slashdot.org/ _______________________________________________ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
