sm-discuss AT lists.ibiblio.org
Subject: Public SourceMage Discussion List
List archive
- From: Javier Vasquez <j.e.vasquez.v AT gmail.com>
- To: "sm, discuss" <sm-discuss AT lists.ibiblio.org>
- Subject: Re: [SM-Discuss] eudev
- Date: Sat, 24 Aug 2013 14:21:57 -0600
On Mon, Aug 19, 2013 at 6:33 PM, Javier Vasquez <j.e.vasquez.v AT gmail.com>
wrote:
> On Mon, Aug 19, 2013 at 10:18 AM, Javier Vasquez
> <j.e.vasquez.v AT gmail.com> wrote:
>> On Mon, Aug 19, 2013 at 7:47 AM, Javier Vasquez <j.e.vasquez.v AT gmail.com>
>> wrote:
>>> On Sun, Aug 18, 2013 at 10:25 PM, Javier Vasquez
>>> <j.e.vasquez.v AT gmail.com> wrote:
>>>> On Sun, Aug 18, 2013 at 10:02 PM, Javier Vasquez
>>>> <j.e.vasquez.v AT gmail.com> wrote:
>>>>> ...
>>>>>> Besides fixing the spell so that INSTALL works as it should, the only
>>>>>> problem left for me would be the rename of interfaces, not paying
>>>>>> attention to the names in rules.d...
>>>>>
>>>>> I was mistaken with the rename... It's not that. I got another
>>>>> machine (see bug 589), where eudev for some reason doesn't perform the
>>>>> rename (not sure why), but it got the interfaces names twisted, not as
>>>>> I required them with the udev rules. So it seems at least the naming
>>>>> rules are not followed by eudev...
>>>>
>>>> Getting back to the renaming theory. The other machine for which
>>>> there's no renaming, is getting the naming right (as int the naming
>>>> rules), so it seems it was 1st time new kernel + 1st time new eudev
>>>> affecting it.
>>>>
>>>> The one that renames though, get the names good at 1st, but then the
>>>> rename changes those names...
>>>>
>>>> But I'm done, at least for a while, :-)
>>>
>>>
>>> I do have a suspect now, but need to recompile the kernel, :-)
>>>
>>> The difference beteween x86_64 and x86_32 machines, is that for x86_64 I
>>> used:
>>>
>>> CONFIG_COREDUMP=y
>>>
>>> That might getting eudev confused, or even better, its purpose might
>>> be related to force [e]udev to rename stuff.
>>>
>>> I'll try that later. Recompiling the kernel takes time, and needs
>>> reboot...
>>
>>
>> My mistake, I was in a hurry, the configuration I had different is:
>>
>> CONFIG_CHECKPOINT_RESTORE=y
>
>
> That was not it. without CONFIG_CHECKPOINT_RESTORE=y udev still
> renames the network interfaces.
>
> Weird that it happens in one machine and not the other, and also that
> the rename doesn't respect the naming rules, even when the 1st naming
> did.
I wanted to mention that while the rename of the network interfaces
not obeying the udev provided rules, is the only issue pending from my
stand point, I do believe eudev is in pretty good shape. And even the
reasons for not mounting some stuff initially was not due to eudev
itself, but because of the way the udev.conf is getting installed.
This renaming is something not stopping eudev from working, :-)
--
Javier.
-
Re: [SM-Discuss] eudev
, (continued)
- Re: [SM-Discuss] eudev, Javier Vasquez, 08/18/2013
- Re: [SM-Discuss] eudev, Javier Vasquez, 08/18/2013
- Re: [SM-Discuss] eudev, Javier Vasquez, 08/18/2013
- Re: [SM-Discuss] eudev, Javier Vasquez, 08/18/2013
- Re: [SM-Discuss] eudev, Javier Vasquez, 08/18/2013
- Re: [SM-Discuss] eudev, Javier Vasquez, 08/19/2013
- Re: [SM-Discuss] eudev, Javier Vasquez, 08/19/2013
- Re: [SM-Discuss] eudev, Javier Vasquez, 08/19/2013
- Re: [SM-Discuss] eudev, Javier Vasquez, 08/19/2013
- Re: [SM-Discuss] eudev, Javier Vasquez, 08/19/2013
- Re: [SM-Discuss] eudev, Javier Vasquez, 08/24/2013
Archive powered by MHonArc 2.6.24.