Re: #342455

2006-02-10 Thread Roger Leigh
Raul Miller [EMAIL PROTECTED] writes: On 2/2/06, Roger Leigh [EMAIL PROTECTED] wrote: It's nearly a month since the last mail to this bug. Is this getting close to being resolved? Did you notice the content of the message before yours in this bug's history? It's from Bastian Blank, and

Re: #342455

2006-02-10 Thread Raul Miller
On 2/10/06, Roger Leigh [EMAIL PROTECTED] wrote: I did read this, and I'm happy progress is being made. However, the default is still currently wrong in unstable, and the fix is a simple change to configure in debian/rules. I agree that the devmapper default should match other debian

Re: #342455

2006-02-10 Thread Raul Miller
On 2/10/06, Ian Jackson [EMAIL PROTECTED] channelled: The proposed change to devmapper changes the permissions for all block devices, doesn't it ? Whereas the other debian defaults vary from one kind of device to another. For example, floppies are g+w floppy. The change to devmapper is

Re: #342455

2006-02-10 Thread Steve Langasek
On Fri, Feb 10, 2006 at 04:40:22PM -0800, Steve Langasek wrote: On Fri, Feb 10, 2006 at 04:29:39PM +, Ian Jackson wrote: Raul Miller writes (Re: #342455): I agree that the devmapper default should match other debian defaults, and vice-versa. If I may try to channel Bastian Blank

Re: #342455

2006-02-10 Thread Steve Langasek
On Sat, Feb 11, 2006 at 01:46:56AM +0100, Bastian Blank wrote: On Fri, Feb 10, 2006 at 04:40:22PM -0800, Steve Langasek wrote: Otherwise, having access to the underlying block devices means having access to meddle with anything on the LVM devices as well. And who says that anyone have

Re: #342455

2006-02-10 Thread Anthony Towns
On Fri, Feb 10, 2006 at 04:48:25PM +, Ian Jackson wrote: It's also inconsistent over time on many single machines. I agree that the current situation is unsatisfactory. But I think (at the moment, at least) that it should be fixed by adopting Bastian's code fragments with an appropriate