Centos – GNOME license not accepted issue when system has been rebooted

centosgnomelicensesrebootsoftware installation

GNOME Desktop has been installed on CentOS7 using sudo yum -y groups install "GNOME Desktop" and when startx is executed the desktop starts. However, when the system reboots the following issue occurs:

enter image description here

When c has been executed the following occurs:

enter image description here

1 results in:

enter image description here

and typing 2

enter image description here

unchecks the box and the issue persists.

Attempts to solve the issue

According this Q&A, 1 should be executed to solve the issue, but that did not help.

Questions

Why does the issue occur once the system has been rebooted?
If it works to accept the license by issuing certain commands how to avoid that these commands need to be executed every time the system boots?
The last and main question is how to avoid that this accept license prompt appears at boot?

Best Answer

Concise

Press 1
Press 2 in order to change [ ] to [x] in front of 2) I accept the license agreement
Press q
Accept license menu does not prompt anymore at boot

Comprehensive

The issue was caused because the prompt was not clear to me. First I thought that pressing c would result in continue, i.e., moving to section2, but that was not the case.

A Q&A was found that indicated that 1 should be pressed in order to continue to section 2 (see question).

Braiam asked whether 2 was pressed. Pressing 2 over and over again added an X and removed it once it was pressed again (see comments to question).

When the X was added, i.e. [X] 2) I accept the license agreement., pressing c did not work, but q had to be chosen. My assumption was that an instruction would be displayed, e.g. press a to accept.

enter image description here

Once yes was entered the license was accepted. Every time the system reboots the accept license menu does not prompt anymore.

I still do not understand why the license agreement menu did not prompt during the installation of GNOME and this desktop could run without accepting any license agreement and the menu was prompted once the system had been rebooted, but the license is accepted now and answers this question.

Related Solutions

Solaris 10 – Is it possible to reboot a system from a startup script

I have tested moving this script from /etc/rc0.d to /etc/rcS.d, /etc/rc1.d, /etc/rc2.d and /etc/rc3.d with the following results:

/etc/rcS.d - same behaviour as /etc/rc0.d - /etc/DR_Network_Configured is created, but no reboot occurs.
/etc/rc1.d - /etc/DR_Network_Configured is not created, and no reboot happens.
/etc/rc2.d - /etc/DR_Network_Configured is created and the system is rebooted.
/etc/rc3.d - /etc/DR_Network_Configured is created and the system is rebooted.

To summarise, when the system is booted to its default (milestone/multi-user-server:default, similar to run-level 3), it executes startup scripts located in /etc/rc0.d, /etc/rcS.d, /etc/rc2.d and /etc/rc3.d, but not /etc/rc1.d.

The reboot and init commands do not work when run from a startup script in /etc/rc0.d, /etc/rcS.d (and possibly /etc/rc1.d although I can't confirm this as the startup script in this directory never ran). They do work when run from startup scripts in /etc/rc2.d and /etc/rc3.d.

I imagine that this is designed to prevent a system from constantly rebooting. Should an erroneous startup script in /etc/rc2.d or /etc/rc3.d put the system into an infinite reboot loop, then the system can be fairly easily be rebooted to the single-user milestone and the offending startup script disabled rather than having to locate alternate boot media to boot off, mount the root volume/disk and disable the offending script.

Based on the above, I have modified my network reconfiguration script as follows:

Kept my script in /etc/rc0.d to change the network settings.
Added a function to it so that if the system needs to be rebooted after reconfiguring the network, a new script /etc/rc2.d/S99reboot is created which will reboot the system.
If the /etc/DR_Network_Configured file exists, and /etc/rc2.d/S99reboot exists, then remove the latter to avoid the system constantly rebooting.

My relevant code is:

#!/sbin/sh
reboot_script="/etc/rc2.d/S99reboot"

Create_Reboot_File ()
{
   echo "#!/sbin/sh" > $reboot_script
   echo "case \"\$1\" in" >> $reboot_script
   echo "start)" >> $reboot_script
   echo "  init 6" >> $reboot_script
   echo "  exit 0" >> $reboot_script
   echo "  ;;" >> $reboot_script
   echo "esac" >> $reboot_script
   echo "exit 0" >> $reboot_script
   chmod 740 $reboot_script
   chown root:root $reboot_file
}

case "$1" in
start)
   if [ -f /etc/DR_Network_Configured ]; then
      [ -f $reboot_script ] && rm $reboot_script
      exit 0
   else
      # My reconfigure network functions are here
      # ...
      touch /etc/DR_Network_Configured
      Create_Reboot_File
   fi
   exit 0
   ;;
*)
   echo "Usage: $0 { start }"
   exit 1
   ;;
esac
exit 0

Centos – Allow virtual terminal switch only for root

You can use the pam_time PAM module to restrict logins for certain users on certain tty's (and at certain times of the day, which is the module's main use).

So if you want to tell the system that logins on tty0 through tty7 (that is, all the VT's that are typically enabled) for all users other than root are never allowed, add this line to /etc/security/time.conf:

login ; tty0|tty1|tty2|tty3|tty4|tty5|tty6|tty7 ; !root ; !Al0000-2400

and then add the following line at or near the first account line in /etc/pam.d/login:

account  required  pam_time.so

Users will still be able to login by using the gdm login screen. And while they can switch to a VT before (or after) logging in, all they'll be able to do is see the login and password prompts; they won't be able to login successfully on a VT.

Tested on CentOS 6.6.

Best Answer

Related Solutions

Solaris 10 – Is it possible to reboot a system from a startup script

Centos – Allow virtual terminal switch only for root

Related Question