I just installed CentOS 6.4 on my laptop and have a quick question. I'm extremely new to Linux and have never really worked on an actual Linux system before. I have some vision issues and am finding the default font size pretty difficult to see. Can anyone tell me how I can adjust the text size? I am using a text-based environment with no graphical desktop installed and like I said, I'm using CentOS 6.4
update
For anyone having this same problem, I thought I'd give a quick update to give y'all a couple different options I've discovered on how to fix this. If you're using a graphical desktop, the answer to this post is definitely a quick and easy fix. If you're working in a solely text-based environment, here's a command my professor gave me today that increases the font as well, however, this may only be for that particular session unless you add it to a configuration file, I haven't tested that though.
setfont sun12x22
Hope that helps anyone having the same issue :-)
You'll find your font options at System -> Preferences -> Fonts menu option
reference link http://www.techotopia.com/index.php/Configuring_CentOS_Desktop_Fonts
Suggestions for text based install https://www.centos.org/forums/viewtopic.php?t=2932
install yum install epel-release
install yum -y install terminus*
run command setfont ter-p18b
Here 18 is your font size(according to ur need),but this is not permanent,to make it permanent open /etc/rc.local in vi and write the setfont ter-p22b command in last line and save it.
Lastly give it all permissions by chmod +x /etc/rc.local and reboot,now it is default.
Word of caution:DO NOT MISHANDLE rc.local
Related
I am using the Linux Xfce machine provided for us by our professor which has Turkish keyboard layout. Every time I change the language, it changes for a while and then return back to the Turkish layout again, even if I remove the Turkish layout form the system!!
Is there any way to solve this problem? Any help would be appreciated.
The problem disappeared after running the following commands:
sudo apt-get install x11-xkb-utils
setxkbmap us
echo "setxkbmap us" >> ~/.bashrc
I found the answer here
I'm using the Atom editor. Yesterday, if I typed:
sudo atom . it opened the current directory as root
sudo atom it opened Atom with whatever I last had open as root
Today if I run either of those commands nothing happens. The editor doesn't open and there are no error messages.
These terminal commands worked yesterday on these exact same files, today they do not.
How can I fix this?
Why is this happening?
If I have not provided enough information it's because I don't know what info one would need to have a fuller explanation of my circumstance. Let me know what I should add I'll happily edit this question to provide it.
Atom : 1.13.0
Electron: 1.3.13
Chrome : 52.0.2743.82
Node : 6.5.0
Ubuntu 14.04 LTS
Elementary OS Freya (64-bit)
After updating Atom text editor it seems I require to run --no-sandbox flag but after a while it becomes boring so I wrote a simple BASH script to be doing this for me:
eval "atom --no-sandbox flag"
just save this in a common directory that you frequently use and type ./atom_text_editor.sh in the terminal to deploy(Depending on the name you choose for your script)
A recommendation, when working on linux avoid using sudo or su instrucctions, they are intended to execute privileged instructions like system configurations. It might be related to permissions, execute ls -al and verify that the owner/group of yor files is root, if not, then check if "others" have read permission, if not, then thats is the problem.
Be aware running atom with sudo is not recommended.
I've had this problem for a few days, I installed atom using snap (on ubuntu 18.04) a few weeks ago, back then it worked perfectly, but the last few days if i ran 'sudo atom' nothing would happen at all, reinstalled it using snap, still didn't work, removed settings, still didn't work.
I ended up installing atom using the apt packagage manager and now it works. I used this guide: https://codeforgeek.com/install-atom-editor-ubuntu-14-04/
Furthermore when running atom with sudo it should be ran with the --no-sandbox flag.
Conclusion: seems to be a problem with atom when installed using snap.
I am a linux noob trying to setup openbox on an arch linux base. I am trying to get it as lightweight as possible in terms of resources used.
My final plan is to use openbox, with tint1 and conky.
however I am having an issue getting openbox to start. I have followed numerous guides and am struggling to figure out the problem.
I have so far installed the following (and done this config)
openbox (installed default option with the extras asked for)
create ~/.conifg/openbox
copied, rc.xml, menu.xml, autostart, environment to the above location
pyxdg
xorg-xinit
xorg-server
this didn't work so I the installed the full
xorg
still nothing, although when I try to run startx the screen goes black for a second as though it is trying, but then goes back to text mode saying it has failed.
I have had a look at the attached log file, but I don't know enough to be able to interpret it properly.
log file: https://www.dropbox.com/s/r76fowkooi822y9/Xorg.log?dl=0
I would appreciate any assistance.
Thanks
Steve
still nothing, although when I try to run startx the screen goes black for a second as though it is trying, but then goes back to text mode saying it has failed.
what is it saying?
There is only one error: (EE) open /dev/fb0: Permission denied, try starting your environment with the same configuration as root - just to see if it works. Maybe its a problem related to rootless X.
Have you configured/checked your installation (xserver, graphics driver, xinit config) using the following guides?
https://wiki.archlinux.org/index.php/xorg
https://wiki.archlinux.org/index.php/xinitrc
Try to start a minimal X (As described in the xinitrc article) to see if your xserver and graphics driver is working correctly.
Recently I decided to delve into Vim after looking for a new text editor after adopting a Linux distro as a secondary operating system. I've installed Powerline as it seems the norm to do and for about 20 minutes I had it fully working (until I closed Vim), though after that (about a week ago) they failed to appear again (pretty sure they were just separators, not actual symbols - although that coming from me is entirely unqualified).
I've followed just about every fix I could find under the Sun, followed the documentation on font patching etc, nothing seems to be working.
I'm sure it's a stupidly easy fix and I'm just a bit too dull to find it, but hopefully I can fix it somehow as it's really, really bugging me.
Have a good Christmas!
PS. I just registered (I could've sworn I already had an account though apparently not), so I'm unable to post images. But I'll do my best to explain it: On the left of the status bar you have the mode, then next to that it the first symbol error (again, it might not even be a symbol error, I'm just going off what I think was my issue online), it's a rectangle (portrait) with 2B80 in it, after that there's the filename, and immediately after is the very same rectangle with the same code in it. But there are other errors as stated in the title such as 2B83 and 2B61, as well as just 28.
I'd imagine they are supposed to be separators as they're after every segment of the status bar, but I have no idea. I'm stumped.
Thanks for any/all help!
Apparently I was following some outdated instructions. This worked fine for me:
Completely remove anything I'd already done with the modification (a
fresh start)
sudo apt-get install python-pip
pip install --user git+git://github.com/Lokaltog/powerline
Add the following to your .vimrc
python from powerline.vim import setup as powerline_setup
python powerline_setup()
python del powerline_setup
set laststatus=2
call vundle#end() (only applicable if you use Vundle)
You should then download the latest version of the Powerline Symbols OpenType font (use the commands below)
cd ~
wget https://github.com/Lokaltog/powerline/raw/develop/font/PowerlineSymbols.otf
Move the downloadef file to one of your font directories (either ~/.local/share/fonts/ or ~/usr/local/share/fonts as ~/.fonts is deprecated and won't be used in future versions).
mv PowerlineSymbols.otf ~/.local/share/fonts
Update your system's font chahe
sudo fc-cache -f -v
Download and move the fontconfig file to ~/.fonts.conf
wget https://github.com/Lokaltog/powerline/raw/develop/font/10-powerline-symbols.conf
Create a per-user fontconfig folder if it doesn't already exist
mkdir -p ~/.config/fontconfig/fonts.conf
mv 10-powerline-symbols.conf ~/.config/fontconfig/fonts.conf/
Again, this worked for me, can't guarantee that it will for others but it certainly worked charms for me.
Is there a way to run conky in the terminal? I don't care about the graphics but I would like to have a window in screen that would effectively run as my 'conky' and display conky-like stats/scripts etc.
If this isn't possible, are there alternatives that do what I'm asking?
I found this Conky interface post which uses the out_to_console option. I don't really consider this a solution as I'm looking for something ncurses based.
There is a cli version of conky. On debian wheezy you can install it with:-
sudo apt-get install conky-cli
However, it will remove conky-std if you already have that installed.
Further googling 'conky ncurses' led me full circle back to conky's documentation http://conky.sourceforge.net/docs.html.
There is an out_to_ncurses option.
Based on this post http://www.linuxquestions.org/questions/linux-general-1/howto-live-life-in-a-text-based-world-856017/#post4234633 you need to set out_to_console and out_to_x to no to get it to work.
I simply took my working graphical conky and set out_to_console and out_to_x to no and out_to_ncurses to yes and commented out a line where I was setting the background image (not sure if this was necessary) and ran it and she worked like a charm!
HTH
N.B.: In the newer versions of conky, these argument take boolean values such as true or false instead of yes of no.