[ANNOUNCE] udev 047 release

[ANNOUNCE] udev 047 release

[Greg KH]

I've released the 047 version of udev.  It can be found at:
  	kernel.org/pub/linux/utils/kernel/hotplug/udev-046.tar.gz

udev allows users to have a dynamic /dev and provides the ability to
have persistent device names.  It uses sysfs and /sbin/hotplug and runs
entirely in userspace.  It requires a 2.6 kernel with CONFIG_HOTPLUG
enabled to run.  Please see the udev FAQ for any questions about it:
	kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ

For any udev vs devfs questions anyone might have, please see:
	kernel.org/pub/linux/utils/kernel/hotplug/udev_vs_devfs

And there is a general udev web page at:
	http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html

Lots of changes here in this release, see the full changelog below.
Highlights are:
	- massive change with the way udevd can now work.  See
	  http://thread.gmane.org/gmane.linux.hotplug.devel/6173 for
	  more details on this (Kay's changes are now part of udev
	  proper, you don't have to apply anything for this to work,
	  just follow the directions in
	  http://article.gmane.org/gmane.linux.hotplug.devel/6192
	  to enable this mode.)
	- wait_for_sysfs is now gone.
	- bugfixes and rules file tweaks
	- add ability to handle expressions in GROUP rules.

Thanks to everyone who has send me patches for this release, a full list
of everyone, and their changes is below.

udev development is done in a BitKeeper repository located at:
	bk://linuxusb.bkbits.net/udev

Daily snapshots of udev from the BitKeeper tree can be found at:
	http://www.codemonkey.org.uk/projects/bitkeeper/udev/
If anyone ever wants a tarball of the current bk tree, just email me.

thanks,

greg k-h

Summary of changes from v046 to v047
======================

<klauser:access.unizh.ch>:
  o Various typos and other litte errors in udev.8.in

<sjoerd:spring.luon.net>:
  o DEVNAME on device removal

<sschweizer:gmail.com>:
  o Allow GROUP to have modifiers in it

Greg Kroah-Hartman:
  o add more debian rules files
  o move distro specific config files into their own directories
  o update debian rules files
  o added asterix rules to the gentoo file
  o use udevstart for udev.init.* files
  o delete a bunch of files no longer needed
  o fix gentoo scsi cdrom rule
  o Fix the multithreaded build again
  o merge
  o comment out ability to run udev-test.pl with valgrind
  o fix spurious valgrind warning in udev
  o fix udevinfo '-q path' option as it was not working
  o merge
  o fix parallel build error

Kay Sievers:
  o update Fedora dev.d/ example and remove unused conf.d/ directory
  o don't install distribution specific init script on "make install"
  o restore OWNER/GROUP assignment in rule coming from RESULT
  o make gcov compile scripts working with recent gcc
  o fix udev-test/udev-test.pl to work with again
  o add net/atml and class/ppdev to the wait_for_sysfs exception list
  o add net/nlv* devices to the exception list
  o add "pcmcia" and "fc_transport" to the wait_for_sysfs lists
  o remove unused timestamp field
  o simplify permission handling
  o handle /etc/hotplug.d/ only if the event comes from udevd
  o trivial cleanups and change some comments
  o remove unused variables
  o udevsend/udevd handle events without a subsystem
  o use blacklist on device "remove" and remove dev.d/ call code duplication
  o update the man pages and correct Usage: hints
  o don't call the hotplug scripts with a test run
  o don't call dev.d/ scripts twice, if directory = subsystem
  o remove archive file if we changed something
  o link archive insted of objects
  o rename udev_lib to udev_utils and dev_d to udev_multiplex
  o handle whole hotplug event with udevd/udev
  o integrate wait_for_sysfs in udev
  o make the searched multiplex directories conditionally
  o add MANAGED_EVENT to the forked udev environment
  o export DEVNAME on remove event
  o export udev_log flag to the environment
  o remove my test code
  o add support for /devices-devices without any file to wait for
  o Patch from Alex Riesen <raa.lkml@gmail.com>
  o add a bunch of busses to the list of what to wait for
  o close connection to syslog in forked udevd child
  o udevd exit path cleanup
  o fix network device naming bug




-------------------------------------------------------
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

Re: [ANNOUNCE] udev 047 release

[Greg KH]

On Wed, Dec 08, 2004 at 10:58:56AM -0800, Greg KH wrote:
> I've released the 047 version of udev.  It can be found at:
>   	kernel.org/pub/linux/utils/kernel/hotplug/udev-046.tar.gz

Ick, the programs in the extras/ directory don't seem to build anymore.
I'll fix that up and do a new release in a few hours.  Sorry about
that...

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

[ANNOUNCE] udev 048 release

[Greg KH]

On Wed, Dec 08, 2004 at 11:28:10AM -0800, Greg KH wrote:
> On Wed, Dec 08, 2004 at 10:58:56AM -0800, Greg KH wrote:
> > I've released the 047 version of udev.  It can be found at:
> >   	kernel.org/pub/linux/utils/kernel/hotplug/udev-046.tar.gz
> 
> Ick, the programs in the extras/ directory don't seem to build anymore.
> I'll fix that up and do a new release in a few hours.  Sorry about
> that...

Ok, version 048 has been released to fix the build errors for the
extras/ directory.  It's available at
	kernel.org/pub/linux/utils/kernel/hotplug/udev-048.tar.gz

