Re: sudo echo 1 > /proc/sys/net/ipv4/ip_forward [was: How to run automatically a script as soon root login]

[tomas]

On Tue, May 14, 2024 at 04:54:26PM +0800, Bret Busby wrote:
> 
> Wasn't sudo echo the name of a pop group?
> 
> :)

If it wasn't it should've been one.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: sudo echo 1 > /proc/sys/net/ipv4/ip_forward [was: How to run automatically a script as soon root login]

[Bret Busby]

Wasn't sudo echo the name of a pop group?

:)



Bret Busby
Armadale
Western Australia
(UTC+0800)
.

Re: sudo echo 1 > /proc/sys/net/ipv4/ip_forward [was: How to run automatically a script as soon root login]

[tomas]

On Mon, May 13, 2024 at 08:37:16PM +0200, Erwan David wrote:
> Le 13/05/2024 à 19:45, Stefan Monnier a écrit :

[...]

> >      % sudo zsh -l
> >  # echo 1 > /proc/sys/net/ipv4/ip_forward
> >  # ^D
> >  logout
> >  %
> > 
> > 
> > 
> > 
> >  Stefan
> > 
> > 
> sudo -i will do the job instead of sudo zsh -l

...provided Stefan's shell in /etc/passwd is set to
zsh, that is :)

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: sudo echo 1 > /proc/sys/net/ipv4/ip_forward [was: How to run automatically a script as soon root login]

[Erwan David]

Le 13/05/2024 à 19:45, Stefan Monnier a écrit :

$ su -
Password:
# echo 1 > /proc/sys/net/ipv4/ip_forward
# ^D
logout
$

I don't need no stinkin' sudo :-)

And if you only have `sudo`, but not the root password, of course:

 % sudo zsh -l
 # echo 1 > /proc/sys/net/ipv4/ip_forward
 # ^D
 logout
 %




 Stefan



sudo -i will do the job instead of sudo zsh -l

Re: sudo echo 1 > /proc/sys/net/ipv4/ip_forward [was: How to run automatically a script as soon root login]

[tomas]

On Mon, May 13, 2024 at 01:45:40PM -0400, Stefan Monnier wrote:
> > $ su -
> > Password:
> > # echo 1 > /proc/sys/net/ipv4/ip_forward
> > # ^D
> > logout
> > $
> >
> > I don't need no stinkin' sudo :-)
> 
> And if you only have `sudo`, but not the root password, of course:
> 
> % sudo zsh -l
> # echo 1 > /proc/sys/net/ipv4/ip_forward
> # ^D
> logout
> %

Or just "sudo -s", which will invoke "your" favourite shell. Or "sudo -i",
which will do roughly the same (-s looks first at $SHELL, then at passwd,
-i looks at passwd and invokes a login shell).

> 

I always forget how my fave shell is spelt ;-)

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: sudo echo 1 > /proc/sys/net/ipv4/ip_forward [was: How to run automatically a script as soon root login]

[Stefan Monnier]

> $ su -
> Password:
> # echo 1 > /proc/sys/net/ipv4/ip_forward
> # ^D
> logout
> $
>
> I don't need no stinkin' sudo :-)

And if you only have `sudo`, but not the root password, of course:

% sudo zsh -l
# echo 1 > /proc/sys/net/ipv4/ip_forward
# ^D
logout
%




Stefan

Re: sudo echo 1 > /proc/sys/net/ipv4/ip_forward [was: How to run automatically a script as soon root login]

[Christian Groessler]

On 5/13/24 18:52, to...@tuxteam.de wrote:


Now share your ideas :-)



$ su -
Password:
# echo 1 > /proc/sys/net/ipv4/ip_forward
# ^D
logout
$


I don't need no stinkin' sudo :-)

regards,
chris

sudo echo 1 > /proc/sys/net/ipv4/ip_forward [was: How to run automatically a script as soon root login]

[tomas]

Since this happens so often, I'm trying to offer a recap.

As others have noted, the above

  sudo echo 1 > /proc/sys/net/ipv4/ip_forward

won't work, since it runs echo under sudo, but the file opening
(that pesky ">") happens in your shell, which is probably running
unprivileged (otherwise, what do you need the sudo for, anyway?)

Others have rightfully noticed that, in this case, sysctl possibly
is the more appropriate tool for the job.

Barring that -- what is to do?

One solution put forward was to wrap a whole shell in the sudo:

  sudo sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward"

Of course, you can (gasp!) wrap a whole xterm which invokes a
shell (why not go the full thing and wrap LibreOffice Calc? It
surely has a shell escape hidden somewhere ;-)

Another solution is to find a program which would be willing
to open a named file for you and sudo that one.

