On Monday 15 September 2003 22:40, Pim Bliek wrote:
> Even easier is to read it afterwards.
>
> Try:
> 'dmesg | less'
> or:
> 'less /var/log/kern.log'
>
> Both ways give you lots of info what happened during bootup and enables
> you grep'ing for stuff as well of course :).
>
> Pim
>
> On Mon, 20
On Tue, Sep 16, 2003 at 01:23:51AM +0100, Karsten M. Self wrote:
> on Tue, Sep 16, 2003 at 12:45:25AM +0100, Colin Watson ([EMAIL PROTECTED]) wrote:
> > On Mon, Sep 15, 2003 at 06:37:11PM -0500, Jason Pepas wrote:
> > > Colin Watson wrote:
> > > > Note, though, that neither of those shows you messa
on Tue, Sep 16, 2003 at 12:45:25AM +0100, Colin Watson ([EMAIL PROTECTED]) wrote:
> On Mon, Sep 15, 2003 at 06:37:11PM -0500, Jason Pepas wrote:
> > Colin Watson wrote:
> > > Note, though, that neither of those shows you messages output by init
> > > scripts.
> >
> > are there any tricks for obtai
On Mon, Sep 15, 2003 at 06:37:11PM -0500, Jason Pepas wrote:
> Colin Watson wrote:
> > Note, though, that neither of those shows you messages output by init
> > scripts.
>
> are there any tricks for obtaining this?
I always just use Ctrl-S and Ctrl-Q; see further up the thread.
Cheers,
--
Coli
> Note, though, that neither of those shows you messages output by init
> scripts.
are there any tricks for obtaining this?
-jason
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Colin Watson wrote:
[...]
You can hit Ctrl-S as messages are scrolling up the screen to pause
them. Hit Ctrl-Q to resume when you're ready.
Thank you so much.
You just solved my problem:
I hit Ctrl-S quite often accidently. Either missing the Ctrl-D by just
one key to the left, or by hitting emac
On Mon, Sep 15, 2003 at 04:40:42PM +0200, Pim Bliek wrote:
> Even easier is to read it afterwards.
>
> Try:
> 'dmesg | less'
> or:
> 'less /var/log/kern.log'
>
> Both ways give you lots of info what happened during bootup and enables
> you grep'ing for stuff as well of course :).
Note, though, t
Even easier is to read it afterwards.
Try:
'dmesg | less'
or:
'less /var/log/kern.log'
Both ways give you lots of info what happened during bootup and enables
you grep'ing for stuff as well of course :).
Pim
On Mon, 2003-09-15 at 15:47, Colin Watson wrote:
> On Mon, Sep 15, 2003 at 09:27:30PM +
On Mon, Sep 15, 2003 at 09:27:30PM +0800, David Palmer wrote:
> I'm experimenting on my Libranet setup, and I've got things in a bit of a
> mess.
> Never mind it matches the rest of the house.
> When I was in my Windows days, there was an obscure setting that would slow
> down the start up graphi
Hello everyone,
I'm experimenting on my Libranet setup, and I've got things in a bit of a
mess.
Never mind it matches the rest of the house.
When I was in my Windows days, there was an obscure setting that would slow
down the start up graphics to a pace that you had time to read them.
Is there a
10 matches
Mail list logo
