On 10/03/2022 20:44, Michael wrote:
~ # sysctl -a | grep fs.protected_regular
fs.protected_regular = 1
To check the current value of a setting, you can just run:
sysctl fs.protected_regular
No grep or root needed.
Greetings,
On Wednesday, 2022-03-09 19:28:49 +0100, I myself wrote:
> ...
>$ touch /tmp/file
>$ ls -l /tmp/file
>-rw--- 1 rainer rainer 0 2022-03-09 19:06 /tmp/file
>$ echo x | sudo tee /tmp/file
>Password:
>tee: /tmp/file: Permission denied
>x
>$ ...
>$
On 10/03/2022 11:55, Dr Rainer Woitok wrote:
Big thanks to all kind people making suggestions. But up to now nothing
helped.
Are you sure that:
sysctl fs.protected_regular=0
does not help? I can reproduce it here on my system with kernel 5.15.27,
and setting that sysctl to 0 fixes it
Hello Rainer,
Big thanks to all kind people making suggestions. But up to now nothing
helped.
on my rig I can fully reproduce Nikos' statement.
Additionally, on 5.15.16 "fs.protected_regular" defaults to "0" while on
5.15.27 it defaults to "1".
Cheers,
Björn
Hello,
I am trying to create my first package using ebuild.
I've created ebuild file pum-outss-1.0.0.ebuild in directory
/var/db/repos/pum-outss/dev-python/pum-outss
The file pum-outss-1.0.0.ebuild has following content:
EAPI=7
DESCRIPTION="Exchange data between PUM and OUTSS"
I've corrected the file /etc/make.conf as follows:
FETCHCOMMAND="/usr/bin/wget --no-check-certificate -P \${DISTDIR}
\${URI}"
RESUMECOMMAND="/usr/bin/wget -c --no-check-certificate -P \${DISTDIR}
\${URI}"
After that I've run command:
ebuild ./pum-outss-1.0.0.ebuild manifest clean unpack
This
>On 09/03/2022 20:28, Dr Rainer Woitok wrote:
>> until recently my system behaves sort of strangely:
>>
>> $ echo x | sudo tee /tmp/file
>> Password:
>> tee: /tmp/file: Permission denied
>> [...]
>>
>> Since when can't root write to files it doesn't own? And not even, if
>>
On 3/9/22 11:50 PM, Nikos Chantziaras wrote:
This is normal, at least when using systemd.
How is this a /systemd/ thing?
Is it because systemd is enabling a /kernel/ thing that probably is
otherwise un(der)used?
I ask as someone who disliked systemd as many others do. But I fail to
see
Nikos,
On Thursday, 2022-03-10 12:21:36 +0200, you wrote:
> ...
> Are you sure that:
>
> sysctl fs.protected_regular=0
>
> does not help? I can reproduce it here on my system with kernel 5.15.27,
> and setting that sysctl to 0 fixes it immediately.
No, I'm not at all sure. Since you
>
>
>-Original Message-
>From: Dr Rainer Woitok
>Sent: Thursday, March 10, 2022 9:51 AM
>To: gentoo-user@lists.gentoo.org; Nikos Chantziaras
>Subject: [gentoo-user] Re: Root can't write to files owned by others?
>
>Nikos,
>
>On Thursday, 2022-03-10 12:21:36 +0200, you wrote:
>
>> ...
>>
Here is the kernel patch: https://git.kernel.org/pub/scm/linux/kernel/git/
torvalds/linux.git/commit/?id=30aba6656f61ed44cba445a3c0d38b296fa9e8f5
for this:
Am Donnerstag, 10. März 2022, 19:44:46 CET schrieb Michael:
>
> Just checked and it is so, on openrc:
>
> ~ # uname -r
> 5.15.26-gentoo
>
On Thursday, 10 March 2022 17:59:00 GMT Laurence Perkins wrote:
> >-Original Message-
> >From: Dr Rainer Woitok
> >Sent: Thursday, March 10, 2022 9:51 AM
> >To: gentoo-user@lists.gentoo.org; Nikos Chantziaras
> >Subject: [gentoo-user] Re: Root can't write to files owned by others?
> >
>
12 matches
Mail list logo
