Re: [MiNT] Idea for boot sequence

[Jo Even Skarstein <joska@online.no>]

On Wed, 2010-12-15 at 22:56 +0000, Alan Hourihane wrote:
> > If the sym link in /usr/bin is still pointing to xaloader then it is not
> > possible to start 1.15.12 and NAES then I have to start the farce of
> > booting in TOS editing mint.cnf to boot to a shell. Rebooting in Mint
> > so I can delete the symlink. Reboot, etc. etc.
> 
> Eh? So you've just broke your stable mint.cnf ??
> 
> > So why not take advantage of the optional Mint folders and make them
> > available when the Mint kernel loads ? Why rely on the hard-coded folder
> > being perfect ?  I hate hard-coded stuff like this.
> 
> It's hard coded for safety. So if your "stable" 1.15.x release has a
> nice and unmodified mint.cnf - where's the problem ?
> 
> If you broke a symlink then fix it, as if you mint.cnf's are all the
> same no matter which kernel you boot, you've broken it. xaloader should
> be in C:\MINT\1-17-0\XAAES\XALOADER.PRG anyway and your mint.cnf should
> point to that, so I'm not sure why you are using symlinks. 

That's because Peter is using EasyMiNT, which symlinks xaloader.prg
to /usr/bin. Then the symlink is referenced in ttytab. The idea is most
likely that you can easily select which xaaes to load by updating the
symlink. In reality it prevents you from easily booting different
versions of the kernel.

I personally don't use init, I start xaaes directly from mint.cnf. So
for me this is not a problem. If you use init and start xaaes
automatically from it, the symlink or ttytab must be updated whenever
you switch between kernel versions. It can easily be done by creating
the correct symlink in mint.cnf. That would solve the problem - booting
from a different system folder wont ;)

Jo Even