[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] C:\MINT directory locked & xa_boot.log

To: mint <mint@lists.fishpool.fi>
Subject: Re: [MiNT] C:\MINT directory locked & xa_boot.log
From: "J. F. Lemaire" <jflemaire@skynet.be>
Date: Mon, 28 Jan 2013 10:52:07 +0100
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=Ixb2BuSzVavk4OjckyymqCqAO22HVyKHKHZ6fGiM/3s=; b=ROJK7gJEb4iB5sOVF9UNDJkpkY8uRB+TJbNapN8HTdPfUFfGMULteKf2vDa7U8cTvS DJ6bAFWZhmyqZ6IUYWNWS7QOutczZRr6ms0zwB9nGqNviJU6QRaKHZKV39iLmChxnA5A sClqJ8upVNGqI8pNRF7QLKj4BvXhggkZCNzch+qwKQU4umNtzem/xM4ILTI0pZ8hlgOD uhsbvJkV0vfgW7SpXBQKwkk1HUnDG7GiuOvZ0+CJ2u+ts3kkmJ9hFZh7i2zalyAmrazx 6e6uhbd4H2ynh1jsNsTE9rm5jasSarPpCgAb9FV/daWhKRa2ztvYkhn0cCKCW/+qPqmP U4sQ==
In-reply-to: <201301281024.40855.oak@helsinkinet.fi>
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-id: <mint.lists.fishpool.fi>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
References: <5102FE07.20001@freesbee.fr> <1359345283.78264.YahooMailNeo@web124502.mail.ne1.yahoo.com> <CAHMGLYQcb=+0s7+xO53SCL9gUgrC3uQnBVzG1TWbHq_wHUGjGw@mail.gmail.com> <201301281024.40855.oak@helsinkinet.fi>
Sender: mint-bounce@lists.fishpool.fi

On 28 January 2013 09:24, Eero Tamminen <oak@helsinkinet.fi> wrote:
 On maanantai 28 tammikuu 2013, J. F. Lemaire wrote:

>> One thing I don't understand about xa_boot.log is why it's important
>> to keep its previous content intact during each boot. Why not wipe the
>> file out? At least we would be sure it would never grow into a
>> multi-MB monster.

> If you have a problem that requires reboot, the log disappearing
> at that point would make it rather useless for investigating
> the issue afterwards, wouldn't it? :-)

Boot into TOS and backup/examine the log before rebooting into MiNT.
If XaAES doesn't start you'll probably need to boot into TOS anyway.

Cheers,
JFL
-- 
Jean-François Lemaire

References:
- [MiNT] C:\MINT directory locked & xa_boot.log
  - From: Vincent Rivière <vincent.riviere@freesbee.fr>
- Re: [MiNT] C:\MINT directory locked & xa_boot.log
  - From: WongCK <wongck68@yahoo.com>
- Re: [MiNT] C:\MINT directory locked & xa_boot.log
  - From: "J. F. Lemaire" <jflemaire@skynet.be>
- Re: [MiNT] C:\MINT directory locked & xa_boot.log
  - From: Eero Tamminen <oak@helsinkinet.fi>

Prev by Date: Re: [MiNT] C:\MINT directory locked & xa_boot.log
Next by Date: Re: [MiNT] GEM mainloop and time consuming tasks
Previous by thread: Re: [MiNT] C:\MINT directory locked & xa_boot.log
Next by thread: Re: [MiNT] C:\MINT directory locked & xa_boot.log
Index(es):
- Date
- Thread