Simon Ruiz wrote: > We've been using Norton Ghost for all our imaging needs, and I had to > come up with a pretty convoluted system to really be able to use it > effectively to keep all the workstations updated (read all about it > at my homepage http://www.mccsc.edu/~sruiz/5.10/imaging.htm). If you > notice, I was already using your jargon (golden client) since I have > been intending on moving to SystemImager since the beginning of this > in the interest of removing proprietary software from our system > altogether.
Totally agree! ;-) anyway norton ghost approach is totally different and it's totally filesystem-agnostic. Systemimager has other big advantages (and disadvantages), it treats filesystem images instead of block-by-block disk images, and for now you cannot manage windows installations (at least not for now...). But I'm sure that with systemimager you can obtain better results dealing with different hardware respect to the disk images approach. > > > 1) I want identical workstations, however since we have 2 (soon 3) > hardware specs to work with (Dell 170Ls with IDE drives, Dell 210Ls > with SATA drives, and soon some laptops), it seems like I'm going to > have to maintain 3 separate images. My question regarding this is: is > there a simple way to keep from having to maintain three separate > golden clients for this? The vast majority of the image, is going to > supposedly be identical between all the different hardware types, and > I can't imagine that the parts that are different are all that > dynamic... Regarding the hardware heterogeneity you can resolve using the standard kernel of a common distribution in your image, in this way you'll be sure that your image will be able to support different hardware devices. During the installation you should be able to manage the heterogeneity using UYOK feature (http://wiki.systemimager.org/index.php/UYOK) and --autodetect-disks option with si_getimage (or si_mkautoinstallscript). At least I've successfully installed a little lab with IDE and SCSI workstations in this way, using the same identical image. > > 2) In our network, we already have a DHCP server and have been > functioning with dynamic IPs thus far. We have no control over the > DHCP server and are not allowed to interfere with its normal > functioning. Is it a requirement that we turn around and assign > static IPs to the workstations now? Is there a simple way to work > with hostnames instead? Not a huge issue, really, it'd just take > communicating with the corporate people and letting them know we need > this done, and then waiting for them to do it. You can boot your workstation with an autoinstalling cd (see si_mkautoinstallcd) and define all the local options in the kernel boot parameters (http://wiki.systemimager.org/index.php/Installation_Parameters). IMHO a good approach would be to get the ip via dhcp and manually define the parameter that you can't define via the dhcp server (like the address of the image server, the image to use, the monitor server, etc), in this way you can use the same CD to install all the workstation. > > 3) So, I used mkautoinstalldiskette to, well, make an autoinstall > diskette. I could not set it to make the diskette at /dev/sda which > is where our USB disk drive is, so I made an image file and DDed that > to the diskette. This does not work, as the diskette (I think) > assumes it's going to be /dev/fd0. The actual error message for this > is "Checking for floppy diskette." followed by a reocurring > "end_request: I/O error, dev 02:00 (floppy), sector 0. Am I basically > screwed as far as using diskettes since all we have are USB disk > drives? That would be rather annoying, especially considering the > following: si_mkautoinstalldiskette is deprecated, you need to use an autoinstallcd. If you want to use a USB key and if you BIOS support the boot over USB, you need to manually create a USB boot key, copying the systemimager kernel and initrd on it (at the moment there is not a si_mkautoinstallusbdev or a similar command). I think you can create that using grub-install or lilo, but I've never tried it... > > 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. The error occurs because it tries to check > the partitions and doesn't recognize the FAT12 partition (hda1 or > hd0,0) that we have running in order to enable the use of GRUB 4 DOS > which we need to boot to a diskette image in order to be able to > Ghost a machine without running around with our silly little slow USB > disk drives. Since it cannot recognize that partition (and in fact, I > think it mangles it by overwriting the MBR on the hard disk so it > likely can't recognize it because it destroyed it), it cannot read > the partition table. Later on in the process I get the very evocative > "FATAL: Couldn't mount hard drive!" error followed by some likely > irrelevant stuff about how the kernel needs all necessary block and > filesystem drivers. So...any ideas? am I going to have to Ghost an > image onto the workstations, one that doesn't have a FAT12 partition > in hda1, in order to be able to boot SystemImage from the harddisk? > (The FAT12 partition is FreeDOS, and I had a hell of a headache > getting it to work in the first place, I know that Linux doesn't > quite like dealing with that partition) which version of systemconfigurator are you using? are you using lilo or grub in you client? versions? Regards, -Andrea ------------------------------------------------------------------------- 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=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
