On Thursday, March 05, 2015 3:16:55 AM Dale wrote:
Yea, it won't catch everything. This is sort of designed for that point
where one log stops and the other hasn't started yet. This is usually
where dmesg stops and syslog and friends hasn't yet started. Of course,
if /var isn't mounted,
Neil Bothwick wrote:
On Thu, 5 Mar 2015 03:08:46 -0500, German wrote:
Thanks Dale, done it. Unfortunately it doesn't log everything. For
instance Warning: /lib64/rc/cache is not writable wasn't written
to /var/log/rc.log
Of course it wasn't. Warnings about /var not being writeable are not
On Thu, 5 Mar 2015 03:08:46 -0500, German wrote:
Thanks Dale, done it. Unfortunately it doesn't log everything. For
instance Warning: /lib64/rc/cache is not writable wasn't written
to /var/log/rc.log
Of course it wasn't. Warnings about /var not being writeable are not going
to be written to
On Thu, 05 Mar 2015 00:17:34 -0600
Dale rdalek1...@gmail.com wrote:
German wrote:
I have a SSD in my laptop and the system boots really fast so I can't see
the details of the warnings it displays. Are there any way to scroll the
screen or see some system boot's logs? Thanks
You
On Thu, 5 Mar 2015 09:38:07 -0500, Rich Freeman wrote:
I personally use dracut which has quite a few bells and whistles. If
you're using systemd as has already been pointed out it runs the
journal during early boot and merges it into the system journal when
it pivots. I believe that if
On Thu, Mar 5, 2015 at 12:08 PM, Neil Bothwick n...@digimed.co.uk wrote:
On Thu, 5 Mar 2015 09:38:07 -0500, Rich Freeman wrote:
I personally use dracut which has quite a few bells and whistles. If
you're using systemd as has already been pointed out it runs the
journal during early boot and
On Thu, 05 Mar 2015 03:16:55 -0600, Dale wrote:
Of course it wasn't. Warnings about /var not being writeable are not
going to be written to /var.
Yea, it won't catch everything. This is sort of designed for that point
where one log stops and the other hasn't started yet. This is usually
On Thu, Mar 5, 2015 at 8:19 AM, Dale rdalek1...@gmail.com wrote:
I just recall reading somewhere, systemd or not, that that is how it is
supposed to work. After all, it can't run fsck and such while mounted
rw from my understanding.
Keep in mind that an initramfs is nothing more than an
Dale rdalek1...@gmail.com wrote:
Neil Bothwick wrote:
On Thu, 5 Mar 2015 03:08:46 -0500, German wrote:
Thanks Dale, done it. Unfortunately it doesn't log everything. For
instance Warning: /lib64/rc/cache is not writable wasn't written
to /var/log/rc.log
Of course it wasn't.
cov...@ccs.covici.com wrote:
Dale rdalek1...@gmail.com wrote:
Neil Bothwick wrote:
On Thu, 5 Mar 2015 03:08:46 -0500, German wrote:
Thanks Dale, done it. Unfortunately it doesn't log everything. For
instance Warning: /lib64/rc/cache is not writable wasn't written
to /var/log/rc.log
Of
I have a SSD in my laptop and the system boots really fast so I can't see the
details of the warnings it displays. Are there any way to scroll the screen or
see some system boot's logs? Thanks
--
German gentger...@gmail.com
On Thu, Mar 5, 2015 at 1:58 PM, German gentger...@gmail.com wrote:
I have a SSD in my laptop and the system boots really fast so I can't see
the details of the warnings it displays. Are there any way to scroll the
screen or see some system boot's logs?
Try;
dmesg | less
And you may also
German wrote:
I have a SSD in my laptop and the system boots really fast so I can't see the
details of the warnings it displays. Are there any way to scroll the screen
or see some system boot's logs? Thanks
You may want to read this post and try this method too. I did this ages
ago and on
13 matches
Mail list logo
