Hi,

what exactly changed? Format totally different, or just "some rule" to make 
some kernel module load or vital device node to appear?

On Oct 22, 2013, at 22:42 , [email protected] wrote:

> Hi,
> 
> i would love to keep them at minimum but the new udev loves to have them
> in place even in initrd otherwise it will not boot correctly from CD. i
> will do further tests to minimize packages but for now that is my
> recommendation.
> 
> Regards,
> 
> Iulian
> 
> 
>> Hi,
>> 
>> looks like Gerardo Di Iorio broke that in June, ieek :-/ - he already
>> committed your fix in r42121.
>> 
>> What is wrong with our u/dev rules? As far as I remember the default rules
>> (years ago) where very verbose and created all kinds of random compat
>> stuff and whatnot all over. I would prefer keeping the default rules
>> minimal, lean and clean.
>> 
>> On Oct 21, 2013, at 10:33 , [email protected] wrote:
>> 
>>> Hi all,
>>> 
>>> managed to make current udev to work and boot from CD and stuff. THere
>>> are
>>> two issues that has to be fixed.
>>> 
>>> No 1:
>>> in package configuration file ( trunk/package/filesystem/udev/udev.conf)
>>> there is the line : var_append confopt " " "--libexecdir=/lib udev/" #
>>> $libdir?
>>> 
>>> change the line to be : var_append confopt " " "--libexecdir=/lib/udev/"
>>> #
>>> $libdir? ( aka remove the dam space from between the udev and lib. This
>>> will cause all the udev rules to be written where they should be not in
>>> /lib/rules.d.
>>> 
>>> 
>>> No2:
>>> 
>>> go into downloads, (trunk/download/mirror/u/) unpack the
>>> udev-167.tar.bz2
>>> and copy al the rules from /udev/rules/rules.d into package config
>>> folder
>>> ( from udev-167/rules/rules.d to /trunk/package/filesystem/udev)
>>> 
>>> this will cause all valid rules of udev to be written into
>>> /etc/udev/rules.d and also into initrd image when this image is built.
>>> Witout these rules the installer cannot find stage 2 because there are
>>> no
>>> rules to describe the devices and map corresponding things into /dev
>>> before 2nd stage can be loaded.
>>> 
>>> 
>>> there are still some minor messages on the console after 2nd stage loads
>>> but i will fix them ( or at least try to)
>>> 
>>> 
>>> now clean all the stuff from cache and build and put your CPU's to
>>> rebuild
>>> the distro. It will build and install.
>>> 
>>> cheers,
>>> 
>>> Iulian
>>> 
>>> 
>> 
>> --
>> ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin
>> DE Legal: Amtsgericht Berlin (Charlottenburg) HRB 105123B, Tax-ID#:
>> DE251602478
>> Managing Director: René Rebe
>> http://exactcode.com | http://exactscan.com | http://ocrkit.com |
>> http://t2-project.org | http://rene.rebe.de
>> 
>> 
> 

-- 
 ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin
 DE Legal: Amtsgericht Berlin (Charlottenburg) HRB 105123B, Tax-ID#: DE251602478
 Managing Director: René Rebe
 http://exactcode.com | http://exactscan.com | http://ocrkit.com | 
http://t2-project.org | http://rene.rebe.de

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2

Reply via email to