From: David Brown <dmlb2000@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev-067 and 2.6.12?
Date: Tue, 16 Aug 2005 23:31:48 +0000 [thread overview]
Message-ID: <9c21eeae0508161631746af15f@mail.gmail.com> (raw)
In-Reply-To: <200508162349.01610.s0348365@sms.ed.ac.uk>
Okay you can disable syslog or I had to make an extra C file and patch
the makefile to get it to work.
to disable syslog `make USE_LOGúlse`
- David Brown
== begin Makefile.patch =--- Makefile.old 2005-07-23 09:27:02.000000000 -0700
+++ Makefile 2005-07-24 22:52:21.000000000 -0700
@@ -145,7 +145,8 @@
udev_db.o \
udev_rules.o \
udev_rules_parse.o \
- udev_libc_wrapper.o
+ udev_libc_wrapper.o \
+ udev_logger.o
OBJS = \
udev.a \
@@ -377,11 +378,6 @@
$(INSTALL_PROGRAM) -D $(INFO) $(DESTDIR)$(usrbindir)/$(INFO)
$(INSTALL_PROGRAM) -D $(TESTER) $(DESTDIR)$(usrbindir)/$(TESTER)
$(INSTALL_PROGRAM) -D $(STARTER) $(DESTDIR)$(sbindir)/$(STARTER)
-ifndef DESTDIR
- - killall $(DAEMON)
- - rm -rf $(udevdb)
- - $(sbindir)/$(DAEMON) --daemon
-endif
@extras="$(EXTRAS)" ; for target in $$extras ; do \
echo $$target ; \
$(MAKE) prefix=$(prefix) LD="$(LD)" SYSFS="$(SYSFS)" \
== end Makefile.patch =
== begin udev_logger.c =#include <syslog.h>
#include <stdarg.h>
extern int udev_log_priority;
#ifdef USE_LOG
void log_message(int priority, const char *format, ...)
{
va_list args;
if (priority > udev_log_priority)
return;
va_start(args, format);
vsyslog(priority, format, args);
va_end(args);
}
#endif
== end udev_logger.c =
On 8/16/05, Alistair John Strachan <s0348365@sms.ed.ac.uk> wrote:
> On Tuesday 16 August 2005 23:49, Alistair John Strachan wrote:
> > On Tuesday 16 August 2005 23:33, David Brown wrote:
> > > Check out the release notes for udev 059
> > > I think your problem may be caused by the changes in that release
> > > and you should probably add the code below to your udev rules file
> > > <snip>
> > > RUN+="/sbin/udev_run_devd"
> > > </snip>
> > >
> > > I've noticed this problem as well loading firmware but everything was
> > > fixed when I made the two extra binaries in extras/run_directory and
> > > added the code above to my rules file
> > >
> > > - David Brown
> >
> > (Sorry linux-hotplug-devel, I thought I'd add to CC after Greg's suggestion
> > elsewhere in this thread).
> >
> > Obviously, this fixed it. Thanks a lot for the hint.
>
> Okay, I've found a few problems with udev 067 so far.
>
> Greg suggested changing comparisons in the udev rules to = instead of =,
> which makes sense (comparison versus assignment). There are several files in
> the etc/udev directory that don't observe this (frugalware/slackware).
>
> Secondly, the stuff in run_directory doesn't link:
>
> # make
> cc -DUSE_LOG -O2 -march=k8 -mfpmath=sse -s -pipe -c -o run_directory.o
> run_directory.c
> ld -s -o udev_run_devd udev_run_devd.o
> run_directory.o ../../udev.a ../../libsysfs/sysfs.a
> ld: warning: cannot find entry symbol _start; defaulting to 00000000004000f0
> udev_run_devd.o: In function `log_message':
> udev_run_devd.c:(.text+0x9d): undefined reference to `vsyslog'
> udev_run_devd.c:(.text+0xb6): undefined reference to `getenv'
>
> GCC 4.0.1/binutils 2.16.91.0.2. I worked around it by linking with gcc instead
> (like the rest of udev does). This worked fine. I didn't compile udev or the
> run_directory stuff against klibc.
>
> Finally, I'm sure this is my fault, but modules like "mousedev" and "sd_mod"
> don't get loaded by hotplug/udev when I plug in my mouse or pendrive after
> booting. This is because they are not actually dependencies of the modules
> usbhid and usb-storage, so they don't get loaded by modprobe.
>
> udev 053 used to do this, 067 doesn't any more. I've got both the
> udev_run_devd and udev_run_hotplugd binaries compiled and in the right place;
> I stole the configuration from the gentoo rules. Any idea what's changed?
>
> These are my now vastly simplified rules (no other rules files exist):
> http://devzero.co.uk/~alistair/50-desktop.rules
>
> --
> Cheers,
> Alistair.
>
> 'No sense being pessimistic, it probably wouldn't work anyway.'
> Third year Computer Science undergraduate.
> 1F2 55 South Clerk Street, Edinburgh, UK.
>
-------------------------------------------------------
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-16 23:31 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 [this message]
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
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=9c21eeae0508161631746af15f@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).