On Tue, Aug 24, 2021 at 10:34:22PM +0200, François Patte wrote:
Le 2021-08-24 19:03, Samuel Sieb a écrit :
On 2021-08-24 9:50 a.m., François Patte wrote:
Thank you for your explanations. I made some progress in my
investigations: the problem seems to be a change in the "su"
command from f32
Le 2021-08-24 19:03, Samuel Sieb a écrit :
On 2021-08-24 9:50 a.m., François Patte wrote:
Thank you for your explanations. I made some progress in my
investigations: the problem seems to be a change in the "su" command
from f32 to f34: my personnal umask is 0077 and I use to log as root
using
On Tue, Aug 24, 2021 at 11:43:10AM -0600, Joe Zeff wrote:
On 8/24/21 11:03 AM, Samuel Sieb wrote:
umask isn't an environment variable. It's a kernel setting for the
process. Why are you using "su" anyway instead of "sudo"? (I don't
know if that will change anything regarding the umask, but
I'm looking to upgrade from Fedora 32 to Fedora 34
Does pipewire support the Apple Airplay protocol featured in pulseaudio?
Specifically, the pulseaudio module-raop-sink ?
My setup is: Rhythmbox --> pulseaudio (module-raop-sink) --> RaspberryPi
(Shairport Sync AirPlay audio player)
Or is
On 8/24/21 11:03 AM, Samuel Sieb wrote:
umask isn't an environment variable. It's a kernel setting for the
process. Why are you using "su" anyway instead of "sudo"? (I don't
know if that will change anything regarding the umask, but it's better
to not have a root password.)
I can't speak
On 2021-08-24 1:03 p.m., Samuel Sieb wrote:
On 2021-08-24 9:50 a.m., François Patte wrote:
Thank you for your explanations. I made some progress in my
investigations: the problem seems to be a change in the "su" command
from f32 to f34: my personnal umask is 0077 and I use to log as root
On 2021-08-24 9:50 a.m., François Patte wrote:
Thank you for your explanations. I made some progress in my
investigations: the problem seems to be a change in the "su" command
from f32 to f34: my personnal umask is 0077 and I use to log as root
using the command "su -". Until f32 this way of
Le 2021-08-24 15:17, Jonathan Billings a écrit :
On Tue, Aug 24, 2021 at 10:28:17AM +0200, François Patte wrote:
The only file talking of umask is /etc/bashrc:
if [ $UID -gt 199 ] && [ "`id -gn`" = "`id -un`" ]; then
umask 002
else
umask 022
fi
I don't understand the
On Tue, Aug 24, 2021 at 10:28:17AM +0200, François Patte wrote:
> The only file talking of umask is /etc/bashrc:
>
> if [ $UID -gt 199 ] && [ "`id -gn`" = "`id -un`" ]; then
>umask 002
> else
>umask 022
> fi
>
> I don't understand the meaning
It means:
If your
Le 2021-08-24 11:29, Tim via users a écrit :
François Patte:
I have another computer with fedora 32 and the default umask for
root is 0022. Has config been changed from f32 to f34?
Samuel Sieb:
All my F34 systems have a umask of 0022 for root, so it must be
something specific to yours.
The
François Patte:
>> I have another computer with fedora 32 and the default umask for
>> root is 0022. Has config been changed from f32 to f34?
Samuel Sieb:
> All my F34 systems have a umask of 0022 for root, so it must be
> something specific to yours.
The first thing that springs to mind when
Le 2021-08-24 10:34, Samuel Sieb a écrit :
On 8/24/21 1:28 AM, François Patte wrote:
Le 2021-08-23 23:34, Joe Wulf via users a écrit :
Check: /etc/bashrc, /etc/profile, /root/.bash_profile and
/root/.bashrc, in that order
The only file talking of umask is /etc/bashrc:
if [ $UID -gt
On 8/24/21 1:28 AM, François Patte wrote:
Le 2021-08-23 23:34, Joe Wulf via users a écrit :
Check: /etc/bashrc, /etc/profile, /root/.bash_profile and
/root/.bashrc, in that order
The only file talking of umask is /etc/bashrc:
if [ $UID -gt 199 ] && [ "`id -gn`" = "`id -un`" ]; then
Le 2021-08-23 23:34, Joe Wulf via users a écrit :
Check: /etc/bashrc, /etc/profile, /root/.bash_profile and
/root/.bashrc, in that order
The only file talking of umask is /etc/bashrc:
if [ $UID -gt 199 ] && [ "`id -gn`" = "`id -un`" ]; then
umask 002
else
umask 022
14 matches
Mail list logo
