From owner-freebsd-questions@FreeBSD.ORG Thu Dec 20 11:34:35 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 47A3D770; Thu, 20 Dec 2012 11:34:35 +0000 (UTC) (envelope-from egoitz@ramattack.net) Received: from proxypop04.sare.net (proxypop04.sare.net [194.30.0.65]) by mx1.freebsd.org (Postfix) with ESMTP id BC0478FC0C; Thu, 20 Dec 2012 11:34:34 +0000 (UTC) Received: from [172.16.2.46] (izaro.sarenet.es [192.148.167.11]) by proxypop04.sare.net (Postfix) with ESMTPSA id A1FD79DED6E; Thu, 20 Dec 2012 12:34:20 +0100 (CET) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: about unattended installation From: Egoitz Aurrekoetxea Aurre In-Reply-To: <7FFE45C4-2001-46CF-AAE3-D1DF7B6EC9DE@fisglobal.com> Date: Thu, 20 Dec 2012 12:34:26 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <01CDE828-3BA6-48E5-8FA2-F06082A0B582@ramattack.net> References: <40FD5C3B-CF8B-4376-BA6B-9F90747CFFAF@ramattack.net> <7FFE45C4-2001-46CF-AAE3-D1DF7B6EC9DE@fisglobal.com> To: Devin Teske X-Mailer: Apple Mail (2.1499) Cc: FreeBSD Mailing List X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2012 11:34:35 -0000 Good morning, El 19/12/2012, a las 19:59, Devin Teske = escribi=F3: >=20 > On Dec 19, 2012, at 10:06 AM, Egoitz Aurrekoetxea Aurre wrote: >=20 >> Good afternoon, >>=20 >> One little question=85 I'm trying to have ready our new unattended = FreeBSD installation system. Until now, I have been using Sysinstall = scripting file but now with 9.1 out I think it's moment to start using = BSDInstaller in the unattended installation process. >=20 > Hold on a moment. You might want to wait until 9.2. (read more below) >=20 Well in the ftp can be seen :=20 FreeBSD-9.1-RELEASE-amd64-disc1.iso downloadable file=85. so I assume = it's a release??? >=20 >=20 >> I have seen the new installer, works basically like an script=85. my = real question is=85 before I did in install.cfg something like :=20 >>=20 >> ################################ >> disk=3Dda0 >> partition=3Dall >> bootManager=3Dstandard >> diskPartitionEditor >>=20 >> ################################ >>=20 >> da0s1-1=3Dufs 3072000 / >> da0s1-2=3Dswap 8096000 none >> da0s1-3=3Dufs 20485760 /var 1 >> da0s1-4=3Dufs 30720760 /usr 1 >> da0s1-5=3Dufs 0 /expert 1 >> diskLabelEditor >>=20 >> ################################ >>=20 >> Now I assume there's no way of getting this same through any command = like=85 'bsdinstall partedit _______________________' am I wrong??. >=20 > You're correct. In 9.0 and 9.1, it's just not feasible to man-handle = the user interface (partedit) as one could sysinstall. (read below about = 9.2) >=20 >=20 So I suppose that till the new installer is able to handle this in a = similar way to sysinstall (although the syntax to be different or = whatever)=85. or partitioning can be achieved in some non interactive = way, to maintain the possibility of rebuilding one's own release in = order to be able to use sysinstall and to be able to maintain working = unattended installation systems=85. because this is essential for some = of us=85.. and of course sysinstall to still continue working :)... >=20 >> So I assume all should be done by hand like this example of the = Handbook :=20 >>=20 >> # dd if=3D/dev/zero of=3D/dev/da1 bs=3D1k count=3D1 >> # fdisk -BI da1 #Initialize your new disk >> # bsdlabel -B -w da1s1 auto #Label it. >> # bsdlabel -e da1s1 # Edit the bsdlabel just created and add any = partitions. >> # mkdir -p /1 >> # newfs /dev/da1s1e # Repeat this for every partition you created. >> # mount /dev/da1s1e /1 # Mount the partition(s) >> # vi /etc/fstab # Add the appropriate entry/entries to your = /etc/fstab. >>=20 >> In the auto script=85. >>=20 >> am I wrong?. If the answer is yes=85 could you point me to some = documentation in order to be able to complete all this doc. >=20 > The answer is (unfortunately) yes=85 that is until (hopefully) 9.2. >=20 > It's an on-going significant amount of work to make add backward = compatibility (so bsdinstall can load sysinstall "install.cfg" files). = I'm not going to discuss the specifics here or yet, but I'm actively = working on it. >=20 > No docs on how to mangle the auto script to do what you want (that I = know of). Ok then :) >=20 >=20 >=20 >> Apart from all this=85 is Sysinstall going to be maintained in = parallel?. >>=20 >=20 > Sysinstall is dead. Devin, sysinstall should not be died till the new installer allows or = exists a way of doing same thing than before we did in some manner or = other one=85.. because else=85 don't know... can this commands be = translated to gpart for example??=85 and to act in a non interactive = way??. But apart from the own gpart the are later other parts of the = installation which should be done too=85 like selecting which = distributions to install in a non interactive way for example=85.. if = that is not possible to be done=85 in a non interactive way=85. = sysinstall should not disappear=85. > The bsdinstall you know can be considered the "first generation" and = accordingly is a bit spartan. I'm working hard on the next generation. = My plan is to have 10.0 with bsdinstall able to run sysinstall scripts = (for backward compatibility; can't yet say what 9.x release will be = MFC'd to, but that could be 9.2). >=20 > I'm planning one helluva BSDCan-2013 presentation. > --=20 > Devin >=20 Thanks a lot for all !! Best regards,