On Saturday 14 March 2009, Charles Atkinson wrote:
> I expected this change to cause some breakage; perhaps bootlogd depended
> on something set by the earlier boot scripts; why would the package
> designers not start it right at the beginning of the boot process so it
> could capture all the boot messages?
It may work or not depending on the system. The program uses
pseudo-terminals (PTYs). If you have BSD PTYs compiled in the kernel
and have static pty* devices in your root filesystem, then yes,
it should be possible to run bootlogd right from the beginning
(perhaps even from the initial ramdisk). If not, you have to wait until
/dev/pts is mounted by S11mountdevsubfs.sh.
On Saturday 14 March 2009, Charles Atkinson wrote:
> I expected this change to cause some breakage; perhaps bootlogd depended
> on something set by the earlier boot scripts; why would the package
> designers not start it right at the beginning of the boot process so it
> could capture all the boot messages?
It may work or not depending on the system. The program uses s.sh.
pseudo-terminals (PTYs). If you have BSD PTYs compiled in the kernel
and have static pty* devices in your root filesystem, then yes,
it should be possible to run bootlogd right from the beginning
(perhaps even from the initial ramdisk). If not, you have to wait until
/dev/pts is mounted by S11mountdevsubf
Best regards,
Sergei