From owner-freebsd-questions Wed Dec 6 5:10:19 2000 From owner-freebsd-questions@FreeBSD.ORG Wed Dec 6 05:10:16 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from cisco.com (sword.cisco.com [161.44.208.100]) by hub.freebsd.org (Postfix) with ESMTP id DF91437B400 for ; Wed, 6 Dec 2000 05:10:15 -0800 (PST) Received: from sjt-u10.cisco.com (sjt-u10.cisco.com [161.44.212.77]) by cisco.com (8.8.5-Cisco.1/8.8.8) with ESMTP id IAA16767 for ; Wed, 6 Dec 2000 08:10:14 -0500 (EST) From: Steve Tremblett Received: (sjt@localhost) by sjt-u10.cisco.com (8.8.5-Cisco.1/CISCO.WS.1.2) id IAA27171 for freebsd-questions@freebsd.org; Wed, 6 Dec 2000 08:10:20 -0500 (EST) Message-Id: <200012061310.IAA27171@sjt-u10.cisco.com> Subject: switching boot configs on the fly? To: freebsd-questions@freebsd.org Date: Wed, 6 Dec 2000 08:10:20 -0500 (EST) X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running FreeBSD on a laptop, which leads to 2 separate network configs (work = DHCP, home = 10.0.0.1 & PPPoE). I was thinking about dropping an interactive (ie. prints a question and receives a keyboard response) script into the boot process to switch my rc.conf files before they are parsed. Writing the script isn't the issue, but where exactly would one plug such a script in, and would an interactive script work at that point of the boot process? If such a scenario wouldn't work, how would you suggest one goes about this? I could write a script to do the ifconfigs and make the choice as a user after boot, but either scenario above (DHCP or PPPoE) has to time out and fail when they are not on the proper network. I guess I could write a script to do the ifconfigs to setup after booting AND one to switch the rc.conf before booting it on a different network. Thanks to any and all suggestions -- Steve Tremblett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message