There has been some mention of booting UEFI systems in
this thread. This appears to be a comprehensive resource:
http://www.rodsbooks.com/efi-bootloaders/index.html
Many bootloaders are covered, and the author also
mentions his own project, rEFInd
http://www.rodsbooks.com/refind/
cheers,
--
On Sun 10 Jul 2016 at 08:38:15 -0500, Richard Owlett wrote:
> On 7/9/2016 4:00 PM, Stephen Powell wrote:
> >[snip]
> >>What I'd like to find which I've had no luck with so far, is finding a
> >>Debian
> >>installer cmdline option to skip the waste of time that is installation of
> >>any
On 7/9/2016 4:00 PM, Stephen Powell wrote:
[snip]
What I'd like to find which I've had no luck with so far, is finding a Debian
installer cmdline option to skip the waste of time that is installation of
any bootloader. My disks get generic MBR code and Grub installed by me before
any OS gets
On Sun, Jul 10, 2016, at 03:31, Pascal Hambourg wrote:
>
> AFAICS, elilo is not available any more in stretch and sid.
>
I'm sorry to hear that. I don't have any UEFI-based systems right now, so
it's not an issue for me -- yet. But it may be someday. On the other hand,
CSM-less UEFI systems
On Sun 10 Jul 2016 at 10:31:38 +0200, to...@tuxteam.de wrote:
> On Sat, Jul 09, 2016 at 11:15:08PM +0100, Brian wrote:
>
> [...]
>
> > This is a common misconception. Debian is about providing the best free
> > operating system possible.
>
> In your humble opinion.
>
> (sorry, I know I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Jul 09, 2016 at 11:15:08PM +0100, Brian wrote:
[...]
> This is a common misconception. Debian is about providing the best free
> operating system possible.
In your humble opinion.
(sorry, I know I'm feeding it, but I couldn't resist).
-
Le 09/07/2016 à 22:41, Stephen Powell a écrit :
So I'm not concerned about it's maintenance status. As long as there are
PCs with a BIOS, or a CSM, lilo will remain usable. If the BIOS/CSM goes,
lilo goes with it. lilo can't function without a BIOS/CSM. But for UEFI-only
systems, there's
Le 09/07/2016 à 22:00, Brian a écrit :
All well and good but the installer inexplicably offers a choice between
GRUB and LILO. The installer manual is unhelpful on which to choose. A
newcomer wouldn't have a clue. We do them no service with this retrograde
offering. Get rid of it.
What is the
Stephen Powell wrote:
> As far as LILO being unmaintained is concerned, I wouldn't be too concerned
> about that. I've been thinking about offering to maintain it myself. I
> haven't
> heard from Joachim lately. Maybe I'll drop him another line.
I think LILO is an important part of Linux
On Sat, Jul 9, 2016, at 18:25, Brian wrote:
> On Sat 09 Jul 2016 at 16:41:24 -0400, Stephen Powell wrote:
>>
>> Long live choice!
>
> For choice to exist it does not have to be presented as such in the
> installer.
>
Your point is well taken. The installer does not offer choice in everything,
Brian composed on 2016-07-09 21:00 (UTC+0100):
...the installer inexplicably offers a choice between
GRUB and LILO. The installer manual is unhelpful on which to choose. A
newcomer wouldn't have a clue. We do them no service with this retrograde
offering. Get rid of it.
Probably a Bad idea.
On Sat 09 Jul 2016 at 16:41:24 -0400, Stephen Powell wrote:
> On Sat, Jul 9, 2016, at 16:00, Brian wrote:
> >
> > All well and good but the installer inexplicably offers a choice between
> > GRUB and LILO. The installer manual is unhelpful on which to choose. A
> > newcomer wouldn't have a clue.
On Sat 09 Jul 2016 at 22:05:45 +0200, Erwan David wrote:
> Le 09/07/2016 à 22:00, Brian a écrit :
> >
> > What is the point of a choice? Just offer GRUB; it is the bootloader for
> > Debian and has many advantages over LILO in todayss Linux ecosystem.
> > People who have a great desire to use
On Sat, Jul 9, 2016, at 16:33, Felix Miata wrote:
>
> All that's well and good, but I see nothing there that equates to my
> understanding of the meaning of "editing", which includes removal as well as
> appending.
Oh, I see what you're saying. Well, the Linux kernel generally does it's own
On Sat, Jul 9, 2016, at 16:00, Brian wrote:
>
> All well and good but the installer inexplicably offers a choice between
> GRUB and LILO. The installer manual is unhelpful on which to choose. A
> newcomer wouldn't have a clue. We do them no service with this retrograde
> offering. Get rid of it.
Erwan David composed on 2016-07-09 22:05 (UTC+0200):
Brian composed:
What is the point of a choice? Just offer GRUB; it is the bootloader for
Debian...
What is the point of a choice, just use the windows provided with your PC...
:-D
Linux and debian is just about choice given to the
Stephen Powell composed on 2016-07-09 13:19 (UTC-0400):
Felix Miata wrote:
Stephen Powell composed on 2016-07-09 08:58 (UTC-0400):
As for features, LILO has all the features that I need.
One feature it never acquired AFAIK, which Grub shares with Syslinux, is the
Le 09/07/2016 à 22:00, Brian a écrit :
>
> What is the point of a choice? Just offer GRUB; it is the bootloader for
> Debian and has many advantages over LILO in todayss Linux ecosystem.
> People who have a great desire to use LILO can search it out.
>
> Unmaintained in Debian, The bit-rot starts
On Sat 09 Jul 2016 at 13:19:08 -0400, Stephen Powell wrote:
> On Sat, Jul 9, 2016, at 10:53, Felix Miata wrote:
> > Stephen Powell composed on 2016-07-09 08:58 (UTC-0400):
> >
> >> As for features, LILO has all the features that I need.
> >
> > One feature it never acquired AFAIK, which Grub
On Sat, Jul 9, 2016, at 10:53, Felix Miata wrote:
> Stephen Powell composed on 2016-07-09 08:58 (UTC-0400):
>
>> As for features, LILO has all the features that I need.
>
> One feature it never acquired AFAIK, which Grub shares with Syslinux, is the
> ability to edit the kernel cmdline at boot
Stephen Powell composed on 2016-07-09 08:58 (UTC-0400):
As for features, LILO has all the features that I need.
One feature it never acquired AFAIK, which Grub shares with Syslinux, is the
ability to edit the kernel cmdline at boot time, before kernel load. With
problematic hardware,
On Thu, Jul 7, 2016, at 20:53, Felix Miata wrote:
> Stephen Powell composed on 2016-07-07 20:30 (UTC-0400):
>
> > If your system has a BIOS and a traditional DOS-style partition table,
> > there's no reason not to use LILO, unless you just don't want to.
>
> Or, if you like to be able to boot
On 08/07/16 07:06 PM, Brian wrote:
On Fri 08 Jul 2016 at 18:13:01 -0400, Gary Dale wrote:
On 08/07/16 02:19 PM, Brian wrote:
If you have some way of easily adjusting files in /etc/grub.d to the
needs of a user I wish you would say.
So that's the problem. You never took the time to RTFM. See
On Fri 08 Jul 2016 at 18:13:01 -0400, Gary Dale wrote:
> >>On 08/07/16 02:19 PM, Brian wrote:
> >
> >If you have some way of easily adjusting files in /etc/grub.d to the
> >needs of a user I wish you would say.
> So that's the problem. You never took the time to RTFM. See
>
On Fri 08 Jul 2016 at 16:57:30 -0500, David Wright wrote:
> On Fri 08 Jul 2016 at 21:16:00 (+0100), Brian wrote:
>
> > Stop moaning. Do it or file file a bug, Then stop moaning and do it.
>
> I'm the person without a complaint about Grub2, not the one moaning.
Apologies. I was intending to
On 08/07/16 03:51 PM, Brian wrote:
On Fri 08 Jul 2016 at 15:08:21 -0400, Gary Dale wrote:
On 08/07/16 02:19 PM, Brian wrote:
On Thu 07 Jul 2016 at 23:34:11 -0400, Gary Dale wrote:
On 07/07/16 05:12 PM, Brian wrote:
On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote:
On 07/07/16
On Fri 08 Jul 2016 at 21:16:00 (+0100), Brian wrote:
> On Fri 08 Jul 2016 at 14:23:01 -0500, David Wright wrote:
> > On Fri 08 Jul 2016 at 19:19:00 (+0100), Brian wrote:
> > > On Thu 07 Jul 2016 at 23:34:11 -0400, Gary Dale wrote:
> > > > On 07/07/16 05:12 PM, Brian wrote:
> > > > >On Thu 07 Jul
On Fri 08 Jul 2016 at 14:23:01 -0500, David Wright wrote:
> On Fri 08 Jul 2016 at 19:19:00 (+0100), Brian wrote:
> > On Thu 07 Jul 2016 at 23:34:11 -0400, Gary Dale wrote:
> > > On 07/07/16 05:12 PM, Brian wrote:
> > > >On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote:
> > > >>On 07/07/16
On Fri 08 Jul 2016 at 15:08:21 -0400, Gary Dale wrote:
> On 08/07/16 02:19 PM, Brian wrote:
> >On Thu 07 Jul 2016 at 23:34:11 -0400, Gary Dale wrote:
> >
> >>On 07/07/16 05:12 PM, Brian wrote:
> >>>On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote:
> >>>
> On 07/07/16 02:55 PM, David
On Fri 08 Jul 2016 at 19:19:00 (+0100), Brian wrote:
> On Thu 07 Jul 2016 at 23:34:11 -0400, Gary Dale wrote:
> > On 07/07/16 05:12 PM, Brian wrote:
> > >On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote:
> > >>On 07/07/16 02:55 PM, David Wright wrote:
> > >>>On Thu 07 Jul 2016 at 14:39:51
On 08/07/16 02:19 PM, Brian wrote:
On Thu 07 Jul 2016 at 23:34:11 -0400, Gary Dale wrote:
On 07/07/16 05:12 PM, Brian wrote:
On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote:
On 07/07/16 02:55 PM, David Wright wrote:
On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote:
The big
On Thu 07 Jul 2016 at 23:34:11 -0400, Gary Dale wrote:
> On 07/07/16 05:12 PM, Brian wrote:
> >On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote:
> >
> >>On 07/07/16 02:55 PM, David Wright wrote:
> >>>On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote:
> The big selling feature of
Gary Dale composed on 2016-07-07 14:39 (UTC-0400):
It also has a "rescue shell" that I've never been able to do anything
useful with. When grub fails, I boot from a rescue cd instead. That way
I get a real working environment.
The Grub shell works the same whether in boot rescue mode or run
On 07/07/16 05:12 PM, Brian wrote:
On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote:
On 07/07/16 02:55 PM, David Wright wrote:
On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote:
The big selling feature of Grub over Lilo was that it didn't need to
updated each time you changed
Stephen Powell composed on 2016-07-07 20:30 (UTC-0400):
If your system has a BIOS and a traditional DOS-style partition table,
there's no reason not to use LILO, unless you just don't want to.
Or, if you like to be able to boot without hunting down rescue media even
though you forgot to
On Thu, Jul 7, 2016, at 10:57, Giovanni Gigante wrote:
>
> At the end, I decided to try the upgrade to jessie with LiLo (24.1) in
> place. I thought that the probability of hitting some bug caused by the
> interaction between LiLo and the upgraded distribution was less than the
> probabily of
On 07/07/2016 05:47 PM, rhkra...@gmail.com wrote:
I'll take advantage of this thread to ask a question / express my frustration
with grub:
The thing that always frustrated me about grub is that, iirc, they counted
disks / partitions different than lilo and the rest of Linux--they start
On 07/07/2016 05:47 PM, rhkra...@gmail.com wrote:
I'll take advantage of this thread to ask a question / express my frustration
with grub:
The thing that always frustrated me about grub is that, iirc, they counted
disks / partitions different than lilo and the rest of Linux--they start
I'll take advantage of this thread to ask a question / express my frustration
with grub:
The thing that always frustrated me about grub is that, iirc, they counted
disks / partitions different than lilo and the rest of Linux--they start
counting at 1 (like Windows, iirc), and lilo and Linux
On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote:
> On 07/07/16 02:55 PM, David Wright wrote:
> >On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote:
> >>The big selling feature of Grub over Lilo was that it didn't need to
> >>updated each time you changed something. That fell by the
On 07/07/2016 01:55 PM, David Wright wrote:
On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote:
The big selling feature of Grub over Lilo was that it didn't need to
updated each time you changed something. That fell by the wayside
with Grub 2. Now the big selling feature is that it works
On Thu 07 Jul 2016 at 15:18:05 (-0400), Gary Dale wrote:
> On 07/07/16 02:55 PM, David Wright wrote:
> >On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote:
> >>The big selling feature of Grub over Lilo was that it didn't need to
> >>updated each time you changed something. That fell by the
On 07/07/16 02:55 PM, David Wright wrote:
On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote:
The big selling feature of Grub over Lilo was that it didn't need to
updated each time you changed something. That fell by the wayside
with Grub 2. Now the big selling feature is that it works
On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote:
> The big selling feature of Grub over Lilo was that it didn't need to
> updated each time you changed something. That fell by the wayside
> with Grub 2. Now the big selling feature is that it works with more
> than just Linux.
I guess I
On 05/07/16 09:38 AM, Giovanni Gigante wrote:
Hello,
I am preparing my system for the upgrade from wheezy to jessie.
Since ancient ages, this system has been using LILO as the bootloader,
because, long ago, it was the only bootloader that was recommended for
my setup: this machine has two
On Thu 07 Jul 2016 at 08:33:57 (+0200), to...@tuxteam.de wrote:
> On Wed, Jul 06, 2016 at 02:23:39PM -0500, Don Armstrong wrote:
> > On Wed, 06 Jul 2016, Jonathan Dowland wrote:
> > > YMMV, I find it impenetrable.
> >
> > I'm assuming you mean the generated configuration? It's literally just
> >
Brian wrote:
Giovanni Gigante seems happy enough with LiLo and there appears to be
no definite indication that it would fail to boot an upgraded machine.
He could consider leaving it in place, reading the bug reports and
having a plan to install GRUB should something go wrong afterwards.
At
On Thu 07 Jul 2016 at 12:44:40 +0200, to...@tuxteam.de wrote:
> On Thu, Jul 07, 2016 at 11:32:42AM +0100, Brian wrote:
> > On Thu 07 Jul 2016 at 10:35:47 +0100, Lisi Reisz wrote:
> >
> > > On Thursday 07 July 2016 07:33:57 to...@tuxteam.de wrote:
> > > > Let's make it (GRUB2) impenetrable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jul 07, 2016 at 11:32:42AM +0100, Brian wrote:
> On Thu 07 Jul 2016 at 10:35:47 +0100, Lisi Reisz wrote:
>
> > On Thursday 07 July 2016 07:33:57 to...@tuxteam.de wrote:
> > > Let's make it (GRUB2) impenetrable boilerplate, then.
> >
> > :-)
On Thu 07 Jul 2016 at 10:35:47 +0100, Lisi Reisz wrote:
> On Thursday 07 July 2016 07:33:57 to...@tuxteam.de wrote:
> > Let's make it (GRUB2) impenetrable boilerplate, then.
>
> :-) +1!
It doesn't need to be penetrable, does it? The generated grub.cfg just
needs to boot the machine. In any
On Thursday 07 July 2016 07:33:57 to...@tuxteam.de wrote:
> Let's make it (GRUB2) impenetrable boilerplate, then.
:-) +1!
Lisi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Jul 06, 2016 at 02:23:39PM -0500, Don Armstrong wrote:
> On Wed, 06 Jul 2016, Jonathan Dowland wrote:
> > YMMV, I find it impenetrable.
>
> I'm assuming you mean the generated configuration? It's literally just
> some boilerplate [...]
Let's
On Wed, 06 Jul 2016, Jonathan Dowland wrote:
> YMMV, I find it impenetrable.
I'm assuming you mean the generated configuration? It's literally just
some boilerplate for fancy splash screens, and then menu entries. Each
entry containing appropriate module loading, root configuration, kernel
and
On Tue, Jul 05, 2016 at 04:46:32PM -0500, Don Armstrong wrote:
> On Tue, 05 Jul 2016, Marc Shapiro wrote:
> > I finally switched to Jessie (but still using SysV Init) a few months
> > ago. This box and its predecessors have uses lilo (and SysV Init)
> > since Bo was a pup. I have yet to see any
On Tue, 05 Jul 2016, Marc Shapiro wrote:
> I finally switched to Jessie (but still using SysV Init) a few months
> ago. This box and its predecessors have uses lilo (and SysV Init)
> since Bo was a pup. I have yet to see any real reason to switch from
> lilo to grub. I have never had a problem
On 07/05/2016 10:10 AM, Don Armstrong wrote:
On Tue, 05 Jul 2016, Giovanni Gigante wrote:
I am preparing my system for the upgrade from wheezy to jessie.
Since ancient ages, this system has been using LILO as the bootloader,
because, long ago, it was the only bootloader that was recommended for
On Tue, 05 Jul 2016, Giovanni Gigante wrote:
> I am preparing my system for the upgrade from wheezy to jessie.
> Since ancient ages, this system has been using LILO as the bootloader,
> because, long ago, it was the only bootloader that was recommended for my
> setup: this machine has two SATA
Hello,
I am preparing my system for the upgrade from wheezy to jessie.
Since ancient ages, this system has been using LILO as the bootloader,
because, long ago, it was the only bootloader that was recommended for
my setup: this machine has two SATA disks in a software RAID 1 & LVM;
that is,
58 matches
Mail list logo
