Re: [MiNT] Idea for boot sequence

[Peter Slegg <p.slegg@scubadivers.co.uk>]

On Thu, 16 Dec 2010 10:37:04 -0500, Lonny Pursell <atari@bright.net> wrote:
>
> on 12/16/10 7:10 AM, Jo Even Skarstein wrote:
>
> > As said many times before - if you have several system folders you also
> > have a kernel for each folder. Instead of rebooting the same kernel and
> > attempt to use the system folder from a different version, just boot
> > another kernel with a working system folder. That's much easier and
> > safer, and it can be done today.
>
> I use init, I have 2 possible mint boot sequences, neither use symlinks.  It
> either boots xaaes, or naes and both have access to all partitions.  Seems
> to me this discussion was solved when you informed Peter about easymint and
> its going in a loop now.

No you've got the wrong end of the stick. I've been using Easymint for
6-7 years. There is no problem at this time. I was suggesting a
better solution to boot-up problems that didn't require resorting to
TOS.

>  Just removing the symlinks would solve the
> problems.  No need to hack up the boot sequence further.  It simply depends
> on the kernel I pick in my boot selector as it was intended.
>
If I remove the symlinks, no AES will start This is how Easymint is meant
to work. It relies on ttytab which for convenience uses a symlink so that
you don't have to edit files to change the aes.

console "/usr/bin/aes"  tw52    on secure

Maybe the developers don't see the boot-up going wrong but as a user
it does happen and getting back into a working Mint system can be
a PITA.

Peter