On 01/14/2017 05:38 PM, Stephen Powell wrote:
On Sat, Jan 14, 2017, at 10:05, Richard Owlett wrote:
On 1/14/2017 8:45 AM, Miroslav Skoric wrote:
Hello all,
Intro: I have been using LILO for ages. Now running Wheezy 7.11
LTS. As usual and for test purposes on older machines I have two
kernel fl
On Wed, Jan 18, 2017, at 20:49, Stephen Powell wrote:
>
> ...
> The first two "image" entries define the standard "most recent" and
> "next-most recent" kernels and don't need to be messed with, provided
> that the standard symbolic link names are being maintained by
> "do_symlinks = yes" in /etc/
On Wed, Jan 18, 2017, at 20:49, Stephen Powell wrote:
> ...
> One such program, memtest86+, provides a stand-alone memory testing
> program built to resemble a Linux kernel, so that Linuxboot loaders
> think it is a Linux kernel and will load it like one (the entire boot image is
> loaded, not just
On Sat, Jan 14, 2017, at 11:38, Stephen Powell wrote:
>
> If there are special kernels that you want to be able to boot which are
> outside
> the normal "last two", then you must manually edit /etc/lilo.conf to provide
> the capability to boot this kernel, then run lilo.
>
As an example, here is
On Sat, Jan 14, 2017, at 10:05, Richard Owlett wrote:
> On 1/14/2017 8:45 AM, Miroslav Skoric wrote:
> > Hello all,
> >
> > Intro: I have been using LILO for ages. Now running Wheezy 7.11
> > LTS. As usual and for test purposes on older machines I have two
> > kernel flavours: 486 and 686-rt. In LI
On 1/14/2017 8:45 AM, Miroslav Skoric wrote:
Hello all,
Intro: I have been using LILO for ages. Now running Wheezy 7.11
LTS. As usual and for test purposes on older machines I have two
kernel flavours: 486 and 686-rt. In LILO boot menu they appear as
Linux486 and Linux686 (before renaming they w
6 matches
Mail list logo