A common choice would be tee (which in this case has the side
effect of dumping the desired output *also* to stdout:

  echo 1 | sudo tee /proc/sys/net/ipv4/ip_forward

(also outputs 1 to stdout). Less common, but my personal favourite
is dd, which is free of that side effect (it's harmless enough
when it's just an "1", but if longer data is involved...):

  echo 1 | sudo dd of=/proc/sys/net/ipv4/ip_forward

(note that dd's default if is stdin).

Now share your ideas :-)

Cheers
-- 
t


signature.asc
Description: PGP signature

Debian 12.5 i386 sudo returns "Illegal instruction"

[Vic tor]

> The new minimum requirement is i686.

> Debian requires i686 compatibility - even when the arch is being
displayed as i386 due to compatibility reasons.

Thank you for your insights. I'll have to pay more attention to the release
notes in the future. I have mourned the loss of my Soekris boxes and
am over it.

Re: Debian 12.5 i386 sudo returns "Illegal instruction"

[Marco Moock]

Am 25.04.2024 schrieb Vic tor :

> On a fresh installation of Debian 12.5, i386 I receive "Illegal
> instruction" when executing sudo. Is there any way to debug and
> workaround this; should I take this to another list as a bug?

Here it is described with gdb:
https://stackoverflow.com/questions/10354147/find-which-assembly-instruction-caused-an-illegal-instruction-error-without-debu

> This is on a Soekris net5501 powered by an AMD Geode LX which is the
> only oddball factor.

Debian requires i686 compatibility - even when the arch is being
displayed as i386 due to compatibility reasons.

According to this thread, the Geode LX lacks some i686 instructions.
https://lists.debian.org/debian-user/2019/04/msg01093.html

Re: Debian 12.5 i386 sudo returns "Illegal instruction"

[Greg Wooledge]

On Thu, Apr 25, 2024 at 09:54:17AM -0400, Vic tor wrote:
> On a fresh installation of Debian 12.5, i386 I receive "Illegal instruction"
> when executing sudo. Is there any way to debug and workaround this; should I
> take this to another list as a bug?
> 
> This is on a Soekris net5501 powered by an AMD Geode LX which is the only
> oddball factor. I've been running Debian on these guys since version 8 without
> any problem.

https://www.debian.org/releases/stable/i386/release-notes/ch-information.en.html#i386-is-i686

  Debian's support for 32-bit PC (known as the Debian architecture i386)
  now no longer covers any i586 processor. The new minimum requirement
  is i686. What this means that the i386 architecture now requires the
  "long NOP" (NOPL) instruction, while bullseye still supported some
  i586 processors without that instruction (e.g. the "AMD Geode").

  If your machine is not compatible with this requirement, it is
  recommended that you stay with bullseye for the remainder of its
  support cycle.

Debian 12.5 i386 sudo returns "Illegal instruction"

[Vic tor]

On a fresh installation of Debian 12.5, i386 I receive "Illegal instruction"
when executing sudo. Is there any way to debug and workaround this; should I
take this to another list as a bug?

This is on a Soekris net5501 powered by an AMD Geode LX which is the only
oddball factor. I've been running Debian on these guys since version 8 without
any problem.

Re: sudo udisksctl

[David Wright]

On Mon 19 Feb 2024 at 23:53:41 (+0700), Max Nikulin wrote:
> David, feel free to stop discussion if you find me annoying. My
> problem in some sense is close to your one and I am trying to figure
> out if missed some udisks feature and the result is some
> inconvenience.
> 
> On 19/02/2024 11:26, David Wright wrote:
> > On Sun 18 Feb 2024 at 12:41:29 (+0700), Max Nikulin wrote:
> > > On 18/02/2024 11:40, David Wright wrote:
> > > > $ udisksctl unlock --block-device /dev/disk/by-partlabel/Nokia01
> > 
> > > When sudo is
> > > involved, I still do not see any advantage of udisk[s]ctl over
> > > "cryptsetup open".
> > 
> > I'd be more worried about disadvantages. About the only difference
> > I see is that   cryptsetup open   requires a name.
> 
> I find it convenient to have a meaningful name in /dev/mapper in
> addition to /dev/dm-X. So I would not call it pure disadvantage.

True, it makes the NAME in lsblk shorter. But the only time I've
defined a name is when opening the partition tocreate the filesystem:

  # cryptsetup --align-payload 2048 luksFormat /dev/sdz9

  WARNING!
  
  This will overwrite data on /dev/sdb1 irrevocably.

  Are you sure? (Type uppercase yes): YES
  Enter passphrase:
  Verify passphrase:
  # cryptsetup luksAddKey /dev/sdz9
  Enter any existing passphrase:
  Enter new passphrase for key slot:
  Verify passphrase:
  # cryptsetup open --type luks /dev/sdz9 thename
  Enter passphrase for /dev/sdz9:
  # ls -l /dev/mapper/
  total 0
  crw--- 1 root root 10, 236 Aug 18 10:35 control
  lrwxrwxrwx 1 root root   7 Aug 18 10:35 thename -> ../dm-0
  # ls -l /dev/dm-0
  brw-rw 1 root disk 254, 0 Aug 18 10:35 /dev/dm-0
  # mkfs.ext4 -L name09 /dev/mapper/thename
  mke2fs 1.44.5 (15-Dec-2018)
  Creating filesystem with 10598 4k blocks and 26492928 inodes
  Filesystem UUID: 3c832120-d40a-4998-b927-1318eb1e17f8
  Superblock backups stored on blocks:
  32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 
2654208,
  4096000, 7962624, 11239424, 2048, 23887872, 71663616, 78675968,
  10240

  Allocating group tables: done
  Writing inode tables: done
  Creating journal (262144 blocks): done
  Writing superblocks and filesystem accounting information: done

  # e2label /dev/mapper/thename name09 (if forgotten above).
  # 

[ … creating, chown-ing, chmod-ing top-level directories ]

  # cryptsetup luksClose thename
  # 

> > > As third option, if I remember it correctly, pmount
> > 
> > That would be pointless for me. After udev creates correctly-named
> > mountpoints using my rules, entries in fstab set the appropriate
> > flags for each individual device. That contradicts the expressed main
> > purpose of pmount: "permits normal users to mount removable devices
> > without a matching /etc/fstab entry." — precisely what I don't want.
> 
> I consider pmount as a tool does not need separate unlock and mount
> commands, so a shell function becomes unnecessary. In respect to
> permissions (for removable drives) it acts as a substitute for sudo.
> 
> I expected that you need to mount a partition under /media into the
> directory with name taken from filesystem LABEL. If so then udisksd
> can do it and /etc/fstab entry is unnecessary. You anyway added an
> udev rule. The following one should change mountpoint from
> /media/$USER/lulu01 to /media/lulu01
> 
> SUBSYSTEM=="block", ENV{ID_FS_LABEL}=="lulu01",
> ENV{UDISKS_FILESYSTEM_SHARED}="1"
> 
> It seems that mixing of udisksctl and non-udisksctl commands can be avoided.

I hadn't thought about that as an issue. I've just chosen, for
each step, the method that's most convenient (for me). See:

  https://lists.debian.org/debian-user/2024/01/msg00737.html

for some details of the first step, which I won't duplicate here.
I group-control the directory /etc/udev/rules.d/my-mountpoints,
hence all the 59 entries.

For decrypting, I use either the PARTLABEL or the device-ID. The
latter's useful for sticks and cards that I wipe more frequently,
which makes the other symlinks variable over time.

For mounting, I use fstab entries because they have the flags defined,
rather than putting them in the mount command. When I need to mount
with sudo, the flags include a private x-mysudo flag, which is picked
up by my wrapper around mount. (The bash function that started this
discussion doesn't say "mount /media/lulu01" but "mmm /media/lulu01".)

Unmounting is also wrapped, not just for sudo, but because it contains
a script to updatedb (for locate), ls -lR (for mc), and create a
listing (using find) that lists modification time, size and filename
in a customised format. After any locking, the three products are
automatically transferred to my other hosts to keep them up-to-date.

It probably all looks hackish to someone running a multiuser system.

Cheers,
David.

Re: sudo udisksctl

[Max Nikulin]

David, feel free to stop discussion if you find me annoying. My problem 
in some sense is close to your one and I am trying to figure out if 
missed some udisks feature and the result is some inconvenience.


On 19/02/2024 11:26, David Wright wrote:

On Sun 18 Feb 2024 at 12:41:29 (+0700), Max Nikulin wrote:

On 18/02/2024 11:40, David Wright wrote:

$ udisksctl unlock --block-device /dev/disk/by-partlabel/Nokia01



When sudo is
involved, I still do not see any advantage of udisk[s]ctl over
"cryptsetup open".


I'd be more worried about disadvantages. About the only difference
I see is that   cryptsetup open   requires a name.


I find it convenient to have a meaningful name in /dev/mapper in 
addition to /dev/dm-X. So I would not call it pure disadvantage.



As third option, if I remember it correctly, pmount


That would be pointless for me. After udev creates correctly-named
mountpoints using my rules, entries in fstab set the appropriate
flags for each individual device. That contradicts the expressed main
purpose of pmount: "permits normal users to mount removable devices
without a matching /etc/fstab entry." — precisely what I don't want.


I consider pmount as a tool does not need separate unlock and mount 
commands, so a shell function becomes unnecessary. In respect to 
permissions (for removable drives) it acts as a substitute for sudo.


I expected that you need to mount a partition under /media into the 
directory with name taken from filesystem LABEL. If so then udisksd can 
do it and /etc/fstab entry is unnecessary. You anyway added an udev 
rule. The following one should change mountpoint from 
/media/$USER/lulu01 to /media/lulu01


SUBSYSTEM=="block", ENV{ID_FS_LABEL}=="lulu01", 
ENV{UDISKS_FILESYSTEM_SHARED}="1"


It seems that mixing of udisksctl and non-udisksctl commands cat be avoided.

Re: sudo udisksctl

[David Wright]

On Sun 18 Feb 2024 at 12:41:29 (+0700), Max Nikulin wrote:
> On 18/02/2024 11:40, David Wright wrote:
> >$ ssh bhost
> >$ udisksctl unlock --block-device /dev/disk/by-partlabel/Nokia01
> >Passphrase:
> > AUTHENTICATING FOR org.freedesktop.udisks2.encrypted-unlock ===
> >Authentication is required to unlock the encrypted device Multiple Card  
> > Reader (/dev/sdc1)
> 
> It should be possible to modify policy to allow a specific user or a
> group to perform disk operations, see polkit(8).

This is basically a single-user network here, and I simplify matters
by keeping all the permitted privileged operations in one place,
under sudoers.d/. I'm happy to let policykit look after the way that
system components work together, but I'm not interested in getting
involved in that stuff myself. The flexibility in configuration,
desirable in multiuser systems, comes with a learning curve that
I'm not interested in climbing.

> When sudo is
> involved, I still do not see any advantage of udisk[s]ctl over
> "cryptsetup open".

I'd be more worried about disadvantages. About the only difference
I see is that   cryptsetup open   requires a name.

> As third option, if I remember it correctly, pmount
> relies on group membership, not on systemd-logind "uaccess", so local
> vs. remote user should not matter. This variant combines unlock and
> mount into a single command.

That would be pointless for me. After udev creates correctly-named
mountpoints using my rules, entries in fstab set the appropriate
flags for each individual device. That contradicts the expressed main
purpose of pmount: "permits normal users to mount removable devices
without a matching /etc/fstab entry." — precisely what I don't want.

Cheers,
David.

Re: sudo udisksctl

[Max Nikulin]

On 18/02/2024 11:40, David Wright wrote:

   $ ssh bhost
   $ udisksctl unlock --block-device /dev/disk/by-partlabel/Nokia01
   Passphrase:
    AUTHENTICATING FOR org.freedesktop.udisks2.encrypted-unlock ===
   Authentication is required to unlock the encrypted device Multiple Card  
Reader (/dev/sdc1)


It should be possible to modify policy to allow a specific user or a 
group to perform disk operations, see polkit(8). When sudo is involved, 
I still do not see any advantage of udiskctl over "cryptsetup open". As 
third option, if I remember it correctly, pmount relies on group 
membership, not on systemd-logind "uaccess", so local vs. remote user 
should not matter. This variant combines unlock and mount into a single 
command.

Re: sudo udisksctl

[David Wright]

On Sun 18 Feb 2024 at 10:23:52 (+0700), Max Nikulin wrote:
> I have decided to ask the following in a separate thread.
> 
> On 17/02/2024 02:59, David Wright wrote
> (Re: f3tools vs Silicon Power 4T drive):
> >   lulu ()   { sudo udisksctl unlock --block-device
> > /dev/disk/by-partlabel/Lulu01 && mount /media/lulu01
> >   }
> 
> I am evaluating if udisks2 D-Bus API allows to create a tool as
> convenient as pmount(1) that is smart enough to unlock a device before
> mounting it (optionally with specified name of mountpoint)
> 
> pmount /dev/sda1 mybackup
> 
> I have puzzled by your function however. I believed that udisks was
> created to allow *regular* users to mount drives. If you are using
> sudo why do not you use "cryptsetup open" directly? Otherwise
> udisksctl can ask password if policy does not allow disk operations
> for the current user.
> 
> P.S. Unfortunately mount name is hardcoded in udisksd. It is either
> label or UUID, it can not be specified when a partition is mounted.

Because policykit allows me to unlock partitions only if they're
local. I rely on being able to unlock partitions remotely. For
example, if I wakeonlan the PC in the basement, I need to be able
to unlock its /home before I can login as myself.

As a demonstration:

  $ hostname
  bhost
  $ udisksctl unlock --block-device /dev/disk/by-partlabel/Nokia01
  Passphrase: 
  Unlocked /dev/sdc1 as /dev/dm-2.
  $ udisksctl lock --block-device /dev/disk/by-partlabel/Nokia01
  Locked /dev/sdc1.
  $ 

is fine, but ssh to a laptop and back to this machine:

  $ ssh ahost
  Linux ahost 5.10.0-27-amd64 #1 SMP Debian 5.10.205-2 (2023-12-31) x86_64
  [ … ]
  You have new mail.
  Last login: Sun Feb 18 04:18:39 2024 from 192.168.1.14
  $ ssh bhost
  Linux bhost 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31) x86_64
  [ … ]
  You have new mail.
  Last login: Sun Feb 18 04:18:44 2024 from 192.168.1.16
  $ udisksctl unlock --block-device /dev/disk/by-partlabel/Nokia01
  Passphrase: 
   AUTHENTICATING FOR org.freedesktop.udisks2.encrypted-unlock ===
  Authentication is required to unlock the encrypted device Multiple Card  
Reader (/dev/sdc1)
  Authenticating as: root
  Password: 
  [ pressed ^C ]

That's what I'm avoiding with sudo.

Cheers,
David.

sudo udisksctl

[Max Nikulin]

I have decided to ask the following in a separate thread.

On 17/02/2024 02:59, David Wright wrote
(Re: f3tools vs Silicon Power 4T drive):
  lulu () 
  { 
sudo udisksctl unlock --block-device /dev/disk/by-partlabel/Lulu01 && mount /media/lulu01

  }


I am evaluating if udisks2 D-Bus API allows to create a tool as 
convenient as pmount(1) that is smart enough to unlock a device before 
mounting it (optionally with specified name of mountpoint)


pmount /dev/sda1 mybackup

I have puzzled by your function however. I believed that udisks was 
created to allow *regular* users to mount drives. If you are using sudo 
why do not you use "cryptsetup open" directly? Otherwise udisksctl can 
ask password if policy does not allow disk operations for the current user.


P.S. Unfortunately mount name is hardcoded in udisksd. It is either 
label or UUID, it can not be specified when a partition is mounted.

Re: AW: AW: su su- sudo dont work

[chris]

Bump?

On Wed, Feb 14, 2024 at 3:29 PM chris  wrote:

> Yes there are many updated kernels to choose from. Please go ahead and do
> so
>
>
>
> On Sat, Feb 10, 2024 at 8:21 AM Schwibinger Michael 
> wrote:
>
>> Yes.
>>
>>
>> I found out
>> I do use an old kernel.
>>
>> Can LINUX update a kernel?
>>
>> Regards
>> Sophie
>>
>>
>> --
>> *Von:* chris 
>> *Gesendet:* Mittwoch, 7. Februar 2024 19:35
>> *An:* Schwibinger Michael 
>> *Betreff:* Re: AW: AW: su su- sudo dont work
>>
>> Very helpful ty
>>
>> On Wed, Feb 7, 2024, 1:57 PM Schwibinger Michael 
>> wrote:
>>
>> Good afternoon.
>>
>> The bug report
>>
>> sudo ...
>> You are not in the sudoers file.
>> Regards
>> Sophie
>>
>>
>> --
>> *Von:* Hans 
>> *Gesendet:* Freitag, 26. Januar 2024 18:44
>> *An:* debian-user@lists.debian.org 
>> *Betreff:* Re: AW: AW: su su- sudo dont work
>>
>>
>> Am Freitag, 26. Januar 2024, 17:23:07 CET schrieben Sie:
>>
>> Yes, if you want to install soemthing for example by using the apt
>> command, best way is becoming root with the command "su -" and then install
>> the rquired package.
>>
>>
>> Example:
>>
>> su -  then enter the password of the user root
>>
>>
>> If installing for example firefox, first read the repository:
>>
>>
>> apt update
>>
>>
>> then install the package
>>
>>
>> apt install firefox-esr
>>
>>
>> -
>>
>>
>> Hint: If you want a graphical method and you have no X and Wndow-Manager
>> running (like KDE, Gnome, XFCE whatever), I suggest using aptitude.
>>
>>
>> You have to install aptitude first:
>>
>>
>> apt install aptitude
>>
>>
>> Then you can start the gui with the command "aptitude" as root.
>>
>>
>> Hint 2: aptitude is controlled by keypresses without any enter-key.
>>
>> For example, when started aptitude, just press the "u" key and it reads
>> the update, "U" (Shift + u)  marks all newer packages automatically to be
>> updated, then press "g" and you will shwo, what it will do. Press "g"
>> again, and it will do the update.
>>
>>
>> Please note: If you want to upgrade the whole sytem, then using apt or
>> apt-get will be the better choice!
>>
>>
>> But aptitude is very well for installing single packages or weekly
>> upgrades, where not much packages will be renewed.
>>
>>
>> If you are not much experienced, and you have a window-manager running
>> like KDE, Gnome, XFCE, LXDE or another one, then look at synaptic. Synaptic
>> is a graphical tool for installing packages, it is a GUI for apt.
>>
>>
>> Synaptic MUST run as root.
>>
>>
>> Hope this helps.
>>
>>
>> By the way: I believe, you are not very experienced in English language,
>> so I suggest to suscribe in the fine German forum,
>>
>> which is debian-user-ger...@lists.debioan.org.
>>
>>
>> Here is the link:
>>
>> https://lists.debian.org/debian-user-german/
>>
>>
>> Good luck!
>>
>>
>> Hans
>>
>>
>>
>> > Sorry
>>
>> > it was my mistake
>>
>> >
>>
>> > It is
>>
>> >
>>
>> > su -
>>
>> > su
>>
>> > or sudo.
>>
>> >
>>
>> > Sorry.
>>
>> >
>>
>> > Is su -
>>
>> > the best for install?
>>
>> >
>>
>> > Regards
>>
>> >
>>
>> > Sophie
>>
>> >
>>
>> >
>>
>> > 
>>
>> >
>>
>>

Re: AW: AW: su su- sudo dont work

[chris]

Yes there are many updated kernels to choose from. Please go ahead and do so



On Sat, Feb 10, 2024 at 8:21 AM Schwibinger Michael 
wrote:

> Yes.
>
>
> I found out
> I do use an old kernel.
>
> Can LINUX update a kernel?
>
> Regards
> Sophie
>
>
> --
> *Von:* chris 
> *Gesendet:* Mittwoch, 7. Februar 2024 19:35
> *An:* Schwibinger Michael 
> *Betreff:* Re: AW: AW: su su- sudo dont work
>
> Very helpful ty
>
> On Wed, Feb 7, 2024, 1:57 PM Schwibinger Michael  wrote:
>
> Good afternoon.
>
> The bug report
>
> sudo ...
> You are not in the sudoers file.
> Regards
> Sophie
>
>
> --
> *Von:* Hans 
> *Gesendet:* Freitag, 26. Januar 2024 18:44
> *An:* debian-user@lists.debian.org 
> *Betreff:* Re: AW: AW: su su- sudo dont work
>
>
> Am Freitag, 26. Januar 2024, 17:23:07 CET schrieben Sie:
>
> Yes, if you want to install soemthing for example by using the apt
> command, best way is becoming root with the command "su -" and then install
> the rquired package.
>
>
> Example:
>
> su -  then enter the password of the user root
>
>
> If installing for example firefox, first read the repository:
>
>
> apt update
>
>
> then install the package
>
>
> apt install firefox-esr
>
>
> -
>
>
> Hint: If you want a graphical method and you have no X and Wndow-Manager
> running (like KDE, Gnome, XFCE whatever), I suggest using aptitude.
>
>
> You have to install aptitude first:
>
>
> apt install aptitude
>
>
> Then you can start the gui with the command "aptitude" as root.
>
>
> Hint 2: aptitude is controlled by keypresses without any enter-key.
>
> For example, when started aptitude, just press the "u" key and it reads
> the update, "U" (Shift + u)  marks all newer packages automatically to be
> updated, then press "g" and you will shwo, what it will do. Press "g"
> again, and it will do the update.
>
>
> Please note: If you want to upgrade the whole sytem, then using apt or
> apt-get will be the better choice!
>
>
> But aptitude is very well for installing single packages or weekly
> upgrades, where not much packages will be renewed.
>
>
> If you are not much experienced, and you have a window-manager running
> like KDE, Gnome, XFCE, LXDE or another one, then look at synaptic. Synaptic
> is a graphical tool for installing packages, it is a GUI for apt.
>
>
> Synaptic MUST run as root.
>
>
> Hope this helps.
>
>
> By the way: I believe, you are not very experienced in English language,
> so I suggest to suscribe in the fine German forum,
>
> which is debian-user-ger...@lists.debioan.org.
>
>
> Here is the link:
>
> https://lists.debian.org/debian-user-german/
>
>
> Good luck!
>
>
> Hans
>
>
>
> > Sorry
>
> > it was my mistake
>
> >
>
> > It is
>
> >
>
> > su -
>
> > su
>
> > or sudo.
>
> >
>
> > Sorry.
>
> >
>
> > Is su -
>
> > the best for install?
>
> >
>
> > Regards
>
> >
>
> > Sophie
>
> >
>
> >
>
> > 
>
> >
>
>

Can Linux update an old kernel [WAS Re: AW: AW: AW: su su- sudo dont work]

[Andrew M.A. Cater]

On Sat, Feb 10, 2024 at 01:21:55PM +, Schwibinger Michael wrote:
> Yes.
> 
> 
> I found out
> I do use an old kernel.
> 
> Can LINUX update a kernel?
> 

Hi Sophie,

Yes, of course. As root/sudo user, apt-get update ; apt-get dist-upgrade

But you still don't give anybody any actual *details*

All best, as ever,

Andy

> Regards
> Sophie
> 
> 
> 
> Von: chris 
> Gesendet: Mittwoch, 7. Februar 2024 19:35
> An: Schwibinger Michael 
> Betreff: Re: AW: AW: su su- sudo dont work
> 
> Very helpful ty
> 
> On Wed, Feb 7, 2024, 1:57 PM Schwibinger Michael 
> mailto:h...@hotmail.com>> wrote:
> Good afternoon.
> 
> The bug report
> 
> sudo ...
> You are not in the sudoers file.
> Regards
> Sophie
> 
> 
> 
> Von: Hans mailto:hans.ullr...@loop.de>>
> Gesendet: Freitag, 26. Januar 2024 18:44
> An: debian-user@lists.debian.org<mailto:debian-user@lists.debian.org> 
> mailto:debian-user@lists.debian.org>>
> Betreff: Re: AW: AW: su su- sudo dont work
> 
> 
> Am Freitag, 26. Januar 2024, 17:23:07 CET schrieben Sie:
> 
> Yes, if you want to install soemthing for example by using the apt command, 
> best way is becoming root with the command "su -" and then install the 
> rquired package.
> 
> 
> Example:
> 
> su -  then enter the password of the user root
> 
> 
> If installing for example firefox, first read the repository:
> 
> 
> apt update
> 
> 
> then install the package
> 
> 
> apt install firefox-esr
> 
> 
> -
> 
> 
> Hint: If you want a graphical method and you have no X and Wndow-Manager 
> running (like KDE, Gnome, XFCE whatever), I suggest using aptitude.
> 
> 
> You have to install aptitude first:
> 
> 
> apt install aptitude
> 
> 
> Then you can start the gui with the command "aptitude" as root.
> 
> 
> Hint 2: aptitude is controlled by keypresses without any enter-key.
> 
> For example, when started aptitude, just press the "u" key and it reads the 
> update, "U" (Shift + u)  marks all newer packages automatically to be 
> updated, then press "g" and you will shwo, what it will do. Press "g" again, 
> and it will do the update.
> 
> 
> Please note: If you want to upgrade the whole sytem, then using apt or 
> apt-get will be the better choice!
> 
> 
> But aptitude is very well for installing single packages or weekly upgrades, 
> where not much packages will be renewed.
> 
> 
> If you are not much experienced, and you have a window-manager running like 
> KDE, Gnome, XFCE, LXDE or another one, then look at synaptic. Synaptic is a 
> graphical tool for installing packages, it is a GUI for apt.
> 
> 
> Synaptic MUST run as root.
> 
> 
> Hope this helps.
> 
> 
> By the way: I believe, you are not very experienced in English language, so I 
> suggest to suscribe in the fine German forum,
> 
> which is 
> debian-user-ger...@lists.debioan.org<mailto:debian-user-ger...@lists.debioan.org>.
> 
> 
> Here is the link:
> 
> https://lists.debian.org/debian-user-german/
> 
> 
> Good luck!
> 
> 
> Hans
> 
> 
> 
> > Sorry
> 
> > it was my mistake
> 
> >
> 
> > It is
> 
> >
> 
> > su -
> 
> > su
> 
> > or sudo.
> 
> >
> 
> > Sorry.
> 
> >
> 
> > Is su -
> 
> > the best for install?
> 
> >
> 
> > Regards
> 
> >
> 
> > Sophie
> 
> >
> 
> >
> 
> > 
> 
> >

AW: AW: AW: su su- sudo dont work

[Schwibinger Michael]

Yes.


I found out
I do use an old kernel.

Can LINUX update a kernel?

Regards
Sophie



Von: chris 
Gesendet: Mittwoch, 7. Februar 2024 19:35
An: Schwibinger Michael 
Betreff: Re: AW: AW: su su- sudo dont work

Very helpful ty

On Wed, Feb 7, 2024, 1:57 PM Schwibinger Michael 
mailto:h...@hotmail.com>> wrote:
Good afternoon.

The bug report

sudo ...
You are not in the sudoers file.
Regards
Sophie



Von: Hans mailto:hans.ullr...@loop.de>>
Gesendet: Freitag, 26. Januar 2024 18:44
An: debian-user@lists.debian.org<mailto:debian-user@lists.debian.org> 
mailto:debian-user@lists.debian.org>>
Betreff: Re: AW: AW: su su- sudo dont work


Am Freitag, 26. Januar 2024, 17:23:07 CET schrieben Sie:

Yes, if you want to install soemthing for example by using the apt command, 
best way is becoming root with the command "su -" and then install the rquired 
package.


Example:

su -  then enter the password of the user root


If installing for example firefox, first read the repository:


apt update


then install the package


apt install firefox-esr


-


Hint: If you want a graphical method and you have no X and Wndow-Manager 
running (like KDE, Gnome, XFCE whatever), I suggest using aptitude.


You have to install aptitude first:


apt install aptitude


Then you can start the gui with the command "aptitude" as root.


Hint 2: aptitude is controlled by keypresses without any enter-key.

For example, when started aptitude, just press the "u" key and it reads the 
update, "U" (Shift + u)  marks all newer packages automatically to be updated, 
then press "g" and you will shwo, what it will do. Press "g" again, and it will 
do the update.


Please note: If you want to upgrade the whole sytem, then using apt or apt-get 
will be the better choice!


But aptitude is very well for installing single packages or weekly upgrades, 
where not much packages will be renewed.


If you are not much experienced, and you have a window-manager running like 
KDE, Gnome, XFCE, LXDE or another one, then look at synaptic. Synaptic is a 
graphical tool for installing packages, it is a GUI for apt.


Synaptic MUST run as root.


Hope this helps.


By the way: I believe, you are not very experienced in English language, so I 
suggest to suscribe in the fine German forum,

which is 
debian-user-ger...@lists.debioan.org<mailto:debian-user-ger...@lists.debioan.org>.


Here is the link:

https://lists.debian.org/debian-user-german/


Good luck!


Hans



> Sorry

> it was my mistake

>

> It is

>

> su -

> su

> or sudo.

>

> Sorry.

>

> Is su -

> the best for install?

>

> Regards

>

> Sophie

>

>

> 

>

Re: AW: AW: su su- sudo dont work

[chris]

Nobody has ever used it no

On Wed, Feb 7, 2024, 2:17 PM Schwibinger Michael  wrote:

>
> Good afternoon
>
> I did send the bugreport.
>
> Thank You.
> Did anybody use the rescue mode?
>
> Regards Sophie
>
>
> --
> *Von:* Andrew M.A. Cater 
> *Gesendet:* Mittwoch, 31. Januar 2024 20:36
> *An:* debian-user@lists.debian.org ;
> Schwibinger Michael 
> *Betreff:* Re: AW: AW: su su- sudo dont work
>
> On Wed, Jan 31, 2024 at 01:58:41PM +, Schwibinger Michael wrote:
> > Good afternoon
> > I think
> > maybe Im sure
> > it is because of rescue mode.
> >
> Hi Sophie,
>
> Once again: we need to you to show us what commands you run.
>
> We need to see error messages.
>
> if you cannot run sudo or su, we need you to run the id command
> as previously suggested.
>
> We have literally nothing of use from you to help any of us problem
> solve. This is throwing good effort away in persuading you to help us.
>
> Also - please address requests first to the list and not to individuals -
> it makes it a lot easier to follow on the list.
>
> > Normal booting did not have this problem.
> >
> > Anybody familiar with panic?
> >
> > Regards
> > Thank You
> > Sophie
> >
> Andy
> >
> > 
> > Von: Andrew M.A. Cater 
> > Gesendet: Donnerstag, 25. Januar 2024 18:40
> > An: debian-user@lists.debian.org 
> > Betreff: Re: AW: su su- sudo dont work
> >
> > On Thu, Jan 25, 2024 at 03:53:10PM +, Schwibinger Michael wrote:
> > > Good afternoon
> > > Why do I have to open a group?
> > >
> >
> > This is to *tell* us information about why you're having problems with su
> > and sudo
> >
> > Running the
> >
> > id
> >
> > command should give you information like
> >
> > uid=1000(amacater) gid=1000(amacater) groups=1000(amacater),27(sudo)
> >
> > which shows you that my user - amacater - is the first user on the
> > machine (because Debian starts user id numbers at 1000 for ordinary
> > users) and that I'm a member of group sudo - so can use sudo instead of
> su.
> >
> > /etc/sudoers will show you what privileges the sudo user has.
> > Here are the last lines of the file on my machine (which has not been
> > modified from Debian defaults)
> >
> > # User privilege specification
> > rootALL=(ALL:ALL) ALL
> >
> > # Allow members of group sudo to execute any command
> > %sudo   ALL=(ALL:ALL) ALL
> >
> > # See sudoers(5) for more information on "@include" directives:
> >
> > @includedir /etc/sudoers.d
> > (END)
> >
> > If you are _not_ a user of group sudo for whatever reason - and want to
> > use sudo - then you will need root privileges and the root password
> > (once) to add your user name to the group.
> >
> > For example: adduser sophie sudo
> >
> > I hope this helps
> >
> > > 2 years ago
> > > sudo was no problem.
> > >
> >
> > As yet, we have *no idea* what you have done in the last two years to
> > break your Debian system - or even to know which kernel you boot or
> > how you "rescue" your system when you log onto it every day.
> >
> > Please give us information in order that the readers on this list can
> > use their knowledge to help you.
> >
> > With every good wish, as ever,
> >
> > Andy
> > (amaca...@debian.org)
> > > Regards
> > >
> > > Sophie
> > >
> > > Thank You
> > > 
> > > Von: Timothy M Butterworth 
> > > Gesendet: Montag, 22. Januar 2024 00:07
> > > An: Schwibinger Michael 
> > > Cc: Greg Wooledge ; debian-user@lists.debian.org <
> debian-user@lists.debian.org>
> > > Betreff: Re: su su- sudo dont work
> > >
> > >
> > >
> > > On Sun, Jan 21, 2024 at 4:07 PM Schwibinger Michael  <mailto:h...@hotmail.com>> wrote:
> > > Thank You
> > > Example
> > > I say
> > >
> > > sudo apt-get install firefox
> > > Reaction LINUX
> > > This is not allowed we send a message to the admin.
> > >
> > > This error message means that your account is not in the sudo group.
> > >
> > > Run the command "groups" and look for the group sudo.
> > > groups
> > >
> > > Here is the command to add a user account to the sudo group. You will
> need to run it as root.

Re: AW: AW: su su- sudo dont work

[chris]

Very helpful ty

On Wed, Feb 7, 2024, 1:57 PM Schwibinger Michael  wrote:

> Good afternoon.
>
> The bug report
>
> sudo ...
> You are not in the sudoers file.
> Regards
> Sophie
>
>
> --
> *Von:* Hans 
> *Gesendet:* Freitag, 26. Januar 2024 18:44
> *An:* debian-user@lists.debian.org 
> *Betreff:* Re: AW: AW: su su- sudo dont work
>
>
> Am Freitag, 26. Januar 2024, 17:23:07 CET schrieben Sie:
>
> Yes, if you want to install soemthing for example by using the apt
> command, best way is becoming root with the command "su -" and then install
> the rquired package.
>
>
> Example:
>
> su -  then enter the password of the user root
>
>
> If installing for example firefox, first read the repository:
>
>
> apt update
>
>
> then install the package
>
>
> apt install firefox-esr
>
>
> -
>
>
> Hint: If you want a graphical method and you have no X and Wndow-Manager
> running (like KDE, Gnome, XFCE whatever), I suggest using aptitude.
>
>
> You have to install aptitude first:
>
>
> apt install aptitude
>
>
> Then you can start the gui with the command "aptitude" as root.
>
>
> Hint 2: aptitude is controlled by keypresses without any enter-key.
>
> For example, when started aptitude, just press the "u" key and it reads
> the update, "U" (Shift + u)  marks all newer packages automatically to be
> updated, then press "g" and you will shwo, what it will do. Press "g"
> again, and it will do the update.
>
>
> Please note: If you want to upgrade the whole sytem, then using apt or
> apt-get will be the better choice!
>
>
> But aptitude is very well for installing single packages or weekly
> upgrades, where not much packages will be renewed.
>
>
> If you are not much experienced, and you have a window-manager running
> like KDE, Gnome, XFCE, LXDE or another one, then look at synaptic. Synaptic
> is a graphical tool for installing packages, it is a GUI for apt.
>
>
> Synaptic MUST run as root.
>
>
> Hope this helps.
>
>
> By the way: I believe, you are not very experienced in English language,
> so I suggest to suscribe in the fine German forum,
>
> which is debian-user-ger...@lists.debioan.org.
>
>
> Here is the link:
>
> https://lists.debian.org/debian-user-german/
>
>
> Good luck!
>
>
> Hans
>
>
>
> > Sorry
>
> > it was my mistake
>
> >
>
> > It is
>
> >
>
> > su -
>
> > su
>
> > or sudo.
>
> >
>
> > Sorry.
>
> >
>
> > Is su -
>
> > the best for install?
>
> >
>
> > Regards
>
> >
>
> > Sophie
>
> >
>
> >
>
> > 
>
> >
>

Request for output of commands [WAS Re: AW: AW: AW: su su- sudo dont work]

[Andrew M.A. Cater]

On Wed, Feb 07, 2024 at 02:15:06PM +, Schwibinger Michael wrote:
> 
> Good afternoon
> 
> I did send the bugreport.
> 
> Thank You.
> Did anybody use the rescue mode?
> 
> Regards Sophie
> 
> 
> 
> Von: Andrew M.A. Cater 
> Gesendet: Mittwoch, 31. Januar 2024 20:36
> An: debian-user@lists.debian.org ; Schwibinger 
> Michael 
> Betreff: Re: AW: AW: su su- sudo dont work
> 
> On Wed, Jan 31, 2024 at 01:58:41PM +, Schwibinger Michael wrote:
> > Good afternoon
> > I think
> > maybe Im sure
> > it is because of rescue mode.
> >
> Hi Sophie,
> 
> Once again: we need to you to show us what commands you run.
> 
> We need to see error messages.
> 
> if you cannot run sudo or su, we need you to run the id command
> as previously suggested.
> 

Where is the output of the id command?

The other message you quote suggests that you aren't in the sudo group

*Show the error messages*


> Also - please address requests first to the list and not to individuals -
> it makes it a lot easier to follow on the list.
> 

>From the output of my mailer: you sent first to me, copy to the list -
could you please do this the other way round as requested. It is more
important for the list to see this - and it also means that there is
no personal reply sent to the list by mistake: any personal reply is
intended as such.

> > Normal booting did not have this problem.
> >
> > Anybody familiar with panic?
> >

Yes: a (kernel) panic can have many causes: if you can give us meaningful
responses, we may be able to help. In the absence of these, you only
get guesses - wheich may or may not be helpful.

Again, as previously requested, please use meaningful subjects on your
emails so that we can deal with one issue at a time.

Andy
(amaca...@debian.org)


> > Regards
> > Thank You
> > Sophie
> >
> Andy
> >
> > 
> > Von: Andrew M.A. Cater 
> > Gesendet: Donnerstag, 25. Januar 2024 18:40
> > An: debian-user@lists.debian.org 
> > Betreff: Re: AW: su su- sudo dont work
> >
> > On Thu, Jan 25, 2024 at 03:53:10PM +, Schwibinger Michael wrote:
> > > Good afternoon
> > > Why do I have to open a group?
> > >
> >
> > This is to *tell* us information about why you're having problems with su
> > and sudo
> >
> > Running the
> >
> > id
> >
> > command should give you information like
> >
> > uid=1000(amacater) gid=1000(amacater) groups=1000(amacater),27(sudo)
> >
> > which shows you that my user - amacater - is the first user on the
> > machine (because Debian starts user id numbers at 1000 for ordinary
> > users) and that I'm a member of group sudo - so can use sudo instead of su.
> >
> > /etc/sudoers will show you what privileges the sudo user has.
> > Here are the last lines of the file on my machine (which has not been
> > modified from Debian defaults)
> >
> > # User privilege specification
> > rootALL=(ALL:ALL) ALL
> >
> > # Allow members of group sudo to execute any command
> > %sudo   ALL=(ALL:ALL) ALL
> >
> > # See sudoers(5) for more information on "@include" directives:
> >
> > @includedir /etc/sudoers.d
> > (END)
> >
> > If you are _not_ a user of group sudo for whatever reason - and want to
> > use sudo - then you will need root privileges and the root password
> > (once) to add your user name to the group.
> >
> > For example: adduser sophie sudo
> >
> > I hope this helps
> >
> > > 2 years ago
> > > sudo was no problem.
> > >
> >
> > As yet, we have *no idea* what you have done in the last two years to
> > break your Debian system - or even to know which kernel you boot or
> > how you "rescue" your system when you log onto it every day.
> >
> > Please give us information in order that the readers on this list can
> > use their knowledge to help you.
> >
> > With every good wish, as ever,
> >
> > Andy
> > (amaca...@debian.org)
> > > Regards
> > >
> > > Sophie
> > >
> > > Thank You
> > > 
> > > Von: Timothy M Butterworth 
> > > Gesendet: Montag, 22. Januar 2024 00:07
> > > An: Schwibinger Michael 
> > > Cc: Greg Wooledge ; debian-user@lists.debian.org 
> > > 
> > > Betreff: Re: su su- sudo dont work
> > >
> > >
> > >
> > > On Sun, Jan 21, 2024 at 4:07 PM Schwibinger Michael 
> > > mailto

AW: AW: AW: su su- sudo dont work

[Schwibinger Michael]

Good afternoon

I did send the bugreport.

Thank You.
Did anybody use the rescue mode?

Regards Sophie



Von: Andrew M.A. Cater 
Gesendet: Mittwoch, 31. Januar 2024 20:36
An: debian-user@lists.debian.org ; Schwibinger 
Michael 
Betreff: Re: AW: AW: su su- sudo dont work

On Wed, Jan 31, 2024 at 01:58:41PM +, Schwibinger Michael wrote:
> Good afternoon
> I think
> maybe Im sure
> it is because of rescue mode.
>
Hi Sophie,

Once again: we need to you to show us what commands you run.

We need to see error messages.

if you cannot run sudo or su, we need you to run the id command
as previously suggested.

We have literally nothing of use from you to help any of us problem
solve. This is throwing good effort away in persuading you to help us.

Also - please address requests first to the list and not to individuals -
it makes it a lot easier to follow on the list.

> Normal booting did not have this problem.
>
> Anybody familiar with panic?
>
> Regards
> Thank You
> Sophie
>
Andy
>
> 
> Von: Andrew M.A. Cater 
> Gesendet: Donnerstag, 25. Januar 2024 18:40
> An: debian-user@lists.debian.org 
> Betreff: Re: AW: su su- sudo dont work
>
> On Thu, Jan 25, 2024 at 03:53:10PM +, Schwibinger Michael wrote:
> > Good afternoon
> > Why do I have to open a group?
> >
>
> This is to *tell* us information about why you're having problems with su
> and sudo
>
> Running the
>
> id
>
> command should give you information like
>
> uid=1000(amacater) gid=1000(amacater) groups=1000(amacater),27(sudo)
>
> which shows you that my user - amacater - is the first user on the
> machine (because Debian starts user id numbers at 1000 for ordinary
> users) and that I'm a member of group sudo - so can use sudo instead of su.
>
> /etc/sudoers will show you what privileges the sudo user has.
> Here are the last lines of the file on my machine (which has not been
> modified from Debian defaults)
>
> # User privilege specification
> rootALL=(ALL:ALL) ALL
>
> # Allow members of group sudo to execute any command
> %sudo   ALL=(ALL:ALL) ALL
>
> # See sudoers(5) for more information on "@include" directives:
>
> @includedir /etc/sudoers.d
> (END)
>
> If you are _not_ a user of group sudo for whatever reason - and want to
> use sudo - then you will need root privileges and the root password
> (once) to add your user name to the group.
>
> For example: adduser sophie sudo
>
> I hope this helps
>
> > 2 years ago
> > sudo was no problem.
> >
>
> As yet, we have *no idea* what you have done in the last two years to
> break your Debian system - or even to know which kernel you boot or
> how you "rescue" your system when you log onto it every day.
>
> Please give us information in order that the readers on this list can
> use their knowledge to help you.
>
> With every good wish, as ever,
>
> Andy
> (amaca...@debian.org)
> > Regards
> >
> > Sophie
> >
> > Thank You
> > 
> > Von: Timothy M Butterworth 
> > Gesendet: Montag, 22. Januar 2024 00:07
> > An: Schwibinger Michael 
> > Cc: Greg Wooledge ; debian-user@lists.debian.org 
> > 
> > Betreff: Re: su su- sudo dont work
> >
> >
> >
> > On Sun, Jan 21, 2024 at 4:07 PM Schwibinger Michael 
> > mailto:h...@hotmail.com>> wrote:
> > Thank You
> > Example
> > I say
> >
> > sudo apt-get install firefox
> > Reaction LINUX
> > This is not allowed we send a message to the admin.
> >
> > This error message means that your account is not in the sudo group.
> >
> > Run the command "groups" and look for the group sudo.
> > groups
> >
> > Here is the command to add a user account to the sudo group. You will need 
> > to run it as root.
> > usermod -a -G sudo 
> >
> > I do open root terminal
> > there its working.
> > Regards
> > Sophie
> >
> > 
> > Von: Greg Wooledge mailto:g...@wooledge.org>>
> > Gesendet: Samstag, 20. Januar 2024 14:14
> > An: debian-user@lists.debian.org<mailto:debian-user@lists.debian.org> 
> > mailto:debian-user@lists.debian.org>>
> > Betreff: Re: su su- sudo dont work
> >
> > On Sat, Jan 20, 2024 at 01:26:06PM +, Schwibinger Michael wrote:
> > > Good afternoon.
> > > Root terminal is fine.
> > > What do I do wrong?
> > > What did I destroy?
> > >
> > > PC does have only one user=admin.
> > >
> > > Regar

AW: AW: AW: su su- sudo dont work

[Schwibinger Michael]

Its no fun
its not dangerous.
I do use the root terminal.

I dont use my real name in www,
to much SPAM then.

Regards
Sophie

Problem is cause of the panic.


Von: Andy Smith 
Gesendet: Samstag, 27. Januar 2024 09:47
An: debian-user@lists.debian.org 
Betreff: Re: AW: AW: su su- sudo dont work

Hi Hans,

On Sat, Jan 27, 2024 at 10:23:09AM +0100, Hans wrote:
> I see this exactly as you and are watching this list for may years.

I'm not sure who you're replying to as you've removed those details,
though I may guess from your In-Reply-To header which doesn't point
to a list message. You haven't replied to an off-list (personal)
mail back onto the list have you? Be careful there!

> But since the beginning, I had the suspicion, that someone just
> wants to make fun with us.

It is hard to understand how what Michael/Sophie/Tobias does can in
any way be "fun" for them, though maybe that is just our lack of
understanding.

Either they are incredibly confused by Linux or they are pretending
to be for reasons beyond my understanding. Whatever the case, I
don't think I have ever seen one of their threads result in a
positive resolution.

It's probably best to not assume that what we don't understand is
hostile and/or an AI experiment. Even so, that doesn't mean it is
possible to help.

Thanks,
Andy

--
https://bitfolk.com/ -- No-nonsense VPS hosting

AW: AW: AW: su su- sudo dont work

[Schwibinger Michael]

Good afternoon.

The bug report

sudo ...
You are not in the sudoers file.
Regards
Sophie



Von: Hans 
Gesendet: Freitag, 26. Januar 2024 18:44
An: debian-user@lists.debian.org 
Betreff: Re: AW: AW: su su- sudo dont work


Am Freitag, 26. Januar 2024, 17:23:07 CET schrieben Sie:

Yes, if you want to install soemthing for example by using the apt command, 
best way is becoming root with the command "su -" and then install the rquired 
package.


Example:

su -  then enter the password of the user root


If installing for example firefox, first read the repository:


apt update


then install the package


apt install firefox-esr


-


Hint: If you want a graphical method and you have no X and Wndow-Manager 
running (like KDE, Gnome, XFCE whatever), I suggest using aptitude.


You have to install aptitude first:


apt install aptitude


Then you can start the gui with the command "aptitude" as root.


Hint 2: aptitude is controlled by keypresses without any enter-key.

For example, when started aptitude, just press the "u" key and it reads the 
update, "U" (Shift + u)  marks all newer packages automatically to be updated, 
then press "g" and you will shwo, what it will do. Press "g" again, and it will 
do the update.


Please note: If you want to upgrade the whole sytem, then using apt or apt-get 
will be the better choice!


But aptitude is very well for installing single packages or weekly upgrades, 
where not much packages will be renewed.


If you are not much experienced, and you have a window-manager running like 
KDE, Gnome, XFCE, LXDE or another one, then look at synaptic. Synaptic is a 
graphical tool for installing packages, it is a GUI for apt.


Synaptic MUST run as root.


Hope this helps.


By the way: I believe, you are not very experienced in English language, so I 
suggest to suscribe in the fine German forum,

which is debian-user-ger...@lists.debioan.org.


Here is the link:

https://lists.debian.org/debian-user-german/


Good luck!


Hans



> Sorry

> it was my mistake

>

> It is

>

> su -

> su

> or sudo.

>

> Sorry.

>

> Is su -

> the best for install?

>

> Regards

>

> Sophie

>

>

> 

>

Re: AW: AW: su su- sudo dont work

[Timothy M Butterworth]

On Fri, Feb 2, 2024 at 7:17 PM Schwibinger Michael  wrote:

> Good afternoon
>
> Before there was panic
>
> su
> su -
> sudo
> did work.
>
> Somebody does have experience with
> rescue mode?
>

If you are in Single User Mode you are already root and do not need: su or
sudo.



> Regards
> Sophie
>
>
> --
> *Von:* Greg Wooledge 
> *Gesendet:* Freitag, 26. Januar 2024 17:45
> *An:* debian-user@lists.debian.org 
> *Betreff:* Re: AW: AW: su su- sudo dont work
>
> On Fri, Jan 26, 2024 at 04:23:07PM +, Schwibinger Michael wrote:
> > su -
> > su
> > or sudo.
> >
> > Is su -
> > the best for install?
>
> Whatever works best for *you* is best.  "su -" is quite popular.
> If it does what you need, and is convenient for you, then there's
> your answer.
>
>

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

AW: AW: AW: su su- sudo dont work

[Schwibinger Michael]

Good afternoon

Before there was panic

su
su -
sudo
did work.

Somebody does have experience with
rescue mode?

Regards
Sophie



Von: Greg Wooledge 
Gesendet: Freitag, 26. Januar 2024 17:45
An: debian-user@lists.debian.org 
Betreff: Re: AW: AW: su su- sudo dont work

On Fri, Jan 26, 2024 at 04:23:07PM +, Schwibinger Michael wrote:
> su -
> su
> or sudo.
>
> Is su -
> the best for install?

Whatever works best for *you* is best.  "su -" is quite popular.
If it does what you need, and is convenient for you, then there's
your answer.

Re: su su- sudo dont work

[CL]

Am 27.01.24 um 10:23 schrieb Hans:

I see this exactly as you and are watching this list for may years.

However, I wanted not to be so directly because I want not to blame anyone on
this list.

But since the beginning, I had the suspicion, that someone just wants to make
fun with us.

Aleady from the beginning I checked after the mail adress (please note, I am
German myself) and found some theater group behind the mailadress.

So I personally(!) believe, the group is making fun with us, but even then I
gave him a chance.

And again I personally(!) (and this is my very personal opinion), I think,
nobody is so stupid, that he/she can not do a su or install a package. NOT
after 2 years!!!

For me, I will get no help here for this person, just ignore it. This is my
very personal decision!

Sorry to say it, but for me personally it looks like fake! Like a morone, like
a troll.

And those I can not support, sorry.

Please excuse, I do not want to hurt anyone, just tell, what I think.

Best regards

Hans


I see very similar posts in the German language list from the last two
years but as Tobias Schwibingerr or similar - also signed by a Sophie

When I asked this question some time ago, it seems that the German language
list had concluded that this person might be a troll (or even a psychology
experiment / AI) :(

Like you, I have attempted to engage - but I think none of us will see
any change - I think the German list pays no attention / may have blocked
this user.






Hello,

I agree completely with you.

Follow this list for appr. one year now and this "person" (Michael 
Schwibinger / Sophie / ???) pop up every couple of month.


He/She works always with the same "scam".

1. Came up with a simple sounding cry for help (Computer / OS destroyed 
or something else)
2. React on questions for clarification with stupid and even more 
confusing answers


What I notice that every popup it is a little bit better with the 
answers. They stay stupid and unrelated but the are more wordy.


So I think at the moment it is a troll who works with AI to generate 
some answers. But this is of course my personal opinion.


For a real psychological experiment the design of the experiment is much 
to poor.


I decided for me not care on threads which are based on a message of 
this persons.


The most disappointing thing is that there is no possibility to block 
such "contributors". As I know. Even a block won't really help. They 
might start with a new email in the same way again.



--
---
mit freundlichen Grüßen / Best Regards

**Christian Lorenz**

mailto:cl.debian.mail...@t-online.de
---

Re: su su- sudo dont work

[Christian Lorenz]

Yes,

He/She is back again.

In my opinion no serious request intended by this "person".

Same approach as last time (and the issues before)

* crying for help (destroyed OS)
* no real answers to questions
* repeating the same complain frequently


Some possibilities

1. Shity AI
2. Troll
3. Bored child
4. 
5. ...

I think best thing: ignore it latest after the first fail response to a clear 
quedtion.



--- 
Mit freundlichen Grüßen / Best Regards

**Christian Lorenz**

mailto:cl.debian.mail...@t-online.de
--- 

Am 20. Januar 2024 15:34:16 MEZ schrieb David Wright :
>On Sat 20 Jan 2024 at 09:14:30 (-0500), Greg Wooledge wrote:
>> On Sat, Jan 20, 2024 at 01:26:06PM +, Schwibinger Michael wrote:
>> > Good afternoon.
>> > Root terminal is fine.
>> > What do I do wrong?
>> > What did I destroy?
>> > 
>> > PC does have only one user=admin.
>> > 
>> > Regards Sophie
>> > Is it the rescue mode?
>> 
>> Explain, please.
>> 
>> Your Subject: header says "su su- sudo dont work".  What does this MEAN?
>> 
>> Please show us your attempts to USE each of these commands, and the
>> results that you got.  This means, run the commands in a terminal
>> window, and then PASTE the contents of that terminal window into the
>> body of your next email.  Show us the shell prompt, the command as you
>> typed it, and the full output.
>> 
>> In other words, show us WHAT IS WRONG, or at least what appears wrong.
>> 
>> In addition, please give basic background information -- what version
>> of Debian you are running, what desktop environment if any, how you
>> logged in (*especially* if it isn't just a "standard graphical login
>> for your desktop environment"), and anything else you can think of
>> that might be relevant.
>> 
>> How does "rescue mode" factor into the problem?
>> 
>> When you installed Debian, did you give a root password, or did you
>> leave it blank?
>> 
>> Finally, it would be helpful for you to run the "id" command (with no
>> arguments), in the same terminal session as your failed su or sudo
>> command(s), and include that command and its output in your paste.
>
>Welcome to the world of déjà vu.
>
>  https://lists.debian.org/debian-user/2022/07/msg00601.html
>
>Cheers,
>David.
>

Re: AW: AW: su su- sudo dont work

[Andrew M.A. Cater]

On Wed, Jan 31, 2024 at 01:58:41PM +, Schwibinger Michael wrote:
> Good afternoon
> I think
> maybe Im sure
> it is because of rescue mode.
> 
Hi Sophie,

Once again: we need to you to show us what commands you run.

We need to see error messages.

if you cannot run sudo or su, we need you to run the id command
as previously suggested.

We have literally nothing of use from you to help any of us problem
solve. This is throwing good effort away in persuading you to help us.

Also - please address requests first to the list and not to individuals -
it makes it a lot easier to follow on the list.

> Normal booting did not have this problem.
> 
> Anybody familiar with panic?
> 
> Regards
> Thank You
> Sophie
> 
Andy
> 
> 
> Von: Andrew M.A. Cater 
> Gesendet: Donnerstag, 25. Januar 2024 18:40
> An: debian-user@lists.debian.org 
> Betreff: Re: AW: su su- sudo dont work
> 
> On Thu, Jan 25, 2024 at 03:53:10PM +, Schwibinger Michael wrote:
> > Good afternoon
> > Why do I have to open a group?
> >
> 
> This is to *tell* us information about why you're having problems with su
> and sudo
> 
> Running the
> 
> id
> 
> command should give you information like
> 
> uid=1000(amacater) gid=1000(amacater) groups=1000(amacater),27(sudo)
> 
> which shows you that my user - amacater - is the first user on the
> machine (because Debian starts user id numbers at 1000 for ordinary
> users) and that I'm a member of group sudo - so can use sudo instead of su.
> 
> /etc/sudoers will show you what privileges the sudo user has.
> Here are the last lines of the file on my machine (which has not been
> modified from Debian defaults)
> 
> # User privilege specification
> rootALL=(ALL:ALL) ALL
> 
> # Allow members of group sudo to execute any command
> %sudo   ALL=(ALL:ALL) ALL
> 
> # See sudoers(5) for more information on "@include" directives:
> 
> @includedir /etc/sudoers.d
> (END)
> 
> If you are _not_ a user of group sudo for whatever reason - and want to
> use sudo - then you will need root privileges and the root password
> (once) to add your user name to the group.
> 
> For example: adduser sophie sudo
> 
> I hope this helps
> 
> > 2 years ago
> > sudo was no problem.
> >
> 
> As yet, we have *no idea* what you have done in the last two years to
> break your Debian system - or even to know which kernel you boot or
> how you "rescue" your system when you log onto it every day.
> 
> Please give us information in order that the readers on this list can
> use their knowledge to help you.
> 
> With every good wish, as ever,
> 
> Andy
> (amaca...@debian.org)
> > Regards
> >
> > Sophie
> >
> > Thank You
> > 
> > Von: Timothy M Butterworth 
> > Gesendet: Montag, 22. Januar 2024 00:07
> > An: Schwibinger Michael 
> > Cc: Greg Wooledge ; debian-user@lists.debian.org 
> > 
> > Betreff: Re: su su- sudo dont work
> >
> >
> >
> > On Sun, Jan 21, 2024 at 4:07 PM Schwibinger Michael 
> > mailto:h...@hotmail.com>> wrote:
> > Thank You
> > Example
> > I say
> >
> > sudo apt-get install firefox
> > Reaction LINUX
> > This is not allowed we send a message to the admin.
> >
> > This error message means that your account is not in the sudo group.
> >
> > Run the command "groups" and look for the group sudo.
> > groups
> >
> > Here is the command to add a user account to the sudo group. You will need 
> > to run it as root.
> > usermod -a -G sudo 
> >
> > I do open root terminal
> > there its working.
> > Regards
> > Sophie
> >
> > 
> > Von: Greg Wooledge mailto:g...@wooledge.org>>
> > Gesendet: Samstag, 20. Januar 2024 14:14
> > An: debian-user@lists.debian.org<mailto:debian-user@lists.debian.org> 
> > mailto:debian-user@lists.debian.org>>
> > Betreff: Re: su su- sudo dont work
> >
> > On Sat, Jan 20, 2024 at 01:26:06PM +, Schwibinger Michael wrote:
> > > Good afternoon.
> > > Root terminal is fine.
> > > What do I do wrong?
> > > What did I destroy?
> > >
> > > PC does have only one user=admin.
> > >
> > > Regards Sophie
> > > Is it the rescue mode?
> >
> > Explain, please.
> >
> > Your Subject: header says "su su- sudo dont work".  What does this MEAN?
> >
> > Please show us your attempts to USE each of these commands, and the
> &g

AW: AW: su su- sudo dont work

[Schwibinger Michael]

Good afternoon
I think
maybe Im sure
it is because of rescue mode.

Normal booting did not have this problem.

Anybody familiar with panic?

Regards
Thank You
Sophie



Von: Andrew M.A. Cater 
Gesendet: Donnerstag, 25. Januar 2024 18:40
An: debian-user@lists.debian.org 
Betreff: Re: AW: su su- sudo dont work

On Thu, Jan 25, 2024 at 03:53:10PM +, Schwibinger Michael wrote:
> Good afternoon
> Why do I have to open a group?
>

This is to *tell* us information about why you're having problems with su
and sudo

Running the

id

command should give you information like

uid=1000(amacater) gid=1000(amacater) groups=1000(amacater),27(sudo)

which shows you that my user - amacater - is the first user on the
machine (because Debian starts user id numbers at 1000 for ordinary
users) and that I'm a member of group sudo - so can use sudo instead of su.

/etc/sudoers will show you what privileges the sudo user has.
Here are the last lines of the file on my machine (which has not been
modified from Debian defaults)

# User privilege specification
rootALL=(ALL:ALL) ALL

# Allow members of group sudo to execute any command
%sudo   ALL=(ALL:ALL) ALL

# See sudoers(5) for more information on "@include" directives:

@includedir /etc/sudoers.d
(END)

If you are _not_ a user of group sudo for whatever reason - and want to
use sudo - then you will need root privileges and the root password
(once) to add your user name to the group.

For example: adduser sophie sudo

I hope this helps

> 2 years ago
> sudo was no problem.
>

As yet, we have *no idea* what you have done in the last two years to
break your Debian system - or even to know which kernel you boot or
how you "rescue" your system when you log onto it every day.

Please give us information in order that the readers on this list can
use their knowledge to help you.

With every good wish, as ever,

Andy
(amaca...@debian.org)
> Regards
>
> Sophie
>
> Thank You
> 
> Von: Timothy M Butterworth 
> Gesendet: Montag, 22. Januar 2024 00:07
> An: Schwibinger Michael 
> Cc: Greg Wooledge ; debian-user@lists.debian.org 
> 
> Betreff: Re: su su- sudo dont work
>
>
>
> On Sun, Jan 21, 2024 at 4:07 PM Schwibinger Michael 
> mailto:h...@hotmail.com>> wrote:
> Thank You
> Example
> I say
>
> sudo apt-get install firefox
> Reaction LINUX
> This is not allowed we send a message to the admin.
>
> This error message means that your account is not in the sudo group.
>
> Run the command "groups" and look for the group sudo.
> groups
>
> Here is the command to add a user account to the sudo group. You will need to 
> run it as root.
> usermod -a -G sudo 
>
> I do open root terminal
> there its working.
> Regards
> Sophie
>
> 
> Von: Greg Wooledge mailto:g...@wooledge.org>>
> Gesendet: Samstag, 20. Januar 2024 14:14
> An: debian-user@lists.debian.org<mailto:debian-user@lists.debian.org> 
> mailto:debian-user@lists.debian.org>>
> Betreff: Re: su su- sudo dont work
>
> On Sat, Jan 20, 2024 at 01:26:06PM +, Schwibinger Michael wrote:
> > Good afternoon.
> > Root terminal is fine.
> > What do I do wrong?
> > What did I destroy?
> >
> > PC does have only one user=admin.
> >
> > Regards Sophie
> > Is it the rescue mode?
>
> Explain, please.
>
> Your Subject: header says "su su- sudo dont work".  What does this MEAN?
>
> Please show us your attempts to USE each of these commands, and the
> results that you got.  This means, run the commands in a terminal
> window, and then PASTE the contents of that terminal window into the
> body of your next email.  Show us the shell prompt, the command as you
> typed it, and the full output.
>
> In other words, show us WHAT IS WRONG, or at least what appears wrong.
>
> In addition, please give basic background information -- what version
> of Debian you are running, what desktop environment if any, how you
> logged in (*especially* if it isn't just a "standard graphical login
> for your desktop environment"), and anything else you can think of
> that might be relevant.
>
> How does "rescue mode" factor into the problem?
>
> When you installed Debian, did you give a root password, or did you
> leave it blank?
>
> Finally, it would be helpful for you to run the "id" command (with no
> arguments), in the same terminal session as your failed su or sudo
> command(s), and include that command and its output in your paste.
>
>
>
> --
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
> ⠈⠳⣄⠀⠀

AW: su su- sudo dont work

[Schwibinger Michael]

Good afternoon
Thank You

There is only one password.
The problem was created until
the update to DEBIAN 11 created panic.
Before
sudo
su
su -

did work.

Regards
Sophie



Von: Gareth Evans 
Gesendet: Mittwoch, 24. Januar 2024 04:31
An: debian-user@lists.debian.org 
Cc: debian-user@lists.debian.org 
Betreff: Re: su su- sudo dont work



> On 23 Jan 2024, at 18:30, Hans  wrote:
>
> Am Dienstag, 23. Januar 2024, 13:54:25 CET schrieb Schwibinger Michael:
> For gvetting root as normal user, best is use "su -".
>
> Note: It is not "su-", but "su -", with a space between su and the minus sign.

Also su requires root's password, not the user's, just in case that's worth 
mentioning...

Re: AW: AW: su su- sudo dont work

[Andy Smith]

Hello,

On Sat, Jan 27, 2024 at 11:05:30AM +0100, Thomas Schmitt wrote:
> Andy Smith wrote:
> > It is hard to understand how what Michael/Sophie/Tobias does can in
> > any way be "fun" for them, though maybe that is just our lack of
> > understanding.
> 
> I expressed my suspicion of a "Hurz" performance in
>   https://lists.debian.org/debian-user/2023/05/msg00100.html

Okay, but it seems to me that watching an audience try to take a
nonsense opera seriously is a bit more sophisticated and has scope
for amusement, unlike for example an endless stream of mispastes and
misunderstandings about "sudo" and "su".

But I guess what one finds amusing can have a very wide variability…

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: AW: AW: su su- sudo dont work

[Thomas Schmitt]

Hi,

Andy Smith wrote:
> It is hard to understand how what Michael/Sophie/Tobias does can in
> any way be "fun" for them, though maybe that is just our lack of
> understanding.

I expressed my suspicion of a "Hurz" performance in
  https://lists.debian.org/debian-user/2023/05/msg00100.html


Have a nice day :)

Thomas

Re: AW: AW: su su- sudo dont work

[Andy Smith]

Hi Hans,

On Sat, Jan 27, 2024 at 10:23:09AM +0100, Hans wrote:
> I see this exactly as you and are watching this list for may years.

I'm not sure who you're replying to as you've removed those details,
though I may guess from your In-Reply-To header which doesn't point
to a list message. You haven't replied to an off-list (personal)
mail back onto the list have you? Be careful there!

> But since the beginning, I had the suspicion, that someone just
> wants to make fun with us.

It is hard to understand how what Michael/Sophie/Tobias does can in
any way be "fun" for them, though maybe that is just our lack of
understanding.

Either they are incredibly confused by Linux or they are pretending
to be for reasons beyond my understanding. Whatever the case, I
don't think I have ever seen one of their threads result in a
positive resolution.

It's probably best to not assume that what we don't understand is
hostile and/or an AI experiment. Even so, that doesn't mean it is
possible to help.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: AW: AW: su su- sudo dont work

[Hans]

I see this exactly as you and are watching this list for may years.

However, I wanted not to be so directly because I want not to blame anyone on 
this list.

But since the beginning, I had the suspicion, that someone just wants to make 
fun with us.

Aleady from the beginning I checked after the mail adress (please note, I am 
German myself) and found some theater group behind the mailadress. 

So I personally(!) believe, the group is making fun with us, but even then I 
gave him a chance. 

And again I personally(!) (and this is my very personal opinion), I think, 
nobody is so stupid, that he/she can not do a su or install a package. NOT 
after 2 years!!!

For me, I will get no help here for this person, just ignore it. This is my 
very personal decision!

Sorry to say it, but for me personally it looks like fake! Like a morone, like 
a troll.

And those I can not support, sorry.

Please excuse, I do not want to hurt anyone, just tell, what I think.

Best regards

Hans  

> I see very similar posts in the German language list from the last two
> years but as Tobias Schwibingerr or similar - also signed by a Sophie
> 
> When I asked this question some time ago, it seems that the German language
> list had concluded that this person might be a troll (or even a psychology
> experiment / AI) :(
> 
> Like you, I have attempted to engage - but I think none of us will see
> any change - I think the German list pays no attention / may have blocked
> this user.
> 

Re: AW: AW: su su- sudo dont work

[Hans]

Am Freitag, 26. Januar 2024, 17:23:07 CET schrieben Sie:
Yes, if you want to install soemthing for example by using the apt command, 
best way is 
becoming root with the command "su -" and then install the rquired package.


Example:
su -  then enter the password of the user root


If installing for example firefox, first read the repository:


apt update


then install the package


apt install firefox-esr


-


Hint: If you want a graphical method and you have no X and Wndow-Manager 
running (like KDE, 
Gnome, XFCE whatever), I suggest using aptitude.


You have to install aptitude first:


apt install aptitude


Then you can start the gui with the command "aptitude" as root.


Hint 2: aptitude is controlled by keypresses without any enter-key.
For example, when started aptitude, just press the "u" key and it reads the 
update, "U" (Shift + 
u)  marks all newer packages automatically to be updated, then press "g" and 
you will shwo, 
what it will do. Press "g" again, and it will do the update.


Please note: If you want to upgrade the whole sytem, then using apt or apt-get 
will be the 
better choice!


But aptitude is very well for installing single packages or weekly upgrades, 
where not much 
packages will be renewed.


If you are not much experienced, and you have a window-manager running like 
KDE, Gnome, 
XFCE, LXDE or another one, then look at synaptic. Synaptic is a graphical tool 
for installing 
packages, it is a GUI for apt.


Synaptic MUST run as root.


Hope this helps.


By the way: I believe, you are not very experienced in English language, so I 
suggest to suscribe 
in the fine German forum, 
which is debian-user-ger...@lists.debioan.org.


Here is the link:
https://lists.debian.org/debian-user-german/[1]


Good luck!


Hans



> Sorry
> it was my mistake
> 
> It is
> 
> su -
> su
> or sudo.
> 
> Sorry.
> 
> Is su -
> the best for install?
> 
> Regards
> 
> Sophie
> 
> 
> 
>


[1] https://lists.debian.org/debian-user-german/

Re: AW: AW: su su- sudo dont work

[Greg Wooledge]

On Fri, Jan 26, 2024 at 04:23:07PM +, Schwibinger Michael wrote:
> su -
> su
> or sudo.
> 
> Is su -
> the best for install?

Whatever works best for *you* is best.  "su -" is quite popular.
If it does what you need, and is convenient for you, then there's
your answer.

AW: AW: su su- sudo dont work

[Schwibinger Michael]

Sorry
it was my mistake

It is

su -
su
or sudo.

Sorry.

Is su -
the best for install?

Regards

Sophie



Von: Hans 
Gesendet: Dienstag, 23. Januar 2024 18:29
An: debian-user@lists.debian.org 
Betreff: Re: AW: su su- sudo dont work

Am Dienstag, 23. Januar 2024, 13:54:25 CET schrieb Schwibinger Michael:
For gvetting root as normal user, best is use "su -".

Note: It is not "su-", but "su -", with a space between su and the minus sign.

Good luck!

Hans

> Thank You.
>
> 2 questions
> 1
> Is the best to use su-
> for ding install?
> 2
> All 4 dont work.
> What do I do wrong?
> Regards
> Sophie
>
>

Re: AW: su su- sudo dont work

[Andrew M.A. Cater]

On Thu, Jan 25, 2024 at 03:53:10PM +, Schwibinger Michael wrote:
> Good afternoon
> Why do I have to open a group?
> 

This is to *tell* us information about why you're having problems with su
and sudo

Running the 

id

command should give you information like

uid=1000(amacater) gid=1000(amacater) groups=1000(amacater),27(sudo)

which shows you that my user - amacater - is the first user on the 
machine (because Debian starts user id numbers at 1000 for ordinary
users) and that I'm a member of group sudo - so can use sudo instead of su.

/etc/sudoers will show you what privileges the sudo user has.
Here are the last lines of the file on my machine (which has not been
modified from Debian defaults)

# User privilege specification
rootALL=(ALL:ALL) ALL

# Allow members of group sudo to execute any command
%sudo   ALL=(ALL:ALL) ALL

# See sudoers(5) for more information on "@include" directives:

@includedir /etc/sudoers.d
(END)

If you are _not_ a user of group sudo for whatever reason - and want to
use sudo - then you will need root privileges and the root password
(once) to add your user name to the group.

For example: adduser sophie sudo

I hope this helps

> 2 years ago
> sudo was no problem.
> 

As yet, we have *no idea* what you have done in the last two years to 
break your Debian system - or even to know which kernel you boot or 
how you "rescue" your system when you log onto it every day.

Please give us information in order that the readers on this list can
use their knowledge to help you.

With every good wish, as ever,

Andy
(amaca...@debian.org)
> Regards
> 
> Sophie
> 
> Thank You
> 
> Von: Timothy M Butterworth 
> Gesendet: Montag, 22. Januar 2024 00:07
> An: Schwibinger Michael 
> Cc: Greg Wooledge ; debian-user@lists.debian.org 
> 
> Betreff: Re: su su- sudo dont work
> 
> 
> 
> On Sun, Jan 21, 2024 at 4:07 PM Schwibinger Michael 
> mailto:h...@hotmail.com>> wrote:
> Thank You
> Example
> I say
> 
> sudo apt-get install firefox
> Reaction LINUX
> This is not allowed we send a message to the admin.
> 
> This error message means that your account is not in the sudo group.
> 
> Run the command "groups" and look for the group sudo.
> groups
> 
> Here is the command to add a user account to the sudo group. You will need to 
> run it as root.
> usermod -a -G sudo 
> 
> I do open root terminal
> there its working.
> Regards
> Sophie
> 
> 
> Von: Greg Wooledge mailto:g...@wooledge.org>>
> Gesendet: Samstag, 20. Januar 2024 14:14
> An: debian-user@lists.debian.org<mailto:debian-user@lists.debian.org> 
> mailto:debian-user@lists.debian.org>>
> Betreff: Re: su su- sudo dont work
> 
> On Sat, Jan 20, 2024 at 01:26:06PM +, Schwibinger Michael wrote:
> > Good afternoon.
> > Root terminal is fine.
> > What do I do wrong?
> > What did I destroy?
> >
> > PC does have only one user=admin.
> >
> > Regards Sophie
> > Is it the rescue mode?
> 
> Explain, please.
> 
> Your Subject: header says "su su- sudo dont work".  What does this MEAN?
> 
> Please show us your attempts to USE each of these commands, and the
> results that you got.  This means, run the commands in a terminal
> window, and then PASTE the contents of that terminal window into the
> body of your next email.  Show us the shell prompt, the command as you
> typed it, and the full output.
> 
> In other words, show us WHAT IS WRONG, or at least what appears wrong.
> 
> In addition, please give basic background information -- what version
> of Debian you are running, what desktop environment if any, how you
> logged in (*especially* if it isn't just a "standard graphical login
> for your desktop environment"), and anything else you can think of
> that might be relevant.
> 
> How does "rescue mode" factor into the problem?
> 
> When you installed Debian, did you give a root password, or did you
> leave it blank?
> 
> Finally, it would be helpful for you to run the "id" command (with no
> arguments), in the same terminal session as your failed su or sudo
> command(s), and include that command and its output in your paste.
> 
> 
> 
> --
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
> ⠈⠳⣄⠀⠀

AW: su su- sudo dont work

[Schwibinger Michael]

Good afternoon
Why do I have to open a group?

2 years ago
sudo was no problem.

Regards

Sophie

Thank You

Von: Timothy M Butterworth 
Gesendet: Montag, 22. Januar 2024 00:07
An: Schwibinger Michael 
Cc: Greg Wooledge ; debian-user@lists.debian.org 

Betreff: Re: su su- sudo dont work



On Sun, Jan 21, 2024 at 4:07 PM Schwibinger Michael 
mailto:h...@hotmail.com>> wrote:
Thank You
Example
I say

sudo apt-get install firefox
Reaction LINUX
This is not allowed we send a message to the admin.

This error message means that your account is not in the sudo group.

Run the command "groups" and look for the group sudo.
groups

Here is the command to add a user account to the sudo group. You will need to 
run it as root.
usermod -a -G sudo 

I do open root terminal
there its working.
Regards
Sophie


Von: Greg Wooledge mailto:g...@wooledge.org>>
Gesendet: Samstag, 20. Januar 2024 14:14
An: debian-user@lists.debian.org<mailto:debian-user@lists.debian.org> 
mailto:debian-user@lists.debian.org>>
Betreff: Re: su su- sudo dont work

On Sat, Jan 20, 2024 at 01:26:06PM +, Schwibinger Michael wrote:
> Good afternoon.
> Root terminal is fine.
> What do I do wrong?
> What did I destroy?
>
> PC does have only one user=admin.
>
> Regards Sophie
> Is it the rescue mode?

Explain, please.

Your Subject: header says "su su- sudo dont work".  What does this MEAN?

Please show us your attempts to USE each of these commands, and the
results that you got.  This means, run the commands in a terminal
window, and then PASTE the contents of that terminal window into the
body of your next email.  Show us the shell prompt, the command as you
typed it, and the full output.

In other words, show us WHAT IS WRONG, or at least what appears wrong.

In addition, please give basic background information -- what version
of Debian you are running, what desktop environment if any, how you
logged in (*especially* if it isn't just a "standard graphical login
for your desktop environment"), and anything else you can think of
that might be relevant.

How does "rescue mode" factor into the problem?

When you installed Debian, did you give a root password, or did you
leave it blank?

Finally, it would be helpful for you to run the "id" command (with no
arguments), in the same terminal session as your failed su or sudo
command(s), and include that command and its output in your paste.



--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

AW: AW: su su- sudo dont work

[Schwibinger Michael]

Good afternoon
Thank You.

I ll print it out and read it.

2 questions:

Is this the same problem with su
su -
su -p?

Is it not a problem of rescue mode,
before panic it did work.

Problem:
root terminal is not accepting copy paste.
Regards
Sophie



Von: Greg Wooledge 
Gesendet: Sonntag, 21. Januar 2024 14:40
An: debian-user@lists.debian.org 
Betreff: Re: AW: su su- sudo dont work

On Sun, Jan 21, 2024 at 12:57:17PM +, Schwibinger Michael wrote:
> sudo apt-get install firefox
> Reaction LINUX
> This is not allowed we send a message to the admin.
>
> I do open root terminal
> there its working.

It sounds like you are not authorized to use "sudo" on this computer.

This is precisely the scenario for which I requested that you run the
"id" command and paste its output into your email.  If you are in
the "sudo" group, then you should be allowed to use sudo.  Here, for
example, is my output:

unicorn:~$ id
uid=1000(greg) gid=1000(greg) 
groups=1000(greg),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),108(netdev)

You can see that it includes ",27(sudo)" which demonstrates that I am in
the sudo group, and I am therefore allowed to use sudo on this computer.

If your output does not include this group, then we see the cause.
And then the solution becomes obvious.

We would also see your UID, and this might inform us as to *underlying*
reasons why you are not in the sudo group.  Maybe this isn't UID 1000
(the one created during installation).  Maybe it's a user that was
created later, with a higher UID.  In that case, it's *normal* for you
not to be in the sudo group, until you explicitly add yourself.

We would also see your username, so that if we have to tell you to
run a command to add yourself to the sudo group, we'd be able to give
you the *exact* command, and you could just paste it, or type it,
without having to think.

All of this would have been *REVEALED TO US* if you had simply done what
we asked.

At this point, after years of your membership here, I don't think I've
ever seen you paste information from a Debian terminal session into
your emails.  This leads me to believe you are *incapable* of doing so,
for one reason or another.  Maybe the Debian system is air-gapped,
and you can't ssh to it from the system where you compose emails.
Maybe you compose emails on a handheld mobile device which can't ssh or
copy text.  Maybe you're just too technologically ignorant to do things
like installing PuTTY on Windows and using that to ssh into Debian to
run the commands so they can be pasted.

All I know for sure is that helping you is *incredibly* frustrating,
because not only do you not do the basic steps that are requested, you
also refuse to *explain* why you don't do them.  All we can ever do is
guess.

So anyway, here is my prescription for this particular problem.  These
are the steps you should follow.  They will require that you read and
understand them, and that you actually do them.

1) On the Debian system, while you are logged in as the user who cannot
   use sudo, open a terminal, and run the "id" command.

2) Look for (sudo) in the output.

3) If you see (sudo) in the output, this means your sudoers file is not
   the normal one for Debian.  Something has changed it.  You will have
   to figure out what has changed, and WHY it has changed, and fix it.
   In this case, STOP.  Do not proceed to step 4 or 5.

4) If you do NOT see (sudo), then you will want to add yourself to the
   sudo group.  To do this, you will need your username, which you have
   never revealed to us.  I will therefore have to write a template
   command in which you will have to FILL IN YOUR USERNAME.

   Open a root terminal (which you claim you can do) and run this
   command:

adduser YOURUSERNAME sudo

   But replace YOURUSERNAME with your Debian username.

5) If you added yourself to the sudo group, then you will need to logout
   of Debian and log back in to make it take effect.  After logging back
   in, run "id" and verify that you are now in the sudo group.

Once you are in the sudo group, you should be able to use sudo, unless
your /etc/sudoers file has been altered, or came from a non-Debian system.

If your /etc/sudoers file is not of Debian origin, then I personally
will refuse to try to help you fix it, because I don't believe you will
be able to follow my instructions correctly.  You will need help from
someone with whom you can communicate effectively.  This may mean you
need to go to a German-language Debian mailing list.  It may mean you
need in-person help from a local expert.  It may mean you have to hand
your entire computer over to a professional.  I don't know what you
need at this point.

Re: su su- sudo dont work

[Gareth Evans]

> On 23 Jan 2024, at 18:30, Hans  wrote:
> 
> Am Dienstag, 23. Januar 2024, 13:54:25 CET schrieb Schwibinger Michael:
> For gvetting root as normal user, best is use "su -".
> 
> Note: It is not "su-", but "su -", with a space between su and the minus sign.

Also su requires root's password, not the user's, just in case that's worth 
mentioning...

Re: AW: su su- sudo dont work

[Hans]

Am Dienstag, 23. Januar 2024, 13:54:25 CET schrieb Schwibinger Michael:
For gvetting root as normal user, best is use "su -".

Note: It is not "su-", but "su -", with a space between su and the minus sign.

Good luck!

Hans

> Thank You.
> 
> 2 questions
> 1
> Is the best to use su-
> for ding install?
> 2
> All 4 dont work.
> What do I do wrong?
> Regards
> Sophie
> 
>

AW: su su- sudo dont work

[Schwibinger Michael]

Thank You.

2 questions
1
Is the best to use su-
for ding install?
2
All 4 dont work.
What do I do wrong?
Regards
Sophie



Von: Hans 
Gesendet: Samstag, 20. Januar 2024 14:23
An: debian-user@lists.debian.org 
Betreff: Re: su su- sudo dont work

Am Samstag, 20. Januar 2024, 14:26:06 CET schrieb Schwibinger Michael:
There is not "su su-", but there is

su   = change to root, envirenmont of former user without changing of X
environment (hope, this is corect said)
su -= change to root, environment of user root
su -p   = change to root, environment of former user (usefull when in
window manager and you want to start graphical applications with root rights)

Hope this helps.

Best

Hans



> Good afternoon.
> Root terminal is fine.
> What do I do wrong?
> What did I destroy?
>
> PC does have only one user=admin.
>
> Regards Sophie
> Is it the rescue mode?

AW: su su- sudo dont work

[Schwibinger Michael]

Good afternoon
Its DEBIAN 11 LXDE
There is user id + password.
I think the problem
appeared only after update to 11
created panic.
Root terminal is working
but its not accepting
copypaste.
Regards
Thank You
Sophie



Von: David Wright 
Gesendet: Samstag, 20. Januar 2024 14:34
An: debian-user@lists.debian.org 
Betreff: Re: su su- sudo dont work

On Sat 20 Jan 2024 at 09:14:30 (-0500), Greg Wooledge wrote:
> On Sat, Jan 20, 2024 at 01:26:06PM +, Schwibinger Michael wrote:
> > Good afternoon.
> > Root terminal is fine.
> > What do I do wrong?
> > What did I destroy?
> >
> > PC does have only one user=admin.
> >
> > Regards Sophie
> > Is it the rescue mode?
>
> Explain, please.
>
> Your Subject: header says "su su- sudo dont work".  What does this MEAN?
>
> Please show us your attempts to USE each of these commands, and the
> results that you got.  This means, run the commands in a terminal
> window, and then PASTE the contents of that terminal window into the
> body of your next email.  Show us the shell prompt, the command as you
> typed it, and the full output.
>
> In other words, show us WHAT IS WRONG, or at least what appears wrong.
>
> In addition, please give basic background information -- what version
> of Debian you are running, what desktop environment if any, how you
> logged in (*especially* if it isn't just a "standard graphical login
> for your desktop environment"), and anything else you can think of
> that might be relevant.
>
> How does "rescue mode" factor into the problem?
>
> When you installed Debian, did you give a root password, or did you
> leave it blank?
>
> Finally, it would be helpful for you to run the "id" command (with no
> arguments), in the same terminal session as your failed su or sudo
> command(s), and include that command and its output in your paste.

Welcome to the world of déjà vu.

  https://lists.debian.org/debian-user/2022/07/msg00601.html

Cheers,
David.

Re: su su- sudo dont work

[Timothy M Butterworth]

On Sun, Jan 21, 2024 at 4:07 PM Schwibinger Michael 
wrote:

> Thank You
> Example
> I say
>
> sudo apt-get install firefox
> Reaction LINUX
> This is not allowed we send a message to the admin.
>

This error message means that your account is not in the sudo group.

Run the command "groups" and look for the group sudo.
groups

Here is the command to add a user account to the sudo group. You will need
to run it as root.
usermod -a -G sudo 


> I do open root terminal
> there its working.
> Regards
> Sophie
>
> --
> *Von:* Greg Wooledge 
> *Gesendet:* Samstag, 20. Januar 2024 14:14
> *An:* debian-user@lists.debian.org 
> *Betreff:* Re: su su- sudo dont work
>
> On Sat, Jan 20, 2024 at 01:26:06PM +, Schwibinger Michael wrote:
> > Good afternoon.
> > Root terminal is fine.
> > What do I do wrong?
> > What did I destroy?
> >
> > PC does have only one user=admin.
> >
> > Regards Sophie
> > Is it the rescue mode?
>
> Explain, please.
>
> Your Subject: header says "su su- sudo dont work".  What does this MEAN?
>
> Please show us your attempts to USE each of these commands, and the
> results that you got.  This means, run the commands in a terminal
> window, and then PASTE the contents of that terminal window into the
> body of your next email.  Show us the shell prompt, the command as you
> typed it, and the full output.
>
> In other words, show us WHAT IS WRONG, or at least what appears wrong.
>
> In addition, please give basic background information -- what version
> of Debian you are running, what desktop environment if any, how you
> logged in (*especially* if it isn't just a "standard graphical login
> for your desktop environment"), and anything else you can think of
> that might be relevant.
>
> How does "rescue mode" factor into the problem?
>
> When you installed Debian, did you give a root password, or did you
> leave it blank?
>
> Finally, it would be helpful for you to run the "id" command (with no
> arguments), in the same terminal session as your failed su or sudo
> command(s), and include that command and its output in your paste.
>
>

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

Re: AW: su su- sudo dont work

[Greg Wooledge]

On Sun, Jan 21, 2024 at 12:57:17PM +, Schwibinger Michael wrote:
> sudo apt-get install firefox
> Reaction LINUX
> This is not allowed we send a message to the admin.
> 
> I do open root terminal
> there its working.

It sounds like you are not authorized to use "sudo" on this computer.

This is precisely the scenario for which I requested that you run the
"id" command and paste its output into your email.  If you are in
the "sudo" group, then you should be allowed to use sudo.  Here, for
example, is my output:

unicorn:~$ id
uid=1000(greg) gid=1000(greg) 
groups=1000(greg),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),108(netdev)

You can see that it includes ",27(sudo)" which demonstrates that I am in
the sudo group, and I am therefore allowed to use sudo on this computer.

If your output does not include this group, then we see the cause.
And then the solution becomes obvious.

We would also see your UID, and this might inform us as to *underlying*
reasons why you are not in the sudo group.  Maybe this isn't UID 1000
(the one created during installation).  Maybe it's a user that was
created later, with a higher UID.  In that case, it's *normal* for you
not to be in the sudo group, until you explicitly add yourself.

We would also see your username, so that if we have to tell you to
run a command to add yourself to the sudo group, we'd be able to give
you the *exact* command, and you could just paste it, or type it,
without having to think.

All of this would have been *REVEALED TO US* if you had simply done what
we asked.

At this point, after years of your membership here, I don't think I've
ever seen you paste information from a Debian terminal session into
your emails.  This leads me to believe you are *incapable* of doing so,
for one reason or another.  Maybe the Debian system is air-gapped,
and you can't ssh to it from the system where you compose emails.
Maybe you compose emails on a handheld mobile device which can't ssh or
copy text.  Maybe you're just too technologically ignorant to do things
like installing PuTTY on Windows and using that to ssh into Debian to
run the commands so they can be pasted.

All I know for sure is that helping you is *incredibly* frustrating,
because not only do you not do the basic steps that are requested, you
also refuse to *explain* why you don't do them.  All we can ever do is
guess.

So anyway, here is my prescription for this particular problem.  These
are the steps you should follow.  They will require that you read and
understand them, and that you actually do them.

1) On the Debian system, while you are logged in as the user who cannot
   use sudo, open a terminal, and run the "id" command.

2) Look for (sudo) in the output.

