| 1 |
On Mon, Jun 03, 2013 at 12:35:29AM +0200, Luca Barbato wrote |
| 2 |
|
| 3 |
> - eselect init will be opt-in ***FOR THE TIME BEING***, people can |
| 4 |
> be left on their own tools if the want it |
| 5 |
|
| 6 |
This statement should bring the same reaction as the posting that udev |
| 7 |
source was being rolled into the systemd tarball. It implies that |
| 8 |
eselect init will eventually become mandatory. |
| 9 |
|
| 10 |
Your situation is a special use-case, i.e. a developer who wants to |
| 11 |
switch between a "production" init system, and a "test" init system, |
| 12 |
possibly multiple times a day. You're a developer, you know which files |
| 13 |
to change, put together your own scripts, and run them as necessary. |
| 14 |
Set up your own overlay and write your own eselect init ebuild. No |
| 15 |
problem. But why should this eventually be a part of mainstream Gentoo? |
| 16 |
|
| 17 |
BTW, I'm a bigger fan of busybox than most Gentoo users. Remember the |
| 18 |
announcement of systemd/udev tarball integration, and supposed |
| 19 |
deprecation of a separate /usr? I was the ****-disturber who started up |
| 20 |
the https://wiki.gentoo.org/wiki/Mdev wiki page on how to replace udev |
| 21 |
with mdev. I also did a page on automounting at... |
| 22 |
https://wiki.gentoo.org/wiki/Mdev/Automount_USB/automount Having said |
| 23 |
that, I don't see how busybox development justifies an additional layer |
| 24 |
of complexity for everybody's bootup. |
| 25 |
|
| 26 |
-- |
| 27 |
Walter Dnes <waltdnes@××××××××.org> |
| 28 |
I don't run "desktop environments"; I run useful applications |
Archives