thanks,

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

Re: [ANNOUNCE] udev 048 release

[Tomasz Kłoczko]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1890 bytes --]

On Wed, 8 Dec 2004, Greg KH wrote:

> On Wed, Dec 08, 2004 at 11:28:10AM -0800, Greg KH wrote:
>> On Wed, Dec 08, 2004 at 10:58:56AM -0800, Greg KH wrote:
>>> I've released the 047 version of udev.  It can be found at:
>>>   	kernel.org/pub/linux/utils/kernel/hotplug/udev-046.tar.gz
>>
>> Ick, the programs in the extras/ directory don't seem to build anymore.
>> I'll fix that up and do a new release in a few hours.  Sorry about
>> that...
>
> Ok, version 048 has been released to fix the build errors for the
> extras/ directory.  It's available at
> 	kernel.org/pub/linux/utils/kernel/hotplug/udev-048.tar.gz

I have question about curent form of udev source.

First: is it any real reason for use by udev private copy libsysfs which
is statically linked with udev ?

I'm using udev with shared libsysfs for a months and all works correcly.

If no reasons patches for using system avalaible libsysfs for udev 048 
can be downloaded from:

http://cvs.pld.org.pl/SOURCES/udev-uses_system_libsysfs.patch?rev=1.7
http://cvs.pld.org.pl/SOURCES/udev-extras_scsi_id_sysfs.patch?rev=1.1

Also after aplying this patches libsysfs/ subdirectory can be removed from 
udev source tree.

Second: in current udev Makefile is used direct stripping linked binaries.
Why ? It makes harder packaging udev if someone will try generate udev in 
for example rpm form with debug info in separated udev-debug package.

Patch for remove stripping:

http://cvs.pld.org.pl/SOURCES/udev-no_strip.patch?rev=1.7

After aplying this patch pereviouse behavior can be obtained by:

% make LDFLAGS="-s"

kloczek
-- 
-----------------------------------------------------------
*Ludzie nie mają problemów, tylko sobie sami je stwarzają*
-----------------------------------------------------------
Tomasz Kłoczko, sys adm @zie.pg.gda.pl|*e-mail: kloczek@rudy.mif.pg.gda.pl*

Re: [ANNOUNCE] udev 048 release

[Greg KH]

On Wed, Dec 08, 2004 at 10:56:27PM +0100, Tomasz K?oczko wrote:
> 
> First: is it any real reason for use by udev private copy libsysfs which
> is statically linked with udev ?

Yes, the "system" version of libsysfs is not always the same one that
udev wants.  Over the past year or so, sometimes it has varied a lot.
Hopefully now we are properly synced up, but I still trust our own
version, not any other version (this really matters on boxes that have
older versions of libsysfs, like SLES 9 and friends.)

> I'm using udev with shared libsysfs for a months and all works correcly.

Great.  Notice any code size savings?  Yeah, it's not really all that
much.  You also need static linking when using klibc to get a very tiny
udev for your boot initramfs image.

> If no reasons patches for using system avalaible libsysfs for udev 048 
> can be downloaded from:
> 
> http://cvs.pld.org.pl/SOURCES/udev-uses_system_libsysfs.patch?rev=1.7
> http://cvs.pld.org.pl/SOURCES/udev-extras_scsi_id_sysfs.patch?rev=1.1
> 
> Also after aplying this patches libsysfs/ subdirectory can be removed from 
> udev source tree.

Will it still properly build with klibc?

Also, please realize that libsysfs is really not on many machines, due
to it only being used by 1 other program at this time.  So any memory
size savings is very limited.

> Second: in current udev Makefile is used direct stripping linked binaries.
> Why ?

Smaller size :)

> It makes harder packaging udev if someone will try generate udev in 
> for example rpm form with debug info in separated udev-debug package.

I'm sure those who package up rpms of udev have dealt with this properly
somehow.  For the rest of the world, I'd prefer to keep the current way.

thanks,

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

Re: [ANNOUNCE] udev 048 release

[Kay Sievers]

On Wed, 2004-12-08 at 14:05 -0800, Greg KH wrote:
> On Wed, Dec 08, 2004 at 10:56:27PM +0100, Tomasz K?oczko wrote:

> > Also after aplying this patches libsysfs/ subdirectory can be removed from 
> > udev source tree.
> 
> Will it still properly build with klibc?

This will not work at the moment, as we fake the getmntent() call in
libsysfs at compile time for the klibc build.

> I'm sure those who package up rpms of udev have dealt with this properly
> somehow.  For the rest of the world, I'd prefer to keep the current way.

I agree. It's much easier to tweak the udev sources to use a dynamic
linked libsysfs than the other way around.

Thanks,
Kay



-------------------------------------------------------
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

Re: [ANNOUNCE] udev 048 release

[Tomasz Kłoczko]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 3423 bytes --]

On Wed, 8 Dec 2004, Greg KH wrote:

> On Wed, Dec 08, 2004 at 10:56:27PM +0100, Tomasz K?oczko wrote:
>>
>> First: is it any real reason for use by udev private copy libsysfs which
>> is statically linked with udev ?
>
> Yes, the "system" version of libsysfs is not always the same one that
> udev wants.

Sorry but from eons spend some time on prepare correct build enviromet 
isn't task for each project maintainers but for persons who tries buid 
specified project from source tree :-|

