Hello Camaleón,
Excerpt from Camaleón:
> On Sun, 15 Apr 2012 18:48:21 +0200, Thilo Six wrote:
-- --
> the "--noclear" parameter so I think it has to be placed in "/etc/
> inittab" file:
>
> 1:2345:respawn:/sbin/getty --noclear 38400 tty1
Excellent. Thats it. Apparently i did look into '/etc/i
On 04/15/2012 12:48 PM, Thilo Six wrote:
Hello
since the upgrade to wheezy i have a problem with the messages that are shown
during boot. Currently during boot messages are shown as usual on vt1 but then
at some point late in the boot process these messages are cleared and then only
the login pr
On Sun, 15 Apr 2012 18:48:21 +0200, Thilo Six wrote:
> since the upgrade to wheezy i have a problem with the messages that are
> shown during boot. Currently during boot messages are shown as usual on
> vt1 but then at some point late in the boot process these messages are
> cleared and then only
El Diumenge 17 Setembre 2006 09:06, Ron Johnson va escriure:
> Edit /etc/default/bootlogd so that "BOOTLOGD_ENABLE=Yes". Next time
> you reboot, such messages should be in /var/log/boot.
Thanks!
Finally I can see boot errors :)
-
Mon Sep 18 16:52:28 2006: Configuring network interfaces.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/17/06 00:04, Benjamí Villoslada wrote:
> How I can read the boot messages? With /var/log grep and zgrep I
> can't locate some error messages that appears when the system
> starts. I.e. today have read some about /etc/ntp... ? and ntpdate
> doesn
/var/log/messages
-gnana
> The original question was about suppressing verbose messages at boot.
My question: I want to know what the computer said at boot time.
Something like dmesg. dmesg isn't useful anymore after a few months
uptime, because it only contains new information which has pused the old
boot messages out of
Sorry, I deleted the original message before I realized that I might
have an answer.
The original question was about suppressing verbose messages at boot.
In the file: /etc/defaults/rcS
# Set VERBOSE to "no" if you would like a more quiet bootup.
VERBOSE=yes
Hope this helps.
--
Subject: boot messages too fast to read.
Date: Thu, Aug 19, 1999 at 06:14:02PM +1000
In reply to:Alexander Jankowsky
Quoting Alexander Jankowsky([EMAIL PROTECTED]):
>
>
> How do you look at all the start up information that scrolls past
> too quickly to read when the computer
In article <[EMAIL PROTECTED]>,
Hwei Sheng TEOH <[EMAIL PROTECTED]> wrote:
>It seems that certain messages are not recorded by dmesg: such as isapnp
>messages. (I've never been able to see the board ID and "activated OK" message
>in dmesg -- only on the console.) Anybody can explain why??
Yes. Th
On Tue, Aug 24, 1999 at 12:40:19AM -0400, Hwei Sheng TEOH wrote:
> It seems that certain messages are not recorded by dmesg: such as isapnp
> messages. (I've never been able to see the board ID and "activated OK" message
> in dmesg -- only on the console.) Anybody can explain why?? I'd like to hav
On Tue, 24 Aug 1999, Mark Wagnon wrote:
> On Mon 08/23/99 11:31PM, David Teague wrote:
>
> > After boot, dmesg will give a good bit of the boot messages, but
> > sometimes it fails to give parts of the boot message that I want :(
>
> I have this problem, and it drives me crazy. Sometimes I wan
On Mon 08/23/99 11:31PM, David Teague wrote:
> After boot, dmesg will give a good bit of the boot messages, but
> sometimes it fails to give parts of the boot message that I want :(
I have this problem, and it drives me crazy. Sometimes I want to cut
and paste the info into my pleas for help, but
On Mon, 23 Aug 1999, Patrick Ouellette wrote:
> You shouldn't need to do anything special to enable this, but if
> you switch virtual consoles the buffer that Shift-PGUP/PGDN
> scrolls through is reset.
Pat
Don't switch consoles. That does indeed reset the scrollback buffer.
Wait until the lo
You shouldn't need to do anything special to enable this, but if you switch
virtual consoles the buffer that Shift-PGUP/PGDN scrolls through is reset.
Pat
On Thu, Aug 19, 1999 at 01:16:48AM -0700, Steve Lamb wrote:
> Thursday, August 19, 1999, 1:14:02 AM, Alexander wrote:
> > How do you look at all the start up information that scrolls past
> > too quickly to read when the computer is first booted.
>
> dmesg from the command prompt.
>
> Shi
Alexander Jankowsky <[EMAIL PROTECTED]> wrote:
>How do you look at all the start up information that scrolls past
>too quickly to read when the computer is first booted.
>
>
Use Shift + pgup/pgdown before you logon to see the messages.
Henning Olsen
___
Alexander Jankowsky wrote on Thursday, August 19, 1999 10:14 AM:
-- snip --
> How do you look at all the start up information that scrolls past
> too quickly to read when the computer is first booted.
-- snip --
Try SHIFT a
Thursday, August 19, 1999, 1:14:02 AM, Alexander wrote:
> How do you look at all the start up information that scrolls past
> too quickly to read when the computer is first booted.
dmesg from the command prompt.
Shift-PGUP/PGDN for console scrolling.
--
Steve C. Lamb |
Hi tony,
you wrote on: 24 Jan 99 at 22:05 (received 25.01.99)
about : _boot messages/logging_
>I'm at a loss to find the way to get all the
>boot messages logged to a file. Is there a
>recommended procedure or configuration file
>change that I can make?
After boot, just type
dmes
Hi Tony,
> I'm at a loss to find the way to get all the
> boot messages logged to a file. Is there a
> recommended procedure or configuration file
> change that I can make?
dmesg displays boot messages. It is usually run at system startup and
it's output redirected to /var/log/boot.msg or a simila
On Tue, Sep 15, 1998 at 01:25:41PM +0200, E.L. Meijer (Eric) wrote:
> >
> > This is a long story. I'll make it as short as I can.
> >
> > I've been having a devil of a time trying to get the Hamm install
> > kernel to read my hd at boot. I'm using the lowmem option to
> > install on a 4mb PS/2
Could it be a bad EPROM or wrong BIOS ?
I had these Problems with a PC based Shuttle 569
after I installed
the updated BIOS (and it was the correct one !!)
from their webp.
It would overheat the CPU or work fine, but when
idle for a long
time would just die on me.
In the end I took out the CPU pu
>
> This is a long story. I'll make it as short as I can.
>
> I've been having a devil of a time trying to get the Hamm install
> kernel to read my hd at boot. I'm using the lowmem option to
> install on a 4mb PS/2 model 35. (By the way, this is one of the
> very few PS/2's that have an AT bus
Ole J. Tetlie wrote:
>
> | I checked /etc/syslog.conf which has the line:
> |
> | kern.*-/var/log/kern.log
>
> Mine too.
>
> | This hasn't changed since bo. I also checked /etc/rc?.d to see if
> | syslogd or klogd were being started any differently, but I can't
>
Ole J. Tetlie wrote:
>
> * Shiraz Sayani <[EMAIL PROTECTED]>
> |
> | Anyone know where it goes now, or what's changed, or how to scroll
> | the console back?
>
> Use 'dmesg' to see the messages. Have you checked /var/log/kern.log ?
Thanks for the pointer to dmesg, but I did used to get all these
* Shiraz Sayani <[EMAIL PROTECTED]>
|
| Anyone know where it goes now, or what's changed, or how to scroll
| the console back?
Use 'dmesg' to see the messages. Have you checked /var/log/kern.log ?
| installed kernel rather than my existing 3.0.33 kernel.
That would probably be 2.0.33...
--
O
27 matches
Mail list logo
