From owner-freebsd-questions@freebsd.org Sun Jan 28 00:15:46 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F703ECCEE2 for ; Sun, 28 Jan 2018 00:15:46 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::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 0FEA6819DD for ; Sun, 28 Jan 2018 00:15:46 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by mail-io0-x229.google.com with SMTP id b198so4049765iof.6 for ; Sat, 27 Jan 2018 16:15:46 -0800 (PST) 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=Syv4Hb8OMNRh0CgdMBUo9xM4H2ABNaqtypXhudx0YWs=; b=lxm4AAJOTb2n2HYwROznOSKcrlFyA2IWbu7Zqcpfi+GaD6gY6Mc/AWqRo3IRLsBygF 35cJILXw4XeEKhXT4VY1wuyAyPzsSO4ACfu0uSSPqvay9xs86PaT2R5UBxIiG4PX+1X6 R+UCqqQBrcUDUUZkp94DPdwE7vDCkKbXywed9Yqeu+WOUlGJbZEbDcuwAm/6n9IfWQJE 1os7j+VGGgtCEsjqyF+pel2T34fvijbqg6EYaIx4NN1Uf7pqsbDHBsF/nQ3ExcGDbsDO Kjvt1198g4QvhZ94KB2nUGTOXMwGEu2aDkvpFqaebMe+zSnOttRRPcqNwMH0UC2UqnNe +5iQ== 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=Syv4Hb8OMNRh0CgdMBUo9xM4H2ABNaqtypXhudx0YWs=; b=maCGju0EVpgpoYd1YNxcKLN2spKQ7LJyB6KhkjJ+TzeNhVuzzjPkFN38+IRes1GSm3 VW9ZvD9C0zZsQQOI8mPjDp3G4RkzzK5/WjCC+6vCM6aG4Nnek6zQmFojBW0jn2/P9YDF zr4gp9q1bvOi+Wj3kNhc8QaxUUYVbXqn288DAm5t9sC3nMTbGlv5IpNwQa0VaiuOnvHj FaEcYdwRgRxQ9NBpxthxwxRyvomqH31lf1PrpqMW4rnbng2o5JA5UTRG3krVRaRxkAF6 Gpi2ITGdsc7FZJdJLJ7PRK2QmcTfKJzzS2JxrR3wOk0a3zJP70uUqFScvjeCNIWh9JhM hPzQ== X-Gm-Message-State: AKwxyteAq4pnH9cFF8h2DXCKouaEIjOrpIprazJh2+4lNXNUkTT3/QOy 4bgjifPiFNM33pUCgkiN29f101Ypp8yIVhxVHc0= X-Google-Smtp-Source: AH8x225T/VxPQq+qguxzAnilqJIOPDdQ0Ql06vUt8Sugl2sFY2lxOdUBgvSUPwlwHlwi34ier4Qjc9Kp/ITvbqYZSR8= X-Received: by 10.107.55.132 with SMTP id e126mr21549532ioa.32.1517098545606; Sat, 27 Jan 2018 16:15:45 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.156.70 with HTTP; Sat, 27 Jan 2018 16:15:45 -0800 (PST) In-Reply-To: <20180128.072704.1527334119280589760.yasu@utahime.org> References: <20180128.072704.1527334119280589760.yasu@utahime.org> From: Adam Vande More Date: Sat, 27 Jan 2018 18:15:45 -0600 Message-ID: Subject: Re: Difference in wainting time between update of base/doc/ports tree To: Yasuhiro KIMURA Cc: FreeBSD Questions Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jan 2018 00:15:46 -0000 On Sat, Jan 27, 2018 at 4:27 PM, Yasuhiro KIMURA wrote: > Hello. > > I check out head of base/doc/ports repository in one FreeBSD box and > update them periodically. When I execute 'svn update' in base or doc > tree update always starts within 10 seconds or so. But when I do it in > ports tree it typically takes from 5 to 10 minutes and sometimes takes > more before update begins. > > Update is done from one server (https://svn.freebsd.org/) to one > client (my FreeBSD box). So spec of server, client and/or network > cannot cause such difference. Then why it happens? Repository size > or number of committed files affect waiting time of update and result > in such large differernce? Or some complicated hooks that works at > update time is implemented in ports repository and its processing time > results in such a long waiting time? > > Please let me know if someone knows about it. > It is most likely due to IO. There are tools to profile processes if you want empirical verification. -- Adam From owner-freebsd-questions@freebsd.org Sun Jan 28 08:08:27 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 22359EDE8D9 for ; Sun, 28 Jan 2018 08:08:27 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id 9D4B070552 for ; Sun, 28 Jan 2018 08:08:25 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id 7383514224; Sun, 28 Jan 2018 17:08:22 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id 031F43378D; Sun, 28 Jan 2018 17:08:22 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPSA id D38953378C; Sun, 28 Jan 2018 17:08:21 +0900 (JST) Date: Sun, 28 Jan 2018 17:07:58 +0900 (JST) Message-Id: <20180128.170758.1927192209618154831.yasu@utahime.org> To: freebsd-questions@freebsd.org Subject: Re: Difference in wainting time between update of base/doc/ports tree From: Yasuhiro KIMURA In-Reply-To: References: <20180128.072704.1527334119280589760.yasu@utahime.org> X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jan 2018 08:08:27 -0000 From: Adam Vande More Subject: Re: Difference in wainting time between update of base/doc/ports tree Date: Sat, 27 Jan 2018 18:15:45 -0600 > It is most likely due to IO. There are tools to profile processes if you > want empirical verification. I would like to know why this happens. So would you please tell me what tools can be used to investigate it? FreeBSD version of my box is 11.1-RELEASE amd64. Best Regards. --- Yasuhiro KIMURA From owner-freebsd-questions@freebsd.org Sun Jan 28 14:01:11 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DF813EC7D14 for ; Sun, 28 Jan 2018 14:01:10 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::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 75E887C4D7 for ; Sun, 28 Jan 2018 14:01:10 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by mail-it0-x22a.google.com with SMTP id 196so6417490iti.5 for ; Sun, 28 Jan 2018 06:01:10 -0800 (PST) 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=hhvRsRJr5LiO1YWD6qJNumb8Nhs38KXGNif9hKiMgy0=; b=cAH0FF88KNsOKyJxUZ55dQbpYA0izru/ZJcNgqM8MtZQi6Vnkiz1BiOB6CAKb8H5Nz um/U/jIfRizVL/7c94Ww72/uPixrMMy5Ubn20nijUd1RlB5cBpE9aRUfuqy3/jFr7N0u GgBbB34MDoLaiMq+oZL6j8kv/kB+BuonQ6HQVjTDuSkyXx1Nu6JGotNKgxWrk+RvcloP ZmgiY2mLVK5je3qlCEOgPX557OYcRZEB0NUZ0orxE3tdZQmpjC0jzKchDaBM8it/YMw3 g2FXwZ6UDyHE5Z27PzoU5PyrgzpSGtdftOlk9poe+0Lbsc1mHUJdCndgB5kYKfgpgeZ0 elGg== 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=hhvRsRJr5LiO1YWD6qJNumb8Nhs38KXGNif9hKiMgy0=; b=Tlxrb+VcVVXSwbiYR2Nmt5gHpL8ONVc04ObTmelmeKW5cQL7hqVH7NuVo44x4s+XQ+ VWFEw+ruaOeqHaQpOnFuObNosOyRQZyJrdahM+kDh4V/s5UyIWIErkX5UUKNYk7XiKIh BYr/Fw7lTmCo4NlI3mzYdMtOdRNRdP4R4NCMMj4anl+PbAJAZ/Ln/AXAilMwBrqdEFPq Q75SRRhtsz3BQ9EFItqyNlVhaXgJJwg52+K47JSgMkJBqxVT+7d4bxFPaP5CykRDDTeK hy/WEamjyOyA+nXB46PcuSGKEhIDcfBqTUnmVCT3Q5ErK+lHPhIRaNr4QJRIkNMqIFbH x7sg== X-Gm-Message-State: AKwxyteyOhdCv3LRq8c9zLjrrKCCzODayTi7lTV4mAzMQ9T9dDhQiZQY /PLS7Rrr5BkRLg9uIutUQEhAzc/W+58a5QTe6Yvjrw== X-Google-Smtp-Source: AH8x225CzKkVpNRthUohtTTm/v50VjxkJn8vbxCovohIiKioKKEFYzUTFVGcbZWjnWFFqP/mre1zx3YQyWMTQxYfsCo= X-Received: by 10.36.138.134 with SMTP id v128mr23898612itd.153.1517148069719; Sun, 28 Jan 2018 06:01:09 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.156.70 with HTTP; Sun, 28 Jan 2018 06:01:09 -0800 (PST) In-Reply-To: <20180128.170758.1927192209618154831.yasu@utahime.org> References: <20180128.072704.1527334119280589760.yasu@utahime.org> <20180128.170758.1927192209618154831.yasu@utahime.org> From: Adam Vande More Date: Sun, 28 Jan 2018 08:01:09 -0600 Message-ID: Subject: Re: Difference in wainting time between update of base/doc/ports tree To: Yasuhiro KIMURA Cc: FreeBSD Questions Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jan 2018 14:01:11 -0000 On Sun, Jan 28, 2018 at 2:07 AM, Yasuhiro KIMURA wrote: > From: Adam Vande More > Subject: Re: Difference in wainting time between update of base/doc/ports > tree > Date: Sat, 27 Jan 2018 18:15:45 -0600 > > > It is most likely due to IO. There are tools to profile processes if you > > want empirical verification. > > I would like to know why this happens. So would you please tell me > what tools can be used to investigate it? FreeBSD version of my box is > 11.1-RELEASE amd64. > pcmstat or dtrace might be a good starting place. Then you can use something like https://github.com/brendangregg/FlameGraph to produce a more visual output if desired. -- Adam From owner-freebsd-questions@freebsd.org Sun Jan 28 13:10:11 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 64123EC55BC for ; Sun, 28 Jan 2018 13:10:11 +0000 (UTC) (envelope-from johannes-maria@t-online.de) Received: from mailout03.t-online.de (mailout03.t-online.de [194.25.134.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F0CC37A3DD for ; Sun, 28 Jan 2018 13:10:10 +0000 (UTC) (envelope-from johannes-maria@t-online.de) Received: from fwd38.aul.t-online.de (fwd38.aul.t-online.de [172.20.26.138]) by mailout03.t-online.de (Postfix) with SMTP id A5A744263E2C for ; Sun, 28 Jan 2018 14:04:40 +0100 (CET) Received: from t-online.de (GoSxymZrohXLyhjv7GWV0QF2wakeFM2UvsEBMhtveNKPdZL484Epq4g1LxMoJaAwOV@[84.145.236.2]) by fwd38.t-online.de with (TLSv1:DHE-RSA-AES256-SHA encrypted) esmtp id 1efmdO-0COIe80; Sun, 28 Jan 2018 14:04:34 +0100 Received: by t-online.de (nbSMTP-1.00) for uid 1001 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-SHA (256/256 bits)) johannes-maria@t-online.de; Sun, 28 Jan 2018 14:04:34 +0100 (CET) Date: Sun, 28 Jan 2018 14:04:33 +0100 From: johannes-maria@t-online.de To: freebsd-questions@freebsd.org Subject: Re: problem with upgrade and unable to build openjdk8 in poudriere Message-ID: <20180128130433.GA2196@localhost.org> References: <20180115151549.GA9923@localhost.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180115151549.GA9923@localhost.org> User-Agent: Mutt/1.4.2.3i X-ID: GoSxymZrohXLyhjv7GWV0QF2wakeFM2UvsEBMhtveNKPdZL484Epq4g1LxMoJaAwOV X-TOI-MSGID: a9b9f43c-503a-4ac5-8985-94f07fdd7354 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jan 2018 13:10:11 -0000 On Mon, Jan 15, 2018 at 04:15:49PM +0100, johannes-maria@t-online.de wrote: > Hello, > > I'm still working with 9.3 and thought it's time to install 11.1 > but there are two problems I couldn't solve myself. > > I've never worked with jails or poudriere before and probably > made some errors so I first describe in detail what I've done. > > To not destroy my working system I made this on a separate > (clear) slice of my hard disk. > > First I installed the basic 11.1 system with the boot disk > (FreeBSD-11.1-RELEASE-amd64-disc1.iso) without problems. > > Then I installed poudriere (pkg install poudriere) > and created a jail with poudriere: > poudriere jail -c -v 11.1-RELEASE -a amd64 -j 11amd64 > and installed the ports tree: > poudriere ports -c > I created a list of ports to install and started poudriere: > poudriere -v bulk -j 11amd64 -f list_of_ports_to_install > > > First problem: > > One of the ports to install is x11/kde4 which as a dependency > adds java/openjdk8 to the list but poudriere seems to be > unable to build it: > =>> Failed ports: java/openjdk8:build > [excerpt from the log-file: > gmake[2]: *** No rule to make target '1'. Stop. > gmake[2]: Leaving directory '/wrkdirs/usr/ports/java/openjdk8/work/openjdk/langtools/make' > ] > > And therefore > =>> Skipped ports: devel/antlr devel/kdesdk4 devel/poxml x11/kde4 > > On the other hand a direct make in ports/java/openjdk8 is successful > but it fails repeatedly when called by poudriere. > > > Second problem: > > I tried to install the successfully built software > (i. e. my list without kde4) with > pkg -j 11amd64 upgrade > but this fails with > pkg: jail "11amd64" not found > > and jls doesn't list any jails > whereas > poudriere jail -l > displays > JAILNAME VERSION ARCH METHOD ... PATH > 11amd64 11.1-RELEASE-p6 amd64 ftp ... /usr/local/poudriere/jails/11amd64 > > > Any help greatly appreciated. > > Best regards, > Johannes-Maria Is there really no-one who could give me a hint? Best regards, Johannes-Maria From owner-freebsd-questions@freebsd.org Sun Jan 28 16:08:56 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 15A1BECFB79 for ; Sun, 28 Jan 2018 16:08:56 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id 95A3D83B98 for ; Sun, 28 Jan 2018 16:08:54 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id 6570C142CC; Mon, 29 Jan 2018 01:08:52 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id 2053C33A34; Mon, 29 Jan 2018 01:08:52 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPSA id DCC8533A31; Mon, 29 Jan 2018 01:08:51 +0900 (JST) Date: Mon, 29 Jan 2018 01:08:27 +0900 (JST) Message-Id: <20180129.010827.592736819244903988.yasu@utahime.org> To: freebsd-questions@freebsd.org Subject: Re: Difference in wainting time between update of base/doc/ports tree From: Yasuhiro KIMURA In-Reply-To: References: <20180128.170758.1927192209618154831.yasu@utahime.org> X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jan 2018 16:08:56 -0000 From: Adam Vande More Subject: Re: Difference in wainting time between update of base/doc/ports tree Date: Sun, 28 Jan 2018 08:01:09 -0600 > pcmstat or dtrace might be a good starting place. Then you can use > something like > > https://github.com/brendangregg/FlameGraph > > to produce a more visual output if desired. Thank you for suggestion. I'll try them. --- Yasuhiro KIMURA From owner-freebsd-questions@freebsd.org Sun Jan 28 23:59:52 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6EEA7EC5A31 for ; Sun, 28 Jan 2018 23:59:52 +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 92CA074AB1 for ; Sun, 28 Jan 2018 23:59:51 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (unknown [IPv6:2001:8b0:151:1:e930:bf41:9abc:521e]) (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 942E712DA6 for ; Sun, 28 Jan 2018 23:59:44 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none (p=none dis=none) header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/942E712DA6; dkim=none; dkim-atps=neutral Subject: Re: problem with upgrade and unable to build openjdk8 in poudriere To: freebsd-questions@freebsd.org References: <20180115151549.GA9923@localhost.org> <20180128130433.GA2196@localhost.org> From: Matthew Seaman Message-ID: Date: Sun, 28 Jan 2018 23:59:43 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <20180128130433.GA2196@localhost.org> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="LtZ1B9UqGQJl9Ti3FMGF8b1zxUbldS1mP" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jan 2018 23:59:52 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --LtZ1B9UqGQJl9Ti3FMGF8b1zxUbldS1mP Content-Type: multipart/mixed; boundary="Ddpf5f1FX3h7tQzLlnnv5rVfyUGRAaPc8"; protected-headers="v1" From: Matthew Seaman To: freebsd-questions@freebsd.org Message-ID: Subject: Re: problem with upgrade and unable to build openjdk8 in poudriere References: <20180115151549.GA9923@localhost.org> <20180128130433.GA2196@localhost.org> In-Reply-To: <20180128130433.GA2196@localhost.org> --Ddpf5f1FX3h7tQzLlnnv5rVfyUGRAaPc8 Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 28/01/2018 13:04, johannes-maria@t-online.de wrote: > On Mon, Jan 15, 2018 at 04:15:49PM +0100, johannes-maria@t-online.de wr= ote: >> Hello, >> >> I'm still working with 9.3 and thought it's time to install 11.1 >> but there are two problems I couldn't solve myself. >> >> I've never worked with jails or poudriere before and probably >> made some errors so I first describe in detail what I've done. >> >> To not destroy my working system I made this on a separate >> (clear) slice of my hard disk. >> >> First I installed the basic 11.1 system with the boot disk >> (FreeBSD-11.1-RELEASE-amd64-disc1.iso) without problems. >> >> Then I installed poudriere (pkg install poudriere) >> and created a jail with poudriere: >> poudriere jail -c -v 11.1-RELEASE -a amd64 -j 11amd64 >> and installed the ports tree: >> poudriere ports -c >> I created a list of ports to install and started poudriere: >> poudriere -v bulk -j 11amd64 -f list_of_ports_to_install >> >> >> First problem: >> >> One of the ports to install is x11/kde4 which as a dependency >> adds java/openjdk8 to the list but poudriere seems to be >> unable to build it: >> =3D>> Failed ports: java/openjdk8:build >> [excerpt from the log-file: >> gmake[2]: *** No rule to make target '1'. Stop. >> gmake[2]: Leaving directory '/wrkdirs/usr/ports/java/openjdk8/work/ope= njdk/langtools/make' >> ] I can't really give you much help with this: openjdk8 is building just fine for me on 11.1-RELEASE. This is probably some small configuration mistake that will have you face-palming once you find it... >> And therefore >> =3D>> Skipped ports: devel/antlr devel/kdesdk4 devel/poxml x11/kde4 >> >> On the other hand a direct make in ports/java/openjdk8 is successful >> but it fails repeatedly when called by poudriere. >> >> >> Second problem: >> >> I tried to install the successfully built software >> (i. e. my list without kde4) with >> pkg -j 11amd64 upgrade >> but this fails with >> pkg: jail "11amd64" not found >> >> and jls doesn't list any jails >> whereas >> poudriere jail -l >> displays >> JAILNAME VERSION ARCH METHOD ... PATH >> 11amd64 11.1-RELEASE-p6 amd64 ftp ... /usr/local/poudriere/jails/1= 1amd64 >> OK. Confusion over jails here. The '-j' flag to pkg(8) allows you to install files into a jail from the host system. As you don't have any actual jails configured, you don't want to use this flag. These are completely different to the jails used by poudriere. In fact, when you "create a jail" by eg. poudriere jail -c -j 11amd64 -v 11.1-RELEASE -a amd64 -m ftp What you are actually doing is creating a template. 'poudriere jail -l' will list all the templates poudriere knows about. It's only during a poudriere run that jails are actually created from these templates -- in fact, as many jails as the degree of parallelism you've allowed in poudriere.conf. Try running jls(1) while poudriere is compiling stuff and you'll see. These build jails are only temporary and are destroyed as soon as the poudriere run ends. Now, poudriere will collect all the packages it has built into a repository. It's typical to set up a webserver (nginx recommended) to allow distribution of those packages, and you will need to write a configuration file for pkg(8) giving the correct URL for your custom repository. You'll probably also want to turn off the default FreeBSD package repository -- see the comment in /etc/pkg/FreeBSD.conf for how to do that. Then you can just upgrade your system by: pkg upgrade Hint: try 'pkg -vv' to see your pkg(8) configuration including all the repositories you have configured. Cheers, Matthew --Ddpf5f1FX3h7tQzLlnnv5rVfyUGRAaPc8-- --LtZ1B9UqGQJl9Ti3FMGF8b1zxUbldS1mP Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKoBAEBCgCSFiEEGfFU7L8RLlBUTj8wAFE/EOCp5OcFAlpuY/BfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDE5 RjE1NEVDQkYxMTJFNTA1NDRFM0YzMDAwNTEzRjEwRTBBOUU0RTcUHG1hdHRoZXdA ZnJlZWJzZC5vcmcACgkQAFE/EOCp5OdaYw//Rzuyi9Vk54jS7QOOLSMLWyZIQVno RH7/YjA4uBxI/xzD1wbQuvQEhF1CJj6I54zWyvvkXF07h73QQciPledmdHZ5NifU VwiF3m3WSDYvbowS9IcorXLc2Nk/dj1u5tPNeD4t4k1p9BBP//eQ7/NdDWUt7bK2 mtm6SReYMJTCUmGJzFpvVrIuN/VRTLGYdo01IsXosk2VBKuKqnRQz9CYcIat0cFH ynfCLJ2UsWiv+TAIMzmj7scf0EhvSRKpiQXw4u0FjpjFhkqAwAaLL+ueVmKco/Dk B5tW33YKm0J3kYQR/xkfgvInJiRbM2JAj8zVi8Nrqr+EKKk2zWyaKKasxi/xeMC/ 13uYidm9+ws0UOKIFn39iiZL/GXgUZouWDhsGsIqWxtgigBwXcINa70967VQlJVV TcI5+p4oDp5ELaBCyjf4MDKZsYn8UTANC8MREoAKWlsbWinytYV6o0Xxc8Vl+hE6 lB6vr8PlwdKtSld6f60Kibq8LRbU7yyA8VG5OHGMuBN5/xUT2is1PPogg9ENz8f3 KMlVEwYY2SZ/GYrXHoX2OeNKJ44EbgwKqhu5CHxXePccoL7Lx7pdabkXfafqJ65I 8mp5LtvqQ86WeGqZfS+ptOHwMC4iZTxAP+zofuSvqOORdFqTdEy+LCPdZAoE5jeF nQLnvVbPDdKEbJE= =Z29n -----END PGP SIGNATURE----- --LtZ1B9UqGQJl9Ti3FMGF8b1zxUbldS1mP-- From owner-freebsd-questions@freebsd.org Mon Jan 29 01:11:01 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7C6CBECA75B for ; Mon, 29 Jan 2018 01:11:01 +0000 (UTC) (envelope-from dave.mehler@gmail.com) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (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 ED55E77C22 for ; Mon, 29 Jan 2018 01:11:00 +0000 (UTC) (envelope-from dave.mehler@gmail.com) Received: by mail-wm0-x236.google.com with SMTP id g1so11050320wmg.2 for ; Sun, 28 Jan 2018 17:11:00 -0800 (PST) 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=PgEXtHRaW9K326KR3FIu5ArenvZErlfKXkeUwZyEAww=; b=UAdTv2GE1vfmzmL7ZsAxke9fy//2hTNE/0SUUxALiZQ1THJsZehzAiIoauh5o13/m3 0W8usOU1lHgf3uxEt6PqfO46eNBnmmKjdNOjRo31tcFSc8/4o1XFwrmHYLNkPnYmCnfx 9tK7UI7Vzso0KVH6zJS1YnYKg52pvc7jmMKwtkQH+BqFyfMPM5mihufuMZfdnQmENL2L EFwEusQmUEj+VMdDP73jKYCxCq6ALMK0hTnhTjPEOkjXc3N2W0mPO2KSSXnLFDBpziHS N3RgHDzQJ4DLknRkbjfuTEPk8C/CFKXlcC2SO2H0ipeAxLIjYlE2vtJmE4t0wrcup49g RPAw== 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=PgEXtHRaW9K326KR3FIu5ArenvZErlfKXkeUwZyEAww=; b=BW7weluRyNjkMoP84jtbVb1XYc3lA4v9/7V90b/09YUDBObHpZdUgLFI+uIN1eq01O lfw2SbfOX8KIQahPzphAj7lyB07Ufs2GOecA4QgaPvmkNfFErfEaaopU6M+UBCpJZyxX FB017v+lfHXa+a0oZiAMp6kSMwjO5mSUrVcP1D+ZqBYh9qDISzm1UeQn/m835ac4rCHz vIvJ9UGMCORGmPyLSCkWbl8Ux2WTmnwvkH3eGhF2nPuvBOWvDVV2CCg3/e21iKP0Focg yFtGyUSGsaq2/jWt5W4KlqWeqMFeh0OAvk5eHWQsxsg85Hi6y6VGl26O/atBi86VVB+r QQRw== X-Gm-Message-State: AKwxytdrIVpR7DIzDDKK2odRJe9BK9ZcG7WhH7TY1psGvEzdxuWV5n4e TSwXbGjktW1KpYIXw13vcGuiGvs0C2oZkVvs8X0= X-Google-Smtp-Source: AH8x224WQEsW07s7K+wORQm0qShFX9ccTyKZIljkjeW7O5yfUqNo/Hx3Sk9E+D975SXIsEVxcVE4RgCP+ImjltJ/GJg= X-Received: by 10.28.166.20 with SMTP id p20mr15569666wme.85.1517188259777; Sun, 28 Jan 2018 17:10:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.141.184 with HTTP; Sun, 28 Jan 2018 17:10:59 -0800 (PST) From: David Mehler Date: Sun, 28 Jan 2018 20:10:59 -0500 Message-ID: Subject: Setting up an https accessible git server on FreeBSD To: freebsd-questions Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jan 2018 01:11:01 -0000 Hello, If anyone has a git server going on FreeBSD, accessible via http smart protocol https only, i'd appreciate knowing how you got it going? I'm wanting to make private repos accessible to myself and a select group of users invisible to everyone else. Thanks. Dave. From owner-freebsd-questions@freebsd.org Mon Jan 29 06:37:47 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 66111ED8D06 for ; Mon, 29 Jan 2018 06:37:47 +0000 (UTC) (envelope-from kaiwindle@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 CE535818E2 for ; Mon, 29 Jan 2018 06:37:46 +0000 (UTC) (envelope-from kaiwindle@gmail.com) Received: by mail-wr0-x230.google.com with SMTP id v15so5880240wrb.8 for ; Sun, 28 Jan 2018 22:37:46 -0800 (PST) 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-language:content-transfer-encoding; bh=9xe+9eXRVD7BQWi88bDDftaewp0Iw5IQQwrUArRV82Q=; b=AXu74PgdDh9fa/GrkMgbpYyrtxjCue4yPrUYWABeUCLAC3Uly9dpxRoiq0Ef6FkasX Yg+m0+zow5/jMGiBot9rgvi/wIjfREYLp4/WxgIlfJcqoGL9gA5k62p5mh03QJ0PTIMb 1ogHcBbT82Xap3+O9uXYM/cmt3KkakvuyPKTkGQxbdp6uapempziJS5978Cgu7z5deyq 6vW97iIKZ2npEif2zgVTerl+vRaY/jr33gjsumKB6P3rxHKt4r1SUdA6h8tmT2heRnfO hGhkQImk3Y0kTRyJAUkrktIf+EehWWBbPkroB7ElGxByTEjiSBHAYeazdadopKsBp8J8 0JFw== 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-language :content-transfer-encoding; bh=9xe+9eXRVD7BQWi88bDDftaewp0Iw5IQQwrUArRV82Q=; b=SqaMtC7XCDXzC7VSPYuLtAic2SGm17oFDwvk+RqRhVhjP99VPSe515eg719e2vehv9 qm+YS6UKHdRL5ZA7s0LlwJyA0MospeOrZVXW8Ap0vGEmu1vyGC6/KG/jSod6pIKiO6Q7 SL9DeVe+O0ka8WnZV2XQ5hGBNpTgQOHQDktbd0jGcoM5KXos0cbtfw8RBisjpVhpanCm 0tnLcDdUrAH4EnEbNoEEc/Ji0KMWNTLSGfSFyhI6yIJsTl6Py2Jv6Znbv31ub3O+pQ6k bFifS/r5fC8rMOiyI4BaUcyLL8l7aLf8QfvXtluAWmXJT3R4z1fV+wmdB+wi4cPryVBT PaLA== X-Gm-Message-State: AKwxytc1beVenLQXj0frRr9EFQq6OTM4jV0cIwBMdmdd4iRLiJhhCG+R /jYPiVr5n0uVNmy/DXczZn2gjDRU X-Google-Smtp-Source: AH8x226+cM7lhMeCaQiQX48bo4PmA9zixteSibZCxHqOER3sGI10HQDhtwXlkfAtEsDrVXuXDW2AhA== X-Received: by 10.223.196.154 with SMTP id m26mr8334704wrf.56.1517207865323; Sun, 28 Jan 2018 22:37:45 -0800 (PST) Received: from [10.10.130.178] ([86.188.129.1]) by smtp.gmail.com with ESMTPSA id r1sm8493086wmg.22.2018.01.28.22.37.43 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 28 Jan 2018 22:37:44 -0800 (PST) Subject: Re: Setting up an https accessible git server on FreeBSD To: freebsd-questions@freebsd.org References: From: Kai Windle Message-ID: Date: Mon, 29 Jan 2018 06:37:42 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jan 2018 06:37:47 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello, I've just done a quick google search (sorry I didn't have much time) and found http://zewaren.net/site/node/159 it looks like this might give you enough to get what you want and you could make ngix auto forward to http s On 29/01/18 01:10, David Mehler wrote: > Hello, > > If anyone has a git server going on FreeBSD, accessible via http > smart protocol https only, i'd appreciate knowing how you got it > going? I'm wanting to make private repos accessible to myself and a > select group of users invisible to everyone else. > > Thanks. Dave. _______________________________________________ > 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" > Regards Kai -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJabsEyAAoJEL1+cVd38wHM9jUIAKA3cFs84OOjTn3kIH/kkG0H vrtt304jMJi2BRFxcQkVp9QL8Eka9GZwaX5Yb/O/j00tnSqeoD9Ittwi7mQBsGOf aOIMTdmEEcw4VE2/9xKkgR9JzrbWnzERV+9Iryj6uDzbH2+gG4ckdBEYSEXwjlo8 GPNp01ZirTMfCQrpvlM2s6LfUv9PsZtHS7A2Z92K51j5z9aZDnSm261ZD5B6wFiy 6rZdRJ+9p0sbsFoGuh2cRwv+Md51OO39n/DZzMZfg+qpYmK3ZiiI69gYIcjM3uz8 V97B14ZdJNUQyFk+QnNJ1vb4ukHslDPChhXMDckeAZB18CzLbsySej1camnxXjI= =Mugk -----END PGP SIGNATURE----- From owner-freebsd-questions@freebsd.org Mon Jan 29 07:26:11 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4DD40EDA8C7 for ; Mon, 29 Jan 2018 07:26:11 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (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 D723682FC1 for ; Mon, 29 Jan 2018 07:26:10 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: by mail-oi0-x22f.google.com with SMTP id 24so1327117oij.3 for ; Sun, 28 Jan 2018 23:26:10 -0800 (PST) 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=jBpoRjt904powm3Qilff8/Q3HYiFFGqAsxqCbtJUG5g=; b=DWYX+DNCNO8tYPTYA9OS2xfeSB2iQVULg8Mu5Zullc82VWmv6ClXoskRq7hx9+EmPX 9nfTdhvvCwter9ZDtAoy/elmN8cOqvJTpxiobdNH70PYVswfF63RyJ7tWxL5XYbdUvtS z8uSydcMcfTQP82BB/hyYem5jDjiC05FG5soEamV2LY7hVsEdJR0spQtbYoKCZ/y3Jq/ 2ZWMorbX35cPhNgQ2oDoZWHdmtIGphWPfc2He2947jApXmxICDpV0CEE6Cl+PCjhLJ7U lCspIUo9gVk+eumpfW3oZAWPoV7EvWj+JWFypGTyQcFrvfcnRlTZtRGnKSi8GN2zcXe5 SW3w== 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=jBpoRjt904powm3Qilff8/Q3HYiFFGqAsxqCbtJUG5g=; b=CYbfDJivUuaIBebKSXi+du9drxJOBgzIGzzDV0OZIgcm+QxKFX+VnjDaVbfA27ZBWR 9QWADz+zYprOwR+pUsYQUE83YfRz2Y3hRn96wV3e9S9TwUyopkyoZ0zyo7VKdSIAe1vZ tE4fTVhiDwvVYvZK1hR+arP6WVecvBqaqgrdnlX2Tksn2DcnIs9vZCbsW6JXR+40sERb 1lrsBEwbmdX4jnVUIRVZBqh4w4x5EdJOhlxw+B+11kzks0Nzzv6QLU51A9hXNGthRZPe pEMC1iD0sB2JeN0wPi9EGDoJZVYZFwII49XGDrZh7wEEvQcUpyqYTlX/Lis74yur3HbG BDxA== X-Gm-Message-State: AKwxytf/nb/Hxak6GdC6IaDYdfxNylZ4aUZW8fPp1SvfYTuwe9w15E+6 92O1JpVLNtJj9h1rvuitWcwm7bKm6ohvrcE/zxYyZKBP X-Google-Smtp-Source: AH8x224ebEKb/k9GtEOgkCDFmC/Bq6Svj36f2jptD/juTHTAEwCZmLomzwigaZezfEIU5VYKtiMhszKejhXiUw8HA9c= X-Received: by 10.202.52.10 with SMTP id b10mr14174299oia.49.1517210769842; Sun, 28 Jan 2018 23:26:09 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.0.71 with HTTP; Sun, 28 Jan 2018 23:25:29 -0800 (PST) From: Odhiambo Washington Date: Mon, 29 Jan 2018 10:25:29 +0300 Message-ID: Subject: buildkernel failure on FreeBSD 11-STABLE To: User Questions Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jan 2018 07:26:11 -0000 Hi, I am trying to update a box from 11 to 11.1. I have already successfully run 'make buildworld'. I am now on the 2nd stage of 'make buildkernel" and it fails at the stage shown below. Any advise is welcome. PS: I am not willing to use freebsd-update :-) clang -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/BEASTIE-11.x/opt_global.h -I. -I/usr/src/sys -fno-common -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/obj/usr/src/sys/BEASTIE-11.x -MD -MF.depend.if_bge.o -MTif_bge.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -Wno-error-unused-function -Wno-error-pointer-sign -Wno-error-shift-negative-value -Wno-error-address-of-packed-member -mno-aes -mno-avx -std=iso9899:1999 -c /usr/src/sys/dev/bge/if_bge.c -o if_bge.o ld -d -warn-common -r -d -o if_bge.ko if_bge.o :> export_syms awk -f /usr/src/sys/conf/kmod_syms.awk if_bge.ko export_syms | xargs -J% objcopy % if_bge.ko objcopy --strip-debug if_bge.ko ===> bhnd (all) machine -> /usr/src/sys/amd64/include x86 -> /usr/src/sys/x86/include sh /usr/src/sys/dev/bhnd/tools/nvram_map_gen.sh /usr/src/sys/dev/bhnd/nvram/nvram_map -h *** Error code 2 Stop. bmake[4]: stopped in /usr/src/sys/modules/bhnd *** Error code 1 Stop. bmake[3]: stopped in /usr/src/sys/modules *** Error code 1 Stop. bmake[2]: stopped in /usr/obj/usr/src/sys/BEASTIE-11.x *** Error code 1 Stop. bmake[1]: stopped in /usr/src *** Error code 1 Stop. make: stopped in /usr/src -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft." From owner-freebsd-questions@freebsd.org Mon Jan 29 07:46:08 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 482CDEDB693 for ; Mon, 29 Jan 2018 07:46:08 +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 D065B83A38 for ; Mon, 29 Jan 2018 07:46:07 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (unknown [IPv6:2001:8b0:151:1:e930:bf41:9abc:521e]) (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 7912212E04 for ; Mon, 29 Jan 2018 07:46:06 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none (p=none dis=none) header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/7912212E04; dkim=none; dkim-atps=neutral Subject: Re: buildkernel failure on FreeBSD 11-STABLE To: freebsd-questions@freebsd.org References: From: Matthew Seaman Message-ID: Date: Mon, 29 Jan 2018 07:46:05 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Yphfj1ILVNwslSvQ16Qz0GUMzBaSeWW9v" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jan 2018 07:46:08 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Yphfj1ILVNwslSvQ16Qz0GUMzBaSeWW9v Content-Type: multipart/mixed; boundary="j1oTYnsWpN2WgBP35y3rLk2sfiumleciy"; protected-headers="v1" From: Matthew Seaman To: freebsd-questions@freebsd.org Message-ID: Subject: Re: buildkernel failure on FreeBSD 11-STABLE References: In-Reply-To: --j1oTYnsWpN2WgBP35y3rLk2sfiumleciy Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 29/01/2018 07:25, Odhiambo Washington wrote: > I am trying to update a box from 11 to 11.1. > I have already successfully run 'make buildworld'. I am now on the 2nd > stage of 'make buildkernel" and it fails at the stage shown below. Any > advise is welcome. >=20 > PS: I am not willing to use freebsd-update :-) Can you build a GENERIC kernel? How does your BEASTIE-11.x kernel config differ from GENERIC ? Cheers, Matthew --j1oTYnsWpN2WgBP35y3rLk2sfiumleciy-- --Yphfj1ILVNwslSvQ16Qz0GUMzBaSeWW9v Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKoBAEBCgCSFiEEGfFU7L8RLlBUTj8wAFE/EOCp5OcFAlpu0T5fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDE5 RjE1NEVDQkYxMTJFNTA1NDRFM0YzMDAwNTEzRjEwRTBBOUU0RTcUHG1hdHRoZXdA ZnJlZWJzZC5vcmcACgkQAFE/EOCp5OeAAxAAqW2gUkLzidNW+ZpOHTLUqiU0+NEo u6+tfbMc9jSR9umvqKLcrkP6s5QV9+7kfX6Ch3eWuLdwTeSa1IZMTpZHhT8dBKX6 UFRm274+wywUNMyB+sLMAnHT4HRWd/zyRWsXrgMLdzcopheKRn3XdJMH+Ik5458I G+UnX1hUxb8Y0iIawHfkO+0VbJsYYxg1XkgyUbRjREX9x32fzT1o1bXO1tk4fQLw 4dMz5l3pHHzP+wUU+VYYKvS1rB5vv9YHgwwu8OZImKApPN96E7fK9GlwzUWmRFzX +4bDO51Ayg+avrHLy0wMI37MLOH9mSpF/32QdUfeBokE4XoNKSXZJYJgo0qbYi4I MezKvpktMKuXh7qGqT/M54msT1tZGiw/QOvFP+ku8hfewq2+DDCd+BHSMLvvNGan c5muiFvIlW5K8cMmMWMoxc6QIBOCdfNL/D0gnR1S5VnJN7DXId5WX8YFW43pEF8P E0P03dQhEWq3s0Wsn4sBqCIEX8GOysfICKEOB8RRC8cLQe5mTWN1BiGovhFnZAS9 /3OCcKaw4lm3mJLqRpkiXI4jHecfw5n4Yw6F8HEwv5MzFvZUdqWZjhboMdDXwbjJ Y5qv7EOqyf8ihbUupNRlPoTz20JPsO+zGpBFla9rBFbqMbDgckaTdDuf1RmDFsJQ xCptwkrsBI7f0cA= =lXZi -----END PGP SIGNATURE----- --Yphfj1ILVNwslSvQ16Qz0GUMzBaSeWW9v-- From owner-freebsd-questions@freebsd.org Mon Jan 29 08:13:12 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F57EEDC8E7 for ; Mon, 29 Jan 2018 08:13:12 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: from mail-ot0-x233.google.com (mail-ot0-x233.google.com [IPv6:2607:f8b0:4003:c0f::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 E555D84885; Mon, 29 Jan 2018 08:13:11 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: by mail-ot0-x233.google.com with SMTP id v5so5751802oth.5; Mon, 29 Jan 2018 00:13:11 -0800 (PST) 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=VOY5lKyq9tGqcn6po7sOSowKF0GeHb/2Bkzef/5RXqk=; b=dF4ReDBb7FA3mceIHdMIOyHPTfi17pHxWU2abvh8G2bSv6Dy8hrwvPHZE/sFc1LJ7B 0crQnyqB0Ud9Ebynw9qXM2evOEqEqUKgX1BH4gijBu6EJ7UUUFJaY8UiKUG/Z8TMiIP5 OeFJ+Oxzu744BKUWTAb3t9D37MvzzaiJbhTIDZwEqrFpHL/JUoSplfZ5pOrSYDHcW+5I Th6P8Y2Nij+5PPJG36tUjN2cWfBkHsY+MsE3neyZwES5iP+6ZAk+I9QS3OIYjOkDd4Kz B+uPzOY/9la0p1siDb7Zvzr0roZB9i8Z2O+RacyI3imdkwT6ObiwxIJsgpHeqebG2LjY OsZw== 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=VOY5lKyq9tGqcn6po7sOSowKF0GeHb/2Bkzef/5RXqk=; b=R8rbJKGsoIKkTu2XNb+zTkVOlJ0YrIkd1b7qKxKcRIqIa5KwtZFzjlMVjwP10mhkNV mNZHtZXcSWk0P9t5dW0fG6i/J6VqW5eBoxYAp+RXlXB7TyzBMtvrmWDR1b9p/sF2jaZM CyBBFDgvU2//6ovfSHtDAN/b4XnTEPehT/HMt8W5FU2qLcSPR7yGMnfawoNA0c3gArZP gUFhA9k1WHTB6+GFEgYwY+AD87hT8tMK59TCq8GyU8ZM4QapTQxHd9Q8GdC/l+eBnuN5 5z8oU4Qc5VitgNjNHjjdgJNXws760D0/JnBDr63LRY9kK+YlKex+UgyU0o70O+kA2Q/c tH1g== X-Gm-Message-State: AKwxytcqTD3yo81118z1xJdbj69MOLrhQcmOkqyxZnh4X2Rbwxj+2cQ1 qDJpfSUhqJMxQjIIm4Uy9WXspj1YTCvTLha/S3hnyn/l X-Google-Smtp-Source: AH8x227oeLaBZfeQqs7YdfhY+p5IFRcLXYfEqGl3XvhMrjvGI8JMRKewsAjEnEF4mF7nAP9VeGE/B78/cylqHuD2C4s= X-Received: by 10.157.112.193 with SMTP id w1mr7407192otj.122.1517213590913; Mon, 29 Jan 2018 00:13:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.0.71 with HTTP; Mon, 29 Jan 2018 00:12:30 -0800 (PST) In-Reply-To: References: From: Odhiambo Washington Date: Mon, 29 Jan 2018 11:12:30 +0300 Message-ID: Subject: Re: buildkernel failure on FreeBSD 11-STABLE To: Matthew Seaman Cc: User Questions Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jan 2018 08:13:12 -0000 On 29 January 2018 at 10:46, Matthew Seaman wrote: > On 29/01/2018 07:25, Odhiambo Washington wrote: > > I am trying to update a box from 11 to 11.1. > > I have already successfully run 'make buildworld'. I am now on the 2nd > > stage of 'make buildkernel" and it fails at the stage shown below. Any > > advise is welcome. > > > > PS: I am not willing to use freebsd-update :-) > > Can you build a GENERIC kernel? > > How does your BEASTIE-11.x kernel config differ from GENERIC ? > > Cheers, > > Matthew > > Hi Matthew, Thank you for the quick response and taking your time to look at this. The result of the sdiff can be accessed on this link: https://goo.gl/pBQKtx -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft." From owner-freebsd-questions@freebsd.org Mon Jan 29 09:37:15 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 33E76EE0029 for ; Mon, 29 Jan 2018 09:37:15 +0000 (UTC) (envelope-from kremels@kreme.com) Received: from mail.covisp.net (www.covisp.net [65.121.55.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 D5FD387AB4 for ; Mon, 29 Jan 2018 09:37:13 +0000 (UTC) (envelope-from kremels@kreme.com) From: "@lbutlr" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Setting console resultion Message-Id: <5919B7EF-A04A-47CD-AFE1-3B2290420AEF@kreme.com> Date: Mon, 29 Jan 2018 02:37:05 -0700 To: Freebsd Questions X-Mailer: Apple Mail (2.3445.6.9) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jan 2018 09:37:15 -0000 I'm not sure why this is so hard, but I've read dozens of pages and = threads on setting up the console to boot into something other than VGA = 80x24 and I can't get anything to change the resolution. I have an old Core 2 duo machine with a 27" screen. Once I change by = boot.conf to use sc instead of vt, I can see the mode that I want = (1920x1440x32) but I cannot get the screen to change. vidcontrol mode=20 This is a fresh install of 11.1. If I try to load the intel driver, the screen goes blank. The onboard video connector not he machine is VGA, so even though the = monitor supports higher resolutions, I don't think those would work. I've also tried 1024x600, just to see if I can get *something* to work. Every attempt requires changing /boot/loader.conf and then rebooting, so = it gets very aggravating very quickly, and I can't find consistent = information since most of the pages i've found refer to FreeBSD 9.x or = 10.x (or sometimes earlier) and it appears a lot has changed in 11.x. I did manage to get a screensaver to load, which switches resolutions, = but I can't get the console to show anything but 80x24 text which it = overscan on the screen so the first and last character positions are = clipped. From owner-freebsd-questions@freebsd.org Mon Jan 29 11:41:55 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F2EC8EB77D2 for ; Mon, 29 Jan 2018 11:41:54 +0000 (UTC) (envelope-from zainco30@gmail.com) Received: from mail-yw0-x234.google.com (mail-yw0-x234.google.com [IPv6:2607:f8b0:4002:c05::234]) (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 877F56DD3C for ; Mon, 29 Jan 2018 11:41:54 +0000 (UTC) (envelope-from zainco30@gmail.com) Received: by mail-yw0-x234.google.com with SMTP id v139so2552707ywg.4 for ; Mon, 29 Jan 2018 03:41:54 -0800 (PST) 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=3DhbL+jQLRtY5ZgctF2xHGS8hv3y3Kb+zYjp+68XKc8=; b=R1sv5ctRov94+WFMqGVTr4oH7KRtccc6X189G7YaBHhh19VjcoDp2J98iLhe6OVLXq DGGF9ve3UAckhsC95WUFg5GK2Okb0MAPd4bwyvZ91RRpGr6bGw9c+M+Ek8sZn4cQV2tf pLt9gSBXs3GlI64Ks0IvHW2bVhVUmBegmHHMdozZ8sfCIw3RhVXlIq4Qd0Ah4lJYLsOT +3MQWzYLie111E39btT3mZ69klkqziM4iaDdRs8reDM6tjqBRuKSZKv2ho7HtHhXRuhl jiF1vzmmF6Kpam2YDFjDGl+P+k7mLvhf1CvJzCr7q8UnvyguiII0mdQUvbzkistinPGf mhzw== 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=3DhbL+jQLRtY5ZgctF2xHGS8hv3y3Kb+zYjp+68XKc8=; b=U1zsfcdkTB7TV0M6j5xr0y5v3NyxeJWyZTE/L2hPWtWJY14pcUEIC5mh2DOTUDfffa ZNs7Orm0kEzv3SJBj36OqLKPVGdo/8Uapzz9lFTpgTH37MFABCljcwe43HvgRJbrAN8o mRwfs80dVPfGiuWoMGGqtlX2hAcGugQLrFn2Uh7Hm5kmG1HfTHglYq8WJ0gt8vYZPL0A Ks9ASl0R5sEuG0ljhC22jsCe/OtaRUGQtSz+RsAxJEuCIZsGj1kiy/tS17giQruTEaFp Q4pnV0sQZ3Y7BKnlCc2TuzFsgaNbLI/Og8PIC2yDZUTnwaJBCFdKd/i9/oHdZ3gARJSn hCDw== X-Gm-Message-State: AKwxytcPuXKpvL2TsT89yPYZzIrGlZ1ru5Hw/ns5oFoeaNKavt56nO+w BfA7nW+XIxKTjjNj+n9I95bXm3Txu+MM+n7F+Luvlg== X-Google-Smtp-Source: AH8x224iGF1gCJwNjeATz797SGM9dWeLEbU9NXnwQRyPfoVWBR60itHTXce799A/qp4UaFkA1/MYO75jhlYTmvny1G4= X-Received: by 10.129.101.3 with SMTP id z3mr16524755ywb.42.1517226113665; Mon, 29 Jan 2018 03:41:53 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.46.78 with HTTP; Mon, 29 Jan 2018 03:41:53 -0800 (PST) From: "Zainelabdeen S.A Elgraeed" Date: Mon, 29 Jan 2018 14:41:53 +0300 Message-ID: Subject: ISCSI initiator inside jail To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jan 2018 11:41:55 -0000 hello I am asking can I use ISCSI initiator inside a jail or not? and how? From owner-freebsd-questions@freebsd.org Mon Jan 29 12:21:08 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1EE7BEC339E for ; Mon, 29 Jan 2018 12:21:08 +0000 (UTC) (envelope-from kremels@kreme.com) Received: from mail.covisp.net (www.covisp.net [65.121.55.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 C2BC36FCBD for ; Mon, 29 Jan 2018 12:21:07 +0000 (UTC) (envelope-from kremels@kreme.com) From: "@lbutlr" Date: Mon, 29 Jan 2018 05:21:05 -0700 Subject: Re: ISCSI initiator inside jail Message-Id: <53152960-7E1F-4484-BF95-91654AB6C249@kreme.com> References: In-Reply-To: To: freebsd-questions@freebsd.org X-Mailer: iPhone Mail (15E5167f) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jan 2018 12:21:08 -0000 On Jan 29, 2018, at 04:41, Zainelabdeen S.A Elgraeed wr= ote: > I am asking can I use ISCSI initiator inside a jail or not? and how? Does this help? https://forums.freebsd.org/threads/51780/ --=20 This is my signature. There are many like it, but this one is mine.= From owner-freebsd-questions@freebsd.org Mon Jan 29 13:21:56 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA49EEC6B34 for ; Mon, 29 Jan 2018 13:21:56 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward102p.mail.yandex.net (forward102p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:102]) (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 0428E72867 for ; Mon, 29 Jan 2018 13:21:55 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from mxback8j.mail.yandex.net (mxback8j.mail.yandex.net [IPv6:2a02:6b8:0:1619::111]) by forward102p.mail.yandex.net (Yandex) with ESMTP id 677424302C77; Mon, 29 Jan 2018 16:21:44 +0300 (MSK) Received: from smtp2o.mail.yandex.net (smtp2o.mail.yandex.net [2a02:6b8:0:1a2d::26]) by mxback8j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id fCeTeEeAcf-LioWfvOY; Mon, 29 Jan 2018 16:21:44 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1517232104; bh=j4YHJjVl3au513vwasvf7cE6+uTPrBfta0Ze+/p3LZs=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=NVs+ge22m+aO81SSSrp8ARfy9Wy8UXkgUqWjWkPXb6SSpzgF6GVgb/fPXT/KS5cGz dK1NIbAGW+joU9dwKMEyx8/UeCnEo88DLD4OodTGfl/lI/pyDfdhG5c0gFsecNWmD5 +i3WoKPNQL1K6O+LpMqjrJFiCGbrYg6rmdRMIO7A= Received: by smtp2o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id qqfMmW6xiu-LhdW9pea; Mon, 29 Jan 2018 16:21:43 +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=passap.ru; s=mail; t=1517232103; bh=j4YHJjVl3au513vwasvf7cE6+uTPrBfta0Ze+/p3LZs=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=TA4eD9Sr9iq3uB7wGg6svu2nBPQUjX2tu+gIn4+eH1Opwfh83ydKIXaOwBiIsh9Jp idfe+XhqBSUNg+kSOW7q5uazi1UTowtHHf8H42pC0pmmIUlobwKWVNOnJxXfeekLiN ORxe6NfeYqH67Jst6h0bsPBiFAQezqAG1vdbqCgs= Authentication-Results: smtp2o.mail.yandex.net; dkim=pass header.i=@passap.ru Subject: Re: Setting up an https accessible git server on FreeBSD To: David Mehler , freebsd-questions References: From: Boris Samorodov Message-ID: <62e7858b-b2ba-ce1b-6150-c302dcfe7dd1@passap.ru> Date: Mon, 29 Jan 2018 16:21:43 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jan 2018 13:21:56 -0000 29.01.2018 04:10, David Mehler пишет: > If anyone has a git server going on FreeBSD, accessible via http smart > protocol https only, i'd appreciate knowing how you got it going? I'm > wanting to make private repos accessible to myself and a select group > of users invisible to everyone else. I use www/gitea for git repositories. Nice and fast enough tool. It listens at localhost only: [...] [server] HTTP_ADDR = 127.0.0.1 HTTP_PORT = 3333 [...] While for HTTPS I use www/nginx reverse proxy: [...] listen 443 ssl; location / { proxy_pass http://localhost:3333; } [...] HTH -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From owner-freebsd-questions@freebsd.org Mon Jan 29 14:44:11 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B0D39ECACA7 for ; Mon, 29 Jan 2018 14:44:11 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1968F768A8 for ; Mon, 29 Jan 2018 14:44:10 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.213.55]) by mrelayeu.kundenserver.de (mreue007 [212.227.15.167]) with ESMTPA (Nemesis) id 0LiJxI-1fCDhB38to-00clSJ; Mon, 29 Jan 2018 15:44:05 +0100 Date: Mon, 29 Jan 2018 15:44:04 +0100 From: Polytropon To: "@lbutlr" Cc: Freebsd Questions Subject: Re: Setting console resultion Message-Id: <20180129154404.f1662f20.freebsd@edvax.de> In-Reply-To: <5919B7EF-A04A-47CD-AFE1-3B2290420AEF@kreme.com> References: <5919B7EF-A04A-47CD-AFE1-3B2290420AEF@kreme.com> 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-Provags-ID: V03:K0:BK7bOmWKCsAQMwOMhYV1GTDUaP/WxnDd9njzakM17QfJGixYVdb GvBOl1t6XLvJI4ltb/J4hylR1xfXulD/9MBVMq6/vPc6cYaOwg0nQqNqzWYpiQbfufu0Rpu nEaOkMkUPzdRDpcbyY4G8+QcGRAgIsLl3PeFBLE0Q47Zf1nKAoVHgYbokrzCZUcDDSZswOL +xAxyZNsMtrlDKSRrAwfw== X-UI-Out-Filterresults: notjunk:1;V01:K0:uCYS6lkl4p4=:FyEQ2pNF94T993KDKXpUG3 X0SYff4MckfGR7bS5aFjFApGoSXWrbHJOkXRdTBzZJQJtKRHpiphg/gzd5wSrFj5HZvHGmDGX k7IwI83Pa5dI5muENmoig7vuAR3KAYK3oxz8przikpWNYEeWuYNBZW4yV2qzCa+hWR59/MO08 UvVmVr9CeQIB3ZGh0F3qj/5R2LPkISSeL16a/HnyucVnF0a93vajpSQ6IN3RdalY4eFKs7YrW gzG6cWU0dA7otg6lx9tuH+J7vtIxBZLm9ObgEOzgydECtH2051nfJzM/85bnxEGJNMm60PJGn 3h1laOSX2iySR6EzO1T90McDfKhQsbho4nohBN3GEPLwJskT5ooe+2HLmuYsbgDXTdi3Ek5BL 1P6YGp82o2mLRD0qmuZM4tIvqT8l1hVJJPlJSBgaX6sJ+gQE/GXCN4p2e8XeTi67YmJ4vQ69e rOFQ8ahunti4jcqa0bAXTmpd7PvHFz+/2Z/0VVKIOZ76EdtRIb19+FkcU7OofZCOxcOb824Dc 9SuL/QIWgBCR2ubDgLAk0fPhmbYzquVSAPPQvavSqZs2/ZOHd2FnQJ+bjX2aCaKYY9JNnIB/Z ycQQNymGbnap4SGtovZ8RGuYH0yyaLE7XIXVxXsohuZ0jP+1bO4UmZcOdTdb+UursMEhhX2Yq MgGtT7P8vBfFKgcnn72NY2usQebAT9N3Eqg4bna93ZKhB4sgnSG4QXmeMk39X0c4g0Fhdy9ai Y2OrgwtvKbt9fYGkH05kUibFkXW6uZai/Z+ujZMi+kqlaJjroiLNKQJr7Co= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jan 2018 14:44:11 -0000 On Mon, 29 Jan 2018 02:37:05 -0700, @lbutlr wrote: > I'm not sure why this is so hard, but I've read dozens of pages > and threads on setting up the console to boot into something > other than VGA 80x24 and I can't get anything to change the > resolution. I think with vt, it's the exact opposite problem: You cannot set it to 80x25 anymore. ;-) > I have an old Core 2 duo machine with a 27" screen. Once I > change by boot.conf to use sc instead of vt, I can see the > mode that I want (1920x1440x32) but I cannot get the screen > to change. > > vidcontrol mode > This is a fresh install of 11.1. > > If I try to load the intel driver, the screen goes blank. If you are using X, you cannot use sc anymore. X requires the use of vt now. > The onboard video connector not he machine is VGA, so even > though the monitor supports higher resolutions, I don't think > those would work. > > I've also tried 1024x600, just to see if I can get *something* > to work. If you can, use the exact size of your monitor (in pixels); I assume you're talking about a LCD monitor, which is common today, as hardly anyone still uses CRTs like I do (which can have more than one mode, while LCDs only have one physical mode, determined by the amount of pixels). > Every attempt requires changing /boot/loader.conf and then > rebooting, so it gets very aggravating very quickly, and I > can't find consistent information since most of the pages > i've found refer to FreeBSD 9.x or 10.x (or sometimes > earlier) and it appears a lot has changed in 11.x. The vt documentation isn't fully complete yet, but here is a good starting point: https://wiki.freebsd.org/Newcons Maybe this is helpful too: https://forums.freebsd.org/threads/49601/ https://forums.freebsd.org/threads/55222/ > I did manage to get a screensaver to load, which switches > resolutions, but I can't get the console to show anything > but 80x24 text which it overscan on the screen so the first > and last character positions are clipped. In all settings I've tested, vt has always changed the "text mode" resolution from 80x25 to something much bigger (and therefore unreadable tiny ugly characters). The key is that you now cannot set a screen size (in columns x lines), instead you have to deal with fonts, the screen's size in pixels (if it has any), and this also depends on the OS version... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Mon Jan 29 16:00:59 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 465F4ECE998 for ; Mon, 29 Jan 2018 16:00:59 +0000 (UTC) (envelope-from dave.mehler@gmail.com) Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c: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 B6AC479785 for ; Mon, 29 Jan 2018 16:00:58 +0000 (UTC) (envelope-from dave.mehler@gmail.com) Received: by mail-wm0-x22d.google.com with SMTP id v123so34676977wmd.5 for ; Mon, 29 Jan 2018 08:00:58 -0800 (PST) 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:content-transfer-encoding; bh=Y0D+8NhMX4S/wqACKyXCZCyjFwjhfp1oMlUjX/rxpL8=; b=ingiCtSRD81ULBQv5+Q6QVOgiJStX1FgeMyVkQ1Nl+/+vWAosT1ql+yWzwhVzAKLXo qRFCJGlv1N9ZyyJCOED4y2T+A4djs0uAm5Dy7MRhxWbDM5vfk4PsC6SIZN6IFyZfE/6y 9gEtDMkiiLc+ZM+9jToVONy+wrEq7XZzopSmN00djqqjSm33CAV5SVCRXVOsEhQxqAbF Pu9dgRmZ7RH9yHVqJ5yvkY1il9cIqgCCJLCEIGd3MXZUt6eJ/3XYZBMi/KhMM0AZ9Ros h1akPJjxRmwq0RvJQPY7q3y6uOhNmDPZo6kl0QAIqeLOT6nOHW98+q2TXWS5Z4XCmAas GrFA== 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:content-transfer-encoding; bh=Y0D+8NhMX4S/wqACKyXCZCyjFwjhfp1oMlUjX/rxpL8=; b=QHjG+XaiS9RFNL1mt00TXQXcrDbbGoEws7Fx5E3DswJsd+LSrSx3k/r3gs5LiMDmt/ kbiTpoTtG9HccDFC0U8PqBkXDeS3Kk9vxuKtDama6k8NEA0YfbTWw8ab24kogAjbQS0y CzXcvE5RbjButoavq14gE+WdtEheOyFj2QPLdpigCayXgXZH6EYMx0Z7TWstEo6dTPlB z/uoYq+1ZqAc1dBzuXJH3ZMgw8E1kIny5sZUPCZuseLhFyGqnfXCbNpVMaU4ySVkeIoL f5ZSj+8MFIHJu2yIjC95/g55e8iJ7Xx9dot0RvVZ+FmG93Z5F5IjC1QZtc8Dv+wrIIFH 3njw== X-Gm-Message-State: AKwxytcXpg5Sa8M5Yr3E4w2iBG+VfcQfTZ0K29LdcJ6kGmbPAPRLKSSE 7GzKV3y88H68peCUeyiSvN0JgiwjBCH7UaEp4mI= X-Google-Smtp-Source: AH8x225oHq2XZVbopALi/s5sjjBjiDALmPtraCK7zZdgzNBxph0tVOZZa7XXwf8rZlqLgu+43zKjJQ+2MTQW2XfwZUY= X-Received: by 10.28.166.20 with SMTP id p20mr17400386wme.85.1517241657667; Mon, 29 Jan 2018 08:00:57 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.141.184 with HTTP; Mon, 29 Jan 2018 08:00:57 -0800 (PST) In-Reply-To: <62e7858b-b2ba-ce1b-6150-c302dcfe7dd1@passap.ru> References: <62e7858b-b2ba-ce1b-6150-c302dcfe7dd1@passap.ru> From: David Mehler Date: Mon, 29 Jan 2018 11:00:57 -0500 Message-ID: Subject: Re: Setting up an https accessible git server on FreeBSD To: Boris Samorodov Cc: freebsd-questions Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jan 2018 16:00:59 -0000 Hello Everyone, Thank you for your replies. Are there any solutions that utilize apache? Thanks. DAve. On 1/29/18, Boris Samorodov wrote: > 29.01.2018 04:10, David Mehler =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > >> If anyone has a git server going on FreeBSD, accessible via http smart >> protocol https only, i'd appreciate knowing how you got it going? I'm >> wanting to make private repos accessible to myself and a select group >> of users invisible to everyone else. > > I use www/gitea for git repositories. Nice and fast enough tool. > It listens at localhost only: > [...] > [server] > HTTP_ADDR =3D 127.0.0.1 > HTTP_PORT =3D 3333 > [...] > > While for HTTPS I use www/nginx reverse proxy: > [...] > listen 443 ssl; > location / { > proxy_pass http://localhost:3333; > } > [...] > > HTH > -- > WBR, Boris Samorodov (bsam) > FreeBSD Committer, http://www.FreeBSD.org The Power To Serve > From owner-freebsd-questions@freebsd.org Mon Jan 29 19:19:15 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 824C8ED91BF for ; Mon, 29 Jan 2018 19:19:15 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (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 2170581D3F for ; Mon, 29 Jan 2018 19:19:15 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: by mail-io0-x22b.google.com with SMTP id f89so8803459ioj.4 for ; Mon, 29 Jan 2018 11:19:15 -0800 (PST) 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=AqHRqm7CvTShCdjetUqcw+FYouIJKgShiNp89+R9iYI=; b=iq+P4Ls5TrflCMnVzOh91nDrpbLzfoy0hJInx1u9s5cyJSiPsxABAc5ya3Fbc/uJba 1fA7b+yZFQ/uiA8iTf42Daic6irW21odl3pd0XCem8kGnIVGUvlqA0NcDPj4eweEwU5q pOj4YMEQ9nyeY7VmvL7pWekd+mO1qG3nRoLMBbXWD2ZcjUaEeqFrJaZyVceldzBq+lXd 73QVQ3QYGKy7om52uuoOeKod6nJZrbCeMPoRbfu8jwzrQoobZfJl5AkqmgMmvSU7M7hO p2eRqgZDrWCvErNXxqoJmIxcIPjmQBLd5fDgNKFkg/kMSL3aHEM+qxR7nKfhcGUDvqHn ERbw== 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=AqHRqm7CvTShCdjetUqcw+FYouIJKgShiNp89+R9iYI=; b=f2li9IzZXzttPqiRQmwmc053kX0wFvcgCGp2dKMah/H0tkce+3sR8Nmtn4Gv8EOpXA 2dMLun54Rn/FDNTSs+JtyV6+FSf1TK+Id/DF80GA+MTkwrP23FR/wokGmxrWK+aEMDql EO6bihrjgtKEeK6wRqlsUhZn8NE0pxJ8a3dSSI+cnyuHW/DdGG0YgpnmedHEIbK54Vr1 pwiXrrBXNY3F5xgjEzlqCQC9/g67Is1fJU3+/l4gSLoLsUw21sLgLk87PvXwwHxFuVDs EKPAXNzIWH7ALFaArz3reOXCiEXikjR1SID+drpP+2Zjbskv59KPYF3AC9MIL5YP7Ijx vuHg== X-Gm-Message-State: AKwxytd8zbQsFKz1IA8+hRhj3bfH95UT70dCJC01zGkniCbN9x/ZaOYQ 0C5EhgwGxKEfo8w7fVSfi94vTpibTVtLCBTSb8Iekw== X-Google-Smtp-Source: AH8x2257JeaDF+UW9XX1a25tHrXEyKRLqbX2H4636UG2iXBhw/IOXeLRQeO9gRyfqysKfD4j4xsbhjS/nGuO0kzZiCU= X-Received: by 10.107.137.26 with SMTP id l26mr28095699iod.108.1517253553996; Mon, 29 Jan 2018 11:19:13 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.198.138 with HTTP; Mon, 29 Jan 2018 11:19:13 -0800 (PST) From: Kurt Buff Date: Mon, 29 Jan 2018 11:19:13 -0800 Message-ID: Subject: Synth error message I don't understand To: "freebsd-questions@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jan 2018 19:19:15 -0000 All, Just completed a run with synth, and at the end I see an error, but I can't seem to find anything regarding it. Any help would be appreciated. This is the line that has me puzzled: raised PROGRAM_ERROR : finalize/adjust raised exception Also, help understanding the messages regarding the packages failing dependency checks would be useful. The full console output is below. Thanks, Kurt # portsnap fetch update && synth upgrade-system Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found. Fetching snapshot tag from your-org.portsnap.freebsd.org... done. Fetching snapshot metadata... done. Updating from Tue Jan 30 03:02:27 EST 2018 to Tue Jan 30 03:45:12 EST 2018. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 0 metadata files... done. Fetching 1 patches. (1/1) 100.00% done. done. Applying patches... done. Fetching 0 new ports or files... done. Removing old files and directories... done. Extracting new files: /usr/ports/ftp/curl/ Building new INDEX files... done. Regenerating flavor index: this may take a while ... Scanning entire ports tree. Querying system about current package installations. Stand by, comparing installed packages against the ports tree. Scanning existing packages. cairo-1.14.8_1,2.txz failed dependency check. gobject-introspection-1.50.0,1.txz failed dependency check. harfbuzz-1.7.4.txz failed dependency check. gcc6-aux-20170802.txz failed dependency check. pango-1.40.6.txz failed dependency check. rrdtool-1.7.0_1.txz failed dependency check. nfdump-1.6.16.txz failed dependency check. nfsen-1.3.8_1.txz failed dependency check. The task is complete. Final tally: Initial queue size: 36 packages built: 36 ignored: 0 skipped: 0 failed: 0 Duration: 00:33:39 The build logs can be found at: /var/log/synth Stand by, prescanning existing packages. Removed: py27-sphinx-1.4.8_2,1.txz Removed: curl-7.57.0.txz Removed: glib-2.50.2_7,1.txz Removed: pkgconf-1.4.0,1.txz Removed: binutils-2.28,1.txz Removed: php56-5.6.32_1.txz Removed: php56-sockets-5.6.32_1.txz Removed: cmake-3.10.1_2.txz Removed: php56-session-5.6.32_1.txz Removed: portmaster-3.19_2.txz Removed: mod_php56-5.6.32_1.txz Stand by, recursively scanning 148 ports serially. raised PROGRAM_ERROR : finalize/adjust raised exception From owner-freebsd-questions@freebsd.org Mon Jan 29 20:29:27 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 758AFEDCE4A for ; Mon, 29 Jan 2018 20:29:27 +0000 (UTC) (envelope-from johannes-maria@t-online.de) Received: from mailout12.t-online.de (mailout12.t-online.de [194.25.134.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0596484B2E for ; Mon, 29 Jan 2018 20:29:26 +0000 (UTC) (envelope-from johannes-maria@t-online.de) Received: from fwd08.aul.t-online.de (fwd08.aul.t-online.de [172.20.26.151]) by mailout12.t-online.de (Postfix) with SMTP id 0332741F630E for ; Mon, 29 Jan 2018 21:21:52 +0100 (CET) Received: from t-online.de (SrHcgvZ-whLE4oLeIJo-Lle8nP7Q8XHC3fClwSrKVOdeTJDdzQznfdbhrXKnH5UwjL@[84.145.225.114]) by fwd08.t-online.de with (TLSv1:DHE-RSA-AES256-SHA encrypted) esmtp id 1egFw2-0kAqAq0; Mon, 29 Jan 2018 21:21:46 +0100 Received: by t-online.de (nbSMTP-1.00) for uid 1001 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-SHA (256/256 bits)) johannes-maria@t-online.de; Mon, 29 Jan 2018 21:21:46 +0100 (CET) Date: Mon, 29 Jan 2018 21:21:45 +0100 From: Johannes-Maria Kaltenbach To: freebsd-questions@freebsd.org Subject: Re: problem with upgrade and unable to build openjdk8 in poudriere Message-ID: <20180129202145.GA2773@localhost.org> References: <20180115151549.GA9923@localhost.org> <20180128130433.GA2196@localhost.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-ID: SrHcgvZ-whLE4oLeIJo-Lle8nP7Q8XHC3fClwSrKVOdeTJDdzQznfdbhrXKnH5UwjL X-TOI-MSGID: 3ee15404-8d9a-4ecd-8ee4-7f222c2a80fe X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jan 2018 20:29:27 -0000 Hello Matthew, thanks for your help and explanations. On Sun, Jan 28, 2018 at 11:59:43PM +0000, Matthew Seaman wrote: > On 28/01/2018 13:04, johannes-maria@t-online.de wrote: > > On Mon, Jan 15, 2018 at 04:15:49PM +0100, johannes-maria@t-online.de wrote: > >> Hello, > >> > >> I'm still working with 9.3 and thought it's time to install 11.1 > >> but there are two problems I couldn't solve myself. > >> > >> I've never worked with jails or poudriere before and probably > >> made some errors so I first describe in detail what I've done. > >> > >> To not destroy my working system I made this on a separate > >> (clear) slice of my hard disk. > >> > >> First I installed the basic 11.1 system with the boot disk > >> (FreeBSD-11.1-RELEASE-amd64-disc1.iso) without problems. > >> > >> Then I installed poudriere (pkg install poudriere) > >> and created a jail with poudriere: > >> poudriere jail -c -v 11.1-RELEASE -a amd64 -j 11amd64 > >> and installed the ports tree: > >> poudriere ports -c > >> I created a list of ports to install and started poudriere: > >> poudriere -v bulk -j 11amd64 -f list_of_ports_to_install > >> > >> > >> First problem: > >> > >> One of the ports to install is x11/kde4 which as a dependency > >> adds java/openjdk8 to the list but poudriere seems to be > >> unable to build it: > >> =>> Failed ports: java/openjdk8:build > >> [excerpt from the log-file: > >> gmake[2]: *** No rule to make target '1'. Stop. > >> gmake[2]: Leaving directory '/wrkdirs/usr/ports/java/openjdk8/work/openjdk/langtools/make' > >> ] > > I can't really give you much help with this: openjdk8 is building just > fine for me on 11.1-RELEASE. This is probably some small configuration > mistake that will have you face-palming once you find it... did you built it in the ports or with poudriere? I have also no problem building it in the ports: a make in java/openjdk8 runs through without an error. But not if it's build with poudriere (and it was the only package with such a problem in poudriere) and as a consequence poudriere could also not build x11/kde4 (in which I'm interested; no interest in java/openjdk8 itself). > >> And therefore > >> =>> Skipped ports: devel/antlr devel/kdesdk4 devel/poxml x11/kde4 > >> > >> On the other hand a direct make in ports/java/openjdk8 is successful > >> but it fails repeatedly when called by poudriere. > >> > >> > >> Second problem: > >> > >> I tried to install the successfully built software > >> (i. e. my list without kde4) with > >> pkg -j 11amd64 upgrade > >> but this fails with > >> pkg: jail "11amd64" not found > >> > >> and jls doesn't list any jails > >> whereas > >> poudriere jail -l > >> displays > >> JAILNAME VERSION ARCH METHOD ... PATH > >> 11amd64 11.1-RELEASE-p6 amd64 ftp ... /usr/local/poudriere/jails/11amd64 > >> > > OK. Confusion over jails here. > > The '-j' flag to pkg(8) allows you to install files into a jail from the > host system. As you don't have any actual jails configured, you don't > want to use this flag. > > These are completely different to the jails used by poudriere. In fact, > when you "create a jail" by eg. > > poudriere jail -c -j 11amd64 -v 11.1-RELEASE -a amd64 -m ftp > > What you are actually doing is creating a template. 'poudriere jail -l' > will list all the templates poudriere knows about. It's only during a > poudriere run that jails are actually created from these templates -- in > fact, as many jails as the degree of parallelism you've allowed in > poudriere.conf. Try running jls(1) while poudriere is compiling stuff > and you'll see. These build jails are only temporary and are destroyed > as soon as the poudriere run ends. thanks for your explanations. Yes, I misunderstood it and as already stated I've no experience or knowledge of jails. > Now, poudriere will collect all the packages it has built into a > repository. It's typical to set up a webserver (nginx recommended) to > allow distribution of those packages, and you will need to write a > configuration file for pkg(8) giving the correct URL for your custom > repository. You'll probably also want to turn off the default FreeBSD > package repository -- see the comment in /etc/pkg/FreeBSD.conf for how > to do that. Then you can just upgrade your system by: > > pkg upgrade > > Hint: try 'pkg -vv' to see your pkg(8) configuration including all the > repositories you have configured. I'm not sure what the correct URL for the poudriere-created repository is, so I looked in /var/poudriere for something plausible and thought it could be /usr/local/poudriere/data/packages/11amd64-default so I set up a /usr/local/etc/pkg/repos/FreeBSD.conf with: FreeBSD: { url: "file:///usr/local/poudriere/data/packages/11amd64-default/", mirror_type: "none", signature_type: "none", enabled: yes } pkg -vv confirmed that ist URL would be used. Then pkg upgrade produced the following output: Updating FreeBSD repository catalogue... FreeBSD repository is up to date. All repositories are up to date. Checking for upgrades (123 candidates): .......... done Processing candidates (123 candidates): . done Checking integrity... done (0 conflicting) Your packages are up to date. At least there was no error but none of the packages which poudriere had built [built 954, 1 failed, 4 skipped] were installed. I don't know how to proceed. Best regards, Johannes-Maria From owner-freebsd-questions@freebsd.org Mon Jan 29 21:19:39 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E7F8EDF569 for ; Mon, 29 Jan 2018 21:19:39 +0000 (UTC) (envelope-from kaylin@smtsz.top) 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 18BB287062 for ; Mon, 29 Jan 2018 21:19:39 +0000 (UTC) (envelope-from kaylin@smtsz.top) Received: by mailman.ysv.freebsd.org (Postfix) id CBA2AEDF567; Mon, 29 Jan 2018 21:19:38 +0000 (UTC) Delivered-To: questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A6E89EDF566 for ; Mon, 29 Jan 2018 21:19:38 +0000 (UTC) (envelope-from kaylin@smtsz.top) Received: from out29-94.mail.aliyun.com (out29-94.mail.aliyun.com [115.124.29.94]) (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 DCECC87061 for ; Mon, 29 Jan 2018 21:19:36 +0000 (UTC) (envelope-from kaylin@smtsz.top) X-Alimail-AntiSpam: AC=AD; BC=0.7725134|0.2358864; BR=01201311R211b1; CH=blue; FP=9202822159408549545|2|2|2|0|-1|-1|-1; HT=e01e01534; MF=kaylin@smtsz.top; NM=1; PH=DS; RN=1; RT=1; SR=0; TI=SMTPD_---.AcBWq.F_1517257108; Received: from DESKTOP-SUPA2ML(mailfrom:kaylin@smtsz.top fp:113.91.38.70) by smtp.aliyun-inc.com(10.147.41.138); Tue, 30 Jan 2018 04:18:29 +0800 Message-ID: <20180130041828526.kaylin@smtsz.top> MIME-Version: 1.0 From: "Smart" To: "Questions" Reply-To: sales5@smartsecurityinfo.com Date: 30 Jan 2018 04:18:28 +0800 Subject: small spy camera hidden install see the true life 04:18:26 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jan 2018 21:19:39 -0000 Hello Questions,=0D=0A=0D=0AWant see what happen when you are not= at home? Try this small wireless wifi camera, you will see the w= orld.=0D=0A=0D=0A=0D=0A=0D=0AHidden anywhere, with build in batte= ry=0D=0ABuild in HD 1080P camera=0D=0AWifi connection to local ne= twork=0D=0ACan keep video and audio on tf card=0D=0ACheck the vid= eo remote on app=0D=0AFree app for ios and android =0D=0A=0D=0ACo= ntact with us for more information.=0D=0ABest Regards.=0D=0ALeo L= ee=0D=0A=0D=0ASmartTechnology (ShenZhen) co., Limited=0D=0AAdd:F6= , No348, Ai Nan Road,Long Gang District,Shenzhen, China.=0D=0ATel= : 86-755-2690 1469Fax: 86-755-2691 6144=0D=0AMp: 86-134 8096 7752= =0D=0A=0D=0AEmail:sales5@smartsecurityinfo.com=0D=0ASkype: smarts= ecurityhk=0D=0AUnsubscribe/=E9=80=80=E8=AE=A2=0D=0A04:18:26=0A=0Aw9rPGeAk3eO7e7awY7UZHTTMfQaBPHn0OajyKQqCjQ4Ne0i= HxKwMTEvCgEzQ3YulROj3OBM7GiFRP5yext45bA6aEGi5gzykmIWqHeSVXo5BYENa= 5kiAUoahH8o8jGQ7Jlu697xjA88MuvbZS70VhYpXxEJyQKBgxYRDaG1XNZZLgoMbX= ofcGUQKVxzuoYtPxSewDyPc528hYDG9SxBrvpzD87IC7wyPwaeo9gxoy36EMyLhQp= CQm1k7iBowQd4ztiLOpiZC0cSsiVQzlqMHUIsuQ66yS0ylYxatNXSyqZQa8RPmLOb= prmELQgYicrKZDxuLKmLnydhURhmYhJN3P9UBSpCxYzlYfRwBn3Bo2NQd5KTzUZ0s= EG9uDSSlJeoYSiE0LLBd7o11iGw8v3CYzSkzH2XubgFNoSkM5TN8oNlfF8bWmJQFB= qpZY5iJN62RJdCqlJ3BguzMx4UzQ08rpZbYslOZB4liKtwrvKACGep7QDsTbJSMXA= rJ1EX0V30b8h13ys35qwKbA38PSVORbyl91NqRNAHCedZyBokIFMmrQg8Xv880e80= zWR2K1ciQO8Wn4zeuA5cocTjKEslFrHn5dpCJmzHtuwCHkKTVTDp9WBn2xh5zQDo7= KRaFWu80oIUGhBqUzqLOhe9B1Ab4t8DQ7uXsAeZpvoKeGHLWQbZqSAQvIyDmi3wg5= 3yMDXjlrliStVVkPfdi8cYxEsK2AC6rSu8D8ZiTSEZwhX1NDix3Qe8S407bdhKOfQ= 0ZMibPXkpudsgHqXoi53BDmgy8S6FATagqW10k6H5vODECKpKfSsIbfnDwK3XQEOA= 2bPKoW4boX5OIBVoslqIrs5bzouA3JeR03CqUEljOgkd9yVVOFvve69A6Db0st8EJ= eOEYvtNZ6Ua7R21szMneJCTT1jhtlQk7GuUJgWicHv7cYtfBayTGLpZBUKXbbjEgz= 3qm7hcCtbweuHVy4GjMXEmgvjPvZ60oQRCU2TtSmgczTL6dPp7v0RiVHaQOsGDna8= nD40vbcqqGrMnKcBGAZunZyHdS2FqFCPoLnt8OTWjzqBuUN6BQ03nGKo4nND9w0K4= BnBmItRG3bOyWdj5V3zFzsI0ZoK1gNMyFxSwbKTm8mjuWP7atxdsq5u9FBmkIQqgo= fSokMUbacxc8e4agAxIzk8A3JRznzEiW35GWJPHD2idxh1rxc38iIG47hlBUkNByf= g48odxLQ4x2U2LIq2bvvZem1yFndMjeGEi1Wi8YvmsD92dfATuhB52f2H6Pyax3Li= lfKJL7Tc08xAdZlqMji1CBB2ZecjqlPpSQHXuQ7mnp5UIru7u8neLJGJDHKxVAMEj= 7HninVVbVDdwHkxK5PiXAD9aXjN6ArNDqAAK6P6cr2P5scWncMPLtHItydk48PBtQ= A67JNDgI5wyN4HLnqUNC19IR6bTu24CqmeS6ODp9z2naaFuwzGIVNROqngDBJLG1U= 8rPOFzMuD2ZLyHqHnVlmGCvqsIx0NpOmmg1eFHT7Vq9OPEPzcUmPkEdvVomW1MHee= CphFc2F1ergsHANSYOS3Y1H3wjglW69IVzcfyT0SGN6dW2eOy42YPagBHd9SMj48i= yw7oyk5N0maUu7t4sNS3aTKjAxkK76mIYVov6pZJXaPO5Hd6FOkwc47FLNN0ZkGUZ= rVyIXX2N9603WdTke5jLQwUOJKjCZKDtVOELFnIQhJ2Y6BPATGKfn89U1JZdEqOpt= w88z8FRntu6uVH8UJIiZo6MFKJVoubRVDvzsH1K1TSUD2q52RiVHwp4plsOpKsShC= bQq8FdHYg5wc9CjDSxcgapdq96eclhqZC1QzFTb4dJfkydcPuLRVG1sMC0YyZvCYE= wz7MJYZl72q9TRWUoHzqvjBy3XFVC5H6hF2D43KNRzzY1DJ81EBO3x9dYzIMi3J1k= kSePjPkWLyVKDwqewTYuT2JvPFvkYuOQxDHKvjIPgRiYetl2iyM9Kxqh9IZEj0YgK= 4cZPFJcb9e2KKgmjt2pIE5ZdpBMk4vfT1eaglcCPzYBjoxosDkQXyx6YdMp4WS6DY= 8Iv56Xgpz8FuGOSckGKFhlt8c3zMySGRYlgOTmxmzyYoquxYxRCcmYGNenT3ouRHs= Nwkx4jY9n5Jm5HIvBfHguvZFtzvsuY5GhWDYcqsxE2YTWr9GaxMe9qXiwF4uOvFp0= 2484KjbM9Csw6I2pPiWbQwQZkrxlXJ9nzSTm1BqdBr0OvLqW25YdId9vd8JjMPOpt= 4WdPFodRJApw2uy0AiSLWFlIn8SR7rLCBlqPc7mHLlZDKZbEaibwWExoBurxvlKhO= MUH3JOtWbZAGIYoXeGPgeGXN1dIFPbpAHOY4tBruHAKEWITw3AgEV0A5XT1v5N6Zz= 0YT0jtDfkyEWiRjkbCeVLEHeS7AzVoUtK4VKZwK6DoArV9F1IbTbR4OlgE7cT3kWE= abdVykFR8hm4fiIryRKuICFfAtloydA4DNLXr59QekJNsh1loKlbzsWywXl5ZhjUH= hqswL0sIUgoSSNisZZOSovbRdrtK3QW0P6aQyODJTtFbxFEa3DZhv2iLeBjkwIE3j= n2LCsTam4YVQZjxMjHqREvMNoBXvicbOBSaCSxAKPVq3nVeiLxd0ecESfYdQVE3SN= 6e79UUL6G1J5JqtnFKLYaApdinUjKOaRyfgH79QCsUxaVMwxKtgUiTDvOURx0rlSR= Rwt9LfwT8wf2fhvQmzhxfzFCKTciiC0zFi4g2nYdK1amosyDlHDS3kChRRpS3eAvw= GnWceOZA4NepjehkyWBZ7vlGMoaY69wqEPH5Bq7SEiZwnSyD7xuhZwoa2gqQD1tUh= OLtwcI8PJlPwOiUQwQyFer8qx3l0geDO4fz657VPmsfbyEdXvZ7aVf2mD2Z8n8yuH= 1ryJNLpVJiLbWRSPnvh7sTPcct28MseULtxcFeHeIebWhbGa6iZDgme8CmwkIg8h4= RptkGa8N2peHSV1NS2usBDpepAiInvr5URqLdPp7QPeX0qKquxQeEOtd0eV6RqqwX= 8M0ufz2CmBLpseYQSdQFdr5odLYUjgppHZSEJWfXNBicHNy0XfZdARKHGChuA8i6b= mIslk6VXSRB9SGpdYW3gcPPebX6ELmFic1l55ED93fHZ8xNWShCbePZxSeamZhcwb= iWRlj7jjUcX7Q5D9aLuKu4m1NdRtg9M2aOQAWAy9iRkD2p28xdOvIMHeAQx6gQ2Lp= UX2f2dAckrCJIZnaIW2kgko6B053sTsOyd7s0Tv0eink4uSQ9VxT0r8zyVD27wKrZ= ObuSVaPq15YW3277fTwlyO75xU5ftTIyWlgjnYeLIsYlaCvSwURCd6qZ3pk15zX8m= p0IMNJhFLC5PLUUpcIy25kPUgfYDdF8vQYKBM6IazXstl9iupBSQo5h5bNvyLDs5u= AZM9jC60os8Smy6XteBNh6KHFqYAapVumZLavl6ZMQ0D8cOfoAhpQicte5tSDvPZw= DwnNWs87B0r57ztCJcz7wE4MhVqSelh116uGqrr89hehLn7vZfTjfR0ZsAw11gTfJ= p414NbiKqYepM1TOUSYsXLa6veQVq6ToYylj6qc3BzPSLzFyCc7oUNLEUVzylmjk5= QqeGAItFVQoWhkVyhieZvtaMHpbRDHefuNV9rS2uDIZXnHCAE0435kAmfsZawC1dB= 8ruoL7pgJlMudpZMAcDDbaaczTZSRX0HLmeg7cSSFNlYOS230nWpnAqXhhPR8wpLk= 4IRaIFnkKYnOboGRWSt1BkbWgYPn0K8oADJabShIy5CB285T80bEVKJKwUTJP0j0P= ZexEwG3BKswHzT7SWe0yusQUYDgYxTyLCM2UyeCj83ahd3W1MQTLjrlxoDFSq53RT= K4NRdkHCGqrhyHVHfcG0MrbruvVyJT3ZjosY89ywb9C0TgQWKbbSnR6jTmmHp8SNn= rXaeXy5DaODPbxeFZOyHaCsh95MMQ72gPCriGHNC5ed2ttIO82qkk5dPvT5RLjM2L= m0y6WZh1VCVppNFmXEOHIWJpCMMBVRMsah7t9Ib38jothq55quOEYl3ph9t9cG54P= te8GbdfsLzoxf7bGHbq From owner-freebsd-questions@freebsd.org Tue Jan 30 00:04:28 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E1A89EC2AB3 for ; Tue, 30 Jan 2018 00:04:27 +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 04F2D6DFAB for ; Tue, 30 Jan 2018 00:04:25 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (unknown [IPv6:2001:8b0:151:1:a10b:46dc:663d:903b]) (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 B194D12F4D for ; Tue, 30 Jan 2018 00:04:09 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none (p=none dis=none) header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/B194D12F4D; dkim=none; dkim-atps=neutral Subject: Re: problem with upgrade and unable to build openjdk8 in poudriere To: freebsd-questions@freebsd.org References: <20180115151549.GA9923@localhost.org> <20180128130433.GA2196@localhost.org> <20180129202145.GA2773@localhost.org> From: Matthew Seaman Message-ID: <9043f574-25d7-12f7-e219-e37bbefbde8c@FreeBSD.org> Date: Tue, 30 Jan 2018 00:04:08 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <20180129202145.GA2773@localhost.org> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="VxB8g0jWfYs2gTGoU0RAYmfaTKvnjvbfw" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2018 00:04:28 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --VxB8g0jWfYs2gTGoU0RAYmfaTKvnjvbfw Content-Type: multipart/mixed; boundary="N4Xdymjz50Is0Mjv397VILLrrXofk6j4M"; protected-headers="v1" From: Matthew Seaman To: freebsd-questions@freebsd.org Message-ID: <9043f574-25d7-12f7-e219-e37bbefbde8c@FreeBSD.org> Subject: Re: problem with upgrade and unable to build openjdk8 in poudriere References: <20180115151549.GA9923@localhost.org> <20180128130433.GA2196@localhost.org> <20180129202145.GA2773@localhost.org> In-Reply-To: <20180129202145.GA2773@localhost.org> --N4Xdymjz50Is0Mjv397VILLrrXofk6j4M Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 29/01/2018 20:21, Johannes-Maria Kaltenbach wrote: >>>> First problem: >>>> >>>> One of the ports to install is x11/kde4 which as a dependency >>>> adds java/openjdk8 to the list but poudriere seems to be >>>> unable to build it: >>>> =3D>> Failed ports: java/openjdk8:build >>>> [excerpt from the log-file: >>>> gmake[2]: *** No rule to make target '1'. Stop. >>>> gmake[2]: Leaving directory '/wrkdirs/usr/ports/java/openjdk8/work/o= penjdk/langtools/make' >>>> ] >> >> I can't really give you much help with this: openjdk8 is building just= >> fine for me on 11.1-RELEASE. This is probably some small configuratio= n >> mistake that will have you face-palming once you find it... >=20 > did you built it in the ports or with poudriere? I'm building it with poudriere >> Now, poudriere will collect all the packages it has built into a >> repository. It's typical to set up a webserver (nginx recommended) to= >> allow distribution of those packages, and you will need to write a >> configuration file for pkg(8) giving the correct URL for your custom >> repository. You'll probably also want to turn off the default FreeBSD= >> package repository -- see the comment in /etc/pkg/FreeBSD.conf for how= >> to do that. Then you can just upgrade your system by: >> >> pkg upgrade >> >> Hint: try 'pkg -vv' to see your pkg(8) configuration including all the= >> repositories you have configured. >=20 > I'm not sure what the correct URL for the poudriere-created > repository is, so I looked in /var/poudriere for something > plausible and thought it could be > /usr/local/poudriere/data/packages/11amd64-default > so I set up a /usr/local/etc/pkg/repos/FreeBSD.conf with: >=20 > FreeBSD: { > url: "file:///usr/local/poudriere/data/packages/11amd64-default/", > mirror_type: "none", > signature_type: "none", > enabled: yes > } Yes, that looks about right. The '11amd64-default' part is the combination of the poudriere jail name and the ports tree used to build those packages. pkg(8) should work fine with a file:// URL, but obviously that only works to install packages on the same machine where you run poudriere. One thing I'd recommend: change the 'tag' for your own repository so that it's different to the default 'FreeBSD:' It doesn't matter what you use here. The tag is just an arbitrary label. > pkg -vv confirmed that ist URL would be used. >=20 >=20 > Then pkg upgrade produced the following output: >=20 > Updating FreeBSD repository catalogue... > FreeBSD repository is up to date. > All repositories are up to date. > Checking for upgrades (123 candidates): .......... done > Processing candidates (123 candidates): . done > Checking integrity... done (0 conflicting) > Your packages are up to date. >=20 > At least there was no error but none of the packages > which poudriere had built [built 954, 1 failed, 4 skipped] > were installed. > I don't know how to proceed. Well, try updating your ports tree (poudriere ports -u) and then running a poudriere bulk to update any outdated packages. Then try 'pkg upgrade' again. Chances are something will have an update available. For extra credit, try changing the options on a package (poudriere options -c some/port), update your repo via (poudriere bulk ...) and then do 'pkg upgrade' -- pkg(8) should notice the changed options and update the package for you. You can then use pkg-info(8) to show the option settings your package was compiled with to verify that it is the one you built. Failing that, just install anything. Use 'pkg rquery -a %n-%v' to get a list of all your available packages, and then just install something interesting. Cheers, Matthew --N4Xdymjz50Is0Mjv397VILLrrXofk6j4M-- --VxB8g0jWfYs2gTGoU0RAYmfaTKvnjvbfw Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKoBAEBCgCSFiEEGfFU7L8RLlBUTj8wAFE/EOCp5OcFAlpvtnhfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDE5 RjE1NEVDQkYxMTJFNTA1NDRFM0YzMDAwNTEzRjEwRTBBOUU0RTcUHG1hdHRoZXdA ZnJlZWJzZC5vcmcACgkQAFE/EOCp5OdWqA//blwLHjpBVMRcbrCTm2YXpPfWCF3b sGcxYl0seuR7CM0+hRSUr9o51vAt6aHcJU7khsd+V3359YkPv3/OxLNyjCNPlals zV9TTl9q4uzJjI4ouCMqCFcLRqqBq+lmC5fBI5Edw36mEaYR4XMYWpHFvqAB3OW9 aT4kjjemIKrjnQLCFwdLEVsFu13hQkKi4iAGMX/x3S57n2LA9JKFGumU3+rYZhyB bt8EeEKwCG9k+WemMfcmRfCSdrTrHcvuVNmixkFt46f4gzTJmK+xB4IttyEzKHEt 1CoJsTSnKS8mv9QHBFgrpBDAGfOXwJt+sgMgxPWZiJYpKTxnpPsJJa6yTGHRY96Q NWFnS1e4luiEWZlprO64EToPoUNIHwj4//jltUKZd6NPGUyrIax1mW+1e/xaefl/ XWp+lzKk8HGCPK47QeelYN0Ult7Gk/ApGHT9p8xtkx1TV81bBlAel8nsrqFaN9qv fLORpmYvytRtB63C5n6aoA3n3ckkNFWKJJ4mI+rRmbjcHHMqDAgJ3/frs2lgitON N+qq5tDZl1GjpFHXVfY2e5bF6LzDfZilmiEzm0xO7PBSr9HtQGGffWvoYflQ26g+ 9EhGm4zNcH98EqGEXH/Bo23jLuLmrVO1+SqIK4tKQ0Zl2D5SMxe7tZzEKgy+ivxl fmbxMC+fivkjdHs= =r5QP -----END PGP SIGNATURE----- --VxB8g0jWfYs2gTGoU0RAYmfaTKvnjvbfw-- From owner-freebsd-questions@freebsd.org Tue Jan 30 04:07:59 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1C8C9ED5095 for ; Tue, 30 Jan 2018 04:07:59 +0000 (UTC) (envelope-from kremels@kreme.com) Received: from mail.covisp.net (www.covisp.net [65.121.55.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 9E39579373 for ; Tue, 30 Jan 2018 04:07:57 +0000 (UTC) (envelope-from kremels@kreme.com) From: "@lbutlr" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Re: Setting console resultion Date: Mon, 29 Jan 2018 21:07:54 -0700 References: <5919B7EF-A04A-47CD-AFE1-3B2290420AEF@kreme.com> <20180129154404.f1662f20.freebsd@edvax.de> To: Freebsd Questions In-Reply-To: <20180129154404.f1662f20.freebsd@edvax.de> Message-Id: X-Mailer: Apple Mail (2.3445.6.9) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2018 04:07:59 -0000 On 29 Jan 2018, at 07:44, Polytropon wrote: > On Mon, 29 Jan 2018 02:37:05 -0700, @lbutlr wrote: >> I'm not sure why this is so hard, but I've read dozens of pages >> and threads on setting up the console to boot into something >> other than VGA 80x24 and I can't get anything to change the >> resolution. >=20 > I think with vt, it's the exact opposite problem: You cannot > set it to 80x25 anymore. ;-) I dunno, that was what my console was set to and I could not change it. >> I have an old Core 2 duo machine with a 27" screen. Once I >> change by boot.conf to use sc instead of vt, I can see the >> mode that I want (1920x1440x32) but I cannot get the screen >> to change. >>=20 >> vidcontrol mode=20 >> This is a fresh install of 11.1. >>=20 >> If I try to load the intel driver, the screen goes blank. >=20 > If you are using X, you cannot use sc anymore. X requires > the use of vt now. I do not use X, I am only talking about the text console. >> The onboard video connector not he machine is VGA, so even >> though the monitor supports higher resolutions, I don't think >> those would work. >>=20 >> I've also tried 1024x600, just to see if I can get *something* >> to work. >=20 > If you can, use the exact size of your monitor (in pixels); > I assume you're talking about a LCD monitor, which is common > today, as hardly anyone still uses CRTs like I do (which can > have more than one mode, while LCDs only have one physical > mode, determined by the amount of pixels). LCDs support many resolutions, and the VGA connector will not support = the maximum number of pixels the screen can display (2564x1440). Also, there will be a different display connected once the setup is done = and the machine is actually installed in it's final location. >> Every attempt requires changing /boot/loader.conf and then >> rebooting, so it gets very aggravating very quickly, and I >> can't find consistent information since most of the pages >> i've found refer to FreeBSD 9.x or 10.x (or sometimes >> earlier) and it appears a lot has changed in 11.x. >=20 > The vt documentation isn't fully complete yet, but here is a > good starting point: >=20 > https://wiki.freebsd.org/Newcons kldload i915kms <- screen goes black, never comes back. hw.vga.textmode <- already set kern.vt.fb.default_mode=3D"1024x768" Not sure if I tried that specific number, as that's still a very limited = sccreen size, but certainly the other numbers I tried did not work. Reading that, other than UTF-8 support, vt appears to be extremely = limited and its know issues list is nearly 4 years old, which certainly = gives one pause. "Pre-loading i915kms.ko/radeonkms.ko disables video output from the = point of time these video drivers are attached until interrupt threads = are enabled way later. This makes kernel panics during boot = undebugable." Anyway, I have set the console to use sc which is how I got a = screensaver to load (not that I want/need a screensaver, but I was = testing) and I've managed to set the screen size of a current session, = but I still can't get it to change during boot (so I can actually read = some of the output) and I have to apply it to each console manually = after logging in. > The key is that you now cannot set a screen size (in columns x lines), = instead you have to deal with fonts, the screen's size in pixels (if it = has any), and this also depends on the OS > version... This seems needlessly obtuse and complicated. Not that sc was much = better, though things have gotten much worse that they were in, say, = freebsd 9 in terms of plugging in a screen and having a reasonable hope = you'd be able to set it to a mode where each characters isn't 24-30 = points. --=20 Bart, don't use the Touch of Death on your sister. From owner-freebsd-questions@freebsd.org Tue Jan 30 11:32:21 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 809D5EC355C for ; Tue, 30 Jan 2018 11:32:21 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E423168348 for ; Tue, 30 Jan 2018 11:32:20 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.213.55]) by mrelayeu.kundenserver.de (mreue005 [212.227.15.167]) with ESMTPA (Nemesis) id 0Mczwc-1ePMja3E0Y-00I9sQ; Tue, 30 Jan 2018 12:32:08 +0100 Date: Tue, 30 Jan 2018 12:32:07 +0100 From: Polytropon To: "@lbutlr" Cc: Freebsd Questions Subject: Re: Setting console resultion Message-Id: <20180130123207.b7739451.freebsd@edvax.de> In-Reply-To: References: <5919B7EF-A04A-47CD-AFE1-3B2290420AEF@kreme.com> <20180129154404.f1662f20.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-Provags-ID: V03:K0:V8HEZ7SpBU2Z9xQXuft2Zm9Vq/9rD6i5/4hu5yk6ibSszRxBxHb SV3nh6vNf+7m1xt7fBDoXJbjnaumcPLqrvUlldsUtE1GAZrdVzBYQLXEdxRpkZlplkRnQ0p AkfkHc0X3+OBwcP2uc+u+ZD8kGHd/x5pupg54jUlWm1ERjrTBW2SfycsmRmpibAKF7Rg4nb zs7cZQdDvsEIKR1WKPS8g== X-UI-Out-Filterresults: notjunk:1;V01:K0:bw0kTmTrByU=:HSWge2b1IGnC8VvTf5JU0C SRenBPxywgjStVOitveT61I7vyGVPF6eb7tpskD3mvx46+SILSzTJrRww5PtB5NsYK7bQCqO3 X96HKxr6gOj+0QmxZJBmELQg9LAh4+FtEDOVHuepIu0b/lTG9fIP8OTVjlbavfHD+lBkWNgOa Trvi6ltiLJVa+z/inGtTCNRaWjb7VPl9OyfoTz5E68Ynsti1uiGAKb7JatSmaFQ/e9M4ygmAg h34wNhLdPWGTxjwKGrN1VgqWtYQq1uG09gVidoxrk+UM9th4ukOsuyiL0f6NxLxRdvz0u73Fd Fgv7lGLJLEo742AqiD92Hw9duh5JjYAXiHB1imW8ALiLX6tQ3+UKLIaXY+O6Kl9br+0uQ8J1U wUtgGHjWzE9PaUmaubizGSTcqOBdb1pXLhRVJQNDIR7b9yI2n/IPwfMOYdZQLg31b5h5dNi/U /dRa1jKrjOZ2cd/I9mcy0Ny2UPQe7AAFIZn3yzEQEFFgrBCsoLhb7X8M728QeQxOtM9ZLtbnv u2GAES8EfVf0Rx/OH76KvBssRdFS6RwGc1P74/uC8CgQbngLHcdjOR3fuQ5o+0xPtvp1gx1w0 TDlijEZgjKdwyQJsxHtvCz/C1rlMcmx7ongRAJbZ8MK1SVsIvI0nPW82WIKNehNDS5ddA6YwE mZu0twpau0EsPzqaq8LxPWac2MQQAUozOEG1jEsWWAr16SCOiUIswy3qAQ8D/9UNzk4wNJXAk DSXfCdhX2H0P5NjwOtC1T+6g4as+WIZUiLPvIWxWO3Sg1o9PwaMqm0cr63s= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2018 11:32:21 -0000 On Mon, 29 Jan 2018 21:07:54 -0700, @lbutlr wrote: > On 29 Jan 2018, at 07:44, Polytropon wrote: > > On Mon, 29 Jan 2018 02:37:05 -0700, @lbutlr wrote: > >> I'm not sure why this is so hard, but I've read dozens of pages > >> and threads on setting up the console to boot into something > >> other than VGA 80x24 and I can't get anything to change the > >> resolution. > > > > I think with vt, it's the exact opposite problem: You cannot > > set it to 80x25 anymore. ;-) > > I dunno, that was what my console was set to and I could not change it. With vt as the console driver? Is that even possible?! > >> I have an old Core 2 duo machine with a 27" screen. Once I > >> change by boot.conf to use sc instead of vt, I can see the > >> mode that I want (1920x1440x32) but I cannot get the screen > >> to change. > >> > >> vidcontrol mode > >> This is a fresh install of 11.1. > >> > >> If I try to load the intel driver, the screen goes blank. > > > > If you are using X, you cannot use sc anymore. X requires > > the use of vt now. > > I do not use X, I am only talking about the text console. In that case, you can choose between vt and sc. I'd suggest becoming friends with vt under any circumstances as sc will probably be abolished soon. Both systems allow you to change the screen resolution, and with sc, it has always been easy to do (with vidcontrol). But you've been talking about loading the intel driver, this is usually only needed if you want to use X (and X requires you to use vt instead of sc), that's why my assumption that you also were using X on that system (because this is the only reason to load that driver). > >> The onboard video connector not he machine is VGA, so even > >> though the monitor supports higher resolutions, I don't think > >> those would work. > >> > >> I've also tried 1024x600, just to see if I can get *something* > >> to work. > > > > If you can, use the exact size of your monitor (in pixels); > > I assume you're talking about a LCD monitor, which is common > > today, as hardly anyone still uses CRTs like I do (which can > > have more than one mode, while LCDs only have one physical > > mode, determined by the amount of pixels). > > LCDs support many resolutions, and the VGA connector will not > support the maximum number of pixels the screen can display > (2564x1440). An LC display has only a fixed amount of pixels, and this amount does _not_ change. What you are describing is done in software. Still it's common for LCDs to address them in their native mode. So if a display has 2564x1440 pixels ("hardware pixels"), this should be the mode the driver talks to it in; however, if its internal software also "speaks" 1024x768, you can get to see something in that mode, even though it will look ugly. But many displays are able to internally "re-calculate" images and either apply a border, or just scale them up ("light 2x2 pixels where the source image contains 1"). So if you input 1200x800 px, the device _can_ scale it up to fill 2564x1440 px, but that doesn't change its physical properties. Note that even though commonly "resolution" is being used as a term for "size in pixels", it's technically not correct. The resolution is provided in dpi, dots per inch, like 75, 100, or 120 dpi (with the assumption that the horizontal and the vertical resolution will be equal), or 150x150dpi (to explicitely state they are equal): width in inch height in inch resolution = ------------- x -------------- pixels wide pixels high As both values are _physically fixed_ on a flatpanel display, the resolution is also fixed ("native resolution"). On a CRT, the amount of (addressable) pixels changes with the size, so does the resolution. > Also, there will be a different display connected once the > setup is done and the machine is actually installed in it's > final location. In combination with vt, this might require you to change your settings once you got them working for _one_ display. > >> Every attempt requires changing /boot/loader.conf and then > >> rebooting, so it gets very aggravating very quickly, and I > >> can't find consistent information since most of the pages > >> i've found refer to FreeBSD 9.x or 10.x (or sometimes > >> earlier) and it appears a lot has changed in 11.x. > > > > The vt documentation isn't fully complete yet, but here is a > > good starting point: > > > > https://wiki.freebsd.org/Newcons > > kldload i915kms <- screen goes black, never comes back. I'm almost sure you won't need that if you use sc. For vt... maybe yes... but this is probably only needed if you are going to use X (which you denied). > hw.vga.textmode <- already set This is only relevant for vt. > kern.vt.fb.default_mode="1024x768" This isn't the size in pixels your system has (it's even 4:3, nobody uses that anymore). Use the loader command "gop" to see what the system _thinks_ your screen looks like. > Not sure if I tried that specific number, as that's still a > very limited sccreen size, but certainly the other numbers I > tried did not work. It might cause the screen to blank, or to to perform a fallback to a known "good mode". Maybe you can experiment with the following syttings (from a FreeBSD 10.3 system connected to a CRT with now unreadable "text mode" thanks to vt): /boot/loader.conf: kern.vty=vt hw.vga.textmode=0 i915kms_load="YES" # can be removed if causing trouble && !X /etc/rc.conf: allscreens_flags="-f gallant" # ugly This will give you 132x54 ugly characters on a 21" 4:3 CRT. :-) Try fonts like vgarom-8x14 or vgarom-8x8 if you want to try a smaller character size. I have also experimented with kern.vt.fb.default_mode in /boot/loader.conf, but it didn't seem to have any effect. The "gop" loader command is not available on FreeBSD 10, so I couldn't check that. > Reading that, other than UTF-8 support, vt appears to be > extremely limited and its know issues list is nearly 4 years > old, which certainly gives one pause. Yes, vt doesn't provide the functionality sc provided for decades, without any trouble. Keep in mind vt isn't text mode. It is already a graphics mode that just disguises as a text mode (by displaying text characters). But vt is rich on features, it's just that the documentation isn't complete yet. If you want things like normal 16 colors, block graphics or german umlauts, then definitely stay with sc; vt hasn't achieved that level of excellece yet. ;-) > "Pre-loading i915kms.ko/radeonkms.ko disables video output > from the point of time these video drivers are attached > until interrupt threads are enabled way later. This makes > kernel panics during boot undebugable." Great... > Anyway, I have set the console to use sc which is how I got > a screensaver to load (not that I want/need a screensaver, > but I was testing) and I've managed to set the screen size > of a current session, but I still can't get it to change > during boot (so I can actually read some of the output) and > I have to apply it to each console manually after logging in. With vt, the screensaver wouldn't even work. ;-) > This seems needlessly obtuse and complicated. Not that sc > was much better, though things have gotten much worse that > they were in, say, freebsd 9 in terms of plugging in a > screen and having a reasonable hope you'd be able to set it > to a mode where each characters isn't 24-30 points. The alternative "solution" is to have tiny crappy characters and blurry colors, so you can't read anything on your huuuge screen. ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Tue Jan 30 16:34:03 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 89893ED4195 for ; Tue, 30 Jan 2018 16:34:03 +0000 (UTC) (envelope-from kremels@kreme.com) Received: from mail.covisp.net (www.covisp.net [65.121.55.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 35CD374B07 for ; Tue, 30 Jan 2018 16:34:02 +0000 (UTC) (envelope-from kremels@kreme.com) From: "@lbutlr" Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Date: Tue, 30 Jan 2018 09:33:54 -0700 Subject: Re: Setting console resultion Message-Id: <6825E56C-1AA5-4B34-9221-28B987C321C9@kreme.com> References: <5919B7EF-A04A-47CD-AFE1-3B2290420AEF@kreme.com> <20180129154404.f1662f20.freebsd@edvax.de> <20180130123207.b7739451.freebsd@edvax.de> In-Reply-To: <20180130123207.b7739451.freebsd@edvax.de> To: freebsd-questions@freebsd.org X-Mailer: iPhone Mail (15E5167f) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2018 16:34:03 -0000 I=E2=80=99ve seen gop mentioned a few times and I have no idea what it is, o= r what a =E2=80=9Cloader command=E2=80=9D is. Do you mean rebooting into the= boot loader on the initial pre-startup screen (multi user, single user, etc= ?) --=20 This is my signature. There are many like it, but this one is mine. > On Jan 30, 2018, at 04:32, Polytropon wrote: >=20 > The "gop" loader command is not available on FreeBSD 10, > so I couldn't check that. From owner-freebsd-questions@freebsd.org Tue Jan 30 16:36:29 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C22F2ED4419 for ; Tue, 30 Jan 2018 16:36:29 +0000 (UTC) (envelope-from kremels@kreme.com) Received: from mail.covisp.net (www.covisp.net [65.121.55.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 71FAD74DB5 for ; Tue, 30 Jan 2018 16:36:29 +0000 (UTC) (envelope-from kremels@kreme.com) From: "@lbutlr" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 30 Jan 2018 09:36:28 -0700 Subject: Re: Setting console resultion Message-Id: References: <5919B7EF-A04A-47CD-AFE1-3B2290420AEF@kreme.com> <20180129154404.f1662f20.freebsd@edvax.de> <20180130123207.b7739451.freebsd@edvax.de> In-Reply-To: <20180130123207.b7739451.freebsd@edvax.de> To: freebsd-questions@freebsd.org X-Mailer: iPhone Mail (15E5167f) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2018 16:36:29 -0000 On Jan 30, 2018, at 04:32, Polytropon wrote: > The alternative "solution" is to have tiny crappy characters > and blurry colors, so you can't read anything on your huuuge > screen. ;-) Sorry, hit send too soon. Silly tiny screen phone. Under FreeBSD 9.x I had no problems reading a console screen set to 132x50. -- This is my signature. There are many like it, but this one is mine. From owner-freebsd-questions@freebsd.org Tue Jan 30 16:56:00 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8203DED597B for ; Tue, 30 Jan 2018 16:56:00 +0000 (UTC) (envelope-from dalescott@shaw.ca) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0A876761BC for ; Tue, 30 Jan 2018 16:55:59 +0000 (UTC) (envelope-from dalescott@shaw.ca) Received: from dalet420 ([174.0.43.39]) by shaw.ca with ESMTP id gZCJef6Ekb3YIgZCKe1Wov; Tue, 30 Jan 2018 09:55:53 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shaw.ca; s=s20150330; t=1517331353; bh=1U1CODgf3O20nBhlccr0nG5xwa6nsYF4IwHjYOMDrm8=; h=From:To:Subject:Date; b=w2K+wX69Pm9/lAzfP/z4DO1hTcskfg0cuKsjRZLb3SBFj5xEnzQKrwJYF0lXDTIiH IwI19E5lZ5MqozNf7mGIqcSQ9F4NC/Naco6W1B0FjLG0mBN5g4kZa0EEujA4Yv7/C+ h8tDdMI5GRukct7PSt+uSDnC6d/pltiib0qCkVtaXPkHLB76CP9HtATjoHMbkH+aAz umYId65NvmA7IRVdYM/84tkVJzKYmRZC3KrV+QERgwYSzlPLU8MiRxnEK20obtBRrG 044kTtuP1rELPDkSVbSpEwi5AEvYCIexQwzQ42iVE+Y2ax5AV30BhN7uasBNBoMRQb IyqCpJAv7xklA== X-Authority-Analysis: v=2.2 cv=J/va1EvS c=1 sm=1 tr=0 a=TiBur8m8wieNAdBnNdHE5Q==:117 a=TiBur8m8wieNAdBnNdHE5Q==:17 a=x7bEGLp0ZPQA:10 a=DAwyPP_o2Byb1YXLmDAA:9 a=5mcg790sAAAA:8 a=s9oXJcMGAAAA:8 a=mDV3o1hIAAAA:8 a=RNKTT3IqYLM9geqPklwA:9 a=wPNLvfGTeEIA:10 a=dI9p-avQWAUA:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=-40Vp6Y4ial9AZcOMS8A:9 a=dbvwRFfKCrPPDsZu:21 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10 a=uQeDYW1NI25gHNlrW_eK:22 a=cNNliUDrGJfcKjVfkxUC:22 a=_FVE-zBwftR9WsbkzFJk:22 From: "Dale Scott" To: Subject: freebsd tar fails but not gtar ?!? Date: Tue, 30 Jan 2018 09:55:53 -0700 Message-ID: <00d101d399eb$318a7c40$949f74c0$@shaw.ca> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdOZ6hy+YoGt9BwcQSSfttQOWlAkxA== Content-Language: en-us X-CMAE-Envelope: MS4wfH2CcMGgOW9m7RMpXUePYxFi2YaEY0Kabg9lYSaphV65Pb5hfmbDdcHnrs5cE3+RoUqB0YLcbqEQwCVje9uyBVuP0w4cJnOuN1rXV1oED6GIyJ4Eu6gB c0zdSDqg4NMwwnwU5RnAaA+c0ktfvpB8UmAPneO7E/ZXCtVKMX3sZXGo Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2018 16:56:00 -0000 Hi all. I noticed the tar backup of my WordPress content directory is failing. It may be coincidental that the filenames tar is failing are = longer than 99-characters, which was reportedly a failing of the =93old=94 tar. = I installed gtar from packages and it completes successfully. Adding = =96posix to the tar command doesn=92t help. It=92s been suggested that locale on the = system isn=92t set correctly. Does this sound familiar to anyone? =20 Fwiw, the failing long filenames were auto-generated by WordPress. I was writing a blog post in Chrome on a Windows system and found I could = paste images from the Windows clipboard directly into the WordPress editor. =20 Thanks, Dale =20 dale@whizzer:~ % uname -a FreeBSD whizzer.dalescott.net 11.1-RELEASE-p4 FreeBSD 11.1-RELEASE-p4 = #0: Tue Nov 14 06:12:40 UTC 2017 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 =20 First, basic native tar on FreeBSD 11.1 =20 dale@whizzer:~ % sudo tar cf /backup/yyyy-mm-dd/webapps/wordpress_wp-content.tar /usr/local/www/wordpress/wp-content tar: Removing leading '/' from member names : Can't translate pathname 'usr/local/www/wordpress/wp-content/uploads/2018/01/2018-01-25-14_52_00-f= ix- Removed-leave-and-join-chapter-web-pages-by-vishdha-=C2=B7-Pull-Request-1= 11-=C2=B7-. png' to UTF-8: Can't translate pathname 'usr/local/www/wordpress/wp-content/uploads/2018/01/2018-01-25-14_52_00-f= ix- Removed-leave-and-join-chapter-web-pages-by-vishdha-=C2=B7-Pull-Request-1= 11-=C2=B7-- 150x150.png' to UTF-8: Can't translate pathname 'usr/local/www/wordpress/wp-content/uploads/2018/01/2018-01-25-14_52_00-f= ix- Removed-leave-and-join-chapter-web-pages-by-vishdha-=C2=B7-Pull-Request-1= 11-=C2=B7-- 300x201.png' to UTF-8: Can't translate pathname 'usr/local/www/wordpress/wp-content/uploads/2018/01/2018-01-25-14_52_00-f= ix- Removed-leave-and-join-chapter-web-pages-by-vishdha-=C2=B7-Pull-Request-1= 11-=C2=B7-- 768x514.png' to UTF-8: Can't translate pathname 'usr/local/www/wordpress/wp-content/uploads/2018/01/2018-01-25-14_52_00-f= ix- Removed-leave-and-join-chapter-web-pages-by-vishdha-=C2=B7-Pull-Request-1= 11-=C2=B7-- 1024x686.png' to UTF-8: Can't translate pathname 'usr/local/www/wordpress/wp-content/uploads/2018/01/2018-01-25-14_52_00-f= ix- Removed-leave-and-join-chapter-web-pages-by-vishdha-=C2=B7-Pull-Request-1= 11-=C2=B7-- 100x100.png' to UTF-8dale@whizzer:~ % dale@whizzer:~ % =20 Next, native freebsd tar with --posix flag (google found some Linux = posts that indicated pre-posix tar had a filename length limit) =20 dale@whizzer:~ % sudo tar cf --posix /backup/yyyy-mm-dd/webapps/wordpress_wp-content.tar /usr/local/www/wordpress/wp-content tar: Removing leading '/' from member names : Can't translate pathname 'usr/local/www/wordpress/wp-content/uploads/2018/01/2018-01-25-14_52_00-f= ix- Removed-leave-and-join-chapter-web-pages-by-vishdha-=C2=B7-Pull-Request-1= 11-=C2=B7-. png' to UTF-8: Can't translate pathname 'usr/local/www/wordpress/wp-content/uploads/2018/01/2018-01-25-14_52_00-f= ix- Removed-leave-and-join-chapter-web-pages-by-vishdha-=C2=B7-Pull-Request-1= 11-=C2=B7-- 150x150.png' to UTF-8: Can't translate pathname 'usr/local/www/wordpress/wp-content/uploads/2018/01/2018-01-25-14_52_00-f= ix- Removed-leave-and-join-chapter-web-pages-by-vishdha-=C2=B7-Pull-Request-1= 11-=C2=B7-- 300x201.png' to UTF-8: Can't translate pathname 'usr/local/www/wordpress/wp-content/uploads/2018/01/2018-01-25-14_52_00-f= ix- Removed-leave-and-join-chapter-web-pages-by-vishdha-=C2=B7-Pull-Request-1= 11-=C2=B7-- 768x514.png' to UTF-8: Can't translate pathname 'usr/local/www/wordpress/wp-content/uploads/2018/01/2018-01-25-14_52_00-f= ix- Removed-leave-and-join-chapter-web-pages-by-vishdha-=C2=B7-Pull-Request-1= 11-=C2=B7-- 1024x686.png' to UTF-8: Can't translate pathname 'usr/local/www/wordpress/wp-content/uploads/2018/01/2018-01-25-14_52_00-f= ix- Removed-leave-and-join-chapter-web-pages-by-vishdha-=C2=B7-Pull-Request-1= 11-=C2=B7-- 100x100.png' to UTF-8dale@whizzer:~ % =20 Finally with gtar =20 dale@whizzer:~ % gtar --version tar (GNU tar) 1.29 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later . This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. =20 Written by John Gilmore and Jay Fenlason. dale@whizzer:~ % sudo gtar cf /backup/yyyy-mm-dd/webapps/wordpress_wp-content.tar /usr/local/www/wordpress/wp-content gtar: Removing leading `/' from member names dale@whizzer:~ % ls /backup/yyyy-mm-dd/webapps/wordpress_wp-content.tar /backup/yyyy-mm-dd/webapps/wordpress_wp-content.tar dale@whizzer:~ % ls -lh = /backup/yyyy-mm-dd/webapps/wordpress_wp-content.tar -rw-r--r-- 1 root wheel 505M Jan 28 19:46 /backup/yyyy-mm-dd/webapps/wordpress_wp-content.tar dale@whizzer:~ % =20 Output of locale: =20 dale@whizzer:~ % sudo locale LANG=3D LC_CTYPE=3D"C" LC_COLLATE=3D"C" LC_TIME=3D"C" LC_NUMERIC=3D"C" LC_MONETARY=3D"C" LC_MESSAGES=3D"C" LC_ALL=3D dale@whizzer:~ % =20 =20 =20 --- Dale R. Scott, P.Eng. Web: http://www.dalescott.net =20 =20 From owner-freebsd-questions@freebsd.org Tue Jan 30 19:45:25 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 38801EDE89F for ; Tue, 30 Jan 2018 19:45:25 +0000 (UTC) (envelope-from odhiambo@gmail.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 C2BC37DAC9 for ; Tue, 30 Jan 2018 19:45:24 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 8388BEDE89E; Tue, 30 Jan 2018 19:45:24 +0000 (UTC) Delivered-To: questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4937EEDE89D for ; Tue, 30 Jan 2018 19:45:24 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (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 DDCB07DAC7 for ; Tue, 30 Jan 2018 19:45:23 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: by mail-oi0-x22f.google.com with SMTP id c189so8011897oib.12 for ; Tue, 30 Jan 2018 11:45:23 -0800 (PST) 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=/Rh7MTZazD0o5HtKeTzvJMlGvtv8LUzKRMfs9N3ppSY=; b=V3BkdSiZrw4Njv6IZ9rN4wJFkIDlvSiGHYb/uVRyP9LA9JfF+7G768/3d9bf5Yk2rE aAMGqqIRL30UNHoWMqzKDEXYaWpVzdK0ls9wJV5VSmlgSN8pdnrYfJIap+s6IJOv6Lsw OqshYv1nJScLz5QNnSW092JMhPzZ4OUK3kv8SMrt6DNkRAf5ACsARaGy21nevtrSLAIq UlucZvPuQyU0Recn/HxTx/ofyTu4QvNtJc9qJC2cBEMy1J7MZ2mxjhD8JlCyDlBCGIWQ 0hcMYYIEruAaIhX08jRkcAuS4RZ6/cS2wQF+vYVXD0JXqYuj3d+RIb381vt8g7ffPKY8 daVQ== 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=/Rh7MTZazD0o5HtKeTzvJMlGvtv8LUzKRMfs9N3ppSY=; b=bF1XoPdd9WtJQ1NcnnKZ126OqoWBjf8Cgwz/Fx73dk3zRbqIYvSS5vtR7bbPkk8jRj TxViqm2tbkwYLH21kcge5Ta08w1eeQPvx2cUDcpEM3eFhGFpGm/t0E9QU1mpOlw4Jdn7 gmCv7NRrYqi9V1xZyXFU+Fz/J9Vggs8JgHN6BDECmFpNz64Pg0m6gpN0QUpxuNvF6OVY hSaquRg+/E7zGLX8vamHjRXCN205NTR5klcibmsX/mk7VIwW7EyF6Fzm6K53GRFBo2hE Gp1wgOJ9QoUtEZlOVr7cGYBjn6Q9IJX6QlP7qLuwBSlbAYnVfwemo/e9S1oYhwumcQxD DgSg== X-Gm-Message-State: AKwxytcggQXbA0a0BzKEMjla8rLMHFNlwrQ0hM8x5QxamSeRa/RQFM7x TiMmtUO+NFNt0N9Nq5b7NwDL48i0fSkUgqcsGckLaA== X-Google-Smtp-Source: AH8x227DtG8YuzOx5hD+sxZoRR6dVK+Bp8aujZJa5YgdX7svQ7ImKPjJ8VKHfapCOKANilnX19dkD4fSaYYxpnY48ew= X-Received: by 10.202.175.207 with SMTP id y198mr20337414oie.213.1517341522577; Tue, 30 Jan 2018 11:45:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.13.9 with HTTP; Tue, 30 Jan 2018 11:44:42 -0800 (PST) From: Odhiambo Washington Date: Tue, 30 Jan 2018 22:44:42 +0300 Message-ID: Subject: Re: Strange Name Server Problem - SOLVED To: questions Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2018 19:45:25 -0000 On 20 April 2017 at 21:48, Odhiambo Washington wrote: > I have a server running FreeBSD 11.0-STABLE. > > I am a little stumped why my local caching bind instance doesn't answer > queries. I have then opted to run bind on port 5353 and unbound on port 53. > I still experience the same problem! > > root@waridi:/usr/local/etc/unbound # sockstat -l | grep named > bind named 50877 20 tcp4 192.168.27.254:5353 *:* > bind named 50877 21 tcp4 127.0.0.1:5353 *:* > bind named 50877 22 tcp4 127.0.0.1:953 *:* > bind named 50877 23 tcp6 ::1:953 *:* > bind named 50877 512 udp4 192.168.27.254:5353 *:* > bind named 50877 513 udp4 192.168.27.254:5353 *:* > bind named 50877 514 udp4 192.168.27.254:5353 *:* > bind named 50877 515 udp4 127.0.0.1:5353 *:* > bind named 50877 516 udp4 127.0.0.1:5353 *:* > bind named 50877 517 udp4 127.0.0.1:5353 *:* > root@waridi:/usr/local/etc/unbound # sockstat -l | grep unb > unbound unbound 51296 3 udp4 127.0.0.1:53 *:* > unbound unbound 51296 4 tcp4 127.0.0.1:53 *:* > unbound unbound 51296 5 udp4 192.168.27.254:53 *:* > unbound unbound 51296 6 tcp4 192.168.27.254:53 *:* > unbound unbound 51296 10 udp4 *:29712 *:* > unbound unbound 51296 11 udp4 *:28511 *:* > unbound unbound 51296 13 udp4 *:35511 *:* > unbound unbound 51296 14 udp4 *:19644 *:* > unbound unbound 51296 15 udp4 *:22549 *:* > unbound unbound 51296 16 udp4 *:30714 *:* > unbound unbound 51296 17 udp4 *:11907 *:* > unbound unbound 51296 18 udp4 *:50834 *:* > root@waridi:/usr/local/etc/unbound # > > Name resolution takes so long because it has to happen via the ISPs DNS > Servers, which are the 3rd and 4th options in /etc/resolv.conf > > I am actually lost as to where to start looking. > It turns out that bind was trying to resolve the names against IPv6 addresses. It's only today (20180130) that I figured this out by running nslookup and looking at what bind was logging. I installed bind-9.11 with IPv6 disabled and now my name lookups is fast! As I had wanted. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft." From owner-freebsd-questions@freebsd.org Tue Jan 30 21:11:25 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 04666EE364D for ; Tue, 30 Jan 2018 21:11:25 +0000 (UTC) (envelope-from kremels@kreme.com) Received: from mail.covisp.net (www.covisp.net [65.121.55.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 A62F081B9F for ; Tue, 30 Jan 2018 21:11:23 +0000 (UTC) (envelope-from kremels@kreme.com) From: "@lbutlr" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: [OT] sshguard list? Message-Id: <87638A7F-F265-460D-B68D-994F94FF1E2D@kreme.com> Date: Tue, 30 Jan 2018 14:11:21 -0700 To: Freebsd Questions X-Mailer: Apple Mail (2.3445.6.9) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2018 21:11:25 -0000 Is anyone here on the sshguard-users list? I tried to subscribe to it, = which resulted in an email directing me to a website = (https://lists.sourceforge.net/lists/listinfo/sshguard-users) which = resulted in nothing at all. From owner-freebsd-questions@freebsd.org Tue Jan 30 21:17:54 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4E305EE3C3E for ; Tue, 30 Jan 2018 21:17:54 +0000 (UTC) (envelope-from jungleboogie0@gmail.com) Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::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 DA4D581F88 for ; Tue, 30 Jan 2018 21:17:53 +0000 (UTC) (envelope-from jungleboogie0@gmail.com) Received: by mail-io0-x22d.google.com with SMTP id d13so13022186iog.5 for ; Tue, 30 Jan 2018 13:17:53 -0800 (PST) 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=+JXVbMp2A1RtXPsvMW/Zb/8FRFi7VpYDXGXLcG8bLTk=; b=HkY706da82L1LcqNb9gEH16jS/jh6n9HX7BGqo/QDPUMNRJ4UQmoJu+iSx6Gow9RXs f9y8+j9EOWoNlMbd9Kog7NuusvS74o3FXiJQ92fscKzz2fEnUih0QxHLYn6xjQ5QIbP0 wAxa/x2h9BEmCUEduKZHsk1QwY6xxGZobUkcjKqd6ke+SOonlxSnykhmIk3bqLQKjllG WavC1G0/IEjmnJ57J2W1atBihlk1jqvSeoHO8JGkTSp/nypagnSoyykAgiPz3kFhqbK4 X60cYEl4bjT1VwLixftyuEFWuhuV1MNXtDW4VE0XffaI6LPsk71OuY5CFnhWZDux12ym 8heA== 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=+JXVbMp2A1RtXPsvMW/Zb/8FRFi7VpYDXGXLcG8bLTk=; b=j5fb8T7k9P6Y7PwUDwB/P6PN73jXds+ji9o7geWjLh3bS1hCedlIvvXFAdx7ECsgT7 Q44SYA9ArkrUmDeGD6tAzXVSsJrA920YvKaak+g3uI5qtyWgggcTq/hlSaXiDo4YqNbJ BGp9q8A8SfrAnzSIV0J+GSL7D4ZpGTXUdmVr73C1HxBy7gC/ZhdMcFkVthTubP8wDHfW 7dgTmB08tjp6aj6qrs/RdQefznUd/FJZd5Ae8GZdTHa63hjvZ+d5z5xqxR1qNkp4IBgk uwXtHh54QE7EvAivU/7qU1F5B4h+Z7RvSAOz+EL0qokIDVfe5siYXOIvtXO6vBtVvWvB StVQ== X-Gm-Message-State: AKwxytdvxNFlb1z/XO5xURDjZEMKyyDyiGt/llMkUTV6kMlRZ6r6+zKy 5oSD2cuA4lFdBBrTxRPOPCKQjWfJW+lX1AuIahM= X-Google-Smtp-Source: AH8x226RnCeVzgsvgvp7K+9oN0ztGIsn2N+ab8Qx3QdTzUtV497RXC0Xm0zDE4sVBc40rhhuZ4KfvBEQydR7Z5IYqmQ= X-Received: by 10.107.170.148 with SMTP id g20mr31089150ioj.206.1517347073252; Tue, 30 Jan 2018 13:17:53 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.203.194 with HTTP; Tue, 30 Jan 2018 13:17:52 -0800 (PST) In-Reply-To: <87638A7F-F265-460D-B68D-994F94FF1E2D@kreme.com> References: <87638A7F-F265-460D-B68D-994F94FF1E2D@kreme.com> From: jungle Boogie Date: Tue, 30 Jan 2018 13:17:52 -0800 Message-ID: Subject: Re: [OT] sshguard list? To: "@lbutlr" Cc: Freebsd Questions Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2018 21:17:54 -0000 On 30 January 2018 at 13:11, @lbutlr wrote: > Is anyone here on the sshguard-users list? I tried to subscribe to it, which resulted in an email directing me to a website (https://lists.sourceforge.net/lists/listinfo/sshguard-users) which resulted in nothing at all. > At the bottom of the email: ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ sshguard-users mailing list sshguard-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sshguard-users -- ------- inum: 883510009027723 sip: jungleboogie@sip2sip.info From owner-freebsd-questions@freebsd.org Tue Jan 30 21:34:54 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5E9C1EE4ADD for ; Tue, 30 Jan 2018 21:34:54 +0000 (UTC) (envelope-from kremels@kreme.com) Received: from mail.covisp.net (www.covisp.net [65.121.55.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 0E62582DE0 for ; Tue, 30 Jan 2018 21:34:53 +0000 (UTC) (envelope-from kremels@kreme.com) From: "@lbutlr" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Re: sshguard list? Date: Tue, 30 Jan 2018 14:34:51 -0700 References: <87638A7F-F265-460D-B68D-994F94FF1E2D@kreme.com> To: Freebsd Questions In-Reply-To: Message-Id: <9BC33D4B-D3A1-4932-A9EB-A959FD55CB5B@kreme.com> X-Mailer: Apple Mail (2.3445.6.9) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2018 21:34:54 -0000 On 30 Jan 2018, at 14:17, jungle Boogie jungleboogie0@gmail.com> wrote: > At the bottom of the email: The confirmations were coming from an email address that didn't contain = sshguard (noreply@sourceforge.net) so they were no showing up in my = search for confirmation emails. Subscribe appears to have worked now. Thanks. --=20 Experience is something you don't get until just after you need it. From owner-freebsd-questions@freebsd.org Tue Jan 30 21:48:12 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 61935EB7C48 for ; Tue, 30 Jan 2018 21:48:12 +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 065FE839A9 for ; Tue, 30 Jan 2018 21:48:11 +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 833A7624A1 for ; Tue, 30 Jan 2018 16:48:05 -0500 (EST) 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 x51joktSK7TI for ; Tue, 30 Jan 2018 16:48:03 -0500 (EST) 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 3018262300 for ; Tue, 30 Jan 2018 16:48:01 -0500 (EST) Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Tue, 30 Jan 2018 16:48:01 -0500 Message-ID: <870deecf052d36d03aae9613410b38ba.squirrel@webmail.harte-lyne.ca> Date: Tue, 30 Jan 2018 16:48:01 -0500 Subject: LPD listen directive? From: "James B. Byrne" To: 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2018 21:48:12 -0000 Can lpd be configured such that it listens only on specific IP addresses? If so where and how is it done? We are running lpd and cups on the same host. Cups is configured to only listen on the loopback address. But lpd is listening on all available addresses. netstat -a | grep LISTEN tcp4 0 0 localhost.domain *.* LISTEN tcp6 0 0 localhost.domain *.* LISTEN tcp4 0 0 localhost.ssh *.* LISTEN tcp4 0 0 192.168.216.44.ssh *.* LISTEN tcp4 0 0 vhost04.ssh *.* LISTEN tcp4 0 0 vhost04.2222 *.* LISTEN tcp4 0 0 localhost.ftp-proxy *.* LISTEN tcp4 0 0 localhost.ipp *.* LISTEN tcp6 0 0 localhost.ipp *.* LISTEN tcp4 0 0 vhost04.smtp *.* LISTEN tcp4 0 0 localhost.smtp *.* LISTEN tcp4 0 0 *.printer *.* LISTEN tcp6 0 0 *.printer *.* LISTEN -- *** 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 Tue Jan 30 22:34:16 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85E23EC3AE4 for ; Tue, 30 Jan 2018 22:34:16 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from smtp9.server.rpi.edu (smtp9.server.rpi.edu [128.113.2.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "canit.localdomain", Issuer "canit.localdomain" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3269A85971 for ; Tue, 30 Jan 2018 22:34:15 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from smtp-auth1.server.rpi.edu (smtp-auth1.server.rpi.edu [128.113.2.231]) by smtp9.server.rpi.edu (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id w0UMYDWQ020364 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 30 Jan 2018 17:34:14 -0500 Received: from smtp-auth1.server.rpi.edu (localhost [127.0.0.1]) by smtp-auth1.server.rpi.edu (Postfix) with ESMTP id B45DB58019; Tue, 30 Jan 2018 17:34:13 -0500 (EST) Received: from [172.16.67.1] (gilead-qc124.netel.rpi.edu [128.113.124.17]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: drosih) by smtp-auth1.server.rpi.edu (Postfix) with ESMTPSA id A6FB458018; Tue, 30 Jan 2018 17:34:13 -0500 (EST) From: "Garance A Drosehn" To: byrnejb@harte-lyne.ca Cc: freebsd-questions@freebsd.org Subject: Re: LPD listen directive? Date: Tue, 30 Jan 2018 17:34:13 -0500 X-Mailer: MailMate (1.10r5443) Message-ID: <0F811690-40FD-45F6-AAD7-BD24E1016DFF@rpi.edu> In-Reply-To: <870deecf052d36d03aae9613410b38ba.squirrel@webmail.harte-lyne.ca> References: <870deecf052d36d03aae9613410b38ba.squirrel@webmail.harte-lyne.ca> MIME-Version: 1.0 X-Virus-Scanned: ClamAV using ClamSMTP X-Bayes-Prob: 0.0001 (Score 0, tokens from: outgoing, @@RPTN) X-Spam-Score: 0.00 () [Hold at 10.10] X-CanIt-Incident-Id: 02V4KydH9 X-CanIt-Geo: ip=128.113.124.17; country=US; region=New York; city=Troy; latitude=42.7495; longitude=-73.5951; http://maps.google.com/maps?q=42.7495,-73.5951&z=6 X-CanItPRO-Stream: outgoing X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.229 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2018 22:34:16 -0000 On 30 Jan 2018, at 16:48, James B. Byrne via freebsd-questions wrote: > Can lpd be configured such that it listens only on specific IP > addresses? If so where and how is it done? We are running lpd and > cups on the same host. Cups is configured to only listen on the > loopback address. But lpd is listening on all available addresses. > > netstat -a | grep LISTEN > tcp4 0 0 192.168.216.44.ssh *.* LISTEN > tcp4 0 0 localhost.ipp *.* LISTEN > tcp6 0 0 localhost.ipp *.* LISTEN > tcp4 0 0 *.printer *.* LISTEN > tcp6 0 0 *.printer *.* LISTEN The man page for 'lpd' describes a few options which might help you, depending on what you want. '-s' means that lpd won't be listening anywhere (however printing for all users on the localhost should still work fine). '-4' means it listens only on IPv4 addresses, and '-6' means it listens only on IPv6 addresses. Unless you're doing something odd, you would only need 'lpd' listening on localhost if you have printcap entries which point at rm=localhost . I haven't done much with CUPS, but IIRC it needs to be listening on localhost or printing doesn't work for anyone. -- Garance Alistair Drosehn = drosih@rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy, NY; USA From owner-freebsd-questions@freebsd.org Wed Jan 31 00:34:53 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CFC01ECC22B for ; Wed, 31 Jan 2018 00:34:53 +0000 (UTC) (envelope-from 14th.president@gmail.com) Received: from mail-ot0-x22f.google.com (mail-ot0-x22f.google.com [IPv6:2607:f8b0:4003:c0f::22f]) (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 6828269FCF for ; Wed, 31 Jan 2018 00:34:53 +0000 (UTC) (envelope-from 14th.president@gmail.com) Received: by mail-ot0-x22f.google.com with SMTP id q9so810086oti.0 for ; Tue, 30 Jan 2018 16:34:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=M8EF7Hgn8h8tH5WseB9d1GhktiYSlCzbUNTygO0oN8w=; b=t+QAo/My9yh70gEK1G21B+tE8tCEVfJ7hQWTmlBwOIEyK0BzNB0PIIb8/OzkgBs3Ja tzGxLZA2ZUx2et161M8nvI4rsXczkCJ9iZmfl3DgYCxhF0/GxsdeFDfDl/P9mFocixnq rwy7h0klbmY2YatbyEpRnOnrkCVFEHQCwhBDfvKTCcJDRDHsYLSXePWbOpG2WBICaIO5 XMOFusZzJun0lLfKNxXujyeoWXr9CbhF6pDrxq15DCZXOj1rPZ0j2nkLWnJDVh+ekebb wCp5ccIAjdDRMJ+mU09igNhMQbR8wMZhXfzG3yrNCCcGkDqk+JFIjO5gU5yvNLsjfbxN 6xaQ== 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:cc; bh=M8EF7Hgn8h8tH5WseB9d1GhktiYSlCzbUNTygO0oN8w=; b=MasOam2NtsCx8FEfXCGBn8M5mYANMAtLnwKf6sRN5XeS4md1Cwz6zSTlJA3o+RMczx O09FyHVIIk7LoynGm7TDvw4H0rCbBqv/RvIYlW/TeaDtKS1dCYNAtTgQsZQnswCBP1xh rSDrb8HvMfyLzJWaIhHAesm3N5gBXR9BCto2ymlw9w1dbr00LjWSq4x/sEYEW6C60GNn qElCben/UdwegcoAyBAAfS/o/4aJyhjzAxFWfK4JYJ57pxZlDoCiaGPcxY/XwRNvulTW bEI0MqvbxNiCgVXFlXewJ4c4d/kG0cNZYayeP4ZCCqDDgYz+NclhscPe8Q0EeSPxISNP Akhw== X-Gm-Message-State: AKwxytdym4/jNnoVRVcjHPz2qLdjOxt3Ux9E0q3kSUwhRz32IqkbAgE1 rPmLuKp2C1wtMasiPnJVXsN6UrYHc89lHEjJAI0= X-Google-Smtp-Source: AH8x226dNQ77abOoutV19cUBQ3NiKKqNd/UlnwINkoOIkvJC0v6d2Ls1QSGKIDPAlqZvcBylZTBMfow4/VUksCA4YgI= X-Received: by 10.157.48.148 with SMTP id s20mr4045343otc.218.1517358892537; Tue, 30 Jan 2018 16:34:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.46.29 with HTTP; Tue, 30 Jan 2018 16:34:52 -0800 (PST) From: "14th.president@gmail.com" <14th.president@gmail.com> Date: Tue, 30 Jan 2018 19:34:52 -0500 Message-ID: Subject: Re: Setting console resultion To: freebsd-questions@freebsd.org Cc: kremels@kreme.com Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 00:34:54 -0000 >> I'm not sure why this is so hard, but I've read dozens of pages >> and threads on setting up the console to boot into something >> other than VGA 80x24 and I can't get anything to change the >> resolution. On an ancient Core Duo laptop: /usr/src/sys/i386/conf/MYCUSTOMKERNEL: (note what's commented out) # device vga # options VESA device splash # syscons is the default console driver, resembling an SCO console # device sc # options SC_PIXEL_MODE # vt is the new video console driver device vt device vt_vga device agp # support several AGP chipsets /boot/loader.conf: (irrelevent lines omitted) cuse_load="YES" drm2_load="YES" acpi_video_load="YES" /etc/rc.conf: (again, rear elephant lines emitted) kld_list="i915kms" This autodetects the correct resolution halfway (or a bit more) through the boot sequence with a two or three sec- ond pause while the screen is blank and then gives a nearly un-readably small console font. I use the good ol' "startx" to start X, but I guess that's not relevant here. I have a similar setup on an older Xeon (amd64) that works pretty much exactly the same, though it runs headless most of the time. From owner-freebsd-questions@freebsd.org Wed Jan 31 00:49:45 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6E5CAECD268 for ; Wed, 31 Jan 2018 00:49:45 +0000 (UTC) (envelope-from jkerian@gmail.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::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 044476A85C for ; Wed, 31 Jan 2018 00:49:44 +0000 (UTC) (envelope-from jkerian@gmail.com) Received: by mail-it0-x233.google.com with SMTP id 196so2773837iti.5 for ; Tue, 30 Jan 2018 16:49:44 -0800 (PST) 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=l1hD9WMEAwqDlYe2R3A+Q7M0zKyfUbzJSEUYnuZsPJs=; b=uTn3qvVc6YhvVOa4G3ILeWaCUTGIBYadK+7zabRWZkMM5IZ5/qNU4emnG+2Lhv4k7u m45lBAsi/tCb8w5438EIfOT8mvYsbVhqxsyaAeZ7BrWG4Y8OOLT3qP3J35wTtnmZaKc4 zvBmJUJ1+AkpXRZm/AoPwGXh/kMkKQaxn2Qbpvqor4qlKko37v6SmQY1LdTulEgM2ns6 I8hjcBpfGtaby7zQrTe5RWA9fUzZUVGNkhPAlquXugqY6dOscnX+l8mzqonydu+ZR3D0 9SpWSEW7hicblJyejlg7eE/53snucpCyEA3r1dOrqf6RtlAAM7qvk9+TLH4gPWgJlLGl uYeg== 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=l1hD9WMEAwqDlYe2R3A+Q7M0zKyfUbzJSEUYnuZsPJs=; b=kkSUmDh1Y2GFydbVBohGj1vDRy5hCHsiX81stQjOiLZ4s2uHj+Rwo5iPBUFEd0yArl ZpjE/rt4n7WqKUBoYnCNqDG33Qd0j3BTxdM3AvPPV9K5G+F5juWJALiuNH+fRn53uLuP 0dKxE6EJK8Qo6a0eM7rMdUFoJK02K846bnNA/A7//kstHU1aI/17Gx2nuIibz+3VyHdL g4QRZjANdPiCoLS69xEOpDTkvflJuqADLymNSCoN3CfsH6c7PjjVS3Nbo38oAIPddyeg BHpA21wCmMtvLdLve07SU7IXIwKB7/0z6hrg/00fYjzLi8WQvb938U5ek+Qi4ay2FABQ eafA== X-Gm-Message-State: AKwxytc9uVzIMPafumycyagc2bjt8RyT/EgX3nqoGFCx0knaCqH/w5S5 vZjQezmFM0Q3RXo1RxirL90iNm/FRLblGmre2/Ljsw== X-Google-Smtp-Source: AH8x227da7zFDrQaqUqWWX+FH4JxTpz7qC4/FG168itcmYLtJE+6s+hTDK4RUy+IXcHhcHADXieyd/zT11A2mp28qZ4= X-Received: by 10.36.31.5 with SMTP id d5mr20592648itd.136.1517359783970; Tue, 30 Jan 2018 16:49:43 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.136.30 with HTTP; Tue, 30 Jan 2018 16:49:43 -0800 (PST) From: Joseph Kerian Date: Tue, 30 Jan 2018 18:49:43 -0600 Message-ID: Subject: FreeBSD iswprint() returns false for U+FF08 in UTF-8 locale To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 00:49:45 -0000 I recently searched one of my drives for files containing "unprintable characters" due to some issues I was seeing with file-listing programs. When I run ls -B on one of the files, the UTF-8 pattern 0xef 0xbc 0x88 appears to be the culprit. According to http://www.utf8-chartable.de/unicode-utf8-table.pl?start=65280&utf8=0x, this should be U+FF08 a fullwidth left parenthesis. This makes some sense, given the file. According to http://demo.icu-project.org/icu-bin/ubrowse?ch=FF08, U+FF08 should be a perfectly printable character in a UTF-8 locale. Looking at the ls.c source code eventually led me to iswprint(). I wrote the simple program to test print the character enums and then print iswprint() results in a few locales on a series of characters. https://wandbox.org/permlink/ZDc36tQhh7BLRpBx Linux and OSX have some odd behavior around the classes, but U+2002 and U+FF08 are both perfectly printable on both systems. On the other hand FreeBSD is only returning 1 for iswprint(0x64) Results from my box here here: https://gist.github.com/anonymous/0f21e139ae10c8c7996e7c056d686a7b, the results on that wandbox link are pretty typical for Linux systems. (My box is running: FreeBSD 11.1-RELEASE-p4 GENERIC amd64) Is this a bug? Am I missing a pkg/port to properly support UTF-8? -- -- Joe Kerian Email: jkerian@gmail.com From owner-freebsd-questions@freebsd.org Wed Jan 31 02:09:41 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BA710ED1B66 for ; Wed, 31 Jan 2018 02:09:41 +0000 (UTC) (envelope-from freebsd@pki2.com) Received: from btw.pki2.com (static-50-125-237-106.rdmd.wa.frontiernet.net [50.125.237.106]) (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 306136D5F5 for ; Wed, 31 Jan 2018 02:09:40 +0000 (UTC) (envelope-from freebsd@pki2.com) Received: from localhost (localhost [127.0.0.1]) by btw.pki2.com (8.15.2/8.15.2) with ESMTP id w0V1Zxuk049987 for ; Tue, 30 Jan 2018 17:35:59 -0800 (PST) (envelope-from freebsd@pki2.com) Message-ID: <1517362559.13652.1.camel@pki2.com> Subject: Where do I find ntpd configure options? From: Dennis Glatting To: freebsd-questions@freebsd.org Date: Tue, 30 Jan 2018 17:35:59 -0800 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.24.2 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-yoursite-MailScanner-Information: Please contact the ISP for more information X-yoursite-MailScanner-ID: w0V1Zxuk049987 X-yoursite-MailScanner: Found to be clean X-yoursite-MailScanner-From: freebsd@pki2.com X-Spam-Status: No X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 02:09:41 -0000 I am looking for the NTPD configuration (./configure) options used to compile NTPD in /usr/src. Where can I find them? From owner-freebsd-questions@freebsd.org Wed Jan 31 02:37:44 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2B274ED3370 for ; Wed, 31 Jan 2018 02:37:44 +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 C610F6E3AC for ; Wed, 31 Jan 2018 02:37:43 +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 BE87D623AD; Tue, 30 Jan 2018 21:37:41 -0500 (EST) 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 YKR3ZtAEmXU3; Tue, 30 Jan 2018 21:37:37 -0500 (EST) 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 3682E62300; Tue, 30 Jan 2018 21:37:37 -0500 (EST) Received: from 70.27.88.114 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Tue, 30 Jan 2018 21:37:37 -0500 Message-ID: <4747d314efd1614e211c557b469ad98f.squirrel@webmail.harte-lyne.ca> In-Reply-To: <0F811690-40FD-45F6-AAD7-BD24E1016DFF@rpi.edu> References: <870deecf052d36d03aae9613410b38ba.squirrel@webmail.harte-lyne.ca> <0F811690-40FD-45F6-AAD7-BD24E1016DFF@rpi.edu> Date: Tue, 30 Jan 2018 21:37:37 -0500 Subject: Re: LPD listen directive? From: "James B. Byrne" To: "Garance A Drosehn" 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 02:37:44 -0000 On Tue, January 30, 2018 17:34, Garance A Drosehn wrote: > On 30 Jan 2018, at 16:48, James B. Byrne via freebsd-questions wrote: > >> Can lpd be configured such that it listens only on specific IP >> addresses? If so where and how is it done? We are running lpd and >> cups on the same host. Cups is configured to only listen on the >> loopback address. But lpd is listening on all available addresses. >> >> netstat -a | grep LISTEN >> tcp4 0 0 192.168.216.44.ssh *.* >> LISTEN >> tcp4 0 0 localhost.ipp *.* >> LISTEN >> tcp6 0 0 localhost.ipp *.* >> LISTEN >> tcp4 0 0 *.printer *.* >> LISTEN >> tcp6 0 0 *.printer *.* >> LISTEN > > The man page for 'lpd' describes a few options which might help you, > depending on what you want. '-s' means that lpd won't be listening > anywhere (however printing for all users on the localhost should > still work fine). '-4' means it listens only on IPv4 addresses, > and '-6' means it listens only on IPv6 addresses. > > Unless you're doing something odd, you would only need 'lpd' > listening on localhost if you have printcap entries which point > at rm=localhost . I haven't done much with CUPS, but IIRC it > needs to be listening on localhost or printing doesn't work for > anyone. > It still remains for me to discover how exactly to configure those options. Lpd is enabled in rc.conf with lpd_enable="YES". Is there a variable like lpd_switches to see the command line options? If so, what is its name? And where might it be documented? -- *** 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 Jan 31 08:27:46 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 851DFEE29BA for ; Wed, 31 Jan 2018 08:27:46 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from relay2.tomsk.ru (mail.sibptus.tomsk.ru [212.73.124.5]) by mx1.freebsd.org (Postfix) with ESMTP id C79A2794FA for ; Wed, 31 Jan 2018 08:27:44 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) X-Virus-Scanned: by clamd daemon 0.98.5_1 for FreeBSD at relay2.tomsk.ru Received: from [212.73.125.240] (HELO admin.sibptus.transneft.ru) by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.16) with ESMTPS id 39925004 for freebsd-questions@freebsd.org; Wed, 31 Jan 2018 14:22:52 +0600 Received: from admin.sibptus.transneft.ru (sudakov@localhost [127.0.0.1]) by admin.sibptus.transneft.ru (8.15.2/8.15.2) with ESMTP id w0V8Rf5N046931 for ; Wed, 31 Jan 2018 15:27:41 +0700 (+07) (envelope-from vas@mpeks.tomsk.su) Received: (from sudakov@localhost) by admin.sibptus.transneft.ru (8.15.2/8.15.2/Submit) id w0V8Rck9046930 for freebsd-questions@freebsd.org; Wed, 31 Jan 2018 15:27:38 +0700 (+07) (envelope-from vas@mpeks.tomsk.su) X-Authentication-Warning: admin.sibptus.transneft.ru: sudakov set sender to vas@mpeks.tomsk.su using -f Date: Wed, 31 Jan 2018 15:27:38 +0700 From: Victor Sudakov To: freebsd-questions@freebsd.org Subject: Re: Dualboot and ZFS Message-ID: <20180131082738.GA46395@admin.sibptus.transneft.ru> References: <20180115051308.GA45168@admin.sibptus.transneft.ru> <20180115125241.GB60956@admin.sibptus.transneft.ru> <20180115144747.GA65526@admin.sibptus.transneft.ru> <20180115151526.GA66342@admin.sibptus.transneft.ru> <20180116034929.GB89443@admin.sibptus.transneft.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180116034929.GB89443@admin.sibptus.transneft.ru> Organization: AO "Svyaztransneft", SibPTUS X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 08:27:46 -0000 My pool works successfully in a bhyve environment, but in VirtualBox 5.0.14 (to test the real boot sequence) I get this message from zfsboot: zfsboot: No ZFS pools located, can't boot However, if I boot from LiveCD, the pool is there, it's healthy and can be imported. Why is it that zfsboot is not finding the pool? Is it because the pool has been created in /dev/ada0s1a instead of /dev/ada0s1 ? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN AS43859 From owner-freebsd-questions@freebsd.org Wed Jan 31 09:29:24 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 50DC3EE5258 for ; Wed, 31 Jan 2018 09:29:24 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A3B947B76C for ; Wed, 31 Jan 2018 09:29:23 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.213.55]) by mrelayeu.kundenserver.de (mreue006 [212.227.15.167]) with ESMTPA (Nemesis) id 0Mah5x-1eRCgz0mZF-00KCJL; Wed, 31 Jan 2018 10:29:12 +0100 Date: Wed, 31 Jan 2018 10:29:10 +0100 From: Polytropon To: "@lbutlr" Cc: freebsd-questions@freebsd.org Subject: Re: Setting console resultion Message-Id: <20180131102910.1f821ddd.freebsd@edvax.de> In-Reply-To: <6825E56C-1AA5-4B34-9221-28B987C321C9@kreme.com> References: <5919B7EF-A04A-47CD-AFE1-3B2290420AEF@kreme.com> <20180129154404.f1662f20.freebsd@edvax.de> <20180130123207.b7739451.freebsd@edvax.de> <6825E56C-1AA5-4B34-9221-28B987C321C9@kreme.com> 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=UTF-8 Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:B/0bujj4RlcK9ob9VgojLHGEHciuUN/FVDH3MKQXZe4eVvU/5B6 jDQE+yJQ1zTj9O9ZJMTnuIvoy8XUireAMWfWq3rTL19IP6FYlOT9/8Wt1psEgxxypBtCtxX O4HbAuqD1mB3aymTcyCnlieMDcswovV8WfPIjxkHYbBeA4oCIi/xUZ9dNmJH8pOFa6/akuE hCAuaHSo6HaXn1DQO0n1A== X-UI-Out-Filterresults: notjunk:1;V01:K0:fRpR3Xf/F1E=:16g+z/Wc5Px3s0jdxTuxi3 lk47Ftx7IzAR8gPYJmP2mDtCysp4MKbg01deu4jC5gzxlbljdaE6M/Ce18/sEOOLU/pwajLWR 1xvBos/dRmATxhDpy/oZUEwjxNMOQJLCg1mabzSsPdhy4B6pxrmg+QeTE6Y6jBkU2AnJFsRnx WCLs0JeGHE5oDvgDFWeNPjx0Hq5bKMc1RCa0HjHV6zlOV6KEtB/922p7hJYFYKAYoUfVgG3mj 8XWCyTKSFG63Ymj7zxqDzjIIn0kvWjh4A64f79p/pQmDbrzutypn4LF1rDQyMeoztju4xovZj 4bKn2kKSROqK14/dxxPYMtdO8PdvIhaNFeWUjD+AwUzscu6WbUWX/3yBytDrGYCSS4s22oGyY YjYmNij9eNYMl6YS6zUdrR+0sklq1bn5f2PJ4KsopQPfaa4sbkyoCB3L/zV4ucUQtZYdUzZ4/ Ki78k4fZAEbUp4a1hp7KJAPFuxYgHmvZ/cNRLrJui3SYYZcjqpDLYFInIMGtOg97zkEOdINYH PBcdppYo+0kUAuPsll8X2N2oqaV9I09vQGvATNW62RLWSdfh4aC5jVB6TJePyESjz95GOt+4I qDXYpJB/hgJlTPKHikSaby/jCnMUe+/N0Qq55gRk+iKgh1c2K6UOI6lqLSwlc/hkROeX/z3Ea rq3eE4qwwTzOLpgSRAwzlhL7/HBifsDK3zqR0+ND6dsxfkBdMzkorgGuYCwTZ4RQeULVmTRQ0 G7fAU3vtjkbRjsYHgIZQ4UehA7nqF2NgAj/dopwmCJFYTb+vD/PIJDhW1h8= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 09:29:24 -0000 On Tue, 30 Jan 2018 09:33:54 -0700, @lbutlr wrote: > I’ve seen gop mentioned a few times and I have no idea what it is, > or what a “loader command” is. Do you mean rebooting into the boot > loader on the initial pre-startup screen (multi user, single user, > etc?) A loader command is being issued inside the loader ("_the_ loader"), i. e., the thing with the "Ok" prompt (where you can load and unload kernels and modules). :-) See "man 8 loader" for details. At system reboot, escaping from the menu (I don't use it, so I don't know how), or simply pressing the space bar a few times will drop you to the loader prompt where the "gop list" command can be used, and a specific mode can be set for further booting. See the following thread for inspiration: https://forums.freebsd.org/threads/53150/ Note that the particular gop command won't be available on non-recent versions, like FreeBSD 10. Additionally: http://lme.postach.io/post/changing-console-resolution-in-freebsd-10-with-vt-4 (reference from above thread) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Wed Jan 31 09:35:28 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E85ECEE58F2 for ; Wed, 31 Jan 2018 09:35:27 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 466AC7BDFD for ; Wed, 31 Jan 2018 09:35:27 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.213.55]) by mrelayeu.kundenserver.de (mreue004 [212.227.15.167]) with ESMTPA (Nemesis) id 0MGmAP-1eTOXB2fhp-00DTcE; Wed, 31 Jan 2018 10:35:12 +0100 Date: Wed, 31 Jan 2018 10:35:11 +0100 From: Polytropon To: Dennis Glatting Cc: freebsd-questions@freebsd.org Subject: Re: Where do I find ntpd configure options? Message-Id: <20180131103511.290fed68.freebsd@edvax.de> In-Reply-To: <1517362559.13652.1.camel@pki2.com> References: <1517362559.13652.1.camel@pki2.com> 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-Provags-ID: V03:K0:bqbGMYHZuSIEndZpxrVBV53Nj6DV4VI97JFEtivkPBvcudaJ0x4 GMn8tQVpaWHXhZpTa0skeG0Vn7w862lUQIZOzEcF/iOwQywcTiGx+n8zg0aghh+SJvpiqKi 7FgKWNHASlkDKQWkyaC8/WIwkO17oJinDF2P/ePFC/Q4+ASbjd1wAhiG9D1TOTR0LNdwRkp KWWe3iG8odQ/kgrOABTlQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:UxC+3wX4Gog=:QPTN4c8TTB0PiYwkbZjlxW Rn7MgUM3Qw2XrVxkBoDBSXp1Ss7bsRiu93XvkV3pQt8Bw4ZWWPAQxsdRncXlmNiFxdUB5XILz gY4gY4QQidwv+HuPniLKHFGdPggwURtFCpep/yTbxPQlD4/5bqlUQZztNp2C0vH2wPGjaDP04 qagLjp2ZwKeJuPmLCBBJC6PQ9KlxfyBGT/PGMhj6OYqMgp6npVWOhMc3Z5OBVN1QWU8UuYovd 1v2pWLZcqvNCRFAYLWQ2qDvqBAS2hh2N74qET/BRhcYzi+HDfYNxvB1+dAt8A7FRe8Njkc5Q5 Rskl1ChmuqWkT2pf7K4itkVFBIkwXcWi4XRoyAj6geMcUYRgoEby4cjhlEg+DiylbPASj06yi K1WLlWpTfI62moFPP1Ne0ny2rr4zvXvxaF467K6iZ+cTEXhdqRU1I9WxLaGwci3IjGnMwx+r9 zp5MB25pz/8RtBlSpBsa1mhg11z854zZ+mtjTKMXt9wExKn4r0M2DyGLYgOR9hQBLLsqFjxRv fBVYpJolxwMTa7xO6UmOKPnTe1yUw0Kz/1U8VoW5lNqQ4Yl0xu/JqOcDPTtAoPngNK900Acr5 pi1kec76P6ihHxPJg4L3OMPav5Dhm7kwJpa8vz5nXF9V2InJ9j2bU4rgkAuiQHaFte5F9hZ95 QfDZmAMrXn0qiAb25P9DzwsDXlMoeveb/6Zq0fFe8dtTFsODS9n0PZNfvT8Y72TNkaO7Wn/Ws s4/7wsYYVMKa8QHXDmXeF6HEGhQe/N2gV5OwURqtBV4s8qKd8mA8WvKh+C0= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 09:35:28 -0000 On Tue, 30 Jan 2018 17:35:59 -0800, Dennis Glatting wrote: > I am looking for the NTPD configuration (./configure) options used to > compile NTPD in /usr/src. Where can I find them? The directory to interact with its Makefile is /usr/src/usr.sbin/ntp/ntpd from where you can "make install"; an individual ./configure step is not needed here. The code of ntpd is in /usr/src/contrib/ntp/ntpd. You can find the top level ./configure script for the whole ntp software package in /usr/src/contrib/ntp. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Wed Jan 31 09:46:31 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AC0BBEE60A6 for ; Wed, 31 Jan 2018 09:46:31 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 099107C3BF for ; Wed, 31 Jan 2018 09:46:30 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.213.55]) by mrelayeu.kundenserver.de (mreue002 [212.227.15.167]) with ESMTPA (Nemesis) id 0Mhqzr-1eL9UH3dqt-00MsL6; Wed, 31 Jan 2018 10:46:10 +0100 Date: Wed, 31 Jan 2018 10:46:08 +0100 From: Polytropon To: byrnejb@harte-lyne.ca Cc: "James B. Byrne via freebsd-questions" , "Garance A Drosehn" Subject: Re: LPD listen directive? Message-Id: <20180131104608.858e4a41.freebsd@edvax.de> In-Reply-To: <4747d314efd1614e211c557b469ad98f.squirrel@webmail.harte-lyne.ca> References: <870deecf052d36d03aae9613410b38ba.squirrel@webmail.harte-lyne.ca> <0F811690-40FD-45F6-AAD7-BD24E1016DFF@rpi.edu> <4747d314efd1614e211c557b469ad98f.squirrel@webmail.harte-lyne.ca> 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-Provags-ID: V03:K0:hF268D+jQZyUewkZG82LDr8i6ju7DHz9yuVN5Kh91UNV2mvepGl f0+N0ICiC2zEHV1RPRl+rl0lh2XD4CNcRCDeH0y1Rn3zk0QVpbVvo+4tK2+kiEQ4kjCGHw5 brXXj4U8xWIoh/SD6JCvp6abYgohGd0ZbP0fAv7Np+Hw+2vVGT4n3XX1mPwARejRmf1Zwo5 +veDlghNHsv/pBFplzTKg== X-UI-Out-Filterresults: notjunk:1;V01:K0:95/NVKL2/QI=:eyazpmsJGsNWueTbtwjv2K QlD9xFVKJXX8QhT+iXe8Vz6BQ+QFl+qm65GkTbQjzEko8T7QA8/eXE2NSMu4DwPzdphCjqXl+ Ii0jXPVJt9SgSR+FxA4w8TcvUcY0Qi7G6vVMgNXTFeIHW5Iezbt7wKyJ/zXqDTSu8ZbvxEPsB 7Bvz4bn4B7zQrA/v/5MXDZJlYBdxjqgdwCjTkXCdfKtUagiOdiNwjTi4hMT2sOf0KPwcZx00M 7RuVDHCaCWDPl787x/qRN62Yu54KpKZxNnc8GHaO4h8z7M1wif/LbJOY0fTqlvKqpLAbwHwrC a8za/UVPRNX2vW0aItLa3WJNslLuoiTE43ZnmA77x+7xx9aKrJfZpQtg3F8jhBDbQuR751Cvg M5b8nJKXowl+HhaaY41cSNS3Zm9ocArfrkESxh8CTlrpglTU2bnkCuiV1Bla/Iyayaa9fe71p nBMz/PqUFrnYH2GJc0VsIFrbKD41QWO9Rd2tyAUAblWuowmayGsfX+rQuxFCgJ1ukXsJokS2s hviNf81jRePiXe7opQkDMI8EE5xRVy3pD47XJQZOI3OrpXzpeUD//nfTIdVk7xITq2xlQr+MC wLOJypEGQ2pYOYne9nGy0qvADXhFDIAlWkNsti6JFaiQTIND9y70GaiegUNYtqOFjUsfZtX8k ISsDZqN5PlqoC53CJd8wlJQ+3LqHai4ExNJBV4QSV6izBzBEZ8naH4YxZBTx7f9kDK5uoQZ7b LsDhQr2pZIMzTOPabZaJCpLdn5kRePoMLuyCYbOCWYeC1J3EQR0x0qp8/vI= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 09:46:31 -0000 On Tue, 30 Jan 2018 21:37:37 -0500, James B. Byrne via freebsd-questions wrote: > It still remains for me to discover how exactly to configure those > options. Lpd is enabled in rc.conf with lpd_enable="YES". Is there a > variable like lpd_switches to see the command line options? If so, > what is its name? And where might it be documented? Check /etc/defaults/rc.conf and you'll discover those: lpd_enable="NO" # Run the line printer daemon. lpd_program="/usr/sbin/lpd" # path to lpd, if you want a different one. lpd_flags="" # Flags to lpd (if enabled). chkprintcap_enable="NO" # Run chkprintcap(8) before running lpd. See "man 8 lpd" for a list of options. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Wed Jan 31 10:57:43 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B5A5DEC3282 for ; Wed, 31 Jan 2018 10:57:43 +0000 (UTC) (envelope-from mary.johnson01@weboptimizes.com) Received: from mail-wr0-x242.google.com (mail-wr0-x242.google.com [IPv6:2a00:1450:400c:c0c::242]) (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 302657E657 for ; Wed, 31 Jan 2018 10:57:43 +0000 (UTC) (envelope-from mary.johnson01@weboptimizes.com) Received: by mail-wr0-x242.google.com with SMTP id v31so14447041wrc.11 for ; Wed, 31 Jan 2018 02:57:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=weboptimizes.com; s=google; h=mime-version:sender:from:date:message-id:subject:to; bh=F8LiUEldoY0DqVoU/85jD7nD0IRfUQyEvbFnXJqKyvM=; b=EMzCVx0ddvJI17B+uq5sJUL7R0kMkkvWbNDjyvc6s813SF0NCKhncL2LXlJaAgsZn5 0UgoIhnOjwMy01G8wPtYpUIM+7TICdD2iaWOL3qJaU1r2L9T4e2U8/oqSSPCby0P75z+ rZUcvzmNFoVRs70SeZbiGdbLru0DAvCwyOiuQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=F8LiUEldoY0DqVoU/85jD7nD0IRfUQyEvbFnXJqKyvM=; b=gOmdeeR+EbGHhYi00J+eQYGxNkf/Z4RQ97u8wZo0UjC9ne0hDmk43+ftgKI/EI+h0h q1kfR1oD1ZClj/NOO0ewfCspHhKfQ4OOVoULFsiAKs0N85wzlJEikj4GbEsDPBwS4WH7 D6PPCU2Zy9BamVMa6B83k52QaKt8zS+yfKNBTBN1InIwdMNlp/JezgxyQNVqlWZH/x93 ZJjXxUyqCPGuOmRmtWQg1MpzH/KGvb28ErRciYmRV1p/PDOd6+zOP8KEazvsTyjW90Rm ZPvKgk5Uv2KMcgIGms/3ocb+JHBnrJ6Eg/QNQkwcTtoOssR7yaNYk7CGjAQpABDCKx/a FSeA== X-Gm-Message-State: AKwxytfX8Z5sCZENBlvGzRJ0DihMrrcpyBg++7Eb7fwX102zYGP2utbP oHig+2aA/is0j++B8it7R7EWsrFJjzNTgY+usMBfJg== X-Google-Smtp-Source: AH8x226GGCqpKETDLmOhbOeG9LqT0p0kV6KIDoo7DAZ6gXgjjFMr1r5HXZbl9120PXeZCShLPtDK2Ku2vPRbmiykfEU= X-Received: by 10.223.172.168 with SMTP id o37mr18360101wrc.268.1517396261781; Wed, 31 Jan 2018 02:57:41 -0800 (PST) Received: from 52669349336 named unknown by gmailapi.google.com with HTTPREST; Wed, 31 Jan 2018 05:57:40 -0500 MIME-Version: 1.0 Sender: Mary Johnson From: Mary Johnson Date: Wed, 31 Jan 2018 05:57:40 -0500 X-Google-Sender-Auth: bOb3NufGRPlwpmMg7Gw6dm8Q1RQ Message-ID: Subject: Corporate MAKEUP for your BUSINESS WEBSITE To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 10:57:43 -0000 Hi *freebsd.org *, *Are you looking for a reliable, creative and experience team for the web designing or redesigning of your website???* AS we know *freebsd.org *is the reflection of your business, Do you want to put your business model and creative ideas in the design of your website? We will match your business goal with our creative ideas. We are one of the reputed companies with finely crafted creative and strategic designers and develop an SEO friendly website to give meaning to your Online business. We have innovative web solutions for organizations including *Advanced Database Interactivity* *& database design, e-commerce solutions, Flash design*, *HTML/D-HTML**, **Programming in PHP, ASP.Net**, **Logo Designing, Mobile/Tab Responsive Design. **with programming* etc. *Problems with your original site:1. You can=E2=80=99t control your site or= change content2. Search engines can=E2=80=99t find you3. Your site has outdated technology4. Out dated looking5. No call to action6. Slow load times7. No Dynamic content* So if you are *interested* we want to *Design and Develop your website* with Latest *newly added features* that might benefit the overall usability and user experience which usually leads to better sales! We could lower that cost and not compromise on quality! *Waiting for your positive reply!* Kind Regards *Mary Johnson* Sr. web consultant. [image: beacon] From owner-freebsd-questions@freebsd.org Wed Jan 31 11:07:29 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 54132EC39EB for ; Wed, 31 Jan 2018 11:07: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 D7D5E7EB21 for ; Wed, 31 Jan 2018 11:07: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 w0VAqcFY039337; Wed, 31 Jan 2018 10:52:38 GMT (envelope-from freebsd@qeng-ho.org) Subject: Re: LPD listen directive? To: byrnejb@harte-lyne.ca, freebsd-questions@freebsd.org References: <870deecf052d36d03aae9613410b38ba.squirrel@webmail.harte-lyne.ca> From: Arthur Chance Message-ID: <8109ee79-2871-67bc-4279-36ed9fe5a36b@qeng-ho.org> Date: Wed, 31 Jan 2018 10:52:38 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <870deecf052d36d03aae9613410b38ba.squirrel@webmail.harte-lyne.ca> 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 11:07:29 -0000 On 30/01/2018 21:48, James B. Byrne via freebsd-questions wrote: > Can lpd be configured such that it listens only on specific IP > addresses? If so where and how is it done? We are running lpd and > cups on the same host. Cups is configured to only listen on the > loopback address. But lpd is listening on all available addresses. > > netstat -a | grep LISTEN > tcp4 0 0 localhost.domain *.* LISTEN > tcp6 0 0 localhost.domain *.* LISTEN > tcp4 0 0 localhost.ssh *.* LISTEN > tcp4 0 0 192.168.216.44.ssh *.* LISTEN > tcp4 0 0 vhost04.ssh *.* LISTEN > tcp4 0 0 vhost04.2222 *.* LISTEN > tcp4 0 0 localhost.ftp-proxy *.* LISTEN > tcp4 0 0 localhost.ipp *.* LISTEN > tcp6 0 0 localhost.ipp *.* LISTEN > tcp4 0 0 vhost04.smtp *.* LISTEN > tcp4 0 0 localhost.smtp *.* LISTEN > tcp4 0 0 *.printer *.* LISTEN > tcp6 0 0 *.printer *.* LISTEN > Quick hint: sockstat -l is (IMO) a better way to show what listening sockets are open. I haven't actually tried this, so can't guarantee it's totally correct, but in theory you can use jail(8) to lock any program down to one address. I believe a command like jail path=/ ip4.addr=1.2.3.4 ip6=disable cmd ... would run cmd with only the IPv4 address 1.2.3.4 usable and IPv6 locked out totally. The path=/ bit sets the root of the jail to see the full file system as normal. Using this with an /etc/rc.d/* service files would probably require tweaking the shutdown command to kill the relevant jail. -- An amusing coincidence: log2(58) = 5.858 (to 0.0003% accuracy). From owner-freebsd-questions@freebsd.org Wed Jan 31 14:25:03 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3CBDDECE38E for ; Wed, 31 Jan 2018 14:25:03 +0000 (UTC) (envelope-from johannes-maria@t-online.de) Received: from mailout01.t-online.de (mailout01.t-online.de [194.25.134.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C12CA85FA4 for ; Wed, 31 Jan 2018 14:25:02 +0000 (UTC) (envelope-from johannes-maria@t-online.de) Received: from fwd39.aul.t-online.de (fwd39.aul.t-online.de [172.20.27.138]) by mailout01.t-online.de (Postfix) with SMTP id 495A1433FFEE for ; Wed, 31 Jan 2018 15:24:55 +0100 (CET) Received: from t-online.de (rP1y-QZbYhn6oI-385WEvHGCJ43vtrTPZX7ZU6FJA5RXYCDJnKxrBBTMC193ThXwQ4@[84.145.230.15]) by fwd39.t-online.de with (TLSv1:DHE-RSA-AES256-SHA encrypted) esmtp id 1egtJj-1pJnaC0; Wed, 31 Jan 2018 15:24:51 +0100 Received: by t-online.de (nbSMTP-1.00) for uid 1001 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-SHA (256/256 bits)) johannes-maria@t-online.de; Wed, 31 Jan 2018 15:24:51 +0100 (CET) Date: Wed, 31 Jan 2018 15:24:50 +0100 From: johannes-maria@t-online.de To: freebsd-questions@freebsd.org Subject: Re: problem with upgrade and unable to build openjdk8 in poudriere Message-ID: <20180131142450.GA30798@localhost.org> References: <20180115151549.GA9923@localhost.org> <20180128130433.GA2196@localhost.org> <20180129202145.GA2773@localhost.org> <9043f574-25d7-12f7-e219-e37bbefbde8c@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9043f574-25d7-12f7-e219-e37bbefbde8c@FreeBSD.org> User-Agent: Mutt/1.4.2.3i X-ID: rP1y-QZbYhn6oI-385WEvHGCJ43vtrTPZX7ZU6FJA5RXYCDJnKxrBBTMC193ThXwQ4 X-TOI-MSGID: 8a84bd78-eadd-4381-949a-700bff69f306 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 14:25:03 -0000 On Tue, Jan 30, 2018 at 12:04:08AM +0000, Matthew Seaman wrote: 1. > >> I can't really give you much help with this: openjdk8 is building just > >> fine for me on 11.1-RELEASE. This is probably some small configuration > >> mistake that will have you face-palming once you find it... > > > > did you built it in the ports or with poudriere? > > I'm building it with poudriere thanks for the info. I've not yet found the cause; configuration in ports and poudriere are both the default ones and whereas the 'make' in the ports runs without an error with poudriere it stops reproducible with | =>> Failed ports: java/openjdk8:build | [excerpt from the log-file: | gmake[2]: *** No rule to make target '1'. Stop. | gmake[2]: Leaving directory | '/wrkdirs/usr/ports/java/openjdk8/work/openjdk/langtools/make 2. > Yes, that looks about right. The '11amd64-default' part is the > combination of the poudriere jail name and the ports tree used to build > those packages. pkg(8) should work fine with a file:// URL, but > obviously that only works to install packages on the same machine where > you run poudriere. that's OK with me, I'm only upgrading on this one machine. > Well, try updating your ports tree (poudriere ports -u) and then running > a poudriere bulk to update any outdated packages. Then try 'pkg > upgrade' again. Chances are something will have an update available. thanks for the hints. I updated the ports tree and started poudriere with my list of ports to install (115; already installed is only the base system 11.1 from the boot CD + poudriere). Due to dependencies the first poudriere run (some weeks ago) tried to build approximately 1000 ports (all but 1 failed, 4 skipped). After the ports tree update: Queued: 584. It is not yet finished (Built: 369, Failed: 1, Skipped: 4, Ignored: 0, Tobuild: 210), but after more than 26 hours (degree of parallelism: 4, old computer) I didn't want to wait until tomorrow and give you at least a provisional result: with pkg upgrade I still see | Updating FreeBSD repository catalogue... | FreeBSD repository is up to date. | All repositories are up to date. | Checking for upgrades (123 candidates): .......... done | Processing candidates (123 candidates): . done | Checking integrity... done (0 conflicting) | Your packages are up to date. I don't know the origin of the '123 candidates'; my list of ports to install has 115 entries and the actual list poudriere is handling is much longer due to dependencies. Do I have so specify the repository created by poudriere explicitly? I thought that the entry | FreeBSD: { | url: "file:///usr/local/poudriere/data/packages/11amd64-default/", | ... in /usr/local/etc/pkg/repos/FreeBSD.conf was enough. Best regards, Johannes-Maria From owner-freebsd-questions@freebsd.org Wed Jan 31 15:09:45 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2048CED055F for ; Wed, 31 Jan 2018 15:09:45 +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 B975287D45 for ; Wed, 31 Jan 2018 15:09:44 +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 69DFE6235B; Wed, 31 Jan 2018 10:09:43 -0500 (EST) 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 YtOEP3WvbZcv; Wed, 31 Jan 2018 10:09:39 -0500 (EST) 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 EB0396235A; Wed, 31 Jan 2018 10:09:37 -0500 (EST) Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Wed, 31 Jan 2018 10:09:38 -0500 Message-ID: <9e6a89f6ac654b113372b3f8b736061a.squirrel@webmail.harte-lyne.ca> In-Reply-To: <20180131104608.858e4a41.freebsd@edvax.de> References: <870deecf052d36d03aae9613410b38ba.squirrel@webmail.harte-lyne.ca> <0F811690-40FD-45F6-AAD7-BD24E1016DFF@rpi.edu> <4747d314efd1614e211c557b469ad98f.squirrel@webmail.harte-lyne.ca> <20180131104608.858e4a41.freebsd@edvax.de> Date: Wed, 31 Jan 2018 10:09:38 -0500 Subject: Re: LPD listen directive? From: "James B. Byrne" To: "Polytropon" Cc: "James B. Byrne via freebsd-questions" , "Garance A Drosehn" 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 15:09:45 -0000 On Wed, January 31, 2018 04:46, Polytropon wrote: > Check /etc/defaults/rc.conf and you'll discover those: > > lpd_enable="NO" # Run the line printer daemon. > lpd_program="/usr/sbin/lpd" # path to lpd, if you want a different > one. > lpd_flags="" # Flags to lpd (if enabled). > chkprintcap_enable="NO" # Run chkprintcap(8) before running lpd. > Thank you. It would not have occurred to me to look in/etc/defaults/ > See "man 8 lpd" for a list of options. I did that, several times, before posting. I infer that the thing to do in this case is to set lpd_flags="-s". Thank you for the help. Regards, -- *** 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 Jan 31 15:37:35 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 201B2ED1EB2 for ; Wed, 31 Jan 2018 15:37:35 +0000 (UTC) (envelope-from cara.john@globaletradsz.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 9DB5369179 for ; Wed, 31 Jan 2018 15:37:34 +0000 (UTC) (envelope-from cara.john@globaletradsz.com) Received: by mailman.ysv.freebsd.org (Postfix) id 5C4CDED1EB1; Wed, 31 Jan 2018 15:37:34 +0000 (UTC) Delivered-To: questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 37B3AED1EAC for ; Wed, 31 Jan 2018 15:37:34 +0000 (UTC) (envelope-from cara.john@globaletradsz.com) Received: from homiemail-a116.g.dreamhost.com (sub5.mail.dreamhost.com [208.113.200.129]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C67C669178 for ; Wed, 31 Jan 2018 15:37:33 +0000 (UTC) (envelope-from cara.john@globaletradsz.com) Received: from homiemail-a116.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a116.g.dreamhost.com (Postfix) with ESMTP id 110F960001344 for ; Wed, 31 Jan 2018 07:37:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=globaletradsz.com; h=from :to:references:in-reply-to:subject:date:message-id:mime-version :content-type; s=globaletradsz.com; bh=UPsuQFHHuYnjcyDBEY/zQrJIO cE=; b=DpZPBHh/I9kSwF51t6I5G0wiuba0aiGetqq53heYHp2lBip5Hen7m5HDy /D1wvBCmU+o9lvPD7Wt6V7D2tZyqjzl8vXLJPrpoKyRVOM16RKmLzpgn8cTAOh5H QqDYe4EejWU/0VFjhvGA8ojz/rp3E+nI+aigzMHp106TWHh0/Y= Received: from NESS05PC (unknown [157.49.173.55]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: cara.john@globaletradsz.com) by homiemail-a116.g.dreamhost.com (Postfix) with ESMTPSA id 0161C60001341 for ; Wed, 31 Jan 2018 07:37:24 -0800 (PST) From: "Cara John" To: References: In-Reply-To: Subject: RE: WWETT Attendees Email List 2018 Date: Wed, 31 Jan 2018 10:36:40 -0500 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdOJmR8X+X8BSYg8QzugZi2eUyis5gAABpOAArgblaAAAA6lUAAASqeAAAAY2aAAAAAQYAAAB5eAAAATA/AAAAAJ8AAAAAjQAAAPK4AAAAAJEAAAAAdgAAAABhAAAAAIQAAAAydQAAApW4AAAAAKQAAANuWgAAAVcZAAAAICMAABYq8wAABIR5AAAE2NAAAAHiMAAAAxvnAAAAAKYAAAAAkAAAAABzAAACyL8AAABdTQAAAACRAAAAAIoAAADfFwAAAsLwAAAAAJkAAAAAhgAAADy1AAAAN2IAAALAJwAAANM9AAAAP5cAACAusAAADFstAAIExWQAAAC7ZgAABIUsAAACrfsAAAAAkQAAAEulAAABDh4AAAAAhQAAAAB7AAAAAI4AAAAAdAAAAAB6AAAAAHEAAAAAigAAAABzAAAAAIoAAAAAcwAWQqBwA= Content-Language: en-in Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 15:37:35 -0000 =20 =20 Hi, =20 I hope you=92re doing well. =20 I was wondering if you had a chance to review my previous email that I = sent to you. =20 Kindly let me know your interest so that I can get back to you with = counts and pricing available. =20 Best Regards, Cara =20 From: Cara John [mailto:cara.john@globaletradsz.com]=20 Sent: 24 January 2018 08:39 To: 'questions@FreeBSD.org' Subject: WWETT Attendees Email List 2018 =20 Hi, =20 Would you be interested in acquiring Water & Wastewater Equipment, = Treatment & Transport Attendees Email List 2018 for pre-show marketing campaign, Networking and various Marketing initiatives. =20 List includes E-mail address and Contact number on an excel spread = sheet. =20 Visitors Interest : =20 =D8 Municipal water & sewer management =D8 Septic pumping and maintenance =D8 Sewer contractors, installers, and cleaners =D8 Septic installation and repair =D8 Portable restroom service =D8 Plumbing & drain cleaning =D8 Relining, rehabbing and bursting =D8 Water blasting =D8 Treatment plant operators =20 If you are interested please let me know so that I can get back to you = with the number of counts we have and pricing for the same. =20 Regards, Cara John Business Development Executive =20 If you do not wish to receive future emails from us, please reply as = 'Leave out' From owner-freebsd-questions@freebsd.org Wed Jan 31 17:39:56 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E9589ED8927 for ; Wed, 31 Jan 2018 17:39:55 +0000 (UTC) (envelope-from koue@chaosophia.net) Received: from chaosophia.net (chaosophia.net [91.121.173.144]) (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 7965F6FF7C for ; Wed, 31 Jan 2018 17:39:55 +0000 (UTC) (envelope-from koue@chaosophia.net) Received: from chaosophia.net (localhost [127.0.0.1]) by chaosophia.net (8.15.2/8.15.2) with ESMTP id w0VHdfDG074411 for ; Wed, 31 Jan 2018 18:39:41 +0100 (CET) (envelope-from koue@chaosophia.net) Received: (from _prayer@localhost) by chaosophia.net (8.15.2/8.15.2/Submit) id w0VHdf5Q074410 for freebsd-questions@freebsd.org; Wed, 31 Jan 2018 18:39:41 +0100 (CET) (envelope-from koue@chaosophia.net) Received: from [194.97.158.70] by chaosophia.net with HTTP (Prayer-1.3.5); 31 Jan 2018 18:39:40 +0100 Date: 31 Jan 2018 18:39:40 +0100 From: Nikola Kolev To: freebsd-questions@freebsd.org Subject: bsd.lib.mk LIBDIR Message-ID: X-Mailer: Prayer v1.3.5 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=ISO-8859-1 X-Spam-Status: No, score=-1.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, SURBL_BLOCKED,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on chaosophia.net X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 17:39:56 -0000 Howdy, I'm dealing with bsd.lib.mk and if 'LIBDIR' is defined in the Makefile file it's not handled properly. # cat Makefile LIB= test CFLAGS+= -Wall -Wstrict-prototypes SRCS= test.c NO_OBJ= yes .include # make cc -O2 -pipe -Wall -Wstrict-prototypes -DNDEBUG -std=gnu99 -Qunused-arguments -c test.c -o test.o building static test library ranlib -D libtest.a # make install install -C -o root -g wheel -m 444 libtest.a /usr/lib # ls -la /usr/lib/libtest.a -r--r--r-- 1 root wheel 1398 Jan 31 18:23 /usr/lib/libtest.a If 'LIBDIR' is defined the library file is installed as '${LIBDIR}' not in '${LIBDIR}' # cat Makefile LIB= test CFLAGS+= -Wall -Wstrict-prototypes SRCS= test.c NO_OBJ= yes LIBDIR= /usr/lib/mylibz .include # make cc -O2 -pipe -Wall -Wstrict-prototypes -DNDEBUG -std=gnu99 -Qunused-arguments -c test.c -o test.o building static test library ranlib -D libtest.a # make install install -C -o root -g wheel -m 444 libtest.a /usr/lib/mylibz # ls -la /usr/lib/mylibz -r--r--r-- 1 root wheel 1398 Jan 31 18:24 /usr/lib/mylibz According to /usr/share/mk/bsd.README: LIBDIR Target directory for libraries. Instead of install the library file as '${LIBDIR}' 'make' should complain if the directory is missing or try to create it and then install the library file in it. Did I miss something? Thanks, Nikola -- Nikola Kolev koue@chaosophia.net https://github.com/koue/ From owner-freebsd-questions@freebsd.org Wed Jan 31 20:45:30 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BF2E3EE0BCA for ; Wed, 31 Jan 2018 20:45:30 +0000 (UTC) (envelope-from Abderrahmane.Zahrir@ca.com) Received: from mx0a-001c7801.pphosted.com (mx0a-001c7801.pphosted.com [148.163.156.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.pphosted.com", Issuer "thawte SHA256 SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3DE2D775EF for ; Wed, 31 Jan 2018 20:45:29 +0000 (UTC) (envelope-from Abderrahmane.Zahrir@ca.com) Received: from pps.filterd (m0082002.ppops.net [127.0.0.1]) by mx0a-001c7801.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id w0VKDbd6001901 for ; Wed, 31 Jan 2018 15:13:40 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ca.com; h=from : to : subject : date : message-id : content-type : mime-version; s=20151012; bh=8F2pC4ImVMm/ZUtiKHzQvaACavdNlehoMI/dr/MzIqo=; b=Pb7XmZpENA6Ol2qeEHwofKbLKKHM4buOsPjFuTLuTtl1fe0CyhNu+yfdbc2Z9scCuSeI EIpZvaDLYx/jHyp6RRp+L0dT/FLRbfH7zGTJ5S/x6CNyqWThLpC20ItNKzTULiNxJ06U VdwtUAxNSIHnzxgaQnqS5oxNk7cb0WbsuciwQcrhtydpJAPAzufmAXvSLzjslr6bjDfi sdNW4bNOoVBr7nYEC022Z360hFNsnQ0Oxjbr/Qm6CHmCY1zZeNLgoxbzSu3rWKMxnjMP SnjgcyoYDmqf57ikmUO/7xfbf3tA9pfiQHLgcbYxnxryMvEM8hF/v7INfvIBnkE3/Qwk KQ== Received: from usilms290.ca.com ([141.202.246.44]) by mx0a-001c7801.pphosted.com with ESMTP id 2fum6mr2um-3 (version=TLSv1.2 cipher=AES128-SHA bits=128 verify=FAIL) for ; Wed, 31 Jan 2018 15:13:39 -0500 Received: from usilms214.ca.com (141.202.6.104) by usilms290.ca.com (141.202.246.44) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Wed, 31 Jan 2018 15:13:30 -0500 Received: from usilms214.ca.com (141.202.6.104) by usilms214.ca.com (141.202.6.104) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Wed, 31 Jan 2018 15:13:29 -0500 Received: from usilms291.ca.com (141.202.246.45) by usilms214.ca.com (141.202.6.104) with Microsoft SMTP Server (TLS) id 15.0.1347.2 via Frontend Transport; Wed, 31 Jan 2018 15:13:29 -0500 Received: from NAM02-CY1-obe.outbound.protection.outlook.com (207.46.163.53) by o365smtp.ca.com (141.202.246.45) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Wed, 31 Jan 2018 15:13:27 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ca.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=8F2pC4ImVMm/ZUtiKHzQvaACavdNlehoMI/dr/MzIqo=; b=CVwlusEFRC4kelz+Hvck4cMFPWB0fshvHpaHAZP4RgC/XbW+wcHH/I6lg/cOVT99ABoj0oyYsTEISpgqfn2ZZjNDk6G0hGYRsPIyWTifHLNJ1qqDvb5TR2RRn+zjPj5jPP0kryy38UurCgOfYnuFhi7KaUwhto7WlschEDjiiMk= Received: from CY1PR01MB1247.prod.exchangelabs.com (10.163.17.29) by CY1PR01MB2155.prod.exchangelabs.com (10.166.206.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.444.14; Wed, 31 Jan 2018 20:13:25 +0000 Received: from CY1PR01MB1247.prod.exchangelabs.com ([10.163.17.29]) by CY1PR01MB1247.prod.exchangelabs.com ([10.163.17.29]) with mapi id 15.20.0444.016; Wed, 31 Jan 2018 20:13:24 +0000 From: "Zahrir, Abderrahmane" To: "freebsd-questions@FreeBSD.org" Subject: RE: Re: Response to Meltdown and Spectre Thread-Topic: Re: Response to Meltdown and Spectre Thread-Index: AdOLkQI0JmSCRlohTrWavodA9QvhKwO4+i1gABa9OKA= Date: Wed, 31 Jan 2018 20:13:24 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [194.75.229.113] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; CY1PR01MB2155; 7:JY0LH7EKay3lTW2wBehMer7MpnxMC9+NNrF4Fc2Lmww9rYo4jBOIIJCd0fIz+NsHbdd0di2loyD/KzLJLL7tTvSZbHgkhaEMJtt75hyb75ZuSms1oBvG435V0mLN5uKryzOh39MNfMwy7V5dttITk9fmXUjZKuA7atLyqFsUA1NnxlwC5ezvDh5tTP/wXRcIDceN7c8N1yd9rscuZ4g9Z8Wy/Cw7agDK7sTJYvbl+hjaGVKBo/F2rUMzv7jAT3rS; 20:SBuhs4a6+HmRA9y3GknOo4YVsdtuvZFj6QfxG1zIMVG/Q1Ta02VoWZ4VjkKgoxbAP1RL5Hfvqv1h0YfnbBU6exxaEwPCcrrRXP6C4AZ1LkJOwczxSHLDMb/ToiXlZQJRRr8JrOF1accfyyUy8ZuwYvIp3J3fxlESXloNz16vndszl+Y2lsgi4+6UwBDLFL2kzeF0yEkAs31jw/qTKkpKNApy4TywsOb5jd28dhctdk+anD8GVHKbiw/HlFNzeAK+ x-ms-exchange-antispam-srfa-diagnostics: SSOS; x-ms-office365-filtering-correlation-id: ad50437f-cb58-4fa8-cf87-08d568e71577 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:CY1PR01MB2155; x-ms-traffictypediagnostic: CY1PR01MB2155: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(28532068793085)(192374486261705)(21748063052155); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(5005006)(8121501046)(93006095)(93001095)(3231101)(2400082)(944501161)(3002001)(10201501046)(6041288)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123562045)(20161123558120)(6072148)(201708071742011); SRVR:CY1PR01MB2155; BCL:0; PCL:0; RULEID:; SRVR:CY1PR01MB2155; x-forefront-prvs: 056929CBB8 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(39860400002)(346002)(396003)(366004)(39380400002)(189003)(199004)(6306002)(99286004)(54896002)(97736004)(2501003)(14454004)(558084003)(72206003)(66066001)(33656002)(105586002)(478600001)(86362001)(106356001)(68736007)(9686003)(2351001)(8676002)(9326002)(316002)(6246003)(790700001)(7696005)(6506007)(59450400001)(53936002)(3846002)(2900100001)(74316002)(8936002)(186003)(6116002)(81166006)(6436002)(3660700001)(6916009)(2906002)(229853002)(25786009)(5640700003)(10090500001)(3280700002)(5660300001)(77096007)(81156014)(5630700001)(26005)(55016002)(102836004)(7736002); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR01MB2155; H:CY1PR01MB1247.prod.exchangelabs.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: ca.com does not designate permitted sender hosts) x-microsoft-antispam-message-info: +6bamy+56QvYtkdUVXHV50+q5/QRD/AWT5YzO29s7/U6xzQgPBlrYFvuc6D6zRKMTtcQERwkx6/3XFoLerm2zw== spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: ad50437f-cb58-4fa8-cf87-08d568e71577 X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Jan 2018 20:13:24.8606 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 1194df16-3ae0-49aa-b48b-5c4da6e13689 X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR01MB2155 X-WgnSS: 01000000010010usilms291.ca.com ID004C X-OriginatorOrg: ca.com X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-01-31_10:, , signatures=0 X-Proofpoint-Outbound-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=479 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1801310252 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 20:45:31 -0000 Hi Guys, I understand that you have not been notified early enough about the Meltdow= n and spectre security flow. However do we have a rough estimate (something like an approximate month) o= f when a patch will be available for the latest version 11.1 and possibly 1= 1.0? Regards, Dahman From owner-freebsd-questions@freebsd.org Wed Jan 31 20:59:37 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EB71FEE14C3 for ; Wed, 31 Jan 2018 20:59:36 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from kicp.uchicago.edu (kicp.uchicago.edu [128.135.20.70]) by mx1.freebsd.org (Postfix) with ESMTP id 9951977C81 for ; Wed, 31 Jan 2018 20:59:36 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from point.uchicago.edu (point.uchicago.edu [128.135.52.6]) by kicp.uchicago.edu (Postfix) with ESMTP id 8ABE571804D; Wed, 31 Jan 2018 14:59:29 -0600 (CST) Subject: Re: Response to Meltdown and Spectre To: "Zahrir, Abderrahmane" , "freebsd-questions@FreeBSD.org" References: From: Valeri Galtsev Message-ID: <87f124e9-2310-b751-d027-e4bf34275441@kicp.uchicago.edu> Date: Wed, 31 Jan 2018 14:59:29 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 20:59:37 -0000 On 01/31/18 14:13, Zahrir, Abderrahmane wrote: > Hi Guys, > > I understand that you have not been notified early enough about the Meltdown and spectre security flow. > However do we have a rough estimate (something like an approximate month) of when a patch will be available for the latest version 11.1 and possibly 11.0? First of all, I'm by no means speaking for FreeBSD developers team, I am just one of the users (sysadmins who runs FreeBSD on several servers). I would not ask FreeBSD folks to speed it up, or anything. They really do great job to deal with somebody's else crap the best system architecture wise way possible. One thing could be mentioned here: Intel released new microcode some time ago, which effectively was bricking some of end user's machines. They withdrew it, and recommended to hold off, and go back to old microcode. [Co-]incidentally, RedHat removed from its updates patching microcode; this they had to do for the same reason, and basically made it the issue between end user and CPU (or machine?) manufacturer. Sorry if I misinterpreted anything (most of which I know from CentOS general mail list). Valeri > > Regards, Dahman ++++++++++++++++++++++++++++++++++++++++ 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 Wed Jan 31 21:01:37 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E285AEE180E for ; Wed, 31 Jan 2018 21:01:36 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp.rcn.com (smtp.rcn.com [69.168.97.78]) (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 8BB3777FA3 for ; Wed, 31 Jan 2018 21:01:36 +0000 (UTC) (envelope-from roberthuff@rcn.com) X_CMAE_Category: , , X-CNFS-Analysis: v=2.2 cv=YuZNfMQX c=1 sm=1 tr=0 a=9TgA2UwI6Wy+6BV4wQM/cQ==:117 a=9TgA2UwI6Wy+6BV4wQM/cQ==:17 a=KGjhK52YXX0A:10 a=kj9zAlcOel0A:10 a=XRQyMpdBKAEA:10 a=RgaUWeydRksA:10 a=48faUk6PgeAA:10 a=USkNwYM6PY2z0l2W2EcA:9 a=CjuIK1q_8ugA:10 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine X-Authed-Username: cm9iZXJ0aHVmZkByY24uY29t Authentication-Results: smtp03.rcn.cmh.synacor.com smtp.mail=roberthuff@rcn.com; spf=softfail; sender-id=softfail Authentication-Results: smtp03.rcn.cmh.synacor.com header.from=roberthuff@rcn.com; sender-id=softfail Authentication-Results: smtp03.rcn.cmh.synacor.com smtp.user=roberthuff; auth=pass (PLAIN) Received-SPF: softfail (smtp03.rcn.cmh.synacor.com: transitional domain rcn.com does not designate 209.6.230.48 as permitted sender) Received: from [209.6.230.48] ([209.6.230.48:32746] helo=jerusalem.litteratus.org.litteratus.org) by smtp.rcn.com (envelope-from ) (ecelerity 3.6.25.56547 r(Core:3.6.25.0)) with ESMTPSA (cipher=AES256-GCM-SHA384) id 94/7E-00908-AAE227A5; Wed, 31 Jan 2018 16:01:30 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <23154.11945.856955.523027@jerusalem.litteratus.org> Date: Wed, 31 Jan 2018 16:01:29 -0500 From: Robert Huff To: "Zahrir\, Abderrahmane" Cc: "freebsd-questions\@FreeBSD.org" Subject: RE: Re: Response to Meltdown and Spectre In-Reply-To: References: X-Mailer: VM 8.2.0b under 25.3.1 (amd64-portbld-freebsd12.0) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 21:01:37 -0000 Zahrir, Abderrahmane writes: > I understand that you have not been notified early enough about > the Meltdown and spectre security flow. > > However do we have a rough estimate (something like an > approximate month) of when a patch will be available for the > latest version 11.1 and possibly 11.0? Given that - at this writing - _Intel_ doesn't fully understand how to fix this .... Respectfully, Robert Huff From owner-freebsd-questions@freebsd.org Wed Jan 31 21:02:52 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8FE55EE199F for ; Wed, 31 Jan 2018 21:02:52 +0000 (UTC) (envelope-from freebsd@coombscloud.com) Received: from mini.coombscloud.com (mini.coombscloud.com [67.42.252.43]) by mx1.freebsd.org (Postfix) with ESMTP id 2EED37821B for ; Wed, 31 Jan 2018 21:02:51 +0000 (UTC) (envelope-from freebsd@coombscloud.com) Received: from [192.168.8.255] (209-180-88-130.dia.static.qwest.net [209.180.88.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mini.coombscloud.com (Postfix) with ESMTPSA id 5D7DE14B7D; Wed, 31 Jan 2018 13:54:55 -0700 (MST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.99.3 at mini.coombscloud.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mini.coombscloud.com; s=mail; t=1517432095; bh=9KwW0RkwJwEnkGyQW+KWUK8xgVYXLRDQdHsln8nFmVg=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=lN2oIvS1v7xBqICNLbDdXvUiG9ZsadS1LoxabmWrKgBBERDLjZZJybJzdra2bO8a3 WrmMXupFxm/344PZr5FksDk8/bIrxKg/Rd2gPq1t60GVFkPaUrv1wIo1bNtt/AEBwJ ZF0ORBA8uCNaDKMesxfXhLD5oQd1mS2NwibXwu/g= From: Kirk Coombs Message-Id: <154CCA2F-93E6-4D2C-A00B-6670BD88052B@coombscloud.com> Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Response to Meltdown and Spectre Date: Wed, 31 Jan 2018 13:54:54 -0700 In-Reply-To: Cc: "freebsd-questions@FreeBSD.org" To: "Zahrir, Abderrahmane" References: X-Mailer: Apple Mail (2.3445.5.20) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,HTML_MESSAGE autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mini.coombscloud.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 21:02:52 -0000 > On Jan 31, 2018, at 1:13 PM, Zahrir, Abderrahmane = wrote: >=20 > I understand that you have not been notified early enough about the = Meltdown and spectre security flow. > However do we have a rough estimate (something like an approximate = month) of when a patch will be available for the latest version 11.1 and = possibly 11.0? There=E2=80=99s was fairly detailed update by the FreeBSD foundation = yesterday: = https://www.freebsdfoundation.org/wp-content/uploads/2018/01/FreeBSD-Found= ation-January-2018-Update.pdf = From owner-freebsd-questions@freebsd.org Wed Jan 31 21:39:34 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A2D1EE3497 for ; Wed, 31 Jan 2018 21:39:34 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from smtp10.server.rpi.edu (smtp10.server.rpi.edu [128.113.2.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "canit.localdomain", Issuer "canit.localdomain" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 259CF79CD7 for ; Wed, 31 Jan 2018 21:39:33 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from smtp-auth1.server.rpi.edu (route.canit.rpi.edu [128.113.2.231]) by smtp10.server.rpi.edu (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id w0VLdQZC028957 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 31 Jan 2018 16:39:26 -0500 Received: from smtp-auth1.server.rpi.edu (localhost [127.0.0.1]) by smtp-auth1.server.rpi.edu (Postfix) with ESMTP id 51CCF580ED; Wed, 31 Jan 2018 16:39:26 -0500 (EST) Received: from [172.16.67.1] (gilead-qc124.netel.rpi.edu [128.113.124.17]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: drosih) by smtp-auth1.server.rpi.edu (Postfix) with ESMTPSA id 462315800D; Wed, 31 Jan 2018 16:39:26 -0500 (EST) From: "Garance A Drosehn" To: "James B. Byrne" Cc: "James B. Byrne via freebsd-questions" Subject: Re: LPD listen directive? Date: Wed, 31 Jan 2018 16:39:26 -0500 X-Mailer: MailMate (1.10r5443) Message-ID: In-Reply-To: <9e6a89f6ac654b113372b3f8b736061a.squirrel@webmail.harte-lyne.ca> References: <870deecf052d36d03aae9613410b38ba.squirrel@webmail.harte-lyne.ca> <0F811690-40FD-45F6-AAD7-BD24E1016DFF@rpi.edu> <4747d314efd1614e211c557b469ad98f.squirrel@webmail.harte-lyne.ca> <20180131104608.858e4a41.freebsd@edvax.de> <9e6a89f6ac654b113372b3f8b736061a.squirrel@webmail.harte-lyne.ca> MIME-Version: 1.0 Content-Type: text/plain; markup=markdown X-Virus-Scanned: ClamAV using ClamSMTP X-Bayes-Prob: 0.0001 (Score 0, tokens from: outgoing, @@RPTN) X-Spam-Score: 0.00 () [Hold at 10.10] X-CanIt-Incident-Id: 03V59DqjC X-CanIt-Geo: ip=128.113.124.17; country=US; region=New York; city=Troy; latitude=42.7495; longitude=-73.5951; http://maps.google.com/maps?q=42.7495,-73.5951&z=6 X-CanItPRO-Stream: outgoing X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.230 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 21:39:34 -0000 On 31 Jan 2018, at 10:09, James B. Byrne wrote: > On Wed, January 31, 2018 04:46, Polytropon wrote: > >> Check /etc/defaults/rc.conf and you'll discover those: >> >> lpd_enable="NO" # Run the line printer daemon. >> lpd_program="/usr/sbin/lpd" # path to lpd, if you want a different >> one. >> lpd_flags="" # Flags to lpd (if enabled). >> chkprintcap_enable="NO" # Run chkprintcap(8) before running lpd. >> > > Thank you. It would not have occurred to me to look in/etc/defaults/ > >> See "man 8 lpd" for a list of options. > > I did that, several times, before posting. I infer that the thing > to do in this case is to set lpd_flags="-s". Yes, just add lpd_flags="-s" as a line in /etc/rc.conf. You could then run the unix command: /etc/rc.d/lpd restart to restart 'lpd' and see how well it works for you with that option specified. The file /etc/defaults/rc.conf is very useful to see what other things can be set via environment variables in /etc/rc.conf. There are hundreds! -- Garance Alistair Drosehn = drosih@rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy, NY; USA From owner-freebsd-questions@freebsd.org Wed Jan 31 21:59:14 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE850EE45BC for ; Wed, 31 Jan 2018 21:59:14 +0000 (UTC) (envelope-from dch@skunkwerks.at) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (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 575457AF5B for ; Wed, 31 Jan 2018 21:59:13 +0000 (UTC) (envelope-from dch@skunkwerks.at) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 9CE2920A7B; Wed, 31 Jan 2018 16:59:12 -0500 (EST) Received: from web6 ([10.202.2.216]) by compute7.internal (MEProxy); Wed, 31 Jan 2018 16:59:12 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=skunkwerks.at; h=content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=3LTsGRz0Q/nR/vWUMe7voJExyZE8R x66zmf7aYTpaok=; b=V0ybZK+n1LSjizdHi3CX4IjY1MMeLz1V++gS6yM1IP4O4 ToMLj0IPTZN80JlHaMmqOVAfMF3ptsLEKiPxhqv9gtXNfm8g9KnxRe3C6KNsETrJ n8ljJQcCle8bJRKQI30PKGoTTKLKOVHwyNKlEJn8vtZasXOBwzPhdnYOxRhddx2h W3ME9vgNS4KvkXYcqr2DqUFxqUfGHhhijx/GEi7A6KmdHXlRRIuoZYXZblY8nSsC smcHcrEjUqHixRkWqhTOOegPmJJgQinECBCf3Ho2fvZPa3LcYYeVypR3s4hx/YqN YupwA8aIs1MqkZ25OMBG9tOAznKMxopB8MBHso1HA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=3LTsGR z0Q/nR/vWUMe7voJExyZE8Rx66zmf7aYTpaok=; b=fcD0bNqyJmYFPltJJMIBvH ncTmrxMjJebc9asgDEXz3eGY4kAWbbNyDsT5zlGJ0wiprQiyTTJKn/EUmxzSAs/w b+BsTszFgzP7zmwOg2ehsemFDWu/h/1QKrFTsIQbqBQ3tUd/D1Sx8pT7pQzC1s49 VavJkpCJbmMVReQSf6iEA8Hp5zJNmVTzbtY/EwAfi4GdT/SR1Cm0qVnrlRMCkn/8 7FmuYOn5EDCayYyDX2bDK55fc710rnU8pFM1bSZmSQsdOa0iKCq0kpTUjk0LPfV0 2lPfYJ5e41jjw2SXeSmLXGgU9/5/KgqhMMeCgn6v7N1KriFDiXlcWvXeWGUK9nUA == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 6069F4251; Wed, 31 Jan 2018 16:59:12 -0500 (EST) Message-Id: <1517435952.2407347.1255099432.2DE20786@webmail.messagingengine.com> From: Dave Cottlehuber To: freebsd-questions@freebsd.org, bennett@sdf.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-20f48d70 Subject: Re: ZFS error message questions Date: Wed, 31 Jan 2018 22:59:12 +0100 In-Reply-To: <201801100811.w0A8B62K027111@sdf.org> References: <201801100811.w0A8B62K027111@sdf.org> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 21:59:14 -0000 On Wed, 10 Jan 2018, at 09:11, Scott Bennett wrote: Hopefully somebody replied off-line to get you out of your dilemma, Scott. If not, at least I hope this is useful to your understanding. > After running 11.1-STABLE with root on ZFS for a week and a half or so, > I apparently screwed something up such that the system became unusable while > trying to enter multi-user mode. It looked like the easiest way to correct > the mess would be to wipe it out and re-install. I'm a huge fan of using Boot Environments via sysutils/beadm-devel for this. Basically your / filesystem lives in zroot/ROOT/a_meaningful_name, except you can: - have multiple copies / versions - select one of those at start time - keep "anything useful" on a dataset that lives outside (zroot/usr/home for example) so that it stays between environments - I can build and install from source into a new boot environment - or try out the next release safely inside there - have super powers for sysadmins > However, I wanted to save the home directory tree because there had been > important changes in it since it had been imported from the 10.3-STABLE system > with root, /usr/home, and so on on UFS2, so I ran > > zfs send -ReL -I @15dec2017.freshlyinstalled-11.1S-r236620 zrootx/usr/ > home@28dec2017 > /mnt/bootdisks/usrhome.28dec2017.zfs-send > > which is supposed, as I understand it, to have saved a full replication stream, > including four snapshots. Now I wish to receive this into the newly > re-installed system, but here is what happens. > > Script started on Sun Jan 7 00:54:39 2018 > # zfs recv -dv zrootx receiving incremental stream of zrootx/usr/home@16dec2017.post-import- > from-10.3S into zrootx/usr/home@16dec2017.post-import-from-10.3S > cannot receive incremental stream: most recent snapshot of zrootx/usr/ > home does not > match incremental source > # exit Almost - you're not starting from the beginning of the zfs dataset, but a snapshot partway through, 15dec2017.freshlyinstalled-11.1S-r236620. As an example if we squint hard and pretend that the dataset is just a simple array, e.g. dataset [0,1,2,3,4] is the entire dataset and all snapshots, then you've sent [2,3,4] along, but you still need [0,1] to be able to have all the data, and also to be able to create a valid dataset you'll need the first few chunks - anything that hasn't changed in [2,3,4] is only going to exist in the early blocks in [0,1]. If you don't need the earlier snapshots, its sufficient to `zfs send -Lev zrootx/usr/home@28dec2017 > zrootx_usr_home_28dec2017.zfs`. Just remember that's not recursive so you'll need to do that for each dataset separately. This is likely to be a lot smaller than the full set with all intermediary snapshots. > Script done on Sun Jan 7 00:55:59 2018 > > I have two questions at this point. > 1) What in hell does this apparently undocumented error message mean? The zfs recv is normally (aka I do this and I hope it's common practice) done with `zfs recv -Fuvs zroot/usr/home` which will try to rollback (the F) any later snapshots on the receiving dataset to find the last preceding snapshot that your [2,3,4] stream needs to link onto - the [1] snapshot is that predecessor. So the error is simply saying "I can't find anything to continue on from", as your destination dataset has no blocks in common at all with the incoming replication stream, as [0,1] are missing. > 2) Is there still any way to recover what I need from the saved > stream? It's a couple of hundred gigabytes in length, so if it's just > junk now, I'd like to free up the space. If the original [0,1] are no longer about then this is difficult. I am sure there are people who can extract the changes from the incomplete zfs stream, but to my knowledge there's no magic command line tool to do so. I'd love to be proved wrong, and have something like a .zip or .tar recovery tool that can work with incomplete streams. > I think I only need three or four files that have changed since I imported > /usr/home into 11.1-STABLE from 10.3-STABLE by > > dump 0f - /usr/home>/mnt/bootdisks/usrhome > > on the 10.3-STABLE system, followed by > > cd /usr/home > restore rDf /mnt/bootdisks/usr/home Some reference for future BE (boot environment fun) are here: http://www.infracaninophile.co.uk/articles/zfs-update-management/ http://www.callfortesting.org/bhyve-boot-environments/ https://dan.langille.org/2017/09/30/upgrading-from-freebsd-10-3-to-11-1-via-freebsd-update-and-beadm/ A+ Dave From owner-freebsd-questions@freebsd.org Wed Jan 31 23:02:38 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA31EEC2611 for ; Wed, 31 Jan 2018 23:02:38 +0000 (UTC) (envelope-from frankfenderbender@council124.org) Received: from vps349.pairvps.com (vps349.pairvps.com [216.92.231.69]) (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 609957DA07 for ; Wed, 31 Jan 2018 23:02:38 +0000 (UTC) (envelope-from frankfenderbender@council124.org) Received: from [192.168.0.100] (unknown [104.220.39.23]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by vps349.pairvps.com (Postfix) with ESMTPSA id DF19CA640C; Wed, 31 Jan 2018 18:02:31 -0500 (EST) Subject: sound-card/driver question Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: C Gray Date: Wed, 31 Jan 2018 15:02:30 -0800 Reply-To: C Gray Content-Transfer-Encoding: quoted-printable Message-Id: <8F08E935-33A8-4B5F-9057-51FAD51DA97D@council124.org> To: freebsd-questions@freebsd.org X-Mailer: Apple Mail (2.1085) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 23:02:38 -0000 I have a Dell PowerEdge T300 server which has the following slots = available: slot 1: 3.3-V, full-length PCIe x4 with x8 connector slot 2: 3.3-V, full-length PCIe x4 slot 3: 3.3-V, full-length PCIe x8 slot 4: 3.3-V, full-length PCIe x8 slot 5: 3.3-V, full-length PCI-X The system is based around: Xeon X3440 @ 2.50 GHz Quad core 2GB DDR3 RAM. It's been said that a driver supported for Vista will work with for = FreeBSD. The card I am looking at works with Microsoft Windows7, Vista, and XP. It's PCI-X based, and would, thus, be inserted into [my] slot 5: Creative Sound Blaster X-Fi Xtreme Gamer SB0770 7.1-Channel PCI = Sound Card My question is whether the CD of sound card drivers are in a = standardized format such that,=20 FreeBSD/TrueOS can use them, as is, just as the Microsoft-verified = environments do? Do they even use the same suffix? Are they well-written enough to = discover the platform whereon they are expected to run (*that is, to "drive"). It the OS discovers the = driver rather than the driver=20 discovering the OS, the same functional use may be achieved, however, = I'm ignorant other than=20 guessing as to how drivers work and what is required for that to take = place. Where are they stored in Windows and in FreeBSD, and how do I install = the proper one from the=20 disk accompanying the card (most likely meant for Microsoft's = toolset/installer. I do recognize that [cr]Apple spent more time avoiding Linux and Windows = standards for=20 customer-control reasons... for their bottom line. So, I am hoping that = the line "canyon" between=20 FreeBSD and Windows is negligible, if non-existent w/r/t card access and = driver installs. Suggestions? Thanks, C Gray frankfenderbender@council124.org From owner-freebsd-questions@freebsd.org Thu Feb 1 01:20:10 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AFAC1ECAA51 for ; Thu, 1 Feb 2018 01:20:10 +0000 (UTC) (envelope-from jd1008@gmail.com) Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::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 3AE7581E17 for ; Thu, 1 Feb 2018 01:20:10 +0000 (UTC) (envelope-from jd1008@gmail.com) Received: by mail-io0-x230.google.com with SMTP id l17so17336483ioc.3 for ; Wed, 31 Jan 2018 17:20:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-transfer-encoding; bh=dt8wvy1edeJdBkZ+QO8CgV/rSDBANC2TymZLpeP/onw=; b=N6DEkA0H5XNDAVDivMU3e5S3pZQzL+hlVksSoFJ+GaCto8eQCL/WO+8P1nQrx82kJ4 I1u4/mVRvQCL4QA3yA7lPXMj6Dazi6vIUclPxZAkXbBVFGdKI+jtuWONsR23KMRvKf6Y /bh51UHz6ORxYtpi40wH1uwBI2B46M9LfycuXHEBJ+y9NNfPnGkrlRJfQTH4QIJeMefa oQ+6jyTAXACS/XsUcWcF/0tXP93080exgDukHqjU6N0HFKtGdFjhpiE4qWm3Fc5+6Rlj 9tJ/km3XnPJGrLNCaf8MJswQDJrpOvbRLkBe+8Hzp3SAJ2FIH5ahSTEfullXHrM11HA6 6T+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-transfer-encoding; bh=dt8wvy1edeJdBkZ+QO8CgV/rSDBANC2TymZLpeP/onw=; b=OEF0y3Cl1uSOMnN7X++S60T1+Cmt3dveyME+F4mfotsJyZw72A3uhLfzds8k9dUlw9 m5OOGn7fr+XgE0tpsByhCixa5RujK9ysIW6B33WX3HxlUILiWuDrp5vxqp40cI1O9FOH MjDy0G3N/M+9XfaUg8FRmjygbDngcgbhJmG5SSpqQB2fX3N3BQa4JMiiAeu2hbG4l30t vhiloKjWs1Ysi6rzTrUAfErN4CJHJ/NFltry0Iqx19uQfsSOeoEndh0xhX8kZNi7srIX 2fPsmD5EF78CVfyPBOlTLqmFLWIz13WpPwefYE1lpqxLriw1O2QxNE859JiP9/UZARSo PWMQ== X-Gm-Message-State: AKwxytf5WRuJDLReSEG0fZ2Iim4xcC2khFmk4hdkoC8/SSke1wKStmay OdhVA4XFWy+ZRt/2820jFUuEsQ== X-Google-Smtp-Source: AH8x2260tBHxdpy0poQflRy6K63JrUj/l/Ce/AYTwYP1fVh9WBMLI1SSwpMhHMPghAVHg0icIB+N0A== X-Received: by 10.107.78.17 with SMTP id c17mr28151788iob.18.1517448009452; Wed, 31 Jan 2018 17:20:09 -0800 (PST) Received: from localhost.localdomain (50-243-4-3-static.hfc.comcastbusiness.net. [50.243.4.3]) by smtp.googlemail.com with ESMTPSA id s70sm211731itb.0.2018.01.31.17.20.08 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Jan 2018 17:20:08 -0800 (PST) Message-ID: <5A726B60.7040606@gmail.com> Date: Wed, 31 Jan 2018 18:20:32 -0700 From: JD User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: Response to Meltdown and Spectre References: <23154.11945.856955.523027@jerusalem.litteratus.org> In-Reply-To: <23154.11945.856955.523027@jerusalem.litteratus.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 01:20:10 -0000 On 01/31/2018 02:01 PM, Robert Huff wrote: > Zahrir, Abderrahmane writes: > >> I understand that you have not been notified early enough about >> the Meltdown and spectre security flow. >> >> However do we have a rough estimate (something like an >> approximate month) of when a patch will be available for the >> latest version 11.1 and possibly 11.0? > Given that - at this writing - _Intel_ doesn't fully understand > how to fix this .... > > > Respectfully, > > > Robert Huff I think this blunder by MS-Intel Duopoly could be the poison pill that will kill both. > > _______________________________________________ > 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 Thu Feb 1 02:10:02 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EFE23ECEB42 for ; Thu, 1 Feb 2018 02:10:01 +0000 (UTC) (envelope-from sales05@lspower.info) Received: from m213139.ym.163.com (m213139.ym.163.com [223.252.213.139]) by mx1.freebsd.org (Postfix) with ESMTP id 32E038409E for ; Thu, 1 Feb 2018 02:09:59 +0000 (UTC) (envelope-from sales05@lspower.info) Received: from HP-PC (unknown [120.197.250.156]) by m213139.ym.163.com (HMail) with ESMTPA id 821F41C474D for ; Thu, 1 Feb 2018 10:09:49 +0800 (CST) Message-ID: <20180201100949252.sales05@lspower.info> MIME-Version: 1.0 From: "Longsun Generator" To: "Freebsd-questions" Reply-To: sales08@longsunpower.com Date: 1 Feb 2018 10:09:49 +0800 Subject: cummins and perkins generators X-HM-Spam-Status: e1ktWUFJV1koWUFPN1dZCBgUCR5ZQUtVS1dZCQ4XHghZQVkyNS06NzI*QU tVS1kG X-HM-Sender-Digest: e1kSHx4VD1lBWUc6MEk6EBw5OToaS01WNEgBQzgWDhkwCyNVSlVKTkpM T05LQkNCQ05LVTMWGhIXVQgaFx4IS047FwgLFAweCVUSFR0URVlXWQweGVlBHRoXCB5XWQgBWUFC T0lLTjdXWRILWUFZSklLVUpCTFVJTktVSk5NWQY+ X-HM-Tid: 0a614f2090037d8bkuuk821f41c474d Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 02:10:02 -0000 =0D=0AHelloFreebsd-questions=EF=BC=8C=0D=0AHow are you ?=0D=0APle= ase check ourin stockgenerators below, if you need more informati= on please let me know, thanks=0D=0A=0D=0A=0D=0A=0D=0A=0D=0A=0D=0A= =0D=0A=0D=0A=0D=0A=0D=0A=0D=0A=0D=0A=0D=0ALSP GENERATOR STOCK LIS= T for immediatatly delivery (0 running hour)=0D=0A=0D=0AProductio= n Date=0D=0AType=0D=0APrime Power=0D=0AEngine Brand=0D=0AEngine += Alternator=0D=0AQty=0D=0A=0D=0A=0D=0A2016/10/13=0D=0AOPEN=0D=0A6= 25kva=0D=0ACUMMINS=0D=0AKTAA19-G6A + HCI544FS=0D=0A1=0D=0A=0D=0A2= 016/9/8=0D=0ASILENT=0D=0A180kva=0D=0ACUMMINS=0D=0A6CTA8.3-G2 + UC= I274G=0D=0A1=0D=0A=0D=0A2016/3/9=0D=0ASILENT=0D=0A250kva=0D=0ACUM= MINS=0D=0ANT855-GA + HCI434E=0D=0A1=0D=0A=0D=0A2016/7/8=0D=0ASILE= NT=0D=0A200kva=0D=0ACUMMINS=0D=0A6CTAA8.3-G2 + EG280-160N=0D=0A8=0D=0A= =0D=0A2016/12/1=0D=0AOPEN=0D=0A450kva=0D=0APERKINS=0D=0A2506C-E15= TAG1 + HCI544C=0D=0A1=0D=0A=0D=0A2017/1/1=0D=0AOPEN=0D=0A1700kva=0D=0A= PERKINS=0D=0A4012-46TAG3A + MRG-S1440E=0D=0A2=0D=0A=0D=0A2017/1/1= =0D=0AOPEN=0D=0A1000kva=0D=0APERKINS=0D=0A008TAG2A+MRG-S1440E=0D=0A= 2=0D=0A=0D=0A2017/1/1=0D=0AOPEN=0D=0A1500kva=0D=0APERKINS=0D=0A40= 12-46TAG2A+MRG-S1440E=0D=0A2=0D=0A=0D=0A2017/1/5=0D=0AOPEN=0D=0A3= 5.2KW=0D=0AOLYMPIAN=0D=0AGEP44-5=0D=0A4=0D=0A=0D=0A2017/1/5=0D=0A= SILENT=0D=0A12KW=0D=0APERKINS=0D=0A403D-15G=0D=0A1=0D=0A=0D=0A201= 7/1/5=0D=0ASILENT=0D=0A24KW=0D=0APERKINS=0D=0A404D-22TG=0D=0A1=0D=0A= =0D=0A2017/1/5=0D=0AOPEN=0D=0A88KW=0D=0AOLYMPIAN=0D=0AGEP110-4=0D=0A= 2=0D=0A=0D=0A2017/1/5=0D=0AOPEN=0D=0A52KW=0D=0APERKINS=0D=0A1103A= -33TG2=0D=0A1=0D=0A=0D=0A2017/1/5=0D=0AOPEN=0D=0A220KW=0D=0AOLYMP= IAN=0D=0AGEH275-2=0D=0A1=0D=0A=0D=0A2017/1/5=0D=0AOPEN=0D=0A221KW= =0D=0APERKINS=0D=0A1104C-44TAG1=0D=0A1=0D=0A=0D=0A2017/1/5=0D=0AS= ILENT=0D=0A222KW=0D=0APERKINS=0D=0A1104C-44TAG1=0D=0A1=0D=0A=0D=0A= 2013/1/1=0D=0AOPEN=0D=0A1875kva=0D=0ACUMMINS=0D=0AKTA50-G9 + PI73= 4C=0D=0A1=0D=0A=0D=0A2017/1/5=0D=0ASILENT=0D=0A200 kva=0D=0AMITSU= BISHI=0D=0A6D24-TC + ECO38 2S4A=0D=0A2=0D=0A=0D=0A=0D=0A=0D=0A=0D=0A= =0D=0A=0D=0A33=0D=0A=0D=0A=0D=0AWe are diesel genset factory from= China, we manufacture cummins, perkins, doosan, Mitsubishi gener= ators from 10kva to 2500 kva coupled with Stamford and Leroy Somm= er Alternators, we also supply CKD gensets as engines, alternator= s, radiator, baseframe, ATS, canopy, controller and other spare p= arts in loose.=0D=0A=0D=0AIf you have any inquiry please kindly s= end to us, thanks.=0D=0A=0D=0A=0D=0A=0D=0A=0D=0A=0D=0ABest Regard= s,=0D=0A=0D=0A=0D=0ALONGSUN POWER CO LTD=0D=0A=0D=0ATel: +86 1343= 3313044 =EF=BC=88Whatsapp, wechat=EF=BC=89=0D=0AEmail: info@longs= unpower.com=0D=0AWeb: www.longsunpower.com =0D=0AAdd:No.83 Jinsha= zhongRoad,ShantouCity,GuangdongChina=0D=0A=0D=0AIf you don't want= to receive emails from us, please click Unsubscribe Thank you ve= ry much for you time.=0A=0A3E7mExxQq2DhfhzFUy7treda1By9hK380XK4bz= 65dPhconjboG3ZAYQPrWk3ZoyFZuhixuuks1fBW0MDinKBH4y16VDef26PhCdT61D= TbJwyIfSqaHLCDWYUVfbCRg5pUqjkMTwhJRpXxZiR2d4yhuckEiXRP12VE7DiVyDh= auSMw0nWWkzDcx7qeZFuVErHOujpl0VuzMnNBpNEU1VvroJ6Zd4VS9lv2bX2GYAVo= 54p9kPOb1zTJVgpLcp8WZBprSKqsLXWqZ7mkkXFofKRAsL7UyhtysZotEYhzomq3C= sKOT4rfKKGfJPY6DvUtuoYZISGmG5ZTjOXZ1i0tQeOHj8JOZaWTsWzetK61o5yEKM= WVRZ4luqDfzgGz9Rmw96rmfJvhbZ4LG9WwcOX05Bo1ijEd3wRwI2vElzG7tN9vlSz= qjamlUmqxHq4W4idE7y2DEibD7PwhrTFpJeTTawClBXXUuK3aAunNPVM1ZId5Q86O= KEcQpkuBVH1Glg8nMmHXwRzNsRTrjxvtR89QxcKg0LS8U5GJzPitr8iT4ooyq2ioc= yPc6iPzBrWKZrTmaaRte11IQgM9OcPXtuWlguDhZJS0byUCu1ngaO9aw6mPvGLoBZ= gvvy5Gxztv81wim9EMOzMEkLOa7NMjYtocho7WVHJBlE1vA4tm1YA2cCbJJVyJNax= FCj0X1IR7PbjFJjz3kqiZTmZEdocZ8ZNb7mSg3vki6sc1jvZqlvpnRxLgkmJDwRZQ= n7ynqjZO6ZSr9YlIoLDCzqjzABWHLGMftlDbWC02wAhSEk7l01eKdmhXOZMOni3pd= DXNkaMMLB6Y9qUfuAGKr1164FmXPbFdxRF1mk0QesZCgiOn4wkMCiXbBRIENPXzWS= qhLTTazPvZ2pQLRZSiRSBeTupvBm3pvpFnSwCaD9dMNY8c1XNOWEI4hbnhunzdL5u= DJsTkmIEHEOrVldtEyftQHB5G9lGfA01Huvsy3trdZ0ptKsVgUVEwBDW8mdb12p7E= NJrPKUA5NfRGbCVGpplFlu5QzkcPhqbATLG115vZkzIlMfWKiuBD3sjiDAgqIKNn4= gNqWUFkTlkLMJ3knrxNPywqsnnqP5hzLlhvrwOnPgJI7xwTwW2gd0xwKmXywevO4K= ZqsySRD9XyOOjURuTS20mLNKL4yfRALVDmx5qY3bD32ZHV33H2lCL3oeDHNOjoinN= SaWnM3VPRniIN3P1vyOf9azYjrIbfSeLFcOK7FUZqNUG5vPEXMNQt7EIBX4kkJAZ8= x2Be4UPDPPmgTTNB4ds4ohyy699BAFGcUyyteqTSYdEhisI4hJgw7VJfu38VKd2a9= 9lkkjnDkz5bDggDr5kRp95ZOjYaiY8Kau897nJXlCcxPyBeNutFSbLZ3lw1lckmrk= 0977v3lnvMXxafHKnNusSYJ85LQHB8hQ6uxr6GZqjuGY2vbhkAPxRYs2qZ1JcDMnu= 7rFHgEHO48niK6zAzn0jKY72v17EfdGIjtV3wz3W8INP5KGSr9DgL3K8kCbfx2zRs= EYgbw40j4a1ahXLked5zpXfJMJTnOp69WmqLpGV5DWHTIX2FqUiPth2GJxpMaCuE4= ReUw0Vxh0Wtgl0OGdXU7hGEjJ1Rh8U0r2ORJ79pYKxskzqnxB5XFAxNazAMZ4g96W= 2dw94y4xWmKekKjDkG2XlRu1G9xmqUunlowcQnwxS8Db3WfPtlJz69AbIvsU1I62R= mSVe6MW9v4ddjYJUHT5bUhcNltlUBv91BjH3kBmyMpB4nXowJ0kO1RX4F7SCr1yZU= bC0hFA5xwouG8qo4ObBbl0KmCncJJ7KRB9clof3qfhussoxHtxCQXOzaREFinlNoD= D5Zd2Gy8bW3vhTdQvfbvUUMz1tJAK2Tu6OOjytrR3HLSwFzKrrR5CTJIipcyWYn82= zpt4Th2Okrd8U2lUZ8jaNSc5618gSU5jDPXg6FxaPhhsvzomQEXP4XfHcnYS8LWpl= Tv455OjA9lwAKzwDMqdXgeFAg4IHF13kS6C4jgLQEeVCI6rOsfmlJs5FQuP15CV7h= bHEXrjvFmi2j2R9CUeqEIBp1XdOrJL2iNkxoNQ0VRGm93lNDGobnvtzAhC0ev3VBg= JvHjKP3evN2fgYBpaLlAENjLX6aQMpNLKSjP6jVz79ZGwk1EoOkiA1CVcVmDEcr5Z= gvnELjRPLsuNDeC5vrX5ubIgoDaXhUUHUGfPD0DutsOz77yGJy9Lt0v5M7g89TyQx= NTXZNrvOtB1m98g5tdJL9eUba2wKulzUX1keAHW6EW0otJCYZ2GGO5ozYMOKVKj71= 6p8O2uLgC7cdwHqqxKrFT5SCLfOTcbTCSmmkuaXyUpcYbls4nkn0Ss81wv3MFS4qd= Ak9l6VnNTKtSTrpNJvROTKpelNY6bS2kMKB0jJhoZdYIE8C4DYVncBkPVUZjWgB1I= 969Ppu0dsPGMHzdaUtcWE7aqL5oJXsIBXZv1teeuV9KMD3dlM91No431VI3j5gg06= 4OH4bGFfI0vnoMIR3XOqVdSWu6LbUoFTJFyewgBsmxF3yDxVls2jrzbRVLA4Vulkl= BEIdtlMlm4nxOnQzPPrlls9uHiKGwxSclIWZOHS7gX5vOk6nJv5FTYZ9uewaA5POb= bb6rRK8Wk5omEGmbnX1scinIMvAbIwa8gjC90WRKXIzSBNPxaYc8NmZSNoEmaWeNV= g6k3dbr5gvuIv6ZF20Kj1kUkJlBhvz0uLXlHvuWML3xRuaiiEG7VutTWbZjRA9zHu= 0XxLi9y4XyYN3Pz3jCOr4Zh3pvva5bBtQmucKwmwzRwVV889KOhxKfq0FtlNEoYLX= uWGlniMgiSctm8gnlqhU4JAWuxgbySbSLXqbrOnvugsmdwjl5qiYHQTLmKQQ1BIpH= jIoH4Vw2LpNgeIXdV58zcbU4FPGYxuTy3FUOUD1uLVWr5u72SC5vzPu8Nk1eeyvgw= fdzO9jh4EOhetYaIE5VonZdaL0zBMfdpFUQhydJiOrU1dUklQwAtAS8g0o38JFhpA= Ryy8T9qlCAW4bWRGeKgFKONMAh9aBy89vqllMdXm97YibbOscrvU1KQ3LLxCZfK4s= MyKAvU0NTvDQvAosHY92d8LziA0FknTmTQpD3RGxv77edcga99hgA1eDMahUTktwB= gWEbLpQiCx60xm6kPwb5CLRBLQSzLEaEBDXfBZnKrYYu8CfObA3OhqYu43pVwhwYm= spUpQIQ8qEENns9A3nbAmmbEsaxzsd9s07GdlplRdFRMkHHAgktTln05dfWFagGdu= bMfMVfE2jnGvpkKtXj8Kg7C7AZ5tFGWYDh8UsOl5PQ10kAOVbcdXysd498bV9anCr= HR7bP09Y2Vp5CN0bahstYqa33KkCpWEtozCJGJmb3ZvxOYxkbKYTU9shG384Fxy6h= VH3ahuqVhpYVDf4dZqFXKzf6l2DBhvwrpgShuaUfxYDKtm3O3RG6S8wmrWPeRPDLS= xwmmNIPwpqMWuCZYOypPqygJvPxkFoIkSRVQGrf8QzsIKqWjQg2geVrZfDQXbvQ1H= r3DG9hmihYQ5xY5Setplr6WpWA3BiXlJr1jmjCHYGYWWBUIEL4W1qGgl7dKyeL0jD= 7EwFJzBMrFs90O2RpPd0kiLKXf6S8JUXCjtgcY2vleZ0Nb7oHHPVMjjPSLHttJEHK= uwGlMEqNIF5jKWM8HaqUZbj0Dnqhy2CAhgiFq3V2o74Ddw7PVlLydMLjcGHpe9fG3= v1uD6HDfovR7GM7fBlcg3nuuZsJlwOfRoAIuDbOD8jPgTcwUA9CN3p08wZEEYiIzg= ZI64CCpwy8JxdBNVPLmcrOYzAYDx9FPAf0TtqPYxcguhgAioQJ9xmnOaKwuEYSmTi= 9hdHjuZNPZakGjZFeGqvieSbJIUljykUBZ7i5Hxe9KxnDQ3cuYKbWnZVo1XBAEtgF= gJHcGAw9cmyGvySEHQlO8Yd0cT3JWEvggIm7m0Ood2J1qeTt5WSO7rxivH0MwMdyR= hqNbLiH2XA6eczY0AEZLG9Ob4BF01RqPb98N6hjDaMaQq4j72MW8dMa8BC7aDH15a= h32raUikmBUYXKZixXeViBoZZcta90sK5G90gGRSDNRbfaDS7S5JM9SFF3rXq8bl8= 9ThAY1R5liuKcJPzB2hUIYVOuldfUsuCv25gli8QeDqRnUsjBnO6TqpbYt5DOBbTN= Sf9DzdjTrG5x3qzTTEwDnI4DUiScv2Csx4vFiF2avdsKkEU2vKUXFfpaawJgk6oo3= CZZVUAdBm8afkjfnQGL7FNhEluLWLPoP3GHEV7B9Gli7eUQdtSuqChoPIkApOhQwJ= lbDBBsJ4Bqju9pqEytSkXcMhSWAxckpvLnTJdBSqLl1R5kyV9LgOXcL9olJERcSh1= NILwGrWAszCbVcxnFnr4ByzBJkRSdyztJPhCMotjjduC9Yt9bgcPqdpf8aMlz3mT0= 8r5UVBgT7Kn3XsLRHHXmJ3wq2tCB7JfQBB1woegFVVis2bbH1uSmpxg5UFSsYELou= xslrestrhqOK4oQhUADRTq3lVBJlNGg9UXuJPgN1oU76skQh2a448wB6o0vCJ7DBa= EQ6T6rDNBtYjXSBLsiDCb1omokPLahghwVOtJnVIqhw3CMr7TRhO0ZYCsKuMCSCjc= HN14714nUbUvkKBTISj0rgwXb1ZT96yFcQVZp2LPdr6N3770SSUZijKqg3T51adND= fiuPCuF6uMZaIT3UZ1gcymS6uJl9FN2eiaOPDbgoeTOxKfxaPb29WA4TpnkS8wqGJ= LSy5ehOKSYFxllfbbjuLThH5VpfQngHs8NYnZ4BTdo4Cpm424HWdWVQuasaO2XnCg= coxnSb6IAxuc4FzldLGjuvcXtcwUMRf1smcXwFcvQulnli5MAtOcHiLGczTFFcWIh= tJItCOyyatZaOBb6Jji23k9AvLWLwQDyD6SynjYEgDwPLwnYHzVSDFe8z8XQRM2kP= rxIICJqkDMqOjOYoY4XULVXSKYel7MuBb0kZEf5QvxZTNkfjZsTI4q4vzQYDu4cRh= PCjtYJIZ7odV34pIVmFTMwLVPqNgrmrk8BYIWQ0IaJX1RzwMzVyHxXviQnEyWsxLX= SNr6HM5mWJ3yK4fT1HwNJMa6FRybrMIbc3YM4FR8tlBesK6jpFUK1Ye5ClrPeTV90= RmG5sPlPnjobWDVKfMMRX9ePT9Ie1UApsdAnqdWPzUEEPUGIv5Y78i2I7Rcj66OtJ= YJI2xk1PWi3vzZZt0IWVsg9bSfy1CJs6aVRaXFYKXhc0ZcyScQ6nRxgHzxahMZcdP= WkD7OvkKbYb49bFHFPMC4eDF9BqvHYX4Za2SUKokLDGy5DpluA6aqAKHHYYd4O3c1= 65Y9NMVqrRry4Awb416SMEoqkbWMbgWAtxYxqcHNbJYJj9Cor10NWjerGyOCQ8fbU= Q5wBYKRjjH2FF6byyl9f9E9jxQSo5X2uMPt35Msg8tCCcL1rC3hN6VKbVd48StelE= yTQD7sLST7F1x6LPqL1FfnQ4h7SIknEfgXDSbNvAwUcO5ao6ijrIcGpa2MmZA2yvt= pKztSEDgr8kb2Y7JLq1VW2AxtQoqvZumGlFpPDqEOsKx5ZZNfgPCwAxna1Z2fcLsE= XuHjHU8Zm6th2suQBbeaRP6OieNDnpCGiT8uiuymHCat357zvbD1whM7oT0s6uBWu= NZ9kZx7CRtfFCLd6d8cMBa1605pt5fd0eZf5YfvEwoEOxsL7NmTlpaSCY3jU8DxCg= fqCv78YDxfdvcyxkhFJmRA46D7UVBwSQ2yi18CGdUHSUF7LuMAQXOfoEmwSZd321n= msEgvbFZvr9I9rvmq91FU1M9DFCKGZRFQwiE7dgobYiOeWc4mDNU0lslGuDQyUjvA= uSD9QecSCuWIYUHsyn2cXEu3XYCApQgENdK4zVvoA1oQwCIAVoZxgjDPnzbSCCtLe= hVKaDSCRECVgDxlg2E0QJotAVG0JDLYxCCfGXqiwmFBGHyK2QCAXtUvSraeWSSeSD= oD1hEiCltt3NNSmVXT0b14I6meNbmEtrJ3jVJKbjYBZqs5EhR0UZdHCjVUVqvqZPZ= C3JyrcdHGcp4hEhzvjlKud1qZ0OPLOxBarP1UIqOGhwucfDgEQ06E4vo2jzqooWSE= NUQOfEMSx3dHwdKmybUNrX5VrZB90qikDQpkNroced71iHv6O3Pd24dQPUmg3CS7K= S3GOqz6MIzdP3DKtvlWA5izCyvT479Bl0gpDPhnuIqju00LhCNxgWwFzu3gUF1EzY= RPNd6DdXrRFY4CxKCskBkptBQ9L1tOHLKw8bX3v9jjuE0AqrIa3zjYDslbnXRcuCa= TextlMyWbh1UOBfJkijL7sMSFPMGyh7PRu6mSXmnvC8GCywA7exTbR2rsFNv0SoT9= b2kuSQmVVgvj5f7jbykJeE0rFUd9QnCdfxrvc5enaXfBx7mpGcOk49Vx2TOYDc4xD= h4yOB75jWzgooUxxNtEzi95BTtihgKYSHXf3OB55I17AE9DYgqPJqYl8YWV7OO2cA= nGqFuJcnyQh1vXJQk0PUesJC75RFXhTYVZgtcjMGDlS746tZbhtOdimVWOyoSwqgX= i6vGgE0d8gSzBy0BSuGN5KDCkwnLoO7VBaL0XiVCsA41umkfxMZ1JsRysSmJgfPj8= WXrN0DAy3kuFB8Yb8dBO5b9icx5VcmdKLTxoTsx8ptG7mSRKox81ev2KO8AsyEmH7= KUIAziFGspCv1WkGkxEebwfQNAKS4AL6Z0CX9aOfslM6qfNcfMd6IsVdERNZxNBSD= vv1jmwaJoLQK9pxNyCimFow4pihnPIFJUsUJLTTf3njH4surfcZbjvY7ZWU4fNUG6= 7QHvO1EJ2ji4PZWNP7DItqotNKPZOZfsDAXCNWraksgcG39WXgqFgYCHrdI3cFU33= Pqe2j0SGsn19cNJAS1yzzcFXgazenYFxd8RCUUDgxZOABxfqYsjDlttCLhL9qEiuI= tW3V7FXni2An5mIU9fUE1cJEeQD8uPSGkS7AcuQNmg3rTfGU3ehpnPGhdoHg2OTta= T3ce7IEo7hL9iLZaI5gytjubQnONAKynAh0btGVvC0fxV8UCH6jICUGAz1nJUROmJ= oz1LNG2aKVt3WfItb5trPKFApCrjbBLbTOxzSRTphxSZdxCMFgJLkVUDTrlbeIZ8a= ha8I9Ajb4ahRFmSZFEUSZRXUTFrwIayyKPWmt4vGpzgKCMe4sbz44gapceOu8NtTC= I7QqvwB8esqAdh7rn3wBtutEwaef1xC5n8TEnEWFYWPNJPYWH3LKXi8eDbTlhl7HQ= kd5os3I6RDxEGUHbhyYMS85ZE1bLBnCP8WpBTyeZ2D5EBAXhc9ZN8UYb85JrSXvt0= HvJv5hJjYJe2qn43UzsnOGdYetOON648CEU4dL6Rgu9bJ8HIFnYo25c1hLgBtUvSE= 6qMtZQ8sA7jw2e5M69q8G5wrSMsvvnmZhwDHVeFwPWrYSufwbPnK5JY1UkAdoDXdL= kevBnQRuTiJDyyoxVjGZBUyxBNADr8cZedyfJUNYwgbqenlMcGsjgd9pGXZzgd2K5= KplZ8N0wItlI7jesOrLFTI138zLVdHidqluY0M4SsMyJOHzEL7sMg5c2nhRz25i0b= 7iMPfr2mTd69hfrZ695fvWl8sAIUvPmuyxGoNPvGppnR5S62pzVWcKFbWDmEI7R3R= CBJy2cgDpP6zt3zuFvVUqhNSvrasRXixj0thmumnEiNVzBtzNa3CW9qkNR3B1OMsw= ygtzi8b8xf7uSiUYAFGUGB9z8tuqLlQwko0kZ0u1RtoUjQVy9Cr85yQW7UrPELmbo= B9uizZAaF2cdegiyVh9UHqMy3d5yFn67cvHGrgzDRXqvDJSE9gItchGbnVemU1viV= 50IyB7EHw3KZgUkkqpoECVUPwjv2cIPs8AyJ95x94LFeWb70U2tB6Dj95T2iBCuNd= hRGmBalRfARfGSlcu8afdmugoDg3fxrgS0FjqEjR7KR3sUp1G67uky0VmpYXUiCH8= AnFd1LQPj7tuqOtdem9qXWj0JW1FlWP79VRxJNFlhF1qwqWAuKFVthaD3Ft4Jaumi= lkvWVuqHO8iVTui0qaAgUESLeu4jAB6bE8a5qDygeeE8RH9ab3iZT5oHsKIrp76c1= 7gLjcANBk2GZKTwkT8wi7hzKtDGV7Q77s6KqoRYtvoy3HHIRc6vYATUPH1QzTSutU= yxD85W2a2NJJv2LVPI0l9xybUJm1pADT499a4I6atOx6b6cZ4D39t8L1Yremz0Ksa= PEmSAQ7CQRk0s0OxnWLwupVn8cDuKAs44WmrP6uNWxDgq0wrpPc3YWGpIYKodDRgo= gWwDnHgsYzWMFX7Fc4Vnp57fWIQl5AjFnRa40N27VA0mJD31DI0yVSZbOgHEQVnog= hpNM2Fp1OsO5LwjEPInzKKvSZgJ5ng0dB6sdgeA2Bx7pa63Jn01cZPvwUVNLVjDxs= AtE45oA7kYdC5HTd0InfOeMBVjkrP7hTAXACoEhBq4FQiUOeUxVBfhEmH39L49idG= j286gOlqMPJzVj1v5whcGDijdVlvvxhLraYRG7EIzatsUNLJ8gYC11ZFJPTktQUfx= X7Kk9OYSyCwaQop9BmfzEKpai8RdjfIgeUWG1pZsZKtotvTqubRtFGTdHz20XKziU= fWVrI8cnMzUg1HNeqJ8oeBx0JYrnYvfbaudyYZL2E6S7ZXGSeMw1qUGEoUIKHPphj= I5xtfgrX6J8Iq1Liy8cYdKgNy93g1kPGANgR9oZv54kbxWXTWs8Gdj6YPJU5caVLT= r8DKU9a9GS9p5gCcakzc8sgGi2ptUiU8zh5Nj81jYxxqXzJshS2QmyKYRWsSJGenX= 0POaPS2igeBVQJIiWc1g4M1w7WmG9zhi9sWJVis0Zx5k831dJAMud6TeOh3Svm9GW= jMnNZmEJ1gxGHn4V9WyNN52zIVEfzuDopnPgDqKd7KbPmy7TZXmpAS9dJO44IoaxC= 8gkyNhJclF2TddaNLgB8eOwdCxPlFuIAEcdhNkbFCdec7jwAUgX8yookJ6VfsnwQX= rf0ZS0q4Wv1zk6i1eqpxA2fOTxGpWcfGnfF4wB1fw4CTnKp0DeeW6inpZb6lk17Jg= kb4qdvDo91vpmr87FLHYiz4Sf5kuGVvWTD2ylApJBxXhRZCKXdEfqLXK6cb8a8Iev= ywJoAM5mYmKCN0fsAwsgfw7Fir9ogytPJLjsTlnrzTrod7jbVGACfXf2p468DG5pT= UT1HMze81Hm4Ira8XtAYQALvg3OefNSN2vidit87ltdfTXGCW0Fdvq2k8vqJKZTdO= y2d8WPtksDnmvCjncif8FiBtY5N3pnlAZrkVstZacS2NEXCS7lxHE59fqKaQ2qV5h= Nn4hoUIi4WMgNO1tUW4PEWTh4uIj98LXXwRAxBIqPoz9nZCW8n8uRfCRtMcTco9Wa= OihWrVjdD0fmKU4RLbMZh6HT06KoOdqfDYyGlZHrPhdfnuIS72qdnWTHBnWkaUopz= ZJLmnvLtka0TrwvoSgMMdSG5Q5Y3ngUSOGnLXvJwFJ2MTOaRqWiDCCl73GvixH63f= 74K8Jrmwf7tPTb1U6CrYggblgIgZqZXDZxLJpIHuV7muRh9uuoq5F4YRTpR1am5fa= QQlqhunVW39TGtYyMv2zSXUzUQ0QGky16k0rN4cT29J1OYcVTsnR3GiTVMvquxfBu= 8MmsxKIi8wIeTLWE4XdWHYq27w1yLpvT7wFbQtmHFyUazE11zMpz1EMamjl0J9wJ1= O6m5KNBBwh93fssu0YZ0WStKvPw7lYv1b9KyEWPZOXvnD66RSvJbxI5WDCzUhtfyL= 7S6IUQ49ZbYm66oIFfQfkus3NU2mUHkHXBwdZ8XFE2xx6AxvbbCdpirDq2UZNIehR= gpuAaJwhaAhWVXdnwaI56iEaTNWeXRWNfFQa2V0s5WfI9Gv5GChxvcKYKkHnMijiD= tGf73kBag0a2W0chRxlApi3VRpIdCGNCW4FZgYDhGmfczVOkv6VKYIebDjfDCnxAc= y6Rkc1TU4U22RmWBnIwK2EdQumXI0EiPFZ1PXZi42QUOb9LXj1fF0P9UT0QP3aTpB= dnSl7DoprIcJoFkB0pYpCOQP6VX9s1SWucXMTBcoRfz6Xaulve3KV0Zpw2ebGeXqQ= gfcHyHodzynfKSWrBDdX71tdyfRn0HCi8fHUhDWxFwlsB9MahJ4AJsJeLY8jQ0cRV= 56ub19XHGiAF1BosG6hD1yFws9jvDHEktww2iZfz6T3a8zJmJQ9UVeTwrYISQs3ZD= gcv4laHQIw8vvnTpWLNxKoeC0BjgnIDQ4wRmeinFr3dHL0WAPtUHgrTRXT4KQrtZS= irYvwaEn75HbxQZEJqTOWACD0pkdDP0AdOtzX4jigj8mcGq24570zbWIPkv7QqKi5= 6XInqGF7BxDrgrkZi8xIZ12SLKCycsPyPg5IIFEorTXDigyTb7yhdA65VPBF46V9H= 4BZlBhCt8g53ozubJm4Uxlfa0MS4ZkkYOVeEzxzQVO4k01wf6ukKReaImOlPoyuOV= 7fslQBbMdYJhVaYfCXu0A6zLwiKcKsnjgoSM4UgS9XDgqrqEmzMAZOk0FGPxQZ2LA= q1wicbHGCQDtil4S6PaGMjs4R6n5J19USF0qTmao4UnXHxmlKFK9S5O6ysq5NBXBH= IADlEYKFLBSWvmkJ2l4h02NRTRqV4BsWMfYXJZ5GZu6tVa355lLgTjGFMLrNxOAa9= Wafon02fnhvWkVJOkQJQc3syiaXyi8aTVkZ0OHIlI0w1bJsPIYcYRkWSHG5c3uXe7= C00WJ0D7o7bwqnzI7QjVb2Bn6i7Bwie3hUyIsTYYzRtcKmhiwuVDDiWzpCQqS1B6T= 8fvOQgeRkmkzoCK1P52mApZYZiP3x6ygnjC6LtFdGMiWB0105p3WzJiIfxPyqbjeO= 4c40DflpOFO73mZhPX82BGD1TQdE7Mvs48xNW0saHxK3tBcbQhBdbbcny36M1Hi1a= m3UObkPvYl4WAxiE2NQbhgSVafSTF80eJT7yhmEWMIdQ8rYwO8ZTsQS5aZEWrVPQk= PcGpJmG9Tpz31MJgm5x86MS11niIHuQSnvieh64MjKyri28cVG5QiHe2jFnm3Yrpy= GFwtuYf0KPmerIZe5M1p0AGhgUCJIIli9SCmCIqHQQyRROSXo7Ybp0y6ZedAmwh1u= 45y6CBmmky91Opr2FkAK9S9kvnnvPljywnNJjRLvCO5ro4bPLyHbGhkbVeAfeRwYe= BvqCIINy57lMHVqbyJhE8Re2BN4gwhKh6cNyKc3PTCB9Zoej93F7fk6Jho0VEx2Nn= 3Gv8RrlFrLvf43dzL6sCD2M53hmc8blzOMVIIahCjsNzAtclNlSqAaJ1Up4A58xgp= Vrh7uQAOQiaecvz41pMiUZD2UOi6HwaUw9E2VdivhBJSzMHUvv4JKXuWNecGyu7j7= gI2Qx9N6h1igLt87nAcsr9zEIeG1CXMuqKi4E4XlgDtWcF2L4zaTUQG69o7itMuke= OQ0a4sjDRcOGCs2cVW3MTzz4cUgWFRu88IoP1AZ6Qg3ESpwV45yPrxkegWX9cmXZH= FxT4dakXWWCwVcNokRzjEHBn9z5CQTti4WcRCQRVdSuBIIlJaLRuoG2XWwUE4I63s= jrYZVLu0E5McZFremr52YUnTeV6VdQvLr8ogmKeZnuJBgKWRtqIg10to34K0FyNOA= 1LRgbRBc5EubMDtYesN7eKqEZchZekOHV0eZ5Bhy73VmZdgqg2q60GlhkcgYzBYLQ= NfMouTDae0aO4FMVQJbUHGfEXESkjYv5avcYu2M9MVLGbsgxu2ISNR8607qP0jRfu= 5DztNqOX27MVytvnlQggDhjm5YnBW8t3wb6PH4GBUVKJmbrEVrFsBZRNjcnP3d0UD= IpmmFGg9ElIxAZUwJFus1swkivuGRyGUQ5EL5hgLoiXD9gJdtjjxwrCgS149bAi5E= NGul8rspJ3IuSb2Mhdye9nptoT3d6zO0SYlzfRkRR8NnULZQ1nTnKQvph1Wfnfj9f= HCTQsxqSGn0A2yCTdbJFrg1tVieU5uCPD7c86ZyQtu4tuPeskma3AtOrBqVajvNbL= bWUltMdDScWbyY53LAIkyfajKxF4oxYHSHiSk6QzWqHhRf3rP6xU4RcWMABW79eld= fjQFdJFK9n7xTsuudehZ3D0vm6JvUsMbl3BWcLBnSaUu5pT86rTUXl9Cilj7Z9QHA= VcPQyhrCT7TIwqXcBpsyRdZUZDRsuoIkcT9c3hx9ri4efTMVmUoKn9JIcVRVqZ8uo= zvDgK8jRi7z9LE6RW5AZYW39q08qCJrazPGn8ECL5S419zrgL3tUxvqDrtPJ0SfzF= pzWXIIitOU6R20RzSFyfxC4o3VFOSLcCvmKZvj2lbrIAkLptYa8cGk7NuxUM2uA3I= tmFgS4yCc36Tu4iwcQIDZVaeWvXogjHQFRQoKd56zzug1TZsCgQDSqIxbrjm6amTm= feCdTLYKC4prUd3vvM0s3Ye9jciTIZodAULFneIuRTfmj5hegRAnmqihZtUGt51CF= cQ0rn7g3vBaISQdV4DRp0RaBuFUk11MSDG7fhMSJkkQP8y7CGLoradEkGoXIdW1uO= h5bJYDhL74G0ktVyhDgClIq2MySP9wnil1QtVTI77F28YjlV1aWiLStzE8WqKsBAH= nFjCsCnV8vFFi4scXNZA4xtyhOMWinE3rrAE2iyxynCmNTm4udNEC0CPbLlEPqDLQ= BdQuNaEes1HU6KnrIs4z0rqOKshXUH8KRwbFvAG38paZUV40Xc7YybQaN2JkSHkKT= X3AzHV7M1rAhrTPog0IAabGF1StQlar5p6XSurfgZbxKfSl8UWBGC9JLmUyPsgqQZ= vRlWXTPKrAYEVq8wlWoyKsgncvzTqOILGKJ10cW3MWbyL6rupi6k2if2BYJrkWkCS= cYbG6w8ZlMOhHB644t7HoJnuGq2suIPByGy8fOiMYkGwrKTmDngtdUttAGZGtGuDW= cJ13XOgakJ42R3VwGP6smoDc4xzOCjhP3ze1SiFzZiSbprJD3aMQnaAO5OYqesy1r= eYiOUEnaxs3vsNDNWKswrrSYqV3kekxKQJasrO9vpGQHxiD1kDiH6v0N6joYA3VcV= iFICbm7BW7KAar8i2ZB2PElJnm8qaVlKEMeDVp9ga5anfcVSfGx4k95EjZePeHq0M= ZWocunDPkRKtYtbqfaunhquGAkWak2tF9BffxFLjUeZilakv3oYwVDuzrHBaqsuio= 4kmeVTzpbs2rclpZr7W4WJw6GNP4ASsJHTgQYg7uo7Jar7flcbZkyerkNfx73vOj0= jKi4z0aZrFOZlFzytRoS7asrV2II0rSjqa8nXhDaPl7yDlrAYzzDpqS8hQ8wisY0N= vzbwcBcee3M3UOAA7JrReTZh05686Rmm7L7Lg4MYnpbn64n2yVbIx8yCzTw6u37mG= pW9GOk2WstPHCbVI3AbGEOYdvcmyGtjhPGG8elJB8L4FIUWIAoqtWF2BXVbCXugZa= ySWvNuIRzySJjuAfEXi2Pk9E5aia6DDv5ua10dNTICn79RErAmjwYXkeJipCcyKVU= nEOkzfraojdW2vewRzKk6x7aViINaHaRrdLcP616RmzD6hGNb6lY0ANQwEogxD0H9= mvOJ1HKyDsKXu3EBVB4mbRQpVGaILydlStKMS3aoAqm82S2AJEC2VkYuEpOkw2N4e= p50jSJRrFLLvIn2EzY6Wbpxvf7sfPSyDhTDM1hRULAgydZV2LGW3G83Zxu3KhCBMd= 7dPJfCi7cbB9Zifcqu9WvW8QEfwd6D9Ztl5L6iv4EWuXrPycNyQ7sQIb4Z50540y2= CGDdu57Y5iysboOGkqyM1wCDUG7duYzVVVP8VYjsJ8ny9JTAgkKEsL053ZjNYUu6I= CwgyGLl653S94uaNwXadVtaUK5VFwuOEgPwcC2AyoxmI8VYv8ZrXjSM9mlNAQGABe= dSfXYaumCPo6rMO6pxw2Rlo2nQgeZIIWLtU2JyaOXAH3o2UzYuq93ymSudA7UfnT6= rlYRMnRnI4hDkEkWHfuhzTc62ywX2UHcNWWHWIc7zMlu4e9yfbc0SCxy8ROdQTkNn= 5QoHD0Y2nIMxI1NpXIQHHjbooz4TZgFry6ZoLRBbeXvTL1pQ0OTbt5FLEZj4V4363= lZB2pD56FtJOhDn9dSbmuYsrdJLyxf9UoQp1NOBaO4NCWXmlVUHcSKynxaOGSwzqj= Oqrdlmph0yqaPugmpCCxX2Eh2uCZUihuni7xV8AyiURb8cHFyjsUWSmMLaaRJpmIh= VMwnIrh24f3bt8QMWrBPmxvWlLLXJOSx9TdqbiPSaRSDjBi1k4MYLSUngz1WFkjfn= v1zVpBECIEvFSDKtKCE2UMgYQ9BgSdQyCfNzI5Vt8l3dpHoWhtVIEdtIKB5f0nKvO= W2CPaKEGaTyJ3y8KEZoh8TpM5O70FtKBxptFM66Jh1ujUZH2XuloldF2DPKmDD0G9= WbD5tXySF07p5R6643a8mgkJr1XmK5D0NaYN3XuxNwGdyCxXEfyzQyMGRUDr0c7zm= 6BVTi26zDlQA6aOu0Hvw4aenhW9j2wBo6Rs0B3mcr0cdW6KJPW0uC2iWnxCmTMw6J= stfINSWli53X1rabpu6w6L3zvD4rZjFt5tuDv11338kXeYl6rbtiqADGqFcaOulZp= zSxXxFot2sXr5lwhX0OPm3vQNdPORfzMlxE6O9Tv5On7FfkkFSQux93wmH9kPzCNT= a5yGqtO6iKyGoaxSu8Yo4fcu7J7ZzGvczdu9LEfp2ofouQYwBrkrEpOVT3yGmPwCf= m6aGn6QTzmG0NZhKAn7l4xaoygI5y3dRC98JOQdkuy528V63gVLrphbOVL77oLkv9= OnERyWK9MQvs8gDaEOCiLslXkN3I6WJdzTkyrcIZ0hCqFlNvuXJWHdnm2GxKT23Q7= iTeV5Is6DhuPUiY0ye8cMvlvXvKFX6YdMimsyzpfhQ4WTx7oyKkOUElMxJYzXM8wj= g3BVwrYOTUWqpCqnm6dLaj7XzUPBPhuIyCCtws2jlZ0Kom77xbBGUK9XVDlBCnZCp= eSNZWRT4UpainydMI3DGONNtExS7qHXZokatk7BkHB0kYFy57PUklWAq5jloYMEdr= bT2nKsAsjYdMsvZZNZBMDEsKKo0MclVWNSNMwHnmjS2XmDCOlpbM3qOwqhDmrOfX3= gZzHct6CetKCvn6LbqNa8Tm4gle31VvC4T6E379W4aOW4UVUxAfnsNVnDvqRf3BjY= 7yChrH4hR5Y4pZmqjvqF7agYI1yGhG1zvYWljC6Sb6BIXjdv4rVybERXhDyq9oZa4= pyr307Hpxu0yy1pN2BQLsnR7Y4F3FIM6rExKMs3ke9D9QpJC9D7M9oB1Hj4WrDJOH= U6UtF1AywxjKHhzk2U2B0X33w2sn6SApPsViP9uBxdCQhh02uCpIHcHX3RWCzcrEW= UUflhvSqq4MkcLf2pTusSHCKYeYdR1kMYTnmKGc6wig8VCQ5Gz9jXb4ciun2xFyoJ= ZlioThIGnWzruPmnSwiS1ONPb4gj9zRJSoVgyHNhrCzfuLOF0FE8fwIaytcO1pwO4= Py5T5PbI1qpfylqgBiuUJu From owner-freebsd-questions@freebsd.org Thu Feb 1 03:18:03 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E39FAED4569 for ; Thu, 1 Feb 2018 03:18:02 +0000 (UTC) (envelope-from bo-b2cf62tbfe23pyaudbb2kbydx4a0sj@b.marker.advfromnwl.com) Received: from mta952.chtah.net (mta952.chtah.net [8.7.44.148]) (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 423AD872BF for ; Thu, 1 Feb 2018 03:18:02 +0000 (UTC) (envelope-from bo-b2cf62tbfe23pyaudbb2kbydx4a0sj@b.marker.advfromnwl.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marker.advfromnwl.com; s=20170929051602; t=1517455082; x=1533093482; bh=W4hVWyobrXGpp/iLVw97Jx2xD8Q02iZoB5kBdcnykTE=; h=From:Reply-To; b=1SConkaPHn7DpQHagfk8yCeL8omYbtlsauibrxdMDyMg3ErFmTKlAi+ulyzY+mjmH zgWlwOOUQT161Rj79gufebkTiL8aVKfwiBhj3Y5YIAkx6/50I8zo22JgBksY0sWSOL AojZhkekK1D8ck8LB2YXvXKLrrDVsbmXRo7O6JB+PKcA6okzBj3eHzajA2fY64WHFR niOuIFKaGMUdAqFK9CJ+X1l0op33Z2oYayxtQpUPEWkZMg2fJ99O3fThjcysgMEViu W/H4n0AbE1BNiaQGcNSF3ICig1DgEZ+Os4/18hVRiBSL92EYcheKjTSLqmzxzdrqYi PRn2BtEB3fruw== Date: Thu, 1 Feb 2018 03:18:02 -0000 Message-ID: From: "KangooSave" To: freebsd-questions@freebsd.org Subject: =?UTF-8?B?V2hlcmV2ZXIgeW91IGFyZSwgYWNjZXNzIEFMTCB5b3VyIGNvbnQ=?= =?UTF-8?B?YWN0cw==?= MIME-Version: 1.0 Reply-To: "NoReply" X-Mailer: CheetahMailer X-mid: 2106732779 X-aid: 2094058101 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 03:18:03 -0000 KangooSaveBusiness KangooSave your smart adress book presents. See in browser : http://ebm.cheetahmail.com/c/tag/BaceWbB80Mp1B9kjDrAA3HbJ25/doc.html?t_params=OysNZtmkEd0hQ5PKV1YuADWoEzzQWVDkgE$n8umG9HLVcchhLnT0N3X9cB5B6ekLUA1qsFwPY3iiaM2ueMPsgjjirAa38AlU8KG http://marker.advfromnwl.com/a/tBaceWbB80Mp1B9kjDrAA3HbJ25/ksb1?email=freebsd-questions@freebsd.org http://marker.advfromnwl.com/a/tBaceWbB80Mp1B9kjDrAA3HbJ25/ksb1?email=freebsd-questions@freebsd.org Problems with rotation of the sales teamAre over! Kangoosave.com : http://marker.advfromnwl.com/a/tBaceWbB80Mp1B9kjDrAA3HbJ25/ksb1?email=freebsd-questions@freebsd.org All mobile activity of your sales forceIn just one place! 100% in the cloud without introducing information as a CRM ✓Always up-to-date and secure customer data ✓Easy to use and dynamism for all ✓Speed in outbound and coworkers entries ✓Productivity, without reporting ✓Plan and control of actions in real time http://marker.advfromnwl.com/a/tBaceWbB80Mp1B9kjDrAA3HbJ25/ksb1?email=freebsd-questions@freebsd.org The personal information contained in this and future messages are processed by MakeMailing in accordance with the principles of proportionality and quality required by the regulations in this area. Your information will not be shared with third parties under any circumstances. At any time, you may revoke the consent subject to the receipt of commercial communications by electronic means, and exercise the rights of access, rectification or cancellation you can send email to info@makemailing com. You can also exercise your right to opt out of receiving newsletters by clicking on the link : http://ebm.cheetahmail.com/r/webunsub?t=BaceWbB80Mp1B9kjDrAA3HbJ25&aid=2097091387&n=1&email=freebsd-questions@freebsd.org . From owner-freebsd-questions@freebsd.org Thu Feb 1 11:13:03 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1106CEE165E for ; Thu, 1 Feb 2018 11:13:02 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0569984B7C for ; Thu, 1 Feb 2018 11:13:01 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.213.55]) by mrelayeu.kundenserver.de (mreue007 [212.227.15.167]) with ESMTPA (Nemesis) id 0LdyNE-1f6Jrc26e4-00pucC; Thu, 01 Feb 2018 12:12:52 +0100 Date: Thu, 1 Feb 2018 12:12:51 +0100 From: Polytropon To: C Gray Cc: freebsd-questions@freebsd.org Subject: Re: sound-card/driver question Message-Id: <20180201121251.95e345cf.freebsd@edvax.de> In-Reply-To: <8F08E935-33A8-4B5F-9057-51FAD51DA97D@council124.org> References: <8F08E935-33A8-4B5F-9057-51FAD51DA97D@council124.org> 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-Provags-ID: V03:K0:Ko+oA+y953rzirol71f4ijAKv88zCF5pYB26WYbjA28T6M4dL4I GtINJcjQIs+WUM/LvvqgVGG1Bcf9HBbe2+5xz+9pavHPiyIPm4d3qRuH/CBCmOLj5+G3LCQ MldBd9UsgzDSIjV7CvphIg69BiKdWlFQHYADXoxhLy2F87qRHym6jpcNq2/GLY4I/GLt2hL eTdlOSGHeGTa4+yUMa74w== X-UI-Out-Filterresults: notjunk:1;V01:K0:TasIIAXVD5g=:VNaoDxcZho8ZhcvjdzrdpG orv9Egze7K5x5SoTOq+rrZtTxt/FjDLeETJdtkBoqzfWsOJdaf1p9GV2QVdRHTAUx5n61D7XP Pc28PJrk/zk2jteAo+n26dwBMaK4z/LPI5ZQ8N/+NVa/QiwMBOAYT7Dku+lcJCJLqmrj+eozY 7DDs5jQwKNyWGkJ3Z3XUMOyXfFMl6vpzpQmATmr6VRgqw/Vv6B82F53Wxi+IcqdF2bYyXRK/B ub9CRadIviFtEsaMx5x4wQll4bUJ85QTPj7+1vfRp7knBYPwuOsUghMJ/UsgHxNZsV9vIesET ZvagAa9dsd7PTmQErxwlg8z4OUHZjxBLbRAWgfKezWpcwMCEC+6Ye+mATf0nRYH66YBCCsVp/ jfKqtDlGRQVzBxfP0vR+S04FUoc8PLtE3nVuME56I58sAgc7HdOklWaqpMREoGw5cAE5ZmZdQ axhOAtcY5K4zAim3Fglh3mTTBdC1ckblaCvBxDlzk/tggG5LvomEiso/Lf9oRV8OdrZTxKEF4 KBvhEFKVm/fdjmvL+grg16RjkbxF7QO5Q3NLyuEfnqv9tqNK1xbYY2b5bwcYf6KElKQXReKgI lAxhaUqciK6WqoGdbs+YDleStKT2Phnhh6EsIGn9dIfsz842nbWGkXH3kq1mhnL2+tRLzMftm 0FBKgmP5LxqYqjOBye8JDyKo2J6xu5T/Bv8l17/AxejoUXCsGImOf8dDhJhi2bBHms/NFKOjQ w9uZCaodrNGl5zSRaZUlI3Ex42To8ZkyIYNKWFsICoFjN9McmLeBSiOl7rM= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 11:13:03 -0000 On Wed, 31 Jan 2018 15:02:30 -0800, C Gray wrote: > I have a Dell PowerEdge T300 server which has the following slots available: > slot 1: 3.3-V, full-length PCIe x4 with x8 connector > slot 2: 3.3-V, full-length PCIe x4 > slot 3: 3.3-V, full-length PCIe x8 > slot 4: 3.3-V, full-length PCIe x8 > slot 5: 3.3-V, full-length PCI-X > > The system is based around: > Xeon X3440 @ 2.50 GHz Quad core > 2GB DDR3 RAM. > > It's been said that a driver supported for Vista will work with for FreeBSD. That sounds very strange. Both systems are so fundamentally different in architecture and binary interfaces. > The card I am looking at works with Microsoft Windows7, Vista, and XP. > It's PCI-X based, and would, thus, be inserted into [my] slot 5: > Creative Sound Blaster X-Fi Xtreme Gamer SB0770 7.1-Channel > PCI Sound Card > > My question is whether the CD of sound card drivers are in a > standardized format such that, > FreeBSD/TrueOS can use them, as is, just as the Microsoft-verified > environments do? Probably not. But it's not needed. FreeBSD provides the drivers needed and loads them automatically at system startup once the hardware has been detected properly. There usually is no need to manually download or install something. I've been using Creative Labs SoundBlaster cards in the past, and the OS automatically loaded the correct driver. You can easily verify this with # pciconf -lv | less and # cat /dev/sndstat The sound card should then be listed, and the corresponding driver right next to it. SoundBlaster cards have a long tradition of out-of-the-box support on FreeBSD. Even on Linux, ALSA seems to provide support for this particular card. > Do they even use the same suffix? What kind of suffix are you talking about? > Are they well-written enough to discover the platform whereon > they are expected to run (*that is, to "drive"). Probably not. Drivers made for "Windows" will only work on a specific subset of "Windows" versions, i. e., the "driver system" they have been created for. So their use is even limited within the "Windows" ecosystem, and outside of it, they are more or less useless. > It the OS discovers the driver rather than the driver > discovering the OS, the same functional use may be achieved, > however, I'm ignorant other than > guessing as to how drivers work and what is required for that > to take place. As I said, manually supplying drivers is not needed on FreeBSD because the drivers are already there. The OS discovers the hardware and loads the driver. Simple and easy. :-) > Where are they stored in Windows and in FreeBSD, and how do I > install the proper one from the > disk accompanying the card (most likely meant for Microsoft's > toolset/installer. You don't. The OS already has the drivers installed. > Suggestions? If you have the card at hand, install it as recommended into the system and boot FreeBSD. With the commands mentioned above, check if (a) the device has been recognized, and (b) the appropriate driver has been loaded. There isn't much more you have to do, as FreeBSD is a "plug & play" OS. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Thu Feb 1 11:05:35 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BAFFDEE066F for ; Thu, 1 Feb 2018 11:05:34 +0000 (UTC) (envelope-from mary.johnson02@weboptimizes.com) Received: from mail-oi0-x243.google.com (mail-oi0-x243.google.com [IPv6:2607:f8b0:4003:c06::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 4A4EC84395 for ; Thu, 1 Feb 2018 11:05:34 +0000 (UTC) (envelope-from mary.johnson02@weboptimizes.com) Received: by mail-oi0-x243.google.com with SMTP id 24so10010997oij.3 for ; Thu, 01 Feb 2018 03:05:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=weboptimizes.com; s=google; h=mime-version:sender:from:date:message-id:subject:to; bh=mSa18FferUgkr8HtMCGSb1gp0YvequrLK9okDIdHiss=; b=AmLSCLYo8WmGmOaQbw4HexIJd6jcwjeghQOQoqeWX5Wv6TR/sxqvz4Qrtq89rTT0TX Ae9kniIGQCG7johLm/+zc+7OrGV//pT18BZ6s2wGnF1ZxInVG8A58ylDTVwgV4YY+DzO FWa3NhO9C3wOVZ7jNJcBgSDucmZnyOKYxMZfk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=mSa18FferUgkr8HtMCGSb1gp0YvequrLK9okDIdHiss=; b=Or/h0hVA+UqdE2voihfNbnMZ0Q+7Uwl/HIvuxpLw4SuoIvBlCUhz3cZn/ICQHd172v 1mpz3lGMo2nuplfAeYWNFZImEflWWnDKhwaiphBAXF03PtntHAdHNiM0DEZ3i8kRA6ri F7DsEmNxXXz89pUlhKBhxpwm3xPDSoQoSosfZEvTYRF6+EG2V9h+udISk+YnxRANAt05 kPOBqPuEQChKMHVTtjdJ4xBaKYWT5GmYOGbgNBwaiDNa2czk6QqHX3Bj6QF9ruykvHy5 Mw/MQLPT6HMoqYExw1rU2L5R9yavNjKeehRFXgzBWzFmLtbJANTDY/+1e7LKHY5vBav0 V7sw== X-Gm-Message-State: AKwxyte6Pn78GdCs4kIRqWFtDG0jY1M8pTq3tB8KuDH5ovGlXrfS0djw POLlDIUReMh/IRWAKg6EXGg0AzqauXhkQPh0kKHnow== X-Google-Smtp-Source: AH8x225tza4oZDllK4wtwWy6Gk1qMUVxY0MbL81UhhJ8JXkafkAxHZzpw4ax+JmR3/vTPX4airjxvxeaXyCPvfiE99Q= X-Received: by 10.202.207.151 with SMTP id f145mr9575305oig.263.1517483132887; Thu, 01 Feb 2018 03:05:32 -0800 (PST) Received: from 52669349336 named unknown by gmailapi.google.com with HTTPREST; Thu, 1 Feb 2018 03:05:32 -0800 MIME-Version: 1.0 Sender: Mary Johnson From: Mary Johnson Date: Thu, 1 Feb 2018 03:05:32 -0800 X-Google-Sender-Auth: W0ROS_wD0Hx_m_F2LZaJYehv1qs Message-ID: Subject: Do you know what your website is doing wrong? To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 11:05:35 -0000 Hi *freebsd.org *, *Are you looking for a reliable, creative and experience team for the web designing or redesigning of your website???* AS we know *freebsd.org *is the reflection of your business, Do you want to put your business model and creative ideas in the design of your website? We will match your business goal with our creative ideas. We are one of the reputed companies with finely crafted creative and strategic designers and develop an SEO friendly website to give meaning to your Online business. We have innovative web solutions for organizations including *Advanced Database Interactivity* *& database design, e-commerce solutions, Flash design*, *HTML/D-HTML**, **Programming in PHP, ASP.Net**, **Logo Designing, Mobile/Tab Responsive Design. **with programming* etc. *Problems with your original site:1. You can=E2=80=99t control your site or= change content2. Search engines can=E2=80=99t find you3. Your site has outdated technology4. Out dated looking5. No call to action6. Slow load times7. No Dynamic content* So if you are *interested* we want to *Design and Develop your website* with Latest *newly added features* that might benefit the overall usability and user experience which usually leads to better sales! We could lower that cost and not compromise on quality! *Waiting for your positive reply!* bsite design, Mobile Apps and Software. Regards *Mary Johnson* Sr. web consultant. [image: beacon] From owner-freebsd-questions@freebsd.org Thu Feb 1 12:27:51 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3AB6BEC3E1C for ; Thu, 1 Feb 2018 12:27:51 +0000 (UTC) (envelope-from Tim1Kopplow@bundeswehr.org) Received: from Mail201.bwehr.de (mail201.bwehr.de [91.221.58.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailprz.bwehr.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7FDDA87FEF for ; Thu, 1 Feb 2018 12:27:49 +0000 (UTC) (envelope-from Tim1Kopplow@bundeswehr.org) Received: from zdstbmta01.rz-dienste.rzsrv.svc (unknown) by Mail201.bwehr.de with smtp id 74d5_1484_782dc0f8_6e8d_4eda_a090_7ad7594dbd03; Thu, 01 Feb 2018 13:17:28 +0100 To: freebsd-questions@freebsd.org MIME-Version: 1.0 Subject: FreeBSD Proxy Madness X-KeepSent: 0A46FBAF:E1582018-C1258227:004120DE; type=4; name=$KeepSent Message-ID: From: Tim1Kopplow@bundeswehr.org Date: Thu, 1 Feb 2018 13:17:10 +0100 Content-Type: text/plain; charset="US-ASCII" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 12:27:51 -0000 Hello there, I'm super new to FreeBSD and i really enjoy using it so far! Our environment is behind a proxy which makes things "interesting" all the time. I'm coming from Linux and expected issues with proxy usage but at first everything went smoothly (using pkg, git, npm) with just giving Environment Variables like: HTTP_PROXY=http://username:password@proxyurl:port Today i encountered that freebsd-update, which is using phttpget, doesn't like it like this Instead it requires: HTTP_PROXY=http://proxyurl:port HTTP_PROXY_AUTH=basic:*:username:password to be set. Which atleast makes git and npm not work again. Probably because git and npm and mainstream applications like this are coming not necessarily from bsd work where i first encountered HTTP_PROXY_AUTH usage. So it is atleast understandable to some degree. So far my experience with FreeBSD and proxy usage. Now, since this is the Question Mailinglist here comes my Question: "What is wrong with fetch??" This little piece of software says that it respects all the stuff (according to the man page). It says it respects, http_proxy, HTTP_PROXY, HTTP_AUTH, HTTP_PROXY_AUTH basically everything. But it's just not working. I looked already at the source of "Fetch" an the only thing regarding proxy i can find is a little code about "noproxy". TBF i don't know if i looked at the right place since the webinterface of the svn isn't the most userfriendly place in existance but i tried. So What's the deal with Fetch? Am i missing obvious Points or did i just gone mad already? Oh and is there a IRC i can join to discuss stuff like this? Thanks in advance. From owner-freebsd-questions@freebsd.org Thu Feb 1 15:23:18 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9FA49ED77FF for ; Thu, 1 Feb 2018 15:23:18 +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 4A711711B1 for ; Thu, 1 Feb 2018 15:23:17 +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 6D7E7624E4 for ; Thu, 1 Feb 2018 10:23:11 -0500 (EST) 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 P-1bNjen3z_G for ; Thu, 1 Feb 2018 10:23:09 -0500 (EST) 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 16AA0624DA for ; Thu, 1 Feb 2018 10:23:09 -0500 (EST) Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Thu, 1 Feb 2018 10:23:09 -0500 Message-ID: <05940d076ac711b2c9b740451706c5d4.squirrel@webmail.harte-lyne.ca> Date: Thu, 1 Feb 2018 10:23:09 -0500 Subject: EZJAIL and ping on FreeBSD-11. From: "James B. Byrne" To: 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 15:23:18 -0000 I have read the various 'howtos' respecting this issue and I cannot see where I have failed to properly follow the instructions. But clearly I have not done it right. I have setup a jail named hll124. it is configured and running. It can connect to the network and the Internet without issue. DNS resolution works fine using local_unbound. In /etc/sysctl.conf on the host I have this: # $FreeBSD: releng/11.1/etc/sysctl.conf 112200 2003-03-13 18:43:50Z mux $ # # This file is read when going to multi-user and its contents piped thru # ``sysctl'' to adjust kernel values. ``man 5 sysctl.conf'' for details. # # Uncomment this to prevent users from seeing information about processes that # are being run under another UID. #security.bsd.see_other_uids=0 security.bsd.see_other_uids=0 security.bsd.see_other_gids=0 security.bsd.unprivileged_read_msgbuf=0 security.bsd.unprivileged_proc_debug=0 security.bsd.stack_guard_page=1 # Required for Chrome/Chromium kern.ipc.shm_allow_removed=1 # Add to allow jails to create sockets - 2018-01-31 JBB security.jail.allow_raw_sockets=1 The host system shows this: $ sudo sysctl security.jail.allow_raw_sockets security.jail.allow_raw_sockets: 1 In the ezjail configuration file I have this: # Allow ping, traceroute and other things 2018-01-31 JBB export jail_hll124_allow_raw_sockets="YES" When I connect to the ezjail instance with ezjail-admin console and run ping then I see this: # ping 192.168.71.44 ping: ssend socket: Operation not permitted What else am I missing? -- *** 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 Feb 1 15:40:00 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9B3CED8998 for ; Thu, 1 Feb 2018 15:40:00 +0000 (UTC) (envelope-from johannes-maria@t-online.de) Received: from mailout06.t-online.de (mailout06.t-online.de [194.25.134.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 591E87228B for ; Thu, 1 Feb 2018 15:40:00 +0000 (UTC) (envelope-from johannes-maria@t-online.de) Received: from fwd12.aul.t-online.de (fwd12.aul.t-online.de [172.20.26.241]) by mailout06.t-online.de (Postfix) with SMTP id 1D24741EA181 for ; Thu, 1 Feb 2018 16:39:58 +0100 (CET) Received: from t-online.de (XL0X0BZUYh3+kngK9JKxlsG6toNKwC4tCkevhEv2A6k-ltxvBkymJboGwjh0VeVZDJ@[84.145.228.58]) by fwd12.t-online.de with (TLSv1:DHE-RSA-AES256-SHA encrypted) esmtp id 1ehGxl-3EDFmC0; Thu, 1 Feb 2018 16:39:45 +0100 Received: by t-online.de (nbSMTP-1.00) for uid 1001 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-SHA (256/256 bits)) johannes-maria@t-online.de; Thu, 1 Feb 2018 16:39:45 +0100 (CET) Date: Thu, 1 Feb 2018 16:39:44 +0100 From: johannes-maria@t-online.de To: freebsd-questions@freebsd.org Subject: Re: problem with upgrade and unable to build openjdk8 in poudriere Message-ID: <20180201153944.GA5998@localhost.org> References: <20180115151549.GA9923@localhost.org> <20180128130433.GA2196@localhost.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180128130433.GA2196@localhost.org> User-Agent: Mutt/1.4.2.3i X-ID: XL0X0BZUYh3+kngK9JKxlsG6toNKwC4tCkevhEv2A6k-ltxvBkymJboGwjh0VeVZDJ X-TOI-MSGID: 5edbf8d9-755f-4c7e-a7a3-289b2a119002 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 15:40:00 -0000 Hello, a supplementation to the first problem in my question to the list: > On Mon, Jan 15, 2018 at 04:15:49PM +0100, johannes-maria@t-online.de wrote: > First problem: > > One of the ports to install is x11/kde4 which as a dependency > adds java/openjdk8 to the list but poudriere seems to be > unable to build it: > =>> Failed ports: java/openjdk8:build > [excerpt from the log-file: > gmake[2]: *** No rule to make target '1'. Stop. > gmake[2]: Leaving directory '/wrkdirs/usr/ports/java/openjdk8/work/openjdk/langtools/make' > ] > > And therefore > =>> Skipped ports: devel/antlr devel/kdesdk4 devel/poxml x11/kde4 > > On the other hand a direct make in ports/java/openjdk8 is successful > but it fails repeatedly when called by poudriere. I should have been a little bit more detailed: when I said > On the other hand a direct make in ports/java/openjdk8 is successful I meant the ports tree of the 11.1 basic system in /usr/ports > but it fails repeatedly when called by poudriere. and here poudriere used the tree /var/poudriere/ports (also 11.1). Both trees were updated at the same time and the files in java/openjdk8 were identical in both trees (except for 'work'). After the stop with error by poudriere I performed the make in /usr/ports/java/openjdk8 (not in the identical tree /var/poudriere/ports to not destroy any data for poudriere). Only now I tried a 'make' in poudriere's ports tree and this time I also got an error (as in the poudriere run). (And I repeated the make in /usr/ports successfully). I've no idea why a make in two identical ports differ so much. Best regards, Johannes-Maria From owner-freebsd-questions@freebsd.org Thu Feb 1 15:50:36 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B20EEED9676 for ; Thu, 1 Feb 2018 15:50:36 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from kicp.uchicago.edu (kicp.uchicago.edu [128.135.20.70]) by mx1.freebsd.org (Postfix) with ESMTP id 6441A72E1D for ; Thu, 1 Feb 2018 15:50:36 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from point.uchicago.edu (point.uchicago.edu [128.135.52.6]) by kicp.uchicago.edu (Postfix) with ESMTP id 635EE718049; Thu, 1 Feb 2018 09:50:35 -0600 (CST) Subject: Re: EZJAIL and ping on FreeBSD-11. To: byrnejb@harte-lyne.ca, freebsd-questions@freebsd.org References: <05940d076ac711b2c9b740451706c5d4.squirrel@webmail.harte-lyne.ca> From: Valeri Galtsev Message-ID: <2e179f4e-8811-25b2-081c-906d13149129@kicp.uchicago.edu> Date: Thu, 1 Feb 2018 09:50:35 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <05940d076ac711b2c9b740451706c5d4.squirrel@webmail.harte-lyne.ca> 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 15:50:36 -0000 On 02/01/18 09:23, James B. Byrne via freebsd-questions wrote: > I have read the various 'howtos' respecting this issue and I cannot > see where I have failed to properly follow the instructions. But > clearly I have not done it right. > > I have setup a jail named hll124. it is configured and running. It > can connect to the network and the Internet without issue. DNS > resolution works fine using local_unbound. > > In /etc/sysctl.conf on the host I have this: > > # $FreeBSD: releng/11.1/etc/sysctl.conf 112200 2003-03-13 18:43:50Z mux $ > # > # This file is read when going to multi-user and its contents piped thru > # ``sysctl'' to adjust kernel values. ``man 5 sysctl.conf'' for > details. > # > > # Uncomment this to prevent users from seeing information about > processes that > # are being run under another UID. > #security.bsd.see_other_uids=0 > security.bsd.see_other_uids=0 > security.bsd.see_other_gids=0 > security.bsd.unprivileged_read_msgbuf=0 > security.bsd.unprivileged_proc_debug=0 > security.bsd.stack_guard_page=1 > > # Required for Chrome/Chromium > kern.ipc.shm_allow_removed=1 > > # Add to allow jails to create sockets - 2018-01-31 JBB > security.jail.allow_raw_sockets=1 > Yes, I'm sure you need that > > The host system shows this: > > $ sudo sysctl security.jail.allow_raw_sockets > security.jail.allow_raw_sockets: 1 > Good. > > In the ezjail configuration file I have this: > > # Allow ping, traceroute and other things 2018-01-31 JBB > export jail_hll124_allow_raw_sockets="YES" > I don't know much about ezjail... but this sounds to me as pertinent to one particular jail with the name "hll124". I set up jails "by the book". To enable access to raw sockets in _all jails, I have somewhere in the configuration pertinent to all jails (i.e. not inside particular jail settings) in /etc/jail.conf the line allow.raw_sockets = 1; If you wan to give that only to some jail, add this only inside jail specific configuration in the same /etc/jail.conf, e.g.: db { host.hostname = "example.uchicago.edu"; allow.raw_sockets = 1; ... } I hope, this helps. Valeri > > When I connect to the ezjail instance with ezjail-admin console and > run ping then I see this: > > # ping 192.168.71.44 > ping: ssend socket: Operation not permitted > > What else am I missing? > -- ++++++++++++++++++++++++++++++++++++++++ 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 Thu Feb 1 16:02:03 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 29F0EEDA432 for ; Thu, 1 Feb 2018 16:02:03 +0000 (UTC) (envelope-from jude.obscure@yandex.com) Received: from forward105p.mail.yandex.net (forward105p.mail.yandex.net [77.88.28.108]) (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 AC7B3738EE for ; Thu, 1 Feb 2018 16:02:01 +0000 (UTC) (envelope-from jude.obscure@yandex.com) Received: from mxback7o.mail.yandex.net (mxback7o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::21]) by forward105p.mail.yandex.net (Yandex) with ESMTP id C95704084D72 for ; Thu, 1 Feb 2018 19:01:53 +0300 (MSK) Received: from smtp3o.mail.yandex.net (smtp3o.mail.yandex.net [2a02:6b8:0:1a2d::27]) by mxback7o.mail.yandex.net (nwsmtp/Yandex) with ESMTP id WGTGhRhjv8-1rjarLcu; Thu, 01 Feb 2018 19:01:53 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1517500913; bh=1IjVEqGzUkebpQ+kxQtuTR8zTFrVoG7k31JQnqxhrBA=; h=To:From:Subject:Message-ID:Date; b=L/Cu2HsUquKM2VAgHD/vHEib3Lakvew5LDWeOQCcNQhKdheDDQIa/5O53ziDfu/O9 mm8lZ9eAHEueXzETZEpLFU/bRKjlOQg2ravgDKKMkWLpQ8Q58cEyiXE/TtrfsMiPQO cvrN9PdgMPAYOXjmBQnZkwziZ/e4vkLmBf/21jtg= Received: by smtp3o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id E5Ih4g6w6H-1qd4VZgd; Thu, 01 Feb 2018 19:01:52 +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.com; s=mail; t=1517500913; bh=1IjVEqGzUkebpQ+kxQtuTR8zTFrVoG7k31JQnqxhrBA=; h=To:From:Subject:Message-ID:Date; b=L/Cu2HsUquKM2VAgHD/vHEib3Lakvew5LDWeOQCcNQhKdheDDQIa/5O53ziDfu/O9 mm8lZ9eAHEueXzETZEpLFU/bRKjlOQg2ravgDKKMkWLpQ8Q58cEyiXE/TtrfsMiPQO cvrN9PdgMPAYOXjmBQnZkwziZ/e4vkLmBf/21jtg= Authentication-Results: smtp3o.mail.yandex.net; dkim=pass header.i=@yandex.com To: "freebsd-questions@freebsd.org" From: Manish Jain Subject: Do Radeon HD 5450 graphics work under FreeBSD ? Message-ID: <9dffe9ca-8e6a-8016-8ee1-fe354ea21cc3@yandex.com> Date: Thu, 1 Feb 2018 21:31:48 +0530 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 16:02:03 -0000 Hi, I need to find out a low cost Radeon card that works under FreeBSD and is generally available in the US. XFX ATI Radeon HD5450 (1 GB; USD 34) seems to be a good candidate, but I have no idea whether this card works under FreeBSD ? Does anyone on this list use Radeon HD5450 ? Or is certain that the FreeBSD radeon driver would support the chip ? -- Thanks for any information. Manish Jain From owner-freebsd-questions@freebsd.org Thu Feb 1 16:13:49 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4A49AEDAFFE for ; Thu, 1 Feb 2018 16:13:49 +0000 (UTC) (envelope-from sysadmin@grouchysysadmin.com) Received: from outbound00.knthost.com (outbound00.knthost.com [209.195.10.81]) (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 E7AC0744A6 for ; Thu, 1 Feb 2018 16:13:48 +0000 (UTC) (envelope-from sysadmin@grouchysysadmin.com) Reply-To: sysadmin@i.grouchysysadmin.com DKIM-Filter: OpenDKIM Filter v2.10.3 outbound00.knthost.com CA1DD51880 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=grouchysysadmin.com; s=default; t=1517501308; bh=76UaYyxgY/JIt9Qh2JFQQo6saOdtdXU1yqrEAjtIrbc=; h=Reply-To:Subject:To:References:From:Date:In-Reply-To; b=o6ik6eNtDaGRUyAWmzwVyhNEN/xtgc3oJ3cIlG+ofX3oHoEgGRug6ZAgVB3HM9wnr lFd74uSZ6tCcF+Xqm6qGCtRIoNZixAnjKyZT+U+hZb85Tr/0Vlprl+a2hWIqvanOHB huqhX+U4sImzzdwOl4XccXUU264KNuBrX1Tqo4cW8QUe/4TxsXes3pmayfhRb4Gpn1 XRrOac+m7yHYHq29g05vu+ATdekPYmpNhFjwMc60H+gHHzCG0OuLvFK6Q47zKmVGaP QbYz7yV5Zy1u6OTI5yYzDPaEShH8y45xLpN+8dttLtM8aiaWqg5KM0hEMGo6gy2w4w WRpiWblFqNL0A== Subject: Re: EZJAIL and ping on FreeBSD-11. To: freebsd-questions@freebsd.org References: <05940d076ac711b2c9b740451706c5d4.squirrel@webmail.harte-lyne.ca> From: Grouchy Sysadmin Message-ID: <0fe114e1-bc87-db17-ed24-8035bb1582b1@grouchysysadmin.com> Date: Thu, 1 Feb 2018 10:08:25 -0600 MIME-Version: 1.0 In-Reply-To: <05940d076ac711b2c9b740451706c5d4.squirrel@webmail.harte-lyne.ca> 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 16:13:49 -0000 On 02/01/2018 09:23 AM, James B. Byrne via freebsd-questions wrote: > I have read the various 'howtos' respecting this issue and I cannot > see where I have failed to properly follow the instructions. But > clearly I have not done it right. > > I have setup a jail named hll124. it is configured and running. It > can connect to the network and the Internet without issue. DNS > resolution works fine using local_unbound. > > In /etc/sysctl.conf on the host I have this: > > # $FreeBSD: releng/11.1/etc/sysctl.conf 112200 2003-03-13 18:43:50Z mux $ > # > # This file is read when going to multi-user and its contents piped thru > # ``sysctl'' to adjust kernel values. ``man 5 sysctl.conf'' for > details. > # > > # Uncomment this to prevent users from seeing information about > processes that > # are being run under another UID. > #security.bsd.see_other_uids=0 > security.bsd.see_other_uids=0 > security.bsd.see_other_gids=0 > security.bsd.unprivileged_read_msgbuf=0 > security.bsd.unprivileged_proc_debug=0 > security.bsd.stack_guard_page=1 > > # Required for Chrome/Chromium > kern.ipc.shm_allow_removed=1 > > # Add to allow jails to create sockets - 2018-01-31 JBB > security.jail.allow_raw_sockets=1 > > > The host system shows this: > > $ sudo sysctl security.jail.allow_raw_sockets > security.jail.allow_raw_sockets: 1 > > > In the ezjail configuration file I have this: > > # Allow ping, traceroute and other things 2018-01-31 JBB > export jail_hll124_allow_raw_sockets="YES" > > > When I connect to the ezjail instance with ezjail-admin console and > run ping then I see this: > > # ping 192.168.71.44 > ping: ssend socket: Operation not permitted > > What else am I missing? > You don't need to allow raw sockets globally. I'd leave it set as, "security.jail.allow_raw_sockets=0". Then allow raw sockets on a per jail basis by changing the parameters in the ezjail configuration. For example, add this to the /usr/local/etc/ezjail/hll124 file. export jail_hll124_parameters="allow.raw_sockets=1" Stop the jail, and then start it for the setting to take effect. From owner-freebsd-questions@freebsd.org Thu Feb 1 16:30:49 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 992EDEDC257 for ; Thu, 1 Feb 2018 16:30:49 +0000 (UTC) (envelope-from stoa@gmx.us) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 ED414759E8 for ; Thu, 1 Feb 2018 16:30:48 +0000 (UTC) (envelope-from stoa@gmx.us) Received: from fedora27 ([97.66.214.165]) by mail.gmx.com (mrgmx003 [212.227.17.184]) with ESMTPSA (Nemesis) id 0MKqOW-1ehHl81Ypc-0001tL for ; Thu, 01 Feb 2018 17:30:46 +0100 Date: Thu, 1 Feb 2018 10:30:34 -0600 From: Dutch Ingraham To: freebsd-questions@freebsd.org Subject: Re: Do Radeon HD 5450 graphics work under FreeBSD ? Message-ID: <20180201163034.GA1616@fedora27> References: <9dffe9ca-8e6a-8016-8ee1-fe354ea21cc3@yandex.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9dffe9ca-8e6a-8016-8ee1-fe354ea21cc3@yandex.com> User-Agent: Mutt/1.9.1 (2017-09-22) X-Provags-ID: V03:K0:TwIYnKUoDwpLFKVZ6dXUssi9AqPgol/asJVM1V9wkuc69h2/ZG7 +eqUzjzZTPBbwbhpX3TFNzFwwHUxdbfWKIBh5VIfaoWyEaK+mvKCwglg11r+H+tMbTTIWUZ yU23FCNol/mbue+XAa8DHkP55kztAoZso6WnHKZc6IPfKGmvRyoGRxGXI/9wPwls6dJWXXz cURhw6/NwIAZx8IJKyEPQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:y82E87XnFhM=:rgseAj6+JhegnLokc0eNG8 hYFER66dk0Ruk+3IjvOOYewVeDLZy8xTcqD5VTkIAg1iUmLPQW2M40+bSG2kH0uwLirNp3h4Y S5oTZ5VxpMqvV+hup/dIJlG2U7TR/4segpRzb5beTqd5j04H6I68MsWbCAy0DGJohlSd2WUWk nlnolEdRUiNNfU/3w5h8bkPFF6njkkvtSEwhb80q0Kc6PvxrBTH+jFFJOcubgbu+OS9sub7eM k6nh0It0OQ1IhBh34IZbQHiB/21Ooha+5lxKysJzj9ePRILn/fbWqmJgIcdQYH+6pizJUycJb qPz/MQWxW/RTOpqcgtZjrwmDbMtVrjsNMEaKZLASC+gswwH13zkA4v+GSlghqw1PCxG1djrwD bU65nBJ1WhzVOBmY9u1xDp+IjhIF6YtXbLcCAtM70b2VBYzGxtff+xjOhKvzXH42F7mUELcmu 6tAjuiHVycHmNtBXkF/pgTXj7BmcO3M/OxdDW4yd7FM8yc5tXH7zB5gTTsDPFiLgl9EpMW2SN 3REr8ncIhz6rj2NQWKdE9ZfRUGAj/qb6wHWA9hVCONv6/GKfk/0i3Yi59FbUfAmTNd3ltV998 vLic5e3luOaBINbwCwIODLoACwqjmxxd+pSmiwWOKXZWq7GnW65rnOgn4qKItzFGu7wk4cAsi rfdJvccmb0j4JG0Mr5jFbq3HEzuhRgE4P28AhElRjdw421pnfEnRgw22xN8G0Vh70jTHCQt8M cCMA3oVqSRam5V+ddXzYDRPNLGjQYN5N0lenXC6X6g29OD3KhpPCnjzqQaJuq4YSTjhAJJsiP XGUgSyVCRTE7E5OIXcBbTDRV2MAlQ== X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 16:30:49 -0000 On Thu, Feb 01, 2018 at 09:31:48PM +0530, Manish Jain wrote: > Hi, > > I need to find out a low cost Radeon card that works under FreeBSD and is > generally available in the US. XFX ATI Radeon HD5450 (1 GB; USD 34) seems to > be a good candidate, but I have no idea whether this card works under > FreeBSD ? Does anyone on this list use Radeon HD5450 ? Or is certain that > the FreeBSD radeon driver would support the chip ? I'm using it now, so yes, it works. Also, there is a nice chart here for future reference: https://wiki.freebsd.org/Graphics From owner-freebsd-questions@freebsd.org Thu Feb 1 16:41:12 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ACDF6EDCC3D for ; Thu, 1 Feb 2018 16:41:12 +0000 (UTC) (envelope-from asv@inhio.net) Received: from cz-prg-mx-01.inhio.net (mail.inhio.net [178.238.36.226]) by mx1.freebsd.org (Postfix) with ESMTP id 3DFDB76446 for ; Thu, 1 Feb 2018 16:41:11 +0000 (UTC) (envelope-from asv@inhio.net) Received: from titanio (titanio.inhio.net [10.0.0.21]) by cz-prg-mx-01.inhio.net (Postfix) with ESMTPSA id C412E6016B for ; Thu, 1 Feb 2018 17:35:05 +0100 (CET) Message-ID: <1517502929.27269.3.camel@inhio.net> Subject: MAC BIBA/MLS Compartments From: ASV To: freebsd-questions@freebsd.org Date: Thu, 01 Feb 2018 17:35:29 +0100 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.24.2 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 16:41:12 -0000 Hi everyone, I'm experiencing something which is making me doubting completely about my understanding of compartments through BIBA and MLS models. I'm working in /home/shared # setpmac biba/equal,mls/equal ls -lZ /home/ drwxrwxrwt 2 root wheel biba/equal,mls/equal 512 Feb 1 16:43 shared ...... playing with file "class2" within "shared" # setpmac biba/equal,mls/equal ls -lZ /home/shared/ total 24 -rw-rw-r-- 1 lld wheel biba/10:1+2,mls/10:1+2 42 Jan 30 20:56 class0 -rw-rw-r-- 1 asv wheel biba/10:1+2+3,mls/10:1+2+3 31 Jan 31 10:49 class1 -rw-rw-r-- 1 asv wheel biba/10:1+2+3,mls/10:1+2+3 106 Feb 1 17:05 class2 which contains a line for testing # setpmac biba/equal,mls/equal cat /home/shared/class2 classified content working as user asv $ getpmac biba/10:1+2+3(8:1+2-12:1+2+3+4),mls/10:1+2+3(8:1+2- 12:1+2+3+4),partition/5 $ setpmac biba/12:1+2+3,mls/8:1+2 echo "blablabla2" >> shared/class2 $ setpmac biba/12:1+2+3,mls/8:1+2+3 echo "blablabla3" >> shared/class2 $ setpmac biba/12:1+2+3,mls/8:1+2+3+4 echo "blablabla4" >> shared/class2 $ setpmac biba/12:1+2+3,mls/8:1+2+3+4+5 echo "blablabla5" >> shared/class2 biba/12:1+2+3,mls/8:1+2+3+4+5: Operation not permitted (ok as subject isn’t in compartment 5) $ setpmac biba/12:1+2+3+4,mls/8:1+2+3+4 echo "blablabla5" >> shared/class2 $ setpmac biba/12:1+2,mls/8:1+2+3+4 echo "blablabla6" >> shared/class2 $ setpmac biba/12:1,mls/8:1+2+3+4 echo "blablabla7" >> shared/class2 biba/12:1,mls/8:1+2+3+4: Operation not permitted (WHY?! if "biba/12:1+2" worked why "12:1" failed?) $ setpmac biba/12:1+2,mls/8:1+2+3+4 echo "blablabla7" >> shared/class2 $ setpmac biba/12:1+2,mls/8:1+2+3 echo "blablabla8" >> shared/class2 $ setpmac biba/12:1+2,mls/8:1+2 echo "blablabla9" >> shared/class2 $ setpmac biba/12:1+2,mls/8:1 echo "blablabla10" >> shared/class2 biba/12:1+2,mls/8:1: Operation not permitted (again, why?) $ setpmac biba/12:1+2+3,mls/8:1 echo "blablabla10" >> shared/class2 biba/12:1+2+3,mls/8:1: Operation not permitted (?) $ setpmac biba/12:1+2+3+4,mls/8:1 echo "blablabla10" >> shared/class2 biba/12:1+2+3+4,mls/8:1: Operation not permitted (?) I feel like blind. The idea of the LABEL:GRADE it's fine, I see consistency with the "no write up" and "no read down" for BIBA and the "no read up" and "no write down" for MLS according to the assigned subject and grade. But this compartmentalization still looks like a mistery to me. As documentation on this subject (especially compartments) and its implementation on FreeBSD is largely insufficient (to be very politically correct) I need to try to bother somebody around here. :) Some of mine highly likely wrong assumptions: 1) numbers in compartments are not representing an order of importance (2>1, 3<4) but are only identifiers 2) an object which is labeled "biba/10:1+2,mls/10:1+2+3" should be accessed by a subject which not only matches the r/w requirements dictated by the GRADE but which belongs to at least one of the respective BIBA/MLS compartments the object belongs to. So subject "biba/9:1+2,mls/11:1+2+3" should be able to read objects labeled as follows: "biba/10:1+2,mls/10:1+2+3" "biba/10:1+2,mls/10:3" "biba/10:1,mls/10:1+2" "biba/10:1+2,mls/10:1" 3) the BIBA declaration "biba/10:1+2+3(8:1+2-12:1+2+3+4)" states that: - biba grade is 10 and has default access for compartments 1, 2 and 3 - biba grade 8 has access to compartments 1 and 2 - biba grade from 9 to 11 (which aren't explicitly declared) fall back to default compartments 1,2 and 3 - the above biba declaration allows to access an object which is at least in one of the compartments of the respective labels, if the GRADE actually allows that I know it's a tricky matter and MAC on FreeBSD is kind of a very niche topic but I have to try. MANY thanks in advance to whoever would help me on this. From owner-freebsd-questions@freebsd.org Thu Feb 1 17:32:24 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF17DEE0204 for ; Thu, 1 Feb 2018 17:32:23 +0000 (UTC) (envelope-from jude.obscure@yandex.com) Received: from forward101p.mail.yandex.net (forward101p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:101]) (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 7C90E79531 for ; Thu, 1 Feb 2018 17:32:23 +0000 (UTC) (envelope-from jude.obscure@yandex.com) Received: from mxback5g.mail.yandex.net (mxback5g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:166]) by forward101p.mail.yandex.net (Yandex) with ESMTP id 9C93C6A812BB; Thu, 1 Feb 2018 20:32:13 +0300 (MSK) Received: from smtp2p.mail.yandex.net (smtp2p.mail.yandex.net [2a02:6b8:0:1472:2741:0:8b6:7]) by mxback5g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id CqmAQxAlQ2-WDoGeZHi; Thu, 01 Feb 2018 20:32:13 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1517506333; bh=qOk/S37FeyxVvbsP40g0ofK4hPCgrouG5Yvg0sj+hZE=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=xp0pBV0ENXcTkmvOBURCLk1D0l+zWVQSZd1qTwf5ZQD/xTZFOYN9LQoerCGOxbAwN 3w7RKE7CPb9HAGWGh93PmrswRNbY7m6AbSJIaUT1pIPYWVIH6GCLyux2f2XdUe4LvR 2DbYcrNL91Q2Cckl0ZHLvPv3H5lik0skpetBcTGA= Received: by smtp2p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id RJNbFvUnBq-W6KaEerY; Thu, 01 Feb 2018 20:32:06 +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.com; s=mail; t=1517506327; bh=qOk/S37FeyxVvbsP40g0ofK4hPCgrouG5Yvg0sj+hZE=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=RlUm66s+fEBZOZwVxHpjKnMp29GcYcvblJymQmhKaX0J5+araOF9FBV6IhuZY+VO4 mTbq4ZNMuMhtrQZDyTGthA3Qxe7GnUsqSp0yHE29IWR/dr8BK/XjYSjKEuOObC0ikq yaonN/T6aiIYRZweqg04VyKFasNrDIirTiujQngA= Authentication-Results: smtp2p.mail.yandex.net; dkim=pass header.i=@yandex.com Subject: Re: Do Radeon HD 5450 graphics work under FreeBSD ? To: Dutch Ingraham , freebsd-questions@freebsd.org References: <9dffe9ca-8e6a-8016-8ee1-fe354ea21cc3@yandex.com> <20180201163034.GA1616@fedora27> From: Manish Jain Message-ID: <7ccf8ef5-5904-f7de-366d-946dd4710e15@yandex.com> Date: Thu, 1 Feb 2018 23:02:03 +0530 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20180201163034.GA1616@fedora27> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 17:32:24 -0000 On 02/01/18 22:00, Dutch Ingraham wrote: > On Thu, Feb 01, 2018 at 09:31:48PM +0530, Manish Jain wrote: >> Hi, >> >> I need to find out a low cost Radeon card that works under FreeBSD and is >> generally available in the US. XFX ATI Radeon HD5450 (1 GB; USD 34) seems to >> be a good candidate, but I have no idea whether this card works under >> FreeBSD ? Does anyone on this list use Radeon HD5450 ? Or is certain that >> the FreeBSD radeon driver would support the chip ? > > I'm using it now, so yes, it works. Also, there is a nice chart here > for future reference: Hello Dutch, Thanks for replying. I am glad to know that the chip works with FreeBSD. That's confirmed by the Graphics url too. The url unfortunately cannot be deemed authoritative: there are many chips which actually work (HD8470D, for instance) but are not listed there. I will, in future, though try to remember to refer to the site first. If that says 'Works', then no more querying should be necessary. -- Tx and Regards, Manish Jain From owner-freebsd-questions@freebsd.org Thu Feb 1 17:36:23 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0778BEE053B for ; Thu, 1 Feb 2018 17:36:23 +0000 (UTC) (envelope-from dave.mehler@gmail.com) Received: from mail-wr0-x233.google.com (mail-wr0-x233.google.com [IPv6:2a00:1450:400c:c0c::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 7B4CB79844 for ; Thu, 1 Feb 2018 17:36:22 +0000 (UTC) (envelope-from dave.mehler@gmail.com) Received: by mail-wr0-x233.google.com with SMTP id h9so6869372wre.12 for ; Thu, 01 Feb 2018 09:36:22 -0800 (PST) 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=+UKhU34Jm6nTaDgGc2GdudB3SL+kDjyYHFmwV9CJsU0=; b=NAl5OGAZOAzvaJEnbuzDUFDy3yB1Vcp7skGnUlEUTgJPZgYDAzQzMM1KiGCu38LPlO /idqXBEoLoqUgI+iCW27fYWLM3Z8/62OVdKoJon4gaEXtjo83j1Gv/zbHaS9vbN9JI6P +UdWbye1egGGeJ5Y0PsF/FtXsnTMULLGsEF/jRlpLGjHq3RIq8GBT9X6/dj+vatL+iyR unGwu8CEsb1JiSsXFmkl1OHxU4/KmZ6cNvmeMLq6cYtKrrpfYEdnesjLRP8fI1rZzpB7 2h3n1vytn+WZFz0OKAYqxe9VqqK+jXIDBCp9WX8sXkrupSy1QP4FtZhWg/pWV1DuNKNE 7hJw== 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=+UKhU34Jm6nTaDgGc2GdudB3SL+kDjyYHFmwV9CJsU0=; b=T10LmLVqz1tjWEWvgEDWMQJt12kjC7rhVfc6kOYIL9X1js7Wr2oF/cAGZsedpD37qE XdObHbns0mBUK6tkAAgtaT+SOf4KTTU7C/MPtpHz4RzNCqhF172ZuDLvD53/BR8DUHv3 jP1MFeYLLVKZgLMLIkFX1UxpD1GrWdN8Yny+zSnGJnEN59NEoYT32fFi62e5XhAOa4Zu goMbll4Ib8F15Lfa8iS7T/za+VuTqhuL7yvarNyZFY8E3BajpQlCSzyEufjc6Crnbwkc WDeFX57TQXuudrNvt9vkXG3pMsZwGDSLisByNl7pMJU52DzBW2z07Uh4vXQry9wgxc3H W/Kw== X-Gm-Message-State: AKwxytcXk82OIQVUIrZ8fMMjQQaHb2Sn0mfAXUT9uu2d5IgsSgkRWuta Flv/hG3hwTz0FRcbDzLmL4dEBq+RpkH17PgdxuI= X-Google-Smtp-Source: AH8x224of+7j6Y9flRWMe2i9m4J57OOWWzSxSDkDG7WYfYEepG1S+hcuaP8MobexOPVJ8yYS2njxoqJkOEQ2OVVIASU= X-Received: by 10.223.143.4 with SMTP id p4mr13729023wrb.261.1517506580027; Thu, 01 Feb 2018 09:36:20 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.141.184 with HTTP; Thu, 1 Feb 2018 09:36:19 -0800 (PST) From: David Mehler Date: Thu, 1 Feb 2018 12:36:19 -0500 Message-ID: Subject: freebsd git server To: freebsd-questions Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 17:36:23 -0000 Hello, I'm trying to set up a git server on FreeBSD. I'm wanting to use apache and gitweb. I've got anonymous read/write going as I can clone using https and I can push changes back to the repo. I'd like to get user authentication going on some but not all repos, some I want them to be public. All transactions are going over https. Any suggestions appreciated. Thanks. Dave. From owner-freebsd-questions@freebsd.org Thu Feb 1 17:40:02 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2E04DEE0974 for ; Thu, 1 Feb 2018 17:40:02 +0000 (UTC) (envelope-from jungleboogie0@gmail.com) Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::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 B748B79B5C for ; Thu, 1 Feb 2018 17:40:01 +0000 (UTC) (envelope-from jungleboogie0@gmail.com) Received: by mail-it0-x229.google.com with SMTP id 196so4726729iti.5 for ; Thu, 01 Feb 2018 09:40:01 -0800 (PST) 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=CuOLTl5uExRh5QjEDIAlwQP/SBcwvmULfufOLdM+74g=; b=JhbFa8ZrQuxcfo4Jx79HKYD8v3GDnS38ioXY3vNZbzh7mW79o4K1Evg7/Hdpwx/kJS 30aU/bTorIP2OKrey9S/ZRUwD8YrXgXWpA5MGvdyfnRFBFxf0XlR4l7rCjN9q94RrrWL hQhfFs0mANYTG4DEBlZ0FAI6ws32DnCGOs2w1jsX1BxphmEYUYRYeNYOSWubIMEltGGt VenFgm93jXqNscq41aP3t2G856BTqRwVgplzUx3V6NcmboxmC1FuOu0zESLTkEv/g6tX aN69YPK3+rF4Xe7mJScFRgzGIN1pwtQ96cp5+KeA3TYJRGJ4NA+OvItaDMr5sNTqXAyz o4UQ== 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=CuOLTl5uExRh5QjEDIAlwQP/SBcwvmULfufOLdM+74g=; b=YEv1vZmDh0deadslwosk60PI/rSR+6NshzAD3ZQ9WY/D07ldi5FOl2hrpkFfA/VYpZ VOdkkwgYyepgD6V07ETf8ZLPj1b83ztsX/7dDdo2V0H3EKaTzQivJ1BtAOqh/+40m2DA iocFE1f81FFL2MHruAsywji5LG8qei4UpbvfZsaXtIl3SzF+rzGQiTZ783uJUVsrPiv/ w9gNZ50zzqADm1G9oqoo6RDlfKManoq48ZPdg5cyunxxQs+WLEBVkSPT9ElfBUXpyshR dhBGLc7jxMyI7LHtBdQn3B9KqqDjOJzC5r48NZkn2a7ygydTJsvfeTrgiwALIC4ICKuu Yf7w== X-Gm-Message-State: AKwxytdnIOLhIRdDyJMdkg1xDItnBxz3zGXCFIBkVVC2QsQ3lB14LWiU 9M5/+U8D6DSRlPahAKwncjmMn3ISA2jo5B4J9nM= X-Google-Smtp-Source: AH8x227tc+KnXmhf9ledur1pedOfw7Z1NmZqQ1Xqeiv1LlHaaqZjeqtvxmuiVmANjLhe1qhxDVa3IN5nGZT8N94OelE= X-Received: by 10.36.25.15 with SMTP id b15mr42368245itb.147.1517506801185; Thu, 01 Feb 2018 09:40:01 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.203.194 with HTTP; Thu, 1 Feb 2018 09:40:00 -0800 (PST) In-Reply-To: References: From: jungle Boogie Date: Thu, 1 Feb 2018 09:40:00 -0800 Message-ID: Subject: Re: freebsd git server To: David Mehler Cc: freebsd-questions Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 17:40:02 -0000 On 1 February 2018 at 09:36, David Mehler wrote: > Hello, > > I'm trying to set up a git server on FreeBSD. I'm wanting to use > apache and gitweb. I've got anonymous read/write going as I can clone > using https and I can push changes back to the repo. I'd like to get > user authentication going on some but not all repos, some I want them > to be public. All transactions are going over https. > > Any suggestions appreciated. > Did you see the replies from the first time you asked this question? https://lists.freebsd.org/pipermail/freebsd-questions/2018-January/280683.html > Thanks. > Dave. -- ------- inum: 883510009027723 sip: jungleboogie@sip2sip.info From owner-freebsd-questions@freebsd.org Thu Feb 1 17:55:41 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DDFEAEE18A4 for ; Thu, 1 Feb 2018 17:55:41 +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 811EC7A630 for ; Thu, 1 Feb 2018 17:55:41 +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 647EF624DA for ; Thu, 1 Feb 2018 12:55:40 -0500 (EST) 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 PKtag4wemXZu for ; Thu, 1 Feb 2018 12:55:37 -0500 (EST) 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 7C8A0624B5 for ; Thu, 1 Feb 2018 12:55:37 -0500 (EST) Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Thu, 1 Feb 2018 12:55:37 -0500 Message-ID: <35d8e9b01acbb929ba4cb9b98241df54.squirrel@webmail.harte-lyne.ca> Date: Thu, 1 Feb 2018 12:55:37 -0500 Subject: FreeBSD, jail, ping From: "James B. Byrne" To: 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 17:55:42 -0000 On the jail I see this behaviour: root@hll124:~ # sysctl security.jail.allow_raw_sockets security.jail.allow_raw_sockets: 0 root@hll124:~ # sysctl security.jail.allow_raw_sockets=1 security.jail.allow_raw_sockets: 0 sysctl: security.jail.allow_raw_sockets=1: Operation not permitted So, how is this fixed? -- *** 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 Feb 1 18:04:55 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4D2CEE2215 for ; Thu, 1 Feb 2018 18:04:54 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from kicp.uchicago.edu (kicp.uchicago.edu [128.135.20.70]) by mx1.freebsd.org (Postfix) with ESMTP id 8FF857AFC4 for ; Thu, 1 Feb 2018 18:04:54 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from point.uchicago.edu (point.uchicago.edu [128.135.52.6]) by kicp.uchicago.edu (Postfix) with ESMTP id C5525718049; Thu, 1 Feb 2018 12:04:52 -0600 (CST) Subject: Re: FreeBSD, jail, ping To: byrnejb@harte-lyne.ca, freebsd-questions@freebsd.org References: <35d8e9b01acbb929ba4cb9b98241df54.squirrel@webmail.harte-lyne.ca> From: Valeri Galtsev Message-ID: <2be7ad99-225f-59eb-056f-469efdcae2e5@kicp.uchicago.edu> Date: Thu, 1 Feb 2018 12:04:52 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <35d8e9b01acbb929ba4cb9b98241df54.squirrel@webmail.harte-lyne.ca> 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 18:04:55 -0000 On 02/01/18 11:55, James B. Byrne via freebsd-questions wrote: > On the jail I see this behaviour: > > root@hll124:~ # sysctl security.jail.allow_raw_sockets > security.jail.allow_raw_sockets: 0 > > root@hll124:~ # sysctl security.jail.allow_raw_sockets=1 > security.jail.allow_raw_sockets: 0 > sysctl: security.jail.allow_raw_sockets=1: Operation not permitted You are not doing it inside the jail, right? You are doing it on the host system, right? Tahnks. Valeri > > So, how is this fixed? > -- ++++++++++++++++++++++++++++++++++++++++ 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 Thu Feb 1 18:05:23 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BEDA0EE2263 for ; Thu, 1 Feb 2018 18:05:23 +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 660A57B002 for ; Thu, 1 Feb 2018 18:05:23 +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 9812A6254A for ; Thu, 1 Feb 2018 13:05:22 -0500 (EST) 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 nrITNm4rBWSk for ; Thu, 1 Feb 2018 13:05:20 -0500 (EST) 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 F4149624B5 for ; Thu, 1 Feb 2018 13:05:19 -0500 (EST) Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Thu, 1 Feb 2018 13:05:20 -0500 Message-ID: In-Reply-To: <35d8e9b01acbb929ba4cb9b98241df54.squirrel@webmail.harte-lyne.ca> References: <35d8e9b01acbb929ba4cb9b98241df54.squirrel@webmail.harte-lyne.ca> Date: Thu, 1 Feb 2018 13:05:20 -0500 Subject: Re: FreeBSD, jail, ping From: "James B. Byrne" To: 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 18:05:23 -0000 On Thu, February 1, 2018 12:55, James B. Byrne wrote: > On the jail I see this behaviour: > > root@hll124:~ # sysctl security.jail.allow_raw_sockets > security.jail.allow_raw_sockets: 0 > > root@hll124:~ # sysctl security.jail.allow_raw_sockets=1 > security.jail.allow_raw_sockets: 0 > sysctl: security.jail.allow_raw_sockets=1: Operation not permitted > > So, how is this fixed? > On host: # jls JID IP Address Hostname Path 6 127.0.124.1 hll124.hamilton.harte-lyne.ca /usr/jails/hll124 # jail -m jid=6 allow.raw_sockets=1 On jail: # sysctl security.jail.allow_raw_sockets security.jail.allow_raw_sockets: 1 root@hll124:~ # ping 192.168.71.1 PING 192.168.71.1 (192.168.71.1): 56 data bytes 64 bytes from 192.168.71.1: icmp_seq=0 ttl=64 time=0.253 ms So, how does one get the jail to automatically configure this setting? -- *** 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 Feb 1 18:15:57 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2686EE2DAE for ; Thu, 1 Feb 2018 18:15:57 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from kicp.uchicago.edu (kicp.uchicago.edu [128.135.20.70]) by mx1.freebsd.org (Postfix) with ESMTP id 763CE7B94C for ; Thu, 1 Feb 2018 18:15:57 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from point.uchicago.edu (point.uchicago.edu [128.135.52.6]) by kicp.uchicago.edu (Postfix) with ESMTP id 1D67E71804D; Thu, 1 Feb 2018 12:15:57 -0600 (CST) Subject: Re: FreeBSD, jail, ping To: byrnejb@harte-lyne.ca, freebsd-questions@freebsd.org References: <35d8e9b01acbb929ba4cb9b98241df54.squirrel@webmail.harte-lyne.ca> From: Valeri Galtsev Message-ID: Date: Thu, 1 Feb 2018 12:15:56 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 18:15:57 -0000 On 02/01/18 12:05, James B. Byrne via freebsd-questions wrote: > > On Thu, February 1, 2018 12:55, James B. Byrne wrote: >> On the jail I see this behaviour: >> >> root@hll124:~ # sysctl security.jail.allow_raw_sockets >> security.jail.allow_raw_sockets: 0 >> >> root@hll124:~ # sysctl security.jail.allow_raw_sockets=1 >> security.jail.allow_raw_sockets: 0 >> sysctl: security.jail.allow_raw_sockets=1: Operation not permitted >> >> So, how is this fixed? >> > > On host: > > # jls > JID IP Address Hostname Path > 6 127.0.124.1 hll124.hamilton.harte-lyne.ca /usr/jails/hll124 > > # jail -m jid=6 allow.raw_sockets=1 > > On jail: > > # sysctl security.jail.allow_raw_sockets > security.jail.allow_raw_sockets: 1 > > root@hll124:~ # ping 192.168.71.1 > PING 192.168.71.1 (192.168.71.1): 56 data bytes > 64 bytes from 192.168.71.1: icmp_seq=0 ttl=64 time=0.253 ms > > > So, how does one get the jail to automatically configure this setting? > I do not know how to do it using ezjail, but after ezjail does its magic, the following line allow.raw_sockets = 1; will be in /etc/jail.conf inside particular jail configuration. ( after that setting is modified, particular jail has to be restarted as someone already mentioned) I hope, someone who uses ezjail will chime in. Thanks. 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 Thu Feb 1 18:22:51 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C935EEE350C for ; Thu, 1 Feb 2018 18:22:51 +0000 (UTC) (envelope-from sysadmin@grouchysysadmin.com) Received: from outbound00.knthost.com (outbound00.knthost.com [209.195.10.81]) (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 4BA537BFE4 for ; Thu, 1 Feb 2018 18:22:50 +0000 (UTC) (envelope-from sysadmin@grouchysysadmin.com) Reply-To: sysadmin@i.grouchysysadmin.com DKIM-Filter: OpenDKIM Filter v2.10.3 outbound00.knthost.com D82F9519D0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=grouchysysadmin.com; s=default; t=1517509367; bh=VDW0Iefp1JnBtieepcg1DQsrsFW3tD+2q64MbljjKo4=; h=Reply-To:Subject:To:References:From:Date:In-Reply-To; b=TtIRiYJNrvP6/zWlnDsD5TDVG0XPz/+3b1T0px7thCXeEnZ4JDlvok5vlsH13ntIe 2TfLgEmKwQroZGKGH8BLvCsdafvwVE/c9WupMQtP+beVwqFZhDF9mnH7xYQ03PIwy6 CwfYTxo39CcYdlA+X6l7L3v3afLYI0RKO3IyK1L/23wIsEixwxWjB2uegjie+h02pp rsAh7O+8+SfMej0GD8BjStFe5P+Qzd0Z3DzxjBkqS1S/BF6ixTFxLk4MwergtIyKi0 eKGbDQNXcci05z5YLgc2w7jn5kRs8i499XhraHB+g2IXZF26RYnnPLfUO+tE6Sc1d4 D7oevsbYhv7ng== Subject: Re: FreeBSD, jail, ping To: freebsd-questions@freebsd.org References: <35d8e9b01acbb929ba4cb9b98241df54.squirrel@webmail.harte-lyne.ca> From: Grouchy Sysadmin Message-ID: Date: Thu, 1 Feb 2018 12:22:44 -0600 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 18:22:52 -0000 On 02/01/2018 12:15 PM, Valeri Galtsev wrote: > > > On 02/01/18 12:05, James B. Byrne via freebsd-questions wrote: >> >> On Thu, February 1, 2018 12:55, James B. Byrne wrote: >>> On the jail I see this behaviour: >>> >>> root@hll124:~ # sysctl security.jail.allow_raw_sockets >>> security.jail.allow_raw_sockets: 0 >>> >>> root@hll124:~ # sysctl security.jail.allow_raw_sockets=1 >>> security.jail.allow_raw_sockets: 0 >>> sysctl: security.jail.allow_raw_sockets=1: Operation not permitted >>> >>> So, how is this fixed? >>> >> >> On host: >> >> # jls >>     JID  IP Address      Hostname                      Path >>       6  127.0.124.1     hll124.hamilton.harte-lyne.ca /usr/jails/hll124 >> >> # jail -m jid=6 allow.raw_sockets=1 >> >> On jail: >> >> # sysctl security.jail.allow_raw_sockets >> security.jail.allow_raw_sockets: 1 >> >> root@hll124:~ # ping 192.168.71.1 >> PING 192.168.71.1 (192.168.71.1): 56 data bytes >> 64 bytes from 192.168.71.1: icmp_seq=0 ttl=64 time=0.253 ms >> >> >> So, how does one get the jail to automatically configure this setting? >> > > I do not know how to do it using ezjail, but after ezjail does its > magic, the following line > > allow.raw_sockets = 1; > > will be in /etc/jail.conf inside particular jail configuration. > > ( after that setting is modified, particular jail has to be restarted > as someone already mentioned) > > I hope, someone who uses ezjail will chime in. > > Thanks. > Valeri > >> > For ezjail, see https://lists.freebsd.org/pipermail/freebsd-questions/2018-February/280740.html From owner-freebsd-questions@freebsd.org Thu Feb 1 19:41:43 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DA9FCEE8534 for ; Thu, 1 Feb 2018 19:41:43 +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 8360C81544 for ; Thu, 1 Feb 2018 19:41:43 +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 893C96254B; Thu, 1 Feb 2018 14:41:40 -0500 (EST) 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 t2TtAhKWFMN7; Thu, 1 Feb 2018 14:41:38 -0500 (EST) 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 67B826235A; Thu, 1 Feb 2018 14:41:37 -0500 (EST) Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Thu, 1 Feb 2018 14:41:38 -0500 Message-ID: <023b34c19e71fcf0a6156c750eed9005.squirrel@webmail.harte-lyne.ca> In-Reply-To: References: <35d8e9b01acbb929ba4cb9b98241df54.squirrel@webmail.harte-lyne.ca> Date: Thu, 1 Feb 2018 14:41:38 -0500 Subject: Re: FreeBSD, jail, ping From: "James B. Byrne" To: "Valeri Galtsev" 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 19:41:44 -0000 On Thu, February 1, 2018 13:15, Valeri Galtsev wrote: > > I do not know how to do it using ezjail, but after ezjail does its > magic, the following line > > allow.raw_sockets = 1; > > will be in /etc/jail.conf inside particular jail configuration. > > ( after that setting is modified, particular jail has to be restarted > as someone already mentioned) > EZJail does not use the jail.conf technique. It instead uses the deprecated environment-variable method to pass configuration values to jail. -- *** 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 Feb 1 20:24:22 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 64EA3EC6423 for ; Thu, 1 Feb 2018 20:24:22 +0000 (UTC) (envelope-from frankfenderbender@council124.org) Received: from vps349.pairvps.com (vps349.pairvps.com [216.92.231.69]) (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 181E883E2C for ; Thu, 1 Feb 2018 20:24:21 +0000 (UTC) (envelope-from frankfenderbender@council124.org) Received: from [192.168.0.100] (unknown [104.220.39.23]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by vps349.pairvps.com (Postfix) with ESMTPSA id 65402A5FD9; Thu, 1 Feb 2018 15:24:20 -0500 (EST) Subject: Re: sound-card/driver question Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: C Gray In-Reply-To: <20180201121251.95e345cf.freebsd@edvax.de> Date: Thu, 1 Feb 2018 12:24:19 -0800 Cc: freebsd-questions@freebsd.org Reply-To: C Gray Content-Transfer-Encoding: quoted-printable Message-Id: <09DEB81A-3DC1-4147-9249-0497C89F429B@council124.org> References: <8F08E935-33A8-4B5F-9057-51FAD51DA97D@council124.org> <20180201121251.95e345cf.freebsd@edvax.de> To: Polytropon X-Mailer: Apple Mail (2.1085) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 20:24:22 -0000 Much appreciation for sharing that wisdom.=20 Ordering the card now.=20 thanks and best wishes, chris On 01-February-2018, at 03:12 AM, Polytropon wrote: > On Wed, 31 Jan 2018 15:02:30 -0800, C Gray wrote: >> I have a Dell PowerEdge T300 server which has the following slots = available: >> slot 1: 3.3-V, full-length PCIe x4 with x8 connector >> slot 2: 3.3-V, full-length PCIe x4 >> slot 3: 3.3-V, full-length PCIe x8 >> slot 4: 3.3-V, full-length PCIe x8 >> slot 5: 3.3-V, full-length PCI-X >>=20 >> The system is based around: >> Xeon X3440 @ 2.50 GHz Quad core >> 2GB DDR3 RAM. >>=20 >> It's been said that a driver supported for Vista will work with for = FreeBSD. >=20 > That sounds very strange. Both systems are so fundamentally > different in architecture and binary interfaces. >=20 >=20 >=20 >> The card I am looking at works with Microsoft Windows7, Vista, and = XP. >> It's PCI-X based, and would, thus, be inserted into [my] slot 5: >> Creative Sound Blaster X-Fi Xtreme Gamer SB0770 7.1-Channel >> PCI Sound Card >>=20 >> My question is whether the CD of sound card drivers are in a >> standardized format such that,=20 >> FreeBSD/TrueOS can use them, as is, just as the Microsoft-verified >> environments do? >=20 > Probably not. >=20 > But it's not needed. FreeBSD provides the drivers needed and loads > them automatically at system startup once the hardware has been > detected properly. There usually is no need to manually download > or install something. >=20 > I've been using Creative Labs SoundBlaster cards in the past, and > the OS automatically loaded the correct driver. You can easily > verify this with >=20 > # pciconf -lv | less >=20 > and >=20 > # cat /dev/sndstat >=20 > The sound card should then be listed, and the corresponding driver > right next to it. >=20 > SoundBlaster cards have a long tradition of out-of-the-box support > on FreeBSD. Even on Linux, ALSA seems to provide support for this > particular card. >=20 >=20 >=20 >> Do they even use the same suffix? >=20 > What kind of suffix are you talking about? >=20 >=20 >=20 >> Are they well-written enough to discover the platform whereon >> they are expected to run (*that is, to "drive"). >=20 > Probably not. Drivers made for "Windows" will only work on a > specific subset of "Windows" versions, i. e., the "driver system" > they have been created for. So their use is even limited within > the "Windows" ecosystem, and outside of it, they are more or > less useless. >=20 >=20 >=20 >> It the OS discovers the driver rather than the driver=20 >> discovering the OS, the same functional use may be achieved, >> however, I'm ignorant other than=20 >> guessing as to how drivers work and what is required for that >> to take place. >=20 > As I said, manually supplying drivers is not needed on FreeBSD > because the drivers are already there. The OS discovers the > hardware and loads the driver. Simple and easy. :-) >=20 >=20 >=20 >> Where are they stored in Windows and in FreeBSD, and how do I >> install the proper one from the=20 >> disk accompanying the card (most likely meant for Microsoft's >> toolset/installer. >=20 > You don't. The OS already has the drivers installed. >=20 >=20 >=20 >> Suggestions? >=20 > If you have the card at hand, install it as recommended into the > system and boot FreeBSD. With the commands mentioned above, check > if (a) the device has been recognized, and (b) the appropriate > driver has been loaded. There isn't much more you have to do, as > FreeBSD is a "plug & play" OS. :-) >=20 >=20 >=20 >=20 > --=20 > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... > _______________________________________________ > 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" >=20 C Gray frankfenderbender@council124.org From owner-freebsd-questions@freebsd.org Thu Feb 1 21:35:19 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 19CE7ECBBB0 for ; Thu, 1 Feb 2018 21:35:19 +0000 (UTC) (envelope-from gobble.wa@gmail.com) Received: from mail-ua0-x22d.google.com (mail-ua0-x22d.google.com [IPv6:2607:f8b0:400c:c08::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 A862E68972 for ; Thu, 1 Feb 2018 21:35:18 +0000 (UTC) (envelope-from gobble.wa@gmail.com) Received: by mail-ua0-x22d.google.com with SMTP id n2so12885631uak.9 for ; Thu, 01 Feb 2018 13:35:18 -0800 (PST) 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; bh=x9q/XkYLqVLhGzg/3AE8KFBeq4/YXGIwSgZdnFM1VCQ=; b=Ef1OizoAgbec4FK0Mp/p3RgUa+arwO7ghH5tksL4cvQVL1Ud3FOQHWGK0Yys3T1CUP rkLsSdJor5WNgybAV3ukC01ACm8xH25AjzI991EysCLK2CnQCfQcLF/PwIJmzrh+SC8M O7g0RwbtS0J700VYAs27zfaFLaknV5h+igvlgNBbXN5wY2f3K0YPA7c6FAtynFKq1h0S ekyY+/h8+0HAhfQzn5+xfXJSm9JuCosfkkrU9AUV6S9AjqX+L+6BVUo5XuxqErl7RndZ QaXzkPB/EX671PjRy8jEx+5hFoVNcJmwcPM3uUF1dHcDcC/FYVLqFy6+MXOrW7ZdSnyf rzQw== 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; bh=x9q/XkYLqVLhGzg/3AE8KFBeq4/YXGIwSgZdnFM1VCQ=; b=XxOnfGviFQbCWm9ki4mDrqbY5RmDVydKLm0qfgxf9/su8FlRo4Il55sNBhYx6Z6mXk I3ad8K4WPB9zH2yw3ScOiuhdGMf0cnYEq8Iq6NwU/IDMlmwGTT6W3nJ6iJGTO2sP5RiR RMiLvhamLEIvJ4urdhT71fZftQ8NQU12j/rfoZPna04enWXKOLqZBv3KPH6CzJj6Ivd1 6W4WqePnTgyZzNg8QIxzAqKY+2YHWB4EA0gkTlv6VB/rkOUdR3rKkQugLlYWfyD1gpCb 5D5/ijwxHBpQGw3lydlAVHUlSofD2IyD2hGEcBPO7SOc0lh5evoP5iaYM55N2+yciyy8 mUyg== X-Gm-Message-State: AKwxytcala5+l3pXay1Or4qGaI5bz9TgPRNDkWUdzU/ZrPYCyXSGtiD8 yLbqGxNo6LJc5PJcVkZilGMzOQ8OIcPkSFwa7nTuOg== X-Google-Smtp-Source: AH8x224y6VNemQQyTc5pMjorbxuTCub9lr5QO0Qybj8XmdBlKxxeBnkLoxzON7w8tVDBDoWES3Csv1+wFANyM/wAxxQ= X-Received: by 10.176.80.211 with SMTP id d19mr30894337uaa.88.1517520917811; Thu, 01 Feb 2018 13:35:17 -0800 (PST) MIME-Version: 1.0 Received: by 10.103.119.211 with HTTP; Thu, 1 Feb 2018 13:35:17 -0800 (PST) In-Reply-To: <09DEB81A-3DC1-4147-9249-0497C89F429B@council124.org> References: <8F08E935-33A8-4B5F-9057-51FAD51DA97D@council124.org> <20180201121251.95e345cf.freebsd@edvax.de> <09DEB81A-3DC1-4147-9249-0497C89F429B@council124.org> From: Waitman Gobble Date: Thu, 1 Feb 2018 15:35:17 -0600 Message-ID: Subject: Re: sound-card/driver question To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 21:35:19 -0000 On Thu, Feb 1, 2018 at 2:24 PM, C Gray wrote: > > Much appreciation for sharing that wisdom. > Ordering the card now. > > thanks and best wishes, > chris > > On 01-February-2018, at 03:12 AM, Polytropon wrote: > > > On Wed, 31 Jan 2018 15:02:30 -0800, C Gray wrote: > >> I have a Dell PowerEdge T300 server which has the following slots available: > >> slot 1: 3.3-V, full-length PCIe x4 with x8 connector > >> slot 2: 3.3-V, full-length PCIe x4 > >> slot 3: 3.3-V, full-length PCIe x8 > >> slot 4: 3.3-V, full-length PCIe x8 > >> slot 5: 3.3-V, full-length PCI-X > >> > >> The system is based around: > >> Xeon X3440 @ 2.50 GHz Quad core > >> 2GB DDR3 RAM. > >> > >> It's been said that a driver supported for Vista will work with for FreeBSD. > > > > That sounds very strange. Both systems are so fundamentally > > different in architecture and binary interfaces. > > > > > > > >> The card I am looking at works with Microsoft Windows7, Vista, and XP. > >> It's PCI-X based, and would, thus, be inserted into [my] slot 5: > >> Creative Sound Blaster X-Fi Xtreme Gamer SB0770 7.1-Channel > >> PCI Sound Card > >> > >> My question is whether the CD of sound card drivers are in a > >> standardized format such that, > >> FreeBSD/TrueOS can use them, as is, just as the Microsoft-verified > >> environments do? > > > > Probably not. > > > > But it's not needed. FreeBSD provides the drivers needed and loads > > them automatically at system startup once the hardware has been > > detected properly. There usually is no need to manually download > > or install something. > > > > I've been using Creative Labs SoundBlaster cards in the past, and > > the OS automatically loaded the correct driver. You can easily > > verify this with > > > > # pciconf -lv | less > > > > and > > > > # cat /dev/sndstat > > > > The sound card should then be listed, and the corresponding driver > > right next to it. > > > > SoundBlaster cards have a long tradition of out-of-the-box support > > on FreeBSD. Even on Linux, ALSA seems to provide support for this > > particular card. > > > > > > > >> Do they even use the same suffix? > > > > What kind of suffix are you talking about? > > > > > > > >> Are they well-written enough to discover the platform whereon > >> they are expected to run (*that is, to "drive"). > > > > Probably not. Drivers made for "Windows" will only work on a > > specific subset of "Windows" versions, i. e., the "driver system" > > they have been created for. So their use is even limited within > > the "Windows" ecosystem, and outside of it, they are more or > > less useless. > > > > > > > >> It the OS discovers the driver rather than the driver > >> discovering the OS, the same functional use may be achieved, > >> however, I'm ignorant other than > >> guessing as to how drivers work and what is required for that > >> to take place. > > > > As I said, manually supplying drivers is not needed on FreeBSD > > because the drivers are already there. The OS discovers the > > hardware and loads the driver. Simple and easy. :-) > > > > > > > >> Where are they stored in Windows and in FreeBSD, and how do I > >> install the proper one from the > >> disk accompanying the card (most likely meant for Microsoft's > >> toolset/installer. > > > > You don't. The OS already has the drivers installed. > > > > > > > >> Suggestions? > > > > If you have the card at hand, install it as recommended into the > > system and boot FreeBSD. With the commands mentioned above, check > > if (a) the device has been recognized, and (b) the appropriate > > driver has been loaded. There isn't much more you have to do, as > > FreeBSD is a "plug & play" OS. :-) > > > > > > > > > > -- > > Polytropon > > Magdeburg, Germany > > Happy FreeBSD user since 4.0 > > Andra moi ennepe, Mousa, ... > > _______________________________________________ > > 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" > > > > C Gray > frankfenderbender@council124.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" If you are an audiophile.... I'm pretty sure i saw a note in the Creative driver source that it only supports up to 48Khz. ... uggh. Option, you can pay 10 bucks for OSS if you can get ahold of an older card, this works great with older Asus Xonar cards but the currently available cards use a different chipset that totally does not work. It would be risky to buy one without knowing for certain the chipset used. Here's a USB adapter that supports 192 KHz and works with FreeBSD. And it's cheap. Sewell Direct Soundbox Pro External USB Sound Card, 24 bit 192 KHz Audio, 7.1 Channels Sound Cards SW-30415 It's what I believe to be a rebrand, I bought the exact same unit several years ago under a different name. -- Waitman Gobble Los Altos California USA 650-621-0423 From owner-freebsd-questions@freebsd.org Thu Feb 1 21:48:34 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4ADC1ECCB81 for ; Thu, 1 Feb 2018 21:48:34 +0000 (UTC) (envelope-from kremels@kreme.com) Received: from mail.covisp.net (www.covisp.net [65.121.55.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 E789F6930D for ; Thu, 1 Feb 2018 21:48:33 +0000 (UTC) (envelope-from kremels@kreme.com) From: "@lbutlr" Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: Response to Meltdown and Spectre Date: Thu, 1 Feb 2018 14:48:24 -0700 References: <23154.11945.856955.523027@jerusalem.litteratus.org> <5A726B60.7040606@gmail.com> To: Freebsd Questions In-Reply-To: <5A726B60.7040606@gmail.com> Message-Id: <92120E50-19A7-4A44-90DF-505243D77259@kreme.com> X-Mailer: Apple Mail (2.3445.6.9) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 21:48:34 -0000 On 31 Jan 2018, at 18:20, JD wrote: > I think this blunder by MS-Intel Duopoly could be the poison pill that = will kill both. That seems highly unlikely. It will damage the role of Intel in the = server market fora time, but the trouble is that AMD's behavior has been = at least as bad as Intel's, if not worse, in regards to Meltdown, so = there's not a clearly better choice even though the AMD chips have less = issues. And what other choices are there for server kit? --=20 =E2=80=9CIf you want to get rich from writing, write the sort of thing = that's read by persons who move their lips when they're reading to = themselves.=E2=80=9D=20 =E2=80=95 Don Marquis From owner-freebsd-questions@freebsd.org Thu Feb 1 23:04:16 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AAAB6ED1E3F for ; Thu, 1 Feb 2018 23:04:16 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (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 3F1B96CDC4 for ; Thu, 1 Feb 2018 23:04:16 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by mail-it0-x22f.google.com with SMTP id n206so5798792itg.1 for ; Thu, 01 Feb 2018 15:04:16 -0800 (PST) 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=OVSFUwWpkFmHI1z40t1k/sOeFiLcJxnbAAUkoicG/KI=; b=KeY9+PNZZPIQsRI13flPjj8uce06Qn7NGJA9sX7NrzvHSyUXjKFHF6cEzGRrav/gdH pXvDTGkNgSm2yLppwxF62WjhNIOOgBWvJecpNbKTJrmDoob24g5ab5GmuKKvewSKTiLn 3VDYrM3b1H4o0M4myBhKc7Xq5CzbbvXbC4bKKTNRDnhMDmpG5zXd0rqDpOkBJ33Guqno 7uU2cLHu3LAd81sjJTJfcb/Px4V9fEDwDNFfy8gTDeZlvQDjVyXc0UrEEEU/RCnLy3A+ GEAikhTyOKGJjvALOO2HqPweb0xTvs593BYSM85YkSgYkOrHsIAgUUs5gmBvItf+Y9+h 16dw== 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=OVSFUwWpkFmHI1z40t1k/sOeFiLcJxnbAAUkoicG/KI=; b=cuH3eMMBmBUgAoXanPdrB4y9IWPctX89FaMiKEuu9oZqCcnN7isuVoRN9Iou3KcgeC 52m5x0baZNr4aOyxeZt+LGikS1X27TNZYFDKxgmEW+9dd9fGzHy8lgR8bU9v6poOI7qb HW5k9rIUaIg3HF/P8ZBVMXDNlt73Dg9AZzPE5GccEMpN5yIGsmquQ16jJVvzQKtInOeO AyC6Zy6uidOlbwlV0UzF4j6c0McAHDEBWh8WFP29jbAK5jDSgtj8/mdgIlqUQhOA0TUb GUY1HRQVmEJo9dccrKLUXWDyzUA+rSC1G/5+FBhQ9frCKogQumvyQaRX2O5QG9WMaE1v +qcg== X-Gm-Message-State: AKwxytcz+8ti82cRKswqLStyQv7z40IOlla12MkyOWunO/DHqt3yr3eX K7OzkhDcyYDNze7qmQc07d5PAzDUGYjeYBAN+Nw= X-Google-Smtp-Source: AH8x224SwcctAJSuriCORYO2hapQEsps35UNpgm4QSYu4R4ahExYI5ouqMhF7jK6oXpuXKp35f05fF+BHh4pgZNEZ3Y= X-Received: by 10.36.23.20 with SMTP id 20mr8842902ith.135.1517526255572; Thu, 01 Feb 2018 15:04:15 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.156.70 with HTTP; Thu, 1 Feb 2018 15:04:15 -0800 (PST) In-Reply-To: <92120E50-19A7-4A44-90DF-505243D77259@kreme.com> References: <23154.11945.856955.523027@jerusalem.litteratus.org> <5A726B60.7040606@gmail.com> <92120E50-19A7-4A44-90DF-505243D77259@kreme.com> From: Adam Vande More Date: Thu, 1 Feb 2018 17:04:15 -0600 Message-ID: Subject: Re: Response to Meltdown and Spectre To: "@lbutlr" Cc: Freebsd Questions Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 23:04:17 -0000 On Thu, Feb 1, 2018 at 3:48 PM, @lbutlr wrote: > the trouble is that AMD's behavior has been at least as bad as Intel's, if > not worse, in regards to Meltdown, > Can you explain what provoked this assertion? -- Adam From owner-freebsd-questions@freebsd.org Thu Feb 1 23:32:58 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 846C9ED3B2C for ; Thu, 1 Feb 2018 23:32:58 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from kicp.uchicago.edu (kicp.uchicago.edu [128.135.20.70]) by mx1.freebsd.org (Postfix) with ESMTP id 2721B6DDF8 for ; Thu, 1 Feb 2018 23:32:57 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from point.uchicago.edu (point.uchicago.edu [128.135.52.6]) by kicp.uchicago.edu (Postfix) with ESMTP id 3716371804B; Thu, 1 Feb 2018 17:32:51 -0600 (CST) Subject: Re: Response to Meltdown and Spectre To: JD , freebsd-questions@freebsd.org References: <23154.11945.856955.523027@jerusalem.litteratus.org> <5A726B60.7040606@gmail.com> From: Valeri Galtsev Message-ID: Date: Thu, 1 Feb 2018 17:32:50 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <5A726B60.7040606@gmail.com> 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 23:32:58 -0000 On 01/31/18 19:20, JD wrote: > > > On 01/31/2018 02:01 PM, Robert Huff wrote: >> Zahrir, Abderrahmane writes: >> >>>   I understand that you have not been notified early enough about >>>   the Meltdown and spectre security flow. >>> >>>   However do we have a rough estimate (something like an >>>   approximate month) of when a patch will be available for the >>>   latest version 11.1 and possibly 11.0? >>     Given that - at this writing - _Intel_ doesn't fully understand >> how to fix this .... >> >> >>                 Respectfully, >> >> >>                     Robert Huff > I think this blunder by MS-Intel Duopoly could be the poison pill that > will kill both. > Quite unlikely. MS existence is backed up by customers, 90% of whom are computer ignorant, which solidifies MS existence. Intel has substantial share of CPU market, probably about 85% of all sold amd64 architecture are Intel ones. Which in itself makes it unlikely Intel to disappear, or even loose noticeable share of market. They are not monopoly strictly speaking, but almost such. I myself am quite neutral to either of them. On this subject what my friend likes to say about operating systems is quite applicable: All systems suck... and thanks to that I got my job ;-) Valeri > >> >> _______________________________________________ >> 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" >> . >> > > _______________________________________________ > 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 Thu Feb 1 23:46:26 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3352DED4745 for ; Thu, 1 Feb 2018 23:46:26 +0000 (UTC) (envelope-from pathiaki2@yahoo.com) Received: from sonic312-22.consmr.mail.ne1.yahoo.com (sonic312-22.consmr.mail.ne1.yahoo.com [66.163.191.203]) (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 B977F6E4AD for ; Thu, 1 Feb 2018 23:46:25 +0000 (UTC) (envelope-from pathiaki2@yahoo.com) X-YMail-OSG: nfH8.coVM1loeMFIIhG.eJFH9k0iSDN_fzaHvb3vkH2ezaWUMfBI4JR3I8qGd0Y of9nyU6r0U2lHGzS2tzlwCoQVnuNAy46Kr614cqg6vudyb.WtAPEitOpMnLxdPPUJxdb7gbO69nr ihMMQiGnmCQYkMnfweGsbimM3u25AHW6x4oxCQdtPYUs3CuBPXBVUulUUK0kvfdSpod3YeY52CbM 03n6fcgfX10wI3ghm6.vxLoEmOaYE657DRxL8_MpiyYTfQREY0bgSvdvtSmdjKNTewMk1DJNQWNj UxW5C9DsTVnnmjY2VSaNU3JDj2gNr5me0amEkpKSWs3HE4yRcSeegtwOPmGMmYtCIUANSvg.DNfP eHAJNwJjuCo26vsS5084Vdfj43HGXSfeE6Hp2fVzcZemFOUgYO60getLeJEtZYUEPFGL1OHO3rvD NsiRn4N7qGo_tKvBmGMy815O7qbbJpx6KvCthj3qFAi_i8_Fs2o6zmiQeAYgREtkd_F4fah0XUWy LlEklJLRcq7hKQSK0s4Q1dDL_pXWxUsGZqtg- Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.ne1.yahoo.com with HTTP; Thu, 1 Feb 2018 23:46:19 +0000 Received: from smtp235.mail.ne1.yahoo.com (EHLO [192.168.0.6]) ([10.218.253.206]) by smtp413.mail.ne1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID 0863e17cc356e7de0df688d5422c76d8 for ; Thu, 01 Feb 2018 23:36:08 +0000 (UTC) Subject: Re: Response to Meltdown and Spectre To: freebsd-questions@freebsd.org References: <23154.11945.856955.523027@jerusalem.litteratus.org> <5A726B60.7040606@gmail.com> <92120E50-19A7-4A44-90DF-505243D77259@kreme.com> From: Paul Pathiakis Message-ID: <71736b45-cbff-36d6-81ee-8e945375779c@yahoo.com> Date: Thu, 1 Feb 2018 18:36:08 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 23:46:26 -0000 Yes, please explain. AMD stated up front that they weren't vulnerable to 1 and were almost 0-potential for the others. Just a plain better design. They, then, reiterated the very same thing. From what I've seen, AMD has a done a good job of being on top of their 'non-issue'. P. On 02/01/2018 18:04, Adam Vande More wrote: > On Thu, Feb 1, 2018 at 3:48 PM, @lbutlr wrote: > >> the trouble is that AMD's behavior has been at least as bad as Intel's, if >> not worse, in regards to Meltdown, >> > Can you explain what provoked this assertion? > From owner-freebsd-questions@freebsd.org Fri Feb 2 00:26:25 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F24F2ED748A for ; Fri, 2 Feb 2018 00:26:24 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from kicp.uchicago.edu (kicp.uchicago.edu [128.135.20.70]) by mx1.freebsd.org (Postfix) with ESMTP id A1A49709C0 for ; Fri, 2 Feb 2018 00:26:24 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from point.uchicago.edu (point.uchicago.edu [128.135.52.6]) by kicp.uchicago.edu (Postfix) with ESMTP id 51BC271804B; Thu, 1 Feb 2018 18:26:23 -0600 (CST) Subject: Re: Response to Meltdown and Spectre To: Paul Pathiakis , freebsd-questions@freebsd.org References: <23154.11945.856955.523027@jerusalem.litteratus.org> <5A726B60.7040606@gmail.com> <92120E50-19A7-4A44-90DF-505243D77259@kreme.com> <71736b45-cbff-36d6-81ee-8e945375779c@yahoo.com> From: Valeri Galtsev Message-ID: Date: Thu, 1 Feb 2018 18:26:23 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <71736b45-cbff-36d6-81ee-8e945375779c@yahoo.com> 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 00:26:25 -0000 On 02/01/18 17:36, Paul Pathiakis via freebsd-questions wrote: > Yes, please explain. > > AMD stated up front that they weren't vulnerable to 1 and were almost > 0-potential for the others.  Just a plain better design. > > They, then, reiterated the very same thing.  From what I've seen, AMD > has a done a good job of being on top of their 'non-issue'. > Thanks, Paul. And since the beginning of the issue I keep thanking myself for having almost all boxes in the server room built with AMD Opterons... Luckily for me the choice of what we get was entrusted into me, and luckily for all of us here I was quite impressed by Opteron architecture, and > P. > > > On 02/01/2018 18:04, Adam Vande More wrote: >> On Thu, Feb 1, 2018 at 3:48 PM, @lbutlr wrote: >> >>> the trouble is that AMD's behavior has been at least as bad as >>> Intel's, if >>> not worse, in regards to Meltdown, >>> >> Can you explain what provoked this assertion? >> > > _______________________________________________ > 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 Fri Feb 2 00:35:18 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9546ED7D15 for ; Fri, 2 Feb 2018 00:35:17 +0000 (UTC) (envelope-from frankfenderbender@council124.org) Received: from vps349.pairvps.com (vps349.pairvps.com [216.92.231.69]) (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 85C9C70FBA for ; Fri, 2 Feb 2018 00:35:17 +0000 (UTC) (envelope-from frankfenderbender@council124.org) Received: from [192.168.0.100] (unknown [104.220.39.23]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by vps349.pairvps.com (Postfix) with ESMTPSA id 403D9A5FD9; Thu, 1 Feb 2018 19:35:11 -0500 (EST) Subject: followup to my previous sound-card/driver question Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=windows-1252 From: C Gray In-Reply-To: <09DEB81A-3DC1-4147-9249-0497C89F429B@council124.org> Date: Thu, 1 Feb 2018 16:35:09 -0800 Reply-To: C Gray Content-Transfer-Encoding: quoted-printable Message-Id: <69060D2E-8ED1-4BDB-8801-2BA29F15C632@council124.org> References: <8F08E935-33A8-4B5F-9057-51FAD51DA97D@council124.org> <20180201121251.95e345cf.freebsd@edvax.de> <09DEB81A-3DC1-4147-9249-0497C89F429B@council124.org> To: freebsd-questions@freebsd.org X-Mailer: Apple Mail (2.1085) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 00:35:18 -0000 Creative Lab apparently now only produces/sells/supports "x1" = SoundBlaster sound cards. My slots are for "PCIe x4", "PCIe x8", or "PCI-X". No "PCIe x1". Creative Labs support is digging through archives to find which EOL'ed = cards were which as most are listed on Amazon w/o that pertinent = information, rather just listing as a model in a card family. I actually = found a telephone number and got an answer in 2-3 rings: (405) = 742-6655. And, of course, there are the "fake" cards called "SoundBlaster" = (clones, unsupported and seldom taken back if incompatible) rather than = those named "Creative SoundBlaster" (officially made by Creative Labs). None show the listed models down to a level indicating {x1, x4, x8} or = even if it is a PCI-X slot-fitting card. So, reverse engineering is what I shall try to do while waiting for the = technical support email with a hopeful list. The FreeBSD page, = , indicates the = following for 64-bit system supported sound cards that are supported by = either the "snd_emu10k1(4)" or the "snd_emu10kx(4)" drivers: =95 Creative SoundBlaster Live! (EMU10K1 Chipset) =95 Creative SoundBlaster Audigy (EMU10K2 Chipset) =95 Creative SoundBlaster Audigy 2 (EMU10K2 Chipset) =95 Creative SoundBlaster Audigy 2 (EMU10K3 Chipset) =95 Creative Sound Blaster Live! (EMU10K1 Chipset).=20 Both PCM and MIDI interfaces are available. =95 Creative Sound Blaster Audigy (CA0100 and CA0101 Chipset).=20= PCM and two MIDI interfaces available. =95 Creative Sound Blaster Audigy 2 and Creative Sound Blaster = Audigy 4 (CA0102 Chipset).=20 PCM support is limited to 48kHz/16 bit stereo (192kHz/24 bit = part of this chipset is not supported). =95 Creative Sound Blaster Audigy 2 Value (CA0108 Chipset).=20 PCM support is limited to 48kHz/16 bit stereo (192kHz/24 bit = part of this chipset is not supported).=20 There is no MIDI support for this card. The following doc is less helpful: The snd_emu10kx(4) driver does not support the following sound cards = (although they have names similar to some supported ones): =95 ... =95 All Creative X-Fi series sound cards. Too bad because the ad for "Creative Labs SB0880 PCI Express Sound = Blaster X-Fi Titanium Sound Card" =20 on = . It "System Requirements" list seems to fit, as far as I'm aware at the = present, of what barriers could get in the way. It appears to tell me that its work for my slots: Microsoft Windows 7, Vista, or XP;=20 Intel Pentium 4 1.6 GHz or AMD Athlon XP 2000+ processor or = equivalent;=20 available PCI Express (x1, x4, x8, or x16) slot;=20 256MB RAM (512 MB RAM for Vista);=20 600MB of free hard-disk space;=20 CD or DVD-ROM for software installation; <<<< [not needed] headphones or amplified speakers;=20 Internet connection to download PowerDVD player software. Unfortunately, there is no mention of the chipset, but having the PCI = types listed is encouraging. The FreeBSD doc, although very helpful, does not tell me which X-Fi = models are NOT supported by theFreeBSD's "snd_emu10kx(4)" driver. So, if anyone knows the "supported X-Fi" list that would be very = helpful. FreeBSD doc's "not specific enough" list for me, logic-wise, arise from = the phrases "does not support" (from the list intro) and "All"..." (from = the actual list). Together they form the phrase "does not support... all", which = delineates a set, N, with an indeterminant # of elements. It can support (0-to-N) of the X-Fi sound cards. Supporting only (1-of-N) X-Fi sound cards meets the criteria of "not = supporting all" as does supporting (N-1) X-Fi sound cards. Even supporting 0 meets the logic of the chosen phraseology. Thus, I will stay away from the X-Fi family due to the "non-specific = list" factor, unless I hear of a very matchable, qualified application = by someone. That's not too much of a loss w/so many supported devices.=20 My first list from the FreeBSD doc, is still quite vast, as far as a = list goes, though availability may narrow that down a bit. =20 I have also read bad reviews of the Audigy family which have proprietary = cables.=20 Non-standard proprietaries so well-deployed by Microsoft and Apple. No = thanks.=20 They are the 180-degree flip-sides of clones. The "chipset" is never listed with the sound card descriptions on = Amazon.com, SoundBlaster.com, or Creative.com web pages. Some of a chipset's models may not be supported so I must know all vars = before I can select and order a card. Does a list of specific models (selling name as well as actual model = nomenclature) exist. The four-variable algorithm (chipset; x1/x4/x8/-X; model #; = FreeBSD-supported) list is what I seek so that I avoid the = somewhere-documented failure. My dragged-out question can be pared down to this: which of the FreeBSD driver-supported Creative Labs sound cards = (listed above) are made for {x4, x8, -X) slots AND are built with a = supported chipset? It would appear that I am trying to find exact model #s -- and not just = the all-encompassing advertisement family called "Creative SoundBlaster = Live! - EMU10K1 Chipset)" that will fit one of my PCIe x4. PCIe x8, or = PCI-X slots. [Note: it would also be great to find one that will work with my Ensoniq = TS-10 Sampler-Sequencer-Synthesizer via MIDI, so I can move away from = another Apple-broken tool, MIDI (like NFS, X11, mail, BSD, ad finitum), = however, that would just add another variable into the 'find-a-card' = algorithm. Even considering this seems foolhardy. I just want some audio = for my Python/PHP/Java/Javascript/Perl/C development server.]=20 best wishes (and sorry for the elongated clarification), Chris Gray frankfenderbender@council124.org From owner-freebsd-questions@freebsd.org Fri Feb 2 03:14:45 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2932EDFF86 for ; Fri, 2 Feb 2018 03:14:45 +0000 (UTC) (envelope-from kremels@kreme.com) Received: from mail.covisp.net (www.covisp.net [65.121.55.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 6F255766CE for ; Fri, 2 Feb 2018 03:14:45 +0000 (UTC) (envelope-from kremels@kreme.com) From: "@lbutlr" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Re: Response to Meltdown and Spectre Date: Thu, 1 Feb 2018 20:14:42 -0700 References: <23154.11945.856955.523027@jerusalem.litteratus.org> <5A726B60.7040606@gmail.com> <92120E50-19A7-4A44-90DF-505243D77259@kreme.com> To: Freebsd Questions In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3445.6.9) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 03:14:46 -0000 On 1 Feb 2018, at 16:04, Adam Vande More amvandemore@gmail.com> wrote: >=20 > On Thu, Feb 1, 2018 at 3:48 PM, @lbutlr wrote: >=20 >> the trouble is that AMD's behavior has been at least as bad as = Intel's, if >> not worse, in regards to Meltdown, >>=20 >=20 > Can you explain what provoked this assertion? First, they violated (not technically, but they made it bloody obvious) = the NDA so that the flaw was widely discovered a week early by adding a = comment to a meltdown patch that lead every expert int he field straight = to the vulnerability: "The AMD microarchitecture does not allow memory = references, including speculative references, that access higher = privileged data when running in a lesser privileged mode when that = access would result in a page fault." Second, they initially claimed they were would not release any firmware = because they were entirely immune, which was untrue. They were almost immediately proved to be vulnerable to some of the = flaws. Third, while Intel released (and continues to release) detailed = technical information, AMD released PR statements. Honestly, as bad as Intel has looked in the last month, AMD looks worse = since they'd behaved like children. --=20 Don't be afraid to be weak, Don't be too proud to be strong. From owner-freebsd-questions@freebsd.org Fri Feb 2 03:23:35 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B451AEE0603 for ; Fri, 2 Feb 2018 03:23:35 +0000 (UTC) (envelope-from kremels@kreme.com) Received: from mail.covisp.net (www.covisp.net [65.121.55.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 60D1576BC7 for ; Fri, 2 Feb 2018 03:23:34 +0000 (UTC) (envelope-from kremels@kreme.com) From: "@lbutlr" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Response to Meltdown and Spectre Date: Thu, 1 Feb 2018 20:23:33 -0700 References: <23154.11945.856955.523027@jerusalem.litteratus.org> <5A726B60.7040606@gmail.com> <92120E50-19A7-4A44-90DF-505243D77259@kreme.com> To: Freebsd Questions In-Reply-To: Message-Id: <01065F53-87F3-4207-9745-C8611C46312A@kreme.com> X-Mailer: Apple Mail (2.3445.6.9) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 03:23:36 -0000 On 1 Feb 2018, at 20:14, @lbutlr rote: > They were almost immediately proved to be vulnerable to some of the flaws. (Spectre flaws, that is) -- Happy Jack wasn't tall, but he was a man From owner-freebsd-questions@freebsd.org Fri Feb 2 04:04:25 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 83203EE2573 for ; Fri, 2 Feb 2018 04:04:25 +0000 (UTC) (envelope-from opsyspref@gmail.com) Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (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 17F8378450 for ; Fri, 2 Feb 2018 04:04:25 +0000 (UTC) (envelope-from opsyspref@gmail.com) Received: by mail-oi0-x22b.google.com with SMTP id l8so15100604oig.0 for ; Thu, 01 Feb 2018 20:04:25 -0800 (PST) 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=BK7S2nM/9/chwoeNoPUcnE8YfkP7uu1dHRMvM+4lTso=; b=fOvjH8dSXnOhsT7wlMcgMtw9kL9wk8pKVWIHGlXycHkVczqr3dOAqdNw2bkuEKMnQK usL/nXWpG8yxwAyTP/IgWGvs0j+uesDgIFVH5cW3kpJ4wGYJmRBo4+vQOG218IV2ncrA YrQkjHK4rz2732eXBb/g7UHte+qu0bHjXhxCKqtsG6cHrwJc4UojXK++ec1xQsqAvbyK TBlPo6DqFP+rd+ZhwNbUyYzHif0XQfwjCfo0mJhQhJEuPUGl4TseLrYzPPwNSqT7tDFj 7pzlEEyaHndiZN/NmsQaYgxlJ+Kj7hRjQQSKQ9aiqYFZBTldWMKASJ1ILGbtJEr4JML9 7tow== 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=BK7S2nM/9/chwoeNoPUcnE8YfkP7uu1dHRMvM+4lTso=; b=tuL4c5Oc4EKdrqyVJnTkYZuvyJh75U7yEnInvAQ0KkmmupZB5AsmmdhiC8ROwSbkS2 pVAPMm0QdtdPYgWRgeOmwg6b6sF5FpXKNWRv9nC6HZXzzr1wZozYKRZtgAM29ZvpXilC meepKH8RJCj05DqOqNKoWGhueEuaGj16R5sG1syftifQugWRA6+yBZq4FialVJJfNZKN rkx6uBs3BxggNiR9jjdDPQnJJIH602Ea8jB5S5+IBm967/Mxpo+3/6r66fy7xT3Qfc73 emoJY/APxjVIGoAF3JDhXQtti7djXMPeB6mXqM8BsJa2TAsly/KCd7wh8hPsB52dVYgU 0Qyw== X-Gm-Message-State: APf1xPBBB2vBh2LNghzgSn2TFB9lJzhIQpNTcqaicHvZ+zOyVvqmICW4 tjbG2dIOvjDEtKN1wz4XEx1KlOj/Fnw5h8tL0LI0i71P X-Google-Smtp-Source: AH8x225DUUj9pC9n/3iwmgzHNzvfwkvqYG0QKD/86uYpzhBx4BoFUG2OVjtQA6g9TFY8xbsI4HXcWhjDH1/saBVwuU0= X-Received: by 10.202.61.198 with SMTP id k189mr2724066oia.247.1517544264403; Thu, 01 Feb 2018 20:04:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.11.203 with HTTP; Thu, 1 Feb 2018 20:04:24 -0800 (PST) From: Peter Ulrich Kruppa Date: Fri, 2 Feb 2018 05:04:24 +0100 Message-ID: Subject: German keyboard support for gdm??? To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 04:04:25 -0000 Hello, does anyone know how to make gnome's display manager gdm understand german keyboard input? I can find many discussions, hints and ideas in the web, but whatever I try, gdm stubbornly insists on using en_US default keyboard. I am running gdm-3.16.4_3 from ports on FreeBSD 11.1-RELEASE amd64 . My german keyboard is supported on console and "inside" Gnome 3 , but not on gdm's username/password dialog. Thanks an greetings Peter From owner-freebsd-questions@freebsd.org Fri Feb 2 04:16:05 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 786F8EE2F4A for ; Fri, 2 Feb 2018 04:16:05 +0000 (UTC) (envelope-from frankfenderbender@council124.org) Received: from vps349.pairvps.com (vps349.pairvps.com [216.92.231.69]) (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 2816F78BC2 for ; Fri, 2 Feb 2018 04:16:04 +0000 (UTC) (envelope-from frankfenderbender@council124.org) Received: from [192.168.0.100] (unknown [104.220.39.23]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by vps349.pairvps.com (Postfix) with ESMTPSA id C0A6FA6399; Thu, 1 Feb 2018 23:16:03 -0500 (EST) Subject: anyone use different PCI Express card & slot #s? Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=windows-1252 From: C Gray In-Reply-To: <69060D2E-8ED1-4BDB-8801-2BA29F15C632@council124.org> Date: Thu, 1 Feb 2018 20:16:02 -0800 Reply-To: C Gray Content-Transfer-Encoding: quoted-printable Message-Id: References: <8F08E935-33A8-4B5F-9057-51FAD51DA97D@council124.org> <20180201121251.95e345cf.freebsd@edvax.de> <09DEB81A-3DC1-4147-9249-0497C89F429B@council124.org> <69060D2E-8ED1-4BDB-8801-2BA29F15C632@council124.org> To: freebsd-questions@freebsd.org X-Mailer: Apple Mail (2.1085) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 04:16:05 -0000 While [re]searching PIC-X, PCIe x{1,4,8.16} internal slots and cards, I = came across this=20 interesting usage suggested by a bright ICT author: "... A little-known fact is that you can install any PCI Express = expansion card in any=20 PCI Express slot.=20 For example, you can install an x1 expansion card in any kind of = PCI Express slot;=20 it doesn=92t need to be installed in an x1 slot.=20 So, if you have an x4 expansion card but your motherboard = doesn=92t have an=20 x4 PCI Express slot, no problem; simply install it in an x8 or = x16 slot. The same holds true for =93bigger=94 cards. For example, you can = install an x16=20 video card in a =93smaller=94 slot. (The slot, however, must = have its rear side open;=20 otherwise, the bigger expansion card won=92t fit. It is up to = the motherboard manufacturer=20 whether or not to provide slots with their rear side open.) The = only disadvantage is=20 that it will only have the maximum bandwidth provided by the = slot; i.e., if you install=20 an x16 video card in an x4 slot, it will have only x4 bandwidth = available. ..." -- from "Everything You Need to Know About the PCI Express" - by = Gabriel Torres (July 12, 2012) = http://hardwaresecrets.com/everything-you-need-to-know-about-the-pci-expre= ss/4/ Has anyone tried an x1 expansion (sound) card, esp. manufactured by = Creative Labs,=20 in either an x4 or x8 slot? I'd like to know how it has worked out for you, and how it has affected = your system's other slots? Thanks, C Gray frankfenderbender@council124.org From owner-freebsd-questions@freebsd.org Fri Feb 2 04:36:25 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 25BB9EE3C78 for ; Fri, 2 Feb 2018 04:36:25 +0000 (UTC) (envelope-from frankfenderbender@council124.org) Received: from vps349.pairvps.com (vps349.pairvps.com [216.92.231.69]) (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 CDCF9794D1 for ; Fri, 2 Feb 2018 04:36:24 +0000 (UTC) (envelope-from frankfenderbender@council124.org) Received: from [192.168.0.100] (unknown [104.220.39.23]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by vps349.pairvps.com (Postfix) with ESMTPSA id EC041A6399; Thu, 1 Feb 2018 23:36:23 -0500 (EST) Subject: followup: anyone use different PCI Express card & slot #s? Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: C Gray In-Reply-To: Date: Thu, 1 Feb 2018 20:36:22 -0800 Reply-To: C Gray Content-Transfer-Encoding: quoted-printable Message-Id: <0D88BD2A-7DD3-4EB8-A33E-BEB18CE5122A@council124.org> References: <8F08E935-33A8-4B5F-9057-51FAD51DA97D@council124.org> <20180201121251.95e345cf.freebsd@edvax.de> <09DEB81A-3DC1-4147-9249-0497C89F429B@council124.org> <69060D2E-8ED1-4BDB-8801-2BA29F15C632@council124.org> To: freebsd-questions@freebsd.org X-Mailer: Apple Mail (2.1085) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 04:36:25 -0000 This opens up lots of short-term solutions to my Dell PowerEdge T300, = which came w/o a sound card. Nonetheless, wasting slots is a bit foolish, so I am still searching for = an x4 sound card that is supported=20 by FreeBSD drivers. Along the way, I am finding many imaginative tips = such as these two.... Q: I have a PCI Express 4x slot on my Asus Crosshair = motherboard.=20 It is open ended, but there are capacitors directly behind = it blocking any 16x cards.=20 So, what are PCI Express 4x slots for? What would I put = there? A: The PCI Express 4X connector has 64 pins and is intended to = be used on servers,=20 but not limited to servers: - PCIe x1 card in a PCIe x16 slot will run at PCIe x1 = speeds - PCIe x16 card in a PCIe x16 slot will run at PCIe x16 = speed. - PCIe cards are all backwards compatible, as in a x1, = x2, x4, x8 cards will all work in a PCIe x16 slot - x1, x2, x4 will all work in a PCIe x8/x16 slot - x1, x2 will all work in a PCIe x4/x8/x16 slot - x1 will all work in a PCIe x2/x4/x8/x16 slot -- from "What are PCI Express 4x slots made for?" - by Dougx1317 = (June 9, 2009) = Q: What can you do with a PCI Express x4 slot? A: Except for the most powerful of video cards, you can do = pretty much everything with=20 an x4 slot, and without any adapters, as well. Plenty of boards with x4 slots have them open ended, so a = x16 card will fit just fine=20 (and work at x4). So HDTV tuners, RAID controllers, cards = for PhysX, video cards to=20 drive more monitors, sound cards, 10Gbit Ethernet (don't ask = me why, though...lol).... -- from "What can you do with a PCI Express x4 slot?" - by = Yukikaze (Sep 24, 2008) = Anyone found a affordable/non-cloned//FreeBSD-supported sound board = solution for a server=20 running the latest LTS TrueOS... utilizing PCIe x4/x4/x8/x16 (with no = x1) slots? thanks, chris gray frankfenderbender@council124.org From owner-freebsd-questions@freebsd.org Fri Feb 2 05:48:31 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7EFEBEE6C34 for ; Fri, 2 Feb 2018 05:48:31 +0000 (UTC) (envelope-from giaphu8000@gmail.com) Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::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 159CB7B89D for ; Fri, 2 Feb 2018 05:48:31 +0000 (UTC) (envelope-from giaphu8000@gmail.com) Received: by mail-it0-x230.google.com with SMTP id h129so6601993ita.2 for ; Thu, 01 Feb 2018 21:48:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:subject:from:to:mime-version :content-transfer-encoding; bh=041AX/7yGVc850AlSwC7DuERo7KW1yPaqRkEm0l/kYE=; b=lSjMrOoCUmAOaFexqwZE8IW9/gKO5BgBjRlN3tbtD9Jp0jkZ/NwqX524BU1V+aYsC2 OT1cOm7YQd2YW1oFzT4VXBVRWdeJR+v3XxoC+YKsfCrdp+AMqnTZBYMrQwYfJbl7uVlv Fzwv2pIsWWD522Z/yB8+Nybt+gnBQUJEG3fDsHUKFxKMgqVfCx5JrK59AQWgmhJlMPYk fB485BANQZTnGSxXfBM5shAm0kzQjXjoQCG63h8wHTHNn7JgbYkW+omKdO419/Fw2vq9 Qfd8eZJpx+sZF+naa3bVamv7jkuZpa3YVamew6HDesqP6/Y4AQfRbgsxN+I4n1GtYdtA OotA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:subject:from:to:mime-version :content-transfer-encoding; bh=041AX/7yGVc850AlSwC7DuERo7KW1yPaqRkEm0l/kYE=; b=ak+K4BzFzjG/rfYVJ5DlFaOjvOrKY21cpuOiqreNUjXnhI19LDMgvgymBqFdnS2Cck sfR/fnfDNtbr3KzCUCmfLxuejTgBYXxyfpt5fILLddBllh3XuEL4TziH6ClOM4qfWGpF vzdVezthptfkRp2oq8nfwBRhCVtBS//mDxaqdD67aDb09bUXBHs7lES57Qu9NPhKOvwZ sN+9yuJTu0vOlyBPDN3q7O3xIFcNp8SzxcTtxkeSD1JkkoWfqFb+xhM2EfBHN+BBy00o PgX5fVC5OGiwUOMWy+4br2uCf7Y3pmrYrr7jKv34nJSugmdo4bhvgWmz+Y61lW8GizJa oxdA== X-Gm-Message-State: AKwxytcl0HmDVgFU1zVttamem3icXgdyr7x6x6Y+w5Yq61h5YVxGu2A8 bjtPvLPphFgMCf6aWNHR8plYOi6x X-Google-Smtp-Source: AH8x224HHuyt8ugRoSvgn7dNw3i0paSQjMv9fOOHoLSrlhyqFBJ2dvgy6EOqdvlAh3+dDcD1YcxjwA== X-Received: by 10.36.192.10 with SMTP id u10mr43837020itf.73.1517550510140; Thu, 01 Feb 2018 21:48:30 -0800 (PST) Received: from [192.168.1.104] ([115.79.30.154]) by smtp.gmail.com with ESMTPSA id 82sm783689iod.54.2018.02.01.21.48.27 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Feb 2018 21:48:29 -0800 (PST) Message-ID: <5a73fbad.55036b0a.7f6d6.4b38@mx.google.com> Date: Fri, 02 Feb 2018 12:48:19 +0700 Subject: The sea From: "giaphu8000@gmail.com" To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 05:48:31 -0000 CgrEkMOjIGfhu61pIHThu6sgSHVhd2VpIERpIMSR4buZbmcgY+G7p2EgdMO0aQ== From owner-freebsd-questions@freebsd.org Fri Feb 2 11:18:32 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3AC97ED13A5 for ; Fri, 2 Feb 2018 11:18:32 +0000 (UTC) (envelope-from pathiaki2@yahoo.com) Received: from sonic310-21.consmr.mail.ne1.yahoo.com (sonic310-21.consmr.mail.ne1.yahoo.com [66.163.186.202]) (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 CA21386AC9 for ; Fri, 2 Feb 2018 11:18:31 +0000 (UTC) (envelope-from pathiaki2@yahoo.com) X-YMail-OSG: x.GxR1gVM1kH9Pmnu7Sdn7oYzDANGkPIxU1Yy3NGp_zQ5L2kWGCH0y5OsVzfiqj fLgVIAKngFeeB2tkvz3jxUBWoZzT8ckNoPMe84rdJWwdDQm.H_n6mJpk9OzCpPQdysfR8CJ5tLB5 joLW7So8EVIV.CnRz3snAlmdd5UhP1ECLSa8QV01mXeO3VK0J5U7xoXBuXEdvVfE.u3b0dmvsxeC KcufH6rBw8o8RtGlnFQsrVqwRGoWuwk4NyX5y.5cY9dLMaULbo4k0aubkBX1sc.JQtn9Ls4FneIA AmAdGctcFUmVnmw84WetKiK.Dk.SJ7.I37U740OG__fo2CLGZFRIaIxro8yFjgkj_USmu4sl4bmX FgOa_WW4MKhu_kfQ3faqFuyoRSuVu_Zd.D_h514IOEl77.Llgl9E_R9vzqIaaHYNJLGIGXuO8SQO En851vqCxBL5vj2uq9_txjvX0QHLFEYAt68Gkhb5O87._BNAjUhqqz7cvrFWcC.bXyaapqT.5Yd1 3.FJaXkBbtrP.EQr6VvXpdu2sNQ2cjKIDPep_a49x Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.ne1.yahoo.com with HTTP; Fri, 2 Feb 2018 11:18:25 +0000 Received: from smtp234.mail.ne1.yahoo.com (EHLO [192.168.0.6]) ([10.218.253.207]) by smtp416.mail.ne1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID 34e5ac256949f0b3644ba1915dc37ff2 for ; Fri, 02 Feb 2018 11:18:21 +0000 (UTC) Subject: Re: Response to Meltdown and Spectre To: freebsd-questions@freebsd.org References: <23154.11945.856955.523027@jerusalem.litteratus.org> <5A726B60.7040606@gmail.com> <92120E50-19A7-4A44-90DF-505243D77259@kreme.com> From: Paul Pathiakis Message-ID: <044e62f7-69ca-71fe-34a8-5c5cafc06f08@yahoo.com> Date: Fri, 2 Feb 2018 06:18:20 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 11:18:32 -0000 On 02/01/2018 22:14, @lbutlr wrote: > On 1 Feb 2018, at 16:04, Adam Vande More amvandemore@gmail.com> wrote: >> On Thu, Feb 1, 2018 at 3:48 PM, @lbutlr wrote: >> >>> the trouble is that AMD's behavior has been at least as bad as Intel's, if >>> not worse, in regards to Meltdown, >>> >> Can you explain what provoked this assertion? > First, they violated (not technically, but they made it bloody obvious) the NDA so that the flaw was widely discovered a week early by adding a comment to a meltdown patch that lead every expert int he field straight to the vulnerability: "The AMD microarchitecture does not allow memory references, including speculative references, that access higher privileged data when running in a lesser privileged mode when that access would result in a page fault." > > Second, they initially claimed they were would not release any firmware because they were entirely immune, which was untrue. > > They were almost immediately proved to be vulnerable to some of the flaws. > > Third, while Intel released (and continues to release) detailed technical information, AMD released PR statements. > > Honestly, as bad as Intel has looked in the last month, AMD looks worse since they'd behaved like children. > This is the exact opposite of what I have seen/read. What NDA is this? "A week early"? Again, this was found out about in June of last year to affect intel architecture. A flaw that existed for over 10, if not 20 years. They did not release the information, Google researchers and other independents did.... Again, they stated the are immune to all variants of 1 and almost non-zero potential to the other. They have not changed this story at all. Again, proving what they stated is just someone doing due diligence and they made a public statement as to which ones that could under the right 'blue moon' circumstances MIGHT be exploited. Their statement is that they would do 'what is necessary' to mitigate ANY risk from them no matter how small. Intels patches have 'bricked' processors. Yes, made them totally unusable as they rushed them out the door. They pulled them immediately and told people to destroy them. I consider that 'highly irresponsible' as their QA is shabby or not-fully encompassing. Intel and AMD cannot release detailed information as it will make it a lot more obvious as to hack those ships. As far as I know, making a user's product useless by bricking them due to lack of testing was the most irresponsible thing anyone can do and that wasn't AMD who did it. Another thing I find disturbing about the situation is that Intel, already knowing about the vulnerability, pushed out the i9 series knowing it had the same fundamental flaw and putting more chips out there with the issue. Also, firmware is not the only problem but OS memory management is another issue. TG for FreeBSD and it's proper design and management. P. From owner-freebsd-questions@freebsd.org Fri Feb 2 13:14:23 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 23292ED8E3D for ; Fri, 2 Feb 2018 13:14:23 +0000 (UTC) (envelope-from robroy@robroygregg.com) Received: from mail.robroygregg.com (173-13-147-189-sfba.hfc.comcastbusiness.net [173.13.147.189]) (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 92F546B0B4 for ; Fri, 2 Feb 2018 13:14:21 +0000 (UTC) (envelope-from robroy@robroygregg.com) Received: from beak.h.net (beak.h.net [192.168.32.10]) by mail.robroygregg.com (OpenSMTPD) with ESMTP id 97609b75; Fri, 2 Feb 2018 05:07:39 -0800 (PST) Date: Fri, 2 Feb 2018 05:07:39 -0800 (PST) From: Robroy Gregg X-X-Sender: robroy@beak.h.net To: C Gray cc: freebsd-questions@freebsd.org Subject: Re: followup to my previous sound-card/driver question In-Reply-To: <69060D2E-8ED1-4BDB-8801-2BA29F15C632@council124.org> Message-ID: References: <8F08E935-33A8-4B5F-9057-51FAD51DA97D@council124.org> <20180201121251.95e345cf.freebsd@edvax.de> <09DEB81A-3DC1-4147-9249-0497C89F429B@council124.org> <69060D2E-8ED1-4BDB-8801-2BA29F15C632@council124.org> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 13:14:23 -0000 'morning Chris, On Thu, 1 Feb 2018, C Gray wrote: > I just want some audio for my Python/PHP/Java/Javascript/Perl/C > development server. For this use I'd recommend skipping the internal sound card all together, and buying an external, USB-connected sound card (DAC). This one works fine for me with FreeBSD 11.1-RELEASE in a USB 2.0 port: http://www.m-audio.com/products/view/micro-dac-24-192 I bought one through eBay for $49. You just plug this item in to any USB 2.0 or 3.0 port (no penalty for 2.0), plug your headphones in, and you have sound--and the sound quality seems excellent. A USB connected sound card may seem hokey, but I gather from the more audio-inclined that it's a nicer design since it's less subject to EMI than internal cards. To respond to your other questions about PCI-e card mixing'n'matching, here are a few goofy things I did recently that completely worked (also with 11.1-RELEASE): a] A QLE2562 (PCI-e 2.0 x8) card in a PCI-e 3.0 x4 slot b] An nVidia PCI-e 3.0 x16 card in a PCI-e 2.0 x8 slot Yet I think you'll be better off using the external DAC and saving your PCI-e slots for a card that can actually use the bandwidth. Days of joy to you Chris From owner-freebsd-questions@freebsd.org Fri Feb 2 13:24:15 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AD4E3ED95A0 for ; Fri, 2 Feb 2018 13:24:15 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0DC7A6B5A1 for ; Fri, 2 Feb 2018 13:24:14 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.213.55]) by mrelayeu.kundenserver.de (mreue101 [212.227.15.183]) with ESMTPA (Nemesis) id 0MI6MY-1ejG5F2scI-003upP; Fri, 02 Feb 2018 14:11:15 +0100 Date: Fri, 2 Feb 2018 14:11:15 +0100 From: Polytropon To: Peter Ulrich Kruppa Cc: freebsd-questions@freebsd.org Subject: Re: German keyboard support for gdm??? Message-Id: <20180202141115.aa7bbf16.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-Provags-ID: V03:K0:MFTcGsbbuh+ZUuHME4VWHK1Pd+BIvmqmorTEG1mPJfO70p7l65n P7TTATq+5WGeCI8gDioOWbvkwoSgADwJx2vAnz2TuBK5oLpgOQlFItLfnDmpeTWrz5gmlci 4jj7nOJsv67FtC8eBz39SJkw2yNLYpsXv+vHFHMd/upV3fNMiPnlibPtF+ab10BONOPPWTG dZmjP20tPT4Ab9cvloJ9A== X-UI-Out-Filterresults: notjunk:1;V01:K0:TDaPSRWGFOU=:2KgBHX1N9IGrpGn0Y+9KBW FYupi6cm6XaWDqQM0N+BHncWb2GzWeikduTS7S/Ap/j5UbC+vXwEaYl3o1PG/eBnuZJBxGwu3 cVZG5fDudm2J76cPZr+3F0p8v/zIyCg1bZ8nkEXyWq71/ZXieOqjywSk6eONohCq/QUr74F9M CqZxcnncy/1R43gqhOu5/4Jl4NdDvCkG8VrByYRQVsVQyScuU1xwTvjjen7XHjO85qQvS1HXw Sy2aZ8QC5k6mH+m45xOh6iLPAq4dnqy+DDBH7AWdbohQu8vXoRrtZngYYlbkwuoHqZUoZcHuU DgxwipdUeS63xKl7GKKmprk7ytXmiEaLFojSRAn0GQNn3l6cxg7UF+ibQSsh1IGvPQX7W3Z8j qaMZD859jPvT6q9r3Gf6MUOmlaPKzvMdLImalLeO1Jhb5D94fUzTzR8b6glsZMqUrkt6nNjwy iaDkRiGgAun5WVttrmdYoMZ8qlz1v3e5iZ84/Pp0GcPZjE3QPFfBYYsJaRS9T15Sl0HnDefK/ e2bH9FJ9noKhKSahvs6OsPWhwvDbJLUYjSf0jjpUo3t2L20/LVw23k1Tz4Xce+sC465fCSxzj fA1VU6UK/7M27aLQ8KYCCRHLitAzkif78S8OavjCVwKN7v9X3kpZC/o1Lr5dFyWCBSkLxD+P2 3vjDU6VGIStlcS/zFmXxhvMkWImhrUPjrU5lxxyGyrW1VAuq2Gx+sQ6cYn+cyNsjqyq8Hx7o4 /hwdnFM/iOILFt8QTHkuBjsKhjRY4Tqeuz26TD28J2jKBNUEbLa0CbvctjY= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 13:24:15 -0000 On Fri, 2 Feb 2018 05:04:24 +0100, Peter Ulrich Kruppa wrote: > does anyone know how to make gnome's display manager gdm understand german > keyboard input? Historically, you put an entry in /etc/X11/xorg.conf, but today, this is not so easy anymore. There are at least two options: a) Use X11 cofiguration /usr/local/etc/X11/xorg.conf.d/keyboard-de.conf Section "InputClass" Identifier "KeyboardDefaults" Driver "keyboard" MatchIsKeyboard "on" Option "XkbLayout" "de" EndSection See chapter 5.4.7.1. in the handbook: https://www.freebsd.org/doc/handbook/x-config.html b) Use HAL configuration /usr/local/etc/hal/fdi/policy/x11-input.fdi: pc102 fr See chapter 5.9. in the handbook: https://www.freebsd.org/doc/handbook/x11-understanding.html c) Use Gnome's configuration utility (the one which can also configure gdm). I've never used that, so I cannot be more specific, sorry. :-) > I can find many discussions, hints and ideas in the web, but whatever I > try, gdm stubbornly insists on using en_US default keyboard. Which idea(s) did you already test? > I am running gdm-3.16.4_3 from ports on FreeBSD 11.1-RELEASE amd64 . > My german keyboard is supported on console and "inside" Gnome 3 , but not > on gdm's username/password dialog. Which can cause lots of "fun" if you're user name or password includes german Umlauts, Eszett, and special characters. ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Fri Feb 2 14:24:41 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 71277EDBF25 for ; Fri, 2 Feb 2018 14:24:41 +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 130E66D559 for ; Fri, 2 Feb 2018 14:24:40 +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 9C02562467 for ; Fri, 2 Feb 2018 09:24:39 -0500 (EST) 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 xY6r8F9SKGZ0 for ; Fri, 2 Feb 2018 09:24:36 -0500 (EST) 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 8F61D623EF for ; Fri, 2 Feb 2018 09:24:35 -0500 (EST) Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Fri, 2 Feb 2018 09:24:35 -0500 Message-ID: <42dc63c396f2550226e56325c9474ddc.squirrel@webmail.harte-lyne.ca> Date: Fri, 2 Feb 2018 09:24:35 -0500 Subject: cat to standard out acts like tail From: "James B. Byrne" To: 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 14:24:41 -0000 FreeBSD-11p6 # ll /bin/cat -r-xr-xr-x 1 root wheel 13288 Nov 13 10:00 /bin/cat [root@inet19 ~]# ll /bin/cat -r-xr-xr-x 1 root wheel 13288 Nov 13 10:00 /bin/cat # wc /etc/rc.conf 46 226 2093 /etc/rc.conf # cat /etc/rc.conf | wc 46 226 2093 # cat -n /etc/rc.conf 12 13 # Cloned i/f and assigned ipv4 addr for jails 14 cloned_interfaces="lo1 lo2 lo3" # For shared jail configuration 15 ipv4_addrs_lo1="127.0.100.1/32" # idempaire / theheart 16 ipv4_addrs_lo2="127.0.109.1/32" # redmine - wiki / pas 17 ipv4_addrs_lo3="127.0.107.1/32" # redmine - wiki / pas 18 19 ### Firewall 20 # This is a bhyve vm and the firewall is handled on the host system 21 pf_enable="No " # Enable PF firewall on startup 22 pflog_enable="YES" # Enable logging 23 pflog_logfile="/var/log/pflog" # where pflogd should store the logfile 24 pflog_flags="" # additional flags for pflogd startup 25 26 ### Services 27 local_unbound_enable="YES" # Enable caching only DNS 28 ntpd_enable="YES" # Enable local network time server 29 postfix_enable="YES" # Enable Postfix SMTP MTA 30 sendmail_enable="NONE" # Disable Sendmail SMTP MTA 31 sshd_enable="YES" # Enable ssh access 32 33 ### Jailed Services 34 #jail_enable="YES" # Set to NO to disable starting of any jails 35 ezjail_enable="YES" # Use EZJail to manage 36 #jail_list="hllidempiere \ 37 # hll107 \ 38 # hllredmine" # Space separated list of names of jails 39 40 ### File system 41 clear_tmp_enable="YES" # Clear /tmp on boot 42 #dumpdev="NO" # Disable crash dumps 43 dumpdev="AUTO" # Enable crash dumps 44 zfs_enable="YES" # Enable zeta file-system 45 46 syslogd_flags="-b 127.0.0.1 -b 192.168.216.19 -b 216.185.71.19" What happened to the first 11 lines? -- *** 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 Fri Feb 2 14:42:16 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9EC2EDC917 for ; Fri, 2 Feb 2018 14:42:16 +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 2747F6DF73 for ; Fri, 2 Feb 2018 14:42:15 +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 0F15762460 for ; Fri, 2 Feb 2018 09:42:15 -0500 (EST) 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 poFT7CRAdwzm for ; Fri, 2 Feb 2018 09:42:12 -0500 (EST) 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 6A8036231C for ; Fri, 2 Feb 2018 09:42:12 -0500 (EST) Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Fri, 2 Feb 2018 09:42:12 -0500 Message-ID: <737005a0c3e97d8d1e9306eb52471f89.squirrel@webmail.harte-lyne.ca> Date: Fri, 2 Feb 2018 09:42:12 -0500 Subject: Jails, ping, and now DNS From: "James B. Byrne" To: 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 14:42:17 -0000 Ok, this jail setup thing is slowly driving me mad. Can someone explain the following behaviour observed on a jail (hll124) set up using ezjail? root@hll107:~ # sysctl security.jail.allow_raw_sockets security.jail.allow_raw_sockets: 1 root@hll107:~ # service local_unbound onestatus local_unbound is running as pid 76810. root@hll107:~ # drill vhost04.hamilton.harte-lyne.ca ;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4 ;; QUESTION SECTION: ;; vhost04.hamilton.harte-lyne.ca. IN A ;; ANSWER SECTION: vhost04.hamilton.harte-lyne.ca. 172765 IN A 216.185.71.44 ;; AUTHORITY SECTION: harte-lyne.ca. 172765 IN NS dns04.harte-lyne.ca. harte-lyne.ca. 172765 IN NS dns01.harte-lyne.ca. harte-lyne.ca. 172765 IN NS dns03.harte-lyne.ca. harte-lyne.ca. 172765 IN NS dns02.harte-lyne.ca. ;; ADDITIONAL SECTION: dns01.harte-lyne.ca. 172765 IN A 216.185.71.33 dns02.harte-lyne.ca. 172765 IN A 209.47.176.33 dns03.harte-lyne.ca. 172765 IN A 216.185.71.34 dns04.harte-lyne.ca. 172765 IN A 209.47.176.34 ;; Query time: 0 msec ;; SERVER: 127.0.0.1 ;; WHEN: Fri Feb 2 14:34:17 2018 ;; MSG SIZE rcvd: 208 root@hll107:~ # ping 216.185.71.44 PING 216.185.71.44 (216.185.71.44): 56 data bytes 64 bytes from 216.185.71.44: icmp_seq=0 ttl=64 time=0.357 ms 64 bytes from 216.185.71.44: icmp_seq=1 ttl=64 time=0.382 ms ^C --- 216.185.71.44 ping statistics --- 3 packets transmitted, 2 packets received, 33.3% packet loss round-trip min/avg/max/stddev = 0.357/0.369/0.382/0.012 ms root@hll107:~ # ping vhost04.hamilton.harte-lyne.ca ping: cannot resolve vhost04.hamilton.harte-lyne.ca: Host name lookup failure root@hll107:~ # -- *** 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 Fri Feb 2 14:46:26 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85351EDCDE8 for ; Fri, 2 Feb 2018 14:46:26 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (mail.dpedia.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 1D3186E1B3 for ; Fri, 2 Feb 2018 14:46:25 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [88.217.125.30] (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 1ehcbe-00022M-Jw for freebsd-questions@freebsd.org; Fri, 02 Feb 2018 15:46:22 +0100 Received: from localhost.my.domain (localhost [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id w12EkLax003077 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 2 Feb 2018 15:46:21 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id w12EkKMf003076 for freebsd-questions@freebsd.org; Fri, 2 Feb 2018 15:46:20 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Fri, 2 Feb 2018 15:46:20 +0100 From: Matthias Apitz To: freebsd-questions@freebsd.org Subject: Re: cat to standard out acts like tail Message-ID: <20180202144620.GA3050@c720-r314251> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , freebsd-questions@freebsd.org References: <42dc63c396f2550226e56325c9474ddc.squirrel@webmail.harte-lyne.ca> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ew6BAiZeqk4r7MaW" Content-Disposition: inline In-Reply-To: <42dc63c396f2550226e56325c9474ddc.squirrel@webmail.harte-lyne.ca> 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.125.30 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 14:46:26 -0000 --ew6BAiZeqk4r7MaW Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable El d=C3=ADa viernes, febrero 02, 2018 a las 09:24:35a. m. -0500, James B. B= yrne via freebsd-questions escribi=C3=B3: > FreeBSD-11p6 >=20 > # ll /bin/cat > -r-xr-xr-x 1 root wheel 13288 Nov 13 10:00 /bin/cat >=20 > [root@inet19 ~]# ll /bin/cat > -r-xr-xr-x 1 root wheel 13288 Nov 13 10:00 /bin/cat > # wc /etc/rc.conf > 46 226 2093 /etc/rc.conf > # cat /etc/rc.conf | wc > 46 226 2093 > # cat -n /etc/rc.conf >=20 > 12 > 13 # Cloned i/f and assigned ipv4 addr for jails > 14 cloned_interfaces=3D"lo1 lo2 lo3" # For shared jail configurati= on > 15 ipv4_addrs_lo1=3D"127.0.100.1/32" # idempaire / theheart > 16 ipv4_addrs_lo2=3D"127.0.109.1/32" # redmine - wiki / pas =2E.. > 45 > 46 syslogd_flags=3D"-b 127.0.0.1 -b 192.168.216.19 -b 216.185.71.19" >=20 > What happened to the first 11 lines? Please check with 'od -c ...' the content of the file or do # cat -n /etc/rc.conf > /tmp/x # vi /tmp/x matthias --=20 Matthias Apitz, =E2=9C=89 guru@unixarea.de, =E2=8C=82 http://www.unixarea.d= e/ =F0=9F=93=B1 +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub --ew6BAiZeqk4r7MaW Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEXmn7rBYYViyzy/vBR8z35Hb+nREFAlp0ebkACgkQR8z35Hb+ nRHpORAAiRCSxW6Zujthnd7ZMQaKYeXv1eYR/ynwsYfYFTJq+rBdFZJFEn7i+vEN UYriy7gdxjWCEDPlhzSkLUTI7IwrIols2lYxswy9Pum0E3XhRZ3ynEwKyvmQhV99 UjYb0bV3rzPlGM16d7Kv28JDVBREDFtppoOqcT0P/Ad02GqfpBk998NCUPhLIreH BCULoQYqpzNxZGAfUHkx+kVpsJTGIEdrQH4ruySgDlKSlcZEQd2OsQ3Mn4id3N0J qSmobVcoVt7hW5lZB2ogY9Kre+DFOqy1CiezEx6pCUxBuUhxlk6/L9rIsjZIYGve c2BkZrAzuuknz4NnzWj0uKam5AqBWYBR4dpMo4d920h1GThDBmOYn1f3LkxZoMd+ xTM+PYkclpX9Rk5PIgG6V8CFJiz1m7MqXV3NVKxRoMFJ/S8GYItLRYRfL5AutXKf 7bf1Tj7zfo74ET/WVdXfJUiAOiLLMRbyosmBpW5mX+xOCWRokd9F6adhnnupkTps 6Yg+Ws+oLcZe7wnPJNW965efMGnJKT01boAGkdJ4f8Llc+HtBOuF7xgUbuYvUdrO /lbCxxOsD4RsXYHPK3wFdVG6JWdtr4ZcKkn/pO2O2qEElBqshsoXc2DkM3Y0ZTtL HN1ma5hIqm2GH7S/lfnzMUjHDAWvyRYIVSWVMfCP/GtN6aRdNQI= =B+50 -----END PGP SIGNATURE----- --ew6BAiZeqk4r7MaW-- From owner-freebsd-questions@freebsd.org Fri Feb 2 15:44:34 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7BF1BEDFA1F for ; Fri, 2 Feb 2018 15:44:34 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::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 0D0D07090E for ; Fri, 2 Feb 2018 15:44:34 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-io0-x232.google.com with SMTP id f89so23349238ioj.4 for ; Fri, 02 Feb 2018 07:44:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=aCauHs4/tQ+deYhR3OCOmHRFS81qiVcu4GX3amW0Scg=; b=Xlrc0bVNPCVFHcBBSWAoqfkY/d3ji0t8ISYoELgo/2nVemhoy69BoYly73wO/j+pQ4 D8LXOQcZIQjQn/lI4J94FuCpfXmXVjbf0x9UYjIaNpsfa2Y+5W081snO2kP3nWMVXTas yaT/C2XPvdJUKSEIliPyhK+qF5nPNQi2kAiQN/fn1MIpylyysbv+Bz5UYNDIhryrYWt4 IX2CW6FzGb/Gk5ZRsoymIQvwVEjQn824QyBk/dm4Xn95tELtbjzLvy1AHrBLfuVMtkRZ RGy78q1mW3PJHfq8L2qhTib7MJkQgRysYp3lNjmPH+g+rBMLiKvyskKWemPWr83CO5h7 gLqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=aCauHs4/tQ+deYhR3OCOmHRFS81qiVcu4GX3amW0Scg=; b=MA2VZG11Pso6Yv2KZxhiCCOKlcR/i044bR8cUGuwb4DgQ76ELlD8UVSWy4Swc0TOvv AkPCNOTUCnAkCwzqiY6wAmaTN2DvB2yxriY6LlGbIgLMkLbDzBlC+Zr1dB50aXOCsrHr X07erUXn5JfD+Gg6dgI0AbjsbGCfHtDEvkxx6R3JcCor4V7cDuzyYrnmvz28XOv0hK8s 3ZCUfdzYVOBBDK5d835oYFkMK3oFiKxBVKDjlepL433O+E/HKq8Lgw2LjlMyvrd3MwVA 84VXV2XmYv+AkoLiB/LrrwMfZRb386xYZQXGLD4Q0pLoVsItPRXA3juuYJaJ/sBx1ODX 5pAg== X-Gm-Message-State: AKwxytewy9Ave0NCn8iWYWMwiP6YMZylDbdT1rxihTJ/JXKfOXPaYLtt BJzqGgUMS8/n9PFMEetvvWg= X-Google-Smtp-Source: AH8x2277T65YzUCmMH1hucKdlOCeZG4EnQWJincHXQZfc8HpHJ5+1O52w1NIyzQqEHFmjDKMhxGOUw== X-Received: by 10.107.132.158 with SMTP id o30mr29042731ioi.70.1517586273394; Fri, 02 Feb 2018 07:44:33 -0800 (PST) Received: from [10.0.10.7] (cpe-65-25-48-31.neo.res.rr.com. [65.25.48.31]) by smtp.googlemail.com with ESMTPSA id f7sm1481243iod.60.2018.02.02.07.44.32 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 02 Feb 2018 07:44:32 -0800 (PST) Message-ID: <5A74875F.9080901@gmail.com> Date: Fri, 02 Feb 2018 23:44:31 +0800 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: byrnejb@harte-lyne.ca CC: freebsd-questions@freebsd.org Subject: Re: Jails, ping, and now DNS References: <737005a0c3e97d8d1e9306eb52471f89.squirrel@webmail.harte-lyne.ca> In-Reply-To: <737005a0c3e97d8d1e9306eb52471f89.squirrel@webmail.harte-lyne.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 15:44:34 -0000 James B. Byrne via freebsd-questions wrote: > Ok, this jail setup thing is slowly driving me mad. Can someone > explain the following behaviour observed on a jail (hll124) set up > using ezjail? > > root@hll107:~ # sysctl security.jail.allow_raw_sockets > security.jail.allow_raw_sockets: 1 > > root@hll107:~ # service local_unbound onestatus > local_unbound is running as pid 76810. > > root@hll107:~ # drill vhost04.hamilton.harte-lyne.ca > > ;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4 > ;; QUESTION SECTION: > > > ;; vhost04.hamilton.harte-lyne.ca. IN A > > ;; ANSWER SECTION: > vhost04.hamilton.harte-lyne.ca. 172765 IN A 216.185.71.44 > > ;; AUTHORITY SECTION: > harte-lyne.ca. 172765 IN NS dns04.harte-lyne.ca. > harte-lyne.ca. 172765 IN NS dns01.harte-lyne.ca. > harte-lyne.ca. 172765 IN NS dns03.harte-lyne.ca. > harte-lyne.ca. 172765 IN NS dns02.harte-lyne.ca. > > ;; ADDITIONAL SECTION: > dns01.harte-lyne.ca. 172765 IN A 216.185.71.33 > dns02.harte-lyne.ca. 172765 IN A 209.47.176.33 > dns03.harte-lyne.ca. 172765 IN A 216.185.71.34 > dns04.harte-lyne.ca. 172765 IN A 209.47.176.34 > > ;; Query time: 0 msec > ;; SERVER: 127.0.0.1 > ;; WHEN: Fri Feb 2 14:34:17 2018 > ;; MSG SIZE rcvd: 208 > > root@hll107:~ # ping 216.185.71.44 > PING 216.185.71.44 (216.185.71.44): 56 data bytes > 64 bytes from 216.185.71.44: icmp_seq=0 ttl=64 time=0.357 ms > 64 bytes from 216.185.71.44: icmp_seq=1 ttl=64 time=0.382 ms > ^C > --- 216.185.71.44 ping statistics --- > 3 packets transmitted, 2 packets received, 33.3% packet loss > round-trip min/avg/max/stddev = 0.357/0.369/0.382/0.012 ms > > root@hll107:~ # ping vhost04.hamilton.harte-lyne.ca > ping: cannot resolve vhost04.hamilton.harte-lyne.ca: Host name lookup > failure > > root@hll107:~ # > > > Your problem is your using ezjail which uses the deprecated rc.conf environment-variable method. Most jail users have stopped using ezjail so support for problems like you are having is very limited. Every time you start a ezjail jail an error message popes out telling you to convert your jail system to the jail.conf method. That error message has been issued since 9.1. Its about time you do as it says before you get caught with a unsupported production jail environment. There is a good chance the deprecated rc.conf environment-variable method will be removed in 12.0 release. If you are addicted to the ezjail jail coding method then check out qjail which is a fork of ezjail that uses the jail.conf method. From owner-freebsd-questions@freebsd.org Fri Feb 2 16:08:48 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ABD0BEE1068 for ; Fri, 2 Feb 2018 16:08:48 +0000 (UTC) (envelope-from opsyspref@gmail.com) Received: from mail-ot0-x241.google.com (mail-ot0-x241.google.com [IPv6:2607:f8b0:4003:c0f::241]) (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 3B4C6717AF for ; Fri, 2 Feb 2018 16:08:48 +0000 (UTC) (envelope-from opsyspref@gmail.com) Received: by mail-ot0-x241.google.com with SMTP id a2so9372387otf.2 for ; Fri, 02 Feb 2018 08:08:48 -0800 (PST) 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=YsAjGV3DY9AxSSlKKjBEWhzA3SKLi8Moz06VtOr9YnQ=; b=iMVf3xaDQCk40e8lP3UW2Pt61awLwPUTVjZpTRiOcNwGJjyb+g9gpo45yHyd2bl9u1 zUBdhnzp6GKTSi21YGWtM3GtEGdeNtKSXUH/LzG9hM5TzghnKcAFv+aUlVQukldW7KoA Q8/Y6XBm36t7fwk0pYNysaHFYIzH26SybyBqZKqNJ9j6qQ5MeMx+GPttuuPpQ8oFwZic wfxJhUgH/FVioZ4zJJbn0FtiIHTPCZKhyv84BsIT9Url/q5ftaxg0qzlB3rJ9j0y3vNQ GgDJPoCdOVgprWwY384WNrSWfuNUTduJ229lwb33LzAWzzX8anzdeQOBRHY/cuTmgFTj dkGw== 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=YsAjGV3DY9AxSSlKKjBEWhzA3SKLi8Moz06VtOr9YnQ=; b=cjkFK9yARXyXn6fqm9wOwXGUz77BuDqERSEvP2kHa1Bv89erY8e53FhteLlDERqcDo H+LYQA6TFNiWQ+/wmz5Y4LMwtjWvLQYsHpmJQfkt8HRZ17kvyqh9P6OFWRi5b3QqHyDq idhag/KcTUonvugp+wLaJwrBX1l1RSl5n1vAzPNV10TBzVTpbDUUAEUqo/Pcq/mBDGLu rzNbMfotLk86sw07CfWEneDfYByvH+oQBC3RpnqbK22j+VxJVqZSIGlN1FkV96wVU6p0 Vwr2Ep3Pohn5xFFPG0uRlf1t1OItFHQWpx2l0EkQMXHKpftOv6PeWJG79+wPiOFUQry+ 5Plg== X-Gm-Message-State: AKwxytfsnw/0X9ClOZLT/00Y0JkgUWJjp/ozebbtyJE73lz9duqVLFA+ 1H+d4mSwwLcN5Y0wURmu1ZcFjXh35BcjOMoswecFX8sW X-Google-Smtp-Source: AH8x224xLRUlu5lPcG1zJKrizdWxxECPnZENx34oeok5Szc2+cnIQELzbIXdbk6hN39MMrLuLb0U7vQBPCOujf9Nv6I= X-Received: by 10.157.0.8 with SMTP id 8mr12436022ota.69.1517587727468; Fri, 02 Feb 2018 08:08:47 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.11.203 with HTTP; Fri, 2 Feb 2018 08:08:46 -0800 (PST) In-Reply-To: <20180202141115.aa7bbf16.freebsd@edvax.de> References: <20180202141115.aa7bbf16.freebsd@edvax.de> From: Peter Ulrich Kruppa Date: Fri, 2 Feb 2018 17:08:46 +0100 Message-ID: Subject: Re: German keyboard support for gdm??? To: Polytropon Cc: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 16:08:49 -0000 (I hope this webmailer doesn't produce any HTML mess - it's the first time I try it on a mailing-list) On Fri, Feb 2, 2018 at 2:11 PM, Polytropon wrote: > On Fri, 2 Feb 2018 05:04:24 +0100, Peter Ulrich Kruppa wrote: > > does anyone know how to make gnome's display manager gdm understand > german > > keyboard input? > > Historically, you put an entry in /etc/X11/xorg.conf, > but today, this is not so easy anymore. There are at > least two options: > > a) Use X11 cofiguration /usr/local/etc/X11/xorg.conf.d/keyboard-de.conf > > Section "InputClass" > Identifier "KeyboardDefaults" > Driver "keyboard" > MatchIsKeyboard "on" > Option "XkbLayout" "de" > EndSection > That one I have found myself. It's nice to set german keyboard in twm or xfce4 , but is ignored by gdm. > b) Use HAL configuration /usr/local/etc/hal/fdi/policy/x11-input.fdi: > > > > > > type="string">pc102 > type="string">fr > > > > This one I didn't know. I tried it and checked if hald is started. Result: Nothing, not even a french keyboard :-) And by the way: The space in (behind pc102) will produce some error. > c) Use Gnome's configuration utility (the one which can also > configure gdm). I've never used that, so I cannot be more > specific, sorry. :-) > Which one might that be: I have got gnome-control-center, gnome-tweak-tool and dconf-editor and can't see where anything about gdm could be done ... But in the meantime I found this: https://help.gnome.org/admin/system-admin-guide/stable/keyboard-layout.html.en To me it sounds as if I either need the program localectl , which is only available on Linux or a /dev/input/event which can be produced by installing libudev-devd and rebuilding xorg-server with DEVD option - see the README at https://help.gnome.org/admin/system-admin-guide/stable/keyboard-layout.html.en I will try that, but it will take some time on this old box. Greetings Peter > > > > I can find many discussions, hints and ideas in the web, but whatever I > > try, gdm stubbornly insists on using en_US default keyboard. > > Which idea(s) did you already test? > > > > > I am running gdm-3.16.4_3 from ports on FreeBSD 11.1-RELEASE amd64 . > > My german keyboard is supported on console and "inside" Gnome 3 , but not > > on gdm's username/password dialog. > > Which can cause lots of "fun" if you're user name or password > includes german Umlauts, Eszett, and special characters. ;-) > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... > From owner-freebsd-questions@freebsd.org Fri Feb 2 16:11:35 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 12FB1EE13F9 for ; Fri, 2 Feb 2018 16:11:35 +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 9F01C71A65 for ; Fri, 2 Feb 2018 16:11:34 +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 F40B4624E9 for ; Fri, 2 Feb 2018 11:11:27 -0500 (EST) 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 p4eaeGiF1z0M for ; Fri, 2 Feb 2018 11:11:25 -0500 (EST) 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 C8C9C62467 for ; Fri, 2 Feb 2018 11:11:24 -0500 (EST) Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Fri, 2 Feb 2018 11:11:25 -0500 Message-ID: <31a7ab261a3a67b716edf635923c789c.squirrel@webmail.harte-lyne.ca> In-Reply-To: <5A74875F.9080901@gmail.com> References: <737005a0c3e97d8d1e9306eb52471f89.squirrel@webmail.harte-lyne.ca> <5A74875F.9080901@gmail.com> Date: Fri, 2 Feb 2018 11:11:25 -0500 Subject: [solved] Re: Jails, ping, and now DNS From: "James B. Byrne" To: 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 16:11:35 -0000 On Fri, February 2, 2018 10:44, Ernie Luzar wrote: > > Your problem is your using ezjail which uses the deprecated rc.conf > environment-variable method. Most jail users have stopped using ezjail > so support for problems like you are having is very limited. > Actually, no, the problem is not with ezjail at all. I have re-discovered that network changes relating to jails are not completely cleared with: service netif restart && service routing restart & I had found in the past, but had in the meantime forgotten, that is actually necessary to restart the host system to remove all artefacts of previous jailed network configurations. Once I did that then all of the mysterious problems that I was having in the jail disappeared. The hint was when I compared an existing jail with the new one I was attempting to configure. On the pre-existing jail I saw this: # netstat -an | grep -i listen netstat: kvm not available: /dev/mem: No such file or directory tcp4 0 0 *.22 *.* LISTEN tcp4 0 0 127.0.124.1.53 *.* LISTEN On the jail that I was working on I saw this instead: root@hll107:~ # service local_unbound onestatus local_unbound is running as pid 2792. root@hll107:~ # netstat -an | grep -i listen netstat: kvm not available: /dev/mem: No such file or directory tcp4 0 0 127.0.107.1.25 *.* LISTEN Curious is it not? This problem, no listening port 53 open on the jail whilst unbound is running therein, persisted no matter how many times I reset the netif and routing services; both inside the jail and on the host. Shutting down and restarting the jail did not change anything either. However, shutting down and restarting the host and then starting the jail resulted in this: [root@hll107 ~]# netstat -an | grep -i listen netstat: kvm not available: /dev/mem: No such file or directory tcp4 0 0 127.0.107.1.53 *.* LISTEN tcp4 0 0 127.0.107.1.25 *.* LISTEN So something on the host can get misaligned when one does numerous network configuration changes during setup of a new jail. And the only means I have discovered to correct it is to restart the host. -- *** 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 Fri Feb 2 16:14:44 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85CD1EE1860 for ; Fri, 2 Feb 2018 16:14:44 +0000 (UTC) (envelope-from spointer@humdai.net) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (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 31F3372044 for ; Fri, 2 Feb 2018 16:14:43 +0000 (UTC) (envelope-from spointer@humdai.net) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 266AC2120D for ; Fri, 2 Feb 2018 11:14:43 -0500 (EST) Received: from web2 ([10.202.2.212]) by compute6.internal (MEProxy); Fri, 02 Feb 2018 11:14:43 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=humdai.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=DmBg+mxj76JPtd7BUv3h34Mx5WbHj D/V//b28JQH5Ls=; b=BpxFr7y/7+n1hotJxuiepVQC9ntWSR/KMrW313/MKc3kz KbuBXMUFIPkF0HbVCeNV96ck1FA7Qd+FsmlOeiJmf9DRcdFW+K0GZhLhIe08ffZx ysuhdsMyK9QtmOY5s1l8EZS2jssJohSuEtrfMvaqZBeqE/+HsbR6ilLq9RrJqJwv L7yZQ4zXTvxcZDk07/p4a4kJlLGXht2afABLatBt+0Gd2Z4cxce6Tb7P9ek7LD/Y zxtzvWZV0qvsKrI4AYJor2p9JiqUxDK5YODQjtybylfrp+i7pSn8eIt0CK6A1DWj xkadWyqQ/+1H6ALg1euNgE50Xbs7ueJxGXicZ6Eog== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=DmBg+m xj76JPtd7BUv3h34Mx5WbHjD/V//b28JQH5Ls=; b=C0+hJihfeVAnXECLNYnjzB PkmefQm5AgEZz4hGdBboRLKPQk2H4CCK7oxQMbsdlXbdGIGOJ/YMqLfYawJT1HeA Yn8xJhaUzenWxCQp9uWsQwCx4wIcqiaFKRkOLqLHWVxaZQEmDiQ+HkSz493BH4Mb gH3ebk4BRQoTL41oxxRc7WzfXGwsPu4LxmssQP4xIvYpgLPbbkqKB6yQE2X4q58U iQUpso3MWabrsY1hGD5YjfB9R+HthVgtDLD64/LPdSDGAJox4Imk9951YVPsRqe5 uQDyPQvmXb1XKJDR9L+ntM8VWkKrueRH5KEqLbvB5HUhh7jHkWGURuf1qgcYhCLQ == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 02FF362B78; Fri, 2 Feb 2018 11:14:42 -0500 (EST) Message-Id: <1517588082.2117241.1257377040.499E7DC3@webmail.messagingengine.com> From: Steve Pointer To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-fde26eb3 References: <737005a0c3e97d8d1e9306eb52471f89.squirrel@webmail.harte-lyne.ca> <5A74875F.9080901@gmail.com> In-Reply-To: <5A74875F.9080901@gmail.com> Date: Fri, 02 Feb 2018 16:14:42 +0000 Subject: Re: Jails, ping, and now DNS X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 16:14:44 -0000 > > Your problem is your using ezjail which uses the deprecated rc.conf > environment-variable method. Most jail users have stopped using ezjail > so support for problems like you are having is very limited. > > Every time you start a ezjail jail an error message popes out telling > you to convert your jail system to the jail.conf method. That error > message has been issued since 9.1. Its about time you do as it says > before you get caught with a unsupported production jail environment. > There is a good chance the deprecated rc.conf environment-variable > method will be removed in 12.0 release. > > If you are addicted to the ezjail jail coding method then check out > qjail which is a fork of ezjail that uses the jail.conf method. > The FreeBSD handbook refers to ezjail: https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails.html If this is no longer the best method then maybe this should be changed. If a bug report was posted with edits to the recommended method what do most people use? qjail ? Personally I have had success with iocage , which I understood all the cool kids were using now. https://github.com/iocage/iocage Am I in the minority in using this method? Steve From owner-freebsd-questions@freebsd.org Fri Feb 2 17:11:09 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E5443EE4822 for ; Fri, 2 Feb 2018 17:11:08 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from kicp.uchicago.edu (kicp.uchicago.edu [128.135.20.70]) by mx1.freebsd.org (Postfix) with ESMTP id 955767530B for ; Fri, 2 Feb 2018 17:11:08 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from point.uchicago.edu (point.uchicago.edu [128.135.52.6]) by kicp.uchicago.edu (Postfix) with ESMTP id B322071804B; Fri, 2 Feb 2018 11:11:05 -0600 (CST) Subject: Re: Jails, ping, and now DNS To: Steve Pointer , freebsd-questions@freebsd.org References: <737005a0c3e97d8d1e9306eb52471f89.squirrel@webmail.harte-lyne.ca> <5A74875F.9080901@gmail.com> <1517588082.2117241.1257377040.499E7DC3@webmail.messagingengine.com> From: Valeri Galtsev Message-ID: <47ca7d96-dd74-f041-f3fd-daed4c696dae@kicp.uchicago.edu> Date: Fri, 2 Feb 2018 11:11:05 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <1517588082.2117241.1257377040.499E7DC3@webmail.messagingengine.com> 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 17:11:09 -0000 On 02/02/18 10:14, Steve Pointer wrote: > > >> >> Your problem is your using ezjail which uses the deprecated rc.conf >> environment-variable method. Most jail users have stopped using ezjail >> so support for problems like you are having is very limited. >> >> Every time you start a ezjail jail an error message popes out telling >> you to convert your jail system to the jail.conf method. That error >> message has been issued since 9.1. Its about time you do as it says >> before you get caught with a unsupported production jail environment. >> There is a good chance the deprecated rc.conf environment-variable >> method will be removed in 12.0 release. >> >> If you are addicted to the ezjail jail coding method then check out >> qjail which is a fork of ezjail that uses the jail.conf method. >> > > The FreeBSD handbook refers to ezjail: > > https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails.html > > If this is no longer the best method then maybe this should be changed. I don't think HandBook suggests ezjail is "the best method"? And it is not my book. It can be recommended if keeps up with doing configuration the modern way, and it should be discouraged if it stays with deprecated way. But in my book doing jails "by the book", that is: creation jail environment without using any scripts put out by someone. That was the first thing about how to set up jails I learned from FreeBSD Handbook. The second thing I learned was one can use something like ezjail... but as usually we realize that will deprive your flexibility. I don't think HandBook ever insisted on ezjail to be a "preferred method". Am I missing something? Valeri > If a bug report was posted with edits to the recommended method what do most people use? > > qjail ? Personally I have had success with iocage , which I understood all the cool kids were using now. > > https://github.com/iocage/iocage > > Am I in the minority in using this method? > > Steve > _______________________________________________ > 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 Fri Feb 2 17:30:25 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8BCF4EE560F for ; Fri, 2 Feb 2018 17:30:25 +0000 (UTC) (envelope-from frankfenderbender@council124.org) Received: from vps349.pairvps.com (vps349.pairvps.com [216.92.231.69]) (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 3C84475F7E for ; Fri, 2 Feb 2018 17:30:24 +0000 (UTC) (envelope-from frankfenderbender@council124.org) Received: from [192.168.0.100] (unknown [104.220.39.23]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by vps349.pairvps.com (Postfix) with ESMTPSA id CD3C1A5F9A; Fri, 2 Feb 2018 12:30:23 -0500 (EST) Subject: soundbar loading-output question Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: C Gray In-Reply-To: Date: Fri, 2 Feb 2018 09:30:22 -0800 Reply-To: C Gray Content-Transfer-Encoding: quoted-printable Message-Id: <826E6CDC-4B36-46C5-BB2E-9BB620EFCD48@council124.org> References: <8F08E935-33A8-4B5F-9057-51FAD51DA97D@council124.org> <20180201121251.95e345cf.freebsd@edvax.de> <09DEB81A-3DC1-4147-9249-0497C89F429B@council124.org> <69060D2E-8ED1-4BDB-8801-2BA29F15C632@council124.org> To: freebsd-questions@freebsd.org X-Mailer: Apple Mail (2.1085) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 17:30:25 -0000 First, thanks esp. to Scott Bennett, Robroy Gregg, and Polytropon. Indispensable friendliness in sharing their experiences, tips, and = tricks, and suggestions. Forgive me if I ask a bit more of you (and others) as this great = opportunity of tapping your interest and aid just a bit more... These "mix" success stories are useful news!=20 It is also great to hear of 'external' sound system experience. In such a climate, I offer up a strange appearance, through = re-connection luck, of my soundbar suddenly being recognized, although = to what degree I am uncertain. I hate to wait until runtime issues ask for camouflaged resolutions, so = this before-the-problem research will surely help, and if it is not an = imposition. Initially, I discovered the lack of a sound system in my server (vs. = serving out or streaming sound files to a client's sound system) because = a FreeBSD base or port installer option I may have clicked in one of = many DOS-like install checklists, kept giving me bootloader error:s = w/r/t "mixer" and a "missing", unusable, and/or undiscovered sound = device. Did I mention mistakenly appearing to be properly-attached? ;-) Yesterday, I swapped desktop locations of my FreeBSD monitor and my = Macmini5,1 running MacOSX10.7 Lion -- the last [cr]Apple OS to = supply/support X11, a 'security bust'-must required by their cohorts in = the PRISM-NSA association, much as they've now removed NFS, BSD, and = security-rich modules/modalities which guard against intrusion except by = them and their BFFs). After the swap I've noticed lines that may or may = not have been there before w/r/t its "Dell Stereo USB Monitor Soundbar = AC511" attached like a lamprey to the the 'landscape' bottom-side of its = 90-degree-flippable, very code-reading "friendly", Dell 22 Monitor = (model) P2217H. The FreeBSD system wants to use it, or is, but may be = having issues, as a loose "eye" with pre-logged screen-scrolls was = missed or altered by a re-seated connection. Either way: ugen4.2: at usbus4 (disconnected) uhub5: at uhub2, port 6, addr 2 (disconnected) ugen4.3: at usbus4 (disconnected) uaudio0: at uhub5, port 3, addr 3 (disconnected) pcm0: detached uaudio0: detached uhub5: detached ugen4.2: at usbus4 uhub5 on uhub2 uhub5: on usbus4 uhub5: MTT enabled uhub5: 4 ports with 4 removable, self powered random: harvesting attach, 8 bytes (4 bits) from uhub5 ugen4.3: at usbus4 uaudio0 on uhub5 uaudio0: on usbus4 uaudio0: Play: 48000Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms = buffer. uaudio0: Play: 44100Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms = buffer. uaudio0: Record: 48000Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms = buffer. uaudio0: Record: 44100Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms = buffer. uaudio0: No MIDI sequencer.=20 pcm0: on uaudio0 pcm0: Mixer "vol" -> "none": child=3D0x00000010 pcm0: Mixer "pcm": parent=3D"vol" pcm0: Mixer "line": random: harvesting attach, 8 bytes (4 bits) from pcm0 uaudio0: HID volume keys found. random: harvesting attach, 8 bytes (4 bits) from uaudio0 This readout came after I was already logged in as root, some time = during the night when I and the screen were asleep. Very odd, however, it has now discovered the soundbar, albeit to what = extent I am quite unclear. ;-) Whenever these brain-scratchers appear, I find it is best to go at it = with documentation, advice, and a relaxed time-full approach, esp. since = I cannot turn on a debugger-tracer or have a file and setting BOM for = each port or even for the base. At Analogy (a less-than-250 person EDA company bought up by Synopsis) we = used to ship a release BOM that said exactly what a clean install would = change (and how) in terms of settings or dynamic files, where it would = add folders and files, and what those file sizes and types would be. We = also gave a checker that would verify the install process so handheld = tweaks could be made and installer issues reported. We did similar = things at Network General and Tektronix with robust documentation and = ways to change a generic install into the specific one your particular = platform would need in order to run (usually most heavily changed in the = I/O). So, I wonder what the process has been in terms of tools for that = or attempts at that w/r/t FreeBSD. Often, "open" team software hits the = wall w/r/t standards, documentation updating, process = verification/improvement.... I imagine it spreads out into millions of = hours of extra work by installers, much like the extra work required by = so many to write the same work-arounds for bad Microsoft IE code which = failed to follow standards like the rest of the browser community. Oh = well, you work with what you have until you and others are determined to = leap past a recurring issue with contributing yourselves. Maybe that = will be on my 2019 list after I finish my GNU self-directed health = analysis and simulation software. So, for now, does the above output = indicate a standardized way of saying "this is all okay and will work" = or is it like the famous "maybe gate" in board logic circuits? ;-) Oh, if anyone can suggest a few books w/r/t to actual FreeBSD output by = the base and port and upgrade processes, so I can decipher what "notes = to the logger" which will "speak to me" as well, I am all eyes and ears, = and hopefully, a learning brain.... best wishes, chris (aka "frank" as in Zappa and "fenderbender" as in parking lots and = guitars) frankfenderbender@council124.org= From owner-freebsd-questions@freebsd.org Fri Feb 2 18:04:41 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1BE7EEE70D6 for ; Fri, 2 Feb 2018 18:04:41 +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 A41B277D94 for ; Fri, 2 Feb 2018 18:04:40 +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 w12I4dd2061952 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 2 Feb 2018 11:04:39 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id w12I4dWa061948; Fri, 2 Feb 2018 11:04:39 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Fri, 2 Feb 2018 11:04:39 -0700 (MST) From: Warren Block To: Steve Pointer cc: freebsd-questions@freebsd.org Subject: Re: Jails, ping, and now DNS In-Reply-To: <1517588082.2117241.1257377040.499E7DC3@webmail.messagingengine.com> Message-ID: References: <737005a0c3e97d8d1e9306eb52471f89.squirrel@webmail.harte-lyne.ca> <5A74875F.9080901@gmail.com> <1517588082.2117241.1257377040.499E7DC3@webmail.messagingengine.com> 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, 02 Feb 2018 11:04:39 -0700 (MST) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 18:04:41 -0000 On Fri, 2 Feb 2018, Steve Pointer wrote: >> Your problem is your using ezjail which uses the deprecated rc.conf >> environment-variable method. Most jail users have stopped using ezjail >> so support for problems like you are having is very limited. >> >> Every time you start a ezjail jail an error message popes out telling >> you to convert your jail system to the jail.conf method. That error >> message has been issued since 9.1. Its about time you do as it says >> before you get caught with a unsupported production jail environment. >> There is a good chance the deprecated rc.conf environment-variable >> method will be removed in 12.0 release. >> >> If you are addicted to the ezjail jail coding method then check out >> qjail which is a fork of ezjail that uses the jail.conf method. >> > > The FreeBSD handbook refers to ezjail: > > https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails.html > > If this is no longer the best method then maybe this should be changed. If a bug report was posted with edits to the recommended method what do most people use? There are numerous jail management methods. ezjail was and still is popular. The warning message has annoyed enough people that there is actually a sysctl to disable it now. > qjail ? Personally I have had success with iocage , which I understood all the cool kids were using now. qjail is a forked version of ezjail. It is strongly recommended by the person who forked it. There is a long story here, and a search of the mail archives will result in some interesting reading. > https://github.com/iocage/iocage > > Am I in the minority in using this method? iocage is a valid choice, and probably the most popular new jail management method. Of course, there are two versions of iocage, one in shell and one in Python. From owner-freebsd-questions@freebsd.org Fri Feb 2 18:08:01 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4E844EE740C for ; Fri, 2 Feb 2018 18:08:01 +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 D1BA978220 for ; Fri, 2 Feb 2018 18:08:00 +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 w12I7xKf063289 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 2 Feb 2018 11:07:59 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id w12I7xRj063286; Fri, 2 Feb 2018 11:07:59 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Fri, 2 Feb 2018 11:07:59 -0700 (MST) From: Warren Block To: Valeri Galtsev cc: Steve Pointer , freebsd-questions@freebsd.org Subject: Re: Jails, ping, and now DNS In-Reply-To: <47ca7d96-dd74-f041-f3fd-daed4c696dae@kicp.uchicago.edu> Message-ID: References: <737005a0c3e97d8d1e9306eb52471f89.squirrel@webmail.harte-lyne.ca> <5A74875F.9080901@gmail.com> <1517588082.2117241.1257377040.499E7DC3@webmail.messagingengine.com> <47ca7d96-dd74-f041-f3fd-daed4c696dae@kicp.uchicago.edu> 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, 02 Feb 2018 11:07:59 -0700 (MST) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 18:08:01 -0000 On Fri, 2 Feb 2018, Valeri Galtsev wrote: > I don't think HandBook suggests ezjail is "the best method"? And it is not my > book. It can be recommended if keeps up with doing configuration the modern > way, and it should be discouraged if it stays with deprecated way. But in my > book doing jails "by the book", that is: creation jail environment without > using any scripts put out by someone. That was the first thing about how to > set up jails I learned from FreeBSD Handbook. The second thing I learned was > one can use something like ezjail... but as usually we realize that will > deprive your flexibility. I don't think HandBook ever insisted on ezjail to > be a "preferred method". > > Am I missing something? No, that's correct. We needed a section on jail management that was reasonably up to date and showed best practices, and there wasn't one. So I picked ezjail as the most popular jail management framework and wrote that section for the Handbook. Interestingly, a famous FreeBSD person said to me at BSDCan in the last couple of years that we ought to delete everything but the ezjail section from the Jails chapter, as most of it is so old. From owner-freebsd-questions@freebsd.org Fri Feb 2 19:18:06 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E8D7EEA643 for ; Fri, 2 Feb 2018 19:18:06 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E31A37B65E for ; Fri, 2 Feb 2018 19:18:04 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.213.55]) by mrelayeu.kundenserver.de (mreue004 [212.227.15.167]) with ESMTPA (Nemesis) id 0MIAwM-1ejL0O2mMA-003ukp; Fri, 02 Feb 2018 20:18:02 +0100 Date: Fri, 2 Feb 2018 20:18:02 +0100 From: Polytropon To: Peter Ulrich Kruppa Cc: freebsd-questions@freebsd.org Subject: Re: German keyboard support for gdm??? Message-Id: <20180202201802.4a9b70f5.freebsd@edvax.de> In-Reply-To: References: <20180202141115.aa7bbf16.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-Provags-ID: V03:K0:1uxY9TP8hm8fiB6hKqXizE4OW9qCbHA4UDdh4jpkk3J5BF+Ky8p q16dwi9cl5YGxfZLNXM7oAM+XI+NAvEUGJ+n7bJ4jZ/uFj2s7oR4D2icMRg5Q/xOkynAl0O k2b8fPzUjZJrPOgupLpGP/D3hFlpcH5I6a/vM91NsBQCa01BBnpAWo9aEpVWFFfvHPZJtlA imBRIlWZblut75l/qDTeQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:zsnYxYJuYzs=:3ub+dULZbGhqVEIJ81YRII /vfQwG3cDW2kowIBUOFiMbhwI1KkkFEiE53e8FY1C05h77NwL/k3JPQEgOn/XTyNTOacZPo2H Lc+pLlRKdIpVakhbhZcNnVmFibta6U08x8rRjWqV4C4RW97ukSeTg8bEjARmmtbk3NXuSjzzy Toa+5Jfpi0vASr4lY+sNJXQEUdA0gaQzhB/poi5cdAL2WQXsg4x/MqpfY4QXTG2INZnEy9byH LrR4qB1EGz2uuPDL7wEaB2g6v1cHxxoiRWMuN/wwP2MwOmJokERhwzAGqRNh0wcpLlJzNkDKT D6/OwK8UfAaPlbwNmH+cbj+gk6s//VrkfjXYf2AFMUi7CtQCTptern9dktyNk6zGbCzStCoEE cwgfQUd98evm6llMLuQ9+9n9x/PJpHQ3DBV5i/EmTx0aSZZD4YBy3k3zpkCHB76TmloTCKio8 Bu5eGyKB1aQ/xxHuEfMp4gARjXHkj3V8lkB7VVs2J+H7JZrMkMWsQSG2rhuzXSDF9NKEe4sQB lTXaMzjO2tPSmFhK8lktUhg+cWJvR5rTiTMXEvAPtlB31UM19wbetxhrgHaPlxByjdWdfEJKZ nZt1iBMRl9XUwHC09lsbcxNsU/W8pBLYejdltNm7+sBtxXR+FLY26l9Th36cfEAKCASMhqsDu Ke6h1nHTloybOQcZ/vDl66tcLQPJfpx2iViQmputuoX9jXilkYV8NQXoUEPBrx7NWq20n3a7z LCBrKmVwjfLY9UbUmfsU8bpcFv0uXk+E6pZVyA7J7eegJxLsxMkSPK2QY5Y= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 19:18:06 -0000 On Fri, 2 Feb 2018 17:08:46 +0100, Peter Ulrich Kruppa wrote: > (I hope this webmailer doesn't produce any HTML mess - it's the first time > I try it on a mailing-list) Everything alright, no HTML garbage. :-) > On Fri, Feb 2, 2018 at 2:11 PM, Polytropon wrote: > > > On Fri, 2 Feb 2018 05:04:24 +0100, Peter Ulrich Kruppa wrote: > > > does anyone know how to make gnome's display manager gdm understand > > german > > > keyboard input? > > > > Historically, you put an entry in /etc/X11/xorg.conf, > > but today, this is not so easy anymore. There are at > > least two options: > > > > a) Use X11 cofiguration /usr/local/etc/X11/xorg.conf.d/keyboard-de.conf > > > > Section "InputClass" > > Identifier "KeyboardDefaults" > > Driver "keyboard" > > MatchIsKeyboard "on" > > Option "XkbLayout" "de" > > EndSection > > > That one I have found myself. It's nice to set german keyboard in twm or > xfce4 , but is ignored by gdm. This should be a X-wide setting, so the only reason for gdm to ignore it is that somewhere else (!) a gdm setting says "en" (and "don't use system's setting"). By the way, I've been using Gnome 2 and gdm in the past, with german keyboard support, but as Gnome 3 became unusable, I switched the particular systems to Mate and slim. Both seem to honor the X-wide setting (global) for keyboard. By the way, you could also try a partial xorg.conf with the content mentioned above, located in /usr/local/etc/X11. > > b) Use HAL configuration /usr/local/etc/hal/fdi/policy/x11-input.fdi: > > > > > > > > > > > > > type="string">pc102 > > > type="string">fr > > > > > > > > > This one I didn't know. I tried it and checked if hald is started. Result: > Nothing, not even a french keyboard :-) I'm almost sure Gnome still requires HAL and DBus in order to run; do you have hald_enable="YES" dbus_enable="YES" in your /etc/rc.conf? Maybe gnome_enable="YES" implies them. > And by the way: The space in (behind pc102) will produce some > error. Yes, that seems to be a reformatting issue (indentation with one tab, manually). And of course it should be "de" instead of "fr". :-) > > c) Use Gnome's configuration utility (the one which can also > > configure gdm). I've never used that, so I cannot be more > > specific, sorry. :-) > > > Which one might that be: I have got gnome-control-center, gnome-tweak-tool > and dconf-editor and can't see where anything about gdm could be done ... That is very strange. Still I seem to remember that there was a tool to configure gdm, but I cannot remember what it was... > But in the meantime I found this: > > https://help.gnome.org/admin/system-admin-guide/stable/keyboard-layout.html.en > To me it sounds as if I either need the program localectl , which is only > available on Linux or a /dev/input/event which can be produced by > installing libudev-devd and rebuilding xorg-server with DEVD option - see > the README at > > https://help.gnome.org/admin/system-admin-guide/stable/keyboard-layout.html.en > I will try that, but it will take some time on this old box. Both localectl and udev are Linuxisms. Maybe Gnome 3 isn't actually as cross-platform as it claims? ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Fri Feb 2 20:53:11 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AFCF0EC96E0 for ; Fri, 2 Feb 2018 20:53:11 +0000 (UTC) (envelope-from frankfenderbender@council124.org) Received: from vps349.pairvps.com (vps349.pairvps.com [216.92.231.69]) (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 61D907FDCD for ; Fri, 2 Feb 2018 20:53:10 +0000 (UTC) (envelope-from frankfenderbender@council124.org) Received: from [192.168.0.100] (unknown [104.220.39.23]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by vps349.pairvps.com (Postfix) with ESMTPSA id A11E1A68E8; Fri, 2 Feb 2018 15:53:08 -0500 (EST) Subject: Q about conf'd system's self-checking output Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: C Gray In-Reply-To: <826E6CDC-4B36-46C5-BB2E-9BB620EFCD48@council124.org> Date: Fri, 2 Feb 2018 12:53:07 -0800 Reply-To: C Gray Content-Transfer-Encoding: quoted-printable Message-Id: <0DD02E02-F53B-41BB-B237-7154847FC1B2@council124.org> References: <8F08E935-33A8-4B5F-9057-51FAD51DA97D@council124.org> <20180201121251.95e345cf.freebsd@edvax.de> <09DEB81A-3DC1-4147-9249-0497C89F429B@council124.org> <69060D2E-8ED1-4BDB-8801-2BA29F15C632@council124.org> <826E6CDC-4B36-46C5-BB2E-9BB620EFCD48@council124.org> To: freebsd-questions@freebsd.org X-Mailer: Apple Mail (2.1085) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 20:53:11 -0000 So I have the .conf[ig] files (e.g., = /usr/local/etc/security/pwquality.conf) set so that=20 my mail-less FreeBSD system will allow root to send my mail-gateway = Macmini=20 with reports. I had and fixed these warnings so the detailed reports are already very = useful (for=20 system operations' debugging) and will be even more so (for security) = over time: Warning: Variable $daily_status_security_chksetuid_enable is = deprecated,=20 use $security_status_chksetuid_enable instead. Warning: Variable $daily_status_security_neggrpperm_enable is = deprecated,=20 use $security_status_neggrpperm_enable instead. Warning: Variable $daily_status_security_chkmounts_enable is = deprecated,=20 use $security_status_chkmounts_enable instead. My changes w/r/t my soundbar issue seem to have partially self-resolved = (maybe=20 because a connection re-seated itself better) itself due to = self-diagnoses a, upgrades,=20 or rediscovery attempts therewith... a welcome surprise but one I wish I = better=20 understood and quasi-controlled. Here's "lanserve1 daily security run output" from 3:14am: -------------- Checking login.conf permissions: lanserve1 kernel log messages: +Calibrating TSC clock ... TSC clock: 2500051110 Hz +LAPIC: ipi_wait() us multiplier 60 (r 4100692 tsc 2500051110) +Timecounter "TSC-low" frequency 1250025555 Hz quality 1000 +usbus0: random: harvesting attach, 8 bytes (4 bits) from uhci0 +12Mbps Full Speed USB v1.0 +acpi0: wakeup code va 0xfffffe008b02c000 pa 0x99000 +atkbd: the current kbd controller command byte 0045 +ugen4.1: at usbus4 +uhub0: on = usbus3 +uhub1: on = usbus1 +uhub2: on = usbus4 +ugen2.1: at usbus2 +ugen0.1: at usbus0 +uhub4: on = usbus0 +uhub3: on = usbus2 +uhub0: 2 ports with 2 removable, self powered +random: harvesting attach, 8 bytes (4 bits) from uhub0 +uhub3: 2 ports with 2 removable, self powered +random: harvesting attach, 8 bytes (4 bits) from uhub3 +uhub2: 8 ports with 8 removable, self powered +random: harvesting attach, 8 bytes (4 bits) from uhub2 +ugen4.2: at usbus4 +uhub5 on uhub2 +uhub5: on = usbus4 +uhub5: MTT enabled +uhub5: 4 ports with 4 removable, self powered +ugen4.3: at usbus4 +ugen4.4: at usbus4 +uhub6 on uhub2 +uhub6: on usbus4 +uhub6: 2 ports with 2 removable, self powered +random: harvesting attach, 8 bytes (4 bits) from uhub6 +Trying to mount root from = zfs:tank1/ROOT/12.0-CURRENT-up-20180124_175726 []... +ugen1.2: at usbus1 +ukbd0 on uhub1 +ukbd0: on usbus1 +kbd2 at ukbd0 +kbd2: ukbd0, generic (0), config:0x0, flags:0x3d0000 +random: harvesting attach, 8 bytes (4 bits) from ukbd0 +ums0 on uhub3 +uaudio0 on uhub5 +uaudio0: on usbus4 +uaudio0: Play: 48000 Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms buffer. +uaudio0: Play: 44100 Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms buffer. +uaudio0: Record: 48000 Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms buffer. +uaudio0: Record: 44100 Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms buffer. +uaudio0: No MIDI sequencer. +pcm0: on uaudio0 +pcm0: Mixer "vol" -> "none": child=3D0x00000010 +pcm0: Mixer "pcm": parent=3D"vol" +pcm0: Mixer "line": +random: harvesting attach, 8 bytes (4 bits) from pcm0 +uaudio0: HID volume keys found. +random: harvesting attach, 8 bytes (4 bits) from uaudio0 +ugen4.2: at usbus4 (disconnected) +uhub5: at uhub2, port 6, addr 2 (disconnected) +ugen4.3: at usbus4 (disconnected) +uaudio0: at uhub5, port 3, addr 3 (disconnected) +pcm0: detached +uaudio0: detached +uhub5: detached -------------- Here's the stdout which the process(es) sent to my screen early this = morning=20 appending directly just after my root csh-login-prompt. I imagine that = the=20 stderr and stdout are synchronized time-wise in the above rendition, = however,=20 I have included the screen output [again] in case it may offer a clue or = two.... > [root@lanserve1] ~# ugen4.2: at usbus4 = (disconnected) > uhub5: at uhub2, port 6, addr 2 (disconnected) > ugen4.3: at usbus4 (disconnected) > uaudio0: at uhub5, port 3, addr 3 (disconnected) > pcm0: detached > uaudio0: detached > uhub5: detached > ugen4.2: at usbus4 > uhub5 on uhub2 > uhub5: on usbus4 > uhub5: MTT enabled > uhub5: 4 ports with 4 removable, self powered > random: harvesting attach, 8 bytes (4 bits) from uhub5 > ugen4.3: at usbus4 > uaudio0 on uhub5 > uaudio0: on usbus4 > uaudio0: Play: 48000Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms = buffer. > uaudio0: Play: 44100Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms = buffer. > uaudio0: Record: 48000Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms = buffer. > uaudio0: Record: 44100Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms = buffer. > uaudio0: No MIDI sequencer.=20 > pcm0: on uaudio0 > pcm0: Mixer "vol" -> "none": child=3D0x00000010 > pcm0: Mixer "pcm": parent=3D"vol" > pcm0: Mixer "line": > random: harvesting attach, 8 bytes (4 bits) from pcm0 > uaudio0: HID volume keys found. > random: harvesting attach, 8 bytes (4 bits) from uaudio0 What I am interested in: (1) what actual call launched at 3-ish am? (2) what and where were conditionals met-or-not-met which = 'decided' to vector off to (a) attempt to resolve? (b) attempt to discover new devices? (c) attempt to resolve newly-discovered = device-configuration issues? (d) attempt to resolve previously-discovered but = unresolved device-configuration issues? I'm also getting an old issue again when I tried to vi/vim (view works) = on /usr/local/etc/security/pwquality.conf: Shared object "libSM.so.6" not found, required by "vim". After my base install and attempts to 'make' ports, I ran into a missing = link from /usr/local/lib/ to /lib/ Now I have this 'base'-ic issue.=20 I've found that certain base-ic install tools have dependencies which = when take ]n care of also have missing dependencies. Is there a tool that will walk through all executables to list all = runtime issues at once rather than over a piecemeal call-and-see = scenario? Whene I run whereis, locate, which, and find nothing, I'm stumped as to = how I am supposed to fix the problem I expected to be configured at = install time. That I may have to start the install all over is a problem as well = because re-doing every .conf file setenv, alias, and such -- or backing = that all up -- is near monumental, so if there is a logical tree-top = walkthrough of logs, in the topmost sequence, so that a fix trickles = down and fixes sub-issues, then I can learn quite a bit just fixing the = system rather than hoping it doesn't just reproduce itself. Make sense. = So, a guide to system->module->function calls may be useful if anyone = can recommend an approach.1 My stdout listed above suggests questions based only on my asynchronous = observations at this point, and I need to better understand the calls = that generate the basic setup taking place w/r/t terms, phrases, and = processes like: "harvesting attach"? "detached"? the boot-time and login-time setting of buffer sizes and = locations? the boot-time and login-time mounting of and/or linking to = devices or volumes? if certain things are set at boot time, login time, or at the = time of need by a port or base module? Is there a 'most pertinent' section (in your manuals' travels you'd = recommend? Have you seen that one graphical depiction (as is often well done when = describing the disk-track-sector relationship) which "hit the mark" for = you w/r/t any of my questions? I will read all suggestions and = appreciate you taking the time, making the effort. I apologize for this flurry, and I will definitely share back whatever I = can when an "aha!" opportunity arises.=20 Thanks. best wishes, chris 'smart' devices are con[niving]s and 'dumb' users are man-made From owner-freebsd-questions@freebsd.org Sat Feb 3 04:11:36 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA1FDEE50A7 for ; Sat, 3 Feb 2018 04:11:35 +0000 (UTC) (envelope-from ralf.mardorf@rocketmail.com) Received: from sonic308-20.consmr.mail.ir2.yahoo.com (sonic308-20.consmr.mail.ir2.yahoo.com [77.238.178.148]) (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 71C5E713B1 for ; Sat, 3 Feb 2018 04:11:35 +0000 (UTC) (envelope-from ralf.mardorf@rocketmail.com) X-YMail-OSG: C.TkEYIVM1lM5SCi7uA8R349EgH6I3A7g00elp1nlt9Kdt4xun8HSkL5xc1pwPB lQS0jRRv9mpVysLbHY_zDfogBQwmHojJjSV735r48kRRB2EPOYrwPydG6m.hhZ0xEen496WO__EU VbL.wLurTxp6vghel.Sw1hzz8vjUSDdFGlE9ZVVY_TqYrSxI_xR4iHzxJvfbKbb.hVEJTbB3dEWL .Ep49fDFe.PEfd_z168JzV1Aeb6shZZEWz.vj5d70U921zlw0AuG0iIwJgjHyt9VrfsFWuUdo9rx dKeQQZEgglPAedv2g.fTZBan_DAzx54M2JQViND8aR_XHy0LW.U7w6hFfm7qH8.ZarNHJ2.rmRPA R2umPO4Xh9f54Z.you.zA.3OfYmo8KGrfe24x3ju3swDpjJOP2_VZ4jdAvQc1C4gQAkrUKg2G8dq maTIICP3avAZrlxO77.CZCXEIzVWuV3jj9DvPuWqD0LgSDcI.1hQMAvPuq2VJ14gxqzzwAT24ndK HtGt8euzAAUOzoYhfpvWfvtOMpCAmYZRBtq1F5otVH1c8S3NJqiA- Received: from sonic.gate.mail.ne1.yahoo.com by sonic308.consmr.mail.ir2.yahoo.com with HTTP; Sat, 3 Feb 2018 04:11:28 +0000 Received: from smtp155.mail.ir2.yahoo.com (EHLO archlinux.localdomain) ([46.228.39.118]) by smtp404.mail.ir2.yahoo.com (JAMES SMTP Server ) with ESMTPA ID d1b62157e91a51175609b79cf6e604f9 for ; Sat, 03 Feb 2018 04:01:16 +0000 (UTC) Date: Sat, 3 Feb 2018 05:01:15 +0100 From: Ralf Mardorf To: freebsd-questions@freebsd.org Subject: Re: German keyboard support for gdm??? Message-ID: <20180203050115.102d6f98@archlinux.localdomain> In-Reply-To: References: <20180202141115.aa7bbf16.freebsd@edvax.de> X-Mailer: Claws Mail 3.16.0git24 (GTK+ 2.24.32; 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 04:11:36 -0000 On Fri, 2 Feb 2018 17:08:46 +0100, Peter Ulrich Kruppa wrote: >> c) Use Gnome's configuration utility (the one which can also >> configure gdm). I've never used that, so I cannot be more >> specific, sorry. :-) >> >Which one might that be: I have got gnome-control-center, >gnome-tweak-tool and dconf-editor and can't see where anything about >gdm could be done ... Hi, from command line use the gsettings command or the dconf command. In your case gesetttings is the way to go. If something like $ cat /etc/X11/xorg.conf.d/keyboard.conf Section "InputClass" Identifier "keyboard" MatchIsKeyboard "yes" Option "XkbLayout" "de" #Option "XkbVariant" "nodeadkeys" EndSection doesn't work, then GDM's or it's greeter's config overrides the X settings. Keep in mind that GNOME upstream supports/expects Wayland as GNOME default. This already breaks Linux installs and much more likely will breake FreeBSD installs. Perhaps https://wiki.archlinux.org/index.php/GDM#Keyboard_layout does help, but I would stay away from a GUI to change the appropriate setting/s. I once provided a short example how to use gsettings for the dconf crap, see https://mail.gnome.org/archives/evolution-list/2017-October/msg00110.html , just use GDM insteadof evolution related keywords for the grep pipe. Regards, Ralf From owner-freebsd-questions@freebsd.org Sat Feb 3 09:10:07 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4DD6EECFF56 for ; Sat, 3 Feb 2018 09:10:07 +0000 (UTC) (envelope-from ralf.mardorf@alice-dsl.net) Received: from mail70c50.megamailservers.eu (mail80c50.megamailservers.eu [91.136.10.90]) (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 B1B2C7D31F for ; Sat, 3 Feb 2018 09:10:05 +0000 (UTC) (envelope-from ralf.mardorf@alice-dsl.net) X-Authenticated-User: ralf.mardorf.alice-dsl.net Received: from archlinux.localdomain (x4e3215c6.dyn.telefonica.de [78.50.21.198]) (authenticated bits=0) by mail70c50.megamailservers.eu (8.14.9/8.13.1) with ESMTP id w138WCMo014073 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 3 Feb 2018 08:32:13 +0000 Message-ID: <1517646733.4926.6.camel@alice-dsl.net> Subject: Re: German keyboard support for gdm??? From: Ralf Mardorf To: freebsd-questions@freebsd.org Date: Sat, 03 Feb 2018 09:32:13 +0100 In-Reply-To: <1517646306.4926.3.camel@alice-dsl.net> References: <20180202141115.aa7bbf16.freebsd@edvax.de> <20180203050115.102d6f98@archlinux.localdomain> <1517646306.4926.3.camel@alice-dsl.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.4 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-CTCH-RefID: str=0001.0A0B0202.5A75738E.0020, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-CTCH-Score: 0.000 X-CTCH-Rules: X-CTCH-Flags: 0 X-CTCH-ScoreCust: 0.000 X-CSC: 0 X-CHA: v=2.2 cv=bNdmGL2Z c=1 sm=1 tr=0 a=PZfyA6fGuTNt5onReiFkmA==:117 a=PZfyA6fGuTNt5onReiFkmA==:17 a=IkcTkHD0fZMA:10 a=Br9LfDWDAAAA:8 a=aiIX5UjjAAAA:8 a=DsgmV-yhImkGFg7uuG0A:9 a=QEXdDO2ut3YA:10 a=zzKm1fRokcUA:10 a=_tHamj0Rg94A:10 a=gR_RJRYUad_6_ruzA8cR:22 a=K4UmP72BP_XnEf30ZnvK:22 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 09:10:07 -0000 On Sat, 2018-02-03 at 09:25 +0100, Ralf Mardorf wrote: > On Sat, 2018-02-03 at 05:01 +0100, Ralf Mardorf wrote: > > Perhaps https://wiki.archlinux.org/index.php/GDM#Keyboard_layout does > > help, but I would stay away from a GUI to change the appropriate > > setting/s. > > > > I once provided a short example how to use gsettings for the dconf crap, > > see > > https://mail.gnome.org/archives/evolution-list/2017-October/msg00110.html , > > just use GDM insteadof evolution related keywords for the grep pipe. > > Perhaps it isn't a dconf setting, but the config might be located in > /etc/gdm3/ , IOW take a look using an editor and/or consider to send a > request to a GNOME mailing list. The dconf settings are much likely user related settings only, while GDM settings should be independent of a user's settings, so dconf unlikely is the correct config, more likely it is located in /etc/gdm/ or similar. From owner-freebsd-questions@freebsd.org Sat Feb 3 09:40:04 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D84F5ED25E0 for ; Sat, 3 Feb 2018 09:40:04 +0000 (UTC) (envelope-from ralf.mardorf@alice-dsl.net) Received: from mail37c50.megamailservers.eu (mail233c50.megamailservers.eu [91.136.10.243]) (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 720DB7E48F for ; Sat, 3 Feb 2018 09:40:03 +0000 (UTC) (envelope-from ralf.mardorf@alice-dsl.net) X-Authenticated-User: ralf.mardorf.alice-dsl.net Received: from archlinux.localdomain (x4e3215c6.dyn.telefonica.de [78.50.21.198]) (authenticated bits=0) by mail37c50.megamailservers.eu (8.14.9/8.13.1) with ESMTP id w138P5s4004328 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 3 Feb 2018 08:25:06 +0000 Message-ID: <1517646306.4926.3.camel@alice-dsl.net> Subject: Re: German keyboard support for gdm??? From: Ralf Mardorf To: freebsd-questions@freebsd.org Date: Sat, 03 Feb 2018 09:25:06 +0100 In-Reply-To: <20180203050115.102d6f98@archlinux.localdomain> References: <20180202141115.aa7bbf16.freebsd@edvax.de> <20180203050115.102d6f98@archlinux.localdomain> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.4 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-CTCH-RefID: str=0001.0A0B0207.5A7571E2.0114, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-CTCH-Score: 0.000 X-CTCH-Rules: X-CTCH-Flags: 0 X-CTCH-ScoreCust: 0.000 X-CSC: 0 X-CHA: v=2.2 cv=esev9shX c=1 sm=1 tr=0 a=PZfyA6fGuTNt5onReiFkmA==:117 a=PZfyA6fGuTNt5onReiFkmA==:17 a=IkcTkHD0fZMA:10 a=Br9LfDWDAAAA:8 a=aiIX5UjjAAAA:8 a=zJ5NQEhj3fj5EePEyaEA:9 a=QEXdDO2ut3YA:10 a=zzKm1fRokcUA:10 a=_tHamj0Rg94A:10 a=gR_RJRYUad_6_ruzA8cR:22 a=K4UmP72BP_XnEf30ZnvK:22 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 09:40:05 -0000 On Sat, 2018-02-03 at 05:01 +0100, Ralf Mardorf wrote: > Perhaps https://wiki.archlinux.org/index.php/GDM#Keyboard_layout does > help, but I would stay away from a GUI to change the appropriate > setting/s. > > I once provided a short example how to use gsettings for the dconf crap, > see > https://mail.gnome.org/archives/evolution-list/2017-October/msg00110.html , > just use GDM insteadof evolution related keywords for the grep pipe. Perhaps it isn't a dconf setting, but the config might be located in /etc/gdm3/ , IOW take a look using an editor and/or consider to send a request to a GNOME mailing list. From owner-freebsd-questions@freebsd.org Sat Feb 3 12:49:28 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 08588EE55CC for ; Sat, 3 Feb 2018 12:49:28 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 56B3F86FEE for ; Sat, 3 Feb 2018 12:49:26 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.213.55]) by mrelayeu.kundenserver.de (mreue103 [212.227.15.183]) with ESMTPA (Nemesis) id 0M2XRt-1ey6QV27a1-00sJDg; Sat, 03 Feb 2018 13:36:22 +0100 Date: Sat, 3 Feb 2018 13:36:22 +0100 From: Polytropon To: Ralf Mardorf Cc: freebsd-questions@freebsd.org Subject: Re: German keyboard support for gdm??? Message-Id: <20180203133622.1b4048de.freebsd@edvax.de> In-Reply-To: <1517646733.4926.6.camel@alice-dsl.net> References: <20180202141115.aa7bbf16.freebsd@edvax.de> <20180203050115.102d6f98@archlinux.localdomain> <1517646306.4926.3.camel@alice-dsl.net> <1517646733.4926.6.camel@alice-dsl.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-Provags-ID: V03:K0:lcIkntO3Sip4532ZbaNSI5ZMSXZDDeMYJqDuCX+5FyNELC+7jPM jFAE61nHg8D+Frh6TD4QuoGWcer2jBxNvgNv6MVMtjyLmchS7H+vBAseW1y4kuJYAhwN9b1 QOKOn61Wx5EhEuDmPmQ3dSvcps9mvJ4xhCCA7Q3FJXi1XjgmUqBOxrpMikfb95fa8WyH6pQ i222WI0R/9thp5Rbwd1Jg== X-UI-Out-Filterresults: notjunk:1;V01:K0:D73bqyjuZqc=:YH9RW/VcCFy7Ef7Lct+SRB FgG2BqivCRkvAMqyhhO4gKoFqnst+rpl6f+wxNjzkY9SpUwa2hPfOeilbZOqtGdSjfcZNyz9r jKmK1rFM4jsNP1nYTgl7wvzK7QrRsiMKk2Rkj4zbwAGmuJlhOa5b1tuGeHWUGR9NBon07I1Qs BZ3nkun+uNQfatfEI6cHE94ExqrXmAhoVi3KQuFrmmVmtqUOL34TxqYDbQf/V2ueNzNCI8TFn ariuUlfuobMAaOVsvBEv9z7O27MdPdPDlL2e6pk01kVJVMsD9/EwAFgdkr5phOXMgGnIKvhLs Xcphc0PxB5lQwLpunjTQXCP+4m7CJh3toaK0MDbIRHXcYABjDYMfx0oAunggfI91CLQpbMQzs BuuhdI3Ajl2SLyUp9wRk8AaE8DK8nSeRtHDOVK/LxlzCMDFc2FlABZ2UoQE+E4UOvUA2qRnbU /D/E64xA3FqGg1J2bmYpHqfpkwzJLUdf8IAS+rWuxo7/SEAngoA7YOHM4HFNf2np299MJFYdp KCzyROtOYwpMQm37Jcjb/vDIL/VqPrw0OY91j3wSk2Y1/8+vg11scXYYA3lHqzBb3nmq8rigL VsS/SKbpWMsmxn3CJYrOPo9pjvevLzpfNLcSTj3B3RqwKbVi3+4EUFUc194xtyzR5mENAyY/s uCrDVRx5lmv6zq4Q1GzZ7g3VVXTOh9JkhheNfQmcfwZdtYYTAMVy8cEgIImargA2n1b9bFd6T uA4nGjzFrbnJstAomocwqkyo4R0aV6+KYtqiS/GciZtoEmJzewa9OQi0INw= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 12:49:28 -0000 On Sat, 03 Feb 2018 09:32:13 +0100, Ralf Mardorf wrote: > On Sat, 2018-02-03 at 09:25 +0100, Ralf Mardorf wrote: > > On Sat, 2018-02-03 at 05:01 +0100, Ralf Mardorf wrote: > > > Perhaps https://wiki.archlinux.org/index.php/GDM#Keyboard_layout does > > > help, but I would stay away from a GUI to change the appropriate > > > setting/s. > > > > > > I once provided a short example how to use gsettings for the dconf crap, > > > see > > > https://mail.gnome.org/archives/evolution-list/2017-October/msg00110.html , > > > just use GDM insteadof evolution related keywords for the grep pipe. > > > > Perhaps it isn't a dconf setting, but the config might be located in > > /etc/gdm3/ , IOW take a look using an editor and/or consider to send a > > request to a GNOME mailing list. > > The dconf settings are much likely user related settings only, while GDM > settings should be independent of a user's settings, so dconf unlikely > is the correct config, more likely it is located in /etc/gdm/ or > similar. On FreeBSD, that would probably be /usr/local/etc/gdm or maybe /usr/local/etc/gdm3 worth checking. Overriding an X (global!) setting is still a bad idea for "the right behaviour" for GDM, in my opinion... but well, that's Linux... ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Sat Feb 3 15:03:29 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 24F61ECDA44 for ; Sat, 3 Feb 2018 15:03:29 +0000 (UTC) (envelope-from opsyspref@gmail.com) Received: from mail-ot0-x233.google.com (mail-ot0-x233.google.com [IPv6:2607:f8b0:4003:c0f::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 A064C6CFCE for ; Sat, 3 Feb 2018 15:03:28 +0000 (UTC) (envelope-from opsyspref@gmail.com) Received: by mail-ot0-x233.google.com with SMTP id x4so23088437otg.7 for ; Sat, 03 Feb 2018 07:03:28 -0800 (PST) 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; bh=jq3oHcXIYAifQiWiXKSBPYZo1bvodNEDSDAgPabBddU=; b=ZsxyFVBIQFTZWTUtJjqWDi7WFlHpWo49wZx5tbPvhMPQ+yN3Y/DlpPeypzNUegDQW7 60P/N/LheGd4pCL4HzTFGkaGQB/3EgSp0i10PZH0a/kChsnMJsVFQlRmWAfFlWfVniFk BHjRw53pKbVJ7Z1i4LnUtgFORKqIAFCRIps5YPX/39fAbJN0+CAI6p0LS5qDjyhsNyGC jfB+z2uhm894j04ikpjakseH1rD3dqYtq8mBA9MWpMkHeFQHaaPQ3cabV6QRKvBX4uNc GJhbb2bAkjP9nJZqNGJ5CsNf5/0izbTs2iTpUiyWKjEVwgOf2H6aZHEq6XrgDlwAjSFq u4IA== 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; bh=jq3oHcXIYAifQiWiXKSBPYZo1bvodNEDSDAgPabBddU=; b=YCchySO/f30cbxAdpXv0fecVHz3t71vSSqS8EVR7P7Ii2nJ0uowX/GaZ6MEyi849QE q/gsQS38Xfpv9e8Mr3uo42aUDVQf60FZfgO0gXhXuGPvH/6SR+LpfuzxvFjj6O1nhkcf FwD4+XiDdKEnd6/bUlRAQ3Fgbto6ajU45RGWR1tknGU/2VH+gw0jEqTc73u3URtw8Uw9 tLZlZSr412/dm7w/0UaqLA31C/whGPsOLAVKO4WTxgpkDdkT3wvf2NzlAdUzw45uRsMP tY3x73I05nUuGvYkQXxvICWMAXZt0CuZ+ehAXf8CJjfsWBf5PpjDQp8oGgEFEkFkRwLL Y1QQ== X-Gm-Message-State: AKwxytfMaR9qjPrNB6Ve8089RYGVa+SRci9JI/nPjQ2Tw3DCpfy2wcyl igb59C6d9ogOTgsb4uEBcC5kCAcY76hGBqGYsfwCcw== X-Google-Smtp-Source: AH8x226YvFn+NHAG86oYRRBfbQ1rBKZFx+m8msPtZQgF8eWXct27bispLj6jLKA8yPcz0wEeliFC56pNo73qWQzfJdc= X-Received: by 10.157.40.13 with SMTP id m13mr17845184otb.55.1517670207807; Sat, 03 Feb 2018 07:03:27 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.11.203 with HTTP; Sat, 3 Feb 2018 07:03:27 -0800 (PST) In-Reply-To: References: From: Peter Ulrich Kruppa Date: Sat, 3 Feb 2018 16:03:27 +0100 Message-ID: Subject: Re: German keyboard support for gdm??? To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 15:03:29 -0000 Pooh, there really seem to be a lot of "confs" and "customs" for gdm and apparently everything has been changed and renamed between gnome-2 and gnome-3 . I guess I will have to check if there is still someone alive on freebsd-gnome ... Thanks Peter On Fri, Feb 2, 2018 at 5:04 AM, Peter Ulrich Kruppa wrote: > Hello, > > does anyone know how to make gnome's display manager gdm understand german > keyboard input? > I can find many discussions, hints and ideas in the web, but whatever I > try, gdm stubbornly insists on using en_US default keyboard. > > I am running gdm-3.16.4_3 from ports on FreeBSD 11.1-RELEASE amd64 . > My german keyboard is supported on console and "inside" Gnome 3 , but not > on gdm's username/password dialog. > > Thanks an greetings > > Peter > From owner-freebsd-questions@freebsd.org Sat Feb 3 15:39:10 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 911C8ED325B for ; Sat, 3 Feb 2018 15:39:10 +0000 (UTC) (envelope-from ralf.mardorf@rocketmail.com) Received: from sonic310-13.consmr.mail.ir2.yahoo.com (sonic310-13.consmr.mail.ir2.yahoo.com [77.238.177.34]) (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 1C62F6E681 for ; Sat, 3 Feb 2018 15:39:09 +0000 (UTC) (envelope-from ralf.mardorf@rocketmail.com) X-YMail-OSG: YFXaqSoVM1mYuk0RFmthSnapyiyUG8tGF.mTdeni8vmZpytYJtGH5UpVqFB4Slf VnoU3CRvtc3v6eyoZo1SFb6PvfYYQC2xNAn_ubSOTsPTEqOJaz6HTvJZRaGRicUFhJD7SqnefawG b1t7wjXjBScf2EH6aEo9clyHy_h4knT15LHnuX2c4V3bsMDXLuKqO4PaXQ7YmGTsBdPodbBhEIg8 5WEhBFUf2q7MMkY0WJ7pqliQzOULZ1M.JgMOU2ukqwjFkzxtX9rsXbIY3fyZr_So_yn0K78_WNU0 U_juztVQ5nhvPOocnlVdH0_5kz0xCcq93mRzY0tVsDFFTiPJfm2pEvYqZTXajSAWm2VLxlP3N3O9 XaHGFaOTLoStCBUHx1BKuTnvhb3fwu9KT_f1QnRNcG70sVUweliBdx6Lck9hBpS99bMPiV1k0rW0 mp9L3zZJpqo_puflFtP1VgqnGU6LDZ0JDQFLEATjb92KUVq.ev63V8y9vTQA2E1MZ9d0Qv7GMYeT psH6DLkdM4cB6AFxsTuMEYgXdDHKkZVFDOiWCO1cNcJpcKCSi2mo- Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.ir2.yahoo.com with HTTP; Sat, 3 Feb 2018 15:39:02 +0000 Received: from smtp171.mail.ir2.yahoo.com (EHLO archlinux.localdomain) ([46.228.39.38]) by smtp414.mail.ir2.yahoo.com (JAMES SMTP Server ) with ESMTPA ID 5a475486c1843904cce9ca3c9636c93e; Sat, 03 Feb 2018 15:39:01 +0000 (UTC) Date: Sat, 3 Feb 2018 16:39:02 +0100 From: Ralf Mardorf To: freebsd-questions@freebsd.org Cc: Polytropon Subject: Re: German keyboard support for gdm??? Message-ID: <20180203163902.0ae3ea93@archlinux.localdomain> In-Reply-To: <20180203133622.1b4048de.freebsd@edvax.de> References: <20180202141115.aa7bbf16.freebsd@edvax.de> <20180203050115.102d6f98@archlinux.localdomain> <1517646306.4926.3.camel@alice-dsl.net> <1517646733.4926.6.camel@alice-dsl.net> <20180203133622.1b4048de.freebsd@edvax.de> X-Mailer: Claws Mail 3.16.0git24 (GTK+ 2.24.32; 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 15:39:10 -0000 On Sat, 3 Feb 2018 13:36:22 +0100, Polytropon wrote: >Overriding an X (global!) setting is still a bad idea for "the right >behaviour" for GDM, in my opinion... but well, that's Linux... ;-) I won't tolerate that :D! Asuming this should be the case, then it's a GTK/GNOME folks related upstream default config issue! I suspect that several display managers or their greeters provide an option to override X settings, but this at least is disabled by default (if this should be the GDM culprit, theire still is the chance for the FreeBSD maintainers to care about the defaults ;). However, FreeBSD does provide Linux DEs. At least the "big" DE's seem to require Wayland as an X replacement in the close future. The last time I used FreeBSD + Linux I was on Xfce, nowadays I'm using Linux only and migrated to a plain window manager. I can't stand DE's anymore and on top of my "I can't stand this list" is GNOME >2, given that I never tested Unity and I gnore something ridiculous, such as Enlightenment. Btw. I don't remember why I renamed a lightdm config to *fuck in 2013, but it definitively wasn't a keyboard language issue. $ ls -hAl /etc/lightdm/ total 40K -rw-r--r-- 1 root root 40 Dec 23 11:45 keys.conf -rw-r--r-- 1 root root 6.9K Dec 23 11:45 lightdm.conf -rw-r--r-- 1 root root 4.7K Aug 2 2013 lightdm.conf.fuck -rw-r--r-- 1 root root 1.1K Aug 7 2013 lightdm-gtk-greeter.conf -rw-r--r-- 1 root root 2.7K Mar 8 2015 lightdm-gtk-greeter.conf.2.0.0-2 -rw-r--r-- 1 root root 2.7K Oct 29 19:33 lightdm-gtk-greeter.conf.pacnew -rw-r--r-- 1 root root 452 Dec 23 11:45 users.conf -rwxr-xr-x 1 root root 1.5K Dec 23 11:45 Xsession Everything depending on GTK >= 3.20 does break things, even within minor relases, IOW you even can't trust common soname sense. From owner-freebsd-questions@freebsd.org Sat Feb 3 15:45:08 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 26670ED3CF0 for ; Sat, 3 Feb 2018 15:45:08 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mail.inka.de (quechua.inka.de [IPv6:2a04:c9c7:0:1073:217:a4ff:fe3b:e77c]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B77646ECF6 for ; Sat, 3 Feb 2018 15:45:07 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mips.inka.de (news@[127.0.0.1]) by mail.inka.de with uucp (rmailwrap 0.5) id 1ei001-0007id-IY; Sat, 03 Feb 2018 16:45:05 +0100 Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.15.2/8.15.2) with ESMTP id w13Fgc27002946 for ; Sat, 3 Feb 2018 16:42:38 +0100 (CET) (envelope-from news@lorvorc.mips.inka.de) Received: (from news@localhost) by lorvorc.mips.inka.de (8.15.2/8.15.2/Submit) id w13Fgcqq002945 for freebsd-questions@freebsd.org; Sat, 3 Feb 2018 16:42:38 +0100 (CET) (envelope-from news) To: freebsd-questions@freebsd.org From: Christian Weisgerber Newsgroups: list.freebsd.questions Subject: Re: Do Radeon HD 5450 graphics work under FreeBSD ? Date: Sat, 3 Feb 2018 15:42:38 -0000 (UTC) Message-ID: References: <9dffe9ca-8e6a-8016-8ee1-fe354ea21cc3@yandex.com> User-Agent: slrn/1.0.3 (FreeBSD) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 15:45:08 -0000 On 2018-02-01, Manish Jain wrote: > I need to find out a low cost Radeon card that works under FreeBSD and > is generally available in the US. XFX ATI Radeon HD5450 (1 GB; USD 34) > seems to be a good candidate, but I have no idea whether this card works > under FreeBSD ? Does anyone on this list use Radeon HD5450 ? I can confirm that the Radeon HD5450 works fine via xf86-video-ati and has for years. I'm using it in the machine I'm typing this on. -- Christian "naddy" Weisgerber naddy@mips.inka.de From owner-freebsd-questions@freebsd.org Sat Feb 3 15:55:06 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B5CB8ED4D97 for ; Sat, 3 Feb 2018 15:55:06 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mail.inka.de (quechua.inka.de [IPv6:2a04:c9c7:0:1073:217:a4ff:fe3b:e77c]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 531CE6F483 for ; Sat, 3 Feb 2018 15:55:06 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mips.inka.de (news@[127.0.0.1]) by mail.inka.de with uucp (rmailwrap 0.5) id 1ei09h-0008Bc-B3; Sat, 03 Feb 2018 16:55:05 +0100 Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.15.2/8.15.2) with ESMTP id w13FsUEb003162 for ; Sat, 3 Feb 2018 16:54:30 +0100 (CET) (envelope-from news@lorvorc.mips.inka.de) Received: (from news@localhost) by lorvorc.mips.inka.de (8.15.2/8.15.2/Submit) id w13FsUQp003161 for freebsd-questions@freebsd.org; Sat, 3 Feb 2018 16:54:30 +0100 (CET) (envelope-from news) To: freebsd-questions@freebsd.org From: Christian Weisgerber Newsgroups: list.freebsd.questions Subject: Re: Where do I find ntpd configure options? Date: Sat, 3 Feb 2018 15:54:30 -0000 (UTC) Message-ID: References: <1517362559.13652.1.camel@pki2.com> <20180131103511.290fed68.freebsd@edvax.de> User-Agent: slrn/1.0.3 (FreeBSD) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 15:55:06 -0000 On 2018-01-31, Polytropon wrote: > On Tue, 30 Jan 2018 17:35:59 -0800, Dennis Glatting wrote: >> I am looking for the NTPD configuration (./configure) options used to >> compile NTPD in /usr/src. Where can I find them? > > The directory to interact with its Makefile is /usr/src/usr.sbin/ntp/ntpd > from where you can "make install"; an individual ./configure step is not > needed here. The code of ntpd is in /usr/src/contrib/ntp/ntpd. The configure script generates a config.h file. In the FreeBSD build of the ntpd suite, configure isn't run, instead a pre-generated config.h file is supplied: /usr/src/usr.sbin/ntp/config.h Additional options are set in /usr/src/usr.sbin/ntp/Makefile.inc as -DXXX compiler flags. -- Christian "naddy" Weisgerber naddy@mips.inka.de From owner-freebsd-questions@freebsd.org Sat Feb 3 15:58:00 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E0B3EED6315 for ; Sat, 3 Feb 2018 15:57:59 +0000 (UTC) (envelope-from opsyspref@gmail.com) Received: from mail-oi0-x241.google.com (mail-oi0-x241.google.com [IPv6:2607:f8b0:4003:c06::241]) (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 777656F6B0 for ; Sat, 3 Feb 2018 15:57:59 +0000 (UTC) (envelope-from opsyspref@gmail.com) Received: by mail-oi0-x241.google.com with SMTP id j188so16901410oib.6 for ; Sat, 03 Feb 2018 07:57:59 -0800 (PST) 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=ZENj/wcK/S9eNRRX3AuQ60XCfi5ZPY6lnaLjAKqdL3c=; b=jhQ8h4jO04vY2tC94G9MhJhHG6NFkYLFtCli5UiOnAHmlNimQfQsUwg+XOtTPzTwH5 eNGGKoF+RD/pCMCZahy6wbRmIwi6DKERTynvfDOwy261p3H+YGjOZ1jQWhtFkZQA7pXd 6SD3P1p9L0odMgwkNZ32/4Ruufw2GbtCLFO24UrToEbQ1NJzXoJrbifLKVdm7owAPc05 NYKk8pMCGqnUZLtRM5lWhNwzD38lFaTmL8yHmqKPIZMPSYdgNlHq66H47XiK9J9PkcvX E/T4YzXDEWq1Me9Ryvawqm4HclphDOWvFPUmBjKXUgrEucr0AKJWTlwoOZcew4l+o6eg bRqg== 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=ZENj/wcK/S9eNRRX3AuQ60XCfi5ZPY6lnaLjAKqdL3c=; b=lhoMUf7fJ/SsAMPQ8hKiwxPwmZeA0tPLQBQuEsZiZn+zG5CZ/mWiqPVbJknybmjX8i WuAn3xt6u5PYnRXSd5TAiH40+xxg+WefClWlYs2MwtaUQKl7GzbHorNRDO2zp+B8Z2ly vxUqeJDXmVHNO/bYaBZp68tSAO+xTagRIai1Lq+N/Jln/mn3guQx4/tKlR4EhLT1V5fK juSoib8vEIrvtj3hlf4ejZMHOCgpb6PkgptJF8VFD0C8h9u3MFrGhbt/oG1jgZ0xocPi e1UCZ3HaC6H2vvnm1jVcZYGDMLgkbu3dXUEw2AMHKzhJzWfQS1kiJjH0QNBVM7FIl8SW 38Bg== X-Gm-Message-State: AKwxytfmLqPlNX9O0/m0o4nev/JveMzDIepJdf5nFmJ6qttA/CCaA4Dl u7TbzUu9dsMZ0FVj8UPKkvKnV/Jj1hX/gYqADNYkGw== X-Google-Smtp-Source: AH8x226DWbYSmgwkD7vRcwel5eyUNlKw5cFamwx2H86A+HPg+zrHEmgOX12aSZJeSSXXpjsoJH+42weS2KPSPWizgsg= X-Received: by 10.202.243.84 with SMTP id r81mr14192815oih.5.1517673478896; Sat, 03 Feb 2018 07:57:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.11.203 with HTTP; Sat, 3 Feb 2018 07:57:58 -0800 (PST) In-Reply-To: <20180203163902.0ae3ea93@archlinux.localdomain> References: <20180202141115.aa7bbf16.freebsd@edvax.de> <20180203050115.102d6f98@archlinux.localdomain> <1517646306.4926.3.camel@alice-dsl.net> <1517646733.4926.6.camel@alice-dsl.net> <20180203133622.1b4048de.freebsd@edvax.de> <20180203163902.0ae3ea93@archlinux.localdomain> From: Peter Ulrich Kruppa Date: Sat, 3 Feb 2018 16:57:58 +0100 Message-ID: Subject: Re: German keyboard support for gdm??? To: Ralf Mardorf Cc: freebsd-questions@freebsd.org, Polytropon Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 15:58:00 -0000 Hmm, this sounds a bit frustrated. I didn't use freebsd for some time because somewhere around 9.x things started getting a little bit too weird for my daily work. Last week I came across some old notebook at work and was completely surprised I could install and run FreeBSD 11.1 nearly "out of the box". Especially Gnome-3 runs as smoothly as one can expect and looks quite nice. So someone seems to have invested a lot of work and I would like to make use of it. Peter On Sat, Feb 3, 2018 at 4:39 PM, Ralf Mardorf via freebsd-questions < freebsd-questions@freebsd.org> wrote: > On Sat, 3 Feb 2018 13:36:22 +0100, Polytropon wrote: > >Overriding an X (global!) setting is still a bad idea for "the right > >behaviour" for GDM, in my opinion... but well, that's Linux... ;-) > > I won't tolerate that :D! Asuming this should be the case, then it's a > GTK/GNOME folks related upstream default config issue! > > I suspect that several display managers or their greeters provide an > option to override X settings, but this at least is disabled by > default (if this should be the GDM culprit, theire still is the chance > for the FreeBSD maintainers to care about the defaults ;). > > However, FreeBSD does provide Linux DEs. At least the "big" DE's seem > to require Wayland as an X replacement in the close future. > > The last time I used FreeBSD + Linux I was on Xfce, nowadays I'm using > Linux only and migrated to a plain window manager. I can't stand DE's > anymore and on top of my "I can't stand this list" is GNOME >2, > given that I never tested Unity and I gnore something ridiculous, such > as Enlightenment. > > Btw. I don't remember why I renamed a lightdm config to *fuck > in 2013, but it definitively wasn't a keyboard language issue. > > $ ls -hAl /etc/lightdm/ > total 40K > -rw-r--r-- 1 root root 40 Dec 23 11:45 keys.conf > -rw-r--r-- 1 root root 6.9K Dec 23 11:45 lightdm.conf > -rw-r--r-- 1 root root 4.7K Aug 2 2013 lightdm.conf.fuck > -rw-r--r-- 1 root root 1.1K Aug 7 2013 lightdm-gtk-greeter.conf > -rw-r--r-- 1 root root 2.7K Mar 8 2015 lightdm-gtk-greeter.conf.2.0.0-2 > -rw-r--r-- 1 root root 2.7K Oct 29 19:33 lightdm-gtk-greeter.conf.pacnew > -rw-r--r-- 1 root root 452 Dec 23 11:45 users.conf > -rwxr-xr-x 1 root root 1.5K Dec 23 11:45 Xsession > > Everything depending on GTK >= 3.20 does break things, even within > minor relases, IOW you even can't trust common soname sense. > _______________________________________________ > 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 Sat Feb 3 16:20:07 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CA928ED8470 for ; Sat, 3 Feb 2018 16:20:07 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mail.inka.de (quechua.inka.de [IPv6:2a04:c9c7:0:1073:217:a4ff:fe3b:e77c]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6B09F70315 for ; Sat, 3 Feb 2018 16:20:07 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mips.inka.de (news@[127.0.0.1]) by mail.inka.de with uucp (rmailwrap 0.5) id 1ei0Xu-0001E1-El; Sat, 03 Feb 2018 17:20:06 +0100 Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.15.2/8.15.2) with ESMTP id w13GIUik003871 for ; Sat, 3 Feb 2018 17:18:30 +0100 (CET) (envelope-from news@lorvorc.mips.inka.de) Received: (from news@localhost) by lorvorc.mips.inka.de (8.15.2/8.15.2/Submit) id w13GIUbB003870 for freebsd-questions@freebsd.org; Sat, 3 Feb 2018 17:18:30 +0100 (CET) (envelope-from news) To: freebsd-questions@freebsd.org From: Christian Weisgerber Newsgroups: list.freebsd.questions Subject: Re: Response to Meltdown and Spectre Date: Sat, 3 Feb 2018 16:18:30 -0000 (UTC) Message-ID: References: <23154.11945.856955.523027@jerusalem.litteratus.org> <5A726B60.7040606@gmail.com> <92120E50-19A7-4A44-90DF-505243D77259@kreme.com> User-Agent: slrn/1.0.3 (FreeBSD) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 16:20:08 -0000 On 2018-02-01, "@lbutlr" wrote: > That seems highly unlikely. It will damage the role of Intel in > the server market fora time, but the trouble is that AMD's behavior > has been at least as bad as Intel's, if not worse, in regards to > Meltdown, so there's not a clearly better choice even though the > AMD chips have less issues. AMD's initial response appeared to have been written by a PR person who simply summarized the vulnerability information from the Spectre/Meltdown papers and deployed the usual head-in-the-sand position that there is no vulnerability until an exploit is demonstrated. AMD has always said that their x86 CPUs are not vulnerable to Meltdown and nobody is contradicting them on this. However, like everybody else implementing speculative executaion, they are vulnerable to Spectre variants 1 and 2. The initial response downplayed this dangerously, but they eventually admitted it. The best reaction came from ARM. They provided a COMPLETE list of all their CPUs that are affected, and they documented another vulnerability (Meltdown 3a, reading of supervisor registers from user mode) that had not even been considered in the original research papers. -- Christian "naddy" Weisgerber naddy@mips.inka.de From owner-freebsd-questions@freebsd.org Sat Feb 3 16:40:07 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D38D2EDA023 for ; Sat, 3 Feb 2018 16:40:07 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mail.inka.de (quechua.inka.de [IPv6:2a04:c9c7:0:1073:217:a4ff:fe3b:e77c]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7200970F64 for ; Sat, 3 Feb 2018 16:40:07 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mips.inka.de (news@[127.0.0.1]) by mail.inka.de with uucp (rmailwrap 0.5) id 1ei0rG-000259-AH; Sat, 03 Feb 2018 17:40:06 +0100 Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.15.2/8.15.2) with ESMTP id w13GbNLB004307 for ; Sat, 3 Feb 2018 17:37:23 +0100 (CET) (envelope-from news@lorvorc.mips.inka.de) Received: (from news@localhost) by lorvorc.mips.inka.de (8.15.2/8.15.2/Submit) id w13GbNvt004306 for freebsd-questions@freebsd.org; Sat, 3 Feb 2018 17:37:23 +0100 (CET) (envelope-from news) To: freebsd-questions@freebsd.org From: Christian Weisgerber Newsgroups: list.freebsd.questions Subject: Re: Response to Meltdown and Spectre Date: Sat, 3 Feb 2018 16:37:23 -0000 (UTC) Message-ID: References: <23154.11945.856955.523027@jerusalem.litteratus.org> <5A726B60.7040606@gmail.com> <92120E50-19A7-4A44-90DF-505243D77259@kreme.com> <044e62f7-69ca-71fe-34a8-5c5cafc06f08@yahoo.com> User-Agent: slrn/1.0.3 (FreeBSD) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 16:40:08 -0000 On 2018-02-02, Paul Pathiakis via freebsd-questions wrote: > Intels patches have 'bricked' processors. Yes, made them totally > unusable as they rushed them out the door. They pulled them immediately > and told people to destroy them. That is wildly exaggerated. I'm running several machines with the microcode updates that Intel later pulled--in fact I'm typing this on one of them--and nothing has been bricked. Intel is extremely coy with details, but it stands to reason that the reliability problems that caused them to retract the microcode will only appear when the operating system actually uses the newly introduced IBRS/IBPB/STIBP features. -- Christian "naddy" Weisgerber naddy@mips.inka.de From owner-freebsd-questions@freebsd.org Sat Feb 3 16:59:22 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 81762EDB6AF for ; Sat, 3 Feb 2018 16:59:22 +0000 (UTC) (envelope-from ralf.mardorf@rocketmail.com) Received: from sonic310-13.consmr.mail.ir2.yahoo.com (sonic310-13.consmr.mail.ir2.yahoo.com [77.238.177.34]) (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 EA30071A0F for ; Sat, 3 Feb 2018 16:59:21 +0000 (UTC) (envelope-from ralf.mardorf@rocketmail.com) X-YMail-OSG: MJYsOZAVM1k8zUjdnjRc2A00mVWK3l8OtuXWdXfYbk6XNTBr2L96Yi8ZInWjDMt aCCIqWhHPevjFUKbSqP13BnYl6qmXdyiEwQM.TqUarx1Ao03y5Xo1cFfQqRlqtzrebidQ_wriJ_F ZE42dneNCrw6R1lareRgFJEA_yKKfXY4.lxw9KrlPAUr7AJvZe9NHgkZwWMl5QmUx38F7UAO7rl8 Ijh8jOt4RC_ToLNdanjMLIIQASRifCwYj4p8AWwD94Meh8.6XZAIekqPc7GfWQbSkzy7g_frZu2R 40RuAsOu5JzHnet57Ue_UViw4Z8MIHD7G7Xc3BXw4ZgW7WouO092RHRSBKhoY50gPTadje76xTWf y5aVFdLe1cO30QJ420ByKxliLOCl5mevh1Dyg5bd9JCLs4.USUUazCgb8j.YHisDQS2Oi__PqSnB x08UCpzBLLFkYTcKH3TYSavWoMbtpqO6xvQY_.URrCDOn0m5eT5UVhxMxcNg5YorYaLjbDBgYp1v a2S4lmUsMacRbzX7PiOkvr3LdQJBOTdrffde5cAa.Lg4GR6Fo0Uc- Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.ir2.yahoo.com with HTTP; Sat, 3 Feb 2018 16:59:19 +0000 Received: from smtp165.mail.ir2.yahoo.com (EHLO archlinux.localdomain) ([46.228.39.32]) by smtp413.mail.ir2.yahoo.com (JAMES SMTP Server ) with ESMTPA ID 477f1e93f70e20461c3e28380b7b36be for ; Sat, 03 Feb 2018 16:59:17 +0000 (UTC) Date: Sat, 3 Feb 2018 17:59:19 +0100 From: Ralf Mardorf To: freebsd-questions@freebsd.org Subject: Re: Response to Meltdown and Spectre Message-ID: <20180203175919.69a5dd44@archlinux.localdomain> In-Reply-To: References: <23154.11945.856955.523027@jerusalem.litteratus.org> <5A726B60.7040606@gmail.com> <92120E50-19A7-4A44-90DF-505243D77259@kreme.com> X-Mailer: Claws Mail 3.16.0git24 (GTK+ 2.24.32; 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 16:59:22 -0000 On Sat, 3 Feb 2018 16:18:30 -0000 (UTC), Christian Weisgerber wrote: >On 2018-02-01, "@lbutlr" wrote: > >> That seems highly unlikely. It will damage the role of Intel in >> the server market fora time, but the trouble is that AMD's behavior >> has been at least as bad as Intel's, if not worse, in regards to >> Meltdown, so there's not a clearly better choice even though the >> AMD chips have less issues. > >AMD's initial response appeared to have been written by a PR person >who simply summarized the vulnerability information from the >Spectre/Meltdown papers and deployed the usual head-in-the-sand >position that there is no vulnerability until an exploit is >demonstrated. > >AMD has always said that their x86 CPUs are not vulnerable to >Meltdown and nobody is contradicting them on this. However, like >everybody else implementing speculative executaion, they are >vulnerable to Spectre variants 1 and 2. The initial response >downplayed this dangerously, but they eventually admitted it. > >The best reaction came from ARM. They provided a COMPLETE list of >all their CPUs that are affected, and they documented another >vulnerability (Meltdown 3a, reading of supervisor registers from >user mode) that had not even been considered in the original research >papers. They are all liars, https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00088&languageid=en-fr doesn't list my Intel(R) Celeron(R) CPU G1840. I seriously doubt that it isn't affected. However, using FreeBSD I can't do the work of my domain. Using AMD processors I only made bad experiences for my domain, now with my first Intel CPU, I'm much more troublefree. the domain is real-time pro-audio. Blanket judgement regarding CPU, as well as kernel design are foolish. I didn't test if I need to do it, but I welcom that I could disable page-table isolation for new Linux kernels, since the Meltdown security vulnerability is irrelevand for an audio workstaton. In short, we should take the chance to reconsider the one computer for everything approach. Why not using computers with operating systems and CPUs tailored to their purposes? The one computer for everything attitude implies issues. I'm using a record player to listen to recordings and a washing machine to wash my clothes, they aren't networked. I'm using one and the same computer as a digital audio workstation and to access the Internet for emailing, browsing and updating, but I don't do both at the same time, so different boot options are helpful. For audio work I might buy a new computer with more horse power and more power consumption in the future and use another computer with less horse power and less power consumpton for emailing, browsing and downloading updates. The real issue is to expect the "eierlegende Wollmilchsau" (all-in-one device or creature suitable for every purpose), see https://upload.wikimedia.org/wikipedia/commons/f/f3/Wollmilchsau.jpg , since such monsters are asking for trouble. From owner-freebsd-questions@freebsd.org Sat Feb 3 19:00:06 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 33518EE3FD9 for ; Sat, 3 Feb 2018 19:00:06 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mail.inka.de (quechua.inka.de [IPv6:2a04:c9c7:0:1073:217:a4ff:fe3b:e77c]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C46D575D11 for ; Sat, 3 Feb 2018 19:00:05 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mips.inka.de (news@[127.0.0.1]) by mail.inka.de with uucp (rmailwrap 0.5) id 1ei32i-00016V-RR; Sat, 03 Feb 2018 20:00:04 +0100 Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.15.2/8.15.2) with ESMTP id w13Iuvps075330 for ; Sat, 3 Feb 2018 19:56:57 +0100 (CET) (envelope-from news@lorvorc.mips.inka.de) Received: (from news@localhost) by lorvorc.mips.inka.de (8.15.2/8.15.2/Submit) id w13IuvoO075329 for freebsd-questions@freebsd.org; Sat, 3 Feb 2018 19:56:57 +0100 (CET) (envelope-from news) To: freebsd-questions@freebsd.org From: Christian Weisgerber Newsgroups: list.freebsd.questions Subject: SUJ - turn off for SSDs? Date: Sat, 3 Feb 2018 18:56:57 -0000 (UTC) Message-ID: User-Agent: slrn/1.0.3 (FreeBSD) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 19:00:06 -0000 Recent commits to bsdinstall now enable softupdates journaling (SUJ) by default, with the caveat "turn off for SSDs". https://svnweb.freebsd.org/base/head/usr.sbin/bsdinstall/partedit/gpart_ops.c?view=log Why would you want to turn off journaling on SSDs? -- Christian "naddy" Weisgerber naddy@mips.inka.de From owner-freebsd-questions@freebsd.org Sat Feb 3 19:34:44 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 55BEEEE6645 for ; Sat, 3 Feb 2018 19:34:44 +0000 (UTC) (envelope-from ralf.mardorf@rocketmail.com) Received: from sonic307-7.consmr.mail.ir2.yahoo.com (sonic307-7.consmr.mail.ir2.yahoo.com [87.248.110.32]) (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 CC3D3773C1 for ; Sat, 3 Feb 2018 19:34:43 +0000 (UTC) (envelope-from ralf.mardorf@rocketmail.com) X-YMail-OSG: KNtg2KsVM1kqL4yqE_zn2bwR08dWbaKp9Z4GMydQkTlSBRIKScpNA1l7g4K5CPR qOq2J1Hl.XTVpKCpB2VpZYmrFLclMPRS_E_6jpunmtI6Wka80HYBbm0Tauec7heA3.vNLkw0moLe 2qFUHMuPVLre05ldmgmchNY5OL68yO2Em2l2TSxTLVM.ah3JMqGgONqT0bUlG5PXtZPUdHegjg3r .zKT7SIV4PBpiafY8F6m7K80OC_ls8NS1WECIk0mdh4hPbdq6FAEjwSvRwKvQehJ4aVose_d88AN kJw3r2CGIzuG_2ozn1NvN2VhKAeXVwoeZhAWd0ufXJX6JvMw7abedCOU5BLSDX2Vqmur5m8HCUJj eFMCZBr5DOCpNEk1nGKYj1vwK.tDuAHs59Oe_QOnNSMj4.hkbW_MxhWyxgj2NH6FhwaO3rpfMdE8 2SHIrBHoMAR8w77MWWtLqV__g1QrKvEGjBxrOuHE4NKcR01riiSFn08GiBKdpOupbmBfCy7y_yNE 3JFc3hdSLHRqa1sAQdz60oj_Fk5QV9n1y3wyt2qBXYy.bwbtCzpo- Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.ir2.yahoo.com with HTTP; Sat, 3 Feb 2018 19:34:34 +0000 Received: from smtp164.mail.ir2.yahoo.com (EHLO archlinux.localdomain) ([46.228.39.127]) by smtp412.mail.ir2.yahoo.com (JAMES SMTP Server ) with ESMTPA ID cdbfe01db642fd619483e2ce7469f45c for ; Sat, 03 Feb 2018 19:24:26 +0000 (UTC) Date: Sat, 3 Feb 2018 20:24:28 +0100 From: Ralf Mardorf To: freebsd-questions@freebsd.org Subject: Re: SUJ - turn off for SSDs? Message-ID: <20180203202428.4798ea4f@archlinux.localdomain> In-Reply-To: References: X-Mailer: Claws Mail 3.16.0git24 (GTK+ 2.24.32; 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 19:34:44 -0000 On Sat, 3 Feb 2018 18:56:57 -0000 (UTC), Christian Weisgerber wrote: >Why would you want to turn off journaling on SSDs? Because idiots guess that it's useful to decrease the write cycles, to increase the lifespan of SSDs? I migrated to SSDs only internal my tower desktop PC and just use external HDDs for backups. However, I treat my internal SSDs the same way as I treated my internal HDDs. I want to use my computer as a tool, without warpping any part of it in cotton wool. It already is bad enough, that I can't handle my LCD that rough as I could handl my CRTs. Don't watch too long at your LCD screen, since it could cause visable scratches. Sorry, actually I need to take a look very often and very long on my LCD screen and I also want to use any file system with or without journaling and any kind of work-flow when using a SSD. The only compromise I'm willng to do is cleaning my LCD display at full moon nights only, with microfibre cloth and destilated water only, instead of using the sandblaster I could use withou any side effects to clean my CRTs at any daytime and at half moon as well as full moon. From owner-freebsd-questions@freebsd.org Sat Feb 3 19:35:07 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D66B3EE66AD for ; Sat, 3 Feb 2018 19:35:07 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mail.inka.de (quechua.inka.de [IPv6:2a04:c9c7:0:1073:217:a4ff:fe3b:e77c]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 795AB773E3 for ; Sat, 3 Feb 2018 19:35:07 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mips.inka.de (news@[127.0.0.1]) by mail.inka.de with uucp (rmailwrap 0.5) id 1ei3ac-0005Q9-F1; Sat, 03 Feb 2018 20:35:06 +0100 Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.15.2/8.15.2) with ESMTP id w13JVTXv076103 for ; Sat, 3 Feb 2018 20:31:29 +0100 (CET) (envelope-from news@lorvorc.mips.inka.de) Received: (from news@localhost) by lorvorc.mips.inka.de (8.15.2/8.15.2/Submit) id w13JVTan076102 for freebsd-questions@freebsd.org; Sat, 3 Feb 2018 20:31:29 +0100 (CET) (envelope-from news) To: freebsd-questions@freebsd.org From: Christian Weisgerber Newsgroups: list.freebsd.questions Subject: Re: freebsd tar fails but not gtar ?!? Date: Sat, 3 Feb 2018 19:31:29 -0000 (UTC) Message-ID: References: <00d101d399eb$318a7c40$949f74c0$@shaw.ca> User-Agent: slrn/1.0.3 (FreeBSD) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 19:35:08 -0000 On 2018-01-30, "Dale Scott" wrote: > Hi all. I noticed the tar backup of my WordPress content directory is > failing. How is it failing? The "Can't translate pathname" messages you quote are warnings, not errors. > It?s been suggested that locale on the system > isn?t set correctly. Does this sound familiar to anyone? Well, when I take a file with UTF-8-encoded non-ASCII characters in its name and tar it up in the POSIX locale, then I get the same warning. Clearly tar is trying to normalize path name encodings in some way. Unfortunately this is not documented. My best guess is that it tries to iconv(3) path names from the current locale encoding to UTF-8. If the path names are have an invalid encoding in the current locale, iconv(3) fails, prompting the warning. You can simply ignore the warnings. If you extract the archive under the same conditions as those when you created it, the path names will be just fine. Or you can make sure that the character encoding in your locale setting matches those of the file names you are backing up. Most likely something like LC_CTYPE=en_US.UTF-8 will do. If you don't understand what I'm talking about, you might want to read up on those topics. > Next, native freebsd tar with --posix flag That switches the archive format from the default ustar to pax, says the man page, but you're not looking at an archive format limitation. > (google found some Linux posts that indicated pre-posix tar had > a filename length limit) Unless you are using a time machine to post from the 1980s, "old" pre-POSIX tar is utterly irrelevant. -- Christian "naddy" Weisgerber naddy@mips.inka.de From owner-freebsd-questions@freebsd.org Sat Feb 3 20:08:44 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F229EE8D26 for ; Sat, 3 Feb 2018 20:08:44 +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 AF64178B2D for ; Sat, 3 Feb 2018 20:08:43 +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 w13K8aZw006617 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 3 Feb 2018 13:08:36 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id w13K8ax8006614; Sat, 3 Feb 2018 13:08:36 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Sat, 3 Feb 2018 13:08:36 -0700 (MST) From: Warren Block To: Christian Weisgerber cc: freebsd-questions@freebsd.org Subject: Re: SUJ - turn off for SSDs? In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21 (BSF 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (wonkity.com [127.0.0.1]); Sat, 03 Feb 2018 13:08:36 -0700 (MST) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 20:08:44 -0000 On Sat, 3 Feb 2018, Christian Weisgerber wrote: > Recent commits to bsdinstall now enable softupdates journaling (SUJ) > by default, with the caveat "turn off for SSDs". > https://svnweb.freebsd.org/base/head/usr.sbin/bsdinstall/partedit/gpart_ops.c?view=log > > Why would you want to turn off journaling on SSDs? Because the problems it was meant to solve (slow fsck) are not a problem on SSDs, and SUJ has problems with snapshots for use with dump(8). From owner-freebsd-questions@freebsd.org Sat Feb 3 20:17:51 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B18B3EE96C4 for ; Sat, 3 Feb 2018 20:17:51 +0000 (UTC) (envelope-from ralf.mardorf@rocketmail.com) Received: from sonic310-13.consmr.mail.ir2.yahoo.com (sonic310-13.consmr.mail.ir2.yahoo.com [77.238.177.34]) (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 3B63079079 for ; Sat, 3 Feb 2018 20:17:50 +0000 (UTC) (envelope-from ralf.mardorf@rocketmail.com) X-YMail-OSG: 3x8b50EVM1nu97Crfzahn2kSeszbfXRMKJoGNKlypzyL7AWLgzxzmZYtxF_qPYq l6dX06wR5MkGwNnScFmszBfUTd_7B_2Kwf_Viq2iANT4a.XHuDkw6b6Q_y3uuw01ZLV1ajqCaqYX 3RZQdzErhu88YsekdGKTEatjTqTuVZ3x5JkT3TLnifxYef2jytmhOCX1FPqCGaqxRx_e31pHsUKo QlKHfTVJaKyz5ihKUKDhB1sSGj3P1hJKr.Q7Vcl7DArNyQNLOdmmakerSZbLw5RbgtENBl6Mf0b2 SJ7lX0kfhX222oEUGIpl9D6blHPdGP2sONO08srESgIVP2OLNnWylTbzm6U2YJG2Db4fml3iOvk. ebSHbXkXPdSMspAV_8Hmb3Xy.Ac9wThxr2kHq3yUV8Q1VkTh8LL2xifBp6X0F13rnAndS7A5KtJy 5EsBrB5RDpMk9CcpsuCKLqXuqr.f9KYhXcvCMHxHb1O8HbLgqp998izomRPF3t0gZhhUSMCIljPt LBDj0oU.t3fyOxdkrtoCa5yd2CWzxDnc4xvTThZzEjgdk9q0Tgqpa6gQ- Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.ir2.yahoo.com with HTTP; Sat, 3 Feb 2018 20:17:49 +0000 Received: from smtpgate101.mail.ir2.yahoo.com (EHLO archlinux.localdomain) ([217.146.189.7]) by smtp414.mail.ir2.yahoo.com (JAMES SMTP Server ) with ESMTPA ID ad7108b5aa0d9ffbfb2e0853ca2e220a for ; Sat, 03 Feb 2018 20:17:45 +0000 (UTC) Date: Sat, 3 Feb 2018 21:17:48 +0100 From: Ralf Mardorf To: freebsd-questions@freebsd.org Subject: Re: SUJ - turn off for SSDs? Message-ID: <20180203211748.44790724@archlinux.localdomain> In-Reply-To: References: X-Mailer: Claws Mail 3.16.0git24 (GTK+ 2.24.32; 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 20:17:51 -0000 On Sat, 3 Feb 2018 13:08:36 -0700 (MST), Warren Block wrote: >(slow fsck) are not a problem on SSDs Oops, so my guess is proven wrong. From owner-freebsd-questions@freebsd.org Sat Feb 3 20:33:57 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 29736EEA8D4 for ; Sat, 3 Feb 2018 20:33:57 +0000 (UTC) (envelope-from ralf.mardorf@rocketmail.com) Received: from sonic311-31.consmr.mail.ir2.yahoo.com (sonic311-31.consmr.mail.ir2.yahoo.com [77.238.176.163]) (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 989D579B9D for ; Sat, 3 Feb 2018 20:33:56 +0000 (UTC) (envelope-from ralf.mardorf@rocketmail.com) X-YMail-OSG: CT_BbyAVM1kfM8Zzl_L1cbihBKJUR1Z3ovj71BbKUqnpsqrF_U_NIqYybZp30zj ScemJN1RzINqzWxAKZn0QqG_nfNKU.e_z9.xW6qYJIeyTexrAQua4ygoZ5RuNOgkwncZpvtgmxg6 zCJGZmBMpfcJ4fP9vSn1IoHa.SGLylMeKDirpe8rLEs4cmOQjSEzlNlR3lwZKICpAWUs93QKFJj9 hbfAr2TlAhrMrVbBG5JpFIsH20Adhf4JNSCNk.ZLMnop4_VnJIeyclAeZ6MEIx7nRFbaPqS50PRf S8SBUdv9Xu5tz4TEQGRZHJmQtyX0Lfd4fze_d9sVHZC0CfJcVvPk1vAVYKXzLA69tYnPm_0z7kSX yi2Ec11ydbiQWFkLjmQat0bMcsnzTyR8xGbmixr3Dy3vmjKBX_qe.TXo1HfD4Pr.nlB5svVEQ_wc d9baETkcb9kSjPoBHSnF8nFoFfbCmfTAQ2s.4WFfHIS8NOmwqyJcgYjwYGxvCtRTTwEnK0SbpRG0 27mVRugcnSYU25IfTct9JrfSv_P.KqTHf.ylNojme8aZ_WkR4CqM- Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.ir2.yahoo.com with HTTP; Sat, 3 Feb 2018 20:33:54 +0000 Received: from smtpgate103.mail.ir2.yahoo.com (EHLO archlinux.localdomain) ([217.146.188.6]) by smtp407.mail.ir2.yahoo.com (JAMES SMTP Server ) with ESMTPA ID 4e047d4f287623482cb5c85e26c787df for ; Sat, 03 Feb 2018 20:23:46 +0000 (UTC) Date: Sat, 3 Feb 2018 21:23:49 +0100 From: Ralf Mardorf To: freebsd-questions@freebsd.org Subject: Re: SUJ - turn off for SSDs? Message-ID: <20180203212349.40b6ebb7@archlinux.localdomain> In-Reply-To: <20180203211748.44790724@archlinux.localdomain> References: <20180203211748.44790724@archlinux.localdomain> X-Mailer: Claws Mail 3.16.0git24 (GTK+ 2.24.32; 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 20:33:57 -0000 On Sat, 3 Feb 2018 21:17:48 +0100, Ralf Mardorf wrote: >On Sat, 3 Feb 2018 13:08:36 -0700 (MST), Warren Block wrote: >>(slow fsck) are not a problem on SSDs > >Oops, so my guess is proven wrong. It wasn't intended to shorten the qoutes this way :S, it was an accident. The full qoute should (does) read: >Because the problems it was meant to solve (slow fsck) are not a >problem on SSDs, and SUJ has problems with snapshots for use with >dump(8). From owner-freebsd-questions@freebsd.org Sat Feb 3 20:45:07 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3CF5FEEB3B3 for ; Sat, 3 Feb 2018 20:45:07 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mail.inka.de (quechua.inka.de [IPv6:2a04:c9c7:0:1073:217:a4ff:fe3b:e77c]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CEB537A24B for ; Sat, 3 Feb 2018 20:45:06 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mips.inka.de (news@[127.0.0.1]) by mail.inka.de with uucp (rmailwrap 0.5) id 1ei4gL-0001z6-Op; Sat, 03 Feb 2018 21:45:05 +0100 Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.15.2/8.15.2) with ESMTP id w13KiUwA001420 for ; Sat, 3 Feb 2018 21:44:30 +0100 (CET) (envelope-from news@lorvorc.mips.inka.de) Received: (from news@localhost) by lorvorc.mips.inka.de (8.15.2/8.15.2/Submit) id w13KiU1A001419 for freebsd-questions@freebsd.org; Sat, 3 Feb 2018 21:44:30 +0100 (CET) (envelope-from news) To: freebsd-questions@freebsd.org From: Christian Weisgerber Newsgroups: list.freebsd.questions Subject: How to set default pcm device? Date: Sat, 3 Feb 2018 20:44:30 -0000 (UTC) Message-ID: User-Agent: slrn/1.0.3 (FreeBSD) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 20:45:07 -0000 After boot, my /dev/sndstat looks like this: Installed devices: pcm0: (play) pcm1: (play/rec) default pcm2: (play/rec) pcm3: (play) No devices installed from userspace. However, I would like the USB audio device, pcm3, to be the default sound unit. How do I set this persistently across reboots? The traditional solution was to set hw.snd.default_unit=3 in /boot/loader.conf. That worked for FreeBSD 10.x, but with 11.x the USB devices are attached very late and the boot loader setting (which I still have) is effectively ignored. Loading the uaudio module early with snd_uaudio_load=YES doesn't change this. Setting hw.snd.default_unit in /etc/sysctl.conf is unlikely to work either; certainly it's a race. Do I need to define a devd(8) action for when uaudio attaches or is there a better way? -- Christian "naddy" Weisgerber naddy@mips.inka.de From owner-freebsd-questions@freebsd.org Sat Feb 3 22:30:17 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4CD10EC82C6 for ; Sat, 3 Feb 2018 22:30:17 +0000 (UTC) (envelope-from pathiaki2@yahoo.com) Received: from sonic305-4.consmr.mail.bf2.yahoo.com (sonic305-4.consmr.mail.bf2.yahoo.com [74.6.133.43]) (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 DCF447E6F7 for ; Sat, 3 Feb 2018 22:30:16 +0000 (UTC) (envelope-from pathiaki2@yahoo.com) X-YMail-OSG: jrMwy_AVM1mNaimjGRfiiFlGOqhCztdLpxuEft7.earR4LswK8iy00.bztLCF9Q xWh5gMDuJMdj1mFogDkFPcRLpGxg8VUYAYKOE5lQn5HLPBryszxVufbXmNfYli_yfhTj7Wo4MvH0 YxyVvbDAwhHaqiljjo9jL.rfP8xJfM8ErHZQ1wnMa7aF_VHNe0dZ83tPlfqbxPl07WzsLLtflrsv YnUz3vVe8bXwVN4kzzbLDLZjRCbNe56DWMO_BiyYKWY3GV.iFHQaoRXCQHUsXDLROCdU33hEqZ2X 3WDozl98sl7642uPya1q4mOd3PsOFJPPGazn8dLxlM4RM04lrtGFiO62ufIdsNzQc8NOBCudUMB_ V5Fc5XXSqLNzVYArtnl0lBXfDAKJCPUWUN9OxuXzqzKMvOONG5YBZ6z3vbnDz2aoJTJtgTEi9brJ 5S40Hc5jPo4fbeipNW_QuzxNqgU40hZmpu9UnlAUje6Djo17qedg8hCA7TNQGY5mPi.o7lc3svOR mZIc332s21f.znw.O2l12KaBpEd0- Received: from sonic.gate.mail.ne1.yahoo.com by sonic305.consmr.mail.bf2.yahoo.com with HTTP; Sat, 3 Feb 2018 22:30:16 +0000 Received: from smtpgate103.mail.bf1.yahoo.com (EHLO [192.168.0.201]) ([72.30.28.111]) by smtp401.mail.bf1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID a38a1f87bfc03813acd05d55f82bdf32 for ; Sat, 03 Feb 2018 22:30:11 +0000 (UTC) Subject: Re: Response to Meltdown and Spectre To: freebsd-questions@freebsd.org References: <23154.11945.856955.523027@jerusalem.litteratus.org> <5A726B60.7040606@gmail.com> <92120E50-19A7-4A44-90DF-505243D77259@kreme.com> <044e62f7-69ca-71fe-34a8-5c5cafc06f08@yahoo.com> From: Paul Pathiakis Message-ID: <0520dd84-c00c-fbf2-da1c-f6ff4c63739d@yahoo.com> Date: Sat, 3 Feb 2018 17:30:10 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 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-Antivirus: AVG (VPS 180203-0, 02/03/2018), Outbound message X-Antivirus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 22:30:17 -0000 http://www.zdnet.com/article/meltdown-spectre-firmware-glitch-intel-warns-of-risk-of-sudden-reboots/ The sudden reboots and non-starts have been tracked to the patch. On 2/3/2018 11:37 AM, Christian Weisgerber wrote: > On 2018-02-02, Paul Pathiakis via freebsd-questions wrote: > >> Intels patches have 'bricked' processors. Yes, made them totally >> unusable as they rushed them out the door. They pulled them immediately >> and told people to destroy them. > That is wildly exaggerated. I'm running several machines with the > microcode updates that Intel later pulled--in fact I'm typing this > on one of them--and nothing has been bricked. Intel is extremely > coy with details, but it stands to reason that the reliability > problems that caused them to retract the microcode will only appear > when the operating system actually uses the newly introduced > IBRS/IBPB/STIBP features. > --- This email has been checked for viruses by AVG. http://www.avg.com From owner-freebsd-questions@freebsd.org Sat Feb 3 22:48:50 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 04DE7EC9F1D for ; Sat, 3 Feb 2018 22:48:50 +0000 (UTC) (envelope-from zarniwhoop@ntlworld.com) Received: from know-smtprelay-omc-3.server.virginmedia.net (know-smtprelay-omc-3.server.virginmedia.net [80.0.253.67]) (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 93C777F7D2 for ; Sat, 3 Feb 2018 22:48:49 +0000 (UTC) (envelope-from zarniwhoop@ntlworld.com) Received: from localhost.localdomain ([81.97.232.230]) by cmsmtp with ESMTP id i6ZYeelLAsTvEi6ZYeUvWV; Sat, 03 Feb 2018 22:46:12 +0000 X-Originating-IP: [81.97.232.230] X-Authenticated-User: X-Spam: 0 X-Authority: v=2.3 cv=VocN/d+n c=1 sm=1 tr=0 a=obylDaYnIsVqxbenyIBF4Q==:117 a=obylDaYnIsVqxbenyIBF4Q==:17 a=IkcTkHD0fZMA:10 a=x7bEGLp0ZPQA:10 a=Op4juWPpsa0A:10 a=sA-ssjpUAAAA:8 a=5l4X1vu6py5dhS5auckA:9 a=QEXdDO2ut3YA:10 a=MeU51efvtLpnGWnoXA2X:22 Received: by localhost.localdomain (Postfix, from userid 1000) id 2D75E41BA4; Sat, 3 Feb 2018 22:46:12 +0000 (GMT) Date: Sat, 3 Feb 2018 22:46:12 +0000 From: Ken Moffat To: Paul Pathiakis via freebsd-questions Subject: Re: Response to Meltdown and Spectre Message-ID: <20180203224612.GA10517@milliways.localdomain> References: <23154.11945.856955.523027@jerusalem.litteratus.org> <5A726B60.7040606@gmail.com> <92120E50-19A7-4A44-90DF-505243D77259@kreme.com> <044e62f7-69ca-71fe-34a8-5c5cafc06f08@yahoo.com> <0520dd84-c00c-fbf2-da1c-f6ff4c63739d@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline X-Clacks-Overhead: GNU Terry Pratchett Content-Transfer-Encoding: 8bit In-Reply-To: <0520dd84-c00c-fbf2-da1c-f6ff4c63739d@yahoo.com> User-Agent: Mutt/1.9.3 (2018-01-21) X-CMAE-Envelope: MS4wfM2Lo6MaBGqTMPvnjwAbq6QDFIzfc/GkXyN/r1FGdXVQPpCTp2OwDe2L1uXmgci1Q8TXPtSNqG8QHSN2AvXOxHWoN5D/vGVWJyzKc6NBTDizG5pOwr1R yJ7I62LxfiDwpJjBcAhatqq7Pk3UGL6COBU17kF4cNaJ7gTiJYRyjShUjTTqwd1T5qFttWFAxLRzporcVkrAUeBKdv6IIAok0xQ= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 22:48:50 -0000 On Sat, Feb 03, 2018 at 05:30:10PM -0500, Paul Pathiakis via freebsd-questions wrote: > http://www.zdnet.com/article/meltdown-spectre-firmware-glitch-intel-warns-of-risk-of-sudden-reboots/ > > The sudden reboots and non-starts have been tracked to the patch. > > Well, I've certainly heard of these microcode versions being blamed for sudden reboots, but like Christian I'm using the now-withdrawn versions on two machines without issue. But then I'm applying them from linux (I don't trust BIOS updates, even if they are available). I haven't heard of non-starts, but I suppose that would be down to BIOS or EFI updates. Probably my hardware is different (each microcode blob applies to a range of different machines in the same generation, and probably to different steppings), and also I'm not using VMs. ĸen -- Truth, in front of her huge walk-in wardrobe, selected black leather boots with stiletto heels for such a barefaced truth. - Unseen Academicals From owner-freebsd-questions@freebsd.org Sat Feb 3 23:42:21 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99AE9ED263C for ; Sat, 3 Feb 2018 23:42:21 +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 4A57581624 for ; Sat, 3 Feb 2018 23:42:20 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id AD056CB8D0F; Sat, 3 Feb 2018 17:12:11 -0600 (CST) Received: from 108.68.160.114 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Sat, 3 Feb 2018 17:12:11 -0600 (CST) Message-ID: <51178.108.68.160.114.1517699531.squirrel@cosmo.uchicago.edu> In-Reply-To: <20180203224612.GA10517@milliways.localdomain> References: <23154.11945.856955.523027@jerusalem.litteratus.org> <5A726B60.7040606@gmail.com> <92120E50-19A7-4A44-90DF-505243D77259@kreme.com> <044e62f7-69ca-71fe-34a8-5c5cafc06f08@yahoo.com> <0520dd84-c00c-fbf2-da1c-f6ff4c63739d@yahoo.com> <20180203224612.GA10517@milliways.localdomain> Date: Sat, 3 Feb 2018 17:12:11 -0600 (CST) Subject: Re: Response to Meltdown and Spectre From: "Valeri Galtsev" To: "Ken Moffat" Cc: "Paul Pathiakis via freebsd-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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 23:42:21 -0000 On Sat, February 3, 2018 4:46 pm, Ken Moffat via freebsd-questions wrote: > On Sat, Feb 03, 2018 at 05:30:10PM -0500, Paul Pathiakis via > freebsd-questions wrote: >> http://www.zdnet.com/article/meltdown-spectre-firmware-glitch-intel-warns-of-risk-of-sudden-reboots/ >> >> The sudden reboots and non-starts have been tracked to the patch. >> >> > Well, I've certainly heard of these microcode versions being blamed > for sudden reboots, but like Christian I'm using the now-withdrawn > versions on two machines without issue. But then I'm applying them > from linux (I don't trust BIOS updates, even if they are available). With all due respect, one person saying, it didn't affect me, doesn't prove it is not disastrous for somebody else. Even if it is one machine out of thousand that is "bricked" for some time, it is a disaster for sysadmin who has that machine as a production server (don't think in terms of home workstation, these are not comparable by any means). I'm glad Intel withdrew what was potentially dangerous for some users. Does not excuse then for [thoughtlessly it appears] implementation of "cheating the reality" type of performance improvement tricks ;-( This is going to be long and painful way (on the end user side for sure) out of this crap we all are in now. Just my $0.02. Valeri > > I haven't heard of non-starts, but I suppose that would be down to > BIOS or EFI updates. > > Probably my hardware is different (each microcode blob applies to a > range of different machines in the same generation, and probably to > different steppings), and also I'm not using VMs. > > ĸen > -- > Truth, in front of her huge walk-in wardrobe, selected black leather > boots with stiletto heels for such a barefaced truth. > - Unseen Academicals > _______________________________________________ > 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 ++++++++++++++++++++++++++++++++++++++++