On Saturday 23 May 2009, Roy Marples wrote:
Basically as Doug said, each OpenRC version comes with a few big
chances. Well not massive as in your box will break now, but just a
different spin on how things should work. OpenRC-0.5 will have the
biggest re-spin to date - net.lo (net.eth0 etc) is
Robert Buchholz wrote:
On Saturday 23 May 2009, Roy Marples wrote:
Basically as Doug said, each OpenRC version comes with a few big
chances. Well not massive as in your box will break now, but just a
different spin on how things should work. OpenRC-0.5 will have the
biggest re-spin to date -
Mike Auty wrote:
Roy Marples wrote:
Attached is the new conf.d/net sample.
Sorry, I missed those. Did lists.g.o remove them, or were they not
attached?
As such, a side project I've started is a new ifconfig tool
[1] to handle everything from vlans, to bridging, to bonding, to
wireless
Hi!
On Fri, 22 May 2009, Dawid Węgliński wrote:
Haven't tested it yet on my box, but i'd like to know if openrc
handles 801.2Q support.
Near as I can tell, it does (some lines shortened for brevity):
[r...@sareth ~]# eix -Ic openrc
[I] sys-apps/openrc (0.4.3...@05/15/2009): OpenRC manages
On Saturday 23 of May 2009 10:53:49 Tobias Klausmann wrote:
Hi!
On Fri, 22 May 2009, Dawid Węgliński wrote:
Haven't tested it yet on my box, but i'd like to know if openrc
handles 801.2Q support.
Near as I can tell, it does (some lines shortened for brevity):
[r...@sareth ~]# eix -Ic
Doug Goldstein wrote:
The only reason why OpenRC has not come up for stabilization by it's
maintainers is the fact that everytime there's a new version readied
for release, on the horizon there's new incompatible changes being
planned for the next version. The OpenRC maintainers in Gentoo have
Alin Năstac wrote:
Doug Goldstein wrote:
The only reason why OpenRC has not come up for stabilization by it's
maintainers is the fact that everytime there's a new version readied
for release, on the horizon there's new incompatible changes being
planned for the next version. The OpenRC
Roy Marples wrote:
One side effect of this is that daemons such was wpa_supplicant and PPP
are now init scripts proper - this is good. The only downside is that
you lose the ability to control each interface via init.d. Instead I
propose you control this via ifconfig.
Uh, so in summary any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roy Marples wrote:
Attached is the new conf.d/net sample.
Sorry, I missed those. Did lists.g.o remove them, or were they not
attached?
As such, a side project I've started is a new ifconfig tool
[1] to handle everything from vlans, to bridging,
Hi,
I'd like to collect some things we need to do before Baselayout 2 and
OpenRC can go stable. Up to now I have:
* eselect 1.1 stable (current RC3) for the support in the rc module
* a newer splashutils stable
* documentation updates (http://bugs.gentoo.org/213988, thanks Jeremy)
What else?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Faulhammer wrote:
What else? As some of you might foresee, this can be as hard as a
major GCC stabilisation, so it must be well-planned and organised.
Depends on which version of openrc gets stabilized in the process.
We're currently
On Fri, May 22, 2009 at 5:17 AM, Christian Faulhammer fa...@gentoo.org wrote:
Hi,
I'd like to collect some things we need to do before Baselayout 2 and
OpenRC can go stable. Up to now I have:
* eselect 1.1 stable (current RC3) for the support in the rc module
* a newer splashutils stable
On Fri, May 22, 2009 at 5:17 AM, Christian Faulhammer fa...@gentoo.org wrote:
Hi,
I'd like to collect some things we need to do before Baselayout 2 and
OpenRC can go stable. Up to now I have:
* eselect 1.1 stable (current RC3) for the support in the rc module
* a newer splashutils stable
On Friday 22 of May 2009 12:17:17 Christian Faulhammer wrote:
Hi,
I'd like to collect some things we need to do before Baselayout 2 and
OpenRC can go stable. Up to now I have:
* eselect 1.1 stable (current RC3) for the support in the rc module
* a newer splashutils stable
* documentation
14 matches
Mail list logo
