From owner-freebsd-sysinstall@FreeBSD.ORG Mon Jan 2 11:07:14 2012 Return-Path: Delivered-To: freebsd-sysinstall@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41AC91065672 for ; Mon, 2 Jan 2012 11:07:14 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2E2928FC22 for ; Mon, 2 Jan 2012 11:07:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q02B7Eqg005262 for ; Mon, 2 Jan 2012 11:07:14 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q02B7D76005260 for freebsd-sysinstall@FreeBSD.org; Mon, 2 Jan 2012 11:07:13 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 2 Jan 2012 11:07:13 GMT Message-Id: <201201021107.q02B7D76005260@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-sysinstall@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-sysinstall@FreeBSD.org X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2012 11:07:14 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o bin/163123 sysinstall bsdinstall(8): IPV6 only errors connecting o bin/162693 sysinstall sysinstall(8): release/Makefile.sysinstall on 9.x refe o bin/162675 sysinstall bsdinstall(8): miscount of remaining diskspace after p o bin/162605 sysinstall sysinstall(8) doesn't identify CD/DVD drives for the u o bin/162429 sysinstall bsdinstall(8): 9.x installer: selecting ZFS for the ro o bin/162428 sysinstall bsdinstall(8): 9.x installer fails with extract error o bin/162258 sysinstall sysinstall(8): long-time bugs o bin/162175 sysinstall [patch] bsdinstall(8): add keymap selection loop and t o bin/162152 sysinstall bsdinstall(8): No up-to-date IPv6 French mirror f bin/161931 sysinstall bsdinstall(8): (add sysinstall partition config as opt o bin/161929 sysinstall bsdinstall(8): (change partition editor screen default o bin/161928 sysinstall bsdinstall(8): (add option to enable 2 button mouse co o bin/161926 sysinstall bsdinstall(8): disk layout trouble o bin/161924 sysinstall bsdinstall(8): add msg box telling user to remove inst o bin/161923 sysinstall bsdinstall(8) games & ports install options o kern/161837 sysinstall [libdisk] [patch] sysinstall(8) has a 32 disk limit o bin/161720 sysinstall bsdinstall(8): partition editor does not put partition o bin/161547 sysinstall [patch] bsdinstall(8) should identify wireless network f bin/161113 sysinstall bsdinstall(8): 9.0-BETA3: overwrites Win*-bootcodes wi o bin/161101 sysinstall bsdinstall(8): 9.0-BETA3: partition editor: UFS-option o bin/161100 sysinstall bsdinstall(8): 9.0-BETA3: Add User but no Add Group o bin/161056 sysinstall bsdinstall(8): could allow full control over newfs arg o bin/161055 sysinstall bsdinstall(8): partitioner should auto-populate GPT la f bin/161054 sysinstall bsdinstall(8): partitioner should list valid "type"s o bin/161053 sysinstall bsdinstall(8): network setup dialog is hard to navigat o bin/161052 sysinstall bsdinstall(8): should be consistent about saving confi o bin/161050 sysinstall bsdinstall(8): should use new syntax for IPv4 in rc.co o bin/161049 sysinstall bsdinstall(8): could try to tell if SSDs support TRIM o bin/161048 sysinstall bsdinstall(8): should run a concurrent shell on anothe o bin/161047 sysinstall bsdinstall(8): should not run on vt0 o bin/157635 sysinstall sysinstall(8): "none" Do not install a boot manager - o bin/157117 sysinstall sysinstall(8): Add ftp4.se.freebsd.org to list of IPv6 o bin/154788 sysinstall sysinstall(8) crashes if no network interface found o bin/154613 sysinstall sysinstall(8) does not rescan USB automatically o bin/151229 sysinstall sysinstall(8) - shift-tab doesn't work as expected o bin/150995 sysinstall sysinstall(8): corruption of partition table s bin/150237 sysinstall sysinstall(8): Suggestion: installer should suggest th o bin/148805 sysinstall [hang] FreeBSD 7.2, 8.0, and 9.0 hang during install a f bin/148220 sysinstall sysinstall(8): 9.0-current gets "Cannot resolv hostnam o bin/148201 sysinstall sysinstall(8): core dump (Error 10) while trying to in o bin/148053 sysinstall sysinstall(8) labeling o bin/146299 sysinstall sysinstall(8): cannot create slice o bin/145735 sysinstall sysinstall(8) trashes Vista-created partition tables o bin/145027 sysinstall Remove all sysinstall(8) references to floppy and slip o bin/144278 sysinstall [install] Fixit from USB dont work o bin/142867 sysinstall sysinstall(8): in a custom installation re-entering th o misc/142335 sysinstall Download of Release 8.0 LIVE is NOT a "live" from CD p o bin/140843 sysinstall sysinstall(8): cannot software install from usb o bin/140842 sysinstall sysinstall(8): destroyed ncurses interface with FBSD8. o bin/140595 sysinstall [request] sysinstall(8): Replace "Country Selection" w o bin/138423 sysinstall sysinstall(8): Installer (and sade) get wrong number o o bin/138025 sysinstall sysinstall(8) fails to create big partition o bin/137864 sysinstall [patch] sysinstall(8): add possibility to shutdown/pow o bin/137713 sysinstall sysinstall(8): installer partition editor generates in o bin/134425 sysinstall sysinstall(8) custom distributions select all and dese o bin/129762 sysinstall sysinstall(8) doesn't seem to support GPT for EFI boar s bin/123304 sysinstall sysinstall(8): missing sensible and user friendly prog o bin/121503 sysinstall sysinstall(8): 7.0 upgrade doesn't let me mount all of a bin/121124 sysinstall sysinstall(8): FreeBSD 6.3 installation deletes MBR pa o bin/119077 sysinstall [patch] sysinstall(8) - reading packages from index is o bin/113682 sysinstall [patch] sysinstall(8) warns for invalid geometry which o bin/112757 sysinstall sysinstall(8): sysinstall(8): in the FDISK tool we can o bin/110151 sysinstall sysinstall(8): sysinstall(8) don't respects install ro o bin/108191 sysinstall sysinstall(8): Disklabel editor help text (by F1 key) o bin/107830 sysinstall sysinstall(8): Change Units (Z) in fdisk doesn't work p bin/102638 sysinstall [patch] sysinstall(8): custom dist set always install o bin/102498 sysinstall sysinstall(8): Cursor doesn't track sysinstall hilight a bin/101762 sysinstall sysinstall(8) does not obey /usr/ports symlink while i o bin/97108 sysinstall sysinstall(8): write failure on transfer (wrote -1 byt o bin/93275 sysinstall sysinstall(8): Failure to install after restarting ins o bin/90656 sysinstall sysinstall(8): 6.0-RELEASE (i386) cannot be installed s bin/86859 sysinstall sysinstall(8): Installer should ask about Linux earlie o bin/86454 sysinstall sysinstall(8): sysinstall terminates with signal 10 if o bin/79910 sysinstall sysinstall(8): Cannot escape from failed port/package o bin/79840 sysinstall sysinstall(8): Partitioning and formating a new disk f o bin/79621 sysinstall sysinstall(8): sysinstall(8) does not create a device o bin/78964 sysinstall sysinstall(8): can not write labels to hdd on installa s bin/73617 sysinstall sysinstall(8): fdisk editor unmarks active partition o bin/73410 sysinstall sysinstall(8): Sysinstall could not allocate disklabel o bin/72895 sysinstall sysinstall(8): Sysinstall generates invalid partition o bin/70002 sysinstall sysinstall(8): fails to locate FTP dirs if the OS has o bin/69986 sysinstall sysinstall(8): [patch] no job control in fixit shell o o bin/69942 sysinstall sysinstall(8): sysinstall changes /etc/rc.conf after i o bin/69723 sysinstall sysinstall(8): [request] allow to continue from packag o bin/62702 sysinstall sysinstall(8): backup of /etc and /root during sysinst o bin/62367 sysinstall sysinstall(8): 5.2.1-RC installation problems o bin/61890 sysinstall sysinstall(8): fdisk(8) uses incorrect calculations fo o bin/61603 sysinstall sysinstall(8): wrong geometry guessed o bin/60632 sysinstall sysinstall(8): UI bug in partition label screen in sys o bin/53341 sysinstall sysinstall(8): [patch] dump frequency in sysinstall is o bin/48989 sysinstall sysinstall(8): Sysinstall's partition editor gets con s bin/48341 sysinstall sysinstall(8): changes the active slice flag when it p o bin/46905 sysinstall sysinstall(8): FreeBSD 5.x cannot be installed from mu o bin/46235 sysinstall sysinstall(8): NTP servers for Finland require updatin o bin/42162 sysinstall sysinstall(8): after restart, installation crashes, md o bin/41949 sysinstall sysinstall(8): sysinstall sorts /etc/rc.conf during ne o bin/41850 sysinstall sysinstall(8): sysinstall fails to create root filesys f bin/40260 sysinstall sysinstall(8): hang when detecting devices (No CD/DVD s conf/39580 sysinstall sysinstall(8): [request] more secure mount options o bin/38854 sysinstall sysinstall(8): resetting during setup causes the targe s bin/38609 sysinstall sysinstall(8): [request] sysinstall should know the si o bin/38478 sysinstall sysinstall(8): In Choose Distributions screen, it's di o bin/38057 sysinstall sysinstall(8): "install" document doesn't display corr o bin/38056 sysinstall sysinstall(8): User (creation)'s "Member groups" item o bin/38055 sysinstall sysinstall(8): Groups (creation) item should be before o bin/37710 sysinstall sysinstall(8): LAN interface in wrong state after atte a bin/32375 sysinstall sysinstall(8): sysinstall doesn't respect User generat o bin/31363 sysinstall sysinstall(8): "partition editor" silently corrects pa a bin/30737 sysinstall sysinstall(8): sysinstall leaks file descriptors on re o bin/29375 sysinstall sysinstall(8): disk editor gets confused by slices tha a bin/23402 sysinstall sysinstall(8): upgrade ought to check partition sizes o bin/16948 sysinstall sysinstall(8): sysinstall/disklabel: bad partition tab o bin/15038 sysinstall sysinstall(8): easy to not notice that selection lists s bin/7232 sysinstall sysinstall(8): suggestion for FreeBSD installation dia 114 problems total. From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 00:02:03 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB3E4106564A for ; Wed, 4 Jan 2012 00:02:03 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 73B378FC0A for ; Wed, 4 Jan 2012 00:02:03 +0000 (UTC) Received: by lahl5 with SMTP id l5so8930670lah.13 for ; Tue, 03 Jan 2012 16:02:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:from:date:message-id:subject:to:content-type; bh=FRutf9+ACbztcVpv2YJyHsq9zA15Hb2vfuFfeKTLJwY=; b=ovxDHIJCgH0LZz0j7vmF06ePeFl1MG3WxCVkGTfror1idiBdaPR1LWp69i+A9404/A Y8zg+yt4EfupGzN03BhE5bIEc+QuBbXTuPIHaJSRH/vnPPszUivP9WFtRqGgAMaKy/vk y+d8bD/sMd2chid0cjGhipYAl218WGj5U7wzE= Received: by 10.152.103.71 with SMTP id fu7mr43167653lab.31.1325633644197; Tue, 03 Jan 2012 15:34:04 -0800 (PST) MIME-Version: 1.0 Received: by 10.152.129.8 with HTTP; Tue, 3 Jan 2012 15:33:33 -0800 (PST) From: Eitan Adler Date: Tue, 3 Jan 2012 18:33:33 -0500 Message-ID: To: freebsd-current Current , freebsd-sysinstall@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: Subject: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 00:02:04 -0000 Hi, In the the recent sysinstall thread there seems to be general agreement that having a post-install configuration tool is a good thing. Until such a tool is written I think it would be a good idea to use sysinstall for this purpose. I am willing to do the work to restore sysinstall and maintain it as a post-install tool until a new one is written. My plan would be to: - Restore sysinstall and libodialog - Statically link libodialog and make it specific to sysinstall A rewrite of sysinstall to use libdialog is not worth it. It would be better to just write a new configuration tool at that point. - Remove front end non-configure facing features (ie "upgrade" and installation options) - Remove scripting support from sysinstall Additionally I would agree to - Ensure that sysinstall continues to function as time goes on - Review and test patches to sysinstall What I am not agreeing to: - Rewrite sysinstall - Make a new tool Please follow up to freebsd-sysinstall@ -- Eitan Adler From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 00:49:40 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 137FD1065673; Wed, 4 Jan 2012 00:49:40 +0000 (UTC) (envelope-from marcel@xcllnt.net) Received: from mail.xcllnt.net (mail.xcllnt.net [70.36.220.4]) by mx1.freebsd.org (Postfix) with ESMTP id AB7FE8FC17; Wed, 4 Jan 2012 00:49:39 +0000 (UTC) Received: from sa-nc-cs-216.static.jnpr.net (natint3.juniper.net [66.129.224.36]) (authenticated bits=0) by mail.xcllnt.net (8.14.5/8.14.5) with ESMTP id q040R9mJ079360 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 3 Jan 2012 16:27:17 -0800 (PST) (envelope-from marcel@xcllnt.net) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=us-ascii From: Marcel Moolenaar In-Reply-To: Date: Tue, 3 Jan 2012 16:27:04 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Eitan Adler X-Mailer: Apple Mail (2.1251.1) Cc: freebsd-current Current , freebsd-sysinstall@freebsd.org Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 00:49:40 -0000 On Jan 3, 2012, at 3:33 PM, Eitan Adler wrote: > Hi, >=20 > In the the recent sysinstall thread there seems to be general = agreement that > having a post-install configuration tool is a good thing. Until such a > tool is written I think it would be a good idea to use sysinstall for > this purpose. I am willing to do the work to restore sysinstall and > maintain it as a post-install tool until a new one is written. I though sade was created for that purpose, because sysinstall was too much tied to the installation process. If sysinstall comes back, sade definitely has to go: ------------------------------------------------------------------------ r161060 | netchild | 2006-08-07 16:35:49 -0700 (Mon, 07 Aug 2006) | 9 = lines Say welcome to 'sade', the SysAdmins Disk Editor. It's the fdisk and = disklabel part of sysinstall. So sysinstall may retire now, we have the important = non-install part of it covered. ATM it doesn't understand GEOM stuff (like mirror, stripe, raid, ...), = but patches to change this and to clean it up internally are more than welcome. Submitted by: mami@nyitolap.hu ------------------------------------------------------------------------ In general I think it's a bad idea to revive sysinstall. It doesn't function appropriately on most architectures that FreeBSD supports and it's definitely the opposite of what we've been working towards for at least the last 5 years. FYI, --=20 Marcel Moolenaar marcel@xcllnt.net From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 00:55:08 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DBA3D1065670; Wed, 4 Jan 2012 00:55:08 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id 65BE18FC12; Wed, 4 Jan 2012 00:55:08 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 02360E622B; Wed, 4 Jan 2012 00:55:07 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cran.org.uk; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=mail; bh=kveQcqzDnxbW HYstXoK6flTLskw=; b=bi8L8ZhoFr9QCcbajbZodtk+DqMdm+XjMNg+5tvfSOd2 UeK0nPRu0WBlnx72bYSmGbDjKy1YEZPrgB3aiOZkcnrfB0zrUigQ5TMPAf9KmwgC lenQurXqX/n+Si01/bdfbuCUM2WIaVe8geCAeNqHwuuxk117LYnPww2BjQm67FM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=cran.org.uk; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=mail; b=VGK0OP aglAFHJzBrI6CPL+n+A6ijUefh3ko58JJIw0Ox6A2of1CffYrC3pgsAjm7ipzlgb LJQS0MtvPifri8umlZ6+dF7hPvitWAyuDuCQAk10/wqd3vOA/OIaPU0o40ZwynyB hFbB3EAlmVId4ys2wDLxm6DkBX1lj4X5NVsDg= Received: from [192.168.1.66] (188-220-36-32.zone11.bethere.co.uk [188.220.36.32]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id CE29CE620E; Wed, 4 Jan 2012 00:55:06 +0000 (GMT) Message-ID: <4F03A366.5030601@cran.org.uk> Date: Wed, 04 Jan 2012 00:55:02 +0000 From: Bruce Cran User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: Marcel Moolenaar References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current Current , freebsd-sysinstall@freebsd.org Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 00:55:08 -0000 On 04/01/2012 00:27, Marcel Moolenaar wrote: > ATM it doesn't understand GEOM stuff (like mirror, stripe, raid, ...), but patches > to change this and to clean it up internally are more than welcome. There's a rewrite almost ready to go that supports ZFS etc. at http://butcher.heavennet.ru/sade/ - I'm hoping to find some time to finish it off and import it. -- Bruce Cran From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 00:55:15 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B91A5106564A for ; Wed, 4 Jan 2012 00:55:15 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id 69D788FC13 for ; Wed, 4 Jan 2012 00:55:15 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 91449E622F; Wed, 4 Jan 2012 00:55:14 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cran.org.uk; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=mail; bh=ZEw7rNKbwz98 2EBLr/f1pVUx1bA=; b=dapxlTAnm7L121y6FRqwohYZVOmpHlbrsSdAwf6cuSfb lkQxKB71yKgYZqY2EeOrrO5T+vjP4rEc9sj2P2SoQZNhx01wF6o1BWYOx/awm8WR HhSi5qfNC2iWHbKcOHsHLTg3uvUEapc91BQAANvWQJ9XX7N7Om/3YAP/Vl3CpjA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=cran.org.uk; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=mail; b=wk035j LdMUvH9z4il9J9Q+0z3XYIPWEOAlLhRi9puDO2VZ1uyrvZy6vvDf88zCvM2fnQQB GPE2/z5w3i4bew0ndIj88GkMp9w921gzIRbiSXLiqdMH0oV6L6zrbIEYYSS+mzKL eKKZgEBCOcYxDgCyoh4iYn74VjbXgXLFncESI= Received: from [192.168.1.66] (188-220-36-32.zone11.bethere.co.uk [188.220.36.32]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 52E65E620E; Wed, 4 Jan 2012 00:55:14 +0000 (GMT) Message-ID: <4F03A36E.3000901@cran.org.uk> Date: Wed, 04 Jan 2012 00:55:10 +0000 From: Bruce Cran User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: Eitan Adler References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-sysinstall@freebsd.org Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 00:55:15 -0000 On 03/01/2012 23:33, Eitan Adler wrote: > - Restore sysinstall and libodialog > - Statically link libodialog and make it specific to sysinstall > A rewrite of sysinstall to use libdialog is not worth it. It would > be better to just write a new configuration tool at that point. > - Remove front end non-configure facing features (ie "upgrade" and > installation options) > - Remove scripting support from sysinstall > > Additionally I would agree to > - Ensure that sysinstall continues to function as time goes on > - Review and test patches to sysinstall > > What I am not agreeing to: > - Rewrite sysinstall > - Make a new tool Please don't remove the install and upgrade functionality - I'm willing to put time into fixing any issues, and adding support for ZFS etc. once it's restored. I'd like to see sysinstall refactored into something more manageable and converted into a YAST-like tool because I don't think bsdinstall is anywhere near the experience we want for a technical OS like FreeBSD - we're not, and shouldn't aim to be IMO, the Ubuntu of the BSDs. -- Bruce Cran From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 00:20:53 2012 Return-Path: Delivered-To: sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02181106564A for ; Wed, 4 Jan 2012 00:20:53 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id BCC278FC0A for ; Wed, 4 Jan 2012 00:20:52 +0000 (UTC) Received: by mail-tul01m020-f182.google.com with SMTP id wd18so19515397obb.13 for ; Tue, 03 Jan 2012 16:20:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=noQXKRrwF+4Bp1CHmYj33I5naH7VFeALVtob59/TEVc=; b=n49ScWCCTx9GUrnmzZQCdG2uLTdoeocNBmu/0nn3kvEkRJolRKGb8fewo+ZOweyzWV x1jjXct3f4xQZR5ClLaKbgdl0rTA4ppRripfUjI5+Xh7R7Lrsvu9DIMte/KWN+SiA0J6 E4wB0y8n6xDHyVFZkxeluwdM9bVHT1707OOkg= MIME-Version: 1.0 Received: by 10.182.51.37 with SMTP id h5mr46110478obo.51.1325634623405; Tue, 03 Jan 2012 15:50:23 -0800 (PST) Received: by 10.182.152.6 with HTTP; Tue, 3 Jan 2012 15:50:23 -0800 (PST) In-Reply-To: References: Date: Tue, 3 Jan 2012 15:50:23 -0800 Message-ID: From: Garrett Cooper To: Eitan Adler Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Wed, 04 Jan 2012 01:56:16 +0000 Cc: Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 00:20:53 -0000 (sysinstall@ BCCed) On Tue, Jan 3, 2012 at 3:33 PM, Eitan Adler wrote: > Hi, > > In the the recent sysinstall thread there seems to be general agreement t= hat > having a post-install configuration tool is a good thing. Until such a > tool is written I think it would be a good idea to use sysinstall for > this purpose. =A0I am willing to do the work to restore sysinstall and > maintain it as a post-install tool until a new one is written. > > My plan would be to: > > - Restore sysinstall and libodialog > - Statically link libodialog and make it specific to sysinstall > =A0 =A0 =A0 A rewrite of sysinstall to use libdialog is not worth it. It = would > =A0 =A0 =A0 be better to just write a new configuration tool at that poin= t. > - Remove front end non-configure facing features (ie "upgrade" and > installation options) > - Remove scripting support from sysinstall > > Additionally I would agree to > - Ensure that sysinstall continues to function as time goes on > - Review and test patches to sysinstall > > What I am not agreeing to: > - Rewrite sysinstall > - Make a new tool > > Please follow up to freebsd-sysinstall@ Reviving sysinstall solely for this purpose is probably a big step backwards (especially because it's after 9.0-RELEASE): sysinstall needs to be permanently retired and bsdinstall needs work becoming a more complete tool (FWIW, iXsystems has tentatively offered to pick up the maintainership of the installer so that it's properly integrated into pc-sysinstall as we originally intended to do). So we shouldn't be wasting effort on sysinstall. Please talk to Devin Teske about his 'host-setup' tool first. Thanks, -Garrett From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 02:03:24 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 138C4106585C for ; Wed, 4 Jan 2012 02:03:24 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id 8651C8FC08 for ; Wed, 4 Jan 2012 02:03:23 +0000 (UTC) Received: from lstewart1.loshell.room52.net (ppp59-167-184-191.static.internode.on.net [59.167.184.191]) by lauren.room52.net (Postfix) with ESMTPSA id 5B36E7E891; Wed, 4 Jan 2012 12:45:08 +1100 (EST) Message-ID: <4F03AF24.70102@freebsd.org> Date: Wed, 04 Jan 2012 12:45:08 +1100 From: Lawrence Stewart User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111016 Thunderbird/7.0.1 MIME-Version: 1.0 To: Marcel Moolenaar References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lauren.room52.net Cc: Ron McDowell , freebsd-sysinstall@freebsd.org Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 02:03:24 -0000 [switching to freebsd-sysinstall@ which I'm no subscribed to, please keep me CC'ed] On 01/04/12 11:27, Marcel Moolenaar wrote: > > On Jan 3, 2012, at 3:33 PM, Eitan Adler wrote: > >> Hi, >> >> In the the recent sysinstall thread there seems to be general agreement that >> having a post-install configuration tool is a good thing. Until such a >> tool is written I think it would be a good idea to use sysinstall for >> this purpose. I am willing to do the work to restore sysinstall and >> maintain it as a post-install tool until a new one is written. > > I though sade was created for that purpose, because sysinstall was too > much tied to the installation process. If sysinstall comes back, sade > definitely has to go: > > ------------------------------------------------------------------------ > r161060 | netchild | 2006-08-07 16:35:49 -0700 (Mon, 07 Aug 2006) | 9 lines > > Say welcome to 'sade', the SysAdmins Disk Editor. It's the fdisk and disklabel part > of sysinstall. So sysinstall may retire now, we have the important non-install part > of it covered. > > ATM it doesn't understand GEOM stuff (like mirror, stripe, raid, ...), but patches > to change this and to clean it up internally are more than welcome. > > Submitted by: mami@nyitolap.hu > > ------------------------------------------------------------------------ > > In general I think it's a bad idea to revive sysinstall. It doesn't > function appropriately on most architectures that FreeBSD supports > and it's definitely the opposite of what we've been working towards > for at least the last 5 years. In the sysinstall removal thread, Ron (CC'ed) suggested he might be interested in getting involved with writing a post installation config script which leverages bsdinstall's sh code where possible, but is separate and stand alone. Ron's extensive sysadmin background would be very useful in developing such a tool, so it seems silly not to take the offer and run with it to see where we end up. Ron, are you still interested in this project? What help and/or support do you need to get things moving? Eitan, as discussed briefly on IRC, I suspect the amount of work required to revive sysinstall and do all the hacking to make it do what you suggest would be in the same ballpark as syncing up with Ron and having a crack at a shell script based on a set of dialogs a la bsdinstaller to achieve the same goal. I know you said you didn't want to write a new tool, so if getting involved with the above doesn't take your fancy, perhaps just waiting to see what comes of the effort to write said tool would be prudent. Cheers, Lawrence From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 00:26:46 2012 Return-Path: Delivered-To: FreeBSD-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C72801065675 for ; Wed, 4 Jan 2012 00:26:46 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 87AFD8FC15 for ; Wed, 4 Jan 2012 00:26:46 +0000 (UTC) Received: from pps.filterd (ltcfislmsgpa02 [127.0.0.1]) by ltcfislmsgpa02.fnfis.com (8.14.4/8.14.4) with SMTP id q03NPxlx003246 for ; Tue, 3 Jan 2012 17:58:00 -0600 Received: from smtp.fisglobal.com ([10.132.206.15]) by ltcfislmsgpa02.fnfis.com with ESMTP id 1249up8cg4-9 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for ; Tue, 03 Jan 2012 17:58:00 -0600 Received: from dtwin (10.14.152.15) by smtp.fisglobal.com (10.132.206.15) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 3 Jan 2012 17:57:50 -0600 From: Devin Teske To: "'Garrett Cooper'" , "'Eitan Adler'" References: In-Reply-To: Date: Tue, 3 Jan 2012 15:57:55 -0800 Message-ID: <054901ccca73$83bb1ef0$8b315cd0$@fisglobal.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQGioPys4U3YFAHSWDxI2KBhfkp2BwGGY4GdlkNwqKA= Content-Language: en-us X-Originating-IP: [10.14.152.15] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.5.7110, 1.0.211, 0.0.0000 definitions=2012-01-03_03:2012-01-03, 2012-01-03, 1970-01-01 signatures=0 Content-Type: text/plain; charset="iso-8859-1" X-Mailman-Approved-At: Wed, 04 Jan 2012 02:28:00 +0000 Cc: Subject: RE: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 00:26:47 -0000 -sysinstall@ [re-]BCC'd. > -----Original Message----- > From: Garrett Cooper [mailto:yanegomi@gmail.com] > Sent: Tuesday, January 03, 2012 3:50 PM > To: Eitan Adler > Cc: Devin Teske > Subject: Re: sysinstall as a post-install tool >=20 > (sysinstall@ BCCed) >=20 > On Tue, Jan 3, 2012 at 3:33 PM, Eitan Adler wrote: > > Hi, > > > > In the the recent sysinstall thread there seems to be general > > agreement that having a post-install configuration tool is a good > > thing. Until such a tool is written I think it would be a good idea to > > use sysinstall for this purpose. =A0I am willing to do the work to > > restore sysinstall and maintain it as a post-install tool until a new o= ne is written. > > > > My plan would be to: > > > > - Restore sysinstall and libodialog > > - Statically link libodialog and make it specific to sysinstall > > =A0 =A0 =A0 A rewrite of sysinstall to use libdialog is not worth it. It > > would > > =A0 =A0 =A0 be better to just write a new configuration tool at that po= int. > > - Remove front end non-configure facing features (ie "upgrade" and > > installation options) > > - Remove scripting support from sysinstall > > > > Additionally I would agree to > > - Ensure that sysinstall continues to function as time goes on > > - Review and test patches to sysinstall > > > > What I am not agreeing to: > > - Rewrite sysinstall > > - Make a new tool > > > > Please follow up to freebsd-sysinstall@ >=20 > Reviving sysinstall solely for this purpose is probably a big step backwards > (especially because it's after 9.0-RELEASE): sysinstall needs to be permanently > retired and bsdinstall needs work becoming a more complete tool (FWIW, > iXsystems has tentatively offered to pick up the maintainership of the installer so > that it's properly integrated into pc-sysinstall as we originally intende= d to do). > So we shouldn't be wasting effort on sysinstall. Please talk to Devin Teske > about his 'host-setup' tool first. Eitan, Do check out the latest version: http://druidbsd.sourceforge.net/download/host-setup.txt Garrett, Maybe it's time to get host-setup added to the ports tree? Will increase its visibility at least. Yeah? --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 02:34:36 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A406106567B for ; Wed, 4 Jan 2012 02:34:36 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4D4528FC12 for ; Wed, 4 Jan 2012 02:34:35 +0000 (UTC) Received: by lahl5 with SMTP id l5so8965310lah.13 for ; Tue, 03 Jan 2012 18:34:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=+XZojvGKNuQd9e2Xxt8aJQJrLJscuLFXGXudvOnS36E=; b=rG5DeHIH0xZ8s1tE7FMybBHJwRv9Lk7Lwan3NjY/Xr2enq3gENQEIPuOKyayWTrAMw zfy1QgudGHLnS3JtUqJ9Wltx7I6a2KBS9j9G6c8/Wn59xjoYWfD4hkz1tR5ADgVeOtKq EEP3axGrW24fEgKJjkgMSUeJD+kbAmYYLlJlg= Received: by 10.152.103.71 with SMTP id fu7mr43416568lab.31.1325644474088; Tue, 03 Jan 2012 18:34:34 -0800 (PST) MIME-Version: 1.0 Received: by 10.152.129.8 with HTTP; Tue, 3 Jan 2012 18:34:03 -0800 (PST) In-Reply-To: <4F03AF24.70102@freebsd.org> References: <4F03AF24.70102@freebsd.org> From: Eitan Adler Date: Tue, 3 Jan 2012 21:34:03 -0500 Message-ID: To: Lawrence Stewart Content-Type: text/plain; charset=UTF-8 Cc: freebsd-sysinstall@freebsd.org, Marcel Moolenaar Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 02:34:36 -0000 On Tue, Jan 3, 2012 at 8:45 PM, Lawrence Stewart wrote: > On 01/04/12 11:27, Marcel Moolenaar wrote: >> In general I think it's a bad idea to revive sysinstall. It doesn't >> function appropriately on most architectures that FreeBSD supports >> and it's definitely the opposite of what we've been working towards >> for at least the last 5 years. What I said was an offer based on some previous discussion. If people don't think this is a good idea, or better yet if we have people willing to work on a new tool lets go with that instead. > In the sysinstall removal thread, Ron (CC'ed) suggested he might be > interested in getting involved with writing a post installation config > script which leverages bsdinstall's sh code where possible, but is separate > and stand alone. Ron's extensive sysadmin background would be very useful in > developing such a tool, so it seems silly not to take the offer and run with > it to see where we end up. > Ron, are you still interested in this project? What help and/or support do > you need to get things moving? I would be willing to work with Ron and develop a useful configuration tool that fits into the base system a la bsdinstall. My original hesitancy of writing a new tool had to with past experience where I was not able to get anyone to review the code. I think things will likely be different this time. -- Eitan Adler From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 02:51:02 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9678C106566B; Wed, 4 Jan 2012 02:51:02 +0000 (UTC) (envelope-from rcm@fuzzwad.org) Received: from mail.volente.us (unknown [IPv6:2001:470:7:d47::2]) by mx1.freebsd.org (Postfix) with ESMTP id 158568FC17; Wed, 4 Jan 2012 02:51:01 +0000 (UTC) Received: from zombie.fuzzwad.net (localhost [127.0.0.1]) by mail.volente.us (8.14.4/8.14.4) with ESMTP id q042oxpV034400; Tue, 3 Jan 2012 20:50:59 -0600 (CST) (envelope-from rcm@fuzzwad.org) Message-ID: <4F03BE93.9040708@fuzzwad.org> Date: Tue, 03 Jan 2012 20:50:59 -0600 From: Ron McDowell User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Lawrence Stewart References: <4F03AF24.70102@freebsd.org> In-Reply-To: <4F03AF24.70102@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-sysinstall@freebsd.org, Marcel Moolenaar Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 02:51:02 -0000 Lawrence Stewart wrote: > [switching to freebsd-sysinstall@ which I'm no subscribed to, please > keep me CC'ed] > > On 01/04/12 11:27, Marcel Moolenaar wrote: >> >> On Jan 3, 2012, at 3:33 PM, Eitan Adler wrote: >> >>> Hi, >>> >>> In the the recent sysinstall thread there seems to be general >>> agreement that >>> having a post-install configuration tool is a good thing. Until such a >>> tool is written I think it would be a good idea to use sysinstall for >>> this purpose. I am willing to do the work to restore sysinstall and >>> maintain it as a post-install tool until a new one is written. >> >> I though sade was created for that purpose, because sysinstall was too >> much tied to the installation process. If sysinstall comes back, sade >> definitely has to go: >> >> ------------------------------------------------------------------------ >> r161060 | netchild | 2006-08-07 16:35:49 -0700 (Mon, 07 Aug 2006) | 9 >> lines >> >> Say welcome to 'sade', the SysAdmins Disk Editor. It's the fdisk and >> disklabel part >> of sysinstall. So sysinstall may retire now, we have the important >> non-install part >> of it covered. >> >> ATM it doesn't understand GEOM stuff (like mirror, stripe, raid, >> ...), but patches >> to change this and to clean it up internally are more than welcome. >> >> Submitted by: mami@nyitolap.hu >> >> ------------------------------------------------------------------------ >> >> In general I think it's a bad idea to revive sysinstall. It doesn't >> function appropriately on most architectures that FreeBSD supports >> and it's definitely the opposite of what we've been working towards >> for at least the last 5 years. > > In the sysinstall removal thread, Ron (CC'ed) suggested he might be > interested in getting involved with writing a post installation config > script which leverages bsdinstall's sh code where possible, but is > separate and stand alone. Ron's extensive sysadmin background would be > very useful in developing such a tool, so it seems silly not to take > the offer and run with it to see where we end up. > > Ron, are you still interested in this project? What help and/or > support do you need to get things moving? > > Eitan, as discussed briefly on IRC, I suspect the amount of work > required to revive sysinstall and do all the hacking to make it do > what you suggest would be in the same ballpark as syncing up with Ron > and having a crack at a shell script based on a set of dialogs a la > bsdinstaller to achieve the same goal. > > I know you said you didn't want to write a new tool, so if getting > involved with the above doesn't take your fancy, perhaps just waiting > to see what comes of the effort to write said tool would be prudent. > > Cheers, > Lawrence I [Ron] just added myself to the sysinstall list. A comment about the "sade" mention above...sade performs a very small part of what sysinstall does and cannot be thought of as a replacement for sysinstall, just as a replacement for a small but vital part of it. I'm not sure if that's what the OP meant or not...but thought I'd throw it out there in case anyone did. Yes, I'm in the process of building up a box I can dedicate to this project...new HD arrived today. What I envision is a text based system administration suite that will [hopefully] do everything that the "Configure" option on the top level of the sysinstall menu does. I see it as being part of the base OS, such that once one has rebooted from HD after the install and logged in as root [or user+su], a menu can be brought up by entering "sysadmin" or such. Does "sysadmin" work for a name? I kinda like it. I plan on basically going through the sysinstall post-configuration menu: Distributions Install additional distribution sets Documentation installation Install FreeBSD Documentation set Packages Install pre-packaged software for FreeBSD Root Password Set the system manager's password Fdisk The disk Slice (PC-style partition) Editor Label The disk Label editor User Management Add user and group information Console Customize system console behavior Time Zone Set which time zone you're in Media Change the installation media type Mouse Configure your mouse Networking Configure additional network services Security Configure system security options Startup Configure system startup options TTYs Configure system ttys. Options View/Set various installation options HTML Docs Go to the HTML documentation menu (post-ins Load KLD Load a KLD from a floppy and as close as reasonable, stick to the same task flow. I plan on writing it against 10-current and look at back-porting to 9 after it's somewhat stable. One new, important, and not-so-difficult task will be: on exiting, check the sanity of /etc/rc.conf and complain if needed, but allow the user to override the safety-switch if foot-shooting is really requested. :) I'm a firm believer of not disallowing anything. -- Ron McDowell San Antonio TX From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 02:57:44 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 30718106566B; Wed, 4 Jan 2012 02:57:44 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7714D8FC14; Wed, 4 Jan 2012 02:57:43 +0000 (UTC) Received: by lahl5 with SMTP id l5so8970298lah.13 for ; Tue, 03 Jan 2012 18:57:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=E/Z9w0gz4hbnfEqSPKycmIUj7e3IY9y9tPHp204PAbM=; b=tNBJgqtpy9i0dLHip6NGu7yTqqh0paMIca32q5WXN/UVaQw/M5ginLXH+pH3KoTuPS TnNQRVbfZpjwP4VOW+KSi3XHj/2uLRJo8tTWUKAHB4w+ff39WLUge1u/iqc9wyS14qvf FysNvYiF6sxKVJD32LNw3dDFJieJf7dmqZExk= Received: by 10.152.133.70 with SMTP id pa6mr44146253lab.0.1325645862091; Tue, 03 Jan 2012 18:57:42 -0800 (PST) MIME-Version: 1.0 Received: by 10.152.129.8 with HTTP; Tue, 3 Jan 2012 18:57:11 -0800 (PST) In-Reply-To: <4F03BE93.9040708@fuzzwad.org> References: <4F03AF24.70102@freebsd.org> <4F03BE93.9040708@fuzzwad.org> From: Eitan Adler Date: Tue, 3 Jan 2012 21:57:11 -0500 Message-ID: To: Ron McDowell Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Lawrence Stewart , freebsd-sysinstall@freebsd.org, Marcel Moolenaar Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 02:57:44 -0000 On Tue, Jan 3, 2012 at 9:50 PM, Ron McDowell wrote: > I [Ron] just added myself to the sysinstall list. Good > > What I envision is a text based system administration suite that will > [hopefully] do everything that the "Configure" option on the top level of > the sysinstall menu does. =C2=A0I see it as being part of the base OS, su= ch that > once one has rebooted from HD after the install and logged in as root [or > user+su], a menu can be brought up by entering "sysadmin" or such. =C2=A0= Does > "sysadmin" work for a name? =C2=A0I kinda like it. Do you plan on this tool being run "late in the game" after the system has been used for a while or this is a "welcome new user" only tool? > I plan on basically going through the sysinstall post-configuration menu: [snip configure menu] Do you plan on making this a C based program or a shell script? > and as close as reasonable, stick to the same task flow. =C2=A0I plan on = writing > it against 10-current and look at back-porting to 9 after it's somewhat > stable. I'd like to work with you on this, especially w.r.t to ensuring that it meets the requirements for entering the base system. > One new, important, and not-so-difficult task will be: on exiting, check = the > sanity of /etc/rc.conf and complain if needed, but allow the user to > override the safety-switch if foot-shooting is really requested. =C2=A0:)= =C2=A0I'm a > firm believer of not disallowing anything. Good on both counts. --=20 Eitan Adler From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 03:12:16 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E1EB106564A; Wed, 4 Jan 2012 03:12:16 +0000 (UTC) (envelope-from rcm@fuzzwad.org) Received: from mail.volente.us (unknown [IPv6:2001:470:7:d47::2]) by mx1.freebsd.org (Postfix) with ESMTP id 15E468FC15; Wed, 4 Jan 2012 03:12:15 +0000 (UTC) Received: from zombie.fuzzwad.net (localhost [127.0.0.1]) by mail.volente.us (8.14.4/8.14.4) with ESMTP id q043CDHU034790; Tue, 3 Jan 2012 21:12:14 -0600 (CST) (envelope-from rcm@fuzzwad.org) Message-ID: <4F03C38D.1080909@fuzzwad.org> Date: Tue, 03 Jan 2012 21:12:13 -0600 From: Ron McDowell User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Eitan Adler References: <4F03AF24.70102@freebsd.org> <4F03BE93.9040708@fuzzwad.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Lawrence Stewart , freebsd-sysinstall@freebsd.org, Marcel Moolenaar Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 03:12:16 -0000 Eitan Adler wrote: > On Tue, Jan 3, 2012 at 9:50 PM, Ron McDowell wrote: > >> I [Ron] just added myself to the sysinstall list. >> > > Good > >> What I envision is a text based system administration suite that will >> [hopefully] do everything that the "Configure" option on the top level of >> the sysinstall menu does. I see it as being part of the base OS, such that >> once one has rebooted from HD after the install and logged in as root [or >> user+su], a menu can be brought up by entering "sysadmin" or such. Does >> "sysadmin" work for a name? I kinda like it. >> > > Do you plan on this tool being run "late in the game" after the system > has been used for a while or this is a "welcome new user" only tool? > I want it to be both. Similar in concept to scoadmin on SCO, sysadm on SVR4, smit on AIX if you're familiar with any of them. >> I plan on basically going through the sysinstall post-configuration menu: >> > > [snip configure menu] > [apologies for the way that menu came out..."worked fine on my email!" :) ] > Do you plan on making this a C based program or a shell script? > /bin/sh and hopefully use the dialog library like sysinstall, if it can be made to do what needs doing. >> and as close as reasonable, stick to the same task flow. I plan on writing >> it against 10-current and look at back-porting to 9 after it's somewhat >> stable. >> > > I'd like to work with you on this, especially w.r.t to ensuring that > it meets the requirements for entering the base system. > Great! Give me a few days to get the box up and poke around with the dialog stuff, and I'll ping you then. >> One new, important, and not-so-difficult task will be: on exiting, check the >> sanity of /etc/rc.conf and complain if needed, but allow the user to >> override the safety-switch if foot-shooting is really requested. :) I'm a >> firm believer of not disallowing anything. >> > > Good on both counts. > > > -- Ron McDowell San Antonio TX From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 03:14:45 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1E69106566B for ; Wed, 4 Jan 2012 03:14:44 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 9EC5C8FC0A for ; Wed, 4 Jan 2012 03:14:44 +0000 (UTC) Received: from pps.filterd (ltcfislmsgpa02 [127.0.0.1]) by ltcfislmsgpa02.fnfis.com (8.14.4/8.14.4) with SMTP id q042Px8n021373; Tue, 3 Jan 2012 21:14:42 -0600 Received: from smtp.fisglobal.com ([10.132.206.17]) by ltcfislmsgpa02.fnfis.com with ESMTP id 124cffgbtj-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 03 Jan 2012 21:14:42 -0600 Received: from [10.0.0.104] (10.14.152.28) by smtp.fisglobal.com (10.132.206.17) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 3 Jan 2012 21:14:40 -0600 MIME-Version: 1.0 (Apple Message framework v1084) From: Devin Teske In-Reply-To: Date: Tue, 3 Jan 2012 19:14:38 -0800 Message-ID: <964E978A-C016-4A53-A034-8959140CDF68@fisglobal.com> References: <4F03AF24.70102@freebsd.org> <4F03BE93.9040708@fuzzwad.org> To: Eitan Adler X-Mailer: Apple Mail (2.1084) X-Originating-IP: [10.14.152.28] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.5.7110, 1.0.211, 0.0.0000 definitions=2012-01-03_03:2012-01-03, 2012-01-03, 1970-01-01 signatures=0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Devin, Marcel Moolenaar , Lawrence Stewart , freebsd-sysinstall@freebsd.org Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 03:14:45 -0000 On Jan 3, 2012, at 6:57 PM, Eitan Adler wrote: > On Tue, Jan 3, 2012 at 9:50 PM, Ron McDowell wrote: >> I [Ron] just added myself to the sysinstall list. >=20 > Good >>=20 >> What I envision is a text based system administration suite that will >> [hopefully] do everything that the "Configure" option on the top level of >> the sysinstall menu does. I see it as being part of the base OS, such t= hat >> once one has rebooted from HD after the install and logged in as root [or >> user+su], a menu can be brought up by entering "sysadmin" or such. Does >> "sysadmin" work for a name? I kinda like it. >=20 > Do you plan on this tool being run "late in the game" after the system > has been used for a while or this is a "welcome new user" only tool? >=20 >> I plan on basically going through the sysinstall post-configuration menu: >=20 > [snip configure menu] >=20 > Do you plan on making this a C based program or a shell script? If he plans on making it sh(1) based, then I wonder if he would be interest= ed in starting with host-setup as a very solid and robust substrate. I was just about to start building the port Makefile and getting host-setup= to fill this exact need. We @vicor have been working on this exact thing for years now. I feel that it would be a *very* simple task to add the remaining [missing]= menu items considering how hard it was to simply get this far. host-setup ... (we can change the name; I'll have to sleep on "sysadmin" --= leaning more toward perhaps "sysconfig" ... it's the logical name consider= ing we're taking the "Config[uration]" menu from "sys[install]", so the nam= e ought to perhaps be "sysconfig") ... is a multi-thousand-line shell scrip= t that uses a very full-proof approach to solving the problem. It's unbreak= able in its current form and has undergone hundreds of hours of testing (it= 's current version is 4.0.1). Oh, and it's BSD Licensed. Oh, and it's FreeBSD specific (originally works on both Linux and FreeBSD, = but we've stripped the Linux stuff to make it FreeBSD-clean). >=20 >> and as close as reasonable, stick to the same task flow. I plan on writ= ing >> it against 10-current and look at back-porting to 9 after it's somewhat >> stable. >=20 If you use host-setup as a substrate, it works on FreeBSD-4.x up to 10-CURR= ENT (tested 4.8, 4.11, 8.1, 9-CURRENT and 10-CURRENT). > I'd like to work with you on this, especially w.r.t to ensuring that > it meets the requirements for entering the base system. >=20 I too would like to work with you on this, regardless of language used or w= hether you use host-setup as a substrate or not. We also maintain a custom version of sysinstall in-house. So we're intimate= ly involved with all of the code. >> One new, important, and not-so-difficult task will be: on exiting, check= the >> sanity of /etc/rc.conf and complain if needed, but allow the user to >> override the safety-switch if foot-shooting is really requested. :) I'= m a >> firm believer of not disallowing anything. > Good on both counts. host-setup actually leverages the power and safety of my sysrc(8) utility (= just added to ports tree as sysutils/sysrc). In fact, sysrc was written as a test-script solely to feed back into host-s= etup so that we could replace sysinstall's Configure menu. We're just not t= here with all the menu items (but we've got the most important ones -- IMHO= -- and made them rock-stable). --=20 Devin Links: http://druidbsd.sourceforge.net/ http://druidbsd.sourceforge.net/download/host-setup.txt http://druidbsd.sourceforge.net/download/sysrc.txt _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 03:23:08 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B8661065672 for ; Wed, 4 Jan 2012 03:23:08 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 16DE28FC12 for ; Wed, 4 Jan 2012 03:23:07 +0000 (UTC) Received: from pps.filterd (ltcfislmsgpa02 [127.0.0.1]) by ltcfislmsgpa02.fnfis.com (8.14.4/8.14.4) with SMTP id q042Ql7c022361; Tue, 3 Jan 2012 21:23:06 -0600 Received: from smtp.fisglobal.com ([10.132.206.16]) by ltcfislmsgpa02.fnfis.com with ESMTP id 124cffgcex-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 03 Jan 2012 21:23:06 -0600 Received: from [10.0.0.104] (10.14.152.28) by smtp.fisglobal.com (10.132.206.16) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 3 Jan 2012 21:23:04 -0600 MIME-Version: 1.0 (Apple Message framework v1084) From: Devin Teske In-Reply-To: <4F03C38D.1080909@fuzzwad.org> Date: Tue, 3 Jan 2012 19:23:02 -0800 Message-ID: <678B5145-6FA4-489D-A31B-DDD3A6876DA7@fisglobal.com> References: <4F03AF24.70102@freebsd.org> <4F03BE93.9040708@fuzzwad.org> <4F03C38D.1080909@fuzzwad.org> To: Ron McDowell X-Mailer: Apple Mail (2.1084) X-Originating-IP: [10.14.152.28] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.5.7110, 1.0.211, 0.0.0000 definitions=2012-01-03_03:2012-01-03, 2012-01-03, 1970-01-01 signatures=0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Marcel Moolenaar , freebsd-sysinstall@freebsd.org, Lawrence Stewart Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 03:23:08 -0000 On Jan 3, 2012, at 7:12 PM, Ron McDowell wrote: > Eitan Adler wrote: >> On Tue, Jan 3, 2012 at 9:50 PM, Ron McDowell wrote: >>=20=20 >>> I [Ron] just added myself to the sysinstall list. >>>=20=20=20=20 >>=20 >> Good >>=20=20 >>> What I envision is a text based system administration suite that will >>> [hopefully] do everything that the "Configure" option on the top level = of >>> the sysinstall menu does. I see it as being part of the base OS, such = that >>> once one has rebooted from HD after the install and logged in as root [= or >>> user+su], a menu can be brought up by entering "sysadmin" or such. Does >>> "sysadmin" work for a name? I kinda like it. >>>=20=20=20=20 >>=20 >> Do you plan on this tool being run "late in the game" after the system >> has been used for a while or this is a "welcome new user" only tool? >>=20=20 >=20 > I want it to be both. Similar in concept to scoadmin on SCO, sysadm on S= VR4, smit on AIX if you're familiar with any of them. >=20 Same exact ideas host-setup was built on. We actually have a customized installer that set's the root-user's login sh= ell to this (perfectly safe for you to try, by the way -- it resets to csh = on Ctrl-C or Exit). But I use it almost on a daily basis to change settings as it saves me so m= uch time (we made it very smart -- when it asks you "Would you like to brin= g [interface] up" and you say "Yes" ... it actually does it ... unlike sysi= nstall(8), lol). >>> I plan on basically going through the sysinstall post-configuration men= u: >>>=20=20=20=20 >>=20 >> [snip configure menu] >>=20=20 >=20 > [apologies for the way that menu came out..."worked fine on my email!" :)= ] >=20 >> Do you plan on making this a C based program or a shell script? >>=20=20 >=20 > /bin/sh and hopefully use the dialog library like sysinstall, if it can b= e made to do what needs doing. If you have a look at host-setup, you'll see we fully support three version= s of $DIALOG ... dialog(1) from FreeBSD-8.x and earlier dialog(1) from FreeBSD-9.x and higher (which is now "cdialog" as imported b= y NWhitehorn) Xdialog(1) available from ports (x11/xdialog) It can also be configured as a menu-item in your window manager (exec host-= setup -sX) or even display manager running as root (similarly, exec host-se= tup -sX). HINT: it [safely] prompts for sudo(8) credentials using Xdialog(1= )'s --password box >=20 >>> and as close as reasonable, stick to the same task flow. I plan on wri= ting >>> it against 10-current and look at back-porting to 9 after it's somewhat >>> stable. >>>=20=20=20=20 >>=20 >> I'd like to work with you on this, especially w.r.t to ensuring that >> it meets the requirements for entering the base system. >>=20=20 >=20 > Great! Give me a few days to get the box up and poke around with the dia= log stuff, and I'll ping you then. >=20 Can you try host-setup on your new box? http://druidbsd.sourceforge.net/download/host-setup.txt --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 03:27:11 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07658106564A; Wed, 4 Jan 2012 03:27:11 +0000 (UTC) (envelope-from rcm@fuzzwad.org) Received: from mail.volente.us (unknown [IPv6:2001:470:7:d47::2]) by mx1.freebsd.org (Postfix) with ESMTP id 9E0458FC0C; Wed, 4 Jan 2012 03:27:10 +0000 (UTC) Received: from zombie.fuzzwad.net (localhost [127.0.0.1]) by mail.volente.us (8.14.4/8.14.4) with ESMTP id q043R54L034983; Tue, 3 Jan 2012 21:27:06 -0600 (CST) (envelope-from rcm@fuzzwad.org) Message-ID: <4F03C709.9@fuzzwad.org> Date: Tue, 03 Jan 2012 21:27:05 -0600 From: Ron McDowell User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Devin Teske References: <4F03AF24.70102@freebsd.org> <4F03BE93.9040708@fuzzwad.org> <964E978A-C016-4A53-A034-8959140CDF68@fisglobal.com> In-Reply-To: <964E978A-C016-4A53-A034-8959140CDF68@fisglobal.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Marcel Moolenaar , freebsd-sysinstall@freebsd.org, Lawrence Stewart Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 03:27:11 -0000 Devin Teske wrote: > > On Jan 3, 2012, at 6:57 PM, Eitan Adler wrote: > >> On Tue, Jan 3, 2012 at 9:50 PM, Ron McDowell > > wrote: >>> I [Ron] just added myself to the sysinstall list. >> >> Good >>> >>> What I envision is a text based system administration suite that will >>> [hopefully] do everything that the "Configure" option on the top >>> level of >>> the sysinstall menu does. I see it as being part of the base OS, >>> such that >>> once one has rebooted from HD after the install and logged in as >>> root [or >>> user+su], a menu can be brought up by entering "sysadmin" or such. Does >>> "sysadmin" work for a name? I kinda like it. >> >> Do you plan on this tool being run "late in the game" after the system >> has been used for a while or this is a "welcome new user" only tool? >> >>> I plan on basically going through the sysinstall post-configuration >>> menu: >> >> [snip configure menu] >> >> Do you plan on making this a C based program or a shell script? > > If he plans on making it sh(1) based, then I wonder if he would be > interested in starting with host-setup as a very solid and robust > substrate. > > I was just about to start building the port Makefile and getting > host-setup to fill this exact need. > > We @vicor have been working on this exact thing for years now. > > I feel that it would be a *very* simple task to add the remaining > [missing] menu items considering how hard it was to simply get this far. > > host-setup ... (we can change the name; I'll have to sleep on > "sysadmin" -- leaning more toward perhaps "sysconfig" ... it's the > logical name considering we're taking the "Config[uration]" menu from > "sys[install]", so the name ought to perhaps be "sysconfig") ... is a > multi-thousand-line shell script that uses a very full-proof approach > to solving the problem. It's unbreakable in its current form and has > undergone hundreds of hours of testing (it's current version is 4.0.1). > > Oh, and it's BSD Licensed. > > Oh, and it's FreeBSD specific (originally works on both Linux and > FreeBSD, but we've stripped the Linux stuff to make it FreeBSD-clean). > > >> >>> and as close as reasonable, stick to the same task flow. I plan on >>> writing >>> it against 10-current and look at back-porting to 9 after it's somewhat >>> stable. >> > > If you use host-setup as a substrate, it works on FreeBSD-4.x up to > 10-CURRENT (tested 4.8, 4.11, 8.1, 9-CURRENT and 10-CURRENT). > > >> I'd like to work with you on this, especially w.r.t to ensuring that >> it meets the requirements for entering the base system. >> > > I too would like to work with you on this, regardless of language used > or whether you use host-setup as a substrate or not. > > We also maintain a custom version of sysinstall in-house. So we're > intimately involved with all of the code. > > >>> One new, important, and not-so-difficult task will be: on exiting, >>> check the >>> sanity of /etc/rc.conf and complain if needed, but allow the user to >>> override the safety-switch if foot-shooting is really requested. :) >>> I'm a >>> firm believer of not disallowing anything. > >> Good on both counts. > > host-setup actually leverages the power and safety of my sysrc(8) > utility (just added to ports tree as sysutils/sysrc). > > In fact, sysrc was written as a test-script solely to feed back into > host-setup so that we could replace sysinstall's Configure menu. We're > just not there with all the menu items (but we've got the most > important ones -- IMHO -- and made them rock-stable). > -- > Devin > > Links: > http://druidbsd.sourceforge.net/ > http://druidbsd.sourceforge.net/download/host-setup.txt > http://druidbsd.sourceforge.net/download/sysrc.txt > _____________ > The information contained in this message is proprietary and/or > confidential. If you are not the intended recipient, please: (i) > delete the message and all copies; (ii) do not disclose, distribute or > use the message in any manner; and (iii) notify the sender > immediately. In addition, please be aware that any message addressed > to our domain is subject to archiving and review by persons other than > the intended recipient. Thank you. Devin, thanks, this looks very intriguing, pulling it down now. And sysconfig is a good name, better than sysadmin. -- Ron McDowell San Antonio TX From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 03:31:27 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 46739106566C; Wed, 4 Jan 2012 03:31:27 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8495D8FC12; Wed, 4 Jan 2012 03:31:26 +0000 (UTC) Received: by lahl5 with SMTP id l5so8976926lah.13 for ; Tue, 03 Jan 2012 19:31:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=dujVB5HF8jlvQbPa5wD8IVsFnzxj0lfus6SlwU+mCbc=; b=HvF8goN9kzI2gO13cXLCrPkvAAcXcgxcHUWWVhz9L3oCl5QsdRW58ycusulXSpRgwZ wkfNu6GJgovv6Ptt02zpQtTRV2zx9TFL8CxHY1n934ieA4QAqZItkyFhX7h5NdA/Eabn dvDriboar1Xmz931JtgTjrVPtJKSXqNkE8MXU= Received: by 10.152.106.227 with SMTP id gx3mr21608342lab.45.1325647885115; Tue, 03 Jan 2012 19:31:25 -0800 (PST) MIME-Version: 1.0 Received: by 10.152.129.8 with HTTP; Tue, 3 Jan 2012 19:30:54 -0800 (PST) In-Reply-To: <964E978A-C016-4A53-A034-8959140CDF68@fisglobal.com> References: <4F03AF24.70102@freebsd.org> <4F03BE93.9040708@fuzzwad.org> <964E978A-C016-4A53-A034-8959140CDF68@fisglobal.com> From: Eitan Adler Date: Tue, 3 Jan 2012 22:30:54 -0500 Message-ID: To: Devin Teske Content-Type: text/plain; charset=UTF-8 Cc: Lawrence Stewart , freebsd-sysinstall@freebsd.org, Marcel Moolenaar Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 03:31:27 -0000 On Tue, Jan 3, 2012 at 10:14 PM, Devin Teske wrote: > host-setup actually leverages the power and safety of my sysrc(8) utility > (just added to ports tree as sysutils/sysrc). > > In fact, sysrc was written as a test-script solely to feed back into > host-setup so that we could replace sysinstall's Configure menu. We're just > not there with all the menu items (but we've got the most important ones -- > IMHO -- and made them rock-stable). I want to see these tools in the base system. -- Eitan Adler From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 03:39:17 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36E3E1065735; Wed, 4 Jan 2012 03:39:17 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id DF4CB8FC14; Wed, 4 Jan 2012 03:39:16 +0000 (UTC) Received: by obbwd18 with SMTP id wd18so19662403obb.13 for ; Tue, 03 Jan 2012 19:39:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=E7pgaVkh/ixkEAB38bMcOa2sGQf9HBC2VUUFenXtawE=; b=sEeJMpPh26pmgeK+no5NpGNXiTbszfc9uBN1LzoK7CRKaYJcziURx6ZWw2FLu8dNZ0 q8SziMR4C/ENV8zrzRyXsLDz3VAXV4W4is1sXiftavAigqtoiiAgAvk+qj3LH3b8K6Ww +85Y7tixABifJYbs1190alfn0DK8TgusRWSjw= MIME-Version: 1.0 Received: by 10.182.164.106 with SMTP id yp10mr4058944obb.71.1325646561903; Tue, 03 Jan 2012 19:09:21 -0800 (PST) Received: by 10.182.152.6 with HTTP; Tue, 3 Jan 2012 19:09:21 -0800 (PST) In-Reply-To: References: <4F03AF24.70102@freebsd.org> <4F03BE93.9040708@fuzzwad.org> Date: Tue, 3 Jan 2012 19:09:21 -0800 Message-ID: From: Garrett Cooper To: Eitan Adler Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Lawrence Stewart , freebsd-sysinstall@freebsd.org, Marcel Moolenaar Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 03:39:17 -0000 On Tue, Jan 3, 2012 at 6:57 PM, Eitan Adler wrote: > On Tue, Jan 3, 2012 at 9:50 PM, Ron McDowell wrote: >> I [Ron] just added myself to the sysinstall list. > > Good >> >> What I envision is a text based system administration suite that will >> [hopefully] do everything that the "Configure" option on the top level o= f >> the sysinstall menu does. =A0I see it as being part of the base OS, such= that >> once one has rebooted from HD after the install and logged in as root [o= r >> user+su], a menu can be brought up by entering "sysadmin" or such. =A0Do= es >> "sysadmin" work for a name? =A0I kinda like it. > > Do you plan on this tool being run "late in the game" after the system > has been used for a while or this is a "welcome new user" only tool? > >> I plan on basically going through the sysinstall post-configuration menu= : > > [snip configure menu] > > Do you plan on making this a C based program or a shell script? > >> and as close as reasonable, stick to the same task flow. =A0I plan on wr= iting >> it against 10-current and look at back-porting to 9 after it's somewhat >> stable. > > I'd like to work with you on this, especially w.r.t to ensuring that > it meets the requirements for entering the base system. > >> One new, important, and not-so-difficult task will be: on exiting, check= the >> sanity of /etc/rc.conf and complain if needed, but allow the user to >> override the safety-switch if foot-shooting is really requested. =A0:) = =A0I'm a >> firm believer of not disallowing anything. > > Good on both counts. Please note that there's already existing infrastructure in FreeBSD that partitions UFS and ZFS: pc-sysinstall. This doesn't need to be [re]written... It needs polishing, maybe some work with non-Intel architectures, some documentation, and integration into a complete tool (and I will be the first to help out with this because I have the ear of several members who help maintain pc-sysinstall). In this case, all that really needs to be done is guide things with an ncurses frontend. That can be written in Unix shell with dialog to avoid bitrot that occurred with sysinstall when the underlying partitioning tools and defacto method of doing things in C dramatically changed (libdisk -> libgeom). It already works reasonably well for PC-BSD and is used by other projects such as FreeNAS. Thanks, -Garrett From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 03:53:07 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC3ED106564A; Wed, 4 Jan 2012 03:53:07 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 952728FC0C; Wed, 4 Jan 2012 03:53:07 +0000 (UTC) Received: from pps.filterd (ltcfislmsgpa03 [127.0.0.1]) by ltcfislmsgpa03.fnfis.com (8.14.4/8.14.4) with SMTP id q043Pb3D024238; Tue, 3 Jan 2012 21:53:05 -0600 Received: from smtp.fisglobal.com ([10.132.206.15]) by ltcfislmsgpa03.fnfis.com with ESMTP id 124c0g0h9k-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 03 Jan 2012 21:53:05 -0600 Received: from [10.0.0.104] (10.14.152.28) by smtp.fisglobal.com (10.132.206.15) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 3 Jan 2012 21:53:03 -0600 MIME-Version: 1.0 (Apple Message framework v1084) From: Devin Teske In-Reply-To: Date: Tue, 3 Jan 2012 19:53:00 -0800 Message-ID: References: <4F03AF24.70102@freebsd.org> <4F03BE93.9040708@fuzzwad.org> <964E978A-C016-4A53-A034-8959140CDF68@fisglobal.com> To: Eitan Adler X-Mailer: Apple Mail (2.1084) X-Originating-IP: [10.14.152.28] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.5.7110, 1.0.211, 0.0.0000 definitions=2012-01-03_03:2012-01-03, 2012-01-03, 1970-01-01 signatures=0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Devin, Marcel Moolenaar , Lawrence Stewart , freebsd-sysinstall@freebsd.org Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 03:53:07 -0000 On Jan 3, 2012, at 7:30 PM, Eitan Adler wrote: > On Tue, Jan 3, 2012 at 10:14 PM, Devin Teske = wrote: >> host-setup actually leverages the power and safety of my sysrc(8) utility >> (just added to ports tree as sysutils/sysrc). >>=20 >> In fact, sysrc was written as a test-script solely to feed back into >> host-setup so that we could replace sysinstall's Configure menu. We're j= ust >> not there with all the menu items (but we've got the most important ones= -- >> IMHO -- and made them rock-stable). >=20 > I want to see these tools in the base system. Just FYI, I've got an open PR to update sysutils/sysrc from 3.2.1 to 3.2.2. PR ports/163797 Already assigned to someone (culot). I'm very happy with 3.2.2. But I'm sure it would have to be checked for sty= le compliance and sanitized before being brought into the base. As far as host-setup goes, let's get it into ports first, yeah? --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 04:06:45 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 656F6106566B for ; Wed, 4 Jan 2012 04:06:45 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id EB7F38FC12 for ; Wed, 4 Jan 2012 04:06:44 +0000 (UTC) Received: by eaaf13 with SMTP id f13so21730511eaa.13 for ; Tue, 03 Jan 2012 20:06:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=wb6dFNtV34OLxIQ28a74jLdkGANYhWl1ZZW+ZNmSjNE=; b=rrk3mxJr3l4gAoAN142Hu7sdUjSPAXHD+06XfPNhu5cBf44PTrv0wWlAdp0g01WaYA 3a7kv8mK3B/H7MDnDiWJMREO+ZBE8bD02p8e+kG5ho+6tilwANJ4UqGs884LA9PPTuKA eVImWqDbJEcEf1Y6+FWaBOIARKv5IQj2u9PHk= MIME-Version: 1.0 Received: by 10.205.129.3 with SMTP id hg3mr12639726bkc.20.1325648344640; Tue, 03 Jan 2012 19:39:04 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.205.115.138 with HTTP; Tue, 3 Jan 2012 19:39:04 -0800 (PST) In-Reply-To: <4F03A366.5030601@cran.org.uk> References: <4F03A366.5030601@cran.org.uk> Date: Tue, 3 Jan 2012 19:39:04 -0800 X-Google-Sender-Auth: 5ho492aD8Y3UXHOq0wM_ndBiIkU Message-ID: From: Craig Rodrigues To: Bruce Cran Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current Current , freebsd-sysinstall@freebsd.org, Marcel Moolenaar Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 04:06:45 -0000 On Tue, Jan 3, 2012 at 4:55 PM, Bruce Cran wrote: > There's a rewrite almost ready to go that supports ZFS etc. at > http://butcher.heavennet.ru/sade/ - I'm hoping to find some time to finish > it off and import it. > > -- > Bruce Cran > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Bruce, Where is the code for this? Would committing your sade additions now to a project branch in Subversion be appropriate? That way folks could check it out from SVN, and provide comments and patches, and help push things along faster. When your code is complete, it could be merged to HEAD. While I understand some of the concerns about removing sysinstall in HEAD, I think that sysinstall is so far behind the curve in usefulness, that I think that putting a bullet in its head now and forcing a mini-crisis to implement something better is not a bad idea, even though it may violate POLA. Many thanks to Nathan for all his latest work on the installer. The state of sysinstall today is worse than some of the installers I used in various Linux distributions about 15 years ago, and makes FreeBSD look silly for new users trying to set it up. I think we can do better. -- Craig Rodrigues rodrigc@crodrigues.org From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 04:08:07 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E90FF106566C; Wed, 4 Jan 2012 04:08:07 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id A20B38FC08; Wed, 4 Jan 2012 04:08:07 +0000 (UTC) Received: from pps.filterd (ltcfislmsgpa06 [127.0.0.1]) by ltcfislmsgpa06.fnfis.com (8.14.4/8.14.4) with SMTP id q043QIMa022985; Tue, 3 Jan 2012 22:08:05 -0600 Received: from smtp.fisglobal.com ([10.132.206.31]) by ltcfislmsgpa06.fnfis.com with ESMTP id 124c8srh0t-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 03 Jan 2012 22:08:05 -0600 Received: from [10.0.0.104] (10.14.152.28) by smtp.fisglobal.com (10.132.206.31) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 3 Jan 2012 22:08:03 -0600 MIME-Version: 1.0 (Apple Message framework v1084) From: Devin Teske In-Reply-To: Date: Tue, 3 Jan 2012 20:07:59 -0800 Message-ID: References: <4F03AF24.70102@freebsd.org> <4F03BE93.9040708@fuzzwad.org> <964E978A-C016-4A53-A034-8959140CDF68@fisglobal.com> To: Eitan Adler X-Mailer: Apple Mail (2.1084) X-Originating-IP: [10.14.152.28] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.5.7110, 1.0.211, 0.0.0000 definitions=2012-01-03_03:2012-01-03, 2012-01-03, 1970-01-01 signatures=0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Devin, Garrett Cooper , Marcel Moolenaar , Lawrence Stewart , freebsd-sysinstall@freebsd.org Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 04:08:08 -0000 On Jan 3, 2012, at 7:30 PM, Eitan Adler wrote: > On Tue, Jan 3, 2012 at 10:14 PM, Devin Teske = wrote: >> host-setup actually leverages the power and safety of my sysrc(8) utility >> (just added to ports tree as sysutils/sysrc). >>=20 >> In fact, sysrc was written as a test-script solely to feed back into >> host-setup so that we could replace sysinstall's Configure menu. We're j= ust >> not there with all the menu items (but we've got the most important ones= -- >> IMHO -- and made them rock-stable). >=20 > I want to see these tools in the base system. I should mention one more tool that plays into all this... tzdialog. Part of the puzzle to completing our quest of "replacing sysinstall" involv= ed rewriting tzsetup(8). Largely because we had written host-setup(1) to wo= rk with Xdialog(1) and therefore thought that it would be better to have a = tzsetup(8) that also supported Xdialog(1) rather than launching it within a= n xterm(1) (which was not-so-nice, but does work). In rewriting tzsetup(8) to produce tzdialog(1), I strived _very_ hard to ac= tually make it so that you can literally line up the C-code with the sh(1)-= code. Picking out comments that are word-for-word the same is one thing, bu= t re-using variable names and even going as far as to invent struct-analogs= with the same names is another story. All the sh(1)-code follows the exact= same logic as the C-code. When the C-code opens the ISO-3166 table from NI= ST and parses-out the data it needs, so does the sh(1)-code. Line-for-line,= we try to mimic the C-code for the express purpose that we can perhaps rep= lace tzsetup(8), but I'll let you be the judge. I mention all this, because host-setup(1) will automatically pick-up on the= existence of tzdialog(8) and prefer it as a drop-in replacement for tzsetu= p(8), should tzdialog(8) be installed and available. Thus, achieving the ab= ility to actually set the time-zone via host-setup from a menu-item configu= red in a window manager or display manager (HINT: We've got our fvwm2 confi= guration configured with "exec host-setup -sX" which correctly hands-off th= e "-X" flag to tzdialog). I haven't yet tossed the idea out there yet for creating a port for tzdialo= g(8) -- this is the first that I'm suggesting -- but since I'm going to mak= e a request to submit host-setup(8), I'd figure I ought to make a request f= or tzdialog too, since the former can take advantage of the latter if/when = installed. --=20 Devin Links: http://druidbsd.sourceforge.net/ http://druidbsd.sourceforge.net/download/tzdialog.txt _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 04:09:29 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B9C4106567B for ; Wed, 4 Jan 2012 04:09:29 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 1DFEA8FC1C for ; Wed, 4 Jan 2012 04:09:28 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q043eM6N019985; Tue, 3 Jan 2012 20:40:22 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q043eMLG019982; Tue, 3 Jan 2012 20:40:22 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Tue, 3 Jan 2012 20:40:22 -0700 (MST) From: Warren Block To: Ron McDowell In-Reply-To: <4F03C38D.1080909@fuzzwad.org> Message-ID: References: <4F03AF24.70102@freebsd.org> <4F03BE93.9040708@fuzzwad.org> <4F03C38D.1080909@fuzzwad.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Tue, 03 Jan 2012 20:40:22 -0700 (MST) Cc: Marcel Moolenaar , freebsd-sysinstall@freebsd.org, Lawrence Stewart Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 04:09:29 -0000 On Tue, 3 Jan 2012, Ron McDowell wrote: > Eitan Adler wrote: >> On Tue, Jan 3, 2012 at 9:50 PM, Ron McDowell wrote: >> >>> I [Ron] just added myself to the sysinstall list. >>> >> >> Good >> >>> What I envision is a text based system administration suite that will >>> [hopefully] do everything that the "Configure" option on the top level of >>> the sysinstall menu does. I see it as being part of the base OS, such >>> that >>> once one has rebooted from HD after the install and logged in as root [or >>> user+su], a menu can be brought up by entering "sysadmin" or such. Does >>> "sysadmin" work for a name? I kinda like it. >>> >> >> Do you plan on this tool being run "late in the game" after the system >> has been used for a while or this is a "welcome new user" only tool? >> > > I want it to be both. Similar in concept to scoadmin on SCO, sysadm on SVR4, > smit on AIX if you're familiar with any of them. bsdinstall already does some of these config things in the last menu. It really ought to be split into two pieces, bsdinstall to do the installing, and "bsdconfig", to do the configuring. bsdconfig would just be the pieces that are already there, run by bsdinstall after the installation but also useful separately. And then bsdconfig could have all the added config functionality that everyone loves about sysinstall. From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 04:25:47 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A3BF1065670 for ; Wed, 4 Jan 2012 04:25:47 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id 3435B8FC12 for ; Wed, 4 Jan 2012 04:25:45 +0000 (UTC) Received: from lstewart1.loshell.room52.net (ppp59-167-184-191.static.internode.on.net [59.167.184.191]) by lauren.room52.net (Postfix) with ESMTPSA id A29307E824; Wed, 4 Jan 2012 15:25:43 +1100 (EST) Message-ID: <4F03D4C7.2040703@freebsd.org> Date: Wed, 04 Jan 2012 15:25:43 +1100 From: Lawrence Stewart User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111016 Thunderbird/7.0.1 MIME-Version: 1.0 To: Ron McDowell References: <4F03AF24.70102@freebsd.org> <4F03BE93.9040708@fuzzwad.org> <964E978A-C016-4A53-A034-8959140CDF68@fisglobal.com> <4F03C709.9@fuzzwad.org> In-Reply-To: <4F03C709.9@fuzzwad.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lauren.room52.net Cc: Marcel Moolenaar , Devin Teske , freebsd-sysinstall@freebsd.org Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 04:25:47 -0000 On 01/04/12 14:27, Ron McDowell wrote: > > > Devin Teske wrote: >> >> On Jan 3, 2012, at 6:57 PM, Eitan Adler wrote: >> >>> On Tue, Jan 3, 2012 at 9:50 PM, Ron McDowell >> > wrote: >>>> I [Ron] just added myself to the sysinstall list. >>> >>> Good >>>> >>>> What I envision is a text based system administration suite that will >>>> [hopefully] do everything that the "Configure" option on the top >>>> level of >>>> the sysinstall menu does. I see it as being part of the base OS, >>>> such that >>>> once one has rebooted from HD after the install and logged in as >>>> root [or >>>> user+su], a menu can be brought up by entering "sysadmin" or such. Does >>>> "sysadmin" work for a name? I kinda like it. >>> >>> Do you plan on this tool being run "late in the game" after the system >>> has been used for a while or this is a "welcome new user" only tool? >>> >>>> I plan on basically going through the sysinstall post-configuration >>>> menu: >>> >>> [snip configure menu] >>> >>> Do you plan on making this a C based program or a shell script? >> >> If he plans on making it sh(1) based, then I wonder if he would be >> interested in starting with host-setup as a very solid and robust >> substrate. >> >> I was just about to start building the port Makefile and getting >> host-setup to fill this exact need. >> >> We @vicor have been working on this exact thing for years now. >> >> I feel that it would be a *very* simple task to add the remaining >> [missing] menu items considering how hard it was to simply get this far. >> >> host-setup ... (we can change the name; I'll have to sleep on >> "sysadmin" -- leaning more toward perhaps "sysconfig" ... it's the >> logical name considering we're taking the "Config[uration]" menu from >> "sys[install]", so the name ought to perhaps be "sysconfig") ... is a >> multi-thousand-line shell script that uses a very full-proof approach >> to solving the problem. It's unbreakable in its current form and has >> undergone hundreds of hours of testing (it's current version is 4.0.1). >> >> Oh, and it's BSD Licensed. >> >> Oh, and it's FreeBSD specific (originally works on both Linux and >> FreeBSD, but we've stripped the Linux stuff to make it FreeBSD-clean). >> >> >>> >>>> and as close as reasonable, stick to the same task flow. I plan on >>>> writing >>>> it against 10-current and look at back-porting to 9 after it's somewhat >>>> stable. >>> >> >> If you use host-setup as a substrate, it works on FreeBSD-4.x up to >> 10-CURRENT (tested 4.8, 4.11, 8.1, 9-CURRENT and 10-CURRENT). >> >> >>> I'd like to work with you on this, especially w.r.t to ensuring that >>> it meets the requirements for entering the base system. >>> >> >> I too would like to work with you on this, regardless of language used >> or whether you use host-setup as a substrate or not. >> >> We also maintain a custom version of sysinstall in-house. So we're >> intimately involved with all of the code. >> >> >>>> One new, important, and not-so-difficult task will be: on exiting, >>>> check the >>>> sanity of /etc/rc.conf and complain if needed, but allow the user to >>>> override the safety-switch if foot-shooting is really requested. :) >>>> I'm a >>>> firm believer of not disallowing anything. >> >>> Good on both counts. >> >> host-setup actually leverages the power and safety of my sysrc(8) >> utility (just added to ports tree as sysutils/sysrc). >> >> In fact, sysrc was written as a test-script solely to feed back into >> host-setup so that we could replace sysinstall's Configure menu. We're >> just not there with all the menu items (but we've got the most >> important ones -- IMHO -- and made them rock-stable). >> -- >> Devin >> >> Links: >> http://druidbsd.sourceforge.net/ >> http://druidbsd.sourceforge.net/download/host-setup.txt >> http://druidbsd.sourceforge.net/download/sysrc.txt > > Devin, thanks, this looks very intriguing, pulling it down now. And > sysconfig is a good name, better than sysadmin. I like how all this is sounding, and if host-setup turns out to be a good base (which it certainly sounds like it could be), this could all come together quite quickly. Whilst thinking about all the constraints and required/desired features, do keep in mind Marcel's concern and one of Nathan's aims with bsdinstall, which is that we need to be platform agnostic. powerpc and sparc64 at a minimum should be considered, even if only in so much as putting stubs in appropriate places for people who use those platforms to fill in later. Perhaps getting in touch with key platform maintainers to get a list of things that generally differ between x86 and that specific platform would help inform the process, so you get an idea where additional design discussion may be required... Onwards! Cheers, Lawrence From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 08:29:44 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 95DB51065670; Wed, 4 Jan 2012 08:29:42 +0000 (UTC) (envelope-from joel@freebsd.org) Received: from mail.vnode.se (mail.vnode.se [62.119.52.80]) by mx1.freebsd.org (Postfix) with ESMTP id 466588FC0A; Wed, 4 Jan 2012 08:29:42 +0000 (UTC) Received: from mail.vnode.se (localhost [127.0.0.1]) by mail.vnode.se (Postfix) with ESMTP id 57364E3F07A; Wed, 4 Jan 2012 09:11:56 +0100 (CET) X-Virus-Scanned: amavisd-new at vnode.se Received: from mail.vnode.se ([127.0.0.1]) by mail.vnode.se (mail.vnode.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yFZ9GaZkoOU3; Wed, 4 Jan 2012 09:11:53 +0100 (CET) Received: from goofy01.vnodelab.local (unknown [212.247.52.12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.vnode.se (Postfix) with ESMTPSA id 6C1B0E3F079; Wed, 4 Jan 2012 09:11:53 +0100 (CET) Date: Wed, 4 Jan 2012 09:11:51 +0100 From: Joel Dahl To: Eitan Adler Message-ID: <20120104081151.GC61584@goofy01.vnodelab.local> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current Current , freebsd-sysinstall@freebsd.org Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 08:29:44 -0000 On 03-01-2012 18:33, Eitan Adler wrote: > Hi, > > In the the recent sysinstall thread there seems to be general agreement that > having a post-install configuration tool is a good thing. Until such a > tool is written I think it would be a good idea to use sysinstall for > this purpose. I am willing to do the work to restore sysinstall and > maintain it as a post-install tool until a new one is written. > > My plan would be to: > > - Restore sysinstall and libodialog You should read the following post by Freddie Cash to current@, in case you haven't seen it: http://lists.freebsd.org/pipermail/freebsd-current/2012-January/030954.html I agree with all his points. -- Joel From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 08:52:56 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 48BAC10656B0; Wed, 4 Jan 2012 08:52:56 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id C244F8FC16; Wed, 4 Jan 2012 08:52:55 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id B26B1E622D; Wed, 4 Jan 2012 08:52:54 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cran.org.uk; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=mail; bh=HAc34GAI6XNq aQqzcNs0+H9n/+Q=; b=X/Zr6MjhIXGgXqKcsfQFUwjnyrl3nyATirpyNITkB6LL sHfiUS6NJ02MimH+Sixe6qBuQ/Voa7HHCVpxd3P5U1LXNQWdhYLUGioEp3WE+uyK agX5VHsYg+KfUOFxTUj7FZJjfqQvRRRiQan6AifBdAszo09sg4NLd2ogYFKAC4E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=cran.org.uk; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=mail; b=Y+UN/i 4yTHWM6tBu9wlK8HC9SEtxuMYcixOjaCBIUvHslppSZ4MoJlsvXrorDTkIDom6NM 6vy5ITAwyD/L6jUoqzY5587qW/5pMFrjfnJPZXkW7enSUi0+nRmqzWMACvn81CZ5 qpeT1PEuhUo4sW9DyIyGI/Kt+3oMm1agETZ8A= Received: from [192.168.1.66] (188-220-36-32.zone11.bethere.co.uk [188.220.36.32]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 7A2F8E6219; Wed, 4 Jan 2012 08:52:54 +0000 (GMT) Message-ID: <4F041361.7000802@cran.org.uk> Date: Wed, 04 Jan 2012 08:52:49 +0000 From: Bruce Cran User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: Craig Rodrigues References: <4F03A366.5030601@cran.org.uk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current Current , freebsd-sysinstall@freebsd.org, Marcel Moolenaar Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 08:52:56 -0000 On 04/01/2012 03:39, Craig Rodrigues wrote: > Where is the code for this? Would committing your sade additions now > to a project branch in Subversion > be appropriate? That way folks could check it out from SVN, and > provide comments and patches, > and help push things along faster. > When your code is complete, it could be merged to HEAD. I didn't do the work, it was Andrey Elsukov (ae@) - the code's at http://svnweb.freebsd.org/base/user/ae/usr.sbin/sade/ . > While I understand some of the concerns about removing sysinstall in HEAD, > I think that sysinstall is so far behind the curve in usefulness, that I think > that putting a bullet in its head now and forcing a mini-crisis to > implement something better is not a bad idea, > even though it may violate POLA. I can see that people prefer bsdinstall so I'll stop trying to keep sysinstall going. -- Bruce Cran From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 16:43:18 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B8881065716 for ; Wed, 4 Jan 2012 16:43:15 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from agogare.doit.wisc.edu (agogare.doit.wisc.edu [144.92.197.211]) by mx1.freebsd.org (Postfix) with ESMTP id C090B8FC14 for ; Wed, 4 Jan 2012 16:43:15 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from avs-daemon.smtpauth2.wiscmail.wisc.edu by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0LXA009026C21000@smtpauth2.wiscmail.wisc.edu>; Wed, 04 Jan 2012 09:43:14 -0600 (CST) Received: from comporellon.tachypleus.net ([unknown] [76.210.61.211]) by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0LXA006JX6BWIE00@smtpauth2.wiscmail.wisc.edu>; Wed, 04 Jan 2012 09:43:08 -0600 (CST) Date: Wed, 04 Jan 2012 09:43:07 -0600 From: Nathan Whitehorn In-reply-to: <4F03D4C7.2040703@freebsd.org> To: Lawrence Stewart Message-id: <4F04738B.7010705@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.210.61.211 X-Spam-PmxInfo: Server=avs-12, Version=5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.1.4.153018, SenderIP=76.210.61.211 References: <4F03AF24.70102@freebsd.org> <4F03BE93.9040708@fuzzwad.org> <964E978A-C016-4A53-A034-8959140CDF68@fisglobal.com> <4F03C709.9@fuzzwad.org> <4F03D4C7.2040703@freebsd.org> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:8.0) Gecko/20111113 Thunderbird/8.0 Cc: freebsd-sysinstall@freebsd.org, Devin Teske , Marcel Moolenaar Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 16:43:18 -0000 On 01/03/12 22:25, Lawrence Stewart wrote: > On 01/04/12 14:27, Ron McDowell wrote: >> >> >> Devin Teske wrote: >>> >>> On Jan 3, 2012, at 6:57 PM, Eitan Adler wrote: >>> >>>> On Tue, Jan 3, 2012 at 9:50 PM, Ron McDowell >>> > wrote: >>>>> I [Ron] just added myself to the sysinstall list. >>>> >>>> Good >>>>> >>>>> What I envision is a text based system administration suite that will >>>>> [hopefully] do everything that the "Configure" option on the top >>>>> level of >>>>> the sysinstall menu does. I see it as being part of the base OS, >>>>> such that >>>>> once one has rebooted from HD after the install and logged in as >>>>> root [or >>>>> user+su], a menu can be brought up by entering "sysadmin" or such. >>>>> Does >>>>> "sysadmin" work for a name? I kinda like it. >>>> >>>> Do you plan on this tool being run "late in the game" after the system >>>> has been used for a while or this is a "welcome new user" only tool? >>>> >>>>> I plan on basically going through the sysinstall post-configuration >>>>> menu: >>>> >>>> [snip configure menu] >>>> >>>> Do you plan on making this a C based program or a shell script? >>> >>> If he plans on making it sh(1) based, then I wonder if he would be >>> interested in starting with host-setup as a very solid and robust >>> substrate. >>> >>> I was just about to start building the port Makefile and getting >>> host-setup to fill this exact need. >>> >>> We @vicor have been working on this exact thing for years now. >>> >>> I feel that it would be a *very* simple task to add the remaining >>> [missing] menu items considering how hard it was to simply get this >>> far. >>> >>> host-setup ... (we can change the name; I'll have to sleep on >>> "sysadmin" -- leaning more toward perhaps "sysconfig" ... it's the >>> logical name considering we're taking the "Config[uration]" menu from >>> "sys[install]", so the name ought to perhaps be "sysconfig") ... is a >>> multi-thousand-line shell script that uses a very full-proof approach >>> to solving the problem. It's unbreakable in its current form and has >>> undergone hundreds of hours of testing (it's current version is 4.0.1). >>> >>> Oh, and it's BSD Licensed. >>> >>> Oh, and it's FreeBSD specific (originally works on both Linux and >>> FreeBSD, but we've stripped the Linux stuff to make it FreeBSD-clean). >>> >>> >>>> >>>>> and as close as reasonable, stick to the same task flow. I plan on >>>>> writing >>>>> it against 10-current and look at back-porting to 9 after it's >>>>> somewhat >>>>> stable. >>>> >>> >>> If you use host-setup as a substrate, it works on FreeBSD-4.x up to >>> 10-CURRENT (tested 4.8, 4.11, 8.1, 9-CURRENT and 10-CURRENT). >>> >>> >>>> I'd like to work with you on this, especially w.r.t to ensuring that >>>> it meets the requirements for entering the base system. >>>> >>> >>> I too would like to work with you on this, regardless of language used >>> or whether you use host-setup as a substrate or not. >>> >>> We also maintain a custom version of sysinstall in-house. So we're >>> intimately involved with all of the code. >>> >>> >>>>> One new, important, and not-so-difficult task will be: on exiting, >>>>> check the >>>>> sanity of /etc/rc.conf and complain if needed, but allow the user to >>>>> override the safety-switch if foot-shooting is really requested. :) >>>>> I'm a >>>>> firm believer of not disallowing anything. >>> >>>> Good on both counts. >>> >>> host-setup actually leverages the power and safety of my sysrc(8) >>> utility (just added to ports tree as sysutils/sysrc). >>> >>> In fact, sysrc was written as a test-script solely to feed back into >>> host-setup so that we could replace sysinstall's Configure menu. We're >>> just not there with all the menu items (but we've got the most >>> important ones -- IMHO -- and made them rock-stable). >>> -- >>> Devin >>> >>> Links: >>> http://druidbsd.sourceforge.net/ >>> http://druidbsd.sourceforge.net/download/host-setup.txt >>> http://druidbsd.sourceforge.net/download/sysrc.txt >> >> Devin, thanks, this looks very intriguing, pulling it down now. And >> sysconfig is a good name, better than sysadmin. > > I like how all this is sounding, and if host-setup turns out to be a > good base (which it certainly sounds like it could be), this could all > come together quite quickly. > > Whilst thinking about all the constraints and required/desired > features, do keep in mind Marcel's concern and one of Nathan's aims > with bsdinstall, which is that we need to be platform agnostic. > powerpc and sparc64 at a minimum should be considered, even if only in > so much as putting stubs in appropriate places for people who use > those platforms to fill in later. > > Perhaps getting in touch with key platform maintainers to get a list > of things that generally differ between x86 and that specific platform > would help inform the process, so you get an idea where additional > design discussion may be required... > > Onwards! Hopefully, sysconfig won't do anything very platform specific (setting up partition tables, etc.), so this shouldn't be too much of an issue. But please do check in if you have doubts. One brief comment I have on your code is with the giant table of driver name -> description. I realize this was copied from sysinstall, but you can get this in a much easier way by doing: sysctl -n dev.$(echo $IF | sed -E 's/([[:alpha:]]*)([[:digit:]]*)/\1.\2/g').%desc -Nathan From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 17:02:58 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E28601065676; Wed, 4 Jan 2012 17:02:58 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 9D0688FC14; Wed, 4 Jan 2012 17:02:58 +0000 (UTC) Received: from pps.filterd (ltcfislmsgpa07 [127.0.0.1]) by ltcfislmsgpa07.fnfis.com (8.14.4/8.14.4) with SMTP id q04GRm5x028606; Wed, 4 Jan 2012 11:02:54 -0600 Received: from smtp.fisglobal.com ([10.132.206.16]) by ltcfislmsgpa07.fnfis.com with ESMTP id 124t59r671-55 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 04 Jan 2012 11:02:54 -0600 Received: from dtwin (10.14.152.15) by smtp.fisglobal.com (10.132.206.16) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 4 Jan 2012 11:02:35 -0600 From: Devin Teske To: "'Nathan Whitehorn'" , "'Lawrence Stewart'" References: <4F03AF24.70102@freebsd.org> <4F03BE93.9040708@fuzzwad.org> <964E978A-C016-4A53-A034-8959140CDF68@fisglobal.com> <4F03C709.9@fuzzwad.org> <4F03D4C7.2040703@freebsd.org> <4F04738B.7010705@freebsd.org> In-Reply-To: <4F04738B.7010705@freebsd.org> Date: Wed, 4 Jan 2012 09:02:42 -0800 Message-ID: <05a001cccb02$ad0d12b0$07273810$@fisglobal.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQGioPys4U3YFAHSWDxI2KBhfkp2BwIq9j8xAfDLopcCvv0auQFUZietAi8uHZUCO0oxxQEXtDuqAaHZ5PmV1ifrMA== Content-Language: en-us X-Originating-IP: [10.14.152.15] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.5.7110, 1.0.211, 0.0.0000 definitions=2012-01-04_06:2012-01-04, 2012-01-04, 1970-01-01 signatures=0 Cc: freebsd-sysinstall@freebsd.org, devin.teske@fisglobal.com, 'Marcel Moolenaar' Subject: RE: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 17:02:59 -0000 > -----Original Message----- > From: Nathan Whitehorn [mailto:nwhitehorn@freebsd.org] > Sent: Wednesday, January 04, 2012 7:43 AM > To: Lawrence Stewart > Cc: Ron McDowell; Marcel Moolenaar; Devin Teske; freebsd- > sysinstall@freebsd.org > Subject: Re: sysinstall as a post-install tool > > On 01/03/12 22:25, Lawrence Stewart wrote: > > On 01/04/12 14:27, Ron McDowell wrote: > >> > >> > >> Devin Teske wrote: > >>> > >>> On Jan 3, 2012, at 6:57 PM, Eitan Adler wrote: > >>> > >>>> On Tue, Jan 3, 2012 at 9:50 PM, Ron McDowell >>>> > wrote: > >>>>> I [Ron] just added myself to the sysinstall list. > >>>> > >>>> Good > >>>>> > >>>>> What I envision is a text based system administration suite that > >>>>> will [hopefully] do everything that the "Configure" option on the > >>>>> top level of the sysinstall menu does. I see it as being part of > >>>>> the base OS, such that once one has rebooted from HD after the > >>>>> install and logged in as root [or > >>>>> user+su], a menu can be brought up by entering "sysadmin" or such. > >>>>> Does > >>>>> "sysadmin" work for a name? I kinda like it. > >>>> > >>>> Do you plan on this tool being run "late in the game" after the > >>>> system has been used for a while or this is a "welcome new user" only tool? > >>>> > >>>>> I plan on basically going through the sysinstall > >>>>> post-configuration > >>>>> menu: > >>>> > >>>> [snip configure menu] > >>>> > >>>> Do you plan on making this a C based program or a shell script? > >>> > >>> If he plans on making it sh(1) based, then I wonder if he would be > >>> interested in starting with host-setup as a very solid and robust > >>> substrate. > >>> > >>> I was just about to start building the port Makefile and getting > >>> host-setup to fill this exact need. > >>> > >>> We @vicor have been working on this exact thing for years now. > >>> > >>> I feel that it would be a *very* simple task to add the remaining > >>> [missing] menu items considering how hard it was to simply get this > >>> far. > >>> > >>> host-setup ... (we can change the name; I'll have to sleep on > >>> "sysadmin" -- leaning more toward perhaps "sysconfig" ... it's the > >>> logical name considering we're taking the "Config[uration]" menu > >>> from "sys[install]", so the name ought to perhaps be "sysconfig") > >>> ... is a multi-thousand-line shell script that uses a very > >>> full-proof approach to solving the problem. It's unbreakable in its > >>> current form and has undergone hundreds of hours of testing (it's current > version is 4.0.1). > >>> > >>> Oh, and it's BSD Licensed. > >>> > >>> Oh, and it's FreeBSD specific (originally works on both Linux and > >>> FreeBSD, but we've stripped the Linux stuff to make it FreeBSD-clean). > >>> > >>> > >>>> > >>>>> and as close as reasonable, stick to the same task flow. I plan on > >>>>> writing it against 10-current and look at back-porting to 9 after > >>>>> it's somewhat stable. > >>>> > >>> > >>> If you use host-setup as a substrate, it works on FreeBSD-4.x up to > >>> 10-CURRENT (tested 4.8, 4.11, 8.1, 9-CURRENT and 10-CURRENT). > >>> > >>> > >>>> I'd like to work with you on this, especially w.r.t to ensuring > >>>> that it meets the requirements for entering the base system. > >>>> > >>> > >>> I too would like to work with you on this, regardless of language > >>> used or whether you use host-setup as a substrate or not. > >>> > >>> We also maintain a custom version of sysinstall in-house. So we're > >>> intimately involved with all of the code. > >>> > >>> > >>>>> One new, important, and not-so-difficult task will be: on exiting, > >>>>> check the sanity of /etc/rc.conf and complain if needed, but allow > >>>>> the user to override the safety-switch if foot-shooting is really > >>>>> requested. :) I'm a firm believer of not disallowing anything. > >>> > >>>> Good on both counts. > >>> > >>> host-setup actually leverages the power and safety of my sysrc(8) > >>> utility (just added to ports tree as sysutils/sysrc). > >>> > >>> In fact, sysrc was written as a test-script solely to feed back into > >>> host-setup so that we could replace sysinstall's Configure menu. > >>> We're just not there with all the menu items (but we've got the most > >>> important ones -- IMHO -- and made them rock-stable). > >>> -- > >>> Devin > >>> > >>> Links: > >>> http://druidbsd.sourceforge.net/ > >>> http://druidbsd.sourceforge.net/download/host-setup.txt > >>> http://druidbsd.sourceforge.net/download/sysrc.txt > >> > >> Devin, thanks, this looks very intriguing, pulling it down now. And > >> sysconfig is a good name, better than sysadmin. > > > > I like how all this is sounding, and if host-setup turns out to be a > > good base (which it certainly sounds like it could be), this could all > > come together quite quickly. > > > > Whilst thinking about all the constraints and required/desired > > features, do keep in mind Marcel's concern and one of Nathan's aims > > with bsdinstall, which is that we need to be platform agnostic. > > powerpc and sparc64 at a minimum should be considered, even if only in > > so much as putting stubs in appropriate places for people who use > > those platforms to fill in later. > > > > Perhaps getting in touch with key platform maintainers to get a list > > of things that generally differ between x86 and that specific platform > > would help inform the process, so you get an idea where additional > > design discussion may be required... > > > > Onwards! > > Hopefully, sysconfig won't do anything very platform specific (setting up partition > tables, etc.), so this shouldn't be too much of an issue. > But please do check in if you have doubts. > > One brief comment I have on your code is with the giant table of driver name -> > description. I realize this was copied from sysinstall, but you can get this in a much > easier way by doing: > sysctl -n dev.$(echo $IF | sed -E > 's/([[:alpha:]]*)([[:digit:]]*)/\1.\2/g').%desc > -Nathan If/When we clean up host-setup for the base, I indeed advocate making the change you suggest. However, The following is probably a bit cleaner (doesn't require a fork of sed): IF=fxp0 sysctl -n dev.${IF%%[0-9]*}.${IF##*[^0-9]}.%desc But, for now (that is, until we do a clean-up for HEAD by removing legacy support), I'd like to retain the mess of "name -> desc" because the above code doesn't work on FreeBSD-4 (which, we obviously wouldn't need to support if we take this into HEAD, though my port would do well to keep the mess, so that persons can expect the port to work on FreeBSD-4). -- Devin _____________ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 22:41:17 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5689106566B; Wed, 4 Jan 2012 22:41:16 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id A611C8FC1D; Wed, 4 Jan 2012 22:41:16 +0000 (UTC) Received: from pps.filterd (ltcfislmsgpa01 [127.0.0.1]) by ltcfislmsgpa01.fnfis.com (8.14.4/8.14.4) with SMTP id q04MaBkm030965; Wed, 4 Jan 2012 16:41:15 -0600 Received: from smtp.fisglobal.com ([10.132.206.16]) by ltcfislmsgpa01.fnfis.com with ESMTP id 124yq2r0g1-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 04 Jan 2012 16:41:15 -0600 Received: from dtwin (10.14.152.15) by smtp.fisglobal.com (10.132.206.16) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 4 Jan 2012 16:41:14 -0600 From: Devin Teske To: "'Warren Block'" , "'Ron McDowell'" References: <4F03AF24.70102@freebsd.org> <4F03BE93.9040708@fuzzwad.org> <4F03C38D.1080909@fuzzwad.org> In-Reply-To: Date: Wed, 4 Jan 2012 14:41:22 -0800 Message-ID: <05fd01cccb31$fcbc80f0$f63582d0$@fisglobal.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQGioPys4U3YFAHSWDxI2KBhfkp2BwIq9j8xAfDLopcCvv0auQFUZietAb3+e1kCMi3iJJXwHL2A Content-Language: en-us X-Originating-IP: [10.14.152.15] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.5.7110, 1.0.211, 0.0.0000 definitions=2012-01-04_08:2012-01-04, 2012-01-04, 1970-01-01 signatures=0 Cc: 'Lawrence Stewart' , devin.teske@fisglobal.com, freebsd-sysinstall@freebsd.org, 'Marcel Moolenaar' Subject: RE: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 22:41:17 -0000 > -----Original Message----- > From: owner-freebsd-sysinstall@freebsd.org [mailto:owner-freebsd- > sysinstall@freebsd.org] On Behalf Of Warren Block > Sent: Tuesday, January 03, 2012 7:40 PM > To: Ron McDowell > Cc: Marcel Moolenaar; freebsd-sysinstall@freebsd.org; Lawrence Stewart > Subject: Re: sysinstall as a post-install tool > > On Tue, 3 Jan 2012, Ron McDowell wrote: > > > Eitan Adler wrote: > >> On Tue, Jan 3, 2012 at 9:50 PM, Ron McDowell wrote: > >> > >>> I [Ron] just added myself to the sysinstall list. > >>> > >> > >> Good > >> > >>> What I envision is a text based system administration suite that > >>> will [hopefully] do everything that the "Configure" option on the > >>> top level of the sysinstall menu does. I see it as being part of > >>> the base OS, such that once one has rebooted from HD after the > >>> install and logged in as root [or > >>> user+su], a menu can be brought up by entering "sysadmin" or such. > >>> user+Does > >>> "sysadmin" work for a name? I kinda like it. > >>> > >> > >> Do you plan on this tool being run "late in the game" after the > >> system has been used for a while or this is a "welcome new user" only tool? > >> > > > > I want it to be both. Similar in concept to scoadmin on SCO, sysadm > > on SVR4, smit on AIX if you're familiar with any of them. > > bsdinstall already does some of these config things in the last menu. > It really ought to be split into two pieces, bsdinstall to do the installing, and > "bsdconfig", to do the configuring. bsdconfig would just be the pieces that are > already there, run by bsdinstall after the installation but also useful separately. > And then bsdconfig could have all the added config functionality that everyone > loves about sysinstall. Dare I say what perhaps others (including myself) are thinking... mv host-setup bsdconfig I'm thinking: a. Take host-setup into the ports tree. b. Shake it out. c. Copy it into the base as "bsdconfig" d. Start sanitizing it (remove support for legacy FreeBSD versions, etc.) e. Start enhancing it gradually over time f. Allow host-setup to remain in the ports tree (will retain support for legacy FreeBSD versions, etc.) g. I will sync-up with bsdconfig from time-to-time as bsdconfig should sync-up with me from time-to-time. -- Devin _____________ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. From owner-freebsd-sysinstall@FreeBSD.ORG Wed Jan 4 22:56:17 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 692311065675; Wed, 4 Jan 2012 22:56:17 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 0B9008FC17; Wed, 4 Jan 2012 22:56:16 +0000 (UTC) Received: from pps.filterd (ltcfislmsgpa05 [127.0.0.1]) by ltcfislmsgpa05.fnfis.com (8.14.4/8.14.4) with SMTP id q04Ml9Vw005740; Wed, 4 Jan 2012 16:56:14 -0600 Received: from smtp.fisglobal.com ([10.132.206.17]) by ltcfislmsgpa05.fnfis.com with ESMTP id 124yv380ym-11 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 04 Jan 2012 16:56:14 -0600 Received: from [192.168.1.109] (10.14.152.28) by smtp.fisglobal.com (10.132.206.17) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 4 Jan 2012 16:55:28 -0600 MIME-Version: 1.0 (Apple Message framework v1084) From: Devin Teske In-Reply-To: <4F03C709.9@fuzzwad.org> Date: Wed, 4 Jan 2012 14:55:27 -0800 Message-ID: References: <4F03AF24.70102@freebsd.org> <4F03BE93.9040708@fuzzwad.org> <964E978A-C016-4A53-A034-8959140CDF68@fisglobal.com> <4F03C709.9@fuzzwad.org> To: Ron McDowell X-Mailer: Apple Mail (2.1084) X-Originating-IP: [10.14.152.28] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.5.7110, 1.0.211, 0.0.0000 definitions=2012-01-04_08:2012-01-04, 2012-01-04, 1970-01-01 signatures=0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Marcel Moolenaar , freebsd-sysinstall@freebsd.org, Lawrence Stewart Subject: Re: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 22:56:17 -0000 On Jan 3, 2012, at 7:27 PM, Ron McDowell wrote: >=20 >=20 > Devin Teske wrote: >>=20 >>=20 >> On Jan 3, 2012, at 6:57 PM, Eitan Adler wrote: >>=20 >>> On Tue, Jan 3, 2012 at 9:50 PM, Ron McDowell wrote: >>>> I [Ron] just added myself to the sysinstall list. >>>=20 >>> Good >>>>=20 >>>> What I envision is a text based system administration suite that will >>>> [hopefully] do everything that the "Configure" option on the top level= of >>>> the sysinstall menu does. I see it as being part of the base OS, such= that >>>> once one has rebooted from HD after the install and logged in as root = [or >>>> user+su], a menu can be brought up by entering "sysadmin" or such. Do= es >>>> "sysadmin" work for a name? I kinda like it. >>>=20 >>> Do you plan on this tool being run "late in the game" after the system >>> has been used for a while or this is a "welcome new user" only tool? >>>=20 >>>> I plan on basically going through the sysinstall post-configuration me= nu: >>>=20 >>> [snip configure menu] >>>=20 >>> Do you plan on making this a C based program or a shell script? >>=20 >> If he plans on making it sh(1) based, then I wonder if he would be inter= ested in starting with host-setup as a very solid and robust substrate. >>=20 >> I was just about to start building the port Makefile and getting host-se= tup to fill this exact need. >>=20 >> We @vicor have been working on this exact thing for years now. >>=20 >> I feel that it would be a *very* simple task to add the remaining [missi= ng] menu items considering how hard it was to simply get this far. >>=20 >> host-setup ... (we can change the name; I'll have to sleep on "sysadmin"= -- leaning more toward perhaps "sysconfig" ... it's the logical name consi= dering we're taking the "Config[uration]" menu from "sys[install]", so the = name ought to perhaps be "sysconfig") ... is a multi-thousand-line shell sc= ript that uses a very full-proof approach to solving the problem. It's unbr= eakable in its current form and has undergone hundreds of hours of testing = (it's current version is 4.0.1). >>=20 >> Oh, and it's BSD Licensed. >>=20 >> Oh, and it's FreeBSD specific (originally works on both Linux and FreeBS= D, but we've stripped the Linux stuff to make it FreeBSD-clean). >>=20 >>=20 >>>=20 >>>> and as close as reasonable, stick to the same task flow. I plan on wr= iting >>>> it against 10-current and look at back-porting to 9 after it's somewhat >>>> stable. >>>=20 >>=20 >> If you use host-setup as a substrate, it works on FreeBSD-4.x up to 10-C= URRENT (tested 4.8, 4.11, 8.1, 9-CURRENT and 10-CURRENT). >>=20 >>=20 >>> I'd like to work with you on this, especially w.r.t to ensuring that >>> it meets the requirements for entering the base system. >>>=20 >>=20 >> I too would like to work with you on this, regardless of language used o= r whether you use host-setup as a substrate or not. >>=20 >> We also maintain a custom version of sysinstall in-house. So we're intim= ately involved with all of the code. >>=20 >>=20 >>>> One new, important, and not-so-difficult task will be: on exiting, che= ck the >>>> sanity of /etc/rc.conf and complain if needed, but allow the user to >>>> override the safety-switch if foot-shooting is really requested. :) = I'm a >>>> firm believer of not disallowing anything. >>=20 >>> Good on both counts. >>=20 >> host-setup actually leverages the power and safety of my sysrc(8) utilit= y (just added to ports tree as sysutils/sysrc). >>=20 >> In fact, sysrc was written as a test-script solely to feed back into hos= t-setup so that we could replace sysinstall's Configure menu. We're just no= t there with all the menu items (but we've got the most important ones -- I= MHO -- and made them rock-stable). >> --=20 >> Devin >>=20 >> Links: >> http://druidbsd.sourceforge.net/ >> http://druidbsd.sourceforge.net/download/host-setup.txt >> http://druidbsd.sourceforge.net/download/sysrc.txt >> _____________ >> The information contained in this message is proprietary and/or confiden= tial. If you are not the intended recipient, please: (i) delete the message= and all copies; (ii) do not disclose, distribute or use the message in any= manner; and (iii) notify the sender immediately. In addition, please be aw= are that any message addressed to our domain is subject to archiving and re= view by persons other than the intended recipient. Thank you. >=20 > Devin, thanks, this looks very intriguing, pulling it down now. And sysc= onfig is a good name, better than sysadmin. After sleeping on it, I'm actually thinking "bsdconfig" is a better name. My reasoning is that "sysinstall" was C-based and "bsdinstall" is sh(1) bas= ed. A "sysconfig" might imply sysinstall-roots, when in reality it's a rewr= ite based on sh(1) and thus my reasoning is that "bsdconfig" would be a bet= ter name. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-sysinstall@FreeBSD.ORG Thu Jan 5 01:28:52 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 96909106566C; Thu, 5 Jan 2012 01:28:52 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 4E74D8FC08; Thu, 5 Jan 2012 01:28:52 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q051SnBI032111; Wed, 4 Jan 2012 18:28:49 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q051Sn3c032108; Wed, 4 Jan 2012 18:28:49 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Wed, 4 Jan 2012 18:28:49 -0700 (MST) From: Warren Block To: Devin Teske In-Reply-To: <05fd01cccb31$fcbc80f0$f63582d0$@fisglobal.com> Message-ID: References: <4F03AF24.70102@freebsd.org> <4F03BE93.9040708@fuzzwad.org> <4F03C38D.1080909@fuzzwad.org> <05fd01cccb31$fcbc80f0$f63582d0$@fisglobal.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Wed, 04 Jan 2012 18:28:49 -0700 (MST) Cc: 'Lawrence Stewart' , freebsd-sysinstall@freebsd.org, 'Marcel Moolenaar' Subject: RE: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2012 01:28:52 -0000 On Wed, 4 Jan 2012, Devin Teske wrote: >> bsdinstall already does some of these config things in the last menu. >> It really ought to be split into two pieces, bsdinstall to do the >> installing, and "bsdconfig", to do the configuring. bsdconfig would >> just be the pieces that are already there, run by bsdinstall after >> the installation but also useful separately. >> >> And then bsdconfig could have all the added config functionality that everyone >> loves about sysinstall. > > Dare I say what perhaps others (including myself) are thinking... > > mv host-setup bsdconfig > > I'm thinking: > > a. Take host-setup into the ports tree. > b. Shake it out. > c. Copy it into the base as "bsdconfig" > d. Start sanitizing it (remove support for legacy FreeBSD versions, etc.) > e. Start enhancing it gradually over time > f. Allow host-setup to remain in the ports tree (will retain support for legacy > FreeBSD versions, etc.) > g. I will sync-up with bsdconfig from time-to-time as bsdconfig should sync-up > with me from time-to-time. Works for me. Obviously there's a concern with duplicating effort already in bsdinstall and pc-sysinstall, and trying to have some semblance of user interface consistency. But one working system config utility is better than none, and two would be an embarrassment of riches.