Date: Tue, 15 Jul 2014 10:30:09 +0200 From: Oliver Pinter <oliver.pntr@gmail.com> To: =?ISO-8859-1?Q?Bruno_Lauz=E9?= <brunolauze@msn.com> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: libdevattr Message-ID: <CAPjTQNFVrDq1vUCOcW4KFaUBvvtXtpw6N5ZmTYBA8ckvt7JYYA@mail.gmail.com> In-Reply-To: <BLU179-W85BEC84BAEF68EEBADF4B8C6F60@phx.gbl>
index | next in thread | previous in thread | raw e-mail
On 7/15/14, Bruno Lauzé <brunolauze@msn.com> wrote: > I was looking at dragonfly and why they have libdevattr and we don'tI really > think having udev compatible api would open the door to a lot of software, > imho.I feel it wouldn't be so complicated to port dragonfly kern_udev, > libprop and libdevattr from dragonfly bsd. > Am i missing a point or is this in contradiction witch any of freebsd > objectives? > Let me know your thoughts... > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > In FreeBSD exists similar utility like udev, the so called devd. In github is there a project, which would improve the compatibility or completely change the udev like brain-damage. https://github.com/freebsd/libdevq Other problem with udev is, that moving so fast, and every time changed their API, and udev's future are not clear, possibly merged with systemd.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPjTQNFVrDq1vUCOcW4KFaUBvvtXtpw6N5ZmTYBA8ckvt7JYYA>