Re: [Dng] vdev update and design document

2015-01-04 Thread Enrico Weigelt, metux IT consult
On 03.01.2015 15:24, Hendrik Boom wrote: > It looks as if this whole discussion is in the direction of building > a capability architecture on top of Linux. I wouldn't call that capabilities - that, IMHO, is an entirely orthogonal concept. (one which I don't particularily like). Instead I'm attem

Re: [Dng] vdev update and design document

2015-01-04 Thread Enrico Weigelt, metux IT consult
On 03.01.2015 23:07, Jude Nelson wrote: > Hi Aldemir, > > That sounds like a good idea--give the Linux port the option to exit > once it processes all devices from sysfs. If run again by root > manually, it will "patch" /dev by adding new nodes for new devices and > remove nodes for devices no lo

Re: [Dng] package submission

2015-01-04 Thread Enrico Weigelt, metux IT consult
On 04.01.2015 06:45, Franco Lanza wrote: > The idea is to have that for release branches but not for master so we > can easily integrate new upstream releases, rebase. > considering not all sources are on an (external) git repo and we cannot > just merge changes on every new upstream release J

Re: [Dng] package submission

2015-01-04 Thread Franco Lanza
> But still, I'm not convinced at all on tarballs. Instead I'd set up an > automatic vcs mirror/import infrastructure. Already did that about > a decade ago (called the OSS-QM project - maybe some old maillist > archives still have some bits about it ;-)). It's not a big deal. > > Well, as i ca

Re: [Dng] vdev update and design document

2015-01-04 Thread Hendrik Boom
On Sat, Jan 03, 2015 at 07:31:19PM +0100, Enrico Weigelt, metux IT consult wrote: > On 03.01.2015 07:27, Jude Nelson wrote: > > >> I'd rather raise the question whether that's useful at all. > > > > There was an LWN article on this a while back [2]. The examples > > provided there are as follow

Re: [Dng] vdev update and design document

2015-01-04 Thread Hendrik Boom
On Sat, Jan 03, 2015 at 04:01:55PM -0500, Jude Nelson wrote: > Hi Hendrik, > > > It looks as if this whole discussion is in the direction of building a > > capability architecture on top of Linux. I'm not sure this isn't a > > much greater change than imposing systemd. If you want such a thing,

Re: [Dng] Release roadmap

2015-01-04 Thread Go Linux
On Sun, 1/4/15, Franco Lanza wrote: Subject: [Dng] Release roadmap To: dng@lists.dyne.org Date: Sunday, January 4, 2015, 12:03 AM As many already known, i will be unreliable next week, and this will cause a little bit of slow down in the package repository population. Sorry for that, but my

Re: [Dng] Release roadmap

2015-01-04 Thread Dima Krasner
Indeed, it's a good way forward for now. Once everything is in place, I'll start playing with rebuilding GDM without tons of dependencies, to ease the debugging of LoginKit. Once I can debug GDM on a Devuan system with sysvinit and a barebones build of GDM with debugging symbols, things will be

Re: [Dng] Release roadmap

2015-01-04 Thread Hendrik Boom
On Sun, Jan 04, 2015 at 09:22:52PM +0200, Dima Krasner wrote: > Indeed, it's a good way forward for now. > > Once everything is in place, I'll start playing with rebuilding GDM > without tons of dependencies, to ease the debugging of LoginKit. Once > I can debug GDM on a Devuan system with sysvi

Re: [Dng] Release roadmap

2015-01-04 Thread Dima Krasner
Don't get me started ;) Yes, when built against systemd, both GDM and LightDM depend on it quite heavily, both directly and via stuff like AccountsService, D-Bus, gnome-session, gnome-shell and whatever. Just take a look at the code - lots of LOGIND_RUNNING() all over. It's extremely hard to is

Re: [Dng] vdev update and design document

2015-01-04 Thread Jude Nelson
Hi Enrico, I think vdev can support this while keeping a consistent design. vdev would have two Linux-specific back-ends--one that listens for netlink packets and forwards them to the rest of vdev (the one slated for alpha release), and one that simply exits once it all of the initial requests ge

Re: [Dng] vdev update and design document

2015-01-04 Thread Jude Nelson
Hi Hendrik, > In VAX/VMS there was a feature that could in theory be useful, > though I've never seen it actually used. Fila permissions could > forbid the root user from reading the file. This might be useful > for dire secrets. Even the sysadmin couldn't back up that file. I think for some a

Re: [Dng] Release roadmap

2015-01-04 Thread Adam Borowski
On Sun, Jan 04, 2015 at 09:52:18PM +0200, Dima Krasner wrote: > Yes, when built against systemd, both GDM and LightDM depend on it quite > heavily, both directly and via stuff like AccountsService, D-Bus, > gnome-session, gnome-shell and whatever. Just take a look at the code - > lots of LOGIND_RU

Re: [Dng] vdev update and design document

2015-01-04 Thread Enrico Weigelt, metux IT consult
On 05.01.2015 00:40, Jude Nelson wrote: Hi >> In VAX/VMS there was a feature that could in theory be useful, >> though I've never seen it actually used. Fila permissions could >> forbid the root user from reading the file. This might be useful >> for dire secrets. Even the sysadmin couldn't ba

Re: [Dng] Release roadmap

2015-01-04 Thread Enrico Weigelt, metux IT consult
On 04.01.2015 20:52, Dima Krasner wrote: > Yes, when built against systemd, both GDM and LightDM depend on it > quite heavily, both directly and via stuff like AccountsService, > D-Bus, gnome-session, gnome-shell and whatever. Just take a look at > the code - lots of LOGIND_RUNNING() all over. It'

Re: [Dng] vdev update and design document

2015-01-04 Thread Martijn Dekkers
On 5 January 2015 at 07:47, Enrico Weigelt, metux IT consult < enrico.weig...@gr13.net> wrote: > On 05.01.2015 00:40, Jude Nelson wrote: > > >> In VAX/VMS there was a feature that could in theory be useful, > >> though I've never seen it actually used. Fila permissions could > >> forbid the root