Bug 45981
| Summary: | Printer setup documentation: Running dmesg weeks after boot up | ||
|---|---|---|---|
| Product: | Documentation | Reporter: | Pierre-Paul Lavoie <ppl> |
| Component: | Books & Articles | Assignee: | Ceri Davies <ceri> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
State Changed From-To: open->analyzed Good idea. Responsible Changed From-To: freebsd-doc->ceri I'll take care of this. State Changed From-To: analyzed->closed I committed the change in this specific section, and also in various other places around the handbook - thanks for your submission. |
Taken from FreeBSD handbook printing section 11.3.1.2.1 (Kernel Configuration): <snip> To find out if the kernel you are currently using supports a serial interface, type: # dmesg | grep sioN </snip> If it have been a while that the operating system is boot up, original messages might have been silently discarded. As a result, the user will not get any output from the above command. Maybe `cat /var/run/dmesg.boot' should be use instead of dmesg(1)? It is uglier, but have the advantage of beeing guaranteed to work (I think). Or perhaps add a new -b(oot) option to dmesg(1) that simply echo back `dmesg.boot'. I believe that it would be a good thing to warn about this potential pitfall. Fix: Mention `cat /var/run/dmesg.boot` instead of dmesg if it have been a while that you have boot up. How-To-Repeat: Go to http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/printing-intro-setup.html#PRINTING-SIMPLE section 11.3.1.2.1 Kernel Configuration