From: Didier Spaier <didier@slint.fr>
To: eudev@lists.gentoo.org
Subject: Re: [eudev] Unbind eudev of btrfs
Date: Thu, 06 Nov 2014 19:27:17 +0100 [thread overview]
Message-ID: <545BBD85.5060301@slint.fr> (raw)
In-Reply-To: <20141106092610.GA3157@minihost>
On 06/11/2014 10:26, Александр Паутов wrote:
> В Четверг, 06.11.2014 в 08:47 +0100, Didier Spaier писал:
>>
>> Maybe I was wrongly assuming that the need of kernel
>> version 3.7 for firmware loading support implied the same
>> need for udev as for systemd?
>>
>> I'll let other people respond as I'm not a developer.
>>
>> Didier
>
> Forgive me if impolite wrote.
> It seems to find where to fix. Make a temporary patch. Eudev compiled
> without btrfs.h. I will test what happened.
Hi Александр,
You were not impolite at all!
My question (admittedly off topic and now answered by Anthony) was
genuine as I wrote that in a forum post:
http://www.linuxquestions.org/questions/slackware-14/%5Bannounce%5D-eudev-for-slackware-14-1-is-available-for-testing-purposes-4175505218/#post5262869
and wondered if what I wrote was accurate.
By the way Anthony, I have no bug or weirdness report yet coming from
users of eudev 2.1.1 for Slackware 14.1: so far so good, thanks to you
and the whole team!
Best regards,
Didier
PS: Александр, our Slint project now provides polyglot installers and
administration tools for Slackware in Russian an Ukrainian among other
languages, see:
http://slint.fr
if you want to try it.
next prev parent reply other threads:[~2014-11-06 18:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 4:58 [eudev] Unbind eudev of btrfs Александр Паутов
2014-11-06 7:15 ` Didier Spaier
2014-11-06 7:36 ` Александр Паутов
2014-11-06 7:47 ` Didier Spaier
2014-11-06 9:26 ` Александр Паутов
2014-11-06 10:39 ` Anthony G. Basile
2014-11-06 18:27 ` Didier Spaier [this message]
2014-11-06 10:38 ` Anthony G. Basile
2014-11-06 10:35 ` Anthony G. Basile
2014-11-06 10:33 ` Anthony G. Basile
2014-11-07 1:45 ` Александр Паутов
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=545BBD85.5060301@slint.fr \
--to=didier@slint.fr \
--cc=eudev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox