From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 0D8A615838C for ; Fri, 26 Jan 2024 11:54:17 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6CB5DE29D9; Fri, 26 Jan 2024 11:54:10 +0000 (UTC) Received: from mp-relay-01.fibernetics.ca (mp-relay-01.fibernetics.ca [208.85.217.136]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1C5C1E29D1 for ; Fri, 26 Jan 2024 11:54:10 +0000 (UTC) Received: from mailpool-fe-01.fibernetics.ca (mailpool-fe-01.fibernetics.ca [208.85.217.144]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mp-relay-01.fibernetics.ca (Postfix) with ESMTPS id D1C65E105C for ; Fri, 26 Jan 2024 11:54:09 +0000 (UTC) Received: from localhost (mailpool-mx-01.fibernetics.ca [208.85.217.140]) by mailpool-fe-01.fibernetics.ca (Postfix) with ESMTP id CB2A828CF0 for ; Fri, 26 Jan 2024 11:54:09 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at X-Spam-Flag: NO X-Spam-Score: -0.299 X-Spam-Level: X-Spam-Status: No, score=-0.299 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Received: from mailpool-fe-01.fibernetics.ca ([208.85.217.144]) by localhost (mail-mx-01.fibernetics.ca [208.85.217.140]) (amavisd-new, port 10024) with ESMTP id 2Ey4ODxoviTn for ; Fri, 26 Jan 2024 11:54:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ca.inter.net; s=mail; t=1706270049; bh=A3AoeNc6PpWL2WpW6ZfVXzBDCAtCsL09CoD/GWuZEpc=; h=Date:From:To:Subject:References:In-Reply-To:From; b=L+mE37Du6Vb/quEUxWXF+HHwliR38pXv0p0fPDklId78W1uLtTFwJHK3+8inm8j87 MptfuSKVf3qKn3eVLYqut5UMZv18cEbw9I+dSqx8HU3jbxW96TV2LNsdQHmo30IzYz jmTKupXCDTAH9dbiCSxcJGSc/uVvCJ8KgCTp06nNXwcs+nnmuLXTl1ibJS2Xs/M+6c t6G7Cd9QiKE+7ptBaUkHKgfDArJQWGPhWPzRMEfbu+TA5lhnwSmKa25gYxPTzCdBvX HyqPCf6hCJGqRYFBC4AIZXO556+S24WI5+kcfYvtphpsqa93diWKEVpOnj1wQlrsar mi24/ZMGulCUw== Date: Fri, 26 Jan 2024 06:54:08 -0500 From: Philip Webb To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] 'make install' hijacked by installkernel ? Message-ID: Mail-Followup-To: gentoo-user@lists.gentoo.org References: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Archives-Salt: aa060b90-9f32-4b46-a756-44e675d3a3dd X-Archives-Hash: e57f022377aa476c363047179867a990 240126 Adam Carter wrote: > I just tried to install a new kernel using 'make install' > only to find that the behaviour has changed > and it appears to be running a bunch on installkernel stuff. > > 'make help' says > install - Install kernel using (your) ~/bin/installkernel or > (distribution) /sbin/installkernel or install to > $(INSTALL_PATH) and run lilo > > So I guess that I want the 'install to $(INSTALL_PATH) and run lilo' > behaviour that i'm used to. > How to i get 'make install' to ignore /sbin/installkernel ? I too just installed a new kernel (6.6.13). My notes told me to do : make && make firmware_install && make modules_install mount /boot cp arch/x86_64/boot/bzImage /boot/vmlinuz--gentoo-r cp System.map /boot/System.map--gentoo-r which worked with the appropriate version numbers inserted, but not before it choked on 'make firmware_install', which has disappeared. I too use Lilo, a simple + reliable boot manager. I have long wondered why the compile stage takes so long : it compiles innumerable .o files, which seem to involve config options I haven't chosen. The new kernel image is size 17633728 via 'ls -l /boot' : is that correct ? It does indeed boot & there are no changes in behaviour. -- ========================,,============================================ SUPPORT ___________//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT `-O----------O---' purslowatcadotinterdotnet