Hi there,
I am working on a fedora remix. I need to let user to add organization name/id during the user account creation. Is there any guide or examples on such additional changes for anaconda?
Regards,
Hi Navin For years I have been using the RFREMIX version of Fedora, and will most likely continue with the release of Fedora 30.It is a great wrapper to Fedora. I only make use of the network or Everything installation alternatives. To use the live ISO, I have to login (which is in Russian), search for the little flag icon and change the language/keyboardand relog. From thereon its in English. The link follows
Index of /fedora/russianfedora/releases/RFRemix/
| | | | Index of /fedora/russianfedora/releases/RFRemix/
|
|
|
Regards Leslie Leslie Satenstein Montréal Québec, Canada
On Monday, April 15, 2019, 11:31:45 a.m. GMT-4, Danishka Navin danishka@gmail.com 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.Is there any guide or examples on such additional changes for anaconda?
Regards,
Hi Leslie,
On Tue, Apr 16, 2019 at 3:40 AM Leslie S Satenstein lsatenstein@yahoo.com wrote:
Hi Navin
For years I have been using the RFREMIX version of Fedora, and will most likely continue with the release of Fedora 30. It is a great wrapper to Fedora. I only make use of the network or Everything installation alternatives.
To use the live ISO, I have to login (which is in Russian), search for the little flag icon and change the language/keyboard and relog. From thereon its in English. The link follows
Index of /fedora/russianfedora/releases/RFRemix/
Index of /fedora/russianfedora/releases/RFRemix/
Have you customized anaconda as I mentioned above? I mean allowing additional user inputs.
Regards
- Leslie*
*Leslie Satenstein* *Montréal Québec, Canada*
On Monday, April 15, 2019, 11:31:45 a.m. GMT-4, Danishka Navin < danishka@gmail.com> 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. Is there any guide or examples on such additional changes for anaconda?
Regards,
Danishka Navin
Anaconda-devel-list mailing list Anaconda-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/anaconda-devel-list _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/anaconda-devel-list
Hi Navin, It depends how you want to control this user organization/id. Do you have an addon which will setup this? Do you want to extend the existing Anaconda graphical user interface?Do you want to extend the existing Anaconda text user interface?Or should this be supported by kickstart installation only? Could you please answer the questions?Jirka 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. Is there any guide or examples on such additional changes for anaconda?
Regards,
Danishka Navin
_______________________________________________Anaconda-devel-list mailing listAnaconda-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/anaconda-devel-list
Hi Jirka,
My real use case is to deploy hundreds of moodle servers across the country where less technical people will do the installation. Each server required to setup with different access credentials. [1]
These servers will host Government Exam in remote areas and send the backup to central server which required to identify exam center separately. We have done the pilot exam by running a script which read centerid and then reset user passwords and hostname. But the issue is person do the installation know whats actually happening and what does this script. So, we can't do this for real exam. Other than this, we manage to run the pilot exam in 655 centers to facilitate nearly 200k candidates.
Above two requirements can be solved using entering center/organization ID which added during the installation, but we can't let them to manually setup the system.
Please find my in-line reply.
On Tue, Apr 16, 2019 at 2:28 PM jkonecny@redhat.com wrote:
Hi Navin,
It depends how you want to control this user organization/id.
Do you have an addon which will setup this?
hostname required to set based on the organizationID.
Do you want to extend the existing Anaconda graphical user interface?
no, prefer to have it on the same window where we create user or the window that prompt to choose installation destination, time & date, etc.
Do you want to extend the existing Anaconda text user interface?
same as graphical interface.
Or should this be supported by kickstart installation only?
servers are not connected each other and there is a chance that server is totally online during the installation (internet may available during the installation).
Could you please answer the questions?
I hope above information is answer your questions.
Other than this, we need to make disk level encryption (as the server keep the exam papers and answers till the evaluation of exam) which wasn't tested during the pilot test. As a fedora contributor I highly believe that this project will make a big impact on our community.
Jirka
[1] http://www.dailynews.lk/2019/03/07/local/179610/git-examination-online-first...
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] Currently this is not supported in the graphicala and text user interface, but can be donevia 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. 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.
Is there any guide or examples on such additional changes for anaconda?
Regards,
Danishka Navin
Best WishesMartin Kolman [0] https://en.wikipedia.org/wiki/Gecos_field%5B1] https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#user
_______________________________________________Anaconda-devel-list mailing listAnaconda-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/anaconda-devel-list
On Tue, Apr 16, 2019 at 4:55 PM Martin Kolman mkolman@redhat.com 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). 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 ? Can we prompt user to input a value during the installation using kickstart?
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.
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
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
Anaconda-devel-list mailing list Anaconda-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/anaconda-devel-list
On Tue, Apr 16, 2019 at 7:05 AM Danishka Navin danishka@gmail.com wrote:
On Tue, Apr 16, 2019 at 4:55 PM Martin Kolman mkolman@redhat.com 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"...
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.
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. 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.
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_...
On Tue, Apr 16, 2019 at 8:28 PM Jerry Amundson jamundso@gmail.com wrote:
On Tue, Apr 16, 2019 at 7:05 AM Danishka Navin danishka@gmail.com wrote:
On Tue, Apr 16, 2019 at 4:55 PM Martin Kolman mkolman@redhat.com 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_... _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/anaconda-devel-list
On Tue, Apr 16, 2019 at 8:28 PM Jerry Amundson jamundso@gmail.com wrote:
On Tue, Apr 16, 2019 at 7:05 AM Danishka Navin danishka@gmail.com wrote:
On Tue, Apr 16, 2019 at 4:55 PM Martin Kolman mkolman@redhat.com 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"...
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.
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]
I was trying to build ISO using fedora 29 ISO and anaconda-ks.cfg from a installed system.
I have add new entry with label of F29 as follows in to isolinux/isolinux.cfg But could not figure out what's wrong here. I was expecting anaconda to start after selecting give label "F29".
*menu separator # insert an empty linemenu separator # insert an empty line*
label F29 menu label ^F29 menu default kernel vmlinuz append initrd=initrd.img inst.stage2=hd:LABEL=CDLABEL=Fedora-WS-Live-29-1-2 inst.ks=cdrom:/f29.cfg
*label linux menu label ^Start Fedora-Workstation-Live 29 kernel vmlinuz append initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-29-1-2 rd.live.image quietlabel check menu label Test this ^media & start Fedora-Workstation-Live 29 kernel vmlinuz append initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-29-1-2 rd.live.image rd.live.check quiet*
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. 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.
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_... _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/anaconda-devel-list
On Thu, May 02, 2019 at 11:14:29AM +0530, Danishka Navin wrote:
I was trying to build ISO using fedora 29 ISO and anaconda-ks.cfg from a installed system.
I have add new entry with label of F29 as follows in to isolinux/isolinux.cfg But could not figure out what's wrong here. I was expecting anaconda to start after selecting give label "F29".
*menu separator # insert an empty linemenu separator # insert an empty line*
label F29 menu label ^F29 menu default kernel vmlinuz append initrd=initrd.img inst.stage2=hd:LABEL=CDLABEL=Fedora-WS-Live-29-1-2 inst.ks=cdrom:/f29.cfg
You need to use a boot.iso for inst.ks to work. Live does not support kickstart installs since version 21.15 - https://bugzilla.redhat.com/show_bug.cgi?id=1027160
anaconda-devel@lists.fedoraproject.org
-
Brian C. Lane -
Danishka Navin -
Jerry Amundson -
jkonecny＠redhat.com -
Leslie S Satenstein -
Martin Kolman