I'm having problems with the new version of emacs after I
upraded to Kubuntu 22.04. I can't seem to get superscripts
now. What other good and convenient editors are there under
Linux?
On 07/04/2023 11:03, db wrote:
I'm having problems with the new version of emacs after I
upraded to Kubuntu 22.04. I can't seem to get superscripts
now. What other good and convenient editors are there under
Linux?
Editing what?
I like notepadqq, texstudio, vscode, vi.
I'm having problems with the new version of emacs after I
upraded to Kubuntu 22.04. I can't seem to get superscripts
now.
What other good and convenient editors are there under
Linux?
I'm having problems with the new version of emacs after I
upraded to Kubuntu 22.04. I can't seem to get superscripts
now. What other good and convenient editors are there under
Linux?
On 07/04/2023 16:59, Pancho wrote:
On 07/04/2023 11:03, db wrote:
I'm having problems with the new version of emacs after I
upraded to Kubuntu 22.04. I can't seem to get superscripts
now. What other good and convenient editors are there under
Linux?
Editing what?
I like notepadqq, texstudio, vscode, vi.
Superscripts are probably a keyboard mapping issue
For coding, in a GUI, Geany. Joes Own Editor is nice in a console
And no, I edit 'sudoers' with nano ... works fine,
just get it RIGHT .....
I'm having problems with the new version of emacs after I
upraded to Kubuntu 22.04. I can't seem to get superscripts
now. What other good and convenient editors are there under
Linux?
On Fri, 7 Apr 2023 12:03:38 +0200, db wrote:
I'm having problems with the new version of emacs after I
upraded to Kubuntu 22.04. I can't seem to get superscripts
now. What other good and convenient editors are there under
Linux?
Before changing the editor, can you see superscript characters? Find one elsewhere and paste them into a text in the editor.
Found and fixed https://wiki.mageia.org/en/Local_Communities_Team
On Fri, 07 Apr 2023 19:38:11 -0400, 26B.X919 <26BX919@zoq21u.net> wrote:
And no, I edit 'sudoers' with nano ... works fine,
just get it RIGHT .....
Don't edit it directly. If you want to use nano, use
EDITOR="/usr/bin/nano" visudo
On 4/7/23 8:00 PM, David W. Hodgins wrote:
On Fri, 07 Apr 2023 19:38:11 -0400, 26B.X919 <26BX919@zoq21u.net> wrote:
And no, I edit 'sudoers' with nano ... works fine,
just get it RIGHT .....
Don't edit it directly. If you want to use nano, use
EDITOR="/usr/bin/nano" visudo
I've edited it directly for like 15 years.
If you get something wrong sudo will stop
working right so you know you screwed up.
Re-edit in root terminal.
Everyone can make a typo and not notice it soon enough. The visudo
command exists for a reason. Advising people to bypass it when you
don't know their setup or skill level is not appropriate.
On Sun, 09 Apr 2023 21:00:07 -0400, David W. Hodgins wrote:
Everyone can make a typo and not notice it soon enough. The visudo
command exists for a reason. Advising people to bypass it when you
don't know their setup or skill level is not appropriate.
+1
Like I've never fat-fingered any text while typing.... :-)
On Sun, 09 Apr 2023 20:18:03 -0400, 26B.X929 <26BX929@zoq22u.net> wrote:
On 4/7/23 8:00 PM, David W. Hodgins wrote:
On Fri, 07 Apr 2023 19:38:11 -0400, 26B.X919 <26BX919@zoq21u.net> wrote: >>>> And no, I edit 'sudoers' with nano ... works fine,
just get it RIGHT .....
Don't edit it directly. If you want to use nano, use
EDITOR="/usr/bin/nano" visudo
I've edited it directly for like 15 years.
If you get something wrong sudo will stop
working right so you know you screwed up.
Re-edit in root terminal.
It's bad advice to give. Some distributions do not allow login as root
(even from
a text login), or have the su command available. Using sudo is the only
way to do
things as root. If the bios/uefi has been set to only boot from the hard drive,
the only option would be to remove the hard drive and use another
install to edit
it. That too may be made impossible with hardware based encryption.
Everyone can make a typo and not notice it soon enough. The visudo
command exists
for a reason. Advising people to bypass it when you don't know their
setup or
skill level is not appropriate.
Regards, Dave Hodgins
BTW ... have you ever wondered about the POINT of sudo ???
If somebody finds your regular-user password then they can
also be root. So much for security. When building up a
server I'll use sudo a fair bit, but once everything's set
I remove the sudo privs. Meanwhile root has a DIFFERENT
password .....
26B.X929 <26BX929@zoq22u.net> wrote:
BTW ... have you ever wondered about the POINT of sudo ???
If somebody finds your regular-user password then they can
also be root. So much for security. When building up a
server I'll use sudo a fair bit, but once everything's set
I remove the sudo privs. Meanwhile root has a DIFFERENT
password .....
I've always wondered why you use your user-id password with
sudo. It sounds rather insecure. I seem to recall using
an older version of Unix where you had to give sudo the root
password. That makes more sense; you're doing things that
require root permission...
Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:
26B.X929 <26BX929@zoq22u.net> wrote:
BTW ... have you ever wondered about the POINT of sudo ???
If somebody finds your regular-user password then they can
also be root. So much for security. When building up a
server I'll use sudo a fair bit, but once everything's set
I remove the sudo privs. Meanwhile root has a DIFFERENT
password .....
I've always wondered why you use your user-id password with
sudo. It sounds rather insecure. I seem to recall using
an older version of Unix where you had to give sudo the root
password. That makes more sense; you're doing things that
require root permission...
It means you can revoke superuser privilege from a user without changing
and redistributing the root password.
On 4/10/23 11:37 AM, Allodoxaphobia wrote:
On Sun, 09 Apr 2023 21:00:07 -0400, David W. Hodgins wrote:
Everyone can make a typo and not notice it soon enough. The visudo
command exists for a reason. Advising people to bypass it when you
don't know their setup or skill level is not appropriate.
+1
Like I've never fat-fingered any text while typing.... :-)
I do also ... but his dire warnings have never come
true for me ever. I hate line editors - and REMOVE
'vi' so it can NEVER pop up.
On 2023-04-13, 26B.X929 <26BX929@zoq22u.net> wrote:
BTW ... have you ever wondered about the POINT of sudo ???
If somebody finds your regular-user password then they can
also be root. So much for security. When building up a
server I'll use sudo a fair bit, but once everything's set
I remove the sudo privs. Meanwhile root has a DIFFERENT
password .....
I've always wondered why you use your user-id password with
sudo. It sounds rather insecure. I seem to recall using
an older version of Unix where you had to give sudo the root
password. That makes more sense; you're doing things that
require root permission...
Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:
On 2023-04-13, 26B.X929 <26BX929@zoq22u.net> wrote:
BTW ... have you ever wondered about the POINT of sudo ???
If somebody finds your regular-user password then they can
also be root. So much for security. When building up a
server I'll use sudo a fair bit, but once everything's set
I remove the sudo privs. Meanwhile root has a DIFFERENT
password .....
I've always wondered why you use your user-id password with
sudo. It sounds rather insecure. I seem to recall using
an older version of Unix where you had to give sudo the root
password. That makes more sense; you're doing things that
require root permission...
A sudoer got his permissions from root.
In a multi-user environment, it allows other admins to tell who made
changes.
BTW ... have you ever wondered about the POINT of sudo ???
If somebody finds your regular-user password then they can
also be root.
On Thu, 13 Apr 2023 12:05:00 -0400, Dan Espen <dan1espen@gmail.com> wrote:
Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:
On 2023-04-13, 26B.X929 <26BX929@zoq22u.net> wrote:
BTW ... have you ever wondered about the POINT of sudo ???
If somebody finds your regular-user password then they can
also be root. So much for security. When building up a
server I'll use sudo a fair bit, but once everything's set
I remove the sudo privs. Meanwhile root has a DIFFERENT
password .....
I've always wondered why you use your user-id password with
sudo. It sounds rather insecure. I seem to recall using
an older version of Unix where you had to give sudo the root
password. That makes more sense; you're doing things that
require root permission...
A sudoer got his permissions from root.
In a multi-user environment, it allows other admins to tell who made
changes.
The big difference between sudo and su is that sudo allows granting limited permissions to some users.
For example, using the leafnode package sudo can be used to allow some regular users to run /usr/sbin/fetchnews as the user news to update
the local usenet cache. As those users enter their own password to confirm they are the ones controlling the terminal to run sudo, they don't need the root password that would give them full superuser privileges.
On 13/04/2023 09:01, Richard Kettlewell wrote:
Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:
26B.X929 <26BX929@zoq22u.net> wrote:
BTW ... have you ever wondered about the POINT of sudo ???
If somebody finds your regular-user password then they can
also be root. So much for security. When building up a
server I'll use sudo a fair bit, but once everything's set
I remove the sudo privs. Meanwhile root has a DIFFERENT
password .....
I've always wondered why you use your user-id password with
sudo. It sounds rather insecure. I seem to recall using
an older version of Unix where you had to give sudo the root
password. That makes more sense; you're doing things that
require root permission...
It means you can revoke superuser privilege from a user without changing
and redistributing the root password.
Yes. Its all horses for courses. Most of us here do not operate huge multiuser linux systems with multiple users that may need to be placed
in groups that need limited access to certain root privileges.
We want restricted access for normal usage to avoid fat fingers, and
the ability to easily circumvent that for the rare occasions we want to
edit system files and change the machine configuration.
Personally I add a root password to all my machines and often use su -
to gain a permanent root terminal for doing extensive editing of configs
etc.
But for occasional access - mounting file systems, installing into root privilege directiories etc -' sudo mount -a' or 'sudo make install' is perfectly fine.
Everyone can make a typo and not notice it soon enough. The visudo command >exists for a reason. Advising people to bypass it when you don't know
their setup or skill level is not appropriate.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 299 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 66:10:49 |
| Calls: | 6,691 |
| Calls today: | 1 |
| Files: | 12,228 |
| Messages: | 5,345,897 |
| Posted today: | 1 |