[CentOS] how to use an own ks.cfg booting from a usb-device (centos 8 & 9)

Fri Jan 5 20:36:14 UTC 2024
Leon Fauster <leonfauster at googlemail.com>

Am 05.01.24 um 21:26 schrieb Christer M. Fekjan:
> On Thursday 04 January 2024 11:02:27 Ralf Prengel wrote:
>> Zitat von "Christer M. Fekjan" <drift.CentOS.i02 at 3x9.no>:
>>> Hello Ralf,
>>>
>>> Does your kickstart file contain all obligatory settings? Like e.g.
>>> language. Otherwise the installation will prompt for these, at least it
>>> did in previous CentOS versions.
>>>
>>> In my kickstart file I have these settings for an old CentOS 5 version
>>> (used ks a lot then):
>>> # use whatever fits you
>>> # System keyboard
>>> keyboard no
>>> # System language
>>> lang nb_NO
>>>
>>>  From a running CentOS 7 system's kickstart files (generated from the
>>> installation):
>>> - /root/anaconda-ks.cfg and/or
>>> - /root/initial-setup-ks.cfg
>>> # Keyboard layouts
>>> keyboard --vckeymap=no --xlayouts='no'
>>> # System language
>>> lang en_US.UTF-8
>>>
>>> As you see, the directives for v5 and v7 differs slightly. I don't know
>>> whether v5 directives would work on v7 or the other way around.
>>> Anyway, if you
>>> install a system manually, copying the necessary configuration
>>> directives from
>>> the then generated /root/*ks.cfg-files should give you a working ks-file.
>>>
>>> Also check that the path to the ks-file is correct. If possible host it
>>> on a webserver or any other way you can check, by logs or other means,
>>> that the ks-
>>> file is requested and correctly retrieved.
>>>
>>> Good luck, hope it helps!
>>>
>>> Kind regards,
>>> Christer M. Fekjan
>>
>> Hallo,
>> thanks for the hints.
>> In which file do you refere to the ks.cfg and which syntax are you using?
>> Is it isolinux.cg?
>>
>> Ralf
> 
> Short version: I guess you can use a network (or local) install media, enter
> "Edit boot command line" (or something similar) and add something like:
> ks=http://example.local/kickstart ksdevice=eth0
> I remember fiddling with a ks-file on a USB stick, but had no luck with that.
> 


IIRC - the kernel parameters must be namespaced:

inst.ks= and inst.ks.device=


--
Leon