corruption in serial boot log

I'm getting some corrupted text in the empeg's boot-time serial output. It's very localized, reproducible, and apparently unchanging. It looks like this:

empeg-pump v0.03 (19980601)

Press Ctrl-A to enter pump...ta=U9QtpI==QtaQx%1tMeMQt5Itp=91echange_root: old root has d_count=1

~{^=U95=U9Q=1pI==Qokay

Freeing unused kernel memory: 4k

Some of those are 8-bit characters that won't show up properly here, I'm afraid, but you get the idea.

Is anyone else seeing this? I don't know if it's normal or if it's something I've done during my serial uploader development.

I seem to recall that this happens whenever the player changes serial port speeds. Which it does sometimes depending on settings and circumstances. I could be wrong...

But I see it sometimes, too, so you're not alone.

Let me restate. Since I've upgraded to 2.0 (I think), it seems to happen every time. I remember seeing once or twice before, but never this often.

Here's what I get with v2.00final installed, after a fresh power-on:

VFS: Mounted root (ext2 filesystem).

empeg-pump v0.03 (19980601)

Press Ctrl-A to enter pump...VFS: Mounted root (ext2 filesystem) readonly.

change_root: old root has d_count=1

Trying to unmount old root ... Freeing unused kernel memory: 4k initempeg init 0.8

I see this is a developer image!

Mounting proc

Mounting first music partition

..

And why aren't the [ pre ] tags working here?

And why aren't the [ pre ] tags working here?

Yeah, that's a pain. And I don't like the double spacing on the [ code ] tag either. It's ok for a very small snippet, but useless for anything longer.

What I really want is a [ code=x ] tag where x can be any of {perl, php, c, sh, java, ...}, that will color and space syntactically.

Yeah, that's a pain. And I don't like the double spacing on the [ code ] tag either. It's ok for a very small snippet, but useless for anything longer.

The problem here is that the backend is replacing all linefeeds with <BR> tags, thus creating the doublespace issue. I remember looking at it when I added the [q] tags, and decided it was too much of a pain to fix at the time. I am going to do some limited testing hopefully in the next few weeks to migrate the BBS to the 6.x codebase.

What I really want is a [ code=x ] tag where x can be any of {perl, php, c, sh, java, ...}, that will color and space syntactically.

I'll adopt Mark's policy on Hijack addons here. Send me the code, and I'll look at implementing it

Mmm.. must be that GPL viral effect that billg used to rant about..