Andrea Borgia wrote:
> Hi.
>
> AFAIK the following symlinks in "/" were required for LILO and are no
> longer needed with GRUB2:
> initrd.img
> initrd.img.old
> vmlinuz
> vmlinuz.old
>
> Is there a reason for keeping them around nowadays?
i use refind to boot via UEFI and those links are
nice t
On Sun 26 May 2019 at 14:57:57 +0200, Andrea Borgia wrote:
> Il 26/05/19 00:19, Brian ha scritto:
>
> > Booting from a GRUB prompt can be a little easier when you know that
> > the kernel and initrd can be reached from /.
>
> In those cases where the system doesn't boot on its own, I dig out the
Il 26/05/19 00:19, Brian ha scritto:
Booting from a GRUB prompt can be a little easier when you know that
the kernel and initrd can be reached from /.
In those cases where the system doesn't boot on its own, I dig out the
USB drive where I keep the ISOs and run from there.
It's rare enough
Il 25/05/19 19:24, Sven Joachim ha scritto:
If you stick to grub, not really. You can safely delete them, and use
do_symlinks = 0
in /etc/kernel-img.conf so that they will not come back.
Thanks, I've just done as you suggested :)
On Sat 25 May 2019 at 18:16:17 +0200, Andrea Borgia wrote:
> Hi.
>
> AFAIK the following symlinks in "/" were required for LILO and are no longer
> needed with GRUB2:
> initrd.img
> initrd.img.old
> vmlinuz
> vmlinuz.old
>
> Is there a reason for keeping them around nowadays?
Booting from a GRU
On 2019-05-25 18:16 +0200, Andrea Borgia wrote:
> AFAIK the following symlinks in "/" were required for LILO and are no
> longer needed with GRUB2:
> initrd.img
> initrd.img.old
> vmlinuz
> vmlinuz.old
>
> Is there a reason for keeping them around nowadays?
If you stick to grub, not really. You
Hi.
AFAIK the following symlinks in "/" were required for LILO and are no
longer needed with GRUB2:
initrd.img
initrd.img.old
vmlinuz
vmlinuz.old
Is there a reason for keeping them around nowadays?
Thanks,
Andrea.
On Mon, 9 Jun 2003, Colin Watson wrote:
>On Mon, Jun 09, 2003 at 06:03:21PM +0200, David List wrote:
>> I have built a new kernel with make-kpkg and installed it with
>> dpkg -i .deb
>> I then checked /boot and saw that the vmlinuz symlink there still points
>> to the old kernel, whereas the vmlin
On Mon, Jun 09, 2003 at 06:03:21PM +0200, David List wrote:
> I have built a new kernel with make-kpkg and installed it with
> dpkg -i .deb
> I then checked /boot and saw that the vmlinuz symlink there still points
> to the old kernel, whereas the vmlinuz symlink under / points to the
> recently in
I have built a new kernel with make-kpkg and installed it with
dpkg -i .deb
I then checked /boot and saw that the vmlinuz symlink there still points
to the old kernel, whereas the vmlinuz symlink under / points to the
recently installed kernel.
Why is there a vmlinuz symlink under /boot if it not
10 matches
Mail list logo
