Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Linux Software

Customized Linux Installations 10

edmz asks: "At work we have about 20 PCs which are all identical. We are planning on installing Red Hat on them but we want to fine tune it for the specific hardware that we have. We would like to install it and tune it on just one box and then somehow make an image or installation from it and store it in CD so that it can easilly be installed in the other machines. We would like to go the CD way, and I was wondering if there is any software that does this or if somebody knows an easy way to do it."
This discussion has been archived. No new comments can be posted.

Customized Linux Installations

Comments Filter:

  • This is exactly what the KickStart file is used for, it allows you to select the packages, etc, that will be used for the installation.

    You can find info in the RedHat manual once you have installed it, or online at:


    Steve
  • Kickstart is nice for genning boxes, but it seems you basically want to ghost your boxes.

    I think what you need to look at is LRP (linux router project). At the red hat certification class, we booted off a floppy and basically ghosted our machines with a copy of nt server. This can be used with any image.

    The method we used, the floppy booted, mounted a nfs share, and basically cat'd a file to /dev/hda.

    There's probually no reason why you can't pull the image from a cdrom just as easily.

    LRP is just a kernel small enough to fit on a floppy, with room to spare for scripts.

    So if you built a system, fine tuned and customized it, you can make an image, then 'ghost' it to other machines.

    Hope this helps out.

    Here's some links:
    http://www.linuxrouter.org/
    http://math.nyu.edu/phd_students/wilkinsm/linux/ www.linuxrouter.org_docs.html

    ghost=dos program that does the same, but LRP is much easier
  • Anonymous Coward wrote
    www.fezbox.com
    Why was this post moderated to -1? I found it to be actually useful.
  • Prepare a linux box with drivers (or driver modules) for all your PC you need. Then dump the full HD image to a file (dd if=/dev/hda of=/tmp/hdimage.raw ...) and burn that onto a CD.

    Prepare a Linux bootdisk which can provide you with an ISO9660 (=CD) filesystem.

    Boot the PC with the Linux bootdisk, mount the CD and copy the image file back to the harddisc.


    That's all. (Disclaimer: copying the image from CD to harddisc will destroy all and any data that was on that PC)
  • (damn I may have a put up a blank post, sorry)
    Anyway, here's a non-linux solution.
    *gasp!*
    Try using Powerquest's Drive Image program. We've used it here and it works well enough with Linux. You make your installation on one machine. Boot to DOS with a floppy and make an image of the hard drive (you'll need to put it up on a server or another hard drive or something.) Then just burn the image on a CD and blast it out on the other computers. It's relatively easy (though the version you'll need to buy is pricey.)
    Another program which does the same thing AND does IP multicasting (allowing you to update the other computers across the network all at the same time) is Norton's Ghost.
    Anyway, just another method.
  • the problem with these is that they don't really understand ext2fs all that well, so it's doing, from what I understand, the same job as if you used dd if=/cdrom/image of=/dev/hda1.

    This is fine so long as you've got a hard drive image that'll fit on a cd. But with a 650MB cdrom and a 18GB hard drive... I don't think it will work all that well. (note: I haven't tried this myself, it's just my understanding of how ghost works)

    Basically, you know that whatever solution you use should probably use linux, as it should understand ext2fs, but once you get past there, there's a lot that you can do. dd an image from an nfs server, use kickstart, or for that matter, use tar. The biggest problem that I see is partitioning the drives in the first place. One of the nicest things about ghost is their gdisk program. (a completely command line scriptable replacement for fdisk. extremely customizable and very nice. If anyone knows of a similar tool under linux, let me know.)

    -joe

  • Slackware's install is all shell. I like the shell installers myself, dialog rocks. It also allows customised installs. In my old lab I put up an NFS server with slack 4 on it which everyone installed off. It was a 100MBit LAN so it was incredibly speedy.

    Not sure how Red Hat installs though, I was never a fan.
  • (Note: I've basically done this before, but only from RH4.2 to RH5.2 -- it's probably changed little in RH6))

    1. Create a customized RedHat installation.
      1. Mirror the RedHat distribution.
      2. copy the RPMs you want into the big RPMS directory, remove RPMS you don't want, etc. I'd highly reccomend replacing old RPMs with the updates and grabbing the ssh (etc) rpms [replay.com] from ftp.replay.com. Also, install autorpm and either customize it or make a separate RPM with just the files for autorpm to use an updates mirror that you make.
      3. Edit RedHat/base/comps -- the format is somewhat self-explanatory. For the purpose you're describing, go to the "0 --hide Workstation" section and customize that. It's probably easiest to make that list by doing a completely custom install off of the mirror you made in step one and then doing rpm -qa --queryformat '%{NAME}\n' to get a list of all the packages that got installed.
      4. run genhdlist on the appropriate directory.
      5. Put that all up someplace
      6. Optionally, do the whole kickstart thing.
    2. Set up an updates "mirror" someplace and point autorpm on all those workstations at that mirror. Presumably set up to only install from your relatively secure mirror and to check PGP signatures, etc...
    You can put your custom install on an NFS mount point or burn it onto a CD (possibly even a bootable CD) and install all those machines... If you had more than 20 machines I'd suggest using DHCP, but you can probably manage without with 20 machines. You still might want to consider using DHCP to assign addresses to minimize how much effort you need to go through when you do the installs.

Happiness is twin floppies.

Working...