How Green Was My Valley... err, My CentOS 7 (screenshots)

General support questions
Post Reply
User avatar
InitOrNot
Posts: 122
Joined: 2015/06/10 18:26:51

How Green Was My Valley... err, My CentOS 7 (screenshots)

Post by InitOrNot » 2015/09/02 15:46:03

I have just finished tuning my CentOS 7 test system (I am focusing on it as a server platform, therefore it is in text mode), and I thought it would be nice to share some screenshots of it booting inside a VMware virtual machine.

This system is peculiar, for it is a rebuild of CentOS 7 sources for the i686 CPU (32 bits), sourced from here, if anyone cares.

To get CentOS 7 to display the booting up messages, I had to edit the file /etc/default/grub and remove "rhgb" from the parameter "GRUB_CMDLINE_LINUX", and then run the command:

Code: Select all

# grub2-mkconfig -o /boot/grub2/grub.cfg
To easily grab the screenshots, I used this one liner in Bash (on the host):

Code: Select all

$ end=$((SECONDS+300)) ; while [ $SECONDS -lt $end ] ; do scrot ; done
So without further ado, the screenshots:

Image


Image


Image


Image


Image


Image


Image


Image


Image


Image


Image


Image


Image

I hope you liked them! :D

User avatar
avij
Retired Moderator
Posts: 3046
Joined: 2010/12/01 19:25:52
Location: Helsinki, Finland
Contact:

Re: How Green Was My Valley... err, My CentOS 7 (screenshots

Post by avij » 2015/09/02 18:16:36

Note that you could have used the beta images of CentOS 7 i386 as well.

User avatar
InitOrNot
Posts: 122
Joined: 2015/06/10 18:26:51

Re: How Green Was My Valley... err, My CentOS 7 (screenshots

Post by InitOrNot » 2015/09/02 22:24:25

avij wrote:Note that you could have used the beta images of CentOS 7 i386 as well.
Oh, I didn't know the official i386 beta for CentOS 7 already existed, there is no word of it yet in the FAQ.

It's nice to know, thank you!

So I thought I should also post the screenshots for a shutdown, here they come:

Image

Image

Image

Image

Image

----------------

By the way, I have pruned the running services to what I consider the bare minimum for a text-based working system (plus the "gpm" service, for good measure), and as can be seen in my first post the system is only using 22 MB of RAM memory just after boot --so I'd like to share what services I have running, and also what sockets are listening in order to start services on-demand:

Code: Select all

# systemctl --all | grep active | egrep -v 'inactive|exited' | egrep -e '.service|.socket'

atd.service                   loaded active   running   Job spooling tools
chronyd.service               loaded active   running   NTP client/server
crond.service                 loaded active   running   Command Scheduler
dbus.service                  loaded active   running   D-Bus System Message Bus
getty@tty1.service            loaded active   running   Getty on tty1
gpm.service                   loaded active   running   Console Mouse manager
lvm2-lvmetad.service          loaded active   running   LVM2 metadata daemon
network.service               loaded active   running   LSB: Bring up/down networking
postfix.service               loaded active   running   Postfix Mail Transport Agent
rngd.service                  loaded active   running   Hardware RNG Entropy Gatherer Daemon
rsyslog.service               loaded active   running   System Logging Service
sshd.service                  loaded active   running   OpenSSH server daemon
systemd-journald.service      loaded active   running   Journal Service
systemd-logind.service        loaded active   running   Login Service
systemd-udevd.service         loaded active   running   udev Kernel Device Manager
dbus.socket                   loaded active   running   D-Bus System Message Bus Socket
dm-event.socket               loaded active   listening Device-mapper event daemon FIFOs
lvm2-lvmetad.socket           loaded active   running   LVM2 metadata daemon socket
systemd-initctl.socket        loaded active   listening /dev/initctl Compatibility Named Pipe
systemd-journald.socket       loaded active   running   Journal Socket
systemd-shutdownd.socket      loaded active   listening Delayed Shutdown Socket
systemd-udevd-control.socket  loaded active   running   udev Control Socket
systemd-udevd-kernel.socket   loaded active   running   udev Kernel Socket
That's it for now!

-----------------

Edit to add: I can seamlessly go to the GUI from the command line console, and it works well with this command:

Code: Select all

# systemctl isolate graphical.target
Image

And then to go back to the command line console, run the command:

Code: Select all

# systemctl isolate multi-user.target
Note: to set the command line as the default upon boot, instead of the GUI, run this command:

Code: Select all

# systemctl set-default multi-user.target

User avatar
avij
Retired Moderator
Posts: 3046
Joined: 2010/12/01 19:25:52
Location: Helsinki, Finland
Contact:

Re: How Green Was My Valley... err, My CentOS 7 (screenshots

Post by avij » 2015/09/03 12:32:11

InitOrNot wrote:
avij wrote:Note that you could have used the beta images of CentOS 7 i386 as well.
Oh, I didn't know the official i386 beta for CentOS 7 already existed, there is no word of it yet in the FAQ.

It's nice to know, thank you!
True, it's not there yet because it's still in beta. Once it gets officially released, it will be included in all appropriate documentation.

giulix63
Posts: 1305
Joined: 2014/05/14 10:06:37
Location: UK

Re: How Green Was My Valley... err, My CentOS 7 (screenshots

Post by giulix63 » 2015/09/03 13:00:05

Is this green enough? :D
Image
Root is evil: Do not use root (sudo) to run any of the commands specified in my posts unless explicitly indicated. Please, provide the necessary amount of context to understand your problem/question.

User avatar
InitOrNot
Posts: 122
Joined: 2015/06/10 18:26:51

Re: How Green Was My Valley... err, My CentOS 7 (screenshots

Post by InitOrNot » 2015/09/03 14:00:42

giulix63 wrote:Is this green enough? :D
Green enough it is, but not quite readable.

What about this? :mrgreen:

Image

Post Reply