Well I now have a 4.0 server at a solid checkpoint. Before I start the chore of setting up SAMBA and LDAP.
Part of the delay was I did not copy all of the needed DNS files, and I have to reerad the BIND book.
So I want to be able to get to this point again easily.
I did not note down what options I had selected during install. Is there some way in the install log to figure that out?
Is there some way to do an image backup? I only have a Win2000 server available for the backup, no NFS on another system.
Appreciate any and all help.
Barrs Law of Recursive futility If you're smart enough to use one of these.... .....you can probably manage without one!
Do you have access to a FTP server? If so there is a nice project out there, G4U, that does a good job of imaging systems.
Boot from the G4U floppy or CD and pass a command or two......
Andrew
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Robert Moskowitz Sent: Tuesday, April 05, 2005 9:22 AM To: CentOS mailing list Subject: [CentOS] Milestone
Well I now have a 4.0 server at a solid checkpoint. Before I start the chore of setting up SAMBA and LDAP.
Part of the delay was I did not copy all of the needed DNS files, and I have to reerad the BIND book.
So I want to be able to get to this point again easily.
I did not note down what options I had selected during install. Is there some way in the install log to figure that out?
Is there some way to do an image backup? I only have a Win2000 server available for the backup, no NFS on another system.
Appreciate any and all help.
Barrs Law of Recursive futility If you're smart enough to use one of these.... .....you can probably manage without one!
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Quoting Robert Moskowitz rgm@htt-consult.com:
<SNIP>
I did not note down what options I had selected during install. Is there some way in the install log to figure that out?
<SNIP>
You can look at /root/anaconda-ks.cfg .. this is a kickstart file that was generated from your install. If you needed to rebuild this machine you could copy this file to a DOS/FAT/VFAT formatted floppy as the name ks.cfg and boot off of Disc 1 with this floppy in your drive and when it comes to the boot prompt type "text ks=floppy" which will instruct the installer to use the text mode installer and use a file called ks.cfg off of the first floppy drive.
If you use this method, please read the ks.cfg file first to understand what it is doing. Also, I believe it will list as comments your drive partitioning, so if you were to use this kickstart file it would not repartition your disk unless you uncomment those lines.
Hope this helps, Barry
Barry Brimer wrote:
If you use this method, please read the ks.cfg file first to understand what it is doing. Also, I believe it will list as comments your drive partitioning, so if you were to use this kickstart file it would not repartition your disk unless you uncomment those lines.
Ah, seems that we were typing same reply in parallel ;-)
The only thing I could add is that if he uncommets the partition info, he might need to also use clearpart option to clear partition table on target drives. For example "clearpart --drives=hda,hdb --initlabel" would clear partition tables from first two IDE drives (use with caution if there's any data on the system that needs to be preserved).
On Apr 5, 2005 7:36 AM, Barry Brimer barry.brimer@bigfoot.com wrote:
Quoting Robert Moskowitz rgm@htt-consult.com:
<SNIP> > I did not note down what options I had selected during install. Is there > some way in the install log to figure that out? <SNIP>
You can look at /root/anaconda-ks.cfg .. this is a kickstart file that was
The kickstart file is a direct recording of the install, but is less detailed than these two files:
/root/install.log.syslog /root/install.log
I think all three together provide a full picture of what was initially installed on a machine.
Regards, Greg
At 09:53 AM 4/5/2005, Greg Knaddison wrote:
On Apr 5, 2005 7:36 AM, Barry Brimer barry.brimer@bigfoot.com wrote:
Barry, Greg, and Aleksandar:
thank you all for the information. This is just the sort of help I needed.
Great place this list!
Barrs Law of Recursive futility If you're smart enough to use one of these.... .....you can probably manage without one!
Robert Moskowitz wrote:
I did not note down what options I had selected during install. Is there some way in the install log to figure that out?
Check the file /root/anaconda-ks.cfg. This is kickstart configuration file that was generated based on your choices during the install. You can use it to perform completeley automatic installation of the server. All you would do is copy the file to floppy disk and name it ks.cfg, boot from first CD, and on boot prompt type "linux ks=floppy" (this is just one method, ks.cfg can be also stored on USB stcik, CD ROM, or on the network).
Or you can modify it and use to install some other server. Check documentation at:
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/sysadmin-guide/
In particular this chapter that explains what kickstart installations are, options for creating kickstart configuration file, and what options are available:
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/sysadmin-guide/c...
Robert Moskowitz wrote:
Is there some way to do an image backup? I only have a Win2000 server available for the backup, no NFS on another system.
These two projects might interest you..
http://www.partimage.org http://www.mondorescue.org/about/about.html
-
Aleksandar Milivojevic -
Andrew Cotter -
Avtar Gill -
Barry Brimer -
Greg Knaddison -
Robert Moskowitz