Re: Boot-Log[Solved] WAS: Re: 3 Kernel-Fragen
Am Montag, 2. August 2004 13:42 schrieb Andreas Janssen: Hallo Patrick C.D. ([EMAIL PROTECTED]) wrote: 2.) Gibt es die Möglichkeit eine Boot-Log zu bekommen (bei SuSE war das glaube ich /var/log/boot.msg)? Gibt es vllt einen Deamon, der das übernehmen kann, oder etwas in der Art? In Sarge und Sid gibt es so ein Programm. Du mußt in /etc/default/bootlogd die Opion BOOTLOGD_ENABLE auf YES setzen. Danke, klappt.. :) -- [EMAIL PROTECTED]:~ less teachers [EMAIL PROTECTED]:~ cd /pub [EMAIL PROTECTED]:~ more beer
Re: Console is screwy (shows what looks like boot log)
I have added the following line Xfree86.config Option UseFBDev true and at boot prompt added vga=normal and it seems to have worked at least for now g -- I predict future happiness for Americans if they can prevent the government from wasting the labors of the people under the pretense of taking care of them. -Thomas Jefferson
Re: Console is screwy (shows what looks like boot log)
On Thu, Mar 18, 2004 at 10:40:13PM -0600, Brad Sims wrote: On Thursday 18 March 2004 9:50 pm, Paul Johnson wrote: From what I've noticed, some video cards just plain don't like switching between graphical and text modes and pretty much just crash while switching modes. Hrm, weird... I never had any problems with SuSE 7.3 doing this... (same hw) and its fine for a little while after boot... (never actually timed it to see how long it takes). Video card is a stately Raedon QD (ie no blazing screamer) But it is perfectly supported by XFree and I don't need no steenking drivers g -- I have a radeon 9800. With the ati binaries it does work perfectly from X to console, switches back and forth, can change resolution, etc. I am using sid, so, the presence of the xlibmesa in fireglx was causing a lot of trouble for me. So I decided to switch to vesa (the only that worked) and removed the ati binaries. I gave up the possibility of switching back and forth (console - X), the possiblity of changing resolution, I got a shifted screen and a somewhat flickering screen. But my system doesn't break or require manual intervention every two days now. I wonder if there are any good cards left that are truly open to open source. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Console is screwy (shows what looks like boot log)
Brad Sims [EMAIL PROTECTED] writes: My virtual consoles (ie F1-whatever) after a short period will go screwy and show what looks like boot logs or multi-color flashing garbage... I tried /c and even the reset command to no avail... They are fine after a hardware reboot but this is annoying... SSH works just fine, as does XFree86. I am running Debian Sid with latest everything g Any ideas? 'Cause I am fresh out... Maybe you are having the same problem as I, does it happens after a while during the bootup process? I'm beginning to suspect it was a recent kernel upgrade. Cheers, Jorge -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Console is screwy (shows what looks like boot log)
Hello Brad Sims ([EMAIL PROTECTED]) wrote: My virtual consoles (ie F1-whatever) after a short period will go screwy and show what looks like boot logs or multi-color flashing garbage... I tried /c and even the reset command to no avail... They are fine after a hardware reboot but this is annoying... SSH works just fine, as does XFree86. I am running Debian Sid with latest everything g Any ideas? 'Cause I am fresh out... Do you use any framebuffer driver? I had the same problem switching from XFree to a console using rivafb. Vesafb of plain text mode work best regards Andreas Janssen -- Andreas Janssen [EMAIL PROTECTED] PGP-Key-ID: 0xDC801674 Registered Linux User #267976 http://www.andreas-janssen.de/debian-tipps.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Console is screwy (shows what looks like boot log)
Andreas Janssen [EMAIL PROTECTED] writes: Hello Brad Sims ([EMAIL PROTECTED]) wrote: My virtual consoles (ie F1-whatever) after a short period will go screwy and show what looks like boot logs or multi-color flashing garbage... I tried /c and even the reset command to no avail... They are fine after a hardware reboot but this is annoying... SSH works just fine, as does XFree86. I am running Debian Sid with latest everything g Any ideas? 'Cause I am fresh out... Do you use any framebuffer driver? I had the same problem switching from XFree to a console using rivafb. Vesafb of plain text mode work Hello, I'm having a similar problem and I would like to know how do I get the kernel to use vesafb or plain text mode. TIA, Jorge -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Console is screwy (shows what looks like boot log)
Hello Jorge Santos ([EMAIL PROTECTED]) wrote: Andreas Janssen [EMAIL PROTECTED] writes: Brad Sims ([EMAIL PROTECTED]) wrote: My virtual consoles (ie F1-whatever) after a short period will go screwy and show what looks like boot logs or multi-color flashing garbage... I tried /c and even the reset command to no avail... They are fine after a hardware reboot but this is annoying... SSH works just fine, as does XFree86. Do you use any framebuffer driver? I had the same problem switching from XFree to a console using rivafb. Vesafb of plain text mode work Hello, I'm having a similar problem and I would like to know how do I get the kernel to use vesafb or plain text mode. To use the vesafb driver, it has to be compiled into the kernel (the normal Debian 2.4 kernel packages from Woody except bf2.4 don't support that), and you have to select a mode using the vga parameter in your boot loader configuration. Read the Framebuffer Howto (package doc-linux-html) to learn more about it. To use plain text mode, set the vga parameter to normal (vga=normal). In some cases you excplicitly have to switch off the vga16 framebuffer driver. Add video=vga16:off to the append line in your boot loader configuration. best regards Andreas Janssen -- Andreas Janssen [EMAIL PROTECTED] PGP-Key-ID: 0xDC801674 Registered Linux User #267976 http://www.andreas-janssen.de/debian-tipps.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Console is screwy (shows what looks like boot log)
On Friday 19 March 2004 10:11 am, Andreas Janssen wrote: Do you use any framebuffer driver? I had the same problem switching from XFree to a console using rivafb. Vesafb of plain text mode work Hrm how do I tell what framebuffer I am using? I have the following line commented out in Xfree86.config #Option UseFBDev true I am gonna readd that line and see what hapens g -- I predict future happiness for Americans if they can prevent the government from wasting the labors of the people under the pretense of taking care of them. -Thomas Jefferson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Console is screwy (shows what looks like boot log)
Hrm, I rebooted and added the phrase vga=normal and uncommented the line in config about Option UseFBDev true... We'll see if that fixed it g It's nice to know I wasn't the only one with that problem g -- I predict future happiness for Americans if they can prevent the government from wasting the labors of the people under the pretense of taking care of them. -Thomas Jefferson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Console is screwy (shows what looks like boot log)
My virtual consoles (ie F1-whatever) after a short period will go screwy and show what looks like boot logs or multi-color flashing garbage... I tried /c and even the reset command to no avail... They are fine after a hardware reboot but this is annoying... SSH works just fine, as does XFree86. I am running Debian Sid with latest everything g Any ideas? 'Cause I am fresh out... -- If Washington fears honest citizens armed at their own expense and desire, then Washington should. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Console is screwy (shows what looks like boot log)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brad Sims [EMAIL PROTECTED] writes: My virtual consoles (ie F1-whatever) after a short period will go screwy and show what looks like boot logs or multi-color flashing garbage... I tried /c and even the reset command to no avail... They are fine after a hardware reboot but this is annoying... SSH works just fine, as does XFree86. - From what I've noticed, some video cards just plain don't like switching between graphical and text modes and pretty much just crash while switching modes. - -- .''`. Paul Johnson [EMAIL PROTECTED] : :' : `. `'` proud Debian admin and user `- Debian. Because it *must* work. debian.org aboutdebian.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAWm31UzgNqloQMwcRAuBUAJ93mpqOamnmywfPT6MHlaTot5DNZwCgvzYf ePc9+5qASwaAfB7Cta8EAOo= =udCH -END PGP SIGNATURE-
Re: Console is screwy (shows what looks like boot log)
On Thursday 18 March 2004 9:50 pm, Paul Johnson wrote: From what I've noticed, some video cards just plain don't like switching between graphical and text modes and pretty much just crash while switching modes. Hrm, weird... I never had any problems with SuSE 7.3 doing this... (same hw) and its fine for a little while after boot... (never actually timed it to see how long it takes). Video card is a stately Raedon QD (ie no blazing screamer) But it is perfectly supported by XFree and I don't need no steenking drivers g -- Conquerors do not apologize; the dead never complain. -- Uncle Al -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: empty boot log
Florian Ernst wrote: Hello Peter! On Tue, Jan 06, 2004 at 07:49:44PM -0500, Peter McAlpine wrote: On Tue, 2004-01-06 at 19:01, Hugo Vanwoerkom wrote: I no longer have a /var/log/boot although I remember having one, what does its presence depend on? Hugo. [19:[EMAIL PROTECTED]:~$ dpkg -S /var/log/boot dpkg: /var/log/boot not found. oh. Maybe when I dist-upgraded to unstable it changed. What do you suppose the method used to log my boot msgs is now? /var/log/boot is created by bootlogd from initscripts / sysvinit, but recently (since 2.85-8) this logging is turned off by default, see the changelogs for details. You can turn it on again by editing /etc/default/bootlogd. HTH, Fl o None of that exists in Woody 3.0r1. And you cannot use apt-file with CD's. So a possibility is changing sources.list to Woody, getting rid of the CD entries, doing an update and then using apt-file and then putting everything back again. A lot of work to find out where bootlogd went ;-) Hugo. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: empty boot log
Hello Hugo! - bootlogd... On Wed, Jan 07, 2004 at 07:59:14AM -0600, Hugo Vanwoerkom wrote: None of that exists in Woody 3.0r1. And you cannot use apt-file with CD's. So a possibility is changing sources.list to Woody, getting rid of the CD entries, doing an update and then using apt-file and then putting everything back again. A lot of work to find out where bootlogd went ;-) $ wget http://ftp.de.debian.org/debian/dists/Debian3.0r2/Contents-i386.gz [...] $ zgrep -e bootlogd Contents-i386.gz usr/share/doc/sysvinit/examples/bootlogdbase/sysvinit $ Only this 'example'-script and no /sbin/bootlogd in Woody? Strange... But a short quote from /usr/share/doc/sysvinit/examples/bootlogd/README |Some of them are not really examples but I had to stuff some |default scripts somewhere.. OK, I cannot tell where the bootlogd you had came from, sorry... Cheers, Flo signature.asc Description: Digital signature
Re: empty boot log
Florian Ernst wrote: Hello Hugo! - bootlogd... On Wed, Jan 07, 2004 at 07:59:14AM -0600, Hugo Vanwoerkom wrote: None of that exists in Woody 3.0r1. And you cannot use apt-file with CD's. So a possibility is changing sources.list to Woody, getting rid of the CD entries, doing an update and then using apt-file and then putting everything back again. A lot of work to find out where bootlogd went ;-) $ wget http://ftp.de.debian.org/debian/dists/Debian3.0r2/Contents-i386.gz [...] $ zgrep -e bootlogd Contents-i386.gz usr/share/doc/sysvinit/examples/bootlogdbase/sysvinit $ Only this 'example'-script and no /sbin/bootlogd in Woody? Strange... But a short quote from /usr/share/doc/sysvinit/examples/bootlogd/README |Some of them are not really examples but I had to stuff some |default scripts somewhere.. OK, I cannot tell where the bootlogd you had came from, sorry... Cheers, Flo I found the contents file in CD#1 so you don't need apt-file like you showed. And no /sbin/bootlogd, so there is no bootlogd in woody apparently... Thanks for your help. Hugo. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: empty boot log
In article [EMAIL PROTECTED], Hugo Vanwoerkom [EMAIL PROTECTED] wrote: None of that exists in Woody 3.0r1. And you cannot use apt-file with CD's. So a possibility is changing sources.list to Woody, getting rid of the CD entries, doing an update and then using apt-file and then putting everything back again. A lot of work to find out where bootlogd went ;-) Woody doesn't have bootlogd. It was introduced in sysvinit 2.85 (sarge). Mike. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
empty boot log
Hello, I recently deleted /var/log/boot, and then did a touch /var/log/boot. However, I have rebooted multiple times and the log remains empty. Does anyone have ideas where I could start looking for solutions to this problem? ls excerpt: -rw-r--r--1 root root0 Jan 5 16:11 boot -rw-r--r--1 root root 3.6K Jan 1 11:37 boot.0 -rw-r--r--1 root root 1.1K Dec 25 19:32 boot.1.gz -rw-r--r--1 root root 1.1K Dec 24 06:31 boot.2.gz -rw-r--r--1 root root 1.1K Dec 23 22:01 boot.3.gz -rw-r--r--1 root root 1.1K Dec 23 18:42 boot.4.gz Thanks in advance, Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: empty boot log
Peter McAlpine wrote: Hello, I recently deleted /var/log/boot, and then did a touch /var/log/boot. However, I have rebooted multiple times and the log remains empty. Does anyone have ideas where I could start looking for solutions to this problem? ls excerpt: -rw-r--r--1 root root0 Jan 5 16:11 boot -rw-r--r--1 root root 3.6K Jan 1 11:37 boot.0 -rw-r--r--1 root root 1.1K Dec 25 19:32 boot.1.gz -rw-r--r--1 root root 1.1K Dec 24 06:31 boot.2.gz -rw-r--r--1 root root 1.1K Dec 23 22:01 boot.3.gz -rw-r--r--1 root root 1.1K Dec 23 18:42 boot.4.gz Thanks in advance, Peter I no longer have a /var/log/boot although I remember having one, what does its presence depend on? Hugo. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: empty boot log
On Tue, 2004-01-06 at 19:01, Hugo Vanwoerkom wrote: I no longer have a /var/log/boot although I remember having one, what does its presence depend on? Hugo. [19:[EMAIL PROTECTED]:~$ dpkg -S /var/log/boot dpkg: /var/log/boot not found. oh. Maybe when I dist-upgraded to unstable it changed. What do you suppose the method used to log my boot msgs is now? -Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: empty boot log
Hello Peter! On Tue, Jan 06, 2004 at 07:49:44PM -0500, Peter McAlpine wrote: On Tue, 2004-01-06 at 19:01, Hugo Vanwoerkom wrote: I no longer have a /var/log/boot although I remember having one, what does its presence depend on? Hugo. [19:[EMAIL PROTECTED]:~$ dpkg -S /var/log/boot dpkg: /var/log/boot not found. oh. Maybe when I dist-upgraded to unstable it changed. What do you suppose the method used to log my boot msgs is now? /var/log/boot is created by bootlogd from initscripts / sysvinit, but recently (since 2.85-8) this logging is turned off by default, see the changelogs for details. You can turn it on again by editing /etc/default/bootlogd. HTH, Flo signature.asc Description: Digital signature
Re: newbie boot log question
On Fri, Nov 28, 2003 at 04:45:53AM +0100, Christian Schnobrich wrote: On Thu, 2003-11-27 at 19:08, [EMAIL PROTECTED] wrote: Hello, I want to review the lines and lines of text that printout during startup, but they quickly scroll off the screen. just type 'dmesg'. Once done, you maybe want to type 'dmesg | less' :) HTH, Schnobs Hi, yes dmesg will show what happends from boot to init. to see what happends after, look at /var/log/messages it show what happens from init to shutdown. The difference is that dmesg is reset after each reboot but /var/log/messages is kept and eventually has its log rotated. Also try tail -f /var/log/messages and then insert something (a usb device, a pcmcia card) and what the result. (do ctrl - c to break out of the tail) -kev -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: newbie boot log question
Type dmesg at the command prompt. Then use Shift-Page Up to scroll upward. On Thu, 2003-11-27 at 10:08, [EMAIL PROTECTED] wrote: Hello, I want to review the lines and lines of text that printout during startup, but they quickly scroll off the screen. Are they logged in a file or files in /var/log or somewhere else? __ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: newbie boot log question
On Thu, Nov 27, 2003 at 10:08:50AM -0800, [EMAIL PROTECTED] wrote: Hello, I want to review the lines and lines of text that printout during startup, but they quickly scroll off the screen. Are they logged in a file or files in /var/log or somewhere else? Yes. Sometimes subsquent kernel messages will fill the ring buffer and the messages stored early in startup will be losted. The startup messages are preserved in /var/log/dmesg. Check there if you don't find what you are looking for when you run dmesg. -- The sky is blue so we know where to stop mowing. -- Judge Harold T. Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
newbie boot log question
Hello, I want to review the lines and lines of text that printout during startup, but they quickly scroll off the screen. Are they logged in a file or files in /var/log or somewhere else? __ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: newbie boot log question
On Thu, 2003-11-27 at 19:08, [EMAIL PROTECTED] wrote: Hello, I want to review the lines and lines of text that printout during startup, but they quickly scroll off the screen. just type 'dmesg'. Once done, you maybe want to type 'dmesg | less' :) HTH, Schnobs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
boot log
Hi, is there a log file where I can find all boot messages? Or, if not, is there a possibility to make them written into a log file? Florian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: boot log
Florian Sukup said: Hi, is there a log file where I can find all boot messages? Or, if not, is there a possibility to make them written into a log file? kernel boot messages from the last boot are stored in /var/log/dmesg messages from daemons starting as far as I know are not logged. if you really need it logged I'd reccomend setting up a serial console. nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: boot log
From: Florian Sukup, Wednesday, January 29, 2003 10:25 AM is there a log file where I can find all boot messages? Or, if not, is there a possibility to make them written into a log file? There is better than that. prompt dmesg This will show you the boot messages, but it will also keep up to date with loaded and unloaded modules. -- This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: boot log
This one time, at band camp, Florian Sukup said: Hi, is there a log file where I can find all boot messages? Or, if not, is there a possibility to make them written into a log file? /var/log/dmesg Can be viewed with `dmesg | $pager` HTH, -- -- | Stephen Gran | A friend of mine won't get a divorce, | | [EMAIL PROTECTED] | because he hates lawyers more than he | | http://www.lobefin.net/~steve | hates his wife. | -- msg27210/pgp0.pgp Description: PGP signature
Re: boot log
On Wed, Jan 29, 2003 at 04:15:16PM +0100, Florian Sukup wrote: is there a log file where I can find all boot messages? Or, if not, is there a possibility to make them written into a log file? /var/log/dmesg contains boot messages. -- Seneca [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: boot log
El Wednesday 29 January 2003 16:15, Florian Sukup escribió: Hi, is there a log file where I can find all boot messages? Or, if not, is there a possibility to make them written into a log file? Florian. Try dmesg | more it may help Cheers == Felipe Martínez Hermo [EMAIL PROTECTED] [EMAIL PROTECTED] == Servicios Informáticos UGT Galicia [EMAIL PROTECTED] == -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: boot log
Run 'dmesg', or alternatively, they may be stored in
/var/log/dmesg{.log}
j.
--
Jeremy L. Gaddis [EMAIL PROTECTED] http://www.gaddis.org
-Original Message-
From: Florian Sukup [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 29, 2003 10:15 AM
To: [EMAIL PROTECTED]
Subject: boot log
Hi,
is there a log file where I can find all boot messages?
Or, if not, is there a possibility to make them written into
a log file?
Florian.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: boot log
On Wed, Jan 29, 2003 at 04:15:16PM +0100, Florian Sukup wrote: Hi, is there a log file where I can find all boot messages? Try dmesg | less, or just look in /var/log. But some stuff never gets written there and is inevitably lost. Search the list for the past month or so; this has been mentioned a few times. Pigeon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: boot log
Try dmesg | less, or just look in /var/log. But some stuff never gets written there and is inevitably lost. Search the list for the past month or so; this has been mentioned a few times. If you want to just look at the messages you can use the scrollback buffer: have the system boot in runlevel 3 and use shift-pgup to scroll up. The buffer is lost if you switch console. If you desperatly need to cut and paste some lines (ex. to produce some documentation) you can use this trick: - install and configure gpm - reboot in runlevel 3 - login - press return a few times to leave some blank lines (a screenfull) - edit a new text file vi log_messages - enter insert mode - scroll up to the messages you want - select them with the mouse - paste them with third mouse button, they should be pasted into the text file - repeat until you get all messages you need (you can copy just a screen at a time) since each time yoy paste vi scrolls down it's better to start from the first lines you need I've done this successfully to get the complete boot sequence of a pc and it works, but it's a real pain ;) http://www.midhgard.it/docs/lvm/html/appendix.boot.messages.html Before resorting to this horror I also tried a different approach: I wrote a script that redirected the output of the scrollback buffer to file: I think it was something like cat /dev/vcsa1 log_file and I called it at the end of the boot sequence at regular intervals (a few secs)... but, alas, it didn't work :) Don't know if there is some package/tool able to get the content of the scrollback buffer. Massimiliano -- Massimiliano Ferrero Midhgard s.r.l. C/so Re Umberto 23 10128 - Torino tel. +39-0112301400 - fax +39-0112301422 e-mail: [EMAIL PROTECTED] sito web: http://www.midhgard.it -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: newbie qstion, boot log
Bruce Burhans [EMAIL PROTECTED] writes: $dmesg will read out *most* of your last boot-time messages.However, if you want to see them ALL, before you login, or right after,do Shift+PageUp/PageDown and it will scrollback a halfscreen at a time.This is without X. Cool! I didn't know that. Regards, KBK -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
boot log on debian 2.0
Hi, Prior to the debian 2.0 installation I used to have a detail boot log on /usr/adm/messages. Where is it on the 2.0 version. the /var/log/messages is very abbreviated the /var/log/syslog is also very abbreviated -Oz -- NAME Oz Dror, Los Angeles, California EMAIL [EMAIL PROTECTED] Linux since 8/15/94 PHONE Fax (310) 474-3126