3) If you see (sudo) in the output, this means your sudoers file is not
   the normal one for Debian.  Something has changed it.  You will have
   to figure out what has changed, and WHY it has changed, and fix it.
   In this case, STOP.  Do not proceed to step 4 or 5.

4) If you do NOT see (sudo), then you will want to add yourself to the
   sudo group.  To do this, you will need your username, which you have
   never revealed to us.  I will therefore have to write a template
   command in which you will have to FILL IN YOUR USERNAME.

   Open a root terminal (which you claim you can do) and run this
   command:

adduser YOURUSERNAME sudo

   But replace YOURUSERNAME with your Debian username.

5) If you added yourself to the sudo group, then you will need to logout
   of Debian and log back in to make it take effect.  After logging back
   in, run "id" and verify that you are now in the sudo group.

Once you are in the sudo group, you should be able to use sudo, unless
your /etc/sudoers file has been altered, or came from a non-Debian system.

If your /etc/sudoers file is not of Debian origin, then I personally
will refuse to try to help you fix it, because I don't believe you will
be able to follow my instructions correctly.  You will need help from
someone with whom you can communicate effectively.  This may mean you
need to go to a German-language Debian mailing list.  It may mean you
need in-person help from a local expert.  It may mean you have to hand
your entire computer over to a professional.  I don't know what you
need at this point.

