public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "VALETTE Eric" <valette@crf.canon.fr>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Moving from 2.2.18 + M-system proprietray code to 2.4.6 => does not work
Date: Thu, 12 Jul 2001 12:44:52 +0200	[thread overview]
Message-ID: <3B4D7FA4.9040805@crf.canon.fr> (raw)
In-Reply-To: 7474.994930069@redhat.com

David Woodhouse wrote:

> 
> valette@crf.canon.fr said:
> 
>>NB : /dev/discs/disc1# ls -l
>>total 0
>>brw-------    1 root     root      93,   0 Jan  1  1970 disc
>>brw-------    1 root     root      93,   1 Jan  1  1970 part1
>>
> 
>>But I can not mount the filesystem. The filesystem is valid as it
>>works with the 2.2.18 kernel...
>>
> 
> Does it work without devfs?

I did not even tested it as I need devfs for USB devices hotplug... 
Besides, I had hoped to not be hurt by major/minor like I had been in 
the past...

What are the right major minor for DOC 2000? I found values in mtd.h and 
other in major.h.


-- 
    __
   /  `                          Eric Valette - Canon CRF
  /--   __  o _.                 Canon Development Europe Team Leader
(___, / (_(_(__                 Rue de la touche lambert
                                 35517 Cesson-Sevigne  Cedex
                                 FRANCE
Tel: +33 (0)2 99 87 68 91       Fax: +33 (0)2 99 84 11 30
E-mail: valette@crf.canon.fr    http://www.crf.canon.fr

  reply	other threads:[~2001-07-12 10:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-12  9:18 Moving from 2.2.18 + M-system proprietray code to 2.4.6 => does not work VALETTE Eric
2001-07-12  9:27 ` David Woodhouse
2001-07-12 10:44   ` VALETTE Eric [this message]
2001-07-12 11:19     ` David Woodhouse

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=3B4D7FA4.9040805@crf.canon.fr \
    --to=valette@crf.canon.fr \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    /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