| 1 |
On Fri, Jun 21, 2013 at 04:39:59AM +0200, Michał Górny wrote: |
| 2 |
> Dnia 2013-06-20, o godz. 15:56:09 |
| 3 |
> William Hubbs <williamh@g.o> napisał(a): |
| 4 |
> |
| 5 |
> > On Thu, Jun 20, 2013 at 12:16:36PM +0200, Fabio Erculiani wrote: |
| 6 |
> > > There is a new version of eselect-init in the systemd-love overlay to play with. |
| 7 |
> > > The new version saw the following major changes: |
| 8 |
> > > |
| 9 |
> > > - the /sbin/init (aka the symlink that eselect-init handles) can be |
| 10 |
> > > changed to whatever one wants through make.conf [1] (this is a compile |
| 11 |
> > > time option, as documented in the eclass) |
| 12 |
> > |
| 13 |
> > Why do we need to mess with /sbin/init at all? |
| 14 |
> |
| 15 |
> Yes, we do because we don't want sysvinit randomly getting run |
| 16 |
> as fallback and messing with our systems. |
| 17 |
|
| 18 |
I don't understand what you are saying here. |
| 19 |
|
| 20 |
If eselect-init installs the wrapper as /sbin/einit, we don't have to |
| 21 |
touch /sbin/init at all, then, the only thing someone would have to do |
| 22 |
is to add an entry to their boot loader with init=/sbin/einit on the kcl |
| 23 |
to use it. |
| 24 |
|
| 25 |
> > I like the suggestion that came up here on the list a while back, have |
| 26 |
> > the eselect init module install its own symlink at, say, /sbin/einit. |
| 27 |
> > You would still have to have the user edit their boot loader |
| 28 |
> > configuration file one time if they want to use this, but this makes it |
| 29 |
> > completely opt-in. |
| 30 |
> |
| 31 |
> Plus hacking kernel sources to disable /sbin/init fallback. |
| 32 |
|
| 33 |
No, there is no reason we would have to hack anything in the kernel |
| 34 |
sources. |
| 35 |
|
| 36 |
William |
Archives