[Grml] dmesg is empty

[T o n g]

Hi,

IIRC, the /var/log/dmesg file is empty when booting into grml.

Can anyone confirm this?
How can I fix it so that my device info is retained?

Thanks

[Michael Prokop]

Post by T o n g
IIRC, the /var/log/dmesg file is empty when booting into grml.
Can anyone confirm this?
How can I fix it so that my device info is retained?

That's because we don't invoke /etc/init.d/bootlogs in live mode.
Why would you need that? Doesn't invoking dmesg(1) provide what
you'd need?

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.mur.at/pipermail/grml/attachments/20100714/4ed2fad9/attachment.pgp>

[T o n g]

Why would you need that? Doesn't invoking dmesg(1) provide what you'd
need?

I was trying to use dmesg to see what kind of peripheral does the booted
machine has. IIRC, dmesg yielded empty output as well.

A better alternative to see all peripheral info for the box?

Thanks

[Michael Prokop]

Post by T o n g

Why would you need that? Doesn't invoking dmesg(1) provide what you'd
need?

I was trying to use dmesg to see what kind of peripheral does the booted
machine has. IIRC, dmesg yielded empty output as well.

Basically /var/log/dmesg provides the same as running dmesg.

Post by T o n g
A better alternative to see all peripheral info for the box?

Invoking dmesg, lspci, lshw, hwinfo --all,...
Check out what grml-hwinfo does.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.mur.at/pipermail/grml/attachments/20100715/74ff1ca7/attachment.pgp>

[T o n g]

. . . Doesn't invoking dmesg(1) provide what you'd
need?

. . . IIRC, dmesg yielded empty output as well.

Nope, incorrect -- invoking dmesg(1) right after boot can get boot up
peripheral info.

Thanks

[Michael Prokop]

Post by T o n g

Why would you need that? Doesn't invoking dmesg(1) provide what you'd
need?

I was trying to use dmesg to see what kind of peripheral does the booted
machine has. IIRC, dmesg yielded empty output as well.

Basically /var/log/dmesg provides the same as running dmesg.

Post by T o n g
A better alternative to see all peripheral info for the box?

Invoking dmesg, lspci, lshw, hwinfo --all,...
Check out what grml-hwinfo does.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://ml.grml.org/pipermail/grml/attachments/20100715/74ff1ca7/attachment-0002.pgp>

[T o n g]

. . . Doesn't invoking dmesg(1) provide what you'd
need?

. . . IIRC, dmesg yielded empty output as well.

Nope, incorrect -- invoking dmesg(1) right after boot can get boot up
peripheral info.

Thanks

[Michael Prokop]

Post by T o n g

Why would you need that? Doesn't invoking dmesg(1) provide what you'd
need?

I was trying to use dmesg to see what kind of peripheral does the booted
machine has. IIRC, dmesg yielded empty output as well.

Basically /var/log/dmesg provides the same as running dmesg.

Post by T o n g
A better alternative to see all peripheral info for the box?

Invoking dmesg, lspci, lshw, hwinfo --all,...
Check out what grml-hwinfo does.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://ml.grml.org/pipermail/grml/attachments/20100715/74ff1ca7/attachment-0003.pgp>

[T o n g]

. . . Doesn't invoking dmesg(1) provide what you'd
need?

. . . IIRC, dmesg yielded empty output as well.

Nope, incorrect -- invoking dmesg(1) right after boot can get boot up
peripheral info.

Thanks

[T o n g]

Why would you need that? Doesn't invoking dmesg(1) provide what you'd
need?

I was trying to use dmesg to see what kind of peripheral does the booted
machine has. IIRC, dmesg yielded empty output as well.

A better alternative to see all peripheral info for the box?

Thanks

[T o n g]

Why would you need that? Doesn't invoking dmesg(1) provide what you'd
need?

I was trying to use dmesg to see what kind of peripheral does the booted
machine has. IIRC, dmesg yielded empty output as well.

A better alternative to see all peripheral info for the box?

Thanks

[T o n g]

Hi,

IIRC, the /var/log/dmesg file is empty when booting into grml.

Can anyone confirm this?
How can I fix it so that my device info is retained?

Thanks

[Michael Prokop]

Post by T o n g
IIRC, the /var/log/dmesg file is empty when booting into grml.
Can anyone confirm this?
How can I fix it so that my device info is retained?

That's because we don't invoke /etc/init.d/bootlogs in live mode.
Why would you need that? Doesn't invoking dmesg(1) provide what
you'd need?

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://ml.grml.org/pipermail/grml/attachments/20100714/4ed2fad9/attachment-0002.pgp>

[T o n g]

Hi,

IIRC, the /var/log/dmesg file is empty when booting into grml.

Can anyone confirm this?
How can I fix it so that my device info is retained?

Thanks

[Michael Prokop]

Post by T o n g
IIRC, the /var/log/dmesg file is empty when booting into grml.
Can anyone confirm this?
How can I fix it so that my device info is retained?

That's because we don't invoke /etc/init.d/bootlogs in live mode.
Why would you need that? Doesn't invoking dmesg(1) provide what
you'd need?

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://ml.grml.org/pipermail/grml/attachments/20100714/4ed2fad9/attachment-0003.pgp>