I'm supporting all your effort to improve our boot process.
Arch was famous for its single rc.conf file configuration that now
seems to fade away. While this may be done for good technical reasons I
suggest to bring this up to some central point (hotplug/udev or
systemd list ). I'd like to see
On 22 July 2012 16:14, Andreas Radke andy...@archlinux.org wrote:
I'm supporting all your effort to improve our boot process.
Arch was famous for its single rc.conf file configuration that now
seems to fade away. While this may be done for good technical reasons I
suggest to bring this up to
On Sat, Jul 21, 2012 at 2:52 AM, Tom Gundersen t...@jklm.no wrote:
[..]
* All variables in rc.conf can now be left unset and will default to
something sensible
I find removing most of the variables to be confusing and would
suggest that [1] and [2] get reverted.
The commit log for [1] lists
Am 21.07.2012 08:48, schrieb Evangelos Foutras:
On Sat, Jul 21, 2012 at 2:52 AM, Tom Gundersen t...@jklm.no wrote:
[..]
* All variables in rc.conf can now be left unset and will default to
something sensible
I find removing most of the variables to be confusing and would
suggest that [1] and
On Jul 21, 2012 8:49 AM, Evangelos Foutras evange...@foutrelis.com
wrote:
On Sat, Jul 21, 2012 at 2:52 AM, Tom Gundersen t...@jklm.no wrote:
[..]
* All variables in rc.conf can now be left unset and will default to
something sensible
I find removing most of the variables to be confusing
On Jul 21, 2012 9:46 AM, Tobias Powalowski
tobias.powalow...@googlemail.com wrote:
Am 21.07.2012 08:48, schrieb Evangelos Foutras:
On Sat, Jul 21, 2012 at 2:52 AM, Tom Gundersen t...@jklm.no wrote:
[..]
* All variables in rc.conf can now be left unset and will default to
something
On Sat, Jul 21, 2012 at 8:48 AM, Evangelos Foutras
evange...@foutrelis.com wrote:
I find removing most of the variables to be confusing and would
suggest that [1] and [2] get reverted.
I'm not going to revert them outright, but we can discuss individual
options (some clearly must go, others are
On 07/21/2012 12:51 PM, Tom Gundersen wrote:
On Sat, Jul 21, 2012 at 8:48 AM, Evangelos Foutras
evange...@foutrelis.com wrote:
I find removing most of the variables to be confusing and would
suggest that [1] and [2] get reverted.
I'm not going to revert them outright, but we can discuss
Am 21.07.2012 23:28, schrieb Ionut Biru:
I pretty much hate everything you have described here.
We started from a simple and elegant, single file configuration to over
9k(not to mention that i have no freaking idea which one to edit)
Bring back the old rc.conf until we are switching to
On 07/22/2012 12:40 AM, Pierre Schmitz wrote:
Am 21.07.2012 23:28, schrieb Ionut Biru:
I pretty much hate everything you have described here.
We started from a simple and elegant, single file configuration to over
9k(not to mention that i have no freaking idea which one to edit)
Bring back
On Sat, Jul 21, 2012 at 11:28 PM, Ionut Biru ib...@archlinux.org wrote:
I pretty much hate everything you have described here.
We started from a simple and elegant, single file configuration to over
9k
Before rejecting everything, please explain why the problems I
outlined are not real?
(not
On 07/22/2012 01:01 AM, Tom Gundersen wrote:
On Sat, Jul 21, 2012 at 11:28 PM, Ionut Biru ib...@archlinux.org wrote:
I pretty much hate everything you have described here.
We started from a simple and elegant, single file configuration to over
9k
Before rejecting everything, please explain
On Sun, Jul 22, 2012 at 12:09 AM, Ionut Biru ib...@archlinux.org wrote:
The only logic i can see is that you want to force existing users to
move to this awesome configurations schema but in the same time you
say don't do it because your old rc.conf still works
I want to give the best possible
What we need is someone to write a daemon that monitors rc.conf for
changes and then write them to the appropriate configuration file. Also
the opposite needs monitored, so when the separate configurations files
are changed (probably by GUI stuff), the changes are made back to rc.conf.
(That was
14 matches
Mail list logo