Your message dated Sat, 21 Apr 2012 00:52:18 +0100
with message-id <[email protected]>
and subject line Close old and unfixable sysvinit bugs
has caused the Debian Bug report #345741,
regarding Please add INIT_PROG env var to override re-exec'ing from /sbin/init
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
345741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=345741
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sysvinit
Version: 2.86.ds1-6

The "telinit u" feature can be used to re-exec /sbin/init,
useful if you've just rewritten (re-installed) /sbin/init.

However, if /sbin/init is on a read-only filesystem,
or you want to redirect init to be running from a different
filesystem because you need to umount /sbin ,
this feature is inadequate.

The attached patch causes re-exec to execute the binary
specified in the INIT_PROG environment variable if it exists,
otherwise the re-exec will be to the same place the currently
running init came from (which is the current behavior).

The INIT_PROG environment variable can be set using
the telinit -e env feature, which already exists. This is why
the INIT_ prefix was chosen -- otherwise telinit -e will reject
the environment change request.

Thanks,
--
Dana L. How  [email protected]  +1 650 804 5991 cell

Sorry about the previous submission in which I forgot
"Package:" and "Version:".

Attachment: sysvinit-2.86-initprog.patch
Description: Binary data


--- End Message ---
--- Begin Message ---
This bug is being closed as part of a cleanup of the old bug
reports in the sysvinit package, in an attempt to make it easier
to address the bug reports which actually are fixable.  Some
reasons:

- Not a bug and/or it's a patch which will not be applied
- It will not be fixed, ever for various reasons
- Problem is not fixable in sysvinit or not our responsibility
- A better solution has become available in the interim
- No activity or submitter response in over a decade or more


Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux             http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?       http://gutenprint.sourceforge.net/
   `-    GPG Public Key: 0x25BFB848   Please GPG sign your mail.


--- End Message ---
_______________________________________________
Pkg-sysvinit-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel

Reply via email to