X-Original-To: alpine-devel@mail.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from mail.alpinelinux.org (dallas-a1.alpinelinux.org [127.0.0.1]) by mail.alpinelinux.org (Postfix) with ESMTP id 049CFDC03BF for ; Sun, 26 Jul 2015 00:51:13 +0000 (UTC) Received: from mail-ie0-f176.google.com (mail-ie0-f176.google.com [209.85.223.176]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id C6BDCDC00FF for ; Sun, 26 Jul 2015 00:51:12 +0000 (UTC) Received: by iecrl10 with SMTP id rl10so38354720iec.1 for ; Sat, 25 Jul 2015 17:51:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BNzxDIyRRf6ME8iC0u+DvQTxM/SciHWneSQrJfAvdkE=; b=fWyKiviSeC3Bkr8Rb8JS0jScjBkhONdBPTZFa+TFdbwlMhQ7GAvZu/IOf8vnHtvatK dItmij6xu41/X7Fu98mOSYMkO+y6PdbZYJ36Gin1nDZj0+QcQHcAsMc7SgZFWnQ0Wkp+ FF1X99rtCwhkQXMKjRE34L4aDDzbBiDpQhTNHoLX8IbM3Ulgp2lblbW+V4CFvEOYFtwH VzR12qKURU1NC3yNbFie0zynaGgngIWiAns7CMugiGp68xCzXkcJp/hlntXimZIrmgUt HE5Fe/eGHVbenhpLcBXQkg2GWAJAzIARR3j/bcl+H0QoGKhREjwu+RtujCbDw41enpHY 3sYw== X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 X-Received: by 10.107.129.24 with SMTP id c24mr36518587iod.158.1437871872081; Sat, 25 Jul 2015 17:51:12 -0700 (PDT) Received: by 10.64.81.164 with HTTP; Sat, 25 Jul 2015 17:51:12 -0700 (PDT) In-Reply-To: References: Date: Sat, 25 Jul 2015 20:51:12 -0400 Message-ID: Subject: [alpine-devel] Re: udev replacement on Alpine Linux From: Jude Nelson To: Alan Pillay Cc: alpine-devel@lists.alpinelinux.org, sin@2f30.org, hiltjo@codemadness.org, rob@landley.net, frank@tuxrocks.com, dev@frign.de Content-Type: multipart/alternative; boundary=001a113f90482b0793051bbca2f3 X-Virus-Scanned: ClamAV using ClamSMTP --001a113f90482b0793051bbca2f3 Content-Type: text/plain; charset=UTF-8 Hi everyone, > [vdev] a device manager with an approach a bit different, offers an > optional filesystem interface that implements a per-process view of > /dev. Possibly the least simple alternative, but interesting > nonetheless. > > Thank you for your interest in vdev. I am the principal developer. I hope you all don't mind me chiming in to provide a little bit more information. First, I can't emphasize the "optional" qualifier enough regarding the filesystem component vdevfs. The hotplug daemon vdevd and the libudev-compat library are meant to replace udevd and libudev respectively; the filesystem is an add-on that can be used independently of whatever device manager is running. There are more detailed write-up's on the design goals for each of the three vdev components in [0] and [1]. Second, I would like to point out that vdevd by itself is not too different from mdev, nldev, and smdev. The udev-like behavior comes almost entirely from the shell scripts and auxiliary helper programs it executes in reaction to device uevents. I bring this up because these scripts and helper programs could easily be ported to mdev, nldev, and smdev simply by providing a wrapper that sets the appropriate environment variables (a listing can be found in Appendix A of [2]). Third, I would like to point out that libudev-compat is *not* dependent on vdevd or any device manager. A libudev-compat process receives device events by watching for new files written into a well-defined directory in a RAM-backed filesystem. Vdevd simply runs a script to fill in /run/udev and write device event files in order to communicate with libudev-compat processes. I'm happy to help test and evaluate vdev with Alpine. This document [2] contains a tutorial on how to try it out without installing, and what to send me if something breaks. We'll be making an alpha branch soon (see [3]). [0] http://judecnelson.blogspot.com/2015/01/introducing-vdev.html [1] https://github.com/jcnelson/vdev/issues/32 [2] https://github.com/jcnelson/vdev/blob/master/how-to-test.md [3] https://github.com/jcnelson/vdev/issues/33 Thanks, Jude --001a113f90482b0793051bbca2f3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi everyone,
=C2=A0
[vdev] a device manager with an approach a bit different, offers an
optional filesystem interface that implements a per-process view of
/dev. Possibly the least simple alternative, but interesting
nonetheless.


Thank you for your int= erest in vdev.=C2=A0 I am the principal developer.=C2=A0 I hope you all don= 't mind me chiming in to provide a little bit more information.

First, I can't emphasize the "optional" qua= lifier enough regarding the filesystem component vdevfs.=C2=A0 The hotplug = daemon vdevd and the libudev-compat library are meant to replace udevd and = libudev respectively; the filesystem is an add-on that can be used independ= ently of whatever device manager is running.=C2=A0 There are more detailed = write-up's on the design goals for each of the three vdev components in= [0] and [1].

Second, I would like to point out th= at vdevd by itself is not too different from mdev, nldev, and smdev.=C2=A0 = The udev-like behavior comes almost entirely from the shell scripts and aux= iliary helper programs it executes in reaction to device uevents.=C2=A0 I b= ring this up because these scripts and helper programs could easily be port= ed to mdev, nldev, and smdev simply by providing a wrapper that sets the ap= propriate environment variables (a listing can be found in Appendix A of [2= ]).

Third, I would like to point out that libudev-= compat is *not* dependent on vdevd or any device manager.=C2=A0 A libudev-c= ompat process receives device events by watching for new files written into= a well-defined directory in a RAM-backed filesystem.=C2=A0 Vdevd simply ru= ns a script to fill in /run/udev and write device event files in order to c= ommunicate with libudev-compat processes.

I'm happy to help test= and evaluate vdev with Alpine.=C2=A0 This document [2] contains a tutorial= on how to try it out without installing, and what to send me if something = breaks.=C2=A0 We'll be making an alpha branch soon (see [3]).

[0= ]=C2=A0http://judecnelson.blogspot.com/2015/01/introducing-vdev.html
= [1] https://github.c= om/jcnelson/vdev/issues/32
[2] https://github.com/jcnelson/vdev/blob/ma= ster/how-to-test.md
[3]=C2=A0https://github.com/jcnelson/vdev/issues/33

Thank= s,
Jude
--001a113f90482b0793051bbca2f3-- --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---