On 2019-01-14 20:20:49 +0100, Pascal Hambourg wrote:
> Le 14/01/2019 à 11:09, Vincent Lefevre a écrit :
> > On 2019-01-14 11:06:01 +0100, Vincent Lefevre wrote:
> > > On 2019-01-08 20:12:43 +0100, Pascal Hambourg wrote:
> > > > This issue is not specific to lilo. It would affect grub-pc updates too
Le 14/01/2019 à 11:09, Vincent Lefevre a écrit :
On 2019-01-14 11:06:01 +0100, Vincent Lefevre wrote:
On 2019-01-08 20:12:43 +0100, Pascal Hambourg wrote:
This issue is not specific to lilo. It would affect grub-pc updates too,
because the boot device is specified by device id.
For example on
On 2019-01-14 11:06:01 +0100, Vincent Lefevre wrote:
> On 2019-01-08 20:12:43 +0100, Pascal Hambourg wrote:
> > This issue is not specific to lilo. It would affect grub-pc updates too,
> > because the boot device is specified by device id.
> >
> > For example on my system :
> > $ debconf-show grub
On 2019-01-08 20:12:43 +0100, Pascal Hambourg wrote:
> This issue is not specific to lilo. It would affect grub-pc updates too,
> because the boot device is specified by device id.
>
> For example on my system :
> $ debconf-show grub-pc
> (...)
> * grub-pc/install_devices: /dev/disk/by-id/ata-WDC_
On 2019-01-06 10:30:26 +, Johan en Katrien Dewaele wrote:
> Hi,
>
> my weekly upgrade on testing failed yesterday as, after an initrd.img was
> generated, lilo could not run successfully.
>
>
> After checking my /etc/lilo.conf, where I had my boot disk identified by ID
> as :
>
>
> "boo
Le 08/01/2019 à 12:51, Johan en Katrien Dewaele a écrit :
Only the location of my boot-disk is identified by "ID" in lilo, seems
it is not possible to do this by UUID in lilo.
I wrote previously in this thread :
This is because the UUID is only part of filesystem metadata and cannot
be used
Johan en Katrien Dewaele wrote:
> Thinking of switching to grub2 to avoid these problems.
>
good thinking
songbird wrote:
> first thing i would try is to go back to the previous
> known working kernel via dpkg (not apt) and see if that
> succeeds in installing and generating an initramfs.
don't underestimate udev - AFAIK it is responsible for those names and it
fall recently to systemd, so that you c
David Wright wrote:
> On Sun 06 Jan 2019 at 10:30:26 (+), Johan en Katrien Dewaele wrote:
>> my weekly upgrade on testing failed yesterday as, after an initrd.img was
>> generated, lilo could not run successfully.
>> After checking my /etc/lilo.conf, where I had my boot disk identified by ID
On Sun 06 Jan 2019 at 10:30:26 (+), Johan en Katrien Dewaele wrote:
> my weekly upgrade on testing failed yesterday as, after an initrd.img was
> generated, lilo could not run successfully.
> After checking my /etc/lilo.conf, where I had my boot disk identified by ID
> as :
> "boot=/dev/disk
Le 06/01/2019 à 14:35, songbird a écrit :
i don't mount by ids, i mount by labels, but in looking
at the doc for lilo.conf i see that it should also be
possible to use UUIDs too.
No, UUIDs and LABELs cannot be used to specify a whole partitioned disk
as the boot device because they are fil
Le 06/01/2019 à 14:35, songbird a écrit :
Johan en Katrien Dewaele wrote:
my weekly upgrade on testing failed yesterday as,=C2=A0 after an initrd.img=
was generated, lilo could not run successfully.
i can't help with lilo, haven't used that in ages...
This issue is not specific to lilo
Johan en Katrien Dewaele wrote:
> Hi,
>
> my weekly upgrade on testing failed yesterday as,=C2=A0 after an initrd.img=
> was generated, lilo could not run successfully.
hi,
i can't help with lilo, haven't used that in ages...
i don't mount by ids, i mount by labels, but in looking
at the d
13 matches
Mail list logo
