From: Peter Christy <christy@attglobal.net>
To: linux-hotplug@vger.kernel.org
Subject: udev init
Date: Fri, 02 Jan 2004 11:00:00 +0000 [thread overview]
Message-ID: <200401021100.00758.christy@attglobal.net> (raw)
I've just been trying to install udev, as I was having naming consistency
problems with devfs, and udev holds the tantalising promise of sorting this.
Unfortunately, udev-011 seems to be built for systems using SysV style init
scripts. I'm running Slackware, which uses BSD style init.
"make install" seems to have created an etc/init.d directory containing the
startup script (?), which presumably I can rename and install in the correct
place (/etc/rc.d/rc.udev) for Slackware. However, it seems to refer to an /
etc/rc.d/initd/functions script, which doesn't exist in Slackware. Since I
don't have it, I can't figure out what its meant to be doing to work around
it.
Sorry if this question has been asked before, but Google has drawn a blank,
and I don't know where to go next. Any pointers would be appreciated!
--
Pete
christy@attglobal.net
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
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 reply other threads:[~2004-01-02 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 11:00 Peter Christy [this message]
2004-01-02 19:07 ` udev init Panagiotis Issaris
2004-01-02 20:26 ` Greg KH
2004-01-02 21:02 ` Marco d'Itri
2004-01-02 21:30 ` Dave Dodge
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=200401021100.00758.christy@attglobal.net \
--to=christy@attglobal.net \
--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).