On Wed, 21 Mar 2012 14:17:06 -0600, Bob Proulx wrote: > Camaleón wrote: >> Wilko Fokken wrote: >> > Camaleón wrote: >> >> Open a terminal, run "dmesg | tail" and then insert the card to see >> >> what's going on. >> > >> > Should'nt it be written: >> > >> > run "dmesg | tail -f" ? >> >> I only wanted to print the last few line from dmesg, nothing >> interactive. > > The issue everyone was poking at was the order of actions.
Ah, that... true :-) > If you run "dmesg|tail" first before inserting the card then that is > before and there won't be any messages about it yet. Instead the order > would be to insert the card first and then run dmesg afterward to see > what output it produced. Sure, the order matters here. He can re-run the command again to view the new messages. > But that output may be slow to be emitted over time. I think it is > better to tail the syslog file. USB (hardware) events are dropped there? > AFAIK /var/log/syslog would would have all of the same information as > dmesg and so tail'ing with -f it would give real-time coverage of the > messages and no need to repeatedly run the dmesg command. To be sincere, I'm still unsure about what log file holds what information. In openSUSE, the main log was "/var/log/messages" and you had to look there to see the most relevant information, but here (Debian) seems to be "/var/log/syslog". Then there are additional small files for authentication, user and other stuff I never remember which is disseminated into small registries files. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jkfe20$qin$4...@dough.gmane.org
