Date: Fri, 21 Jul 2017 11:25:00 +0200 From: "Kristof Provost" <kristof@sigsegv.be> To: "Nikos Vassiliadis" <nvass@gmx.com> Cc: "Panagiotes Mousikides" <paggas1@yandex.com>, "Alan Somers" <asomers@freebsd.org>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, "FreeBSD Current" <freebsd-current@freebsd.org> Subject: Re: Attn: CI/Jenkins people; Run bhyve instance for testing pf Message-ID: <1DA23B47-AC65-450F-A643-55162D300638@sigsegv.be> In-Reply-To: <81ab7ffc-c89d-0a79-5736-32d555366f3f@gmx.com> References: <871d6043-0c56-2c9b-1e3e-5db33898c24a@yandex.com> <CAOtMX2g8T48p2jereubD46yeVpsOjmHNX_Bt7G6N0BP4kuZ%2Bdw@mail.gmail.com> <a7468a38-5288-9eb2-b354-ec797e46d39e@yandex.com> <81ab7ffc-c89d-0a79-5736-32d555366f3f@gmx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 20 Jul 2017, at 18:24, Nikos Vassiliadis wrote: > It would be great if you use vnet jails for that. I am not > sure regarding the per-vnet pf functionality but I have seen > many bug fixes hitting the tree since last year. You can ask > on freebsd-virtualization@freebsd.org or freebsd-pf@freebsd.org > to learn more about it. > It’s starting to become usable, yes. > Pf within a jail should behave more or less like the "normal" one. > Plus you will be testing per-vnet functionality, which the project > needs anyhow, in one go. > It *should* behave the same, but the fact is that a setup like that tests vnet pf, not just pf. Ideally we should have both setups, but the priority should be on the setup most people use today, which is not vnet enabled. Regards, Kristof From owner-freebsd-hackers@freebsd.org Fri Jul 21 09:41:27 2017 Return-Path: <owner-freebsd-hackers@freebsd.org> Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2645DA0A8E for <freebsd-hackers@mailman.ysv.freebsd.org>; Fri, 21 Jul 2017 09:41:27 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id BBAA46A085 for <freebsd-hackers@FreeBSD.org>; Fri, 21 Jul 2017 09:41:27 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yv.noip.me (c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id v6L9fLpu031309 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <freebsd-hackers@FreeBSD.org>; Fri, 21 Jul 2017 02:41:21 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56] claimed to be yv.noip.me From: Yuri <yuri@rawbw.com> Subject: Do midi devices work on FreeBSD? To: Freebsd hackers list <freebsd-hackers@FreeBSD.org> Message-ID: <9d39ebdc-8b61-b3f9-b6c1-1b99e1f932e6@rawbw.com> Date: Fri, 21 Jul 2017 02:41:19 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD <freebsd-hackers.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>; List-Post: <mailto:freebsd-hackers@freebsd.org> List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 21 Jul 2017 09:41:28 -0000 The midi device isn't created for the soundcard that has a "midi" driver: EMU10Kx. For some weird reason even the probe in kernel, emu_midi_probe, isn't called. Yuri
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1DA23B47-AC65-450F-A643-55162D300638>