Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi every one, here is my problem:
my X doesn't work and i do things in cli, when i'm trying to bring up my wireless card , its driver start send all its messages to all vt's\tty's in the same time, i suppose it's normal but it doesn't let me type another commands....
I know the proper way to redirect command output , but apparently this is not the case....
i would be happy if someone gave me tips how to deal with CLI without X in particular situation and in general..
If it's the driver that's printing the messages, then they're probably coming from the kernel. You shouldn't lose your shell unless the system panics or something disastrous like that happens. But you will lose your prompt when a message from the kernel gets written to the screen (because the shell isn't aware that something else wrote a message to the terminal, the shell doesn't know that it has to re-print the prompt). If hitting enter a few times doesn't get your prompt back, something else is wrong. Maybe the program you're running to enable the wireless device is actually hanging, so the shell never gets to continue execution. In Linux, I don't know; but in BSD only one VT (called the "console") actually gets kernel messages, while the rest stay clean. If the problem is that kernel messages get written to all VTs, there's probably some way you can change that in your system's terminal configuration file. For a guess, it's /etc/ttys on BSD.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.