From: Robert Milasan <rmilasan@suse.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: how to do ? minimal udev script for my rc.sysinit ?
Date: Wed, 06 May 2015 06:46:35 +0000 [thread overview]
Message-ID: <20150506084635.7fe9f561@viper.suse.cz> (raw)
In-Reply-To: <CAJ-LWjMrUwRSn4Fr_eUchG8=zfv6VR3dxT6ySfwa2gur2OD1zw@mail.gmail.com>
On Tue, 5 May 2015 21:27:38 +0000
"linuxcbon linuxcbon" <linuxcbon@gmail.com> wrote:
> Hi,
>
> my kernel boots ok and gives the hand to init which runs rc.sysinit.
> I am writing a minimal rc.sysinit.
> It creates /dev with devtmpfs and now all works except udev.
> I need 1 or 2 or 3 lines with udev commands to make it work
> and detect and modprobe needed modules.
> I don't know the minimal and shortest commands to do this ?
> Can you please help me ?
>
> Thanks in advance.
> Linuxcbon
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-hotplug" in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
This might help:
# start udev daemon (udevd might be called systemd-udevd)
/path/to/udevd --daemon || echo "udev error" >&2
# trigger events
/path/to/udevadm trigger --actiond || echo "udev trigger error" >&2
/path/to/udevadm trigger --type=subsystems --actiond || echo "udev trigger error" >&2
# wait for events to finish
/path/to/udevadm settle || echo "udev settle error" >&2
--
Robert Milasan
L3 Support Engineer
SUSE Linux (http://www.suse.com)
email: rmilasan@suse.com
GPG fingerprint: B6FE F4A8 0FA3 3040 3402 6FE7 2F64 167C 1909 6D1A
next prev parent reply other threads:[~2015-05-06 6:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 21:27 how to do ? minimal udev script for my rc.sysinit ? linuxcbon linuxcbon
2015-05-05 21:34 ` Greg KH
2015-05-06 0:43 ` linuxcbon linuxcbon
2015-05-06 6:01 ` Tom Gundersen
2015-05-06 6:46 ` Robert Milasan [this message]
2015-05-06 17:16 ` linuxcbon linuxcbon
2015-05-06 17:20 ` linuxcbon linuxcbon
2015-05-06 17:33 ` Robert Milasan
2015-05-07 1:15 ` linuxcbon linuxcbon
2015-05-07 6:25 ` Robert Milasan
2015-05-07 9:33 ` Tom Gundersen
2015-05-07 9:34 ` Tom Gundersen
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=20150506084635.7fe9f561@viper.suse.cz \
--to=rmilasan@suse.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).