Re: Customizing Anaconda
Danishka Navin <[email protected]> Tue, 16 Apr 2019 21:11:14 +0530
| Newsgroups | gmane.linux.redhat.anaconda.devel |
|---|---|
| Message-ID | <CAKjxiWQ2ycdH=vFL+D0kYfHacnWYBo=y1Yk4smF+Gk6GTg6Fig@mail.gmail.com> |
On Tue, Apr 16, 2019 at 8:28 PM Jerry Amundson <[email protected]> wrote: > On Tue, Apr 16, 2019 at 7:05 AM Danishka Navin <[email protected]> wrote: > >> On Tue, Apr 16, 2019 at 4:55 PM Martin Kolman <[email protected]> wrote: >> >>> On Mon, 2019-04-15 at 21:00 +0530, Danishka Navin wrote: >>> >>> Hi there, >>> >>> I am working on a fedora remix. >>> I need to let user to add organization name/id during the user account >>> creation. >>> >>> Do you mean setting the gecos field for the user ?[0] >>> >> >> Some what this is I am expecting but I don't need it to keep in >> /etc/passwd <https://en.wikipedia.org/wiki//etc/passwd> (save it in >> different file is good enough) as multiple users in the same system should >> have same id (centerid). >> > > Then you shouldn't need to involve anaconda. > > >> we should able to retrieve the given id during the installation if we >> remove all local users. Imagine a situation only root account exists. Best >> solution is to write that value to a different file such as /etc/centerid >> or /etc/service, etc >> >> Currently this is not supported in the graphicala and text user >>> interface, but can be done >>> via kickstart (which is basically a config file that can be used to >>> configure an installation)[1]. >>> A kickstart file can be loaded either from network or from local media >>> during the installation. >>> >> >> Isn't it a static value if we use kickstart ? >> > > Depends on your definition of "it"... > normally we hardcode values for variables in the kickstart right? I thought you were asking to hardcode centerid in kicksart. > > >> Can we prompt user to input a value during the installation using >> kickstart? >> > > Anaconda will prompt for any required information that has not been > provided already, but anaconda only *requires* what is needed to perform > the install. > you mean only for what anaconda usually require but it wont support on additional requirements define in kickstart, am I right? > >> I also thinking about a silent installation (unattended). >> It would be great if its possible to prompt via kickstart but I never >> heard such option. >> > > Unattended install is kickstart's bread and butter.[2] > It sounds like you would be better off putting these customisation(s) into > the %post script of the kickstart file. > You might have the grub menu contain a list of the hundreds of servers, the > human installer chooses one and that determines the kickstart file, and > thus the custom parts. > let people to select a centerid from a list with hundreds of items not practicle at least it cause human errors of selecting wrong centerid. Or, depending on what you know about, hardware, on-site networking, etc. > the %post script might be made smart in a what-machine-am-I kind of way, > then have it do the custom parts automagically... > Or, some other creative way to utilize grub2, kickstart, and so on. > what we know is there is a lab with 1 server, 20 machines (at least) and everything networked with dhcp enabled ADSL/4G router. But there is no installation server setup only installation mechanism is DVD rom. > jerry > > If what you need is really setting the gecos field manually in the user >>> interface during the installation, >>> it looks like we could add it to the "Advanced" dialog on the user >>> configuration screen. >>> >>> this would be great if if you can enable it. >> >>> Is there any guide or examples on such additional changes for anaconda? >>> >>> >>> Regards, >>> -- >>> Danishka Navin >>> >>> Best Wishes >>> Martin Kolman >>> >>> [0] https://en.wikipedia.org/wiki/Gecos_field >>> [1] >>> https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#user >>> >> > [2] > https://docs.fedoraproject.org/en-US/fedora/f29/install-guide/advanced/Boot_Options/ > _______________________________________________ > Anaconda-devel-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/anaconda-devel-list -- Danishka Navin http://danishkanavin.blogspot.com http://twitter.com/danishkanavin _______________________________________________ Anaconda-devel-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/anaconda-devel-list