AW: su su- sudo dont work

[Schwibinger Michael]

Thank You
Example
I say

sudo apt-get install firefox
Reaction LINUX
This is not allowed we send a message to the admin.

I do open root terminal
there its working.
Regards
Sophie


Von: Greg Wooledge 
Gesendet: Samstag, 20. Januar 2024 14:14
An: debian-user@lists.debian.org 
Betreff: Re: su su- sudo dont work

On Sat, Jan 20, 2024 at 01:26:06PM +, Schwibinger Michael wrote:
> Good afternoon.
> Root terminal is fine.
> What do I do wrong?
> What did I destroy?
>
> PC does have only one user=admin.
>
> Regards Sophie
> Is it the rescue mode?

Explain, please.

Your Subject: header says "su su- sudo dont work".  What does this MEAN?

Please show us your attempts to USE each of these commands, and the
results that you got.  This means, run the commands in a terminal
window, and then PASTE the contents of that terminal window into the
body of your next email.  Show us the shell prompt, the command as you
typed it, and the full output.

In other words, show us WHAT IS WRONG, or at least what appears wrong.

In addition, please give basic background information -- what version
of Debian you are running, what desktop environment if any, how you
logged in (*especially* if it isn't just a "standard graphical login
for your desktop environment"), and anything else you can think of
that might be relevant.

How does "rescue mode" factor into the problem?

When you installed Debian, did you give a root password, or did you
leave it blank?

Finally, it would be helpful for you to run the "id" command (with no
arguments), in the same terminal session as your failed su or sudo
command(s), and include that command and its output in your paste.

Re: su su- sudo dont work

[Byung-Hee HWANG]

On Sat, 2024-01-20 at 13:26 +, Schwibinger Michael wrote:
> 
> Good afternoon.
> Root terminal is fine.
> What do I do wrong?
> What did I destroy?
> 
> 
> PC does have only one user=admin.
> 
> 
> Regards Sophie
> Is it the rescue mode?

Hellow Sophie,

English is not my native language. Sometimes i use Korean mailing list
for me. Because i am Korean and i feel hard to write/speak English.


I guess English is not your native language. There is a German-only Q
mailing. See  please.


Es gibt ein Q nur auf Deutsch.

Schau hier:



Sincerely, Byung-Hee from South Korea

-- 
^고맙습니다 _布德天下_ 감사합니다_^))//

