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 #272428,
regarding [BOOTLOGD] bootlogd should be started in the initrd
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.)
--
272428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=272428
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: initscripts
Version: 2.85-22
Severity: wishlist
Bug#247775 says
The reason why it isn't logged anywhere is because while we're running
in the initial ramdisk, none of the logging services have started yet.
(Arguably we could start bootlogd in the initrd, which would allow us
to capture messages during the initial ramdisk --- but them the memory
taken by the initial ramdisk wouldn't be released until the bootlogd
had been killed. If you think this is worthwhile, please file a
wishlist bug against initscripts package.)
I say:
OK, done.
Well, all this is over my head, which has hairs torn out due to trying
to copy things as they flit by even though this is already the 21st
century.
Just for sport, have a
****************
WORRISOME MESSAGE: .... ....
****************
that isn't logged and flies off one's home's only monitor and see how
many users 1. even notice it, as they thought things like that would
be in the logs where they look for them. 2. are able to read and copy
it down with pencil before it leaves the screen.
Anyway,
DESCRIPTION
Bootlogd runs in the background and copies all strings sent to the
/dev/console device to a logfile.
So the job description is clear, "all strings".
--- 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
