From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev-067 and 2.6.12?
Date: Thu, 18 Aug 2005 15:38:52 +0000 [thread overview]
Message-ID: <20050818153852.GA9860@kroah.com> (raw)
In-Reply-To: <200508162349.01610.s0348365@sms.ed.ac.uk>
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?
On Thu, Aug 18, 2005 at 08:27:52AM -0700, David Brown wrote:
> Well I'm a developer for SourceMage and one of the things that we
> pride ourselves on is options. So there's a couple of things we had
> to change with udev to make it fit into our system of doing things.
> 1) no package to start or stop services in the process of installing
> the package... hence the removal of the killall udevd && udevd
> --daemon call
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.)
> 2) the `make -C extras/run_directory USE_LOG=true` didn't work if the
> root directory of udev was built with logging support.
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?
> I had to add the udev_logger.c to the root directory add that file to
> the Makefile so it would end up in udev.a, then the command I used to
> build with syslog support is `make -C extras/run_directory
> LDFLAGS="-lc" USE_LOG=true`.
>
> So the main reason for using this patch and adding the udev_logger.c
> source file is so that the extras/run_directory can have syslog
> support or not have syslog support.
Ok, and as I don't think you are building things correctly, I don't
think this patch is needed :)
thanks,
greg k-h
-------------------------------------------------------
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:38 UTC|newest]
Thread overview: 23+ 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 [this message]
2005-08-18 15:53 ` David Brown
2005-08-18 16:32 ` Alistair John Strachan
2005-08-18 16:56 ` Greg KH
2005-08-18 17:19 ` Alistair John Strachan
-- strict thread matches above, loose matches on Subject: below --
2005-08-16 22:02 Alistair John Strachan
2005-08-16 22:05 ` Greg KH
2005-08-16 22:12 ` Alistair John Strachan
2005-08-16 22:14 ` Greg KH
2005-08-16 23:09 ` Kay Sievers
2005-08-16 23:33 ` 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=20050818153852.GA9860@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.