Problem booting the Debian machine [WAS Re: AW: su su- sudo dont work]

[Andrew M.A. Cater]

On Sat, Jan 20, 2024 at 02:30:43PM +, Schwibinger Michael wrote:
> Good afternoon
> I destroyed DEBIAN
> now 2 years agon.
> I asked here for help
> no solution.
> So every morning
> I interrupt booting
> change to rescue mode.
> 
> "Normal" booting does create panic.
> 
> Regards
> Sophie
> 
> PC
> accident happened after update to DEBIAN 11.
> 

Hi Sophie,

We are asking you questions because we can't see you, we can't see 
what you type, we need clear information.

It's like playing chess by post: every time we ask for details
on what you have - what has happened, how the pieces are laid
out - we get an "I have a chess problem" message.

In your reply, please try and answer each of the questions
written below *under* the question so it is clear. If you only have
a phone to reply, that's OK, but please reply to one question
at a time in that case.

Please try and keep to the subject of the message. I have changed
that to "Problem booting the machine" I expect your reply to be
something like AW: Problem booting the machine

First - and most important question - is this your only computer?

If so, I would not want to break it further but in order to fix it,
we will need more information.

Second question - is this the computer that you mail us from to this list
or are you using some other device to mail us?

Your reply above has given more information: this happened after
you upgraded from Debian 10 to Debian 11. 

