Re: [lfs-dev] udev, eudev, mdev
From: Armin K. kre...@email.com Subject: Re: [lfs-dev] udev, eudev, mdev Date: Tue, 04 Mar 2014 17:09:16 +0100 On 03/04/2014 04:23 PM, Bruce Dubbs wrote: I've been working on udev and have got it to build with the systemd-210 source. The problem is that it is getting more and more intertwined with the rest of systemd requiring things that don't seem to be applicable. For instance, filea.c requires a function from fileb.c which requires a function from filec.c. The problem is that filea really doesn't require anything from filec, but the build process doesn't like unresolved references. My question is whether we need to try either eudev or mdev. Does anyone have any experience with eudev or mdev? I note that the latest eudev is dated today. http://dev.gentoo.org/~blueness/eudev/ -- Bruce eudev is rather the udev from pre-systemd merge with all the latest fixes pulled from systemd tree. Note sure, but I think mdev is something else and not really compatible with original udev. eudev seems to be the best solution for (B)LFS. You probably alredy know that clfs uses eudev. I am personnaly running a clfs 2.1.0 multilib 64-32 and eudev seems to work perfectly. Since an lfs is very close to a clfs (before this clfs I installed 2 or 3 lfs version so I may consider that I know these system quite well.) I might predict that eudev will work on an lfs. Regards Pierre -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] udev, eudev, mdev
From: Bruce Dubbs bruce.du...@gmail.com Subject: Re: [lfs-dev] udev, eudev, mdev Date: Tue, 04 Mar 2014 10:43:49 -0600 Armin K. wrote: On 03/04/2014 04:23 PM, Bruce Dubbs wrote: I've been working on udev and have got it to build with the systemd-210 source. The problem is that it is getting more and more intertwined with the rest of systemd requiring things that don't seem to be applicable. For instance, filea.c requires a function from fileb.c which requires a function from filec.c. The problem is that filea really doesn't require anything from filec, but the build process doesn't like unresolved references. My question is whether we need to try either eudev or mdev. Does anyone have any experience with eudev or mdev? I note that the latest eudev is dated today. http://dev.gentoo.org/~blueness/eudev/ eudev is rather the udev from pre-systemd merge with all the latest fixes pulled from systemd tree. Note sure, but I think mdev is something else and not really compatible with original udev. eudev seems to be the best solution for (B)LFS. One difference that jumped out at me was that systemd's libudev is 1.4.0 and eudev's version is 1.3.0. I don't know how much that changes things. eudev wants gperf and gtk-doc. We could add gperf to LFS and probably do away with both gperf and the gudev build in BLFS. gtk-doc needs several other prerequisites and is not a candidate for LFS, but I don't think that's needed. On clfs we used eudev 1.3 but nieghter gperf nor gtk-doc are installed. Regards Pierre -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] udev, eudev, mdev
Ken Moffat wrote:
On Tue, Mar 04, 2014 at 11:37:32AM -0600, William Harrington wrote:
On Mar 4, 2014, at 10:43 AM, Bruce Dubbs wrote:
eudev wants gperf and gtk-doc. We could add gperf to LFS and probably
do away with both gperf and the gudev build in BLFS. gtk-doc needs
several other prerequisites and is not a candidate for LFS, but I
don't
think that's needed.
In CLFS we use Eudev up to v 1.4 and that doesn't require gperf and
gtk-doc.
http://dev.gentoo.org/~blueness/eudev/
Grab the tarballs from there.
Sincerely,
William Harrington
I've been using that version with LFS-7.5, so thanks for putting it
in clfs - much easier to find the released version by looking in
your book than by trying to find a working link from google ;-)
Unfortunately, like many github projects, eudev doesn't go out of its
way to point to released tarballs. Also, I think I now use your
command switches.
When systemd swallowed udev, I initially tried a separate
stand-alone udev, but eudev seems to have gained a sufficient number
of maintainers who are prepared to look at what is happening in
systemd and decide whether or not to use any of each change. I
don't always agree with their judgement (specifically, they took
systemd's mysterious naming of the ethernet port), but it all seems
to work well enough.
There was a suggestion in the past few months that 'tree' was
needed for the eudev testsuite, but it doesn't seem to add anything
for me so I've now dropped it.
I built eudev in LFS-7.5 chroot like this:
1. it doesn't seem to need the symlinks for the blkid and uuid
headers, nor the library path.
2. create directories
install -dv /lib/{firmware,udev/devices/pts}
3. configure
./configure --prefix=/usr --sysconfdir=/etc \
--with-rootprefix= --libdir=/usr/lib \
--with-firmware-path=/usr/lib/firmware \
--with-rootlibdir=/lib --exec-prefix=/ \
--enable-split-usr --enable-libkmod --enable-rule-generator \
--disable-static --disable-introspection \
--disable-gudev --disable-keymap
4. make : it looks as if multiple make works, at least in LFS
(I see that my rebuild in BLFS for gudev still has -j1, never got
around to confirming that -jN works there).
5. create directories to allow the tests to work in an empty system:
mkdir -pv /etc/udev/rules.d
mkdir -pv /lib/udev/rules.d
6. the tests:
make check
This reports that both tests passed. I am uncertain if the first
test actually does anything (its log is empty, even in BLFS - I found
a suggestion that Python was needed, but that made no difference),
unless python3 was what was meant (they are gentoo devs, so I guess
that is a possibility) but the second test is the old perl script of
135 tests which date back to udev. Their detailed output is in
test/udev-test.pl.log, I find it reassuring to save that file.
In the chroot environment I get one failure in the udev-test.pl script.
The make check says:
FAIL: udev-test.pl
PASS: rules-test.sh
...
See test/test-suite.log
Looking at the log, I see several items:
open /dev/null failed: No such file or directory
but there certainly is
crw-rw-rw- 1 root root 1, 3 Feb 28 17:24 /dev/null
in chroot. However that does not cause the test to fail.
What I do have is:
TEST 93: devnode substitution test
device
'/devices/pci:00/:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda'
expecting node/link 'node'
open /dev/null failed: No such file or directory
add: error
remove: ok
I do have
/sys/devices/pci:00/:00:1f.2
but there is no host0 there. Searching, I also have:
/sys/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0
I'm not sure if this is significant or not, but I get exactly the same
error in a full up system. tree gives:
test/dev
|-- block
| `-- 8:0 - ../sda
|-- char
`-- sda
I'm don't know how to interpret that.
Does anyone have ideas about the test failure?
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Re: [lfs-dev] udev, eudev, mdev
On Mar 5, 2014, at 3:09 PM, Bruce Dubbs wrote: FAIL: udev-test.pl PASS: rules-test.sh ... See test/test-suite.log Same as we have had in CLFS since migrating to eudev. Sincerely, William Harrington -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] udev, eudev, mdev
On 03/05/2014 10:58 PM, William Harrington wrote: On Mar 5, 2014, at 3:09 PM, Bruce Dubbs wrote: FAIL: udev-test.pl PASS: rules-test.sh ... See test/test-suite.log Same as we have had in CLFS since migrating to eudev. Sincerely, William Harrington Same test fails in systemd, too. I have simply disabled it with a sed. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] udev, eudev, mdev
Armin K. wrote: On 03/05/2014 10:58 PM, William Harrington wrote: On Mar 5, 2014, at 3:09 PM, Bruce Dubbs wrote: FAIL: udev-test.pl PASS: rules-test.sh ... See test/test-suite.log Same as we have had in CLFS since migrating to eudev. Sincerely, William Harrington Same test fails in systemd, too. I have simply disabled it with a sed. yes: sed -i '/devnode substitution/ a exp_add_error = yes,' \ test/udev-test.pl Make the error expected. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] udev, eudev, mdev
On 03/06/2014 12:13 AM, Bruce Dubbs wrote: Armin K. wrote: On 03/05/2014 10:58 PM, William Harrington wrote: On Mar 5, 2014, at 3:09 PM, Bruce Dubbs wrote: FAIL: udev-test.pl PASS: rules-test.sh ... See test/test-suite.log Same as we have had in CLFS since migrating to eudev. Sincerely, William Harrington Same test fails in systemd, too. I have simply disabled it with a sed. yes: sed -i '/devnode substitution/ a exp_add_error = yes,' \ test/udev-test.pl Make the error expected. -- Bruce I simply disabled the test entirely from running. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] udev, eudev, mdev
Ken Moffat wrote:
I built eudev in LFS-7.5 chroot like this:
Thanks for those instructions Ken. I took those and built in chroot
with these:
sed -i '/devnode substitution/ a exp_add_error = yes,' test/udev-test.pl
sed -i '/struct ucred/i struct ucred;' src/libudev/util.h
./configure --prefix=/usr \
--sysconfdir=/etc \
--with-rootprefix= \
--libexecdir=/lib \
--enable-split-usr \
--enable-libkmod\
--libdir=/usr/lib \
--with-rootlibdir=/lib \
--sbindir=/sbin \
--bindir=/sbin \
--enable-rule_generator \
--disable-introspection \
--disable-keymap\
--disable-gudev \
--disable-gtk-doc-html \
--with-firmware-path=/lib/firmware
make
mkdir -pv /lib/{firmware,udev/devices/pts}
mkdir -pv /etc/udev/rules.d
mkdir -pv /lib/udev/rules.d
make check
install -dv $DEST/lib/firmware
make DESTDIR=$DEST install
--
The first sed sets the failing test to expected. I'll look into that
some more. With it, the check is clean.
The second sed cleans up some irritating warnings.
Almost everything is as it should be, except the man pages are not
installed. We will probably have to create a patch or tarball for
those. It would probably be easier as a patch.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Re: [lfs-dev] udev, eudev, mdev
Bruce Dubbs wrote: Armin K. wrote: On 03/05/2014 10:58 PM, William Harrington wrote: On Mar 5, 2014, at 3:09 PM, Bruce Dubbs wrote: FAIL: udev-test.pl PASS: rules-test.sh ... See test/test-suite.log Same as we have had in CLFS since migrating to eudev. Sincerely, William Harrington Same test fails in systemd, too. I have simply disabled it with a sed. yes: sed -i '/devnode substitution/ a exp_add_error = yes,' \ test/udev-test.pl Make the error expected. Found the error. The test has a rule where it hard codes /usr/bin/test. We don't have that. We have /bin/test as is should if we are going to support a split / -- /usr setup. In any case the sed should be: sed -r -i 's|/usr(/bin/test)|\1|' test/udev-test.pl -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] udev, eudev, mdev
On 03/04/2014 04:23 PM, Bruce Dubbs wrote: I've been working on udev and have got it to build with the systemd-210 source. The problem is that it is getting more and more intertwined with the rest of systemd requiring things that don't seem to be applicable. For instance, filea.c requires a function from fileb.c which requires a function from filec.c. The problem is that filea really doesn't require anything from filec, but the build process doesn't like unresolved references. My question is whether we need to try either eudev or mdev. Does anyone have any experience with eudev or mdev? I note that the latest eudev is dated today. http://dev.gentoo.org/~blueness/eudev/ -- Bruce eudev is rather the udev from pre-systemd merge with all the latest fixes pulled from systemd tree. Note sure, but I think mdev is something else and not really compatible with original udev. eudev seems to be the best solution for (B)LFS. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] udev, eudev, mdev
Armin K. wrote: On 03/04/2014 04:23 PM, Bruce Dubbs wrote: I've been working on udev and have got it to build with the systemd-210 source. The problem is that it is getting more and more intertwined with the rest of systemd requiring things that don't seem to be applicable. For instance, filea.c requires a function from fileb.c which requires a function from filec.c. The problem is that filea really doesn't require anything from filec, but the build process doesn't like unresolved references. My question is whether we need to try either eudev or mdev. Does anyone have any experience with eudev or mdev? I note that the latest eudev is dated today. http://dev.gentoo.org/~blueness/eudev/ eudev is rather the udev from pre-systemd merge with all the latest fixes pulled from systemd tree. Note sure, but I think mdev is something else and not really compatible with original udev. eudev seems to be the best solution for (B)LFS. One difference that jumped out at me was that systemd's libudev is 1.4.0 and eudev's version is 1.3.0. I don't know how much that changes things. eudev wants gperf and gtk-doc. We could add gperf to LFS and probably do away with both gperf and the gudev build in BLFS. gtk-doc needs several other prerequisites and is not a candidate for LFS, but I don't think that's needed. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] udev, eudev, mdev
On 03/04/2014 05:43 PM, Bruce Dubbs wrote: Armin K. wrote: On 03/04/2014 04:23 PM, Bruce Dubbs wrote: I've been working on udev and have got it to build with the systemd-210 source. The problem is that it is getting more and more intertwined with the rest of systemd requiring things that don't seem to be applicable. For instance, filea.c requires a function from fileb.c which requires a function from filec.c. The problem is that filea really doesn't require anything from filec, but the build process doesn't like unresolved references. My question is whether we need to try either eudev or mdev. Does anyone have any experience with eudev or mdev? I note that the latest eudev is dated today. http://dev.gentoo.org/~blueness/eudev/ eudev is rather the udev from pre-systemd merge with all the latest fixes pulled from systemd tree. Note sure, but I think mdev is something else and not really compatible with original udev. eudev seems to be the best solution for (B)LFS. One difference that jumped out at me was that systemd's libudev is 1.4.0 and eudev's version is 1.3.0. I don't know how much that changes things. eudev wants gperf and gtk-doc. We could add gperf to LFS and probably do away with both gperf and the gudev build in BLFS. gtk-doc needs several other prerequisites and is not a candidate for LFS, but I don't think that's needed. -- Bruce I believe that those files are only required to generate files. Last time I looked at they didn't ship configure and friends, you had to generate them yourself with ./autogen.sh. One solution is to ship a tarball on anduin with pre-generated stuff to avoid dependency on gperf and gtk-doc. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] udev, eudev, mdev
On Mar 4, 2014, at 10:43 AM, Bruce Dubbs wrote: eudev wants gperf and gtk-doc. We could add gperf to LFS and probably do away with both gperf and the gudev build in BLFS. gtk-doc needs several other prerequisites and is not a candidate for LFS, but I don't think that's needed. In CLFS we use Eudev up to v 1.4 and that doesn't require gperf and gtk-doc. http://dev.gentoo.org/~blueness/eudev/ Grab the tarballs from there. Sincerely, William Harrington -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] udev, eudev, mdev
William Harrington wrote: On Mar 4, 2014, at 10:43 AM, Bruce Dubbs wrote: eudev wants gperf and gtk-doc. We could add gperf to LFS and probably do away with both gperf and the gudev build in BLFS. gtk-doc needs several other prerequisites and is not a candidate for LFS, but I don't think that's needed. In CLFS we use Eudev up to v 1.4 and that doesn't require gperf and gtk-doc. http://dev.gentoo.org/~blueness/eudev/ Yes, I have been experimenting with 1.5.1. It builds pretty clean. It needs this to stop all warnings: sed -i '/struct ucred/i struct ucred;' src/libudev/util.h but that's just a little eye candy. Otherwise the clfs instructions look good. I'll test it out. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] udev, eudev, mdev
On Tue, Mar 04, 2014 at 11:37:32AM -0600, William Harrington wrote:
On Mar 4, 2014, at 10:43 AM, Bruce Dubbs wrote:
eudev wants gperf and gtk-doc. We could add gperf to LFS and probably
do away with both gperf and the gudev build in BLFS. gtk-doc needs
several other prerequisites and is not a candidate for LFS, but I
don't
think that's needed.
In CLFS we use Eudev up to v 1.4 and that doesn't require gperf and
gtk-doc.
http://dev.gentoo.org/~blueness/eudev/
Grab the tarballs from there.
Sincerely,
William Harrington
I've been using that version with LFS-7.5, so thanks for putting it
in clfs - much easier to find the released version by looking in
your book than by trying to find a working link from google ;-)
Unfortunately, like many github projects, eudev doesn't go out of its
way to point to released tarballs. Also, I think I now use your
command switches.
When systemd swallowed udev, I initially tried a separate
stand-alone udev, but eudev seems to have gained a sufficient number
of maintainers who are prepared to look at what is happening in
systemd and decide whether or not to use any of each change. I
don't always agree with their judgement (specifically, they took
systemd's mysterious naming of the ethernet port), but it all seems
to work well enough.
There was a suggestion in the past few months that 'tree' was
needed for the eudev testsuite, but it doesn't seem to add anything
for me so I've now dropped it.
I built eudev in LFS-7.5 chroot like this:
1. it doesn't seem to need the symlinks for the blkid and uuid
headers, nor the library path.
2. create directories
install -dv /lib/{firmware,udev/devices/pts}
3. configure
./configure --prefix=/usr --sysconfdir=/etc \
--with-rootprefix= --libdir=/usr/lib \
--with-firmware-path=/usr/lib/firmware \
--with-rootlibdir=/lib --exec-prefix=/ \
--enable-split-usr --enable-libkmod --enable-rule-generator \
--disable-static --disable-introspection \
--disable-gudev --disable-keymap
4. make : it looks as if multiple make works, at least in LFS
(I see that my rebuild in BLFS for gudev still has -j1, never got
around to confirming that -jN works there).
5. create directories to allow the tests to work in an empty system:
mkdir -pv /etc/udev/rules.d
mkdir -pv /lib/udev/rules.d
6. the tests:
make check
This reports that both tests passed. I am uncertain if the first
test actually does anything (its log is empty, even in BLFS - I found
a suggestion that Python was needed, but that made no difference),
unless python3 was what was meant (they are gentoo devs, so I guess
that is a possibility) but the second test is the old perl script of
135 tests which date back to udev. Their detailed output is in
test/udev-test.pl.log, I find it reassuring to save that file.
7. install, create a /sbin/udevd symlink for the LFS bootscripts,
update the hardware db (I've still no idea what that is for) and in
my case ensure that my wired nic is called eth0:
make install
ln -svf /sbin/udevd /lib/udev
udevadm hwdb --update
echo # dummy, so that network is once again on eth0 \
/etc/udev/rules.d/80-net-name-slot.rules
For BLFS, I rebuild it after Xorg on desktops to get gudev : gperf
is already present, so I just omit --disable-gudev (I don't need
keymap for a normal keyboard, nor introspection in my normal build -
but I did remove --disable-introspection to build the gir stuff when
I was building for gnome packages.
ĸen
--
das eine Mal als Tragödie, dieses Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Re: [lfs-dev] udev, eudev, mdev
Ken Moffat wrote:
On Tue, Mar 04, 2014 at 11:37:32AM -0600, William Harrington wrote:
On Mar 4, 2014, at 10:43 AM, Bruce Dubbs wrote:
eudev wants gperf and gtk-doc. We could add gperf to LFS and probably
do away with both gperf and the gudev build in BLFS. gtk-doc needs
several other prerequisites and is not a candidate for LFS, but I
don't
think that's needed.
In CLFS we use Eudev up to v 1.4 and that doesn't require gperf and
gtk-doc.
http://dev.gentoo.org/~blueness/eudev/
Grab the tarballs from there.
Sincerely,
William Harrington
I've been using that version with LFS-7.5, so thanks for putting it
in clfs - much easier to find the released version by looking in
your book than by trying to find a working link from google ;-)
Unfortunately, like many github projects, eudev doesn't go out of its
way to point to released tarballs. Also, I think I now use your
command switches.
When systemd swallowed udev, I initially tried a separate
stand-alone udev, but eudev seems to have gained a sufficient number
of maintainers who are prepared to look at what is happening in
systemd and decide whether or not to use any of each change. I
don't always agree with their judgement (specifically, they took
systemd's mysterious naming of the ethernet port), but it all seems
to work well enough.
There was a suggestion in the past few months that 'tree' was
needed for the eudev testsuite, but it doesn't seem to add anything
for me so I've now dropped it.
I built eudev in LFS-7.5 chroot like this:
1. it doesn't seem to need the symlinks for the blkid and uuid
headers, nor the library path.
2. create directories
install -dv /lib/{firmware,udev/devices/pts}
3. configure
./configure --prefix=/usr --sysconfdir=/etc \
--with-rootprefix= --libdir=/usr/lib \
--with-firmware-path=/usr/lib/firmware \
--with-rootlibdir=/lib --exec-prefix=/ \
--enable-split-usr --enable-libkmod --enable-rule-generator \
--disable-static --disable-introspection \
--disable-gudev --disable-keymap
4. make : it looks as if multiple make works, at least in LFS
(I see that my rebuild in BLFS for gudev still has -j1, never got
around to confirming that -jN works there).
5. create directories to allow the tests to work in an empty system:
mkdir -pv /etc/udev/rules.d
mkdir -pv /lib/udev/rules.d
6. the tests:
make check
This reports that both tests passed. I am uncertain if the first
test actually does anything (its log is empty, even in BLFS - I found
a suggestion that Python was needed, but that made no difference),
unless python3 was what was meant (they are gentoo devs, so I guess
that is a possibility) but the second test is the old perl script of
135 tests which date back to udev. Their detailed output is in
test/udev-test.pl.log, I find it reassuring to save that file.
7. install, create a /sbin/udevd symlink for the LFS bootscripts,
update the hardware db (I've still no idea what that is for) and in
my case ensure that my wired nic is called eth0:
make install
ln -svf /sbin/udevd /lib/udev
udevadm hwdb --update
echo # dummy, so that network is once again on eth0 \
/etc/udev/rules.d/80-net-name-slot.rules
For BLFS, I rebuild it after Xorg on desktops to get gudev : gperf
is already present, so I just omit --disable-gudev (I don't need
keymap for a normal keyboard, nor introspection in my normal build -
but I did remove --disable-introspection to build the gir stuff when
I was building for gnome packages.
Thanks Ken. I'm building a eudev system now for testing. It may take a
couple of iterations to get all the details right, but it looks like the
way to go. The extraction I was doing was a PITA because of upstream's
mixing in non-udev stuff which kept making the task more and more
difficult.
I can change the boot script to point to the new location for udevd
easily enough. We'll need to update Section 7.4 also.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
