From owner-freebsd-advocacy Wed Oct 11 19:24: 6 2000 Delivered-To: freebsd-advocacy@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 9B3B437B502 for ; Wed, 11 Oct 2000 19:24:03 -0700 (PDT) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id TAA22690; Wed, 11 Oct 2000 19:22:27 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp03.primenet.com, id smtpdAAA2uaGkS; Wed Oct 11 19:22:15 2000 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id TAA13034; Wed, 11 Oct 2000 19:23:46 -0700 (MST) From: Terry Lambert Message-Id: <200010120223.TAA13034@usr09.primenet.com> Subject: Re: cvs commit: src/etc inetd.conf To: jkh@winston.osd.bsdi.com (Jordan Hubbard) Date: Thu, 12 Oct 2000 02:23:45 +0000 (GMT) Cc: advocacy@freebsd.org In-Reply-To: <15251.971315263@winston.osd.bsdi.com> from "Jordan Hubbard" at Oct 11, 2000 06:47:43 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ ... moved to advocacy ... ] > Custom is for people who don't want anything in their face, they know > exactly what they're doing and exactly what sysinstall is capable of > at any given time. If people are getting that confused by this then > I'll happily remove custom from the set of options and make all of you > go through the Standard installation whether you like it or not. :-) Speaking of doing something like this... What's the chance of including a Windows-based installer, and an Autorun.inf on the CDROM? Think about it: what's less "in your face" to a Windows user, than a Windows installer? I think the following would work... it would add a "Configure..." and an "Install..." to the right-button menu, when used on the FreeBSD CDROM. This assumes a "setup.exe" in the root of the CDROM drive, as well as just the Autorun.inf. It also assumes that the setup.exe has an icon in it, that icon 1 is the FreeBSD setup icon, and that the program can take the command line arguments "/AUTORUN", "/CONFIGURE", and "/INSTALL". You can leave these off, if they are identical. You can also add/remove right-button menu options, as you see fit. To do the disk manipulation, you will need to obtain a level 3, then a level 1 volume lock on the disk you want to manipulate; this should let you partition things. I'd actually suggest getting "Partition Magic" to provide a version for FreeBSD, or to fix file system stacking (same old rant, there) to permit a "test drive" version that boots from an entire FreeBSD system in "C:\FreeBSD\root", or if you don't insist on a seperate "/usr", swap, and so on, just "C:\FreeBSD". The partition magic approach would make it more likely that the user would leave FreeBSD alone, once installed. ------------------------------------------------------------------- [autorun] OPEN=setup.EXE /AUTORUN ICON=setup.EXE,1 shell\configure=&Configure... shell\configure\command=setup.EXE /CONFIGURE shell\install=&Install... shell\install\command=setup.EXE /INSTALL [ProductFeatures] Feature1=UNIXFiles [ProductInformation] ; Make up a product code; set the suffix to your ethernet address ; instead of 112233445566. Note: all digits are hex. ProductCode={00000000-0000-0000-0000-112233445566} DisplayName=FreeBSD 4.1.1 Version=4.1.1 ;Make this be 1 to do autorun even if the product is installed. AutorunIfInstalled=1 [InstallMSI] ;Make this be zero to aways suppress installing Windows installer InstMsi=0 ------------------------------------------------------------------- Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message