Try prepare in corect form only udev .. and nothing more :_)

Me and probaly many othet people aroud the word who tries build variose
tools for variouse distributions hates maintainers who includes in project 
tree souce code another projects. Much more haten is project maitainer who 
don't allow in easy way use system avalaible libraries.
Please don't try be listed on this long hated maintainers list ;>

Argument allways is like yours .. and allways this is source ass pain
for distribution maintainers like:

- patchin from each new version for use system avalaible libraries if
   something will be changed in build automations (for udev from may this
   year it hapens .. seven times),

- what if in libsysfs will be discovered some nasty bug ? Why I must audit
   not only libsysfs but also any other projests where libsysfs source was
   included ? (this not hipotetycal case .. do you remember case with for
   example with security bugs in zlib ?).

If you want more argumets for not link statisally look at Solarias 10 why 
*ALL* binaries are linked with shared version of any library and lern 
more .. this is _specialy_ for tools very close to kernel layer.

[..]
>> I'm using udev with shared libsysfs for a months and all works correcly.
>
> Great.  Notice any code size savings?  Yeah, it's not really all that
> much.  You also need static linking when using klibc to get a very tiny
> udev for your boot initramfs image.

This not for code saving but for use only one copy of library by any tools 
which uses specifieed API/ABI. In case any bug on for example libsysfs
which can be fixed without changing API/API all what must be performed is
replace libsysfs shared library .. nothing more.

[..]
>> It makes harder packaging udev if someone will try generate udev in
>> for example rpm form with debug info in separated udev-debug package.
>
> I'm sure those who package up rpms of udev have dealt with this properly
> somehow.  For the rest of the world, I'd prefer to keep the current way.

Greg meybe you are very good kernel hacker (for me you are :) but seems 
you are not so good as person for maintaining user space tools ;>

IMO ony ~1-2% of *all* project uses direct stripping chained directly 
chained in build automation which is used by default. All from this ~1-2% 
because maintainer isn't skilled in some subjects.
Default behavior ~99-98% projects build automations is pass not stripped
binaries. On most of this projects (all which uses for example automake)
producing stripped binaries cen be enabled by add -s to linking options
(usualy LDFLAGS="-s").

kloczek
-- 
-----------------------------------------------------------
*Ludzie nie mają problemów, tylko sobie sami je stwarzają*
-----------------------------------------------------------
Tomasz Kłoczko, sys adm @zie.pg.gda.pl|*e-mail: kloczek@rudy.mif.pg.gda.pl*

Re: [ANNOUNCE] udev 048 release

