From mint-bounce@lists.fishpool.fi Tue Mar 2 04:25:40 2010 Message-ID: <0008F327DA6C4C8D910AD2D2648F6FFF@mercatus.local> From: "Jo Even Skarstein" To: "mint_list" References: <72454075-6FA5-46CA-A174-A3AE573771A6@gmail.com> <20100301222525.bcb94ec5.mandin.patrice@orange.fr> <7E7218016F1C4536ACDDACBB605FE084@mercatus.local> In-Reply-To: Subject: Re: [MiNT] Patch for xaloader.prg Date: Tue, 2 Mar 2010 10:25:09 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_010B_01CAB9F2.A2765A50" X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8089.726 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726 X-EsetScannerBuild: 6677 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: joska@online.no Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Dette er en melding med flere deler i MIME-format. ------=_NextPart_000_010B_01CAB9F2.A2765A50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Yes, obviously. The setup you describe would never work on a Milan or = AB, and probably not on the Hades either. Also, when you need to boot = into TOS or MagiC, a boot-manager is required. Jo Even From: Miro Kropacek=20 Sent: Tuesday, March 02, 2010 10:09 AM To: Jo Even Skarstein=20 Cc: mint_list=20 Subject: Re: [MiNT] Patch for xaloader.prg 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 ;-) --=20 MiKRO / Mystic Bytes http://mikro.atari.org ------=_NextPart_000_010B_01CAB9F2.A2765A50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Yes, obviously. The setup you describe would = never work=20 on a Milan or AB, and probably not on the Hades either. Also, when you = need to=20 boot into TOS or MagiC, a boot-manager is required.
 
Jo Even

Sent: Tuesday, March 02, 2010 10:09 AM
Subject: Re: [MiNT] Patch for xaloader.prg

Same with a CT60 - I would be surprised if = the kernel=20 is the only thing that differs between a 030 and 060-setup. My normal = setup on=20 the AB and Milan has no chance to work on a 14Mb 030, so a boot = manager is=20 required anyway.
 
I'm not saying that automatic = kernel-selection is a=20 bad idea. I'm saying that it's usefulness is limited when you're = already using=20 a boot-manager.
Well, it's clear then, our use cases differ quite a much -- my only = AUTO=20 items are nvdi.prg and mint.prg, no matter if 030, 060 or Aranym; on = Aranym I=20 execute fVDI from mint.cnf, everything else is the same. And since I can = made a=20 script for launching fVDI only on Aranym (simple uname check will do), = I'm=20 totally OK with simple bootloader with more focus on kernel = initialization (I=20 can imagine it could parse whole mint.cnf in a future). So question is = what side=20 Peter prefers to take now ;-)

--
MiKRO / Mystic Bytes
http://mikro.atari.org
------=_NextPart_000_010B_01CAB9F2.A2765A50--