On Friday 29 December 2023 09:33:52 Pierre Malard wrote:
> Personnellement toutes mes VM tournent sous formatage GPT et sans UEFI mais
> cela ne fait pas de différences. Effectivement il suffit d?une petite
> partition au début d?environ 1 Mo non formatée mais avec le flag
> « bios-grub ».
> Pour
bonjour,
Le ven. 29 déc. 2023 à 09:34, Pierre Malard
a écrit :
>
> Le 28 déc. 2023 à 14:38, ajh-valmer a écrit :
> >
> > Ok, j'attends avec impatience :
> > "le mécanisme d'amorçage compatible avec le mode legacy BIOS".
> > Merci d’avance.
>
> Bonjour,
>
> Personnellement toutes mes VM tournent
Le 28 déc. 2023 à 14:38, ajh-valmer a écrit :
>
>> Le jeu. 28 déc. 2023 à 12:44, ajh-valmer a écrit :
>>> J'ai vérifié, le répertoire /boot contient bien tous les fichiers :
>>> System.map-5.10.0-21-amd64
>>> config-5.10.0-21-amd64
>>> initrd.img-5.10.0-21-amd64
>>> vmlinuz-5.10.0-21-amd64
>>>
> Le jeu. 28 déc. 2023 à 12:44, ajh-valmer a écrit :
> > J'ai vérifié, le répertoire /boot contient bien tous les fichiers :
> > System.map-5.10.0-21-amd64
> > config-5.10.0-21-amd64
> > initrd.img-5.10.0-21-amd64
> > vmlinuz-5.10.0-21-amd64
> > Quid ? Serait-ce le partitionnement 'hd1,gpt1' ?
>
Le jeu. 28 déc. 2023 à 12:44, ajh-valmer a écrit :
>
> Hello,
>
bonjour
>
> J'ai vérifié, le répertoire /boot contient bien tous les fichiers :
> System.map-5.10.0-21-amd64
> config-5.10.0-21-amd64
> initrd.img-5.10.0-21-amd64
> vmlinuz-5.10.0-21-amd64
>
> Quid ? Serait-ce le partitionnement
Hello,
Je reviens sur mon problème de boot.
Il y avait un mauvais UUID dans "grub.cfg".
Ça boote sans problème sur le 1er disque dur sda2 (hd0,msdos2).
Le boot sur le 2ème, sdb1, estampillé set root='hd1,gpt1',
je reçois immédiatement ce message :
"Erreur, /boot/vmlinuz-5.10.0-21-amd64 non
Le 27 décembre 2023 Basile Starynkevitch a écrit :
> Toutefois, sur Debian ou Ubuntu le fichier de configuration de grub (à savoir
> /boot/grub/grub.cfg ) est la plupart du temps généré par l'utilitaire
> grub-mkconfig (un script shell)
En général on utilise la commande update-grub qui
On 12/26/23 14:36, ajh-valmer wrote:
On Monday 25 December 2023 11:08:10 benoit wrote:
Pourquoi Debian et d'autres distributions ont abandonné lilo
au profit de GRUB?
Il me semble (mais à vérifier) que lilo avait ses limites, le secteur
d’amorçage(MBR) ne pouvait s’adresser qu’à une
Le 26/12/2023 à 14:36, ajh-valmer a écrit :
Lilo a été mis de côté pour de bonnes raisons,
mais Grub a beaucoup de défauts.
Le principal est la configuration de partitions qui contiennent
des n° UUID différents à l'intérieur de leur paragraphe concerné :
obligation de corriger ces n° UUID à la
On Monday 25 December 2023 11:08:10 benoit wrote:
> > Pourquoi Debian et d'autres distributions ont abandonné lilo
> > au profit de GRUB?
> Il me semble (mais à vérifier) que lilo avait ses limites, le secteur
> d’amorçage(MBR) ne pouvait s’adresser qu’à une partition primair
Le 24 décembre 2023 Alex PADOLY a écrit :
> Pourquoi Debian et d'autres distributions ont abandonné lilo au profit de
> GRUB?
grub apportait (apporte ?) plus de possibilités. Je crois notamment qu'un
beau boot graphique (avec un logo...) n'était pas possible avec lilo?
Est-ce que ça
Le 24/12/2023 à 05:29, Alex PADOLY a écrit :
Bonjour à tous,
J'ai participé hier à une install party ou nous avons installé la
dernière version de SLACKWARE, j'ai été très surpris que cette
distribution propose comme gestionnaire d'amorçage lilo.
La première version de Debian que j'ai
On 24/12/2023 05:29:44, Alex PADOLY wrote:
> Bonjour à tous,
> J'ai participé hier à une install party ou nous avons installé la
> dernière version de SLACKWARE, j'ai été très surpris que cette
> distribution propose comme gestionnaire d'amorçage lilo.
> La première version de
Bonjour à tous,
J'ai participé hier à une install party ou nous avons installé la
dernière version de SLACKWARE, j'ai été très surpris que cette
distribution propose comme gestionnaire d'amorçage lilo.
La première version de Debian que j'ai installée (Potato) proposait
lilo.
Pourquoi
Fourhundred Thecat <400the...@gmx.ch> writes:
> How can I boot Debian kernel with lilo?
I have a vague memory you may need to specify root option per image in
lilo.conf. From my ancient lilo.conf:
# Jessie stock kernel
image = /boot/vmlinuz-3.16.0-4-amd64
label = "Jessie&quo
Hello,
On Debian 10, I am using custom kernel, with lilo boot loader.
Now I want to boot the default Debian distribution kernel. I have
installed the debian kernel image:
apt-get install linux-image-amd64
and added the entry to /etc/lilo.conf. Now my lilo.conf looks like this:
https
+0300, Michelle Konzack wrote:
> > >> Good day,
> > >>
> > >> I run Stretch on my Laptop with sysvinit.
> > >>
> > >> I had setup some profiles and tried to start them by passing 2, 3,
> > >> 4, 5 at the end of the Kerne
n my Laptop with sysvinit.
> >>
> >> I had setup some profiles and tried to start them by passing 2, 3,
> >> 4, 5 at the end of the Kernel commandline (I use LILO) but the
> >> appropriated runnlevel ist not entered.
> >>
> >> Do I mis someth
2, 3,
>> 4, 5 at the end of the Kernel commandline (I use LILO) but the
>> appropriated runnlevel ist not entered.
>>
>> Do I mis something?
>
> Whatever you did to LILO you did it wrong.
I have this parameter in "append" of each kernel section since ages!
to be mo
Hi.
On Sun, Jun 10, 2018 at 02:25:30PM +0300, Michelle Konzack wrote:
> Good day,
>
> I run Stretch on my Laptop with sysvinit.
>
> I had setup some profiles and tried to start them by passing 2, 3,
> 4, 5 at the end of the Kernel commandline (I use LILO) but
Good day,
I run Stretch on my Laptop with sysvinit.
I had setup some profiles and tried to start them by passing 2, 3,
4, 5 at the end of the Kernel commandline (I use LILO) but the
appropriated runnlevel ist not entered.
Do I mis something?
Since systemd anything is screwed up und nothing
Bill Brelsford wrote:
> Lilo has always met my needs well, so, although I've considered
> grub, I've never felt the need to switch. But it was one of the
> next steps I was considering in this case -- especially if the
> problem turned out to be lilo.
if there was no need grub wou
On Fri Oct 13 2017 at 01:20 AM +0200, deloptes wrote:
> Bill Brelsford wrote:
>
> > This doesn't explain why I got the EBDA message in the first place,
> > but all is working now..
>
> once again the question: why not use grub?
Lilo has always met my needs well, so,
Bill Brelsford wrote:
> This doesn't explain why I got the EBDA message in the first place,
> but all is working now..
once again the question: why not use grub?
On Mon Oct 09 2017 at 12:50 AM +0200, Bill Brelsford wrote:
> After the stretch 9.2 kernel upgrade to 4.9.0-4, lilo gives, at
> boot, "EBDA is big; kernel setup stack overlaps LILO second stage"
> and freezes.
Problem solved. This is a dual-boot system, with the Win 10
bootloa
Bill Brelsford wrote:
> Suggestions?
grub
After the stretch 9.2 kernel upgrade to 4.9.0-4, lilo gives, at
boot, "EBDA is big; kernel setup stack overlaps LILO second stage"
and freezes.
Steps:
- After upgrading, I installed irqbalance before re-booting.
- Lilo then gave "Loading linux" followed
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
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
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
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 lil
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
> >
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
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 were Linux and LinuxOLD). Both work nice
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,
--
es which can be preseeded.
>
> I find Debian documentation to frequently resemble the early _CPM-80
> Manual_. It's all there but finding it can me daunting.
The template files in the udebs are the definitive source for preseed
options. Some of them interact with each, requiring care and testing i
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
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 p
nment" in tasksel, I get an xfce
desktop instead of a gnome3 desktop. Perhaps the boot loader choice could be
handled in a similar fashion. Something like
expert desktop=xfce bootloader=lilo
with the defaults being gnome3 and grub2, respectively.
(Dare I suggest adding initsystem=sys
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
> > ne
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
oles are used. But, strictly speaking, you're right. LILO appends options
supplied on the command line to options specified in the "append" configuration
file statement, it does not replace them.
>
> What I'd like to find which I've had no luck with so far, is finding a Debian
>
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
> of
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
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,
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
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 k
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
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
: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 with more
than just
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 sell
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 eac
; >>>
> >>>>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
t; >>>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
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 don't know what you mean by "update".
If I change the contents o
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
> >>>>tha
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
On Thursday, July 07, 2016 09:03:38 PM David Wright wrote:
> The most modern fdisk program I have is gdisk (for GPT disks) and it
> counts partitions from 1. Is there some newfangled disk subsystem
> that's passed me by which starts counting at zero?
I guess it still confuses me, but maybe I have
> rhkra...@gmail.com composed on 2016-07-07 18:47 (UTC-0400):
> >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 st
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
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
rhkra...@gmail.com composed on 2016-07-07 18:47 (UTC-0400):
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 start counting at 0
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 c
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 c
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
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
but (for me) wonderfully unusable.
>
> Now don't get me wrong: without Grub, my box wouldn't boot, and chances
> are that the "legacy" emulation of whatever monster bios is in there
> is so buggy that Lilo wouldn't cope: therefore I am still full of thanks
> and praise for th
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
most of the files in /etc/grub.d
are not something I would recommend for bedtime reading.
> And please, again: the fact that I disagree with some Grub design
> decisions shouldn't detract from the fact that I have utmost
> respect for the Grub developers and packagers. Their hard work,
&
-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
box wouldn't boot, and chances
are that the "legacy" emulation of whatever monster bios is in there
is so buggy that Lilo wouldn't cope: therefore I am still full of thanks
and praise for the Grub authors for their hard work.
Still I do disagree on many of its design principles.
Regards
- -- to
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.
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 h
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
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
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 &
El 2016-01-08 a las 15:44 -0300, alparkom . escribió:
(rescato y corrijo)
> El día 8 de enero de 2016, 15:41, Camaleón <noela...@gmail.com> escribió:
> > Hola,
> >
> > Pues eso, parece que el desarrollador de LILO deja de hacerse cargo del
> > mantenimiento del g
Hola,
Pues eso, parece que el desarrollador de LILO deja de hacerse cargo del
mantenimiento del gestor de arranque¹.
La verdad es que se trata de uno de esos programas que nunca me he
planteado cambiar, primero porque cuando se es novato lo último que se te
pasa por la cabeza es ponerte
On 23 Apr 2014, at 17:33, Ralf Mardorf ralf.mard...@rocketmail.com wrote:
However, a lot of
experienced Linux users prefer Syslinux.
I'd like to revisit syslinux at some point. It works well on boot USBs etc. Add
my voice to the chorus of folks not happy with grub2.
--
To UNSUBSCRIBE,
other things. With
gui, splash screens, frame-buffers, and all sorts of other gobblty-gook.
I considered going back to LILO, but it still has no understanding of
filesystems: It's easy to bork and hard to fix. Not as hard as Grub 2
though.
Is there a simpler bootloader that works with Linux? I
On 04/23/2014 06:18 PM, Steve Litt wrote:
Now, with grub 2, I need to be an expert on seven or so files that get
processed into one big one, which acts as the config. I don't mind
Hi
You need to edit only one file: /etc/default/grub
Then
update-grub
and it works...
--
Maderios
--
To
1 - 100 of 5649 matches
Mail list logo
