From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevstart v udevtrigger
Date: Thu, 13 Jul 2006 22:21:20 +0000 [thread overview]
Message-ID: <20060713222120.GB7333@kroah.com> (raw)
In-Reply-To: <200607131359.39003.rich@storix.com>
On Thu, Jul 13, 2006 at 03:06:23PM -0700, Rich Turner wrote:
> we use udev when we perform a bare-metal restore of a system from a backup (if
> the system that we created boot media from has it available). we use udev to
> create device nodes in our boot media environment only. once the system is
> rebuilt then the system's original udev support is used.
>
> our only support requirement is that the system is running kernel 2.4 or
> later. granted udev requires 2.6 so those systems are the only ones we are
> discussing.
>
> in short:
> we create the system installation boot media and include the following
> udev-related files on the media:
> udev
> udevstart
> udevd (only if udev is not available and there is udevstart)
> /etc/udev/*
>
> we use udev by running udevstart if we have udev command. or we start udevd if
> we do not have the udev command and then run udevstart. this is creating all
> necessary device nodes.
>
> i have not tested this yet, but my thoughts are to add udevtrigger to the boot
> media. then if there is not a udevstart command create a link
> udevstart->udevtrigger. that way i will not have to make changes everywhere
> else in the software where i do run udevstart.
>
> i guess the question is can i treat udevstart and udevtrigger as the same
> command?
>
> will udevtrigger provide me with the same results as udevstart?
Yes, it should, it just depends on the kernel version running.
thanks,
greg k-h
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2006-07-13 22:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 20:59 udevstart v udevtrigger Rich Turner
2006-07-13 21:29 ` Greg KH
2006-07-13 22:06 ` Rich Turner
2006-07-13 22:21 ` Greg KH [this message]
2006-07-13 23:59 ` Kay Sievers
2006-07-14 16:49 ` Rich Turner
2006-07-14 17:09 ` Andrey Borzenkov
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=20060713222120.GB7333@kroah.com \
--to=greg@kroah.com \
--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).