Well On Wednesday 29 October 2003 10:22, Maor Meir wrote: > In my limited expirince he simplest method for runing the network install > is probably FTP not NFS. FTP usually gives much less trouble > and the testing we(Alon Shachar and myself) were also done with ftp > installations. I have long experiance with NFS installations. FTP installations require large disk space. What about the %post ? Would you do it from inlined scripts, or from an NFS server? I know (experiance) that NFS works like charm. > > to the best of my knowledge redhat install does not know how to > read a kickstart file from an FTP server only HTTP(and possibly NFS) > this isn't really necessary as we can easily have many floppies and CDs > with our kickstart file available. Fine with me. You can use a local ks.cfg, or you could use an NFS based ks.cfg. either way, fine with me. We could use both, and select which one to initiate during the specific time. > > To have kickstart point to a domain we obviously need to have a working > DNS server running not only the basic DHCP. Do I understand you are > planing some kind of load balancing on two NICs? Not a domain, but a hostname. The server will run a minimilized DNS server, pointing to himself. Better then using IP address. > > server specifications must be finalized ASAP, so we can burn our CDs which > we would like to have a copy of various kickstart files. (one of them to > be used on network installs during insta-party) > these include: server names IP address if necessary install source > directories. I preffer discussing this part on a limited distribution list. It does not interest everyone. > > It would be nice if the install server would have a copy of our extra CD > (update CD does seem to be an adequate name) So that > if necessary it as welll could be installed. If its running an NFS one > could simply mount it and treat it no diffrently form a CD-ROM. There is enough space for it. > > So we need to make clear which of the following services will be > on the install server: FTP/NFS/HTTP/DHCP/DNS > what will the domain name/IP address of the server be. > location of RedHat install. See two comments above. > > I would not be surprised if some of the machines would not play > with the dhcp server(it has been known to happen), It would probably be a > good idea to set aside some of the IP address for manual configuration. I would be surprised. Never happened to me, and I had quite a few KS installs in my life. A small part of the IP addresses will be saved.
> > Meir. > > P.s > just been paranoid, what kind of a server are we talking about? Hard-disk > and RAM? Yep. We're talking about P866, 20GB HDD, 512MB RAM (SDRAM 133) > My bit of math, lets assume an install requires 2GB of data to be > transfered from server to client. and this somehow spreads out over > one hour. So 20 (non synchronized) installations would require 40GB/hour > stream. Which is 11MB/sec, this might be hard on an old hard-drive. It's not old, and it will do the trick. NFS uses all kinds of internal caching methods, as far as I know, and most time will be spent on uncomressing the rpm packages. We better discuss it on a closed forum. Less noise on the list. Ez. -------------------------------------------------------------------------- Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an empty message to [EMAIL PROTECTED]
