| 1 |
On Wed, May 29, 2013 at 09:56:00PM +0200, Tom Wijsman wrote |
| 2 |
|
| 3 |
> "Walter Dnes" <waltdnes@××××××××.org> wrote: |
| 4 |
> |
| 5 |
> > In order for a different init system to come up, some file(s) |
| 6 |
> > somewhere *MUST* be different, no ifs/ands/ors/buts. |
| 7 |
> |
| 8 |
> How true is this in general? It is usually only a change of the init |
| 9 |
> parameter. |
| 10 |
|
| 11 |
Where is the init parameter changed? Even if it's only the "append" |
| 12 |
line in /etc/lilo.conf, my above statement still holds true. If you've |
| 13 |
got two identical machines with byte-identical hard drives, they can not |
| 14 |
boot two different OS's or init systems. |
| 15 |
|
| 16 |
> > The problem with an eselect approach is that it's like asking a brain |
| 17 |
> > surgeon to operate on himself. |
| 18 |
> |
| 19 |
> eselect and wrappers don't operate on themselves, please elaborate. |
| 20 |
|
| 21 |
The operating system is changing itself. |
| 22 |
|
| 23 |
> > [SNIP to shorten mail] |
| 24 |
> |
| 25 |
> Users can already do this, this isn't a solution. |
| 26 |
|
| 27 |
> > [SNIP to shorten mail] |
| 28 |
> |
| 29 |
> Again: Users can already do this, this isn't a solution. See above... |
| 30 |
|
| 31 |
If users can already do it themselves, then why this entire thread? |
| 32 |
Why do we need eselect/whatever? |
| 33 |
|
| 34 |
-- |
| 35 |
Walter Dnes <waltdnes@××××××××.org> |
| 36 |
I don't run "desktop environments"; I run useful applications |
Archives