linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andrew Morton <akpm@osdl.org>
Cc: Daniele Venzano <webvenza@libero.it>,
	wodecki@gmx.de, rgooch@atnf.csiro.au,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test1 devfs question
Date: 27 Jul 2003 12:17:14 +0100	[thread overview]
Message-ID: <1059304634.12758.21.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030726112553.2356cce0.akpm@osdl.org>

On Sad, 2003-07-26 at 19:25, Andrew Morton wrote:
> Is the problem simply that the device has moved from /dev/md1 to /dev/md/1?
> If so, is this change sufficient?

The problem seems to be "user selected devfs"

> 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);


But 2.4 is the same as 2.5 ...

   devfs_handle = devfs_mk_dir (NULL, "md", NULL);
        /* we don't use devfs_register_series because we want to fill
md_hd_str
        for (minor=0; minor < MAX_MD_DEVS; ++minor) {
                char devname[128];
                sprintf (devname, "%u", minor);



  reply	other threads:[~2003-07-27 11:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-25 11:08 2.6.0-test1 devfs question Wiktor Wodecki
2003-07-25 11:18 ` Wiktor Wodecki
2003-07-26 11:12 ` Daniele Venzano
2003-07-26 18:25   ` Andrew Morton
2003-07-27 11:17     ` Alan Cox [this message]
2003-07-25 18:53 Balram Adlakha
2003-07-26 10:45 ` Wiktor Wodecki
     [not found]   ` <20030726175214.GA2535@localhost.localdomain>
     [not found]     ` <20030726183750.GB789@gmx.de>
     [not found]       ` <20030726201919.GA5166@localhost.localdomain>
2003-07-26 20:35         ` Wiktor Wodecki
2003-07-26 19:51 Andrey Borzenkov
2003-07-26 20:50 ` Andrew Morton
2003-07-26 22:30   ` Andrey Borzenkov
2003-07-27  8:58     ` Daniele Venzano
2003-07-28  7:13 "Andrey Borzenkov" 
2003-07-28  7:22 ` Andrew Morton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1059304634.12758.21.camel@dhcp22.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@atnf.csiro.au \
    --cc=webvenza@libero.it \
    --cc=wodecki@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).