I just finished up a LFS systemd build. It all works great except the kernel console messages overwriting the console prompt. I can stop it by typing dmesg -n 1 but I'm looking for a solution to disable them altogether on startup.

Prior to doing a systemd build of LFS, I had done a systemv build which did not have this issue.

Does anyone happen to know how to do that?

Yeah, if you go lfs you use sysvinit. Otherwise what's the point? If you do want to go hardcore, you'd need to figure out why it's using tty1 as console, which is ultimately the reason why it does so. It's still linux after all. In a way.

Apparently you miss the point of Linux and open source altogether. And that point is freedom...and choices.

Thanks for the tip.

How is it only Linux "in a way"?

I do, it's obviously your own choice to abandon certain freedoms using systemd
What I don't get is are ALL severities of messages get printed or only certain critical ones? Maybe you can try telling the kernel to use a certain console=X?

A minor annoyance of systemd that I never looked into. I'm sure it's easy enough to find on goog. A systemd/kernel cmd line tweak or such. Maybe ask in lfs-support mail. Doubt Doug the sysd dev even knows it happens. Sysvinit is nasty crusty slow old.....vs sysd but I digress. Tinfoil is afraid the PTB will soon confiscate his sysv build. Gimme that....too much freedom! ;p

Thanks to tinfoil3d...

On the Raspberry Pi, kernel command line options are passed to the kernel through a file on the boot partition named cmdline.text. I had copied the entire /boot directory (kernel images, firmware files, config.txt and cmdline.txt) from a working Raspbian distribution. console=tty1 is one of Raspbian's default kernel command line options.

I did a complete LFS rebuild and finished it this morning. After copying the /boot files from the working Raspbian distro, I edited cmdline.txt by taking out console=tty1. This build booted right up with no kernel console messages at all.

The thing I find interesting is that Raspbian boots with console=tty1 on the kernel command line, yet Raspbian does not show continuous kernel console logging so they must be suppressing it after the boot sequence in a config file somewhere.

Don't know if its the same with systemd but for sysv I had to add 'kernel.printk = 3 4 1 3' to /etc/sysctl.conf to stop iptables flooding the console with messages ( pi4 )