[Marco d'Itri]

[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]

On Dec 08, Greg KH <greg@kroah.com> wrote:

> Yes, the "system" version of libsysfs is not always the same one that
> udev wants.  Over the past year or so, sometimes it has varied a lot.
> Hopefully now we are properly synced up, but I still trust our own
> version, not any other version (this really matters on boxes that have
> older versions of libsysfs, like SLES 9 and friends.)
What's wrong with letting distributions deal with this? If they package
udev they can package libsysfs as well.

> > It makes harder packaging udev if someone will try generate udev in 
> > for example rpm form with debug info in separated udev-debug package.
> I'm sure those who package up rpms of udev have dealt with this properly
> somehow.  For the rest of the world, I'd prefer to keep the current way.
I doubt that there are many people installing udev from source on a
distribution which does not support it. And if they do, they have to
change so many things that I doubt stripping installed binaries is going
to be a problem.

-- 
ciao, |
Marco | [9659 cawOtuyEEoELY]

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [ANNOUNCE] udev 048 release

[Marco d'Itri]

[-- Attachment #1: Type: text/plain, Size: 355 bytes --]

On Dec 09, Tomasz K?oczko <kloczek@rudy.mif.pg.gda.pl> wrote:

> binaries. On most of this projects (all which uses for example automake)
> producing stripped binaries cen be enabled by add -s to linking options
> (usualy LDFLAGS="-s").
Or even better build unstripped binaries and then use install -s.

-- 
ciao, |
Marco | [9660 alo3B4byfkQYA]

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [ANNOUNCE] udev 048 release

[Mike Frysinger]

On Wednesday 08 December 2004 06:56 pm, Marco d'Itri wrote:
> Or even better build unstripped binaries and then use install -s.

using `install -s` is a very bad idea ... it completely breaks cross compiling 
since install will just call `strip`
-mike


-------------------------------------------------------
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

Re: [ANNOUNCE] udev 048 release

[Andrew Walrond]

On Wednesday 08 Dec 2004 19:46, Greg KH wrote:
>
> Ok, version 048 has been released to fix the build errors for the
> extras/ directory.  It's available at
>  kernel.org/pub/linux/utils/kernel/hotplug/udev-048.tar.gz
>

I've built a boot cd with linux-2.6.10-rc3, udev 048 and latest hotplug.

When I boot a machine with my CD, udev doesn't create /dev/hda
I can't fathom why. Any reasons why it wouldn't create it?
It _has_ created /dev/hdc, (the cdrom drive) and all the other usual devices.

/proc/ide shows hda->ide0/hda
/proc/ide/ide0/hda/model = MAXTOR 6L040J2

This is a simple Asus P4PE m/b with intel ICH4 IDE.

( I know I can mknod, but since this is supposed to be a general purpose 
boot/toolkit CD, I'd like to make sure udev is working properly)

Any clues? hda currently contains windows server and I'm rather eager to wipe 
it ;)

Andrew Walrond


-------------------------------------------------------
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

Re: [ANNOUNCE] udev 048 release

[Greg KH]

On Thu, Dec 09, 2004 at 09:47:14PM +0000, Andrew Walrond wrote:
> On Wednesday 08 Dec 2004 19:46, Greg KH wrote:
> >
> > Ok, version 048 has been released to fix the build errors for the
> > extras/ directory.  It's available at
> >  kernel.org/pub/linux/utils/kernel/hotplug/udev-048.tar.gz
> >
> 
> I've built a boot cd with linux-2.6.10-rc3, udev 048 and latest hotplug.
> 
> When I boot a machine with my CD, udev doesn't create /dev/hda
> I can't fathom why. Any reasons why it wouldn't create it?

Does /sys/block/hda exist?

Did you run udevstart as part of your boot process after init happens?

thanks,

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

Re: [ANNOUNCE] udev 048 release

[Andrew Walrond]

On Thursday 09 Dec 2004 23:25, Greg KH wrote:
>
> Does /sys/block/hda exist?
>
No; ide-disk wasn't loaded :(

Thanks

Andrew


-------------------------------------------------------
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

Re: [ANNOUNCE] udev 048 release

[Kay Sievers]

On Thu, 2004-12-09 at 21:47 +0000, Andrew Walrond wrote:
> On Wednesday 08 Dec 2004 19:46, Greg KH wrote:
> >
> > Ok, version 048 has been released to fix the build errors for the
> > extras/ directory.  It's available at
> >  kernel.org/pub/linux/utils/kernel/hotplug/udev-048.tar.gz
> >
> 
> I've built a boot cd with linux-2.6.10-rc3, udev 048 and latest hotplug.
> 
> When I boot a machine with my CD, udev doesn't create /dev/hda
> I can't fathom why. Any reasons why it wouldn't create it?
> It _has_ created /dev/hdc, (the cdrom drive) and all the other usual devices.
> 
> /proc/ide shows hda->ide0/hda
> /proc/ide/ide0/hda/model = MAXTOR 6L040J2
> 
> This is a simple Asus P4PE m/b with intel ICH4 IDE.
> 
> ( I know I can mknod, but since this is supposed to be a general purpose 
> boot/toolkit CD, I'd like to make sure udev is working properly)
> 
> Any clues? hda currently contains windows server and I'm rather eager to wipe 
> it ;)

Do you run udevstart at one of the first things after boot?
udev only creates a node if it gets a hotplug event, but that may not be
the case for your boot drive...
Kay



-------------------------------------------------------
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

Re: [ANNOUNCE] udev 048 release

[Andrew Walrond]

On Thursday 09 Dec 2004 21:56, Kay Sievers wrote:
> On Thu, 2004-12-09 at 21:47 +0000, Andrew Walrond wrote:
> > On Wednesday 08 Dec 2004 19:46, Greg KH wrote:
> > > Ok, version 048 has been released to fix the build errors for the
> > > extras/ directory.  It's available at
> > >  kernel.org/pub/linux/utils/kernel/hotplug/udev-048.tar.gz
> >
> > I've built a boot cd with linux-2.6.10-rc3, udev 048 and latest hotplug.
> >
> > When I boot a machine with my CD, udev doesn't create /dev/hda
> > I can't fathom why. Any reasons why it wouldn't create it?
> > It _has_ created /dev/hdc, (the cdrom drive) and all the other usual
> > devices.
> >
> > /proc/ide shows hda->ide0/hda
> > /proc/ide/ide0/hda/model = MAXTOR 6L040J2
> >
> > This is a simple Asus P4PE m/b with intel ICH4 IDE.
> >
> > ( I know I can mknod, but since this is supposed to be a general purpose
> > boot/toolkit CD, I'd like to make sure udev is working properly)
> >
> > Any clues? hda currently contains windows server and I'm rather eager to
> > wipe it ;)
>
> Do you run udevstart at one of the first things after boot?
> udev only creates a node if it gets a hotplug event, but that may not be
> the case for your boot drive...

I run start_udev right after mounting proc and sys. Note that the boot drive 
node gets created just fine (hdc, the cdrom) but hda, the harddrive, doesn't.

Andrew


-------------------------------------------------------
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

Re: [ANNOUNCE] udev 048 release

[Kay Sievers]

On Thu, 2004-12-09 at 22:07 +0000, Andrew Walrond wrote:
> On Thursday 09 Dec 2004 21:56, Kay Sievers wrote:
> > On Thu, 2004-12-09 at 21:47 +0000, Andrew Walrond wrote:
> > > On Wednesday 08 Dec 2004 19:46, Greg KH wrote:
> > > > Ok, version 048 has been released to fix the build errors for the
> > > > extras/ directory.  It's available at
> > > >  kernel.org/pub/linux/utils/kernel/hotplug/udev-048.tar.gz
> > >
> > > I've built a boot cd with linux-2.6.10-rc3, udev 048 and latest hotplug.
> > >
> > > When I boot a machine with my CD, udev doesn't create /dev/hda
> > > I can't fathom why. Any reasons why it wouldn't create it?
> > > It _has_ created /dev/hdc, (the cdrom drive) and all the other usual
> > > devices.
> > >
> > > /proc/ide shows hda->ide0/hda
> > > /proc/ide/ide0/hda/model = MAXTOR 6L040J2
> > >
> > > This is a simple Asus P4PE m/b with intel ICH4 IDE.
> > >
> > > ( I know I can mknod, but since this is supposed to be a general purpose
> > > boot/toolkit CD, I'd like to make sure udev is working properly)
> > >
> > > Any clues? hda currently contains windows server and I'm rather eager to
> > > wipe it ;)
> >
> > Do you run udevstart at one of the first things after boot?
> > udev only creates a node if it gets a hotplug event, but that may not be
> > the case for your boot drive...
> 
> I run start_udev right after mounting proc and sys. Note that the boot drive 
> node gets created just fine (hdc, the cdrom) but hda, the harddrive, doesn't.

Does running udevstart manually create the node? What does

  ls -l /sys/block/hda/* print?

Kay



-------------------------------------------------------
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

Re: [ANNOUNCE] udev 048 release

[Andrew Walrond]

On Thursday 09 Dec 2004 22:18, Kay Sievers wrote:
>
> Does running udevstart manually create the node? What does
>
>   ls -l /sys/block/hda/* print?
>

udevstart has no effect.

However, /sys/block/hda doesn't exist. (/sys/block/hdc is there)
What does that tell me? Why would /proc/sys/hda exist, but not /sys/block/hda?

Andrew



-------------------------------------------------------
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

Re: [ANNOUNCE] udev 048 release

[Kay Sievers]

On Thu, 2004-12-09 at 22:24 +0000, Andrew Walrond wrote:
> On Thursday 09 Dec 2004 22:18, Kay Sievers wrote:
> >
> > Does running udevstart manually create the node? What does
> >
> >   ls -l /sys/block/hda/* print?
> >
> 
> udevstart has no effect.
> 
> However, /sys/block/hda doesn't exist. (/sys/block/hdc is there)
> What does that tell me? Why would /proc/sys/hda exist, but not /sys/block/hda?

Try to load ide-disk.

Kay



-------------------------------------------------------
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

Re: [ANNOUNCE] udev 048 release

[Andrew Walrond]

On Thursday 09 Dec 2004 22:27, you wrote:
>
> Try to load ide-disk.

Doh!

Thanks Kay :)

Andrew


-------------------------------------------------------
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

Re: [ANNOUNCE] udev 047 release [u]

[Martin Schlemmer [c]]

[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]

On Wed, 2004-12-08 at 10:58 -0800, Greg KH wrote:

> Lots of changes here in this release, see the full changelog below.
> Highlights are:
> 	- massive change with the way udevd can now work.  See
> 	  http://thread.gmane.org/gmane.linux.hotplug.devel/6173 for
> 	  more details on this (Kay's changes are now part of udev
> 	  proper, you don't have to apply anything for this to work,
> 	  just follow the directions in
> 	  http://article.gmane.org/gmane.linux.hotplug.devel/6192
> 	  to enable this mode.)

Any suggestions to determining the version of the installed udev?
This is now during startup, to see if we can make use of using
udevsend as hotplug agent.  If the system was up, udevinfo could
be used, but that is in /usr/bin that might be on a seperate /usr.
I know we might move udevinfo to /bin, but that might be an issue
for some, and adding a -V switch to /sbin/udev might be a better
choice if you do not have have any nit's against it ....


Thanks,

-- 
Martin Schlemmer


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [ANNOUNCE] udev 047 release [u]

[Kay Sievers]

On Sat, 2004-12-11 at 18:44 +0200, Martin Schlemmer [c] wrote: 
> On Wed, 2004-12-08 at 10:58 -0800, Greg KH wrote:
> 
> > Lots of changes here in this release, see the full changelog below.
> > Highlights are:
> > 	- massive change with the way udevd can now work.  See
> > 	  http://thread.gmane.org/gmane.linux.hotplug.devel/6173 for
> > 	  more details on this (Kay's changes are now part of udev
> > 	  proper, you don't have to apply anything for this to work,
> > 	  just follow the directions in
> > 	  http://article.gmane.org/gmane.linux.hotplug.devel/6192
> > 	  to enable this mode.)
> 
> Any suggestions to determining the version of the installed udev?
> This is now during startup, to see if we can make use of using
> udevsend as hotplug agent.  If the system was up, udevinfo could
> be used, but that is in /usr/bin that might be on a seperate /usr.
> I know we might move udevinfo to /bin, but that might be an issue
> for some, and adding a -V switch to /sbin/udev might be a better
> choice if you do not have have any nit's against it ....

Good idea, we should do that. I've added it to my tree at:
  http://vrfy.bkbits.net:8080/udev/

The next version will print:
  [kay@pim udev.kay]$ /sbin/udev -V
  048

Thanks,
Kay



-------------------------------------------------------
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

Re: [ANNOUNCE] udev 047 release [u]

[Martin Schlemmer [c]]

[-- Attachment #1: Type: text/plain, Size: 1546 bytes --]

On Sat, 2004-12-11 at 18:46 +0100, Kay Sievers wrote:
> On Sat, 2004-12-11 at 18:44 +0200, Martin Schlemmer [c] wrote: 
> > On Wed, 2004-12-08 at 10:58 -0800, Greg KH wrote:
> > 
> > > Lots of changes here in this release, see the full changelog below.
> > > Highlights are:
> > > 	- massive change with the way udevd can now work.  See
> > > 	  http://thread.gmane.org/gmane.linux.hotplug.devel/6173 for
> > > 	  more details on this (Kay's changes are now part of udev
> > > 	  proper, you don't have to apply anything for this to work,
> > > 	  just follow the directions in
> > > 	  http://article.gmane.org/gmane.linux.hotplug.devel/6192
> > > 	  to enable this mode.)
> > 
> > Any suggestions to determining the version of the installed udev?
> > This is now during startup, to see if we can make use of using
> > udevsend as hotplug agent.  If the system was up, udevinfo could
> > be used, but that is in /usr/bin that might be on a seperate /usr.
> > I know we might move udevinfo to /bin, but that might be an issue
> > for some, and adding a -V switch to /sbin/udev might be a better
> > choice if you do not have have any nit's against it ....
> 
> Good idea, we should do that. I've added it to my tree at:
>   http://vrfy.bkbits.net:8080/udev/
> 
> The next version will print:
>   [kay@pim udev.kay]$ /sbin/udev -V
>   048
> 

Ah, great, thanks.

Greg, sorda OT for this list, but mind adding patch to portage,
then I can whip up some /sbin/rc changes ....


Thanks,

-- 
Martin Schlemmer


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [ANNOUNCE] udev 047 release [u]

[Martin Schlemmer [c]]

[-- Attachment #1: Type: text/plain, Size: 1486 bytes --]

On Sat, 2004-12-11 at 18:46 +0100, Kay Sievers wrote:
> On Sat, 2004-12-11 at 18:44 +0200, Martin Schlemmer [c] wrote: 
> > On Wed, 2004-12-08 at 10:58 -0800, Greg KH wrote:
> > 
> > > Lots of changes here in this release, see the full changelog below.
> > > Highlights are:
> > > 	- massive change with the way udevd can now work.  See
> > > 	  http://thread.gmane.org/gmane.linux.hotplug.devel/6173 for
> > > 	  more details on this (Kay's changes are now part of udev
> > > 	  proper, you don't have to apply anything for this to work,
> > > 	  just follow the directions in
> > > 	  http://article.gmane.org/gmane.linux.hotplug.devel/6192
> > > 	  to enable this mode.)
> > 
> > Any suggestions to determining the version of the installed udev?
> > This is now during startup, to see if we can make use of using
> > udevsend as hotplug agent.  If the system was up, udevinfo could
> > be used, but that is in /usr/bin that might be on a seperate /usr.
> > I know we might move udevinfo to /bin, but that might be an issue
> > for some, and adding a -V switch to /sbin/udev might be a better
> > choice if you do not have have any nit's against it ....
> 
> Good idea, we should do that. I've added it to my tree at:
>   http://vrfy.bkbits.net:8080/udev/
> 
> The next version will print:
>   [kay@pim udev.kay]$ /sbin/udev -V
>   048
> 

Another quick question ... why was the '-d' switch to udevinfo
removed?


Thanks,

-- 
Martin Schlemmer


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [ANNOUNCE] udev 047 release [u]

[Kay Sievers]

On Mon, 2004-12-13 at 18:44 +0200, Martin Schlemmer [c] wrote:
> On Sat, 2004-12-11 at 18:46 +0100, Kay Sievers wrote:
> > On Sat, 2004-12-11 at 18:44 +0200, Martin Schlemmer [c] wrote: 
> > > On Wed, 2004-12-08 at 10:58 -0800, Greg KH wrote:
> > > 
> > > > Lots of changes here in this release, see the full changelog below.
> > > > Highlights are:
> > > > 	- massive change with the way udevd can now work.  See
> > > > 	  http://thread.gmane.org/gmane.linux.hotplug.devel/6173 for
> > > > 	  more details on this (Kay's changes are now part of udev
> > > > 	  proper, you don't have to apply anything for this to work,
> > > > 	  just follow the directions in
> > > > 	  http://article.gmane.org/gmane.linux.hotplug.devel/6192
> > > > 	  to enable this mode.)
> > > 
> > > Any suggestions to determining the version of the installed udev?
> > > This is now during startup, to see if we can make use of using
> > > udevsend as hotplug agent.  If the system was up, udevinfo could
> > > be used, but that is in /usr/bin that might be on a seperate /usr.
> > > I know we might move udevinfo to /bin, but that might be an issue
> > > for some, and adding a -V switch to /sbin/udev might be a better
> > > choice if you do not have have any nit's against it ....
> > 
> > Good idea, we should do that. I've added it to my tree at:
> >   http://vrfy.bkbits.net:8080/udev/
> > 
> > The next version will print:
> >   [kay@pim udev.kay]$ /sbin/udev -V
> >   048
> > 
> 
> Another quick question ... why was the '-d' switch to udevinfo
> removed?

The udev db is plaintext now. The -d option was for the binary tdb file,
to get an idea whats in there.
A dump is just a "cat /dev/.udevdb/*" now. :)

Kay



-------------------------------------------------------
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

Re: [ANNOUNCE] udev 047 release [u]

[Martin Schlemmer [c]]

[-- Attachment #1: Type: text/plain, Size: 2856 bytes --]

On Mon, 2004-12-13 at 18:08 +0100, Kay Sievers wrote:
> On Mon, 2004-12-13 at 18:44 +0200, Martin Schlemmer [c] wrote:
> > On Sat, 2004-12-11 at 18:46 +0100, Kay Sievers wrote:
> > > On Sat, 2004-12-11 at 18:44 +0200, Martin Schlemmer [c] wrote: 
> > > > On Wed, 2004-12-08 at 10:58 -0800, Greg KH wrote:
> > > > 
> > > > > Lots of changes here in this release, see the full changelog below.
> > > > > Highlights are:
> > > > > 	- massive change with the way udevd can now work.  See
> > > > > 	  http://thread.gmane.org/gmane.linux.hotplug.devel/6173 for
> > > > > 	  more details on this (Kay's changes are now part of udev
> > > > > 	  proper, you don't have to apply anything for this to work,
> > > > > 	  just follow the directions in
> > > > > 	  http://article.gmane.org/gmane.linux.hotplug.devel/6192
> > > > > 	  to enable this mode.)
> > > > 
> > > > Any suggestions to determining the version of the installed udev?
> > > > This is now during startup, to see if we can make use of using
> > > > udevsend as hotplug agent.  If the system was up, udevinfo could
> > > > be used, but that is in /usr/bin that might be on a seperate /usr.
> > > > I know we might move udevinfo to /bin, but that might be an issue
> > > > for some, and adding a -V switch to /sbin/udev might be a better
> > > > choice if you do not have have any nit's against it ....
> > > 
> > > Good idea, we should do that. I've added it to my tree at:
> > >   http://vrfy.bkbits.net:8080/udev/
> > > 
> > > The next version will print:
> > >   [kay@pim udev.kay]$ /sbin/udev -V
> > >   048
> > > 
> > 
> > Another quick question ... why was the '-d' switch to udevinfo
> > removed?
> 
> The udev db is plaintext now. The -d option was for the binary tdb file,
> to get an idea whats in there.
> A dump is just a "cat /dev/.udevdb/*" now. :)
> 

Ah, ok, thanks.  Btw, using udevsend as hotplug agent seem to work
fine, although hal still do not recognise a flash drive if I have
udev renave the node to /dev/usbfd* ...

PS: you might need something like:

-----
--- udevinfo.c.orig     2004-12-13 21:15:49.000000000 +0200
+++ udevinfo.c  2004-12-13 21:16:59.000000000 +0200
@@ -242,7 +242,7 @@

 static int process_options(int argc, char *argv[])
 {
-       static const char short_options[] = "adn:p:q:rsVh";
+       static const char short_options[] = "an:p:q:rsVh";
        int option;
        int retval = 1;
        struct udevice udev;
@@ -439,7 +439,7 @@
        }

 help:
-       printf("Usage: udevinfo [-anpqrdVh]\n"
+       printf("Usage: udevinfo [-anpqrVh]\n"
               "  -q TYPE  query database for the specified value:\n"
               "             'name'    name of device node\n"
               "             'symlink' pointing to node\n"
-----


Thanks,

-- 
Martin Schlemmer


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [ANNOUNCE] udev 047 release [u]

[Kay Sievers]

On Mon, 2004-12-13 at 21:18 +0200, Martin Schlemmer [c] wrote:
> On Mon, 2004-12-13 at 18:08 +0100, Kay Sievers wrote:
> > On Mon, 2004-12-13 at 18:44 +0200, Martin Schlemmer [c] wrote:
> > > Another quick question ... why was the '-d' switch to udevinfo
> > > removed?
> > 
> > The udev db is plaintext now. The -d option was for the binary tdb file,
> > to get an idea whats in there.
> > A dump is just a "cat /dev/.udevdb/*" now. :)
> > 
> 
> Ah, ok, thanks.  Btw, using udevsend as hotplug agent seem to work
> fine, although hal still do not recognise a flash drive if I have
> udev renave the node to /dev/usbfd* ...
> 
> PS: you might need something like:
> 
> -----
> --- udevinfo.c.orig     2004-12-13 21:15:49.000000000 +0200
> +++ udevinfo.c  2004-12-13 21:16:59.000000000 +0200
> @@ -242,7 +242,7 @@
> 
>  static int process_options(int argc, char *argv[])
>  {
> -       static const char short_options[] = "adn:p:q:rsVh";
> +       static const char short_options[] = "an:p:q:rsVh";
>         int option;
>         int retval = 1;
>         struct udevice udev;
> @@ -439,7 +439,7 @@
>         }
> 
>  help:
> -       printf("Usage: udevinfo [-anpqrdVh]\n"
> +       printf("Usage: udevinfo [-anpqrVh]\n"
>                "  -q TYPE  query database for the specified value:\n"
>                "             'name'    name of device node\n"
>                "             'symlink' pointing to node\n"


Thanks, I've applied it to my tree and it will show up with the next
sync.

Kay



-------------------------------------------------------
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

Re: [ANNOUNCE] udev 047 release [u]

[Greg KH]

On Sat, Dec 11, 2004 at 07:59:53PM +0200, Martin Schlemmer [c] wrote:
> On Sat, 2004-12-11 at 18:46 +0100, Kay Sievers wrote:
> > On Sat, 2004-12-11 at 18:44 +0200, Martin Schlemmer [c] wrote: 
> > > On Wed, 2004-12-08 at 10:58 -0800, Greg KH wrote:
> > > 
> > > > Lots of changes here in this release, see the full changelog below.
> > > > Highlights are:
> > > > 	- massive change with the way udevd can now work.  See
> > > > 	  http://thread.gmane.org/gmane.linux.hotplug.devel/6173 for
> > > > 	  more details on this (Kay's changes are now part of udev
> > > > 	  proper, you don't have to apply anything for this to work,
> > > > 	  just follow the directions in
> > > > 	  http://article.gmane.org/gmane.linux.hotplug.devel/6192
> > > > 	  to enable this mode.)
> > > 
> > > Any suggestions to determining the version of the installed udev?
> > > This is now during startup, to see if we can make use of using
> > > udevsend as hotplug agent.  If the system was up, udevinfo could
> > > be used, but that is in /usr/bin that might be on a seperate /usr.
> > > I know we might move udevinfo to /bin, but that might be an issue
> > > for some, and adding a -V switch to /sbin/udev might be a better
> > > choice if you do not have have any nit's against it ....
> > 
> > Good idea, we should do that. I've added it to my tree at:
> >   http://vrfy.bkbits.net:8080/udev/
> > 
> > The next version will print:
> >   [kay@pim udev.kay]$ /sbin/udev -V
> >   048
> > 
> 
> Ah, great, thanks.
> 
> Greg, sorda OT for this list, but mind adding patch to portage,
> then I can whip up some /sbin/rc changes ....

The 049 version is in portage, and you can use that now.

While we're OT, and Gentoo specific, what about moving all of the udev
specific startup and shutdown stuff to a separate file, owned by the
udev package?  Or is that just too messy now?

Just trying to make your life easier.

thanks,

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

Re: [ANNOUNCE] udev 047 release [u]

[Martin Schlemmer [c]]

[-- Attachment #1: Type: text/plain, Size: 2605 bytes --]

On Thu, 2004-12-16 at 16:08 -0800, Greg KH wrote:
> On Sat, Dec 11, 2004 at 07:59:53PM +0200, Martin Schlemmer [c] wrote:
> > On Sat, 2004-12-11 at 18:46 +0100, Kay Sievers wrote:
> > > On Sat, 2004-12-11 at 18:44 +0200, Martin Schlemmer [c] wrote: 
> > > > On Wed, 2004-12-08 at 10:58 -0800, Greg KH wrote:
> > > > 
> > > > > Lots of changes here in this release, see the full changelog below.
> > > > > Highlights are:
> > > > > 	- massive change with the way udevd can now work.  See
> > > > > 	  http://thread.gmane.org/gmane.linux.hotplug.devel/6173 for
> > > > > 	  more details on this (Kay's changes are now part of udev
> > > > > 	  proper, you don't have to apply anything for this to work,
> > > > > 	  just follow the directions in
> > > > > 	  http://article.gmane.org/gmane.linux.hotplug.devel/6192
> > > > > 	  to enable this mode.)
> > > > 
> > > > Any suggestions to determining the version of the installed udev?
> > > > This is now during startup, to see if we can make use of using
> > > > udevsend as hotplug agent.  If the system was up, udevinfo could
> > > > be used, but that is in /usr/bin that might be on a seperate /usr.
> > > > I know we might move udevinfo to /bin, but that might be an issue
> > > > for some, and adding a -V switch to /sbin/udev might be a better
> > > > choice if you do not have have any nit's against it ....
> > > 
> > > Good idea, we should do that. I've added it to my tree at:
> > >   http://vrfy.bkbits.net:8080/udev/
> > > 
> > > The next version will print:
> > >   [kay@pim udev.kay]$ /sbin/udev -V
> > >   048
> > > 
> > 
> > Ah, great, thanks.
> > 
> > Greg, sorda OT for this list, but mind adding patch to portage,
> > then I can whip up some /sbin/rc changes ....
> 
> The 049 version is in portage, and you can use that now.
> 
> While we're OT, and Gentoo specific, what about moving all of the udev
> specific startup and shutdown stuff to a separate file, owned by the
> udev package?  Or is that just too messy now?
> 
> Just trying to make your life easier.
> 

Hmm - thing is things are currently in flux on the whole rc side
(redoing some code, cleanups, etc), and it uses things that are
pretty tied to baselayout proper that are part of the stuff
fluxing.  Also I guess we want to do whatever for the devfs die-hards
as well, along with a split or three that will happen at some stage
due to the bsd support, as well as my threatened rewrite of some
stuff when I get the time eventually ...  Maybe later when we done
restructuring ...


Thanks,

-- 
Martin Schlemmer


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [ANNOUNCE] udev 047 release [u]

[Greg KH]

On Fri, Dec 17, 2004 at 07:11:08PM +0200, Martin Schlemmer [c] wrote:
> On Thu, 2004-12-16 at 16:08 -0800, Greg KH wrote:
> > 
> > While we're OT, and Gentoo specific, what about moving all of the udev
> > specific startup and shutdown stuff to a separate file, owned by the
> > udev package?  Or is that just too messy now?
> > 
> > Just trying to make your life easier.
> > 
> 
> Hmm - thing is things are currently in flux on the whole rc side
> (redoing some code, cleanups, etc), and it uses things that are
> pretty tied to baselayout proper that are part of the stuff
> fluxing.  Also I guess we want to do whatever for the devfs die-hards
> as well, along with a split or three that will happen at some stage
> due to the bsd support, as well as my threatened rewrite of some
> stuff when I get the time eventually ...  Maybe later when we done
> restructuring ...

Fair enough, thanks for letting me know.

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