Displaying 20 results from an estimated 90000 matches similar to: "Ownership of /dev/snd/*"
2006 Sep 02
3
No sound after upgrade to 4.4
After upgrading from CentOS 4.3 to 4.4 the sound doesn't work anymore. Messages like the following appear in dmesg when I try to use it:
application firefox-bin uses obsolete OSS audio interface
The output from 'lsmod | snd' is:
snd_azx 21713 2
snd_hda_codec 121665 1 snd_azx
snd_pcm_oss 52729 0
snd_mixer_oss 21953 2 snd_pcm_oss
snd_pcm
2020 Mar 23
1
Re: libvirt dynamic file ownership
Hi Martin, thanks for the explanation. Now I understand why libvirt doesn't
revert the file permissions back to the original. I am running these VMs on
an isolated test machine, so I'll disable dynamic file ownership and make
sure libvirt has access to image files.
Sorry about the message formatting. I modified settings on my client,
hopefully it sends plaintext now. (I'll switch to
2020 Mar 20
0
Re: libvirt dynamic file ownership
On Fri, Mar 20, 2020 at 03:38:36PM +0000, Joe Muro wrote:
>Hi,
>
Hi, could you please configure your client to send plaintext version as well?
We mainly prefer plaintext on this list ;-)
>I am trying to understand libvirt dynamic ownership behavior. I have a VM that
>uses a qcow2 image with the following permissions:
>
>$ ll t257kvxg-10-20-101-40.qcow2
>-rw-r--r-- 1 jmuro
2020 Mar 24
0
RE: libvirt dynamic file ownership
"Michal Prívozník" <mprivozn@redhat.com> wrote on 03/23/2020 12:26:14 PM:
> From: "Michal Prívozník" <mprivozn@redhat.com>
> To: Martin Kletzander <mkletzan@redhat.com>, Joe Muro
<joemuro@us.ibm.com>
> Cc: libvirt-users@redhat.com
> Date: 03/23/2020 12:26 PM
> Subject: [EXTERNAL] Re: libvirt dynamic file ownership
>
> On 20. 3. 2020
2009 May 16
2
no snd-hda-codec.ko in CentOS 5.3 is that ok ?
Hello,
When I was running CentOS 5.2 (and other Liuux distribution) on an Asus
W2J laptop, I never get sound.
I upgraded to CentOS 5.3.
Now the sound card is recognized and plays the test sounds.
I checked channels with alsamixer, mix, kamix ....
I still have no sound using aplay alsa command or whatever else audio
display.
Trying to check my configuration I discovered that the snd-hda-codec.ko
2010 Jul 18
3
Audio fails on centos 5.5 sony laptop - snd-hda-intel
Hi List, been chasing my tail for the last two hours and getting nowhere
on my wifes laptop.
I only do updates monthly on her machine, as it is safely behind
firewalls and only does email and browser stuff.
I have never had audio problems on this laptop, Centos just worked from
day one - even the wireless.
It appears that the 5.5 kernels and related audio driver snd-hda-intel
do not function.
2012 Nov 12
2
[LLVMdev] RFC: Code Ownership
On Nov 11, 2012, at 12:44 AM, Chris Lattner wrote:
>
> On Nov 10, 2012, at 10:43 AM, Joe Abbey <jabbey at arxan.com> wrote:
>
>> Hello,
>>
>> Chris's "keynote" at the LLVM Developers' Conference included a call for code owners, and my company has a heavy dependency on Bitcode, I propose taking ownership of:
>>
>> lib/Bitcode/*
2012 Nov 12
0
[LLVMdev] RFC: Code Ownership
On Nov 11, 2012, at 5:13 PM, Meador Inge <meadori at codesourcery.com> wrote:
> On Nov 11, 2012, at 12:44 AM, Chris Lattner wrote:
>
>>
>> On Nov 10, 2012, at 10:43 AM, Joe Abbey <jabbey at arxan.com> wrote:
>>
>>> Hello,
>>>
>>> Chris's "keynote" at the LLVM Developers' Conference included a call for code
2020 Mar 23
2
Re: libvirt dynamic file ownership
On 20. 3. 2020 20:57, Martin Kletzander wrote:
> On Fri, Mar 20, 2020 at 03:38:36PM +0000, Joe Muro wrote:
>> Hi,
>>
>
> Hi, could you please configure your client to send plaintext version as
> well?
> We mainly prefer plaintext on this list ;-)
>
>> I am trying to understand libvirt dynamic ownership behavior. I have a
>> VM that
>> uses a qcow2
2003 Dec 30
5
Question about file ownership on destination
Hello
Regarding ownership on the destination:
rsync's man page indicates that when synchronizing files to a remote host,
-o implies the --numeric-ids option, which makes perfect sense aince the
named users/groups may not exist on the destination host. The problem I
have is that the files created on the destination still appear to be owned
by the local user (server1) on the rsync
2020 Mar 20
3
libvirt dynamic file ownership
<div class="socmaildefaultfont" dir="ltr" style="font-family:Arial, Helvetica, sans-serif;font-size:10pt" ><div dir="ltr" > </div>
<div dir="ltr" ><div dir="ltr" >Hi,</div>
<div dir="ltr" > </div>
<div dir="ltr" >I am trying to understand libvirt
2004 Nov 29
1
root ownership on some profile files cause login errors
Here's another question related to how to use masks --
In my PDC area I specify:
logon path = \\netapp\profiles\%u
This puts server-based (roaming) profiles on my Network Appliance (which
itself is an SMB/PDC client).
A previous admin here left this commented section:
#[profiles]
# path = /var/lib/samba/profiles # path = /netapp/profiles ???
# read only = no
# create
2018 Apr 07
0
Permissions and ownership on /dev/kvm keep reverting after starting a vm
Hey guys,
/dev/kvm permissions and ownership keeps reverting after starting a vm.
The ownership and permissions keep going back to
crw-rw—— root root ....
After starting a vm. I have to revert the perms and ownership to:
crw-crw-crw root kvm ....
To start any vm but it goes back to the first set of permissions as soon
as I start another vm. Wondering what could be doing this?
Cheers,
Tom
1998 Oct 15
0
SO_{RCV,SND}BUF=8192 ?
Mostly out of curiosity:
I've seen people advising that we set SO_{RCV,SND}BUF to 8192 as an
optimization. I added a call to getsockopt() to grab the old
(default) value before setting it to the new, and it turns out (on
DG/UX), that the default value is 8760 (or 8704, when you throw in the
fact that packets are travelling between different sublans), so the
8192 "optimization" is a
2012 Nov 17
1
[LLVMdev] [cfe-dev] !!! 3.2 Release branch patching and the Code Owners
----- Original Message -----
> From: "Pawel Wodnicki" <pawel at 32bitmicro.com>
> To: "Hal Finkel" <hfinkel at anl.gov>
> Cc: "Joe Abbey" <joe.abbey at gmail.com>, llvmdev at cs.uiuc.edu, "Nadav Rotem" <nrotem at apple.com>
> Sent: Saturday, November 17, 2012 2:04:10 PM
> Subject: Re: [LLVMdev] [cfe-dev] !!! 3.2 Release
2012 Nov 17
0
[LLVMdev] [cfe-dev] !!! 3.2 Release branch patching and the Code Owners
> ----- Original Message -----
>> From: "Joe Abbey" <joe.abbey at gmail.com>
>> To: "Nadav Rotem" <nrotem at apple.com>
>> Cc: llvmdev at cs.uiuc.edu
>> Sent: Saturday, November 17, 2012 1:25:04 PM
>> Subject: Re: [LLVMdev] [cfe-dev] !!! 3.2 Release branch patching and the Code Owners
>>
>>
>> On Nov 17, 2012, at
2014 Dec 09
1
[LLVMdev] [Libclc-dev] Resigning code ownership of libclc
Hi Peter,
I'm assuming by this that you mean project ownership/maintainership of
libclc, or are you instead referring to the copyright on your
contributions to this project? I just want to be clear here.
Also, do you plan on leaving the mailing list up, or should we start
making alternative plans?
Regards,
Aaron Watry
On Mon, Dec 8, 2014 at 3:18 PM, Peter Collingbourne <peter at
2006 Oct 19
2
/dev/zap/channel ownership
* is having permission problems accessing /dev/zap/channel. When I
look, these devices (everything in /dev/zap) shows root.root for uid and
gid. If I start Asterisk from the command line, it runs fine (running
as Root). When I start it as a service, I get
Oct 19 23:02:55 WARNING[10587] chan_iax2.c: Unable to open IAX timing
interface: Permission denied
Oct 19 23:02:55 WARNING[10587]
2005 Nov 24
1
Where is the proper place to set the group ownership of devices under /dev/ in Centos3.
Dear list members,
I have a DVD writer /dev/scd0 which after reboot has the following ACL:
brw-rw---- 1 root disk 11, 0 Sep 9 2004 /dev/scd0
However I want to set this device group to "Domain Users" in order to
enable its members to burn DVDs.
If i invoke: #chgroup "Domain Users" /dev/scd0
the next reboot will override the group back to "disk".
Is
2006 Apr 06
2
DOS/Windows Archive bits, and file ownership
Preamble:
I've done a lot of looking round news-group archives etc, and I haven't found a definitive answer on this question:
My environment:
Clients are all Windows boxes.
Assume backup of the "share" is a Windows based client. It relies on
the DOS Archive bit to determine Diff/Incr backup selections. (User
Execute bit in Linux)
Goal: Allow users to "own" their files