CentOS

jlehtone wrote: ↑

2021/05/15 15:51:19

The yum-config-manager is fully functional unless the input data is garbage.

Your are totally right. I plead guilty of not RTFM.

You probably never do that, so feel free to throw the first stone.

Anyway, I sincerely appreciate the help you provided to a poor sinner. Thanx again.

The "solution" posted above, based on yum-config-manager, doesn't work at all. Why ? because the enable/disable function needs a line with "enabled =" in the target section. yum-config-manager doesn't add such a line if it is missing. So my final solution is, so far :-( for f in /etc/yum.repos.d/Cen...

Yum-utils has tool for it: sudo yum-config-manager --disable base updates extras It works, but it disables all repos having sections like [base] [updates] [extra], so it disables my custom repos too. Luckily there is an option (-c) to specify the config file. One at time, because it fails on duplic...

TrevorH wrote: ↑

2021/05/15 03:29:00

It will however, put them back if they are removed.

That's my problem. But I see an easy solution : let these files in place and edit them enable=1 => enable=0.

Do you see a better solution ?

Dear All, In my /etc/yum.repos.d directory, the default .repo files (e.g. CentOS-Base.repo) are replaced by custom files pointing to a local repository. Sometimes, when doing an update, yum reinstalls the default .repo files. Is there a way to protect the content of /etc/yum.repos.d while keeping th...

Basically where I'd put TERM=xterm-256color, now I put TERM=ansi-256color, and nvim works w/o that annoying prompt issue. I solved it with TERM=konsole. ;) After that, another problem showed up : adding "set paste" in my "init.vim" broke the default "statusline" (no more line/column). For 20+ years...

known bug
https://github.com/neovim/neovim/issues/11393

Hello All, On a fresh install of neovim (0.3.0), when I type ':' to go to the command line, I get the normal colon character followed by the letter 'q'. I get a command line beginning with ':q' instead of ':' This letter has no effect on the command entered. That is - if I press the Enter key, I go ...

Solved for me with Use at your own risk.

what's the purpose of plymouth once the system has booted ?