Strange text in all terminal/virtual terminals/boot.
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Strange text in all terminal/virtual terminals/boot.
WHen i go into some form of terminal the virtual ones or if i exit x server this text comes up constantly and keeps scrolling down the screen in an extremely annoying way, stopping me from what I'm doing, any ideas what it is and how to get rid of it?
any ideas what it is and how to get rid of it?
You are running a GNU/Linux release that runs "SELinux" (which is a good thing). These "audit" messages tell you something is wrong (that should and can be corrected). As with most things GNU/Linux there's more than one way:
- the easiest and most fault-tolerant way is to "touch /.autorelabel" as root account user and then reboot. At reboot the filesystem will be relabeled and these messages should not show again,
- the second way would be to run "fixfiles relabel" as root account user. Doing that you don't have to reboot, but you will find the process deletes all your files in /tmp which might cause unexpected results (slight understatement),
- finally you can run "audit2allow" on the log containing your audit messages and load the resulting rules. This you should never have to do in "default" situations and I wouldn't recommend it for you.
A word about the messages in your console. The fact you see those messages is good since you get to see them and have to chance to act on or ignore them (let's not). If the messages bother you and you do read the systems logs regularly, you can set "dmesg -n i" in your ~/.bashrc (i being a single digit, range 1-8 IIRC, usually "4" should do) to make them disappear from the screen. They still will be written to the logs.
//Please ask the moderator(s) of this forum to move this thread to the "Linux kernel" or "Linux general" or your distro's forum where it belongs, it's not a hardware issue.
Ok, well i tried the first method "touch /.autorelabel", rebooted, and it relabelled, now i have more problems, i have a startup message that says something like "Starting System Message Bus, Unknown group 'netdev' in System....."
Also i get more of the terminal commands, funnily they all contain "net" or "dev" as "name='net'" or "name='dev'".
I will not try the second and third method yet but if you could give a suggestion, i have attached the exact dmesg output. Thanks
i have a startup message that says something like "Starting System Message Bus, Unknown group 'netdev' in System....."
Can you return the *exact* message? What does "getent passwd netdev" return? If nothing, any idea how it got deleted? Did you by any chance do some "tweaking"? Like removing accounts you though not necessary?
Could this be to do with the fact i installed with noapic and removed that kernel param only after i found a BIOS upgrade would fix that problem?
"Noapic" is a switch that influences how the kernel will treat APIC, I very much doubt it would influence SELinux behaviour.
Would a fresh install help or is their an easier fix?
Two ways: or "fixfiles relabel" or remove and reinstall Irqbalance and how that does the trick. "fixfiles relabel" *is* destructive in the sense it *completely* relabels the system, so better save /tmp contents you want to keep elsewhere and "telinit 1" (drop to runlevel 1) before you do. Removing and reinstalling Irqbalance "just doesn't seem right" in that you should not need to remove+reinstall apps to fix SELinux problems.
P.S. To the mods
Heh, no, that doesn't work. Report this thread using the "report" button under your OP and ask for a move.
I'm back in doze due to a problem atm but, No, i didn't tweak anything, I just upgraded all my packages through the automatic upgrade thing, I also did a fresh install afterwards, the netdev seemed to be a group that was created in the message bus config file, i commented out the section to do with that group and i no longer see the boot message.
The exact message is:
Unknown group 'netdev' in message bus configuration file.
Some other people seem to have had the same problem and it is definitly due to an update: HERE
Some seem to have solved it by adding the group netdev ..... I however just commented it out of my message bus config file.
Probably not hte best solution but it works for the moment, I'm just trying to iron out half a dozen other problems before my sysem becomes useable.
I don't think this has to do with UNI or SMP. Another way to realign the system would be to have "audit2allow" extract custom rules from your log containing avc errors and add those rules to your SELinux ruleset. FC has some nice docs using audit2allow IIGC.