Installed RHS 2.1 nodes on laptop (4GB, using VMs of 512MB) w/ graphic installation disabled; used text installation. After default install and at first reboot, machine does not have the Gluster tools. Discovered difference between pakages installed: **Text mode installation** ... %packages --nobase @core %end **Graphic mode installation** ... %packages @core @glusterfs-all @glusterfs-swift @rhs-tools @scalable-file-systems abrt-gui %end
The documentation for anaconda says the 'text' boot option should behave this way: text Force text mode install. This will install only base packages for a minimal system and implies that the installed system will boot up in runlevel 3 instead of to the graphical login screen. https://fedoraproject.org/wiki/Anaconda_Boot_Options?rd=Anaconda/Options I'm not sure that's entirely logical (and I couldn't see it documented in the RHEL guides), but it would be something that would need to be changed in RHEL and anaconda upstream, rather than being something specific to RHS. Given it's only an issue if the user specifies the 'text' boot option explicitly or has less than 640MiB of memory, I'm not sure this is worth escalating.
(In reply to Anthony Towns from comment #1) > The documentation for anaconda says the 'text' boot option should behave > this way: > > text > Force text mode install. This will install only base packages for a > minimal system and implies that the installed system will boot up in > runlevel 3 instead of to the graphical login screen. > > https://fedoraproject.org/wiki/Anaconda_Boot_Options?rd=Anaconda/Options > > I'm not sure that's entirely logical (and I couldn't see it documented in > the RHEL guides), but it would be something that would need to be changed in > RHEL and anaconda upstream, rather than being something specific to RHS. > Given it's only an issue if the user specifies the 'text' boot option > explicitly or has less than 640MiB of memory, I'm not sure this is worth > escalating. Per the above, closing this as NOTABUG.