After testing bootlogd in a VM Slackware 12.1 setup, it only logs what other daemons don't (from reading the man pages it looks like it parses kernel output looking for console= lines, which would mean that lines recorded by other daemons wouldn't be recorded by bootlogd, I would guess), but it didn't log any login information -- just up to the last console messages before the login prompt (not even the login prompt messages were shown). It's probably a good idea to kill the daemon anyway in rc.local because it doesn't need to be running after the system is fully booted (and killing it doesn't affect the existing /var/log/boot file), but it doesn't immediately appear to be a security threat. This sounds like a sound solution for the OP, but of course you'll have to look through ALL of the logs in /var/log/* since bootlogd only includes the output directly from the kernel that is not logged by anything else. Unless there's another miracle tool out there, you can't get the entire boot prompt to show up in a log file in chronological order.

I greatly appreciate the info. Thanks a bunch.

I will implement it in my system.

Why I ask the question? Well I compiled a new kernel but it seems to be running on the old kernels modules. The boot screen goes so fast that I was not able to record what was actually going on. Dmesg did not show what I was looking for.

But... That is probably a question for a new thread.

Just installed Fedora 9 and some errors (I guess) swept by during boot)
where is rc.S?

LMKIII (root) /etc/rc.d [911]>lsa
total 132
drwxr-xr-x 10 root root 4096 2008-05-16 23:34 ./
drwxr-xr-x 144 root root 12288 2008-05-16 22:34 ../
drwxr-xr-x 2 root root 4096 2008-05-16 17:26 init.d/
-rwxr-xr-x 1 root root 2848 2008-05-02 13:05 rc*
drwxr-xr-x 2 root root 4096 2008-05-16 17:24 rc0.d/
drwxr-xr-x 2 root root 4096 2008-05-16 17:24 rc1.d/
drwxr-xr-x 2 root root 4096 2008-05-16 17:24 rc2.d/
drwxr-xr-x 2 root root 4096 2008-05-16 17:24 rc3.d/
drwxr-xr-x 2 root root 4096 2008-05-16 17:24 rc4.d/
drwxr-xr-x 2 root root 4096 2008-05-16 17:24 rc5.d/
drwxr-xr-x 2 root root 4096 2008-05-16 17:24 rc6.d/
-rwxr-xr-x 1 root root 220 2008-05-02 13:05 rc.local*
-rwxr-xr-x 1 root root 24152 2008-05-02 13:05 rc.sysinit*

Just a two-center:

If you use any framebuffer video mode to boot, then the scrollback buffer is limited. I use GRUB and when I want to scroll back, I stop GRUB from booting, manually delete the VGA=788 boot option, and then continue booting. Then I am able to scroll back and read all that was sent to the console.