linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev housekeeping
Date: Sun, 05 Dec 2004 08:34:49 +0000	[thread overview]
Message-ID: <20041205083449.GA3644@kroah.com> (raw)
In-Reply-To: <1102227937.5596.57.camel@localhost.localdomain>

On Sun, Dec 05, 2004 at 07:25:37AM +0100, Kay Sievers wrote:
> We have several files laying around in the tree, which should be updated
> or deleted:
> 
> Not useful anymore:
>   etc/conf.d/udev

This came from Red Hat, they don't use it anymore in their rpm?

>   etc/dev.d/default/dbus.dev

Now deleted.

>   etc/dev.d/default/selinux.dev

Now deleted.

>   test/udevd_test.sh

Now deleted.

>   test/wait_for_sysfs_test.sh

Hm, I liked this script... oh well, it's gone.

> RH specific and different from current RH version:
>   etc/dev.d/default/pam_console.dev 

Care to provide the latest version?

> Calls udev binary for every node. Should be deleted or converted
> to use udevstart:
>   etc/init.d/udev

Deleted.

>   etc/init.d/udev.init.LSB

Converted.

>   etc/init.d/udev.init.lfs

Converted.

>   etc/extras/start_udev

Left alone, I want to keep that logic around somewhere :)

> Most of them are broken an replaced by udev-test.pl:
>   test/ignore_test

delted.

>   test/label_test

deleted

>   test/modifier_test

deleted

>   test/net_test

Left alone, as we don't test this in udev-test.pl (yeah, it's broken,
but it can work by hand.)

>   test/replace_test

deleted.

>   test/test.all
>   test/test.block
>   test/test.tty

Left alone, they are good for debugging at times.

>   test/testd.block

Hm, I don't remember even why I added this :)

>   test/topo_test

deleted

>   test/devd_test

Nah, I'll leave this if I need to verify the dev.d stuff again.

Thanks for pointing this all out.

greg k-h


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
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-12-05  8:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-05  6:25 udev housekeeping Kay Sievers
2004-12-05  8:34 ` Greg KH [this message]
2004-12-05 19:24 ` Kay Sievers
2004-12-06 23:02 ` Greg KH
2004-12-07 16:34 ` Kay Sievers
2004-12-07 16:38 ` Kay Sievers
2004-12-07 17:52 ` 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=20041205083449.GA3644@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 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).