From: Peter Rajnoha <prajnoha@redhat.com>
To: lvm-devel@redhat.com
Subject: Now I'm convinced about Linux
Date: Mon, 29 Jul 2013 09:44:36 +0200 [thread overview]
Message-ID: <51F61D64.6070600@redhat.com> (raw)
In-Reply-To: <999744.9869.bm@smtp104.mail.ir2.yahoo.com>
On 07/26/2013 06:37 PM, Kevin Chadwick wrote:
> Having a simple problem today that last_rule would solve just fine and
> finding that I must edit extra files or manage a packages file is
You should not be pushed into editing udev rules unless you do something
(very) extra. If something does not work correctly as expected, you
should submit a bug report against the relevant distro/package.
What exactly is the nature of the problem that needs such a manual
intervention? Also, what udev rules are we talking about exactly?
> quite convincing that they are right, especially the reason
> "Inconsistent behaviour" when that is exactly what I expect to be able
> to do on Unix and is so often made difficult just on Linux these days
> and it seems especially in code mainly managed by RedHat, though I do
> not a member of RedHat raising concerns about it.
>
> I have tried creating /lib/udev/rules.d/zzz-arsewipingidiotfix.rules
> with LABEL="very_end"
>
> but adding GOTO="very_end" to earlier udev rules
> (/etc/udev/rules.d/46-) is having no effect even after a udev restart?
>
> Any ideas?
>
Please, provide more information about the problem and if the problem
is related to LVM, then provide the LVM version as well please
Also, is this Fedora or RHEL or are you trying to use upstream
version directly?
Peter
next prev parent reply other threads:[~2013-07-29 7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 16:37 Now I'm convinced about Linux Kevin Chadwick
2013-07-29 7:44 ` Peter Rajnoha [this message]
2013-07-30 9:56 ` Kevin Chadwick
2013-07-31 8:14 ` Peter Rajnoha
2013-07-31 21:40 ` Kevin Chadwick
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=51F61D64.6070600@redhat.com \
--to=prajnoha@redhat.com \
--cc=lvm-devel@redhat.com \
/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.