From: "John D. Coleman" <jdc843@sccoast.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev HOWTO. Where is it ?
Date: Mon, 13 Sep 2004 04:14:44 +0000 [thread overview]
Message-ID: <20040913041444.GA486@bedhost.bedhost.jdcnet.bogus> (raw)
In-Reply-To: <20040911035914.GC972@bedhost.bedhost.jdcnet.bogus>
On 09/12/04 07:07:55, Mike Frysinger wrote:
> On Saturday 11 September 2004 03:19 pm, John D. Coleman wrote:
> > No I have not looked in the tarball. There wasn't any indication in
> the
> > udev-FAQ that I should look there for documentation.
>
> if you download a tarball full of source where else would you expect
> documentation ?
> an included README or INSTALL file is _very_ common in source
> tarballs
> -mike
Ouch. That burns a bit.
Um, in the tarball itself? In a seperate tarball, only via a website,
or non-existant, or other. Take your pick.
There are several tarballs in that directory. All of which, to me
anyway, have to do with udev. What tells me which ones to get? Should I
get them all because they are there? Not unless I'm told to. Read my
first message again this time carefully.
My first message to this mailing list was not meant to be a smart-ass,
ticked-off remark and it wasn't. It was meant to point out to the
developers that maybe they should "consider" giving somebody an EASILY
found pointer.
Flame mode off. And I'm gone. Still subscribed though. Further flames
will be ignored.
I read HOWTO-udev_for_dev. I don't have a program called "chkconfig",
I'd have to study the scripts to see what they do, and I don't have a
rc.sysinit file either so since I don't *need* udev now, I'll come back
later. I'm tackling iptables for a while longer.
I hate it when packages have their 'make install' install scripts in my /
etc/rc.d directory. They don't work and I have to clean up the
directory afterwards. CUPS for example.
Thanks for the pointers Greg & Arun.
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
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:[~2004-09-13 4:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-11 3:59 udev HOWTO. Where is it ? John D. Coleman
2004-09-11 15:19 ` Arun Bhanu
2004-09-11 16:37 ` Greg KH
2004-09-11 19:19 ` John D. Coleman
2004-09-12 11:07 ` Mike Frysinger
2004-09-12 17:09 ` Greg KH
2004-09-12 17:17 ` Mike Frysinger
2004-09-13 4:14 ` John D. Coleman [this message]
2004-09-14 5:07 ` Mike Frysinger
2004-09-14 6:21 ` Greg KH
2004-09-14 6:25 ` Greg KH
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=20040913041444.GA486@bedhost.bedhost.jdcnet.bogus \
--to=jdc843@sccoast.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).