On 11/28/14, René Rebe <[email protected]> wrote: > Hi, > > On Nov 25, 2014, at 14:45, Barry Kauler <[email protected]> wrote: > >> >> Hi, >> With my distro Quirky Linux (a fork of Puppy Linux), I have used eudev >> for over a year, quite happily. >> >> I would like to bring eudev into T2, however, I was wondering what to >> do about the name 'eudev', as all over the place the dependencies are >> specified as 'udev'. >> >> eudev is a drop-in replacement for udev, although kmod has to be used >> and the kernel configured with automatic creation of device nodes. I >> had some discussion back in June 2013 with the eudev developers, that >> sorted this out: >> >> https://github.com/gentoo/eudev/issues/60 >> >> These two kernel options are required: >> CONFIG_DEVTMPFS=y >> CONFIG_DEVTMPFS_MOUNT=y >> >> kmod is required, replacing the old module-init-tools. >> >> For the record, discussion on my blog: >> http://bkhome.org/blog2/?viewDetailed=00168 >> http://bkhome.org/blog2/?viewDetailed=00284 >> http://bkhome.org/news/?viewDetailed=00112 >> >> Anyway, could anyone kindly advise me about the "eudev" versus "udev" >> naming. Is it possible in T2 to declare that eudev is equivalent to >> udev, as far as deps go? Like, an alias? > > > Currently T2 does not really use the Deps at build-time anyway: They where > historically meant for the installer and such. So you can ignore the > Dependency name for now. > > Can you for the start send the package .desc and such? I hope it has a clear > separate name like eudev - so they can live in parallel? >
I have setup my local T2 with eudev totally replacing udev. I have kept the name 'udev', just changed the download package name in udev.desc to get the eudev source. The reason that it is awkward to run them in parallel is because of tests in the .conf files. I have just done a search, actually, there aren't too many: hotplug++.conf dfb-linux-fusion.conf zaptel.conf These have code in them with this "pkginstalled udev && " If you have eudev as a separate package from udev, then you will have to modify those .conf files to test for either udev or eudev. My situation is different. I am only using T2 to build binary tarballs, then taking those out and importing them into the Quirky build system, which has its own root f.s. skeleton, startup/shutdown scripts, etc. In your case, if you went over to using eudev only, you would have to follow through with configuring the kernel appropriately, removing module-init-tools permanently, etc. if you wanted to do that, you might have to do a branch build and make sure that you can build a sane live-cd or whatever. Then there are some of your embedded targets, they are not setup for building with a kernel that auto-creates dev nodes and loads modules and firmware. I have attached my udev.conf and udev.desc. Perhaps you don't want to go the whole way with throwing out the old udev 167, so you could introduce these files as eudev.conf and eudev.desc, and patch the above-mentioned .conf files to test for both udev and eudev. That would be the simplest way to ease into using eudev, probably, so you can keep udev 167 as well, for now. Regards, Barry
udev.tar.gz
Description: GNU Zip compressed data
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
