top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

How to configure the resolution of text console to standard 80x24 for centos 7?

+2 votes
624 views
posted Oct 23, 2014 by Sidharth

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes

Add 'vga=F00' (those are zeros) to your kernel lines and it'll use 80x25 for the non-X VGA console.

answer Oct 23, 2014 by Deepankar Dubey
Similar Questions
0 votes
systemd: SIGPWR handler for Centos 7.2?

It seems that sigpwr.target is just a dummy. Something
like
kill -PWR 1
or
systemctl isolate sigpwr.target

is visible in the journal, but it does not power down the host.

This breaks a clean shutdown of LXContainers setup with Centos 7.2. I would guess there are problems with UPS monitors, too.

Is there a workaround?

+1 vote
How to set hostname and domain name in CentOS 7?

We can permanently set hostname using hostnamectl set-hostname. How can we permanently set domain name in CentOS 7?
I found an article (http://unix.stackexchange.com/questions/239920/how-to-set-the-fully-qualified-hostname-on-centos-7-0 ) that recommended setting FQDN using hostnamectl. Is that the right way to set hostname and domainname at the same time using hostnamectl set-hostname command?

Running hostnamectl set-hostname will set the hostname in /etc/hostname but it doesn't change /etc/hosts. What's the proper way of adding hostname and FQDN to /etc/hosts in CentOS 7?

0 votes
CentOS 7: System log has repeated lines: Started session 123 of user root.

The system log (/var/log/messages) of a CentOS 7.2 system has frequently-repeated message line pairs like:

Jul 18 14:00:01 localhost systemd: Started Session 307 of user root.
Jul 18 14:00:01 localhost systemd: Starting Session 307 of user root.

where the session number increases each time.

Looking around on this, e.g. Red Hat Bugzilla bug 727315, it looks like it's when crond starts a task; it looks like it might be fixed - I would think that would be in CentOS but don't know how to find/compare the Fedora and CentOS systemd versions to know for sure.

I found a post on a workaround - in /etc/systemd/system.conf to change the line:

#LogLevel=info

to:

LogLevel=notice

I did that and rebooted, and it has stopped the messages.

I'm worried though that this may have knocked out something of actual interest from the syslog.

So my question is, is there a better way? A way that info messages could go to some other log, or better yet, a way that those particular "session" messages, and only those, could go to some other log or be filtered out?

...