linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hunter Chasens <hunter.chasens18@ncf.edu>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] docs: admin-guide: Update bootloader and installation instructions
Date: Fri, 24 Nov 2023 21:42:32 -0500	[thread overview]
Message-ID: <6005603.lOV4Wx5bFT@lux> (raw)
In-Reply-To: <87leanw0ms.fsf@meer.lwn.net>

[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]

On Friday, November 24, 2023 11:56:43 AM EST you wrote:

> But the makefile is looking for "installkernel", right?  Unless I'm
> missing something, that's the one that will work with "make install". ?

The `make install` calls `/scripts/install.sh`. `/scripts/install.sh` uses 
a variable called $INSTALLKERNEL to search a few directories. If it can't 
find what it's looking for it searches for an `install.sh` script in 
srctree/arch/$arch/. `kernel-install` is part of the systemd stack, and can 
be invoked as `installkernel`. It gets invoked as installkernel during 
`make install` through some wizardry I'm not super familiar with. I guess 
it's more of an install binary than an install script, but there's no 
`installkernel.sh` on many current distributions. Just programs that 
pretend to be `installkernel.sh` which might confuse a user looking for 
such a script.

I suppose it would be more accurate to say something like: "It is also 
possible to do `make install` if you have lilo installed or if your 
distribution has an installer compatible with the kernel's makefile."

Thank you for your feedback,
    Hunter




[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      parent reply	other threads:[~2023-11-25  2:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14  3:02 [PATCH v3 1/2] docs: admin-guide: Update bootloader and installation instructions Hunter Chasens
2023-11-14  3:02 ` [PATCH v3 2/2] docs: admin-guide: Adds explicit target to EFI-Stub doc Hunter Chasens
2023-11-17 16:17 ` [PATCH v3 1/2] docs: admin-guide: Update bootloader and installation instructions Jonathan Corbet
     [not found] ` <4525208.LvFx2qVVIh@lux>
     [not found]   ` <87leanw0ms.fsf@meer.lwn.net>
2023-11-25  2:42     ` Hunter Chasens [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6005603.lOV4Wx5bFT@lux \
    --to=hunter.chasens18@ncf.edu \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).