From: David Brown <dmlb2000@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev-067 and 2.6.12?
Date: Thu, 18 Aug 2005 15:53:27 +0000 [thread overview]
Message-ID: <9c21eeae0508180853795293f4@mail.gmail.com> (raw)
In-Reply-To: <200508162349.01610.s0348365@sms.ed.ac.uk>
On 8/18/05, Greg KH <greg@kroah.com> wrote:
>
> A: http://en.wikipedia.org/wiki/Top_post
> Q: Were do I find info about this thing called top-posting?
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> A: No.
> Q: Should I include quotations after my reply?
Sorry I'll try not to do that any more ;-)
> So you install a new version of udev and don't kill the old udevd
> program? That's not good at all. Remember, if you set DEST_DIR, that
> doesn't get called. That is there to allow you to build and not mess
> with any running services (as is needed on rpm and deb build machines.)
I'll mention this to the other developers and see what they think... I
inherited this diff from previous versions of the package (going back
to 04x iirc) it may need another look if it's needed.
> That's not how you build things in the extras directory (as per the
> documentation.)
>
> Did you try:
> make USE_LOG=true EXTRAS="extras/run_directory"
> ? That should work just fine, and if not, please let us know. There's
> a script in the test directory that builds everything with all options
> to determine if we break anything. Have you tried that?
Ah, yes thanks that does work. I must have misread the RELEASE-NOTES... :-\
Maybe adding back-ticks could make that line seem more like 'this is
the exact command to execute.' (just a suggestion)
I'll be sure to fix this thanks...
> Ok, and as I don't think you are building things correctly, I don't
> think this patch is needed :)
Yes agreed thanks for the help :)
Thanks
- David Brown
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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:[~2005-08-18 15:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 22:49 udev-067 and 2.6.12? Alistair John Strachan
2005-08-16 23:00 ` David Brown
2005-08-16 23:26 ` Alistair John Strachan
2005-08-16 23:31 ` David Brown
2005-08-16 23:55 ` Kay Sievers
2005-08-17 8:09 ` Arioch
2005-08-17 8:26 ` Alistair John Strachan
2005-08-17 12:35 ` Kay Sievers
2005-08-17 14:52 ` Alistair John Strachan
2005-08-17 15:10 ` Kay Sievers
2005-08-17 23:48 ` Greg KH
2005-08-18 15:27 ` David Brown
2005-08-18 15:38 ` Greg KH
2005-08-18 15:53 ` David Brown [this message]
2005-08-18 16:32 ` Alistair John Strachan
2005-08-18 16:56 ` Greg KH
2005-08-18 17:19 ` Alistair John Strachan
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=9c21eeae0508180853795293f4@mail.gmail.com \
--to=dmlb2000@gmail.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).