From owner-freebsd-current@FreeBSD.ORG Sat Sep 6 05:51:02 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2D8F3443 for ; Sat, 6 Sep 2014 05:51:02 +0000 (UTC) Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EC2F31844 for ; Sat, 6 Sep 2014 05:51:01 +0000 (UTC) Received: by mail-ie0-f176.google.com with SMTP id x19so14743033ier.7 for ; Fri, 05 Sep 2014 22:51:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=vtHw/ZDd3BBjAWKeKdgNeddZI54ZOVQUmRoq+xZhh2A=; b=OUvWRtguff5TMWQdxifHjBX1LJbtqgECWYf9hQjG9npZiEm1JsFgX/QkbDgF0VR6Y4 mQJcIXpH7Ttvj/iRXvx9QaFbFPD50PQMcIShagVlmg9CRUtwSUQmkS3BqoNJu5kC6pQS QdT7tD9k+gYId64R1JE1Q9exXcb9gAsqkQH47PrpNr1YKIwd7cBUlH2c/a1si+FMm1X1 lCd7a45LamJE0kdNre+8XYn5LD1XGKX8Tl8vyLVP3q8M8jhj6oylZx+05HK1aibG73ik WTQ4BrRt6eRbT9eTokRkXYK03eVAIeony16mJ4fwD1H2S/uWS5Bvcn86tY61DWlAiUvE KMAg== MIME-Version: 1.0 X-Received: by 10.50.7.100 with SMTP id i4mr10074357iga.32.1409982661260; Fri, 05 Sep 2014 22:51:01 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.107.163.148 with HTTP; Fri, 5 Sep 2014 22:51:01 -0700 (PDT) In-Reply-To: <540886EE.3050708@passap.ru> References: <20140825165522.GC91673@spindle.one-eyed-alien.net> <54072D80.4010402@passap.ru> <257cbfbf-959e-44f2-bef0-86c12522de03@email.android.com> <540886EE.3050708@passap.ru> Date: Fri, 5 Sep 2014 22:51:01 -0700 X-Google-Sender-Auth: _8PMa9ouJLQL1bPh7lip3eo24wk Message-ID: Subject: Re: "make installworld" commands used to generate manifest for makefs? From: Kevin Oberman To: Boris Samorodov Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Sep 2014 05:51:02 -0000 On Thu, Sep 4, 2014 at 8:36 AM, Boris Samorodov wrote: > 03.09.2014 21:01, Nenhum_de_Nos =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > > > > > > On September 3, 2014 12:02:24 PM GMT-03:00, Boris Samorodov < > bsam@passap.ru> wrote: > >> 28.08.2014 23:02, Craig Rodrigues =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > >> > >>> I did this: > >>> > >>> make -DDB_FROM_SRC -DNO_ROOT installkernel DESTDIR=3D/tmp/test4 > >>> make -DDB_FROM_SRC -DNO_ROOT installworld DESTDIR=3D/tmp/test4 > >>> make -DDB_FROM_SRC -DNO_ROOT distribution DESTDIR=3D/tmp/test4 > >>> > >>> /tmp/test4/METALOG was created, but it did not seem to have > >>> /boot/kernel/kernel or > >>> any kernel modules. Is that expected? > >> > >> For a new installation "installworld" should be done first (it creates > >> the needed directory infrastructure). And then one may do > >> "installkernel". > > > > As I read from so much time ago to install first kernel, starting from > which FreeBSD version I should change? > > It seems to be true for ages. Take a look at /usr/src/Makefile, > section "To cross-install current onto a separate partition". > > -- > WBR, Boris Samorodov (bsam) > FreeBSD Committer, http://www.FreeBSD.org The Power To Serve > Please understand that this is true when doing a cross-install where a system with the required directory structure to install a kernel is not yet present. It is not true when updating a system on which is existing FreeBSD is running. When updating a system from sources, you should always installkernel first and then reboot to make sure you have a working kernel before installworld blows away the tools needed to fix a kernel problem. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com