On Sat, Dec 30, 2023 at 11:48:31PM -0500, Robert McBroom via users wrote:
On 12/30/23 18:18, Mike Wright wrote:
On 12/30/23 15:13, Robert McBroom via users wrote:
On a system restore from a tar archive sudo won't work. Says
/usr/bin/sudo needs to be owned by 0 with the suid bit set. Root
On 12/30/23 20:48, Robert McBroom via users wrote:
On 12/30/23 18:18, Mike Wright wrote:
On 12/30/23 15:13, Robert McBroom via users wrote:
On a system restore from a tar archive sudo won't work. Says
/usr/bin/sudo needs to be owned by 0 with the suid bit set. Root
owns the file and is 0.
On 12/30/23 18:18, Mike Wright wrote:
On 12/30/23 15:13, Robert McBroom via users wrote:
On a system restore from a tar archive sudo won't work. Says
/usr/bin/sudo needs to be owned by 0 with the suid bit set. Root
owns the file and is 0. Looking at a working system directory list shows
Robert McBroom via users writes:
On a system restore from a tar archive sudo won't work. Says /usr/bin/sudo
needs to be owned by 0 with the suid bit set. Root owns the file and is 0.
Looking at a working system directory list shows
-rwsr-xr-x. 1 root root 57456 Aug 16 20:00 su
On 12/30/23 15:13, Robert McBroom via users wrote:
On a system restore from a tar archive sudo won't work. Says
/usr/bin/sudo needs to be owned by 0 with the suid bit set. Root owns
the file and is 0. Looking at a working system directory list shows
-rwsr-xr-x. 1 root root 57456
On 12/30/23 15:13, Robert McBroom via users wrote:
On a system restore from a tar archive sudo won't work. Says
/usr/bin/sudo needs to be owned by 0 with the suid bit set. Root owns
the file and is 0. Looking at a working system directory list shows
-rwsr-xr-x. 1 root root 57456
On a system restore from a tar archive sudo won't work. Says
/usr/bin/sudo needs to be owned by 0 with the suid bit set. Root owns
the file and is 0. Looking at a working system directory list shows
-rwsr-xr-x. 1 root root 57456 Aug 16 20:00 su
---s--x--x. 1 root root 202872
On Sat, Dec 30, 2023 at 1:41 AM Frederic Muller wrote:
> Problem occured after the last update but a restart fixed it (maybe a
> logging out would have worked too?). I see there is -b in your journalctl
> command. Actually the problem occurs only once logged in, not in GDM at
> all. Is the -b
On Sat, 30 Dec 2023 17:58:41 + Barry wrote:
>> On 30 Dec 2023, at 10:50, Javier Perez wrote:
>> Question here. Can I on the new install select the /boot to be btrfs? Do I
>> need to make it a separate partition or should I just let the install wizard
>> alone to do that?
> I am not sure
> On 30 Dec 2023, at 10:50, Javier Perez wrote:
>
> Question here. Can I on the new install select the /boot to be btrfs? Do I
> need to make it a separate partition or should I just let the install wizard
> alone to do that?
Let the install wizard decide.
There are rules about file system
Hi. I recently created this issue -
https://github.com/389ds/389-ds-base/issues/6020
Maybe github is not the place for such general questions so I repost it here.
In our deployments we have a lot of production environment for out clients. For
granular access every client is placed into separate
Hi Barry. Thanks. I have an additional question down.
On Fri, Dec 29, 2023 at 5:09 AM Barry Scott wrote:
>
>
> On 29 Dec 2023, at 09:02, Javier Perez wrote:
>
> Here come my questions.
> 1. Can I move everything on the SSD to a new SSD with everything under
> btrfs? From what I have been
12 matches
Mail list logo
