On Thu, Sep 14, 2006 at 12:14:11PM +0300, Eddy =?UTF-8?Q?Petri=C5=9For ?= wrote: > [snip] > # use MAKEDEV instead of the original bluez script below as > per policy 10.6 > echo "Creating device nodes ..." > cd /dev && ./MAKEDEV bluetooth > > if [ -r /etc/bluetooth/pin ]; then > echo "Converting default outgoing PIN to default passkey:" > [snip]
> Probably something like this could be the fix (for sarge upgrade path): > --- bluez-utils.postinst.orig 2006-09-11 08:26:53.000000000 +0300 > +++ bluez-utils.postinst 2006-09-14 12:13:06.000000000 +0300 > @@ -35,7 +35,9 @@ > # use MAKEDEV instead of the original bluez script below as > per policy 10.6 > echo "Creating device nodes ..." > - cd /dev && ./MAKEDEV bluetooth > + [ -e /dev/MAKEDEV ] && cd /dev > + [ -e /sbin/MAKDEV ] && cd /sbin > + ./MAKEDEV bluetooth > > if [ -r /etc/bluetooth/pin ]; then > echo "Converting default outgoing PIN to default passkey:" Absolutely not, MAKEDEV acts on the current directory by design. You don't want device files added to /sbin. You also misspelled MAKEDEV in the patch, so it wouldn't do anything anyway. Do you have the makedev package installed on your system? AFAICS, the bug here is that bluez-utils depends on makedev *or* udev, but calls MAKEDEV unconditionally in the postinst. All of my udev-using symbols do have /dev/MAKEDEV as a symlink to /sbin/MAKEDEV, so I don't see any other reason this would fail -- at least, not that it would be a bug in bluez-utils. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
