Precedence: list
MIME-Version: 1.0
In-Reply-To: <174bbc5214754cfa31d9156ec1e78660@riseup.net>
References: <c0880cc02818948a5b400087209c80d0@riseup.net> <AA21151C-A9BB-4FD9-9199-0F57434B8047@jirutka.cz>
 <174bbc5214754cfa31d9156ec1e78660@riseup.net>
From: Alba Pompeo <albapompeo@gmail.com>
Date: Sun, 3 Jul 2016 10:51:09 -0300
Message-ID: <CAJDAfTD9+q3fbYMJp05sLLhHVSdKCzNU-diEtjCyzKXUED4iiA@mail.gmail.com>
Subject: Re: [alpine-devel] smdev
To: =?UTF-8?B?Q8OhZw==?= <caoc@riseup.net>
Cc: alpine-devel@lists.alpinelinux.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I agree with C=C3=A1g about the absence of textual configuration files.
It's an advantage because it keeps complexity down.
Almost no user will change their smdev config options, that's
something Alpine will have sane defaults for.
But if the user really wants to, I see no problem with config.def.h
[0]. /usr/src to the rescue.
I remember smdev developers talked about wanting to integrate it on
Alpine in the past, here on the mailing list.
I think ncopa wants it too, but had problems with hotplugging (?) I think.
But it looks like C=C3=A1g has solved that problem. Let's wait and see if
ncopa thinks now smdev is ready (for 3.5 alpine release?).

Ciao!

[0] http://git.suckless.org/smdev/tree/config.def.h

On Sun, Jul 3, 2016 at 10:35 AM, C=C3=A1g <caoc@riseup.net> wrote:
> Jakub Jirutka wrote:
>
>> I wonder, what are the differences between mdev and smdev? What are
>> the benefits of smdev for end users?
>
>
> smdev is IIRC a fork of mdev (or maybe was, probably it was rewritten)
> that is compatible with it [0], though it doesn't have all its features.
> The benefits are: you don't need BusyBox for it and it is smaller
> (almost thrice as short in terms of LOC). It does what it says -
> manages device nodes, and does it well.
>
>> I currently see one significant drawback - smdev (and all other
>> suckless projects) doesn't support textual configuration files. This
>> approach doesn't go well with binary distributions; users can't simply
>> change any settings. I understand the reasons behind using header
>> files for config, but the fact is that it's not very convenient for
>> users.
>
>
> For me, it's rather an advantage. Once configured you go with it. Actuall=
y
> I've never modified my udev rules, they always worked for me and with smd=
ev
> I use
> the default config.h because it works just fine. Anyway, if users need to
> modify the rules, I'd put the source inside /usr/src and let them do it :=
)
>
> By the way, I don't know why Alpine doesn't use mdev, to me it seems to b=
e
> the
> most appropriate variant (or does it? I heard it uses eudev. I currently
> have
> no chance to check it out).
>
> If ye need more info about smdev, please consult the link down below and =
the
> code.
> Also, write to dev at suckless dot org, since I am not an smdev developer=
.
>
> Sl=C3=A1inte,
> C=C3=A1g
>
> [0]:http://core.suckless.org/smdev
>
>
>
> ---
> Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
> Help:         alpine-devel+help@lists.alpinelinux.org
> ---
>


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---