Re: [Dng] vdev update and design document

2015-01-02 Thread Jude Nelson
Hi Enrico, > I dont believe ACLs are a good idea anyways. They introduce yet another > (orthogonal) dimension to the system, so heavily increase management > complexity. For example, it's hard to trace problems that way, if /dev > layout heavily depends on the calling process. I don't disagree wi

Re: [Dng] dpkg packaging problems

2015-01-02 Thread Enrico Weigelt, metux IT consult
Hi, > Did you have any luck with the packaging scripts under tools/? If you > have fpm [1] installed, just running 'make' in the tools/ directory > should generate some .debs. No. And I strongly disagree with individual source packages carrying their own dist-packaging stuff. Instead the distro'

Re: [Dng] ./debian/ and ./devuan/

2015-01-02 Thread Enrico Weigelt, metux IT consult
On 03.01.2015 02:56, Hendrik Boom wrote: > Poerhaps we should also have a ./devuan/ directory. We'd use the > ./debian/ directiry if the ./devuan/ directory were missing, but it > just might make it easier to track changes in debian, and if debian > were ever to cooperate, it might occasionally b

Re: [Dng] vdev update and design document

2015-01-02 Thread Enrico Weigelt, metux IT consult
On 02.01.2015 20:43, Jude Nelson wrote: Hi, > I should point out, the ACL criteria for matching processes do not all > have to be specified, specifically for the reason you point out. Using > the SHA256 to match the process should be a tool of last resort, useful > only when the executable's pat

Re: [Dng] NetworkManager alternative

2015-01-02 Thread Martinx - ジェームズ
> > > just to test I've cross-compiled connman and oFono with uclibc and a mix > of busybox/util-linux (with busybox init) rootfs and it works on > raspberrypi > happy forking > > m > That is AWESOME!!!:-D ___ Dng mailing list Dng@lists.dyne.org http

[Dng] ./debian/ and ./devuan/

2015-01-02 Thread Hendrik Boom
On Fri, Jan 02, 2015 at 07:05:24PM +0100, Enrico Weigelt, metux IT consult wrote: > Hi folks, > > > do we already have defined workflows for package submission ? > > I'm usually maintaining everything in git repos, where each distro > has a separate branch, which directly adds ./debian/ directo

Re: [Dng] NetworkManager alternative

2015-01-02 Thread mutek
On venerdì 2 gennaio 2015 19:50:52 CEST, Martinx - ジェームズ wrote: On 26 December 2014 at 23:55, Martinx - ジェームズ wrote: Hi! I have compiled Econnman from Enlightenment project, its is a GUI for Connman but, I still did not tested it in deep. It is hosted at my Ubuntu PPA: `ppa:martinx/enlighten

Re: [Dng] dpkg packaging problems

2015-01-02 Thread Jude Nelson
Hey Enrico, Did you have any luck with the packaging scripts under tools/? If you have fpm [1] installed, just running 'make' in the tools/ directory should generate some .debs. -Jude On Fri, Jan 2, 2015 at 12:20 PM, Enrico Weigelt, metux IT consult < enrico.weig...@gr13.net> wrote: > On 02.01

Re: [Dng] vdev update and design document

2015-01-02 Thread Jude Nelson
Hi Luke, I should point out, the ACL criteria for matching processes do not all have to be specified, specifically for the reason you point out. Using the SHA256 to match the process should be a tool of last resort, useful only when the executable's path, inode number, and PID listing commands ar

Re: [Dng] NetworkManager alternative

2015-01-02 Thread Martinx - ジェームズ
On 26 December 2014 at 23:55, Martinx - ジェームズ wrote: > Hi! > > I have compiled Econnman from Enlightenment project, its is a GUI for > Connman but, I still did not tested it in deep. > > It is hosted at my Ubuntu PPA: `ppa:martinx/enlightenment`. > > Maybe, if we stick with Enlightenment for Devu

[Dng] package submission

2015-01-02 Thread Enrico Weigelt, metux IT consult
Hi folks, do we already have defined workflows for package submission ? I'm usually maintaining everything in git repos, where each distro has a separate branch, which directly adds ./debian/ directory and all necessary changes - no additional patches etc. For example: https://github.com/metux/

Re: [Dng] dpkg packaging problems

2015-01-02 Thread Enrico Weigelt, metux IT consult
On 02.01.2015 18:12, Isaac Dunham wrote: > ls -l /lib/i386-linux-gnu/ > in my Debian partition shows all .so's except ld-2.19.so being chmod a-x. Already got an answer on debian-devel: +x is not required and should not be set (except some rare cases). The interesting question here is: why does g

Re: [Dng] dpkg packaging problems

2015-01-02 Thread Isaac Dunham
On Fri, Jan 02, 2015 at 04:52:11PM +0100, Enrico Weigelt, metux IT consult wrote: > Hi folks, > > > I'm just packaging Jude's fskit to various deb distros using > pbuilder + git-buildpackage. > > Unfortunately, the .so's loose the +x flag in the package > (while usual 'make install' is okay) -

[Dng] dpkg packaging problems

2015-01-02 Thread Enrico Weigelt, metux IT consult
Hi folks, I'm just packaging Jude's fskit to various deb distros using pbuilder + git-buildpackage. Unfortunately, the .so's loose the +x flag in the package (while usual 'make install' is okay) - it seems that some of the dh stuff drops that flag :( maybe some of you guys might have an idea ?

Re: [Dng] vdev update and design document

2015-01-02 Thread Luke Diamand
Interesting read, thanks! The ACL logic though doesn't seem quite right. Having to do SHA digests on binaries to be sure you're granting access to the right program doesn't seem correct at all. It's fragile: if the program is updated with a new version it will stop working until the ACL is up

Re: [Dng] NetworkManager alternative

2015-01-02 Thread Enrico Weigelt, metux IT consult
On 01.01.2015 22:19, Hendrik Boom wrote: >> by the way: would you guys prefer 9P or FUSE for a fs-based >> control interface ? > > You mean 9P as in Plan 9? yes, of course. cu -- Enrico Weigelt, metux IT consulting +49-151-27565287 ___ Dng mailing li

[Dng] vdev update and design document

2015-01-02 Thread Jude Nelson
Hey everyone, I just thought I'd post an update on vdev, since I'd mentioned earlier that I was shooting for packages by now. It will take a couple more days, but I'm pleased to say that the pre-alpha vdev can do the following: * populate itself with all block and char devices known to sysfs * h