All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev - kill udevd on install
Date: Sat, 28 Feb 2004 06:50:03 +0000	[thread overview]
Message-ID: <20040228065003.GA3643@kroah.com> (raw)
In-Reply-To: <20040228033339.GB32032@vrfy.org>

On Sat, Feb 28, 2004 at 04:33:39AM +0100, Kay Sievers wrote:
> We want to kill udevd after installing a new version, cause the event
> contains a magic with the version number of udev.
> 
> thanks,
> Kay

> === Makefile 1.122 vs edited ==> --- 1.122/Makefile	Sat Feb 28 02:59:43 2004
> +++ edited/Makefile	Sat Feb 28 04:25:36 2004
> @@ -373,10 +373,12 @@
>  	$(INSTALL_DATA) -D udev.8 $(DESTDIR)$(mandir)/man8/udev.8
>  	$(INSTALL_DATA) -D udevinfo.8 $(DESTDIR)$(mandir)/man8/udevinfo.8
>  	$(INSTALL_DATA) -D udevd.8 $(DESTDIR)$(mandir)/man8/udevd.8
> -	- ln -f -s ./udevd.8 $(DESTDIR)$(mandir)/man8/udevsend.8
> -	- rm -f $(DESTDIR)$(hotplugdir)/$(ROOT).hotplug

Why take away this line?  It's needed if the symlink is set up "wrong"
(like pointing to udev instead of udevsend like old systems would
have...)

thanks,

greg k-h


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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

  reply	other threads:[~2004-02-28  6:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-28  3:33 udev - kill udevd on install Kay Sievers
2004-02-28  6:50 ` Greg KH [this message]
2004-02-28 12:48 ` Kay Sievers
2004-03-01 22:26 ` Greg KH
2004-03-18 14:40 ` Harald Hoyer

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=20040228065003.GA3643@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.