systemd-183

Post by Bruce Dubbs
I see that systemd-183 is out in the
http://www.freedesktop.org/software/systemd/ repository.
My understanding is that this version of systemd has udev included.
I've looked through the NEWS, README, and ./configure --help.

I have the same questions. I don't want to do a full systemd build just
to install udev. Is there some way to build udev only?

William

Karl O. Pinc

2012-05-27 03:19:43 UTC

Post by William Hubbs
I have the same questions. I don't want to do a full systemd build just
to install udev. Is there some way to build udev only?

I don't recall how to do it, but when the merge into systemd
was announced there were instructions for building just udev.

See the mailing list archives.

Karl <***@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein

--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Bruce Dubbs

2012-05-27 03:38:30 UTC

Post by Karl O. Pinc

Post by William Hubbs
I have the same questions. I don't want to do a full systemd build just
to install udev. Is there some way to build udev only?

I don't recall how to do it, but when the merge into systemd
was announced there were instructions for building just udev.
See the mailing list archives.

I looked at the systemd mailing list and I cannot find any such
instructions. The announce message was only yesterday.

I'd appreciate a pointer.

The announcement I found was on the freedesktop.org systemd-devel list.
Is this mailing list going to be abandoned?

-- Bruce
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Karl O. Pinc

2012-05-27 04:06:47 UTC

Post by Bruce Dubbs
I looked at the systemd mailing list and I cannot find any such
instructions. The announce message was only yesterday.
I'd appreciate a pointer.

The udev mailing list: linux-***@vger.kernel.org

Karl <***@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein

--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Kay Sievers

2012-05-27 11:34:11 UTC

Post by Karl O. Pinc

Post by William Hubbs
I have the same questions. I don't want to do a full systemd build just
to install udev. Is there some way to build udev only?

I don't recall how to do it, but when the merge into systemd
was announced there were instructions for building just udev.
See the mailing list archives.

We support stand-alone *operation* of the udev tools, but the build
system does not support a stand-alone *build*. The systemd tree needs
to be built and udev picked out of it.

There are also several other generally useful tools in the built tree,
which you might need too over time, like tmpfiles, module-load,
sysconf, binfmt, ... A couple of D-Bus services to manage system
settings from the desktop.

Various upstream tools start to install config files or use these
interfaces. It might be the simplest to install them too, even when
systemd is not used.

Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Karl O. Pinc

2012-05-27 12:17:24 UTC

Post by Kay Sievers
We support stand-alone *operation* of the udev tools, but the build
system does not support a stand-alone *build*.

Sorry. I got it wrong.

Karl <***@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein

--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

William Hubbs

2012-05-31 17:35:49 UTC

Hi Kay,

Post by Kay Sievers
We support stand-alone *operation* of the udev tools, but the build
system does not support a stand-alone *build*. The systemd tree needs
to be built and udev picked out of it.
There are also several other generally useful tools in the built tree,
which you might need too over time, like tmpfiles, module-load,
sysconf, binfmt, ... A couple of D-Bus services to manage system
settings from the desktop.
Various upstream tools start to install config files or use these
interfaces. It might be the simplest to install them too, even when
systemd is not used.

I understand that folks might want these tools, but I don't want to
install the ones that udev doesn't need as part of the udev package. I
am also concerned about libcap and dbus being hard requirements of the
udev build process.

If udev, or the tools that it needs, like tmpfiles, requires these
libraries, that is one thing, otherwise I really do not want
to make them dependencies of the udev package. The issue is that in
gentoo, since we are source based, I would have to require all of our
users to install dbus and libcap just to build udev.

Do you have any suggestions?

Thanks,

William

Bruce Dubbs

2012-05-31 19:33:32 UTC

Post by William Hubbs
Hi Kay,

I understand that folks might want these tools, but I don't want to
install the ones that udev doesn't need as part of the udev package. I
am also concerned about libcap and dbus being hard requirements of the
udev build process.
If udev, or the tools that it needs, like tmpfiles, requires these
libraries, that is one thing, otherwise I really do not want
to make them dependencies of the udev package. The issue is that in
gentoo, since we are source based, I would have to require all of our
users to install dbus and libcap just to build udev.

The Linux From Scratch community has the same problem. We are working
on this in two ways.

1. I've developed a make.sh script and an install.sh script to build,
link, and install udev from the systemd sources bypassing the autotools
environment completely. This is not desirable, but it gets the job done
and is a proof of concept.

2. We are working to modify configure.ac and Makefile.in to do the
right thing. That may take a little more time.

