patches for mdadm 1.8.0 (auto=dev and stacking of devices)

2005-01-23 Thread Luca Berra
hello, i attach two patches for mdadm 1.8.0 the first one adds an auto=dev parameter rationale: udev does not create /dev/md* device files, so we need a way to create them when assembling the md device. auto=yes allocates the first free minor number, so mdadm -A --auto=yes /dev/md2 yelds a

Re: patches for mdadm 1.8.0 (auto=dev and stacking of devices)

2005-01-23 Thread Peter T. Breuer
Lars Marowsky-Bree [EMAIL PROTECTED] wrote: On 2005-01-23T16:13:05, Luca Berra [EMAIL PROTECTED] wrote: the first one adds an auto=dev parameter rationale: udev does not create /dev/md* device files, so we need a way to create them when assembling the md device. Am I missing something

Re: patches for mdadm 1.8.0 (auto=dev and stacking of devices)

2005-01-23 Thread Michael Tokarev
Lars Marowsky-Bree wrote: On 2005-01-23T16:13:05, Luca Berra [EMAIL PROTECTED] wrote: the first one adds an auto=dev parameter rationale: udev does not create /dev/md* device files, so we need a way to create them when assembling the md device. Am I missing something but shouldn't this be fixed by

Re: patches for mdadm 1.8.0 (auto=dev and stacking of devices)

2005-01-23 Thread Luca Berra
On Sun, Jan 23, 2005 at 07:46:29PM +0300, Michael Tokarev wrote: Lars Marowsky-Bree wrote: On 2005-01-23T16:13:05, Luca Berra [EMAIL PROTECTED] wrote: the first one adds an auto=dev parameter rationale: udev does not create /dev/md* device files, so we need a way to create them when assembling the

Re: patches for mdadm 1.8.0 (auto=dev and stacking of devices)

2005-01-23 Thread Peter T. Breuer
Luca Berra [EMAIL PROTECTED] wrote: I believe the correct solution to this would be implementing a char-misc /dev/mdadm device that mdadm would use instead of the block device, like device-mapper does. Alas i have no time for this in the forseable future. It's a generic problem (or