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 primary job is calling me for a week long trip
i cannot postpone.
Anyway, i want to let you know the roadmap i have for the release of
On Sat, Jan 03, 2015 at 07:06:19PM +0100, Enrico Weigelt, metux IT consult
wrote:
> > and for external hosted sources the devuan gitlab project
> > will have just the debian directory and a devuan specific script similar
> > to the "watch" script used in debian.
>
> I'd strongly suggest NOT doing
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 longer present. Is this what you had in mind? If so,
Hi Enrico,
> IMHO, chroot should be sufficient for that case - at least w/ proper
> mounting. IIRC, running services in a chroot should be pretty standard
> on *BSD. Anyways, are sure, OpenBSD really has no mount namespaces ?
I'm pretty sure the standard practice in FreeBSD is to use jails instea
On 2 January 2015 at 10:58, Jude Nelson wrote:
> 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:
> Snip
>
D
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,
> better to switch to an OS that does this natively, such as, perhaps,
On 03.01.2015 07:27, Jude Nelson wrote:
Hi,
> I don't disagree with you, especially since namespacing will be
> necessary when the same device node in each session must refer to a
> different device. However, as I mentioned in an earlier email, solving
> the problem of per-process access control
On 03.01.2015 09:19, Franco Lanza wrote:
> Devuan have a workflow driven by the autobuild infrastructure based
> on gitlab + jenkins + dak
Ok, sounds good.
> and for external hosted sources the devuan gitlab project
> will have just the debian directory and a devuan specific script similar
> to
On Sat, Jan 03, 2015 at 01:27:38AM -0500, Jude Nelson wrote:
> 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 /de
I recently made the switch to wicd and haven't had any problems with it...
It will even allow for multiple interfaces (onboard/usb) with totally
independent ips' Some of you guys with more exotic setups should see
how well it works for you.
___
Dng ma
On Thu, Jan 01, 2015 at 04:29:56PM -0500, Hendrik Boom wrote:
> Minimal set of packages ... Let me hope. Does that mean we'll be able
> to point sources.list to a new repository and gradually transition from
> Debian's
> Jessie to Devuan's?
Yes, absolutely. This is one of our primary goals for
On Fri, Jan 02, 2015 at 08:56:39PM -0500, 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
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
13 matches
Mail list logo
