From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 30 18:56:26 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5D9481AA for ; Thu, 30 Jan 2014 18:56:26 +0000 (UTC) Received: from smtp10.hushmail.com (smtp10a.hushmail.com [65.39.178.239]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 317E81A03 for ; Thu, 30 Jan 2014 18:56:25 +0000 (UTC) Received: from smtp10.hushmail.com (smtp10a.hushmail.com [65.39.178.239]) by smtp10.hushmail.com (Postfix) with SMTP id BE448C00F0 for ; Thu, 30 Jan 2014 18:56:18 +0000 (UTC) Received: from smtp.hushmail.com (w5.hushmail.com [65.39.178.80]) by smtp10.hushmail.com (Postfix) with ESMTP; Thu, 30 Jan 2014 18:56:18 +0000 (UTC) Received: by smtp.hushmail.com (Postfix, from userid 99) id 7E44E20152; Thu, 30 Jan 2014 18:56:18 +0000 (UTC) MIME-Version: 1.0 Date: Thu, 30 Jan 2014 10:56:18 -0800 To: "Warren Block" Subject: Re: reviving old FreeBSD4 SCSI beast From: "Dave Ng" In-Reply-To: References: <20140121181241.27FF62035E@smtp.hushmail.com> <52DEC272.3070907@mu.org> <20140128055335.450F720152@smtp.hushmail.com> Message-Id: <20140130185618.7E44E20152@smtp.hushmail.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-hackers@freebsd.org, Alfred Perlstein X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 18:56:26 -0000 While I do not understand why my new (amd64) machine was unable to boot, since no drives were rearranged post-install pre-boot, I was able to get the old (i386) full recovered after adjusting fstab and booting 9.2! Thanks a ton. Sent using Hushmail On January 28, 2014 at 7:44 AM, "Warren Block" wrote:On Mon, 27 Jan 2014, Dave Ng wrote: > On January 21, 2014 at 10:54 AM, "Alfred Perlstein" wrote: >> >> Use a more modern machine to install to the IDE using an external >> USB->IDE bridge, then relocate drive to old machine. > > This is the plan I started moving forward with. Looks mostly good, > except when I go to boot the prepared hard drive it gives me errors > mounting root fs, error 19! This happens with both the new amd64 I am > running the recovery from, and the old i386 that I am trying to > revocer. Any idea what I am doing wrong when I install via the > usbide? When installing, the disk device was seen as da0. /etc/fstab was written with that as the base device: # Device Mountpoint FStype Options Dump Pass# /dev/da0p2 / ufs rw 1 1 /dev/da0p3 none swap sw 0 0 Attached to IDE on the old system, it is not da0 any more. If you installed 9.2 or 10.0, it will be ada0, and the loader will not see da0, giving the error 19. At the prompt, you should be able to enter ufs:/dev/ada0p2 That will start in single user mode (as I recall, it's early). Remount the / filesystem read/write: mount -u / Then use vi or ee to fix fstab, changing the da0 entries to ada0. Finally, reboot. From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 30 19:39:52 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A22F4D5 for ; Thu, 30 Jan 2014 19:39:52 +0000 (UTC) Received: from smtp5.hushmail.com (smtp5a.hushmail.com [65.39.178.235]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 82B191E5F for ; Thu, 30 Jan 2014 19:39:52 +0000 (UTC) Received: from smtp5.hushmail.com (smtp5a.hushmail.com [65.39.178.235]) by smtp5.hushmail.com (Postfix) with SMTP id 1CA7060277 for ; Thu, 30 Jan 2014 19:02:18 +0000 (UTC) Received: from smtp.hushmail.com (w5.hushmail.com [65.39.178.80]) by smtp5.hushmail.com (Postfix) with ESMTP for ; Thu, 30 Jan 2014 19:02:18 +0000 (UTC) Received: by smtp.hushmail.com (Postfix, from userid 99) id EE0E820152; Thu, 30 Jan 2014 19:02:17 +0000 (UTC) MIME-Version: 1.0 Date: Thu, 30 Jan 2014 11:02:17 -0800 To: freebsd-hackers@freebsd.org Subject: dual network for single machine, possible bridge From: "Dave Ng" In-Reply-To: References: <20140121181241.27FF62035E@smtp.hushmail.com> <52DEC272.3070907@mu.org> <20140128055335.450F720152@smtp.hushmail.com> Message-Id: <20140130190217.EE0E820152@smtp.hushmail.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 19:39:52 -0000 I have two networks at home, there are some wifi shenanigans going on but for the point of this conversation I only mention the wired ethernet. Two hub/switch setups, 192.168.1.x and 192.168.2.x, they are separate and they work great and life is good. I am adding a single freebsd host with two NICs in it, one on each network. No complications, right? Set the IP addresses manually and I can participate in each network, using a single gateway off one of them to reach the outside world. I think? Next question, can I use this host to bridge the two networks? Next next, assuming I can bridge, is there any way to do so transparently for other hosts on either network? They are a mix of OSX, windows, blah blah every OS. Thanks! Sent using Hushmail From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 30 19:45:30 2014 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9FB224A3 for ; Thu, 30 Jan 2014 19:45:30 +0000 (UTC) Received: from smtp3.hushmail.com (smtp3a.hushmail.com [65.39.178.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 75CCC1EF6 for ; Thu, 30 Jan 2014 19:45:30 +0000 (UTC) Received: from smtp3.hushmail.com (smtp3a.hushmail.com [65.39.178.201]) by smtp3.hushmail.com (Postfix) with SMTP id A289FE0254 for ; Thu, 30 Jan 2014 19:12:27 +0000 (UTC) Received: from smtp.hushmail.com (w5.hushmail.com [65.39.178.80]) by smtp3.hushmail.com (Postfix) with ESMTP; Thu, 30 Jan 2014 19:12:27 +0000 (UTC) Received: by smtp.hushmail.com (Postfix, from userid 99) id 3BC822035E; Thu, 30 Jan 2014 19:12:27 +0000 (UTC) MIME-Version: 1.0 Date: Thu, 30 Jan 2014 11:12:26 -0800 To: rank1seeker@gmail.com, "Tim Kientzle" Subject: Re: Is this a regex bug? From: "Dave Ng" In-Reply-To: <20140126.213255.017.3@DOMY-PC> References: <20140126.210430.622.1@DOMY-PC> <88CC5471-AD3A-4841-89BB-23D585F77079@kientzle.com> <20140126.213255.017.3@DOMY-PC> Message-Id: <20140130191227.3BC822035E@smtp.hushmail.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: hackers@freebsd.org, Mark Blackman X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 19:45:30 -0000 Lots of tools you can use -- to signify the end of option parsing Sent using Hushmail On January 26, 2014 at 1:33 PM, rank1seeker@gmail.com wrote:> -n is being interpreted as an option to ‘echo’ and being swallowed before it gets to egrep. > > - Mark I've tried without echo printf "-nn" | egrep '^-[[:alnum:]]+$' This works! Thanks for pointing out. > Try without the grep: > > $ echo '-m' > -m > $ echo '-n' > $ echo '-o' > -o > $ man echo > > > > > On Jan 26, 2014, at 1:04 PM, rank1seeker@gmail.com wrote: > > > Or am I crazy? > > > > echo '-m' | egrep '^-[[:alnum:]]+$' > > echo '-n' | egrep '^-[[:alnum:]]+$' > > echo '-o' | egrep '^-[[:alnum:]]+$' > > > > Guess what? > > Only middle one, '-n' doesn't match it. > > Is this an RE bug or I clearly ain't seeing obvious?! > > > > echo '-n' | egrep '^-[0-9A-Za-z]+$' > > Doesn't work either > > > > 9.2-RELEASE-p3 i386 _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 30 20:18:28 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EA4F1BEA for ; Thu, 30 Jan 2014 20:18:28 +0000 (UTC) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A782D118E for ; Thu, 30 Jan 2014 20:18:28 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id s0UKIL9v023294 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 30 Jan 2014 12:18:21 -0800 (PST) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id s0UKILoY023293; Thu, 30 Jan 2014 12:18:21 -0800 (PST) (envelope-from jmg) Date: Thu, 30 Jan 2014 12:18:21 -0800 From: John-Mark Gurney To: Dave Ng Subject: Re: dual network for single machine, possible bridge Message-ID: <20140130201821.GR93141@funkthat.com> Mail-Followup-To: Dave Ng , freebsd-hackers@freebsd.org References: <20140121181241.27FF62035E@smtp.hushmail.com> <52DEC272.3070907@mu.org> <20140128055335.450F720152@smtp.hushmail.com> <20140130190217.EE0E820152@smtp.hushmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140130190217.EE0E820152@smtp.hushmail.com> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Thu, 30 Jan 2014 12:18:21 -0800 (PST) Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 20:18:29 -0000 Dave Ng wrote this message on Thu, Jan 30, 2014 at 11:02 -0800: > I have two networks at home, there are some wifi shenanigans going on > but for the point of this conversation I only mention the wired > ethernet. Two hub/switch setups, 192.168.1.x and 192.168.2.x, they are > separate and they work great and life is good. > I am adding a single freebsd host with two NICs in it, one on each > network. No complications, right? Set the IP addresses manually and I > can participate in each network, using a single gateway off one of > them to reach the outside world. I think? > Next question, can I use this host to bridge the two networks? > Next next, assuming I can bridge, is there any way to do so > transparently for other hosts on either network? They are a mix of > OSX, windows, blah blah every OS. Basicly that means you need to setup up your box to forward packets: https://www.freebsd.org/doc/handbook/network-routing.html#network-dedicated-router Getting the routing working is a little bit more difficult but the handbook has useful instructions: https://www.freebsd.org/doc/handbook/network-routing.html You can use a routing daemon to advertise routes, but not all devices default to listening to routing advertisements and may need to be enabled... FreeBSD includes routed(8) that provides basic functionality... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."