Andrey Borzenkov <arvidjaar@mail.ru> wrote:
>
> > Is the problem simply that the device has moved from /dev/md1 to /dev/md/1?
> > If so, is this change sufficient?
> >
> > diff -puN drivers/md/md.c~a drivers/md/md.c
> > --- 25/drivers/md/md.c~a 2003-07-26 11:24:58.000000000 -0700
> > +++ 25-akpm/drivers/md/md.c 2003-07-26 11:25:15.000000000 -0700
> > @@ -3505,7 +3505,7 @@ int __init md_init(void)
> > for (minor=0; minor < MAX_MD_DEVS; ++minor) {
> > devfs_mk_bdev(MKDEV(MAJOR_NR, minor),
> > S_IFBLK|S_IRUSR|S_IWUSR,
> > - "md/%d", minor);
> > + "md%d", minor);
> > }
>
> should not such things be done by devfsd in user space?
Darned if I know - I do not have operational experience with devfs.
> This patch makes it even more incompatible with 2.4 ...
The patch is broken - 2.4 does /dev/md/2 as well.
So what is the bug? Why are people suddenly having problems with this?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jul 31 2003 - 22:00:30 EST