Good time of the day, Jude.
You worte:
No point in doing that at all. If you want to see those messages
after login as root or as sudo root do dmesg dmesg.log. Then less
dmesg.log will let you view those messages one screen at a time. Also
for a
You can shorten that to
dmesg |less
- no
On Mon 16 Jan 2012 at 04:57:13 +, Sharon Kimble wrote:
where do I change the file output of the boot screen messages that
scroll by so fast and are so small as to be unreadable before you get
to the logon screen please? i want to make them bigger and brighter so
that they are readable,
On 16/01/12 15:57, Sharon Kimble wrote:
where do I change the file output of the boot screen messages that
scroll by so fast and are so small as to be unreadable before you get
to the logon screen please? i want to make them bigger and brighter so
that they are readable, like in RHEL, Fedora
On 16/01/2012, Brian a...@cityscape.co.uk wrote:
On Mon 16 Jan 2012 at 04:57:13 +, Sharon Kimble wrote:
where do I change the file output of the boot screen messages that
scroll by so fast and are so small as to be unreadable before you get
to the logon screen please? i want to make them
On 16/01/12 21:35, Scott Ferguson wrote:
On 16/01/12 15:57, Sharon Kimble wrote:
where do I change the file output of the boot screen messages that
scroll by so fast and are so small as to be unreadable before you get
to the logon screen please?
snipped
Try editing grub at the boot
On Mon, 16 Jan 2012 09:10:01 +0100
Sthu Deus sthu.d...@gmail.com wrote:
--SNIP--
You can shorten that to
dmesg |less
- no need to file redirection
--SNIP--
dmesg uses a ring-buffer so as time passes after boot dmesg | less is
useless if the objective is to see what happened at boot
On Mon 16 Jan 2012 at 10:38:40 +, Sharon Kimble wrote:
On 16/01/2012, Brian a...@cityscape.co.uk wrote:
Does
dpkg-reconfigure console-setup
get you what you want?
Sorry, no. I'm looking to view the messages at bootup time before you
logon, the ones that are too small to
Can you disrupt something if it is out of the ordinary while the system
boots up? If not, you may as well wait until after login to find out
what happened. The only possible case I can conceive of where what you
want to do makes any sense is if a change was done to the system; the
system is
On 17/01/12 02:22, Jude DaShiell wrote:
Can you disrupt something if it is out of the ordinary while the system
boots up?
Yes.
SysRq[*1]
If not, you may as well wait until after login to find out
what happened. The only possible case I can conceive of where what you
want to do makes
where do I change the file output of the boot screen messages that
scroll by so fast and are so small as to be unreadable before you get
to the logon screen please? i want to make them bigger and brighter so
that they are readable, like in RHEL, Fedora or Centos. this is during
bootup and before
No point in doing that at all. If you want to see those messages after
login as root or as sudo root do dmesg dmesg.log. Then less dmesg.log
will let you view those messages one screen at a time. Also for a
particular issue of interest, dmesg | grep -in search_string will show
specific
On 16/01/2012, Jude DaShiell jdash...@shellworld.net wrote:
No point in doing that at all. If you want to see those messages after
login as root or as sudo root do dmesg dmesg.log. Then less dmesg.log
will let you view those messages one screen at a time. Also for a
particular issue of
12 matches
Mail list logo
