On 19/4/21 8:55 am, faeychild wrote:
To avoid the drama I decided to reinstall and use "Princeton"
All went well with the updates except for a dependency with mplayer.
Then I decided to install the nvidia driver and failed
************
Some requested packages cannot be installed
gcc-10.3.0-1.mga8.x86_64 (due to unsatisfied libisl.so.15()-
(64bit))
x11-driver-nvidia-video-current-460.67.mga8.nonfree.x86_64
(due to unsatisfied lib64nvidia-egl-wayland1)
**************
Last time the driver installed OK and the updates failed with dependencies
This time the updates went in fine and the driver failed with dependencies
Haven't bothered to install the printer again
It is an unpredictable mess
Is there a secret Masonic installation order in which things must be done?
I really HATE new releases
Going to guess a classic dvd iso was used.
Going to guess you did not install the above package for your kernel type.
Oh yeah, guessing you did not update ~/.bash_profile to generate
your ~/.signature file or you are posting from your Mga7 install.
On 19/4/21 5:59 pm, Bit Twister wrote:
Oh yeah, guessing you did not update ~/.bash_profile to generate
your ~/.signature file or you are posting from your Mga7 install.
That is one of the many little custom changes that must be done to a new setup.
$ ls -l .bash_profile
lrwxrwxrwx 1 bittwister bittwister 34 Feb 9 22:24 .bash_profile ->
/accounts/bittwister/.bash_profile
That way I do not have to modify $HOME/.bash_profile
On 19/4/21 8:28 pm, Bit Twister wrote:
$ ls -l .bash_profile
lrwxrwxrwx 1 bittwister bittwister 34 Feb 9 22:24 .bash_profile ->
/accounts/bittwister/.bash_profile
That way I do not have to modify $HOME/.bash_profile
Intelligent organization can work wonders, it just rarely happens.
For instance
https://doc.mageia.org/mcc/3/en/content/system-config-printer.html
Is a list of instructions to install a printer with MCC.
Almost at the bottom of the page it states
************
"You should install Brother drivers before running the configuration
utility"
************
Yes! of course. Surely that's the first instruction, I would have thought.
I am getting much better at the procedure through practice
Yeah, I used to have a checklist, until it dawned on me instead of documenting what to do when, I could just put the commands in a script.
On 20/4/21 12:36 pm, Bit Twister wrote:
Yeah, I used to have a checklist, until it dawned on me instead of
documenting what to do when, I could just put the commands in a script.
It has severely crossed my mind occasionally.
The other customization that I forget until I shutdown the new install
is to add MY shutdown permission to the sudoers file - sigh
I have just run into a dependency issue with the updating MGA8.
This after the peculiar printer install routine was not comforting.
But I am aware from a previous similar event that the mirror was
probably updating and I should have checked first
When I get back to it I'll try Princeton or Whitby.
The status page show them to be a little more reliably current
Intelligent organization can work wonders, it just rarely happens.
For instance
https://doc.mageia.org/mcc/3/en/content/system-config-printer.html
Is a list of instructions to install a printer with MCC.
Almost at the bottom of the page it states
************
"You should install Brother drivers before running the configuration utility"
************
Yes! of course. Surely that's the first instruction, I would have thought.
I am getting much better at the procedure through practice
Personally, I've stumbled enough times in my life that I've learned that it's usually best to read docs like that page all the way through at
least once before attempting a procedure.
On Tue, 20 Apr 2021 13:11:11 +1000, faeychild wrote:
I can recommend using a drop-in file whenever possible. Those are files
in a .d/ directory and have the changes/directives that you want to add/change/delete.
sudoers man page indicates you can create directory /etc/sudoers.d/ if /etc/sudoers has "#includedir /etc/sudoers.d". Easy check, run
tail -3 /etc/sudoers
On 21/4/21 1:12 am, TJ wrote:
Personally, I've stumbled enough times in my life that I've learned
that it's usually best to read docs like that page all the way
through at least once before attempting a procedure.
Absolutely!
There is a classic recipe for Rabbit stew
It describes the preparation of the vegetables and how to fry the
onions and saute the vegetables. Herbs and seasoning.
The length of simmering and reduction.
Oh!! And first, catch a Rabbit
That par is easy. Just go into the woods, hide behind a tree and
imitate the sound of a carrot. :p
It is less perilous work than "vi /etc/sudoers" and it could also be
farmed out through a link
Note that you don't have to use vi. From man sudoedit in the environment section ...
EDITOR Default editor to use in -e (sudoedit) mode if neither
SUDO_EDITOR nor VISUAL is set.
I use ...
$ env|grep EDITOR
EDITOR=/usr/bin/mcedit
On 21/4/21 12:08 pm, David W. Hodgins wrote:
Note that you don't have to use vi. From man sudoedit in the environment
section ...
EDITOR Default editor to use in -e (sudoedit) mode if neither
SUDO_EDITOR nor VISUAL is set.
I use ...
$ env|grep EDITOR
EDITOR=/usr/bin/mcedit
~]$ env|grep EDITOR
[faeychild@unimatrix ~]$
Not set
And I was reminded by the man page that I should use visudo not vi
It's so infrequent that I forget
FYI:
EDITOR defines which editor to use on files.
VISUAL defines which editor commands to use on the command line
Some apps allow you to have a application editor.
$ env | grep -iE "vis|edit"
EDITOR=geany
SLRN_EDITOR=geany
VISUAL=emacs
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 371 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 175:45:15 |
| Calls: | 7,915 |
| Files: | 12,983 |
| Messages: | 5,797,774 |