From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SANdo-0000Rn-Oy for garchives@archives.gentoo.org; Wed, 21 Mar 2012 15:40:01 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B499FE0AED; Wed, 21 Mar 2012 15:39:46 +0000 (UTC) Received: from svr-us4.tirtonadi.com (svr-us4.tirtonadi.com [69.65.43.212]) by pigeon.gentoo.org (Postfix) with ESMTP id 3E27EE090E for ; Wed, 21 Mar 2012 15:38:19 +0000 (UTC) Received: from mail-vx0-f181.google.com ([209.85.220.181]) by svr-us4.tirtonadi.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.69) (envelope-from ) id 1SANUr-002jg0-9Y for gentoo-user@lists.gentoo.org; Wed, 21 Mar 2012 22:30:45 +0700 Received: by vcge1 with SMTP id e1so1364554vcg.40 for ; Wed, 21 Mar 2012 08:38:15 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.220.149.82 with SMTP id s18mr2062734vcv.42.1332344295841; Wed, 21 Mar 2012 08:38:15 -0700 (PDT) Received: by 10.220.140.194 with HTTP; Wed, 21 Mar 2012 08:38:15 -0700 (PDT) Received: by 10.220.140.194 with HTTP; Wed, 21 Mar 2012 08:38:15 -0700 (PDT) In-Reply-To: <20120321133822.GB3112@acm.acm> References: <20120320223107.GA2961@acm.acm> <20120321111727.GB15011@acm.acm> <20120321130247.GA3112@acm.acm> <20120321133822.GB3112@acm.acm> Date: Wed, 21 Mar 2012 22:38:15 +0700 Message-ID: Subject: Re: [gentoo-user] mdev: sound is only working some of the time. From: Pandu Poluan To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=f46d043d64a378dee804bbc294fc X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - svr-us4.tirtonadi.com X-AntiAbuse: Original Domain - lists.gentoo.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - poluan.info X-Archives-Salt: d08e131a-511c-4432-9813-7b91030c927a X-Archives-Hash: 48be95b6288eb12e933de162a9c448f9 --f46d043d64a378dee804bbc294fc Content-Type: text/plain; charset=UTF-8 On Mar 21, 2012 10:04 PM, "Alan Mackenzie" wrote: > > Hello again, > > On Wed, Mar 21, 2012 at 08:12:40PM +0700, Pandu Poluan wrote: > > On Mar 21, 2012 8:07 PM, "Alan Mackenzie" wrote: > > > > On Wed, Mar 21, 2012 at 07:49:02PM +0700, Pandu Poluan wrote: > > > > Strange... > > > > > Do you use mdev to handle hotplugs, btw? > > > > You mean, like sticking in a USB stick, or turning my printer on? Yes, I > > > do. > > > > No, I mean, did you do : > > > echo /bin/mdev > /proc/sys/kernel/hotplug > > No I haven't. I don't understand at all what this is about. Any chance > of a quick summary? > According to the busybox documentation, /proc/sys/kernel/hotplug contains the path to a program that will be invoked on hotplug events (hotplug here means the creation of a new device node under /dev, not necessarily actually plugging something onto the box). Doing the above 'echo' will result in kernel invoking mdev when a hotplug event fires; mdev will then act upon the newly-created device node according to the 'recipe' in /etc/mdev.conf, e.g., chown-ing the node, renaming/moving the node, making a symlink, or even triggering a script. The above line should go right after the 'mdev -s' line in linuxrc. > > (ensure beforehand that /bin/mdev is a symlink to /bin/busybox) > > my /sbin/mdev is an indirect symlink to /bin/busybox as follows: > ^ > > /sbin/mdev -> /bin/bb -> busybox > > Presumably this would be OK. > I think so... Rgds, --f46d043d64a378dee804bbc294fc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Mar 21, 2012 10:04 PM, "Alan Mackenzie" <acm@muc.de> wrote:
>
> Hello again,
>
> On Wed, Mar 21, 2012 at 08:12:40PM +0700, Pandu Poluan wrote:
> > On Mar 21, 2012 8:07 PM, "Alan Mackenzie" <acm@muc.de> wrote:
>
> > > On Wed, Mar 21, 2012 at 07:49:02PM +0700, Pandu Poluan wrote= :
> > > > Strange...
>
> > > > Do you use mdev to handle hotplugs, btw?
>
> > > You mean, like sticking in a USB stick, or turning my printe= r on? =C2=A0Yes, I
> > > do.
>
>
> > No, I mean, did you do :
>
> > echo /bin/mdev > /proc/sys/kernel/hotplug
>
> No I haven't. =C2=A0I don't understand at all what this is abo= ut. =C2=A0Any chance
> of a quick summary?
>

According to the busybox documentation, /proc/sys/kernel/hotplug contain= s the path to a program that will be invoked on hotplug events (hotplug her= e means the creation of a new device node under /dev, not necessarily actua= lly plugging something onto the box).

Doing the above 'echo' will result in kernel invoking mdev when = a hotplug event fires; mdev will then act upon the newly-created device nod= e according to the 'recipe' in /etc/mdev.conf, e.g., chown-ing the = node, renaming/moving the node, making a symlink, or even triggering a scri= pt.

The above line should go right after the 'mdev -s' line in linux= rc.

> > (ensure beforehand that /bin/mdev is a symlink to /bin/busybox= )
>
> my /sbin/mdev is an indirect symlink to /bin/busybox as follows:
> =C2=A0 =C2=A0^
>
> =C2=A0 =C2=A0/sbin/mdev -> /bin/bb -> busybox
>
> Presumably this would be OK.
>

I think so...

Rgds,

--f46d043d64a378dee804bbc294fc--