I can say that there are several packages currently required by
configure that are not needed by a udev only build: intltool,
XML::Parser, libpcap2, attr, usbutils, libusb, pciutils, and dbus.

The common/systemd files needed for the udev applications are:

src/shared:
log.c label.c mkdir.c cgroup-util.c strv.c path-util.c conf-files.c
hashmap.c set.c exit-status.c util.c dev-setup.c

src/libsystemd-daemon:
sd-daemon.c

src/login:
sd-login.c

If those files are built and put into a separate library, it would make
the rest of a udev only build much more straight forward.

I'll get back to this list when we have more progress.

-- Bruce
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Tom Gundersen

2012-05-31 19:46:41 UTC

I can say that there are several packages currently required by confi=

gure

that are not needed by a udev only build: =C2=A0intltool, XML::Parser=

, libpcap2,

attr, usbutils, libusb, pciutils, and dbus.

Regarding usbutils and pciutils: these are not needed at compile-time
if you pass in the correct configure switch to set the {pci,usb}ids
path.

The {pci,usb}ids databases are however needed by udev on runtime and
they are traditionally shipped with {usb,pci}utils, so that's
something to keep in mind.

On Arch (as well as on Gentoo), we deal with this by shipping the
databases in a separate package[0], and dropping the dependency on
{pci,usb}utils. Maybe that's something other's would benefit from too.

Cheers,

Tom

[0]: <http://www.archlinux.org/packages/core/any/hwids/>
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug=
" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Kay Sievers

2012-05-31 19:57:37 UTC

I can say that there are several packages currently required by conf=

igure

that are not needed by a udev only build: =C2=A0intltool, XML::Parse=

r, libpcap2,

attr, usbutils, libusb, pciutils, and dbus.

=2E

It's probably not worth to put too much effort into it. We are about
to make a more generic query-able hardware database with pre-compiled
efficient lookup interfaces. It will provide additional key/value
pairs that further classify devices we care about. All this will go
far beyond the human readable strings the ids files provide.

Just saying, pretty soon, the ids files will no longer directly read
by udev. We will see how all that will look like when we get there.

Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug=
" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Tom Gundersen

2012-05-31 21:45:32 UTC

Post by Kay Sievers
It's probably not worth to put too much effort into it. We are about
to make a more generic query-able hardware database with pre-compiled
efficient lookup interfaces. It will provide additional key/value
pairs that further classify devices we care about. All this will go
far beyond the human readable strings the ids files provide.
Just saying, pretty soon, the ids files will no longer directly read
by udev. We will see how all that will look like when we get there.

That makes a lot of sense. Hopefully it will be similar to the hwids
package from a packaging point of view (i.e. a standalone db that can
be shipped independently from any libs/tools).

Cheers,

Tom
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Bruce Dubbs

2012-05-31 20:30:51 UTC

I can say that there are several packages currently required by configure
that are not needed by a udev only build: intltool, XML::Parser, libpcap2,
attr, usbutils, libusb, pciutils, and dbus.

We may have been doing it incorrectly, but we've used

--with-usb-ids-path=no
--with-pci-ids-path=no

in LFS for some time with udev. No one has reported any problems with
that, but there may have been some latent issues we are not aware of.

-- Bruce
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Kay Sievers

2012-05-31 20:52:28 UTC

I can say that there are several packages currently required by con=

figure

that are not needed by a udev only build: =C2=A0intltool, XML::Pars=

er,

libpcap2,
attr, usbutils, libusb, pciutils, and dbus.

Regarding usbutils and pciutils: these are not needed at compile-tim=

if you pass in the correct configure switch to set the {pci,usb}ids
path.
The {pci,usb}ids databases are however needed by udev on runtime and
they are traditionally shipped with {usb,pci}utils, so that's
something to keep in mind.
On Arch (as well as on Gentoo), we deal with this by shipping the
databases in a separate package[0], and dropping the dependency on
{pci,usb}utils. Maybe that's something other's would benefit from to=

Post by Bruce Dubbs
We may have been doing it incorrectly, but we've used
--with-usb-ids-path=3Dno
--with-pci-ids-path=3Dno
in LFS for some time with udev. =C2=A0No one has reported any problem=

s with that,

Post by Bruce Dubbs
but there may have been some latent issues we are not aware of.

Nothing should go wrong.

It's only that some user interfaces want to be nice and show the
'real' name of the devices. But if the ids databases are not around,
they will fall back to things like "Audio Device" instead of "Intel
HDA Audio" and such.

Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug=
" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Kay Sievers

2012-05-31 20:15:04 UTC