From owner-freebsd-hackers@freebsd.org Sun Mar 6 01:18:46 2016 Return-Path: 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 2468C9DBB02 for ; Sun, 6 Mar 2016 01:18:46 +0000 (UTC) (envelope-from jim@netgate.com) Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::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 02D7B9B6 for ; Sun, 6 Mar 2016 01:18:45 +0000 (UTC) (envelope-from jim@netgate.com) Received: by mail-pf0-x230.google.com with SMTP id 63so57639293pfe.3 for ; Sat, 05 Mar 2016 17:18:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netgate.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kCAc8TLAjY55r+mpZEijTWHcSBWnVVc6hBQLTg985oE=; b=WEGWVHkqcj2gk5esmjaBXWth1Imj++9MIzIX5DpTiWXvEc3A4ZWgUUb1yaOcI31DuS rKCfo0ZyR2T9zUfZQYfpkc7bypls4hyXaF5+vcIhG8KoG32a3SUoeDpFujZ1vwrRO7oC yPWwWw/4QY+km+mFhJcZKarSXbz42jZ/Vcx7g= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kCAc8TLAjY55r+mpZEijTWHcSBWnVVc6hBQLTg985oE=; b=ayaTlWhmIPh5iprIVxRd665aLDQv7noffK6+E2Sn/RmovA1+jOBBiL6xwKnQbhRYfC J1FfxCclm4A13eslBmQx5KnKKZqqPMDCDGlsJ7zRTWfKLExxUomsegCBgWRtpde8oHDQ rjKajzyQwlUD7sFf16//mKr7lJTA86ATIAg6RG6sHSZIwmkIIwmsrNwXiGfKbgsJQkao KxjghYscNFvkuXlF92oYqkPsutBOfCR6I0I73kDXMedN96ERVtm/pIFlj7vpYKIZk5eQ Vx+pRWSEZyih/DH8ksA0RF6sAB8aiC0ZB6A0M8w+9vFI/IxZd7+/qVAKgZXd9ld26RqY Ljyg== X-Gm-Message-State: AD7BkJI1e/rVUW7bywRvlmWVEjRASAdiJT/j/TjoetOdC2XmpHtsIcQvF2Kqcms9qh+6xQ== X-Received: by 10.98.66.157 with SMTP id h29mr23310920pfd.91.1457227125454; Sat, 05 Mar 2016 17:18:45 -0800 (PST) Received: from [172.20.13.190] ([60.36.186.18]) by smtp.gmail.com with ESMTPSA id 82sm14837917pfi.78.2016.03.05.17.18.43 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 05 Mar 2016 17:18:43 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: Looking for security-related intro project From: Jim Thompson X-Mailer: iPhone Mail (13D15) In-Reply-To: <56DB6352.8010600@gmail.com> Date: Sun, 6 Mar 2016 10:18:39 +0900 Cc: freebsd-hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <46A8199A-2BDC-4A9D-8356-66F4672D7C7B@netgate.com> References: <56DB6352.8010600@gmail.com> To: "m.bryn1u" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Mar 2016 01:18:46 -0000 That's not FreeBSD.=20 -- Jim > On Mar 6, 2016, at 7:53 AM, m.bryn1u wrote: >=20 > Try hardenedbsd.org >=20 > U will find there many security features :) >=20 >> On 05.03.2016 23:45, Kamila Sou=C4=8Dkov=C3=A1 wrote: >> Hello, >>=20 >> I am looking for a project that would help me get started with contributi= ng >> to FreeBSD. I am most interested in something security-related (and as I >> need a project for a security class at my university, going for security >> would allow/force me to dedicate more time to this). I am aware that >> "starting with security" sounds like a horrible idea, and I would like to= >> try anyway. Non-trivial is OK (in fact, good). Any suggestions? >>=20 >> (BTW, I have seen PR 206607 - Update base OpenSSL to 1.0.2, but that >> probably wouldn't be accepted for my school project.) >>=20 >> Thank you! >>=20 >> Kamila >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " >=20 > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"= From owner-freebsd-hackers@freebsd.org Sun Mar 6 07:58:27 2016 Return-Path: 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 CE796AB69A3 for ; Sun, 6 Mar 2016 07:58:27 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: from puchar.net (puchar.net [188.252.31.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 36D2CB0A for ; Sun, 6 Mar 2016 07:58:26 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.15.2/8.14.9) with ESMTPS id u267TE7r044633 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 6 Mar 2016 08:29:14 +0100 (CET) (envelope-from wojtek@puchar.net) Received: from laptop.wojtek.intra (localhost [127.0.0.1]) by laptop.wojtek.intra (8.14.9/8.14.9) with ESMTP id u267TAfY004738; Sun, 6 Mar 2016 08:29:10 +0100 (CET) (envelope-from wojtek@puchar.net) Received: from localhost (wojtek@localhost) by laptop.wojtek.intra (8.14.9/8.14.9/Submit) with ESMTP id u267T55h004735; Sun, 6 Mar 2016 08:29:05 +0100 (CET) (envelope-from wojtek@puchar.net) X-Authentication-Warning: laptop.wojtek.intra: wojtek owned process doing -bs Date: Sun, 6 Mar 2016 08:29:05 +0100 (CET) From: Wojciech Puchar X-X-Sender: wojtek@laptop.wojtek.intra To: Tom Sparks cc: freebsd-hackers@freebsd.org Subject: Re: Pic32 toolchain support In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (puchar.net [10.0.1.1]); Sun, 06 Mar 2016 08:29:14 +0100 (CET) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Mar 2016 07:58:27 -0000 > Has anyone looked at using FreeBSD for working with PIC32 based devices? I don't program pic32 (but STM32) but for toolchain just download gcc and build mips-none-eabi target. building is quite messy but after this it works. Personally i DO NOT use any libraries and other manufacturer supplied shit, instruction consist of all addresses so it's better to just write and read data from peripherals directly. For STM32 i have my own "crt0" (actually 192 bytes of interrupt tables and 20 bytes of startup assembly). For PIC32 make your own. As for programming - there are free software but for linux. you may have to modify sources a bit but it should not be a problem. From owner-freebsd-hackers@freebsd.org Sun Mar 6 11:00:42 2016 Return-Path: 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 6DFC8A954DA for ; Sun, 6 Mar 2016 11:00:42 +0000 (UTC) (envelope-from kamisouckova@gmail.com) Received: from mail-lb0-f176.google.com (mail-lb0-f176.google.com [209.85.217.176]) (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 03DF9110D for ; Sun, 6 Mar 2016 11:00:41 +0000 (UTC) (envelope-from kamisouckova@gmail.com) Received: by mail-lb0-f176.google.com with SMTP id xr8so6439694lbb.1 for ; Sun, 06 Mar 2016 03:00:41 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fEyVekqm5jpD4v2SY3pKWV9FflKk9C1H4nmGaWqq5Ts=; b=Wgt4uotq4gbaVpznG+xkkgVjFts76mxBoYpN/npn05N70wxVvVk0x2YyrgrEjlw/Kj lM5z/mXQU2m5bW89wmKc3kNHHPykM89jRu4lSeUYjf+BRdFDJFBbRr4rGCWwJ6ymAdgY zlW70Prg4Z8QBtHuTXBIAah7dxffmF/ggb7bdoPlDzdHqyKqQ8UbIRB4ZoT6J/wLQh8D kWrJroIt64hD3len4rjYqT31z1l6B1V3TB0AtIL8IXJyDeRWYkir9ffpDVKJqyhS1OPZ NARD6wfgyLmjd+58+ohgWabWqDZb3c5Nqfc3Fz8eWb738dPUr0kOKR9dfRz0PSQSDr1d FhPw== X-Gm-Message-State: AD7BkJKUcJUZbEqh0j6Pc51PrBErgCkUznV6Z47mrNX2AMUNmsLqpVmo/16fqN3juxsj0fEFwIiKdAh8dSORTA== X-Received: by 10.113.3.6 with SMTP id bs6mr6088793lbd.114.1457262033607; Sun, 06 Mar 2016 03:00:33 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?B?S2FtaWxhIFNvdcSNa292w6E=?= Date: Sun, 06 Mar 2016 11:00:24 +0000 Message-ID: Subject: Re: Looking for security-related intro project To: alan somers , m.bryn1u@gmail.com, outbackdingo@gmail.com Cc: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Mar 2016 11:00:42 -0000 > > How about adding Capsicum support to your favorite daemon? > > Try hardenedbsd.org > HardenedBSD looks great, but I currently can't use it in production, so I'll start with adding Capsicum to something I'll end up using. Thanks a lot for the suggestions! Kamila From owner-freebsd-hackers@freebsd.org Sun Mar 6 12:15:24 2016 Return-Path: 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 E5FBD9DA585 for ; Sun, 6 Mar 2016 12:15:24 +0000 (UTC) (envelope-from afiskon@devzen.ru) Received: from relay12.nicmail.ru (relay12.nicmail.ru [195.208.5.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9BA0DA96 for ; Sun, 6 Mar 2016 12:15:24 +0000 (UTC) (envelope-from afiskon@devzen.ru) Received: from [31.177.73.174] (port=54551 helo=nicmail.ru) by f06.mail.nic.ru with esmtp (Exim 5.55) (envelope-from ) id 1acXas-0007LD-1b; Sun, 06 Mar 2016 15:15:30 +0300 Received: from [10.0.6.224] (account afiskon@devzen.ru HELO fujitsu) by fcgp24.nicmail.ru (CommuniGate Pro SMTP 5.2.3) with ESMTPA id 70748480; Sun, 06 Mar 2016 15:15:21 +0300 Received: from [188.123.231.37] (account afiskon@devzen.ru HELO fujitsu) by proxy04.mail.nic.ru (Exim 5.55) with id 1acXaj-0003w7-Px; Sun, 06 Mar 2016 15:15:21 +0300 Date: Sun, 6 Mar 2016 15:12:40 +0300 From: Eax Melanhovich To: Kamila =?UTF-8?B?U291xI1rb3bDoQ==?= Cc: freebsd-hackers@freebsd.org Subject: Re: Looking for security-related intro project Message-ID: <20160306151240.5be6fc41@fujitsu> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Mar 2016 12:15:25 -0000 Hello, Kamila I personally find networking in FreeBSD Jails (this feature is considered security related, right?) not particularly user friendly. It would be nice to have something similar to how LXC and OpenVZ works. You just say "create container" and voila --- container has access to the Internet and you also have host-guest system networking. All of this is by default. No static IPs or anything else is required. Sounds like a good idea for security-related project to me. -- Best regards, Eax Melanhovich http://eax.me/ From owner-freebsd-hackers@freebsd.org Sun Mar 6 12:52:57 2016 Return-Path: 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 949E0A958C2 for ; Sun, 6 Mar 2016 12:52:57 +0000 (UTC) (envelope-from afiskon@devzen.ru) Received: from relay15.nicmail.ru (relay15.nicmail.ru [195.208.5.161]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 48F6BE06 for ; Sun, 6 Mar 2016 12:52:56 +0000 (UTC) (envelope-from afiskon@devzen.ru) Received: from [31.177.73.62] (port=60386 helo=nicmail.ru) by f19.mail.nic.ru with esmtp (Exim 5.55) (envelope-from ) id 1acY5c-000IC8-AX; Sun, 06 Mar 2016 15:47:16 +0300 Received: from [10.0.6.226] (account afiskon@devzen.ru HELO fujitsu) by fcgp14.nicmail.ru (CommuniGate Pro SMTP 5.2.3) with ESMTPA id 17722630; Sun, 06 Mar 2016 15:47:16 +0300 Received: from [188.123.231.37] (account afiskon@devzen.ru HELO fujitsu) by proxy06.mail.nic.ru (Exim 5.55) with id 1acY5c-000246-06; Sun, 06 Mar 2016 15:47:16 +0300 Date: Sun, 6 Mar 2016 15:44:34 +0300 From: Eax Melanhovich To: Kamila =?UTF-8?B?U291xI1rb3bDoQ==?= Cc: freebsd-hackers@freebsd.org Subject: Re: Looking for security-related intro project Message-ID: <20160306154434.5a9a77b0@fujitsu> In-Reply-To: <20160306151240.5be6fc41@fujitsu> References: <20160306151240.5be6fc41@fujitsu> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Mar 2016 12:52:57 -0000 Another idea: create a port of Telegram instant messenger. There is a CLI client in FreeBSD ports and there is also a web-version of Telegram. But a native GUI client is currently not ported. Telegram is an open source instant messaging application with end-to-end encryption feature: * https://telegram.org/ * https://github.com/telegramdesktop/tdesktop -- Best regards, Eax Melanhovich http://eax.me/ From owner-freebsd-hackers@freebsd.org Sun Mar 6 19:53:53 2016 Return-Path: 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 2F3FDA95F9D for ; Sun, 6 Mar 2016 19:53:53 +0000 (UTC) (envelope-from afiskon@devzen.ru) Received: from relay16.nicmail.ru (relay16.nicmail.ru [195.208.5.134]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D9665BC6 for ; Sun, 6 Mar 2016 19:53:51 +0000 (UTC) (envelope-from afiskon@devzen.ru) Received: from [31.177.73.204] (port=41343 helo=nicmail.ru) by f17.mail.nic.ru with esmtp (Exim 5.55) (envelope-from ) id 1aceet-000L8b-4z for freebsd-hackers@freebsd.org; Sun, 06 Mar 2016 22:48:07 +0300 Received: from [10.0.6.228] (account afiskon@devzen.ru HELO fujitsu) by fcgp26.nicmail.ru (CommuniGate Pro SMTP 5.2.3) with ESMTPA id 12419503 for freebsd-hackers@freebsd.org; Sun, 06 Mar 2016 22:48:07 +0300 Received: from [188.123.231.37] (account afiskon@devzen.ru HELO fujitsu) by proxy08.mail.nic.ru (Exim 5.55) with id 1aceet-0008WH-9F for freebsd-hackers@freebsd.org; Sun, 06 Mar 2016 22:48:07 +0300 Date: Sun, 6 Mar 2016 22:45:21 +0300 From: Eax Melanhovich To: freebsd-hackers@freebsd.org Subject: A few question regarding DDB Message-ID: <20160306224521.30c234fc@fujitsu> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Mar 2016 19:53:53 -0000 Hello I'm learning DDB and here are a few things I still can't figure out: * Is it possible to show procedure arguments and local variables? * Can I see source code that correspond to the current eip value? Or at least assembly? * Can I switch between different threads? * How about different stack frames? Perhaps answers to these questions are somewhere in `help` output or in man pages but I didn't managed to find them. So I would appreciate your help. -- Best regards, Eax Melanhovich http://eax.me/ From owner-freebsd-hackers@freebsd.org Sun Mar 6 23:41:33 2016 Return-Path: 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 B966BA95A02 for ; Sun, 6 Mar 2016 23:41:33 +0000 (UTC) (envelope-from mark@heily.com) Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8ED5BFB3 for ; Sun, 6 Mar 2016 23:41:33 +0000 (UTC) (envelope-from mark@heily.com) Received: by mail-ig0-x231.google.com with SMTP id vs8so14040098igb.1 for ; Sun, 06 Mar 2016 15:41:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heily-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-transfer-encoding; bh=Xraxj/uH1pjhmGiIM3juiBR0dB+0PmwDZSSY4Ss3Rhw=; b=frw/v953VxoFvgcZAuNhtjPb2w7WlEtHz6XDd8S90/gn1du2Zt/UymZOZtkIlAAFJ9 lshkikOjcxWK+7vVziYFPB5oqhj1ctDhvfM6GIiIHls9/eFLtTzeMIGfg5jIwmas1dl+ uQ7uUaj8b6my7Dwp+pZb6BaFx63sZDxlKb30qwAwZatw7FXkp90DQPAkoRaFHNIK57rX RA36P4+m3orxXx60bXK4VL8fwcQeE2KJXJRh8HIiqdaUg8yWCQc0KukWclh1iNzAQDrK iFRBoKV1S0EN0qQFTjQdTIEX4ggMeyLVgfbTePuBDddZhtgJZD+PKZnHJaIudTzBS87f bUvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=Xraxj/uH1pjhmGiIM3juiBR0dB+0PmwDZSSY4Ss3Rhw=; b=NlkhvS29HdaW/QV2crozm6NGS//sZgLBAyuPp8BF2mPjqbTe0i0TuJk8oLF7ixjmx0 yTzsksmFp3E1iS6A0+bq24adn2z0sliDUis3bjmepguZ4QNU+7A04reZW8Z+3z9JWJ/9 mRxdTIMMf47m3jnQkN02pMvhExwUozWs5e6K6fYuDLdr49Lidbaxb/KyPhvgX/XrWKC1 RBRfbfJi1SzerKTCkF0x5IuDj4qYL2HRLjOZUDfARDXILCYVnMAnQd7inyhaqNJe78A5 HniutrIEXyDkh9Aq00Lz9FuhWZyHdrfzErkn6Ms58/47qE5Mg7+1SxSD2M+u+hYR3qp8 AGLA== X-Gm-Message-State: AD7BkJIm8iltQZCb8hmJuYQFyZakzmaqrxjL1JcMlWRsMqil+YY9RRKlG7E/KHTEStNveT06T6QyHRHeSKxgrg== MIME-Version: 1.0 X-Received: by 10.50.67.148 with SMTP id n20mr9183389igt.37.1457307692845; Sun, 06 Mar 2016 15:41:32 -0800 (PST) Received: by 10.79.30.133 with HTTP; Sun, 6 Mar 2016 15:41:32 -0800 (PST) X-Originating-IP: [71.70.175.250] In-Reply-To: References: Date: Sun, 6 Mar 2016 18:41:32 -0500 Message-ID: Subject: Re: Looking for security-related intro project From: Mark Heily To: =?UTF-8?B?S2FtaWxhIFNvdcSNa292w6E=?= Cc: FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Mar 2016 23:41:33 -0000 On Sat, Mar 5, 2016 at 5:45 PM, Kamila Sou=C4=8Dkov=C3=A1 w= rote: > Hello, > > I am looking for a project that would help me get started with contributi= ng > to FreeBSD. I am most interested in something security-related.. > I'm working on relaunchd, which is a new service manager for FreeBSD (and other Unix-like systems such as Linux). I have put together some design notes for a security feature I'd like to add. This feature would allow you to create a "virtual private filesystem" for each daemon, which is a fancy way of saying that it populates a chroot(2) jail based on some configuration options. Take a look at this, and let me know if you are interested in working on it= : https://github.com/mheily/relaunchd/issues/35 From owner-freebsd-hackers@freebsd.org Mon Mar 7 11:35:55 2016 Return-Path: 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 59476AC29FB for ; Mon, 7 Mar 2016 11:35:55 +0000 (UTC) (envelope-from meenak1996@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 08601325 for ; Mon, 7 Mar 2016 11:35:54 +0000 (UTC) (envelope-from meenak1996@gmail.com) Received: by mail-wm0-x22d.google.com with SMTP id l68so104311374wml.0 for ; Mon, 07 Mar 2016 03:35:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=9ACG9M5iG0y3gQZGw+HxK9Duh4OmRW7cr9HPPd/cS/o=; b=b05FLNjs/tLWkOwrXmrRuT4jcd9k/QyBQJhOSs+cy4toyJLOutj/DqHXz52MDXga2L lw1heip6fbk/O4rLaVp7msUhNGC/FV58qSTiOABYub2ELUg/Km7o6Eh3NMeyFLizynoW 9OjohDYxnZKFwpT2ijD91IX2JwxFBbE0s0mbny3O76HDbFdpSayRfuT5X9gUh5qTaMge 2kQtMCIRu3M7VTkv2F8NPGyXouCi9LDKp/Hpd0TPzNi0LZkS2hokKEr+YTvERM2rZ4cI 98d8D6pZneK82Wexav1kRs2sspbAG6Z4uwY+YueYMU7+8g+9qE6hV3O5hKXKV8EXd/qT ufEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=9ACG9M5iG0y3gQZGw+HxK9Duh4OmRW7cr9HPPd/cS/o=; b=GSLD+MVsyB5Pq/FCppENHwmOusuI00s9aGxXv2euGpyX/jlOT2A29iIAQjRjCHGL8q voLLiapRvhR7365DugdCRdS6kXLzKBe3OvUs/IqkoulgLKGOHBnIYVVRceS0Egm1UmSi XH5JtYneyJ/y2TaEOL2hKM+ipNaowIpq/qF2+w83XKkFFg7oM3QLQbHckXDzaQIg4ZF9 llRtu9Di/mWTWap29pL/vjjLt0f9AoVLf9QS6zxkDHfbeNmkVV+34nLzbiHs8YgoFFgc pULWP66dD9hBEPeauBhu4nnuDzaHsXYh6YluD0eHIoUiyyrjv1MBkJBpA4Ddc1dovkVg 8Y/g== X-Gm-Message-State: AD7BkJIviD4tBA69cE8wX7u5LQXvt2zdyLtviGmUTG/5lGAashl3JJBi5/7boS5AhtUKo7K1mLzIMswyOtzM+w== MIME-Version: 1.0 X-Received: by 10.28.111.135 with SMTP id c7mr13356348wmi.46.1457350552903; Mon, 07 Mar 2016 03:35:52 -0800 (PST) Received: by 10.27.58.71 with HTTP; Mon, 7 Mar 2016 03:35:52 -0800 (PST) Date: Mon, 7 Mar 2016 17:05:52 +0530 Message-ID: Subject: Help From: Kamlesh Meena To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2016 11:35:55 -0000 Respected, I am new to this platform.Please guide me ,how to find mentor and what else to be done to get the project.I am very enthusiastic person in the field of computer science.In the past 1 year year I have learnt a lot which include c,c++,html,css,javascript ,bit of python and android development and have knowlegde about network system and also know many things relates to hacking stuffs which include scanning,footprinting,reverse engineering,mysql injection,spoofing and tools such as nmap(my favorite),john the ripper and metasploit(meterpreter). I dont want to loose the project as I am very energetic about it.So please someone guide me how to find a mentor and from where. Thanking you, Yours faithfully Kamlesh Kumar Meena 7755047785 From owner-freebsd-hackers@freebsd.org Mon Mar 7 13:47:24 2016 Return-Path: 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 EF77DAB9581; Mon, 7 Mar 2016 13:47:24 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::107]) by mx1.freebsd.org (Postfix) with ESMTP id C143FB76; Mon, 7 Mar 2016 13:47:24 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [IPv6:2001:470:1f11:617:8fe:6a13:797b:e9c9] (unknown [IPv6:2001:470:1f11:617:8fe:6a13:797b:e9c9]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 0A83A1F8E; Mon, 7 Mar 2016 13:47:23 +0000 (UTC) Subject: Librem 13 laptop initial report, issues to fix From: Eric McCorkle X-Mailer: iPad Mail (13D15) Message-Id: <43EB3527-B41B-4618-B7DF-25597CE1C214@metricspace.net> Date: Mon, 7 Mar 2016 08:47:22 -0500 To: freebsd-mobile@freebsd.org, "freebsd-hackers@freebsd.org" Mime-Version: 1.0 (1.0) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2016 13:47:25 -0000 Hello all, I have obtained one of the Librem 13 laptops (https://www.crowdsupply.com/pu= rism/librem-13), and have begun the process is setting up FreeBSD on it. He= re is an initial report of my findings, including the issues I've had. Sinc= e the hardware was chosen for things like open specifications, available for= are source, etc, I'm optimistic about getting all these addressed. The following devices Just Work(tm): * EFI boot/loader (with a pure ZFS system) * SD card reader * Realtek Ethernet (re) * SMBus (ichsmb) * coretemp and cpufreq * Intel HDA (speaker-test works with speakers and headphone jack, haven't te= sted recording yet) * Hard drive and SSD (I have ZFS with main storage on the drive, and swap, Z= FS cache, and a small intent log on the SSD) * USB ports * Bluetooth (though I seem to have disabled it in the latest kernel config b= y accident) * The keyboard fn keys actually work fine, which is the first time I've seen= that. This laptop also features hard-disconnect switches for the camera (a USB dev= ice). I've tested booting with them in various configuration, as well as fl= ipping them on/off. FreeBSD seems to handle this fairly well, however it co= mplains loudly about timeouts before disconnecting the bus. I wonder if the= re might me some setting to say "treat this bus as a hot-pluggable periphera= l" I tried Jean-Sebastian's Intel KMS patch, but it doesn't support the broadwe= ll cards. I have the following issues: * Atheros 9462 wireless card is detected, but the radio doesn't seem to work= . pciconf reports a few errors: receiver error, bad tlp, bad dllp. Just to= rule something like a bad solder, I'm going to try booting up a Linux memst= ick and see what happens. * Blank screen on resume, everything else is fine. This resembles an issue I= had with a Lenovo. I did some initial poking around, and acpi debugging tr= aces reveal some execution errors during the resume process. I will get a m= ore complete report to post to freebsd-acpi. * Sporadic boot-hang, USB timeouts. This seems to be dependent on kernel co= nfiguration. It happens for some configs, not for others, and turning on ve= rbose boot seems to stop it. Based on this, I strongly suspect a timing-rel= ated bug somewhere in the boot process. * VESA weirdness with X. Running X with the VESA driver starts and displays= fine, but when you switch back to a terminal, a few pixels around the borde= r of the X screen still show up in the terminal. Also, when shutting down X= , it hangs and the screen becomes unresponsive. This seemingly implicates t= he vga bios; fortunately, this can probably be fixed due to the nature of th= e Librem project. The blank screen on suspend is probably the most critical, with the Atheros c= ard issue being a close second. If anyone has suggestions about where to lo= ok/how to diagnose, I'd certainly appreciate them. I will also be in contac= t with the Librem developers after I do more diagnosis. Additionally, there are some things I want to look in to once everything is w= orking: * The laptop bios allows for custom signing keys to be configured. This set= s the stage for a secure boot process. * See if anything can be done (or needs to be done) in order to better suppo= rt the hard-off switches. They seem to work (for the camera/mic; can't tell= yet about the wireless), but complain to dmesg about timeouts when switched= off. See if some config exists/can be added to make them detachable.= From owner-freebsd-hackers@freebsd.org Tue Mar 8 00:54:59 2016 Return-Path: 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 ABAB9AC718D for ; Tue, 8 Mar 2016 00:54:59 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: from quine.pinyon.org (quine.pinyon.org [65.101.5.249]) (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 805609C8 for ; Tue, 8 Mar 2016 00:54:59 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: by quine.pinyon.org (Postfix, from userid 122) id 0743416027F; Mon, 7 Mar 2016 17:48:29 -0700 (MST) X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on quine.pinyon.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 Received: from feyerabend.n1.pinyon.org (h5.esturion.net [65.101.5.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by quine.pinyon.org (Postfix) with ESMTPSA id 386FA160044 for ; Mon, 7 Mar 2016 17:48:27 -0700 (MST) To: freebsd-hackers@freebsd.org From: "Russell L. Carter" Subject: libcapsicum, casperd, pdfork and friends in 10/stable? Message-ID: <56DE215A.60802@pinyon.org> Date: Mon, 7 Mar 2016 17:48:26 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2016 00:54:59 -0000 Greetings, I'm interested in using the capsicum framework, but I don't see all the bits available for my 10/stable system. Is it only fully implemented in -current? Thanks, Russell From owner-freebsd-hackers@freebsd.org Tue Mar 8 08:04:18 2016 Return-Path: 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 963EFAC3A77 for ; Tue, 8 Mar 2016 08:04:18 +0000 (UTC) (envelope-from bharghav2947@gmail.com) Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::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 22B42D4A for ; Tue, 8 Mar 2016 08:04:18 +0000 (UTC) (envelope-from bharghav2947@gmail.com) Received: by mail-lb0-x229.google.com with SMTP id bc4so8468651lbc.2 for ; Tue, 08 Mar 2016 00:04:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=FT9VZ8WvafdKz+CoNDZthQFsEQtFo7fdUVb7P7mOpfY=; b=IAVfcbQsh/uAYq46mV1RD5zYGPf/fb/kkOtloEdbMm9nC7NYFctxEV2TaUcLAzTEJR KWLBJWGLOygwdh90Oo47kswBB8/OHtlwX7kU6JaA9na++yuS9TpxF6NQrZZ8AQVzp4/b hgblNnpC9BPvUKLBh54uuPPNOeJDu6TirdC4DBRnK61ARHbGGf0or6lCQwbYUGNUm2cA /Ipwz4sFyAXLjUBhUghYMuj8dEVoLYB9FrnNlKLuD7NAo4+zJmV3pJT6h2emiXAVbsRE PORksNJYwjKS9D5I2cNiBwB26iGcHskxUcMgGQ08EBQjwSGs5VhgvJ9+PCXA2OYPR9si T/dw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=FT9VZ8WvafdKz+CoNDZthQFsEQtFo7fdUVb7P7mOpfY=; b=VOb/Ory1nfg/G6VAGkiP7H7XyqUaA9k+37D8icZi0ECb5AW2jdCl5wlh6nefEDxAHf s9ghsuRtGBNTNj0ZyIYejYTCQonlmDTzcPBfY8JLmjgbFGrAjzmfVvINLvOl+W57OJTw Xs5Si7YRZkzGnQ5GWdl0R+LqQSzSl/wkdKXIibhMyUAghZEFr9nbDpH0Wf19F8hPAFML tGe5X8TSU3FHR7YLioERv3166lcgXuR4onOq7eBH4r2M/h2CudC5+Wf+2dzmbkwioWKH GVtN7SBgqMmMCEuWbO8eQYwFL8tULHD7AqxeKFeB1Mx+5RmLncrDHG1Kl4GYru0ndOl4 l/fQ== X-Gm-Message-State: AD7BkJJE3lB15sKm0Q+67diCoTZicsWvS4AyvspZW7xiqmtv0iEGUKBET/ow4nXH+CizsJoF+fJY21o9x3ot1A== MIME-Version: 1.0 X-Received: by 10.25.154.14 with SMTP id c14mr9725285lfe.35.1457424256338; Tue, 08 Mar 2016 00:04:16 -0800 (PST) Received: by 10.25.196.131 with HTTP; Tue, 8 Mar 2016 00:04:16 -0800 (PST) Date: Tue, 8 Mar 2016 13:34:16 +0530 Message-ID: Subject: Implementing KDBus with Capsicum integration in FreeBSD From: pavan teja To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2016 08:04:18 -0000 Hello everyone, Express your view about adding capabilities sharing among processes by implementing something similar to KDBUS in FreeBSD . Sicne KDBUS supports most of the data structures in Linux adding capabilities to share among processes by using capsicum .Please let me know what you feel . Thank you. From owner-freebsd-hackers@freebsd.org Tue Mar 8 08:40:17 2016 Return-Path: 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 2F1EDAC19DC for ; Tue, 8 Mar 2016 08:40:17 +0000 (UTC) (envelope-from rumpelsepp@sevenbyte.org) Received: from mail.sevenbyte.org (mail.sevenbyte.org [5.9.90.188]) (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 EEC68418 for ; Tue, 8 Mar 2016 08:40:16 +0000 (UTC) (envelope-from rumpelsepp@sevenbyte.org) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.sevenbyte.org (Postfix) with ESMTP id E5AC41260715 for ; Tue, 8 Mar 2016 09:22:43 +0100 (CET) X-Virus-Scanned: amavisd-new at sevenbyte.org Received: from mail.sevenbyte.org ([127.0.0.1]) by localhost (mail.sevenbyte.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aN0e0-fgwTtF for ; Tue, 8 Mar 2016 09:22:42 +0100 (CET) Subject: Re: Implementing KDBus with Capsicum integration in FreeBSD To: freebsd-hackers@freebsd.org References: From: Stefan Tatschner Message-ID: <56DE8BD2.4060301@sevenbyte.org> Date: Tue, 8 Mar 2016 09:22:42 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2016 08:40:17 -0000 On 08.03.2016 09:04, pavan teja wrote: > Hello everyone, > Express your view about adding capabilities sharing > among processes by implementing something similar to KDBUS in FreeBSD . > Sicne KDBUS supports most of the data structures in Linux adding > capabilities to share among processes by using capsicum .Please let me know > what you feel . kdbus is unmaintained and the developers stepped back to the drawing board. AFAIK kdbus is being reworked and redesigned; [1, 2] Stefan [1]: http://www.phoronix.com/scan.php?page=news_item&px=KDBUS-Back-To-Design [2]: https://www.phoronix.com/scan.php?page=news_item&px=BUS1-In-Development From owner-freebsd-hackers@freebsd.org Tue Mar 8 11:38:32 2016 Return-Path: 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 2396EAC70C3 for ; Tue, 8 Mar 2016 11:38:32 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 75762A8F for ; Tue, 8 Mar 2016 11:38:31 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA05636 for ; Tue, 08 Mar 2016 13:38:29 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1adFy9-0005vt-Hy for freebsd-hackers@FreeBSD.org; Tue, 08 Mar 2016 13:38:29 +0200 To: FreeBSD Hackers From: Andriy Gapon Subject: hpet as nmi watchdog X-Enigmail-Draft-Status: N1110 Message-ID: <56DEB97D.2010804@FreeBSD.org> Date: Tue, 8 Mar 2016 13:37:33 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2016 11:38:32 -0000 I toyed a little bit with an idea of using a HPET timer as an NMI watchdog. The idea is that a HPET timer is somehow configured to generate an NMI when it fires. The timer normally would not fire, of course, as it is constantly being reprogrammed to some future time as is the case for all watchdogs. I have written some proof of concept code using two approaches. One approach is to use the "FSB" (MSI-like) mode of a HPET timer and program a corresponding FSB data register (HPET_TIMER_FSB_VAL) with a value that sets NMI delivery mode using the IO-APIC specification. The other approach is to use legacy interrupt mode for the HPET timer and program a corresponding IO-APIC pin for NMI deliver mode. In both cases I haven't got a desired result - instead of an NMI a test system gets reset when the timer fires. I wonder if this is a quirk of my old hardware (HPET in AMD SB7xx, family 10h processor) or if my idea is a non-starter. Thoughts, suggestions?.. Thanks! -- Andriy Gapon From owner-freebsd-hackers@freebsd.org Tue Mar 8 15:14:13 2016 Return-Path: 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 88584AC7968 for ; Tue, 8 Mar 2016 15:14:13 +0000 (UTC) (envelope-from fanyuiharisu@gmail.com) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (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 56E8F96B for ; Tue, 8 Mar 2016 15:14:13 +0000 (UTC) (envelope-from fanyuiharisu@gmail.com) Received: by mail-io0-x22c.google.com with SMTP id z76so29351298iof.3 for ; Tue, 08 Mar 2016 07:14:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=gz+BbSYpdifZqy0UF06xPW2jGpSWxosi0N69lexkB3Q=; b=AVMe5/a25/EadFAhoJw784Lfk6ukanwPyn4kH+aMIrDbIGUKMbT6amHHajRPf/FWXQ gY5R7gD83Hcu2F7uyECB/wYvMm9Dsi9PrB+CuWjaMN5LsbQp604vpu4NrOH1pMr0atZD TC9FqcSsmDu8TvQ1cE2ydmtVPx+scqCxlV9tJEkCk2LetFvVk0THM7uwpD6DfkKPMPyt Y0gt/gI/9snG4j2IwRb1pj0J789W3QEGxzZKHkEcnUnNtNN4IohMLrUERZt/EPl+dgD1 aWYcjoOuOtaGI74ltTuSU4YKytVYcqy+XGfThvCH8Z458mI4W6AgpcXhxaG4+sPs4fty JmHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=gz+BbSYpdifZqy0UF06xPW2jGpSWxosi0N69lexkB3Q=; b=Ird6th5xxmmriXFStdJYnzOqeL1ZcgNWbUI2L4iDkpwCSfDzIwb2H+Mzg/XG62GBZA yza5aKPj4ommcgCAyCLOtpSMfpLi+F7hRfdSYdMfI/Iv8V+91zK4ah3fcun7T8OSkRwC 9o539ZLieSPFv0r+gHZmXClRumlQXtaJukXwQrrdLzAXlEogdjTVVPzwv2Bg2bBtCyTt LWBOiSZ+teqEyYicDCx02pI7SX4CHzO+Nlc7lgZ+m+SU8jQRidR54v4Wp0AR9ApuLsZu fnZccrocBneCnxVJtMIUV06WblaO1Rgjbe+TnCkPX2+u42vpw0GHIldSUeFPGKX69hx2 oBbg== X-Gm-Message-State: AD7BkJK7yQXflRT3HW4lpz2jKwdOghE1eLeh8f2jNalMZluW0+EmOgWcpFNaGN5idSKB0buTdba6yT/6s/HDYA== MIME-Version: 1.0 X-Received: by 10.107.3.16 with SMTP id 16mr5694243iod.155.1457450052631; Tue, 08 Mar 2016 07:14:12 -0800 (PST) Received: by 10.107.183.13 with HTTP; Tue, 8 Mar 2016 07:14:12 -0800 (PST) Date: Tue, 8 Mar 2016 16:14:12 +0100 Message-ID: Subject: GSOC 2016 project suggestion From: Harisu fanyui To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2016 15:14:13 -0000 hello developers, i am a computer engineering student from the university of buea in cameroon. i am interested and wish to participate in gsoc on the project Unified ping and ping6 i have read the wiki page but it is not providing me with all the information i need, can someone help me with a more specific way on how to go about? From owner-freebsd-hackers@freebsd.org Tue Mar 8 16:42:31 2016 Return-Path: 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 C196DAC898A for ; Tue, 8 Mar 2016 16:42:31 +0000 (UTC) (envelope-from rank1seeker@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 A5890D7A for ; Tue, 8 Mar 2016 16:42:31 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id A090AAC8989; Tue, 8 Mar 2016 16:42:31 +0000 (UTC) Delivered-To: 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 A02A7AC8988 for ; Tue, 8 Mar 2016 16:42:31 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3CD4AD76 for ; Tue, 8 Mar 2016 16:42:31 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: by mail-wm0-x231.google.com with SMTP id p65so35649811wmp.0 for ; Tue, 08 Mar 2016 08:42:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:mime-version :content-transfer-encoding; bh=+Pfkd1+GSOUjh7P2n/Eq5nGoEual8W2FIrybA5NPars=; b=I/BWXUKXJaHvnzWnDtR6MOvCpR9H3mYKVkWpPLksxE9dVsqmS/TDjlZfrGpRWuZjKm OeqPxx6y3BH09NjEil53SL/rGGzWekJME+SeR0CSlhiwCAKu7OmY6E3kVJ+1APeQe44F Q/IC2zo2BLEc2f2iGRyOZeQsgutftrWooWVsqOSioOtnG0ddzpZDVy/ipksE+V6bM6um a3Klux2/H3FGV859FTCp083jel9lYzWwoZt1nbk6IQ2rMtI5/rVIVfHyjYUb879Tb15q 5lIsAup0GFDPyWlllyIvApZJ/dnJmo4F7P5493eYpJESrCfOEVsKZAB2r52jGtnjvWz9 oFIA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-transfer-encoding; bh=+Pfkd1+GSOUjh7P2n/Eq5nGoEual8W2FIrybA5NPars=; b=Pcg/UlxffJxWI1WocjiLeWqHAyEwECJKtkJaGOfXBdwUBLIly307kSnYyClOZh4ES2 aNBG/8oA8wQ1f2b08dPYsl9BG7V/kv7UXFGz75j/8cPBhbhjgD2ruK96lhNOUYhpB0Cu oLOOjFoytE4ihyRH1cjskbhKL3JAMLaxa1vZobitu+v11UCkMXbZ2kCFfDxdCNO3L0PU AAiLYKiTHFr6n/ijdEeOI7s4JGbTfSpasVdM3PQEmQKT2IJU4SUlGKeACe3tMPrTf6Fr zP5boJCsOZEgBBvTLiR2Q05fDfGvN4hZMDIUW4o1A3QtTdlt2uvUDqTTARl5SXvi0tKq F1iQ== X-Gm-Message-State: AD7BkJJZaxqbpK7U4+kmc7BsvqmNmK10Uf4yd3IQb4xjy1owIGal468iSDY5yp6t7lsh+A== X-Received: by 10.28.180.84 with SMTP id d81mr21614696wmf.42.1457455349776; Tue, 08 Mar 2016 08:42:29 -0800 (PST) Received: from localhost (cpe-94-253-187-91.zg.cable.xnet.hr. [94.253.187.91]) by smtp.gmail.com with ESMTPSA id hx10sm3765311wjb.25.2016.03.08.08.42.29 for (version=TLSv1/SSLv3 cipher=OTHER); Tue, 08 Mar 2016 08:42:29 -0800 (PST) Date: Tue, 8 Mar 2016 17:41:51 +0100 From: To: hackers@freebsd.org Subject: Missing sec advisories Message-ID: <20160308174151.00002aa5@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2016 16:42:31 -0000 10-REL, for 20160303 p13 FreeBSD-SA-16:12.openssl, why is there no https://www.freebsd.org/security/advisories/FreeBSD-SA-16:12.openssl.asc And even when there is one for a patch, it becomes available sometimes even after half of day, after patch has been released. Domagoj From owner-freebsd-hackers@freebsd.org Tue Mar 8 17:05:46 2016 Return-Path: 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 5418DAC73CB for ; Tue, 8 Mar 2016 17:05:46 +0000 (UTC) (envelope-from vineetp@iitk.ac.in) Received: from mail2.iitk.ac.in (mail2.iitk.ac.in [202.3.77.186]) by mx1.freebsd.org (Postfix) with ESMTP id 6AAB63B9 for ; Tue, 8 Mar 2016 17:05:44 +0000 (UTC) (envelope-from vineetp@iitk.ac.in) Received: from mmtp.iitk.ac.in (mmtp.iitk.ac.in [172.31.1.23]) by mail2.iitk.ac.in (Postfix) with ESMTP id D46BF1000204 for ; Tue, 8 Mar 2016 22:29:47 +0530 (IST) Received: from mail-ob0-f169.google.com (mail-ob0-f169.google.com [209.85.214.169]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: vineetp) by mmtp.iitk.ac.in (Postfix) with ESMTPSA id 09E554A for ; Tue, 8 Mar 2016 22:29:47 +0530 (IST) Received: by mail-ob0-f169.google.com with SMTP id fp4so19848074obb.2 for ; Tue, 08 Mar 2016 08:59:46 -0800 (PST) X-Gm-Message-State: AD7BkJJ4gqqYFpdxsgwQWPnNArd48A7HzlSxFPhfHnLO7mTcd3oobl9fAlNd/y/Uc7FbWu5SM6jS/cwE513KIg== MIME-Version: 1.0 X-Received: by 10.182.250.169 with SMTP id zd9mr18107950obc.59.1457456383216; Tue, 08 Mar 2016 08:59:43 -0800 (PST) Received: by 10.182.105.202 with HTTP; Tue, 8 Mar 2016 08:59:43 -0800 (PST) Date: Tue, 8 Mar 2016 22:29:43 +0530 X-Gmail-Original-Message-ID: Message-ID: Subject: Greetings FreeBSD Community : GSOC Queries From: Vineet Purswani To: freebsd-hackers@freebsd.org X-Mailman-Approved-At: Tue, 08 Mar 2016 19:14:17 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2016 17:05:46 -0000 Greetings FreeBSD Community, My name is Vineet Purswani and I am a fourth year Computer Science MTech Integrated student at IIT Kanpur, India. I am interested in knowing more about a project listed on FreeBSD GSOC ideas page - *Linux to BSM Conversion Tool* I have a great interest in Computer Systems, specifically operating systems, computer architecture and cloud computing. I did a project on compiler design, wherein I developed a Java compiler in python using PLY library. I have worked on NACHOS to test some of the scheduling algorithms, demand paging techniques, implemented condition variables and semaphores. I did an architecture project to get my hands on over cache hierarchy techniques and branch & target predictors. I am currently working on computer security projects, wherein I have done control hijacking, privilege separation, learnt about several symbolic execution techniques like DART, KLEE & EXE. I have a basic knowledge of compiler design, databases, functional programming, machine learning and computer security as well. You can find my work here: https://github.com/vineetpurswani *Kindly guide me as to how do I start working on this idea? Which bug fix/enhancement should I work on? Expectations in proposal?* Kindly share any details that you would like to share or any questions that you may have for me regarding this GSOC project. Let me know what you think. Thanks a lot. Yours Sincerely Vineet Purswani IIT Kanpur From owner-freebsd-hackers@freebsd.org Wed Mar 9 08:06:52 2016 Return-Path: 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 936549DB352 for ; Wed, 9 Mar 2016 08:06:52 +0000 (UTC) (envelope-from sgeos@hotmail.com) Received: from BAY004-OMC2S17.hotmail.com (bay004-omc2s17.hotmail.com [65.54.190.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6D11DC7E for ; Wed, 9 Mar 2016 08:06:52 +0000 (UTC) (envelope-from sgeos@hotmail.com) Received: from BAY182-W44 ([65.54.190.125]) by BAY004-OMC2S17.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Wed, 9 Mar 2016 00:06:46 -0800 X-TMN: [peCkuhjUaIjej3Zx6Y23cYYJ58a8dqAX] X-Originating-Email: [sgeos@hotmail.com] Message-ID: From: Brendan Sechter To: "freebsd-hackers@freebsd.org" Subject: FreeBSD sh on Linux? Date: Wed, 9 Mar 2016 17:06:45 +0900 Importance: Normal Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 09 Mar 2016 08:06:46.0658 (UTC) FILETIME=[A01D9620:01D179DA] X-Mailman-Approved-At: Wed, 09 Mar 2016 13:11:28 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2016 08:06:52 -0000 Is there any reason why FreeBSD sh can't be used on Linux? =A0dash is not a= suitable login shell and bash is GNU. = From owner-freebsd-hackers@freebsd.org Wed Mar 9 13:13:49 2016 Return-Path: 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 3EDEEAC82A1 for ; Wed, 9 Mar 2016 13:13:49 +0000 (UTC) (envelope-from jhellenthal@dataix.net) 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 072AFBE7 for ; Wed, 9 Mar 2016 13:13:49 +0000 (UTC) (envelope-from jhellenthal@dataix.net) Received: by mail-yw0-x234.google.com with SMTP id d65so38997745ywb.0 for ; Wed, 09 Mar 2016 05:13:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dataix.net; s=rsa; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=J4W0KDVivsZVJDnAVNsqdiLx/URaSmLGFdDCPIaGys0=; b=DVBISnd3W+xtCxX3+Bvutjsh3cKg7gjPdYFvceK1ofNbblSL8LBZHxgKazuwOzttOp 8xKEFSGkduD3k3X0CvKi4IOW8dWivF882Kd/oQ6miiFt3pka1ggGEjTaelQP4nmHF/MT uc3CyHqRQKjqUD6iE3mXMHw6jF/ThtvUtohJM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=J4W0KDVivsZVJDnAVNsqdiLx/URaSmLGFdDCPIaGys0=; b=K5L/Gaz0+4TIWV4MnR7zydxuCkPoB9igdf5JqqQ845Rs9RNPjFNzuCQD7lA9F7uYHl UIN9Pw+Y6MLZAaZf7f5RUOu39oXcKwuKNkQmdHz7dSbifEM6t58ej1CrH7sYhDH0guh8 1YNSuilK/nThrInopmxFd188PMetRB4aQqU5R+Z/oqZpwiN57KFCjdedD57ssXT0ZyaV DezMqlezR8cNM8ZPFjlSH97vmpVr6GDKaeKkIMCO3ZkQtzjqSQUZ1gDUC8StjPaHh/A3 /06rP11uCL/Oi0nj33hYaog1taT33T14EkKp98L3T+7WbInj7ufLf99+zat6fazRMCmf Mq8g== X-Gm-Message-State: AD7BkJLpVp9PbpJu0mAKHGcF8JY+9qwptfmMd++S8I1IZZbn0xZ9x6Dxl/YldPP5TvlDEw== X-Received: by 10.129.86.8 with SMTP id k8mr18151526ywb.286.1457529228242; Wed, 09 Mar 2016 05:13:48 -0800 (PST) Received: from [10.31.32.14] ([108.68.81.103]) by smtp.gmail.com with ESMTPSA id c67sm4728906ywb.41.2016.03.09.05.13.47 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 09 Mar 2016 05:13:47 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: FreeBSD sh on Linux? From: Jason Hellenthal X-Mailer: iPhone Mail (13D15) In-Reply-To: Date: Wed, 9 Mar 2016 07:13:47 -0600 Cc: "freebsd-hackers@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <8EC0DC6F-FA0D-4B8D-AECE-F1F797EE4D56@dataix.net> References: To: Brendan Sechter X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2016 13:13:49 -0000 It's just the ash(1) shell with a few modifications that's a little more sta= ndard than most. Shouldn't be any reason why it can't=20 --=20 Jason Hellenthal JJH48-ARIN On Mar 9, 2016, at 02:06, Brendan Sechter wrote: Is there any reason why FreeBSD sh can't be used on Linux? dash is not a su= itable login shell and bash is GNU. =20 _______________________________________________ freebsd-hackers@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@freebsd.org Wed Mar 9 13:27:26 2016 Return-Path: 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 19A3AAC89E2 for ; Wed, 9 Mar 2016 13:27:26 +0000 (UTC) (envelope-from cbergstrom@pathscale.com) Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (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 D5BE6204 for ; Wed, 9 Mar 2016 13:27:25 +0000 (UTC) (envelope-from cbergstrom@pathscale.com) Received: by mail-oi0-x22c.google.com with SMTP id m82so35000518oif.1 for ; Wed, 09 Mar 2016 05:27:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pathscale-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=sTy4h3k75Ae1c15hTKGjn6NfyEN5K5m6WVoandgy6ao=; b=PsV3erdhg6JeDO04f3p6Jwjr72NgMDs2JnSkU+nF7vw1yWg+kNHN6sDzDDAJjFio95 vVZc7Vf/CZC+gPnf7sP0luKXptY1S7d8yZs7+DRohXRntJMGHJ5HseopCSSKKnYZDSgA MxU5oPXEi8DNVX+8tH3udKxgJuzF1/JUr3uaMKSwGARYt2dmuA5hn2dSwmtPuh4hi4Lc damhm9GiErS49NwVtQSlgZTg7JsjqkamhLdnuEU1LbMHkVtkDfMjnO7ZrkJM2GNpFlWc OzlQIwtc97dd3A7mtGc+6LVvF2Hf1wL7Paaxi2JYLJgtf+LfsFqFvbdds1lctRSJwczs zAbQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=sTy4h3k75Ae1c15hTKGjn6NfyEN5K5m6WVoandgy6ao=; b=EFoX1FFuWmcjlJBy1C8YwbobXHJBOqHzJqZrINN6TtaGGlOdlh/mzVHfv2ldBKTbOP F6BRrJAm775JEHQIymJBZr1+EQeU2pX59DxdPaJrDUca+TOxz75+yL5mnzT3MpVoA5wn I192gzX0UQfezGnx/+H344WXZiMJxaFPvu5YtZHXHDrz063hrTV9xTMpD6+jK2A2JZjX AxAlYS0HEv3PaQCDag74ib2ksimCTROj0DvQEd7OidPX5tcthnjQTQMDLnCvUERP5iSU CNdy0BdJzCYahkzB10Pvas5lCBf+n14N/2eXwhSBGu/bc7TrhPsD4Itm1epgCvgyoS+E S7yw== X-Gm-Message-State: AD7BkJIC/X0pnpLUjjw0uMcIul1LThfsqt07yzZL7IGTfxfmjIPeyHjKdTaQWABAdcr7gELzFc7RXWhqi5nqDA== X-Received: by 10.202.64.132 with SMTP id n126mr16337758oia.80.1457530045096; Wed, 09 Mar 2016 05:27:25 -0800 (PST) MIME-Version: 1.0 Received: by 10.202.94.135 with HTTP; Wed, 9 Mar 2016 05:27:05 -0800 (PST) X-Originating-IP: [118.200.139.84] In-Reply-To: <8EC0DC6F-FA0D-4B8D-AECE-F1F797EE4D56@dataix.net> References: <8EC0DC6F-FA0D-4B8D-AECE-F1F797EE4D56@dataix.net> From: =?UTF-8?B?QyBCZXJnc3Ryw7Zt?= Date: Wed, 9 Mar 2016 20:27:05 +0700 Message-ID: Subject: Re: FreeBSD sh on Linux? To: Jason Hellenthal Cc: Brendan Sechter , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2016 13:27:26 -0000 /* not meaning to be a troll */ If you're going down this route - there's also ksh93 from solaris, which may be easy to extract (or maybe has done so already.. not sure) in my experience it's that nice balance between bare minimum sh and bash. There's also fish and zsh if you want tons of features.. On Wed, Mar 9, 2016 at 8:13 PM, Jason Hellenthal wrote: > It's just the ash(1) shell with a few modifications that's a little more standard than most. Shouldn't be any reason why it can't > > -- > Jason Hellenthal > JJH48-ARIN > > On Mar 9, 2016, at 02:06, Brendan Sechter wrote: > > Is there any reason why FreeBSD sh can't be used on Linux? dash is not a suitable login shell and bash is GNU. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@freebsd.org Wed Mar 9 15:17:16 2016 Return-Path: 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 AE6B6AC8A42 for ; Wed, 9 Mar 2016 15:17:16 +0000 (UTC) (envelope-from vbatts@gmail.com) Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::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 76866795 for ; Wed, 9 Mar 2016 15:17:16 +0000 (UTC) (envelope-from vbatts@gmail.com) Received: by mail-ob0-x230.google.com with SMTP id ts10so49697723obc.1 for ; Wed, 09 Mar 2016 07:17:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to; bh=pyhMJmq76Vyzs8wdiq9DDqW5LEX3bo1KxhNb3hVL0qo=; b=I8Ph8WZbYSPcWjwbbisw3X4ZVWgCgJAbEBesqjptZrrxbm4nav1e7/oZwQE0YXuGHf 9lZ9McPAK9CsZ984gvFdeZpy+nlBLHVPWdocIxPThyNg+Lpjd/rQL9/Gu7RYVnyFllz4 V9zN3DrFlz/N1ki9mah3DtepE9tIt+qXNTqrJ5WBr/Jgk4m+DcrzFcsE70PQXUhlDweV PPBe3I64dbOjiDeoljU7cbgXEFFumJrWHaW0Y1N302G6m4djJbye2H+U39KrAvTejjj2 urkgpBIo1r6sOmT6jdbhBivHc3SxdVJbNN03N9ff0lyf6O2tR2OdxfSgfYE6C4AqRxEa zs/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to; bh=pyhMJmq76Vyzs8wdiq9DDqW5LEX3bo1KxhNb3hVL0qo=; b=kgW3FrtChaNKYnb+PuDYwF7QjAKgeoSM778ebs8H5hoXncdQNdFWzr+S9P11qZq2iP GUdF+MLa8B6bmJ+tXkZbT9gEXbgE/okzPCcrbPNu9xMoH/kT3rXDG6TJBkqFOpvBnAur /KX3G3YENuNW3BbxSQ3mAyPcaDOppjnRFGKQmVZKfRDUF2TSMxbSh+5JM06NGPLbJYJE wpFOnv+wazpVIsCzXrivmJ6kw6hub/0L/iDkjxXOt2fBrPL7HMpFVfeeeXVZOrvL+vpE zBnOkvt8/FW89kIXsmkTDCkqstSB6ZcBl7QnVcFPOhSK1bK/3UbIBDQPPwHmWkpkCAMO M55A== X-Gm-Message-State: AD7BkJKqLQV3jGdI8KUoM54+gvGes1Iq40z6k/T6WMC2hzokXNkPGlCUwV/zYT2D+fLRMBzwQtuEvHT1YSJx4A== MIME-Version: 1.0 X-Received: by 10.60.96.164 with SMTP id dt4mr20640137oeb.74.1457536635768; Wed, 09 Mar 2016 07:17:15 -0800 (PST) Sender: vbatts@gmail.com Received: by 10.182.109.228 with HTTP; Wed, 9 Mar 2016 07:17:15 -0800 (PST) In-Reply-To: References: Date: Wed, 9 Mar 2016 10:17:15 -0500 X-Google-Sender-Auth: COdvbBTjdx7kokw7SA6Q5rFsGrY Message-ID: Subject: Fwd: [RFE] mtree support for extattr? From: Vincent Batts To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2016 15:17:16 -0000 Hello all, This is a first post from me. The `mtree` utility (./contrib/mtree/) and the specs that it produces and validates has found it's way into projects that I am involved in. While the projects are initially very Linux focused, they are not limited to such. There is an mtree-port that has been started for Linux, but is not widely packaged yet. Also, libarchive has support for parsing and creating mtree specs. On most Linux filesystems, extend attributes are used commonly for storing ACLs, capabilities, etc. These attributes are something that most definitely would be interesting keywords to include in the spec of a directory hierarchy. >From my researching, it seems that extattr support for mtree on freebsd is not present, while the sys/extattr.h and UFS could support it. It seems this is a valuable feature to add and would be widely useful. Some of the mechanics would be interesting to handle the collation of the extattr data into the keywords for files in the mtree spec. As the key/values are namespaced, perhaps the mtree keyword would use the namespace.key and prefix it with 'extattr.' or 'xattr' or similar. Such that the entry in the mtree spec looks like ``` my.file \ mode=0644 size=24542 time=1455996582.000000000 \ extattr.system.mykey=myvalue \ sha512digest=f758e6d04b527cc024aa70ffaaa75b4899429498d246f41a057753dc51b7d49e0f6b512c1f1920435585067209863c529b2038101ce0576138c7eee7ca359b7c ``` Some issues that I have with this is the information leak of the values of the extended attributes. Also, on Linux xattrs are expected to be ascii strings, it is not uncommon to find binary content in the value. For these two cases, it seems nicer to just include a checksum of the value of each extended attribute. This then requires an election to which hash to use for the checksum digest. I look forward to your response and next steps! vb From owner-freebsd-hackers@freebsd.org Wed Mar 9 15:40:11 2016 Return-Path: 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 91C39AC9484; Wed, 9 Mar 2016 15:40:11 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 545FE902; Wed, 9 Mar 2016 15:40:11 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: by mail-qk0-x235.google.com with SMTP id o6so21705475qkc.2; Wed, 09 Mar 2016 07:40:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=CDNYtEYos3+shpYJnve+43wPKUemR2zLKtjwFAIgXXU=; b=Br8lJ65ozuPVSi7uvKR6uQfux0nXhSr3LQfX1rkxRHuIRxqRN4nSpU07G3Ni4ujXIt wphcTSWXKlNNGIf/HnOennKfPdXPNxWCzAfngFBC5OzDMHGi1E7r+xsVsMFHhhhsy5TG qQZQJlfneA11vY8DeyBtez7SfKuENzXP8rbPeSIVQggJqWMGH7RCihADiSENJGqxxEMR sZ58dpxn5GRlrvPmQndbbu1/Mbp5D643b2HCO3Pdm3m1w+g1mpXrpBrIvr9/XXjwhIrY hh0LOJrkiRzOaWeeRRIaPf4qTXcpMm3Y+oFysil8RqCZVXUYAKQlR4VHhNHISV8udhCv ntvg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=CDNYtEYos3+shpYJnve+43wPKUemR2zLKtjwFAIgXXU=; b=EQRTEh/SYSyIcsuPnnk9GSYINBZZq0IOhGD4FE8JqyYH6UrA5wiuqor3yBrZSeod/0 ku37ehzpzGeBgy1psgW07LGlAA9h2Pvh57SigltseCXM49lps7O4jjOFf+BzxJ36z1II nEGRpKp8W5YM8tKPqb4YV2BxCI9q6OmiTgZdosiMwbAsx1xGh9vbV96VJvqEfrXQGTWp hce2s+nJXQFCCtmGECGcaihdIpOflh/cn+IIWsVvS7deFXmmC5u8NwhtRBeh2qI4DIqd a6OnA7Sf0bhGLLZPBN8TB8EBsdRMxTUu7AgSQfs0MtoTK2nUWDHnzUnMAqIp9+K3bOPi TOmA== X-Gm-Message-State: AD7BkJJslCZnLMdDnx3vKSSQMhl90GaMqqZ0or0l9jeJyyErKnUOwsTAD5iCLvkNkTscwdaizDWIbqXRL8bCMA== MIME-Version: 1.0 X-Received: by 10.55.22.162 with SMTP id 34mr43663078qkw.63.1457538010171; Wed, 09 Mar 2016 07:40:10 -0800 (PST) Received: by 10.55.106.5 with HTTP; Wed, 9 Mar 2016 07:40:10 -0800 (PST) Date: Wed, 9 Mar 2016 18:40:10 +0300 Message-ID: Subject: EFI zfs loader and beadm? From: Andrey Fesenko To: "freebsd-hackers@freebsd.org" , freebsd-current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2016 15:40:11 -0000 Hello, I'm test EFI boot ZFSroot with BE, this not support now? svn 2965489 If i build simplest system http://blog.multiplay.co.uk/2015/12/freebsd-10-2-release-efi-zfs-root-boot/ # zfs get -r mountpoint efifpool NAME PROPERTY VALUE SOURCE efifpool mountpoint /mnt/efifpool default => 40 30712240 da0 GPT (15G) 40 1600 1 efi (800K) 1640 30710632 2 freebsd-zfs (15G) 30712272 8 - free - (4.0K) system boot nice If make BE env # zfs get -r mountpoint efiwpool NAME PROPERTY VALUE SOURCE efiwpool mountpoint none local efiwpool/ROOT mountpoint none inherited from efiwpool efiwpool/ROOT/init mountpoint legacy local efiwpool/ROOT/init@init mountpoint - - efiwpool/ROOT/init/boot mountpoint /media/boot local efiwpool/ROOT/init/tmp mountpoint /media/tmp local efiwpool/ROOT/init/usr mountpoint /media/usr local efiwpool/ROOT/init/usr@init mountpoint - - efiwpool/ROOT/init/usr/home mountpoint /media/usr/home inherited from efiwpool/ROOT/init/usr efiwpool/ROOT/init/usr/home@init mountpoint - - efiwpool/ROOT/init/var mountpoint /media/var local efiwpool/ROOT/init/var@init mountpoint - - efiwpool/ROOT/init/var/crash mountpoint /media/var/crash inherited from efiwpool/ROOT/init/var efiwpool/ROOT/init/var/db mountpoint /media/var/db inherited from efiwpool/ROOT/init/var efiwpool/ROOT/init/var/db/pkg mountpoint /media/var/db/pkg inherited from efiwpool/ROOT/init/var efiwpool/ROOT/init/var/empty mountpoint /media/var/empty inherited from efiwpool/ROOT/init/var efiwpool/ROOT/init/var/log mountpoint /media/var/log inherited from efiwpool/ROOT/init/var efiwpool/ROOT/init/var/mail mountpoint /media/var/mail inherited from efiwpool/ROOT/init/var efiwpool/ROOT/init/var/run mountpoint /media/var/run inherited from efiwpool/ROOT/init/var efiwpool/ROOT/init/var/tmp mountpoint /media/var/tmp inherited from efiwpool/ROOT/init/var system not boot. Not found /boot/loader.efi (in BE system real path efiwpool/ROOT/init/boot/loader.efi) if copy this efiwpool/ROOT/init (blank in BE system) loader found this (but not found /boot/kernel) I can copy this and get a similar system https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192184#c15 (with out msdos kernel part), but this ruin BE update mechanism From owner-freebsd-hackers@freebsd.org Wed Mar 9 15:48:27 2016 Return-Path: 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 34FB4AC9820; Wed, 9 Mar 2016 15:48:27 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [199.48.133.146]) by mx1.freebsd.org (Postfix) with ESMTP id E8584F41; Wed, 9 Mar 2016 15:48:26 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from sweettea.beer.town (unknown [76.164.8.130]) by smtp.vangyzen.net (Postfix) with ESMTPSA id 7B96D56A7A; Wed, 9 Mar 2016 09:48:25 -0600 (CST) Subject: Re: EFI zfs loader and beadm? To: Andrey Fesenko , "freebsd-hackers@freebsd.org" , freebsd-current References: From: Eric van Gyzen X-Enigmail-Draft-Status: N1110 Message-ID: <56E045C8.1040000@vangyzen.net> Date: Wed, 9 Mar 2016 09:48:24 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2016 15:48:27 -0000 On 03/09/2016 09:40, Andrey Fesenko wrote: > Hello, > I'm test EFI boot ZFSroot with BE, this not support now? > svn 2965489 > > If i build simplest system > http://blog.multiplay.co.uk/2015/12/freebsd-10-2-release-efi-zfs-root-boot/ > > # zfs get -r mountpoint efifpool > NAME PROPERTY VALUE SOURCE > efifpool mountpoint /mnt/efifpool default > > => 40 30712240 da0 GPT (15G) > 40 1600 1 efi (800K) > 1640 30710632 2 freebsd-zfs (15G) > 30712272 8 - free - (4.0K) > > system boot nice > > If make BE env > > # zfs get -r mountpoint efiwpool > NAME PROPERTY VALUE SOURCE > efiwpool mountpoint none local > efiwpool/ROOT mountpoint none > inherited from efiwpool > efiwpool/ROOT/init mountpoint legacy local > efiwpool/ROOT/init@init mountpoint - - > efiwpool/ROOT/init/boot mountpoint /media/boot local > efiwpool/ROOT/init/tmp mountpoint /media/tmp local > efiwpool/ROOT/init/usr mountpoint /media/usr local > efiwpool/ROOT/init/usr@init mountpoint - - > efiwpool/ROOT/init/usr/home mountpoint /media/usr/home > inherited from efiwpool/ROOT/init/usr > efiwpool/ROOT/init/usr/home@init mountpoint - - > efiwpool/ROOT/init/var mountpoint /media/var local > efiwpool/ROOT/init/var@init mountpoint - - > efiwpool/ROOT/init/var/crash mountpoint /media/var/crash > inherited from efiwpool/ROOT/init/var > efiwpool/ROOT/init/var/db mountpoint /media/var/db > inherited from efiwpool/ROOT/init/var > efiwpool/ROOT/init/var/db/pkg mountpoint /media/var/db/pkg > inherited from efiwpool/ROOT/init/var > efiwpool/ROOT/init/var/empty mountpoint /media/var/empty > inherited from efiwpool/ROOT/init/var > efiwpool/ROOT/init/var/log mountpoint /media/var/log > inherited from efiwpool/ROOT/init/var > efiwpool/ROOT/init/var/mail mountpoint /media/var/mail > inherited from efiwpool/ROOT/init/var > efiwpool/ROOT/init/var/run mountpoint /media/var/run > inherited from efiwpool/ROOT/init/var > efiwpool/ROOT/init/var/tmp mountpoint /media/var/tmp > inherited from efiwpool/ROOT/init/var > > system not boot. > > Not found /boot/loader.efi (in BE system real path > efiwpool/ROOT/init/boot/loader.efi) if copy this efiwpool/ROOT/init > (blank in BE system) loader found this (but not found /boot/kernel) I > can copy this and get a similar system > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192184#c15 (with out > msdos kernel part), but this ruin BE update mechanism Your dataset hierarchy is not what beadm expects. Specifically, you have /boot separate from /, which I imagine is causing your problem. /boot should be part of /. Also, you have several file systems in the BE that are usually not in it; I doubt this is part of your boot failure, though. For reference, here is my layout, which is mostly the same as the default installation: NAME USED AVAIL REFER MOUNTPOINT zroot 117G 108G 96K none zroot/ROOT 14.8G 108G 96K none zroot/ROOT/10.2 444K 108G 6.35G / zroot/ROOT/103beta 14.8G 108G 8.75G / zroot/ROOT/103beta1 8K 108G 8.17G / zroot/ROOT/103beta3 8K 108G 8.75G / zroot/home 97.8G 108G 94.9G /home zroot/usr 3.36G 108G 96K /usr zroot/usr/ports 985M 108G 736M /usr/ports zroot/usr/src 2.40G 108G 2.19G /usr/src zroot/var 2.19M 108G 96K /var zroot/var/audit 96K 108G 96K /var/audit zroot/var/crash 96K 108G 96K /var/crash zroot/var/log 1.15M 108G 420K /var/log zroot/var/mail 360K 108G 120K /var/mail zroot/var/tmp 416K 108G 144K /var/tmp Eric From owner-freebsd-hackers@freebsd.org Wed Mar 9 16:01:25 2016 Return-Path: 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 589DBAC9F2C; Wed, 9 Mar 2016 16:01:25 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 16E38FAE; Wed, 9 Mar 2016 16:01:25 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: by mail-qg0-x231.google.com with SMTP id u110so45118138qge.3; Wed, 09 Mar 2016 08:01:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=c6EGN4igNJ/bNDZBFoyVjcGpox0c3AR/KnFC9B5QzZA=; b=EjH+GHv64rFjJiquM2yM9m57ZZV892gTMTPmbMT55xWBlesUcm55sNwZcKqEk98I9u SrZSxHitGcYwYrHdY67QxWrL79rf5vX4jO8JtM6gLOzOF0A0D7CJrVruHHTxONDPWeMn MWizC8VUJVtYMXXG9V+TGHDLMKFDZlMQpYLvrcq/i397jTYQqfkSlMb5FUNO99SRVoPp PmQXYIpboUSvOzZ4H0ofd8QONzhsoRm2eLwCVwHNNTlZv7vJnj0y5Qflrx/JRYv5pbj2 HpZbBplsAODGwSgaqFJxjim5NpJgNf1+g7OKlkHT6fKHAOHycYVzzzQraPTDa8d2kTwd 3hiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=c6EGN4igNJ/bNDZBFoyVjcGpox0c3AR/KnFC9B5QzZA=; b=g1HqmkF2P3yOvXDysYKMbC+UmaOJ4g2VgArS7778s+BvBtYLCmUkzf0uR2k7Jor8kS 7bhFFMuCmzEQ2u+is1xvfjTyMq0kxPvrMsXvm46iQd9ZDx5Fpcj63v2wQx50Ux9hPyOv Iaah0OP+qUxJYCos+PSnNnCNC4IVdRxUbtcsEb7rVuB911OKt/1+UDpQutsCMiV2A6AJ UpT1k9lr+zqjS0/MTF/YnINNOYhuspcdn2KprI78JjNwPTBYNpripq6iNZY92Eb2F5OD IGGZ9FTMsfJdifj/TdQccDCbmFsrb2EOAat27I9xljqOCPsTEAtzoRfQAgoHyQl/SOX8 FWaw== X-Gm-Message-State: AD7BkJJk0GeQX3qOOV7y/wn3rFCpYmscKSc06oudIOrVoxW/mj8+BBUQjPjStZPrGZ8MYk8dnizaAQlddr861w== MIME-Version: 1.0 X-Received: by 10.140.168.85 with SMTP id o82mr40470531qho.75.1457539284205; Wed, 09 Mar 2016 08:01:24 -0800 (PST) Received: by 10.55.106.5 with HTTP; Wed, 9 Mar 2016 08:01:24 -0800 (PST) In-Reply-To: <56E045C8.1040000@vangyzen.net> References: <56E045C8.1040000@vangyzen.net> Date: Wed, 9 Mar 2016 19:01:24 +0300 Message-ID: Subject: Re: EFI zfs loader and beadm? From: Andrey Fesenko To: Eric van Gyzen Cc: "freebsd-hackers@freebsd.org" , freebsd-current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2016 16:01:25 -0000 On Wed, Mar 9, 2016 at 6:48 PM, Eric van Gyzen wrote: > On 03/09/2016 09:40, Andrey Fesenko wrote: >> Hello, >> I'm test EFI boot ZFSroot with BE, this not support now? >> svn 2965489 >> >> If i build simplest system >> http://blog.multiplay.co.uk/2015/12/freebsd-10-2-release-efi-zfs-root-boot/ >> >> # zfs get -r mountpoint efifpool >> NAME PROPERTY VALUE SOURCE >> efifpool mountpoint /mnt/efifpool default >> >> => 40 30712240 da0 GPT (15G) >> 40 1600 1 efi (800K) >> 1640 30710632 2 freebsd-zfs (15G) >> 30712272 8 - free - (4.0K) >> >> system boot nice >> >> If make BE env >> >> # zfs get -r mountpoint efiwpool >> NAME PROPERTY VALUE SOURCE >> efiwpool mountpoint none local >> efiwpool/ROOT mountpoint none >> inherited from efiwpool >> efiwpool/ROOT/init mountpoint legacy local >> efiwpool/ROOT/init@init mountpoint - - >> efiwpool/ROOT/init/boot mountpoint /media/boot local >> efiwpool/ROOT/init/tmp mountpoint /media/tmp local >> efiwpool/ROOT/init/usr mountpoint /media/usr local >> efiwpool/ROOT/init/usr@init mountpoint - - >> efiwpool/ROOT/init/usr/home mountpoint /media/usr/home >> inherited from efiwpool/ROOT/init/usr >> efiwpool/ROOT/init/usr/home@init mountpoint - - >> efiwpool/ROOT/init/var mountpoint /media/var local >> efiwpool/ROOT/init/var@init mountpoint - - >> efiwpool/ROOT/init/var/crash mountpoint /media/var/crash >> inherited from efiwpool/ROOT/init/var >> efiwpool/ROOT/init/var/db mountpoint /media/var/db >> inherited from efiwpool/ROOT/init/var >> efiwpool/ROOT/init/var/db/pkg mountpoint /media/var/db/pkg >> inherited from efiwpool/ROOT/init/var >> efiwpool/ROOT/init/var/empty mountpoint /media/var/empty >> inherited from efiwpool/ROOT/init/var >> efiwpool/ROOT/init/var/log mountpoint /media/var/log >> inherited from efiwpool/ROOT/init/var >> efiwpool/ROOT/init/var/mail mountpoint /media/var/mail >> inherited from efiwpool/ROOT/init/var >> efiwpool/ROOT/init/var/run mountpoint /media/var/run >> inherited from efiwpool/ROOT/init/var >> efiwpool/ROOT/init/var/tmp mountpoint /media/var/tmp >> inherited from efiwpool/ROOT/init/var >> >> system not boot. >> >> Not found /boot/loader.efi (in BE system real path >> efiwpool/ROOT/init/boot/loader.efi) if copy this efiwpool/ROOT/init >> (blank in BE system) loader found this (but not found /boot/kernel) I >> can copy this and get a similar system >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192184#c15 (with out >> msdos kernel part), but this ruin BE update mechanism > > Your dataset hierarchy is not what beadm expects. Specifically, you > have /boot separate from /, which I imagine is causing your problem. > /boot should be part of /. Also, you have several file systems in the > BE that are usually not in it; I doubt this is part of your boot > failure, though. > > For reference, here is my layout, which is mostly the same as the > default installation: > > NAME USED AVAIL REFER MOUNTPOINT > zroot 117G 108G 96K none > zroot/ROOT 14.8G 108G 96K none > zroot/ROOT/10.2 444K 108G 6.35G / > zroot/ROOT/103beta 14.8G 108G 8.75G / > zroot/ROOT/103beta1 8K 108G 8.17G / > zroot/ROOT/103beta3 8K 108G 8.75G / > zroot/home 97.8G 108G 94.9G /home > zroot/usr 3.36G 108G 96K /usr > zroot/usr/ports 985M 108G 736M /usr/ports > zroot/usr/src 2.40G 108G 2.19G /usr/src > zroot/var 2.19M 108G 96K /var > zroot/var/audit 96K 108G 96K /var/audit > zroot/var/crash 96K 108G 96K /var/crash > zroot/var/log 1.15M 108G 420K /var/log > zroot/var/mail 360K 108G 120K /var/mail > zroot/var/tmp 416K 108G 144K /var/tmp > > Eric If remove efiwpool/ROOT/init/boot and copy his content on efiwpool/ROOT/init my scheme work fine too. /usr /var /home and other included in BE for consistent boot system (CURRENT world may not boot with kernel other rev), and old home snapshot sometimes useful for backup/restore From owner-freebsd-hackers@freebsd.org Wed Mar 9 18:06:11 2016 Return-Path: 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 6D224AC9A02 for ; Wed, 9 Mar 2016 18:06:11 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from mail.strugglingcoder.info (strugglingcoder.info [104.236.146.68]) by mx1.freebsd.org (Postfix) with ESMTP id 60A2F304 for ; Wed, 9 Mar 2016 18:06:10 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from localhost (unknown [10.1.1.3]) (Authenticated sender: hiren@strugglingcoder.info) by mail.strugglingcoder.info (Postfix) with ESMTPA id 2AA1E17281; Wed, 9 Mar 2016 10:06:10 -0800 (PST) Date: Wed, 9 Mar 2016 10:06:10 -0800 From: hiren panchasara To: Vineet Purswani Cc: freebsd-hackers@freebsd.org Subject: Re: Greetings FreeBSD Community : GSOC Queries Message-ID: <20160309180610.GG20779@strugglingcoder.info> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="z9ECzHErBrwFF8sy" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2016 18:06:11 -0000 --z9ECzHErBrwFF8sy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 03/08/16 at 10:29P, Vineet Purswani wrote: > I am interested in knowing more > about a project listed on FreeBSD GSOC ideas page - *Linux to BSM > Conversion Tool* >=20 > *Kindly guide me as to how do I start working on this idea? Try reaching out to listed mentor(s). Cheers, Hiren --z9ECzHErBrwFF8sy Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAABCgBmBQJW4GYSXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4 QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/lsAQH+wRGxxB6R8Uvt+Rgr2bN+NHZ +ArYAsZcSt2igmB4cmc/ZOk+8hU4nOQWtGkxiLCeRjeMNwU7D7ObljPswlgOaPWy WI6GStU6xgTf71eFYTE6LZHEzDL4WyacYzLs1CiKK+2WnqfvrtT0ji9a4qFLx55u 6bVX0CH9+sanJIR3ksDEjEkbj2gsN/2UntE0SjV1+tLp3k3hpvyiT7w+poS6bXTs gDA++jFPUUcIUJ8DKTUmmwOoUXW4+aoxSm0eR9JDrjNyHnNnIEsvz3B+ylrZMO8x MUiHzQNhWggDQ011rHX+6RUcj/mqO4580CK4Ngi2ufSfhoLZ52bLHzmjU9CEs68= =4Vec -----END PGP SIGNATURE----- --z9ECzHErBrwFF8sy-- From owner-freebsd-hackers@freebsd.org Thu Mar 10 08:50:35 2016 Return-Path: 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 D8C07AC7432 for ; Thu, 10 Mar 2016 08:50:35 +0000 (UTC) (envelope-from bharghav2947@gmail.com) Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com [IPv6:2a00:1450:4010:c04::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 6368F19B0 for ; Thu, 10 Mar 2016 08:50:35 +0000 (UTC) (envelope-from bharghav2947@gmail.com) Received: by mail-lb0-x22d.google.com with SMTP id k15so103151155lbg.0 for ; Thu, 10 Mar 2016 00:50:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=QvRClB6pDZhObBlb5d0Y2GPlOQegsAYG67z9HtACZu8=; b=jAFz2DHPx9QfuWiU+BGcZFbJ0x2hWJ9qOqE52881Kn5E1liwQnIiK/AvgwY3e9sWvV oDkRs5o3SqdR02VnYMn3yyWXG42C4s6yt+PfCOb8yJjJ1fjfRZHThcM0Vie8XNKNgJhf an4vwA36S4OpV1J+bfPRcz+32RZLaXXVWrq5WLc7SUKkprJgfq0UjqCy1c+dL7NzI5t5 O2jSRw6+MAbfIedtMN3bt7HubGMpmE1ogQPpVouzpLk0KUUTZrjEOwSXgRIC/PSkYS5k bFDDiwpPTmW8+pxGmBsYGfckT+aOzp7oPzbjsx4LTcYNMNBaFz34ZFSnmczoPxVCfgzs 8XCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=QvRClB6pDZhObBlb5d0Y2GPlOQegsAYG67z9HtACZu8=; b=Mmj0K9ff3T5F9ziknifuEMenX8RVfwyB8TjL8juK1E9oxqUHRzExMViXcynU63GvEu SlRBWRtr9VxJLXb/41uZnETu6IPSsHSa61miDuZE4g8I7O7a3Tm51t0JUjlJW/LZz53a lafFANhOKvtEk+DOIlViHwt+CtVE0A2O1rkeGrJ9NIoY6NrVrCXLmKjgfpnJUGUd6x0E DnijlBi8wNar956+FR62ld2oitT8AA2msA13lgg2gz0ax1BIVRP2d9ZbOoEKadsCuPYo 3WsZnmMrWGUUtQVIKt+GLw7FQ/HP5JXOAhmZLHr26HG2GepDRvEH8sTJ+rXqKwsBQo63 ItvQ== X-Gm-Message-State: AD7BkJIxhK29JK+iPRBpYrHBFnVLPZLAJiUfAYI0LfCjZzeCa5P/a0QQX9KcU3uqYobdeaQdePTvgiJBdf4PAQ== MIME-Version: 1.0 X-Received: by 10.113.3.6 with SMTP id bs6mr774813lbd.114.1457599833491; Thu, 10 Mar 2016 00:50:33 -0800 (PST) Received: by 10.25.196.196 with HTTP; Thu, 10 Mar 2016 00:50:33 -0800 (PST) Date: Thu, 10 Mar 2016 14:20:33 +0530 Message-ID: Subject: Converting DAC or policy Rules into Capsicum capabilities From: pavan teja To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 08:50:36 -0000 Hello everyone, I'm right now working on Implementing KDBus project into FreeBSD project .In the KDBus we have a set of policy rules by which we can control the bus connectivity by other processes . If viewing from the other side policy rules appeared to me similar to DAC the security mechanism used in Linux . Can anyone suggest me a good way to convert these DAC rules into capabilities .I want to replace these policy rules in KDBus in my design and replace them with some capabilities . *Example for some policy rules are:* KDBUS_ITEM_NAME: str='org.foo.bar' KDBUS_ITEM_POLICY_ACCESS: type=USER, access=OWN, id=1000 KDBUS_ITEM_POLICY_ACCESS: type=USER, access=TALK, id=1001 KDBUS_ITEM_POLICY_ACCESS: type=WORLD, access=SEE Please help me out by stating an example as how i can convert policy rules as these into some form of capabilities given to each process .This would be very helpful for my design. From owner-freebsd-hackers@freebsd.org Thu Mar 10 10:39:45 2016 Return-Path: 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 E6A72ACA29D for ; Thu, 10 Mar 2016 10:39:45 +0000 (UTC) (envelope-from bharghav2947@gmail.com) Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 799ED96C for ; Thu, 10 Mar 2016 10:39:45 +0000 (UTC) (envelope-from bharghav2947@gmail.com) Received: by mail-lb0-x235.google.com with SMTP id k15so106857540lbg.0 for ; Thu, 10 Mar 2016 02:39:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=8ev39W1WczPLQh2aIlQnOSe/fY3YygvNOy7spehgADA=; b=TjEsjERGuBPyrQpCYGyou/JNApXdVGm9792eAx45RW5lE6zuKQmKPhQfO45J7btvql k5ADRPygcdqjwbkpV3JTMW8lChmEVpue6gUNsqktWv48gU7VBeFR5qlkBcNBXuhTa5EQ PLtiD1TyLsoZ400yxeRbmGus60My1oGpSEsnPHBT8SAFL7LD8DUnkiKtbluOlMdiFCnO sfWQm886ZLoJGFr8tf4cvyR9DzzCfu3ySArRN/9tatDSMigUwK+dNXfXnGqF8yjajfKS RaGVPQaRDJuj6lCJXKm+mYveJwex5o2xFyK0N6gLBvZagzafhhUl97moV7iJ03JepOZY ZtHQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=8ev39W1WczPLQh2aIlQnOSe/fY3YygvNOy7spehgADA=; b=fnonIIZ3Y8IBei3i6F9KC7Vk1Lm8JDKuRbYrB4k2bklmoFmllthQIsvsdszDzeuX+0 IhXMKcxfREEWUaM8S272/1Rd9XuGeJb6zsWlQJSCylm5e4U+n4Qvf0FWkEiHVYCKGStz 3O7cIJGVF4UG4JUJpYlocODMuT+iQhtpXAw+uNe29Ec7eIRxPbRKo28kmZ5JOFsNmfW+ eYUVc7/jhYPmUh6P7jH4BcbacjxJM9G52x2VpjPiQFiZDQUiIRrNo/je6Fg25xJk7l+3 WIRyFEXSFZe0arjzsAz0L3CkzyqZ5vk2V9kqZO1WxXe/6mwhS/v7KZlw7fgFrmbI+Byg ZqbA== X-Gm-Message-State: AD7BkJJbGJ9+jtSx7Jd2q3ku0d+njOl/zc3tGpgqA2tANpSZYex6r+BPzXMoYiDB6O6wkknj9EjyqVEY2NOOlw== MIME-Version: 1.0 X-Received: by 10.25.21.151 with SMTP id 23mr951626lfv.89.1457606383647; Thu, 10 Mar 2016 02:39:43 -0800 (PST) Received: by 10.25.196.196 with HTTP; Thu, 10 Mar 2016 02:39:43 -0800 (PST) Date: Thu, 10 Mar 2016 16:09:43 +0530 Message-ID: Subject: Two names when creating a module From: pavan teja To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 10:39:46 -0000 Hello everyone, While I'm testing with creating modules in FreeBSD , I encountered giving two names for a module once in module_t structure and the other when using DECLARE_MODULE(name,module_t struct).Why cant we give a single name .Why are there two names when we create module.I read the man page of FreeBSD but it didnot explain much . Thank You In Advance From owner-freebsd-hackers@freebsd.org Thu Mar 10 11:01:03 2016 Return-Path: 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 B1B76ACAE4C; Thu, 10 Mar 2016 11:01:03 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: from mail-qg0-x22d.google.com (mail-qg0-x22d.google.com [IPv6:2607:f8b0:400d:c04::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 6D650859; Thu, 10 Mar 2016 11:01:03 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: by mail-qg0-x22d.google.com with SMTP id t4so66838296qge.0; Thu, 10 Mar 2016 03:01:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=MbEAxSVOOJji7DGX+sQ3NTj+jms3aEINOXcRBr6yPz4=; b=LeMn0lTNBuLKR6lcEn9dJjvddH84oRLMciJjWUuexvVMt3xHFNZ9srqLm/HPSc1GGN E8UlesuGMO/PiYK6LTNsnC2XHBQSsXZHt4UJMTyOfETp0fmQRP+eLgqtfEWEIzzCwET7 htj9Tc76E/Wtr9ZQHeyNz+xe37ZvnXhZfXrNOEXdYuMD8vpGmO11j1XUuyKhIEZdCeR7 YSnGnqzC3pSJ4d1z/oUsZDaQVClWf0bZ+HMgdIXj/brnEOcGg0mf03wCwLuqzvyd5w0I iA75fV9/8vv7Mlp6qkqzSnGCaAggl27OPEEMtWgXXreAxb0mDex6Q6vPKonm5YJ5EJB/ LJdg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=MbEAxSVOOJji7DGX+sQ3NTj+jms3aEINOXcRBr6yPz4=; b=G7yuidVG42aLyicihZOeIDxJSlZ8ySB5OLLAZsOrXaELK315qOqRQJ5g2MDT80bNne NaJWQ6MGel4+wwony/6vQoQUfUVi4bEmlzXTJqRCPsdB//SoevwkMybLN3uZJeLj9EsR GCy369+CHJCNBZvy4+NImxO4YbufRoKcFNkv6kl+/2nHd1fEJZjT3v3Bn7Mqo3dTygK3 0F9oPeTZkC4Wtwlbz9AZPgTMCelSdTX8pZF7g0o0XOM9Px9skCRAsgfG/VgB8pZyz70I Z1rdcgpgNxMD5S/M/Um3EomJtNV6Bt3V04Izd2Hl2FexGAe1PqNThqVO/ZYI7hRzhWp4 LYNA== X-Gm-Message-State: AD7BkJI9WTgCxON36x4FwBz0AM7tkvzGcEVmyATo24gFkckngx9gISdwCwgWkJVnsk3XU8uusNiyCleGOaP13w== MIME-Version: 1.0 X-Received: by 10.140.138.209 with SMTP id 200mr3274432qhk.100.1457607662648; Thu, 10 Mar 2016 03:01:02 -0800 (PST) Received: by 10.55.106.5 with HTTP; Thu, 10 Mar 2016 03:01:02 -0800 (PST) In-Reply-To: References: <56E045C8.1040000@vangyzen.net> Date: Thu, 10 Mar 2016 14:01:02 +0300 Message-ID: Subject: Re: EFI zfs loader and beadm? From: Andrey Fesenko To: krad Cc: Eric van Gyzen , "freebsd-hackers@freebsd.org" , freebsd-current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 11:01:03 -0000 On Thu, Mar 10, 2016 at 1:49 PM, krad wrote: > Make sure you are running the latest snapshot of current or 10.3 as well, as > the MFC commits were in early February for 10-stable > >> >> If remove efiwpool/ROOT/init/boot and copy his content on >> efiwpool/ROOT/init my scheme work fine too. >> /usr /var /home and other included in BE for consistent boot system >> (CURRENT world may not boot with kernel other rev), and old home >> snapshot sometimes useful for backup/restore >> _______________________________________________ % uname -a FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296548: Wed Mar 9 01:16:17 MSK 2016 root@des.local:/usr/obj/usr/src/sys/X220 amd64 From owner-freebsd-hackers@freebsd.org Thu Mar 10 12:04:35 2016 Return-Path: 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 160C6AC9478 for ; Thu, 10 Mar 2016 12:04:35 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-qg0-x229.google.com (mail-qg0-x229.google.com [IPv6:2607:f8b0:400d:c04::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 CC84D299 for ; Thu, 10 Mar 2016 12:04:34 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: by mail-qg0-x229.google.com with SMTP id u110so67985109qge.3 for ; Thu, 10 Mar 2016 04:04:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=longcount-org.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=MXfokCsh6/A17G6dPzznJxDCSgtiWJ8d80EQPJZ62Dc=; b=O9EA0o+ucfQD59QaYXHcf3UmOXID89RVbA5rtPn0TheAB+Y6NlF7eW4+8utku8/Olc nFRJf5a5TUxizGxaZY0DL21CVRd5H+qAl2or+SCp4rFHKzdhBObYuYCakKZD2lf5iJNf Ue8BCFHh8NKqXjsOqcl0vtaCLcnW6fawO12OKpH4w9Ld/qxaljzP6e6Nolx2GZJZkzc5 0P1jf2yjjc5LEQQzr73tR/W4o1ULq+Kw0z3e57Ap4lmiUTb6gU3VB4Y3DB+hhLLT6hSq bwJmxkVqjR7rfUGzH2bo2nVNu0aPNVA580mI8swV0M2Mpj+Ha0HD4kxFNaHz7VqweQS9 QgCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=MXfokCsh6/A17G6dPzznJxDCSgtiWJ8d80EQPJZ62Dc=; b=L6HFYX6aMUWOg8jJ3Pl12/iI0uxdvaGPNi6JuwABjUnz4hPQUL+Bz8Emmc6S1BkDQ2 9Ur4Z31JhuCoNM5Vh6YSEpTXzxuge01+UeT3i6Iz0Zvrb+KLeth+Y4ylqNc9lttOScrV PKiIAfLlQLWHIE2XrJVbVArzmlwHjs9c0ZUUL6UwaVFf6iu+1qTVWyCfEWNZUOAxOV6q CRzqFTJv2YLXO6BWojTXENzcFOKdLqU7kB5qZDSCfA/SE8GjiCUo1vAL/O8FLgGkm2hz MzgCqeZPdhm43t8Szbqblx+s/SNxNBlkrf/Z4FdtK1mI+qN1D/1t5nEX+5Izu2utogER bdyg== X-Gm-Message-State: AD7BkJKFp/5XvcUEMYLZR8y18etxseLzShlXlRsGry3LwRuXpbDRGyQwzhqO2oCrKlQZhg== X-Received: by 10.140.101.147 with SMTP id u19mr3542990qge.71.1457611473667; Thu, 10 Mar 2016 04:04:33 -0800 (PST) Received: from [192.168.1.51] (ool-4351f633.dyn.optonline.net. [67.81.246.51]) by smtp.gmail.com with ESMTPSA id r18sm1523740qkl.24.2016.03.10.04.04.33 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 10 Mar 2016 04:04:33 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: Converting DAC or policy Rules into Capsicum capabilities From: Mark Saad X-Mailer: iPhone Mail (13D15) In-Reply-To: Date: Thu, 10 Mar 2016 07:04:32 -0500 Cc: freebsd-hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <5F38D237-B15A-48B6-8766-622DA1B17B91@longcount.org> References: To: pavan teja X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 12:04:35 -0000 Pavan What is the use of kdbus ? It's been abandoned,=20 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D806558;msg=3D5 could th= e Mach ipc module from nextbsd be used ? --- Mark Saad | nonesuch@longcount.org > On Mar 10, 2016, at 3:50 AM, pavan teja wrote: >=20 > Hello everyone, > I'm right now working on Implementing KDBus project into= > FreeBSD project .In the KDBus we have a set of policy rules by which we ca= n > control the bus connectivity by other processes . If viewing from the othe= r > side policy rules appeared to me similar to DAC the security mechanism use= d > in Linux . Can anyone suggest me a good way to convert these DAC rules int= o > capabilities .I want to replace these policy rules in KDBus in my design > and replace them with some capabilities . *Example for some policy rules > are:* >=20 > KDBUS_ITEM_NAME: str=3D'org.foo.bar' > KDBUS_ITEM_POLICY_ACCESS: type=3DUSER, access=3DOWN, id=3D1000 > KDBUS_ITEM_POLICY_ACCESS: type=3DUSER, access=3DTALK, id=3D1001 > KDBUS_ITEM_POLICY_ACCESS: type=3DWORLD, access=3DSEE >=20 > Please help me out by stating an example as how i can convert policy > rules as these into some form of capabilities given to each process > .This would be very helpful for my design. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"= From owner-freebsd-hackers@freebsd.org Thu Mar 10 12:11:04 2016 Return-Path: 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 2D3CAAC99DA; Thu, 10 Mar 2016 12:11:04 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: from mail-qg0-x232.google.com (mail-qg0-x232.google.com [IPv6:2607:f8b0:400d:c04::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 E4E26857; Thu, 10 Mar 2016 12:11:03 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: by mail-qg0-x232.google.com with SMTP id u110so68124715qge.3; Thu, 10 Mar 2016 04:11:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=YRhGeoz98/Dum+zjEToCcUn7GZOeUG9O6VHDhsBn/Pw=; b=SRI6M9G038cQOswOC7l8S1pGQQ7zSEV/DRVKX7ex3iTOAs9etq6yLyYRL+gV9HUb2b 36MzXxmnwmPFA01Xo6Wq5i8wcvuJQ2/o/URFhxRtqM4r+Dkxa4qCfEUorwdpMIEc/kCu HUdqzq9g3eCclunlnDQSP0UVGe9C+AnaSZu5xO0gDR23ZTe3plR0bsr/cCXnwT1m6sUK e5QcC4Sm3Y9MlM23C7cEBMiWg5gdgrOfgMTlPB6h6u3cH1quXoivTV/qKy4kDc8ZmgnO z+8i8tLNIgFybUAwj1tmNkk20jRD+OG6QpAFfP8ZJAa5zB7lLWxF2SvE6FLdHZQC/xzb NXww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=YRhGeoz98/Dum+zjEToCcUn7GZOeUG9O6VHDhsBn/Pw=; b=ZOLf9nb0og8K1DdkW5SkSLDA3OzIVq2XeCjMjEbrov+LH7bXjA7mN8QAX5U5KEQme6 q3bRh7wGEvRnpkJcKi2NtfEXsx0swMjO1UUVH8XjwwbegiBqiVPCRa8VY/zA+Yikl9n8 TeBF+/xpv3EGJ89jMDyUXAzELzRi+sZsvFQkNf/7iqdDboi2VPPHWbzo+i0um7PI/Vao ieuwB8s7E2Ep0c+NOWPjVi8/gZ6MnoRjs+Qhbr0sAenXzS64vThLpbSc1NMuyFnEhyo9 m48nYawgGIqmopcK/RT+67KM4H4AtvtA+vz/vCvnxWV+Kxr4b3dp5Ru1Z1v3yCJVDbi/ mLpQ== X-Gm-Message-State: AD7BkJKm7OSHAJp0Q2XtaccydPDOb6McRADSxnpAuzoU3sRVpXAmztA8oqkxDwou+CDW7uecGvJ1rEQmmo5DCg== MIME-Version: 1.0 X-Received: by 10.140.92.180 with SMTP id b49mr3489942qge.81.1457611862726; Thu, 10 Mar 2016 04:11:02 -0800 (PST) Received: by 10.55.106.5 with HTTP; Thu, 10 Mar 2016 04:11:02 -0800 (PST) In-Reply-To: References: <56E045C8.1040000@vangyzen.net> Date: Thu, 10 Mar 2016 15:11:02 +0300 Message-ID: Subject: Re: EFI zfs loader and beadm? From: Andrey Fesenko To: krad Cc: Eric van Gyzen , "freebsd-hackers@freebsd.org" , freebsd-current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 12:11:04 -0000 On Thu, Mar 10, 2016 at 2:55 PM, krad wrote: > presumably it boots now? > > On 10 March 2016 at 11:01, Andrey Fesenko wrote: >> >> On Thu, Mar 10, 2016 at 1:49 PM, krad wrote: >> > Make sure you are running the latest snapshot of current or 10.3 as >> > well, as >> > the MFC commits were in early February for 10-stable >> > >> >> >> >> If remove efiwpool/ROOT/init/boot and copy his content on >> >> efiwpool/ROOT/init my scheme work fine too. >> >> /usr /var /home and other included in BE for consistent boot system >> >> (CURRENT world may not boot with kernel other rev), and old home >> >> snapshot sometimes useful for backup/restore >> >> _______________________________________________ >> >> % uname -a >> FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296548: >> Wed Mar 9 01:16:17 MSK 2016 >> root@des.local:/usr/obj/usr/src/sys/X220 amd64 > > My current working config % mount efiwpool/ROOT/init0 on / (zfs, local, noatime, nfsv4acls) devfs on /dev (devfs, local, multilabel) efiwpool/ROOT/init0/tmp on /tmp (zfs, local, noatime, nosuid, nfsv4acls) efiwpool/ROOT/init0/usr on /usr (zfs, local, noatime, nfsv4acls) efiwpool/ROOT/init0/usr/home on /usr/home (zfs, local, noatime, nfsv4acls) efiwpool/ROOT/init0/var on /var (zfs, local, noatime, nfsv4acls) efiwpool/ROOT/init0/var/crash on /var/crash (zfs, local, noatime, noexec, nosuid, nfsv4acls) efiwpool/ROOT/init0/var/db on /var/db (zfs, local, noatime, noexec, nosuid, nfsv4acls) efiwpool/ROOT/init0/var/db/pkg on /var/db/pkg (zfs, local, noatime, nosuid, nfsv4acls) efiwpool/ROOT/init0/var/db/tlpkg on /var/db/tlpkg (zfs, local, noatime, nosuid, nfsv4acls) efiwpool/ROOT/init0/var/empty on /var/empty (zfs, local, noatime, noexec, nosuid, read-only, nfsv4acls) efiwpool/ROOT/init0/var/log on /var/log (zfs, local, noatime, noexec, nosuid, nfsv4acls) efiwpool/ROOT/init0/var/mail on /var/mail (zfs, local, noatime, noexec, nosuid, nfsv4acls) efiwpool/ROOT/init0/var/run on /var/run (zfs, local, noatime, noexec, nosuid, nfsv4acls) efiwpool/ROOT/init0/var/tmp on /var/tmp (zfs, local, noatime, nosuid, nfsv4acls) => 40 234441568 ada1 GPT (112G) 40 1600 1 efi (800K) 1640 234439960 2 freebsd-zfs (112G) 234441600 8 - free - (4.0K) % zfs get -r mountpoint efiwpool NAME PROPERTY VALUE SOURCE efiwpool mountpoint none local efiwpool/ROOT mountpoint none inherited from efiwpool efiwpool/ROOT/init mountpoint legacy local efiwpool/ROOT/init/tmp mountpoint /tmp local .... This work fine, booted, beadm create new env, activate them, see boot menu and select BE. % beadm list BE Active Mountpoint Space Created init - - 420.7M 2016-03-09 02:57 init0 NR / 35.9G 2016-03-10 05:00 If i'm add separate dataset for /boot (efiwpool/ROOT/init0/boot) system not booted, efi loader (first stage) see only my pool, not found /boot/loader.efi From owner-freebsd-hackers@freebsd.org Thu Mar 10 10:49:39 2016 Return-Path: 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 1376EACA7C8; Thu, 10 Mar 2016 10:49:39 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::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 A526AFFA; Thu, 10 Mar 2016 10:49:38 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: by mail-wm0-x22f.google.com with SMTP id p65so22996439wmp.1; Thu, 10 Mar 2016 02:49:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=SaqzxM3gD9FMcY3XuDuE/wB/eM3gyDl/AxqTk+MkwNQ=; b=SFd9/A6Pg13WfXrf2QpDr8Z3a1TYFmecl6SrvWHaJjGu/3O/a4Uoy+vP60IwQRT1JB ID1eZpLl5fPeTWD0oR/nL8NBPwXhhFzUiuQdrN2cGuM8rRuNPZTGaU+ej/e+jYK1SiLt CIjiu0TGj5DeUs+zbRfiFZOaFt6TYtfrdVkkrfdeTj3hVMwnWTG3Q8YNavEH6e71ePuX +VSWBkHQRuX8fcLgBf8SLHfkVLIfNOwMS/UiwtvLigSWLeAEDA8K5Az9BvgwXJtdVAFB c7uO5Y6w3AFSHsEkl+lBlI5YUXYET9QZQwyKXaZYU8koeEsXSsPmmQPJ54RdniO7m55s 6eLA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=SaqzxM3gD9FMcY3XuDuE/wB/eM3gyDl/AxqTk+MkwNQ=; b=GLtOsvoF7YLgXNebqiZQfrpfBgo21antaJV6eP3ITEyc3Phs9VrOWRIbcRfkUzCEU+ WFjJn0GxlBmQ5BuW9oZP+Vd17z9lvUeLYJYEc+8CQWwfvRT8h5vgfdu08fyZaw6a8lVI si+Zu3h4mm7TXyVSghhz5NGhfgIUDuVKG5kra8B56Qt5O/oOnSfx793VsP/1Tb6qg8Jd Oq+AruVQ2jheVNCH3EbY2Sm0OtmXPslSqvpQK+hCy7rVcDE4KoCdBRJFdKHtYkNFiP1R xtGoa/8tYZyINa/WBG5RVK6o8mMmA00akhWZaNkOjGMU88yXLMxH2Uy+AY8d+49OumGV A3UQ== X-Gm-Message-State: AD7BkJJM4+L3SLSIldLAkpweK+ftnQwlYhX8uJU90MpJgF0eaAsi52O8V4zIcR/9rS+A3Dc7a2y4FoicbM892A== MIME-Version: 1.0 X-Received: by 10.28.17.141 with SMTP id 135mr3266854wmr.48.1457606977028; Thu, 10 Mar 2016 02:49:37 -0800 (PST) Received: by 10.28.31.143 with HTTP; Thu, 10 Mar 2016 02:49:36 -0800 (PST) In-Reply-To: References: <56E045C8.1040000@vangyzen.net> Date: Thu, 10 Mar 2016 10:49:36 +0000 Message-ID: Subject: Re: EFI zfs loader and beadm? From: krad To: Andrey Fesenko Cc: Eric van Gyzen , "freebsd-hackers@freebsd.org" , freebsd-current X-Mailman-Approved-At: Thu, 10 Mar 2016 12:53:44 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 10:49:39 -0000 Make sure you are running the latest snapshot of current or 10.3 as well, as the MFC commits were in early February for 10-stable On 9 March 2016 at 16:01, Andrey Fesenko wrote: > On Wed, Mar 9, 2016 at 6:48 PM, Eric van Gyzen wrote: > > On 03/09/2016 09:40, Andrey Fesenko wrote: > >> Hello, > >> I'm test EFI boot ZFSroot with BE, this not support now? > >> svn 2965489 > >> > >> If i build simplest system > >> > http://blog.multiplay.co.uk/2015/12/freebsd-10-2-release-efi-zfs-root-boot/ > >> > >> # zfs get -r mountpoint efifpool > >> NAME PROPERTY VALUE SOURCE > >> efifpool mountpoint /mnt/efifpool default > >> > >> => 40 30712240 da0 GPT (15G) > >> 40 1600 1 efi (800K) > >> 1640 30710632 2 freebsd-zfs (15G) > >> 30712272 8 - free - (4.0K) > >> > >> system boot nice > >> > >> If make BE env > >> > >> # zfs get -r mountpoint efiwpool > >> NAME PROPERTY VALUE SOURCE > >> efiwpool mountpoint none local > >> efiwpool/ROOT mountpoint none > >> inherited from efiwpool > >> efiwpool/ROOT/init mountpoint legacy local > >> efiwpool/ROOT/init@init mountpoint - - > >> efiwpool/ROOT/init/boot mountpoint /media/boot local > >> efiwpool/ROOT/init/tmp mountpoint /media/tmp local > >> efiwpool/ROOT/init/usr mountpoint /media/usr local > >> efiwpool/ROOT/init/usr@init mountpoint - - > >> efiwpool/ROOT/init/usr/home mountpoint /media/usr/home > >> inherited from efiwpool/ROOT/init/usr > >> efiwpool/ROOT/init/usr/home@init mountpoint - - > >> efiwpool/ROOT/init/var mountpoint /media/var local > >> efiwpool/ROOT/init/var@init mountpoint - - > >> efiwpool/ROOT/init/var/crash mountpoint /media/var/crash > >> inherited from efiwpool/ROOT/init/var > >> efiwpool/ROOT/init/var/db mountpoint /media/var/db > >> inherited from efiwpool/ROOT/init/var > >> efiwpool/ROOT/init/var/db/pkg mountpoint /media/var/db/pkg > >> inherited from efiwpool/ROOT/init/var > >> efiwpool/ROOT/init/var/empty mountpoint /media/var/empty > >> inherited from efiwpool/ROOT/init/var > >> efiwpool/ROOT/init/var/log mountpoint /media/var/log > >> inherited from efiwpool/ROOT/init/var > >> efiwpool/ROOT/init/var/mail mountpoint /media/var/mail > >> inherited from efiwpool/ROOT/init/var > >> efiwpool/ROOT/init/var/run mountpoint /media/var/run > >> inherited from efiwpool/ROOT/init/var > >> efiwpool/ROOT/init/var/tmp mountpoint /media/var/tmp > >> inherited from efiwpool/ROOT/init/var > >> > >> system not boot. > >> > >> Not found /boot/loader.efi (in BE system real path > >> efiwpool/ROOT/init/boot/loader.efi) if copy this efiwpool/ROOT/init > >> (blank in BE system) loader found this (but not found /boot/kernel) I > >> can copy this and get a similar system > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192184#c15 (with out > >> msdos kernel part), but this ruin BE update mechanism > > > > Your dataset hierarchy is not what beadm expects. Specifically, you > > have /boot separate from /, which I imagine is causing your problem. > > /boot should be part of /. Also, you have several file systems in the > > BE that are usually not in it; I doubt this is part of your boot > > failure, though. > > > > For reference, here is my layout, which is mostly the same as the > > default installation: > > > > NAME USED AVAIL REFER MOUNTPOINT > > zroot 117G 108G 96K none > > zroot/ROOT 14.8G 108G 96K none > > zroot/ROOT/10.2 444K 108G 6.35G / > > zroot/ROOT/103beta 14.8G 108G 8.75G / > > zroot/ROOT/103beta1 8K 108G 8.17G / > > zroot/ROOT/103beta3 8K 108G 8.75G / > > zroot/home 97.8G 108G 94.9G /home > > zroot/usr 3.36G 108G 96K /usr > > zroot/usr/ports 985M 108G 736M /usr/ports > > zroot/usr/src 2.40G 108G 2.19G /usr/src > > zroot/var 2.19M 108G 96K /var > > zroot/var/audit 96K 108G 96K /var/audit > > zroot/var/crash 96K 108G 96K /var/crash > > zroot/var/log 1.15M 108G 420K /var/log > > zroot/var/mail 360K 108G 120K /var/mail > > zroot/var/tmp 416K 108G 144K /var/tmp > > > > Eric > > If remove efiwpool/ROOT/init/boot and copy his content on > efiwpool/ROOT/init my scheme work fine too. > /usr /var /home and other included in BE for consistent boot system > (CURRENT world may not boot with kernel other rev), and old home > snapshot sometimes useful for backup/restore > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@freebsd.org Thu Mar 10 11:55:35 2016 Return-Path: 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 A48E9ACA7F2; Thu, 10 Mar 2016 11:55:35 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3B7A9A6C; Thu, 10 Mar 2016 11:55:35 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: by mail-wm0-x231.google.com with SMTP id p65so25238888wmp.1; Thu, 10 Mar 2016 03:55:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=f5RF1izUv83nVSkXWPEaa0fhTTm+n3Q/m4mnw1BqbJ8=; b=GfPQKkog8zVsprGxzzfJyrO+5nJfEQWtzBtsu4AJTZEooApaOT5KPujo7q+wWf43+g WE6CDs/J+h4Hv7JQOBk9MRw5TPBjRlhs32AppL1XERmhvzSY596wBEXrKehiipk9pPtJ 8FUOhtMZYuM7oxWGbj9WifZUJ7wrHIWqDzD60NRkKn8eDDNT5+tFCeNeieHyRGZjtFPr BZgQ0BKPTNDRCcGdhLxsoOD64RGCjPP17Hu5CS46f5cXUNFQA6Dv02bz1dNYnj+vJd12 m3jQpi25GCNrZ9tW2sQquDihcncPD/D/rvmVDCWL/dtWy/YcSQf/ZS1HHhtZe2fxBLyG HTlA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=f5RF1izUv83nVSkXWPEaa0fhTTm+n3Q/m4mnw1BqbJ8=; b=khprmul/2IMDCR5fEee7sVzUyVmKOzK+eQog3dDZpZayUu/xE9l0LjInezLn0Sldnb 2X8u46bbYa1h7NI5DZQZbOU57BDpwMcV5BvIa/wFQxt+V+4Q/YS5GwuqSWvJoI3YRfJ1 r4dmY7tZafJlaJlTPB4dbCH2xUWFrd8tcDHP6COt3Dvl1t09ssgJbPTXSFiZu+1Xko5E /mD09jpuWTyQeciN8gYIL3+HO0xv2RVqwW/PdbVCGEbkRzlTZ+55bJG5lZvsfy1sz02X mCetAfH9PYlAK/40wC9HyQPnI5IlBNL21hjAFBjauE6h1kcp3BVTtMvDw3fTLFqwCDKD l6AA== X-Gm-Message-State: AD7BkJJvH/70Ds9Uxtov2Yg0+RejXjYkzppvFWZs/UpmOaXmU8aSsEv3FS/8tlIiWbxWRDBkMs2a9IN+D6a5qA== MIME-Version: 1.0 X-Received: by 10.194.83.42 with SMTP id n10mr3409338wjy.20.1457610933798; Thu, 10 Mar 2016 03:55:33 -0800 (PST) Received: by 10.28.31.143 with HTTP; Thu, 10 Mar 2016 03:55:33 -0800 (PST) In-Reply-To: References: <56E045C8.1040000@vangyzen.net> Date: Thu, 10 Mar 2016 11:55:33 +0000 Message-ID: Subject: Re: EFI zfs loader and beadm? From: krad To: Andrey Fesenko Cc: Eric van Gyzen , "freebsd-hackers@freebsd.org" , freebsd-current X-Mailman-Approved-At: Thu, 10 Mar 2016 13:09:33 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 11:55:35 -0000 presumably it boots now? On 10 March 2016 at 11:01, Andrey Fesenko wrote: > On Thu, Mar 10, 2016 at 1:49 PM, krad wrote: > > Make sure you are running the latest snapshot of current or 10.3 as > well, as > > the MFC commits were in early February for 10-stable > > > >> > >> If remove efiwpool/ROOT/init/boot and copy his content on > >> efiwpool/ROOT/init my scheme work fine too. > >> /usr /var /home and other included in BE for consistent boot system > >> (CURRENT world may not boot with kernel other rev), and old home > >> snapshot sometimes useful for backup/restore > >> _______________________________________________ > > % uname -a > FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296548: > Wed Mar 9 01:16:17 MSK 2016 > root@des.local:/usr/obj/usr/src/sys/X220 amd64 > From owner-freebsd-hackers@freebsd.org Thu Mar 10 15:11:11 2016 Return-Path: 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 B89E1ACB404; Thu, 10 Mar 2016 15:11:11 +0000 (UTC) (envelope-from kraduk@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 4954511BE; Thu, 10 Mar 2016 15:11:11 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: by mail-wm0-x236.google.com with SMTP id l68so32831211wml.1; Thu, 10 Mar 2016 07:11:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=o0sEDbbUocEEe07HSk0K8gxre3V2u1IKObtqn6xyJe4=; b=pI1CVEO2+ynrqU7tP5Hfy6VyNfzQ2Gt7pdy1RINc2l0oa1gKdF9emb98wjRFFwoFiE q3oW1renG77Jyl281VhVxgF3hCJXVDfQbsU1LVzmXJUxeU+N5suqLuhhUYkyzwm+yrJ1 oXyJY7xcGn6v7TFlsFT63byBBPqeJEmxGYIhM8QT3YmrKP8q8kQ6SDvncKH+CDhJWvSV kKlbB7VAW3eNdnVINWy5A45Tu5FvHQ0l0Ls7CFvZrEB8DMbPCZa8FwFqWY8V1GLyLGDZ ohkwnupxemAz0WJviTAYi90iyJFe0URTOqkcyXoDo6pzY+ytz1Ibdd2EXrc3yKBltGw6 HRcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=o0sEDbbUocEEe07HSk0K8gxre3V2u1IKObtqn6xyJe4=; b=MCXhqbqit4NDong+9XDj0o3UC5vfTMUwolXiDfkTzP12+XMQV3Y4XOZBdbpUCDOKQt x50MxJCElckSh26a7FPtVsPHhKQhm/F4I1yaXWhcWxZApCMLcoyUdZxifbV58y502m49 ngX5HRacqTluoYM3OiVk/HhU5MEDNr04uB7Ccekk+oSJCCwEtFcAEaCXrbdot7KCBLzg 6ANri4AS8yGEjBUoUQMYEYvUuVgbXXuj4hDyExl0CNoGjedoGUX15OQXuwaBZ3ORo0Y0 Bor97VxQY0msAL2F7oeENGIJ2MCiggx8UipWdDTPJTK/J8Gc953FYkU8EIbSgmxzhCpa gG9Q== X-Gm-Message-State: AD7BkJKHyzmjNMEn9Y0UcOIKYw+pdGTeolLaJUKNTiCR4TV6Elvm3O1CSHJKJulMge+qzyBy6yqRo1hQWnf/cw== MIME-Version: 1.0 X-Received: by 10.28.17.141 with SMTP id 135mr4854313wmr.48.1457622669650; Thu, 10 Mar 2016 07:11:09 -0800 (PST) Received: by 10.28.31.143 with HTTP; Thu, 10 Mar 2016 07:11:09 -0800 (PST) In-Reply-To: References: <56E045C8.1040000@vangyzen.net> Date: Thu, 10 Mar 2016 15:11:09 +0000 Message-ID: Subject: Re: EFI zfs loader and beadm? From: krad To: Andrey Fesenko Cc: Eric van Gyzen , "freebsd-hackers@freebsd.org" , freebsd-current X-Mailman-Approved-At: Thu, 10 Mar 2016 15:26:36 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 15:11:11 -0000 As Eric said you cant have /boot on a separate dataset as the whole loader bootstrap isnt designed too look for it on the dataset defined by bootfs. Remember no other datasets are mounted at that stage of the bootstrap. You could maybe bodge something by manually playing around with the bootfs property, symlinks and rootfs variables in the loader.conf. But why would you want to do this? It's more work and non standard, and will break a lot? On 10 March 2016 at 12:11, Andrey Fesenko wrote: > On Thu, Mar 10, 2016 at 2:55 PM, krad wrote: > > presumably it boots now? > > > > On 10 March 2016 at 11:01, Andrey Fesenko wrote: > >> > >> On Thu, Mar 10, 2016 at 1:49 PM, krad wrote: > >> > Make sure you are running the latest snapshot of current or 10.3 as > >> > well, as > >> > the MFC commits were in early February for 10-stable > >> > > >> >> > >> >> If remove efiwpool/ROOT/init/boot and copy his content on > >> >> efiwpool/ROOT/init my scheme work fine too. > >> >> /usr /var /home and other included in BE for consistent boot system > >> >> (CURRENT world may not boot with kernel other rev), and old home > >> >> snapshot sometimes useful for backup/restore > >> >> _______________________________________________ > >> > >> % uname -a > >> FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296548: > >> Wed Mar 9 01:16:17 MSK 2016 > >> root@des.local:/usr/obj/usr/src/sys/X220 amd64 > > > > > > My current working config > % mount > efiwpool/ROOT/init0 on / (zfs, local, noatime, nfsv4acls) > devfs on /dev (devfs, local, multilabel) > efiwpool/ROOT/init0/tmp on /tmp (zfs, local, noatime, nosuid, nfsv4acls) > efiwpool/ROOT/init0/usr on /usr (zfs, local, noatime, nfsv4acls) > efiwpool/ROOT/init0/usr/home on /usr/home (zfs, local, noatime, nfsv4acls) > efiwpool/ROOT/init0/var on /var (zfs, local, noatime, nfsv4acls) > efiwpool/ROOT/init0/var/crash on /var/crash (zfs, local, noatime, > noexec, nosuid, nfsv4acls) > efiwpool/ROOT/init0/var/db on /var/db (zfs, local, noatime, noexec, > nosuid, nfsv4acls) > efiwpool/ROOT/init0/var/db/pkg on /var/db/pkg (zfs, local, noatime, > nosuid, nfsv4acls) > efiwpool/ROOT/init0/var/db/tlpkg on /var/db/tlpkg (zfs, local, > noatime, nosuid, nfsv4acls) > efiwpool/ROOT/init0/var/empty on /var/empty (zfs, local, noatime, > noexec, nosuid, read-only, nfsv4acls) > efiwpool/ROOT/init0/var/log on /var/log (zfs, local, noatime, noexec, > nosuid, nfsv4acls) > efiwpool/ROOT/init0/var/mail on /var/mail (zfs, local, noatime, > noexec, nosuid, nfsv4acls) > efiwpool/ROOT/init0/var/run on /var/run (zfs, local, noatime, noexec, > nosuid, nfsv4acls) > efiwpool/ROOT/init0/var/tmp on /var/tmp (zfs, local, noatime, nosuid, > nfsv4acls) > > => 40 234441568 ada1 GPT (112G) > 40 1600 1 efi (800K) > 1640 234439960 2 freebsd-zfs (112G) > 234441600 8 - free - (4.0K) > > % zfs get -r mountpoint efiwpool > NAME PROPERTY > VALUE SOURCE > efiwpool mountpoint none > local > efiwpool/ROOT mountpoint none > inherited from efiwpool > efiwpool/ROOT/init mountpoint > legacy local > efiwpool/ROOT/init/tmp mountpoint /tmp > local > .... > > This work fine, booted, beadm create new env, activate them, see boot > menu and select BE. > > % beadm list > BE Active Mountpoint Space Created > init - - 420.7M 2016-03-09 02:57 > init0 NR / 35.9G 2016-03-10 05:00 > > If i'm add separate dataset for /boot (efiwpool/ROOT/init0/boot) > system not booted, efi loader (first stage) see only my pool, not > found /boot/loader.efi > From owner-freebsd-hackers@freebsd.org Thu Mar 10 15:38:54 2016 Return-Path: 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 9C70EACA1D7; Thu, 10 Mar 2016 15:38:54 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 574053E0; Thu, 10 Mar 2016 15:38:54 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: by mail-qg0-x231.google.com with SMTP id u110so73436369qge.3; Thu, 10 Mar 2016 07:38:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=lgVWkPrWP1XWoPa+dj0908s7trRWSBUtAulmXbbAkzU=; b=A+cdOf7Jy57No0ZKMCYhBsybsMM+7oLEEXHel6QaetiY35q0k3HQmWA2PXgqlfJGSs wnVypRt3Ve26Ucg+vAeZ2OF/YRTxuYbsoJWN/VpzU/tq+0ochL5OAN2yCtwtDBc+BHH1 OMFGEVf/b+gd9q1xI4y04goDoCI1skF+pybOZy9/CnDXvwaVHmFhESRdof+2qsjn+y8D Id/0cbz+w4u4TXxKUI08Qh8+b6Lu+AZAW2sarv2QsEt2Btd1FiehRP1DJe+z3W723Lu3 a2DP9Y58eXBT1z3FF0FZzfRbtVfB4VgtY4Y54LqKinqr6xUVEfeXspbkCZrI9NtWGLRB 3+TQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=lgVWkPrWP1XWoPa+dj0908s7trRWSBUtAulmXbbAkzU=; b=MKh70oeLGZ2VOk8R9jHvqwV0lNgN42lHrbfeUiy4nSlV31LqL7lFvcgmZNyHm/rrGz elMLwfX3UOe0fvCaEq+aUdzmysD6G3/tvIjNctluinnDxwS67Y9lQxQ2Sp6hRCLaKqrC bcuOfsiBPfGfMLqtR7K/zDWtVu1F+b1PMfL19ujOaO2I3vlxSQaRLbxDhKASvSEOozsx SnindIX7QeNmfD1YUgijkZFOPjvqNuauLLi3AaAHO0hhhtc0G4P/Zu/0nBmgAG/eY5fo 3RB/cMRk57kUnkIelnM1cCLsyYjmqzydyHNAVu4tMoFLgMmZ6a5m+xK4bdjP1QPpdqXA FVCQ== X-Gm-Message-State: AD7BkJKeOzKCy7RbqsOJV5+NQSDY4L3Cc8JoKMhTximC4hmaVPCwUGGMNBHiyaXqt9pu1mXCVNYuD5wcVFsuMg== MIME-Version: 1.0 X-Received: by 10.140.19.52 with SMTP id 49mr4933972qgg.103.1457624333143; Thu, 10 Mar 2016 07:38:53 -0800 (PST) Received: by 10.55.106.5 with HTTP; Thu, 10 Mar 2016 07:38:53 -0800 (PST) In-Reply-To: References: <56E045C8.1040000@vangyzen.net> Date: Thu, 10 Mar 2016 18:38:53 +0300 Message-ID: Subject: Re: EFI zfs loader and beadm? From: Andrey Fesenko To: krad Cc: Eric van Gyzen , "freebsd-hackers@freebsd.org" , freebsd-current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 15:38:54 -0000 On Thu, Mar 10, 2016 at 6:11 PM, krad wrote: > As Eric said you cant have /boot on a separate dataset as the whole loader > bootstrap isnt designed too look for it on the dataset defined by bootfs. > Remember no other datasets are mounted at that stage of the bootstrap. > > You could maybe bodge something by manually playing around with the bootfs > property, symlinks and rootfs variables in the loader.conf. But why would > you want to do this? It's more work and non standard, and will break a lot? > > > > On 10 March 2016 at 12:11, Andrey Fesenko wrote: >> >> On Thu, Mar 10, 2016 at 2:55 PM, krad wrote: >> > presumably it boots now? >> > >> > On 10 March 2016 at 11:01, Andrey Fesenko wrote: >> >> >> >> On Thu, Mar 10, 2016 at 1:49 PM, krad wrote: >> >> > Make sure you are running the latest snapshot of current or 10.3 as >> >> > well, as >> >> > the MFC commits were in early February for 10-stable >> >> > >> >> >> >> >> >> If remove efiwpool/ROOT/init/boot and copy his content on >> >> >> efiwpool/ROOT/init my scheme work fine too. >> >> >> /usr /var /home and other included in BE for consistent boot system >> >> >> (CURRENT world may not boot with kernel other rev), and old home >> >> >> snapshot sometimes useful for backup/restore >> >> >> _______________________________________________ >> >> >> >> % uname -a >> >> FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296548: >> >> Wed Mar 9 01:16:17 MSK 2016 >> >> root@des.local:/usr/obj/usr/src/sys/X220 amd64 >> > >> > >> >> My current working config >> % mount >> .... >> >> This work fine, booted, beadm create new env, activate them, see boot >> menu and select BE. >> >> % beadm list >> BE Active Mountpoint Space Created >> init - - 420.7M 2016-03-09 02:57 >> init0 NR / 35.9G 2016-03-10 05:00 >> >> If i'm add separate dataset for /boot (efiwpool/ROOT/init0/boot) >> system not booted, efi loader (first stage) see only my pool, not >> found /boot/loader.efi > > It probably does not matter, as bootfs have snapshots (BE), just wanted to make it more clear (having taken significant mountpoint /boot, /usr, /var... in zfs dataset) and was surprised why the system does not boot It is clear that as long as the functionality is experimental and under development, but would like to see where the full instructions on its implementation / restrictions, at least as early as has been described https://wiki.freebsd.org/RootOnZFS From owner-freebsd-hackers@freebsd.org Thu Mar 10 19:23:59 2016 Return-Path: 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 93CD2ACA9CA; Thu, 10 Mar 2016 19:23:59 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 22E85B24; Thu, 10 Mar 2016 19:23:58 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTPS id u2AJNqOp051530 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 10 Mar 2016 20:23:52 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id u2AJNpH3051527; Thu, 10 Mar 2016 20:23:51 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Thu, 10 Mar 2016 20:23:51 +0100 (CET) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: Andrey Fesenko cc: "freebsd-hackers@freebsd.org" , freebsd-current Subject: Re: EFI zfs loader and beadm? In-Reply-To: Message-ID: References: <56E045C8.1040000@vangyzen.net> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED, AWL autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.fig.ol.no Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 19:23:59 -0000 On Thu, 10 Mar 2016 18:38+0300, Andrey Fesenko wrote: > On Thu, Mar 10, 2016 at 6:11 PM, krad wrote: > > As Eric said you cant have /boot on a separate dataset as the whole loader > > bootstrap isnt designed too look for it on the dataset defined by bootfs. > > Remember no other datasets are mounted at that stage of the bootstrap. > > > > You could maybe bodge something by manually playing around with the bootfs > > property, symlinks and rootfs variables in the loader.conf. But why would > > you want to do this? It's more work and non standard, and will break a lot? > > > > > > > > On 10 March 2016 at 12:11, Andrey Fesenko wrote: > >> > >> On Thu, Mar 10, 2016 at 2:55 PM, krad wrote: > >> > presumably it boots now? > >> > > >> > On 10 March 2016 at 11:01, Andrey Fesenko wrote: > >> >> > >> >> On Thu, Mar 10, 2016 at 1:49 PM, krad wrote: > >> >> > Make sure you are running the latest snapshot of current or 10.3 as > >> >> > well, as > >> >> > the MFC commits were in early February for 10-stable > >> >> > > >> >> >> > >> >> >> If remove efiwpool/ROOT/init/boot and copy his content on > >> >> >> efiwpool/ROOT/init my scheme work fine too. > >> >> >> /usr /var /home and other included in BE for consistent boot system > >> >> >> (CURRENT world may not boot with kernel other rev), and old home > >> >> >> snapshot sometimes useful for backup/restore > >> >> >> _______________________________________________ > >> >> > >> >> % uname -a > >> >> FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296548: > >> >> Wed Mar 9 01:16:17 MSK 2016 > >> >> root@des.local:/usr/obj/usr/src/sys/X220 amd64 > >> > > >> > > >> > >> My current working config > >> % mount > >> .... > >> > >> This work fine, booted, beadm create new env, activate them, see boot > >> menu and select BE. > >> > >> % beadm list > >> BE Active Mountpoint Space Created > >> init - - 420.7M 2016-03-09 02:57 > >> init0 NR / 35.9G 2016-03-10 05:00 > >> > >> If i'm add separate dataset for /boot (efiwpool/ROOT/init0/boot) > >> system not booted, efi loader (first stage) see only my pool, not > >> found /boot/loader.efi > > > > > > It probably does not matter, as bootfs have snapshots (BE), just > wanted to make it more clear (having taken significant mountpoint > /boot, /usr, /var... in zfs dataset) and was surprised why the system > does not boot > > It is clear that as long as the functionality is experimental and > under development, but would like to see where the full instructions > on its implementation / restrictions, at least as early as has been > described https://wiki.freebsd.org/RootOnZFS If you keep /boot as a separate dataset/filesystem, with efiwpool/ROOT/init0/boot as the given bootfs, then boot1.efi will not see a /boot directory inside that dataset. The files and directories from /boot will be presented as living in /, the local root directory of that dataset. You could create a /boot/boot symlink pointing to . (dot), but it's better to let /boot be part of the regular boot environment, pretty similar to what you would find on a UFS system using a separate root filesystem. -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ From owner-freebsd-hackers@freebsd.org Thu Mar 10 20:18:22 2016 Return-Path: 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 D604EACB7DA for ; Thu, 10 Mar 2016 20:18:22 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (relay02.stack.nl [IPv6:2001:610:1108:5010::104]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mailhost.stack.nl", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A39FE3BC for ; Thu, 10 Mar 2016 20:18:22 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from toad2.stack.nl (toad2.stack.nl [IPv6:2001:610:1108:5010::161]) by mx1.stack.nl (Postfix) with ESMTP id 9A8B23592FB; Thu, 10 Mar 2016 21:18:19 +0100 (CET) Received: by toad2.stack.nl (Postfix, from userid 1677) id 70F99892D0; Thu, 10 Mar 2016 21:18:19 +0100 (CET) Date: Thu, 10 Mar 2016 21:18:19 +0100 From: Jilles Tjoelker To: C =?iso-8859-1?Q?Bergstr=F6m?= Cc: Jason Hellenthal , "freebsd-hackers@freebsd.org" , Brendan Sechter Subject: Re: FreeBSD sh on Linux? Message-ID: <20160310201819.GA5821@stack.nl> References: <8EC0DC6F-FA0D-4B8D-AECE-F1F797EE4D56@dataix.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 20:18:22 -0000 On Wed, Mar 09, 2016 at 08:27:05PM +0700, C Bergström wrote: > On Wed, Mar 9, 2016 at 8:13 PM, Jason Hellenthal > wrote: > > On Mar 9, 2016, at 02:06, Brendan Sechter wrote: > > > Is there any reason why FreeBSD sh can't be used on Linux? dash > > > is not a suitable login shell and bash is GNU. You'd need to do some work to make it compile. There is a package called libbsd which should be helpful. The filename completion in FreeBSD sh also uses a FreeBSD-local patch to libedit. This will be problematic if you want to maintain a package in a distribution. > > It's just the ash(1) shell with a few modifications that's a little > > more standard than most. Shouldn't be any reason why it can't There are quite a few bugfixes, features and performance improvements that are in FreeBSD sh and not in most other ash variants, such as UTF-8 support, $'...' to embed control characters and Unicode more easily, simple command substitutions without fork() and vfork() use. Therefore, I think the original question is reasonable, if the request is for a scripting shell (including for system() and make). > /* not meaning to be a troll */ > If you're going down this route - there's also ksh93 from solaris, > which may be easy to extract (or maybe has done so already.. not sure) > in my experience it's that nice balance between bare minimum sh and > bash. ksh93 is in ports. I think it is more rather than less featureful than bash, though. It has programming features such as lexically-scoped variables and user-defined data types. Interactive features are a bit more limited. It is quite fast as well. Downsides are that it can be buggy, development has slowed down, commonly available versions are quite incompatible with other shells and the programming features are still not nearly as good as more modern non-shell programming languages such as Python. > There's also fish and zsh if you want tons of features.. I think those are better choices for interactive use. There is also mksh which is in between FreeBSD sh and bash in features. I don't like it for interactive use because it does not support editing a very long logical line such as a for loop on multiple physical lines, but you may not mind that. -- Jilles Tjoelker From owner-freebsd-hackers@freebsd.org Fri Mar 11 09:37:36 2016 Return-Path: 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 9D85CACBECD for ; Fri, 11 Mar 2016 09:37:36 +0000 (UTC) (envelope-from bharghav2947@gmail.com) Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com [IPv6:2a00:1450:4010:c04::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 27AE91321 for ; Fri, 11 Mar 2016 09:37:36 +0000 (UTC) (envelope-from bharghav2947@gmail.com) Received: by mail-lb0-x22d.google.com with SMTP id xr8so142998638lbb.1 for ; Fri, 11 Mar 2016 01:37:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=sZOcsLTA3agV0C54rVdKAfRaC+zWZDN34Dxu5RnSrKw=; b=u0oCHYIlfbzS6l9ub1ykPHn/kad4DnSKHYTvpejTlQGnYPc64+WGVo8Rh+AYkmGkfT VXKphxepMvMljiy2PFqoHCgsoB9IGMXgwJ8hO7pA2FgvuLYR2K7saULgK2vv2Ep3S/q5 +Q8tfV2Pw1rQE0RQ9iCwEtOoJf7xSk15s58PissGThnb421LPX9tEFk9vco+4lXkwWU6 foFVkKuH60QqBwjnqGV9Pzt6RfXZ6/xauCREcMDTYoLlssxTj3eYNq/Pgv0ryEGfzLro 4/pWL7trMUtsLf8+WPiLXDyB+iSHhhigDgM3YJI9BW12s7LQDjM4PWuwhrSSHM0+rYAo IbeQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=sZOcsLTA3agV0C54rVdKAfRaC+zWZDN34Dxu5RnSrKw=; b=VuFYytBSbSxLe9Fk7zu0r8ZWLIi33iAD+s97XX5FIeYcmosxK41XKjITf4G/17FmNG GEyo7HKd3ujKx+3QJcPJGft1vXI2ijH8UcEn5ayoRt6/O0ufTKLz/uKIwg+sk+zHSndt PS0UzgfO16MQS1370+/tRXXMOX+zLKxd4Nhw2e9kaf+dMeA8FODiS0EYysvJI1J4e9uZ ExME4jy/tYuYkFuDDJCxf5B53KNs4jKmwg++GtUCuitSoQDcFpGNkj3GKbsXokBfQpNV L/mB61u3Dxh4GsQ7jtKD3miS9j0qRiC6roDbDQV+GfA9Z2YxKFVQDnXQDk8hyzjtRy1f D3FQ== X-Gm-Message-State: AD7BkJJuoZV1Ku020ev079B8sjxB+6eEgk2060PLikpByukCLpuOmpZ6NZiTUqOgUN81oMXs9AM9E7RMFv6p/w== MIME-Version: 1.0 X-Received: by 10.112.126.162 with SMTP id mz2mr2776982lbb.71.1457689054038; Fri, 11 Mar 2016 01:37:34 -0800 (PST) Received: by 10.25.196.196 with HTTP; Fri, 11 Mar 2016 01:37:33 -0800 (PST) Date: Fri, 11 Mar 2016 15:07:33 +0530 Message-ID: Subject: View about passing IPC pointer to the child process from a prent process. From: pavan teja To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 09:37:36 -0000 Hello everyone, I'm right now designing my project idea now I'm confused with a major idea which was implemented differently in different IPC meachanisms. Should a child process be allowed to share a IPC file descriptor from a parent process.Obviously it would be shared since file descriptores passed down.But what if the IPC mechanism puts a restriction on it .That even though it acquired the file descriptor it cannot participate with the file descriptor created by parent rather it shuld make its own connection to the IPC module . Please lemme the pros and cons of the above mechanism. Thank You. From owner-freebsd-hackers@freebsd.org Fri Mar 11 10:00:34 2016 Return-Path: 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 4D34AACC9D1; Fri, 11 Mar 2016 10:00:34 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: from mail-qg0-x235.google.com (mail-qg0-x235.google.com [IPv6:2607:f8b0:400d:c04::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 058FF687; Fri, 11 Mar 2016 10:00:34 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: by mail-qg0-x235.google.com with SMTP id u110so93791342qge.3; Fri, 11 Mar 2016 02:00:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-transfer-encoding; bh=apbuhY39hl/OMjMpwv+ebLv/4IKyhUX4+pRosHbE/Jg=; b=x/y1NpS9Lf7i3juL7serN/Pd3pqhHGX80r+HB7a+Fan6qbSbvKmE7IzSOrP+eeb8jP aTZXAskhLFCAUvRpXgUfm+TLEMdjCh2VJQ7kLsRUPCGQDxoCfhSpDsjJxuJda/0eu7Jl EaFF/3aNylq7vJ2OSR+D0JLHpQQy4dafUJ/Q3bSIYAfRzryFvtfLIxD1nI/FxJYE1NYI WZCpVBK4Dyy7cYGGPJc8/SzKQ/F8F2skIVYtO4qp0Rzx7u97DkRX+4UH8rAdkBL4pfpy 8xE6i9ZXrNXcMnPxqALHEu1LHPzL6qZZPzSNt2A2elhIQaQizacWKX2soqYaNCUh+laa WBbw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=apbuhY39hl/OMjMpwv+ebLv/4IKyhUX4+pRosHbE/Jg=; b=huUhSvXovNooTeAIrj3nQmGvc43VtYH5GxejcyLAtiylRkcdJtvDAE0etS4wCm7WzT ZC07JG5hV2gpm7W9KS9O6mo/+n/gyBkSikW/jIyogk+FYwT4fEZXH/kADo4kzunMw40H 0X7DfK9Y3hrAi2QnlSMQ08ogxEaznrj7Bz8oO8S58ldxaqbPXUh665OX0mJbjeNHR4tG qH5PM5WenseBxlMwLly/Jt1qB6Zb2r0vgmB+igks7f5crnfAEX0Tn26eFjTjrWy2n7Vm RpRw0Y63wfQGSKDFEBM8inLV2n4Vm7WPmmxhm7wL/kd7DHc7LmjPH5Suf/9b3wUNzy4J 6few== X-Gm-Message-State: AD7BkJIPvTrOf1cCwN/fMZNQqnmKKc0Z+p2Q3Txi/QM2iHD8FPmlesVS77xYE7itJkjrwL5iAmn8NaLyd+GOZw== MIME-Version: 1.0 X-Received: by 10.140.138.209 with SMTP id 200mr10888327qhk.100.1457690433032; Fri, 11 Mar 2016 02:00:33 -0800 (PST) Received: by 10.55.106.5 with HTTP; Fri, 11 Mar 2016 02:00:32 -0800 (PST) In-Reply-To: References: <56E045C8.1040000@vangyzen.net> Date: Fri, 11 Mar 2016 13:00:32 +0300 Message-ID: Subject: Re: EFI zfs loader and beadm? From: Andrey Fesenko To: krad Cc: =?UTF-8?Q?Trond_Endrest=C3=B8l?= , "freebsd-hackers@freebsd.org" , freebsd-current Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 10:00:34 -0000 On Fri, Mar 11, 2016 at 10:52 AM, krad wrote: > Its also worth pointing that if you decouple the userland from the kernel > files you no longer have a boot environment, as all the basic stuff to bo= ot > the os isn't contained within the bootfs. I'm still struggling to see why > /boot needs to be on a different dataset, its just a bit of a linuxism. > > On 10 March 2016 at 19:23, Trond Endrest=C3=B8l > wrote: >> >> On Thu, 10 Mar 2016 18:38+0300, Andrey Fesenko wrote: >> >> > On Thu, Mar 10, 2016 at 6:11 PM, krad wrote: >> > > As Eric said you cant have /boot on a separate dataset as the whole >> > > loader >> > > bootstrap isnt designed too look for it on the dataset defined by >> > > bootfs. >> > > Remember no other datasets are mounted at that stage of the bootstra= p. >> > > >> > > You could maybe bodge something by manually playing around with the >> > > bootfs >> > > property, symlinks and rootfs variables in the loader.conf. But why >> > > would >> > > you want to do this? It's more work and non standard, and will break= a >> > > lot? >> > > >> > > >> > > >> > > On 10 March 2016 at 12:11, Andrey Fesenko wrote= : >> > >> >> > >> On Thu, Mar 10, 2016 at 2:55 PM, krad wrote: >> > >> > presumably it boots now? >> > >> > >> > >> > On 10 March 2016 at 11:01, Andrey Fesenko >> > >> > wrote: >> > >> >> >> > >> >> On Thu, Mar 10, 2016 at 1:49 PM, krad wrote: >> > >> >> > Make sure you are running the latest snapshot of current or 10= .3 >> > >> >> > as >> > >> >> > well, as >> > >> >> > the MFC commits were in early February for 10-stable >> > >> >> > >> > >> >> >> >> > >> >> >> If remove efiwpool/ROOT/init/boot and copy his content on >> > >> >> >> efiwpool/ROOT/init my scheme work fine too. >> > >> >> >> /usr /var /home and other included in BE for consistent boot >> > >> >> >> system >> > >> >> >> (CURRENT world may not boot with kernel other rev), and old >> > >> >> >> home >> > >> >> >> snapshot sometimes useful for backup/restore >> > >> >> >> _______________________________________________ >> > >> >> >> > >> >> % uname -a >> > >> >> FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 >> > >> >> r296548: >> > >> >> Wed Mar 9 01:16:17 MSK 2016 >> > >> >> root@des.local:/usr/obj/usr/src/sys/X220 amd64 >> > >> > >> > >> > >> > >> >> > >> My current working config >> > >> % mount >> > >> .... >> > >> >> > >> This work fine, booted, beadm create new env, activate them, see bo= ot >> > >> menu and select BE. >> > >> >> > >> % beadm list >> > >> BE Active Mountpoint Space Created >> > >> init - - 420.7M 2016-03-09 02:57 >> > >> init0 NR / 35.9G 2016-03-10 05:00 >> > >> >> > >> If i'm add separate dataset for /boot (efiwpool/ROOT/init0/boot) >> > >> system not booted, efi loader (first stage) see only my pool, not >> > >> found /boot/loader.efi >> > > >> > > >> > >> > It probably does not matter, as bootfs have snapshots (BE), just >> > wanted to make it more clear (having taken significant mountpoint >> > /boot, /usr, /var... in zfs dataset) and was surprised why the system >> > does not boot >> > >> > It is clear that as long as the functionality is experimental and >> > under development, but would like to see where the full instructions >> > on its implementation / restrictions, at least as early as has been >> > described https://wiki.freebsd.org/RootOnZFS >> >> If you keep /boot as a separate dataset/filesystem, with >> efiwpool/ROOT/init0/boot as the given bootfs, then boot1.efi will not >> see a /boot directory inside that dataset. The files and directories >> from /boot will be presented as living in /, the local root directory >> of that dataset. >> >> You could create a /boot/boot symlink pointing to . (dot), but it's >> better to let /boot be part of the regular boot environment, pretty >> similar to what you would find on a UFS system using a separate root >> filesystem. >> why? On the contrary, my scheme involves the entire system as a single BE (including home) > linuxism Is unlikely, to rather an attempt to use all the features ZFS. ZFS also many possible settings for each dataset/FS (compression, atime, exec......) Probably for /boot many of them unnecessary, but such separate extra snapshots, can would not be harmful From owner-freebsd-hackers@freebsd.org Fri Mar 11 10:58:20 2016 Return-Path: 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 C7B4AACC197 for ; Fri, 11 Mar 2016 10:58:20 +0000 (UTC) (envelope-from moxalt@riseup.net) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B143519B9 for ; Fri, 11 Mar 2016 10:58:20 +0000 (UTC) (envelope-from moxalt@riseup.net) Received: from piha.riseup.net (unknown [10.0.1.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id A3B5D1A14B2 for ; Fri, 11 Mar 2016 10:51:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1457693516; bh=7ynyN8pYEvlbzZy30Shs5N6f8+z2SsMZoCFMjhUI5n0=; h=Date:From:To:Subject:In-Reply-To:References:From; b=kkS2h5t146SywdMb86uzc8Y7ipe8sdBmd6LpWsC4JTUJwkDalerbXZzbbmjvlieEG GnfNhPS3ghH9ldtkN23WEsL+BrzejEgNIT3Od2q0QnFvFg607ojKd/iWBXsLaOqvso F7SFG95+hi49bKIKzQeAwm1T3HsPimWZ0M5y6aqA= Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: moxalt) with ESMTPSA id CE1181C027A Date: Fri, 11 Mar 2016 13:50:14 +0300 From: Adam Wilson To: freebsd-hackers@freebsd.org Subject: Re: FreeBSD sh on Linux? Message-ID: <20160311135014.56c13258@riseup.net> In-Reply-To: <20160310201819.GA5821@stack.nl> References: <8EC0DC6F-FA0D-4B8D-AECE-F1F797EE4D56@dataix.net> <20160310201819.GA5821@stack.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: clamav-milter 0.99 at mx1.riseup.net X-Virus-Status: Clean X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 10:58:20 -0000 On Thu, 10 Mar 2016 21:18:19 +0100 Jilles Tjoelker wrote: > On Wed, Mar 09, 2016 at 08:27:05PM +0700, C Bergstr=C3=B6m wrote: > > On Wed, Mar 9, 2016 at 8:13 PM, Jason Hellenthal > > wrote: >=20 > > > On Mar 9, 2016, at 02:06, Brendan Sechter > > > wrote: >=20 > > > > Is there any reason why FreeBSD sh can't be used on Linux? dash > > > > is not a suitable login shell and bash is GNU. >=20 > You'd need to do some work to make it compile. There is a package > called libbsd which should be helpful. >=20 > The filename completion in FreeBSD sh also uses a FreeBSD-local patch > to libedit. This will be problematic if you want to maintain a > package in a distribution. >=20 > > > It's just the ash(1) shell with a few modifications that's a > > > little more standard than most. Shouldn't be any reason why it > > > can't >=20 > There are quite a few bugfixes, features and performance improvements > that are in FreeBSD sh and not in most other ash variants, such as > UTF-8 support, $'...' to embed control characters and Unicode more > easily, simple command substitutions without fork() and vfork() use. > Therefore, I think the original question is reasonable, if the > request is for a scripting shell (including for system() and make). >=20 > > /* not meaning to be a troll */ >=20 > > If you're going down this route - there's also ksh93 from solaris, > > which may be easy to extract (or maybe has done so already.. not > > sure) in my experience it's that nice balance between bare minimum > > sh and bash. >=20 > ksh93 is in ports. Debian includes the 1993 version of ksh in stable. Not sure if that's the same thing- the package name is ksh, but it conforms to the specification from 1993 as opposed to the 1988 version. From owner-freebsd-hackers@freebsd.org Fri Mar 11 07:52:10 2016 Return-Path: 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 63666ACB098; Fri, 11 Mar 2016 07:52:10 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 DFDFAA70; Fri, 11 Mar 2016 07:52:09 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: by mail-wm0-x22c.google.com with SMTP id l68so6495234wml.1; Thu, 10 Mar 2016 23:52:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=FWdOLhjCF/oVZDYnZTJPH0R1onxzRoA9K/o1KdDp22w=; b=JxPXlpkAAYYOEeq7dQVye40Ed6V6PvqH4jQYDTnj4Cxst3MxEMu5/j+GP+X4qUKijf ngFhbj3528u76U4X63TdpfJJ6mxZKBHhHyO5he9IU7llOH3arfC4Tyn9SP2MtVH3GUZ3 q2A8BQTIAsWqqUUYRiHknL+R1bgENJQwoQQQwrGq4HzLqCGFfdn6SF0olv5uYE8ZDtzK qnG13RMyGt81Q0rb/TpMwVaG7VKbu50/N86y8A5d7OeQZ29i+haKAJ9TRuEJjLdHGwIK 9t7qVPcR28ievxG2m+Gj3OP2HP4WfBmOfTsd5JBu64LmBwIngFYmTZ0ob7MyzjH12pFp Ri1Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=FWdOLhjCF/oVZDYnZTJPH0R1onxzRoA9K/o1KdDp22w=; b=S4kgp8E+aEx/lI6UItPvnoBRXk1nBStsibvMr0d+bBgh4eqj5RbNWWm5kIAV3DPBZ3 s5uEDobt2gLgcxbgVFEmHFvYPOdCYorJ1WJ/4D6w3P8CXGk+5DBiuNW7h8HONS8Ixhbd zbb3qf+EvyZaKWcQ1dVjgwbJPdLCNri27JzAIN+TC1vhsCU7wdgbOYdRXMNrTOmoFOMO Wmjn0N7EX4h+CKRHpKFgaSbrVN+FM+DRq6b7THWLGV1DLwpZx5ckiwxJPjn4br+KdPI8 iAuP05HYfdUBsjEoF1BCO4VqVNfpnnGJpXaGa0E7l/CwCD/KYt05brp5N3cFKDjD6PIL rjbA== X-Gm-Message-State: AD7BkJIp6uX5lD5+L3WHub8Mh22V/AIabnUMB9OmGr2s0hySqDBTR1w8FYZZQAiKNRtMA9GcKmRTbAIQzNDAwQ== MIME-Version: 1.0 X-Received: by 10.28.12.80 with SMTP id 77mr1251282wmm.19.1457682728173; Thu, 10 Mar 2016 23:52:08 -0800 (PST) Received: by 10.28.31.143 with HTTP; Thu, 10 Mar 2016 23:52:08 -0800 (PST) In-Reply-To: References: <56E045C8.1040000@vangyzen.net> Date: Fri, 11 Mar 2016 07:52:08 +0000 Message-ID: Subject: Re: EFI zfs loader and beadm? From: krad To: =?UTF-8?Q?Trond_Endrest=C3=B8l?= Cc: Andrey Fesenko , "freebsd-hackers@freebsd.org" , freebsd-current X-Mailman-Approved-At: Fri, 11 Mar 2016 12:31:23 +0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 07:52:10 -0000 Its also worth pointing that if you decouple the userland from the kernel files you no longer have a boot environment, as all the basic stuff to boot the os isn't contained within the bootfs. I'm still struggling to see why /boot needs to be on a different dataset, its just a bit of a linuxism. On 10 March 2016 at 19:23, Trond Endrest=C3=B8l < Trond.Endrestol@fagskolen.gjovik.no> wrote: > On Thu, 10 Mar 2016 18:38+0300, Andrey Fesenko wrote: > > > On Thu, Mar 10, 2016 at 6:11 PM, krad wrote: > > > As Eric said you cant have /boot on a separate dataset as the whole > loader > > > bootstrap isnt designed too look for it on the dataset defined by > bootfs. > > > Remember no other datasets are mounted at that stage of the bootstrap= . > > > > > > You could maybe bodge something by manually playing around with the > bootfs > > > property, symlinks and rootfs variables in the loader.conf. But why > would > > > you want to do this? It's more work and non standard, and will break = a > lot? > > > > > > > > > > > > On 10 March 2016 at 12:11, Andrey Fesenko wrote: > > >> > > >> On Thu, Mar 10, 2016 at 2:55 PM, krad wrote: > > >> > presumably it boots now? > > >> > > > >> > On 10 March 2016 at 11:01, Andrey Fesenko > wrote: > > >> >> > > >> >> On Thu, Mar 10, 2016 at 1:49 PM, krad wrote: > > >> >> > Make sure you are running the latest snapshot of current or 10.= 3 > as > > >> >> > well, as > > >> >> > the MFC commits were in early February for 10-stable > > >> >> > > > >> >> >> > > >> >> >> If remove efiwpool/ROOT/init/boot and copy his content on > > >> >> >> efiwpool/ROOT/init my scheme work fine too. > > >> >> >> /usr /var /home and other included in BE for consistent boot > system > > >> >> >> (CURRENT world may not boot with kernel other rev), and old > home > > >> >> >> snapshot sometimes useful for backup/restore > > >> >> >> _______________________________________________ > > >> >> > > >> >> % uname -a > > >> >> FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 > r296548: > > >> >> Wed Mar 9 01:16:17 MSK 2016 > > >> >> root@des.local:/usr/obj/usr/src/sys/X220 amd64 > > >> > > > >> > > > >> > > >> My current working config > > >> % mount > > >> .... > > >> > > >> This work fine, booted, beadm create new env, activate them, see boo= t > > >> menu and select BE. > > >> > > >> % beadm list > > >> BE Active Mountpoint Space Created > > >> init - - 420.7M 2016-03-09 02:57 > > >> init0 NR / 35.9G 2016-03-10 05:00 > > >> > > >> If i'm add separate dataset for /boot (efiwpool/ROOT/init0/boot) > > >> system not booted, efi loader (first stage) see only my pool, not > > >> found /boot/loader.efi > > > > > > > > > > It probably does not matter, as bootfs have snapshots (BE), just > > wanted to make it more clear (having taken significant mountpoint > > /boot, /usr, /var... in zfs dataset) and was surprised why the system > > does not boot > > > > It is clear that as long as the functionality is experimental and > > under development, but would like to see where the full instructions > > on its implementation / restrictions, at least as early as has been > > described https://wiki.freebsd.org/RootOnZFS > > If you keep /boot as a separate dataset/filesystem, with > efiwpool/ROOT/init0/boot as the given bootfs, then boot1.efi will not > see a /boot directory inside that dataset. The files and directories > from /boot will be presented as living in /, the local root directory > of that dataset. > > You could create a /boot/boot symlink pointing to . (dot), but it's > better to let /boot be part of the regular boot environment, pretty > similar to what you would find on a UFS system using a separate root > filesystem. > > -- > +-------------------------------+------------------------------------+ > | Vennlig hilsen, | Best regards, | > | Trond Endrest=C3=B8l, | Trond Endrest=C3=B8l, = | > | IT-ansvarlig, | System administrator, | > | Fagskolen Innlandet, | Gj=C3=B8vik Technical College, Norway, = | > | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | > | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | > +-------------------------------+------------------------------------+ > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " > From owner-freebsd-hackers@freebsd.org Fri Mar 11 13:18:50 2016 Return-Path: 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 68472ACB2CA for ; Fri, 11 Mar 2016 13:18:50 +0000 (UTC) (envelope-from bharghav2947@gmail.com) Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 75E3C875 for ; Fri, 11 Mar 2016 13:18:49 +0000 (UTC) (envelope-from bharghav2947@gmail.com) Received: by mail-lb0-x235.google.com with SMTP id xr8so150280409lbb.1 for ; Fri, 11 Mar 2016 05:18:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=mTw4QjjI7sKot7FUiX0dz9N+5OZapVr+b0Rdn9fT6uo=; b=r6Lw6vC5MjI5Uqd7wvHNMz6dV9zP0QbiprsJIE05BpGcbMyNKwX3gyqvPH44uVxQuH VipkpQFGDsu3zLjmIhoORlqCsRUbz0r1nuUkqyb5moiHbIUWlxkmiXswqtocqs3a5Xu0 4pZZ8MSQbN094BntjGxJFLWKud1TZb/vCOysbnMrEyzc04sGy5jL/MgdgtG1s1f62S9D Nn5b4toQA9EA6Edgs+Gob+3ZPT/NzPSxULkyezKWKB9RQ+/4GqWonQObZBWRzV4Ty1Zf GE3Q3BTMzIlIZ86Mx3rklGcrPBKY+VzJwg4x0AN+JZEqcja++QOrc2Fr0+zAmtnlOcbf 0O9Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=mTw4QjjI7sKot7FUiX0dz9N+5OZapVr+b0Rdn9fT6uo=; b=L0jjaD8dOUqeqXdpWVM1bx7q9aZmuxYlzl9nANc0h8cQXoFWuy0JvbhViX5qTZTaJ8 maohzTSIWjGIW5A60ns+vPoLG2i+RWS+kGyeclptCxhrYG7CLBJpoFN/ZI49eagfGnrW JhaqeAGjfCOt8J7yDGoTyrGAxOSj2pM1mHgwHdeJWZ6FVWxJ/koyR443QdbGQ8NMn9xH FCif/XUlxyv1uM6bc9133zmozzQEN7Yg3oqlIWIM7SrtkKWEIDK5s9kA362JOYyYNMcn U7lXz2zXQ13QvPxoYOEDM0bnrk2+Q5A23/7JgHyqZxRaiBxFoenWTE/6DPDckgyUOADk cV6g== X-Gm-Message-State: AD7BkJJBq4tkmVs0z32+YwF9zqYeLTDcAVBhMwHgGB/fIUcPzDv/2omaLRd6oPF5oUA8Mai1ysU+RAGq2GsXhw== MIME-Version: 1.0 X-Received: by 10.25.21.151 with SMTP id 23mr3248605lfv.89.1457702327035; Fri, 11 Mar 2016 05:18:47 -0800 (PST) Received: by 10.25.196.196 with HTTP; Fri, 11 Mar 2016 05:18:46 -0800 (PST) Received: by 10.25.196.196 with HTTP; Fri, 11 Mar 2016 05:18:46 -0800 (PST) Date: Fri, 11 Mar 2016 18:48:46 +0530 Message-ID: Subject: Re: Advantages of kdbus with enhanced capabilities feature From: pavan teja To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 13:18:50 -0000 Hello everyone, After getting a good understanding about capabilities and kdbus I find kdbus very much useful in the following situations: 1. Since kdbus is connection based and not port based .kdbus being a zero copy is highly useful as it reduces the in-between time for capabilities passing. 2.By using capabilities as the primary tokens for connecting to the kdbus the policy rules are no longer used for access restriction which are considered a threat allowing all processes with same uid to allow connecting and sending messages. We can merely use capabilties as the means to communicate with other processes. 3.If forking a parent process would lead to inheriting file descriptors ,when we want to compartmentalize our child process n restrict them to communicate, capabilities can be easily passed down to our child processes n this would be a great thing in terms of security. So entire security issues are handled by capabilities in a IPC mechanism so it's more secure. So adding kdbus into freebsd which uses capabilities over a wide range kdbus provides almost zero copying or one copying and further communication barrier can also be set by disallowing processes to connect a bus just by checking process capabilities not by merely DAC which looks for process uid. What do you think about my view please let me know . On 11-Mar-2016 5:30 PM, wrote: > Send freebsd-hackers mailing list submissions to > freebsd-hackers@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > or, via email, send a message with subject or body 'help' to > freebsd-hackers-request@freebsd.org > > You can reach the person managing the list at > freebsd-hackers-owner@freebsd.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-hackers digest..." > > Today's Topics: > > 1. Re: Converting DAC or policy Rules into Capsicum capabilities > (Mark Saad) > 2. Re: EFI zfs loader and beadm? (Andrey Fesenko) > 3. Re: EFI zfs loader and beadm? (krad) > 4. Re: EFI zfs loader and beadm? (krad) > 5. Re: EFI zfs loader and beadm? (krad) > 6. Re: EFI zfs loader and beadm? (Andrey Fesenko) > 7. Re: EFI zfs loader and beadm? (Trond Endrest?l) > 8. Re: FreeBSD sh on Linux? (Jilles Tjoelker) > 9. View about passing IPC pointer to the child process from a > prent process. (pavan teja) > 10. Re: EFI zfs loader and beadm? (Andrey Fesenko) > 11. Re: FreeBSD sh on Linux? (Adam Wilson) > > > ---------- Forwarded message ---------- > From: Mark Saad > To: pavan teja > Cc: freebsd-hackers@freebsd.org > Date: Thu, 10 Mar 2016 07:04:32 -0500 > Subject: Re: Converting DAC or policy Rules into Capsicum capabilities > Pavan > What is the use of kdbus ? It's been abandoned, > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D806558;msg=3D5 could= the > Mach ipc module from nextbsd be used ? > > > --- > Mark Saad | nonesuch@longcount.org > > > On Mar 10, 2016, at 3:50 AM, pavan teja wrote: > > > > Hello everyone, > > I'm right now working on Implementing KDBus project > into > > FreeBSD project .In the KDBus we have a set of policy rules by which we > can > > control the bus connectivity by other processes . If viewing from the > other > > side policy rules appeared to me similar to DAC the security mechanism > used > > in Linux . Can anyone suggest me a good way to convert these DAC rules > into > > capabilities .I want to replace these policy rules in KDBus in my desig= n > > and replace them with some capabilities . *Example for some policy rule= s > > are:* > > > > KDBUS_ITEM_NAME: str=3D'org.foo.bar' > > KDBUS_ITEM_POLICY_ACCESS: type=3DUSER, access=3DOWN, id=3D1000 > > KDBUS_ITEM_POLICY_ACCESS: type=3DUSER, access=3DTALK, id=3D1001 > > KDBUS_ITEM_POLICY_ACCESS: type=3DWORLD, access=3DSEE > > > > Please help me out by stating an example as how i can convert policy > > rules as these into some form of capabilities given to each process > > .This would be very helpful for my design. > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to " > freebsd-hackers-unsubscribe@freebsd.org" > > > > ---------- Forwarded message ---------- > From: Andrey Fesenko > To: krad > Cc: Eric van Gyzen , "freebsd-hackers@freebsd.org" < > freebsd-hackers@freebsd.org>, freebsd-current > > Date: Thu, 10 Mar 2016 15:11:02 +0300 > Subject: Re: EFI zfs loader and beadm? > On Thu, Mar 10, 2016 at 2:55 PM, krad wrote: > > presumably it boots now? > > > > On 10 March 2016 at 11:01, Andrey Fesenko wrote: > >> > >> On Thu, Mar 10, 2016 at 1:49 PM, krad wrote: > >> > Make sure you are running the latest snapshot of current or 10.3 as > >> > well, as > >> > the MFC commits were in early February for 10-stable > >> > > >> >> > >> >> If remove efiwpool/ROOT/init/boot and copy his content on > >> >> efiwpool/ROOT/init my scheme work fine too. > >> >> /usr /var /home and other included in BE for consistent boot system > >> >> (CURRENT world may not boot with kernel other rev), and old home > >> >> snapshot sometimes useful for backup/restore > >> >> _______________________________________________ > >> > >> % uname -a > >> FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296548: > >> Wed Mar 9 01:16:17 MSK 2016 > >> root@des.local:/usr/obj/usr/src/sys/X220 amd64 > > > > > > My current working config > % mount > efiwpool/ROOT/init0 on / (zfs, local, noatime, nfsv4acls) > devfs on /dev (devfs, local, multilabel) > efiwpool/ROOT/init0/tmp on /tmp (zfs, local, noatime, nosuid, nfsv4acls) > efiwpool/ROOT/init0/usr on /usr (zfs, local, noatime, nfsv4acls) > efiwpool/ROOT/init0/usr/home on /usr/home (zfs, local, noatime, nfsv4acls= ) > efiwpool/ROOT/init0/var on /var (zfs, local, noatime, nfsv4acls) > efiwpool/ROOT/init0/var/crash on /var/crash (zfs, local, noatime, > noexec, nosuid, nfsv4acls) > efiwpool/ROOT/init0/var/db on /var/db (zfs, local, noatime, noexec, > nosuid, nfsv4acls) > efiwpool/ROOT/init0/var/db/pkg on /var/db/pkg (zfs, local, noatime, > nosuid, nfsv4acls) > efiwpool/ROOT/init0/var/db/tlpkg on /var/db/tlpkg (zfs, local, > noatime, nosuid, nfsv4acls) > efiwpool/ROOT/init0/var/empty on /var/empty (zfs, local, noatime, > noexec, nosuid, read-only, nfsv4acls) > efiwpool/ROOT/init0/var/log on /var/log (zfs, local, noatime, noexec, > nosuid, nfsv4acls) > efiwpool/ROOT/init0/var/mail on /var/mail (zfs, local, noatime, > noexec, nosuid, nfsv4acls) > efiwpool/ROOT/init0/var/run on /var/run (zfs, local, noatime, noexec, > nosuid, nfsv4acls) > efiwpool/ROOT/init0/var/tmp on /var/tmp (zfs, local, noatime, nosuid, > nfsv4acls) > > =3D> 40 234441568 ada1 GPT (112G) > 40 1600 1 efi (800K) > 1640 234439960 2 freebsd-zfs (112G) > 234441600 8 - free - (4.0K) > > % zfs get -r mountpoint efiwpool > NAME PROPERTY > VALUE SOURCE > efiwpool mountpoint none > local > efiwpool/ROOT mountpoint none > inherited from efiwpool > efiwpool/ROOT/init mountpoint > legacy local > efiwpool/ROOT/init/tmp mountpoint /tmp > local > .... > > This work fine, booted, beadm create new env, activate them, see boot > menu and select BE. > > % beadm list > BE Active Mountpoint Space Created > init - - 420.7M 2016-03-09 02:57 > init0 NR / 35.9G 2016-03-10 05:00 > > If i'm add separate dataset for /boot (efiwpool/ROOT/init0/boot) > system not booted, efi loader (first stage) see only my pool, not > found /boot/loader.efi > > > > ---------- Forwarded message ---------- > From: krad > To: Andrey Fesenko > Cc: Eric van Gyzen , "freebsd-hackers@freebsd.org" < > freebsd-hackers@freebsd.org>, freebsd-current > > Date: Thu, 10 Mar 2016 10:49:36 +0000 > Subject: Re: EFI zfs loader and beadm? > Make sure you are running the latest snapshot of current or 10.3 as well, > as the MFC commits were in early February for 10-stable > > On 9 March 2016 at 16:01, Andrey Fesenko wrote: > > > On Wed, Mar 9, 2016 at 6:48 PM, Eric van Gyzen > wrote: > > > On 03/09/2016 09:40, Andrey Fesenko wrote: > > >> Hello, > > >> I'm test EFI boot ZFSroot with BE, this not support now? > > >> svn 2965489 > > >> > > >> If i build simplest system > > >> > > > http://blog.multiplay.co.uk/2015/12/freebsd-10-2-release-efi-zfs-root-boo= t/ > > >> > > >> # zfs get -r mountpoint efifpool > > >> NAME PROPERTY VALUE SOURCE > > >> efifpool mountpoint /mnt/efifpool default > > >> > > >> =3D> 40 30712240 da0 GPT (15G) > > >> 40 1600 1 efi (800K) > > >> 1640 30710632 2 freebsd-zfs (15G) > > >> 30712272 8 - free - (4.0K) > > >> > > >> system boot nice > > >> > > >> If make BE env > > >> > > >> # zfs get -r mountpoint efiwpool > > >> NAME PROPERTY VALUE > SOURCE > > >> efiwpool mountpoint none loc= al > > >> efiwpool/ROOT mountpoint none > > >> inherited from efiwpool > > >> efiwpool/ROOT/init mountpoint legacy loc= al > > >> efiwpool/ROOT/init@init mountpoint - - > > >> efiwpool/ROOT/init/boot mountpoint /media/boot loc= al > > >> efiwpool/ROOT/init/tmp mountpoint /media/tmp loc= al > > >> efiwpool/ROOT/init/usr mountpoint /media/usr loc= al > > >> efiwpool/ROOT/init/usr@init mountpoint - - > > >> efiwpool/ROOT/init/usr/home mountpoint /media/usr/home > > >> inherited from efiwpool/ROOT/init/usr > > >> efiwpool/ROOT/init/usr/home@init mountpoint - - > > >> efiwpool/ROOT/init/var mountpoint /media/var loc= al > > >> efiwpool/ROOT/init/var@init mountpoint - - > > >> efiwpool/ROOT/init/var/crash mountpoint /media/var/crash > > >> inherited from efiwpool/ROOT/init/var > > >> efiwpool/ROOT/init/var/db mountpoint /media/var/db > > >> inherited from efiwpool/ROOT/init/var > > >> efiwpool/ROOT/init/var/db/pkg mountpoint /media/var/db/pkg > > >> inherited from efiwpool/ROOT/init/var > > >> efiwpool/ROOT/init/var/empty mountpoint /media/var/empty > > >> inherited from efiwpool/ROOT/init/var > > >> efiwpool/ROOT/init/var/log mountpoint /media/var/log > > >> inherited from efiwpool/ROOT/init/var > > >> efiwpool/ROOT/init/var/mail mountpoint /media/var/mail > > >> inherited from efiwpool/ROOT/init/var > > >> efiwpool/ROOT/init/var/run mountpoint /media/var/run > > >> inherited from efiwpool/ROOT/init/var > > >> efiwpool/ROOT/init/var/tmp mountpoint /media/var/tmp > > >> inherited from efiwpool/ROOT/init/var > > >> > > >> system not boot. > > >> > > >> Not found /boot/loader.efi (in BE system real path > > >> efiwpool/ROOT/init/boot/loader.efi) if copy this efiwpool/ROOT/init > > >> (blank in BE system) loader found this (but not found /boot/kernel) = I > > >> can copy this and get a similar system > > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D192184#c15 (with > out > > >> msdos kernel part), but this ruin BE update mechanism > > > > > > Your dataset hierarchy is not what beadm expects. Specifically, you > > > have /boot separate from /, which I imagine is causing your problem. > > > /boot should be part of /. Also, you have several file systems in th= e > > > BE that are usually not in it; I doubt this is part of your boot > > > failure, though. > > > > > > For reference, here is my layout, which is mostly the same as the > > > default installation: > > > > > > NAME USED AVAIL REFER MOUNTPOINT > > > zroot 117G 108G 96K none > > > zroot/ROOT 14.8G 108G 96K none > > > zroot/ROOT/10.2 444K 108G 6.35G / > > > zroot/ROOT/103beta 14.8G 108G 8.75G / > > > zroot/ROOT/103beta1 8K 108G 8.17G / > > > zroot/ROOT/103beta3 8K 108G 8.75G / > > > zroot/home 97.8G 108G 94.9G /home > > > zroot/usr 3.36G 108G 96K /usr > > > zroot/usr/ports 985M 108G 736M /usr/ports > > > zroot/usr/src 2.40G 108G 2.19G /usr/src > > > zroot/var 2.19M 108G 96K /var > > > zroot/var/audit 96K 108G 96K /var/audit > > > zroot/var/crash 96K 108G 96K /var/crash > > > zroot/var/log 1.15M 108G 420K /var/log > > > zroot/var/mail 360K 108G 120K /var/mail > > > zroot/var/tmp 416K 108G 144K /var/tmp > > > > > > Eric > > > > If remove efiwpool/ROOT/init/boot and copy his content on > > efiwpool/ROOT/init my scheme work fine too. > > /usr /var /home and other included in BE for consistent boot system > > (CURRENT world may not boot with kernel other rev), and old home > > snapshot sometimes useful for backup/restore > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to " > freebsd-hackers-unsubscribe@freebsd.org" > > > > > > ---------- Forwarded message ---------- > From: krad > To: Andrey Fesenko > Cc: Eric van Gyzen , "freebsd-hackers@freebsd.org" < > freebsd-hackers@freebsd.org>, freebsd-current > > Date: Thu, 10 Mar 2016 11:55:33 +0000 > Subject: Re: EFI zfs loader and beadm? > presumably it boots now? > > On 10 March 2016 at 11:01, Andrey Fesenko wrote: > > > On Thu, Mar 10, 2016 at 1:49 PM, krad wrote: > > > Make sure you are running the latest snapshot of current or 10.3 as > > well, as > > > the MFC commits were in early February for 10-stable > > > > > >> > > >> If remove efiwpool/ROOT/init/boot and copy his content on > > >> efiwpool/ROOT/init my scheme work fine too. > > >> /usr /var /home and other included in BE for consistent boot system > > >> (CURRENT world may not boot with kernel other rev), and old home > > >> snapshot sometimes useful for backup/restore > > >> _______________________________________________ > > > > % uname -a > > FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296548: > > Wed Mar 9 01:16:17 MSK 2016 > > root@des.local:/usr/obj/usr/src/sys/X220 amd64 > > > > > > ---------- Forwarded message ---------- > From: krad > To: Andrey Fesenko > Cc: Eric van Gyzen , "freebsd-hackers@freebsd.org" < > freebsd-hackers@freebsd.org>, freebsd-current > > Date: Thu, 10 Mar 2016 15:11:09 +0000 > Subject: Re: EFI zfs loader and beadm? > As Eric said you cant have /boot on a separate dataset as the whole loade= r > bootstrap isnt designed too look for it on the dataset defined by bootfs. > Remember no other datasets are mounted at that stage of the bootstrap. > > You could maybe bodge something by manually playing around with the bootf= s > property, symlinks and rootfs variables in the loader.conf. But why woul= d > you want to do this? It's more work and non standard, and will break a lo= t? > > > > On 10 March 2016 at 12:11, Andrey Fesenko wrote: > > > On Thu, Mar 10, 2016 at 2:55 PM, krad wrote: > > > presumably it boots now? > > > > > > On 10 March 2016 at 11:01, Andrey Fesenko wrote: > > >> > > >> On Thu, Mar 10, 2016 at 1:49 PM, krad wrote: > > >> > Make sure you are running the latest snapshot of current or 10.3 a= s > > >> > well, as > > >> > the MFC commits were in early February for 10-stable > > >> > > > >> >> > > >> >> If remove efiwpool/ROOT/init/boot and copy his content on > > >> >> efiwpool/ROOT/init my scheme work fine too. > > >> >> /usr /var /home and other included in BE for consistent boot syst= em > > >> >> (CURRENT world may not boot with kernel other rev), and old home > > >> >> snapshot sometimes useful for backup/restore > > >> >> _______________________________________________ > > >> > > >> % uname -a > > >> FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296548: > > >> Wed Mar 9 01:16:17 MSK 2016 > > >> root@des.local:/usr/obj/usr/src/sys/X220 amd64 > > > > > > > > > > My current working config > > % mount > > efiwpool/ROOT/init0 on / (zfs, local, noatime, nfsv4acls) > > devfs on /dev (devfs, local, multilabel) > > efiwpool/ROOT/init0/tmp on /tmp (zfs, local, noatime, nosuid, nfsv4acls= ) > > efiwpool/ROOT/init0/usr on /usr (zfs, local, noatime, nfsv4acls) > > efiwpool/ROOT/init0/usr/home on /usr/home (zfs, local, noatime, > nfsv4acls) > > efiwpool/ROOT/init0/var on /var (zfs, local, noatime, nfsv4acls) > > efiwpool/ROOT/init0/var/crash on /var/crash (zfs, local, noatime, > > noexec, nosuid, nfsv4acls) > > efiwpool/ROOT/init0/var/db on /var/db (zfs, local, noatime, noexec, > > nosuid, nfsv4acls) > > efiwpool/ROOT/init0/var/db/pkg on /var/db/pkg (zfs, local, noatime, > > nosuid, nfsv4acls) > > efiwpool/ROOT/init0/var/db/tlpkg on /var/db/tlpkg (zfs, local, > > noatime, nosuid, nfsv4acls) > > efiwpool/ROOT/init0/var/empty on /var/empty (zfs, local, noatime, > > noexec, nosuid, read-only, nfsv4acls) > > efiwpool/ROOT/init0/var/log on /var/log (zfs, local, noatime, noexec, > > nosuid, nfsv4acls) > > efiwpool/ROOT/init0/var/mail on /var/mail (zfs, local, noatime, > > noexec, nosuid, nfsv4acls) > > efiwpool/ROOT/init0/var/run on /var/run (zfs, local, noatime, noexec, > > nosuid, nfsv4acls) > > efiwpool/ROOT/init0/var/tmp on /var/tmp (zfs, local, noatime, nosuid, > > nfsv4acls) > > > > =3D> 40 234441568 ada1 GPT (112G) > > 40 1600 1 efi (800K) > > 1640 234439960 2 freebsd-zfs (112G) > > 234441600 8 - free - (4.0K) > > > > % zfs get -r mountpoint efiwpool > > NAME PROPERTY > > VALUE SOURCE > > efiwpool mountpoint none > > local > > efiwpool/ROOT mountpoint none > > inherited from efiwpool > > efiwpool/ROOT/init mountpoint > > legacy local > > efiwpool/ROOT/init/tmp mountpoint /tmp > > local > > .... > > > > This work fine, booted, beadm create new env, activate them, see boot > > menu and select BE. > > > > % beadm list > > BE Active Mountpoint Space Created > > init - - 420.7M 2016-03-09 02:57 > > init0 NR / 35.9G 2016-03-10 05:00 > > > > If i'm add separate dataset for /boot (efiwpool/ROOT/init0/boot) > > system not booted, efi loader (first stage) see only my pool, not > > found /boot/loader.efi > > > > > > ---------- Forwarded message ---------- > From: Andrey Fesenko > To: krad > Cc: Eric van Gyzen , "freebsd-hackers@freebsd.org" < > freebsd-hackers@freebsd.org>, freebsd-current > > Date: Thu, 10 Mar 2016 18:38:53 +0300 > Subject: Re: EFI zfs loader and beadm? > On Thu, Mar 10, 2016 at 6:11 PM, krad wrote: > > As Eric said you cant have /boot on a separate dataset as the whole > loader > > bootstrap isnt designed too look for it on the dataset defined by bootf= s. > > Remember no other datasets are mounted at that stage of the bootstrap. > > > > You could maybe bodge something by manually playing around with the > bootfs > > property, symlinks and rootfs variables in the loader.conf. But why > would > > you want to do this? It's more work and non standard, and will break a > lot? > > > > > > > > On 10 March 2016 at 12:11, Andrey Fesenko wrote: > >> > >> On Thu, Mar 10, 2016 at 2:55 PM, krad wrote: > >> > presumably it boots now? > >> > > >> > On 10 March 2016 at 11:01, Andrey Fesenko wrote= : > >> >> > >> >> On Thu, Mar 10, 2016 at 1:49 PM, krad wrote: > >> >> > Make sure you are running the latest snapshot of current or 10.3 = as > >> >> > well, as > >> >> > the MFC commits were in early February for 10-stable > >> >> > > >> >> >> > >> >> >> If remove efiwpool/ROOT/init/boot and copy his content on > >> >> >> efiwpool/ROOT/init my scheme work fine too. > >> >> >> /usr /var /home and other included in BE for consistent boot > system > >> >> >> (CURRENT world may not boot with kernel other rev), and old hom= e > >> >> >> snapshot sometimes useful for backup/restore > >> >> >> _______________________________________________ > >> >> > >> >> % uname -a > >> >> FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296548= : > >> >> Wed Mar 9 01:16:17 MSK 2016 > >> >> root@des.local:/usr/obj/usr/src/sys/X220 amd64 > >> > > >> > > >> > >> My current working config > >> % mount > >> .... > >> > >> This work fine, booted, beadm create new env, activate them, see boot > >> menu and select BE. > >> > >> % beadm list > >> BE Active Mountpoint Space Created > >> init - - 420.7M 2016-03-09 02:57 > >> init0 NR / 35.9G 2016-03-10 05:00 > >> > >> If i'm add separate dataset for /boot (efiwpool/ROOT/init0/boot) > >> system not booted, efi loader (first stage) see only my pool, not > >> found /boot/loader.efi > > > > > > It probably does not matter, as bootfs have snapshots (BE), just > wanted to make it more clear (having taken significant mountpoint > /boot, /usr, /var... in zfs dataset) and was surprised why the system > does not boot > > It is clear that as long as the functionality is experimental and > under development, but would like to see where the full instructions > on its implementation / restrictions, at least as early as has been > described https://wiki.freebsd.org/RootOnZFS > > > > ---------- Forwarded message ---------- > From: "Trond Endrest=C3=B8l" > To: Andrey Fesenko > Cc: "freebsd-hackers@freebsd.org" , > freebsd-current > Date: Thu, 10 Mar 2016 20:23:51 +0100 (CET) > Subject: Re: EFI zfs loader and beadm? > On Thu, 10 Mar 2016 18:38+0300, Andrey Fesenko wrote: > > > On Thu, Mar 10, 2016 at 6:11 PM, krad wrote: > > > As Eric said you cant have /boot on a separate dataset as the whole > loader > > > bootstrap isnt designed too look for it on the dataset defined by > bootfs. > > > Remember no other datasets are mounted at that stage of the bootstrap= . > > > > > > You could maybe bodge something by manually playing around with the > bootfs > > > property, symlinks and rootfs variables in the loader.conf. But why > would > > > you want to do this? It's more work and non standard, and will break = a > lot? > > > > > > > > > > > > On 10 March 2016 at 12:11, Andrey Fesenko wrote: > > >> > > >> On Thu, Mar 10, 2016 at 2:55 PM, krad wrote: > > >> > presumably it boots now? > > >> > > > >> > On 10 March 2016 at 11:01, Andrey Fesenko > wrote: > > >> >> > > >> >> On Thu, Mar 10, 2016 at 1:49 PM, krad wrote: > > >> >> > Make sure you are running the latest snapshot of current or 10.= 3 > as > > >> >> > well, as > > >> >> > the MFC commits were in early February for 10-stable > > >> >> > > > >> >> >> > > >> >> >> If remove efiwpool/ROOT/init/boot and copy his content on > > >> >> >> efiwpool/ROOT/init my scheme work fine too. > > >> >> >> /usr /var /home and other included in BE for consistent boot > system > > >> >> >> (CURRENT world may not boot with kernel other rev), and old > home > > >> >> >> snapshot sometimes useful for backup/restore > > >> >> >> _______________________________________________ > > >> >> > > >> >> % uname -a > > >> >> FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 > r296548: > > >> >> Wed Mar 9 01:16:17 MSK 2016 > > >> >> root@des.local:/usr/obj/usr/src/sys/X220 amd64 > > >> > > > >> > > > >> > > >> My current working config > > >> % mount > > >> .... > > >> > > >> This work fine, booted, beadm create new env, activate them, see boo= t > > >> menu and select BE. > > >> > > >> % beadm list > > >> BE Active Mountpoint Space Created > > >> init - - 420.7M 2016-03-09 02:57 > > >> init0 NR / 35.9G 2016-03-10 05:00 > > >> > > >> If i'm add separate dataset for /boot (efiwpool/ROOT/init0/boot) > > >> system not booted, efi loader (first stage) see only my pool, not > > >> found /boot/loader.efi > > > > > > > > > > It probably does not matter, as bootfs have snapshots (BE), just > > wanted to make it more clear (having taken significant mountpoint > > /boot, /usr, /var... in zfs dataset) and was surprised why the system > > does not boot > > > > It is clear that as long as the functionality is experimental and > > under development, but would like to see where the full instructions > > on its implementation / restrictions, at least as early as has been > > described https://wiki.freebsd.org/RootOnZFS > > If you keep /boot as a separate dataset/filesystem, with > efiwpool/ROOT/init0/boot as the given bootfs, then boot1.efi will not > see a /boot directory inside that dataset. The files and directories > from /boot will be presented as living in /, the local root directory > of that dataset. > > You could create a /boot/boot symlink pointing to . (dot), but it's > better to let /boot be part of the regular boot environment, pretty > similar to what you would find on a UFS system using a separate root > filesystem. > > -- > +-------------------------------+------------------------------------+ > | Vennlig hilsen, | Best regards, | > | Trond Endrest=C3=B8l, | Trond Endrest=C3=B8l, = | > | IT-ansvarlig, | System administrator, | > | Fagskolen Innlandet, | Gj=C3=B8vik Technical College, Norway, = | > | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | > | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | > +-------------------------------+------------------------------------+ > > > ---------- Forwarded message ---------- > From: Jilles Tjoelker > To: "C Bergstr=C3=B6m" > Cc: Jason Hellenthal , " > freebsd-hackers@freebsd.org" , Brendan > Sechter > Date: Thu, 10 Mar 2016 21:18:19 +0100 > Subject: Re: FreeBSD sh on Linux? > On Wed, Mar 09, 2016 at 08:27:05PM +0700, C Bergstr=C3=B6m wrote: > > On Wed, Mar 9, 2016 at 8:13 PM, Jason Hellenthal > > wrote: > > > > On Mar 9, 2016, at 02:06, Brendan Sechter wrote: > > > > > Is there any reason why FreeBSD sh can't be used on Linux? dash > > > > is not a suitable login shell and bash is GNU. > > You'd need to do some work to make it compile. There is a package called > libbsd which should be helpful. > > The filename completion in FreeBSD sh also uses a FreeBSD-local patch to > libedit. This will be problematic if you want to maintain a package in a > distribution. > > > > It's just the ash(1) shell with a few modifications that's a little > > > more standard than most. Shouldn't be any reason why it can't > > There are quite a few bugfixes, features and performance improvements > that are in FreeBSD sh and not in most other ash variants, such as UTF-8 > support, $'...' to embed control characters and Unicode more easily, > simple command substitutions without fork() and vfork() use. Therefore, > I think the original question is reasonable, if the request is for a > scripting shell (including for system() and make). > > > /* not meaning to be a troll */ > > > If you're going down this route - there's also ksh93 from solaris, > > which may be easy to extract (or maybe has done so already.. not sure) > > in my experience it's that nice balance between bare minimum sh and > > bash. > > ksh93 is in ports. > > I think it is more rather than less featureful than bash, though. It has > programming features such as lexically-scoped variables and user-defined > data types. Interactive features are a bit more limited. It is quite > fast as well. > > Downsides are that it can be buggy, development has slowed down, > commonly available versions are quite incompatible with other shells and > the programming features are still not nearly as good as more modern > non-shell programming languages such as Python. > > > There's also fish and zsh if you want tons of features.. > > I think those are better choices for interactive use. > > There is also mksh which is in between FreeBSD sh and bash in features. > I don't like it for interactive use because it does not support editing > a very long logical line such as a for loop on multiple physical lines, > but you may not mind that. > > -- > Jilles Tjoelker > > > > ---------- Forwarded message ---------- > From: pavan teja > To: freebsd-hackers@freebsd.org > Cc: > Date: Fri, 11 Mar 2016 15:07:33 +0530 > Subject: View about passing IPC pointer to the child process from a prent > process. > Hello everyone, > I'm right now designing my project idea now I'm > confused with a major idea which was implemented differently in different > IPC meachanisms. > Should a child process be allowed to share a IPC > file descriptor from a parent process.Obviously it would be shared since > file descriptores passed down.But what if the IPC mechanism puts a > restriction on it .That even though it acquired the file descriptor it > cannot participate with the file descriptor created by parent rather it > shuld make its own connection to the IPC module . Please lemme the pros a= nd > cons of the above mechanism. > Thank You. > > > > ---------- Forwarded message ---------- > From: Andrey Fesenko > To: krad > Cc: "Trond Endrest=C3=B8l" , " > freebsd-hackers@freebsd.org" , > freebsd-current > Date: Fri, 11 Mar 2016 13:00:32 +0300 > Subject: Re: EFI zfs loader and beadm? > On Fri, Mar 11, 2016 at 10:52 AM, krad wrote: > > Its also worth pointing that if you decouple the userland from the kern= el > > files you no longer have a boot environment, as all the basic stuff to > boot > > the os isn't contained within the bootfs. I'm still struggling to see w= hy > > /boot needs to be on a different dataset, its just a bit of a linuxism. > > > > On 10 March 2016 at 19:23, Trond Endrest=C3=B8l > > wrote: > >> > >> On Thu, 10 Mar 2016 18:38+0300, Andrey Fesenko wrote: > >> > >> > On Thu, Mar 10, 2016 at 6:11 PM, krad wrote: > >> > > As Eric said you cant have /boot on a separate dataset as the whol= e > >> > > loader > >> > > bootstrap isnt designed too look for it on the dataset defined by > >> > > bootfs. > >> > > Remember no other datasets are mounted at that stage of the > bootstrap. > >> > > > >> > > You could maybe bodge something by manually playing around with th= e > >> > > bootfs > >> > > property, symlinks and rootfs variables in the loader.conf. But w= hy > >> > > would > >> > > you want to do this? It's more work and non standard, and will > break a > >> > > lot? > >> > > > >> > > > >> > > > >> > > On 10 March 2016 at 12:11, Andrey Fesenko > wrote: > >> > >> > >> > >> On Thu, Mar 10, 2016 at 2:55 PM, krad wrote: > >> > >> > presumably it boots now? > >> > >> > > >> > >> > On 10 March 2016 at 11:01, Andrey Fesenko > >> > >> > wrote: > >> > >> >> > >> > >> >> On Thu, Mar 10, 2016 at 1:49 PM, krad wrote= : > >> > >> >> > Make sure you are running the latest snapshot of current or > 10.3 > >> > >> >> > as > >> > >> >> > well, as > >> > >> >> > the MFC commits were in early February for 10-stable > >> > >> >> > > >> > >> >> >> > >> > >> >> >> If remove efiwpool/ROOT/init/boot and copy his content on > >> > >> >> >> efiwpool/ROOT/init my scheme work fine too. > >> > >> >> >> /usr /var /home and other included in BE for consistent boo= t > >> > >> >> >> system > >> > >> >> >> (CURRENT world may not boot with kernel other rev), and ol= d > >> > >> >> >> home > >> > >> >> >> snapshot sometimes useful for backup/restore > >> > >> >> >> _______________________________________________ > >> > >> >> > >> > >> >> % uname -a > >> > >> >> FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 > >> > >> >> r296548: > >> > >> >> Wed Mar 9 01:16:17 MSK 2016 > >> > >> >> root@des.local:/usr/obj/usr/src/sys/X220 amd64 > >> > >> > > >> > >> > > >> > >> > >> > >> My current working config > >> > >> % mount > >> > >> .... > >> > >> > >> > >> This work fine, booted, beadm create new env, activate them, see > boot > >> > >> menu and select BE. > >> > >> > >> > >> % beadm list > >> > >> BE Active Mountpoint Space Created > >> > >> init - - 420.7M 2016-03-09 02:57 > >> > >> init0 NR / 35.9G 2016-03-10 05:00 > >> > >> > >> > >> If i'm add separate dataset for /boot (efiwpool/ROOT/init0/boot) > >> > >> system not booted, efi loader (first stage) see only my pool, not > >> > >> found /boot/loader.efi > >> > > > >> > > > >> > > >> > It probably does not matter, as bootfs have snapshots (BE), just > >> > wanted to make it more clear (having taken significant mountpoint > >> > /boot, /usr, /var... in zfs dataset) and was surprised why the syste= m > >> > does not boot > >> > > >> > It is clear that as long as the functionality is experimental and > >> > under development, but would like to see where the full instructions > >> > on its implementation / restrictions, at least as early as has been > >> > described https://wiki.freebsd.org/RootOnZFS > >> > >> If you keep /boot as a separate dataset/filesystem, with > >> efiwpool/ROOT/init0/boot as the given bootfs, then boot1.efi will not > >> see a /boot directory inside that dataset. The files and directories > >> from /boot will be presented as living in /, the local root directory > >> of that dataset. > >> > >> You could create a /boot/boot symlink pointing to . (dot), but it's > >> better to let /boot be part of the regular boot environment, pretty > >> similar to what you would find on a UFS system using a separate root > >> filesystem. > >> > > why? > On the contrary, my scheme involves the entire system as a single BE > (including home) > > > linuxism > Is unlikely, to rather an attempt to use all the features ZFS. ZFS > also many possible settings for each dataset/FS (compression, atime, > exec......) Probably for /boot many of them unnecessary, but such > separate extra snapshots, can would not be harmful > > > > ---------- Forwarded message ---------- > From: Adam Wilson > To: freebsd-hackers@freebsd.org > Cc: > Date: Fri, 11 Mar 2016 13:50:14 +0300 > Subject: Re: FreeBSD sh on Linux? > On Thu, 10 Mar 2016 21:18:19 +0100 Jilles Tjoelker > wrote: > > > On Wed, Mar 09, 2016 at 08:27:05PM +0700, C Bergstr=C3=B6m wrote: > > > On Wed, Mar 9, 2016 at 8:13 PM, Jason Hellenthal > > > wrote: > > > > > > On Mar 9, 2016, at 02:06, Brendan Sechter > > > > wrote: > > > > > > > Is there any reason why FreeBSD sh can't be used on Linux? dash > > > > > is not a suitable login shell and bash is GNU. > > > > You'd need to do some work to make it compile. There is a package > > called libbsd which should be helpful. > > > > The filename completion in FreeBSD sh also uses a FreeBSD-local patch > > to libedit. This will be problematic if you want to maintain a > > package in a distribution. > > > > > > It's just the ash(1) shell with a few modifications that's a > > > > little more standard than most. Shouldn't be any reason why it > > > > can't > > > > There are quite a few bugfixes, features and performance improvements > > that are in FreeBSD sh and not in most other ash variants, such as > > UTF-8 support, $'...' to embed control characters and Unicode more > > easily, simple command substitutions without fork() and vfork() use. > > Therefore, I think the original question is reasonable, if the > > request is for a scripting shell (including for system() and make). > > > > > /* not meaning to be a troll */ > > > > > If you're going down this route - there's also ksh93 from solaris, > > > which may be easy to extract (or maybe has done so already.. not > > > sure) in my experience it's that nice balance between bare minimum > > > sh and bash. > > > > ksh93 is in ports. > > Debian includes the 1993 version of ksh in stable. Not sure if that's > the same thing- the package name is ksh, but it conforms to the > specification from 1993 as opposed to the 1988 version. > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " > From owner-freebsd-hackers@freebsd.org Fri Mar 11 15:13:52 2016 Return-Path: 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 5111CACB411 for ; Fri, 11 Mar 2016 15:13:52 +0000 (UTC) (envelope-from pfg@FreeBSD.org) Received: from nm4.bullet.mail.bf1.yahoo.com (nm4.bullet.mail.bf1.yahoo.com [98.139.212.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 0CB627A1 for ; Fri, 11 Mar 2016 15:13:51 +0000 (UTC) (envelope-from pfg@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1457709225; bh=QA5ARhFIkIxqvdsh1hC7waTnP1l/ruEfVQf128Zb4Zk=; h=From:Subject:To:Date:From:Subject; b=TfYAiMAf8O5i9I6sr9vufBLJfoU/zxrESs/fXGzf1pypZltYWUvXVxv83rMiAXW/JjMoNN7b0zSuCaNTOYBtozI1vlwTvpl9qbvOEiWAxznGtSiBMqUSvwM7bMWA/c1fMHrJ/GE1Jo25j7xGkiW2lbrHATfeI3kwaTTASdIreaOqkh5zDq6SXlB17FH3wHaA4w0DQBS/dKlHM1TOjZIOsTU9TPkVUMi1BJ82lXTqEjEdgMby3S3pwtQ7Id6Qag/RcaGFNrIG2GdqJ+nOSiWJrLfQEkMruJv8T9plaGn15FQH8ou3LsTNKa8jO7mM/VLGTaqJkVfmCDckOy/GR6QIoQ== Received: from [66.196.81.171] by nm4.bullet.mail.bf1.yahoo.com with NNFMP; 11 Mar 2016 15:13:45 -0000 Received: from [68.142.230.64] by tm17.bullet.mail.bf1.yahoo.com with NNFMP; 11 Mar 2016 15:13:45 -0000 Received: from [127.0.0.1] by smtp221.mail.bf1.yahoo.com with NNFMP; 11 Mar 2016 15:13:45 -0000 X-Yahoo-Newman-Id: 65043.27946.bm@smtp221.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: VZKfyI4VM1niPQsHk2_I7m_6yjDoUNsVDU7bQ2bVrSSLp9E xnCNm3kJHLWS2r0GPwLZhbkL2NZ4ix1jUF9qVafYQx6xrQC02qjIoCHTM97A ikTFWsxwl5YnycQZSBJiX_nojJnk0oAv9oLeSEryACHuKycuE2WL8b52FPTJ pjmrYcjRzvnh5PDsZUHXfK0SAbyDmUFoBNZTGLqVdZ.Y6M.ecIgeSE_zZzcE LjqR2UapujD87X5CENK3BMg2JfKG1imBOQOXts0kg3Ak4yps5Cky.HmSY32M x4tsRCnJ3RlYd.76MF4xoItJG9h0JO9h8YhUPWZfbKvloSe0mqvQFQzvacPR ZZXA2OZK4YNbO6qMLZTp8P_Kmd4k6.9f6WJslBfmk_hdiY__JqYt_JYxL6Yy SYaiy2580nam6rcYs0z5R.Qu7lpVz.SGzXE0yhsOwxbwcy9r4CnlHNZgAaqN NOlrU7aoK6jz6WIbcFaH6GiECekGveBslqy1G7RCGhTycbNTMpR0vOhgAcBp yp5cWIOQ.1Ynh1JmyHdqTENTmes5vhmpoXg-- X-Yahoo-SMTP: xcjD0guswBAZaPPIbxpWwLcp9Unf From: Pedro Giffuni Subject: Re: Advantages of kdbus with enhanced capabilities feature To: FreeBSD Hackers , pavan teja Message-ID: <56E2E0E2.5050202@FreeBSD.org> Date: Fri, 11 Mar 2016 10:14:42 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 15:13:52 -0000 FWIW; While kdbus seems to be in a somewhat flaky situation in other communities, we still have interest in *some* form of IPC for the kernel, or perhaps something mixed kernel/userland. One such mechanism could be Solaris doors, which were implemented for linux but never caught up much steam: http://www.rampant.org/doors/ I think there was also something interesting done for a microkernel (L4?) and it was made compatible with an Apple's Darwin Mach ports. It's an interesting topic for research, but if you want to do it as a GSoC you will have to discuss this with the mentor from the GSoC ideas page. Pedro. From owner-freebsd-hackers@freebsd.org Fri Mar 11 15:34:05 2016 Return-Path: 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 51C21ACC02A for ; Fri, 11 Mar 2016 15:34:05 +0000 (UTC) (envelope-from lokadamus@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AFEC4195E for ; Fri, 11 Mar 2016 15:34:04 +0000 (UTC) (envelope-from lokadamus@gmx.de) Received: from [192.168.0.143] ([95.91.226.72]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MIhDo-1agc011x8q-002ETr; Fri, 11 Mar 2016 16:33:53 +0100 Subject: Re: FreeBSD sh on Linux? To: Brendan Sechter , "freebsd-hackers@freebsd.org" References: From: "lokadamus@gmx.de" Message-ID: <56E2E560.2050009@gmx.de> Date: Fri, 11 Mar 2016 16:33:52 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:lqCstA6twFFyEg4tguIEi5kmq6nKrVPIBrEn+mpv6YxAfE8YFEM 8L6ZL5+b4MRxmI7XOhWTj45JGhyqbxDqeaPslIQY7mwgVoed2kp/KDekjm1oNVMpsI3L+rm ggfuUuqMyCDxg/ECV0NbRpuqg1RXe6m+m8rXE6MPCvF3lBPr4OUzMDAk1YTt+wpsbbUazGR jYgioshl2gwrAjFhQIoqg== X-UI-Out-Filterresults: notjunk:1;V01:K0:QQjkQqEr4D8=:qD11bhYwErLXPUOe+XxxVU BlltvyxArF/blM6tvV6NkTnCeVZpX/1xJHixSVrYBpH7a1m01lgC6wbSPfI0YiLrjAJhwx4qT 7LjCUH5fAEv+NmDbMIqu5pCNCvxQITmDmBqteZ+7/un/VvnPKcG2rI45mKSbAoFk3TMout0yQ fINxIjo6OaRIPbBeLTu1hjt+wd6NNvXcWS2t/GvIIzorTTxxl+TqaFgAqHfPOvGtMMXyPnIxq WX80PKArOLSk3DMWnm/twPqAXc8GYQ7cfLdgKEw4Scpt0P0B/kUX4OAc92trJjFUwrkFWVld5 dlp3pD8S/vM4sjYfezpGxtxaOdva6nNO0SFNwKm0W9b/6I2gIEErS07o0ezJlA99bn/2M/+Ab 8/cQ6TprviOkB7m2Xrp95T2LVXNVcCzQ2+qlWiucoRoBCuIy5BX5KGY6ycBsiDWxlt1yxF1kr 7ftzsA7zWQCkZGeo4+/r1zxw0QcxbgCXEyWjn6cAIGKG+qebMTqQeeuU+ES4SHwKmSsGHopsE 2c3QcJ3QEjZi8ACG9CL0OzO4wDb0mmsrVk42XBYFwmKnj06yZE90SuykBa0Osu2QJCvU4gZON ha+7U61N2ObuxGvkTlbeonhXADnZD0WPV9kJ0J4sAlFdGjK5c1ca49bMnC1V5l4IEvJy3jFRb +ZGKmVO4FpW5HtfPg5MPCuK+Pzc3xMeuE5mY8ucB6VuBSbjrgOd8y4yNb8aX43C6AKjCXZ5id KVgWhX+V/4lS576Q/nqW0TNfU37PKU02vHqstAbTMkRsKVqOz5/U3ZlLwB3+Hh5z9T02oTTQU V+McUN8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 15:34:05 -0000 On 03/09/16 09:06, Brendan Sechter wrote: > Is there any reason why FreeBSD sh can't be used on Linux? dash is not a suitable login shell and bash is GNU. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > Have you an example, what is going and what not? https://www.freebsd.org/doc/en/articles/linux-users/shells.html Greetings From owner-freebsd-hackers@freebsd.org Fri Mar 11 15:37:44 2016 Return-Path: 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 05226ACC193 for ; Fri, 11 Mar 2016 15:37:44 +0000 (UTC) (envelope-from rank1seeker@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 DE4061AED for ; Fri, 11 Mar 2016 15:37:43 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id D8FCCACC192; Fri, 11 Mar 2016 15:37:43 +0000 (UTC) Delivered-To: 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 D87A8ACC190; Fri, 11 Mar 2016 15:37:43 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::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 7625F1AEA; Fri, 11 Mar 2016 15:37:43 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: by mail-wm0-x232.google.com with SMTP id l68so22471990wml.1; Fri, 11 Mar 2016 07:37:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:mime-version :content-transfer-encoding; bh=pFu2hZjSIZG9HAX3pnURj0w0fnnfik1yRYjHH7aiYFg=; b=hD7Gpo2Ze7il2v0z6fjAEWWyjtXKK96C9Cc/5BY0JVIdFDvkNr1v9wNPVbfb4JUSXi DFjudjA6zFIV6fe9l7sUmW6le35QWf6se3SLcqFEx4g/pL3lQS/cT+iI8v3ZVWXST359 JBTWEXrJJmbgnceTOFHuk7t/iGniFkn64JWeCybiRA1e5BuXa4+k0glUfKo9XqomPJxM WLGHXSdpbvY+ahUyIHYNDF9GzIn4BCO0kvLl2K+QeMVLR0RR0Zpt9dzj5M3swd59e+eT 7c2y+9sCg5wzeDQPj4wIUTNW/pqkz+vOFQfxy9w5MuwLQjZuXLMTbbX4cAr7q2iK8EHC tSTg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-transfer-encoding; bh=pFu2hZjSIZG9HAX3pnURj0w0fnnfik1yRYjHH7aiYFg=; b=gvu1Dgk6swMMaUHbAhPoa2zk0QFDo2bQrAG3gjwk7H7RkHblUmZcPqLFhTe0vGPOaA 2KbxaDIJFEtcWpsH65FvIE/fhECOo9tZ2k1xTRzLsqvnifEqo6xJsYr93rjKwWnwBPrz WIDWKb6xl+rcJ4dovSLEscWHOHhr07PfxoVb9oHIpyulgEzhLTpTK8/gAJF6ks+Y2fVW 0QOS7Cwrdfs3bQqbfLJIOpoFL+TnAHS2NOtdZsav0fYyHZa/iA2IemQ5+Su0WeLWpjVo ATzjO+BZxcBGs4YftUKAZ91l9CqZFlZwt1da+GGA+ZoDhjd+Vs3eEXnroMaanjfN46a+ gnwA== X-Gm-Message-State: AD7BkJKFVaA2tS4vuRxL8SLwG4mYPmkCHY5l6qb55Q266JIteop4dL7qSLHXviBTeQsplw== X-Received: by 10.28.7.9 with SMTP id 9mr3492114wmh.8.1457710661935; Fri, 11 Mar 2016 07:37:41 -0800 (PST) Received: from localhost (cpe-94-253-187-91.zg.cable.xnet.hr. [94.253.187.91]) by smtp.gmail.com with ESMTPSA id up6sm9009300wjc.6.2016.03.11.07.37.41 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 11 Mar 2016 07:37:41 -0800 (PST) Date: Fri, 11 Mar 2016 16:37:37 +0100 From: To: hackers@freebsd.org, ports@freebsd.org Subject: (GSoC 2016) Parallel ports build and installation => paraports Message-ID: <20160311163737.00001819@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 15:37:44 -0000 Hi to all. Last year I overlooked the calendar, so am now proposing this project again. Would there be interest for it and mentor too? To cut it short, it works like this: http://starforce.biz/paraports.mp4 PS: It is video from last year. Now it works better and faster. Domagoj From owner-freebsd-hackers@freebsd.org Sat Mar 12 11:33:38 2016 Return-Path: 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 CAA47ACDC44 for ; Sat, 12 Mar 2016 11:33:38 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A7AEDD09 for ; Sat, 12 Mar 2016 11:33:38 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 3066220AA5 for ; Sat, 12 Mar 2016 06:33:31 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Sat, 12 Mar 2016 06:33:31 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=JwqJFyiGssCWLO/fW4SVCC9LgK0=; b=hUkvf t6ZmRKbRnA3xdAtlnLN/up7M2nMHwqsTlRxNKecCOjmk6pVXX/EIsB6nqtjVHaHS OQITR1ehE68/LlKc4V/NOnKJOl53oHY8dbVgPZOz+oIbTCKWiT0XMVhrYw4aJyUU kj7wgVduTRp+7c5psRTi9wlfInE4sT5jVtmwJE= X-Sasl-enc: o3pwRMf0rfRnKyvFctRWdqNc48E/Ivf/kPcoR/XzkYBB 1457782410 Received: from [192.168.1.31] (unknown [203.206.138.26]) by mail.messagingengine.com (Postfix) with ESMTPA id 747E8C00013 for ; Sat, 12 Mar 2016 06:33:30 -0500 (EST) Message-ID: <56E3FE6C.2080401@freebsd.org> Date: Sat, 12 Mar 2016 22:33:00 +1100 From: Darren Reed User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: RDM device from ESX - can't get disk paramters? Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Mar 2016 11:33:38 -0000 Dear All, Oh host A I had a set of disks mapped with ESX as RDMs to a FreeBSD 9.3 VM. No problem, works fine. The goal is to move that VM to a new host, so I migrate the VM over and then take the hard drives out of the old host and put them in the new one. However when FreeBSD boots it doesn't let me use the hard drives - they probe ok through the boot sequence: da3: Fixed Direct Access SCSI-5 device da3: Serial Number xxx da3: 6.600MB/s transfers (16bit) da3: 0MB (0 512 byte sectors: 0H 0S/T 0C) da3: quirks=0x8<4K> ... da5 at mpt1 bus 0 scbus3 target 0 lun 0 da5: Fixed Direct Access SCSI-5 device da5: Serial Number xxx da5: 6.600MB/s transfers (16bit) da5: 0MB (0 512 byte sectors: 0H 0S/T 0C) da5: quirks=0x8<4K> but an fdisk: fdisk: can't get disk parameters on /dev/da3 fdisk: cannot open disk /dev/da3: No such file or directory fdisk: can't get disk parameters on /dev/da5 fdisk: cannot open disk /dev/da5: No such file or directory I can't do anything with these devices: dd if=/dev/da3 dd: /dev/da3: Device not configured 0+0 records in 0+0 records out 0 bytes transferred in 0.000717 secs (0 bytes/sec) 0 0 0 Does anyone have any clues about what's gone (or is) wrong? Cheers, Darren From owner-freebsd-hackers@freebsd.org Sat Mar 12 12:16:43 2016 Return-Path: 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 5642DACB62B for ; Sat, 12 Mar 2016 12:16:43 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 30B3F967 for ; Sat, 12 Mar 2016 12:16:42 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id E455B20BDC for ; Sat, 12 Mar 2016 07:16:41 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute5.internal (MEProxy); Sat, 12 Mar 2016 07:16:41 -0500 DKIM-Signature: v=1; a=rsa-sha1; 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-sasl-enc:x-sasl-enc; s=smtpout; bh=Gzk9NU+znUIf3TK mdeKpwXwSvkI=; b=MSUAcKarm82Q4CB/V/K5tuYgdJM+0WLLnJRNHZjFrCTi+Xc ns/4nCgI294nWt3xJfDEeio+JkTLdN6fjtYzxvqPA2wop5ueIwK76CVPkLFC2Pr4 DblAdSXnR4j3wkzlkCToZrU2g6MnWp3uHuTA+Oqe/gnFwXk28hYl+kfkTV7g= X-Sasl-enc: /zwEggZ7OQ5R2eUTkrFzrgn6i3EvEQpvVGM+H+ggmQTR 1457785001 Received: from [192.168.1.31] (203-206-138-26.perm.iinet.net.au [203.206.138.26]) by mail.messagingengine.com (Postfix) with ESMTPA id 10E6FC00014 for ; Sat, 12 Mar 2016 07:16:40 -0500 (EST) Message-ID: <56E408A6.1000408@freebsd.org> Date: Sat, 12 Mar 2016 23:16:38 +1100 From: Darren Reed User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: RDM device from ESX - can't get disk paramters? References: <56E3FE6C.2080401@freebsd.org> In-Reply-To: <56E3FE6C.2080401@freebsd.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Mar 2016 12:16:43 -0000 On 12/03/2016 10:33 PM, Darren Reed wrote: > Dear All, > > Oh host A I had a set of disks mapped with ESX as RDMs > to a FreeBSD 9.3 VM. No problem, works fine. The goal > is to move that VM to a new host, so I migrate the VM > over and then take the hard drives out of the old host > and put them in the new one. However when FreeBSD boots > it doesn't let me use the hard drives - they probe ok > through the boot sequence: > > da3: Fixed Direct Access SCSI-5 device > da3: Serial Number xxx > da3: 6.600MB/s transfers (16bit) > da3: 0MB (0 512 byte sectors: 0H 0S/T 0C) > da3: quirks=0x8<4K> > ... > da5 at mpt1 bus 0 scbus3 target 0 lun 0 > da5: Fixed Direct Access SCSI-5 device > da5: Serial Number xxx > da5: 6.600MB/s transfers (16bit) > da5: 0MB (0 512 byte sectors: 0H 0S/T 0C) > da5: quirks=0x8<4K> > > but an fdisk: > > fdisk: can't get disk parameters on /dev/da3 > fdisk: cannot open disk /dev/da3: No such file or directory > > fdisk: can't get disk parameters on /dev/da5 > fdisk: cannot open disk /dev/da5: No such file or directory > > I can't do anything with these devices: > > dd if=/dev/da3 > dd: /dev/da3: Device not configured > 0+0 records in > 0+0 records out > 0 bytes transferred in 0.000717 secs (0 bytes/sec) > 0 0 0 > > Does anyone have any clues about what's gone (or is) wrong? I did a bit more looking at what I'd done previously and the answer to my question is this: when creating the RDM with vmkfstools, use the "-a lsilogic" option. Cheers, Darren