Hello,
i would like to know what the exact difference in the installation and configuration of CentOS 6.8 is between an kickstart installation from an usb drive or an cd?
when i install the system from the cd with dhcp the installation runs without errors (db2 database installation works too).
but when i install it from the portable usb drive i always get an error with "The Hostname "fbd123ab.pss.local" is not valid. Please enter an valid Hostname." from the db2 database installation.
so where is the hostname everywhere set?
Kickstart difference between USB and CD
Re: Kickstart difference between USB and CD
There should be no differences, especially if you've dd'ed the same iso image to the USB stick as you are using from the CD/DVD.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Re: Kickstart difference between USB and CD
Well there must be a little difference with the networking.
When i install i use "ks=hd:sda2:/pathtokickstartfile/ks.cfg" for USB and "ks=http://httpserver/pathtokickstartfile/ks.cfg" for CD.
The kickstartfiles are the same and the iso image too.
When i install i use "ks=hd:sda2:/pathtokickstartfile/ks.cfg" for USB and "ks=http://httpserver/pathtokickstartfile/ks.cfg" for CD.
The kickstartfiles are the same and the iso image too.
Re: Kickstart difference between USB and CD
There's actually huge differences.
on isolinux you can specify for example ks=cdrom:/where/your/ks/is.cfg
but on syslinux you can't be as broad
to be fair it's because usually machines don't have more than one cdrom, so the /dev/sr0 works (but it'll break if you try and install from a secondary cd)
and syslinux will probably break if you don't know ahead your device name/label/uuid otherwise you have to apply some changes to your initrd/install image to make it work with broader definitions.
on isolinux you can specify for example ks=cdrom:/where/your/ks/is.cfg
but on syslinux you can't be as broad
to be fair it's because usually machines don't have more than one cdrom, so the /dev/sr0 works (but it'll break if you try and install from a secondary cd)
and syslinux will probably break if you don't know ahead your device name/label/uuid otherwise you have to apply some changes to your initrd/install image to make it work with broader definitions.