Third question - Even if it's now more than two years ago: can you
remember whether the upgrade completed successfully?

Fourth question -Is it that when the computer starts - and you get a
(blue or green??) first screen with white writing, it lists 
several kernels to choose from?
 
Fifth question - If you have only one kernel listed, then under that may be
a "rescue" option - is that what you use to boot the machine every
day?

If so, then *what do you type* to get into the system: what commands?

Sixth question - One line may list the Debian 11 kernel version -
with 5.10 - or may list the Debian 10 kernel version - with 4.19
Which do you select  / which one works?

Thank you in advance for your replies

Andy
(amaca...@debian.org)
> 

> 

Re: su su- sudo dont work

[Andy Smith]

Hi,

On Sat, Jan 20, 2024 at 01:26:06PM +, Schwibinger Michael wrote:
> Good afternoon.
> Root terminal is fine.
> What do I do wrong?
> What did I destroy?

h-boy, strap yourselves in for another epic Sophie/Michael
thread. A bit like the Gene ones, though tend to be circular across
a much smaller pool of non-information, and far less chance of
bringing up the Korean war. Equally pessimistic as to the chances
of ever reaching a resolution.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

AW: su su- sudo dont work

[Schwibinger Michael]

Good afternoon
I destroyed DEBIAN
now 2 years agon.
I asked here for help
no solution.
So every morning
I interrupt booting
change to rescue mode.

"Normal" booting does create panic.

Regards
Sophie

PC
accident happened after update to DEBIAN 11.



Von: Dan Ritter 
Gesendet: Samstag, 20. Januar 2024 14:09
An: Schwibinger Michael 
Cc: debian-user@lists.debian.org 
Betreff: Re: su su- sudo dont work

Schwibinger Michael wrote:
> Good afternoon.
> Root terminal is fine.
> What do I do wrong?
> What did I destroy?
>
> PC does have only one user=admin.
>
> Regards Sophie
> Is it the rescue mode?

Please tell us:

 exactly what rescue mode you were using

 exactly what the prompt was

 exactly what you typed

 exactly what the response was

 exactly what you want to have happen

Unless you tell us all of these things in one email message, it
will not be a good idea for any of us to try to help you.

Re: su su- sudo dont work

[David Wright]

