From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751438AbWFTRYn (ORCPT ); Tue, 20 Jun 2006 13:24:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751445AbWFTRYm (ORCPT ); Tue, 20 Jun 2006 13:24:42 -0400 Received: from outpipe-village-512-1.bc.nu ([81.2.110.250]:49860 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S1751438AbWFTRYm (ORCPT ); Tue, 20 Jun 2006 13:24:42 -0400 Subject: Re: udev bluez From: Alan Cox To: "Robert M. Stockmann" Cc: linux-kernel@vger.kernel.org, Kay Sievers , Hannes Reinecke , Linus Torvalds , Andrew Morton , Alan Cox In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 20 Jun 2006 18:39:22 +0100 Message-Id: <1150825163.11062.51.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.6.2 (2.6.2-1.fc5.5) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Ar Maw, 2006-06-20 am 18:11 +0200, ysgrifennodd Robert M. Stockmann: > The key piece of trouble is udev which has nowadays has to run > in close cooperation with a daemon called hald. I would suggest avoiding hald is a good starting point if you want to control the system rather than be its slave. If you want hal to do nice things and it doesn't then file a bug with the HAL people, they are fighting a billion random weird bits of hardware at once so all the help they get will I'm sure be appreciated.