From owner-freebsd-questions@freebsd.org Sun Jul 9 10:01:29 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F1FC1DAEFDC for ; Sun, 9 Jul 2017 10:01:28 +0000 (UTC) (envelope-from srs0=uwpq=6m=mail.sermon-archive.info=doug@sermon-archive.info) Received: from mail.sermon-archive.info (sermon-archive.info [71.177.216.148]) by mx1.freebsd.org (Postfix) with ESMTP id DEB567F468 for ; Sun, 9 Jul 2017 10:01:28 +0000 (UTC) (envelope-from srs0=uwpq=6m=mail.sermon-archive.info=doug@sermon-archive.info) Received: from [10.0.1.251] (mini [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 3x53ff6gHKz2fjvb for ; Sun, 9 Jul 2017 02:57:14 -0700 (PDT) From: Doug Hardie Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Unusual Question Message-Id: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> Date: Sun, 9 Jul 2017 02:57:14 -0700 To: "freebsd-questions@freebsd.org Questions" X-Mailer: Apple Mail (2.3273) X-Virus-Scanned: clamav-milter 0.99.2 at mail X-Virus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jul 2017 10:01:29 -0000 I have a FreeBSD 9.3 remote server that needs to be purged. I know that = rm -rf / will remove all the directory entries, but I need to write over = the drive. I thought that dd if=3D/dev/zero of=3D/dev/ada0 might do the = trick, but it gives an not permitted error. The whole thing can crash = and burn at the end. This is an unmanned site so moving drives is not = viable.= From owner-freebsd-questions@freebsd.org Sun Jul 9 13:25:43 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A04C8DB216B for ; Sun, 9 Jul 2017 13:25:43 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 05FC984496 for ; Sun, 9 Jul 2017 13:25:42 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id v69DEjhX044506; Sun, 9 Jul 2017 23:14:45 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sun, 9 Jul 2017 23:14:45 +1000 (EST) From: Ian Smith To: Doug Hardie cc: freebsd-questions@freebsd.org Subject: Re: Unusual Question In-Reply-To: Message-ID: <20170709230708.M27871@sola.nimnet.asn.au> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jul 2017 13:25:43 -0000 In freebsd-questions Digest, Vol 683, Issue 8, Message: 1 On Sun, 9 Jul 2017 02:57:14 -0700 Doug Hardie wrote: > I have a FreeBSD 9.3 remote server that needs to be purged. I know > that rm -rf / will remove all the directory entries, but I need to > write over the drive. I thought that dd if=/dev/zero of=/dev/ada0 > might do the trick, but it gives an not permitted error. The whole > thing can crash and burn at the end. This is an unmanned site so > moving drives is not viable. # sysctl kern.geom.debugflags=16 purge at will. if=/dev/random for the more paranoid :) cheers, Ian From owner-freebsd-questions@freebsd.org Sun Jul 9 14:39:47 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B7CC3D872AC for ; Sun, 9 Jul 2017 14:39:47 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from NAM04-CO1-obe.outbound.protection.outlook.com (mail-oln040092010085.outbound.protection.outlook.com [40.92.10.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 796F31983 for ; Sun, 9 Jul 2017 14:39:46 +0000 (UTC) (envelope-from carmel_ny@outlook.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=I938mdQ3D99HvZX1DHEPyeML3AgFVx9J8ZD1M6/bq/k=; b=mW1eRjkLR5fOpd5DYI7rRrT8NG9XP/3qF37UpIr0G6GT7Bjez2nF08yArugDvd8p+z+MaMDJbrR54CsWq6FxY0slp0EQvSB1bXg8Jp17lUtFZVA/fffKJuhnhRTLOx0xKibfmzrZ2bmzYz1Pg19hsEDaROa6JDMWb9w5qE0kMMUnAtjpaLpIFjX/fDbND/GSefNNlSQKWkHAHXS64rlfSPguMqW7JiEVucNWl5YybuojpUHyaNLmUHgcybpDHIvRhZDJfnj1lw1Zra/LrW0CgpUxik+Kbp3lH4JWPmuCIQ1JnxEd799Vz5LBf9AwEG1EvnYga9CZDyBO6U0nJ5QUJA== Received: from CO1NAM04FT044.eop-NAM04.prod.protection.outlook.com (10.152.90.57) by CO1NAM04HT127.eop-NAM04.prod.protection.outlook.com (10.152.90.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1220.9; Sun, 9 Jul 2017 14:39:45 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com (10.152.90.59) by CO1NAM04FT044.mail.protection.outlook.com (10.152.91.95) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1220.9 via Frontend Transport; Sun, 9 Jul 2017 14:39:44 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com ([10.172.31.146]) by BN6PR2001MB1730.namprd20.prod.outlook.com ([10.172.31.146]) with mapi id 15.01.1240.020; Sun, 9 Jul 2017 14:39:44 +0000 From: Carmel NY To: FreeBSD Subject: Interpreting NTP status Thread-Topic: Interpreting NTP status Thread-Index: AQHS+ME08rgrh5at9Ump5LdMaoEGXA== Date: Sun, 9 Jul 2017 14:39:44 +0000 Message-ID: Reply-To: FreeBSD Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: freebsd.org; dkim=none (message not signed) header.d=none;freebsd.org; dmarc=none action=none header.from=outlook.com; x-incomingtopheadermarker: OriginalChecksum:1A754193DFF3E47352F58AAE0BE4D7F3B99DAD72F21944F6933812B3759ECFF8; UpperCasedChecksum:45F769F83CAA1D0AF8BA24C59B93AC25559C5731417850FC7BE1CA20A85B608A; SizeAsReceived:7067; Count:44 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [18MZR0wGceKBGbk9zcOZgC90BQt3kzsL] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; CO1NAM04HT127; 7:DslUyc+USeuzxTyhBQuIkP6fCNl63v6K6rC8rLnV72u9cT+aVYPimhSJvYSGEbBSPFTRoSrm83JXkH2ttkn/ttUDo+okPI8tLrJolGy1egBA58ryliKlE3UMIDU9Vur2VraWBgHgjEsxK+f++u2ln62StwURgnMGqQ5yAYo9GfSce4L934u8ZpxKZA5ZyPJVAA8yaualG4IEymyykbmHy0/yAEtdV/kdcDB2NJz35oWx1ld8zaIk9G5/SxBKUBocteUqkZZ7EEaiTMtWxhAsJFyotig5U/G1L5+tfgWKXy7EQr6RLKnjufByP3AuA2lcXlrVy+72yg6QS/+kAfVTBrdziCurMkrdXGockkL4hcNnQ63xMQc5CdHfJX7Onb4rGSmZKQK1UvxRiC4C1G3kwuwmkoHIwtfZSFhbZBAxNX0AmdYY7Ce8Ipu4u1XjAS441OOhreCmmda/6CFnGQp8/A1g11w6RmfUu2kDDe3vmSRQdjvRdik4GEKEaDDpf9+/M8tZRxk4+OfEM7hUTC/d3VaiHT+XNOT6cCry6hjir62twjvS4uKJ8LViKK8NE48EEegxNccnO2MF5Q0+s8dzBH15s3GxWXeMHUz426kzusv4m4W7fFUAk0dGrQ7J7UDPiTFwhM0mWXWgwIL4JRFx38PmqIhllxLEo/yoDQSMI4UKBh1bhR2i3SOprWvldAqVPOMA72lkXEcLnkEewLETdqrbegMIq842pX0KMbDujhOBkDJOuvffeAXyf0J/QUGJcbryrntJsphTn0GDFPNsiQ== x-incomingheadercount: 44 x-eopattributedmessage: 0 x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:CO1NAM04HT127; H:BN6PR2001MB1730.namprd20.prod.outlook.com; FPR:; SPF:None; LANG:en; x-ms-office365-filtering-correlation-id: bb6e31ee-1995-417b-30a6-08d4c6d85665 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(300000503095)(300135400095)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:CO1NAM04HT127; x-ms-traffictypediagnostic: CO1NAM04HT127: x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031); SRVR:CO1NAM04HT127; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:CO1NAM04HT127; x-forefront-prvs: 03630A6A4A spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="utf-8" Content-ID: Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jul 2017 14:39:44.1399 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1NAM04HT127 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jul 2017 14:39:47 -0000 QSB3aGlsZSBiYWNrLCBJIHdhcyByZWNlaXZpbmcgYW4gZXJyb3IgbWVzc2FnZSBhYm91dCBhbiBv dXRkYXRlZCDigJxsZWFwDQpzZWNvbmTigJ0gZmlsZS4gSSBHb29nbGVkIGFyb3VuZCBhbmQgZm91 bmQgYW4gYXJ0aWNsZSB0aGF0IHNhaWQgdG8gcHV0DQp0aGUgZm9sbG93aW5nIGluIHRoZSDigJxy Yy5jb25m4oCdIGZpbGUgdG8gY29ycmVjdCB0aGUgcHJvYmxlbToNCg0KIyBOVFBEDQpudHBkX2Vu YWJsZT0iWUVTIg0KbnRwZF9zeW5jX29uX3N0YXJ0PSJZRVMiDQpudHBfbGVhcGZpbGVfZmV0Y2hf dmVyYm9zZT0iWUVTIg0KbnRwX2xlYXBmaWxlX3NvdXJjZXM9ZnRwOi8vdHljaG8udXNuby5uYXZ5 Lm1pbC9wdWIvbnRwL2xlYXAtc2Vjb25kcy5saXN0DQoNClRoZW4sIEkgZm91bmQgYW5vdGhlciBh cnRpY2xlIHRoYXQgc2FpZCB0byBwdXQgdGhpcyBpbiB0aGUNCuKAnC9ldGMvcGVyaW9kaWMuY29u ZuKAnSBmaWxlIGdldCBpbmZvcm1hdGlvbiBvbiB0aGUgTlRQRCBwcm9ncmFtOg0KDQojIDQ4MC5s ZWFwZmlsZS1udHBkDQpkYWlseV9udHBkX2xlYXBmaWxlX2VuYWJsZT0iWUVTIiAgICAgICAgIyBG ZXRjaCBOVFAgbGVhcGZpbGUNCmRhaWx5X250cGRfYXZvaWRfY29uZ2VzdGlvbj0iWUVTIiAgICAg ICAjIEF2b2lkIGNvbmdlc3RpbmcgbGVhcGZpbGUgc291cmNlcw0KDQojIDQ4MC5zdGF0dXMtbnRw ZA0KZGFpbHlfc3RhdHVzX250cGRfZW5hYmxlPSJZRVMiICAgICAgICAgICMgQ2hlY2sgTlRQIHN0 YXR1cw0KDQpOb3csIGluIHRoZSDigJxkYWlseSBydW4gb3V0cHV04oCdIGVtYWlsLCBJIGZpbmQg dGhpczoNCg0KTlRQIHN0YXR1czoNCiAgICAgcmVtb3RlICAgICAgICAgICByZWZpZCAgICAgIHN0 IHQgd2hlbiBwb2xsIHJlYWNoICAgZGVsYXkgICBvZmZzZXQgIGppdHRlcg0KPT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09DQorMTk4LjU1LjExMS41MCAgIDEzMy4xNTcuMjkuMzUgICAgMyB1ICA3NjAgMTAy NCAgMzc3ICAgODcuOTEzICAgIDUuNzkzICAxOC40MTgNCioxOTIuMTU1LjkwLjEzICAgMTQyLjY2 LjEwMS4xMyAgICAyIHUgIDI2NCAxMDI0ICAzNzcgICA0NS40NDkgICAtMi4yMzUgICAyLjkyNQ0K IDI2MDc6ZmExODo6MjQwNyAuU1RFUC4gICAgICAgICAgMTYgdSAgICAtIDEwMjQgICAgMCAgICAw LjAwMCAgICAwLjAwMCAgIDAuMDAwDQoNCkkgYW0gaG9waW5nIHNvbWVvbmUgY2FuIHRlbGwgbWUg ZXhhY3RseSB3aGF0IHRoaXMgbWVhbnMuIEkgY2Fubm90IGZpbmQNCmFueSBkb2N1bWVudGF0aW9u IG9uIGhvdyB0byBpbnRlcnByZXQgdGhpcy4NCg0KLS0gDQpDYXJtZWwNCg== From owner-freebsd-questions@freebsd.org Sun Jul 9 15:41:19 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DA9E0D8D4D5 for ; Sun, 9 Jul 2017 15:41:19 +0000 (UTC) (envelope-from steve@sliderule.demon.co.uk) Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0050.outbound.protection.outlook.com [104.47.1.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1AFA235E8 for ; Sun, 9 Jul 2017 15:41:17 +0000 (UTC) (envelope-from steve@sliderule.demon.co.uk) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=slideruledemononcasc.onmicrosoft.com; s=selector1-sliderule-demon-co-uk; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=MmyDHe1zx05vibj4hHj2lkceSMWaUwgBnVRNh61cO08=; b=mqUI7END1SYFydQRHQSbzieiwkQ5u9IwVXYIen4HDjp9islXF6DYoI4cscQGt7WapHmblKHuOaPOhFnGo+TSp//MggUvNgwF5I78PhJ+x5xewwuPM4O56aGmkB9QeNRek5YOHvzXYJ6Qurcu83vhsxKnreHzjL+bLbx98VGBWAo= Authentication-Results: freebsd.org; dkim=none (message not signed) header.d=none;freebsd.org; dmarc=none action=none header.from=sliderule.demon.co.uk; Received: from [192.168.254.7] (80.177.21.188) by MM1P123MB1324.GBRP123.PROD.OUTLOOK.COM (10.166.219.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1240.13; Sun, 9 Jul 2017 15:41:14 +0000 Subject: Re: Interpreting NTP status To: References: From: Steve Burton Message-ID: <18f14980-4918-5715-4a07-b2a7d9d61602@sliderule.demon.co.uk> Date: Sun, 9 Jul 2017 16:41:12 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Language: en-GB X-Originating-IP: [80.177.21.188] X-ClientProxiedBy: DB6P193CA0003.EURP193.PROD.OUTLOOK.COM (10.175.237.13) To MM1P123MB1324.GBRP123.PROD.OUTLOOK.COM (10.166.219.146) X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: 490b879b-f0bb-4e8a-bf59-08d4c6e0ef0b X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(300000503095)(300135400095)(201703131423075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:MM1P123MB1324; X-Microsoft-Exchange-Diagnostics: 1; MM1P123MB1324; 3:sjGvnDW8ETN147uz5O4L23iOIRyaDxMi5Us1fHK7putetnS84mHUYDiAKXkK8Rp2uIQRxZy2tkp/qBi6U5XejI+CYOAlRTTbtQ2BWFtehUc7p0Khfww1Nmy0UieMJC9c3tpwhRXCNnLWaYlOqzzzLotflFJXKyv3ThwH08z/ZqJgd8EUq5q2sh0IgPvjx/CnbGWKkk2q0mRBCyrmVXwXXu+s7jR/IOwTLIaWWiE72jEv9vSwlPNVVCCwGRslN0b0nmPGuaQdidVay+ZZsL710EJZtJYT/4vifvumymWDnojXSzCUpSieSPL34Hp+yN7ptFUC/AIXLAo+VKQ8L/EboaWYRByMgeebdUxTTt9r+Uv8m//m5bupRiLFMnfZ9i7S0o13QnkeNB580CWesmbUbXfzDayOyxOA7qlxoSRoboJfT3354jzcVYXkmTAdQrVatQX7ua5YhD+4NuPpnZwb2VwnFdAocEyDFoWfTuNxLUOq3xboiDfEPQSt7I8AgM/rYTHimBtcBVPzzfguOEA9b/f4eUIkXqik+SH6f95y+yxlI5OsyvQ6lvq+BYmA31DJUN+4r081T1/2WFQApEduJ8CrXkK0rkBFga9kWJO4kHL2VmFvSUxeG6qwNxJVDOE0O0x4KwwaJnOh8PD1He8m/ZSuQOXG1mVS38i2KNbcKVpPIuuQPvpRHNrMpcBsYnFgAHYSvbZ9/P4mcpbQW6girA== X-MS-TrafficTypeDiagnostic: MM1P123MB1324: X-Microsoft-Exchange-Diagnostics: 1; MM1P123MB1324; 25:4hxKNSPVI4UkWydPwvvEpQgtdqNSCJgE3XolFG4cX1KX0+R1Y61bhtYzRNd45Qk06fOYIncYyvtKXhHHYXmCitq+B+TUG0OVL6HaVhf5MEPzZzgXIjq8Rj6AzKJX5ebmcfKdNs/SAJO4xSuq3Sv7feoUZDfhx5neWLlmwHm88VjVA17ABpA8PV/iuAt74EJAz58N23AN7CvwN0oHlcKRiIDDw/9zDSY2pCej36NXEiLmroi04QWPIdbAc/H8IfKFos4aePvhA7+6IiFuQLxBw389Frqz6Rrp2hIuTpMx1GNKBSqPGxyIUMOqiLWx6nUqi6eRTYP+DLW/22QnMi844bOcbjo0gP2rS9ljlpm14ZBqag9v9UYOcwKYIZnLdMTxK0grbqIHbDaaHPDhy67y8tePFnZnnsFcsiRVXZJjS4PXyubyjr774piT59Qw2CwDkNq5xg73r0hOcHTN/8InTcvcnTPR29MrB+uuXLYik2rPbN1h+AYKUBdDIwwjGdwNA7xXVNH6x8DNoRVwMl3mG+Pg50YAw7KvHWJCg2R7BjVaS5lptrVo54QX6V/9KKBHnHfMmstocCTeea7RsYm0NrFzN+WYmicg+3vyRdnaKljxBv+STkrr1uOJaCQL/lCk+uFYmDmVaifNDk/Oec9/rKkWf72q+zs/o6AC8vDFUhsUWUXfFGyiEnE1gInGonoMCqIgbNzajYyEhOKUNcKUtaoS8RJfUy/zqM7n4kaRoGuc8ElTtdQ84rSyTlIL40Sij8jQtaz3jBuFJ7azqgtXbhCtcEbuxtfH9Tn/1wfxTHqlEVO3QerRnRb7IF9gv3TTSHyBS8elF9EGKbwsdc91Kf7DZB9NrDwgEo5D0EISh8YEMozl2SUK3NORs7dxj3RxSdT7RfVoErZy1eA+u8mCTBpuIEODklYrrtaBG7PLNls= X-Microsoft-Exchange-Diagnostics: 1; MM1P123MB1324; 31:MZ/Bv1ymKnThVwHcaB5V/hWqTW3hT8SgS/gyLlZqice4Xvwu83REwWMFX43zWZAy9L/QM9U7mMZukN+hdApWKkW8weTpa2zBhWI/+yvOviIaaMeYtLP4vSz1rdgHU9i+c8hMr/Sf9r8ZLfCjSXx5CYakiWdju7bxbsHBVdSLh8NXg9H+Zfmwq+5R/fNHCROjh4LJ7WCoRYmYjNQndT9mObyoLmSpCpD9Xh2OuBwS2JwjJ7t4BaHNBJjjl6Em+nEYwUR0HkYltQ2aZissCJ7hD9qtEsHQtaetxqAPBpbUDfIXrHsWCA45nW86dAyHkbnR3X0ZSOHwOoy3H7cu4y5VgfORv+rJy7Ppf96/PbvnKgpkjKZAd7VZOnZcehxoiqC7rErYibCLKB7Xj4YOfDXwn6NKgaLPX21DAkCFqRssO7kpFz5r2nR0/SLDghiW+A9kqC8dW0TMy+tLVfow+uohWQvkQGRn3VIQj60EdkKR2x16dvTh0bxUHRo21/vAFH1JWNS7tcnd71UJ4h1J4hJSsM/GJLZ8RxniDs/4LF/8FX7+5u+hHXopyx1DgzTfXywxdpm563LB0jLmpvyyHREWAbQSuoSx+y+EvVSoZFIHlOFOUhF6GkBFhdYOfgDSzOMRJlqr7fDlC4zXFJEQukqC4bJQStoNXg8BcbhYDSEGMARZlG4a+JpQSPA0rWPg1FyGrI3iGTlkrsT+bLJ5VsMVEA== X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:(236129657087228)(189930954265078)(4659246709749); X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(2017060910075)(5005006)(8121501046)(100000703101)(100105400095)(3002001)(10201501046)(93006095)(93001095)(6041248)(20161123564025)(20161123558100)(20161123562025)(20161123555025)(20161123560025)(201703131423075)(201703061421075)(2016111802025)(6043046)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:MM1P123MB1324; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:MM1P123MB1324; X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; MM1P123MB1324; 4:+Iz/KwZCwTT1XqGaqxE9p32PiijQgvNCaMvJBrLHIM?= =?us-ascii?Q?d4wBLnw4tmSOIv5DRYuS1Xig0i8b08rjOtZ2Sn4TbnmRSGL9AnbEYm3jhRpE?= =?us-ascii?Q?yM8JtmE7r12jCCPDU5VStYLQzjEXUqxXPYXwL2v7xf+wH84FIXbSH2SYd2Sv?= =?us-ascii?Q?F7ExajSAC9TcHTaA9dbL4YnQXRBGCGIoPhppXAnCyiRTZW7sNzvx41EDKCui?= =?us-ascii?Q?XmmE1A9JMPFfFtcOIlnwGtD7/0/nqWBdN5Kbx9TBBq5J0tZIOx+fGTLruIx/?= =?us-ascii?Q?jFNMcOIymLBNzoQ5n4gvA5zsRcl5JlQ0qmikXzRvKNLRxw35Xof/dadpLbw6?= =?us-ascii?Q?JGlphmk+ymKebBkWfkWrJ6qp0TubhU7n9XQU+jX6m5MRGkIT4MWGGw0A1aoZ?= =?us-ascii?Q?YMTLXpnVTSMm0tvKoh2K1I3DKVWxGaFzPaVhIpdW5kPjc7EMQNWzh/JFTJUX?= =?us-ascii?Q?IhZ8bsTlc/lP+uajjGWRwbNfPb31qKlOzYfK9h56+eXmOQXMH28PefyjehAv?= =?us-ascii?Q?vgLcT0k7vCDPjmUuQfgP9xW7DjoJRK76DIw+0Ok8cTVtipwabd/wAbeDT1RC?= =?us-ascii?Q?gY3TGIrk73C0gh761y7n2py+klop5jUB56HWE31235fQIctTp4UsARlNsEte?= =?us-ascii?Q?IMGztXp2pBoqwEc1JJM59ZDgrPEI9tg0nZynREytAiN0wcHy3/CsQdSVU6FJ?= =?us-ascii?Q?OOm6X5NKub+b6eMBNqAj3t9/hQSQWm0rXYEEP3Ne5v7LOvbe+S9udUfCaEDM?= =?us-ascii?Q?EmXhDX4GUw0a11bDFh0e6KoClULXWyQrKk6WlEEOhEnqp3tkEDkzQHLH2jpX?= =?us-ascii?Q?T5KnOJZqF/aECO9cCtNWeN4iO0ywKw0kLu2HuApZcVtrOiy1cHhJ9b0uHtD8?= =?us-ascii?Q?33cwMPnfhvtZeI7VE+sqTjID2QbLR427rSMBdD9PI/Qisii3tYaF0elLwnvg?= =?us-ascii?Q?i/dYC2yHymXVpT7LHdg12L5DyG/C4IjdGpufkpQWN33sh5PX328Vl5AeI3eQ?= =?us-ascii?Q?bd2JHJy5/ut1PxW7ga1ID2rpLbMBpf6tT2S7tckgmXX/JKZA9ldgoPc7fO6n?= =?us-ascii?Q?E7J1D5ssPz9oKeXQGnewraZBIviFmlIfdxnvdzONgBo0JiAlhRr0D0ipzMSD?= =?us-ascii?Q?vFsZsktLDmYsNcnsXci+tetd2Tzp3/M8NPuB2ed+cvqY1V8xWpjYVyMh81/M?= =?us-ascii?Q?GgPgi2+R1sFUVzXZvkn4aAUgHoNp4/aLDpc9EeWBl5gbfOC4yVb7BYzsToQK?= =?us-ascii?Q?8mGkxgc27qJU74Jms=3D?= X-Forefront-PRVS: 03630A6A4A X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(7370300001)(4630300001)(6049001)(39450400003)(39400400002)(24454002)(66066001)(6916009)(65806001)(4001350100001)(84326002)(25786009)(83506001)(54896002)(7736002)(31696002)(117156002)(2950100002)(42882006)(74482002)(229853002)(77096006)(6486002)(7350300001)(86362001)(2906002)(64126003)(33646002)(42186005)(53546010)(31686004)(3480700004)(110136004)(189998001)(6246003)(8676002)(53936002)(38730400002)(65826007)(81166006)(3846002)(5660300001)(2351001)(236005)(6116002)(7116003)(508600001)(76176999)(54356999)(50986999); DIR:OUT; SFP:1101; SCL:1; SRVR:MM1P123MB1324; H:[192.168.254.7]; FPR:; SPF:None; MLV:sfv; LANG:en; X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; MM1P123MB1324; 23:JgZ0uduKhBFcbi0PHKcR1hZ/9tpJPN4XeiriK9oqs?= =?us-ascii?Q?murW+zsqK3nG8aB4+YqEdl1eXynDOVdgGkN6ucmNsYA87xHuIsBtpEGMZV+9?= =?us-ascii?Q?ShlgitjgDIjsjMKDnt81+Yi2dQQmAg29IhIP0lughm9fzwzEjlSWV2qavGzK?= =?us-ascii?Q?rLiQeL2cRA43qJ+aWx3Fu3K5vBlzf0PphhYhm294Vy1QI3IiFfrKDiGcIrJX?= =?us-ascii?Q?N109no/aii492kppUJ7TB4C2kiwJQWV3qkzjEJdrXUXWKNj5nhvaOv5pJpNq?= =?us-ascii?Q?sgI02qCcTnI420ksB1FP74XnrAAimy1Vd4OW+ojVLT+cnUjZUj4xYyJGXxYE?= =?us-ascii?Q?GDnncBZjGnntyq9ZKSv41Vdtg27s10Oa9ohXZYqnU3lI8S5VC/t/0NPPGmEG?= =?us-ascii?Q?4303uMnyO/cadmr5BJdXi+MC8oHbMMYDOV5sFx2YMLJf0FEWtQyK8H541Br1?= =?us-ascii?Q?q+T8mSy6FZgBXc6Ssw8pirzfMkSWYZxQ0tqj7Iw7y9+FIlhJtT/jsoQ1Yi50?= =?us-ascii?Q?0uwPdlW0E2A/p5wNIwGsvhIucTS71Lp/SLb6MTKDERCXecrlJlJzzd5U4NYr?= =?us-ascii?Q?0mvy36koaKT82ThA/zFDnlgQyoTbqn40hw7O+x21+Fz0nu0TP9L9B1+0Wcm4?= =?us-ascii?Q?ORAHpEfQmCGnnhDMX5nYnaUgjdjV2Ln3+S96YAumYZuS7IjM7TX294aVSAiK?= =?us-ascii?Q?7dgN2D3H38AxsaBVmHOb2GEJE1EX/fn240CrB4YcloM01Aroq0EDrHmdcQZs?= =?us-ascii?Q?3PrW8Pr8N0LJi/7QHAvtg2Ja6SvvIbcAzzpCGSEaHciG0+JBKo1pv438tfeG?= =?us-ascii?Q?oyPQFCmYEEnDzx6r0PDewe4oOAM61qo7kIfbmnmWcIO8rDkZ/uQDliAowAKk?= =?us-ascii?Q?Phv+58+eRP7aAzd7ux60Ifvdd6ZtqyDMoaYNWZzvPGK6JgaR21HgmUiF5vhI?= =?us-ascii?Q?+djuVr/SsP5yDMJFx1TJ9YqgfmJE+xgxVQCdI/l55PZMZoFIdSAmKzTU31v2?= =?us-ascii?Q?V1fI84ptED2Vte7JxxJOMSu2FShgCliyRVlfYiGqLheghVUDGtU0pRFZaJ8z?= =?us-ascii?Q?NOi31kpkq5xxp9ZgzY5H7LHXPHg6/EoCeYq8UAW8//A+AsdN75a80r8iQtAG?= =?us-ascii?Q?KCHgxrCOiwVRMJbdhHKMWJII+uxHkpF2ySv05NaLdogpTEbQXnNyZhkxzpYU?= =?us-ascii?Q?GzhO40jQlr50+RlOtJh01J5Gn0ZjKc0hiCVQxcIfpg3YpDt8drJ8gE2Ig=3D?= =?us-ascii?Q?=3D?= X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; MM1P123MB1324; 6:wtn2A9tywmdbbW2iZIFrS6gdxypyR90HchVCyF1QyK?= =?us-ascii?Q?dk9p/5F1fxNPlLSr2F3yDdxz3hoxXCM81VZpDDZrCNzWV13XAOF2CLOeXztA?= =?us-ascii?Q?nVq6yA5ZwDNJCAwnWeDUmdQbqsBlkWNd47OQJUpq1jHKpzs/Dx0mdWj7Kd+2?= =?us-ascii?Q?GYMfNdGKQda5PHjIZMLvt4+wAPAvggqepZp/zLfEupy8vrtNK4275MzlD7S4?= =?us-ascii?Q?gYv69xiVSaebPpcrs29b+nhL7TrgQJOUwRaubLCQK5/kFaLr95GxXrPyC9JL?= =?us-ascii?Q?oUX6SO1XLff6BU9EYEtfd0twx9bJSmOCl2LnRABC6Pfcw5M/AUeBApA7es1t?= =?us-ascii?Q?QbQgHvuFwSfGfaHGVcbBSp4qyo50eouE76O8qAJKYi/n2w8SaAbKZhj6ihHD?= =?us-ascii?Q?AC1p6vUB7mJ7JGXbcCDl7YjW6EjzzyFTkc0E2Gx/EA0pyrAQiNypmr6DfvLs?= =?us-ascii?Q?jldeKgpaEwvAxOpN+kU2w/cEJuHdmza2KX1HGtdLtd+xotlIbDDUVERACJvZ?= =?us-ascii?Q?7O9gOs3MebzSjbPNJnb5uh0tjQfuhv8wvyFFdKyrK7VH9jnrh8aWgGzA8KbI?= =?us-ascii?Q?KPqW97qzI+h1cjqg+Yr4sne/YubaBTK3Nj9WNnDSvck7lB7ig/AUG3IZkyJU?= =?us-ascii?Q?a/7y1+sithLTabcgyyPpclYz7/xZZyeei2id7510dqOAzTbEPPPDiXluCJpA?= =?us-ascii?Q?FK/c8CuH7SZZeaRPHjT8Z7Ui1JzA569IUGV/oiTBigJvQdeOQQbyyt29y8cd?= =?us-ascii?Q?gwoXZM6qx0bjCb+keY6+xD3wtIT0yYzBnua6TOEWnoPJfqng9xweEwanzG5P?= =?us-ascii?Q?wBIv9yjZgdqK1gJLTGPoMnkhK5x2kyPRC2N+oULH2EhfqsjyXGX5YIC1EMNh?= =?us-ascii?Q?ykuGFUebUc2rAGvBX78oQl7bOn9lUKteqlRPV/VPSFOoBoGct/cWwOmllNhL?= =?us-ascii?Q?VVt4+9T+2y0T0Gr/9sa8JEGKez3jTeOroMgWC7JMDlnQchZ5lKesToQ5LRKQ?= =?us-ascii?Q?o=3D?= X-Microsoft-Exchange-Diagnostics: 1; MM1P123MB1324; 5:nDxQ9iCHgK3yx4MgT3vEoP2A5CdkfCTwaTsErnvJAvK8aHOdKF1dj9UHj0giuXD5TcY3Eq460FZFcCQ+VBGVD0YnkdeIVr9WlhgO4yjJu11SLAb8oPU832s0rWxMF9ZMpt8d65uZR4DSq8YiTFUk1c6DiPZFO3kfKO1+XC0qMV2cmiMYab7jtRauV95fkU9SuQf4qYt4pzDD6tMStX49fpRgeY9mQNUwk1ptaLanRIQPb3ZIXXIDAzn09Xu3CvcBFzK9WgiugkyfHHkfB3qJFFrXFSO/wJoYa5GZvfiAWZZ4zR2S9cz5g5sJikT8PqJPIvDJurCdMJxqByt4f91lcZVwZ2cBRP7gjbV6BIa6qtYufB4c5tErHw0/0ai+39xSa/kLueH1sK24n7f4xjEDwE2N6gfte/IVHNFAZnisJq/cS+FURoccdpOR36EyF3IbfemgbvZCPZmv7Gu2fRXnw0NTWU19NIHbmmpMW43uylYSSOdHw18B/G+TtCYMHyNW; 24:dbWQ+ibwRFjLKU7vNwm3jvAT91WaNjCrgx/o7uSlvuW++4EQ2TlfKTDCDuQwmqC9pmxP3JQdLd81f0gn6vj79PLTdDfMNqpRBy4F7RzdDYc= SpamDiagnosticOutput: 1:99 SpamDiagnosticMetadata: NSPM X-Microsoft-Exchange-Diagnostics: 1; MM1P123MB1324; 7:mF8RZTkBJqNbzkuDaYv3Gy+7ZcuhXidysavOBDDRUcsSgPvhVERVv5rdCACrOHjiP0nviEIkcygFYY4uxn6JePllhVpJxjrvpKdBewVSqP5F4VWCA9DLLnBk2/+FLOaiExhmJJAXvegcuB1LZ6baWKftxXZsdLvTMxrOSIgPxNQdUe7WT8BT6WQGDlAmHYRLvgLMUP2PGHc6+VyQ4RSYzFrNNlFonh4PjTca3D50BBfpRj3FhvDXunrX1djK0JGZgAfN6w//sOHI2xkPO/Lp1yTrBWjPFC/VgKym3QnthzSbfzqm9K17ZcAoNc1EEIOgLMvmpuOgp9KA0bOXmHU/1ZIwImDvoAVgJ7spN0StzIOrQrqJLIgKkRMCVIvlEZPbabdN35mMmMpFPCPHlvI0n2Th3sNJDrBr6rgfh1S4/9nYn62PwAHUgrTdW/94Hy4fFBi0lbAxtH5vxM5B2mfr2fqpUIZOGrLsXDrl/5nvnT4EU7QA2aygjPC8dOfCcgK0oTDJOHEIIIvCI8MIORhvE4nPNQZfnPbHpumSkxzQACMOB4YlWaJNj5Zj4W0y1GEbYrACPEDGWVpqVIZLcld0lv747sPcKFDjEX6fmUn4lnTYlkpZJzLbLxOLDKJd8ldyEU4NFiWeMu2NtOqHoCfynKcmng0aNRvmAiotRd1UGvitJvwjfDblMdZXMjdvSAcY9q+oHm6NV84cxJL8STOhGCJ/453yiQoYWi8XTNRvMQuqpVvff2mbneN0K8/VfUml2gTb46PYl9FjkfDMU3uKviv3gXFnCKtMIjk0SupyyQA= X-OriginatorOrg: sliderule.demon.co.uk X-MS-Exchange-CrossTenant-OriginalArrivalTime: 09 Jul 2017 15:41:14.8924 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-Transport-CrossTenantHeadersStamped: MM1P123MB1324 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jul 2017 15:41:19 -0000 On 09/07/2017 15:39, Carmel NY wrote: > A while back, I was receiving an error message about an outdated “leap > second” file. I Googled around and found an article that said to put > the following in the “rc.conf” file to correct the problem: > > # NTPD > ntpd_enable="YES" > ntpd_sync_on_start="YES" > ntp_leapfile_fetch_verbose="YES" > ntp_leapfile_sources=ftp://tycho.usno.navy.mil/pub/ntp/leap-seconds.list > > Then, I found another article that said to put this in the > “/etc/periodic.conf” file get information on the NTPD program: > > # 480.leapfile-ntpd > daily_ntpd_leapfile_enable="YES" # Fetch NTP leapfile > daily_ntpd_avoid_congestion="YES" # Avoid congesting leapfile sources > > # 480.status-ntpd > daily_status_ntpd_enable="YES" # Check NTP status > > Now, in the “daily run output” email, I find this: > > NTP status: > remote refid st t when poll reach delay offset jitter > ============================================================================== > +198.55.111.50 133.157.29.35 3 u 760 1024 377 87.913 5.793 18.418 > *192.155.90.13 142.66.101.13 2 u 264 1024 377 45.449 -2.235 2.925 > 2607:fa18::2407 .STEP. 16 u - 1024 0 0.000 0.000 0.000 > > I am hoping someone can tell me exactly what this means. I cannot find > any documentation on how to interpret this. > Check man ntpq(8) Steve. From owner-freebsd-questions@freebsd.org Sun Jul 9 18:11:11 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 35AFED92196 for ; Sun, 9 Jul 2017 18:11:11 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BAB4767827 for ; Sun, 9 Jul 2017 18:11:10 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wr0-x232.google.com with SMTP id k67so109916194wrc.2 for ; Sun, 09 Jul 2017 11:11:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-transfer-encoding; bh=cXeKN20322bJbSo9s3LCR+gHwsfsvzFXzIBMF4+Lcg4=; b=aypTOKH9VNvIouP2Uj5NLRYmGhNJfpdqLNGf4gJucj6lFMgb4Toz8f1unNdFhug4j3 DGpKN1tQEp6ThqdgUF5Rf/l80kHzzXyjF0xPzdLzLdrnhnzClEwBJOsNxO1ckG6hd17W aKVtuw0uAznhhYOpOqpyrOB0BWplpRf/kFrUyPcwp0ULWvUAOKI2xVo7XcH7Q/tPJiYd Cyw8BGto2SKVCXJtX5JewYm7+L9J8adaxh3kvP+DvwCwY2j/G1ejqUh0BEXevBib4jIN LU5Ze+aZk8hVRNjYpvq37TZ179Vcleq+Xe38GJQw7PqZvX7ZoKlB/RyPjv1OWNI7nIiz 6GgQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=cXeKN20322bJbSo9s3LCR+gHwsfsvzFXzIBMF4+Lcg4=; b=ipl9cVlSnC+hEWJvv7eSjZLI5YtXYHzdEKVD1NdWg37BJGLMdpM8yQokSqIJfN8PJv VtY8V3qbFHV9XOePKZFJvpj5LamIAqKSrF7QqWHtpnd8om3lF10ZguH1QwgHUOMMcT9+ zc2+OgvjayFH8KiZPRjuKHNshDXJBuKJEV38z9RUVg2S+fBpWATallyUVMfapwuaxc5C kBBtr7oi6KZ0EyE5Cy/yHkAc3E65jMAIZLSTDI1wUO7z+Z1HPkXlu0lRCbPhMGY0ftRJ J7ebWbzoApiuCni54aNQHPGNxEVzQQv9OKXevrJUK6kZoD4Me0NoaCEdgra0X+KJ0tRX c6JA== X-Gm-Message-State: AIVw111IagRQFd7yX+p1jt+BBvJEZ+X7n0U5+i8SPDfJR8BuD3rRNaYc PPCtJDyFsGpzykEy X-Received: by 10.28.133.76 with SMTP id h73mr5154974wmd.92.1499623868906; Sun, 09 Jul 2017 11:11:08 -0700 (PDT) Received: from gumby.homeunix.com ([81.17.24.158]) by smtp.gmail.com with ESMTPSA id x94sm6614272wrb.47.2017.07.09.11.11.07 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 09 Jul 2017 11:11:08 -0700 (PDT) Date: Sun, 9 Jul 2017 19:11:05 +0100 From: RW To: freebsd-questions@freebsd.org Subject: Re: Interpreting NTP status Message-ID: <20170709191105.52dd6d4f@gumby.homeunix.com> In-Reply-To: References: X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.31; amd64-portbld-freebsd10.3) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jul 2017 18:11:11 -0000 On Sun, 9 Jul 2017 14:39:44 +0000 Carmel NY wrote: > A while back, I was receiving an error message about an outdated =E2=80= =9Cleap > second=E2=80=9D file. I Googled around and found an article that said to = put > the following in the =E2=80=9Crc.conf=E2=80=9D file to correct the problem I wouldn't bother. IIRC it's a cosmetic bug, the working leapfile may not get overwritten by a downloaded version if only the expiry date is changed, so you may get a few bogus warnings until you update your base system. Most of us don't even need the file, the information is supposed to come from an upstream time server, and even if that fails the worst case is that your clock jumps by a second every few years.=20 From owner-freebsd-questions@freebsd.org Mon Jul 10 00:03:21 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD050D98E65 for ; Mon, 10 Jul 2017 00:03:21 +0000 (UTC) (envelope-from k_jinattaporn@orion-electric.co.jp) Received: from mproxy52.aams5.jp (mproxy52.aams5.jp [210.134.181.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8046374D86; Mon, 10 Jul 2017 00:03:20 +0000 (UTC) (envelope-from k_jinattaporn@orion-electric.co.jp) Received: from ns.orion-electric.co.jp (ns.orion-electric.co.jp [202.238.55.34]) by mproxy52.aams5.jp (Sentrion-MTA-4.0.2/Switch-3.3.4) with ESMTP id v6A039Gk030806; Mon, 10 Jul 2017 09:03:10 +0900 Received: from mail1.orion-electric.co.jp (mail1.orion-electric.co.jp [129.1.32.20]) by ns.orion-electric.co.jp (8.12.8/8.12.8) with ESMTP id v6A039c9019604; Mon, 10 Jul 2017 09:03:09 +0900 Received: from OECPL04 (unknown [129.1.40.165]) by mail1.orion-electric.co.jp (Postfix) with ESMTP id 7CD17E980CB; Mon, 10 Jul 2017 09:03:09 +0900 (JST) From: "Jinattaporn K" To: "'Christofer Bell'" Cc: , , "'T_Urita'" References: <000e01d2f6da$423af830$c6b0e890$@orion-electric.co.jp> <19C95576-DE80-4830-9A53-B70B97284245@gmail.com> In-Reply-To: <19C95576-DE80-4830-9A53-B70B97284245@gmail.com> Subject: RE: Requirement for the distribution of FreeBSD License Date: Mon, 10 Jul 2017 09:03:00 +0900 Message-ID: <000d01d2f90f$e4d5d3d0$ae817b70$@orion-electric.co.jp> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQHq68mrMXWkCqqhL59c4P/epJrWqgI3pIVRogqKMPA= Content-Language: ja X-Virus-Header: clean Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 00:03:21 -0000 Dear Chris, =20 Well noted and thank you for your information. =20 =20 =20 =20 Best Regards, K.Jinattaporn. =20 From: Christofer Bell [mailto:christofer.c.bell@gmail.com]=20 Sent: Friday, July 07, 2017 11:29 PM To: Jinattaporn K Cc: freebsd-questions@freebsd.org; privacy@freebsd.org Subject: Re: Requirement for the distribution of FreeBSD License =20 =20 On Jul 6, 2017, at 11:34 PM, Jinattaporn K = > wrote: =20 Dear The Authors, Organization or Whom it may concern, As we have planned to issue your license for our product and trying to = find the preferable solution for distribution. So, could you please help to confirm which solution below are preferable. 1. Due to we already displayed your copyright on our product's display, = Is there any problem if we will issue only the guideline sentence in the Instruction Manual such as " Please reference the copyright information = as displayed on product" ? =20 Do this one =E2=80=94^ =20 --=20 Chris "If you wish to make an apple pie from scratch, you must first invent = the Universe." -- Carl Sagan =20 From owner-freebsd-questions@freebsd.org Mon Jul 10 00:18:19 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97410D99396 for ; Mon, 10 Jul 2017 00:18:19 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.20.71]) by mx1.freebsd.org (Postfix) with ESMTP id 70FE3752B5 for ; Mon, 10 Jul 2017 00:18:18 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id 35CFBCB8CE9; Sun, 9 Jul 2017 19:18:12 -0500 (CDT) Received: from 76.193.16.95 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Sun, 9 Jul 2017 19:18:12 -0500 (CDT) Message-ID: <52627.76.193.16.95.1499645892.squirrel@cosmo.uchicago.edu> In-Reply-To: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> Date: Sun, 9 Jul 2017 19:18:12 -0500 (CDT) Subject: Re: Unusual Question From: "Valeri Galtsev" To: "Doug Hardie" Cc: "freebsd-questions@freebsd.org Questions" Reply-To: galtsev@kicp.uchicago.edu User-Agent: SquirrelMail/1.4.8-5.el5.centos.7 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 00:18:19 -0000 On Sun, July 9, 2017 4:57 am, Doug Hardie wrote: > I have a FreeBSD 9.3 remote server that needs to be purged. I know that > rm -rf / will remove all the directory entries, but I need to write over > the drive. I thought that dd if=/dev/zero of=/dev/ada0 might do the > trick, If you were able to execute this, it still will not do the trick. What will happen is the following: the command at some point will descend into /dev and will delete block device / filesystem lives on, and after that point the command will just fail. I have vague recollection that that was one of the tricky questions on some sysadmin exam (Linux probably). I knew someone who actually did that on multi-user box he administered (space just snuck in after leading slash of absolute path). I happened to help him: we just mounted partitions on another machine and apart from /bin /boot and portion of /dev all still was there, so it was nothing like the disaster on can picture from nasty appearance of this command. Someone at some point mentioned that rm command goes into directories and subdirectories NOR in alphabetical order, so I left that out, but in incident I mention nothing but what alphabetically is before the device / filesystem lives on (/dev/hda2 was our case I believe) was lost. I hope, you had fun reading this ;-) Valeri > but it gives an not permitted error. The whole thing can crash and > burn at the end. This is an unmanned site so moving drives is not viable. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++ From owner-freebsd-questions@freebsd.org Mon Jul 10 00:34:08 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3EEFED99841 for ; Mon, 10 Jul 2017 00:34:08 +0000 (UTC) (envelope-from srs0=cpwb=6n=mail.sermon-archive.info=doug@sermon-archive.info) Received: from mail.sermon-archive.info (sermon-archive.info [71.177.216.148]) by mx1.freebsd.org (Postfix) with ESMTP id 19C8E75915 for ; Mon, 10 Jul 2017 00:34:07 +0000 (UTC) (envelope-from srs0=cpwb=6n=mail.sermon-archive.info=doug@sermon-archive.info) Received: from [10.0.1.251] (mini [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 3x5R6Q2JSpz2fk3B; Sun, 9 Jul 2017 17:34:06 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Unusual Question From: Doug Hardie X-Priority: 3 (Normal) In-Reply-To: <52627.76.193.16.95.1499645892.squirrel@cosmo.uchicago.edu> Date: Sun, 9 Jul 2017 17:34:06 -0700 Cc: "freebsd-questions@freebsd.org Questions" Content-Transfer-Encoding: quoted-printable Message-Id: References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> <52627.76.193.16.95.1499645892.squirrel@cosmo.uchicago.edu> To: galtsev@kicp.uchicago.edu X-Mailer: Apple Mail (2.3273) X-Virus-Scanned: clamav-milter 0.99.2 at mail X-Virus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 00:34:08 -0000 > On 9 July 2017, at 17:18, Valeri Galtsev = wrote: >=20 >=20 > On Sun, July 9, 2017 4:57 am, Doug Hardie wrote: >> I have a FreeBSD 9.3 remote server that needs to be purged. I know = that >> rm -rf / will remove all the directory entries, but I need to write = over >> the drive. I thought that dd if=3D/dev/zero of=3D/dev/ada0 might do = the >> trick, >=20 > If you were able to execute this, it still will not do the trick. What > will happen is the following: the command at some point will descend = into > /dev and will delete block device / filesystem lives on, and after = that > point the command will just fail. I have vague recollection that that = was > one of the tricky questions on some sysadmin exam (Linux probably). I = knew > someone who actually did that on multi-user box he administered (space > just snuck in after leading slash of absolute path). I happened to = help > him: we just mounted partitions on another machine and apart from /bin > /boot and portion of /dev all still was there, so it was nothing like = the > disaster on can picture from nasty appearance of this command. >=20 > Someone at some point mentioned that rm command goes into directories = and > subdirectories NOR in alphabetical order, so I left that out, but in > incident I mention nothing but what alphabetically is before the = device / > filesystem lives on (/dev/hda2 was our case I believe) was lost. >=20 > I hope, you had fun reading this ;-) >=20 > Valeri >=20 >> but it gives an not permitted error. The whole thing can crash and >> burn at the end. This is an unmanned site so moving drives is not = viable. >> _______________________________________________ Thanks for the info. I've never tried the rm approach, but the dd = approach seems to work. After a couple hours the machine became = unresponsive and ssh sessions were terminated. I think the drive is now = empty. I'd like to be able to get it back to verify, but that won't = happen. I still have 3 more systems to do this to. The others will = have to wait for awhile as I may still need them for a few more days. From owner-freebsd-questions@freebsd.org Mon Jul 10 05:22:46 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DF991D9DB2A for ; Mon, 10 Jul 2017 05:22:46 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9ED0B7BFF9 for ; Mon, 10 Jul 2017 05:22:46 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [2.247.251.13] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from ) id 1dUR9W-000233-D0; Mon, 10 Jul 2017 07:22:34 +0200 Received: from localhost.my.domain (localhost [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id v6A5MVsv002394 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 10 Jul 2017 07:22:31 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id v6A5MSM6002393; Mon, 10 Jul 2017 07:22:28 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Mon, 10 Jul 2017 07:22:28 +0200 From: Matthias Apitz To: Doug Hardie Cc: galtsev@kicp.uchicago.edu, "freebsd-questions@freebsd.org Questions" Subject: Re: Unusual Question Message-ID: <20170710052228.GA2338@c720-r314251> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , Doug Hardie , galtsev@kicp.uchicago.edu, "freebsd-questions@freebsd.org Questions" References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> <52627.76.193.16.95.1499645892.squirrel@cosmo.uchicago.edu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="J/dobhs11T7y2rNN" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 12.0-CURRENT r314251 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. User-Agent: Mutt/1.8.0 (2017-02-23) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 2.247.251.13 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 05:22:47 -0000 --J/dobhs11T7y2rNN Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable El d=C3=ADa domingo, julio 09, 2017 a las 05:34:06p. m. -0700, Doug Hardie = escribi=C3=B3: > >> but it gives an not permitted error. The whole thing can crash and > >> burn at the end. This is an unmanned site so moving drives is not via= ble. > >> _______________________________________________ >=20 > Thanks for the info. I've never tried the rm approach, but the dd approa= ch seems to work. After a couple hours the machine became unresponsive and= ssh sessions were terminated. I think the drive is now empty. I'd like t= o be able to get it back to verify, but that won't happen. I still have 3 = more systems to do this to. The others will have to wait for awhile as I m= ay still need them for a few more days. I do not think that this approach worked in the sense of overwriting all blocks of the disk. While walking through at some point the kernel will miss sectors of the disk, for example of memory mapped files of shared libs of other running processes or swapped out memory to disk. And the kern= el will just crash or halt and you will notice that as terminating ssh session. Do not rely on the fact that the (sensitive) information on the disk was overwritten. The only secure way is doing this from a system running on some other disk and even this would allow to recover information with forensic tools reading beside of the tracks. Only physical destruction will help, for example burning the thing, as you said. matthias --=20 Matthias Apitz, =E2=9C=89 guru@unixarea.de, =E2=8C=82 http://www.unixarea.d= e/ =E2=98=8E +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub 8. Mai 1945: Wer nicht feiert hat den Krieg verloren. 8 de mayo de 1945: Quien no festeja perdi=C3=B3 la Guerra. May 8, 1945: Who does not celebrate lost the War. --J/dobhs11T7y2rNN Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEXmn7rBYYViyzy/vBR8z35Hb+nREFAlljDw0ACgkQR8z35Hb+ nRFEPRAAnabnd70ILlE5iNoPShbzcj61aAnpBHu4Dy2HOYzZAsNIoEQ+wv0Qjmoc 3wxqqyjIoTDY6pgzxVHOK6/PMrAdA7OaYOJWfu/QtXo0aqX4qsHyf2TK8zbwGWzs q1ingtBg7BwBZ7CHPgPf4CiuQTyle6RU64icNOtRMCUAZMuSK4sOBiqU7CCCKuYZ CWes7YRBSPMZ0aojaxoS815L+8C+2M7t5Y3MUJ6Gz5pwKEEYT6L4eAp/ylpJMBz9 MkHosNRF81ZcZk+cYyFRCSIEew4/yxSAMkXeYbFH7YPivqosc/RTOIGPtZDnhS3P ErqHNpy3kXyw7UNMzSeuYZMjIg2N2XrodgIK5yqHQIvzcuNCKDGjSNrdVprcf5FD 32Ieqt2I+TuZwdNwCe1sGIoNoWLvHD4Le5Nw/h+z8Uy7clbEF7y/nxtamks256HB tZwiAZBVUbTGw7riVT7hrNPpkvoyIlaHPJSGTdLA/182lntCG5ZKWXDTq/HLR/CI yV4VwjTIGGJct2GYUC8cZkn1zTeyILGWlTAfqSgAZMgjHvDBxeZVTig8el6mD0zy 4eSBcRqPbiq4656MQTPfJreQ1sqPztOF2jVJbA1DLbQT/mowyJOMjwGViJQB54tv OHsyilkWH/6W7ChGMlzklArQfzGvga3y4BceKuNftgEBXf3XrCk= =J113 -----END PGP SIGNATURE----- --J/dobhs11T7y2rNN-- From owner-freebsd-questions@freebsd.org Mon Jul 10 05:33:42 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A2F1D9DED7 for ; Mon, 10 Jul 2017 05:33:42 +0000 (UTC) (envelope-from srs0=cpwb=6n=mail.sermon-archive.info=doug@sermon-archive.info) Received: from mail.sermon-archive.info (sermon-archive.info [71.177.216.148]) by mx1.freebsd.org (Postfix) with ESMTP id 154D07C4C4 for ; Mon, 10 Jul 2017 05:33:41 +0000 (UTC) (envelope-from srs0=cpwb=6n=mail.sermon-archive.info=doug@sermon-archive.info) Received: from [10.0.1.251] (mini [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 3x5Ym50lSGz2fjwC; Sun, 9 Jul 2017 22:33:41 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Unusual Question From: Doug Hardie In-Reply-To: <20170710052228.GA2338@c720-r314251> Date: Sun, 9 Jul 2017 22:33:40 -0700 Cc: Doug Hardie , galtsev@kicp.uchicago.edu, "freebsd-questions@freebsd.org Questions" Content-Transfer-Encoding: quoted-printable Message-Id: <5156E6FD-03AE-4244-B3AB-32007439AD20@mail.sermon-archive.info> References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> <52627.76.193.16.95.1499645892.squirrel@cosmo.uchicago.edu> <20170710052228.GA2338@c720-r314251> To: Matthias Apitz X-Mailer: Apple Mail (2.3273) X-Virus-Scanned: clamav-milter 0.99.2 at mail X-Virus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 05:33:42 -0000 > On 9 July 2017, at 22:22, Matthias Apitz wrote: >=20 > El d=C3=ADa domingo, julio 09, 2017 a las 05:34:06p. m. -0700, Doug = Hardie escribi=C3=B3: >=20 >>>> but it gives an not permitted error. The whole thing can crash and >>>> burn at the end. This is an unmanned site so moving drives is not = viable. >>>> _______________________________________________ >>=20 >> Thanks for the info. I've never tried the rm approach, but the dd = approach seems to work. After a couple hours the machine became = unresponsive and ssh sessions were terminated. I think the drive is now = empty. I'd like to be able to get it back to verify, but that won't = happen. I still have 3 more systems to do this to. The others will = have to wait for awhile as I may still need them for a few more days. >=20 > I do not think that this approach worked in the sense of overwriting = all > blocks of the disk. While walking through at some point the kernel = will > miss sectors of the disk, for example of memory mapped files of shared > libs of other running processes or swapped out memory to disk. And the = kernel > will just crash or halt and you will notice that as terminating ssh = session. > Do not rely on the fact that the (sensitive) information on the disk = was > overwritten. The only secure way is doing this from a system running = on > some other disk and even this would allow to recover information with > forensic tools reading beside of the tracks. Only physical destruction > will help, for example burning the thing, as you said. The swap space was on this drive so it should be overwritten also. = Physical memory will go when the power goes off. It would be nice to be = able to get the drive back and see just how much was overwritten, but = that is not possible. I don't see why dd would not run to completion. = The first test I ran it reported that it had cleared over 300 GB on a = 500 GB drive. I may see if I can setup another system here and try that = where I can monitor and test the result. From owner-freebsd-questions@freebsd.org Mon Jul 10 05:41:23 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 24396D9E20A for ; Mon, 10 Jul 2017 05:41:23 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D76467C7C9 for ; Mon, 10 Jul 2017 05:41:22 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [2.247.251.13] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from ) id 1dURRg-0004Cp-7A; Mon, 10 Jul 2017 07:41:20 +0200 Received: from localhost.my.domain (localhost [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id v6A5fHOL002490 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 10 Jul 2017 07:41:17 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id v6A5fGQA002489; Mon, 10 Jul 2017 07:41:16 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Mon, 10 Jul 2017 07:41:16 +0200 From: Matthias Apitz To: Doug Hardie Cc: "freebsd-questions@freebsd.org Questions" , galtsev@kicp.uchicago.edu Subject: Re: Unusual Question Message-ID: <20170710054116.GA2445@c720-r314251> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , Doug Hardie , "freebsd-questions@freebsd.org Questions" , galtsev@kicp.uchicago.edu References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> <52627.76.193.16.95.1499645892.squirrel@cosmo.uchicago.edu> <20170710052228.GA2338@c720-r314251> <5156E6FD-03AE-4244-B3AB-32007439AD20@mail.sermon-archive.info> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="8t9RHnE3ZwKMSgU+" Content-Disposition: inline In-Reply-To: <5156E6FD-03AE-4244-B3AB-32007439AD20@mail.sermon-archive.info> X-Operating-System: FreeBSD 12.0-CURRENT r314251 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. User-Agent: Mutt/1.8.0 (2017-02-23) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 2.247.251.13 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 05:41:23 -0000 --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable El d=C3=ADa domingo, julio 09, 2017 a las 10:33:40p. m. -0700, Doug Hardie = escribi=C3=B3: > > I do not think that this approach worked in the sense of overwriting all > > blocks of the disk. While walking through at some point the kernel will > > miss sectors of the disk, for example of memory mapped files of shared > > libs of other running processes or swapped out memory to disk. And the = kernel > > will just crash or halt and you will notice that as terminating ssh ses= sion. > > Do not rely on the fact that the (sensitive) information on the disk was > > overwritten. The only secure way is doing this from a system running on > > some other disk and even this would allow to recover information with > > forensic tools reading beside of the tracks. Only physical destruction > > will help, for example burning the thing, as you said. >=20 > The swap space was on this drive so it should be overwritten also. Physi= cal memory will go when the power goes off. It would be nice to be able to= get the drive back and see just how much was overwritten, but that is not = possible. I don't see why dd would not run to completion. The first test I = ran it reported that it had cleared over 300 GB on a 500 GB drive. I may s= ee if I can setup another system here and try that where I can monitor and = test the result. Doug, you missed my point. Your dd proc will overwrite at some point the swaped-out pages and/or text segments which have been memory mapped by the kernel. The kernel will miss them and crash and so you have only overwritten a (maybe small) part of the disk. matthias --=20 Matthias Apitz, =E2=9C=89 guru@unixarea.de, =E2=8C=82 http://www.unixarea.d= e/ =E2=98=8E +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub 8. Mai 1945: Wer nicht feiert hat den Krieg verloren. 8 de mayo de 1945: Quien no festeja perdi=C3=B3 la Guerra. May 8, 1945: Who does not celebrate lost the War. --8t9RHnE3ZwKMSgU+ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEXmn7rBYYViyzy/vBR8z35Hb+nREFAlljE3kACgkQR8z35Hb+ nRFibg//cX7ujNGvdhubkGbQ2O0WqHS6KjDqqbb1wqoUqYCBpvp75KpeuD2lvKYB Kj28NGUBFnECly+JStN1QBJToyCAx0ckCnkHUUgt4XsPt22x4Z0IIbkYfXQFAJCg Ogl4nv9iW69YeZmjAK1pgSKFJdpEpVXGpJUZvJUK9IU2eA0EdV8U0pGtU0TlfXpF D5jvFq8nhiARjL7DeCq0tMgfE423i/6TixFMgGP/310wW99aMCqHz/7eq2GuEAjT JFZMnqQh7x8nbrnLlsAV+ivEDWonUhVuS4DlSvrAUkqunWtjGDfWi86IYCnSm+TN nRaVV0tut/yGbT1C/PnojBEyg4GIS/KKR/RRj51BSo06WBgK2mumDNzIw3Gc/yu8 6TP5R7gNpx9Ssslnd14Qj2WfzxI6+OT9miIY3gzXWB4rsFZWJiaCTkfJHrun7rGd brKYa+LJDnEhDPzREBWF7ZsCXOszLLU55LLx0ffNCbaoSqCf+PuJ3oKYDf4Srkj8 MYBUZz+z6uAGx3dCV4BDuW6ag962xoSOmFKPuduE4U1hLrTxuvBbIOgkBmafiVn9 nO2ghViSqSgP8B2B2tfCy9WI/IguW8aHa9alWqGh0zY0h3gB4XwjB6CYpYH4jeTO /lNCD14cRGKAPA1iju6375rVDd6OgCYYLCt3vxncSb1rJOo1Eho= =nS1x -----END PGP SIGNATURE----- --8t9RHnE3ZwKMSgU+-- From owner-freebsd-questions@freebsd.org Mon Jul 10 05:48:49 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA1A3D9E366 for ; Mon, 10 Jul 2017 05:48:49 +0000 (UTC) (envelope-from holindho@saunalahti.fi) Received: from vs23.mail.saunalahti.fi (vs23.mail.saunalahti.fi [193.64.193.199]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vs23.mail.saunalahti.fi", Issuer "vs23.mail.saunalahti.fi" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A9DC87CAA9 for ; Mon, 10 Jul 2017 05:48:49 +0000 (UTC) (envelope-from holindho@saunalahti.fi) Received: from vs23.mail.saunalahti.fi (localhost [127.0.0.1]) by vs23.mail.saunalahti.fi (Postfix) with ESMTP id B1E3C20091 for ; Mon, 10 Jul 2017 08:48:39 +0300 (EEST) Received: from gw03.mail.saunalahti.fi (gw03.mail.saunalahti.fi [195.197.172.111]) by vs23.mail.saunalahti.fi (Postfix) with ESMTP id A761E2006A for ; Mon, 10 Jul 2017 08:48:39 +0300 (EEST) Received: from [10.0.0.7] (62-78-248-13.bb.dnainternet.fi [62.78.248.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by gw03.mail.saunalahti.fi (Postfix) with ESMTPSA id 9F7BE20097 for ; Mon, 10 Jul 2017 08:48:38 +0300 (EEST) Subject: Re: Unusual Question To: freebsd-questions@freebsd.org References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> <52627.76.193.16.95.1499645892.squirrel@cosmo.uchicago.edu> <20170710052228.GA2338@c720-r314251> <5156E6FD-03AE-4244-B3AB-32007439AD20@mail.sermon-archive.info> From: Heikki Lindholm Message-ID: <947af5eb-6d29-51c2-25b8-b183561008c4@saunalahti.fi> Date: Mon, 10 Jul 2017 08:48:34 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <5156E6FD-03AE-4244-B3AB-32007439AD20@mail.sermon-archive.info> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 05:48:50 -0000 On 10.07.2017 08:33, Doug Hardie wrote: > >> On 9 July 2017, at 22:22, Matthias Apitz wrote: >> >> El día domingo, julio 09, 2017 a las 05:34:06p. m. -0700, Doug Hardie escribió: >> >>>>> but it gives an not permitted error. The whole thing can crash and >>>>> burn at the end. This is an unmanned site so moving drives is not viable. >>>>> _______________________________________________ >>> >>> Thanks for the info. I've never tried the rm approach, but the dd approach seems to work. After a couple hours the machine became unresponsive and ssh sessions were terminated. I think the drive is now empty. I'd like to be able to get it back to verify, but that won't happen. I still have 3 more systems to do this to. The others will have to wait for awhile as I may still need them for a few more days. >> >> I do not think that this approach worked in the sense of overwriting all >> blocks of the disk. While walking through at some point the kernel will >> miss sectors of the disk, for example of memory mapped files of shared >> libs of other running processes or swapped out memory to disk. And the kernel >> will just crash or halt and you will notice that as terminating ssh session. >> Do not rely on the fact that the (sensitive) information on the disk was >> overwritten. The only secure way is doing this from a system running on >> some other disk and even this would allow to recover information with >> forensic tools reading beside of the tracks. Only physical destruction >> will help, for example burning the thing, as you said. > > The swap space was on this drive so it should be overwritten also. Physical memory will go when the power goes off. It would be nice to be able to get the drive back and see just how much was overwritten, but that is not possible. I don't see why dd would not run to completion. The first test I ran it reported that it had cleared over 300 GB on a 500 GB drive. I may see if I can setup another system here and try that where I can monitor and test the result. Virtualbox would seem like the obvious choice to see what happens. Just set up a system with the same attributes and software versions and the same runtime env (daemons). From owner-freebsd-questions@freebsd.org Mon Jul 10 05:54:38 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 78742D9E6F2 for ; Mon, 10 Jul 2017 05:54:38 +0000 (UTC) (envelope-from srs0=cpwb=6n=mail.sermon-archive.info=doug@sermon-archive.info) Received: from mail.sermon-archive.info (sermon-archive.info [71.177.216.148]) by mx1.freebsd.org (Postfix) with ESMTP id 627D57CF1A for ; Mon, 10 Jul 2017 05:54:38 +0000 (UTC) (envelope-from srs0=cpwb=6n=mail.sermon-archive.info=doug@sermon-archive.info) Received: from [10.0.1.251] (mini [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 3x5ZDF4xc6z2fkDV; Sun, 9 Jul 2017 22:54:37 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Unusual Question From: Doug Hardie In-Reply-To: <20170710054116.GA2445@c720-r314251> Date: Sun, 9 Jul 2017 22:54:37 -0700 Cc: Doug Hardie , "freebsd-questions@freebsd.org Questions" , galtsev@kicp.uchicago.edu Content-Transfer-Encoding: quoted-printable Message-Id: <242B2A7C-7E4A-4B22-AA65-AEB6E3B40340@mail.sermon-archive.info> References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> <52627.76.193.16.95.1499645892.squirrel@cosmo.uchicago.edu> <20170710052228.GA2338@c720-r314251> <5156E6FD-03AE-4244-B3AB-32007439AD20@mail.sermon-archive.info> <20170710054116.GA2445@c720-r314251> To: Matthias Apitz X-Mailer: Apple Mail (2.3273) X-Virus-Scanned: clamav-milter 0.99.2 at mail X-Virus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 05:54:38 -0000 > On 9 July 2017, at 22:41, Matthias Apitz wrote: >=20 > El d=C3=ADa domingo, julio 09, 2017 a las 10:33:40p. m. -0700, Doug = Hardie escribi=C3=B3: >=20 >>> I do not think that this approach worked in the sense of overwriting = all >>> blocks of the disk. While walking through at some point the kernel = will >>> miss sectors of the disk, for example of memory mapped files of = shared >>> libs of other running processes or swapped out memory to disk. And = the kernel >>> will just crash or halt and you will notice that as terminating ssh = session. >>> Do not rely on the fact that the (sensitive) information on the disk = was >>> overwritten. The only secure way is doing this from a system running = on >>> some other disk and even this would allow to recover information = with >>> forensic tools reading beside of the tracks. Only physical = destruction >>> will help, for example burning the thing, as you said. >>=20 >> The swap space was on this drive so it should be overwritten also. = Physical memory will go when the power goes off. It would be nice to be = able to get the drive back and see just how much was overwritten, but = that is not possible. I don't see why dd would not run to completion. = The first test I ran it reported that it had cleared over 300 GB on a = 500 GB drive. I may see if I can setup another system here and try that = where I can monitor and test the result. >=20 > Doug, you missed my point. Your dd proc will overwrite at some point = the > swaped-out pages and/or text segments which have been memory mapped by > the kernel. The kernel will miss them and crash and so you have only > overwritten a (maybe small) part of the disk. The swap partition is the last partition on the drive. So if dd/system = failed while writing that, then my goal would be complete. There was = nothing running on the system accessing any sensitive data. The only = areas of concern was the main partition. As for the kernel itself going = down, I would expect that would not be able to hazard a reliable guess. = It could happen, but I would expect if that were the case to not be able = to get to the 60% point. From owner-freebsd-questions@freebsd.org Mon Jul 10 08:06:15 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 79833DA06C0 for ; Mon, 10 Jul 2017 08:06:15 +0000 (UTC) (envelope-from 4250.10.freebsd-questions=freebsd.org@email-od.com) Received: from bca5.email-od.com (bca5.email-od.com [207.246.239.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3F2087FE8D for ; Mon, 10 Jul 2017 08:06:14 +0000 (UTC) (envelope-from 4250.10.freebsd-questions=freebsd.org@email-od.com) DKIM-Signature: v=1; a=rsa-sha256; d=email-od.com;i=@email-od.com;s=dkim; c=relaxed/relaxed; q=dns/txt; t=1499673967; x=1502265967; h=x-thread-info:date:from:to:cc:subject:message-id:in-reply-to:references:mime-version:content-type:content-transfer-encoding; bh=6WpnIts673QzJXg8MoIny8sAw/ZE4JCg6WV+aWzzcws=; b=FwZ2mm/hF87IUG9X/rPVvzG/QFXzAOHtCcPamkaZjWov5BnkDg3vHVu23Xfj5luHdfJ1UrOGGxHjFtypy2m3o/DwiC5g4xNUTDv8fnpi4BKffseJ/7QcJmsC2LZt4T1X4RO2QnnBbGzpWhjIaAvYlevQx3tDefiZB62afAfNZak= X-Thread-Info: NDI1MC4xMi5kNzAwMDAwMDUwMjkxMi5mcmVlYnNkLXF1ZXN0aW9ucz1mcmVlYnNkLm9yZw== Received: from r3.us-west-2a.aws.in.socketlabs.com (r3.us-west-2a.aws.in.socketlabs.com [54.187.94.11]) by bca2.email-od.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Mon, 10 Jul 2017 04:05:55 -0400 Received: from smtp.lan.sohara.org (EMTPY [89.127.62.20]) by r3.us-west-2a.aws.in.socketlabs.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Mon, 10 Jul 2017 04:06:02 -0400 Received: from [192.168.63.1] (helo=steve.lan.sohara.org) by smtp.lan.sohara.org with smtp (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dUTib-0009TR-9h; Mon, 10 Jul 2017 08:06:57 +0000 Date: Mon, 10 Jul 2017 09:05:47 +0100 From: Steve O'Hara-Smith To: freebsd-questions@freebsd.org Cc: Matthias Apitz Subject: Re: Unusual Question Message-Id: <20170710090547.15ee3afc07c09955ba621ae1@sohara.org> In-Reply-To: <20170710052228.GA2338@c720-r314251> References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> <52627.76.193.16.95.1499645892.squirrel@cosmo.uchicago.edu> <20170710052228.GA2338@c720-r314251> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; amd64-portbld-freebsd10.3) X-Clacks-Overhead: "GNU Terry Pratchett" Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 08:06:15 -0000 On Mon, 10 Jul 2017 07:22:28 +0200 Matthias Apitz wrote: > I do not think that this approach worked in the sense of overwriting all > blocks of the disk. While walking through at some point the kernel will I see no reason why it shouldn't, provided the dd process doing the work never needs to swap anything in (likely it's small and running a tight loop). > miss sectors of the disk, for example of memory mapped files of shared > libs of other running processes or swapped out memory to disk. And the The sectors are still there, just filled with 0s or random data the kernel will have no trouble reading them. > kernel will just crash or halt and you will notice that as terminating The kernel will not crash or halt, processes will if they have to page in corrupted data but that's all. Processes that don't page in anything will just carry on running - if they don't read the disc they'll never know it's been overwritten. > ssh session. Unless sshd has to page something in it won't crash. > Do not rely on the fact that the (sensitive) information on > the disk was overwritten. I see no reason to expect that the dd process won't finish clearing the disk and exit normally. > The only secure way is doing this from a system > running on some other disk and even this would allow to recover > information with forensic tools reading beside of the tracks. Only > physical destruction will help, for example burning the thing, as you > said. Sure, but absent a motive to spend the money forensic data analysis costs writing 0s or random numbers over the whole drive will do fine. If you fear forensic analysis then use thermite. -- Steve O'Hara-Smith From owner-freebsd-questions@freebsd.org Mon Jul 10 09:23:15 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5CBCBDA1E1E for ; Mon, 10 Jul 2017 09:23:15 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E06BB821D5 for ; Mon, 10 Jul 2017 09:23:14 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from zero-gravitas.local (unknown [85.199.232.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 8674FCF8B for ; Mon, 10 Jul 2017 09:23:11 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/8674FCF8B; dkim=none; dkim-atps=neutral Subject: Re: Interpreting NTP status To: freebsd-questions@freebsd.org References: From: Matthew Seaman Message-ID: <0c954f96-eeb1-f811-8806-9e5fad7420f4@FreeBSD.org> Date: Mon, 10 Jul 2017 10:23:09 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="0f9FtSHTRNKo8Loq9HNKKawc8M0at3ieq" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 09:23:15 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --0f9FtSHTRNKo8Loq9HNKKawc8M0at3ieq Content-Type: multipart/mixed; boundary="xALBEdqViTQhPXwsK4MnF2uWNVJ4ugKh8"; protected-headers="v1" From: Matthew Seaman To: freebsd-questions@freebsd.org Message-ID: <0c954f96-eeb1-f811-8806-9e5fad7420f4@FreeBSD.org> Subject: Re: Interpreting NTP status References: In-Reply-To: --xALBEdqViTQhPXwsK4MnF2uWNVJ4ugKh8 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2017/07/09 15:39, Carmel NY wrote: > NTP status: > remote refid st t when poll reach delay offset = jitter > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D > +198.55.111.50 133.157.29.35 3 u 760 1024 377 87.913 5.793 = 18.418 > *192.155.90.13 142.66.101.13 2 u 264 1024 377 45.449 -2.235 = 2.925 > 2607:fa18::2407 .STEP. 16 u - 1024 0 0.000 0.000 = 0.000 >=20 > I am hoping someone can tell me exactly what this means. I cannot find > any documentation on how to interpret this. This is the output from 'ntpq -p' It's described under the 'peers' command in ntpq(8) for using ntpq interactively. It shows what NTP servers you are synch'd to, how frequently you are polling those servers, how well you are managing to communicate with them, how long it takes an NTP query to do a round-trip to the servers and how close your local clock is to your time sources. The 'offset' column is measured in milliseconds, so you are fairly well synched. However, you only have two working servers -- you are unable to reach the 3rd server possibly because you don't have IPv6 yet. This means you can't use the 'majority consensus' algorithm -- so if one of your timesources drifted off, you have no way of knowing which is right and which is wrong. Cheers, Matthew --xALBEdqViTQhPXwsK4MnF2uWNVJ4ugKh8-- --0f9FtSHTRNKo8Loq9HNKKawc8M0at3ieq Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJZY0eDXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnhSYP/jreWVAxx3z272D4jnN3VM84 tyXSLQ5+PdQagxg8Fu98rm9fO1dD7kPJfP38f+0jNABYoI6iJTraHsLcvyogjB2L 7cClR09Hb+d70VNz+cknh66/t1VjnLLWChkm514ayseDftMDPpRjZkoFsK7rFgSa TZyfQmDffifO3YI63unRmXnR+6ILuG5TLUjgwHo0o/1F2jMUmPKHcANoy9m2gd90 o3gFmu8ociezUFiYQZgTepD2paOM3E/yP0IXQCnUzMQMKwLKKeBNFNpzXjoBuQPi PR7JDBSFLhtAnstkDK3vhH3r+ckACiBu4sVCtHdPxuZyEoTnkprNlYLdHf1B1HoD T+7y7uxkhXF1kgyZtB44zG6be//47uWCR7ezdN1g+GqtEyhde8xqwIoYqUrIl/8M gLV0zDN6H/o0hS+u8byLNOYnWGogeGU2o2/lZ7bXl+uaZoA4IeG5MR+kNXNpE4nR obyRwfhYo6pC5W8UWAQfNeKkYX/z1lcRy+qv+j3fijoquh/7QFmGRtdAChVTd1cQ b0ubJ3cJAqdWvnPpKXqyoLJ9VJZLUVVFx0XZx/zTIrBnpBebMplLMdZmkJY0BvX0 Ik2+nR3aof1rcJstEdI2/OPB3kgN1s6eima3HYTHm0oCwQAilx+JgAqQRVAHZPGE S94LwL0YuOukNscazR2t =4CV2 -----END PGP SIGNATURE----- --0f9FtSHTRNKo8Loq9HNKKawc8M0at3ieq-- From owner-freebsd-questions@freebsd.org Mon Jul 10 09:34:22 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CCA65DA2364 for ; Mon, 10 Jul 2017 09:34:22 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5C0A882723 for ; Mon, 10 Jul 2017 09:34:21 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from zero-gravitas.local (unknown [85.199.232.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 704AECF93 for ; Mon, 10 Jul 2017 09:34:13 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/704AECF93; dkim=none; dkim-atps=neutral Subject: Re: Unusual Question To: freebsd-questions@freebsd.org References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> From: Matthew Seaman Message-ID: Date: Mon, 10 Jul 2017 10:34:11 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="6GStM2knSQWOC9hhtWNWd1ai6DKwx0BmC" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 09:34:22 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --6GStM2knSQWOC9hhtWNWd1ai6DKwx0BmC Content-Type: multipart/mixed; boundary="QgWhl2lgkxwqaFR5CETtE4tgJa7pQrDXM"; protected-headers="v1" From: Matthew Seaman To: freebsd-questions@freebsd.org Message-ID: Subject: Re: Unusual Question References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> In-Reply-To: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> --QgWhl2lgkxwqaFR5CETtE4tgJa7pQrDXM Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2017/07/09 10:57, Doug Hardie wrote: > I have a FreeBSD 9.3 remote server that needs to be purged. I know > that rm -rf / will remove all the directory entries, but I need to > write over the drive. I thought that dd if=3D/dev/zero of=3D/dev/ada0 > might do the trick, but it gives an not permitted error. The whole > thing can crash and burn at the end. This is an unmanned site so > moving drives is not viable. I'd do this by usinf dd(1) but slightly more carefully. You need a small, temporary, bootable partition that contains dd(8). This could be either by booting from install media -- although as you say, the machine is in an unmanned location so that may not be feasible -- or you could possibly re-purpose an existing swap partition. You can then zero out each of the other partitions /dev/ada0p1 etc on your drive -- the idea being not to try and delete the OS you're running from, as that will likely crash in the middle and leave things half deleted. Cheers, Matthew --QgWhl2lgkxwqaFR5CETtE4tgJa7pQrDXM-- --6GStM2knSQWOC9hhtWNWd1ai6DKwx0BmC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJZY0obXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnZPsP/AupcfY3pL9IMgoHEeQyD9Q+ Xw2isg1KgKtMNLw1reNPKsSscXiMFT3qTwDs5qDHGbcQ7Yiq9yWw1WenIObLSJl3 38GXhQwKHHDC7+xBN/nwcfUzeZBPYEsGJjQRebe8H5a0NZGF+0N4FRLe1PpzYzrx nbm7a2tPZibKh7kBJLJMpYXhNLbu3DNnDbIcy5IZhi4TVYnW6sYoBNH/o719eDv1 d+w4bhxI3mJiQU1snH0/Y49Jubl45iN4A4vj7BgT7YEeFMgemPwY8d9j2P6WrMoy D8wQqzHYFizeIFZnti07ximanU/rKvc8zEJhPR6Hpp9aHQ0ELg1LunE/el/PePOp 9Ti5dHHe9GkvtARLoUhmTGi1PNk2IfXEwIl/55pTY3tY8acVGnKfBtwgqQucGqkD vUlkvAE+ynJg+Xd0l1575S6NOl1tXigRAzi5H55q89rhDuhJO69La8Z2d+h97Tqs D70ow1P1NCcIYwFq1d6dbbxcSNKV1zwh7OntsjMqw7FlowRYIv2a8mYmHNkBe9Xz JP3Vqbzwm+k7roOsTwq7hV82evcMV5XPk2/Z0pwZPuvqj4aHLwV1sFCGFkSce+YG vT96S8Aj/MRbxMjLJKEwNSf35Xthq7aEKbuQ9isvAVrfePC6yRRVRAW6CW5KAPJK 6S4i14dutO3jccWSYEU2 =5ts6 -----END PGP SIGNATURE----- --6GStM2knSQWOC9hhtWNWd1ai6DKwx0BmC-- From owner-freebsd-questions@freebsd.org Mon Jul 10 09:42:05 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 68F40DA25F4 for ; Mon, 10 Jul 2017 09:42:05 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EF6D682A9E for ; Mon, 10 Jul 2017 09:42:04 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from zero-gravitas.local (unknown [85.199.232.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 47950CF96 for ; Mon, 10 Jul 2017 09:42:03 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=infracaninophile.co.uk Authentication-Results: smtp.infracaninophile.co.uk/47950CF96; dkim=none; dkim-atps=neutral Subject: Re: Unusual Question To: freebsd-questions@freebsd.org References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> From: Matthew Seaman Message-ID: Date: Mon, 10 Jul 2017 10:42:08 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ed7MQaNtSWjSnRCL6HjF2vEtoBmqdvLTC" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 09:42:05 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ed7MQaNtSWjSnRCL6HjF2vEtoBmqdvLTC Content-Type: multipart/mixed; boundary="jA5AC8MJ2iOVC1E4bTQkMm6wf1GcbDUME"; protected-headers="v1" From: Matthew Seaman To: freebsd-questions@freebsd.org Message-ID: Subject: Re: Unusual Question References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> In-Reply-To: --jA5AC8MJ2iOVC1E4bTQkMm6wf1GcbDUME Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2017/07/10 10:34, Matthew Seaman wrote: > On 2017/07/09 10:57, Doug Hardie wrote: >> I have a FreeBSD 9.3 remote server that needs to be purged. I know >> that rm -rf / will remove all the directory entries, but I need to >> write over the drive. I thought that dd if=3D/dev/zero of=3D/dev/ada0= >> might do the trick, but it gives an not permitted error. The whole >> thing can crash and burn at the end. This is an unmanned site so >> moving drives is not viable. >=20 > I'd do this by usinf dd(1) but slightly more carefully. You need a > small, temporary, bootable partition that contains dd(8). This could b= e > either by booting from install media -- although as you say, the machin= e > is in an unmanned location so that may not be feasible -- or you could > possibly re-purpose an existing swap partition. You can then zero out > each of the other partitions /dev/ada0p1 etc on your drive -- the idea > being not to try and delete the OS you're running from, as that will > likely crash in the middle and leave things half deleted. >=20 Um.. to clarify. The temporary partition should contain /not only/ dd(8) but also at minimum /all the other basic stuff the system needs to boot into a single user shell/ -- given you haven't got a remote console, then you'ld all the stuff so you could configure it with networking and bring it up multiuser. Cheers, Matthew --jA5AC8MJ2iOVC1E4bTQkMm6wf1GcbDUME-- --ed7MQaNtSWjSnRCL6HjF2vEtoBmqdvLTC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJZY0vwXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnpY8P/jNrYIeDMapXdGMFIjXKYRen ETFJn8knt8075Oa7QSJupuG6qKvI7cAavcQNf1c5Z0Zg2ukSH21DHBOMD8CAg9M8 /u5/k+wdnzev48OWg+DkqZ9lLOy3tmeocM1T2MYIX8rx57kl7fagnEUknc8YszOR tGjbxDXhD9Pn14Atov4aOUYmquuk6rxkf0jPZGzDLkQI/Iq9yx332DgcB/6EnTpu 4RTM+wvAdX5lqi6Eyr1bV2ayiyUDz6EVn8ySW1+ku/AVcNq5bibMIUVkZqLdWjrO wemxUCYCxUPWbB81K17yFTKNn5Ku+YHUK0X7x+luK38pFcuIPMi6hg76v7rr55Tx zPdsBZUD5vfGx37FUHiykXz5IwI3rLKvR6mIqOtDWzg4gy2u0rDWtEowUR3OUSDL ctQkNMLily1iTw7qsjioPPl9usYz401vCQDbaAxJDF6oRpLTfWtWa2avkc8IezYR OhYwnIq3VLz0QfqpTcKRfaod5pA4HSc+8jeB1QcHQMiMpPEB6HtgjcRKahA/kRXa 5dnSrgW0DeJrO9ugHZbturawTEtMyqjXUV//QgOqK763dSiJiAQQiLyQCKO7PN9u 7+ZucdnHVgcUuotDud7p7IsXEpgpzmOYlq//plAg6bHWXidzmyUvGW+e96ux3Vpa qEEdkc9nBQWbrfUOmRyh =5b2H -----END PGP SIGNATURE----- --ed7MQaNtSWjSnRCL6HjF2vEtoBmqdvLTC-- From owner-freebsd-questions@freebsd.org Mon Jul 10 12:10:14 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 256E7DA67EF for ; Mon, 10 Jul 2017 12:10:14 +0000 (UTC) (envelope-from as@cmplx.uk) Received: from jail0199.vps.exonetric.net (jail0199.vps.exonetric.net [IPv6:2a02:1658:1::199:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "jail0199.vps.exonetric.net", Issuer "jail0199.vps.exonetric.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C8F0C20F7 for ; Mon, 10 Jul 2017 12:10:13 +0000 (UTC) (envelope-from as@cmplx.uk) Received: from jail0199.vps.exonetric.net (jail0199.vps.exonetric.net [178.250.76.108]) by jail0199.vps.exonetric.net (8.15.2/8.15.2) with ESMTPS id v6ACAC9R010884 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 10 Jul 2017 12:10:12 GMT (envelope-from as@jail0199.vps.exonetric.net) Received: (from as@localhost) by jail0199.vps.exonetric.net (8.15.2/8.15.2/Submit) id v6ACACeW010883 for freebsd-questions@freebsd.org; Mon, 10 Jul 2017 12:10:12 GMT (envelope-from as) Date: Mon, 10 Jul 2017 12:10:12 GMT From: Anton Shterenlikht Message-Id: <201707101210.v6ACACeW010883@jail0199.vps.exonetric.net> To: freebsd-questions@freebsd.org Subject: sendmail status and auth advice X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 12:10:14 -0000 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/SMTP-Auth.html points to http://www.sendmail.org/~ca/email/auth.html which is up to 8.13, last updated in 2006. The version I have on FreeBSD 11.0-RELEASE-p9 is sendmail+tls+sasl2-8.15.2_3. So I'm worried the advice might not be up to date. Is it? Trying to find some sendmail docs online I realised that sendmail.org now points to https://www.proofpoint.com/us/sendmail-open-source which seems to be a for profit company. And there seem to be no sendmail docs on that site. Are there still current sendmail docs online somewhere? I'm struggling to set up sendmail on my server to *send* only via smtp.office365.com 587 (STARTTLS). What is the easiest strategy to implement and/or the easiest guide to follow? Am I correct that for send only use of AUTH I don't need to issue or use certificates? Would be thankful for any advice. Anton From owner-freebsd-questions@freebsd.org Mon Jul 10 12:56:18 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F55BDA76DA for ; Mon, 10 Jul 2017 12:56:18 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C9D623D8B for ; Mon, 10 Jul 2017 12:56:17 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from zero-gravitas.local (unknown [85.199.232.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 2CC59CFDD for ; Mon, 10 Jul 2017 12:56:15 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/2CC59CFDD; dkim=none; dkim-atps=neutral Subject: Re: sendmail status and auth advice To: freebsd-questions@freebsd.org References: <201707101210.v6ACACeW010883@jail0199.vps.exonetric.net> From: Matthew Seaman Message-ID: Date: Mon, 10 Jul 2017 13:56:08 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <201707101210.v6ACACeW010883@jail0199.vps.exonetric.net> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="2pLlaKjwMCn6vVjhquxxKgSLpk1u2e0uM" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 12:56:18 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --2pLlaKjwMCn6vVjhquxxKgSLpk1u2e0uM Content-Type: multipart/mixed; boundary="871fuqxQ61tc7HpLGNnsjHapJoIUkUHVd"; protected-headers="v1" From: Matthew Seaman To: freebsd-questions@freebsd.org Message-ID: Subject: Re: sendmail status and auth advice References: <201707101210.v6ACACeW010883@jail0199.vps.exonetric.net> In-Reply-To: <201707101210.v6ACACeW010883@jail0199.vps.exonetric.net> --871fuqxQ61tc7HpLGNnsjHapJoIUkUHVd Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2017/07/10 13:10, Anton Shterenlikht wrote: > https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/SMTP-Auth.h= tml > points to > http://www.sendmail.org/~ca/email/auth.html > which is up to 8.13, last updated in 2006. > The version I have on FreeBSD 11.0-RELEASE-p9 is > sendmail+tls+sasl2-8.15.2_3. > So I'm worried the advice might not be up to date. > Is it? >=20 > Trying to find some sendmail docs online I realised > that sendmail.org now points to > https://www.proofpoint.com/us/sendmail-open-source > which seems to be a for profit company. > And there seem to be no sendmail docs on that site. >=20 > Are there still current sendmail docs online somewhere? >=20 > I'm struggling to set up sendmail on my server to *send* > only via smtp.office365.com 587 (STARTTLS). > What is the easiest strategy to implement and/or the > easiest guide to follow? >=20 > Am I correct that for send only use of AUTH I don't > need to issue or use certificates? >=20 > Would be thankful for any advice. >=20 Authentication setup in sendmail hasn't changed for quite some time, so the old docs you may find online are probably still relevant. One problem you'll find is that the vast majority of the stuff you'll find about sendmail authentication is talking about sendmail acting as the server end of the authentication, whereas you want it to behave as the client end. If I recall correctly that needs authinfo settings in /etc/mail/access, or (recommended) you need to add FEATURE(`authinfo') to your .mc file to create a dedicated file. I'd advise you to get hold of a copy of the O'Reilly Sendmail book -- that's a pretty comprehensive guide on everything you need to know about configuring sendmail. Another surprisingly useful guide is /usr/share/sendmail/cf/README -- it covers a remarkably large amount of stuff. If you are trying to configure sendmail to pretend to be a mail client and submit messages by port 587 then in general you don't need a local SSL certificate. Unless, of course, your service provider has configured things to require one, but office365 doesn't do that. However, normal sysadminly paranoia suggests that you definitely want STARTTLS to happen before sendmail tries to send any passwords around. I know it is possible to enforce that from the sendmail client end, but I've forgotten exactly how since I stopped using sendmail for anything significant mail-wize. Cheers, Matthew --871fuqxQ61tc7HpLGNnsjHapJoIUkUHVd-- --2pLlaKjwMCn6vVjhquxxKgSLpk1u2e0uM Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJZY3luXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnzw0P/2xn7REH4gRkpR1f/HoyzqEK GhcNjvDDOTFGrGxQ7CFIbLBbwOhBhNjAgfa2jD4nRVGzCZzGt0Xb3Hl2YeWAxf4M xecb8hm2wGIJnQMza02OLttMPE1J01CazsmjfAzW08fbpN1rGtaZ3Lkty9kIslW0 gdKKklSKHWiK664vo6cyKmS1tF6lfwcCoY9PmITptR54ElW+f/BNK6mpiyHO7tCT cGzQ7N2SLBYxX3+5m13i5ljuYQ/ka8/PlKN25/2APhhwZnsREQgZqr2DgpYL2uEV ISNwCFcaUqIcm+u+3VMs302XbEpxvKLVrgPn6gYQEAZrpGlZNmIlmTidjqnvxyTA +kO/x0CKB64y5ks6gObGBZxqyu4YytgQ2srFEEA30+BD4p6Anl8Vc+kr864Gcrey iTcaNPf4Anp3ohMlbjOnuTsolcjOyju9OD9MGM5y8zT/psgYzb4fB2o8E4i3K72y kJzL7AnZCLRfcFgO9s/ddNEcrRWodq+oeQIoLrJbPcrfvpuRiYsC8Hgf4yvfmg1y JGGDoQnIX+sKS5xknNNGNRALCXZMEOsg8YWbsRFa9F6L57ny/nUDcKh7v2H//7Yj RohYV5ncBI+yf7CQ95LllnokBk4IRYkphVHZA0UOPfjcvw2+Cof1o7VOyQN3lsLX 6Vi2OIXwbTm46kIn1MBB =tSbJ -----END PGP SIGNATURE----- --2pLlaKjwMCn6vVjhquxxKgSLpk1u2e0uM-- From owner-freebsd-questions@freebsd.org Mon Jul 10 15:26:26 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F2BD5DAAAB8 for ; Mon, 10 Jul 2017 15:26:26 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.20.71]) by mx1.freebsd.org (Postfix) with ESMTP id BD77068431 for ; Mon, 10 Jul 2017 15:26:26 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id 9C05FCB8CE7; Mon, 10 Jul 2017 10:26:25 -0500 (CDT) Received: from 128.135.52.6 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Mon, 10 Jul 2017 10:26:25 -0500 (CDT) Message-ID: <26749.128.135.52.6.1499700385.squirrel@cosmo.uchicago.edu> In-Reply-To: <20170710090547.15ee3afc07c09955ba621ae1@sohara.org> References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> <52627.76.193.16.95.1499645892.squirrel@cosmo.uchicago.edu> <20170710052228.GA2338@c720-r314251> <20170710090547.15ee3afc07c09955ba621ae1@sohara.org> Date: Mon, 10 Jul 2017 10:26:25 -0500 (CDT) Subject: Re: Unusual Question From: "Valeri Galtsev" To: "Steve O'Hara-Smith" Cc: freebsd-questions@freebsd.org Reply-To: galtsev@kicp.uchicago.edu User-Agent: SquirrelMail/1.4.8-5.el5.centos.7 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 15:26:27 -0000 On Mon, July 10, 2017 3:05 am, Steve O'Hara-Smith wrote: > On Mon, 10 Jul 2017 07:22:28 +0200 > Matthias Apitz wrote: > >> I do not think that this approach worked in the sense of overwriting all >> blocks of the disk. While walking through at some point the kernel will > > I see no reason why it shouldn't, provided the dd process doing the > work never needs to swap anything in (likely it's small and running a > tight loop). > >> miss sectors of the disk, for example of memory mapped files of shared >> libs of other running processes or swapped out memory to disk. And the > > The sectors are still there, just filled with 0s or random data the > kernel will have no trouble reading them. I believe, the kernel addresses swap not by addressing sectors on raw device covering the whole physical drive, but as "relative sectors" through swap partition device. If I'm right, once drive partition table is gone reading swap will fail and panic kernel. And even though dd has small footprint there maybe some process whose stuff was swapped out; and the kernel does keep switching between processes. Of course, clever person will kill everything. But the suggestion you made in another post: to make tiny bootable system with dd, boot off it, and then overwrite everything else is probably the only way to go in this remote situation. Which became obvious to all of us after someone - YOU - suggested it. THANKS! Valeri > >> kernel will just crash or halt and you will notice that as terminating > > The kernel will not crash or halt, processes will if they have to > page in corrupted data but that's all. Processes that don't page in > anything will just carry on running - if they don't read the disc they'll > never know it's been overwritten. > >> ssh session. > > Unless sshd has to page something in it won't crash. > >> Do not rely on the fact that the (sensitive) information on >> the disk was overwritten. > > I see no reason to expect that the dd process won't finish clearing > the disk and exit normally. > >> The only secure way is doing this from a system >> running on some other disk and even this would allow to recover >> information with forensic tools reading beside of the tracks. Only >> physical destruction will help, for example burning the thing, as you >> said. > > Sure, but absent a motive to spend the money forensic data analysis > costs writing 0s or random numbers over the whole drive will do fine. If > you fear forensic analysis then use thermite. > > -- > Steve O'Hara-Smith > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++ From owner-freebsd-questions@freebsd.org Mon Jul 10 15:34:08 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D73CDDAAEB8 for ; Mon, 10 Jul 2017 15:34:08 +0000 (UTC) (envelope-from 4250.10.freebsd-questions=freebsd.org@email-od.com) Received: from bca5.email-od.com (bca5.email-od.com [207.246.239.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ACB78689F8 for ; Mon, 10 Jul 2017 15:34:08 +0000 (UTC) (envelope-from 4250.10.freebsd-questions=freebsd.org@email-od.com) DKIM-Signature: v=1; a=rsa-sha256; d=email-od.com;i=@email-od.com;s=dkim; c=relaxed/relaxed; q=dns/txt; t=1499700840; x=1502292840; h=x-thread-info:date:from:to:cc:subject:message-id:in-reply-to:references:mime-version:content-type:content-transfer-encoding; bh=WK7PuBcKKS1qfxUodrPEpse+vd1xrl2dwTJS9JLxPI0=; b=LR/1GksmUTsoNXTuNqAPGU5hSrqWyFEv6WOxZdl40/XRVIy/SO2+YsMlKx0N2ec5jCIfgJnw+rGEklQ7OHpijWAUQ9vbCM7nvDurC07ZlOJsWdxVzIM7pHZh2RuVPxqvwOmPCUJQvQeiPeCxlTAY5X8BMTMxS0JoV6P83qMoP4A= X-Thread-Info: NDI1MC4xMi5kNzAwMDAwMDUzZDU1ZC5mcmVlYnNkLXF1ZXN0aW9ucz1mcmVlYnNkLm9yZw== Received: from r3.us-east.aws.in.socketlabs.com (r3.us-east.aws.in.socketlabs.com [54.165.229.15]) by bca2.email-od.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Mon, 10 Jul 2017 11:33:57 -0400 Received: from smtp.lan.sohara.org (EMTPY [89.127.62.20]) by r3.us-east.aws.in.socketlabs.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Mon, 10 Jul 2017 11:34:03 -0400 Received: from [192.168.63.1] (helo=steve.lan.sohara.org) by smtp.lan.sohara.org with smtp (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dUaiD-000C58-LM; Mon, 10 Jul 2017 15:35:01 +0000 Date: Mon, 10 Jul 2017 16:33:51 +0100 From: Steve O'Hara-Smith To: freebsd-questions@freebsd.org Cc: galtsev@kicp.uchicago.edu Subject: Re: Unusual Question Message-Id: <20170710163351.a347713b6d8f64e141d1d9f2@sohara.org> In-Reply-To: <26749.128.135.52.6.1499700385.squirrel@cosmo.uchicago.edu> References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> <52627.76.193.16.95.1499645892.squirrel@cosmo.uchicago.edu> <20170710052228.GA2338@c720-r314251> <20170710090547.15ee3afc07c09955ba621ae1@sohara.org> <26749.128.135.52.6.1499700385.squirrel@cosmo.uchicago.edu> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; amd64-portbld-freebsd10.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 15:34:08 -0000 On Mon, 10 Jul 2017 10:26:25 -0500 (CDT) "Valeri Galtsev" wrote: > I believe, the kernel addresses swap not by addressing sectors on raw > device covering the whole physical drive, but as "relative sectors" > through swap partition device. Sure, but I doubt it reads the partition table again after it has it read the first time, that's an obvious thing to cache. > If I'm right, once drive partition table is > gone reading swap will fail and panic kernel. I doubt it, the partition table should be cached in memory, otherwise yes that would panic the kernel, but reading the partition table every time a page needs swapping in would be stupidly inefficient so I don't believe it happens. > But the suggestion you made in another post: to make Not my suggestion, it's a sensible one but I don't think it's needed. -- Steve O'Hara-Smith | Directable Mirror Arrays C:>WIN | A better way to focus the sun The computer obeys and wins. | licences available see You lose and Bill collects. | http://www.sohara.org/ From owner-freebsd-questions@freebsd.org Mon Jul 10 15:34:23 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B2C7BDAAEEC for ; Mon, 10 Jul 2017 15:34:23 +0000 (UTC) (envelope-from as@cmplx.uk) Received: from jail0199.vps.exonetric.net (jail0199.vps.exonetric.net [IPv6:2a02:1658:1::199:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "jail0199.vps.exonetric.net", Issuer "jail0199.vps.exonetric.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5E56268A57 for ; Mon, 10 Jul 2017 15:34:23 +0000 (UTC) (envelope-from as@cmplx.uk) Received: from jail0199.vps.exonetric.net (jail0199.vps.exonetric.net [178.250.76.108]) by jail0199.vps.exonetric.net (8.15.2/8.15.2) with ESMTPS id v6AFYLX6021479 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 10 Jul 2017 15:34:21 GMT (envelope-from as@jail0199.vps.exonetric.net) Received: (from as@localhost) by jail0199.vps.exonetric.net (8.15.2/8.15.2/Submit) id v6AFYLeA021478 for freebsd-questions@freebsd.org; Mon, 10 Jul 2017 15:34:21 GMT (envelope-from as) Date: Mon, 10 Jul 2017 15:34:21 GMT From: Anton Shterenlikht Message-Id: <201707101534.v6AFYLeA021478@jail0199.vps.exonetric.net> To: freebsd-questions@freebsd.org Subject: SOLVED: WAS Re: sendmail status and auth advice In-Reply-To: <201707101210.v6ACACeW010883@jail0199.vps.exonetric.net> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 15:34:23 -0000 Matthew Seaman matthew at FreeBSD.org Mon Jul 10 12:56:18 UTC 2017 > >Authentication setup in sendmail hasn't changed for quite some time, so >the old docs you may find online are probably still relevant. One >problem you'll find is that the vast majority of the stuff you'll find >about sendmail authentication is talking about sendmail acting as the >server end of the authentication, whereas you want it to behave as the >client end. If I recall correctly that needs authinfo settings in >/etc/mail/access, or (recommended) you need to add FEATURE(`authinfo') >to your .mc file to create a dedicated file. Yes, "Using sendmail as a client with AUTH", http://www.sendmail.org/~ca/email/auth.html#authclientinfo has the required info, apart from: define(`RELAY_MAILER_ARGS', `TCP $h 587')dnl which is mentioned here: https://unix.stackexchange.com/questions/132711/using-port-587-with-sendmail >I'd advise you to get hold of a copy of the O'Reilly Sendmail book -- >that's a pretty comprehensive guide on everything you need to know about >configuring sendmail. I have this book in the library, in fact I ordered it, but... it's a complete monster to read. >Another surprisingly useful guide is >/usr/share/sendmail/cf/README -- it covers a remarkably large amount of >stuff. Agreed. For what I need, one can go straight to SMTP AUTHENTICATION section. >If you are trying to configure sendmail to pretend to be a mail client >and submit messages by port 587 then in general you don't need a local >SSL certificate. Unless, of course, your service provider has >configured things to require one, but office365 doesn't do that. Yes, this is indeed what I'm trying to do, which, as I found out is called "Using sendmail as a client with AUTH". >However, normal sysadminly paranoia suggests that you definitely want >STARTTLS to happen before sendmail tries to send any passwords around. >I know it is possible to enforce that from the sendmail client end, but >I've forgotten exactly how since I stopped using sendmail for anything >significant mail-wize. This I haven't figured out yet. Thanks Anton From owner-freebsd-questions@freebsd.org Mon Jul 10 15:36:24 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 67BDFDAB089 for ; Mon, 10 Jul 2017 15:36:24 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3243468BC9 for ; Mon, 10 Jul 2017 15:36:23 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [89.204.135.176] (helo=[10.148.186.176]) by ms-10.1blu.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from ) id 1dUajU-0006it-Ke for freebsd-questions@freebsd.org; Mon, 10 Jul 2017 17:36:20 +0200 From: Matthias Apitz To: Subject: Re: Unusual Question Date: Mon, 10 Jul 2017 17:36:19 +0200 User-Agent: Dekko/0.6.20; Qt/5.4.1; ubuntumirclient; Linux; MIME-Version: 1.0 Message-ID: <4eff21f6-84f2-4cc5-8b92-b7e787be8853@unixarea.de> In-Reply-To: <26749.128.135.52.6.1499700385.squirrel@cosmo.uchicago.edu> References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> <52627.76.193.16.95.1499645892.squirrel@cosmo.uchicago.edu> <20170710052228.GA2338@c720-r314251> <20170710090547.15ee3afc07c09955ba621ae1@sohara.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 89.204.135.176 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 15:36:24 -0000 The OP should just compile an own version of dd(1) which punches lets say=20 every thousand blocks the current block number to see how far (or better=20 how less) it will walk through before the kernel halts/crashes. matthias --=20 Sent from my Ubuntu phone http://www.unixarea.de/ From owner-freebsd-questions@freebsd.org Mon Jul 10 15:57:23 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB562DAB62B for ; Mon, 10 Jul 2017 15:57:23 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.20.71]) by mx1.freebsd.org (Postfix) with ESMTP id ABC156A620 for ; Mon, 10 Jul 2017 15:57:23 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id 867B7CB8CE7; Mon, 10 Jul 2017 10:57:22 -0500 (CDT) Received: from 128.135.52.6 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Mon, 10 Jul 2017 10:57:22 -0500 (CDT) Message-ID: <60058.128.135.52.6.1499702242.squirrel@cosmo.uchicago.edu> In-Reply-To: <20170710163351.a347713b6d8f64e141d1d9f2@sohara.org> References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> <52627.76.193.16.95.1499645892.squirrel@cosmo.uchicago.edu> <20170710052228.GA2338@c720-r314251> <20170710090547.15ee3afc07c09955ba621ae1@sohara.org> <26749.128.135.52.6.1499700385.squirrel@cosmo.uchicago.edu> <20170710163351.a347713b6d8f64e141d1d9f2@sohara.org> Date: Mon, 10 Jul 2017 10:57:22 -0500 (CDT) Subject: Re: Unusual Question From: "Valeri Galtsev" To: "Steve O'Hara-Smith" Cc: freebsd-questions@freebsd.org Reply-To: galtsev@kicp.uchicago.edu User-Agent: SquirrelMail/1.4.8-5.el5.centos.7 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 15:57:24 -0000 On Mon, July 10, 2017 10:33 am, Steve O'Hara-Smith wrote: > On Mon, 10 Jul 2017 10:26:25 -0500 (CDT) > "Valeri Galtsev" wrote: > >> I believe, the kernel addresses swap not by addressing sectors on raw >> device covering the whole physical drive, but as "relative sectors" >> through swap partition device. > > Sure, but I doubt it reads the partition table again after it has > it read the first time, that's an obvious thing to cache. > >> If I'm right, once drive partition table is >> gone reading swap will fail and panic kernel. > > I doubt it, the partition table should be cached in memory, > otherwise yes that would panic the kernel, but reading the partition table > every time a page needs swapping in would be stupidly inefficient so I > don't believe it happens. I agree, it will be inefficient if it were programmed that way... however, whenever I add partition with gpart, partition table gets re-read, and new device gets created. That is what probably confused me (as gpart may trigger kernel re-read partition table, whereas dd unlikely will). Valeri > >> But the suggestion you made in another post: to make > > Not my suggestion, it's a sensible one but I don't think it's > needed. > > -- > Steve O'Hara-Smith | Directable Mirror Arrays > C:>WIN | A better way to focus the > sun > The computer obeys and wins. | licences available see > You lose and Bill collects. | http://www.sohara.org/ > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++ From owner-freebsd-questions@freebsd.org Mon Jul 10 17:39:31 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92A1ADAD242 for ; Mon, 10 Jul 2017 17:39:31 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay14.qsc.de (mailrelay14.qsc.de [212.99.163.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0310670835 for ; Mon, 10 Jul 2017 17:39:30 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay14.qsc.de; Mon, 10 Jul 2017 19:39:01 +0200 Received: from r56.edvax.de (port-92-195-70-185.dynamic.qsc.de [92.195.70.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 37A833CBF9; Mon, 10 Jul 2017 19:39:00 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v6AHcxpu005099; Mon, 10 Jul 2017 19:38:59 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Mon, 10 Jul 2017 19:38:59 +0200 From: Polytropon To: Matthias Apitz Cc: Subject: Re: Unusual Question Message-Id: <20170710193859.3841a624.freebsd@edvax.de> In-Reply-To: <4eff21f6-84f2-4cc5-8b92-b7e787be8853@unixarea.de> References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> <52627.76.193.16.95.1499645892.squirrel@cosmo.uchicago.edu> <20170710052228.GA2338@c720-r314251> <20170710090547.15ee3afc07c09955ba621ae1@sohara.org> <4eff21f6-84f2-4cc5-8b92-b7e787be8853@unixarea.de> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay14.qsc.de with 81560683BF7 X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1187 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 17:39:31 -0000 On Mon, 10 Jul 2017 17:36:19 +0200, Matthias Apitz wrote: > The OP should just compile an own version of dd(1) which punches lets say > every thousand blocks the current block number to see how far (or better > how less) it will walk through before the kernel halts/crashes. To extend this idea: I'd add a few continuous diagnostic messages (comparable to the ^T status display), so when the SSH connection finally drops, it's possible to see how far the dd process went. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Mon Jul 10 19:18:26 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 129EFDAEF43 for ; Mon, 10 Jul 2017 19:18:26 +0000 (UTC) (envelope-from mj001@rogers.com) Received: from nm30-vm1.bullet.mail.gq1.yahoo.com (nm30-vm1.bullet.mail.gq1.yahoo.com [98.136.216.192]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DB65074930 for ; Mon, 10 Jul 2017 19:18:25 +0000 (UTC) (envelope-from mj001@rogers.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rogers.com; s=s2048; t=1499714192; bh=0+8+Cpbwn5NtIYGMjZDH8BT4Ve1AEE+/cRFn6sFH31I=; h=Subject:References:To:From:Date:In-Reply-To:From:Subject; b=FvHBEPKkV3qCyt3ISbh0MSae8ix1kOYtFfWcNPZml6JXVnlrtsx3Vipq1I1NyNAtoBYNig9m3Osin+k4w3F+hlvfs/ogHXFyVFQnsy+R/QqNcHkHvTCsE5+lDZZBu2LqazbdSY38fRdOosMBoA4IPF8Q5kJacKT5VFYhiDrCYvvtlXyLowtaGL4sKZhd5rmq5+Ky++tQCYcGTioceLtIF9YBW4lI3LZTKWULNh75hLqqBoAJbsDr8lUulqby1eSRLjja85dinlE41MykvqLwCmMgJDwcgFBqsR2YGjuX2Eb/VGRlsyHJJ5VCThCdEouNELPhk6W7rLFLo6lABgspbg== Received: from [216.39.60.183] by nm30.bullet.mail.gq1.yahoo.com with NNFMP; 10 Jul 2017 19:16:32 -0000 Received: from [208.71.42.207] by tm19.bullet.mail.gq1.yahoo.com with NNFMP; 10 Jul 2017 19:16:32 -0000 Received: from [127.0.0.1] by smtp218.mail.gq1.yahoo.com with NNFMP; 10 Jul 2017 19:16:32 -0000 X-Yahoo-Newman-Id: 639571.26100.bm@smtp218.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: qnJ9xqsVM1nWYpfUS4a9kBUNmLhApbWeUB84X9dEAmJrH6C keXtyZCp4zrZkcwQttjWPArH.ZqPMo9iKKOHoJjMXNwtHtUKyD4vbB9Z8s1n WQYXzcu.e7MtZ0GZsmzs9YjVD5etEeXhab3f94wl116GZl73gYphjNsZq3Op FmKKzPaPY3.PMtqosvYdRNjpzAWoItQuc1JDcjyz8NF30zm2.Llxzax24Rj. oeaoEPL2YlXUoWz.hAYDIQVkn748L8G1m9Ww5U6nEwVtsU263tYe2h6jzrkB fYqFPaoNlfuHPY5VMYAVBJ9Gur1tP7amj11uNTZlpnG.tDl5OUrP0WWngAms qhMlCWodAggy7AgbwPVC86qwPwZd29PRuIyPzb3BKMYiVlyDeP1J5tUtZ.vk 12JFB7iGhGjKQDKlDPqWaBB_EE41icv_lsqp3ZqqlEqLmBiIYiM.WYP5drZo A65txSaJqllAgwI2bhhT3xxPMrtuvMl9Grz1D933XZxixOOeXR0xMVwBDuMb vQExPjhqyClZ24.7YPIsAlgaN10xC.tJW5Izk1VsFIte_nHeG5q2xP3dGJ.0 - X-Yahoo-SMTP: TLQliKmswBBvVNxNe7d23d.rcRexF9Jldbuuisg- Subject: Fwd: Re: Unusual Question References: <156b5695-1cbf-c5fa-be49-ff52da58ba0f@rogers.com> To: "freebsd-questions@FreeBSD. ORG" From: Mike Jeays X-Forwarded-Message-Id: <156b5695-1cbf-c5fa-be49-ff52da58ba0f@rogers.com> Message-ID: Date: Mon, 10 Jul 2017 15:16:31 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <156b5695-1cbf-c5fa-be49-ff52da58ba0f@rogers.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 19:18:26 -0000 On 17-07-10 01:38 PM, Polytropon wrote: > On Mon, 10 Jul 2017 17:36:19 +0200, Matthias Apitz wrote: >> The OP should just compile an own version of dd(1) which punches lets say >> every thousand blocks the current block number to see how far (or better >> how less) it will walk through before the kernel halts/crashes. > To extend this idea: > > I'd add a few continuous diagnostic messages (comparable to > the ^T status display), so when the SSH connection finally > drops, it's possible to see how far the dd process went. :-) > > > dd can be made to report its status by sending the kill command USR1. See man dd. You could send one every minute via cron. From owner-freebsd-questions@freebsd.org Mon Jul 10 20:18:46 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EC077DB03A5 for ; Mon, 10 Jul 2017 20:18:46 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AE70B76CD7 for ; Mon, 10 Jul 2017 20:18:46 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [88.217.115.188] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from ) id 1dUf8l-0001Zd-55 for freebsd-questions@freebsd.org; Mon, 10 Jul 2017 22:18:43 +0200 Received: from localhost.my.domain (localhost [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id v6AKIgfJ002311 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 10 Jul 2017 22:18:42 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id v6AKIgv3002310 for freebsd-questions@freebsd.org; Mon, 10 Jul 2017 22:18:42 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Mon, 10 Jul 2017 22:18:42 +0200 From: Matthias Apitz To: freebsd-questions@freebsd.org Subject: Re: Fwd: Re: Unusual Question Message-ID: <20170710201842.GA2244@c720-r314251> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , freebsd-questions@freebsd.org References: <156b5695-1cbf-c5fa-be49-ff52da58ba0f@rogers.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="2oS5YaxWCcQjTEyO" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 12.0-CURRENT r314251 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. User-Agent: Mutt/1.8.0 (2017-02-23) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 88.217.115.188 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 20:18:47 -0000 --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable El d=C3=ADa lunes, julio 10, 2017 a las 03:16:31p. m. -0400, Mike Jeays esc= ribi=C3=B3: > On 17-07-10 01:38 PM, Polytropon wrote: >=20 > > On Mon, 10 Jul 2017 17:36:19 +0200, Matthias Apitz wrote: > >> The OP should just compile an own version of dd(1) which punches lets = say > >> every thousand blocks the current block number to see how far (or bett= er > >> how less) it will walk through before the kernel halts/crashes. > > To extend this idea: > > > > I'd add a few continuous diagnostic messages (comparable to > > the ^T status display), so when the SSH connection finally > > drops, it's possible to see how far the dd process went. :-) >=20 > dd can be made to report its status by sending the kill command USR1. >=20 > See man dd. You could send one every minute via cron. You can assume that I do know dd(1) and its man page. I just do not think that it will work on a system and kernel being overwritten with zeros, running somethings like cron jobs (as you suggest) or shell loops of sleep and kill pid. Adding a fprintf(stderr, ....) to the source of dd is better, don't you think so? matthias --=20 Matthias Apitz, =E2=9C=89 guru@unixarea.de, =E2=8C=82 http://www.unixarea.d= e/ =E2=98=8E +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub 8. Mai 1945: Wer nicht feiert hat den Krieg verloren. 8 de mayo de 1945: Quien no festeja perdi=C3=B3 la Guerra. May 8, 1945: Who does not celebrate lost the War. --2oS5YaxWCcQjTEyO Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEXmn7rBYYViyzy/vBR8z35Hb+nREFAllj4RkACgkQR8z35Hb+ nRGQRg//RyOqkpbFQKcuhHFniJqStRclb6nRsK8qcPeFnQ/SZa10k9H5/yP9ypVP jiXNnwXPvmcdXQ4lFJr4jT8PNm2CS5t4Rb8tTjyvpeUyZ2nbHt+7zjAJehtm8YO1 vUV1COFnmj7gMqFUhQslCQOXdhradOpq4M025UerxgOSBukpDpHp23eHxdT1iPS0 dOA7SZBQdBYasaspuoasHc5yH7JAQlxYj802EjFMc3Q5XRjbmK0v1C+vK4NbqpEw USbyOZv9tdT9TrOvCENEurrhWNFM3D9uGZ/PJWqu+XJpvJisEiqFeNM0OKmOLmy1 hgCzl8NXwqG6q0LKczuLYBBDrWu4e8hzYJ81Nixw8R7DMuzn6eUc6X+5zqv/PTeO ENJUGpCDlxus7swek5kU6wFoOvG0QirVEP1lL5/20EXdv9rrLSC4kY5JjOrp/vYO 1Jh48WnljH4Bsf3Q6T3GW0Z4EG3uC7T+6JyuPOABkS1MRhoXyfqWGh5FD3d/4aHB nvOS+fPK4d7TrDxh7rELsJWirtRdPAMrn3jrx451mkpoHfdAfrIv2oU+ndR3cnsm p1rJAtaJ6wFJQ6V7+hjZ6bkW2lFQw85FmsMIwGlu0IYm+vrU+7Libnj7RuLu/LEp Q532CaAJXByyaYvbvfX69JIQCW9vvX8zJbh8JeEPxJmhfKQqmH8= =Y8cT -----END PGP SIGNATURE----- --2oS5YaxWCcQjTEyO-- From owner-freebsd-questions@freebsd.org Mon Jul 10 22:14:48 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A620DDB1DCE for ; Mon, 10 Jul 2017 22:14:48 +0000 (UTC) (envelope-from markham@ssimicro.com) Received: from barracuda.ssimicro.com (barracuda.ssimicro.com [96.46.39.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.ssimicro.com", Issuer "RapidSSL SHA256 CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 618A479FF0 for ; Mon, 10 Jul 2017 22:14:47 +0000 (UTC) (envelope-from markham@ssimicro.com) X-ASG-Debug-ID: 1499724155-08e717138a1dc4e0001-jLrpzn Received: from mail.ssimicro.com (mail.ssimicro.com [64.247.129.10]) by barracuda.ssimicro.com with ESMTP id iB3d0EzFHZDWpauk (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 10 Jul 2017 18:02:35 -0400 (EDT) X-Barracuda-Envelope-From: markham@ssimicro.com X-Barracuda-Effective-Source-IP: mail.ssimicro.com[64.247.129.10] X-Barracuda-Apparent-Source-IP: 64.247.129.10 Received: from markham.ssimicro.com (markham.ssimicro.com [64.247.130.99]) (authenticated bits=0) by mail.ssimicro.com (8.15.2/8.15.2) with ESMTPSA id v6AM2Yvk081002 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Mon, 10 Jul 2017 16:02:34 -0600 (MDT) (envelope-from markham@ssimicro.com) Subject: Re: Fwd: Re: Unusual Question To: freebsd-questions@freebsd.org X-ASG-Orig-Subj: Re: Fwd: Re: Unusual Question References: <156b5695-1cbf-c5fa-be49-ff52da58ba0f@rogers.com> <20170710201842.GA2244@c720-r314251> From: markham breitbach Message-ID: <55309443-7e6a-0665-2040-8f21270d3d02@ssimicro.com> Date: Mon, 10 Jul 2017 16:02:22 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20170710201842.GA2244@c720-r314251> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GwRimriucMVWAwXoQoeo1LtN1RWlxvcxG" X-Barracuda-Connect: mail.ssimicro.com[64.247.129.10] X-Barracuda-Start-Time: 1499724155 X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384 X-Barracuda-URL: https://barracuda.ssimicro.com:443/cgi-mod/mark.cgi X-ASG-Orig-Subj: Re: Fwd: Re: Unusual Question X-Barracuda-Scan-Msg-Size: 10476 X-Virus-Scanned: by bsmtpd at ssimicro.com X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using per-user scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=5.0 tests=HTML_MESSAGE, HTML_OBFUSCATE_05_10 X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.40792 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.00 HTML_MESSAGE BODY: HTML included in message 0.00 HTML_OBFUSCATE_05_10 BODY: Message is 5% to 10% HTML obfuscation X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 22:14:48 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --GwRimriucMVWAwXoQoeo1LtN1RWlxvcxG Content-Type: multipart/mixed; boundary="ihbOoqXjFBU6HkAsKBUFcFBUlwGeo1Sf6"; protected-headers="v1" From: markham breitbach To: freebsd-questions@freebsd.org Message-ID: <55309443-7e6a-0665-2040-8f21270d3d02@ssimicro.com> Subject: Re: Fwd: Re: Unusual Question References: <156b5695-1cbf-c5fa-be49-ff52da58ba0f@rogers.com> <20170710201842.GA2244@c720-r314251> In-Reply-To: <20170710201842.GA2244@c720-r314251> --ihbOoqXjFBU6HkAsKBUFcFBUlwGeo1Sf6 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable In the past, I hijiacked /boot with mfsbsd which loaded into a RAM disk, making the HDD available for whatever shennanigans I needed. This was about 5 years ago, so my memory is a bit fuzzy on the details, but I do remember heavily testing that on the bench before deploying it, as you only get one shot at something like that :) (same case, remote, unmanned sites, cost $$$K to get someone on-site) =46rom my old notes, this is exactly what we did, and since you are running entirely from RAM disk, you aren't worried about trashing your kernel or /dev. I used it to re-partition and upgrade the remotes, but if all you need to do is nuke 'em you should be fine. The build process requires you to provide the rc.conf from the target machine: * build mfsbsd image and install to remote (Your target PD). make clean make tar BASE=3D/cdrom/8.1-RELEASE mv mfsbsd-8.1-RELEASE-p8-i386.tar /tmp/target-mfs81.tar *STOP! At this point it's best to verify your image is configured properly. If you install a misconfigured image on your target there is NO way to fix it remotely.* Something simple as forgetting to make clean can bugger up the whole process since the old configs from a prior build will remain in the tmp directory. ssh root@target scp root@myhost:/tmp/target-mfs81.tar /tmp mv /boot /boot.old tar -x -C / -f /tmp/target-mfs81.tar * cross fingers * Verify HDD device node by looking at output from "mount" (should be ad2). * reboot * login (password is mfsroot) Installation[edit ] * Nuke that sucker! dd if=3D/dev/zero of=3D/dev/ad2 bs=3D1k count=3D1 gpart create -s gpt /dev/ad2 =2E.. http://mfsbsd.vx.sk/ That might give you a good starting point though. -Markham --ihbOoqXjFBU6HkAsKBUFcFBUlwGeo1Sf6-- --GwRimriucMVWAwXoQoeo1LtN1RWlxvcxG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iEYEARECAAYFAllj+XoACgkQKQ+fauj+jf6rXACgjJbQKIbJYSpmDTvNgibb3gRO Ss0AoITVshsI6rVV+EbU88ikrRGURJq4 =r5t3 -----END PGP SIGNATURE----- --GwRimriucMVWAwXoQoeo1LtN1RWlxvcxG-- From owner-freebsd-questions@freebsd.org Mon Jul 10 22:58:59 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CB3E5DB2BA7 for ; Mon, 10 Jul 2017 22:58:59 +0000 (UTC) (envelope-from thierry.presentation@gmail.com) Received: from smtp.smtpout.orange.fr (smtp09.smtpout.orange.fr [80.12.242.131]) by mx1.freebsd.org (Postfix) with ESMTP id 493737B348 for ; Mon, 10 Jul 2017 22:58:58 +0000 (UTC) (envelope-from thierry.presentation@gmail.com) Received: from localhost ([80.12.38.91]) by mwinf5d85 with ME id jArK1v0031xzjNw03ArKWG; Tue, 11 Jul 2017 00:51:20 +0200 X-ME-Helo: localhost X-ME-Date: Tue, 11 Jul 2017 00:51:20 +0200 X-ME-IP: 80.12.38.91 Date: Mon, 10 Jul 2017 22:51:17 +0000 To: freebsd-questions@freebsd.org From: Thierry PRESENTATION Reply-To: thierry.presentation@gmail.com Subject: tel : 01 76 24 30 81 Message-ID: X-Priority: 3 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 22:58:59 -0000 From owner-freebsd-questions@freebsd.org Tue Jul 11 17:33:15 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 94DFEDA7ABE for ; Tue, 11 Jul 2017 17:33:15 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from queue01a.mail.zen.net.uk (queue01a.mail.zen.net.uk [212.23.3.234]) by mx1.freebsd.org (Postfix) with ESMTP id 4F1317EB0D for ; Tue, 11 Jul 2017 17:33:14 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from [212.23.1.22] (helo=smarthost03c.mail.zen.net.uk) by queue01a.mail.zen.net.uk with esmtp (Exim 4.72) (envelope-from ) id 1dUydD-0006NV-Qr for freebsd-questions@freebsd.org; Tue, 11 Jul 2017 17:07:27 +0000 Received: from [82.71.56.121] (helo=curlew.milibyte.co.uk) by smarthost03c.mail.zen.net.uk with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1dUyd6-0006QQ-Oy for freebsd-questions@freebsd.org; Tue, 11 Jul 2017 17:07:20 +0000 Received: from [192.168.1.13] (helo=curlew) by curlew.milibyte.co.uk with esmtp (Exim 4.89) (envelope-from ) id 1dUyeM-000164-Vg for freebsd-questions@freebsd.org; Tue, 11 Jul 2017 18:08:39 +0100 Date: Tue, 11 Jul 2017 18:08:38 +0100 From: Mike Clarke To: freebsd-questions@freebsd.org Message-ID: <20170711180838.1b9f6539@curlew> In-Reply-To: References: <20170707120936.620323e3@curlew> X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.31; amd64-portbld-freebsd11.0) MIME-Version: 1.0 X-SA-Exim-Connect-IP: 192.168.1.13 X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on curlew.lan X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 Subject: Re: How to fix wx error ? Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on curlew.milibyte.co.uk) X-Originating-smarthost03c-IP: [82.71.56.121] Feedback-ID: 82.71.56.121 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2017 17:33:15 -0000 On Fri, 7 Jul 2017 13:37:34 -0700 "Jack L." wrote: > do a clean checkout of /usr/ports/audio/audacity then > patch -EB '' -p1 < thepatch Thanks, that fixed my problem. -- Mike Clarke From owner-freebsd-questions@freebsd.org Tue Jul 11 22:46:09 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5856FDAD635 for ; Tue, 11 Jul 2017 22:46:09 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay14.qsc.de (mailrelay14.qsc.de [212.99.163.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B03276EE69 for ; Tue, 11 Jul 2017 22:46:07 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay14.qsc.de; Wed, 12 Jul 2017 00:45:58 +0200 Received: from r56.edvax.de (port-92-195-70-185.dynamic.qsc.de [92.195.70.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id BA4513CC3F; Wed, 12 Jul 2017 00:45:57 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v6BMjuHe003201; Wed, 12 Jul 2017 00:45:56 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Wed, 12 Jul 2017 00:45:56 +0200 From: Polytropon To: Shane Ambler Cc: B J , freebsd-questions Subject: Re: FreeBSD Equivalent To Adobe Acrobat Message-Id: <20170712004556.72dc63d5.freebsd@edvax.de> In-Reply-To: <42f8fa2c-a931-0323-203b-8e80494daa8b@ShaneWare.Biz> References: <42f8fa2c-a931-0323-203b-8e80494daa8b@ShaneWare.Biz> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay14.qsc.de with 3D286683787 X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1224 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2017 22:46:09 -0000 On Thu, 6 Jul 2017 12:57:02 +0930, Shane Ambler wrote: > On 04/07/2017 10:02, B J wrote: > > > I tried several and those you mentioned might have been among them. > > None of them appeared to fill in blanks, assuming, of course, I did > > things right in the first place. For each one, I would get a message, > > embedded in the file I was looking at, which said something about me > > having to use Acrobat. > > Could depend on the specific pdf file, pdfs can have some adobe only > features such as XFA and javascript, as these aren't part of the > official spec I expect they aren't supported in free software. At least XFA seems to be supported by Okular, but normal forms (text input fields) are supported by Evince and Okular; gv and xpdf do not support them, but usually can read and print the forms (with blank fields of course). So the "Acrobat Reader" or whatever it is called this year is not really needed anymore, except you get really non-standard PDF files that require special proprietary commercial software. I haven't tried to get the "Windows" version of the mentioned reader running with wine, maybe that is possible for such kinds of "worst case PDF file"... ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Tue Jul 11 23:49:32 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0BEDDDAE4BF for ; Tue, 11 Jul 2017 23:49:32 +0000 (UTC) (envelope-from doug@fledge.watson.org) Received: from cyrus.watson.org (cyrus.watson.org [198.74.231.69]) by mx1.freebsd.org (Postfix) with ESMTP id BB8EA70436 for ; Tue, 11 Jul 2017 23:49:31 +0000 (UTC) (envelope-from doug@fledge.watson.org) Received: from fledge.watson.org (fledge.watson.org [198.74.231.63]) by cyrus.watson.org (Postfix) with ESMTPS id 0861D46B94 for ; Tue, 11 Jul 2017 19:49:31 -0400 (EDT) Received: from fledge.watson.org (doug@localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.15.2/8.15.2) with ESMTP id v6BNnUnG096303 for ; Tue, 11 Jul 2017 19:49:30 -0400 (EDT) (envelope-from doug@fledge.watson.org) Received: from localhost (doug@localhost) by fledge.watson.org (8.15.2/8.15.2/Submit) with ESMTP id v6BNnUht096300 for ; Tue, 11 Jul 2017 19:49:30 -0400 (EDT) (envelope-from doug@fledge.watson.org) Date: Tue, 11 Jul 2017 12:52:34 -0400 (EDT) From: doug Reply-To: doug@safeport.com To: Matthew Seaman Subject: Re: FreeBSD did it again (still) In-Reply-To: <9c9b2c25-e65d-3489-e483-d99c2e746e56@FreeBSD.org> Message-ID: References: <27b3c757-1f00-a033-03f6-303a82ab65f2@columbus.rr.com> <3ce31ee2-5e35-d31c-71ca-dc95ece2dd61@intersonic.se> <020431a6-1a7d-d80e-0725-585c21f3ef27@columbus.rr.com> <563b14d5-ebfb-62b6-28ac-3ebbd663d067@intersonic.se> <8c1bb853-5eb0-4fae-ee26-5ff4684c2b3a@saunalahti.fi> <1499345128.3276.2.camel@gmail.com> <3cbeca30-8801-d800-edcb-f64ea2f079e0@columbus.rr.com> <9c9b2c25-e65d-3489-e483-d99c2e746e56@FreeBSD.org> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed ReSent-Date: Tue, 11 Jul 2017 19:48:42 -0400 (EDT) ReSent-From: doug ReSent-To: freebsd-questions@FreeBSD.ORG ReSent-Subject: Re: FreeBSD did it again (still) ReSent-Message-ID: ReSent-User-Agent: Alpine 2.20 (BSF 67 2015-01-07) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (fledge.watson.org [127.0.0.1]); Tue, 11 Jul 2017 19:49:30 -0400 (EDT) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2017 23:49:32 -0000 On Thu, 6 Jul 2017, Matthew Seaman wrote: > On 2017/07/06 14:46, Warren Block wrote: >> On Thu, 6 Jul 2017, Baho Utot wrote: >> >>> Well FYI the upgrade base 10.1 to 11.0-p10 when as expected. Update >>> the ports to the current quarterly was a tragic happening. I have >>> done this before upgrade a desktop from 10.3 to 11.0-p0 then to >>> 11.0-p9. Again the ports just did not work as it resulted in a broken >>> desktop each time. I started using the quarterly ports branch >>> thinking I get some stablilty. No stability to be found. Should I >>> user be able to update without going thru a weeks worth of debugging? >>> I think that is not too much to ask. >> >> It might or might not be obvious, but after going from FreeBSD 10 to 11 >> all ports must be reinstalled. It is not possible to upgrade only some >> ports without mysterious breakages. > > pkg(8) is actually smart enough to realise that the ABI-version of the > installed packages doesn't match either the ABI-version of the running > kernel[*] or the ABI-version of the repository and it /should/ attempt > to update or reinstall all installed packages to fix that. > > Much of the time that will "just work" -- but not always, which is why > the standard advice is still to delete and reinstall all packages on a > major version upgrade. Working out when and why pkg(8) can fail to do > this correctly and teaching it how to get it right would be a really > useful contribution. > One thing I did not see highlighted in this thread was, it's a laptop. As this is the world I live in, I feel the need to say things ain't that bad. Things would be much better if more Xorg and www ports developers ran FreeBSD workstations. There is a reason that few companies pay anyone to port the wifi and graphics drivers to FreeBSD. I am told many of these were likely developed on FreeBSD because of superior debugging tools. In the current world things are pretty good to great, if you do the following: don't live on the FreeBSD edge unless you are willing to and can help find bugs; make sure your graphics card is supported before buying (for me wifi would be a plus); and lastly, if you do not want to occasionally have to do some serious back-tracking install Xorg, Mozilla stuff and your windowing preference (xfce for me) on a 'clean' system. In that order. So on 10.3, soon to be 10.4 life is good to great. pkg is a monumental improvement and if you are not gaming a $700 laptop will outperform a lot more expensive stuff running Mac or Windows. Will a small hicup with firefox I added libreoff and gimp to a working system. I did test this path on a laptop that I hosed trying to upgrade something in xfce. My experiences; YMMV :) From owner-freebsd-questions@freebsd.org Wed Jul 12 01:22:41 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 48E33DAFEFB for ; Wed, 12 Jul 2017 01:22:41 +0000 (UTC) (envelope-from xxjack12xx@gmail.com) Received: from mail-wr0-x230.google.com (mail-wr0-x230.google.com [IPv6:2a00:1450:400c:c0c::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CEC0E7307E for ; Wed, 12 Jul 2017 01:22:40 +0000 (UTC) (envelope-from xxjack12xx@gmail.com) Received: by mail-wr0-x230.google.com with SMTP id k67so12235516wrc.2 for ; Tue, 11 Jul 2017 18:22:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tVuPwnUYQ0Do2+7+/IOA1cd3CkDyRuMSbjnPWWtbN8Q=; b=AZJyM0Pb5Xc15oOA5rDO7qkTQOozorojKp1MSz/a50D+8VFuGCwwE+s/Akj2RFiMSy R0lZUC1g64Nz8KGTguLDn5zzUuKhHIQ+iNual3tew8NRo3emC0TlVfy8pchYC3uXnluf /DSRjT/x9dE9CGTfKZ2xKeVxYArJQpNtZ+GCSUoBiA+5EsxIuMNAP6VfrkFH6agqr8IJ oXhYrhG8HuGfxmcvxuhawnNVbVxDJgg0p5QZag+xqmfobk2DGynIAd8v0zZ0xa0J16a8 xKcQ37VrjRprLVtIPEfRGkk3Bzsq5sSoN8M/cFcvWF3NBBm2DsBJl+IRNCtJrkyyM97T uFTA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=tVuPwnUYQ0Do2+7+/IOA1cd3CkDyRuMSbjnPWWtbN8Q=; b=hDIUZZ/H9e3ji+OIYAAGE8sUTNPOw3QskyMJ/OKIb6Us+ntSPnG39HVMvShSb9bZn0 fyk3W6C+/k6TtI7E18sA0oB6nlL9uC/6vNKzUkSnFGPvogTEl1+kfskLD/1dYalvc0Hv NUlk8w+RoDFnSr5ZTFwAzF2xu+dfpASLw6CFN4DELXhSMJF+jCBUWIwgG0yUpILmgySs uU2E9t4tcO9ko8XhmYWQccIK+2PFRDdjqRemSVB0bU4naSsrq5+kQ+TjzJS/Au73S9hp is5c45wajBjs4QB4hIhPtsgHTE3mEAPTVQPqDWoPE/47iyzr8TK7+7uiWp+4PmKf8LD1 BWog== X-Gm-Message-State: AIVw113XH1HLQs/8O97x70+A+nJqAyR9+5uByazFGCghNZClzPz0Y+nN UEgZixlJfIyjDtWnpbKDB1I39rTnUw== X-Received: by 10.28.134.144 with SMTP id i138mr607232wmd.27.1499822558647; Tue, 11 Jul 2017 18:22:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.176.241 with HTTP; Tue, 11 Jul 2017 18:21:58 -0700 (PDT) In-Reply-To: <20170711180838.1b9f6539@curlew> References: <20170707120936.620323e3@curlew> <20170711180838.1b9f6539@curlew> From: "Jack L." Date: Tue, 11 Jul 2017 18:21:58 -0700 Message-ID: Subject: Re: How to fix wx error ? To: Mike Clarke Cc: "freebsd-questions@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2017 01:22:41 -0000 Great! Hopefully that patch will be applied to the ports tree before 11.1 release On Tue, Jul 11, 2017 at 10:08 AM, Mike Clarke wrote: > On Fri, 7 Jul 2017 13:37:34 -0700 > "Jack L." wrote: > >> do a clean checkout of /usr/ports/audio/audacity then >> patch -EB '' -p1 < thepatch > > Thanks, that fixed my problem. > > -- > Mike Clarke > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" From owner-freebsd-questions@freebsd.org Wed Jul 12 08:54:04 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 104FBD918A3 for ; Wed, 12 Jul 2017 08:54:04 +0000 (UTC) (envelope-from srs0=flhm=6p=mail.sermon-archive.info=doug@sermon-archive.info) Received: from mail.sermon-archive.info (sermon-archive.info [71.177.216.148]) by mx1.freebsd.org (Postfix) with ESMTP id DFF4F7FA50 for ; Wed, 12 Jul 2017 08:54:03 +0000 (UTC) (envelope-from srs0=flhm=6p=mail.sermon-archive.info=doug@sermon-archive.info) Received: from [10.0.1.251] (mini [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 3x6t6D3Wp5z2fk5S for ; Wed, 12 Jul 2017 01:53:56 -0700 (PDT) From: Doug Hardie Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Unusual Question Date: Wed, 12 Jul 2017 01:53:56 -0700 References: <20170709230708.M27871@sola.nimnet.asn.au> To: "freebsd-questions@freebsd.org Questions" In-Reply-To: <20170709230708.M27871@sola.nimnet.asn.au> Message-Id: X-Mailer: Apple Mail (2.3273) X-Virus-Scanned: clamav-milter 0.99.2 at mail X-Virus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2017 08:54:04 -0000 > On 9 July 2017, at 06:14, Ian Smith wrote: >=20 > In freebsd-questions Digest, Vol 683, Issue 8, Message: 1 > On Sun, 9 Jul 2017 02:57:14 -0700 Doug Hardie = wrote: >=20 >> I have a FreeBSD 9.3 remote server that needs to be purged. I know=20= >> that rm -rf / will remove all the directory entries, but I need to=20 >> write over the drive. I thought that dd if=3D/dev/zero of=3D/dev/ada0=20= >> might do the trick, but it gives an not permitted error. The whole=20= >> thing can crash and burn at the end. This is an unmanned site so=20 >> moving drives is not viable. >=20 > # sysctl kern.geom.debugflags=3D16 >=20 > purge at will. if=3D/dev/random for the more paranoid :) >=20 > cheers, Ian Today was the experimentation. I had an old system here at the house = with 8.2 on it. So I started with a dd in=3D/dev/ada0 out=3D/dev/null = to find out how many blocks were on the device. Once I had that number, = I then ran dd if=3D/dev/random of=3D/dev/ada0 skip=3D. I typed oskip, but somehow the o didn't make it through = the keyboard. When it finished, I realized the error. So I had an install memstick for 11.0 and put it on as I wanted to try = camcontrol sanitize. Unfortunately, it reports an error accessing my = drive. I then used dd if=3D/dev/ada0 skip=3D | od = -c. Then I wrote down the first few bytes of the output. They were = non-zero. I was a bit surprised by that since the last partition is = swap and it was never used. But perhaps that was left over from the = random write. =46rom here on I have pictures of the output. This is a = dumb terminal and I will attempt to enter in the data since the list = doesn't accept attachments. dd if=3D/dev/zero of=3D/dev/ada0 bs=3D32k dd: /dev/ada0: short write on character device dd: /dev/ada0: end of device 2442211+0 records in 2442210+1 records out nnnn bytes transferred..... ls -l pwd /bin/pwd: Exec format error. Binary file not executable. who /usr/bin/who: Exec format error. Binary file not executable. dd if=3D/dev/ada0 skip=3D1000 count=3D5 | od -c 0000000 \0 \0 \0 \0 ... * 0005000 5+0 records in 5+0 records out dd if=3D/dev/ada0 skip=3D10000 count=3D500 | od -c 0000000 \0 \0 \0 \0 ... * 0764000 500+0 records in 500+0 records out nnnn bytes transferred... I didn't capture this but I did run the dd with the oskip of the big = number and it showed all zeros. I believe that dd, od and some of the current directory blocks were = still remaining in memory. However, the drive was definitely zapped. = It did write to the end of the drive. However, I suspect that if = something else was running during the dd and it tried to access the = drive things could have come to a halt before the zap completed. At = this point I tried to do a shutdown command and got the same Exec format = error. However, hitting the reset switch did cause a shutdown. It = seemed to be a normal shutdown as there were messages on the console, = but I was not expecting it to work and only saw them for a brief second = before the display was shut off. I would like to have tried camcontrol sanitize as that appears to be = handled completely in the drive and controller. It would complete = regardless of what happened to the OS. I couldn't use it anyway on the = production systems as they are only at 8.3 and the sanitize command was = added in 11.0. Net result: I am not sure if the first production drive actually = completed the zap. It might have, but there is no way to tell. = However, it was not important as it does not hold any sensitive data. = It was tried first to see what would happen. I will make sure nothing = is running but sshd and dd when I do it on the critical systems. I am = considering starting the dd with a nohup and then killing sshd before it = gets very far. I think that has the best possibility of completing = properly. From owner-freebsd-questions@freebsd.org Wed Jul 12 09:05:02 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4AEBBD91F46 for ; Wed, 12 Jul 2017 09:05:02 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-oln040092002104.outbound.protection.outlook.com [40.92.2.104]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DEEE180111 for ; Wed, 12 Jul 2017 09:05:01 +0000 (UTC) (envelope-from carmel_ny@outlook.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=WGQArqS/LUP26GIeltM30eHQJxmRrith74EsfUzZR1A=; b=Jkk0dQuCyVtPltYlj/dJ3cjswy/C2zZ5GAYJm4vldKOLdEhEi/rEXWbFd0kJiG4TsZLHURX++oQlWhqYQg6BTEwZV8gRoItF5xtE2GUyb5TUMnk5h3ytYk5F8oDWtJtlnNx7Hhh3LQO01unDO3qSfbwS0KRcZTX1gfMaayKwEppLbSxD2jOUgM9DVdQ3OPRjYdkd+7+q0lEistwZ9SPkKbW9vESHBn2PmeHj4l+J2MFexfjQNHAZjzyXmG5XnZ01Kl0B8lM8EBgesQ683Vc6xVgJ+Fepb35DfFRxelloqrW/RuFF4VP0zb//VTQNeHPSZdyQWrjhJGRHNg21w+27OQ== Received: from BY2NAM01FT061.eop-nam01.prod.protection.outlook.com (10.152.68.55) by BY2NAM01HT159.eop-nam01.prod.protection.outlook.com (10.152.69.54) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1240.9; Wed, 12 Jul 2017 09:04:59 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com (10.152.68.57) by BY2NAM01FT061.mail.protection.outlook.com (10.152.68.251) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1240.9 via Frontend Transport; Wed, 12 Jul 2017 09:04:59 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com ([10.172.31.146]) by BN6PR2001MB1730.namprd20.prod.outlook.com ([10.172.31.146]) with mapi id 15.01.1261.015; Wed, 12 Jul 2017 09:04:59 +0000 From: Carmel NY To: FreeBSD Subject: Re: FreeBSD Equivalent To Adobe Acrobat Thread-Topic: FreeBSD Equivalent To Adobe Acrobat Thread-Index: AQHS+u3wKGXqiNb6Z0itX1Nzde8HBQ== Date: Wed, 12 Jul 2017 09:04:59 +0000 Message-ID: References: <42f8fa2c-a931-0323-203b-8e80494daa8b@ShaneWare.Biz> <20170712004556.72dc63d5.freebsd@edvax.de> In-Reply-To: <20170712004556.72dc63d5.freebsd@edvax.de> Reply-To: FreeBSD Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: freebsd.org; dkim=none (message not signed) header.d=none;freebsd.org; dmarc=none action=none header.from=outlook.com; x-incomingtopheadermarker: OriginalChecksum:1815CC7BD9848277DAC8DDA4FB01509EE9F61539A9BC09D65D036B6C12FEAB3A; UpperCasedChecksum:6764F8C26F97A82141D6A0F074C9CB776DC4820DCF0F225C498C09B1F705ED31; SizeAsReceived:7476; Count:46 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [5CD3HQqJ0m0VFgJHOU2VEtUzZKDaK6ZF] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; BY2NAM01HT159; 7:4Uqe4MMdaPFyuwgX5a2JcWGzVUWDFsLNOBAI/iYqbakKiEB8WCYZOD44MWsPS9xjyyb843ZKVwfA7fxQllxL5fJKgVzNOz7IhMb2k4MpfHT3Mz/0csVjM8JjEn9Ccg/kCE1IoRK+/uGOhGsYXn5ZOyJ84bWfQOkq/isIMzvO5sq1Sfzkl9mTLbeEaOdAqgQtl7OFZBSuWiLXxZmStGb3ZHLnkzu0/0WjGeuEKTlMzh6P2KLNpI9l+UmMo2M6H0L4MY32Syrw+xE9kRyWI71Xud9bZB+PE73i99IN9DSk2A/SLRGiIU6YG5yBBHxXDPhrXlrz/PUvUrHRIpo+nu41bGUzgWgy311a27rxpspVPgYFuhUzKJzrlXya/EFvCytDKfV3nM6epBDDvBBXQpmhJNj4JIX8CDaD4El6ivYGOGWFbKOvPEPH7ngjfTriUe5yvj75t7QLWwMbJA3NYv6pZP9tnVjUbT8Dvf5ubJ4Su/m0pKFD6fdMnNAlIillJwQ3G3Os+bOAozfqmH7K1m5CZjZUIjUnVvsJOPB0GcwiUPnuqmkNKf5VhfOODfn5SlvxzuTAjBJsfqwCIpbIq4Fmuqzo8CbAtL23PTMbsCDc2PkPYf3OHnyW9wWEl98cK5CMGG352x5kwNBawyKkoXVrgBvzgWx3Ar+NZJll/x2LE9lMPCgvUgBNEI5uUzitKEM8WcrOKb4JcY4yBJWGCzjE3kky4lZcjAdJxFfsUoyaXA9lzJSYB30Mj4UE8s1mbuX/NUQjp0Zgu0ax8pPxUxutWw== x-incomingheadercount: 46 x-eopattributedmessage: 0 x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:BY2NAM01HT159; H:BN6PR2001MB1730.namprd20.prod.outlook.com; FPR:; SPF:None; LANG:en; x-ms-office365-filtering-correlation-id: f5937264-d65e-49f2-8224-08d4c9051213 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(300000503095)(300135400095)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:BY2NAM01HT159; x-ms-traffictypediagnostic: BY2NAM01HT159: x-exchange-antispam-report-test: UriScan:(125551606395959)(278178393323532)(20558992708506)(133145235818549)(209352067349851)(236129657087228)(225559137633274)(247924648384137); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031); SRVR:BY2NAM01HT159; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BY2NAM01HT159; x-forefront-prvs: 036614DD9C spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="utf-8" Content-ID: <3181C0C60ADB9B478DC50D223017B0C5@namprd20.prod.outlook.com> Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jul 2017 09:04:59.7724 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2NAM01HT159 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2017 09:05:02 -0000 T24gV2VkLCAxMiBKdWwgMjAxNyAwMDo0NTo1NiArMDIwMCwgUG9seXRyb3BvbiBzdGF0ZWQ6DQoN Cj5PbiBUaHUsIDYgSnVsIDIwMTcgMTI6NTc6MDIgKzA5MzAsIFNoYW5lIEFtYmxlciB3cm90ZToN Cj4+IE9uIDA0LzA3LzIwMTcgMTA6MDIsIEIgSiB3cm90ZToNCj4+ICAgDQo+PiA+IEkgdHJpZWQg c2V2ZXJhbCBhbmQgdGhvc2UgeW91IG1lbnRpb25lZCBtaWdodCBoYXZlIGJlZW4gYW1vbmcgdGhl bS4NCj4+ID4gTm9uZSBvZiB0aGVtIGFwcGVhcmVkIHRvIGZpbGwgaW4gYmxhbmtzLCBhc3N1bWlu Zywgb2YgY291cnNlLCBJIGRpZA0KPj4gPiB0aGluZ3MgcmlnaHQgaW4gdGhlIGZpcnN0IHBsYWNl LiAgRm9yIGVhY2ggb25lLCBJIHdvdWxkIGdldCBhDQo+PiA+IG1lc3NhZ2UsIGVtYmVkZGVkIGlu IHRoZSBmaWxlIEkgd2FzIGxvb2tpbmcgYXQsIHdoaWNoIHNhaWQNCj4+ID4gc29tZXRoaW5nIGFi b3V0IG1lIGhhdmluZyB0byB1c2UgQWNyb2JhdC4gIA0KPj4gDQo+PiBDb3VsZCBkZXBlbmQgb24g dGhlIHNwZWNpZmljIHBkZiBmaWxlLCBwZGZzIGNhbiBoYXZlIHNvbWUgYWRvYmUgb25seSANCj4+ IGZlYXR1cmVzIHN1Y2ggYXMgWEZBIGFuZCBqYXZhc2NyaXB0LCBhcyB0aGVzZSBhcmVuJ3QgcGFy dCBvZiB0aGUgDQo+PiBvZmZpY2lhbCBzcGVjIEkgZXhwZWN0IHRoZXkgYXJlbid0IHN1cHBvcnRl ZCBpbiBmcmVlIHNvZnR3YXJlLiAgDQo+DQo+QXQgbGVhc3QgWEZBIHNlZW1zIHRvIGJlIHN1cHBv cnRlZCBieSBPa3VsYXIsIGJ1dCBub3JtYWwgZm9ybXMNCj4odGV4dCBpbnB1dCBmaWVsZHMpIGFy ZSBzdXBwb3J0ZWQgYnkgRXZpbmNlIGFuZCBPa3VsYXI7IGd2IGFuZA0KPnhwZGYgZG8gbm90IHN1 cHBvcnQgdGhlbSwgYnV0IHVzdWFsbHkgY2FuIHJlYWQgYW5kIHByaW50IHRoZQ0KPmZvcm1zICh3 aXRoIGJsYW5rIGZpZWxkcyBvZiBjb3Vyc2UpLg0KDQpUaGUgT1Agd2FudGVkIHRoZSBhYmlsaXR5 IHRvIGVkaXQ7IGluIGhpcyBjYXNlICJmaWxsIGluIHRoZSBibGFua3MsIGluDQphIFBERiBkb2N1 bWVudC4gSG93IGRvZXMgcHJpbnRpbmcgYSBkb2N1bWVudCB3aXRoIGJsYW5rcyBhY2hpZXZlIHRo aXMNCmdvYWw/DQoNCj5TbyB0aGUgIkFjcm9iYXQgUmVhZGVyIiBvciB3aGF0ZXZlciBpdCBpcyBj YWxsZWQgdGhpcyB5ZWFyIGlzDQo+bm90IHJlYWxseSBuZWVkZWQgYW55bW9yZSwgZXhjZXB0IHlv dSBnZXQgcmVhbGx5IG5vbi1zdGFuZGFyZA0KPlBERiBmaWxlcyB0aGF0IHJlcXVpcmUgc3BlY2lh bCBwcm9wcmlldGFyeSBjb21tZXJjaWFsIHNvZnR3YXJlLg0KPkkgaGF2ZW4ndCB0cmllZCB0byBn ZXQgdGhlICJXaW5kb3dzIiB2ZXJzaW9uIG9mIHRoZSBtZW50aW9uZWQNCj5yZWFkZXIgcnVubmlu ZyB3aXRoIHdpbmUsIG1heWJlIHRoYXQgaXMgcG9zc2libGUgZm9yIHN1Y2gga2luZHMNCj5vZiAi d29yc3QgY2FzZSBQREYgZmlsZSIuLi4gOy0pDQoNCkl0IGlzIGNhbGxlZCwgIkFjcm9iYXQgQWRv YmUgUHJvIERDIi4gQnkgdGhlIHdheSwgd2hhdCBpcyBhDQoibm9uLXN0YW5kYXJkIiBQREYgZmls ZSBhbnl3YXkuIEkgaGF2ZSBuZXZlciBydW4gaW50byBvbmUuDQoNCkJ5IHRoZSB3YXksIGFyZSB5 b3UgYXdhcmUgdGhhdCB0aGVyZSBhcmUgOCByZWNvZ25pemVkIFBERiBzdGFuZGFyZHMuDQoNClRo ZXJlIGFyZSBhIHRvdGFsIG9mIGVpZ2h0IFBERiBzdGFuZGFyZHM7IHNpeCBhcmUgSVNPIFN0YW5k YXJkcyBhbmQgdHdvDQphcmUgZnJvbSBvdGhlciBvcmdhbml6YXRpb25zLiBTaXggVHlwZXMgb2Yg UERGIFN0YW5kYXJkcyBmcm9tIElTTzoNCg0KUERGIOKAk1RoaXMgZ2VuZXJhbCBQREYgc3RhbmRh cmQgaXMgc3VmZmljaWVudCBmb3IgaW4tb2ZmaWNlIHVzZSwgc2hhcmluZw0KYW5kIHZpZXdpbmcg b25saW5lIGFuZCBmb3Igc3RhbmRhcmQgcXVhbGl0eSBkb2N1bWVudHMuDQoNClBERi9BIOKAkyBU aGlzIHN0YW5kYXJkIHdhcyBkZXZlbG9wZWQgZm9yIGxvbmctdGVybSBmaWxlIHN0b3JhZ2UsDQpj b21tb25seSB1c2VkIGJ5IGFyY2hpdmlzdHMsIHJlY29yZHMgbWFuYWdlcnMgYW5kIGNvbXBsaWFu Y2UgbWFuYWdlcnMuDQpJdCBoYXMgYSByZXN0cmljdGVkIHNldCBvZiBmZWF0dXJlcywgaW5jbHVk aW5nIEphdmFTY3JpcHQsIGF1ZGlvIGFuZA0KdmlkZW8gY29udGVudCBhbmQgZW5jcnlwdGlvbiwg YmVjYXVzZSB0aGV5IG1heSBkaXNhbGxvdyB1c2VycyBmcm9tDQpvcGVuaW5nIGFuZCB2aWV3aW5n IGFjY3VyYXRlbHkgaW4gdGhlIGZ1dHVyZS4NCg0KUERGL0Ug4oCTIEFyY2hpdGVjdHMsIGVuZ2lu ZWVycywgY29uc3RydWN0aW9uIHByb2Zlc3Npb25hbHMgYW5kDQptYW51ZmFjdHVyaW5nIHByb2R1 Y3QgdGVhbXMgd2lsbCB1c2UgdGhpcyBzdGFuZGFyZCBtb3N0IG9mdGVuLg0KQWNjb3JkaW5nIHRv IFBsYW5ldCBQREYsIOKAnFRoaXMgc3RhbmRhcmQgd2FzIGludGVuZGVkIHRvIGFkZHJlc3Mga2V5 DQppc3N1ZXMgaW4gdGhlIGFyZWFzIG9mIGxhcmdlLWZvcm1hdCBkcmF3aW5ncywgbXVsdGltZWRp YSwgZm9ybSBmaWVsZHMNCmFuZCByaWdodHMgbWFuYWdlbWVudCDigJMgdG8gbmFtZSBhIGZldyDi gJMgdGhhdCBtaWdodCBwcmV2ZW50IHRoZQ0KZW5naW5lZXJpbmcgY29tbXVuaXR5IGZyb20gZW1i cmFjaW5nIFBERiBpbiB0aGVpciB3b3JrZmxvd3Mu4oCdDQoNClBERi9YIOKAkyBUaGlzIHN0YW5k YXJkIGJlc3Qgc3VpdHMgcHJpbnQgcHJvZmVzc2lvbmFscywgZ3JhcGhpYyBkZXNpZ25lcnMNCmFu ZCBjcmVhdGl2ZSBwcm9mZXNzaW9uYWxzLiBIaWdoIHF1YWxpdHksIHByb2Zlc3Npb25hbCBncmFk ZSBkb2N1bWVudHMNCmNhbiBiZSBleHBlY3RlZCB3aGVuIHVzaW5nIHRoaXMgc3RhbmRhcmQuIFRo aXMgUERGIHN0YW5kYXJkIHdpbGwgZW5zdXJlDQpkb2N1bWVudHMgYXJlIHByaW50LXJlYWR5IGJ5 IGNvcnJlY3RseSBlbWJlZGRpbmcgZm9udHMsIGltYWdlcywgY29sb3INCnByb2ZpbGVzIGFuZCBt b3JlLg0KDQpQREYvVUEg4oCTIFRoaXMgc3RhbmRhcmQgZW5oYW5jZXMgdGhlIHJlYWRhYmlsaXR5 IGZvciBwZW9wbGUgd2l0aA0KZGlzYWJpbGl0aWVzLCBJVCBtYW5hZ2VycyBpbiBnb3Zlcm5tZW50 IG9yIGNvbW1lcmNpYWwgZW50ZXJwcmlzZXMgYW5kDQpjb21wbGlhbmNlIG1hbmFnZXJzLiBUaGUg VUEgc3RhbmRzIGZvciBVbml2ZXJzYWwgQWNjZXNzOyB0aGlzIHN0YW5kYXJkDQp3aWxsIHdvcmsg d2l0aCBhc3Npc3RpdmUgdGVjaG5vbG9neSB0aGF0IGFzc2lzdHMgdXNlcnMgdGhyb3VnaCByZWFk aW5nDQphbmQgbmF2aWdhdGlvbi4gIA0KDQpQREYvVlQg4oCTIFByaW50IHByb2Zlc3Npb25hbHMg d2lsbCBhbHNvIHVzZSB0aGlzIHN0YW5kYXJkIGZvciBkb2N1bWVudHMuDQpUaGlzIHN0YW5kYXJk IGlzIGJhc2VkIG9uIGNvbXBvbmVudHMgb2YgdGhlIFBERi9YIHN0YW5kYXJkLCBhbGxvd2luZw0K c29tZSBmZWF0dXJlcyBzdWNoIGFzIGNvbG9yIHByb2ZpbGVzLCBsYXllcnMgYW5kIHRyYW5zcGFy ZW5jeSB0byBiZQ0KbWFpbnRhaW5lZC4gVGhlIGJpZ2dlc3QgYWRkaXRpb24gaXMgdGhlIGFiaWxp dHkgdG8gY3VzdG9taXplIGRhdGENCndpdGhpbiB0aGVzZSBmaWxlcywgc3VjaCBhcyBiYW5rIHN0 YXRlbWVudHMsIGJ1c2luZXNzIGludm9pY2VzIG9yDQpwZXJzb25hbGl6ZWQgbWFya2V0aW5nIG1h dGVyaWFsLg0KDQpUd28gVHlwZXMgb2YgUERGIFN0YW5kYXJkcyBmcm9tIE90aGVyIE9yZ2FuaXph dGlvbnMNCg0KQWRkaXRpb25hbCBvcmdhbml6YXRpb25zIGhhdmUgYWRvcHRlZCBzdGFuZGFyZHMg Zm9yIHRoZWlyIHNwZWNpZmljDQpkb2N1bWVudCBuZWVkcy4NCg0KUEFkRVMg4oCTIFN0YW5kYXJk aXplcyBzZWN1cmUgcGFwZXJsZXNzIHRyYW5zYWN0aW9ucyB0aGF0IGNvbmZvcm0gdG8gdGhlDQpF dXJvcGVhbiBsZWdpc2xhdGlvbi4gVGhpcyBzdGFuZGFyZCB3YXMgZXN0YWJsaXNoZWQgZm9yIFBE RiBkaWdpdGFsDQpzaWduYXR1cmVzIGluIHRoZSBFVS4NCg0KUERGIEhlYWx0aGNhcmUg4oCTIEFj Y29yZGluZyB0byBBY3JvYmF0LCBUaGlzIHN0YW5kYXJkIOKAnFByb3ZpZGVzIGJlc3QNCnByYWN0 aWNlcyBhbmQgaW1wbGVtZW50YXRpb24gZ3VpZGVsaW5lcyB0byBmYWNpbGl0YXRlIHRoZSBjYXB0 dXJlLA0KZXhjaGFuZ2UsIHByZXNlcnZhdGlvbiBhbmQgcHJvdGVjdGlvbiBvZiBoZWFsdGhjYXJl IGluZm9ybWF0aW9uLg0KRm9sbG93aW5nIHRoZXNlIGd1aWRlbGluZXMgcHJvdmlkZXMgYSBtb3Jl IHNlY3VyZSBlbGVjdHJvbmljIGNvbnRhaW5lcg0KdGhhdCBjYW4gc3RvcmUgYW5kIHRyYW5zbWl0 IGhlYWx0aCBpbmZvcm1hdGlvbiBpbmNsdWRpbmcgcGVyc29uYWwNCmRvY3VtZW50cywgWE1MIGRh dGEsIERJQ09NIGltYWdlcyBhbmQgZGF0YSwgY2xpbmljYWwgbm90ZXMsIGxhYg0KcmVwb3J0cywg ZWxlY3Ryb25pYyBmb3Jtcywgc2Nhbm5lZCBpbWFnZXMsIHBob3RvZ3JhcGhzLCBkaWdpdGFsIFgt cmF5cw0KYW5kIEVDR3Mu4oCdDQoNClBlcnNvbmFsbHksIEkgdXNlIFBERC9YICh0aGVyZSBhcmUg c2V2ZXJhbCBzdWJkaXZpc2lvbnMgb2YgdGhpcyBhbHNvKQ0KZXh0ZW5zaXZlbHkuDQoNClRoZXJl IGlzIHNpbXBseSBubyBvdGhlciBzb2Z0d2FyZSBhcHBsaWNhdGlvbiB0aGF0IEkgYW0gYXdhcmUg b2YgdGhhdA0Kb2ZmZXJzIHRoZSBlYXNlIGFuZCBlZmZpY2VudGN5IG9mIHdvcmtpbmcgd2l0aCBh bGwgdGhlIHZhcmlvdXMgUERGDQp0eXBlcyBsaWtlIEFkb2JlJ3MgbGF0ZXN0IFBERiByZWFkZXIv ZWRpdG9yLg0KDQoNCi0tIA0KQ2FybWVsDQo= From owner-freebsd-questions@freebsd.org Wed Jul 12 14:52:28 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 12618D99774 for ; Wed, 12 Jul 2017 14:52:28 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay11.qsc.de (mailrelay11.qsc.de [212.99.187.252]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8C92E65461 for ; Wed, 12 Jul 2017 14:52:26 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay11.qsc.de; Wed, 12 Jul 2017 16:51:24 +0200 Received: from r56.edvax.de (port-92-195-70-185.dynamic.qsc.de [92.195.70.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id C6A5C3CC8A for ; Wed, 12 Jul 2017 16:51:22 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v6CEpL62002031 for ; Wed, 12 Jul 2017 16:51:21 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Wed, 12 Jul 2017 16:51:21 +0200 From: Polytropon To: freebsd-questions@freebsd.org Subject: Re: FreeBSD Equivalent To Adobe Acrobat Message-Id: <20170712165121.fb671434.freebsd@edvax.de> In-Reply-To: References: <42f8fa2c-a931-0323-203b-8e80494daa8b@ShaneWare.Biz> <20170712004556.72dc63d5.freebsd@edvax.de> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay11.qsc.de with 276BC6A3573 X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.2392 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2017 14:52:28 -0000 On Wed, 12 Jul 2017 09:04:59 +0000, Carmel NY wrote: > On Wed, 12 Jul 2017 00:45:56 +0200, Polytropon stated: > > >On Thu, 6 Jul 2017 12:57:02 +0930, Shane Ambler wrote: > >> On 04/07/2017 10:02, B J wrote: > >> > >> > I tried several and those you mentioned might have been among them. > >> > None of them appeared to fill in blanks, assuming, of course, I did > >> > things right in the first place. For each one, I would get a > >> > message, embedded in the file I was looking at, which said > >> > something about me having to use Acrobat. > >> > >> Could depend on the specific pdf file, pdfs can have some adobe only > >> features such as XFA and javascript, as these aren't part of the > >> official spec I expect they aren't supported in free software. > > > >At least XFA seems to be supported by Okular, but normal forms > >(text input fields) are supported by Evince and Okular; gv and > >xpdf do not support them, but usually can read and print the > >forms (with blank fields of course). > > The OP wanted the ability to edit; in his case "fill in the blanks, in > a PDF document. How does printing a document with blanks achieve this > goal? It doesn't, and I didn't claim it did. You know I'm not a native speaker, but it should be clear. The core message is that both gv and xpdf are able to open the file, instead of reporting an error, crashing, or displaying nonsense. This illustrates as well that it is at least _possible_ to create PDF files with forms that can be used in both ways: for filling using the PDF viewer (and saving the result), and for printing the form and filling the fields in a "pen & paper" manner. In this case, a file with text fields was provided for testing. Both Okular and Evince work for this case. Problem solved. :-) > >So the "Acrobat Reader" or whatever it is called this year is > >not really needed anymore, except you get really non-standard > >PDF files that require special proprietary commercial software. > >I haven't tried to get the "Windows" version of the mentioned > >reader running with wine, maybe that is possible for such kinds > >of "worst case PDF file"... ;-) > > It is called, "Acrobat Adobe Pro DC". By the way, what is a > "non-standard" PDF file anyway. I have never run into one. Thanks for the clarification. I usually don't track the naming conventions of all imaginable kinds of software and their changes through time, but I will try to remember that one, until the next name change. :-) I usually understand the term "non-standard PDF" as a PDF file that contains extensions which are not part of the commonly available implementations of PDF processors. Those might be very special cases from one of the standards as well as a proprietary extension of a standard which only a specific program understands (and implements as intended). For all other PDF processors, such extensions will cause problems, such as incorrect rendering, or no renering at all, or in best case, just missing functionality. In the case of xpdf and gv, those simply don't implement editing capabilities for forms. But forms is not the only thing, there is also scripting and "logic" within PDF files that require a more advanced PDF processor to be used. > By the way, are you aware that there are 8 recognized PDF standards. Yes, that is sort of a problem... and I've actually dealt with a few of them (especially PDF/E, PDF/X, and PDF HC). > There is simply no other software application that I am aware of that > offers the ease and efficentcy of working with all the various PDF > types like Adobe's latest PDF reader/editor. In many settings I was working in, several Adobe products were used in combination, mostly on Mac OS X, fill in current naming here. ;-) So "within that industry", exchange never was a real problem, and with the introduction of Linux desktops, at least opening and working with files became easy due to tools like Evince and Okular. It all depends on the complexity of the tasks you want to solve, where a PDF file is the end product. Luckily, you can choose your tools depending on the task... well... at least in most environments you can... ;-) Finally: The ability to at least print a PDF file with text fields is quite welcome when the creator of the file delivered a defective product. I have seen such crap more than often, built by corporate as well as by government, where the file opens, and you are supposed to fill the blanks, but the fields are set to "inactive", or they are located outside of the document (no idea how they got it that way), or where you cannot print the result because printing has been deactivated, or where you cannot save your inputs. In such cases, customers were happy that they could print the whole form, fill in the information with a pen, made a copy for their own filing purposes, and sent the original (printed and filled) sheets to the organisation that requested (or demanded) it. The ability to do so saved a lot of time. Have you tried calling a governmental agency or a corporate entity and telling them that their PDF files are shit and cannot be worked with as they tell you to? "But we are ISO-9660 certified!" Good luck. Again: Problem solved. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Wed Jul 12 15:49:21 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7375BD9B7F0 for ; Wed, 12 Jul 2017 15:49:21 +0000 (UTC) (envelope-from as@cmplx.uk) Received: from jail0199.vps.exonetric.net (jail0199.vps.exonetric.net [IPv6:2a02:1658:1::199:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "jail0199.vps.exonetric.net", Issuer "jail0199.vps.exonetric.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0CD9E67CCF for ; Wed, 12 Jul 2017 15:49:20 +0000 (UTC) (envelope-from as@cmplx.uk) Received: from jail0199.vps.exonetric.net (jail0199.vps.exonetric.net [178.250.76.108]) by jail0199.vps.exonetric.net (8.15.2/8.15.2) with ESMTPS id v6CFnHS6053002 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 12 Jul 2017 15:49:17 GMT (envelope-from as@jail0199.vps.exonetric.net) Received: (from as@localhost) by jail0199.vps.exonetric.net (8.15.2/8.15.2/Submit) id v6CFnHQq053001 for freebsd-questions@freebsd.org; Wed, 12 Jul 2017 15:49:17 GMT (envelope-from as) Date: Wed, 12 Jul 2017 15:49:17 GMT From: Anton Shterenlikht Message-Id: <201707121549.v6CFnHQq053001@jail0199.vps.exonetric.net> To: freebsd-questions@freebsd.org Subject: Error opening terminal: xterm X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2017 15:49:21 -0000 I'm trying to use ports-mgmt/synth. I get: # synth build net/mpich Error opening terminal: xterm. John Marino replied on github this is nothing to do with synth but rather some misconfig on my box. He mentioned termcap. As far as I can see my /etc/termcap.small is the default version. Anybody has a suggestion? Thanks Anton From owner-freebsd-questions@freebsd.org Wed Jul 12 16:32:31 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B2C7D9CC69 for ; Wed, 12 Jul 2017 16:32:31 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay13.qsc.de (mailrelay13.qsc.de [212.99.187.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B18F36AA10 for ; Wed, 12 Jul 2017 16:32:30 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay13.qsc.de; Wed, 12 Jul 2017 18:31:31 +0200 Received: from r56.edvax.de (port-92-195-70-185.dynamic.qsc.de [92.195.70.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 4C91E3CBF9; Wed, 12 Jul 2017 18:31:29 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v6CGVSqq002530; Wed, 12 Jul 2017 18:31:28 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Wed, 12 Jul 2017 18:31:28 +0200 From: Polytropon To: Anton Shterenlikht Cc: freebsd-questions@freebsd.org Subject: Re: Error opening terminal: xterm Message-Id: <20170712183128.9cb516c9.freebsd@edvax.de> In-Reply-To: <201707121549.v6CFnHQq053001@jail0199.vps.exonetric.net> References: <201707121549.v6CFnHQq053001@jail0199.vps.exonetric.net> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay13.qsc.de with A0459683523 X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1375 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2017 16:32:31 -0000 On Wed, 12 Jul 2017 15:49:17 GMT, Anton Shterenlikht wrote: > I'm trying to use ports-mgmt/synth. > I get: > > # synth build net/mpich > Error opening terminal: xterm. Is the "xterm" program installed on your machine? Yes, I know, stupid question, but might be relevant. ;-) > John Marino replied on github this is nothing > to do with synth but rather some misconfig on > my box. He mentioned termcap. > > As far as I can see my /etc/termcap.small is > the default version. Terminal emulators usually have a built-in "sane default" in case of problems with termcap or terminfo. The error message doesn't really look like something termcap-related, it's just that there is no indication of _what_ is the problem. > Anybody has a suggestion? Can you manually start xterm? From within an xterm (or whatever terminal emulator you are using)? Maybe the port in question expects /usr/bin/xterm to be the executable ("hardcoded Linuxism")? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Wed Jul 12 16:40:58 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8D764D9CEED for ; Wed, 12 Jul 2017 16:40:58 +0000 (UTC) (envelope-from as@cmplx.uk) Received: from jail0199.vps.exonetric.net (jail0199.vps.exonetric.net [IPv6:2a02:1658:1::199:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "jail0199.vps.exonetric.net", Issuer "jail0199.vps.exonetric.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3C9E96ADA3 for ; Wed, 12 Jul 2017 16:40:58 +0000 (UTC) (envelope-from as@cmplx.uk) Received: from jail0199.vps.exonetric.net (jail0199.vps.exonetric.net [178.250.76.108]) by jail0199.vps.exonetric.net (8.15.2/8.15.2) with ESMTPS id v6CGetRu055239 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 12 Jul 2017 16:40:55 GMT (envelope-from as@jail0199.vps.exonetric.net) Received: (from as@localhost) by jail0199.vps.exonetric.net (8.15.2/8.15.2/Submit) id v6CGetvf055238; Wed, 12 Jul 2017 16:40:55 GMT (envelope-from as) Date: Wed, 12 Jul 2017 16:40:55 GMT From: Anton Shterenlikht Message-Id: <201707121640.v6CGetvf055238@jail0199.vps.exonetric.net> To: freebsd-questions@freebsd.org, freebsd@edvax.de Subject: Re: Error opening terminal: xterm In-Reply-To: <20170712183128.9cb516c9.freebsd@edvax.de> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2017 16:40:58 -0000 > Date: Wed, 12 Jul 2017 18:31:28 +0200 > From: Polytropon > To: Anton Shterenlikht > Subject: Re: Error opening terminal: xterm > Cc: freebsd-questions@freebsd.org > > On Wed, 12 Jul 2017 15:49:17 GMT, Anton Shterenlikht wrote: > > I'm trying to use ports-mgmt/synth. > > I get: > > > > # synth build net/mpich > > Error opening terminal: xterm. > > Is the "xterm" program installed on your machine? > Yes, I know, stupid question, but might be relevant. ;-) yes, it is, use it every day: # pkg info -xo xterm xterm-330 x11/xterm However, I never launch xterm as root, because I don't allow root access to X: # xterm Warning: This program is an suid-root program or is being run by the root user. The full text of the error or warning message cannot be safely formatted in this environment. You may get a more descriptive message by running the program as a non-root user or by removing the suid bit on the executable. xterm: Xt error: Can't open display: %s xterm: DISPLAY is not set Again John told me this error has nothing to do with X anyway. > > > Anybody has a suggestion? > > Can you manually start xterm? From within an xterm (or > whatever terminal emulator you are using)? yes, sure. > > Maybe the port in question expects /usr/bin/xterm to be > the executable ("hardcoded Linuxism")? unlikely. ports-mgmt/synth was recently strongly recommended by some experienced users in ports@ as a replacement of portmaster. So I guess this must be a well behaved port. Thanks Anton From owner-freebsd-questions@freebsd.org Wed Jul 12 16:52:11 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 547D5D9D3CC for ; Wed, 12 Jul 2017 16:52:11 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from inet08.hamilton.harte-lyne.ca (inet08.hamilton.harte-lyne.ca [216.185.71.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "inet08.hamilton.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1FCB36E29E for ; Wed, 12 Jul 2017 16:52:10 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from localhost (localhost [127.0.0.1]) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTP id A64FF6211D; Wed, 12 Jul 2017 12:44:53 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from inet08.hamilton.harte-lyne.ca ([127.0.0.1]) by localhost (inet08.hamilton.harte-lyne.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DzsdownQdkxV; Wed, 12 Jul 2017 12:44:51 -0400 (EDT) Received: from webmail.harte-lyne.ca (inet04.hamilton.harte-lyne.ca [216.185.71.24]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTPSA id 124F962107; Wed, 12 Jul 2017 12:44:51 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=harte-lyne.ca; s=dkim_hll; t=1499877891; bh=RwvsA+UAv4PmILY8Jfz4iBBNHWhFfW3njRe21rrNF0E=; h=In-Reply-To:References:Date:Subject:From:To:Cc:Reply-To; b=ylgZim+SBbEM9zJ5YMzn+TK7ZJegXtB2lw+lfCO8FxgzQ/DYzBqDw/+0yUYsv7Gzg X4IHLDMOHnh9SVC472Gs+i/CawpvVzU9184MuQtoPn2gL3Qr9dpHV7+1Qn+TWSseuX BJgzwFqs92IhQkArLTFyVpB6twil3N9gcPkylauwlDLcI/GLHB6rsClpWBSjgJN8NV lhMLFRJCEU34an7onhwUECCSY/DssxbNemGKfmkjKJHrxoNHawfPiUfZgoKLix4Z/h V8MfcNmqw0Fj81H9Gnem8JyTSib9+YLWSW9aaP0lG5ckazoFhSoGRTpU2M0GsIbCgU p12KJC8OeppUg== Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Wed, 12 Jul 2017 12:44:51 -0400 Message-ID: In-Reply-To: References: <772bdab1906a8a3deea24fb6b246e40e.squirrel@webmail.harte-lyne.ca> Date: Wed, 12 Jul 2017 12:44:51 -0400 Subject: Re: A readers digest version of transferring a jail from one host to another. From: "James B. Byrne" To: "Ben Woods" Cc: freebsd-questions@freebsd.org Reply-To: byrnejb@harte-lyne.ca User-Agent: SquirrelMail/1.4.22-5.el6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2017 16:52:11 -0000 On Fri, June 30, 2017 19:37, Ben Woods wrote: > Hi James, > > With ezjail the easiest way to take a copy of a jail and move it to > another host is with the build in archive/restore process. > > Old server: > # ezjail-admin stop jailname > # ezjail-admin archive jailname > > default it will be in /usr/jails/ezjail_archives.> > > New server: > # ezjail-admin restore archivefilename > # ezjail-admin start jailname > > For more details and optional arguements to these commands you can > refer to the manpage: > http://man.freebsd.org/ezjail-admin > > Regards, > Ben Thank you for the advice. It was most useful now that I have finally gotten to use it. I did mention that I was pressed for time. I simply did not realize just how pressed I would be. After creating and transferring the archives to the target host what I ended up doing was a variant of this command: ezjail-admin create \ -a /usr/jails/ezjail_archives/hllmx18-201707041251.23.tar.gz \ hllmx150 'lo1|127.0.150.1,lo1|::150:1,re0|192.168.209.150' Which produced exactly the result I sought. Thanks again. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 From owner-freebsd-questions@freebsd.org Wed Jul 12 17:03:34 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 11F45D9DD7E for ; Wed, 12 Jul 2017 17:03:34 +0000 (UTC) (envelope-from kayasaman@gmail.com) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9613F6ED80 for ; Wed, 12 Jul 2017 17:03:33 +0000 (UTC) (envelope-from kayasaman@gmail.com) Received: by mail-wm0-x229.google.com with SMTP id w126so444415wme.0 for ; Wed, 12 Jul 2017 10:03:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=UL1Uu3jUJydZ407T21PyDCuul2T6uVqlXoFEYIEs7GE=; b=GPBn0hji3dT5bhFOsHFHqLV28xcdrQYdaNucq0oioZGl/K1OaUsyPyqpSkozjZlRXQ VbdOZ3nCYxXIrVoPjZCdR47noMM6eOK2wxZHO64E343q++0bSHmYb00XtV4zdYV/lqEg K6mGtQ3nhMuydarsiqNocbOicgF0z4SFD5rrNwz4xAdW2hUpqbBQNHTpuKrIqopDbxZV gDDvjjHbRGnolEpBADYzNf/aOi65dD9PJj38n85JyKu5CUg+Nta8IgqUqWkNcVQ5Q2yb Ypc8EDqxXrRDcgw0hD1vCinGeeoC6K+2ARWU6suSFOCBCPt6HbRr8568//inONAH4qP8 Jomw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=UL1Uu3jUJydZ407T21PyDCuul2T6uVqlXoFEYIEs7GE=; b=rZWnZFHTxVkSU496bFVKeBdn0+jaSXYbDCtgZD+Q3ybASjLDwRqxvACnLqIfacH1K8 wx08WTTIDQSOyK1iP6x3ccfak1OuYuB1aeFKQVSwgW+aEvaJ/r+ZubKOyRLS2HfGieSK vpCD5M6KKjyPLyC+43tg4LYZzM/Z7e/z83rG25JCNQ2liXoq2TbAtcEWxiod/n1yMQeX 3xGlDfrFg47Vcrb2OQtLkHP0ScURSK7qi8HspRWMewywMjrJ3+sZGh7rWtGZR3lBWANI ttTGPoh3Oxp7fUilQuL3jE5S9bfhnxuJFxveBs+jIPlyhGs/m6jLdnTax38SBFKdgY3d dznQ== X-Gm-Message-State: AIVw111f/ewzrnNMhwTtE9EI3d+0E2cHgRY/gyDuyL1/7Nj7Y9+Kb1iG kDr1jrPczvjNNGsI2aw= X-Received: by 10.28.49.7 with SMTP id x7mr3470108wmx.57.1499879011278; Wed, 12 Jul 2017 10:03:31 -0700 (PDT) Received: from x220.optiplex-networks.com (optiplexnetworks.plus.com. [212.159.80.17]) by smtp.gmail.com with ESMTPSA id 79sm1786682wrc.34.2017.07.12.10.03.30 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Jul 2017 10:03:30 -0700 (PDT) Subject: Re: A readers digest version of transferring a jail from one host to another. To: freebsd-questions@freebsd.org References: <772bdab1906a8a3deea24fb6b246e40e.squirrel@webmail.harte-lyne.ca> From: Kaya Saman Message-ID: <74268400-5a27-805f-5c46-dbe36cfffe72@gmail.com> Date: Wed, 12 Jul 2017 18:03:30 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2017 17:03:34 -0000 Just to chime in here quickly as I have had to do this too, however, not using ezjail - forgive me if this has already been mentioned as I've just caught the tail of the thread and of course don't want to hijack anyone elses input... For me I usually stop jail: /etc/rc.d/jail stop rsync -"flags" path/to/jail "rsync:"/new/path/to/jail eg. rsync -avvc --progress --remove-source-files /jl/myjail rsync://10.0.0.1:/jl/myjail then start the new jail on host 10.0.0.1: /etc/rc.d/jail start myjail this is an alternate as an FYI :-) Regards, Kaya On 07/12/2017 05:44 PM, James B. Byrne via freebsd-questions wrote: > On Fri, June 30, 2017 19:37, Ben Woods wrote: >> Hi James, >> >> With ezjail the easiest way to take a copy of a jail and move it to >> another host is with the build in archive/restore process. >> >> Old server: >> # ezjail-admin stop jailname >> # ezjail-admin archive jailname >> >> > default it will be in /usr/jails/ezjail_archives.> >> >> New server: >> # ezjail-admin restore archivefilename >> # ezjail-admin start jailname >> >> For more details and optional arguements to these commands you can >> refer to the manpage: >> http://man.freebsd.org/ezjail-admin >> >> Regards, >> Ben > Thank you for the advice. It was most useful now that I have finally > gotten to use it. I did mention that I was pressed for time. I > simply did not realize just how pressed I would be. > > After creating and transferring the archives to the target host what I > ended up doing was a variant of this command: > > ezjail-admin create \ > -a /usr/jails/ezjail_archives/hllmx18-201707041251.23.tar.gz \ > hllmx150 'lo1|127.0.150.1,lo1|::150:1,re0|192.168.209.150' > > Which produced exactly the result I sought. > > Thanks again. > From owner-freebsd-questions@freebsd.org Wed Jul 12 19:43:29 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 460B5DA1B47 for ; Wed, 12 Jul 2017 19:43:29 +0000 (UTC) (envelope-from friedrich.locke@gmail.com) Received: from mail-yb0-x233.google.com (mail-yb0-x233.google.com [IPv6:2607:f8b0:4002:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 071D574B2B for ; Wed, 12 Jul 2017 19:43:29 +0000 (UTC) (envelope-from friedrich.locke@gmail.com) Received: by mail-yb0-x233.google.com with SMTP id n200so5756370ybg.2 for ; Wed, 12 Jul 2017 12:43:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=X6MHJ0SmrT7B9wBEY23EWBcBnCZlI3DTEibFreupG4w=; b=SBj/LigIP025qEaSDRFcijpb1SrM2OzkhaQmyPKPsjZH6ESXOksxkQxEKEVx3RDsd3 vejMIRx/kMeo4xSKT4hrLUhmY8H/1PaE+Yr1YOiLXrDAQvGxS+6jbX0XokX5657fvhv/ cyc5mWgiJbcxhMetcLACf/OrrFHAZHmHuhs50hDfnAD3xZWO+ekoL8WTxJB13rHr3YPL ao6feM6+LL9coSwUt97dRGvhhecAw9E/u9D96dBTmibuBXVrltxsIC7hkKUH7ngz22bS wGdJMy7BIuHtV1qFqcR+8FlS9ahS8UChn3zN1jbqTC0fd54bmouWboKORDeYgRiinBCF x1Yg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=X6MHJ0SmrT7B9wBEY23EWBcBnCZlI3DTEibFreupG4w=; b=nWDEqlEE45ttML/lWfrKMwltGNhodH9PmiupzCMN2SQ3zM9B3KUEHyQKdoWskbaN/p NOEcKW67nVFkBp9KO2HuJCsp6I4x9sN6uMWCTRQKve1GpprGfKt4rnBj+sHLdM/NOadX 9sjAvIMGILxXJZ2NBotoiNBZoAikPQ5BYBLZZGTgKOWm7XYiayHD3iRvfDDUM6pZ80wL x4kFY2NHqf0cpp8FxhIZLsh3EdqvIUWRUclr1jf6bwAtiua8WLAIfHSrvo7kK8WwhIxW rlacHilyEGLMM9KbIbI+LaWGJYNEK4ojCz75mRLnhjHc1a9MlTgpj1l7c9MXHJAgeQi/ 6v7Q== X-Gm-Message-State: AIVw112XHx6wQmJT5Cb9RP1fAJmu7WSgT2hHgXeHE6377sjOD9aiMt/J R4V5Ah4LnWEh1ijRFZHO5ff4qPTp1w== X-Received: by 10.37.161.3 with SMTP id z3mr197629ybh.18.1499888608110; Wed, 12 Jul 2017 12:43:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.177.146 with HTTP; Wed, 12 Jul 2017 12:43:27 -0700 (PDT) From: Friedrich Locke Date: Wed, 12 Jul 2017 16:43:27 -0300 Message-ID: Subject: xdm replacement To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2017 19:43:29 -0000 I would like to install xdm in my box, but i got error related to security problems with X*** library. What could i replace xdm for ? Thanks in advance. From owner-freebsd-questions@freebsd.org Wed Jul 12 19:43:55 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A6D91DA1BC2; Wed, 12 Jul 2017 19:43:55 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 241F874BD7; Wed, 12 Jul 2017 19:43:54 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.180.71.3]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LbM2k-1dxWDw1jzu-00ktnw; Wed, 12 Jul 2017 21:43:46 +0200 Date: Wed, 12 Jul 2017 21:43:34 +0200 From: "O. Hartmann" To: FreeBSD CURRENT , FreeBSD Questions Subject: Inter-VLAN routing on CURRENT: any known issues? Message-ID: <20170712214334.4fc97335@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/hakecsp8FO_KOq4QSAYnpJl"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:unxbJaZ8sAx0ZhWd4l1EvuV1X00rsh8BW6cvKtD/dd3F6NI0qD2 0I6R89BjuFQk1W1oyk3av6dPc2Q4D3a6FmoLcvaf+5zjkLZoHgvv+7tp9PA0WhF/vS/arfm sqjOGEwgte1WKqHJlpkAiDsjnJFU7HlrWEhVUbpUHXY2UEMQewYHSxGyt5ojNG+YJzvBjEe ud96Z3lbL8uZv4y2f+2EA== X-UI-Out-Filterresults: notjunk:1;V01:K0:pS61UUN7p2Q=:qa/4yIdC3DH9a1KAPOnHm4 R95LAW5wxE+4HbnP6QxEFwafpMgbzbLI0+rG1mdQEn5d9X3maOl7Zr9rEnih4JEl7a9462d0e e508jboTWpZ440ocLNMkIqoWnkr5SNT5Y5WTv+8oze4PjQ3bbqbWzQ6Z4aSUg1Nfp0w+ijaj8 5n2YAQpP3gC7VR2y7OVJwEPX6Lfg8cEUc9XlZ6J3+N5kdNjO+ntEYtWvLh7OevP0YyH94R1Hf uKLYjcRFmpWhrCUgU4a5y5TrPU1ehj691wrPdqxCxpfi3kRow+oUVEnn+Q2L2chorfLlCEP+v Dme6NzjeddkPDbazD8fgi7ikusBGniJOc71fez7xAejrfKiqd6PNOtPEH51BzW9qWKiaoiIEv 4PLnEOwfqfDjz5VCEn8bfrOTCKOo4nFrdbYuIT+0LNC+GFOXBwPZuNbuO2HKih0PsdaGf50qF n57qYO83lV16tecX0hD6D8iqtQMAWsZDAZ6MVD8dDXBXMD6MOoIv/aNgzB/NVCtJkTpKtaqd1 aXhEwI/hZqUoaOSpdRyWbCUOPpEuvVwCO/SjN1vCRObSDJ3cTJiilo3WPeMqqFpdqQQVaQycj ah34liJE6hVqnJWcRG50kccp7CkPsEVa2FR54HVE5HZajQdAlvF9T+ge3NS1irMyaDOwRAdFb E0T/L63pCrXy1EAA3r1LDRFB8VQ9YQ14m0GUsIsUtz2c14EnooBhYUAnEDbLMPCJ7DJTokygG BgkquYVBWOd6BD7CmG7oRVBhrqUaETGFI0kYhF2gIB10qq/xuPtCZBf1JVo= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2017 19:43:55 -0000 --Sig_/hakecsp8FO_KOq4QSAYnpJl Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Since a couple of days for now I fail to setup VLAN trunking on a FreeBSD 1= 2-CURRENT box (FreeBSD 12.0-CURRENT #9 r320913: Wed Jul 12 17:26:22 CEST 2017 amd64) whic= h is based on a PCEngines APU 2C4 board with three Intel i210 NICs. igb0 is connected to a Allnet VDSL modem via tun0/ppp. igb2 is unused. igb1 is considered "multihomed" and comprises several VLANs: [/etc/rc.conf] gateway_enable=3D"YES" ... ifconfig_igb1=3D"up" vlans_igb1=3D"1000 2 3 10 66 100" ifconfig_igb1_1000=3D"inet 192.168.0.1/24" create_args_igb1_1000=3D"vlanpcp 7" ifconfig_igb1_2=3D"inet 192.168.2.1/24" ifconfig_igb1_3=3D"inet 192.168.3.1/24" ifconfig_igb1_10=3D"inet 192.168.10.1/24" ifconfig_igb1_66=3D"inet 192.168.66.1/24" ifconfig_igb1_100=3D"inet 192.168.100.1/24" ... VLAN 1000 is considered my internal network, the others are for special pur= pose, e.g. VLAN 2 is for VoIP equiment. After booting (a customised) kernel the router shows the following settings: root@gate:~ # netstat -Warn Routing tables Internet: Destination Gateway Flags Use Mtu Netif Exp= ire default 111.111.111.111 US 570 1492 tun0 111.111.111.111 link#12 UHS 0 1492 tun0 22.33.44.55 link#12 UHS 0 16384 lo0 127.0.0.1 link#4 UH 115 16384 lo0 192.168.0.0/24 link#2 U 13930 1500 igb1.1000 192.168.0.1 link#2 UHS 0 16384 lo0 192.168.2.0/24 link#7 U 1 1500 igb1.2 192.168.2.1 link#7 UHS 0 16384 lo0 192.168.3.0/24 link#8 U 0 1500 igb1.3 192.168.3.1 link#8 UHS 0 16384 lo0 192.168.10.0/24 link#9 U 0 1500 igb1.10 192.168.10.1 link#9 UHS 0 16384 lo0 192.168.66.0/24 link#10 U 0 1500 igb1.66 192.168.66.1 link#10 UHS 0 16384 lo0 192.168.100.0/24 link#11 U 0 1500 igb1.100 192.168.100.1 link#11 UHS 0 16384 lo0 All interfaces (including vlan) show "UP" in their status.=20 sshd, named and services are bound on the router to 192.168.0.1, which is i= ts IP. The router's igb1-NIC is physically connected to a SoHo switch Netgear GS11= 0TP. Its config in short according to the manual (http://www.netgear.com/support/product/GS110TP.aspx#docs , chapter 3, pagu= s 84) is as follows. Port gs9 is considered the trunk/etherchannel port (via GBIC 1 Gig). Accord= ingly to my setup, the VLANs 1,2,3 (switch-native),10, 66, 100 and 1000 are defined. In= VLAN membership configuration for VLAN 1, only port g1 is marked "U", this is my maintenance port. For VLAN 1000 ports g1-g4 are "U" untagged, g9 is "T" tag= ged. For VLAN 2, port g7 is "U", g8 is "T" (the VoIP telephone has vlan tag 2) and the tr= unk is g9 "T". VLAN 100 occupies port g5 "U", port g9 is "T". The other VLANs are unused a= t the moment. According to handbook section "Port VLAN ID Configuration" (PVID), g1-g4 ar= e PVID 1000, Accept. Frame Type is "Admit All" and Ingress Filtering is "disabled". The = settings for the other so called "access ports" are accordingly.=20 g9, the trunk port, has PVID 1, Admit all, Ingress Filtering is disabled. O= ther configurations are mostly as the switch is set-up after factory reset. On ports g1 - g4 I have a dual-port NIC'ed server (one port vlan 1000, othe= r vlan 100) running and a notebook, which I can configure freely. Now the FUN PART: =46rom any host in any VLAN I'm able to ping hosts on the wild internet via t= heir IP, on VLAN 1000 there is a DNS running, so I'm also able to resolv names like goo= gle.com or FreeBSD.org. But I can NOT(!) access any host via http/www or ssh.=20 I also can not access a host's sshd in the neighbour VLAN routed via the ro= uter, say from a host/server on VLAN 1000 to a host/VoIP telephone on VLAN 2. I can p= ing the hosts from each VLAN to the other (so ICMP flows), but any IP service seems to ge= t sacked by a black hole. From hosts on VLAN 1000 I can access the router's sshd (192.168= .0.1). More disturbing: from the router itself, I'm able to access the sshd of eac= h host on each VLAN, i.e. VLAN 1000, VLAN 2 (VoIP), but when setting up a notebook (F= reeBSD 12-CURRENT of the same or similar revision) in VLAN 2 or VLAN 100 or VLAN 6= 6 with SSHD listening on all interfaces, I'm able to connect to that system. Also, from= the router itself, I can ping any host on any VLAN and the internet (routed via tun0/i= gb0/modem). =46rom any host on any VLAN, I can ping the router, I can ping the world, I c= an ping other hosts on other VLANs. Obviously, ICMP is routed. Any attempt to access a service from a host in any VLAN to a hosts's servic= e on another VLAN fails. IP is not routed and I do not see why. The kernel is compiled with in-kernel IPFW. No matter what I do, either ipf= w "OPEN" or using my ruleset which works in the special case I describe later, routing = through VLANs seems not to work for any IP packet! Using tcpdump on the router while trying to ssh into another host, I see th= e initial [S] marked attempt to connect, i.e. 192.168.0.128 > 192.168.2.50: [S]. Onece th= e packet has been sent from sender to the router, I never is passed to the recipient.=20 Before I start attempting making weird speculations, I must confess that us= ing tcpdump and other network tools is not my favourite and I'm quite new/novice on tha= t field.=20 I need advice. Also, I need to know whether the setup I showed is working o= r whether I make a serious and stupid mistake (maybe due to not having understood FreeB= SD's routing or routing at all).=20 If on the setup shown above the VLAN is dumped and when I use only igb1 as = the "vanilla" NIC, everything works smoothly - execpt the fact I do not have network sepa= rations. But it shows me that in principle the complete setup isn't complete bullshit. F= rom that persepctive, even just changing igb1 to igb1.1000 (a tagged VLAN), it shoul= d work. But it doesn't. I'm not sure whether IPFW is the culprit or not or anothe knob, for the rec= ord, these settings are for ipfw in the kernel: [...] options NETGRAPH # netgraph(4) system options NETGRAPH_IPFW options NETGRAPH_NETFLOW options NETGRAPH_ETHER options NETGRAPH_NAT options NETGRAPH_DEVICE options NETGRAPH_PPPOE options NETGRAPH_SOCKET options NETGRAPH_ASYNC options NETGRAPH_TEE # IPFW firewall options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=3D0 options IPFIREWALL_NAT #ipfw kernel nat support options LIBALIAS #ipfw kernel nat support options IPDIVERT # NAT options DUMMYNET # traffic shaper # #options IPFIREWALL_DEFAULT_TO_ACCEPT [...] and from sysctl: kern.features.ipfw_ctl3: 1 net.link.ether.ipfw: 0 net.link.bridge.ipfw: 0 net.link.bridge.ipfw_arp: 0 So, if someone is willing to give me some hints, I'd be glad to hear from y= ou. I'm starting getting insane over this problem :-( Kind regards and thanks for your patience, Oliver --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/hakecsp8FO_KOq4QSAYnpJl Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWWZ75gAKCRDS528fyFhY lFDtAgCQfzw2Q1HpqjWeMDZDW52syCjmmcheUuOGUqKgikc+Dr1WYUMvhVM+FCkJ Thwef0zCavLdiTbUyf70hs8t3K24AfsHzAn3QMxr+XSgFsyATR1GEmPOjOF3tF/N sfMYty1efOBxW1FwjecyzvSoLu2yEyENt7ZnavjLTRYE8j5xn7tr =t2CV -----END PGP SIGNATURE----- --Sig_/hakecsp8FO_KOq4QSAYnpJl-- From owner-freebsd-questions@freebsd.org Wed Jul 12 21:03:22 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 22E23DA3CEA for ; Wed, 12 Jul 2017 21:03:22 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: from h2.pinyon.org (h2.pinyon.org [65.101.20.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E648077B70 for ; Wed, 12 Jul 2017 21:03:21 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: by h2.pinyon.org (Postfix, from userid 58) id A14D81B230; Wed, 12 Jul 2017 14:03:19 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pinyon.org; s=DKIM; t=1499893399; bh=lywc3a/XeWOvrZy9AOOz0Vkb1YLqowerwqA9+d4Qrsk=; h=Subject:To:References:From:Date:In-Reply-To; b=ezpL1cB5BRDPjKAxU+/HfiZ4sW/Jr7SqkNBC0Cvu2hfyHhD2Z2PFivHxNjJD6pcLm bS4TwuXcwB2IqBTRRQQFfj8NwADlZXc8c94m7ZRm/2AQgkKDO8lM3WQprglbNPc2hI FRiAcTUXNSSrx/jrCGEMiaBG2i83RQKKRk9sAx0o= X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on h2.n1.pinyon.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.1 Received: from [10.0.10.15] (h1.pinyon.org [65.101.20.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by h2.pinyon.org (Postfix) with ESMTPSA id 19D731B223 for ; Wed, 12 Jul 2017 14:03:18 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pinyon.org; s=DKIM; t=1499893399; bh=lywc3a/XeWOvrZy9AOOz0Vkb1YLqowerwqA9+d4Qrsk=; h=Subject:To:References:From:Date:In-Reply-To; b=ezpL1cB5BRDPjKAxU+/HfiZ4sW/Jr7SqkNBC0Cvu2hfyHhD2Z2PFivHxNjJD6pcLm bS4TwuXcwB2IqBTRRQQFfj8NwADlZXc8c94m7ZRm/2AQgkKDO8lM3WQprglbNPc2hI FRiAcTUXNSSrx/jrCGEMiaBG2i83RQKKRk9sAx0o= Subject: Re: xdm replacement To: freebsd-questions@freebsd.org References: From: "Russell L. Carter" Message-ID: Date: Wed, 12 Jul 2017 14:03:18 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2017 21:03:22 -0000 On 07/12/17 12:43, Friedrich Locke wrote: > I would like to install xdm in my box, but i got error related to security > problems with X*** library. > > What could i replace xdm for ? I am still using xdm, but when not using that I usually reach for wdm. Russell > > Thanks in advance. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > From owner-freebsd-questions@freebsd.org Wed Jul 12 22:08:32 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7003BDA6091 for ; Wed, 12 Jul 2017 22:08:32 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay15.qsc.de (mailrelay15.qsc.de [212.99.187.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 65677798CA for ; Wed, 12 Jul 2017 22:08:30 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay15.qsc.de; Thu, 13 Jul 2017 00:07:25 +0200 Received: from r56.edvax.de (port-92-195-13-67.dynamic.qsc.de [92.195.13.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 314493CBF9; Thu, 13 Jul 2017 00:07:24 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v6CM7NcS004245; Thu, 13 Jul 2017 00:07:24 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Thu, 13 Jul 2017 00:07:23 +0200 From: Polytropon To: Friedrich Locke Cc: freebsd-questions@freebsd.org Subject: Re: xdm replacement Message-Id: <20170713000723.9d529bc4.freebsd@edvax.de> In-Reply-To: References: Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay15.qsc.de with 7BD936834AA X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1261 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2017 22:08:32 -0000 On Wed, 12 Jul 2017 16:43:27 -0300, Friedrich Locke wrote: > I would like to install xdm in my box, but i got error related to security > problems with X*** library. > > What could i replace xdm for ? Hmmm... xdm is usually considered quite secure, but maybe this has changed during the development course of X... As alternatives I'd like to suggest wdm (the WindowMaker display manager) and slim. Both are easy to setup, work well with the defaults, and allow customizing if needed. They also play nice with different window managers and desktop environments. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Thu Jul 13 00:34:17 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D8A89DA9564 for ; Thu, 13 Jul 2017 00:34:17 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay13.qsc.de (mailrelay13.qsc.de [212.99.187.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5ED3F7ED95 for ; Thu, 13 Jul 2017 00:34:16 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay13.qsc.de; Thu, 13 Jul 2017 02:34:13 +0200 Received: from r56.edvax.de (port-92-195-13-67.dynamic.qsc.de [92.195.13.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id A9E863CC3F; Thu, 13 Jul 2017 02:34:12 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v6D0YBqC005433; Thu, 13 Jul 2017 02:34:12 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Thu, 13 Jul 2017 02:34:11 +0200 From: Polytropon To: Anton Shterenlikht Cc: freebsd-questions@freebsd.org Subject: Re: Error opening terminal: xterm Message-Id: <20170713023411.ca82e375.freebsd@edvax.de> In-Reply-To: <201707121640.v6CGetvf055238@jail0199.vps.exonetric.net> References: <20170712183128.9cb516c9.freebsd@edvax.de> <201707121640.v6CGetvf055238@jail0199.vps.exonetric.net> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay13.qsc.de with 0C66668345D X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1329 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2017 00:34:17 -0000 On Wed, 12 Jul 2017 16:40:55 GMT, Anton Shterenlikht wrote: > > Date: Wed, 12 Jul 2017 18:31:28 +0200 > > From: Polytropon > > To: Anton Shterenlikht > > Subject: Re: Error opening terminal: xterm > > Cc: freebsd-questions@freebsd.org > > > > On Wed, 12 Jul 2017 15:49:17 GMT, Anton Shterenlikht wrote: > > > I'm trying to use ports-mgmt/synth. > > > I get: > > > > > > # synth build net/mpich > > > Error opening terminal: xterm. > > > > Is the "xterm" program installed on your machine? > > Yes, I know, stupid question, but might be relevant. ;-) > > yes, it is, use it every day: > > # pkg info -xo xterm > xterm-330 x11/xterm > > However, I never launch xterm as root, > because I don't allow root access to X: > > # xterm > Warning: This program is an suid-root program or is being run by the root user. > The full text of the error or warning message cannot be safely formatted > in this environment. You may get a more descriptive message by running the > program as a non-root user or by removing the suid bit on the executable. > xterm: Xt error: Can't open display: %s > xterm: DISPLAY is not set Fully correct. > Again John told me this error has nothing to do with X anyway. It doesn't really look like an X error, but it also doesn't look like a termap/terminfo error, because those errors tend to give a hint through their error message. The message "Error opening terminal: xterm." isn't very helpful. Can you provide some context from where (within the overall construct) this message is coming? What tries to start xterm, and how does it try to do so? Can the maintainer explain? > > > Anybody has a suggestion? > > > > Can you manually start xterm? From within an xterm (or > > whatever terminal emulator you are using)? > > yes, sure. Good. > > Maybe the port in question expects /usr/bin/xterm to be > > the executable ("hardcoded Linuxism")? > > unlikely. ports-mgmt/synth was recently strongly > recommended by some experienced users in ports@ > as a replacement of portmaster. So I guess this > must be a well behaved port. I'd think so, too - but still the error message (which doesn't provide the _actual_ error) might suggest that there is still something not working as intended. As you can manually start xterm, xterm probably isn't the problem; starting xterm as root _could_ be, but there are no X-related error messages (such as $DISPLAY not set, or missing X access permission). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Thu Jul 13 07:37:50 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C41B8D9A158 for ; Thu, 13 Jul 2017 07:37:50 +0000 (UTC) (envelope-from ml@netfence.it) Received: from smtp207.alice.it (smtp207.alice.it [82.57.200.103]) by mx1.freebsd.org (Postfix) with ESMTP id 5C91E68ED1 for ; Thu, 13 Jul 2017 07:37:49 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.ventu (95.250.147.61) by smtp207.alice.it (8.6.060.28) (authenticated as acanedi@alice.it) id 59414648295286A0 for freebsd-questions@freebsd.org; Thu, 13 Jul 2017 09:37:42 +0200 Received: from alamar.ventu (alamar.local.netfence.it [10.1.2.18]) by soth.ventu (8.15.2/8.15.2) with ESMTP id v6D7beM6092832 for ; Thu, 13 Jul 2017 09:37:42 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.ventu: Host alamar.local.netfence.it [10.1.2.18] claimed to be alamar.ventu From: Andrea Venturoli Subject: Cleaning poudriere logs To: freebsd-questions@freebsd.org Message-ID: Date: Thu, 13 Jul 2017 09:37:40 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2017 07:37:50 -0000 Hello. Sorry if this is a FAQ (I searched and found no answer)... My Poudriere directory has reached 37GB, 29 of which are logs (dating back to when I started using this tool). How do I go about deleting these? In the man page I found that "poudriere bulk -c" will "Clean all previously built packages and logs", but I don't want to delete packages. I found no alternative command: is there one? Should I just delete the log dir? Or must I manually delete subdirectories within? bye & Thanks av. From owner-freebsd-questions@freebsd.org Thu Jul 13 13:03:03 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 21593DA1F33 for ; Thu, 13 Jul 2017 13:03:03 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from inet08.hamilton.harte-lyne.ca (inet08.hamilton.harte-lyne.ca [216.185.71.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "inet08.hamilton.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E4DB676CB4 for ; Thu, 13 Jul 2017 13:03:02 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from localhost (localhost [127.0.0.1]) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTP id D2820621F4; Thu, 13 Jul 2017 09:03:00 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from inet08.hamilton.harte-lyne.ca ([127.0.0.1]) by localhost (inet08.hamilton.harte-lyne.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q-63EeQs04Zh; Thu, 13 Jul 2017 09:02:58 -0400 (EDT) Received: from webmail.harte-lyne.ca (inet04.hamilton.harte-lyne.ca [216.185.71.24]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTPSA id 608FC6214A; Thu, 13 Jul 2017 09:02:58 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=harte-lyne.ca; s=dkim_hll; t=1499950978; bh=+UzBZHOB96qAby2ajtccXJvXaVqBwciynIed4aI1ZFI=; h=In-Reply-To:References:Date:Subject:From:To:Cc:Reply-To; b=ARq3KgbCWzrgPqBAG5Hd0OVIhQse4d8pYV0iKvkoSCEZ+e6jRMWXEqlC7vaICj+4Q aOX94AK/2yHX0N7RbNfd6LI88oS32eU0Lhq9YPfY3EBdalA/jm+kfBTeMAcfTz/Odv DnaSr2VMllfxer8oKg58n9uUPo4v63zGEOM7/C3IgeBzgcQ7bEhYtubigPZ5BHU4vB WZk14kPpuALO9mGEkau/LOEMmIG15+9VtgS7UmYb+wkI7HmFDXQvU6fkFBYt0nTSBQ bFQD0r8J9bvr2qeaC9UaYi/Crf86N89JvYWVllYuwo15DzX2eKReFOTnyzrA/PRbNS AjxAuL6YaxDaQ== Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Thu, 13 Jul 2017 09:02:58 -0400 Message-ID: In-Reply-To: References: Date: Thu, 13 Jul 2017 09:02:58 -0400 Subject: Re: A readers digest version of transferring a jail from one host to another. From: "James B. Byrne" To: "Kaya Saman" Cc: freebsd-questions@freebsd.org Reply-To: byrnejb@harte-lyne.ca User-Agent: SquirrelMail/1.4.22-5.el6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2017 13:03:03 -0000 On Wed, July 12, 2017 13:03, Kaya Saman wrote: > Just to chime in here quickly as I have had to do this too, however, > not using ezjail - forgive me if this has already been mentioned as > I've just caught the tail of the thread and of course don't want to > hijack anyone elses input... > > > For me I usually stop jail: > > /etc/rc.d/jail stop > > rsync -"flags" path/to/jail "rsync:"/new/path/to/jail > > > eg. rsync -avvc --progress --remove-source-files /jl/myjail > rsync://10.0.0.1:/jl/myjail > > > then start the new jail on host 10.0.0.1: /etc/rc.d/jail start myjail > > > this is an alternate as an FYI :-) > > > Regards, > > > Kaya > With ezjail one also needs to rsync, or otherwise create or transfer, the /usr/local/etc/ezjail/jailname file and modify it as required for the new host. Alternatively, given one uses zfs with ezjail then one can also snapshot and transfer the base and the configuration files. Again followed by local customisation of the /usr/local/etc/ezjail/jailname file on the target system. This was originally the path i thought to follow. However, for me the ezjail-admin archive and create options proved to be much simpler to use. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 From owner-freebsd-questions@freebsd.org Thu Jul 13 13:15:15 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2CCA2DA25E0; Thu, 13 Jul 2017 13:15:15 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward4o.cmail.yandex.net (forward4o.cmail.yandex.net [IPv6:2a02:6b8:0:1a72::289]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C1969776A4; Thu, 13 Jul 2017 13:15:14 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp2j.mail.yandex.net (smtp2j.mail.yandex.net [IPv6:2a02:6b8:0:801::ac]) by forward4o.cmail.yandex.net (Yandex) with ESMTP id C510220677; Thu, 13 Jul 2017 16:15:02 +0300 (MSK) Received: from smtp2j.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp2j.mail.yandex.net (Yandex) with ESMTP id DF3123EC0F75; Thu, 13 Jul 2017 16:15:00 +0300 (MSK) Received: by smtp2j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id Z9qNUibgxw-Ex0Sa5rQ; Thu, 13 Jul 2017 16:14:59 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1499951699; bh=lI4DhTat2PvGVy7CxSqDLMwksZ329a00wffknnl0l/U=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=soD35o8jNWNu/elsQYJljUo3jh9vTKLUP7SVx9Mfx4aVfQpb1PJAuqvOObstlD8vX rWokZmz3xiPu0IRcH+j70mwkXqE1AP+5Q61DnhtQKRkui0ttLbYAJdMXxzECQZIpFJ oyD5v5AdxCw4Ehv8PFeHrKW1bPgx4hIOXu6vdu5M= Authentication-Results: smtp2j.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-Suid-Status: 1 0,1 0,1 0 Subject: Re: Inter-VLAN routing on CURRENT: any known issues? To: "O. Hartmann" , FreeBSD CURRENT , FreeBSD Questions References: <20170712214334.4fc97335@thor.intern.walstatt.dynvpn.de> From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: Date: Thu, 13 Jul 2017 16:12:06 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: <20170712214334.4fc97335@thor.intern.walstatt.dynvpn.de> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="CueFjnWV1aGbTRKWeDcjoHWXWPmehqWKG" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2017 13:15:15 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --CueFjnWV1aGbTRKWeDcjoHWXWPmehqWKG Content-Type: multipart/mixed; boundary="Qo7f7gLTuFsLwUxFqH9iXR71pR9Qb4nOo"; protected-headers="v1" From: "Andrey V. Elsukov" To: "O. Hartmann" , FreeBSD CURRENT , FreeBSD Questions Message-ID: Subject: Re: Inter-VLAN routing on CURRENT: any known issues? References: <20170712214334.4fc97335@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20170712214334.4fc97335@thor.intern.walstatt.dynvpn.de> --Qo7f7gLTuFsLwUxFqH9iXR71pR9Qb4nOo Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 12.07.2017 22:43, O. Hartmann wrote: > Now the FUN PART: >=20 > From any host in any VLAN I'm able to ping hosts on the wild internet v= ia their IP, on > VLAN 1000 there is a DNS running, so I'm also able to resolv names like= google.com or > FreeBSD.org. But I can NOT(!) access any host via http/www or ssh.=20 You have not specified where is the NAT configured and its settings is matters. VLANs work on the layer2, they do not used for IP routing. Each received packet loses its layer2 header before it gets taken by IP stack. If an IP packet should be routed, the IP stack determines outgoing interface and new ethernet header with VLAN header from this interface is prepended= =2E What I would do in your place: 1. Check the correctness of the switch settings. - on the router use tcpdump on each vlan interface and also directly on igb1. Use -e argument to see ethernet header. Try ping router's IP address from each vlan, you should see tagged packet on igb1 and untagged on corresponding vlan interface. 2. Check the correctness of the routing settings for each used node. - to be able establish connection from one vlan to another, both nodes must have a route to each other. 3. Check the NAT settings. - to be able to connect to the Internet from your addresses, you must use NAT. If you don't have NAT, but it somehow works, this means that some device does the translation for you, but it's configuration does not meet to your requirements. And probably you need to translate prefixes configured for your vlans independently. --=20 WBR, Andrey V. Elsukov --Qo7f7gLTuFsLwUxFqH9iXR71pR9Qb4nOo-- --CueFjnWV1aGbTRKWeDcjoHWXWPmehqWKG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAllncaYACgkQAcXqBBDI oXqW8Af9EWg6ZQlYUzJNA1LrHwfidVi2IOlZz+Qs3sS3yi9LYXTTzG3zRQUXMihl eLrhUAvrS3ro7PRLPyJ5gkueb30WXKCs3ZVyx2KSHLqQAqNHNLuFhwhDrQiMEoBg IKNMinDa2YUSdTpEbH0+2VPsdrigtK69wglqr7LOJsn04KCJFx5Gj6krwFgXQYXe PCMiGwycRSbMWk9YwzNETmoD1/0JRJO4PfUOvasGSOm4DdSqLX2eF894CZScTp+o whxTM35yfbuKGZQkpSRifDJ0kJofSfsVdG8pfMDY7TRKyD5SrG5PyOSDebozOE7o X+M8ooNa7DHg3obdXmgJYe/TmA4dGg== =MKWA -----END PGP SIGNATURE----- --CueFjnWV1aGbTRKWeDcjoHWXWPmehqWKG-- From owner-freebsd-questions@freebsd.org Thu Jul 13 14:02:07 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7BD3DDA3873 for ; Thu, 13 Jul 2017 14:02:07 +0000 (UTC) (envelope-from steven_nikkel@ertyu.org) Received: from vmx.ertyu.org (vmx.ertyu.org [IPv6:2001:19f0:5c00:944f:5400:ff:fe1a:d00]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 514557947D for ; Thu, 13 Jul 2017 14:02:07 +0000 (UTC) (envelope-from steven_nikkel@ertyu.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ertyu.org; s=standard; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Date: Message-ID:Subject:From:To:Sender:Reply-To:Cc:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=UwJJTFuj4jwqO6eT56jTsjmCpG1smjk2sznGPyJm9A8=; b=dVqSufUTVXwVJlCJ/wb8EQdcHx WCJkH5g2vc4t5PlHFpRLd4rnr1UOm47J6DqduoEOgpgsNTXIGeD0wg472Ioq3Qfzfaf7yDkvvtiZx AxF3kOOVhjPKqL61OdliJOqFMmg6xKHh8PyDw2LQ5teFq4YhuRVlPZOa9pGVwanPGlMPmGG/hTOXk eGeKpvdzD1I215Pkj/2tY9BOhEBKdqgkduvjnHLUNpKaqWQeFNKBnuI3sZarcTBixWxEeR/rye2iI X0o6Tl3M/x5f6ojxPyw9g6akvum/hC6Ns7yT5rDEJnum1iA3dq3diiAEwn5R/JM9Znba8E5fDtfa1 GVQ45zFw==; To: freebsd-questions@freebsd.org From: Steven Nikkel Subject: OpenCL Issues Message-ID: Date: Thu, 13 Jul 2017 09:02:04 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2017 14:02:07 -0000 I've been trying to experiment with OpenCL but I just can't get it working. I've installed devel/ocl-icd and devel/clinfo. I installed lang/beignet on a system with Ivy Bridge graphics and loaded the i915kms module. On another system I used the lang/pocl driver instead. Whenever I try to use anything OpenCL I get a segfault. For example: # clinfo Number of platforms 1 Platform Name Intel Gen OCL Driver Platform Vendor Intel Platform Version OpenCL 1.2 beignet 1.3 Platform Profile FULL_PROFILE Platform Extensions cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_3d_image_writes cl_khr_image2d_from_buffer cl_khr_depth_images cl_khr_spir cl_khr_icd cl_intel_accelerator cl_intel_subgroups cl_intel_subgroups_short Platform Extensions function suffix Intel Segmentation fault (core dumped) #0 0x00000008025e5064 in drm_intel_bo_set_softpin_offset () from /usr/local/lib/libdrm_intel.so.1 #1 0x00000008018153bf in clGetProgramBuildInfo () from /usr/local/lib/beignet//libcl.so #2 0x0000000801814e68 in clGetProgramBuildInfo () from /usr/local/lib/beignet//libcl.so #3 0x000000080180caf7 in clBuildProgram () from /usr/local/lib/beignet//libcl.so #4 0x00000008018206a5 in process_extension_str () from /usr/local/lib/beignet//libcl.so #5 0x0000000801820860 in process_extension_str () from /usr/local/lib/beignet//libcl.so #6 0x000000080083498a in clGetDeviceIDs () from /usr/local/lib/libOpenCL.so.1 #7 0x0000000000401fac in ?? () #8 0x0000000000409827 in ?? () #9 0x000000000040150f in ?? () #10 0x000000080062f000 in ?? () #11 0x0000000000000000 in ?? () What am I missing or doing wrong? From owner-freebsd-questions@freebsd.org Thu Jul 13 14:17:13 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D2E9CDA3DD2 for ; Thu, 13 Jul 2017 14:17:13 +0000 (UTC) (envelope-from jgrosch@gmail.com) Received: from mail-pg0-x235.google.com (mail-pg0-x235.google.com [IPv6:2607:f8b0:400e:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A223679B17 for ; Thu, 13 Jul 2017 14:17:13 +0000 (UTC) (envelope-from jgrosch@gmail.com) Received: by mail-pg0-x235.google.com with SMTP id k14so30521441pgr.0 for ; Thu, 13 Jul 2017 07:17:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=Wl39PdHbW1f+EuhvYcgFv9z935FRWNCVUbktU8cuboA=; b=kHSvMY9qv2xu/dcR2df+26VOcYdifddo8XSEQ4vOwoScYmXSlaMctU7YUyf8ch3/Po +qfgFQk/pmWwzorX4nNp1oOVkQWWWvH6/oDNOzUdeYMN1VC9JrCq9rtwJJZIKPqLZx37 lk45Xpy4XPD4DPRPmtokK6+kHmSQcXwDBASHr/QdRi+tweP4zLEOcUBDDVHDyEuRwSTH x3bSjexnRmYl2D6l/mHl7azp4Cxj0Y2akLEqRgusUMjogqAhRj3pP7Nv/50ZQLACLtNK n5FElzvVrU9o70qLZPo22pHobcvwdJf/Nvai06em6h4hMBCnqp4Sj9vL3fsRHeO8XNRH Vm7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=Wl39PdHbW1f+EuhvYcgFv9z935FRWNCVUbktU8cuboA=; b=CQFT8XRjYSWTTTTFb1VRe8ZiVlDdyBVo4vZg111l6xpn0AYMLWCvKgVSXBLN39/pvl /DNeCrqIAuBBi5n3YtCNplJGtHdnaHvDgTPRP3UX/NXy8Ep8jjXT8anKyZVBGqsBuPZp zeMyurHaA7985DtB5V49ttusjCYBjzTN+73cNtLKO3tnk8204Wj9pX6kfqpdO3akuBNn Xn4Q7JNaLzx+LUEn2ZgaNbpUZTE+KyU+3GnFlc/fM2z944MbXMro+9JPYyqg8/rxgbFK kmPo4yVUKfxDm+GnGcR8NXoue+Lz3B4P+Ni7oE8xMIQXD1btl/yA+PrFRqC+MCbA2Xbz buCQ== X-Gm-Message-State: AIVw112ICi6nTu8wanze373zP3en1M4kPf8pdxCkWoUH6oKhKlh5ZaJk ZfdadZ6xaJ+Z15+lyaU= X-Received: by 10.84.217.7 with SMTP id o7mr10223725pli.156.1499955432824; Thu, 13 Jul 2017 07:17:12 -0700 (PDT) Received: from [192.168.1.175] (75-101-50-184.dsl.static.fusionbroadband.com. [75.101.50.184]) by smtp.googlemail.com with ESMTPSA id t11sm12400414pfi.66.2017.07.13.07.17.11 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 13 Jul 2017 07:17:12 -0700 (PDT) To: freebsd-questions@freebsd.org From: Josef Grosch Subject: FreeBSD related domins Message-ID: <6c81cd7a-f28c-9cab-b9f6-f34402eb39aa@gmail.com> Date: Thu, 13 Jul 2017 07:17:10 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2017 14:17:13 -0000 Greetings, Some of you might remember me, I was the co-founder of BAFUG (Bay Area FreeBSD Users Group) in San Francisco. While running BAFUG I registered a number of domains that related to both BAFUG and FreeBSD. I stepped away from BAFUG several years ago and I will not be renewing these domains. They are listed below; Domain Name Expiry Date ----------------------------------- babug.com Oct 10 2017 babug.net Mar 2 2018 bafug.com Jun 15 2018 bafug.net Jun 15 2018 bafug.org Dec 22 2017 bsd-counter.org Dec 10 2017 bsdcounter.org Dec 10 2017 freebsd-support.com Apr 18 2018 freebsd-support.net Oct 2 2017 freebsd-support.org Oct 2 2017 freebsdsupport.com Apr 17 2018 freebsdsupport.net Apr 17 2018 freebsdsupport.org Apr 17 2018 I will be happy to transfer any or all of these domains, for free, to anyone who is willing to take them and put them to good use. Josef -- Josef Grosch | Another day closer | jgrosch@gmail.com | to Redwood Heaven | Berkeley, Ca. From owner-freebsd-questions@freebsd.org Thu Jul 13 15:12:29 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE403DA4FF1 for ; Thu, 13 Jul 2017 15:12:29 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 16EAD7B782 for ; Thu, 13 Jul 2017 15:12:28 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id v6DFCH5T043615; Fri, 14 Jul 2017 01:12:18 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Fri, 14 Jul 2017 01:12:17 +1000 (EST) From: Ian Smith To: Doug Hardie cc: freebsd-questions@freebsd.org Subject: Re: Unusual Question In-Reply-To: Message-ID: <20170713231222.U20026@sola.nimnet.asn.au> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2017 15:12:30 -0000 In freebsd-questions Digest, Vol 684, Issue 3, Message: 5 On 12 Jul 2017 01:53:56 -0700 Doug Hardie wrote: > > On 9 July 2017, at 06:14, Ian Smith wrote: [..] > > # sysctl kern.geom.debugflags=16 > > > > purge at will. if=/dev/random for the more paranoid :) 'Scuse delay, just got this (remote) server back after 4 days down from a broken phone connection somewhere along a bush track .. fixed today. > Today was the experimentation. I had an old system here at the house > with 8.2 on it. So I started with a dd in=/dev/ada0 out=/dev/null to > find out how many blocks were on the device. Once I had that number, # gpart show ada0 | head -1 # is a quick way :) => 63 125045361 ada0 MBR (59G) > I then ran dd if=/dev/random of=/dev/ada0 skip= minus a few>. I typed oskip, but somehow the o didn't make it > through the keyboard. When it finished, I realized the error. There is no oskip; I have to check dd(1) every time myself .. there's: iseek=n Seek on the input file n blocks. This is synonymous with skip=n. oseek=n Seek on the output file n blocks. This is synonymous with seek=n. So yes, it skipped over Gigs of /dev/random, then wrote over all ada0. > So I had an install memstick for 11.0 and put it on as I wanted to > try camcontrol sanitize. Unfortunately, it reports an error > accessing my drive. I wonder if that also needs setting kern.geom.debugflags=16? ala geom(4)? > I then used dd if=/dev/ada0 skip= number> | od -c. > Then I wrote down the first few bytes of the output. They were > non-zero. I was a bit surprised by that since the last partition is > swap and it was never used. But perhaps that was left over from the > random write. Which would tend to indicate that the earlier dd ran to completion. I see no reason to suppose that it wouldn't have. > From here on I have pictures of the output. This is a > dumb terminal and I will attempt to enter in the data since the list > doesn't accept attachments. > > dd if=/dev/zero of=/dev/ada0 bs=32k > dd: /dev/ada0: short write on character device > dd: /dev/ada0: end of device > 2442211+0 records in > 2442210+1 records out > nnnn bytes transferred..... The 'short write' message is expected if the last output block != 32k > ls -l > > pwd > /bin/pwd: Exec format error. Binary file not executable. > who > /usr/bin/who: Exec format error. Binary file not executable. If you'd run pwd and who prior to clobbering the drive, they'd most likely be cached, and so available. You'll get the same effect if you remove and replace a memstick (or USB external drive) you booted off; what was cached in memory works, fresh disk accesses will fail, though mount still shows the mount existing. Pre-9.x or so it'd panic .. > dd if=/dev/ada0 skip=1000 count=5 | od -c > 0000000 \0 \0 \0 \0 ... > * > 0005000 > 5+0 records in > 5+0 records out > > dd if=/dev/ada0 skip=10000 count=500 | od -c > 0000000 \0 \0 \0 \0 ... > * > 0764000 > 500+0 records in > 500+0 records out > nnnn bytes transferred... > I didn't capture this but I did run the dd with the oskip of the big > number and it showed all zeros. There is no oskip. oseek (aka skip) would work. > I believe that dd, od and some of the current directory blocks were > still remaining in memory. However, the drive was definitely zapped. Yes, as indicated above. > It did write to the end of the drive. However, I suspect that if > something else was running during the dd and it tried to access the > drive things could have come to a halt before the zap completed. At It could, but unless it actually panic'd the box the dd should finish, i.e. just some other process/es crashing shouldn't interfere with it. > this point I tried to do a shutdown command and got the same Exec > format error. However, hitting the reset switch did cause a > shutdown. It seemed to be a normal shutdown as there were messages > on the console, but I was not expecting it to work and only saw them > for a brief second before the display was shut off. I think this sort of work - especially to a remote server - is safest done in single-user mode, either via boot menu, where available, or by 'shutdown now' from multi-user, with no daemons running that might want to write logs, or even to console over ssh where possible. See below. > I would like to have tried camcontrol sanitize as that appears to be > handled completely in the drive and controller. It would complete > regardless of what happened to the OS. I couldn't use it anyway on > the production systems as they are only at 8.3 and the sanitize > command was added in 11.0. It looks interesting, if slightly scary :) No 11.x here either. > Net result: I am not sure if the first production drive actually > completed the zap. It might have, but there is no way to tell. Well, when you reinstall something on that drive, you can inspect the end of the disk for zeroes - if that's what you wrote - or random data. If MBR formatted, nothing will (initially) write near the end, and if GPT, nothing except for the last 34 sectors having the secondary GPT. > However, it was not important as it does not hold any sensitive data. > It was tried first to see what would happen. I will make sure > nothing is running but sshd and dd when I do it on the critical > systems. I am considering starting the dd with a nohup and then > killing sshd before it gets very far. I think that has the best > possibility of completing properly. Yes, killing sshd early would be safest, but I'd start on a fresh boot, as (or dropped to) single-user, and stop services that log, notably nptd then syslogd at least. Pre-run commands you want to use, here likely just dd, to cache them. There's no reason any swap would be used after booting - it's not like you're running X or anything big - but you could run swapoff(8) to be sure. In my experience, FreeBSD fiercely caches everything it can in memory and is reluctant to swap out anyway, so I think those fears unfounded, though I think getting dd(1) to write more to console (thus, via ssh) would increase the odds of something getting wedged - in fact the dd option 'status=none' is likely worth considering. You might best run it/them from a little script, avoiding chances of fat-fingering .. maybe something like: #!/bin/sh # exterminate.sh :) service stop ntpd # add one for any others running service stop syslogd # avoid writes to /var/log etc dd if=/dev/zero of=/dev/null count=1 # prime dd; random if preferred (sleep 10 && \ dd if=/dev/zero of=/dev/ada0 bs=1m status=none 2>&1 >/dev/null) & service sshd stop sleep 3600 # well, it shouldn't take an hour .. echo "is anybody listening?" # uh-oh .. shutdown -p now # oh, it's all gone wrong .. I'm not even sure killing sshd is necessary, I think all its sockets and such would be cached, but it sure couldn't hurt. cheers, Ian From owner-freebsd-questions@freebsd.org Thu Jul 13 15:24:30 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 66038DA6616 for ; Thu, 13 Jul 2017 15:24:30 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CF29E7C0BF for ; Thu, 13 Jul 2017 15:24:29 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id v6DFOP4B043990; Fri, 14 Jul 2017 01:24:26 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Fri, 14 Jul 2017 01:24:25 +1000 (EST) From: Ian Smith To: Doug Hardie cc: freebsd-questions@freebsd.org Subject: Re: Unusual Question In-Reply-To: <20170713231222.U20026@sola.nimnet.asn.au> Message-ID: <20170714011941.C20026@sola.nimnet.asn.au> References: <20170713231222.U20026@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2017 15:24:30 -0000 On Fri, 14 Jul 2017 01:12:17 +1000, Ian Smith wrote: > There is no oskip; I have to check dd(1) every time myself .. there's: > iseek=n Seek on the input file n blocks. This is synonymous with > skip=n. > oseek=n Seek on the output file n blocks. This is synonymous with > seek=n. [..] > > I didn't capture this but I did run the dd with the oskip of the big > > number and it showed all zeros. > > There is no oskip. oseek (aka skip) would work. Argh .. I've done it myself: that should say oseek (aka seek). For this very reason I _never_ use iseek or oseek, being quite confused enough :) cheers, Ian From owner-freebsd-questions@freebsd.org Thu Jul 13 17:32:23 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CCB28DA98A4 for ; Thu, 13 Jul 2017 17:32:23 +0000 (UTC) (envelope-from friedrich.locke@gmail.com) Received: from mail-yb0-x22e.google.com (mail-yb0-x22e.google.com [IPv6:2607:f8b0:4002:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8054B810F0 for ; Thu, 13 Jul 2017 17:32:23 +0000 (UTC) (envelope-from friedrich.locke@gmail.com) Received: by mail-yb0-x22e.google.com with SMTP id n205so19513306yba.1 for ; Thu, 13 Jul 2017 10:32:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=l0V8wn1uiGpCADSpjh0fKm/se+kmQSQzvlMJdJ4YQUY=; b=kwrCNpYFpuaI/dRCVthngy2F1D81bOMHIPZy25rs6oCDGtqLJhQ29XRjNFvIMVEfxk FfcMFX/SOLoqyYlxzf9tbtnzjzGQ31spWNpi4436Z9hsdKAqtvpnDZ7brsPjvOPTHbMz HKA3zdZGrrL0qnw5Vi6HMPgpO9NQ3kKND3JIRWho4FWkYfjIacYe3V6iicXxFp+fXY4u VDKGRHou8NmzyaLFjaU6gvl/Bu7Adiv6Lm5TZ/6/gVGS9NUTujGkYusLHX+TnZoTuCye Ac4aukHTZyOMqMxESzWNha3Fy46nqWVy7vQStdu6F1O9aFI5CML+ja3U4dsp1P3BgfU5 8KuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=l0V8wn1uiGpCADSpjh0fKm/se+kmQSQzvlMJdJ4YQUY=; b=XmlIrBOa74xGyGqiOkN6bNTJb4WRy1dUNpLbqqzcj5GpqPejrSH1pVn1xG1Tn08RXG FYDlD1V8LnvSIHIqZfjq13ARdd+qWXPbjQRvOsLf/VmtOuARwDvFH1gAQdR/DDhTyuT4 ALDxhw7EQCQfKgc+Eby+z76pfqQgr+sRe/JdX3DwQHDEGD6YmPZq77nJnALtC4CTxSK2 lIYZz3gl0kmxnEHT6WmyrqVXbzCCc8NolJIWfdAABdFzeuDUiufM94vPbyQ1W6ldGQTZ Z9PSijnSctBbtek7mfW3o8T7g3lsMY1PtS+VmvzzF1owN7zMnWjXVFvSHuPnYam4gIbi 79nA== X-Gm-Message-State: AIVw113WYk2t5mzN0tNNbs39r0B1BTo4dvUC85msEo7jakTxbNtvsKB5 yO+/zjObUkkVG7oTCsexaLlbEUg4ua3Z X-Received: by 10.37.108.2 with SMTP id h2mr3770086ybc.241.1499967142387; Thu, 13 Jul 2017 10:32:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.177.146 with HTTP; Thu, 13 Jul 2017 10:32:22 -0700 (PDT) From: Friedrich Locke Date: Thu, 13 Jul 2017 14:32:22 -0300 Message-ID: Subject: what shoud i do ? To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2017 17:32:23 -0000 I am trying to get xdm insalled from ports. After a "make build" command i am getting: .... ... ... ===> Patching for xcb-proto-1.12 ===> Applying FreeBSD patches for xcb-proto-1.12 ===> xcb-proto-1.12 depends on file: /usr/local/bin/python2.7 - found ===> xcb-proto-1.12 depends on package: pkgconf>=1.3.0_1 - found ===> xcb-proto-1.12 depends on executable: xml2-config - not found ===> libxml2-2.9.4 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by libxml2-2.9.4 for building ===> Extracting for libxml2-2.9.4 => SHA256 Checksum OK for gnome2/libxml2-2.9.4.tar.gz. ===> Patching for libxml2-2.9.4 ===> Applying FreeBSD patches for libxml2-2.9.4 File to patch: The cursor get stopped waiting me to provide the file to patch. What should i type ? Thanks in advance. From owner-freebsd-questions@freebsd.org Thu Jul 13 18:24:25 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D872DAAE0D for ; Thu, 13 Jul 2017 18:24:25 +0000 (UTC) (envelope-from friedrich.locke@gmail.com) Received: from mail-yb0-x22d.google.com (mail-yb0-x22d.google.com [IPv6:2607:f8b0:4002:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5E1F884011 for ; Thu, 13 Jul 2017 18:24:25 +0000 (UTC) (envelope-from friedrich.locke@gmail.com) Received: by mail-yb0-x22d.google.com with SMTP id f194so22781950yba.3 for ; Thu, 13 Jul 2017 11:24:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=+7hZbtqtGtGo3LG0D15NS5dYCEl7NWjV7XDWezFLJ/M=; b=LX3TaLKUCCzZAtM7xU76v/QzxIF5XlvpCNp/+X0gtxaU4QH2uh2XT6FOuEL356COQB pyFsqHicqksuMfFQKSllGeUsuB9mkfTzB9+7SmTIQGOL8vg2/+SBT1oCHPasxIlvYZU3 9UZzxZQYPNxQu+Z3ZsDiMIh+CbARDEK0GbrzHT9FoWp46seOdlDlmz5Q8IP5QgCne1oY znCVxS4LS7JYyYeBn/i+XSpHJk4en9HAo2stBzvonnJhXBg1VjFF/WCQJvK1HRySv1L/ dq5NbC4vRWZ/3lndLZ9GOOjevwfeHttD9tfvRdp3YHYhVeD9Fe/jZixC3DOSpO/xqB+1 26lg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=+7hZbtqtGtGo3LG0D15NS5dYCEl7NWjV7XDWezFLJ/M=; b=kzTOpcrVmFjc7JC7EGt/cvocnfgtQG++0ZKmrSZpgVwjJ9VhIpb7KwZ9Ku3fHaohVr zyycygfj1D7CIyPBbq4oEnz69zF66NWIPBW0hASKPva1fJNP9sCFWhh4FIsiYp5EWjGY tKmsT9ACGUY2KHmxX7lt+/2/jZKJ8xy1tDqRN90ubvYnXJJcf6DT4Cz3FYuSqX8VovSB Cq5DTQWiIogQBySqHDBNTxlnICM+sYYiaAqNPgpZZJuUb7D6Qjc0cmqfy4+YihzJPfV1 d0CP1Fx0dO1az9ZSYsvxMD8ueCQlGR0WEqN1lV8MiiuxkDWyZhoq1TAR2AMyqzuyNHuE 0bSw== X-Gm-Message-State: AIVw110gAaxLQpG7l4F4LdRM9WyxW+PvfgyaZyUkToRwTXSM5geBdovv 4bpHQxJe5bsxcaIpkqFxc8Z1cnWMtQ== X-Received: by 10.37.108.2 with SMTP id h2mr3942212ybc.241.1499970264481; Thu, 13 Jul 2017 11:24:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.177.146 with HTTP; Thu, 13 Jul 2017 11:24:24 -0700 (PDT) From: Friedrich Locke Date: Thu, 13 Jul 2017 15:24:24 -0300 Message-ID: Subject: File to patch: To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2017 18:24:25 -0000 Why, in the name of God, that line (subject) appears when i want to build some application ? And more important: what to type in the keyboard for it ? Thanks. From owner-freebsd-questions@freebsd.org Thu Jul 13 19:06:26 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D1EBBDABB2B for ; Thu, 13 Jul 2017 19:06:26 +0000 (UTC) (envelope-from srs0=doeu=6q=mail.sermon-archive.info=doug@sermon-archive.info) Received: from mail.sermon-archive.info (sermon-archive.info [71.177.216.148]) by mx1.freebsd.org (Postfix) with ESMTP id BE41B859DF for ; Thu, 13 Jul 2017 19:06:26 +0000 (UTC) (envelope-from srs0=doeu=6q=mail.sermon-archive.info=doug@sermon-archive.info) Received: from [10.0.1.251] (mini [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 3x7lfN2zXvz2fk6Q; Thu, 13 Jul 2017 12:06:20 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Unusual Question From: Doug Hardie In-Reply-To: <20170714011941.C20026@sola.nimnet.asn.au> Date: Thu, 13 Jul 2017 12:06:20 -0700 Cc: "freebsd-questions@freebsd.org Questions" Content-Transfer-Encoding: quoted-printable Message-Id: <33484077-6ADF-489D-BB5A-27827393C41F@mail.sermon-archive.info> References: <20170713231222.U20026@sola.nimnet.asn.au> <20170714011941.C20026@sola.nimnet.asn.au> To: Ian Smith X-Mailer: Apple Mail (2.3273) X-Virus-Scanned: clamav-milter 0.99.2 at mail X-Virus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2017 19:06:26 -0000 > On 13 July 2017, at 08:24, Ian Smith wrote: >=20 > On Fri, 14 Jul 2017 01:12:17 +1000, Ian Smith wrote: >=20 >> There is no oskip; I have to check dd(1) every time myself .. = there's: >> iseek=3Dn Seek on the input file n blocks. This is synonymous = with >> skip=3Dn. >> oseek=3Dn Seek on the output file n blocks. This is synonymous = with >> seek=3Dn. > [..] >>> I didn't capture this but I did run the dd with the oskip of the big=20= >>> number and it showed all zeros. >>=20 >> There is no oskip. oseek (aka skip) would work. >=20 > Argh .. I've done it myself: that should say oseek (aka seek). For = this=20 > very reason I _never_ use iseek or oseek, being quite confused enough = :) >=20 > cheers, Ian Yes oskip should have been oseek. I didn't have access to the actual = screen or man page when writing that all down. I previously set = kern.geom.debugflags=3D16. The system here is very old and i386 only. = I may play with that again if time permits.= From owner-freebsd-questions@freebsd.org Thu Jul 13 20:24:34 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F35DDAD34F for ; Thu, 13 Jul 2017 20:24:34 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-in6.apple.com (mail-out6.apple.com [17.151.62.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 388F02E17 for ; Thu, 13 Jul 2017 20:24:33 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay2.apple.com (relay2.apple.com [17.128.113.67]) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail-in6.apple.com (Apple Secure Mail Relay) with SMTP id 3D.6F.06961.BF6D7695; Thu, 13 Jul 2017 13:24:27 -0700 (PDT) X-AuditID: 11973e15-9dace9c000001b31-ae-5967d6fbf1f6 Received: from [17.150.210.232] (Unknown_Domain [17.150.210.232]) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by relay2.apple.com (Apple SCV relay) with SMTP id AE.4E.09069.BF6D7695; Thu, 13 Jul 2017 13:24:27 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: File to patch: From: Chuck Swiger In-Reply-To: Date: Thu, 13 Jul 2017 13:24:27 -0700 Cc: FreeBSD - Content-Transfer-Encoding: quoted-printable Message-Id: <0F77DFE4-242D-4294-9377-5260EC57403E@mac.com> References: To: Friedrich Locke X-Mailer: Apple Mail (2.3273) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrILMWRmVeSWpSXmKPExsUi2FDorPv7Wnqkwcv1FhYvv25isZjz/hmr A5PHjE/zWTx2zrrLHsAUxWWTkpqTWZZapG+XwJVxaNcf5oJdbBXrtyxhbGBsYe1i5OSQEDCR WH7uBjuILSSwmkli27tcmHj7g2tMXYxcQPEFTBJdD9tZQBLMAloSN/69BEpwcPAK6Ev0PmcE CQsLSEt8O/oSrIRNQEVi8az/zCA2p0CgxI1jH8B2sQioSqzaOZEZYoyuRNONt4wQtrbEsoWv weK8AlYSHxbthLonQOJs40mwGhGgVXvebmaGuE1W4tbsS8wgt0kIvGSVuD33GOsERsFZSM6b hXDeLCQrFjAyr2IUyk3MzNHNzDPTSywoyEnVS87P3cQICtPpdqI7GM+ssjrEKMDBqMTD+2Ni eqQQa2JZcWXuIUZpDhYlcd7U0rRIIYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYwrGqx6/pUW 2wusDfcqnTLdUDJ92w/FGtajcqFBN5ILJP0fr71ZO7Nzb9CulPvXn9v1n2/NflPwoV7kkU/5 BLmKkJg/pyZO3vXKxFE3Y9f0u9vePA1a8ik9YPEvP4ZX+n/atauUlacs3qTCd+mxn89p9Zyg y9yehTEvalmqRTasljH7wjHheLcSS3FGoqEWc1FxIgDwpV8YNAIAAA== X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprKLMWRmVeSWpSXmKPExsUiOO3SC93f19IjDTZ1m1q8/LqJxWLO+2es DkweMz7NZ/HYOesuewBTFJdNSmpOZllqkb5dAlfGoV1/mAt2sVWs37KEsYGxhbWLkZNDQsBE ov3BNaYuRi4OIYEFTBJdD9tZQBLMAloSN/69BEpwcPAK6Ev0PmcECQsLSEt8O/oSrIRNQEVi 8az/zCA2p0CgxI1jH8BmsgioSqzaOZEZYoyuRNONt4wQtrbEsoWvweK8AlYSHxbtZAexhQQC JM42ngSrEQFateftZmaI22Qlbs2+xDyBkW8WkotmIVw0C8nUBYzMqxgFilJzEiuN9BILCnJS 9ZLzczcxggKrodB5B+OxZVaHGAU4GJV4eAOmpEcKsSaWFVfmHmKU4GBWEuH9chgoxJuSWFmV WpQfX1Sak1p8iFGag0VJnNeELzZSSCA9sSQ1OzW1ILUIJsvEwSnVwJhZc1715FxB55/6fEbz As8pxk8s1j98V+mwQFxwH5fzFFt1xVXcR7PaeWY8Wr4nYu52i2oHt2OVletn1Amd4Tf5srh4 cmlv34/o82fY9MUkLj3s8Joh8WF3yq0T9z5NevvBROSAqNbTqGWnDeJkHjtlfs+50u3YxJy0 9UTP5k8iageuN2/6U6DEUpyRaKjFXFScCADQrO0fKAIAAA== X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2017 20:24:34 -0000 On Jul 13, 2017, at 11:24 AM, Friedrich Locke = wrote: > Why, in the name of God, that line (subject) appears when i want to = build > some application ? The literal answer is that something ran the patch command against a = diff, but patch cannot find the file(s) it expected to update. > And more important: what to type in the keyboard for it ? Control-C...? While it is possible to enter a diff by hand, the odds approach 100% = that if you do not already know what to change, what you really want to do is cancel and then make sure your ports tree (or whatever it is you are = building) is up-to-date and does not have stale/outdated diffs lingering in the = way. You'll need to provide more details if you want more specific feedback. Regards, --=20 -Chuck From owner-freebsd-questions@freebsd.org Fri Jul 14 00:14:22 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F3419DB13FD for ; Fri, 14 Jul 2017 00:14:22 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay11.qsc.de (mailrelay11.qsc.de [212.99.187.252]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 660ED6E2BF for ; Fri, 14 Jul 2017 00:14:21 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay11.qsc.de; Fri, 14 Jul 2017 02:14:12 +0200 Received: from r56.edvax.de (port-92-195-91-60.dynamic.qsc.de [92.195.91.60]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id E4D7D3CBF9; Fri, 14 Jul 2017 02:14:10 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v6E0EADr001995; Fri, 14 Jul 2017 02:14:10 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Fri, 14 Jul 2017 02:14:10 +0200 From: Polytropon To: Friedrich Locke Cc: freebsd-questions@freebsd.org Subject: Re: what shoud i do ? Message-Id: <20170714021410.f91d606d.freebsd@edvax.de> In-Reply-To: References: Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay11.qsc.de with 39FAD6A3F7F X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1332 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 00:14:23 -0000 On Thu, 13 Jul 2017 14:32:22 -0300, Friedrich Locke wrote: > I am trying to get xdm insalled from ports. > > After a "make build" command i am getting: > > > .... > ... > ... > ===> Patching for xcb-proto-1.12 > ===> Applying FreeBSD patches for xcb-proto-1.12 > ===> xcb-proto-1.12 depends on file: /usr/local/bin/python2.7 - found > ===> xcb-proto-1.12 depends on package: pkgconf>=1.3.0_1 - found > ===> xcb-proto-1.12 depends on executable: xml2-config - not found > ===> libxml2-2.9.4 depends on file: /usr/local/sbin/pkg - found > ===> Fetching all distfiles required by libxml2-2.9.4 for building > ===> Extracting for libxml2-2.9.4 > => SHA256 Checksum OK for gnome2/libxml2-2.9.4.tar.gz. > ===> Patching for libxml2-2.9.4 > ===> Applying FreeBSD patches for libxml2-2.9.4 > File to patch: > > > The cursor get stopped waiting me to provide the file to patch. What should > i type ? Use Ctrl+D to terminate input, or Ctrl+C to stop the operation here. It seems that a patch file is damaged - patch file itself usually contains the information _which_ source file to patch _how_ (diff). Try the following: Run "make clean" and update your ports tree (for example with portsnap), then run a normal "make" again; "make" will execute all steps needed until installation time (like "make fetch", "make extract", or "make patch"). In worst case, use "pkg install xdm". ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Fri Jul 14 04:48:31 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 850F6D947CA for ; Fri, 14 Jul 2017 04:48:31 +0000 (UTC) (envelope-from dpchrist@holgerdanske.com) Received: from holgerdanske.com (holgerdanske.com [184.105.128.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "holgerdanske.com", Issuer "holgerdanske.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6DA607C05E for ; Fri, 14 Jul 2017 04:48:31 +0000 (UTC) (envelope-from dpchrist@holgerdanske.com) Received: from 99.100.19.101 ([99.100.19.101]) by holgerdanske.com with ESMTPSA (ECDHE-RSA-AES128-GCM-SHA256:TLSv1.2:Kx=ECDH:Au=RSA:Enc=AESGCM(128):Mac=AEAD) (SMTP-AUTH username dpchrist@holgerdanske.com, mechanism PLAIN) for ; Thu, 13 Jul 2017 21:44:31 -0700 Subject: Re: Unusual Question To: freebsd-questions@freebsd.org References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> From: David Christensen Message-ID: Date: Thu, 13 Jul 2017 21:44:30 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 04:48:31 -0000 On 07/09/17 02:57, Doug Hardie wrote: > I have a FreeBSD 9.3 remote server that needs to be purged. I know that rm -rf / will remove all the directory entries, but I need to write over the drive. I thought that dd if=/dev/zero of=/dev/ada0 might do the trick, but it gives an not permitted error. The whole thing can crash and burn at the end. This is an unmanned site so moving drives is not viable. If the machine has BIOS and the system drive isn't too large, write an assembly program that fits into the MBR bootstrap code area to wipe the rest of the drive, assemble the program, write it into the MBR, and reboot. Bonus: the program deletes the MBR when done wiping the rest of the drive. David From owner-freebsd-questions@freebsd.org Fri Jul 14 06:11:43 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27C09D96002 for ; Fri, 14 Jul 2017 06:11:43 +0000 (UTC) (envelope-from srs0=kjah=6r=mail.sermon-archive.info=doug@sermon-archive.info) Received: from mail.sermon-archive.info (sermon-archive.info [71.177.216.148]) by mx1.freebsd.org (Postfix) with ESMTP id 087E67E020 for ; Fri, 14 Jul 2017 06:11:42 +0000 (UTC) (envelope-from srs0=kjah=6r=mail.sermon-archive.info=doug@sermon-archive.info) Received: from [10.0.1.251] (mini [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 3x82Q52flbz2fkCV; Thu, 13 Jul 2017 23:11:41 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Unusual Question From: Doug Hardie In-Reply-To: Date: Thu, 13 Jul 2017 23:11:41 -0700 Cc: freebsd-questions@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> To: David Christensen X-Mailer: Apple Mail (2.3273) X-Virus-Scanned: clamav-milter 0.99.2 at mail X-Virus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 06:11:43 -0000 > On 13 July 2017, at 21:44, David Christensen = wrote: >=20 > On 07/09/17 02:57, Doug Hardie wrote: >> I have a FreeBSD 9.3 remote server that needs to be purged. I know = that rm -rf / will remove all the directory entries, but I need to write = over the drive. I thought that dd if=3D/dev/zero of=3D/dev/ada0 might = do the trick, but it gives an not permitted error. The whole thing can = crash and burn at the end. This is an unmanned site so moving drives is = not viable. >=20 > If the machine has BIOS and the system drive isn't too large, write an = assembly program that fits into the MBR bootstrap code area to wipe the = rest of the drive, assemble the program, write it into the MBR, and = reboot. >=20 >=20 > Bonus: the program deletes the MBR when done wiping the rest of the = drive. Neat idea, but I have a number of these systems and they all use = different disk drives. That would be a lot of work writing drivers for = each type. From owner-freebsd-questions@freebsd.org Fri Jul 14 07:37:33 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 620E8D9941D for ; Fri, 14 Jul 2017 07:37:33 +0000 (UTC) (envelope-from willsznet@gmail.com) Received: from mail-pg0-x243.google.com (mail-pg0-x243.google.com [IPv6:2607:f8b0:400e:c05::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1F00B7FED8 for ; Fri, 14 Jul 2017 07:37:33 +0000 (UTC) (envelope-from willsznet@gmail.com) Received: by mail-pg0-x243.google.com with SMTP id j186so9733498pge.1 for ; Fri, 14 Jul 2017 00:37:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:organization:message-id:mime-version :content-transfer-encoding:thread-index:content-language; bh=7+Eo377kmHItKeyLMLxrV1fgc7sHn41C3zwyTOpcxoM=; b=qqML3tkL689VMo9l6ZgJ1XrfZGlQ5Wg6+fByYoCOfc8OZ7+bI5p2bflP75XU0eEVsj HxdyOXnMF8iybrW51ADqt690ibQn4adoVBu6f6iSrSbBnBh4CrQU060FoCHeXURYsip+ qOCnSxYDtH1Z9R66J3hoXF/XtaweeMLd/PogovHnGdsPC8/FfUPn/cRyoBAvXmIi6Buc IavxY1MEaJBnlBUWf19E/wDbEPVZKYBodV7wHfXdPnLSTH6aAXZqSO9TnyVVlyrPwV7g 443p95y67sKSK9f05ieLRdwzZfE8PO2E8uVT6334+PIyQLj6ckaxxL5F6xKlSh+4oqfO CHHw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:organization:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=7+Eo377kmHItKeyLMLxrV1fgc7sHn41C3zwyTOpcxoM=; b=SvXZDt0M4cDWwTiFbIgFZfAZ7hH1qqaCPCKoAX/z+FOhI8pemI3wMg1H0ZlksGC1AE mS/5+f5gkUUu+B00x9vjZCyoytWNCCLIglvLKtg4oYZ1vibFHSgSK7ocnl/2gNITNmcI 3wZXTfef86hn7iVl1C5MLUkhDu3sm9ggMYYV4dn91VDskcZNv+znUiB3UvKoyriOeyxQ y52iVdOzPaTFPl9FFKwMIwf6ALYUih1AbUKGzEJDL2EUshq64ipUu5+yOgqrwC7LNvi1 f5qT8fmY8NShHVPUq7ICZ+OevtJSy69qWc+ylIv/z5KJgiikxYPYqo2A0Tm7Z1QZOmMm eoQQ== X-Gm-Message-State: AIVw112vZTQYcsHTr9lrhLB21fuc1X3OUwU1OHbqgbLSdumfThGYrc6E 8a9IwOr82m36cTQw X-Received: by 10.98.63.91 with SMTP id m88mr3812996pfa.193.1500017852074; Fri, 14 Jul 2017 00:37:32 -0700 (PDT) Received: from pcbill ([180.253.251.227]) by smtp.gmail.com with ESMTPSA id d18sm22675946pgn.27.2017.07.14.00.37.29 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 14 Jul 2017 00:37:31 -0700 (PDT) From: "Willsz.net" To: Subject: make buildworld problem. Date: Fri, 14 Jul 2017 14:37:38 +0700 Organization: Willsz.net - Cyber Internet Station Message-ID: <001201d2fc74$136a86c0$3a3f9440$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdL8dBAOl2bnZlyRTxWrrhX0hrGZ0w== Content-Language: id x-cr-hashedpuzzle: AMVI AmQ0 B5y+ B+8l CHnc CItt Ed8Y Hm6E JJ56 JaRs KAe3 Kk1V Kp27 LQ9V LcqL Lk89; 1; ZgByAGUAZQBiAHMAZAAtAHEAdQBlAHMAdABpAG8AbgBzAEAAZgByAGUAZQBiAHMAZAAuAG8AcgBnAA==; Sosha1_v1; 7; {7182394F-E4CF-4025-B7F6-E1F62055847A}; dwBpAGwAbABzAHoAbgBlAHQAQABnAG0AYQBpAGwALgBjAG8AbQA=; Fri, 14 Jul 2017 07:37:36 GMT; bQBhAGsAZQAgAGIAdQBpAGwAZAB3AG8AcgBsAGQAIABwAHIAbwBiAGwAZQBtAC4A x-cr-puzzleid: {7182394F-E4CF-4025-B7F6-E1F62055847A} X-Antivirus: Avast (VPS 170713-6, 07/13/2017), Outbound message X-Antivirus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 07:37:33 -0000 Hi, I already failed to make buildworld last night. root:~ # uname -srm FreeBSD 10.3-STABLE i386 root:~# mv /usr/src /usr/src.old root:~# mkdir /usr/src root:~# svn checkout svn://svn.FreeBSD.org/base/stable/10 /usr/src root:~# svn info /usr/src Path: /usr/src Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/stable/10 Relative URL: ^/stable/10 Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 320980 Node Kind: directory Schedule: normal Last Changed Author: gjb Last Changed Rev: 320950 Last Changed Date: 2017-07-13 23:18:46 +0700 (Thu, 13 Jul 2017) root:~# cd /usr/src/ root:/usr/src# make buildworld Script started on Fri Jul 14 14:22:21 2017 root:/usr/src# make buildworld Script started on Fri Jul 14 14:22:21 2017 root:/usr/src# make buildworld -------------------------------------------------------------- >>> World build started on Fri Jul 14 14:22:27 WIB 2017 -------------------------------------------------------------- -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- rm -rf /usr/obj/usr/src/tmp mkdir -p /usr/obj/usr/src/tmp/lib mkdir -p /usr/obj/usr/src/tmp/usr mkdir -p /usr/obj/usr/src/tmp/legacy/bin mkdir -p /usr/obj/usr/src/tmp/legacy/usr mtree -deU -f /usr/src/etc/mtree/BSD.usr.dist -p /usr/obj/usr/src/tmp/legacy/usr >/dev/null mtree -deU -f /usr/src/etc/mtree/BSD.groff.dist -p /usr/obj/usr/src/tmp/legacy/usr >/dev/null mtree -deU -f /usr/src/etc/mtree/BSD.usr.dist -p /usr/obj/usr/src/tmp/usr >/dev/null mtree -deU -f /usr/src/etc/mtree/BSD.include.dist -p /usr/obj/usr/src/tmp/usr/include >/dev/null ln -sf /usr/src/sys /usr/obj/usr/src/tmp -------------------------------------------------------------- >>> stage 1.1: legacy release compatibility shims -------------------------------------------------------------- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/tmp INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bi n:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/legacy/bin:/sbi n:/bin:/usr/sbin:/usr/bin WORLDTMP=/usr/obj/usr/src/tmp VERSION="FreeBSD 10.3-STABLE i386 1003514" MAKEFLAGS="-m /usr/src/tools/build/mk -m /usr/src/share/mk" COMPILER_TYPE=clang make -f Makefile.inc1 DESTDIR= BOOTSTRAPPING=1003514 SSP_CFLAGS= -DWITHOUT_HTML -DWITHOUT_INFO -DNO_LINT -DWITHOUT_MAN -DNO_PIC -DNO_PROFILE -DNO_SHARED _BOOTSTRAP_MAKEINFO=yes -DNO_CPU_CFLAGS -DNO_WARNS -DNO_CTF -DEARLY_BUILD -DNO_TESTS legacy ===> tools/build (obj,includes,depend,all,install) /usr/obj/usr/src/tmp/usr/src/tools/build created for /usr/src/tools/build cd /usr/src/tools/build; make buildincludes; make installincludes rm -f .depend mkdep -f .depend -a -I/usr/src/tools/build/../../contrib/libc-pwcache -I/usr/src/tools/build/../../lib/libc/include -I/usr/obj/usr/src/tmp/legacy/usr/include -std=gnu99 /usr/src/tools/build/../../contrib/libc-pwcache/pwcache.c cc -O2 -pipe -I/usr/src/tools/build/../../contrib/libc-pwcache -I/usr/src/tools/build/../../lib/libc/include -std=gnu99 -I/usr/obj/usr/src/tmp/legacy/usr/include -c /usr/src/tools/build/../../contrib/libc-pwcache/pwcache.c -o pwcache.o building static egacy library ranlib -D libegacy.a sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libegacy.a /usr/obj/usr/src/tmp/legacy/usr/lib -------------------------------------------------------------- >>> stage 1.2: bootstrap tools -------------------------------------------------------------- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/tmp INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bi n:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/legacy/bin:/sbi n:/bin:/usr/sbin:/usr/bin WORLDTMP=/usr/obj/usr/src/tmp VERSION="FreeBSD 10.3-STABLE i386 1003514" MAKEFLAGS="-m /usr/src/tools/build/mk -m /usr/src/share/mk" COMPILER_TYPE=clang make -f Makefile.inc1 DESTDIR= BOOTSTRAPPING=1003514 SSP_CFLAGS= -DWITHOUT_HTML -DWITHOUT_INFO -DNO_LINT -DWITHOUT_MAN -DNO_PIC -DNO_PROFILE -DNO_SHARED _BOOTSTRAP_MAKEINFO=yes -DNO_CPU_CFLAGS -DNO_WARNS -DNO_CTF -DEARLY_BUILD -DNO_TESTS bootstrap-tools ===> lib/clang/libllvmsupport (obj,depend,all,install) /usr/obj/usr/src/tmp/usr/src/lib/clang/libllvmsupport created for /usr/src/lib/clang/libllvmsupport rm -f .depend mkdep -f .depend -a -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/includ e -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support -I. -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/in clude -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DNDEBUG -DLLVM_DEFAULT_TARGET_TRIPLE=\"i386-unknown-freebsd10.3\" -DLLVM_HOST_TRIPLE=\"i386-unknown-freebsd10.3\" -DDEFAULT_SYSROOT=\"\" -I/usr/obj/usr/src/tmp/legacy/usr/include -std=gnu99 /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/ConvertU TF.c /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/regcomp. c /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/regerror .c /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/regexec. c /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/regfree. c /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/regstrlc py.c mkdep -f .depend -a -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/includ e -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support -I. -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/in clude -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DNDEBUG -DLLVM_DEFAULT_TARGET_TRIPLE=\"i386-unknown-freebsd10.3\" -DLLVM_HOST_TRIPLE=\"i386-unknown-freebsd10.3\" -DDEFAULT_SYSROOT=\"\" -I/usr/obj/usr/src/tmp/legacy/usr/include /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/APFloat. cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/APInt.cp p /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/APSInt.c pp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Allocato r.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Atomic.c pp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/BlockFre quency.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/BranchPr obability.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/CommandL ine.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Constant Range.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/ConvertU TFWrapper.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/CrashRec overyContext.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/DAGDelta Algorithm.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/DataExtr actor.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Debug.cp p /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/DeltaAlg orithm.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Dwarf.cp p /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/DynamicL ibrary.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Errno.cp p /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/ErrorHan dling.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/FileOutp utBuffer.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/FoldingS et.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Formatte dStream.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/GraphWri ter.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Hashing. cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Host.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/IncludeF ile.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/IntEqCla sses.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Interval Map.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Intrusiv eRefCntPtr.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/IsInf.cp p /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/IsNAN.cp p /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Locale.c pp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/LockFile Manager.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/MD5.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/ManagedS tatic.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Memory.c pp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/MemoryBu ffer.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/MemoryOb ject.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Mutex.cp p /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Path.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/PluginLo ader.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/PrettySt ackTrace.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Process. cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Program. cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/RWMutex. cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Regex.cp p /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/SearchFo rAddressOfSpecialSymbol.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Signals. cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/SmallPtr Set.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/SmallVec tor.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/SourceMg r.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Statisti c.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Streamab leMemoryObject.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/StringEx tras.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/StringMa p.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/StringPo ol.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/StringRe f.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/StringRe fMemoryObject.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/TargetRe gistry.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/ThreadLo cal.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Threadin g.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/TimeValu e.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Timer.cp p /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/ToolOutp utFile.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Triple.c pp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Twine.cp p /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Unicode. cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Valgrind .cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Watchdog .cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/YAMLPars er.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/YAMLTrai ts.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/circular _raw_ostream.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/raw_os_o stream.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/raw_ostr eam.cpp /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/system_e rror.cpp c++ -O2 -pipe -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/includ e -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support -I. -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/in clude -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DNDEBUG -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\"i386-unknown-freebsd10.3\" -DLLVM_HOST_TRIPLE=\"i386-unknown-freebsd10.3\" -DDEFAULT_SYSROOT=\"\" -ffunction-sections -fdata-sections -I/usr/obj/usr/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/APFloat. cpp -o APFloat.o In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/APFloat. cpp:15: In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/ADT/APF loat.h:20: In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/ADT/API nt.h:19: In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/ADT/Arr ayRef.h:14: In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/ADT/Sma llVector.h:17: In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/Support /AlignOf.h:19: In file included from /usr/include/c++/v1/cstddef:38: In file included from /usr/include/c++/v1/stddef.h:51: 1m/usr/include/c++/v1/__nullptr:24:29: 0m0;1;31merror: 0m1mvariable has incomplete type 'struct _LIBCPP_TEMPLATE_VIS'0m struct _LIBCPP_TEMPLATE_VIS nullptr_t 0;1;32m ^ 0m1m/usr/include/c++/v1/__nullptr:24:8: 0m0;1;30mnote: 0mforward declaration of 'std::__1::_LIBCPP_TEMPLATE_VIS'0m struct _LIBCPP_TEMPLATE_VIS nullptr_t 0;1;32m ^ 0m1m/usr/include/c++/v1/__nullptr:24:38: 0m0;1;31merror: 0m1mexpected ';' after top level declarator0m struct _LIBCPP_TEMPLATE_VIS nullptr_t 0;1;32m ^ 0m1m/usr/include/c++/v1/__nullptr:47:48: 0m0;1;31merror: 0m1munknown type name 'nullptr_t'0m inline _LIBCPP_ALWAYS_INLINE _LIBCPP_CONSTEXPR nullptr_t __get_nullptr_t() {return nullptr_t(0);} 0;1;32m ^ 0mIn file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/APFloat. cpp:15: In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/ADT/APF loat.h:20: In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/ADT/API nt.h:19: In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/ADT/Arr ayRef.h:14: In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/ADT/Sma llVector.h:19: In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/Support /MathExtras.h:18: In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/Support /SwapByteOrder.h:18: In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/incl ude/llvm/Support/DataTypes.h:36: In file included from /usr/include/c++/v1/cmath:301: In file included from /usr/include/c++/v1/math.h:309: 1m/usr/include/c++/v1/type_traits:472:114: 0m0;1;31merror: 0m1mexpected class name0m ...sizeof(__libcpp_is_member_function_pointer_imp::__test<_Tp>(nullptr)) == 1> {}; 0;1;32m ^ 0mIn file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/APFloat. cpp:15: In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/ADT/APF loat.h:20: In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/ADT/API nt.h:19: In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/ADT/Arr ayRef.h:14: In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/ADT/Sma llVector.h:19: In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/Support /MathExtras.h:18: In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/Support /SwapByteOrder.h:18: In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/incl ude/llvm/Support/DataTypes.h:36: 1m/usr/include/c++/v1/cmath:679:46: 0m0;1;31merror: 0m1mdeclaration conflicts with target of using declaration already in scope0m inline _LIBCPP_INLINE_VISIBILITY float acos(float __lcpp_x) _NOEXCEPT {return acosf(__lcpp_x);} 0;1;32m ^ 0m1m/usr/include/c++/v1/math.h:654:46: 0m0;1;30mnote: 0mtarget of using declaration0m inline _LIBCPP_INLINE_VISIBILITY float acos(float __lcpp_x) _NOEXCEPT {return acosf(__lcpp_x);} 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:675:9: 0m0;1;30mnote: 0musing declaration0m using ::acos; 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:680:46: 0m0;1;31merror: 0m1mdeclaration conflicts with target of using declaration already in scope0m inline _LIBCPP_INLINE_VISIBILITY long double acos(long double __lcpp_x) _NOEXCEPT {return acosl(__lcpp_x);} 0;1;32m ^ 0m1m/usr/include/c++/v1/math.h:655:46: 0m0;1;30mnote: 0mtarget of using declaration0m inline _LIBCPP_INLINE_VISIBILITY long double acos(long double __lcpp_x) _NOEXCEPT {return acosl(__lcpp_x);} 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:675:9: 0m0;1;30mnote: 0musing declaration0m using ::acos; 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:686:1: 0m0;1;31merror: 0m1mdeclaration conflicts with target of using declaration already in scope0m acos(_A1 __lcpp_x) _NOEXCEPT {return acos((double)__lcpp_x);} 0;1;32m^ 0m1m/usr/include/c++/v1/math.h:661:1: 0m0;1;30mnote: 0mtarget of using declaration0m acos(_A1 __lcpp_x) _NOEXCEPT {return acos((double)__lcpp_x);} 0;1;32m^ 0m1m/usr/include/c++/v1/cmath:675:9: 0m0;1;30mnote: 0musing declaration0m using ::acos; 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:694:46: 0m0;1;31merror: 0m1mdeclaration conflicts with target of using declaration already in scope0m inline _LIBCPP_INLINE_VISIBILITY float asin(float __lcpp_x) _NOEXCEPT {return asinf(__lcpp_x);} 0;1;32m ^ 0m1m/usr/include/c++/v1/math.h:666:46: 0m0;1;30mnote: 0mtarget of using declaration0m inline _LIBCPP_INLINE_VISIBILITY float asin(float __lcpp_x) _NOEXCEPT {return asinf(__lcpp_x);} 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:690:9: 0m0;1;30mnote: 0musing declaration0m using ::asin; 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:695:46: 0m0;1;31merror: 0m1mdeclaration conflicts with target of using declaration already in scope0m inline _LIBCPP_INLINE_VISIBILITY long double asin(long double __lcpp_x) _NOEXCEPT {return asinl(__lcpp_x);} 0;1;32m ^ 0m1m/usr/include/c++/v1/math.h:667:46: 0m0;1;30mnote: 0mtarget of using declaration0m inline _LIBCPP_INLINE_VISIBILITY long double asin(long double __lcpp_x) _NOEXCEPT {return asinl(__lcpp_x);} 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:690:9: 0m0;1;30mnote: 0musing declaration0m using ::asin; 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:701:1: 0m0;1;31merror: 0m1mdeclaration conflicts with target of using declaration already in scope0m asin(_A1 __lcpp_x) _NOEXCEPT {return asin((double)__lcpp_x);} 0;1;32m^ 0m1m/usr/include/c++/v1/math.h:673:1: 0m0;1;30mnote: 0mtarget of using declaration0m asin(_A1 __lcpp_x) _NOEXCEPT {return asin((double)__lcpp_x);} 0;1;32m^ 0m1m/usr/include/c++/v1/cmath:690:9: 0m0;1;30mnote: 0musing declaration0m using ::asin; 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:709:46: 0m0;1;31merror: 0m1mdeclaration conflicts with target of using declaration already in scope0m inline _LIBCPP_INLINE_VISIBILITY float atan(float __lcpp_x) _NOEXCEPT {return atanf(__lcpp_x);} 0;1;32m ^ 0m1m/usr/include/c++/v1/math.h:678:46: 0m0;1;30mnote: 0mtarget of using declaration0m inline _LIBCPP_INLINE_VISIBILITY float atan(float __lcpp_x) _NOEXCEPT {return atanf(__lcpp_x);} 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:705:9: 0m0;1;30mnote: 0musing declaration0m using ::atan; 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:710:46: 0m0;1;31merror: 0m1mdeclaration conflicts with target of using declaration already in scope0m inline _LIBCPP_INLINE_VISIBILITY long double atan(long double __lcpp_x) _NOEXCEPT {return atanl(__lcpp_x);} 0;1;32m ^ 0m1m/usr/include/c++/v1/math.h:679:46: 0m0;1;30mnote: 0mtarget of using declaration0m inline _LIBCPP_INLINE_VISIBILITY long double atan(long double __lcpp_x) _NOEXCEPT {return atanl(__lcpp_x);} 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:705:9: 0m0;1;30mnote: 0musing declaration0m using ::atan; 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:716:1: 0m0;1;31merror: 0m1mdeclaration conflicts with target of using declaration already in scope0m atan(_A1 __lcpp_x) _NOEXCEPT {return atan((double)__lcpp_x);} 0;1;32m^ 0m1m/usr/include/c++/v1/math.h:685:1: 0m0;1;30mnote: 0mtarget of using declaration0m atan(_A1 __lcpp_x) _NOEXCEPT {return atan((double)__lcpp_x);} 0;1;32m^ 0m1m/usr/include/c++/v1/cmath:705:9: 0m0;1;30mnote: 0musing declaration0m using ::atan; 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:724:46: 0m0;1;31merror: 0m1mdeclaration conflicts with target of using declaration already in scope0m inline _LIBCPP_INLINE_VISIBILITY float atan2(float __lcpp_y, float __lcpp_x) _NOEXCEP... 0;1;32m ^ 0m1m/usr/include/c++/v1/math.h:690:46: 0m0;1;30mnote: 0mtarget of using declaration0m inline _LIBCPP_INLINE_VISIBILITY float atan2(float __lcpp_y, float __lcpp_x) _NOEXCEP... 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:720:9: 0m0;1;30mnote: 0musing declaration0m using ::atan2; 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:725:46: 0m0;1;31merror: 0m1mdeclaration conflicts with target of using declaration already in scope0m inline _LIBCPP_INLINE_VISIBILITY long double atan2(long double __lcpp_y, long double __lcpp_x) _NOEXCE... 0;1;32m ^ 0m1m/usr/include/c++/v1/math.h:691:46: 0m0;1;30mnote: 0mtarget of using declaration0m inline _LIBCPP_INLINE_VISIBILITY long double atan2(long double __lcpp_y, long double __lcpp_x) _NOEXCE... 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:720:9: 0m0;1;30mnote: 0musing declaration0m using ::atan2; 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:736:1: 0m0;1;31merror: 0m1mdeclaration conflicts with target of using declaration already in scope0m atan2(_A1 __lcpp_y, _A2 __lcpp_x) _NOEXCEPT 0;1;32m^ 0m1m/usr/include/c++/v1/math.h:702:1: 0m0;1;30mnote: 0mtarget of using declaration0m atan2(_A1 __lcpp_y, _A2 __lcpp_x) _NOEXCEPT 0;1;32m^ 0m1m/usr/include/c++/v1/cmath:720:9: 0m0;1;30mnote: 0musing declaration0m using ::atan2; 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:750:46: 0m0;1;31merror: 0m1mdeclaration conflicts with target of using declaration already in scope0m inline _LIBCPP_INLINE_VISIBILITY float ceil(float __lcpp_x) _NOEXCEPT {return ceilf(__lcpp_x);} 0;1;32m ^ 0m1m/usr/include/c++/v1/math.h:713:46: 0m0;1;30mnote: 0mtarget of using declaration0m inline _LIBCPP_INLINE_VISIBILITY float ceil(float __lcpp_x) _NOEXCEPT {return ceilf(__lcpp_x);} 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:746:9: 0m0;1;30mnote: 0musing declaration0m using ::ceil; 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:751:46: 0m0;1;31merror: 0m1mdeclaration conflicts with target of using declaration already in scope0m inline _LIBCPP_INLINE_VISIBILITY long double ceil(long double __lcpp_x) _NOEXCEPT {return ceill(__lcpp_x);} 0;1;32m ^ 0m1m/usr/include/c++/v1/math.h:714:46: 0m0;1;30mnote: 0mtarget of using declaration0m inline _LIBCPP_INLINE_VISIBILITY long double ceil(long double __lcpp_x) _NOEXCEPT {return ceill(__lcpp_x);} 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:746:9: 0m0;1;30mnote: 0musing declaration0m using ::ceil; 0;1;32m ^ 0m1m/usr/include/c++/v1/cmath:757:1: 0m0;1;31merror: 0m1mdeclaration conflicts with target of using declaration already in scope0m ceil(_A1 __lcpp_x) _NOEXCEPT {return ceil((double)__lcpp_x);} 0;1;32m^ 0m1m/usr/include/c++/v1/math.h:720:1: 0m0;1;30mnote: 0mtarget of using declaration0m ceil(_A1 __lcpp_x) _NOEXCEPT {return ceil((double)__lcpp_x);} 0;1;32m^ 0m1m/usr/include/c++/v1/cmath:746:9: 0m0;1;30mnote: 0musing declaration0m using ::ceil; 0;1;32m ^ 0m0;1;31mfatal error: 0m1mtoo many errors emitted, stopping now [-ferror-limit=]0m 20 errors generated. *** Error code 1 Stop. make[3]: stopped in /usr/src/lib/clang/libllvmsupport *** Error code 1 Stop. make[2]: stopped in /usr/src *** Error code 1 Stop. make[1]: stopped in /usr/src *** Error code 1 Stop. make: stopped in /usr/src How to fix this? Thank you. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From owner-freebsd-questions@freebsd.org Fri Jul 14 07:38:32 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 530DCD994F7 for ; Fri, 14 Jul 2017 07:38:32 +0000 (UTC) (envelope-from srs0=kjah=6r=mail.sermon-archive.info=doug@sermon-archive.info) Received: from mail.sermon-archive.info (sermon-archive.info [71.177.216.148]) by mx1.freebsd.org (Postfix) with ESMTP id 3E7FC7FFC5 for ; Fri, 14 Jul 2017 07:38:31 +0000 (UTC) (envelope-from srs0=kjah=6r=mail.sermon-archive.info=doug@sermon-archive.info) Received: from [10.0.1.251] (mini [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 3x84LH2Gqcz2fkGs; Fri, 14 Jul 2017 00:38:31 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Unusual Question From: Doug Hardie In-Reply-To: <0ccfaae9-6fdb-adfa-71b2-5dd3978f41b3@qeng-ho.org> Date: Fri, 14 Jul 2017 00:38:30 -0700 Cc: David Christensen , "freebsd-questions@freebsd.org Questions" Content-Transfer-Encoding: quoted-printable Message-Id: <36DB0C7C-FF64-4BFA-9D7E-CF2A616FF534@mail.sermon-archive.info> References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> <0ccfaae9-6fdb-adfa-71b2-5dd3978f41b3@qeng-ho.org> To: Arthur Chance X-Mailer: Apple Mail (2.3273) X-Virus-Scanned: clamav-milter 0.99.2 at mail X-Virus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 07:38:32 -0000 > On 14 July 2017, at 00:26, Arthur Chance wrote: >=20 > On 14/07/2017 07:11, Doug Hardie wrote: >>=20 >>> On 13 July 2017, at 21:44, David Christensen = wrote: >>>=20 >>> On 07/09/17 02:57, Doug Hardie wrote: >>>> I have a FreeBSD 9.3 remote server that needs to be purged. I know = that rm -rf / will remove all the directory entries, but I need to write = over the drive. I thought that dd if=3D/dev/zero of=3D/dev/ada0 might = do the trick, but it gives an not permitted error. The whole thing can = crash and burn at the end. This is an unmanned site so moving drives is = not viable. >>>=20 >>> If the machine has BIOS and the system drive isn't too large, write = an assembly program that fits into the MBR bootstrap code area to wipe = the rest of the drive, assemble the program, write it into the MBR, and = reboot. >>>=20 >>>=20 >>> Bonus: the program deletes the MBR when done wiping the rest of the = drive. >>=20 >> Neat idea, but I have a number of these systems and they all use = different disk drives. That would be a lot of work writing drivers for = each type. >=20 > How about using the BIOS extended write sector call (INT 13h, AH=3D43h) = in > your code? That should be portable. I have no experience with the BIOS so that sounds reasonable, but I = couldn't say for sure. Even so, that would be a bunch of work to figure = all that out. Great project for someone with time available. From owner-freebsd-questions@freebsd.org Fri Jul 14 07:45:32 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C4F68D999D8 for ; Fri, 14 Jul 2017 07:45:32 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from bede.home.qeng-ho.org (bede.qeng-ho.org [217.155.128.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fileserver.home.qeng-ho.org", Issuer "fileserver.home.qeng-ho.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 45DDF804F1 for ; Fri, 14 Jul 2017 07:45:31 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from arthur.home.qeng-ho.org (arthur.home.qeng-ho.org [172.23.1.2]) by bede.home.qeng-ho.org (8.15.2/8.15.2) with ESMTP id v6E7QoG1023264; Fri, 14 Jul 2017 08:26:50 +0100 (BST) (envelope-from freebsd@qeng-ho.org) Subject: Re: Unusual Question To: Doug Hardie , David Christensen Cc: freebsd-questions@freebsd.org References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> From: Arthur Chance Message-ID: <0ccfaae9-6fdb-adfa-71b2-5dd3978f41b3@qeng-ho.org> Date: Fri, 14 Jul 2017 08:26:50 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 07:45:32 -0000 On 14/07/2017 07:11, Doug Hardie wrote: > >> On 13 July 2017, at 21:44, David Christensen wrote: >> >> On 07/09/17 02:57, Doug Hardie wrote: >>> I have a FreeBSD 9.3 remote server that needs to be purged. I know that rm -rf / will remove all the directory entries, but I need to write over the drive. I thought that dd if=/dev/zero of=/dev/ada0 might do the trick, but it gives an not permitted error. The whole thing can crash and burn at the end. This is an unmanned site so moving drives is not viable. >> >> If the machine has BIOS and the system drive isn't too large, write an assembly program that fits into the MBR bootstrap code area to wipe the rest of the drive, assemble the program, write it into the MBR, and reboot. >> >> >> Bonus: the program deletes the MBR when done wiping the rest of the drive. > > Neat idea, but I have a number of these systems and they all use different disk drives. That would be a lot of work writing drivers for each type. How about using the BIOS extended write sector call (INT 13h, AH=43h) in your code? That should be portable. -- An amusing coincidence: log2(58) = 5.858 (to 0.0003% accuracy). From owner-freebsd-questions@freebsd.org Fri Jul 14 07:47:30 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4FE9ED99AE4 for ; Fri, 14 Jul 2017 07:47:30 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay10.qsc.de (mailrelay10.qsc.de [212.99.163.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DDC51805DB for ; Fri, 14 Jul 2017 07:47:29 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay10.qsc.de; Fri, 14 Jul 2017 09:47:09 +0200 Received: from r56.edvax.de (port-92-195-0-242.dynamic.qsc.de [92.195.0.242]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 34B6B3CBF9; Fri, 14 Jul 2017 09:47:07 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v6E7l7qx007880; Fri, 14 Jul 2017 09:47:07 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Fri, 14 Jul 2017 09:47:07 +0200 From: Polytropon To: Doug Hardie Cc: David Christensen , freebsd-questions@freebsd.org Subject: Re: Unusual Question Message-Id: <20170714094707.976eb9c1.freebsd@edvax.de> In-Reply-To: References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay10.qsc.de with D14CB68340A X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1489 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 07:47:30 -0000 On Thu, 13 Jul 2017 23:11:41 -0700, Doug Hardie wrote: > > > On 13 July 2017, at 21:44, David Christensen wrote: > > If the machine has BIOS and the system drive isn't too large, > > write an assembly program that fits into the MBR bootstrap code > > area to wipe the rest of the drive, assemble the program, write > > it into the MBR, and reboot. > > > > > > Bonus: the program deletes the MBR when done wiping the rest of the drive. > > Neat idea, but I have a number of these systems and they all use > different disk drives. That would be a lot of work writing drivers > for each type. If the machines have BIOS, you can use BIOS interrupt calls which should be the same for all drives, comparable to the biosdisk() DOS functions. Let's see if I can get the basics together... you'd basically do something like this: biosdisk(0x03, 0x80, h, c, s, 1, (void *)crap); 0x03 is "write", 0x80 is 1st disk detected by BIOS; h, c, s is the head / cylinder / sector address of where you want to write to; 1 is the amount of blocks to write, and crap is a pointer to a vector of unsigned char, for example 512 bytes, the size of a block (addressed by h / c / s, where 0 / 0 / 1 is the starting location of the MBR), containing some random crap (or NULs) you want to write. The translation to assembly is left to the shocked reader. :-) Sources: http://www.digitalmars.com/rtl/bios.html#biosdisk https://en.wikipedia.org/wiki/BIOS_interrupt_call What terrible memories it recalls... ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Fri Jul 14 08:26:21 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8A994D9A915 for ; Fri, 14 Jul 2017 08:26:21 +0000 (UTC) (envelope-from rvan@sdf.org) Received: from mx.sdf.org (mx.sdf.org [205.166.94.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ol.sdf.org", Issuer "ol.sdf.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 655E181977 for ; Fri, 14 Jul 2017 08:26:21 +0000 (UTC) (envelope-from rvan@sdf.org) Received: from sdf.org (IDENT:rvan@otaku.freeshell.org [205.166.94.9]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id v6E8Q4CQ002733 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO) for ; Fri, 14 Jul 2017 08:26:04 GMT Received: (from rvan@localhost) by sdf.org (8.15.2/8.12.8/Submit) id v6E8Q4O4009917 for freebsd-questions@freebsd.org; Fri, 14 Jul 2017 20:26:04 +1200 (NZST) Date: Fri, 14 Jul 2017 20:26:04 +1200 From: Rouan Lucas van Ryn To: freebsd-questions@freebsd.org Subject: Wireless network slows down with zyd0 Message-ID: <20170714082604.GA2022@SDF.ORG> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 08:26:21 -0000 I have been experiencing slow network speeds with my FreeBSD (11.0) system on my wireless LAN. My wireless card is a USB ZyDAS card: zyd0: on usbus3 When I start networking, wireless speeds seem OK (~700KB/s when scp'ing a file to my laptop on the WLAN), but after around 10 seconds of network activity drop off to become very slow (~70KB/s). Speeds stay slow until networking is restarted and then pick up again momentarily. Tests with iperf yield similar results. I have found that the wireless connection is being renegotiated at lower and lower speeds: wlan0: [0c:d6:bd:1a:19:24] AMRR: current rate 72, txcnt=11, retrycnt=17 wlan0: [0c:d6:bd:1a:19:24] AMRR decreasing rate 48 (txcnt=11 retrycnt=17) wlan0: [0c:d6:bd:1a:19:24] AMRR: current rate 48, txcnt=11, retrycnt=14 wlan0: [0c:d6:bd:1a:19:24] AMRR decreasing rate 36 (txcnt=11 retrycnt=14) wlan0: [0c:d6:bd:1a:19:24] AMRR: current rate 36, txcnt=11, retrycnt=13 wlan0: [0c:d6:bd:1a:19:24] AMRR decreasing rate 24 (txcnt=11 retrycnt=13) wlan0: [0c:d6:bd:1a:19:24] AMRR: current rate 24, txcnt=11, retrycnt=11 wlan0: [0c:d6:bd:1a:19:24] AMRR decreasing rate 22 (txcnt=11 retrycnt=11) wlan0: [0c:d6:bd:1a:19:24] AMRR: current rate 22, txcnt=11, retrycnt=13 wlan0: [0c:d6:bd:1a:19:24] AMRR decreasing rate 18 (txcnt=11 retrycnt=13) wlan0: [0c:d6:bd:1a:19:24] AMRR: current rate 18, txcnt=11, retrycnt=11 wlan0: [0c:d6:bd:1a:19:24] AMRR decreasing rate 12 (txcnt=11 retrycnt=11) wlan0: [0c:d6:bd:1a:19:24] AMRR: current rate 12, txcnt=11, retrycnt=12 wlan0: [0c:d6:bd:1a:19:24] AMRR decreasing rate 11 (txcnt=11 retrycnt=12) wlan0: [0c:d6:bd:1a:19:24] AMRR: current rate 11, txcnt=11, retrycnt=11 wlan0: [0c:d6:bd:1a:19:24] AMRR decreasing rate 4 (txcnt=11 retrycnt=11) wlan0: [0c:d6:bd:1a:19:24] AMRR: current rate 4, txcnt=11, retrycnt=11 wlan0: [0c:d6:bd:1a:19:24] AMRR decreasing rate 2 (txcnt=11 retrycnt=11) wlan0: [0c:d6:bd:1a:19:24] AMRR: current rate 2, txcnt=11, retrycnt=11 The same wireless card works well (no slowdown) when connected to a different computer (not FreeBSD) in the same room, leading me to suspect that this isn't a hardware or signal strength issue. Netstat shows that packets are being retransmitted: tcp: 109179 packets sent 108551 data packets (110570192 bytes) 575 data packets (534156 bytes) retransmitted 6 data packets unnecessarily retransmitted ... Relevant parts of ifconfig: zyd0: flags=8843 metric 0 mtu 2290 ether 00:25:xx:xx:xx:xx nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated wlan0: flags=8843 metric 0 mtu 1500 ether 00:25:xx:xx:xx:xx inet 192.168.1.6 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet DS/1Mbps mode 11g status: associated ssid xxxx channel 1 (2412 MHz 11g) bssid 0c:d6:bd:1a:19:24 regdomain APAC country NZ authmode WPA2/802.11i privacy ON deftxkey UNDEF TKIP 2:128-bit txpower 30 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS roaming MANUAL Note in particular the line: media: IEEE 802.11 Wireless Ethernet DS/1Mbps mode 11g ifconfig wlan0 scan gives me: SSID/MESH ID BSSID CHAN RATE S:N INT CAPS SPARK-DFWFMP 0c:d6:bd:1a:19:24 1 54M -58:-95 100 EP RSN HTCAP WPS WPA (among other networks) -- Thanks, Rouan From owner-freebsd-questions@freebsd.org Fri Jul 14 08:30:39 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85737D9AA13 for ; Fri, 14 Jul 2017 08:30:39 +0000 (UTC) (envelope-from holindho@saunalahti.fi) Received: from vs23.mail.saunalahti.fi (vs23.mail.saunalahti.fi [193.64.193.199]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vs23.mail.saunalahti.fi", Issuer "vs23.mail.saunalahti.fi" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46E2381AD1 for ; Fri, 14 Jul 2017 08:30:38 +0000 (UTC) (envelope-from holindho@saunalahti.fi) Received: from vs23.mail.saunalahti.fi (localhost [127.0.0.1]) by vs23.mail.saunalahti.fi (Postfix) with ESMTP id 09FF1200B7; Fri, 14 Jul 2017 11:30:30 +0300 (EEST) Received: from gw02.mail.saunalahti.fi (gw02.mail.saunalahti.fi [195.197.172.116]) by vs23.mail.saunalahti.fi (Postfix) with ESMTP id 0918D2008C; Fri, 14 Jul 2017 11:30:30 +0300 (EEST) Received: from [10.0.0.7] (62-78-248-13.bb.dnainternet.fi [62.78.248.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by gw02.mail.saunalahti.fi (Postfix) with ESMTPSA id F05A940171; Fri, 14 Jul 2017 11:30:27 +0300 (EEST) Subject: Re: Unusual Question To: freebsd-questions@freebsd.org References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> From: Heikki Lindholm Message-ID: <65a4d725-cc3d-4702-77f9-0bb6d57605ce@saunalahti.fi> Date: Fri, 14 Jul 2017 11:30:28 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 08:30:39 -0000 On 14.07.2017 09:11, Doug Hardie wrote: > >> On 13 July 2017, at 21:44, David Christensen wrote: >> >> On 07/09/17 02:57, Doug Hardie wrote: >>> I have a FreeBSD 9.3 remote server that needs to be purged. I know that rm -rf / will remove all the directory entries, but I need to write over the drive. I thought that dd if=/dev/zero of=/dev/ada0 might do the trick, but it gives an not permitted error. The whole thing can crash and burn at the end. This is an unmanned site so moving drives is not viable. >> >> If the machine has BIOS and the system drive isn't too large, write an assembly program that fits into the MBR bootstrap code area to wipe the rest of the drive, assemble the program, write it into the MBR, and reboot. >> >> >> Bonus: the program deletes the MBR when done wiping the rest of the drive. > > Neat idea, but I have a number of these systems and they all use different disk drives. That would be a lot of work writing drivers for each type. I tried clearing the root partition of fbsd 11 under virtualbox. The root was 3 gigabytes and ZFS format. The process was to disable services, disable swap and make a script that does a sync, sleep and the whole disk dd, and then disable sshd and run the script. I then did an ACPI shutdown after waiting enough time for the dd to complete. I thought it would show what the kernel could still flush to disk after the dd. The outcome was that there was about 700k data left on the device. I think something should be done to ZFS ARC to make this work better. The kernel did not crash because of the dd. ---- The steps I took in more detail ---- * remove GEOM MBR protection # sysctl kern.geom.debugflags=0x10 * test disk access # dd if=/dev/ada0 of=mbr bs=512 count=1 # dd if=mbr of=/dev/ada0 bs=512 count=1 * list services # service -e * stop services (just an example; check with ps -A) # service mixer stop # service cron stop # service sendmail stop # service ntpd stop # service dmesg stop # service savecore stop # service syslogd stop * disable swap # swapoff /dev/ada0p2 # swapctl -l * make selfdestruct script # cat selfdestruct.sh #!/bin/csh sync sleep 10s nohup dd if=/dev/zero of=/dev/ada0 bs=20m > & /dev/null < /dev/zero & * run script # ./selfdestruct.sh * kill sshd # service sshd stop From owner-freebsd-questions@freebsd.org Fri Jul 14 10:00:00 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AD250D9CEA9 for ; Fri, 14 Jul 2017 10:00:00 +0000 (UTC) (envelope-from raimo+freebsd@erix.ericsson.se) Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3DE5E84C2A for ; Fri, 14 Jul 2017 09:59:59 +0000 (UTC) (envelope-from raimo+freebsd@erix.ericsson.se) X-AuditID: c1b4fb2d-803ff70000005faa-1a-596896160383 Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.183.36]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 74.59.24490.61698695; Fri, 14 Jul 2017 11:59:50 +0200 (CEST) Received: from duper.otp.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.38) with Microsoft SMTP Server id 14.3.352.0; Fri, 14 Jul 2017 11:59:50 +0200 Received: from duper.otp.ericsson.se (localhost [127.0.0.1]) by duper.otp.ericsson.se (8.15.2/8.15.2) with ESMTP id v6E9xoBd074447 for ; Fri, 14 Jul 2017 11:59:50 +0200 (CEST) (envelope-from raimo+freebsd@erix.otp.ericsson.se) Received: (from raimo@localhost) by duper.otp.ericsson.se (8.15.2/8.15.2/Submit) id v6E9xoEJ074446 for freebsd-questions@freebsd.org; Fri, 14 Jul 2017 11:59:50 +0200 (CEST) (envelope-from raimo+freebsd@erix.otp.ericsson.se) X-Authentication-Warning: duper.otp.ericsson.se: raimo set sender to raimo+freebsd@erix.ericsson.se using -f Date: Fri, 14 Jul 2017 11:59:50 +0200 From: Raimo Niskanen To: Subject: Re: Unusual Question Message-ID: <20170714095950.GA72707@erix.ericsson.se> Mail-Followup-To: freebsd-questions@freebsd.org References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: "To: freebsd-questions@freebsd.org" User-Agent: Mutt/1.7.2 (2016-11-26) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrJLMWRmVeSWpSXmKPExsUyM2K7iq7YtIxIg2ebbSxeft3E4sDoMePT fJYAxigum5TUnMyy1CJ9uwSujJ2LqwpOcFdsPbSZrYFxNmcXIyeHhICJxL5fPexdjFwcQgJH GCW+71jIBuFsZJRo+b0YKtPOJPH75HcmCOcpo8TGD1MZIfpzJN5+OsoEYrMIqErsOToFzGYT MJVo/HmGFcQWEVCW+HftIjOILSwgKzH/32oWEJsXqKa3ZTErhK0v8XHFK1aIBa2MEttWboMq EpQ4OfMJmM0soCOxYPcnoPs4gGxpieX/OEDCnAIuEh/+7QULMwDtajslBGKKgqz9CjZdSEBb YsKbA6wTGEVmIZk5C8nMWQgzFzAyr2IULU4tLs5NNzLWSy3KTC4uzs/Ty0st2cQIDPCDW37r 7mBc/drxEKMAB6MSD6/DhIxIIdbEsuLK3EOMEhzMSiK8KpOBQrwpiZVVqUX58UWlOanFhxil OViUxHkd9l2IEBJITyxJzU5NLUgtgskycXBKNTAuUVt6MGAf+7+YKpa1jas/Pbt30j1n+293 1rTpGTtMO/luqXxjuV/wWtpd5rjppDl/1FjtYubmXdocOGNK7AXn3yzL3YVfeh7l8Mhcar4o WDJ9maXb6owrTjkVVrm27BtXZLzuORwXxXP3deNqubyP76f83dq6OejOxzPrHka7SB7bJq8t 4rtdiaU4I9FQi7moOBEAEO7IfmwCAAA= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 10:00:00 -0000 This thread reminds me of the argument that you should always encrypt your hard disk. For a remote site you could have the key on a key partition for some crypto systems. Then all you have to do is destroy the key, which is much easier. (For an SSD drive to protect against harcore forensics I do not know how to ensure that the data is gone, though) On Thu, Jul 13, 2017 at 09:44:30PM -0700, David Christensen wrote: > On 07/09/17 02:57, Doug Hardie wrote: > > I have a FreeBSD 9.3 remote server that needs to be purged. I know that rm -rf / will remove all the directory entries, but I need to write over the drive. I thought that dd if=/dev/zero of=/dev/ada0 might do the trick, but it gives an not permitted error. The whole thing can crash and burn at the end. This is an unmanned site so moving drives is not viable. > > If the machine has BIOS and the system drive isn't too large, write an > assembly program that fits into the MBR bootstrap code area to wipe the > rest of the drive, assemble the program, write it into the MBR, and reboot. > > > Bonus: the program deletes the MBR when done wiping the rest of the drive. > > > David > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" -- / Raimo Niskanen, Erlang/OTP, Ericsson AB From owner-freebsd-questions@freebsd.org Fri Jul 14 11:13:58 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 189A9D9E5DF; Fri, 14 Jul 2017 11:13:58 +0000 (UTC) (envelope-from kulamani.sethi@gmail.com) Received: from mail-ua0-x231.google.com (mail-ua0-x231.google.com [IPv6:2607:f8b0:400c:c08::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C7BB124AB; Fri, 14 Jul 2017 11:13:57 +0000 (UTC) (envelope-from kulamani.sethi@gmail.com) Received: by mail-ua0-x231.google.com with SMTP id z22so49962592uah.1; Fri, 14 Jul 2017 04:13:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=eG+7ZRaXj2qfr9t095v1uOJhs0zV/RheYOI2I4cL7XI=; b=FLDtecl0gycJhvXGjxtCHox7p28pdSNbg6pw3Cv7kZKxvZp6KAw4GrDG3u33ZoDr3B SWUF2uDXw5O77dTgshUyEKbrPQUUN1D19um1OQNNDz/jmdt6hai7X1t0T5nZt6j14TXv mHyrK0u1XAgI//t3QLKcYcvgDOP4nwH/iIuloSkdbRqJqvwTl7NkQpRRcHk2ydCUqthW 2utkXO/Yi+0kUhXWMTkTuN3g/gDGWUFh0SiM82wUJrJ8H0FACNmiKwPxbGa26p65L/ir /2SFu64MIg0oZbBOlc/H8k2jhO4PqEiJeIas6Aan4SGidDMUgmlcdZKEl/Hf8bGQul0t 6z6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=eG+7ZRaXj2qfr9t095v1uOJhs0zV/RheYOI2I4cL7XI=; b=ZlSib4zzTyd9gQ0F9Rwcff/233y8VMW+/Sji7tdRz3EI17PymkRIfyG13uEhQbSJXm 1mvkYtiu5Gmfh7JmZ+tCnWRY8HW2RONKFgkR9haVyVLLDndjncZB7/Ayk0Q2hKNcmK2n ZSvDonQZlxS37E+xOa/9+g/PK1SUkAOYiRjr2+WeaVNA5zzR3gukkrpqFWDvkr0m4zim r0aibJ5uqFxpXyrb3F+hBi5NoRvpUTZpxrCDc3hKgcPASFJ34PS8LgQ9QOkBUmgN2s1m +dCmwwTb+geRvcFN7Euf3P8G8FQIRs8mu32G1o7efsj40swVcy70ZbXVt4IudbWyDzvf gAjg== X-Gm-Message-State: AIVw112qP1PeCJlp6ZvBp///ltDsb6Mtj1+khei3Buy4hJ/IW82S8VZd yweGv+2i8EK6bo0L18OwMvw0UcuCPsFv X-Received: by 10.176.80.19 with SMTP id b19mr5265930uaa.139.1500030836562; Fri, 14 Jul 2017 04:13:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.81.231 with HTTP; Fri, 14 Jul 2017 04:13:56 -0700 (PDT) From: Kulamani Sethi Date: Fri, 14 Jul 2017 16:43:56 +0530 Message-ID: Subject: Unable to set rule using service name To: freebsd-questions@freebsd.org, freebsd-ipfw@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 11:13:58 -0000 Hi, I want to set a rule for a particular service URL which running on a remote server. I know the IP but don't know the port number where that service is running. If i set rule for IP then it will applied for entire services running over there. There is a option in IPFW rule we can set either port number or name, but it does not accepting using name. Here is a example for my case. suppose URL for test1 service http://x.x.x.x/test1 URL for test2 service http://x.x.x.x/test2 I tried a rule, "ipfw add 104 deny log ip from x.x.x.x test1 to any". Got error "ipfw: missing "to'' ". *I want to set rule for test1 where I have no idea about port.* *Also please help me how to know port number if any way is there.* *With best Regards,* Kulamani Sethi, Bangalore, India Mob: 9686190111 From owner-freebsd-questions@freebsd.org Fri Jul 14 11:47:13 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A5795D9EF09; Fri, 14 Jul 2017 11:47:13 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 598023303; Fri, 14 Jul 2017 11:47:12 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1dVyzf-001LP5-7I>; Fri, 14 Jul 2017 13:42:47 +0200 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=freyja.zeit4.iv.bundesimmobilien.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1dVyze-003z22-Sx>; Fri, 14 Jul 2017 13:42:47 +0200 Date: Fri, 14 Jul 2017 13:42:41 +0200 From: "O. Hartmann" To: FreeBSD CURRENT Cc: "Andrey V. Elsukov" , "O. Hartmann" , FreeBSD Questions Subject: Re: Inter-VLAN routing on CURRENT: any known issues? Message-ID: <20170713211004.13492aef@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20170712214334.4fc97335@thor.intern.walstatt.dynvpn.de> Organization: FU Berlin X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Originating-IP: 87.138.105.249 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 11:47:13 -0000 Am Thu, 13 Jul 2017 16:12:06 +0300 "Andrey V. Elsukov" schrieb: > On 12.07.2017 22:43, O. Hartmann wrote: > > Now the FUN PART: > >=20 > > From any host in any VLAN I'm able to ping hosts on the wild internet v= ia > > their IP, on VLAN 1000 there is a DNS running, so I'm also able to reso= lv > > names like google.com or FreeBSD.org. But I can NOT(!) access any host = via > > http/www or ssh. =20 >=20 > You have not specified where is the NAT configured and its settings is > matters. I use in-kernel NAT. IPFW is performing NAT. In firewall type "OPEN" from t= he vanilla rc.conf, IPFW has instance "nat 123" which provides then NAT. >=20 > VLANs work on the layer2, they do not used for IP routing. Each received > packet loses its layer2 header before it gets taken by IP stack. If an > IP packet should be routed, the IP stack determines outgoing interface > and new ethernet header with VLAN header from this interface is prepended. Since all VLANs are on the same NIC on that router, they should only differ= in the VLAN tag. >=20 > What I would do in your place: > 1. Check the correctness of the switch settings. > - on the router use tcpdump on each vlan interface and > also directly on igb1. Use -e argument to see ethernet header. > Try ping router's IP address from each vlan, you should see tagged > packet on igb1 and untagged on corresponding vlan interface. >=20 > 2. Check the correctness of the routing settings for each used node. > - to be able establish connection from one vlan to another, both nodes > must have a route to each other. >=20 > 3. Check the NAT settings. > - to be able to connect to the Internet from your addresses, you must > use NAT. If you don't have NAT, but it somehow works, this means > that some device does the translation for you, but it's > configuration does not meet to your requirements. And probably you > need to translate prefixes configured for your vlans independently. >=20 According to 1): I consider the settings of the switch now as correct. I have no access to t= he router right now. But I did short experiments yesterday evening and it is weird: loged in on thr router, I can ping every host on any VLAN, so ICMP travel from the router the right way to its destination and back. =46rom any host on any VLAN that is "trunked" through the router, I can ping = any other host on any other VLAN, preferrably not on the same VLAN. By cutting = off the trunk line to the router, pinging stops immediately. =46rom any host on any VLAN I can ping any host which is NATed on the outside world. =46rom the router itself, I can ssh into any host on any VLAN providing ssh service. That said, according to question 3), NAT is considered to be setup correctly. Now the strange things: Neither UDP, nor TCP services "flow" from hosts on = one VLAN to hosts on a different VLAN. Even ssh doens't work.=20 When loged in onto the router, I can't "traceroute" any host on any VLAN. According to question 2), the ability to ping from, say, a host on VLAN 100= 0 to another host on VLAN 2 passing through the router would indicate that both sides know their routes to each other. Or am I wrong? I got words from Sean bruno that there might be a problem with the Intel i2= 10 chipset in recent CURRENT - and the hardware on the PCEngine APU 2C4 is thr= ee i210. I'm aware of the problem since r320134 (the oldest CURRENT I started experimenting with the VLAN trunking). I hope it might be a problem with the driver, otherwise I have fully misunderstood FreeBSD's network abilities and techniques :-( I'll provide tcpdump data later. Kind regards, Oliver=20 --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). From owner-freebsd-questions@freebsd.org Fri Jul 14 12:03:42 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE0DFD9FFAF; Fri, 14 Jul 2017 12:03:42 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward5h.cmail.yandex.net (forward5h.cmail.yandex.net [IPv6:2a02:6b8:0:f35::15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 90602632B7; Fri, 14 Jul 2017 12:03:42 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp4p.mail.yandex.net (smtp4p.mail.yandex.net [95.108.252.166]) by forward5h.cmail.yandex.net (Yandex) with ESMTP id 8BC96210F2; Fri, 14 Jul 2017 15:03:31 +0300 (MSK) Received: from smtp4p.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp4p.mail.yandex.net (Yandex) with ESMTP id 0ED3A65011BD; Fri, 14 Jul 2017 15:03:27 +0300 (MSK) Received: by smtp4p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id u1y8D25su2-3Qa4MN5M; Fri, 14 Jul 2017 15:03:26 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1500033806; bh=/99GvL//BUH+lze/IsxFJOR1AqSWy9p+/OgV2jDNW7Q=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=SSpCQRFQlGnozB/ftWGhQCfUoMT6YbAtAzj1/Hz941ZXEMppxPv1VBcsuMLydMIhP 9YhPHdPDiWL2pTe+P361toPO8QFSHGHlt8+A98aqSDDiyc4sdIur5wc7JbC9nfXr3i UBHXe7GiXc7/eaw4ylZ0UJa09LvVmeG3g//XTG8w= Authentication-Results: smtp4p.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-Suid-Status: 1 0,1 0,1 0,1 0 Subject: Re: Inter-VLAN routing on CURRENT: any known issues? To: "O. Hartmann" , FreeBSD CURRENT Cc: "O. Hartmann" , FreeBSD Questions References: <20170712214334.4fc97335@thor.intern.walstatt.dynvpn.de> <20170713211004.13492aef@thor.intern.walstatt.dynvpn.de> From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: Date: Fri, 14 Jul 2017 15:00:30 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: <20170713211004.13492aef@thor.intern.walstatt.dynvpn.de> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="TXHdgUq6MEvt6OL3RlEmnGILovVvSBmw9" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 12:03:43 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --TXHdgUq6MEvt6OL3RlEmnGILovVvSBmw9 Content-Type: multipart/mixed; boundary="NH8mmNxt8NVIXXsa6qm9RF0ES8NfiqlBV"; protected-headers="v1" From: "Andrey V. Elsukov" To: "O. Hartmann" , FreeBSD CURRENT Cc: "O. Hartmann" , FreeBSD Questions Message-ID: Subject: Re: Inter-VLAN routing on CURRENT: any known issues? References: <20170712214334.4fc97335@thor.intern.walstatt.dynvpn.de> <20170713211004.13492aef@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20170713211004.13492aef@thor.intern.walstatt.dynvpn.de> --NH8mmNxt8NVIXXsa6qm9RF0ES8NfiqlBV Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 14.07.2017 14:42, O. Hartmann wrote: > I use in-kernel NAT. IPFW is performing NAT. In firewall type "OPEN" fr= om the > vanilla rc.conf, IPFW has instance "nat 123" which provides then NAT. I never used default config types for firewall, so, it would be nice to see what rules do you have. # ipfw show # ipfw nat show config >> VLANs work on the layer2 > According to 1): >=20 > I consider the settings of the switch now as correct. I have no access = to the > router right now. But I did short experiments yesterday evening and it = is > weird: loged in on thr router, I can ping every host on any VLAN, so IC= MP > travel from the router the right way to its destination and back. >=20 > From any host on any VLAN that is "trunked" through the router, I can p= ing any > other host on any other VLAN, preferrably not on the same VLAN. By cutt= ing off > the trunk line to the router, pinging stops immediately. >=20 > From any host on any VLAN I can ping any host which is NATed on the out= side > world. >=20 > From the router itself, I can ssh into any host on any VLAN providing s= sh > service. That said, according to question 3), NAT is considered to be s= etup > correctly. >=20 > Now the strange things: Neither UDP, nor TCP services "flow" from hosts= on one > VLAN to hosts on a different VLAN. Even ssh doens't work.=20 > When loged in onto the router, I can't "traceroute" any host on any VLA= N. This is most likely due to the problem with firewall rules. If you set net.inet.ip.firewall.enable=3D0, does it solve the problem wit= h TCP/UDP between hosts on a different VLANs? > According to question 2), the ability to ping from, say, a host on VLAN= 1000 to > another host on VLAN 2 passing through the router would indicate that b= oth > sides know their routes to each other. Or am I wrong? Yes. > I got words from Sean bruno that there might be a problem with the Inte= l i210 > chipset in recent CURRENT - and the hardware on the PCEngine APU 2C4 is= three > i210. I'm aware of the problem since r320134 (the oldest CURRENT I star= ted > experimenting with the VLAN trunking). It is very strange problems, why ICMP works, but TCP/UDP does not? :) You can try to disable any type of offloading for the card, there were some problems in the past with checksum offlading, that may lead to the problems with TCP, but this usually should be noticeable in the tcpdump output. --=20 WBR, Andrey V. Elsukov --NH8mmNxt8NVIXXsa6qm9RF0ES8NfiqlBV-- --TXHdgUq6MEvt6OL3RlEmnGILovVvSBmw9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAllosl4ACgkQAcXqBBDI oXoaNggApk+Q/cCZ1kLczxIfdM2yJFK12Sx5C+uxBkRZ7v2LBKaFwgFwu/3EAHbx wC46VzAC6rqeVemP99NqWyfdLRCc2cjxJNqxGFiSAhI7FqkTqLjHPjuRg4wofj2Y sXXVBXPS8BrWci304nX0anuHXxxZgk65ajvXFTfrebU/jw/6MWSNZrS++rPGGlxR wP2JR6S7TVyJMiD+tnLQu/jZY8QpzCPpgg0HMQmB0n9W30AeZMaz6GHv000UxQ55 e2AX5RdxBoFdW3u3Kol8fOTC1Tez97SH30xa03KQzm4GeUw3koK0T31sPPdAZA8P TpGxiSE0JxdvRS9zK+4NcgJucbgBqg== =2EMb -----END PGP SIGNATURE----- --TXHdgUq6MEvt6OL3RlEmnGILovVvSBmw9-- From owner-freebsd-questions@freebsd.org Fri Jul 14 13:13:20 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 670D7DA17AE for ; Fri, 14 Jul 2017 13:13:20 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4184865531; Fri, 14 Jul 2017 13:13:20 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id 84D59BAB7; Fri, 14 Jul 2017 13:13:19 +0000 (UTC) From: Jan Beich To: Steven Nikkel Cc: freebsd-questions@freebsd.org Subject: Re: OpenCL Issues References: Date: Fri, 14 Jul 2017 15:13:14 +0200 In-Reply-To: (Steven Nikkel's message of "Thu, 13 Jul 2017 09:02:04 -0500") Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 13:13:20 -0000 Steven Nikkel writes: > # clinfo > Number of platforms 1 > Platform Name Intel Gen OCL Driver > Platform Vendor Intel > Platform Version OpenCL 1.2 beignet 1.3 > Platform Profile FULL_PROFILE > Platform Extensions cl_khr_global_int32_base_atomics > cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics > cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store > cl_khr_3d_image_writes cl_khr_image2d_from_buffer cl_khr_depth_images > cl_khr_spir cl_khr_icd cl_intel_accelerator cl_intel_subgroups > cl_intel_subgroups_short > Platform Extensions function suffix Intel > Segmentation fault (core dumped) > > #0 0x00000008025e5064 in drm_intel_bo_set_softpin_offset () > from /usr/local/lib/libdrm_intel.so.1 > #1 0x00000008018153bf in clGetProgramBuildInfo () > from /usr/local/lib/beignet//libcl.so > #2 0x0000000801814e68 in clGetProgramBuildInfo () > from /usr/local/lib/beignet//libcl.so See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217635 From owner-freebsd-questions@freebsd.org Fri Jul 14 13:53:54 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 88B93DA253B for ; Fri, 14 Jul 2017 13:53:54 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2B513666B2 for ; Fri, 14 Jul 2017 13:53:54 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wm0-x22a.google.com with SMTP id 62so21228496wmw.1 for ; Fri, 14 Jul 2017 06:53:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-transfer-encoding; bh=CHHqqhPyUvjGVryZKE/Y2QRw2UFz7Z+5flnVt2p/8o4=; b=DUZTtaenxNMApz8YvKppziUuyV2DIr4wFb3cHuOYEEeCDZCMmoErK4ss9Y5dNExYxg CHFZ1TTd2EWpiMK+IG0why7x3e6Gqpd4PxDC6G6cNGaOc6pbGX4Sy/qGGXqGEgtEYWLn baHygENhmuSOzOauiFjZuG/KHs9NPfixD7SzO6vMZhprCEpRmsMVwX7k5SNg4ja3tWaP jXQgoxMBHUhcSdaoAo8vx5IJxSpBObUnLq6Tv0t1HHvUD6pLzSrerKAYkyO0v0/eZoF7 kHHsteHzI1CTPdaROuw1ydt9Eo1RYi5G8v6xezGZtgplDVd4+YCGDPg6CY6QYtQvhb2n 10cw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=CHHqqhPyUvjGVryZKE/Y2QRw2UFz7Z+5flnVt2p/8o4=; b=jUc/Lv/AUacaP41LhZ9WZbQdEGnkYQhq80GNe10IJ6ju2rE6vQ+tFJ1mESO3NAw3Xy 8X0U75oM4vB+vSr+oPbRB7i5pI559oOjHWHUQDD4bpcsLDMCPSI7DPs/r1DQmtFvD8OC NLkps2lAkHoeaRwSYsyhGdRsZukRGkkpTgrP0YOEG2yP3wYUA74GTCZXyiIvJ6J4Svk0 rGP2fFrUTm6WS9hO1zkwr9bP/+xhh3wA3UYUTgOeh2sr4D0csayXKwIgelXSctM2h9Vf WmWf4egVnphaItrH29M3ZTW76Ju2b+REOB3Wihe5SiORYScaJSrpWL4xaw1WjfXlrett PFxg== X-Gm-Message-State: AIVw110iMxUa0c7opGsN88jVCfKOcGW5ayMPmdA/QHjsWJ141QC4jT29 SN6WSH9mHj8IZTCs X-Received: by 10.28.125.3 with SMTP id y3mr2975431wmc.9.1500040432277; Fri, 14 Jul 2017 06:53:52 -0700 (PDT) Received: from gumby.homeunix.com ([81.17.24.158]) by smtp.gmail.com with ESMTPSA id w30sm9432914wrb.49.2017.07.14.06.53.50 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 14 Jul 2017 06:53:51 -0700 (PDT) Date: Fri, 14 Jul 2017 14:53:47 +0100 From: RW To: freebsd-questions@freebsd.org Subject: Re: Unable to set rule using service name Message-ID: <20170714145347.40401bf7@gumby.homeunix.com> In-Reply-To: References: X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.31; amd64-portbld-freebsd10.3) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 13:53:54 -0000 On Fri, 14 Jul 2017 16:43:56 +0530 Kulamani Sethi wrote: > Hi, > I want to set a rule for a particular service URL which running on a > remote server. > I know the IP but don't know the port number where that service is > running. If i set rule for IP then it will applied for entire > services running over there. > > There is a option in IPFW rule we can set either port number or name, > but it does not accepting using name. Here is a example for my case. > > suppose URL for test1 service http://x.x.x.x/test1 > URL for test2 service http://x.x.x.x/test2 > > I tried a rule, "ipfw add 104 deny log ip from x.x.x.x test1 test1 and test2 aren't port numbers, the port number here is 80 for http From owner-freebsd-questions@freebsd.org Fri Jul 14 14:29:16 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 13A1BDA2E38 for ; Fri, 14 Jul 2017 14:29:16 +0000 (UTC) (envelope-from lisa.williams@digitaldatatechno.com) Received: from IND01-MA1-obe.outbound.protection.outlook.com (mail-ma1ind01on0082.outbound.protection.outlook.com [104.47.100.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 232D7677C7 for ; Fri, 14 Jul 2017 14:29:14 +0000 (UTC) (envelope-from lisa.williams@digitaldatatechno.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=NETORGFT2140629.onmicrosoft.com; s=selector1-digitaldatatechno-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ZTx8HPQXyeiZ3M6GfxPldzQOsyXZW6zH43SldmmqVgE=; b=iXnvxn4eZov03Dfj4z3QqjawziWrHoEtj/ZCsZpHIghDlixAwhfrDjnSbX2C32cCcks3Qj5GqmzVUnwv/JJkEMgpZwKhWTm2WzxvfUrjY7aPSbjJf8ecyj/s7B0JZEf5YwQJApZMa99+fN+t+AmegS8MKMcTdCn9Xtzb62xunQM= Received: from PN1PR01MB0879.INDPRD01.PROD.OUTLOOK.COM (10.174.147.8) by PN1PR01MB0878.INDPRD01.PROD.OUTLOOK.COM (10.174.147.7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1261.13; Fri, 14 Jul 2017 14:29:10 +0000 Received: from PN1PR01MB0879.INDPRD01.PROD.OUTLOOK.COM ([10.174.147.8]) by PN1PR01MB0879.INDPRD01.PROD.OUTLOOK.COM ([10.174.147.8]) with mapi id 15.01.1261.018; Fri, 14 Jul 2017 14:29:10 +0000 From: Lisa Williams To: "freebsd-questions@freebsd.org" Subject: Hosted VoIP Contact List Thread-Topic: Hosted VoIP Contact List Thread-Index: AdL8rQxWHHeWUgS+Rp6MEHGW7UJZ5A== Date: Fri, 14 Jul 2017 14:26:03 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: freebsd.org; dkim=none (message not signed) header.d=none;freebsd.org; dmarc=none action=none header.from=digitaldatatechno.com; x-originating-ip: [106.51.22.45] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; PN1PR01MB0878; 7:YM+f/KqEcO4DgbCiSO4812cEKA7bXekOJOHfZqI0r3YgMOps19f/p9XXHcATN8h1Q+07mbykcLqBCReE6nP2uKkE+Lxdd9jezLQGG0Ssoe02rTGKiA2WXVYFBkZXxU0EhLhnhSpVsMJjES/bpGnKLFtLi88DEALsJngwHhNpOD2dOCgyl+QBcH4EOtdIeFEy9Zo8RkNnuhtRfZADq/ttdlsea1IJ/bss3V1QenrB9GmsRTDTBAUHgl/LiLa7M0O/uuno3KhlLIwFKTdl5/vvx6U4F49viWogEDCiH5imaSirVkWO4Hrb0JMG5sVMns1eIq6cY09MronbfZO+kKl67H51EexjOWwjnHDTDEI7O3PKUKKIRtgScFrjwcRLQKR/8WTQrveb+MeSiFJ9JYQTzu8564RTNLy02hksNBItRb2c9QpselDxOBpbP8tsvZmLrbr4WSSDAFDEOlJZ+uqjSvsHlGyMIxH89DhB4OaYZpM8X2oX2S6VK6v2X5IKhG49o0648B1bKRw49iuzP6yhhTz7ERXrySJdMj2MCwzh+X82HFwWFubFnEb6+aRVdzYpsxmzEuJ8yu73jEmVzM4mrgZ8UkYmH8G7zdttyVbu9CMgtMfNFRnJKZ8lwXLRFbFvWxbYnp3LlbpiQTq1RWDnpu3GHI76kAWkrYzg2OwFFyedCKUKykyOPYAt4jAlU+oor2gVPGUJ6u6uJ4mf4lgsq7b1X3Ce4gyHUmDbip+K2QmKeEL0ov6pVaolgPuT7jWtVIARzoQLHBYOy8MHUvtaqlevRZIIhx5/JQag3DpJQaU= x-ms-office365-filtering-correlation-id: f8729612-4549-49dd-6945-08d4cac4b1aa x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(300000503095)(300135400095)(2017052603031)(201703131423075)(201702085554020)(201702085553020)(201702085551020)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:PN1PR01MB0878; x-ms-traffictypediagnostic: PN1PR01MB0878: x-exchange-antispam-report-test: UriScan:(151999592597050)(26388249023172)(236129657087228)(48057245064654)(148574349560750)(21748063052155); x-microsoft-antispam-prvs: x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(2017060910075)(100000703101)(100105400095)(93006095)(93001095)(10201501046)(3002001)(6041248)(20161123555025)(20161123564025)(2016111802025)(20161123562025)(20161123560025)(20161123558100)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(6043046)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:PN1PR01MB0878; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:PN1PR01MB0878; x-forefront-prvs: 0368E78B5B x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39410400002)(39850400002)(39400400002)(39450400003)(39840400002)(74316002)(2906002)(6306002)(3480700004)(33656002)(9456002)(25786009)(53936002)(7736002)(2351001)(2501003)(54896002)(5640700003)(3280700002)(6436002)(478600001)(55016002)(5660300001)(3660700001)(50986999)(54356999)(7696004)(14454004)(8936002)(189998001)(68736007)(3846002)(6116002)(102836003)(110136004)(6666003)(6506006)(38730400002)(9686003)(2900100001)(77096006)(6916009)(223583001)(66066001)(8676002)(81166006)(86362001)(26710200004); DIR:OUT; SFP:1101; SCL:1; SRVR:PN1PR01MB0878; H:PN1PR01MB0879.INDPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; MLV:nov; PTR:InfoNoRecords; LANG:en; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: digitaldatatechno.com X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Jul 2017 14:26:03.4370 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 16374125-200f-4766-a98f-7e476a02eea1 X-MS-Exchange-Transport-CrossTenantHeadersStamped: PN1PR01MB0878 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 14:29:16 -0000 Hello there, Hope you having a great day! Would you be interested in acquiring the list of customers or companies usi= ng Hosted VoIP Contact List? We also have other Technology Users like: 8x8, RingCentral, Mitel, ShoreTel= , Ooma, Five9, Vonage, Verizon Wireless, Avaya, Dialpad, Mitel, AT&T, T-Mob= ile, ShoreTel and many more. If you're interested please let me know the geography and job title you are= looking out to target for so that we can provide you with counts, pricing,= sample file and more information in my next email. Await your response! Regards, Lisa Williams Demand Generation To Opt Out, please respond "Leave Out" in the Subject line. From owner-freebsd-questions@freebsd.org Fri Jul 14 14:34:53 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F0720DA3129 for ; Fri, 14 Jul 2017 14:34:53 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 88ADF67B66 for ; Fri, 14 Jul 2017 14:34:53 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wm0-x231.google.com with SMTP id i127so24636249wma.0 for ; Fri, 14 Jul 2017 07:34:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-transfer-encoding; bh=aHonkdBt1fVpWhIt/knY3gwhC8FHgjLJ0ll1wYW74kk=; b=bLQfyaDqf4blljfoqqqG8L5Rd3CigRBIIMyda44AbpduQ+fJYsdidKprzXWcuYZbG5 RiKrRL1STLB5pXe87bZhc3ksuRYdrscS0zihufPY865Q9RH2ugQ7kJuBLCBfbbS3hwMR cv8q4PUDMqDzNQjPYEXKu2pzDrpea8Vqc/SEp+REEVlJ6PEsPhayfJaAeREtXGtgxx+i 02lLRAdc3jDBBTPmn0pTWg1jhTwmJxEXy09cv7o91r6b2nYbjGUni4n3qu/ZkYb7Gas3 5v8yKXrSyzL9lFfdfHRojTVRSMi3QF4tpqnQjSDvK4787ZJkudZgyyc4liZfNNTcZQNl 7Cpw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=aHonkdBt1fVpWhIt/knY3gwhC8FHgjLJ0ll1wYW74kk=; b=eat5QsPx41+2TknLl64ric9VKA//UdSBlXp9/q2ZJ8S5IaJ7+Kimf/CjlRmJsxZJpd 0BNRDTQeBbVNl0sf6S+Q6dp56ImPGYFzgdFJ+iYqk9U2SMURMPmVwIn+3h2z590uAO5O GAWNmya2gOhhKz2sJ5WoLpgBgYr8dcyUUDTqRj3+yX/VqushtQ6qkTU2jzNwBZbVYjph WB3sJCI3PC2UC/HiZMFGBiQMYr8ENHSLkb8oIC9Awz44U7rUx1kC9XrPXsnuR9N5vaIw DScBHetGwYvbumb09wmO8FYAZ75MJGB4QAzYqExyA4+iwIIkRCz4RXnFDJ9DeERSoilC Elpw== X-Gm-Message-State: AIVw111CulGVkcvz4Z6ZltqtI9Vw73Uiy2fjFfcl7wbjDpedvdPbptej 4ijqwz5DaKdddGFZ X-Received: by 10.28.74.14 with SMTP id x14mr3085399wma.15.1500042891737; Fri, 14 Jul 2017 07:34:51 -0700 (PDT) Received: from gumby.homeunix.com ([81.17.24.158]) by smtp.gmail.com with ESMTPSA id p99sm8338653wrb.6.2017.07.14.07.34.48 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 14 Jul 2017 07:34:49 -0700 (PDT) Date: Fri, 14 Jul 2017 15:34:46 +0100 From: RW To: freebsd-questions@freebsd.org Subject: Re: Unable to set rule using service name Message-ID: <20170714153446.1fa4241e@gumby.homeunix.com> In-Reply-To: <20170714145347.40401bf7@gumby.homeunix.com> References: <20170714145347.40401bf7@gumby.homeunix.com> X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.31; amd64-portbld-freebsd10.3) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 14:34:54 -0000 On Fri, 14 Jul 2017 14:53:47 +0100 RW wrote: > On Fri, 14 Jul 2017 16:43:56 +0530 > Kulamani Sethi wrote: > > > Hi, > > I want to set a rule for a particular service URL which running on a > > remote server. > > I know the IP but don't know the port number where that service is > > running. If i set rule for IP then it will applied for entire > > services running over there. > > > > There is a option in IPFW rule we can set either port number or > > name, but it does not accepting using name. Here is a example for > > my case. > > > > suppose URL for test1 service http://x.x.x.x/test1 > > URL for test2 service http://x.x.x.x/test2 > > > > I tried a rule, "ipfw add 104 deny log ip from x.x.x.x test1 > > test1 and test2 aren't port numbers, the port number here is 80 for > http I didn't put that very well. The name that you can use in place of a port number is the name of a protocol that uses that port, in this case "http". The name has to be defined in /etc/services From owner-freebsd-questions@freebsd.org Fri Jul 14 16:32:58 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B28ADDA6CEF; Fri, 14 Jul 2017 16:32:58 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2E94C6BE48; Fri, 14 Jul 2017 16:32:57 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.180.149.38]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0Lux3h-1detKC2JNJ-0103GT; Fri, 14 Jul 2017 18:32:49 +0200 Date: Fri, 14 Jul 2017 18:32:48 +0200 From: "O. Hartmann" To: "Andrey V. Elsukov" Cc: FreeBSD CURRENT , "O. Hartmann" , FreeBSD Questions Subject: Re: Inter-VLAN routing on CURRENT: any known issues? Message-ID: <20170714182055.3cb1768a@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20170712214334.4fc97335@thor.intern.walstatt.dynvpn.de> <20170713211004.13492aef@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/3=t_J+X+OLY8=raZazOl390"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:AaoerBJpBE5VPTrXV7GVepINPT3JlvWXtIVtVCV01d5sdF1dMTL Z0zZpvrrl2Y+OaDH8bz3xbG5DSd2i1p0rONmMqGXdbUwstanWIkODGNuzvMibhAy2eAU7NY 4jL8e+kji+VqnMgvn2bUfGFVxf9eIFZgxLilLV3rfkpane16n+Gr8yVSPRTmO6PX+zF8++S mLq2oLZjQ/ev06CdR/B+w== X-UI-Out-Filterresults: notjunk:1;V01:K0:8fiUIRnHfVU=:U/xeMCQqVWwAZa9toSEUjK jySiNO3jUbLXgZwUngPejK4ghdujvR6jqnxJ5y8U5cc4LOCvFh122yfPPK5ILrElMEy96WgAx Gyf/kMr31i2lirwPPNTYv1z/wz9c2aQSAccWdYD9TeJTvM3nrRoDAv8c5d03uVxZCowpGB1r5 ++FshfF+MC4tJbLKIOwgSTtBO87sHffF0UilF6IaP2PB7vuHnTzVCamN1o+3x7pvYCZK5WZzI h5rrH9+hANh0xHX8iN/wOBlmUscz2cILigzySf8SXykuN7Ua6F+Toek6FEynfb7bXhwG6dZcQ LPbqQxMopuRi/CseWeIkG7zKQ9iuayCkChJqGCIteVBxHKcG4qgtLkZWloAOPjZ3iV/Sbx+fx cVucDV8gaOYFGkjhka/jVJ/J52Usu5/U6ab9elVCdyOBWuRAyi+C6yRti5buVv2fXxkv/c0T5 KTnZ3+xEAgYaVACS8MDsDl5pkpGNY/Y/q29fN08sOO+wrbo0Pci/wClGJ6GnyO14pV7PwLw0i ZtUrp5U/xqFdGRjAkA6duMO2EsFz0aglmFLu+ddtEitDX4pcHfwIEnLIRJAjKSqncHAVyL5Ia T5IQpmZ/9GaEhnvCBXxv0vGxCNmxzxVemfk2uD16pf93G6nMyemIS3Hlcpbuc3VRKz9i4eld5 HT5k7K5Z3kP1PXWpOYFoNByPyzVZuMkP+Muw1WF8JN0SpfgaWZrBqDM6pZ0XBS6imKODQNzbb iWM6SEmL4trvhkSKJaoHWx6x4ko/bYbAw+s7e0j0zjLdpVZrmbz6gvuwkBCwW/1JPNctyoEbN Mx4QvJT3BtwxmGLyi9t71RvEOd9ZQ== X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 16:32:58 -0000 --Sig_/3=t_J+X+OLY8=raZazOl390 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am Fri, 14 Jul 2017 15:00:30 +0300 "Andrey V. Elsukov" schrieb: > On 14.07.2017 14:42, O. Hartmann wrote: > > I use in-kernel NAT. IPFW is performing NAT. In firewall type "OPEN" fr= om the > > vanilla rc.conf, IPFW has instance "nat 123" which provides then NAT. = =20 >=20 > I never used default config types for firewall, so, it would be nice to > see what rules do you have. Me neither except on some hosts with very little complications in their set= ups or simple clients. >=20 > # ipfw show The OPEN firewall rules, which show the very same behaviour as I stated bef= ore: root@gate:~ # ipfw list 00050 nat 123 ip4 from any to any via tun0 00100 allow ip from any to any via lo0 00200 deny ip from any to 127.0.0.0/8 00300 deny ip from 127.0.0.0/8 to any 65000 allow ip from any to any 65535 deny ip from any to any > # ipfw nat show config root@gate:~ # ipfw nat show config ipfw nat 123 config if tun0 log or ipfw nat 1 config if tun0 log same_ports reset redirect_port tcp 192.168.0.= 111:9734 9734 redirect_port tcp 192.168.0.111:5432 5432 redirect_port udp 192.168.2.1:242= 7 2427 redirect_port udp 192.168.2.1:4569 4569 redirect_port udp 192.168.2.1:5060 = 5060 redirect_port tcp 192.168.2.1:5060 5060 redirect_port tcp 192.168.0.111:443= 443 redirect_port tcp 192.168.0.111:80 80 redirect_port tcp 192.168.0.111:22 22 >=20 > >> VLANs work on the layer2 =20 > > According to 1): > >=20 > > I consider the settings of the switch now as correct. I have no access = to the > > router right now. But I did short experiments yesterday evening and it = is > > weird: loged in on thr router, I can ping every host on any VLAN, so IC= MP > > travel from the router the right way to its destination and back. > >=20 > > From any host on any VLAN that is "trunked" through the router, I can p= ing any > > other host on any other VLAN, preferrably not on the same VLAN. By cutt= ing off > > the trunk line to the router, pinging stops immediately. > >=20 > > From any host on any VLAN I can ping any host which is NATed on the out= side > > world. > >=20 > > From the router itself, I can ssh into any host on any VLAN providing s= sh > > service. That said, according to question 3), NAT is considered to be s= etup > > correctly. > >=20 > > Now the strange things: Neither UDP, nor TCP services "flow" from hosts= on one > > VLAN to hosts on a different VLAN. Even ssh doens't work.=20 > > When loged in onto the router, I can't "traceroute" any host on any VLA= N. =20 >=20 > This is most likely due to the problem with firewall rules. > If you set net.inet.ip.firewall.enable=3D0, does it solve the problem with > TCP/UDP between hosts on a different VLANs? net.inet.ip.firewall.enable does not exist, I suppose it is net.inet.ip.fw.= enable. Not, it doesn't change anything, last rule in my list is deny all, as you c= an see above (in-kernel). >=20 > > According to question 2), the ability to ping from, say, a host on VLAN= 1000 to > > another host on VLAN 2 passing through the router would indicate that b= oth > > sides know their routes to each other. Or am I wrong? =20 >=20 > Yes. >=20 > > I got words from Sean bruno that there might be a problem with the Inte= l i210 > > chipset in recent CURRENT - and the hardware on the PCEngine APU 2C4 is= three > > i210. I'm aware of the problem since r320134 (the oldest CURRENT I star= ted > > experimenting with the VLAN trunking). =20 >=20 > It is very strange problems, why ICMP works, but TCP/UDP does not? :) > You can try to disable any type of offloading for the card, there were > some problems in the past with checksum offlading, that may lead to the > problems with TCP, but this usually should be noticeable in the tcpdump > output. >=20 I tried that, but somehow I do not have any check: ifconfig_igb1=3D"up" #ifconfig_igb1=3D"inet6 ::1 prefixlen 64 mtu 6121" create_args_igb1=3D"-tso -lro -rxcsum -txcsum -rxcsum6 -txcsum6 -vlanhwtso = -vlanhwcsum -vlanhwfilter -vlanhwtag" and ifconfig igb1: igb1: flags=3D8843 metric 0 mtu 1500 options=3D6525bb Kind regards, Oliver --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/3=t_J+X+OLY8=raZazOl390 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWWjyMAAKCRDS528fyFhY lG8wAf4rs8/mrXg5Xrh1nXcf81faUVZwpFe/W4c8AlMevv7ESJ9DyJnEU93gIVNM 92pShy09yMT/n9QwGFa+uyli3GXuAfwLTVjWDGxKuRyH0988UCdVZ1Z+RnzJ2xOI axcHT+k51gMLxQHRQ8GJu+gl7Ve4WbadfxV4FDFBpobPsxwk4Cmj =3HSF -----END PGP SIGNATURE----- --Sig_/3=t_J+X+OLY8=raZazOl390-- From owner-freebsd-questions@freebsd.org Fri Jul 14 17:01:43 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BA6BADA7CFE; Fri, 14 Jul 2017 17:01:43 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3D9046E215; Fri, 14 Jul 2017 17:01:42 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id v6EH1VNF095674; Sat, 15 Jul 2017 03:01:31 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sat, 15 Jul 2017 03:01:31 +1000 (EST) From: Ian Smith To: Kulamani Sethi cc: freebsd-questions@freebsd.org, freebsd-ipfw@freebsd.org Subject: Re: Unable to set rule using service name In-Reply-To: Message-ID: <20170715024608.T92704@sola.nimnet.asn.au> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 17:01:43 -0000 On Fri, 14 Jul 2017 16:43:56 +0530, Kulamani Sethi wrote: > Hi, > I want to set a rule for a particular service URL which running on a remote > server. > I know the IP but don't know the port number where that service is running. > If i set rule for IP then it will applied for entire services running over > there. > > There is a option in IPFW rule we can set either port number or name, but > it does not accepting using name. Here is a example for my case. > > suppose URL for test1 service http://x.x.x.x/test1 > URL for test2 service http://x.x.x.x/test2 > > I tried a rule, "ipfw add 104 deny log ip from x.x.x.x test1 to any". Got > error "ipfw: missing "to'' ". > *I want to set rule for test1 where I have no idea about port.* > *Also please help me how to know port number if any way is there.* RW well described (in freebsd-questions@) the relationship between port numbers and service names in /etc/services; assuming you know the name, that gives you the number. Are 'test1' and 'test2' real examples, or placeholders for real service names? In any case, you cannot specify a port number in a rule with proto 'ip'; when specifying port/s you need to specify 'udp' or 'tcp' protocol. Can you give an example of the actual packets (protocol, port number/s) that you want to block? cheers, Ian From owner-freebsd-questions@freebsd.org Fri Jul 14 17:03:06 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0F8E4DA8011 for ; Fri, 14 Jul 2017 17:03:06 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B1DF6E3CF for ; Fri, 14 Jul 2017 17:03:05 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id v6EH33b2049074 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 14 Jul 2017 11:03:04 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id v6EH33xR049071; Fri, 14 Jul 2017 11:03:03 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Fri, 14 Jul 2017 11:03:03 -0600 (MDT) From: Warren Block To: Arthur Chance cc: Doug Hardie , David Christensen , freebsd-questions@freebsd.org Subject: Re: Unusual Question In-Reply-To: <0ccfaae9-6fdb-adfa-71b2-5dd3978f41b3@qeng-ho.org> Message-ID: References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> <0ccfaae9-6fdb-adfa-71b2-5dd3978f41b3@qeng-ho.org> User-Agent: Alpine 2.21 (BSF 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (wonkity.com [127.0.0.1]); Fri, 14 Jul 2017 11:03:04 -0600 (MDT) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 17:03:06 -0000 On Fri, 14 Jul 2017, Arthur Chance wrote: > On 14/07/2017 07:11, Doug Hardie wrote: >> >>> On 13 July 2017, at 21:44, David Christensen wrote: >>> >>> On 07/09/17 02:57, Doug Hardie wrote: >>>> I have a FreeBSD 9.3 remote server that needs to be purged. I know that rm -rf / will remove all the directory entries, but I need to write over the drive. I thought that dd if=/dev/zero of=/dev/ada0 might do the trick, but it gives an not permitted error. The whole thing can crash and burn at the end. This is an unmanned site so moving drives is not viable. >>> >>> If the machine has BIOS and the system drive isn't too large, write an assembly program that fits into the MBR bootstrap code area to wipe the rest of the drive, assemble the program, write it into the MBR, and reboot. >>> >>> >>> Bonus: the program deletes the MBR when done wiping the rest of the drive. >> >> Neat idea, but I have a number of these systems and they all use different disk drives. That would be a lot of work writing drivers for each type. > > How about using the BIOS extended write sector call (INT 13h, AH=43h) in > your code? That should be portable. Won't that choke after 2TB? It might wrap around to the start of the drive after the 2TB mark, or just fail. Failure would be better, at least it would mean that half of a 4TB drive might be left intact without notice. But this idea of having a self-destructive boot block has some other problems. A tiny space for code, a dangerous thing to have lying around, and if you have to reboot into it, might as well reboot into mfsBSD (http://mfsbsd.vx.sk/) and be sure that it works. For SSDs, the Secure Erase option might be viable. I have not yet had that work in the couple of times I've tried it, but that could be due to improper usage or possibly lack of support on the old SSDs being used. From owner-freebsd-questions@freebsd.org Fri Jul 14 19:37:12 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F3134DAAAD6 for ; Fri, 14 Jul 2017 19:37:12 +0000 (UTC) (envelope-from steven_nikkel@ertyu.org) Received: from vmx.ertyu.org (vmx.ertyu.org [IPv6:2001:19f0:5c00:944f:5400:ff:fe1a:d00]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7984D7319F; Fri, 14 Jul 2017 19:37:12 +0000 (UTC) (envelope-from steven_nikkel@ertyu.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ertyu.org; s=standard; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=ADXtWArJ81GHcFU3EdhNuWBAMFIDRb/XATTqfFzU8+w=; b=EzM3v7RqCgBGY72DrlNw2zuOX+ 5rws6Fshf1ii82SkWRLpyVF7LNOW/6CpSReVtnx+jlWOMv7WIgiUg447yFsejHS659KNGT6fEH3wX F2IcsWYGtuLNYktrfixO+6pOcp6NepZ5U+qL1ttQKa7F85Ua2Hu9QO/A+rhE/2I8rBu2INThlE3bZ txhHrRg/v8GcfO8fyPt/qYMpQx1aVT8w7nucVlPHyzBslvnJwxbXOdWf4ZRgLFm4Ojnm8qGCNeEuZ UOHXzGl4AtSkiy/DAlAH8zxQuaa2AmkmoQgLCMivJivKJaChpUb0YTXadcnE3gb0XKgZFAPwCVcDV 32KlZE1w==; Subject: Re: OpenCL Issues To: Jan Beich Cc: freebsd-questions@freebsd.org References: From: Steven Nikkel Message-ID: <1b3fafb4-1f41-1ef0-dce5-3c97ccb39570@ertyu.org> Date: Fri, 14 Jul 2017 14:37:09 -0500 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 19:37:13 -0000 On 2017-07-14 8:13 AM, Jan Beich wrote: > Steven Nikkel writes: > > See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217635 > Thanks, work around from the bug report solves my issue with beignet and I can successfully use OpenCL on that host. Second host where I was testing against pocl has some other issue: # clinfo Number of platforms 1 Platform Name Portable Computing Language Platform Vendor The pocl project Platform Version OpenCL 2.0 pocl 0.14, LLVM 4.0.1 Platform Profile FULL_PROFILE Platform Extensions cl_khr_icd Platform Extensions function suffix POCL Segmentation fault (core dumped) #0 0x0000000802d25075 in hwloc_topology_set_userdata_import_callback () from /usr/local/lib/libhwloc.so.5 #1 0x0000000802d24f2d in hwloc_topology_set_userdata_import_callback () from /usr/local/lib/libhwloc.so.5 #2 0x0000000802d24a77 in hwloc_topology_set_userdata_import_callback () from /usr/local/lib/libhwloc.so.5 #3 0x0000000802d0b95b in hwloc_topology_load () from /usr/local/lib/libhwloc.so.5 #4 0x0000000801722913 in pocl_cpuinfo_detect_compute_unit_count () from /usr/local/lib/libpocl.so.1.7.0 #5 0x000000080171e8dc in pocl_cpuinfo_detect_compute_unit_count () from /usr/local/lib/libpocl.so.1.7.0 #6 0x00000008017193e3 in std::__1::vector >::__push_back_slow_path () from /usr/local/lib/libpocl.so.1.7.0 #7 0x00000008016f1fb4 in ?? () from /usr/local/lib/libpocl.so.1.7.0 #8 0x0000000800837a4a in clGetDeviceIDs () from /usr/local/lib/libOpenCL.so.1 #9 0x0000000000401fb9 in ?? () #10 0x0000000000409867 in ?? () #11 0x000000000040151f in ?? () #12 0x0000000800632000 in ?? () #13 0x0000000000000000 in ?? () From owner-freebsd-questions@freebsd.org Fri Jul 14 19:56:17 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 08273DAAEED for ; Fri, 14 Jul 2017 19:56:17 +0000 (UTC) (envelope-from srs0=kjah=6r=mail.sermon-archive.info=doug@sermon-archive.info) Received: from mail.sermon-archive.info (sermon-archive.info [71.177.216.148]) by mx1.freebsd.org (Postfix) with ESMTP id E93F673961 for ; Fri, 14 Jul 2017 19:56:16 +0000 (UTC) (envelope-from srs0=kjah=6r=mail.sermon-archive.info=doug@sermon-archive.info) Received: from [10.0.1.251] (mini [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 3x8NjQ4RRCz2fkbM; Fri, 14 Jul 2017 12:56:10 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Unusual Question From: Doug Hardie In-Reply-To: <20170714095950.GA72707@erix.ericsson.se> Date: Fri, 14 Jul 2017 12:56:10 -0700 Cc: freebsd-questions@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <4B439F2B-B175-480C-8EEE-C200AA16A456@mail.sermon-archive.info> References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> <20170714095950.GA72707@erix.ericsson.se> To: Raimo Niskanen X-Mailer: Apple Mail (2.3273) X-Virus-Scanned: clamav-milter 0.99.2 at mail X-Virus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 19:56:17 -0000 > On 14 July 2017, at 02:59, Raimo Niskanen = wrote: >=20 > This thread reminds me of the argument that you should always encrypt = your > hard disk. For a remote site you could have the key on a key = partition for > some crypto systems. >=20 > Then all you have to do is destroy the key, which is much easier. >=20 > (For an SSD drive to protect against harcore forensics I do not know = how to > ensure that the data is gone, though) >=20 >=20 > On Thu, Jul 13, 2017 at 09:44:30PM -0700, David Christensen wrote: >> On 07/09/17 02:57, Doug Hardie wrote: >>> I have a FreeBSD 9.3 remote server that needs to be purged. I know = that rm -rf / will remove all the directory entries, but I need to write = over the drive. I thought that dd if=3D/dev/zero of=3D/dev/ada0 might = do the trick, but it gives an not permitted error. The whole thing can = crash and burn at the end. This is an unmanned site so moving drives is = not viable. >>=20 >> If the machine has BIOS and the system drive isn't too large, write = an=20 >> assembly program that fits into the MBR bootstrap code area to wipe = the=20 >> rest of the drive, assemble the program, write it into the MBR, and = reboot. >>=20 >>=20 >> Bonus: the program deletes the MBR when done wiping the rest of the = drive. Encryption does not prevent object reuse. It may delay it a bit = depending on the strength of the key generation/algorithm used. = However, the data can be recovered. Given enough horse power, or good = information into the key generation process, the data can be made = available. In most cases, it's actually pretty easy. Overwriting is = the only method that makes the information non-recoverable (and still = leaves the media useful). Years ago in the USAF, we used to use a power sander to remove all the = oxide from the disk. It left a bright, shiny aluminum disk that had no = information on it. The bits were still there on the oxide particles, = but the sander blew them all over the place and its highly unlikely that = anyone could have gathered them all up, let alone put them back into the = proper order. One of those disks was made into a going away memento and = is displayed here. The other option was a thermite grenade which was = tested and verified was extremely effective. Even the platter vanished. From owner-freebsd-questions@freebsd.org Fri Jul 14 23:11:08 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E821DAE20F for ; Fri, 14 Jul 2017 23:11:08 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 579007DEA1; Fri, 14 Jul 2017 23:11:08 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id A7B4015AA1; Fri, 14 Jul 2017 23:11:07 +0000 (UTC) From: Jan Beich To: Steven Nikkel Cc: freebsd-questions@freebsd.org Subject: Re: OpenCL Issues References: <1b3fafb4-1f41-1ef0-dce5-3c97ccb39570@ertyu.org> Date: Sat, 15 Jul 2017 01:11:04 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 23:11:08 -0000 Steven Nikkel writes: > On 2017-07-14 8:13 AM, Jan Beich wrote: >> Steven Nikkel writes: >> >> See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217635 >> > > Thanks, work around from the bug report solves my issue with beignet > and I can successfully use OpenCL on that host. ^^^^^^^^^^^ Awesome! I'd like to update the port to a snapshot to pick up the fix in question upstream, LLVM 4.0 support, more optimizations and catch regressions early. Can you give it a try? https://reviews.freebsd.org/D11377 (see Download Raw Diff) > #0 0x0000000802d25075 in hwloc_topology_set_userdata_import_callback () > from /usr/local/lib/libhwloc.so.5 > #1 0x0000000802d24f2d in hwloc_topology_set_userdata_import_callback () > from /usr/local/lib/libhwloc.so.5 > #2 0x0000000802d24a77 in hwloc_topology_set_userdata_import_callback () > from /usr/local/lib/libhwloc.so.5 > #3 0x0000000802d0b95b in hwloc_topology_load () > from /usr/local/lib/libhwloc.so.5 > #4 0x0000000801722913 in pocl_cpuinfo_detect_compute_unit_count () > from /usr/local/lib/libpocl.so.1.7.0 Probably https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219562 I haven't investigated it myself. From owner-freebsd-questions@freebsd.org Sat Jul 15 00:21:24 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2334EDAF883 for ; Sat, 15 Jul 2017 00:21:24 +0000 (UTC) (envelope-from steven_nikkel@ertyu.org) Received: from vmx.ertyu.org (vmx.ertyu.org [IPv6:2001:19f0:5c00:944f:5400:ff:fe1a:d00]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F0C1A801D3; Sat, 15 Jul 2017 00:21:23 +0000 (UTC) (envelope-from steven_nikkel@ertyu.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ertyu.org; s=standard; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=HDJUuU2j8YByyfaLDFdri3TjmYbXwUUk4vPr+XxqcvQ=; b=aUjTO2F4IjSijZlvXItfu2GdYp IUkM9CaWPi0bVXl3gNLd0VsU+bKSpEEabZoHf9QNnSR9ZiLNBPrInSxUTp6zNqtVcm9fZ6TXb1uPz XhTGWnHFjS77tpbJHNt0Od/5Xn5M/CUdSeL0JzAxaUAaVZ38LSp5eZeIJLk8uxvdCcTeEJylXl8dF yOjUr3v6ASyEq3MMelAnijk0gsL5e7vusioElLLlGNP/rAv8PL/hx1HXJwR0IiDHGKDybQUZBIyJE 89CdEI7ea3h/vBC0M9VxXmRjO5JxI6P2SZ81Cn5KvbUyaCeOQgsEr8aubuAKAUK7N5Adj1DWYclj2 NrJcwvRw==; Subject: Re: OpenCL Issues To: Jan Beich Cc: freebsd-questions@freebsd.org References: <1b3fafb4-1f41-1ef0-dce5-3c97ccb39570@ertyu.org> From: Steven Nikkel Message-ID: Date: Fri, 14 Jul 2017 19:21:21 -0500 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2017 00:21:24 -0000 On 2017-07-14 6:11 PM, Jan Beich wrote: > Steven Nikkel writes: > >> On 2017-07-14 8:13 AM, Jan Beich wrote: >>> See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217635 >>> >> >> Thanks, work around from the bug report solves my issue with beignet >> and I can successfully use OpenCL on that host. > ^^^^^^^^^^^ > > Awesome! I'd like to update the port to a snapshot to pick up the fix in > question upstream, LLVM 4.0 support, more optimizations and catch > regressions early. Can you give it a try? > > https://reviews.freebsd.org/D11377 (see Download Raw Diff) > The update builds and installs. It runs clinfo fine, but I'm getting errors in my CL app, looks like it can't find the cl_amd_media_ops extension. Not sure where that error comes from as it's fine in the 1.3.1 from the existing port. Error building cl program on device 0 Error code -11, message: Program build failure Build log returned 624 bytes Build Log: stringInput.cl:56:17: warning: implicit declaration of function 'amd_byteal ... stringInput.cl:12:19: note: expanded from macro 'SWAP' stringInput.cl:56:17: error: function with no prototype cannot use the spir ... stringInput.cl:12:19: note: expanded from macro 'SWAP' stringInput.cl:58:12: warning: implicit declaration of function 'amd_bitali ... stringInput.cl:11:20: note: expanded from macro 'ROTL' stringInput.cl:58:12: error: function with no prototype cannot use the spir ... stringInput.cl:11:20: note: expanded from macro 'ROTL' From owner-freebsd-questions@freebsd.org Sat Jul 15 01:38:15 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1D5DCDB18FE for ; Sat, 15 Jul 2017 01:38:15 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: from h2.pinyon.org (h2.pinyon.org [65.101.20.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EC94B82393 for ; Sat, 15 Jul 2017 01:38:14 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: by h2.pinyon.org (Postfix, from userid 58) id 32A50198ED; Fri, 14 Jul 2017 18:38:07 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pinyon.org; s=DKIM; t=1500082687; bh=Spu2NbpjJSW/ARGlIflkWyTApxnKehUGgRcVhP5dzLk=; h=To:From:Subject:Date; b=Mdwl1AmZtN7H5htW93xJsGjjcfrTrnDtq0z+VVta11FxSsBsv+Ajw3cNWUXwjY+yh kOSjjHDnhwxUKePpJKb4WkdI2j/CFXh++tm6a6yabQ0ae6VixRGjAdXzSHW8v2RzmM WsG1N7mdr2jHZCLKbAFk77ea9fqJgZ0u5Zs+rwug= X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on h2.n1.pinyon.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, URIBL_BLOCKED shortcircuit=no autolearn=ham autolearn_force=no version=3.4.1 Received: from [10.0.10.15] (h1.pinyon.org [65.101.20.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by h2.pinyon.org (Postfix) with ESMTPSA id 2D41D198D2 for ; Fri, 14 Jul 2017 18:38:06 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pinyon.org; s=DKIM; t=1500082686; bh=Spu2NbpjJSW/ARGlIflkWyTApxnKehUGgRcVhP5dzLk=; h=To:From:Subject:Date; b=T16LXySN63lbVoN2gSRcqB0VPHSYdyXEjAPH/g/KrTHT01zyxUOQ7Rp3LKbMgee1y yL7+fJE5Pszl21ectQJezhFA6ThhAo9BwQ6vcgoC5YVfcrXB5SQM6ylMHljFpbc0Fc YgKNS73U5tBc7izuHaG3Q+ua/xTBJvccZAuO62b4= To: freebsd-questions@freebsd.org From: "Russell L. Carter" Subject: cups and a Brother HL-L2340DW Message-ID: <9d8aae34-8d78-5a9d-1f0d-adae7d5e7c27@pinyon.org> Date: Fri, 14 Jul 2017 18:38:05 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2017 01:38:15 -0000 So this printer is the current wirecutter.com recommendation for best cheap laser printer. After introducing it to dhcpd so that the IP address is fixed, I was ready to introduce it to cups. Add Printer -> Discovered Network Printers -> select Brother HL-L2340D series... (next screen) Connection: lpd://BRWD80F9967A5AB/BINARY_P1 (hit Continue) Or Provide a PPD file: Browse... brother-HLL2340D-cups-en.ppd -> Add Printer -> Set Default Options Which gives me, after some screen changes: Brother_HL-L2340D_series (Idle, Accepting Jobs, Not Shared) Description: Brother HL-L2340D series Location: Driver: Brother HL-L2340D for CUPS (grayscale, 2-sided printing) Connection: lpd://BRWD80F9967A5AB/BINARY_P1 Defaults: job-sheets={job_sheets_default} media=iso_a4_210x297mm sides=one-sided I hit ^P, the print dialog comes up, I select this printer, and all looks good, except if I go look at jobs, I see: ID Name User Size Pages State Control Brother_HL-L2340D_series-124 Unknown Withheld 1k Unknown canceled at Fri Jul 14 18:08:00 2017 What gives? I am on the verge of installing linux on a box to deal with this. Thanks, Russell From owner-freebsd-questions@freebsd.org Sat Jul 15 02:05:31 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 15B0FDB2E6B for ; Sat, 15 Jul 2017 02:05:31 +0000 (UTC) (envelope-from alexmiroslav@gmail.com) Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ACAB7834A6 for ; Sat, 15 Jul 2017 02:05:30 +0000 (UTC) (envelope-from alexmiroslav@gmail.com) Received: by mail-wr0-x235.google.com with SMTP id w4so67536wrb.2 for ; Fri, 14 Jul 2017 19:05:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=b+cbMgBhB5F0myFgsvUSul4smqmP1sdRco70LaNfQZ8=; b=bz9Boaz4NiObciu6LoE+jSThAFEPjHXL72muTIssx9x9YgWEZ8iq3gVcI7YSwOqPQ/ Rye8B8gdU8uWhCm4fmWjpZ5/BCMMGsKfa3sFVCvAF1rMBbaAZW7ovztQ6/Ee71Frm5Gc 366wOTIMvYsdFCqQYvpL7wYE44JZeURi9oYR+PMZRfRmho1jEFbkuux3A+vORQCEkCX2 xuKWY2B0h2Gb6AsHwUgtR/qtkV/WCTEbTS3jjr9ZmRBX0l0kQd+xXmWDscn7XafPWzQY jyfCI745EfIZNw5WP3LAuOATsFMjta9jSf49wZTKVhy0YnX4qjTHKAG4L3lr7/fr55WK c/5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=b+cbMgBhB5F0myFgsvUSul4smqmP1sdRco70LaNfQZ8=; b=ioSpGuLS+O5Hnc2q/Yl4YiyyJucCcvwJgt44EAEo2u97S56cWJtmq5hZ0njELAj34S WAXW8ga1c0GSsljeUfuobqBErbB82tyv9Zi6TFM/pdz1rA/l/Q7TN+uSMsDpGN0+s/BT zfT3BkeI5wOp2Uu0CNjcuLqFtWIrC8gUHiYPPnLN75SfDfRN+l6dGkF0K/IZOKEeyjjq ygZ6/zpxMDRhubNEp+GTRqzf2Zi8VpcD+wpa9agbe5sXgn3Np9a3MMW2hsrO74GpIDlj 2MnUpSo9WIdil4tFAbUptnxJWtPIQdcuumrp+jqxcVxgP4BCXwzYUq5kY2eBbbnWHeg0 5xBA== X-Gm-Message-State: AIVw113HXvilwemO0Ea+ckBhuGWoVqYg+NgG+SXyn8z6Z5ZWnIXj+9IS niLHdnEm2l5Zs78kkJtRNPLYZUl3/z0p X-Received: by 10.223.138.252 with SMTP id z57mr5501550wrz.66.1500084328086; Fri, 14 Jul 2017 19:05:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.139.9 with HTTP; Fri, 14 Jul 2017 19:05:27 -0700 (PDT) From: Aleksandr Miroslav Date: Fri, 14 Jul 2017 19:05:27 -0700 Message-ID: Subject: mfsbsd -- disk partitioning and bsdinstall usage To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2017 02:05:31 -0000 I like using the mfsbsd mini edition to install FreeBSD because it is only 23MiB big. However, the included zfsinstall script doesn't seem to partition things the way the native bsdinstall script does. I get this: tank tank/root tank/root/tmp tank/root/var Instead of this: zroot zroot/ROOT zroot/ROOT/default zroot/tmp zroot/usr zroot/usr/home zroot/usr/ports zroot/usr/src zroot/var zroot/var/audit zroot/var/crash zroot/var/log zroot/var/mail zroot/var/tmp I can change the pool name from tank to zroot, but I don't know how to partition like above. I tried another way to install: boot into freebsd using the mfsbsd iso, and then running bsdinstall, but bsdinstall always errors out. Am I using mfsbsd wrong? From owner-freebsd-questions@freebsd.org Sat Jul 15 12:14:29 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4FFDBAF9184 for ; Sat, 15 Jul 2017 12:14:29 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from bede.home.qeng-ho.org (bede.qeng-ho.org [217.155.128.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fileserver.home.qeng-ho.org", Issuer "fileserver.home.qeng-ho.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DA6B06E9AD for ; Sat, 15 Jul 2017 12:14:28 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from arthur.home.qeng-ho.org (arthur.home.qeng-ho.org [172.23.1.2]) by bede.home.qeng-ho.org (8.15.2/8.15.2) with ESMTP id v6FCEJKQ034005; Sat, 15 Jul 2017 13:14:19 +0100 (BST) (envelope-from freebsd@qeng-ho.org) Subject: Re: Unusual Question To: Warren Block Cc: freebsd-questions@freebsd.org References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> <0ccfaae9-6fdb-adfa-71b2-5dd3978f41b3@qeng-ho.org> From: Arthur Chance Message-ID: <01c6a4c3-1dd9-ee46-a224-a3a2993c377e@qeng-ho.org> Date: Sat, 15 Jul 2017 13:14:19 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2017 12:14:29 -0000 On 14/07/2017 18:03, Warren Block wrote: > On Fri, 14 Jul 2017, Arthur Chance wrote: > >> On 14/07/2017 07:11, Doug Hardie wrote: >>> >>>> On 13 July 2017, at 21:44, David Christensen >>>> wrote: >>>> >>>> On 07/09/17 02:57, Doug Hardie wrote: >>>>> I have a FreeBSD 9.3 remote server that needs to be purged. I know >>>>> that rm -rf / will remove all the directory entries, but I need to >>>>> write over the drive. I thought that dd if=/dev/zero of=/dev/ada0 >>>>> might do the trick, but it gives an not permitted error. The whole >>>>> thing can crash and burn at the end. This is an unmanned site so >>>>> moving drives is not viable. >>>> >>>> If the machine has BIOS and the system drive isn't too large, write >>>> an assembly program that fits into the MBR bootstrap code area to >>>> wipe the rest of the drive, assemble the program, write it into the >>>> MBR, and reboot. >>>> >>>> >>>> Bonus: the program deletes the MBR when done wiping the rest of the >>>> drive. >>> >>> Neat idea, but I have a number of these systems and they all use >>> different disk drives. That would be a lot of work writing drivers >>> for each type. >> >> How about using the BIOS extended write sector call (INT 13h, AH=43h) in >> your code? That should be portable. > > Won't that choke after 2TB? It might wrap around to the start of the > drive after the 2TB mark, or just fail. Failure would be better, at > least it would mean that half of a 4TB drive might be left intact > without notice. It's a while since I last did any BIOS programming, but if my memory is correct the basic disk io with CHS addressing is limited to ~8GB, but the enhanced disk io routines using 48 bit LBAs can handle any existing disk. (48 bit LBAs allow disks up to 128 PiB.) The 2TB limit is in the maximum partition size in the MBR partition table, not the BIOS disk io limit. > But this idea of having a self-destructive boot block has some other > problems. A tiny space for code, a dangerous thing to have lying > around, and if you have to reboot into it, might as well reboot into > mfsBSD (http://mfsbsd.vx.sk/) and be sure that it works. Agreed. It's more of an intellectual exercise that anything else. It's not something I'd want loose in the wild. > For SSDs, the Secure Erase option might be viable. I have not yet had > that work in the couple of times I've tried it, but that could be due to > improper usage or possibly lack of support on the old SSDs being used. -- An amusing coincidence: log2(58) = 5.858 (to 0.0003% accuracy). From owner-freebsd-questions@freebsd.org Sat Jul 15 12:50:16 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 75647AF9A58 for ; Sat, 15 Jul 2017 12:50:16 +0000 (UTC) (envelope-from tijl@freebsd.org) Received: from mailrelay101.isp.belgacom.be (mailrelay101.isp.belgacom.be [195.238.20.128]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (Client CN "relay.skynet.be", Issuer "GlobalSign Organization Validation CA - SHA256 - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D77796F4FD for ; Sat, 15 Jul 2017 12:50:15 +0000 (UTC) (envelope-from tijl@freebsd.org) X-Belgacom-Dynamic: yes IronPort-PHdr: =?us-ascii?q?9a23=3AIVG5JBPDVWHQkHdpi/8l6mtUPXoX/o7sNwtQ0KIM?= =?us-ascii?q?zox0Ivr+rarrMEGX3/hxlliBBdydsKMbzbKO+4nbGkU4qa6bt34DdJEeHzQksu?= =?us-ascii?q?4x2zIaPcieFEfgJ+TrZSFpVO5LVVti4m3peRMNQJW2aFLduGC94iAPERvjKwV1?= =?us-ascii?q?Ov71GonPhMiryuy+4ZPebgFKiTanfb9+MAi9oBnMuMURnYZsMLs6xAHTontPde?= =?us-ascii?q?RWxGdoKkyWkh3h+Mq+/4Nt/jpJtf45+MFOTav1f6IjTbxFFzsmKHw65NfqtRbY?= =?us-ascii?q?UwSC4GYXX3gMnRpJBwjF6wz6Xov0vyDnuOdxxDWWMMvrRr0vRz+s87lkRwPpiC?= =?us-ascii?q?cfNj427mfXitBrjKlGpB6tvgFzz5LIbI2QMvd1Y6HTcs4ARWdZUMhfVzJPDJ6/?= =?us-ascii?q?YYQNAeoOMvpXoYbmqlsSrxayGRWgCP/zxjNWgHL9wK000/4mEQHDxAEuAdMOsH?= =?us-ascii?q?bQrN7oKqoSVue1zLLWwjXGdfxW3yz945XPfxA9oPGMX7ZwfNHRx0k1CQzKkEid?= =?us-ascii?q?p5HrMT+P0eQNqWeb4vNmWOmyhWAnrARxrSKuxscqkoTIiIMVykra+ipl3YY1Oc?= =?us-ascii?q?G4R1BhYdK+DJRQsCSaO5NtTcM4RGFopCY6xaMcuZKhYCcKz5EnyhjCYPKEa4iF?= =?us-ascii?q?+hHuWPuLLTtmi39oeKiziwuw/EWk0OHwS8u53EpMoyFYiNfDrGoN2AbW6sWfT/?= =?us-ascii?q?t9+Vqu1iiX2gDI7+FEPVg0la3GK5492rIwloQcsUDEHiLum0X5lquWdkQh+ue2?= =?us-ascii?q?8eTnZa/qpoOdN492jgHyKLghmsu4AeQjLAcOWnKU+eKn1LH5+k35WrpKguU3kq?= =?us-ascii?q?nfrp/aOdwWq62kDwNPzIou5BayAy273NkamXQLNk9JdRCbg4TxPlHBOvH4DfOx?= =?us-ascii?q?g1S2lzdrwujLPqHgApXPKnjOi7nhfaxj5EFC0wUz1s1Q64hTCrEbL/L/QlXxu8?= =?us-ascii?q?DADh8lLwy0xP7qCNtn1owAR22AGbSZP77LvV+R++IgPfKMZJMUuDb6Lfgl/OXj?= =?us-ascii?q?jXEjmVADY6amxoAXZ22iEvRhOUWZbimkvtBUW10XpREzSOiirBvKejdJe3uoFe?= =?us-ascii?q?po/DoyEp6rF6/bR4a8h7rH2z20SM54fGdDX2yNE3OgXIKDQPoJYSSJapt9kz4A?= =?us-ascii?q?fZa7RoIL7j3osxX1nek0ZtHI8zEV4MqwnON+4PfewFRrrWR5?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2BXAwCiDmpZ/6qz9VFdGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBFQEBAQECAQEBAQgBAQEBgy9UEIEUjn6PA4FqLAGXaC6FGQKDcEQUAQE?= =?us-ascii?q?BAQEBAQEBAQFqKIIzJAGCQQEFJxMcIxALGAklDyoeBhOKMwysEhGDDzqLGgEBA?= =?us-ascii?q?QEBBQIBJYMohS6DJIMmhzgFkFaOXodKjD98gXSPTJVXNiGBClIwCIdhPjYBhjQ?= =?us-ascii?q?EgjsBAQE?= X-IPAS-Result: =?us-ascii?q?A2BXAwCiDmpZ/6qz9VFdGgEBAQECAQEBAQgBAQEBFQEBAQE?= =?us-ascii?q?CAQEBAQgBAQEBgy9UEIEUjn6PA4FqLAGXaC6FGQKDcEQUAQEBAQEBAQEBAQFqK?= =?us-ascii?q?IIzJAGCQQEFJxMcIxALGAklDyoeBhOKMwysEhGDDzqLGgEBAQEBBQIBJYMohS6?= =?us-ascii?q?DJIMmhzgFkFaOXodKjD98gXSPTJVXNiGBClIwCIdhPjYBhjQEgjsBAQE?= Received: from 170.179-245-81.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([81.245.179.170]) by relay.skynet.be with ESMTP; 15 Jul 2017 14:49:02 +0200 Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org [127.0.0.1]) by kalimero.tijl.coosemans.org (8.15.2/8.15.2) with ESMTP id v6FCn1Ac029634; Sat, 15 Jul 2017 14:49:01 +0200 (CEST) (envelope-from tijl@FreeBSD.org) Date: Sat, 15 Jul 2017 14:49:01 +0200 From: Tijl Coosemans To: "Russell L. Carter" Cc: freebsd-questions@freebsd.org Subject: Re: cups and a Brother HL-L2340DW Message-ID: <20170715144901.1a53e2bc@kalimero.tijl.coosemans.org> In-Reply-To: <9d8aae34-8d78-5a9d-1f0d-adae7d5e7c27@pinyon.org> References: <9d8aae34-8d78-5a9d-1f0d-adae7d5e7c27@pinyon.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2017 12:50:16 -0000 On Fri, 14 Jul 2017 18:38:05 -0700 "Russell L. Carter" wrote: > So this printer is the current wirecutter.com recommendation > for best cheap laser printer. After introducing it to dhcpd > so that the IP address is fixed, I was ready to introduce it > to cups. > > Add Printer -> Discovered Network Printers > -> select Brother HL-L2340D series... > > (next screen) Connection: lpd://BRWD80F9967A5AB/BINARY_P1 > > (hit Continue) > > Or Provide a PPD file: Browse... brother-HLL2340D-cups-en.ppd > -> Add Printer > > -> Set Default Options > > Which gives me, after some screen changes: > > Brother_HL-L2340D_series (Idle, Accepting Jobs, Not Shared) > Description: Brother HL-L2340D series > Location: > Driver: Brother HL-L2340D for CUPS (grayscale, 2-sided printing) > Connection: lpd://BRWD80F9967A5AB/BINARY_P1 > Defaults: job-sheets={job_sheets_default} media=iso_a4_210x297mm > sides=one-sided > > I hit ^P, the print dialog comes up, I select this printer, and all > looks good, except if I go look at jobs, I see: > > ID Name User Size Pages State Control > Brother_HL-L2340D_series-124 Unknown Withheld 1k Unknown > canceled at > Fri Jul 14 18:08:00 2017 > > What gives? > > I am on the verge of installing linux on a box to deal with this. I suspect you need to use the official Linux driver from Brother. It should be possible to get this working on FreeBSD using Linux emulation but it'll require some tinkering. Install emulators/linux_base-c6 and print/ghostscript9-agpl-base. Download both the LPR printer driver and CUPSwrapper printer driver here: http://support.brother.com/g/b/downloadlist.aspx?c=us&lang=en&prod=hll2340dw_us_eu_as&os=127 Unpack the rpm packages using tar(1). They contain an /opt directory that you can move to /compat/linux/opt. Inside the directory are some Perl scripts (brother_lpdwrapper_HLL2340D, paperconfigml1 and filter_HLL2340D) where you have to change /usr/bin/perl on the first line into /usr/local/bin/perl. Edit brother_lpdwrapper_HLL2340D to replace line 87 from $PRINTER =~ s/^\/opt\/.*\/Printers\///g; into $PRINTER =~ s/^.*\/Printers\///g; Then create these symbolic links: ln -s /compat/linux/opt/brother/Printers/HLL2340D/cupswrapper/brother_lpdwrapper_HLL2340D /usr/local/libexec/cups/filter/ ln -s /compat/linux/opt/brother/Printers/HLL2340D/cupswrapper/brother-HLL2340D-cups-en.ppd /usr/local/share/cups/model/ More changes may be needed, but this should get you a bit further. The scripts seem to create log files in /tmp so you may want to look there for clues. Also in /var/log/cups. From owner-freebsd-questions@freebsd.org Sat Jul 15 15:11:41 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 90B76AFC362 for ; Sat, 15 Jul 2017 15:11:41 +0000 (UTC) (envelope-from 4250.10.freebsd-questions=freebsd.org@email-od.com) Received: from bca5.email-od.com (bca5.email-od.com [207.246.239.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5DFCA733D1 for ; Sat, 15 Jul 2017 15:11:41 +0000 (UTC) (envelope-from 4250.10.freebsd-questions=freebsd.org@email-od.com) DKIM-Signature: v=1; a=rsa-sha256; d=email-od.com;i=@email-od.com;s=dkim; c=relaxed/relaxed; q=dns/txt; t=1500131496; x=1502723496; h=x-thread-info:date:from:to:subject:message-id:in-reply-to:references:mime-version:content-type:content-transfer-encoding; bh=tZrQUrE9ha6tdIXqGsIbMmlh0o++VubYkxrw0Ovd2p4=; b=Tj9SItkXUxGhTBz7f9lhbdaYe3GLOlZLL/KVVys+5oPRVnxstLH9t5+dhvPqmNgjmUX85kL9KAGhYqEikaN8NPMdBJ4pt7HlP63wCAzaN7352XROl75TwokYVrZb0rb3wHsbckx30z5hdOyZSMgUPv+67rDjetD09Q2fKSgd7G4= X-Thread-Info: NDI1MC4xMi5kOTAwMDAwMDEyNDAwOC5mcmVlYnNkLXF1ZXN0aW9ucz1mcmVlYnNkLm9yZw== Received: from r3.h.in.socketlabs.com (r3.h.in.socketlabs.com [142.0.180.13]) by bca2.email-od.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Sat, 15 Jul 2017 11:11:24 -0400 Received: from smtp.lan.sohara.org (EMTPY [89.127.62.20]) by r3.h.in.socketlabs.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Sat, 15 Jul 2017 11:11:28 -0400 Received: from [192.168.63.1] (helo=steve.lan.sohara.org) by smtp.lan.sohara.org with smtp (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dWOk6-000Agv-3A for freebsd-questions@freebsd.org; Sat, 15 Jul 2017 15:12:26 +0000 Date: Sat, 15 Jul 2017 16:11:14 +0100 From: Steve O'Hara-Smith To: freebsd-questions@freebsd.org Subject: Re: cups and a Brother HL-L2340DW Message-Id: <20170715161114.0bf74135943cb34981bafd7e@sohara.org> In-Reply-To: <20170715144901.1a53e2bc@kalimero.tijl.coosemans.org> References: <9d8aae34-8d78-5a9d-1f0d-adae7d5e7c27@pinyon.org> <20170715144901.1a53e2bc@kalimero.tijl.coosemans.org> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; amd64-portbld-freebsd10.3) X-Clacks-Overhead: "GNU Terry Pratchett" Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2017 15:11:41 -0000 On Sat, 15 Jul 2017 14:49:01 +0200 Tijl Coosemans wrote: > On Fri, 14 Jul 2017 18:38:05 -0700 "Russell L. Carter" > wrote: > > So this printer is the current wirecutter.com recommendation > > for best cheap laser printer. After introducing it to dhcpd > > so that the IP address is fixed, I was ready to introduce it > > to cups. > > > > Add Printer -> Discovered Network Printers > > -> select Brother HL-L2340D series... > > > > (next screen) Connection: lpd://BRWD80F9967A5AB/BINARY_P1 > > > > (hit Continue) > > > > Or Provide a PPD file: Browse... brother-HLL2340D-cups-en.ppd > > -> Add Printer > > > > -> Set Default Options > > > > Which gives me, after some screen changes: > > > > Brother_HL-L2340D_series (Idle, Accepting Jobs, Not Shared) > > Description: Brother HL-L2340D series > > Location: > > Driver: Brother HL-L2340D for CUPS (grayscale, 2-sided printing) > > Connection: lpd://BRWD80F9967A5AB/BINARY_P1 > > Defaults: job-sheets={job_sheets_default} media=iso_a4_210x297mm > > sides=one-sided > > > > I hit ^P, the print dialog comes up, I select this printer, and all > > looks good, except if I go look at jobs, I see: > > > > ID Name User Size Pages State > > Control Brother_HL-L2340D_series-124 Unknown > > Withheld 1k Unknown canceled at > > Fri Jul 14 18:08:00 2017 > > > > What gives? > > > > I am on the verge of installing linux on a box to deal with this. > > I suspect you need to use the official Linux driver from Brother. It > should be possible to get this working on FreeBSD using Linux emulation > but it'll require some tinkering. The easiest way to do it is to set up a Centos 6 userland in a jail (the linux emulation is good enough for that) - use a prebuilt image the install is possible but fiddly. Then just install CUPs and the Brother drivers and away you go. I have my Brother DCP6690CW A3 inkjet running this way. -- Steve O'Hara-Smith From owner-freebsd-questions@freebsd.org Sat Jul 15 18:23:58 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5D404AFF8AF for ; Sat, 15 Jul 2017 18:23:58 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.20.71]) by mx1.freebsd.org (Postfix) with ESMTP id 3966A7E609 for ; Sat, 15 Jul 2017 18:23:57 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id 25D45CB8CEA; Sat, 15 Jul 2017 13:23:51 -0500 (CDT) Received: from 76.193.16.143 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Sat, 15 Jul 2017 13:23:51 -0500 (CDT) Message-ID: <57789.76.193.16.143.1500143031.squirrel@cosmo.uchicago.edu> Date: Sat, 15 Jul 2017 13:23:51 -0500 (CDT) Subject: Best printer makes (manufacturers) for FreeBSD From: "Valeri Galtsev" To: freebsd-questions@freebsd.org Reply-To: galtsev@kicp.uchicago.edu User-Agent: SquirrelMail/1.4.8-5.el5.centos.7 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2017 18:23:58 -0000 Dear All, Recent discussion about replacing old printer prompted me to start this thread. Basically, which makes (or manufacturers) do you use on your FreeBSD boxes? What would you recommend to watch for and avoid when choosing the printer. (I personally would prefer one manufacturer not even mentioned: Xerox. They went bad several years ago, and are banned wherever I have a voice to affect the choice... So if you tell good story about Xerox I definitely will reply with my bad one - enough for having my attitude). In one of recent threads two manufacturers were mentioned: Brother and HP (Hewlett Packard). What prompted me to start this is suggestions that for some model of Brother printer you need to install Linux support and use Linux diver. In the Department I support I use HP printers (mostly high end like Color LaserJet CP4020-CP4520; Color LaserJet 4650, but have one low end LaserJet ColorPro 400 m451). I must confess as Linux refugee, I am not total refugee yet, so my setup is probably only partly relevant. Namely, all print jobs go to printers through CUPS print server, the last is still on Linux - hadn't chance to migrate it to FreeBSD. However, when I set up printing on FreeBSD, the only things I have to do is: install CUPS, drop wherever CUPS keeps printer drivers a bunch of .ppd files (you can download these at linuxprinting.org site, basically PPD is PostScript Printer Description file, and these can be extracted from postscript printer driver manufacturer supplies, and it doesn't matter which system the driver is designed for). After that is done I set up printer on FreeBSD as you usually do in CUPS, I choose postscript driver (and if PPD for the printer is added, your printer will be in the list), and point to my print server and queue. Theoretically, I can point to printer directly (only my printers refuse connection from all but print server), so I'm sure even if I didn't have CUPS based print server running on Linux configuring printers on FreeBSD boxes would be as simple as I described. I would like to hear about other good printer manufacturers, especially cases then you set up printer as hassle-less as HP postscript printers are for me - just curious what is good out there and what is not. Thanks for all your replies! Valeri ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++ From owner-freebsd-questions@freebsd.org Sat Jul 15 19:23:34 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD74EB7A31C for ; Sat, 15 Jul 2017 19:23:34 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay10.qsc.de (mailrelay10.qsc.de [212.99.163.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5369281F24 for ; Sat, 15 Jul 2017 19:23:33 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay10.qsc.de; Sat, 15 Jul 2017 21:23:24 +0200 Received: from r56.edvax.de (port-92-195-0-242.dynamic.qsc.de [92.195.0.242]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id DB3563CBF9; Sat, 15 Jul 2017 21:23:23 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v6FJNLo0002195; Sat, 15 Jul 2017 21:23:22 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sat, 15 Jul 2017 21:23:21 +0200 From: Polytropon To: galtsev@kicp.uchicago.edu Cc: freebsd-questions@freebsd.org Subject: Re: Best printer makes (manufacturers) for FreeBSD Message-Id: <20170715212321.cbf11003.freebsd@edvax.de> In-Reply-To: <57789.76.193.16.143.1500143031.squirrel@cosmo.uchicago.edu> References: <57789.76.193.16.143.1500143031.squirrel@cosmo.uchicago.edu> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay10.qsc.de with 5717568340A X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1482 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2017 19:23:34 -0000 On Sat, 15 Jul 2017 13:23:51 -0500 (CDT), Valeri Galtsev wrote: > Recent discussion about replacing old printer prompted me to start this > thread. Basically, which makes (or manufacturers) do you use on your > FreeBSD boxes? Mostly HP laser (and a few inkpee) printers here with great success. That leads me to the assumption that with educated choice _before_ paying money, HP is always on the "nice" list. > What would you recommend to watch for and avoid when > choosing the printer. Connection: preferred via network (cable or WLAN), USB only if no other choice. Printer language: PDF, PCL or PS (at least one; if none, avoid). Being able to use PS or PDF usually indicates you don't need any printer driver at all. ;-) For HP printers _always_ check: http://hplipopensource.com/hplip-web/supported_devices/index.html Make sure it's supported. Integration of HPLIP and CUPS is easy, but you can use it with system LPR, too. A PPD file is always welcome. > (I personally would prefer one manufacturer not even > mentioned: Xerox. I'd like to add Canon here. :-) > They went bad several years ago, and are banned wherever > I have a voice to affect the choice... So if you tell good story about > Xerox I definitely will reply with my bad one - enough for having my > attitude). This one? :-) http://www.dkriesel.com/en/blog/2013/0802_xerox-workcentres_are_switching_written_numbers_when_scanning > In one of recent threads two manufacturers were mentioned: Brother and HP > (Hewlett Packard). What prompted me to start this is suggestions that for > some model of Brother printer you need to install Linux support and use > Linux diver. Check the technical (!) properties page (not the home consumer marketing speak page). Does the printer _really_ require a Linux driver? Doesn't it speak PS, PCL or PDF natively? > In the Department I support I use HP printers (mostly high end like Color > LaserJet CP4020-CP4520; Color LaserJet 4650, but have one low end LaserJet > ColorPro 400 m451). I must confess as Linux refugee, I am not total > refugee yet, so my setup is probably only partly relevant. Namely, all > print jobs go to printers through CUPS print server, the last is still on > Linux - hadn't chance to migrate it to FreeBSD. However, when I set up > printing on FreeBSD, the only things I have to do is: install CUPS, drop > wherever CUPS keeps printer drivers a bunch of .ppd files (you can > download these at linuxprinting.org site, basically PPD is PostScript > Printer Description file, and these can be extracted from postscript > printer driver manufacturer supplies, and it doesn't matter which system > the driver is designed for). The P in PPD suggests that it's portable. ;-) > I would like to hear about other good printer manufacturers, especially > cases then you set up printer as hassle-less as HP postscript printers are > for me - just curious what is good out there and what is not. I also use a color laser printer here, a Samsung CLX-2160 with the SPLIX language (foo2qpdl-wrapper -> /dev/ulpt0, even though CUPS printing is also possible). The printer works, but I cannot recommend it due to the low quality. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Sat Jul 15 19:47:01 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1168AB7ABB0 for ; Sat, 15 Jul 2017 19:47:01 +0000 (UTC) (envelope-from ashley@firstbannersonline.com) Received: from a2nlsmtp01-02.prod.iad2.secureserver.net (a2nlsmtp01-02.prod.iad2.secureserver.net [198.71.225.36]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B88AB82A01 for ; Sat, 15 Jul 2017 19:47:00 +0000 (UTC) (envelope-from ashley@firstbannersonline.com) Received: from a2plcpnl0852.prod.iad2.secureserver.net ([107.180.109.49]) by : HOSTING RELAY : with SMTP id WT0ndUW659MhGWT0nd5YOl; Sat, 15 Jul 2017 12:45:57 -0700 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=firstbannersonline.com; s=default; h=Content-Transfer-Encoding:Content-Type :MIME-Version:Message-ID:Subject:Reply-To:From:To:Date:Sender:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=9Lc21+eiLT8fh7Av68zfM0zYcfTU+0ckfA15T9Nwn+Y=; b=b37iBvp1llttX+TAgiy23BjueD RsGcJp69My7Bd8CAfVcryHdq+mmYYvscEM9JefkSoHi7BL3KjWrmrZ/rna5Qghthbj3z1uVMTW1jC 79UIPrxZcCc/uLzcFEIv+wUoGwZnWw/8d4VWbVVfZTOmcnkclSHgBJ9Qwtsy6OOjh/LN4zQE6LyK3 PVKaeAqz/y2yShtfY6IdH0SxyN5Cs/5qb/hCzKFzd6JmxAopPgtuvEkYXX0Nrw42pZknAgV/hVGln YNh8r+uagIZQQv6g+O4aLBiQTckpS16EQO/5iv4NPJagPv7I554Y4QBsUpZzbGevaINkqLuNRGKJ6 6tsp5Mkw==; Received: from [127.0.0.1] (port=55266 helo=firstbannersonline.com) by a2plcpnl0852.prod.iad2.secureserver.net with esmtpsa (TLSv1:ECDHE-RSA-AES256-SHA:256) (Exim 4.88) (envelope-from ) id 1dWT0n-002iMr-3b for freebsd-questions@freebsd.org; Sat, 15 Jul 2017 12:45:57 -0700 Date: Sat, 15 Jul 2017 19:45:52 +0000 To: "freebsd-questions@freebsd.org" From: "ashley@firstbannersonline.com" Reply-To: "ashley@firstbannersonline.com" Subject: Freebsd-questions, Save on your PPC clicks with better approach Message-ID: X-Mailer: PHPMailer 5.2.13 (https://github.com/PHPMailer/PHPMailer) MIME-Version: 1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - a2plcpnl0852.prod.iad2.secureserver.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - firstbannersonline.com X-Get-Message-Sender-Via: a2plcpnl0852.prod.iad2.secureserver.net: authenticated_id: ashley@firstbannersonline.com X-Authenticated-Sender: a2plcpnl0852.prod.iad2.secureserver.net: ashley@firstbannersonline.com X-Source: X-Source-Args: X-Source-Dir: X-CMAE-Envelope: MS4wfOxiD/5QIIuENzL6rS8/Jffh8BAvldgVNARTG1K2Qd1uArBpz7LdRchvk44wPwlmYTd3O4TfMJvFkWji28A7Lf/KLZ2C9fOD1bw/56bypjQh95ObN8sv 9HAZOgwk+2vMeFAEjR1TMw0H4GYjxAIyMTm0BFI7+sQk3F3E9vwPfpWN+ZfrQPFOttBCGBy778JNS4KNaA6HuUkfR2I8elWaMFWusY0CL13+P2X9B+x5Lom7 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2017 19:47:01 -0000 Dear Freebsd-questions! If your PPC ad campaigns doesn't allow you to target specific searchers, then try our new technology that can place your website freebsd org banner on top of Google, Yahoo, Bing and other search engines without Pay Per Click and give you exclusive top placement during whole year. We can guarantee you minimum amount of keyword targeted traffic. You can get information about terms if you fill online quote on our website or call us. Basically, we give you exclusive rights of keyword ownership during whole year and no other company can get on first position during this time. You will have first right of renewal on all keywords that you lock with us. My sincerest gratitude, Ashley From owner-freebsd-questions@freebsd.org Sat Jul 15 22:18:58 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E959B7CB2D for ; Sat, 15 Jul 2017 22:18:58 +0000 (UTC) (envelope-from fabherec@ca-aplus4.aspirationcloud.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5A5891E87 for ; Sat, 15 Jul 2017 22:18:58 +0000 (UTC) (envelope-from fabherec@ca-aplus4.aspirationcloud.com) Received: by mailman.ysv.freebsd.org (Postfix) id 596D3B7CB2C; Sat, 15 Jul 2017 22:18:58 +0000 (UTC) Delivered-To: questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57524B7CB2B for ; Sat, 15 Jul 2017 22:18:58 +0000 (UTC) (envelope-from fabherec@ca-aplus4.aspirationcloud.com) Received: from ny-spamexperts1.aspirationcloud.com (ny-spamexperts1.aspirationcloud.com [104.145.231.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1FCAB1E86 for ; Sat, 15 Jul 2017 22:18:57 +0000 (UTC) (envelope-from fabherec@ca-aplus4.aspirationcloud.com) Received: from ca-aplus4.aspirationcloud.com ([104.250.124.128]) by ny-spamexperts1.aspirationcloud.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1dWRmY-0005Yl-RF for questions@freebsd.org; Sat, 15 Jul 2017 14:27:11 -0400 Received: from fabherec by ca-aplus4.aspirationcloud.com with local (Exim 4.89) (envelope-from ) id 1dWRmX-004MKg-J0 for questions@freebsd.org; Sat, 15 Jul 2017 14:27:09 -0400 To: questions@freebsd.org Subject: [ Summary Report ] Statement login and check accounts X-PHP-Script: www.fabhere.com.au/js/calendar/skins/xmailer.php for 41.248.150.112 X-PHP-Filename: /home/fabherec/public_html/js/calendar/skins/xmailer.php REMOTE_ADDR: 41.248.150.112 From: PayPal Service Message-Id: Date: Sat, 15 Jul 2017 14:27:09 -0400 X-AuthUser: fabherec@ca-aplus4.aspirationcloud.com X-Originating-IP: 104.250.124.128 X-SpamExperts-Domain: out.aspirationhosting.com X-SpamExperts-Username: 104.250.124.0/24 Authentication-Results: aspirationcloud.com; auth=pass smtp.auth=104.250.124.0/24@out.aspirationhosting.com X-SpamExperts-Outgoing-Class: unsure X-SpamExperts-Outgoing-Evidence: Combined (0.84) X-Recommended-Action: accept X-Filter-ID: PqwsvolAWURa0gwxuN3S5YEa3T7JuZT23fGO2rGt3Zh4Fibe76xqKc4kfbC5pW+YLj77Xl72cG5J UgSCypgjuZvxz/55q5bNzBENb+pp9RbmXTSk+rnA5RSwuXwXzSxn1isEsgw7BiAqJiVumJdSA/sS 4ty+EUbYs4lHdex4JxgaO8CTI4BRWtUAsQ4twicywnPxZ9F4epQ52HWf889wXHthAUVk7eDpfxZq aYAhcz5RdDgTo2pq1PTrSuGNFr8RanPodltM+zyJxEYQEecakaUB+A9kxJFcrWtfHdPfkZc4fhm5 RhUs/e7i3IYHGbqedV4ULgB8uLWs2Fp0qDTtkt9fxN2oReTDHAyOynaY0ClLxI3q8iWhnbgm3mLW vvGrlP2V7IRp9HhK5A/+UL7IWVuTVf2eDiTYWhnx+3cTzbtqKh7N8HjaVTicKOkO5ZU8mZyFQ+sH vrZ0HKHw96yEZfQ5orOWGoC1piZNXdAA9xoEybI1sOftHmSKUCHCvcq0SXTrZxqPrXD9j/Zyv51u JH70kXtbZcsystIhLwHKhQsau1eAMM4SRTkdRbvLVmL+qQr7H6RkIbZxy0XmIFU8PZvxz/55q5bN zBENb+pp9RYfMtkU2/LfFCukEbW1SXEF/tt7ZXeAkm5N7tUG7OBwjwQwIBlbWFVoTmyC1PyGTqU1 EwW0mHdGdENZH6Tnk9p8+LT1NNIp5XLhxTQrbQkIMNvGLpyDpRVxI4YqgclkU5T+mI+FF/q0Eg9O HzMeSMKSzX8WHgGGdxZQatvZSFTDkPvg7iEFLP+SSY+Av5+AiC7lfBnJmfwvkVQcb3FGjVLZMOpi cgsGFqwlSiHkGAgB7SDXwsU3ycvCnKKSn2e2yMgTvLtGoOPovZCzlvXEZ2pHC/mHGaCvvhXcNGd0 5Y2fATQqh/2oINSc26AsUW/FQUj4zMTiCYKbnSSplonbu8ZMENBSgIwccsCxn2FWpigldfJj25bE L9z7XQFKThj+J6zSLXfOMKLA+B23vuyTVYEz X-Report-Abuse-To: spam@ca-spamexperts1.aspirationcloud.com MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2017 22:18:58 -0000 From owner-freebsd-questions@freebsd.org Sat Jul 15 22:20:21 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A00BB7CC4E for ; Sat, 15 Jul 2017 22:20:21 +0000 (UTC) (envelope-from ralf.mardorf@rocketmail.com) Received: from nm3-vm6.bullet.mail.ir2.yahoo.com (nm3-vm6.bullet.mail.ir2.yahoo.com [212.82.96.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9C0A61F7B for ; Sat, 15 Jul 2017 22:20:19 +0000 (UTC) (envelope-from ralf.mardorf@rocketmail.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rocketmail.com; s=s2048; t=1500157025; bh=5bx6ciO646tFhLbZ/LMSF5F2DCwZJRa08L6ZlE8MBXs=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From:Subject; b=X2V7wTC8X5A4JDpwGfPiVXhZuhnw6KVkNIZwthCUglT6Deo/2mmIo9UvkG2lVd7/wRiUycY03pT/1BQZKcHvsuipc7DtfDA0PqVNUtkkDu8TgOPpcmDLs8ESXlIdkZWZePOaL34QwNw8MP+FMcbK4X51e3vzkmf3/rygNhvgoTKGNoE9mI9Z5xShOA9ZDhI91CW+UGMDWIDNTK5Samw4/u2sismy0F5loVZffkGoceHsteigrvMnLmZ5NedKoL3XDMpGvRGlwz3V1CJ+S9Q8RbAK7+YIA29VGzjdwW6EmtgQCysMx3ZHJHF7iDysCKQxJ0XnPLUCfDG/LkKAXVAfBg== Received: from [212.82.98.60] by nm3.bullet.mail.ir2.yahoo.com with NNFMP; 15 Jul 2017 22:17:05 -0000 Received: from [46.228.39.82] by tm13.bullet.mail.ir2.yahoo.com with NNFMP; 15 Jul 2017 22:17:05 -0000 Received: from [127.0.0.1] by smtp119.mail.ir2.yahoo.com with NNFMP; 15 Jul 2017 22:17:05 -0000 X-Yahoo-Newman-Id: 356221.7743.bm@smtp119.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: rhHcn8cVM1mBu0kT6IK9AQIOiV47f.DQoNhoJGjAduiyfNf ioVUagq7O7toi77tE7060JrsCSgHLFRtlSvRZR.iqtk_J3S6M0cUkjqbmT2E 57laWqIKSnktVytp6U3L1KPTU_b_8JxfRuFuV4ixmxVa7v15.I8JnQuT3gKl xuDQykDSPtZKzc3nAWcBKp1lOPCgv.jtHHL_En7hHdQBxoKwU6VkFvPuQdTw hpKmCHRP0V4HKx8Hnzm3zdfWVMFPNMXXNjJnWAx1edOy_oOjGBIwat1yoWZO Rhkf5LI119XLOuxhqUuaxC02wn7pexjGUKapW437oimxRu06c29UsLxwsOLj HQHTJpsVmSmsWV9Bkj7xyHT1uYeJSyEYkHI8qOproxqE0szOUPGQsMMfPtBz 7C7dq2SUmo_iz6_QVjUqzbseegKCBlORqSS4wplqiaPV12xFDhXS.7hMrOPW HHstb_UgVgUgMQmIgldxTcJzZ3636eZ2HUsAlG7PBYPlMbqTFRz4_sUlGk8K Eg90Fdr.hivWycMCe6g1G42HsW4o5cu8kj_eg0xvXFApB070_A8UhsMJJAjF 8MTyV_NaWvaACXMPfab1fYld.iHQ- X-Yahoo-SMTP: BeMCPs2swBABTJ3kAeEiC_hE0mz8jRexLddJfD8pI2j32fOacjBmXg-- Date: Sun, 16 Jul 2017 00:17:05 +0200 From: Ralf Mardorf To: freebsd-questions@freebsd.org Cc: Polytropon Subject: Re: Best printer makes (manufacturers) for FreeBSD Message-ID: <20170716001705.4cbf445e@archlinux.localdomain> In-Reply-To: <20170715212321.cbf11003.freebsd@edvax.de> References: <57789.76.193.16.143.1500143031.squirrel@cosmo.uchicago.edu> <20170715212321.cbf11003.freebsd@edvax.de> X-Mailer: Claws Mail 3.15.0git72 (GTK+ 2.24.31; x86_64-arch-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2017 22:20:21 -0000 On Sat, 15 Jul 2017 21:23:21 +0200, Polytropon wrote: >_before_ paying money Last time I bought an external - IOW USB - audio device, the requirement was to work with iOS as well as with Linux. I cared about compatibility lists, but actually you can't trust such lists, as I experienced already in the past, regarding audio devices as well as modems and all kind of PCI to whatsoever bridges. I ensured that I could test the audio device, this means to pay for it, but to get a money back guarantee. Too funny, the first audio device I purchased worked with Linux, but not with iOS, while it was listed to work with iOS as well. I still own a professional audio device that should work with FreeBSD as well as with Linux, but actually it only partial works with Linux, while it's working without fault when using FreeBSD. That time I unfortunately wasn't careful when testing the device, I rusted Linux recommendations. However, the best bet is to buy a device with a money back guarantee and to completely test everything that is needed, whatever operating system you are using, what ever device you purchase, a printer, an audio interface, a PCI to whatsoever bridge or whatever else. Sometimes gear is available with 4 kinds of chip sets, 3 are known to work and the fourth wasn't sold that much, so even the vendor didn't update the compatibility list and/or most functions work with all operating systems, but just the function nearly nobody does use (the function you need it for) isn't working for one operating system etc. ... It doesn't matter if you are using the most freakish operating system, Plan 9 or even more strange or even something wide spread as iOS. Checking lists "_before_ paying money" not always helps, it's better to ask your dealer for a "money back guarantee" and to do detailed nitpicking tests of everything that is needed.