On Sat 20 Jan 2024 at 09:14:30 (-0500), Greg Wooledge wrote:
> On Sat, Jan 20, 2024 at 01:26:06PM +, Schwibinger Michael wrote:
> > Good afternoon.
> > Root terminal is fine.
> > What do I do wrong?
> > What did I destroy?
> > 
> > PC does have only one user=admin.
> > 
> > Regards Sophie
> > Is it the rescue mode?
> 
> Explain, please.
> 
> Your Subject: header says "su su- sudo dont work".  What does this MEAN?
> 
> Please show us your attempts to USE each of these commands, and the
> results that you got.  This means, run the commands in a terminal
> window, and then PASTE the contents of that terminal window into the
> body of your next email.  Show us the shell prompt, the command as you
> typed it, and the full output.
> 
> In other words, show us WHAT IS WRONG, or at least what appears wrong.
> 
> In addition, please give basic background information -- what version
> of Debian you are running, what desktop environment if any, how you
> logged in (*especially* if it isn't just a "standard graphical login
> for your desktop environment"), and anything else you can think of
> that might be relevant.
> 
> How does "rescue mode" factor into the problem?
> 
> When you installed Debian, did you give a root password, or did you
> leave it blank?
> 
> Finally, it would be helpful for you to run the "id" command (with no
> arguments), in the same terminal session as your failed su or sudo
> command(s), and include that command and its output in your paste.

Welcome to the world of déjà vu.

  https://lists.debian.org/debian-user/2022/07/msg00601.html

Cheers,
David.

Re: su su- sudo dont work

[Dan Ritter]

Schwibinger Michael wrote: 
> Good afternoon.
> Root terminal is fine.
> What do I do wrong?
> What did I destroy?
> 
> PC does have only one user=admin.
> 
> Regards Sophie
> Is it the rescue mode?

Please tell us:

 exactly what rescue mode you were using

 exactly what the prompt was

 exactly what you typed

 exactly what the response was

 exactly what you want to have happen

Unless you tell us all of these things in one email message, it
will not be a good idea for any of us to try to help you.

Re: su su- sudo dont work

[Hans]

Am Samstag, 20. Januar 2024, 14:26:06 CET schrieb Schwibinger Michael:
There is not "su su-", but there is

su  = change to root, envirenmont of former user without changing of X 
environment (hope, this is corect said)
su -= change to root, environment of user root
su -p   = change to root, environment of former user (usefull when in 
window manager and you want to start graphical applications with root rights)
 
Hope this helps.

Best

Hans
 


> Good afternoon.
> Root terminal is fine.
> What do I do wrong?
> What did I destroy?
> 
> PC does have only one user=admin.
> 
> Regards Sophie
> Is it the rescue mode?

Re: su su- sudo dont work

[Greg Wooledge]

On Sat, Jan 20, 2024 at 01:26:06PM +, Schwibinger Michael wrote:
> Good afternoon.
> Root terminal is fine.
> What do I do wrong?
> What did I destroy?
> 
> PC does have only one user=admin.
> 
> Regards Sophie
> Is it the rescue mode?

Explain, please.

Your Subject: header says "su su- sudo dont work".  What does this MEAN?

Please show us your attempts to USE each of these commands, and the
results that you got.  This means, run the commands in a terminal
window, and then PASTE the contents of that terminal window into the
body of your next email.  Show us the shell prompt, the command as you
typed it, and the full output.

In other words, show us WHAT IS WRONG, or at least what appears wrong.

In addition, please give basic background information -- what version
of Debian you are running, what desktop environment if any, how you
logged in (*especially* if it isn't just a "standard graphical login
for your desktop environment"), and anything else you can think of
that might be relevant.

How does "rescue mode" factor into the problem?

When you installed Debian, did you give a root password, or did you
leave it blank?

Finally, it would be helpful for you to run the "id" command (with no
arguments), in the same terminal session as your failed su or sudo
command(s), and include that command and its output in your paste.

su su- sudo dont work

[Schwibinger Michael]

Good afternoon.
Root terminal is fine.
What do I do wrong?
What did I destroy?

PC does have only one user=admin.

Regards Sophie
Is it the rescue mode?

sudo+use_pty+urxvt+pipe [WAS: apt-get aborts in subshell with redirections on Debian 12]

[John Crawley]

On 26/09/2023 11:52, John Crawley wrote:

On 25/09/2023 20:21, Greg Wooledge wrote:

On Mon, Sep 25, 2023 at 11:14:24AM +0200, Michael wrote:

so i looked into /etc/sudoers and all /etc/sudoers.d/* and found two
suspicous flags:

/etc/sudoers:
Defaults   use_pty

/etc/sudoers.d/0pwfeedback:
Defaults pwfeedback

then consulting the sudo manpage convinced me, it was the 'use_pty' flag (in
section SUDOERS OPTIONS). after removing that flag everything works as
'expected':


Well, that is quite the find. 


Indeed! Many thanks Michael.

8< snip >8

Anyway, for my personal purposes, this new behaviour looks too unpredictable 
and I plan to fall back on capturing stderr in a tempfile. Kludgy but maybe 
more robust than multiple redirections?

:~$ temp=$(mktemp)
:~$ sudo apt-get install nopkg 2>"$temp"
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
:~$ errors=$(<"$temp")
:~$ echo "$errors"
E: Unable to locate package nopkg
:~$ rm "$temp"

It would be nice to unpick the rest of the mystery though...



Revision:
apt commands where STDERR was captured in a variable were (still are) causing the apt 
prompt to be pre-empted to "No", eg:

(replace mirage with any package which is not installed, and needs to pull in 
some dependencies, so will call a prompt to confirm)

john@bookworm-tmp:~$ errors=$(sudo apt-get install mirage 2>&1 1>/dev/tty)
[sudo] password for john:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  gir1.2-gexiv2-0.10 libexiv2-27 libgexiv2-2
Suggested packages:
  exiv2 gimp
The following NEW packages will be installed:
  gir1.2-gexiv2-0.10 libexiv2-27 libgexiv2-2 mirage
0 upgraded, 4 newly installed, 0 to remove and 12 not upgraded.
Need to get 0 B/1,735 kB of archives.
After this operation, 8,373 kB of additional disk space will be used.
Do you want to continue? [Y/n] Abort.

That was because of the new sudo default use_pty, and there seemed to be no 
workaround, so I switched to sending apt's STDERR to a temporary file instead. 
Life could go on.

Background:
The function which ran apt was part of a long script which logged all its 
output to a file for later possible bugfixing, using this line near the 
beginning:

exec > >( tee -ia "$logfile" ) 2>&1

Once the apt functions no longer used the previous subshell capturing then 
everything worked fine, until recently, when the aborts reappeared, but only 
under very specific circumstances, all these:

*) use_pty is set in /etc/sudoers (now default and desirable for security)
*) the apt command is run in a new terminal launched with  -e bash -c 
''
*) the terminal is urxvt (I tested xterm, gnome-terminal, lxterminal and 
terminator - none aborted)
*) the apt command output is either piped (apt install mirage | cat) or 
redirected to a process substitution (as in the above exec).

Redirecting STDERR to a file (sudo apt-get install mirage 2>"$tempfile") is 
fine,
and even redirecting STDOUT to a file works (typing blind!).
Redirecting to a command triggers the Abort.

Examples of commands which will cause apt to abort:
urxvt -e bash -c "sudo apt-get install mirage >  >( tee -ia \"$logfile\" )"
urxvt -e bash -c 'sudo apt-get install mirage | cat'
urxvt -e bash -c 'sudo apt-get install mirage | tee /dev/null'
urxvt -e bash -c 'sudo apt-get install mirage >  >( cat )'
urxvt -e bash -c 'sudo apt-get install mirage 2>  >( cat )'

Examples where the Abort is NOT triggered:
urxvt -e bash -c "sudo apt-get install mirage >$filename"
urxvt -e bash -c "sudo apt-get install mirage 2>$filename"
urxvt -e bash -c 'sudo apt-get install mirage 3>  >( cat )'
urxvt -e bash -c "sudo apt-get install mirage 3>  >( tee -ia \"$logfile\" )"
any command where the terminal is not urxvt
any command run directly in the terminal, not in a new one with -e

In fact, to see what's happening in the terminal before it closes, you should 
append a 'read' command:
urxvt -e bash -c "sudo apt-get install mirage >  >( tee -ia \"$logfile\" ); echo 
'Press any key to continue'; read -srn1"

So, is this a urxvt bug, or is it doing the Right Thing here when in a 
pseudo-terminal and all the others are not?

More practically, is there now any way to record a script's STDOUT to a 
logfile, while also showing it to the user, while urxvt is set as 
x-terminal-emulator, if that script is going to run apt commands with sudo?

--
John

Re: Too much log for sudo.

[Andy Smith]

Hello,

On Thu, Oct 12, 2023 at 10:15:26PM +, Andy Smith wrote:
> On Thu, Oct 12, 2023 at 05:20:58PM +0200, Erwan David wrote:
> > I see that in the logs the VALUE of the env variable is loggued.
> > How to change this ?
> 
> I don't think there is a way to stop that happening. If sudo will
> log, it logs the names and values of any environment you specify on
> its command line.
> 
> Your options as far as I am aware:

Another (gross) one:

- Abuse variables that start with LC_, as sudo on Debian is by
  default configured to preserve these. So you'd call sudo without
  any --preserve-env at all after setting two LC_* variables for
  your repo and passphrase (or just the passphrase and use a
  --preserve-env for the repo if you don't care about that one being
  logged).

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: Too much log for sudo.

[Karl Vogel]

On Thu, Oct 12, 2023 at 11:22:00AM -0400, Erwan David wrote:
> I use a script to run borg backup. For it to be able to backup files that
> only root may read, i use sudo --preserv-env=BORG_REPO,BORG_PASSPHRASE.
> 
> However I see that in the logs the VALUE of the env variable is loggued. How
> to change this?

You can either run "sudo -E" to push the entire environment through without
echoing any values in the sudo log, or play some games by re-invoking the
script with a clean environment.  My environment with the BORG variables:

me% export BORG_REPO=/path/to/repo
me% export BORG_PASSPHRASE='horse battery'

me% env | sort
ATTRIBUTION=%f wrote:
BLOCKSIZE=1m
BORG_PASSPHRASE=horse battery
BORG_REPO=/path/to/repo
EDITOR=vim

[diaper-load of other variables]

XDG_CACHE_HOME=/home/vogelke/.cache
XDG_CONFIG_HOME=/home/vogelke/.config
XDG_DATA_HOME=/home/vogelke/.local/share
XDG_RUNTIME_DIR=/home/vogelke/.local/run
XDG_STATE_HOME=/home/vogelke/.local/state

Script to see if I'm running under a regular environment -- if so, restart
the same script with a bare minimum environment plus the BORG variables:

me% cat tst
#!/bin/bash
#

Re: Too much log for sudo.

[Andy Smith]

Hi,

On Thu, Oct 12, 2023 at 05:20:58PM +0200, Erwan David wrote:
> I use a script to run borg backup. For it to be able to backup files that
> only root may read, i use sudo --preserv-env=BORG_REPO,BORG_PASSPHRASE.
> 
> However I see that in the logs the VALUE of the env variable is loggued. How
> to change this ?

I don't think there is a way to stop that happening. If sudo will
log, it logs the names and values of any environment you specify on
its command line.

Your options as far as I am aware:

- Preserve your entire environment with sudo --preserve-env (no
  specific variables). It won't log the entire environment.

- Add an entry to sudoers that says to not log this particular
  command. There'll be no logging at all.

- Run the job as root to begin with.

- Make your script source another shell file that contains

  BORG_PASSPHRASE=whatever

  and have that file with appropriate restricted permissions.

Thanks,
Andy

Too much log for sudo.

[Erwan David]

I use a script to run borg backup. For it to be able to backup files 
that only root may read, i use sudo --preserv-env=BORG_REPO,BORG_PASSPHRASE.


However I see that in the logs the VALUE of the env variable is loggued. 
How to change this ?

Re: "sudo apt-get install android-tools-adb" ... (then no device listed)

[Anssi Saari]

David Wright  writes:

> You'd have to specify a set of criteria to test. I just treat
> /media/samsungd like any other filesystem, copying files in the
> usual manner.

Well, when I last tried MTP in Linux I got maybe half of a directory
listing and then it hung there. Concluded it doesn't work but to be sure
it's been a minute.

Re: "sudo apt-get install android-tools-adb" ... (then no device listed)

[David Wright]

On Mon 25 Sep 2023 at 21:08:34 (+0300), Anssi Saari wrote:
> David Wright  writes:
> > On Sun 24 Sep 2023 at 22:13:20 (+), Albretch Mueller wrote:
> >> On 9/24/23, Marco M.  wrote:
> >> > On most Android phones, you need to explicit allow data transfers.
> >> 
> >>  What do you functionally mean? I need for you to talk to me like
> >> this:  a) go "Settings"; b) ...
> >
> > On bullseye I have android-file-transfer installed. I connect the
> > phone to the PC with USB, and run this function:
> >
> >   samsungd () 
> >   { 
> >   sudo mkdir -p /media/samsungd || true;
> >   sudo chown "$USER" /media/samsungd;
> >   aft-mtp-mount /media/samsungd
> >   }
> 
> Does this android-file-transfer provide a working and reliable MTP
> implementation for Linux then? I think I'll stick with rsync and adb but
> would be good to know if MTP is working on Linux these days.

You'd have to specify a set of criteria to test. I just treat
/media/samsungd like any other filesystem, copying files in the
usual manner. As mentioned in:

  https://en.wikipedia.org/wiki/Media_Transfer_Protocol

the phone screens are operable while connected (though I haven't
tested making calls), file modification timestamps are only preserved
phone→PC, not the other way, and you don't have to worry about pulling
the plug before unmounting.

In contrast, older phones that use MSC are inoperable as the screen is
locked, with a warning not to physically disconnect until a button has
been tapped.

Cheers,
David.

Re: "sudo apt-get install android-tools-adb" ... (then no device listed)

[David Wright]

On Mon 25 Sep 2023 at 17:41:13 (+), Albretch Mueller wrote:
> On 9/24/23, Michel Verdier  wrote:
> > If you use USB you need a cable allowing data, some allow only power.
> 
>  The  USB cable I have been using to charge the battery of that phone
> visually seems to be the same exact one being advertised as doubling
> as a data cable, but running:
>  $ sudo lsusb
>  Before and after plugging in the phone doesn’t show any difference.
>  Is there a way to test for sure that cable is the right one?

You should see lines appear in the kern.log (or wherever you have
configured your logs) like:

  kernel: usb 2-2: new high-speed USB device number 15 using xhci_hcd
  kernel: usb 2-2: New USB device found, idVendor=04e8, idProduct=6860, 
bcdDevice= 4.04
  kernel: usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
  kernel: usb 2-2: Product: SAMSUNG_Android
  kernel: usb 2-2: Manufacturer: SAMSUNG
  kernel: usb 2-2: SerialNumber: ABCDEF123GH
  kernel: cdc_acm 2-2:1.1: ttyACM0: USB ACM device

when you connect it and

  kernel: usb 2-2: USB disconnect, device number 15

when you disconnect.

On Mon 25 Sep 2023 at 19:21:53 (+), Albretch Mueller wrote:
> On 9/25/23, Albretch Mueller  wrote:
> >  Most probably there is a setting in that phone I haven’t been able to
> > find.

That's possible. I tried to think back to when I first connected up
the phone and, searching diligently, I recalled that when the phone
is connected (data cable, obviously), swiping down the Notifications
screen shows an entry "USB for file transfer". Tapping that changes
it to:

  Android System
  USB for file transfer
  Tap for other USB options

Tapping the last gives another screen with "radio" options to:

  Control USB by This/Connected device
  Use USB for FileTransfer/Tethering/MIDI/ImageTransfer/ChargingOnly

plus a "slider" to transcode exported video. I selected both the
first options. You might have a phone still set to charging only.
On this phone, the selected options stay as selected, though I have
to change the second set when I tether (only done that in the UK).

>  Android awakens when I unplug the cable from the computer; so,
> something is being somehow detected.

Typically that would only indicate that the phone was switched on
and being charged. It could be a data cable, or a power-only one,
like those ones with a bunch of different connectors on the end.

On Mon 25 Sep 2023 at 17:41:13 (+), Albretch Mueller wrote:
> On 9/25/23, Marco  wrote:
> > According to the Google documentation:
> 
>  which I found:
> 
> // __ Transfer files between your computer and Android device
> 
>  https://support.google.com/android/answer/9064445?hl=en-GB
> ~
>  doesn’t really explain what to do. They apparently want for you to
> transfer your files to google drive and all that non sense.

That's not the way I read Option 2: Move files with a USB cable.
My method is very similar to option 2's Mac computer:

  1 Download and install Android File Transfer on your computer.
  4 With a USB cable, connect your device to your computer.

Just the same.

  5 On your device, tap the 'Charging this device via USB' notification.
  6 Under 'Use USB for', select File transfer.

As outlined above.

  2 Open Android File Transfer. The next time that you connect your device, it 
opens automatically.

That's when I run my samsungd command.

  3 Unlock your device.

That's when I tap "Allow". (Using the term "unlock" is confusing to me.)

  7 An Android File Transfer window will open on your computer. Use it to drag 
files.

Perhaps linux DEs do that too, IDK. I just use mc, cp, or anything
else you'd use for a mounted filesystem. (And tools like find,
du and df etc.)

Before their final step, I unmount (with fusermount -u) the
filesystem, but that step is a convenience for the PC side,
taking listings, and removing the mount point.

  8 When you've finished, unplug the USB cable.

This is safe to do at any time.

I don't know anything about clouds etc, and have only used Google
on the phone (AFAIK) for regular searches, maps, and navigation.
I archive my photos, along with those from all the other cameras
of mine, on spinning rust.

>  I also tried mtp fs utility, but I am getting the error message:
> detect failed: no MTP devices found
> 
>  go-mtpfs -android  ""
>  2023/09/25 12:10:10 detect failed: no MTP devices found
> ~
>  I also tried jmtpfs:
> 
> $ which jmtpfs
> /usr/bin/jmtpfs
> 
> $ jmtpfs --version
> jmtpfs version: 0.5
> FUSE library version: 2.9.9
> fusermount version: 2.9.9
> using FUSE kernel interface version 7.19
> 
> $ sudo jmtpfs
> No mtp devices found.

I've no experience with using them, and don't know the pros and cons,
not having had the need. They're mentioned in:

  https://wiki.archlinux.org/title/Media_Transfer_Protocol

Cheers,
David.

Re: "sudo apt-get install android-tools-adb" ... (then no device listed)

[Jeffrey Walton]

On Mon, Sep 25, 2023 at 10:13 PM Jeffrey Walton  wrote:
>
> On Mon, Sep 25, 2023 at 7:05 PM Albretch Mueller  wrote:
> >
> > On 9/24/23, Michel Verdier  wrote:
> > > If you use USB you need a cable allowing data, some allow only power.
> >
> >  The  USB cable I have been using to charge the battery of that phone
> > visually seems to be the same exact one being advertised as doubling
> > as a data cable, but running:
> >  $ sudo lsusb
> >  Before and after plugging in the phone doesn’t show any difference.
> >  Is there a way to test for sure that cable is the right one?
>
> It sounds like you are using a charging cable, or a cheap data cable.
> I would try a quality data cable before going down the rabbit hole.
>
> You should also state which USB protocol your phone uses. Different
> USB standards have different requirements. For example, USB 1.0 and
> 2.0 only need a 4-wire data cable (PWR, GND, D+ and D-). USB-C needs a
> 24-pin data cable and must implement the USB-PD protocol.
>
> Also see <https://www.google.com/search?q=usb+cable+pinouts>.

And one other thing I've found, but I have no explanation for...

Sometimes you cannot use an intermediate USB hub. I have a Dell XPS
8930 and Pixel 4a. I also bought a USB 3.0 Hub with power ports for
charging from my desktop,
<https://www.amazon.com/gp/product/B075NMVGP7>.

When I want to use adb, I have to plug the phone directly into the
computer. When the phone is directly plugged into the computer, 'adb
install ' works as expected. I can also transfer pictures.

When plugged into the hub, I can only install small apk's. If the apk
is too large, then I get an error when running 'adb install '.
You may experience the same or a similar problem with large file
transfers.

Like I said, I have no explanation for it. I just know it happens.
When I experience it, I plug the phone directly into the computer.

Jeff

Re: "sudo apt-get install android-tools-adb" ... (then no device listed)

[Jeffrey Walton]

On Mon, Sep 25, 2023 at 7:05 PM Albretch Mueller  wrote:
>
> On 9/24/23, Michel Verdier  wrote:
> > If you use USB you need a cable allowing data, some allow only power.
>
>  The  USB cable I have been using to charge the battery of that phone
> visually seems to be the same exact one being advertised as doubling
> as a data cable, but running:
>  $ sudo lsusb
>  Before and after plugging in the phone doesn’t show any difference.
>  Is there a way to test for sure that cable is the right one?

It sounds like you are using a charging cable, or a cheap data cable.
I would try a quality data cable before going down the rabbit hole.

You should also state which USB protocol your phone uses. Different
USB standards have different requirements. For example, USB 1.0 and
2.0 only need a 4-wire data cable (PWR, GND, D+ and D-). USB-C needs a
24-pin data cable and must implement the USB-PD protocol.

Also see <https://www.google.com/search?q=usb+cable+pinouts>.

Jeff

Re: "sudo apt-get install android-tools-adb" ... (then no device listed)

[Michel Verdier]

On 2023-09-25, Albretch Mueller wrote:

>  Is there a way to test for sure that cable is the right one?

Usually the original cable furnished with the phone is a data cable. My
only test was to successfully use adb then change cable and see that I
have some power only cables.

Re: "sudo apt-get install android-tools-adb" ... (then no device listed)

[Michel Verdier]

On 2023-09-25, Albretch Mueller wrote:

>  Android awakens when I unplug the cable from the computer; so,
> something is being somehow detected.

android also awakens on power on/off

Re: "sudo apt-get install android-tools-adb" ... (then no device listed)

[Nicolas George]

David Wright (12023-09-25):
> On bullseye I have android-file-transfer installed. I connect the
> phone to the PC with USB, and run this function:

If we are sharing how we do file transfer to and from an Android phone:

My favorite solution is tu install Termux and run sshd in it. Then I can
use rsync or anything I want to do the transfer. Add Tinc to get a
stable reachable IP.

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature

Re: "sudo apt-get install android-tools-adb" ... (then no device listed)

[Albretch Mueller]

On 9/25/23, Albretch Mueller  wrote:
>  Most probably there is a setting in that phone I haven’t been able to
> find.

 Android awakens when I unplug the cable from the computer; so,
something is being somehow detected.

 lbrtchx

Re: "sudo apt-get install android-tools-adb" ... (then no device listed)

[Anssi Saari]

David Wright  writes:

> On Sun 24 Sep 2023 at 22:13:20 (+), Albretch Mueller wrote:
>> On 9/24/23, Marco M.  wrote:
>> > On most Android phones, you need to explicit allow data transfers.
>> 
>>  What do you functionally mean? I need for you to talk to me like
>> this:  a) go "Settings"; b) ...
>
> On bullseye I have android-file-transfer installed. I connect the
> phone to the PC with USB, and run this function:
>
>   samsungd () 
>   { 
>   sudo mkdir -p /media/samsungd || true;
>   sudo chown "$USER" /media/samsungd;
>   aft-mtp-mount /media/samsungd
>   }

Does this android-file-transfer provide a working and reliable MTP
implementation for Linux then? I think I'll stick with rsync and adb but
would be good to know if MTP is working on Linux these days.

Re: "sudo apt-get install android-tools-adb" ... (then no device listed)

[Albretch Mueller]

On 9/24/23, Michel Verdier  wrote:
> If you use USB you need a cable allowing data, some allow only power.

 The  USB cable I have been using to charge the battery of that phone
visually seems to be the same exact one being advertised as doubling
as a data cable, but running:
 $ sudo lsusb
 Before and after plugging in the phone doesn’t show any difference.
 Is there a way to test for sure that cable is the right one?
~
On 9/25/23, Marco  wrote:
> According to the Google documentation:

 which I found:

// __ Transfer files between your computer and Android device

 https://support.google.com/android/answer/9064445?hl=en-GB
~
 doesn’t really explain what to do. They apparently want for you to
transfer your files to google drive and all that non sense.

 I also tried mtp fs utility, but I am getting the error message:
detect failed: no MTP devices found

 go-mtpfs -android  ""
 2023/09/25 12:10:10 detect failed: no MTP devices found
~
 I also tried jmtpfs:

$ which jmtpfs
/usr/bin/jmtpfs

$ jmtpfs --version
jmtpfs version: 0.5
FUSE library version: 2.9.9
fusermount version: 2.9.9
using FUSE kernel interface version 7.19

$ sudo jmtpfs
No mtp devices found.
~
 Most probably there is a setting in that phone I haven’t been able to find.

 lbrtchx

Re: "sudo apt-get install android-tools-adb" ... (then no device listed)

[David Wright]

On Sun 24 Sep 2023 at 22:13:20 (+), Albretch Mueller wrote:
> On 9/24/23, Marco M.  wrote:
> > On most Android phones, you need to explicit allow data transfers.
> 
>  What do you functionally mean? I need for you to talk to me like
> this:  a) go "Settings"; b) ...

On bullseye I have android-file-transfer installed. I connect the
phone to the PC with USB, and run this function:

  samsungd () 
  { 
  sudo mkdir -p /media/samsungd || true;
  sudo chown "$USER" /media/samsungd;
  aft-mtp-mount /media/samsungd
  }

whereupon the phone will ask:

  Allow access to phone data?
  … …
 [Deny]   [Allow]

Tapping Allow makes the contents of the phone appear under
/media/samsungd. I use mc to transfer files in each direction.
When I've finished, I run:

  unsamsungd () 
  { 
  ###;
  fusermount -u /media/samsungd;
  sudo rmdir /media/samsungd || true
  }

and disconnect the cable (the one that came in the box with the phone).

Actually, the ### is really a call to a function that runs a flavour
of updatedb, and generates a compressed ls -lAR (for mc) and a
compressed custom listing of all the files (date/size/name).
BTW the d distinguishes my own phone from our other one when they're
both connected (there's no daemon involved).

As for (android-tools-)adb, I read that unless
android-sdk-platform-tools-common is installed, you need to run adb
as root. I don't know what extra things adb buys you, compared with
android-file-transfer. I'm mainly interested in pictures, movies,
audio, and stuff like that, rather than screwing around the phone's
internals.

Cheers,
David.

Re: "sudo apt-get install android-tools-adb" ... (then no device listed)

[Roland Mueller]

As far as I remember adb requires debugging to be enabled on the Android
device.

For newer androids following - slighly obscure - process has to be used:

Enabling USB Debugging on an Android Device
- On the device, go to Settings > About .
- Tap the Build number seven times to make Settings > Developer options
available.
- Then enable the USB Debugging option.

ma 25. syysk. 2023 klo 7.52 Marco (m...@dorfdsl.de) kirjoitti:

> Am 24.09.2023 22:13 schrieb Albretch Mueller:
>
> >  What do you functionally mean? I need for you to talk to me like
> > this:  a) go "Settings"; b) ...
>
> According to the Google documentation:
> With a USB cable, connect your device to your computer.
> On your device, tap the "Charging this device via USB" notification.
> Under "Use USB for," select File Transfer.
>
>

Re: "sudo apt-get install android-tools-adb" ... (then no device listed)

[Marco]

Am 24.09.2023 22:13 schrieb Albretch Mueller:

>  What do you functionally mean? I need for you to talk to me like
> this:  a) go "Settings"; b) ...

According to the Google documentation:
With a USB cable, connect your device to your computer.
On your device, tap the "Charging this device via USB" notification.
Under "Use USB for," select File Transfer.

Re: "sudo apt-get install android-tools-adb" ... (then no device listed)

[Albretch Mueller]

On 9/24/23, Marco M.  wrote:
> On most Android phones, you need to explicit allow data transfers.

 What do you functionally mean? I need for you to talk to me like
this:  a) go "Settings"; b) ...

 Thank you,
 lbrtchx

On 9/24/23, Marco M.  wrote:
> Am 24.09.2023 um 19:45:11 Uhr schrieb Albretch Mueller:
>
>>  How can you troubleshoot that problem or, do you know about any other
>> way to transfer your data to a drive off your phone?
>
> On most Android phones, you need to explicit allow data transfers.
> Did you do?
>
>

Re: "sudo apt-get install android-tools-adb" ... (then no device listed)

[Michel Verdier]

On 2023-09-24, Albretch Mueller wrote:

>  Basically, I need to transfer selected data (whatsapp, messages,
> phone calls, ...) off my phone to my computer's hdd.
>
>  How can you troubleshoot that problem or, do you know about any other
> way to transfer your data to a drive off your phone?

If you use USB you need a cable allowing data, some allow only power.
Then you have to enable USB debug in developpement options (which you
have to enable using some magic specific to your model, search internet
for it). And USB must be accepted in MTP mode on your phone (usually by
default). If all this is done your device should be listed.

There is also some applications that can do transfer, like syncopoli
using rsync without USB. Or syncthing. Or termux on which you can use
subversion or git or other unix tools.

Re: "sudo apt-get install android-tools-adb" ... (then no device listed)

[Marco M.]

Am 24.09.2023 um 19:45:11 Uhr schrieb Albretch Mueller:

>  How can you troubleshoot that problem or, do you know about any other
> way to transfer your data to a drive off your phone?

On most Android phones, you need to explicit allow data transfers.
Did you do?

"sudo apt-get install android-tools-adb" ... (then no device listed)

[Albretch Mueller]

$ uname -a
Linux debian 5.10.0-18-amd64 #1 SMP Debian 5.10.140-1 (2022-09-02)
x86_64 GNU/Linux

$ sudo apt-get update
...

$ date; sudo apt-get install android-tools-adb
Sun 24 Sep 2023 02:07:24 PM UTC
...

$ which adb
/usr/bin/adb

$ adb --version
Android Debug Bridge version 1.0.41
Version 28.0.2-debian
Installed as /usr/lib/android-sdk/platform-tools/adb

$ adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached

$

 As usual (being a TI makes your life so enjoyable!) I found similar
posts online and ways to solve such problems (some of them quite
voodoo-like):

 
https://stackoverflow.com/questions/21170392/my-android-device-does-not-appear-in-the-list-of-adb-devices
~
 Basically, I need to transfer selected data (whatsapp, messages,
phone calls, ...) off my phone to my computer's hdd.

 How can you troubleshoot that problem or, do you know about any other
way to transfer your data to a drive off your phone?

 lbrtchx

Re: Using the bash shell: determine if the root user used 'sudo -i'

[Greg Wooledge]

On Sat, Aug 26, 2023 at 06:42:42PM -0400, Karl Vogel wrote:
> If you're running bash, the safest way to find your current working
> directory is capturing the output from /bin/pwd.  Symlinked directories
> can surprise you:
> 
> me$ cd
> 
> me$ ls -ldF today
> lrwxr-xr-x  1 me mis   18 Aug 26 00:03 today@ -> notebook/2023/0826
> 
> me$ cd today
> 
> me$ pwd
> /home/me/today
> 
> me$ /bin/pwd
> /home/me/notebook/2023/0826
> 
> me$ echo $PWD
> /home/me/today

unicorn:~$ help pwd
pwd: pwd [-LP]
Print the name of the current working directory.

Options:
  -Lprint the value of $PWD if it names the current working
directory
  -Pprint the physical directory, without any symbolic links

By default, `pwd' behaves as if `-L' were specified.
[...]

Of course, this is all a big tangent from the original request.

Re: Using the bash shell: determine if the root user used 'sudo -i'

[Karl Vogel]

On Sat, Aug 26, 2023 at 12:09:57PM -0400, Tom Browder wrote:
> Excellent mind-reading, Greg! So to use your line I will put in that dir:
> "cd /required-dir || exit"
> 
> Thanks so much.  And thanks to all others who responded.

If you're running bash, the safest way to find your current working
directory is capturing the output from /bin/pwd.  Symlinked directories
can surprise you:

me$ cd

me$ ls -ldF today
lrwxr-xr-x  1 me mis   18 Aug 26 00:03 today@ -> notebook/2023/0826

me$ cd today

me$ pwd
/home/me/today

me$ /bin/pwd
/home/me/notebook/2023/0826

me$ echo $PWD
/home/me/today

If you want to know why you had an early exit:

me$ cat try
#!/usr/bin/env bash
# try: test logging.

export PATH=/usr/local/bin:/bin:/usr/bin
set -o nounset  # check for unbound variables.
tag=${0##*/}
umask 022

# Test file descriptor 2 for interactive or cron use.
test -t 2
case "$?" in
0) logmsg () { echo "$(date '+%F %T') $tag: $@"; } ;;
*) logmsg () { logger -t $tag "$@"; }  ;;
esac

