On Wednesday, 23 October 2019 17:21:50 BST Neil Bothwick wrote:
> On Wed, 23 Oct 2019 15:18:45 +0100, Peter Humphrey wrote:
> > > Yes. It also updates symlinks to all three if you are already using
> > > symlinks.
> >
> > Make install doesn't use symlinks here. This is a UEFI box with /boot
> >
On Wed, 23 Oct 2019 15:18:45 +0100, Peter Humphrey wrote:
> > Yes. It also updates symlinks to all three if you are already using
> > symlinks.
>
> Make install doesn't use symlinks here. This is a UEFI box with /boot
> formatted FAT32, so the three files are copied, not linked to.
"if you
On Tuesday, 22 October 2019 21:34:53 BST Neil Bothwick wrote:
> On Tue, 22 Oct 2019 20:35:27 +0100, Mick wrote:
> > > If I trust the makefile to build the entire operating system kernel,
> > > build all the modules it needs and copy all those modules to the
> > > correct locations, I don't see why
On Tuesday, 22 October 2019 21:34:53 BST Neil Bothwick wrote:
> On Tue, 22 Oct 2019 20:35:27 +0100, Mick wrote:
> > > If I trust the makefile to build the entire operating system kernel,
> > > build all the modules it needs and copy all those modules to the
> > > correct locations, I don't see why
On Tue, 22 Oct 2019 20:35:27 +0100, Mick wrote:
> > If I trust the makefile to build the entire operating system kernel,
> > build all the modules it needs and copy all those modules to the
> > correct locations, I don't see why I can't let it copy one more file
> > to /boot.
>
> I've
On Tuesday, 22 October 2019 14:42:44 BST Neil Bothwick wrote:
> On Tue, 22 Oct 2019 03:33:24 -0500, Dale wrote:
> > If one of those should stop working or I buy something new and need to
> > add support for it, the new kernel will have a -2 on the end instead of
> > -1. I'm not sure on the
Neil Bothwick wrote:
> On Tue, 22 Oct 2019 09:29:01 -0500, Dale wrote:
>
>>> If I trust the makefile to build the entire operating system kernel,
>>> build all the modules it needs and copy all those modules to the
>>> correct locations, I don't see why I can't let it copy one more file
>>> to
On Tue, 22 Oct 2019 09:29:01 -0500, Dale wrote:
> > If I trust the makefile to build the entire operating system kernel,
> > build all the modules it needs and copy all those modules to the
> > correct locations, I don't see why I can't let it copy one more file
> > to /boot.
> Thing is, I
Neil Bothwick wrote:
> On Tue, 22 Oct 2019 03:33:24 -0500, Dale wrote:
>
>> If one of those should stop working or I buy something new and need to
>> add support for it, the new kernel will have a -2 on the end instead of
>> -1. I'm not sure on the -gentoo one. Thing is, I can boot the old
>>
On Tue, 22 Oct 2019 03:33:24 -0500, Dale wrote:
> If one of those should stop working or I buy something new and need to
> add support for it, the new kernel will have a -2 on the end instead of
> -1. I'm not sure on the -gentoo one. Thing is, I can boot the old
> kernel of that version or even
On Tue, 22 Oct 2019 10:42:14 +0100, Mick wrote:
> > I haven't used the symlink approach for some time. I use a script to
> > generate the entries for GRUB or systemd-boot. As I use a script to
> > build and install the kernel in the first place, there are no extra
> > steps as one script calls
On Tuesday, 22 October 2019 10:09:53 BST Neil Bothwick wrote:
> On 22 October 2019 08:58:01 BST, Mick wrote:
> >With manual copying/naming of kernels I can overwrite any non-booting
> >kernels
> >with the latest compiled example, without moving links around. What is
> >the
> >recommended
On 22 October 2019 08:58:01 BST, Mick wrote:
>On Tuesday, 22 October 2019 00:44:00 BST Neil Bothwick wrote:
>> On Tue, 22 Oct 2019 00:42:25 +0100, Neil Bothwick wrote:
>> > make install will create symlinks for vmlinuz and vmlinuz.old to
>the
>> > latest and previous kernel, doing much of what
Mick wrote:
> On Tuesday, 22 October 2019 00:44:00 BST Neil Bothwick wrote:
>> On Tue, 22 Oct 2019 00:42:25 +0100, Neil Bothwick wrote:
>>> make install will create symlinks for vmlinuz and vmlinuz.old to the
>>> latest and previous kernel, doing much of what you need. You need /boot
>>> to be on
On Tuesday, 22 October 2019 00:44:00 BST Neil Bothwick wrote:
> On Tue, 22 Oct 2019 00:42:25 +0100, Neil Bothwick wrote:
> > make install will create symlinks for vmlinuz and vmlinuz.old to the
> > latest and previous kernel, doing much of what you need. You need /boot
> > to be on a filesystem
On Tue, 22 Oct 2019 00:42:25 +0100, Neil Bothwick wrote:
> make install will create symlinks for vmlinuz and vmlinuz.old to the
> latest and previous kernel, doing much of what you need. You need /boot
> to be on a filesystem that supports symlinks and ISTR that it only
> updates the symlinks if
On Mon, 21 Oct 2019 22:54:26 +, Caveman Al Toraboran wrote:
> you are just wrongly assuming that they are mutually
> exclusive...
>
> seriously, one could have kernels named,
> without versions, as:
>
> vmlinuz
> vmlinuz-older
> vmlinuz-older2
> .
> .
> .
> vmlinuz-olderN
>
> this way, new
you are just wrongly assuming that they are mutually
exclusive...
seriously, one could have kernels named,
without versions, as:
vmlinuz
vmlinuz-older
vmlinuz-older2
.
.
.
vmlinuz-olderN
this way, new kernel installation, and rotation,
will be decoupled from the boot loader's configs,
On 18/10/19 10:26, Caveman Al Toraboran wrote:
> specifically, i want to install kernel + initramfs without version
> numbers. this way, i will not need to update my boot loader every time
> i update the kernel.
>
You just want a nasty recovery job if the update screws up ...
Seriously, I
On Friday, 18 October 2019 14:02:58 BST Caveman Al Toraboran wrote:
> what one doesn't use grub?
I don't, for one. Oh, except for grub-legacy on an old 32-bit, single-core
atom box. I won't touch grub-2 for love nor money.
--
Regards,
Peter.
On Fri, Oct 18, 2019 at 9:02 AM Caveman Al Toraboran
wrote:
>
> what one doesn't use grub?
>
None that I'm aware of, but I use grub so I haven't gone looking.
Like I said, I used to do it this way and get why, but since doing it
the new grub way has made my life easier than fighting it with
what one doesn't use grub?
rgrds,
cm.
‐‐‐ Original Message ‐‐‐
On Friday, October 18, 2019 3:36 PM, Rich Freeman wrote:
> On Fri, Oct 18, 2019 at 6:51 AM Alexander Openkowski
> opn...@googlemail.com wrote:
>
> > I struggle with the naming of genkernel generated kernels for quite a
On Fri, Oct 18, 2019 at 6:51 AM Alexander Openkowski
wrote:
>
> I struggle with the naming of genkernel generated kernels for quite a while
> now and have written a small wapper script for this purpose...
>
Somebody else shared the same problem and wrote a fairly complex
wrapper, and it is
I struggle with the naming of genkernel generated kernels for quite a while
now and have written a small wapper script for this purpose...
On Fri, Oct 18, 2019 at 11:27 AM Caveman Al Toraboran <
toraboracave...@protonmail.com> wrote:
> specifically, i want to install kernel + initramfs without
specifically, i want to install kernel + initramfs without version numbers.
this way, i will not need to update my boot loader every time i update the
kernel.
rgrds,
cm.
25 matches
Mail list logo
