You are not logged in.
I've been able to capture the last screen of console boot messages, after starting X, with this command:
sudo cat /dev/vcs1 > console_1.txt
Unfortunately, it records the screen text without line breaks. Everything is on a single line.
Offline
(...)
Some queries:
1. What's it with all the ^[[?
They are color codes, like the ones you can set for bash output. No idea where they come from though.
Offline
toad wrote:(...)
Some queries:
1. What's it with all the ^[[?They are color codes, like the ones you can set for bash output. No idea where they come from though.
They come from initscripts.
Offline
Pardon me for being dumb but what do I do with karol's script?
#!/bin/bash
sed 's#\^\[#\\033#g' /var/log/boot > 00blog
printf "$(cat 00blog) \n"
Please note you are talking to someone who has no IT background or scripting experience whatsoever, i.e. the ideal answer would be: you put it <there> like <this>
Many thanks in advance to the kind soul who takes pity on me...
never trust a toad...
::Grateful ArchDonor::
::Grateful Wikipedia Donor::
Offline
Pardon me for being dumb but what do I do with karol's script?
#!/bin/bash sed 's#\^\[#\\033#g' /var/log/boot > 00blog printf "$(cat 00blog) \n"
Please note you are talking to someone who has no IT background or scripting experience whatsoever, i.e. the ideal answer would be: you put it <there> like <this>
Many thanks in advance to the kind soul who takes pity on me...
Just save is to a file (say, ~/toadboot), make it executable (chmod +x ~/toadboot) and run (assuming you're in your ~, './toadboot' will do).
Offline
Cheers, karol.
And I suppose I could put it in /etc/rc.local so as to forego this arduous task? Or is there a niftier way of integrating it?
never trust a toad...
::Grateful ArchDonor::
::Grateful Wikipedia Donor::
Offline
Cheers, karol.
And I suppose I could put it in /etc/rc.local so as to forego this arduous task? Or is there a niftier way of integrating it?
But it doesn't even work right! It (/var/log/boot) doesn't log all the things it should, so I'm not sure you will see much benefit using it.
But sure, it's basically a two-liner so it definitely doesn't have to be a separate script.
Offline
Cheers, karol.
And I suppose I could put it in /etc/rc.local so as to forego this arduous task? Or is there a niftier way of integrating it?
Since it can be run after the boot, you can put it in ~/.xinitrc instead of rc.local, as that would be easier to maintain.
Offline
B.t.w. most of the color codes are gone when you change USECOLOR="yes" to USECOLOR="no" in /etc/rc.conf .
Offline
Somehow the contents of /var/log/boot can't be directly parsed by 'less -{Rr}'
Anyone has explanations for that?
Offline
The ^[ characters in the /var/log/boot file aren't the escape character \e (or ^[).
Last edited by alem0lars (2011-07-05 13:12:34)
Offline
Can you test if this commit http://projects.archlinux.org/initscrip … 9d8a516abc clears the boot log properly?
Offline
For not opening a new thread I have bootlogd package installed which worked just fine before I switched to systemd, now the daemon doesn't run and systemctl doesn't include it:
# systemctl enable bootlogd
Failed to issue method call: No such file or directory
furthermore lack of a rc.d script makes me ask "How can I make it run just when the system starts?"
Offline
furthermore lack of a rc.d script makes me ask "How can I make it run just when the system starts?"
Just read about journalctl
journalctl --help
In your case run
journalctl -b
and find all needed info about boot process.
Offline