linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alesh Slovak <alesh.slovak@avasys.jp>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev rules file validation
Date: Tue, 15 Sep 2009 23:39:23 +0000	[thread overview]
Message-ID: <4AB025AB.2040203@avasys.jp> (raw)
In-Reply-To: <4AA05A1F.2040009@avasys.jp>

Sujit K M wrote:
> I donot understand what you mean by validate. It could have several meanings.
> For Example.
> 1. We could have something like XML/Document Validation. Much more
> seen in SGML/XML Environment.
> 2. We could have Run Time Validation Like Certificates. Much More of
> an RSS/Feed Environment/Web site Design.
> 3. We could have Validation of Resources. Having an inbuilt database
> of the resources udev is trying to load/unload/link.
> 4. We could have validation of the functionality of the generated
> script or an already present script.
> 
> By Validation what do you mean?
What I mean by validating udev rules files is probably closest to #1 
above. Because I generate udev rules automagically with a script at 
install time I would like to be sure that the rules files are formatted 
correctly before installing them on the system and potentially screwing 
things up (like happened before). I could write my own validation script 
but if there is a good way to validate rules files using udev itself, 
that would obviously be the better way to go.

Regards,
-- 
Alesh Slovak                    Linux Team -- AVASYS Corporation
alesh.slovak@avasys.jp          http://avasys.jp

      parent reply	other threads:[~2009-09-15 23:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-04  0:06 udev rules file validation Alesh Slovak
2009-09-04  1:28 ` Marco d'Itri
2009-09-04 21:30 ` clemens fischer
2009-09-06 23:09 ` Alesh Slovak
2009-09-15  8:00 ` Alesh Slovak
2009-09-15  8:54 ` Sujit K M
2009-09-15 23:39 ` Alesh Slovak [this message]

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=4AB025AB.2040203@avasys.jp \
    --to=alesh.slovak@avasys.jp \
    --cc=linux-hotplug@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 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).