From: Luca Berra <bluca@comedia.it>
To: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: [PATCH] enable auto=yes by default when using udev
Date: Tue, 4 Jul 2006 12:47:03 +0200 [thread overview]
Message-ID: <20060704104658.GC8357@percy.comedia.it> (raw)
In-Reply-To: <44AA42F6.8070307@tls.msk.ru>
On Tue, Jul 04, 2006 at 02:29:10PM +0400, Michael Tokarev wrote:
>Why to test for udev at all? If the device does not exist, regardless
because udev whas what was giving me pains :)
>if udev is running or not, it might be a good idea to try to create it.
>Because IT IS NEEDED, period. Whenever the operation fails or not, and
i believe we can set autof to 2 by default.
>whenever we fail if it fails or not - it's another question, and I think
>that w/o explicit auto=yes, we may ignore create error and try to continue,
>and with auto=yes, we fail on create error.
we need to distinguish between explicit auto=no, explicit auto=yes and
implicit auto=yes for this. maybe this is overkill
>as it does now. If /dev/whatever exist, use it. If not, create it (unless,
>perhaps, auto=no is specified) directly with proper mknod("/dev/mdX"), but
>don't try to use some temporary names in /dev or elsewhere.
agreed!
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
next prev parent reply other threads:[~2006-07-04 10:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-02 22:45 [PATCH] enable auto=yes by default when using udev Luca Berra
2006-07-02 23:14 ` Neil Brown
2006-07-02 23:29 ` Jason Lunz
2006-07-03 9:11 ` Mario 'BitKoenig' Holbe
2006-07-03 10:56 ` David Greaves
2006-07-03 11:13 ` Frank Blendinger
2006-07-03 22:46 ` Luca Berra
2006-07-04 10:43 ` Luca Berra
2006-07-04 10:29 ` Michael Tokarev
2006-07-04 10:47 ` Luca Berra [this message]
2006-07-04 12:19 ` Mario 'BitKoenig' Holbe
2006-07-18 5:19 ` Neil Brown
2006-07-18 10:07 ` Christian Pernegger
2006-07-17 19:42 ` Bill Davidsen
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=20060704104658.GC8357@percy.comedia.it \
--to=bluca@comedia.it \
--cc=linux-raid@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.