From: Lee Revell <rlrevell@joe-job.com>
To: Maurice Volaski <mvolaski@aecom.yu.edu>
Cc: drbd-user@linbit.com, linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.13 is hiding devices from /dev [Was Why is the kernel hiding drbd devices?}
Date: Tue, 06 Sep 2005 23:31:14 -0400 [thread overview]
Message-ID: <1126063875.13159.31.camel@mindpipe> (raw)
In-Reply-To: <a06230908bf43b486d98f@[129.98.90.227]>
On Tue, 2005-09-06 at 17:13 -0400, Maurice Volaski wrote:
> The kernel module drbd (version 0.7.13) can no longer find its
> devices (e.g., /dev/drbd0, /dev/drbd1) in kernel 2.6.13. The version
> of udev I am using 065/068 didn't make a difference. It works fine
> with kernel 2.6.12.5 and 2.6.12.6.
What is drbd? An out of tree driver? Did it work with 2.6.13-rcX? If
not, why didn't they tell us sooner? Does it expect devfs to be present
in the kernel by any chance?
Lee
next prev parent reply other threads:[~2005-09-07 3:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 21:13 Kernel 2.6.13 is hiding devices from /dev [Was Why is the kernel hiding drbd devices?} Maurice Volaski
2005-09-07 3:31 ` Lee Revell [this message]
2005-09-07 4:45 ` Maurice Volaski
2005-09-07 5:03 ` Lee Revell
2005-09-07 5:30 ` Kernel 2.6.13 is NOT " Lars Ellenberg
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=1126063875.13159.31.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=drbd-user@linbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mvolaski@aecom.yu.edu \
/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