From mint-bounce@lists.fishpool.fi Tue Mar 2 04:11:46 2010 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=l9wH7P1Ym7m62B+0zgv/tXci2PfUxw3ImjTUZ1sI9wY=; b=ODtZNcwKRrt0DtqrzZDXJrOrhVuVTqpOIMeuJ3vLs8mpEsEqet5EkLVjv/PuKDddsu DErmW6huG6LO9TF+3LoEd5sfFg7ZXq05kGgzORLD5yTtHw8owOBPH5Aztg7ePNo0ge/i UpzuwbDHCr7UY8TXbNUyh/FKBSBGLSTEI9GZQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=iaAWCuKLtoHAQU4lkwEBOrMD5a1h+vzz8OTt9ngIRk3seik76ubFk511YQ0it2+Nb4 MsXE0QgPdtXXSvtXvxrpz1qEKUKr4fOocP5UDgW0oi1yugVoa6X6z/L2cEoKMKZDuT5/ 9/YvoK9LkO8qrF9dIZ+uQmZb1RPVd4DIqm5GU= MIME-Version: 1.0 In-Reply-To: <7E7218016F1C4536ACDDACBB605FE084@mercatus.local> References: <72454075-6FA5-46CA-A174-A3AE573771A6@gmail.com> <20100301222525.bcb94ec5.mandin.patrice@orange.fr> <7E7218016F1C4536ACDDACBB605FE084@mercatus.local> Date: Tue, 2 Mar 2010 10:09:56 +0100 Message-ID: Subject: Re: [MiNT] Patch for xaloader.prg From: Miro Kropacek To: Jo Even Skarstein Cc: mint_list Content-Type: multipart/alternative; boundary=0015174c1cf2ba692a0480cdbab9 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: miro.kropacek@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: --0015174c1cf2ba692a0480cdbab9 Content-Type: text/plain; charset=ISO-8859-1 > > Same with a CT60 - I would be surprised if the kernel is the only thing > that differs between a 030 and 060-setup. My normal setup on the AB and > Milan has no chance to work on a 14Mb 030, so a boot manager is required > anyway. > > I'm not saying that automatic kernel-selection is a bad idea. I'm saying > that it's usefulness is limited when you're already using a boot-manager. > Well, it's clear then, our use cases differ quite a much -- my only AUTO items are nvdi.prg and mint.prg, no matter if 030, 060 or Aranym; on Aranym I execute fVDI from mint.cnf, everything else is the same. And since I can made a script for launching fVDI only on Aranym (simple uname check will do), I'm totally OK with simple bootloader with more focus on kernel initialization (I can imagine it could parse whole mint.cnf in a future). So question is what side Peter prefers to take now ;-) -- MiKRO / Mystic Bytes http://mikro.atari.org --0015174c1cf2ba692a0480cdbab9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Same with a CT60 - I would be surprised=20 if the kernel is the only thing that differs between a 030 and 060-setup. M= y=20 normal setup on the AB and Milan has no chance to work on a 14Mb 030, so a = boot=20 manager is required anyway.
=A0
I'm not saying that automatic kernel-select= ion is a bad=20 idea. I'm saying that it's usefulness is limited when you're al= ready using a=20 boot-manager.
Well, it's clear then= , our use cases differ quite a much -- my only AUTO items are nvdi.prg and = mint.prg, no matter if 030, 060 or Aranym; on Aranym I execute fVDI from mi= nt.cnf, everything else is the same. And since I can made a script for laun= ching fVDI only on Aranym (simple uname check will do), I'm totally OK = with simple bootloader with more focus on kernel initialization (I can imag= ine it could parse whole mint.cnf in a future). So question is what side Pe= ter prefers to take now ;-)

--
MiKRO / Mystic Bytes
http://mikro.atari.org
--0015174c1cf2ba692a0480cdbab9--