Prev: kde 4 + kpowersave
Next: External USB HDD : files disappeared
From: Gerard H. Pille on 26 Jul 2010 17:00

After a boot, my boot.log is less than 4k in size, and contains only a
small percentage of the boot messages.

Is there any way to increase this so that I can review all messages
that appeared on the console?

Thanks,

Gerard

_________________________________________________________________
Hotmail: Free, trusted and rich email service.
https://signup.live.com/signup.aspx?id=60969

--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/BLU105-W680140D40EAB194057093BCA60(a)phx.gbl
From: Camaleón on 26 Jul 2010 18:10
On Mon, 26 Jul 2010 22:39:36 +0200, Gerard H. Pille wrote:

> After a boot, my boot.log is less than 4k in size, and contains only a
> small percentage of the boot messages.
>
> Is there any way to increase this so that I can review all messages that
> appeared on the console?

Kind of...

/etc/default/bootlogd

BOOTLOGD_ENABLE=Yes

I think the other messages fall into "/var/log/messages"

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/pan.2010.07.26.22.07.41(a)gmail.com
From: Miles Fidelman on 26 Jul 2010 18:20
Camaleón wrote:
> On Mon, 26 Jul 2010 22:39:36 +0200, Gerard H. Pille wrote:
>
>
>> After a boot, my boot.log is less than 4k in size, and contains only a
>> small percentage of the boot messages.
>>
>> Is there any way to increase this so that I can review all messages that
>> appeared on the console?
>>
> Kind of...
>
> /etc/default/bootlogd
>
> BOOTLOGD_ENABLE=Yes
>
> I think the other messages fall into "/var/log/messages"
>
Not quite. This only effects messages generated after the kernel has
booted. Earlier messages, generated by the BIOS and early boot stages
are not captured - unless you have a terminal on the console port that
can capture them.

Miles Fidelman

--
In theory, there is no difference between theory and practice.
In<fnord> practice, there is. .... Yogi Berra



--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4C4E087D.1090703(a)meetinghouse.net
From: Camaleón on 27 Jul 2010 02:20
On Mon, 26 Jul 2010 18:13:17 -0400, Miles Fidelman wrote:

> Camaleón wrote:

(...)

>>> Is there any way to increase this so that I can review all messages
>>> that appeared on the console?
>>>
>> Kind of...
>>
>> /etc/default/bootlogd
>>
>> BOOTLOGD_ENABLE=Yes
>>
>> I think the other messages fall into "/var/log/messages"
>>
> Not quite. This only effects messages generated after the kernel has
> booted. Earlier messages, generated by the BIOS and early boot stages
> are not captured - unless you have a terminal on the console port that
> can capture them.

Messages that appear in console when system boots (as per OP request) are
splitted into "/var/log/messages" and "/var/log/boot" (whether enabled).

BIOS screen (and/or remaining devices initilization) messages are a
different thing.

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/pan.2010.07.27.06.13.37(a)gmail.com
 | 
Pages: 1
Prev: kde 4 + kpowersave
Next: External USB HDD : files disappeared