warn () { logmsg "WARN: $@" ; }
die ()  { logmsg "FATAL: $@"; exit 1 ; }

# Real work starts here.
case "$#" in
0)  die "need a directory" ;;
*)  dir="$1" ;;
esac

test -d "$dir" || die "$dir: not a directory"
cd "$dir"  || die "$dir: cannot cd"
cwd=$(/bin/pwd)

logmsg "start working in $cwd"
exit 0

On FreeBSD, you can use "daemon" to run something detached from the
controlling terminal, which simulates running a cron job:

me$ ls -ldF /etc /var/authpf
drwxr-xr-x 27 root wheel  120 26-Aug-2023 07:55:02 /etc/
drwxrwx---  2 root authpf   2 05-Jul-2019 00:45:45 /var/authpf/

me$ ./try /etc
2023-08-26 18:31:54 try: start working in /etc

me$ daemon -f $PWD/try /etc
me$ daemon -f $PWD/try /var/authpf

me$ tail -2 /var/log/syslog
Aug 26 18:19:17 myhost try: start working in /etc
Aug 26 18:19:19 myhost try: FATAL: /var/authpf: cannot cd

Hope this helps.

--
Karl Vogel  I don't speak for anyone but myself.

Oh, my darlin' had bronchitis and she barfed up half a lung,
what came up looked quite amazing when she rolled it on her tongue.
   --sung to the tune of "My Darling Clementine"

Re: Using the bash shell: determine if the root user used 'sudo -i'

[tomas]

On Sat, Aug 26, 2023 at 01:54:41PM -0500, Tom Browder wrote:
> On Sat, Aug 26, 2023 at 10:42  wrote:

[...]

> > Basically it is not possible to find out [...]

> As I think I replied earier, I am now checking the script is in the
> required directory in order to be executed (by the root user) [...]

Yes, it seems our posts crossed.

Anyway, glad you found a solution.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Using the bash shell: determine if the root user used 'sudo -i'

[Tom Browder]

On Sat, Aug 26, 2023 at 10:42  wrote:

> On Sat, Aug 26, 2023 at 04:45:54PM +0200, DdB wrote:
> > Am 26.08.2023 um 16:25 schrieb Tom Browder:
> > > Is there a way to distinguish whether 'sudo -i' was used or not?
> > >
> > Sorry, i am not an expert on this. But ... since years i am using this
> > to check for it:
> >
> > > # if `echo $HOME` is not "/root" or the working dir (pwd) is not
> "/root", then this was not executed with "sudo -i"
> > > assert "echo $HOME" /root "nicht mit sudo -i aufgerufen"
> > > assert pwd /root "nicht mit sudo -i aufgerufen"
> >
> > hope, this will give you a clue ;-)
> > DdB
>
> Unless, of course, the shell does "export HOME=/root" at some point
> after start. Or one of the other fifty-two ways to achieve that.
>
> That's why I think Roberto is right elsewhere in this thread.
>
> Basically it is not possible to find out, so it makes sense to
> think about the question "why do I need this?" to zoom into what
> the real problem is. Perhaps that one can be solved :-)


As I think I replied earier, I am now checking the script is in the
required directory in order to be executed (by the root user). I am not
concerned with any other caveats or use by any unauthorized users for any
nefarious purpose.

I consider this thread completed.

Thanks to all who responded--Debian users are the best!

-Tom

Re: Using the bash shell: determine if the root user used 'sudo -i'

[Nate Bargmann]

* On 2023 26 Aug 11:10 -0500, Tom Browder wrote:
> On Sat, Aug 26, 2023 at 10:57 Greg Wooledge  wrote:
> 
> > On Sat, Aug 26, 2023 at 10:49:45AM -0500, Tom Browder wrote:
> > > I would like to know whether 'sudo -i' or 'sudo -s' was used.
> 
> ...
> 
> > In fact, I suspect "I need to know if the cwd is /root" is STILL an X-Y
> > problem.  It's sounding like "I need to ensure my script's working
> > directory is /foo".  If that's truly the case, just do "cd /foo || exit"
> > at the top of the script.
> 
> ...
> 
> Excellent mind-reading, Greg! So to use your line I will put in that dir:
> 
> "cd /required-dir || exit"

In such cases I prefer specifying the complete paths in the script so as
not to get lost.  If the script needs to work in a specific directory of
root I'll put:

cd /root/dir/dir1

or something like:

cd /home/username/dir

and so on (adding whatever error recovery is needed).

If I need to source a file I just type in the complete path name.  It's
a one time bother and the executing shell doesn't care and as the script
gets more complex it's much easier to keep one's bearings on where the
script is working at various points.

As I see it, relative paths are more for interactive shell use.

- Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



signature.asc
Description: PGP signature

Re: Using the bash shell: determine if the root user used 'sudo -i'

[tomas]

On Sat, Aug 26, 2023 at 11:56:27AM -0400, Greg Wooledge wrote:
> On Sat, Aug 26, 2023 at 10:49:45AM -0500, Tom Browder wrote:
> > I would like to know whether 'sudo -i' or 'sudo -s' was used.
> 
> That's STILL an X-Y problem.
> 
> > The reason is
> > to know if the cwd is set to '/root' or '.' It's critical for the script
> > execution
> 
> Oh?  Then just look at the current working directory.  It's in the $PWD
> variable.

I guess it's better use the shell builtin pwd:

  PWD=/not/such/file/or/directory
  echo "cwd=" $(pwd) "PWD=" $PWD

(Note: your shell prompt might be a bit... messed up after
that)

> You don't actually need to know what was typed.

Yep, that was my hunch, too.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Using the bash shell: determine if the root user used 'sudo -i'

[Michael Kjörling]

On 26 Aug 2023 11:56 -0400, from g...@wooledge.org (Greg Wooledge):
> You don't actually need to know what was typed.

And even being able to answer the question "how was sudo executed"
doesn't solve the problem of ensuring that the script is executing
within a particular directory. All it takes is the user cd'ing to a
different directory before running the script.


> In fact, I suspect "I need to know if the cwd is /root" is STILL an X-Y
> problem.

Agreed.

Also, a few things worth noting:

* The current working directory will ALWAYS be ".". That's what "." at
the beginning of a relative path _means_. So testing the current
working directory against the actual path corresponding to "." will
always return a truthy result.

* The home directory of the root user won't necessarily be /root. By
convention it often is, but there's no guarantee that this is the
case.

* There can be multiple users with the same numerical user ID
(including 0), with different user names and home directories but
access to the same files. The BSDs do this often; Linux systems more
rarely so, but it's absolutely possible.

And that's just what I can think of off the top of my head.

-- 
Michael Kjörling  https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

Re: Using the bash shell: determine if the root user used 'sudo -i'

[Tom Browder]

On Sat, Aug 26, 2023 at 10:57 Greg Wooledge  wrote:

> On Sat, Aug 26, 2023 at 10:49:45AM -0500, Tom Browder wrote:
> > I would like to know whether 'sudo -i' or 'sudo -s' was used.

...

> In fact, I suspect "I need to know if the cwd is /root" is STILL an X-Y
> problem.  It's sounding like "I need to ensure my script's working
> directory is /foo".  If that's truly the case, just do "cd /foo || exit"
> at the top of the script.

...

Excellent mind-reading, Greg! So to use your line I will put in that dir:

"cd /required-dir || exit"

Thanks so much.

And thanks to all others who responded.

-Tom

Re: Using the bash shell: determine if the root user used 'sudo -i'

[Greg Wooledge]

On Sat, Aug 26, 2023 at 10:49:45AM -0500, Tom Browder wrote:
> I would like to know whether 'sudo -i' or 'sudo -s' was used.

That's STILL an X-Y problem.

> The reason is
> to know if the cwd is set to '/root' or '.' It's critical for the script
> execution

Oh?  Then just look at the current working directory.  It's in the $PWD
variable.

You don't actually need to know what was typed.

In fact, I suspect "I need to know if the cwd is /root" is STILL an X-Y
problem.  It's sounding like "I need to ensure my script's working
directory is /foo".  If that's truly the case, just do "cd /foo || exit"
at the top of the script.

Re: Using the bash shell: determine if the root user used 'sudo -i'

[Tom Browder]

On Sat, Aug 26, 2023 at 09:32 Roberto C. Sánchez  wrote:

> On Sat, Aug 26, 2023 at 09:25:10AM -0500, Tom Browder wrote:
> >In a previous thread it was shown how to detect a SUDO_USER in a bash
> >shell.
> >Is there a way to distinguish whether 'sudo -i' was used or not?


I would like to know whether 'sudo -i' or 'sudo -s' was used. The reason is
to know if the cwd is set to '/root' or '.' It's critical for the script
execution

-Tom

Re: Using the bash shell: determine if the root user used 'sudo -i'

[tomas]

On Sat, Aug 26, 2023 at 04:45:54PM +0200, DdB wrote:
> Am 26.08.2023 um 16:25 schrieb Tom Browder:
> > Is there a way to distinguish whether 'sudo -i' was used or not?
> > 
> Sorry, i am not an expert on this. But ... since years i am using this
> to check for it:
> 
> > # if `echo $HOME` is not "/root" or the working dir (pwd) is not "/root", 
> > then this was not executed with "sudo -i"
> > assert "echo $HOME" /root "nicht mit sudo -i aufgerufen"
> > assert pwd /root "nicht mit sudo -i aufgerufen"
> 
> hope, this will give you a clue ;-)
> DdB

Unless, of course, the shell does "export HOME=/root" at some point
after start. Or one of the other fifty-two ways to achieve that.

That's why I think Roberto is right elsewhere in this thread.

Basically it is not possible to find out, so it makes sense to
think about the question "why do I need this?" to zoom into what
the real problem is. Perhaps that one can be solved :-)

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Using the bash shell: determine if the root user used 'sudo -i'

[Alain D D Williams]

On Sat, Aug 26, 2023 at 09:25:10AM -0500, Tom Browder wrote:
> In a previous thread it was shown how to detect a SUDO_USER in a bash shell.
> 
> Is there a way to distinguish whether 'sudo -i' was used or not?

I have not tested this but if bash was interactive you will find a
.bash_history file in their $HOME.

That assumes that they have not logged in - ie only ever sudo.

> Thanks.
> 
> -Tom

-- 
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT 
Lecturer.
+44 (0) 787 668 0256  https://www.phcomp.co.uk/
Parliament Hill Computers. Registration Information: 
https://www.phcomp.co.uk/Contact.html
#include 

Re: Using the bash shell: determine if the root user used 'sudo -i'

[DdB]

Am 26.08.2023 um 16:25 schrieb Tom Browder:
> Is there a way to distinguish whether 'sudo -i' was used or not?
> 
Sorry, i am not an expert on this. But ... since years i am using this
to check for it:

> # if `echo $HOME` is not "/root" or the working dir (pwd) is not "/root", 
> then this was not executed with "sudo -i"
>   assert "echo $HOME" /root "nicht mit sudo -i aufgerufen"
>   assert pwd /root "nicht mit sudo -i aufgerufen"

hope, this will give you a clue ;-)
DdB

Re: Using the bash shell: determine if the root user used 'sudo -i'

[Roberto C . Sánchez]

On Sat, Aug 26, 2023 at 09:25:10AM -0500, Tom Browder wrote:
>In a previous thread it was shown how to detect a SUDO_USER in a bash
>shell.
>Is there a way to distinguish whether 'sudo -i' was used or not?
>Thanks.
>-Tom

The SUDO_COMMAND environment variable would report /bin/bash in that
instance. Would that be sufficient for your needs?

If not, then what exactly are you trying to accomplish? Please don't say
"I want to know if sudo -i was used" because we already know that. Why
is that a necessary piece of information in your use case? What will you
do with that information? What decision will you make? What action will
you take?

Regards,

-Roberto

-- 
Roberto C. Sánchez

Using the bash shell: determine if the root user used 'sudo -i'

[Tom Browder]

In a previous thread it was shown how to detect a SUDO_USER in a bash shell.

Is there a way to distinguish whether 'sudo -i' was used or not?

Thanks.

-Tom

Re: setting paths for sudo (revisited)

[Tom Browder]

On Mon, Aug 21, 2023 at 08:11 Greg Wooledge  wrote:

> On Mon, Aug 21, 2023 at 07:56:22AM -0500, Tom Browder wrote:
> > For Greg: I'm trying to get my muscle memory to use "sudo -i" and "sudo
> -s"
> > as you said to become root user for more work (thanks for the great
> > explanation).
> >
> > One more question: when I need a one-liner as root, do I also use the
> '-i'
> > or '-s' with sudo to get the desired path?
>
> No.  sudo sets the PATH for you.  You only need -i or -s when you want
> to get an interactive shell, instead of running a specific command.


Thanks. When I get a multi-user system working with Raku as I want it to,
I'll post it on this thread for your critique. On the original thread you
kept wanting me to describe in detail my use case. The problem was (and
still is) how to handle the following requirements:

1. Have root install the Raku executable for all users

2. Have the root user install modules for himself, but have normal users
see and use them in their normal path.

3. Allow normal users to install their own modules which, for them only,
would override the global version.

This is somewhat analogous to Perl, but zef, the equivalebt Raku installer,
is a bit pickier than cpanm about overrides.

Best regards,

-Tom

P.S. Note Debian does have a Raku package, but most real users would rather
use the latest and greatest. The language is under heavy development and
there are real advantages for power users to stay current (a new version is
normally release monthly). There is a painless Debian package system
provided by our community similar to those provided by the PostgreSQL
community.

Do not think the syntax or user-space is changing due to the fast pace.
Certain older things are deprecated and announced automatically when using
them. Old code is usually compatible with new releases. A new release is
always back-compatible until a new version is released. Raku is on its
second version since its initial stable version release in December 2015.
The third version, v6.e, is in the wings. And a user can always install an
older release if all else fails.