From owner-freebsd-hackers@freebsd.org Sun Dec 17 02:12:05 2017 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 0F787E99C62 for ; Sun, 17 Dec 2017 02:12:05 +0000 (UTC) (envelope-from mark@heily.com) Received: from mail-ot0-x22d.google.com (mail-ot0-x22d.google.com [IPv6:2607:f8b0:4003:c0f::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 CC4B07D025 for ; Sun, 17 Dec 2017 02:12:04 +0000 (UTC) (envelope-from mark@heily.com) Received: by mail-ot0-x22d.google.com with SMTP id h9so10828664oti.0 for ; Sat, 16 Dec 2017 18:12:04 -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:from:date:message-id:subject:to :cc; bh=2raIYg3wYsJ69j4JlaieiwrdoFCFfEfWwt462Wwhodk=; b=GL9DadTu2AsEpuRJkTF9Xliq7W3wHZEEF8CeYf9WbpQg8uFJRVhOgmxXxBRJysMUt2 RAXDzZFfPTx6FTcrp1CIv/3w6DNUumW3HC8+6oTfTkqwtEfWl7aA3RDTyBCpFHgRpwCj +Kz40VYgQNOvxYRpUjFw8ufON2jG77tjsnVF+se3ceGdEk0uysv+srpIlEhylEJURSjQ H/4G1C0cTuDgvbPiAozxCcHbN1pNn5mi3wYsTAP1F/TdYteIYW+g6BkO8zttabAVNqpU 7itvoIs7Kc4ETLycZfIh2JSB5reHdp342JaNoo8g93CjySfdSXuR28ydaO1QMQlmDpWn L+JA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=2raIYg3wYsJ69j4JlaieiwrdoFCFfEfWwt462Wwhodk=; b=jbSCfpRP34Q3khqUrRqNnbNvLxlvEQ/LmpY4xslADUCDPKNr8AsZFjZlDiAaZh9Aat yq7jU3F0EeujuamrdXhcVTwPL/FQiDbpYnjqTNGNhQvR/Yp87+KvjIqGx6+8kdyr9TKq AD1vWUJ8UbDKtjfSao9HgJU9Bw4uKFfRUVGl1cu5OXX5uocLEkC8OBESD9EEB1YEbj+N 3Q2jmr61FFdCBgw433WTgTbjwty3eVCssP301T8TUScNZLHpxQxX2iE751gXj34z7M9+ Yxj19kZN5qHr3MzYVxfoQLK+FXnwQer67wWQwPNqySPYH2PjHnzNoAeUfvVm01NvEk1a Lvpw== X-Gm-Message-State: AKGB3mIr/HvpTl+yMYZ3O0VU1Qn8gCOBrnurEF0WQ7PTXhO63fUNIvsv gEjXSBVphCuNCj78lL6elc9sopNpACEUgCtnP04hvdzc1hg= X-Google-Smtp-Source: ACJfBov7jxTgC15FMqVS81/jiUC07alcEjqaUS7iiEir/ATtndLFyWR3H0iCbb47BmUP/+P/wljgJXEM4ClMHFpB4+A= X-Received: by 10.157.37.55 with SMTP id k52mr6565036otb.80.1513476723799; Sat, 16 Dec 2017 18:12:03 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.22.170 with HTTP; Sat, 16 Dec 2017 18:12:03 -0800 (PST) X-Originating-IP: [71.70.173.127] In-Reply-To: <201712161949.vBGJnnMR008332@pdx.rh.CN85.dnsmgr.net> References: <201712161949.vBGJnnMR008332@pdx.rh.CN85.dnsmgr.net> From: Mark Heily Date: Sat, 16 Dec 2017 21:12:03 -0500 Message-ID: Subject: Re: Objections to converting bsd-family-tree to a dot file To: "Rodney W. Grimes" Cc: Eitan Adler , FreeBSD Hackers , tech-misc@netbsd.org, Lyndon Nerenberg , Kernel@dragonflybsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Dec 2017 02:12:05 -0000 On Sat, Dec 16, 2017 at 2:49 PM, Rodney W. Grimes < freebsd-rwg@pdx.rh.cn85.dnsmgr.net> wrote: > > On 15 December 2017 at 08:43, Lyndon Nerenberg > wrote: > > >> I'd like to turn this into into a dot file > > > Sounds like a reasonable idea. With care, the source (text) file(s) > can > > > often be formatted in a way that's at least semi-readable. I assume > this > > > would ship with pregenerated images (PDF, SVG) so people don't have to > > > install the port to render the graph? > > > > > > The overall consensus seems to be: so long as there is a reasonable > > way to view this file in plaintext without requiring a tool in base, > > its fine. I'll likely run with that after ironing out the conversion > > bit. > > I have seen no presentation of a reasonable way to view the > graph in plain text. I have no personal experience with it, but a quick Google search says there are programs based on the Graph::Easy library that can render DOT files as ASCII. Example: https://codeyarns.com/2017/10/21/how-to-convert-dot-graph-to-ascii/ Nor do I find the output you presented > as a sample very usable due to scaling issues, one of the graphs > was massively wide, the other was ok but at such a scale had > to be zoomed significantly to read. > > Though they are "pretty" I find them cumbersumb to use. And that > means they wont be used. > > I agree, there is so much information that you can't see the forest for the trees. Have you considered removing minor releases and bugfix releases from the diagram, especially when you get down into NetBSD/OpenBSD/FreeBSD land? +1 for the idea of using DOT to generate this graph, and good luck with it. From owner-freebsd-hackers@freebsd.org Sun Dec 17 04:24:18 2017 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 65D87EA09F5 for ; Sun, 17 Dec 2017 04:24:18 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yb0-x22e.google.com (mail-yb0-x22e.google.com [IPv6:2607:f8b0:4002:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 362162170 for ; Sun, 17 Dec 2017 04:24:18 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yb0-x22e.google.com with SMTP id 69so8876378ybc.6 for ; Sat, 16 Dec 2017 20:24:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=Fg6acsijBM/HNUfOMYap5YhStkq/2+bpcQG0XknqwRo=; b=STma4KWflvuUZZ7KdTb3ObPAfmBS4LXQLWJVy3mytV04Qey/A606tDl2wm1JE8nAp0 IbPHTP0lt4cKhuX6kUA8ZG1cRKiznZ+ovkGk3mVpBlXEju/M7uRzp5RFXnDRLxuATFwe bBDs4uA6JrsTUVCyyV/TNQ+2c/9KB4KLj7TaM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=Fg6acsijBM/HNUfOMYap5YhStkq/2+bpcQG0XknqwRo=; b=GfwNSQR7nVLB5kpMUhURuDEdmYb6tZe+zxrjoh/46vyEqCmQw/WebkGgQw4pygIPnx Bj80wjh0MNlkNHCDKhEyNntuuMNv8jmInLpxs1moNXoSSJulW9GauVly84UKZRMqVGl+ DE1c0DrYiebLTSjlGxd1et/b0fO4o/ceT8NnjAaQpWZcW4E+lMQb7i0hpA+r1WG3L4sq JqnywA1w/qNi8vmW6UXFnjitT82TGNN7FmvoEdwuC/8+f5pg4iDBJ4BeHMabfHzyxeTH OXGGKY0gmV1j9Es8pWmfi2JW3SKxDFRCddtvjR3F+UEK4LX6rlP84zc5wWBqBvu/Y/jN TWQw== X-Gm-Message-State: AKGB3mKzDjy9oNPCl1NrSWJ0nTib4SOkM4prXBPGSqNMnoSgcQrIGPLm konbBAQpvEMW7nLTgsx3pcPnC0ElWBagzuetprzbX1gp X-Google-Smtp-Source: ACJfBov1TWbr106NV4+H5u2ceRDxhTWY1YUCI/Kv88w/W4XhTGP9HdSG9w70ZfSFmjfrcMNWesraryHOC58nRIXMXy0= X-Received: by 10.129.122.194 with SMTP id v185mr11202497ywc.204.1513484657178; Sat, 16 Dec 2017 20:24:17 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.15.66 with HTTP; Sat, 16 Dec 2017 20:23:46 -0800 (PST) In-Reply-To: References: From: Eitan Adler Date: Sat, 16 Dec 2017 20:23:46 -0800 Message-ID: Subject: Re: faq/troubleshoot.html#indefinite-wait-buffer has the direction of transfer wrong (head -r326888 /usr/src/) To: Mark Millard Cc: FreeBSD Hackers , 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.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Dec 2017 04:24:18 -0000 On 16 December 2017 at 10:47, Mark Millard wrote: > I got a "swap_pager: indefinite wait buffer" notice and looked > it up. (This was on a rpi2 booted (kernel and world) from a > USB SSD, swap partition in use instead of a swap file. It > was building devel/cmake via poudriere-devel .) > > https://www.freebsd.org/doc/faq/troubleshoot.html#indefinite-wait-buffer > reads like it is for page-out to disk: > > > QUOTE > 5.9. > > What does the error swap_pager: indefinite wait buffer: mean? > > This means that a process is trying to page memory to disk, and the page = attempt has hung trying to access the disk for more than 20 seconds. It mig= ht be caused by bad blocks on the disk drive, disk wiring, cables, or any o= ther disk I/O-related hardware. If the drive itself is bad, disk errors wil= l appear in /var/log/messages and in the output of dmesg. Otherwise, check = the cables and connections. > ENDQUOTE > > > But the code containing the message is for "swread": > (head -r326888) If I understand correctly this is fixed by change "trying to page to" to "trying to page from" ? In other words this happens on swap-in, not swap-out. --=20 Eitan Adler From owner-freebsd-hackers@freebsd.org Sun Dec 17 03:30:34 2017 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 4EC26E9EBBE for ; Sun, 17 Dec 2017 03:30:34 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yb0-x22c.google.com (mail-yb0-x22c.google.com [IPv6:2607:f8b0:4002: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 064A2806D6 for ; Sun, 17 Dec 2017 03:30:34 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yb0-x22c.google.com with SMTP id t127so8836587ybf.9 for ; Sat, 16 Dec 2017 19:30:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=72EQuNRad1/2RImkOApYhzEhtZuQ3kDxNWloPaKNSlc=; b=tf7fMFz21knX1q8xZYZ/8XX2Yz8RQ0IW2yNqEZ7aCyMEWBTiJrfNb/vSqENUHQleYz VS05GN+3jCxZA02xIJkvycLfpvjR3DmWeZGbE/Smn8QwrR1hm0dJ1hIGJMggyf3wZ0lj KSYBYeWrm9IzpHxDmIHdFJxvix+4PokAbG06E= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=72EQuNRad1/2RImkOApYhzEhtZuQ3kDxNWloPaKNSlc=; b=G1QlBg4K5lztiA5uOcqubnVK4/mxc7HiNbdkoGDQY7PrhQIg9/OXzfi7MoOYRKbSBF DxGcndne8Aet5qyyDGNG8UakcS/8DwGYPYRyhuPZ8GU2ja9Boh7uBiOT0/ey+njy44Py 6WxfpHX93zuPuvXi6OSCmeGPSOVfqDl2bKHmVNGhmnExVxZ7OGwvzDxsVlwNEfA6tvkx YwJ3tonSzSmqFDx3LkFL+tdALPxO2h9WPm8iFMrMcmgw6p4ZrlQO1otH3X8miyd5LSXO l6WB22iibZ3HtoPkVdPzbO20VVJrAfAUmxnr8yiDD60q5A3Cfaz/izfS4C44N/5Eh9Xq CRrg== X-Gm-Message-State: AKGB3mJmDUjj5xAo4ZWWzUsjHKWOOKR7DXBle/MxsDKDXPPKK6ENm6ec CCBOvZ8RnWRzxTNat4cDwuZ/dWDLQa0mzneHMzfaVQ== X-Google-Smtp-Source: ACJfBosv5iRuadSRrnHoywFRnhv693prLraTKlT9cD7Gixbi/vOmOZ0LX32430Q7eBljg8/JvCgPFlrgKxpUS3+XTy0= X-Received: by 10.129.122.194 with SMTP id v185mr11146772ywc.204.1513481432806; Sat, 16 Dec 2017 19:30:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.15.66 with HTTP; Sat, 16 Dec 2017 19:30:02 -0800 (PST) In-Reply-To: References: <201712161949.vBGJnnMR008332@pdx.rh.CN85.dnsmgr.net> From: Eitan Adler Date: Sat, 16 Dec 2017 19:30:02 -0800 Message-ID: Subject: Re: Objections to converting bsd-family-tree to a dot file To: Mark Heily Cc: "Rodney W. Grimes" , FreeBSD Hackers , tech-misc@netbsd.org, Lyndon Nerenberg , Kernel@dragonflybsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Dec 2017 03:30:34 -0000 On 16 December 2017 at 18:12, Mark Heily wrote: > On Sat, Dec 16, 2017 at 2:49 PM, Rodney W. Grimes > wrote: >> >> > On 15 December 2017 at 08:43, Lyndon Nerenberg >> > wrote: >> > >> I'd like to turn this into into a dot file >> > > Sounds like a reasonable idea. With care, the source (text) file(s) >> > > can >> > > often be formatted in a way that's at least semi-readable. I assume >> > > this >> > > would ship with pregenerated images (PDF, SVG) so people don't have to >> > > install the port to render the graph? >> > >> > >> > The overall consensus seems to be: so long as there is a reasonable >> >> > way to view this file in plaintext without requiring a tool in base, >> > its fine. I'll likely run with that after ironing out the conversion >> > bit. >> >> I have seen no presentation of a reasonable way to view the >> graph in plain text. > > > I have no personal experience with it, but a quick Google search says > there are programs based on the Graph::Easy library that can > render DOT files as ASCII. > > Example: > > https://codeyarns.com/2017/10/21/how-to-convert-dot-graph-to-ascii/ I have not spent time with changing flags or making this output nice, but this is the naive output of graph::easy https://people.freebsd.org/~eadler/files/family-tree/ascii.txt -- Eitan Adler From owner-freebsd-hackers@freebsd.org Sun Dec 17 04:35:05 2017 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 53DA1EA13C6 for ; Sun, 17 Dec 2017 04:35:05 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-149.reflexion.net [208.70.210.149]) (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 00F26293C for ; Sun, 17 Dec 2017 04:35:04 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 18905 invoked from network); 17 Dec 2017 04:34:57 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 17 Dec 2017 04:34:57 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Sat, 16 Dec 2017 23:34:57 -0500 (EST) Received: (qmail 4223 invoked from network); 17 Dec 2017 04:34:57 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 17 Dec 2017 04:34:57 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id B8E14EC7B46; Sat, 16 Dec 2017 20:34:56 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: faq/troubleshoot.html#indefinite-wait-buffer has the direction of transfer wrong (head -r326888 /usr/src/) From: Mark Millard In-Reply-To: Date: Sat, 16 Dec 2017 20:34:56 -0800 Cc: FreeBSD Hackers , FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: <8D8CFFA3-ADE9-402F-B9A1-C311E4244FCB@dsl-only.net> References: To: Eitan Adler X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Dec 2017 04:35:05 -0000 On 2017-Dec-16, at 8:23 PM, Eitan Adler wrote: > On 16 December 2017 at 10:47, Mark Millard = wrote: >> I got a "swap_pager: indefinite wait buffer" notice and looked >> it up. (This was on a rpi2 booted (kernel and world) from a >> USB SSD, swap partition in use instead of a swap file. It >> was building devel/cmake via poudriere-devel .) >>=20 >> = https://www.freebsd.org/doc/faq/troubleshoot.html#indefinite-wait-buffer >> reads like it is for page-out to disk: >>=20 >>=20 >> QUOTE >> 5.9. >>=20 >> What does the error swap_pager: indefinite wait buffer: mean? >>=20 >> This means that a process is trying to page memory to disk, and the = page attempt has hung trying to access the disk for more than 20 = seconds. It might be caused by bad blocks on the disk drive, disk = wiring, cables, or any other disk I/O-related hardware. If the drive = itself is bad, disk errors will appear in /var/log/messages and in the = output of dmesg. Otherwise, check the cables and connections. >> ENDQUOTE >>=20 >>=20 >> But the code containing the message is for "swread": >> (head -r326888) >=20 > If I understand correctly this is fixed by change "trying to page to" > to "trying to page from" ? In other words this happens on swap-in, > not swap-out. That is my understanding of what I reported. Side note comparing with rpi2 (armv7, cortex-A7): A rpi3 (aarch64, cortex-A53) got a couple of the messages during a build of the same port: devel/cmake . In this case it is emmc attached to the microsd-card slot via an adapter, instead of a USB SSD stick. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-hackers@freebsd.org Sun Dec 17 20:01:04 2017 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 40400E9431E for ; Sun, 17 Dec 2017 20:01:04 +0000 (UTC) (envelope-from embaudarm@gmail.com) Received: from mail-ot0-x244.google.com (mail-ot0-x244.google.com [IPv6:2607:f8b0:4003:c0f::244]) (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 06C317C4E9 for ; Sun, 17 Dec 2017 20:01:04 +0000 (UTC) (envelope-from embaudarm@gmail.com) Received: by mail-ot0-x244.google.com with SMTP id v40so1139114ote.13 for ; Sun, 17 Dec 2017 12:01:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=7HVFWCoOkBXzODFCYq34GOGqLh2YEMWe+rU08Jgfk14=; b=FviwUh0OHIHsGF0inaEfT3rdKnMLktaNunzWnpuG+uQQi0RuSX2Fh9UXZ8JxE4/iwV tVNTIS5jn6z4PxUzXZSMpHaYGWxxmUznUVyUzdtQAfL/HsAptOulByO8RzYEhprlPJa2 agpCiOKOypGui/0b0rTn9dZUGJQiCTi2HeuVGWw67EB0TFGK8OKhJd4WkdBQiSHCcwAT DV+M7I2CrXgJIjzaQYO2uKUvH4NJnc1V7FrKCFga66zRRJMc3rnq6CUcdnSEPw6w6/c2 OWMz4wDSd5ha5VFMZ9hvFSm6XS6Anp8/BRIxhe/0+32cFPf+mLk/3Ws+eMnTWHQYmqDw nQuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=7HVFWCoOkBXzODFCYq34GOGqLh2YEMWe+rU08Jgfk14=; b=O1EnUJomT4hhsXfgSxJsstKH8N4q/OAioqwAtNAXgrNVG/WI1GoMmivOrXMsTybc+3 Cg81hyhQWFwj50+06s9Yt/ZL1dfs02razcwcM95PLc4qhcpk7cOGSyMW833slrXgXiVo VCmXXhWP67JwUeeCmN2qmqP1VgE1GjdmRrKrCAfbM10K/fTpATv9Yqi6H1C/XlexNDRb OuoaW03b277IQe7Jfp9d6zTMcAxOyh40tHw5gq5oiJ0PiytmN4ugqXLmiIGpMCOEMF6f CYfat1BDj0hvi4iHKZr5v5Vo7SSDkrgxuVWR8QKx/NAbqwthipOxd59mozJGO2CpgEl2 lXfA== X-Gm-Message-State: AKGB3mLFl9JX+7GlNK8o9Zq22Irry6bUBg5tV3vnhCfl+w9Tw+b/w+T1 6igG6kNwXSK9fWIIv2UOGG1U9r2YvT1I3UFusWNLoQ== X-Google-Smtp-Source: ACJfBovQ6Mf+z1K940QBRkGtgDDVTPvo9LYOFFIVYLMzUGecXwrXDcPPyNDqncnFqnAeBcVg9Bk2/brgNkFXibiXobU= X-Received: by 10.157.33.134 with SMTP id s6mr14090199otb.10.1513540863053; Sun, 17 Dec 2017 12:01:03 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.39.47 with HTTP; Sun, 17 Dec 2017 12:00:22 -0800 (PST) From: Lee D Date: Sun, 17 Dec 2017 15:00:22 -0500 Message-ID: Subject: How do I alloc multiple memory regions specified in a device tree? To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Dec 2017 20:01:04 -0000 Hi everyone. I have a device driver that must access registers in multiple memory ranges. How do I pull those values out of the device tree? This is for a custom ARM embedded board. bus_alloc_resource_any() works, but only for the first memory range. The second time I call it, it crashes the kernel. If I alloc the same memory resources by hardcoding the values in calls to bus_alloc_resource(), it works. The technique of calling bus_alloc_resource_any() multiple times is used in src/sys/dev/sdhci/sdhci_fdt.c, but I can't get it to work. Here is a snippet from my device tree: ... fabric@40000000 { device_type = "soc"; compatible = "simple-bus"; #address-cells = <0x1>; #size-cells = <0x1>; ranges = <0x0 0x40000000 0x5000000>; my_lcd@3C00000 { status = "okay"; compatible = "xlnx,my_lcd"; reg = <0x3C00000 0x1000 0x400000 0x1000 0x3000000 0x1000>; interrupts = <0x0 0x1d 0x1>; interrupt-parent = <0x1>; }; ... Here is my driver code from my_lcd_attach: rid=0; sc->lcd_mem_res = bus_alloc_resource_any(dev, SYS_RES_MEMORY, &rid, RF_ACTIVE); if (sc->lcd_mem_res == NULL) { my_lcd_detach(dev); return (ENOMEM); } rid=0; sc->dma_mem_res = bus_alloc_resource_any(dev, SYS_RES_MEMORY, &rid, RF_ACTIVE); if (sc->dma_mem_res == NULL) { my_lcd_detach(dev); return (ENOMEM); } Thank you. From owner-freebsd-hackers@freebsd.org Sun Dec 17 20:19:52 2017 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 6C7C8E948B6 for ; Sun, 17 Dec 2017 20:19:52 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 50B407CC2D for ; Sun, 17 Dec 2017 20:19:51 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 9e5dddbb-e367-11e7-8486-0934409070aa X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 9e5dddbb-e367-11e7-8486-0934409070aa; Sun, 17 Dec 2017 20:19:44 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id vBHKJnOl003743; Sun, 17 Dec 2017 13:19:49 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1513541989.95072.36.camel@freebsd.org> Subject: Re: How do I alloc multiple memory regions specified in a device tree? From: Ian Lepore To: Lee D , freebsd-hackers@freebsd.org Date: Sun, 17 Dec 2017 13:19:49 -0700 In-Reply-To: References: Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Dec 2017 20:19:52 -0000 On Sun, 2017-12-17 at 15:00 -0500, Lee D wrote: > Hi everyone. > > I have a device driver that must access registers in multiple memory > ranges.  How do I pull those values out of the device tree? > > This is for a custom ARM embedded board. > > bus_alloc_resource_any() works, but only for the first memory range. > The second time I call it, it crashes the kernel. > > If I alloc the same memory resources by hardcoding the values in calls > to bus_alloc_resource(), it works. > > The technique of calling bus_alloc_resource_any() multiple times is > used in src/sys/dev/sdhci/sdhci_fdt.c, but I can't get it to work. > > Here is a snippet from my device tree: > > ... >   fabric@40000000 { >     device_type = "soc"; >     compatible = "simple-bus"; >     #address-cells = <0x1>; >     #size-cells = <0x1>; >     ranges = <0x0 0x40000000 0x5000000>; > >     my_lcd@3C00000 { >       status = "okay"; >       compatible = "xlnx,my_lcd"; >       reg = <0x3C00000 0x1000 >              0x400000 0x1000 >              0x3000000 0x1000>; >       interrupts = <0x0 0x1d 0x1>; >       interrupt-parent = <0x1>; >     }; > ... > > Here is my driver code from my_lcd_attach: > >   rid=0; >   sc->lcd_mem_res = bus_alloc_resource_any(dev, SYS_RES_MEMORY, &rid, > RF_ACTIVE); > >   if (sc->lcd_mem_res == NULL) { >     my_lcd_detach(dev); >     return (ENOMEM); >   } > >   rid=0; >   sc->dma_mem_res = bus_alloc_resource_any(dev, SYS_RES_MEMORY, &rid, > RF_ACTIVE); > >   if (sc->dma_mem_res == NULL) { >     my_lcd_detach(dev); >     return (ENOMEM); >   } > > Thank you. The 'rid' argument is the zero-based index of the register range you want to allocate.  Just increment rid from 0 through the number of offset/length tuples in the fdt regs property. You can allocate all the ranges at once with bus_alloc_resources(). For an example, see the a10fb_spec array in arm/allwinner/a10_fb.c -- Ian From owner-freebsd-hackers@freebsd.org Sun Dec 17 23:04:40 2017 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 3E3BFE98D60 for ; Sun, 17 Dec 2017 23:04:40 +0000 (UTC) (envelope-from embaudarm@gmail.com) Received: from mail-ot0-x232.google.com (mail-ot0-x232.google.com [IPv6:2607:f8b0:4003:c0f::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 033F02010; Sun, 17 Dec 2017 23:04:40 +0000 (UTC) (envelope-from embaudarm@gmail.com) Received: by mail-ot0-x232.google.com with SMTP id q39so5560345otb.8; Sun, 17 Dec 2017 15:04:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=vTrMBotkBaZN81EqUEPzpNNkL3HGP7CXcSaj98Hktbs=; b=RqHLLgZWrlEkAuZH4DF8eJZp7cRkPedcOtZil5hqeh8pzByuuqeWOq93RnfbXFpd0r 0pKdh3Ql2C5jrvhQdAwT7/JAcBM1Z87PXhUnKl0D5k7T0+2bXfTfa90DBELXYm04oH7a cdAbPLI0gjtSdY1G0DPxK+QyQFQolVWh8caqnUkhNGU5PgqJd6e1hvn2+QIfORaMEMVQ F9XS8kYteheiR+zhoiUI+GCwetcm9b8+rEah3bkBLqqmaJtF1E1NxBrPUWp0OMWb7L5H y8fihqHJik/lU//4ljKCRA6IsSYU3eFaWPU88v38W19W0LSQoCSXk9Xjk/b3PAcf26q4 zh8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=vTrMBotkBaZN81EqUEPzpNNkL3HGP7CXcSaj98Hktbs=; b=MjjeKKOmQq3jiF5z1IVVaQ06Fdx5S1xzSIAxZ8rweJ8W5LtIIdvDHdC9eNifcXXDAR cRN8IVWb7wMOJvEkJkWxs9yIH63DUZO1eLy2oYvBHMnKrUrXhYTYiOQVS2BSWWHdkBVV iTw8SaSwMZOM2W4uT16RMLS+7I6fdElUWX/hcho2lISdZWGAl1kwUB1cK3+cALwbdbG5 zvkFhQ2yEQYuQhrd2U2CJ96MabxPm3dUHML3e+DpEUXu7l5IvyuGxeVZMdeJOCTVA2oq Ufn8qafVm/qAseCqhGFL957hBAjMj4C3aBJjJ14MJ6nq8AlRpVUcRlr2vfkgvLxwNlJe oCtw== X-Gm-Message-State: AKGB3mI8nyvlSTCeGQqqhFZAgQP9dLPoWVipa+KimBRA81lRkxX6NDGT 7b4iurP5cgjds1RZITWZXxwA9G7rfIedGVVdyZG5qQ== X-Google-Smtp-Source: ACJfBov0U/b68o19DFwk1+GVupJxJgvvXJq3f4rvFspEo53HVYFEl2sFPvd1S/6qTV9FjoO8gf77yZoNpJxwtAYB7p0= X-Received: by 10.157.33.134 with SMTP id s6mr14389544otb.10.1513551878836; Sun, 17 Dec 2017 15:04:38 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.39.36 with HTTP; Sun, 17 Dec 2017 15:03:58 -0800 (PST) In-Reply-To: <1513541989.95072.36.camel@freebsd.org> References: <1513541989.95072.36.camel@freebsd.org> From: Lee D Date: Sun, 17 Dec 2017 18:03:58 -0500 Message-ID: Subject: Re: How do I alloc multiple memory regions specified in a device tree? To: Ian Lepore Cc: freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Dec 2017 23:04:40 -0000 On Sun, Dec 17, 2017 at 3:19 PM, Ian Lepore wrote: > On Sun, 2017-12-17 at 15:00 -0500, Lee D wrote: >> Hi everyone. >> >> I have a device driver that must access registers in multiple memory >> ranges. How do I pull those values out of the device tree? >> >> bus_alloc_resource_any() works, but only for the first memory range. >> The second time I call it, it crashes the kernel. >> > > The 'rid' argument is the zero-based index of the register range you > want to allocate. Just increment rid from 0 through the number of > offset/length tuples in the fdt regs property. > > You can allocate all the ranges at once with bus_alloc_resources(). > For an example, see the a10fb_spec array in arm/allwinner/a10_fb.c > > -- Ian > Thank you, I see it was staring me in the face the whole time. Setting rid to the tuple index did the trick. Also thanks for the info on bus_alloc_resources(). Lee From owner-freebsd-hackers@freebsd.org Mon Dec 18 01:38:44 2017 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 8FBDBE9CD70 for ; Mon, 18 Dec 2017 01:38:44 +0000 (UTC) (envelope-from tls@panix.com) Received: from l2mail1.panix.com (l2mail1.panix.com [166.84.1.75]) (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 40AAE650B8 for ; Mon, 18 Dec 2017 01:38:43 +0000 (UTC) (envelope-from tls@panix.com) Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) by l2mail1.panix.com (Postfix) with ESMTPS id EC1D37EF3 for ; Sun, 17 Dec 2017 20:18:54 -0500 (EST) Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mailbackend.panix.com (Postfix) with ESMTP id 99EA41192E; Sun, 17 Dec 2017 20:18:47 -0500 (EST) Received: by panix5.panix.com (Postfix, from userid 415) id 7702B242E9; Sun, 17 Dec 2017 20:18:47 -0500 (EST) Date: Sun, 17 Dec 2017 20:18:47 -0500 From: Thor Lancelot Simon To: Mark Heily Cc: "Rodney W. Grimes" , Eitan Adler , FreeBSD Hackers , tech-misc@netbsd.org, Lyndon Nerenberg , Kernel@dragonflybsd.org Subject: Re: Objections to converting bsd-family-tree to a dot file Message-ID: <20171218011847.GA12528@panix.com> References: <201712161949.vBGJnnMR008332@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.2 (2017-04-18) X-Mailman-Approved-At: Mon, 18 Dec 2017 02:32:26 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 01:38:44 -0000 On Sat, Dec 16, 2017 at 09:12:03PM -0500, Mark Heily wrote: > On Sat, Dec 16, 2017 at 2:49 PM, Rodney W. Grimes < > freebsd-rwg@pdx.rh.cn85.dnsmgr.net> wrote: > > > > On 15 December 2017 at 08:43, Lyndon Nerenberg > > wrote: > > > >> I'd like to turn this into into a dot file > > > > Sounds like a reasonable idea. With care, the source (text) file(s) > > can > > > > often be formatted in a way that's at least semi-readable. I assume > > this > > > > would ship with pregenerated images (PDF, SVG) so people don't have to > > > > install the port to render the graph? > > > > > > > > > The overall consensus seems to be: so long as there is a reasonable > > > > way to view this file in plaintext without requiring a tool in base, > > > its fine. I'll likely run with that after ironing out the conversion > > > bit. > > > > I have seen no presentation of a reasonable way to view the > > graph in plain text. > > > I have no personal experience with it, but a quick Google search says > there are programs based on the Graph::Easy library that can > render DOT files as ASCII. And we have to pull what exactly into base or comp to use "Graph::Easy"? Thor From owner-freebsd-hackers@freebsd.org Mon Dec 18 13:53:13 2017 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 3179BE8BC82 for ; Mon, 18 Dec 2017 13:53:13 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 0FD0B7B522 for ; Mon, 18 Dec 2017 13:53:13 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 0BFA7E8BC81; Mon, 18 Dec 2017 13:53:13 +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 0A665E8BC7F for ; Mon, 18 Dec 2017 13:53:13 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: from mail-wr0-x242.google.com (mail-wr0-x242.google.com [IPv6:2a00:1450:400c:c0c::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 955AC7B521 for ; Mon, 18 Dec 2017 13:53:12 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: by mail-wr0-x242.google.com with SMTP id s66so14098971wrc.9 for ; Mon, 18 Dec 2017 05:53:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:mime-version :content-transfer-encoding; bh=97HdbAno9QqapgYvKnoOvoOf8jbGhBTrrhP73TH7nMk=; b=tpsR8xPoDLS7F7Gjdw0UD45jgDKNLq3s8XbAzJu786bBwYlB4sFa8yx3L1YzfW9xlM RZ+lD5t4CYU3DC8TUl3f8eSOZQNEOVvOFAoUc5oNrO2WBxb8JNEFRl2lbGBEk7VNAzym /16yz5ESWG272uZ0oHN2eiIVgIqzNGsUVh9KiWwSHfu8RCvWp6NkqwINEoi00rRG3pkK aelWulPENFJIm7hoH15FXu2st36hUZxTv1st2TWu0AdnjTEUCatzYJ4qI8NM400S2hLj 850kz71MmY6HNY25R54oP8YtZvHu4+H2jTwdhaLnNP0gMco0w7w0D11vbYmRfP2hFi0D dGhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-transfer-encoding; bh=97HdbAno9QqapgYvKnoOvoOf8jbGhBTrrhP73TH7nMk=; b=lv/3onyqiM/FvAEKnj81oucgOgjRl8cHhp413acx2+/4aoA+B7ie0QlHHw6SKoLdBB OzzK0mS+P0suVlR31/dRFb0T4GTNiEGn5Trgaxk73pYqFdXaeTIxrUhGqX7zhOPxqSnk V0xcyG5YzV4hOYHtpGpdMOdVKdolAGuU/JxNX6jtaDBOwb4M0V9mf96RTbfTCtOOQ9sr iec7WhXMwDqKO0qVDhtpE9/nHfFIE/mbhxrKPRVjAj6DHqVYCheMFSfu/2WPsdvwaZQl lVzzyg1IlkBA0K/0aWgp7QXw8u0tyaun6ii6hZtcY1A35wFSSoM5FaXWKGSbUaPgRJX4 KHIQ== X-Gm-Message-State: AKGB3mJ4PGlCKANOCNMxKxUSaQO6unzhULuhxiQdLkRLbeRfOntZ299J /TmgnFcHzbuZE7hBEGYHUMgARw== X-Google-Smtp-Source: ACJfBouR3/oA46dEyNbo305vF9g5n1KtWDURzHKPQ6A61mr6Lm2pbQpkOUfkNMKlo2WKWYsoWnrWBA== X-Received: by 10.223.171.177 with SMTP id s46mr17430022wrc.194.1513605190583; Mon, 18 Dec 2017 05:53:10 -0800 (PST) Received: from localhost ([188.252.245.72]) by smtp.gmail.com with ESMTPSA id f90sm15506242wmh.12.2017.12.18.05.53.09 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Dec 2017 05:53:10 -0800 (PST) Date: Mon, 18 Dec 2017 14:53:03 +0100 From: To: hackers@freebsd.org Subject: Operator group and reboot cmd Message-ID: <20171218145303.00007fb2@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.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 13:53:13 -0000 11.1 REL-p6 As a non-root user and member of operator group, I was able to issue a poweroff and shutdown commands (group set to operator), but not a reboot (group set to wheel) command (Operation not permitted). I was able to reboot by: $ shutdown -r now But to use reboot, cmd I had to: # chgrp 5 /sbin/reboot # chmod 4554 /sbin/reboot Shouldn't this be set by default install? # exit $ reboot From owner-freebsd-hackers@freebsd.org Mon Dec 18 18:22:58 2017 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 A355EEA1E3C for ; Mon, 18 Dec 2017 18:22:58 +0000 (UTC) (envelope-from jlmuir@imca.aps.anl.gov) Received: from tuna.imca.aps.anl.gov (tuna.imca.aps.anl.gov [164.54.200.33]) (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 8773168606 for ; Mon, 18 Dec 2017 18:22:58 +0000 (UTC) (envelope-from jlmuir@imca.aps.anl.gov) Received: by tuna.imca.aps.anl.gov (Postfix, from userid 502) id DD6632005D; Mon, 18 Dec 2017 12:22:50 -0600 (CST) Date: Mon, 18 Dec 2017 12:22:50 -0600 From: "J. Lewis Muir" To: Thor Lancelot Simon Cc: Mark Heily , "Rodney W. Grimes" , Eitan Adler , FreeBSD Hackers , tech-misc@netbsd.org, Lyndon Nerenberg , Kernel@dragonflybsd.org Subject: Re: Objections to converting bsd-family-tree to a dot file Message-ID: <20171218182250.GB19446@tuna.imca.aps.anl.gov> References: <201712161949.vBGJnnMR008332@pdx.rh.CN85.dnsmgr.net> <20171218011847.GA12528@panix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171218011847.GA12528@panix.com> X-Mailman-Approved-At: Mon, 18 Dec 2017 18:30:24 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 18:22:58 -0000 On 12/17, Thor Lancelot Simon wrote: > On Sat, Dec 16, 2017 at 09:12:03PM -0500, Mark Heily wrote: > > On Sat, Dec 16, 2017 at 2:49 PM, Rodney W. Grimes > > I have no personal experience with it, but a quick Google search says > > there are programs based on the Graph::Easy library that can > > render DOT files as ASCII. > > And we have to pull what exactly into base or comp to use "Graph::Easy"? Unfortunately, the output from Graph::Easy looks horrible: https://people.freebsd.org/~eadler/files/family-tree/ascii.txt That's unreadable. If Graph::Easy can't do a lot better than that, then I don't think it's worth worrying about what would need to be pulled in for Graph::Easy. I didn't know about bsd-family-tree until this thread, but I must say that I like the existing bsd-family-tree from the standpoint of readability from a terminal. It's nicely organized and laid out! Of course, I also understand the pain of editing it by hand. Eitan, in your initial post, you said: It has to be maintained by hand, and can't be parsed to do anything more useful (like turn it into an image). In addition, formatting differences between the different projects have led to minor differences that are difficult to merge. Is there any possibility of eliminating the formatting differences between the projects? If so, would that then make the maintenance more reasonable? Regards, Lewis From owner-freebsd-hackers@freebsd.org Mon Dec 18 18:54:47 2017 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 7DED4EA3D26 for ; Mon, 18 Dec 2017 18:54:47 +0000 (UTC) (envelope-from dholland@netbsd.org) Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F67B69AC4 for ; Mon, 18 Dec 2017 18:54:47 +0000 (UTC) (envelope-from dholland@netbsd.org) Received: by mail.netbsd.org (Postfix, from userid 1404) id E008784D9B; Mon, 18 Dec 2017 18:54:46 +0000 (UTC) Date: Mon, 18 Dec 2017 18:54:46 +0000 From: David Holland To: Thor Lancelot Simon Cc: Eitan Adler , FreeBSD Hackers , tech-misc@netbsd.org, Kernel@dragonflybsd.org Subject: Re: Objections to converting bsd-family-tree to a dot file Message-ID: <20171218185446.GA98@netbsd.org> References: <201712161949.vBGJnnMR008332@pdx.rh.CN85.dnsmgr.net> <20171218011847.GA12528@panix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171218011847.GA12528@panix.com> User-Agent: Mutt/1.9.1 (2017-09-22) X-Mailman-Approved-At: Mon, 18 Dec 2017 19:11:38 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 18:54:47 -0000 On Sun, Dec 17, 2017 at 08:18:47PM -0500, Thor Lancelot Simon wrote: > > > I have seen no presentation of a reasonable way to view the > > > graph in plain text. > > > > > > I have no personal experience with it, but a quick Google search says > > there are programs based on the Graph::Easy library that can > > render DOT files as ASCII. > > And we have to pull what exactly into base or comp to use "Graph::Easy"? My vote would be to ship it in base as SVG and PDF, and forget the text version. This is 2017 and everyone has a PDF reader of some kind in their UI somewhere. (and yes, maybe we ought to be able to read PDFs in base, but that's far from a critical issue) -- David A. Holland dholland@netbsd.org From owner-freebsd-hackers@freebsd.org Mon Dec 18 19:52:11 2017 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 AEE3EE81DE6 for ; Mon, 18 Dec 2017 19:52:11 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 70A756BE07 for ; Mon, 18 Dec 2017 19:52:11 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x229.google.com with SMTP id f18so6010209ioh.1 for ; Mon, 18 Dec 2017 11:52:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=w2RPu64x/rdD3shTbFTu30cjpcQNe18tsOz96HZS91Y=; b=aMLLie3S5oShjSmjk57quNSBxwXUAgSZS6HsffIVMVVQ6QpyXUqKPw6ApxaILgAAwC MBueqX8Ch9rw5DWIFN2J5rlNf9iPxy/kTeJ9bOI1TXjwjxOHCktqQKNPwzAD4l+YHI9t 5GD87vE4eBfkMZ2AcjMuqndOhYwM+BW2yOrtSxl06mUd3brIXUiM8q7tjPnaN4D3peut C9Y5GXeCilIL04hjUrjkWbKaBKQCp8k+g3dX3TGcqQ1mJ1E6h9WaNyHlgmka0OFGMowh 0gZRHwI+f0KAdfPJP4J/fg4kDtubOwpAti3WQ1LkFJywxQl2DoRnNrU+tSP21NGUaH/a WwpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=w2RPu64x/rdD3shTbFTu30cjpcQNe18tsOz96HZS91Y=; b=ruBuC2sRRN5OpgJ6y5DjgVNzrNAPgWV8Ef63OrSoowIkcMvfqACKbfvQGe+62Tx3MM qK8BwX76tyaHAHK0mFfDR8KlFKSNGdLg0nz099Jpw6fPaSEvjFPkP90s1iHaWCOsP70J rbA8frv9TyPwWsCaXaoEQcPxgnLl2+ys6Vk3HNkpZASOCNtnvP1NlW0lSl0abesQH2Eo 6orTLnGhYHLpBSU393sn4OvWChlGICtRcQ30eYllicMUsR6nK3SFvepM1I24626lWScn H5dYETS/6sUYhhATftBb+gHicPe/gvlqf72vK0p9AocidO9FtBV0pjAMeVSA16Voes1I utJA== X-Gm-Message-State: AKGB3mI6lACcQa4SAUDSOi5nGwFFNLm/EbGuQLUoxtNmcqJ++iwDn2ck 9GTYd5/mHKxHO4CBO7r3pxRkzuVpvUGFOcu4v483OA== X-Google-Smtp-Source: ACJfBotytGt81hyC4+dKHCYdSJtS2+gMKtOePGjpO1AloUhaW+9i3wwx7P+bx61hMPi1Zcv2Emx6GXTkzt1LrrzKpw4= X-Received: by 10.107.48.197 with SMTP id w188mr1069938iow.301.1513626730439; Mon, 18 Dec 2017 11:52:10 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Mon, 18 Dec 2017 11:52:09 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20171218185446.GA98@netbsd.org> References: <201712161949.vBGJnnMR008332@pdx.rh.CN85.dnsmgr.net> <20171218011847.GA12528@panix.com> <20171218185446.GA98@netbsd.org> From: Warner Losh Date: Mon, 18 Dec 2017 12:52:09 -0700 X-Google-Sender-Auth: ddnwbx8Ly1BZ_eG7UkmOS2e-k1s Message-ID: Subject: Re: Objections to converting bsd-family-tree to a dot file To: David Holland Cc: Thor Lancelot Simon , Eitan Adler , tech-misc@netbsd.org, Kernel@dragonflybsd.org, FreeBSD Hackers Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 19:52:11 -0000 On Mon, Dec 18, 2017 at 11:54 AM, David Holland wrote: > On Sun, Dec 17, 2017 at 08:18:47PM -0500, Thor Lancelot Simon wrote: > > > > I have seen no presentation of a reasonable way to view the > > > > graph in plain text. > > > > > > > > > I have no personal experience with it, but a quick Google search says > > > there are programs based on the Graph::Easy library that can > > > render DOT files as ASCII. > > > > And we have to pull what exactly into base or comp to use "Graph::Easy"? > > My vote would be to ship it in base as SVG and PDF, and forget the > text version. This is 2017 and everyone has a PDF reader of some kind > in their UI somewhere. > > (and yes, maybe we ought to be able to read PDFs in base, but that's > far from a critical issue) > Assuming that the generated graph is something that isn't... well... crazy... Warner From owner-freebsd-hackers@freebsd.org Mon Dec 18 20:20:11 2017 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 0220DE841B9 for ; Mon, 18 Dec 2017 20:20:11 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id D37876DE19 for ; Mon, 18 Dec 2017 20:20:10 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id CFDE3E841B8; Mon, 18 Dec 2017 20:20:10 +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 CF65AE841B7 for ; Mon, 18 Dec 2017 20:20:10 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: from mail-ua0-x22a.google.com (mail-ua0-x22a.google.com [IPv6:2607:f8b0:400c:c08::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 86FE76DE18 for ; Mon, 18 Dec 2017 20:20:10 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: by mail-ua0-x22a.google.com with SMTP id i4so11512900uab.5 for ; Mon, 18 Dec 2017 12:20:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2Dvjsd/ujt9sdv+8B5CpjSm7U8uCb9I1jfFj6E1u/fA=; b=jzVHe1/tl6pIiCuHumSZ1V8/zLu+p9F8ru5XVx5MW3r3jcambmFnBG8sVud3quLjza RI+cHeHrC5pBwDB5igHoJ6JAuI7EOqYrQBuYGBUm99Mxj58jig/SRuRohETHz+LX76ce nlxO/WRR2m6H5oLRC0XtOLiPFnJUFVJSz5Iu8KwSoLcYn8Tn+APC2VcBnIvgjfoaGDJC 5L1GsdbRdZRHDFgV3hhfPS6bMX0Un/+18n0CbQobzADohKc/+JtMmPKcxWGu0/67bDTh 92Q7bMjlQ5nnVpG/kPTq9vCeHuDiqHlisDH6rfvuJJwuK07GZWOFefsn31okk2u3h3nT jNIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2Dvjsd/ujt9sdv+8B5CpjSm7U8uCb9I1jfFj6E1u/fA=; b=GA/+JUX1XH2tjaivhUE5dSeJew8177OLHOwX52KAt35HxVJqAIhCk+o57bEY7noJkM L9EkyoRRxRn9u9+ehHDvwX2O0irB8NijU8hJr+FnAX4eVFMVz++qr3YNxSH4ZbLbjEQH yjJk44bBKftI4Gvi0N8DBKmpTHweKAOdd7x+rAldNsaIsAN3BYWosCcWjgBVq9mN+Yx2 KDdKTSj2jEUqp/elT60r4LBKqVnLxcqgujIQOofKk/oLK1ILlAl2XJXCp5Itzj4Z/ymt wjbb4aWrhXJabGCJtkSJRhmPHm3jvu3ngU3NNQpl9GHxHoY9iCsogfTXotp0O+GwhY6A 9j0A== X-Gm-Message-State: AKGB3mIy7rrqDUaucR5GF95jVjhroOShuWZaE+mzWUSeYxYoEf65f3hb B0MJz7b5M0mux0YOuEM9x44WvaNk7dgyPiB5Io8= X-Google-Smtp-Source: ACJfBov3FYhe+ya7MOC7CrZbwvIjnPodLYm81WonPYSlBZSWyI8tZexm+sYJ/66nsAKZOZOThBl3izx4rKktxllZOd4= X-Received: by 10.159.42.203 with SMTP id d11mr1078678uaj.74.1513628409552; Mon, 18 Dec 2017 12:20:09 -0800 (PST) MIME-Version: 1.0 References: <20171218145303.00007fb2@gmail.com> In-Reply-To: <20171218145303.00007fb2@gmail.com> From: Ben Woods Date: Mon, 18 Dec 2017 20:19:58 +0000 Message-ID: Subject: Re: Operator group and reboot cmd To: rank1seeker@gmail.com Cc: hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 20:20:11 -0000 On Tue, 19 Dec 2017 at 2:53 am, wrote: > 11.1 REL-p6 > > As a non-root user and member of operator group, I was able to issue a > poweroff and shutdown commands (group set to operator), but not a > reboot (group set to wheel) command (Operation not permitted). > > I was able to reboot by: > $ shutdown -r now > > But to use reboot, cmd I had to: > # chgrp 5 /sbin/reboot > # chmod 4554 /sbin/reboot > Shouldn't this be set by default install? > # exit > > $ reboot I suspect this is deliberate because the reboot command does not give processes a proper chance to exit cleanly. Therefore, it makes sense if only those in the wheel group can use this big hammer, whilst operators must follow the proper shutdown model. >From the reboot man page: https://man.freebsd.org/reboot =E2=80=9CNormally, the shutdown(8) utility is used when the system needs to= be halted or restarted, giving users advance warning of their impending doom and cleanly terminating specific programs.=E2=80=9D Regards, Ben --=20 -- From: Benjamin Woods woodsb02@gmail.com From owner-freebsd-hackers@freebsd.org Mon Dec 18 19:57:43 2017 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 15EE2E823EE for ; Mon, 18 Dec 2017 19:57:43 +0000 (UTC) (envelope-from mouse@Stone.Rodents-Montreal.ORG) Received: from Stone.Rodents-Montreal.ORG (Stone.Rodents-Montreal.ORG [98.124.61.89]) by mx1.freebsd.org (Postfix) with ESMTP id 8D9896C2C0 for ; Mon, 18 Dec 2017 19:57:42 +0000 (UTC) (envelope-from mouse@Stone.Rodents-Montreal.ORG) Received: (from mouse@localhost) by Stone.Rodents-Montreal.ORG (8.8.8/8.8.8) id OAA24711; Mon, 18 Dec 2017 14:38:44 -0500 (EST) Date: Mon, 18 Dec 2017 14:38:44 -0500 (EST) From: Mouse Message-Id: <201712181938.OAA24711@Stone.Rodents-Montreal.ORG> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Erik-Conspiracy: There is no Conspiracy - and if there were I wouldn't be part of it anyway. X-Message-Flag: Microsoft: the company who gave us the botnet zombies. X-Composition-Start-Date: Mon, 18 Dec 2017 14:37:08 -0500 (EST) To: David Holland , Eitan Adler , FreeBSD Hackers , tech-misc@NetBSD.org, Kernel@dragonflybsd.org Subject: Re: Objections to converting bsd-family-tree to a dot file In-Reply-To: <20171218185446.GA98@netbsd.org> References: <201712161949.vBGJnnMR008332@pdx.rh.CN85.dnsmgr.net> <20171218011847.GA12528@panix.com> <20171218185446.GA98@netbsd.org> X-Mailman-Approved-At: Mon, 18 Dec 2017 21:04:08 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 19:57:43 -0000 > My vote would be to ship it in base as SVG and PDF, and forget the > text version. This is 2017 and everyone has a PDF reader of some > kind in their UI somewhere. Yes, and I love you too. I'm just glad I have copies of the text file while it still was a text file. /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTML mouse@rodents-montreal.org / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B From owner-freebsd-hackers@freebsd.org Mon Dec 18 21:30:40 2017 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 9B45BE897A9 for ; Mon, 18 Dec 2017 21:30:40 +0000 (UTC) (envelope-from gdt@lexort.com) Received: from linuxpal.mit.edu (linuxpal.ipv6.mit.edu [IPv6:2001:4830:2446:fe60::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "linuxpal.mit.edu", Issuer "Lexort Systems CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5FFC270DC1 for ; Mon, 18 Dec 2017 21:30:40 +0000 (UTC) (envelope-from gdt@lexort.com) Received: by linuxpal.mit.edu (Postfix, from userid 9545) id 9144416079; Mon, 18 Dec 2017 16:30:36 -0500 (EST) From: Greg Troxel To: Eitan Adler Cc: Lyndon Nerenberg , FreeBSD Hackers , Kernel@dragonflybsd.org, tech-misc@netbsd.org Subject: Re: Objections to converting bsd-family-tree to a dot file References: OpenPGP: id=098ED60E X-Hashcash: 1:20:171218:lyndon@orthanc.ca::8E9Aw2BiNsUhgFhb:000000000000000000000000000000000000000000002EE6 X-Hashcash: 1:20:171218:lists@eitanadler.com::qXHXPxd2LucHzxKt:000000000000000000000000000000000000000001ocO X-Hashcash: 1:20:171218:freebsd-hackers@freebsd.org::VyvADBSvg0hSGL97:00000000000000000000000000000000005RK9 X-Hashcash: 1:20:171218:tech-misc@netbsd.org::lOva1rltEnC9cQjh:000000000000000000000000000000000000000003qTt X-Hashcash: 1:20:171218:kernel@dragonflybsd.org::+JmvsBEy9orwsrvi:0000000000000000000000000000000000000028JY Date: Mon, 18 Dec 2017 16:30:32 -0500 In-Reply-To: (Eitan Adler's message of "Sat, 16 Dec 2017 10:26:02 -0800") Message-ID: User-Agent: Gnus/5.130016 (Ma Gnus v0.16) Emacs/24.5 (berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-Mailman-Approved-At: Mon, 18 Dec 2017 21:38:57 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 21:30:40 -0000 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Eitan Adler writes: > On 15 December 2017 at 08:43, Lyndon Nerenberg wrote: >>> I'd like to turn this into into a dot file >> Sounds like a reasonable idea. With care, the source (text) file(s) can >> often be formatted in a way that's at least semi-readable. I assume this >> would ship with pregenerated images (PDF, SVG) so people don't have to >> install the port to render the graph? > > The overall consensus seems to be: so long as there is a reasonable > way to view this file in plaintext without requiring a tool in base, > its fine. I'll likely run with that after ironing out the conversion > bit. I think we also need to be sure that the cost/benefit tradeoff is positive. I wonder why this is coming up now, when the file has existed for years, and exactly what problem is being solved. If the file can be generated into plain text (and also more formats) from a source file, then it might make sense to maintain the source and toolchain requirements as a separate project, which can then be in ports and pkgsrc etc. Then the output can be generated and released, and imported, and the *BSD projects can not care about how it was generated. But it should be as readable as the current file. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAlo4M3gACgkQH9p66AmO1g5uUACeI32F9hzrxeye/rvOjElj75uD bOEAn0TT7vgbrQ1/k9dt0RPXJXkxDlv9 =2+MF -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-hackers@freebsd.org Tue Dec 19 02:54:24 2017 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 AD2C9EA38D2 for ; Tue, 19 Dec 2017 02:54:24 +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 87EA47FC45 for ; Tue, 19 Dec 2017 02:54:24 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 873EBEA38D1; Tue, 19 Dec 2017 02:54:24 +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 86EB4EA38D0 for ; Tue, 19 Dec 2017 02:54:24 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: from mail-wr0-x241.google.com (mail-wr0-x241.google.com [IPv6:2a00:1450:400c:c0c::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 19B957FC44 for ; Tue, 19 Dec 2017 02:54:24 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: by mail-wr0-x241.google.com with SMTP id l19so4093283wrc.2 for ; Mon, 18 Dec 2017 18:54:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=OHw05z9ToJOi9s6sHrt+VKEBdJHXYaDjzwpmY7WIk84=; b=b0fcJbISQ73fdeBbQWgHu8U5hIbzhXZZ729FHDjK38I6SH49J8xWSySp0BfIOEFgdG B8xu3hwHnmZv/k1froMtupybpn4+5MV+CfBH9GwGa3xl27JPqApVWklvudzAywAAeBIS AUD07RLdL21m6Qed73EYKC9bVjvmkdTb0dQntu5OzCEZH+6y3ABqGfJuGjzfCKcdmHSh VUhT6efEAOh/p2ReQIrf499nVuPTtyqZR8dGuuqr6wmacomS5alx40ErsgxXQtr3AeZq 9eX4N6UgiBKgXC2uGlrNiBrd4wP1uMhWfU26Q8+bbI3ijByzXN1qaZDzf79b4/dLJRTJ ChKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=OHw05z9ToJOi9s6sHrt+VKEBdJHXYaDjzwpmY7WIk84=; b=SK5zuAdl1uFrVLgvIJ3uohvREv0vy7bIm873xg7W91f77LInR4HH9dcuxa/SDRmI/+ B7yVPtKC9dpmLCJqSWrCMUEQkSJ5aVoZeI5Tol/thhS9SgPyD5D0Fmn1N3tq8Rzp/Yq3 PuESikQp+hD7DCTwXiBxbcZjVxWeZwKko59Zc3whY4l7zLlwAGNoSW6XtCQ9wyj6l9DQ fsX01Q8mC0c7GPj5fEYCYwiLcxM3iJ6U971GoO5x40EoAwr5T1vLimWa8WK8yoxJWMwf fscKYdZJtFQkwJxVRYF+7nARqKcMjdo3oEd1NpmqjlNDwkodl9cLwZe5WGeZjs6hbubi yS7g== X-Gm-Message-State: AKGB3mJBwh6ocodyrl4lg1b7JzMEqnaUUXufDJg6dzFuyEIazytZv6Pm zam4kAxtvwHIJAVQ2L9uwIg= X-Google-Smtp-Source: ACJfBovtlFRyKk3PYaM+k13AZce+Yja5/gM1qXS+D5ftI5Y/I8qIa3aoupvLNc8D5lNI+1Z6YvqE0Q== X-Received: by 10.223.196.211 with SMTP id o19mr2845046wrf.240.1513652062566; Mon, 18 Dec 2017 18:54:22 -0800 (PST) Received: from localhost ([213.149.52.70]) by smtp.gmail.com with ESMTPSA id 21sm7386625wrt.27.2017.12.18.18.54.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Dec 2017 18:54:22 -0800 (PST) Date: Tue, 19 Dec 2017 03:54:17 +0100 From: To: Ben Woods Cc: hackers@freebsd.org Subject: Re: Operator group and reboot cmd Message-ID: <20171219035417.000012a6@gmail.com> In-Reply-To: References: <20171218145303.00007fb2@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2017 02:54:24 -0000 On Mon, 18 Dec 2017 20:19:58 +0000 Ben Woods wrote: > On Tue, 19 Dec 2017 at 2:53 am, wrote: >=20 > > 11.1 REL-p6 > > > > As a non-root user and member of operator group, I was able to > > issue a poweroff and shutdown commands (group set to operator), but > > not a reboot (group set to wheel) command (Operation not permitted). > > > > I was able to reboot by: > > $ shutdown -r now > > > > But to use reboot, cmd I had to: > > # chgrp 5 /sbin/reboot > > # chmod 4554 /sbin/reboot > > Shouldn't this be set by default install? > > # exit > > > > $ reboot =20 >=20 >=20 > I suspect this is deliberate because the reboot command does not give > processes a proper chance to exit cleanly. Therefore, it makes sense > if only those in the wheel group can use this big hammer, whilst > operators must follow the proper shutdown model. >=20 > From the reboot man page: > https://man.freebsd.org/reboot >=20 > =E2=80=9CNormally, the shutdown(8) utility is used when the system needs = to > be halted or restarted, giving users advance warning of their > impending doom and cleanly terminating specific programs.=E2=80=9D >=20 >=20 > Regards, >=20 > Ben Thanks Ben, I'll have to investigate it, but in a meantime I've figured that it auto affected: -r-sr-xr-- 4 root operator /sbin/fastboot -r-sr-xr-- 4 root operator /sbin/fasthalt -r-sr-xr-- 4 root operator /sbin/halt which means those are hardlinks and man proves it ... From owner-freebsd-hackers@freebsd.org Tue Dec 19 18:34:42 2017 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 D54B9E96A6E for ; Tue, 19 Dec 2017 18:34:42 +0000 (UTC) (envelope-from dholland@netbsd.org) Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C581864CAF for ; Tue, 19 Dec 2017 18:34:42 +0000 (UTC) (envelope-from dholland@netbsd.org) Received: by mail.netbsd.org (Postfix, from userid 1404) id 8911A84E6C; Tue, 19 Dec 2017 18:34:41 +0000 (UTC) Date: Tue, 19 Dec 2017 18:34:41 +0000 From: David Holland To: Mouse Cc: David Holland , Eitan Adler , FreeBSD Hackers , tech-misc@NetBSD.org, Kernel@dragonflybsd.org Subject: Re: Objections to converting bsd-family-tree to a dot file Message-ID: <20171219183441.GA17345@netbsd.org> References: <201712161949.vBGJnnMR008332@pdx.rh.CN85.dnsmgr.net> <20171218011847.GA12528@panix.com> <20171218185446.GA98@netbsd.org> <201712181938.OAA24711@Stone.Rodents-Montreal.ORG> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201712181938.OAA24711@Stone.Rodents-Montreal.ORG> User-Agent: Mutt/1.9.1 (2017-09-22) X-Mailman-Approved-At: Tue, 19 Dec 2017 18:45:21 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2017 18:34:42 -0000 On Mon, Dec 18, 2017 at 02:38:44PM -0500, Mouse wrote: > > My vote would be to ship it in base as SVG and PDF, and forget the > > text version. This is 2017 and everyone has a PDF reader of some > > kind in their UI somewhere. > > Yes, and I love you too. What exactly is stopping you from using xpdf? It depends on nothing written since about 1992... -- David A. Holland dholland@netbsd.org From owner-freebsd-hackers@freebsd.org Wed Dec 20 03:10:37 2017 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 D871FE8E509 for ; Wed, 20 Dec 2017 03:10:37 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (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 4B7FC78FFD for ; Wed, 20 Dec 2017 03:10:36 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id vBK3CJ1K067099 for ; Tue, 19 Dec 2017 19:12:26 -0800 (PST) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: "FreeBSD Hackers" Subject: error: invalid operands to binary expression Date: Tue, 19 Dec 2017 19:12:25 -0800 Message-Id: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Dec 2017 03:10:37 -0000 Apologies if this was better posted on ports@=2E But given the circumstances, I thought this might be a better choice=2E :-) OK I've been hacking on this port all day=2E I've silenced all the warnings, and errors; save one: ImageEventBox=2Ecpp:152:26: error: invalid operands to binary expression ('Gl= ib::RefPtr' and 'int') if(ImagePixbuf_Original !=3D 0 && loaded =3D=3D true) ~~~~~~~~~~~~~~~~~~~~ ^ ~ This *should* be easy to deal with, and I'm probably just over complicating it=2E But I'm stuck=2E Please help=2E Thanks! --Chris From owner-freebsd-hackers@freebsd.org Wed Dec 20 03:19:08 2017 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 C7B5DE8EE33 for ; Wed, 20 Dec 2017 03:19:08 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [74.104.188.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "m5p.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9837479699 for ; Wed, 20 Dec 2017 03:19:08 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:470:1f07:15ff::1f] (haymarket.m5p.com [IPv6:2001:470:1f07:15ff::1f]) (authenticated bits=0) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTPSA id vBK3IR0V012213 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 19 Dec 2017 22:18:33 -0500 (EST) (envelope-from george+freebsd@m5p.com) Subject: Re: error: invalid operands to binary expression To: bsd-lists@BSDforge.com, FreeBSD Hackers References: From: George Mitchell Message-ID: <99287b7a-b922-f161-f05e-34d2db27d301@m5p.com> Date: Tue, 19 Dec 2017 22:18:20 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="9TP6ywOODsvxSYsESI8rWB5JmwelRS02r" X-Spam-Status: No, score=0.2 required=10.0 tests=HELO_MISC_IP, RP_MATCHES_RCVD autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (mailhost.m5p.com [IPv6:2001:470:1f07:15ff::f7]); Tue, 19 Dec 2017 22:18:33 -0500 (EST) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Dec 2017 03:19:08 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --9TP6ywOODsvxSYsESI8rWB5JmwelRS02r Content-Type: multipart/mixed; boundary="wiVfL4bC3LPI8GBy0J5hXDpEX3BtOjwmZ"; protected-headers="v1" From: George Mitchell To: bsd-lists@BSDforge.com, FreeBSD Hackers Message-ID: <99287b7a-b922-f161-f05e-34d2db27d301@m5p.com> Subject: Re: error: invalid operands to binary expression References: In-Reply-To: --wiVfL4bC3LPI8GBy0J5hXDpEX3BtOjwmZ Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 12/19/17 22:12, Chris H wrote: > Apologies if this was better posted on ports@. But given the > circumstances, I thought this might be a better choice. :-) > OK I've been hacking on this port all day. I've silenced all > the warnings, and errors; save one: >=20 > ImageEventBox.cpp:152:26: error: invalid operands to binary expression > ('Glib::RefPtr' and 'int') > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 if(ImagePixbuf_Original !=3D 0 && = loaded =3D=3D true) > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ~~~~~~~~~~~~~~~~= ~~~~ ^=C2=A0 ~ >=20 > This *should* be easy to deal with, and I'm probably just over > complicating it. But I'm stuck. Please help. >=20 > Thanks! >=20 > --Chris > [...] Glib::RefPtr can't be compared to an integer. Compare it to NULL (or nullptr in C++11). Or implicitly convert it to bool: if(ImagePixbuf_Original && loaded =3D=3D true) -- George --wiVfL4bC3LPI8GBy0J5hXDpEX3BtOjwmZ-- --9TP6ywOODsvxSYsESI8rWB5JmwelRS02r Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAlo51oMACgkQwRES3m+p 4fkEfxAAjTDN+foQtKHnOL+HzzvX2+nKuADYeMftty9UbOnk2hR+vym2BWfeWY5q WCISR3mIm0E3L2Q5H2oUjSNbXRAkrovV4Zaj86r6Hgo6/n6wUixZpztymod9lO1Q YIxxwv/uHJU1yEujnPP8ovCxGwVL4wjHDuHTci3f71hRVHawXBRH44Q41ar77MP0 199jUH+LserrsYSsVnSEC15ZWbEp7MbostGgv2o9qdMoUTBepfPLiNpyEu6CbBkm GKN6t5Pzz/YnjJxqoQff5btENqe5lkpZg5QGqjRNkoBtoX8L3Jnv2HkQxAUW3cNj sGvgTAfn6xsgreeXwzJ99lT0+dQRf6vW793JfVmb/5qUS0WcW+OLI7k/yz0KmXVr 5Mbvx7xIKVRUXVoO68zkIM/5PvTEvd4EW2jYGRZg1nGb/XwAwNQgEk/jTx/6Z1/y ZGUj1n28KuRq+I/0lgUJZHaMGBsGEoPEJwqKutPM8o9QqIXeG/JtQHCG3O2glcz5 4r26MgKTTnIENNRQSxNZKegSNvSYwAduxSWOEO725AOenUu/Qa3FFfwyz1wJbHxN rDdFDTNlm5HiMueX8f8AiMX5gOehLEEcCFCixxydraQ9oY1ye89bglN0Xn51R5a1 cd9ngQ2lja20Y9DxfCIpFBbM8mLbSvnl3Q0TLg338H9qjoabq5Y= =TwnJ -----END PGP SIGNATURE----- --9TP6ywOODsvxSYsESI8rWB5JmwelRS02r-- From owner-freebsd-hackers@freebsd.org Wed Dec 20 03:56:31 2017 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 D48FDE90E6B for ; Wed, 20 Dec 2017 03:56:31 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (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 A4DC57AB85 for ; Wed, 20 Dec 2017 03:56:31 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id vBK3wNcP069509; Tue, 19 Dec 2017 19:58:29 -0800 (PST) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 Cc: "FreeBSD Hackers" In-Reply-To: <99287b7a-b922-f161-f05e-34d2db27d301@m5p.com> From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: "George Mitchell" Subject: Re: error: invalid operands to binary expression Date: Tue, 19 Dec 2017 19:58:29 -0800 Message-Id: <18f92fc762e48211b4ad967afa0f2ad3@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Dec 2017 03:56:31 -0000 On Tue, 19 Dec 2017 22:18:20 -0500 "George Mitchell" said > On 12/19/17 22:12, Chris H wrote: > > Apologies if this was better posted on ports@=2E But given the > > circumstances, I thought this might be a better choice=2E :-) > > OK I've been hacking on this port all day=2E I've silenced all > > the warnings, and errors; save one: > >=20 > > ImageEventBox=2Ecpp:152:26: error: invalid operands to binary expression > > ('Glib::RefPtr' and 'int') > > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 if(ImagePixbuf_Original !=3D 0 && = loaded =3D=3D true) > > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ~~~~~~~~~~~~~~~~= ~~~~ ^=C2=A0 ~ > >=20 > > This *should* be easy to deal with, and I'm probably just over > > complicating it=2E But I'm stuck=2E Please help=2E > >=20 > > Thanks! > >=20 > > --Chris > > [=2E=2E=2E] >=20 > Glib::RefPtr can't be compared to an integer=2E Compare it to NULL (or > nullptr in C++11)=2E Or implicitly convert it to bool: Yep=2E it's c++11 >=20 > if(ImagePixbuf_Original && loaded =3D=3D true) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I *knew* I was over complicating things=2E That was it, George=2E Thank you, thank you, thank you=2E --Chris >=20 > -- George From owner-freebsd-hackers@freebsd.org Wed Dec 20 08:40:34 2017 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 6C281E9F7B7 for ; Wed, 20 Dec 2017 08:40:34 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 267473C50 for ; Wed, 20 Dec 2017 08:40:33 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [88.217.106.239] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from ) id 1eRZvF-0002ae-Mq; Wed, 20 Dec 2017 09:40:17 +0100 Received: from localhost.my.domain (localhost [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id vBK8eGwE017688 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 20 Dec 2017 09:40:16 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id vBK8eFuo017687; Wed, 20 Dec 2017 09:40:15 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Wed, 20 Dec 2017 09:40:14 +0100 From: Matthias Apitz To: Mouse Cc: David Holland , Eitan Adler , FreeBSD Hackers , tech-misc@NetBSD.org, Kernel@dragonflybsd.org Subject: Re: Objections to converting bsd-family-tree to a dot file Message-ID: <20171220084014.GA17426@c720-r314251> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , Mouse , David Holland , Eitan Adler , FreeBSD Hackers , tech-misc@NetBSD.org, Kernel@dragonflybsd.org References: <201712161949.vBGJnnMR008332@pdx.rh.CN85.dnsmgr.net> <20171218011847.GA12528@panix.com> <20171218185446.GA98@netbsd.org> <201712181938.OAA24711@Stone.Rodents-Montreal.ORG> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline In-Reply-To: <201712181938.OAA24711@Stone.Rodents-Montreal.ORG> X-Operating-System: FreeBSD 12.0-CURRENT r314251 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. User-Agent: Mutt/1.8.0 (2017-02-23) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 88.217.106.239 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Dec 2017 08:40:34 -0000 --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable El d=C3=ADa lunes, diciembre 18, 2017 a las 02:38:44p. m. -0500, Mouse escr= ibi=C3=B3: > > My vote would be to ship it in base as SVG and PDF, and forget the > > text version. This is 2017 and everyone has a PDF reader of some > > kind in their UI somewhere. >=20 > Yes, and I love you too. >=20 > I'm just glad I have copies of the text file while it still was a text > file. >=20 > /~\ The ASCII Mouse > \ / Ribbon Campaign > X Against HTML mouse@rodents-montreal.org > / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B I'd prefer to keep it as text (or even ASCII) because we will not gain much= from converting it to some other format. Who wants to have got PDF or JPEG can produce them with a CUPS' pdf backend as: $ lpr -Ppdf bsd-family-tree $ file /home/guru/cups-pdf/bsd-family-tree.pdf /home/guru/cups-pdf/bsd-family-tree.pdf: PDF document, version 1.4 and produce from there the 12 pages as JPEG with: $ convert /home/guru/cups-pdf/bsd-family-tree.pdf /tmp/bsd-family-tree.jpg $ ls -ltr /tmp/bsd-family-tree* -rw-r--r-- 1 guru wheel 77005 20 dic. 09:37 /tmp/bsd-family-tree-0.jpg -rw-r--r-- 1 guru wheel 85724 20 dic. 09:37 /tmp/bsd-family-tree-1.jpg -rw-r--r-- 1 guru wheel 82309 20 dic. 09:37 /tmp/bsd-family-tree-2.jpg -rw-r--r-- 1 guru wheel 79413 20 dic. 09:37 /tmp/bsd-family-tree-3.jpg -rw-r--r-- 1 guru wheel 70221 20 dic. 09:37 /tmp/bsd-family-tree-4.jpg -rw-r--r-- 1 guru wheel 162568 20 dic. 09:37 /tmp/bsd-family-tree-5.jpg -rw-r--r-- 1 guru wheel 155729 20 dic. 09:37 /tmp/bsd-family-tree-6.jpg -rw-r--r-- 1 guru wheel 167975 20 dic. 09:37 /tmp/bsd-family-tree-7.jpg -rw-r--r-- 1 guru wheel 162618 20 dic. 09:37 /tmp/bsd-family-tree-8.jpg -rw-r--r-- 1 guru wheel 153778 20 dic. 09:37 /tmp/bsd-family-tree-9.jpg -rw-r--r-- 1 guru wheel 178014 20 dic. 09:37 /tmp/bsd-family-tree-10.jpg -rw-r--r-- 1 guru wheel 9893 20 dic. 09:37 /tmp/bsd-family-tree-11.jpg Btw: The file is not ASCII, but UTF-8 due to a German Umlaut in some name: $ iconv -f utf-8 -t ascii bsd-family-tree > /tmp/i iconv: warning: invalid characters: 1 $ diff bsd-family-tree /tmp/i 739c739 < Andreas Klemm, Lars K=C3=B6ller. If you're going to San Francisco ... --- > Andreas Klemm, Lars K?ller. If you're going to San Francisco ... matthias --=20 Matthias Apitz, =E2=9C=89 guru@unixarea.de, =E2=8C=82 http://www.unixarea.d= e/ =F0=9F=93=B1 +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEXmn7rBYYViyzy/vBR8z35Hb+nREFAlo6IegACgkQR8z35Hb+ nRHTqA//b/neESan7Dnw4D98iFeq7bcgtUNRVbJGTELrKrG8q2IqkF28A42fhcU5 M8APA1O2LFSDtinjPGVl1EwQOqCp8JusRlwkmAXBwIpuPhQKuIaH6SZxpoY5Z+QZ MHkERqtXgP5naTNdMZzfm+vVKlvEMaGqhTB4yP+2rUyw5f4bXa1JPJlWYziMOgKb d8Sr8KWlA6SJG6xyuLvpLJeEgP2cQxFpuC+7LbwVWR8ujDMsUfC1ep9q7paUnAFG hHCuCO6WROubCdm1G5yd0qxhSoX37cAITR1SMxarPahJ/2AwNfAnqM0B/itHCm3U mYHrWPD+u4JmjWgyNWYw68dKf2At3F+r4C6sWN2uKX0WJrqCUTnHoNNzyPFaBUMO 7ijdXDRywWZzNw2zmdC5lFSIvAUxp2yKPKCvQRuCprV0FolyGwPQybDg/rLpMzwo xWfpadt2mPXOIgLiWvMSBTgRK+eZmHZyARNR6bfTiXoB3XhWoIc/FleTdklB//KI 4YXB4VfKnvOYRQEASwCrRLcS6VZqDb+SeX8Kg/fOkABqygkUG47dqvVX13oiEYy2 0JeYEc4eWrRPrB2w1M5CkW1CH33Rs3wludayJCLoh7R7zRgn7juCOMnLg9+BfYzT Jje+ngVSt518e1dXWG21H3uFXRDBtxxopeQ0yL5TsoPUQ7Sd9fg= =jMEx -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o-- From owner-freebsd-hackers@freebsd.org Thu Dec 21 09:26:48 2017 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 415B1E895DE for ; Thu, 21 Dec 2017 09:26:48 +0000 (UTC) (envelope-from dvyukov@google.com) Received: from mail-pl0-x234.google.com (mail-pl0-x234.google.com [IPv6:2607:f8b0:400e:c01::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 1CDC97EFA2 for ; Thu, 21 Dec 2017 09:26:48 +0000 (UTC) (envelope-from dvyukov@google.com) Received: by mail-pl0-x234.google.com with SMTP id o2so10658783plk.12 for ; Thu, 21 Dec 2017 01:26:48 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=X++YWpS+V9eSU7nkPLqBuMLDggalZrA3WSgEdAtMQTA=; b=sIb1iMH6ThXP2PteF9ZQVZg/FS5S1EKlDWFwLBiwY5Em4+vl+BrpdXziDQjonbY5vZ CyUprPmejnDjUvLX7pNOsjeRJdUu9dSmdx9kTn7s28iaKyHh9gq/BpnqZzAwTljrSnep sENSukpEQ/BL8SvmvzrgSIYnxzerd4dFAnacP/9ZkRLF/3UkfYaWltun6ZetgEJCHJV3 qPeWT0JnI7XixennVZ/Hb9HJxaBHW/8gLp/y3imGt31urXXBLAiEQGl1pM8vqu1QTAIP vD1M4MwST05fSa5oNE1/k0QS7MVDMAGDyfphHw/JfUxEOPfT68La4cKSwzJdVR+pEOsC EApw== X-Gm-Message-State: AKGB3mJpeL1ApP5gMISVC6vG//zumP8kngRb2zAePpD6CWqH9NS1J303 PcKCDJ6x5OYQrF+Z4Qvd/FPgSSxNjdJ0g2LBY0Hsq7KQSEY= X-Google-Smtp-Source: ACJfBosjLkDsHji/gwGwTIsd62o1jkFFb4qiUV+xLowk3SjB8Lu20sYaBjhfxenD8zKfM45+Xqt+qGEOp5nXELCcIAo= X-Received: by 10.84.244.12 with SMTP id g12mr9732016pll.69.1513848407187; Thu, 21 Dec 2017 01:26:47 -0800 (PST) MIME-Version: 1.0 Received: by 10.236.138.12 with HTTP; Thu, 21 Dec 2017 01:26:26 -0800 (PST) From: Dmitry Vyukov Date: Thu, 21 Dec 2017 10:26:26 +0100 Message-ID: Subject: syzkaller for freebsd again To: Ed Maste Cc: FreeBSD Hackers , syzkaller Content-Type: text/plain; charset="UTF-8" X-Mailman-Approved-At: Thu, 21 Dec 2017 11:25:21 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Dec 2017 09:26:48 -0000 Hi Ed, I see that you are using syzkaller and I've seen syzkaller mentioned in some frebsd announce. Do you mind sharing how extensively you are using it and how many bugs you have found? I wanted to point out that freebsd support in syzkaller is still far from being complete. We still need better descriptions of system calls and kernel code coverage, report parsing need improvements as well. For linux we are now finding 100+ bugs per months in a completely automated fashion using syzbot system: https://groups.google.com/forum/#!forum/syzkaller-bugs https://github.com/google/syzkaller/blob/master/docs/syzbot.md which does continuous building, fuzzing, automatic aggregation, reporting and status tracking. We could setup a similar thing for freebsd, but for that we need support for building freebsd kernel and GCE-compatible images. For linux that code lives here: https://github.com/google/syzkaller/blob/master/pkg/kernel/kernel.go https://github.com/google/syzkaller/blob/master/pkg/kernel/generated.go I don't know how size of freebsd kernel compares to linux, but if you don't measure bugs in hundreds, no, syzkaller is not yet working :) From owner-freebsd-hackers@freebsd.org Sat Dec 23 05:26:31 2017 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 B540AE99B18 for ; Sat, 23 Dec 2017 05:26:31 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-161.reflexion.net [208.70.210.161]) (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 628EF7650D for ; Sat, 23 Dec 2017 05:26:30 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 22174 invoked from network); 23 Dec 2017 05:26:24 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 23 Dec 2017 05:26:24 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Sat, 23 Dec 2017 00:26:24 -0500 (EST) Received: (qmail 21688 invoked from network); 23 Dec 2017 05:26:23 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 23 Dec 2017 05:26:23 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 29A4CEC9398; Fri, 22 Dec 2017 21:26:23 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: TARGET_ARCH=powerpc64 jump from head -r326192 to -r327075: g_event crashes with "instruction storage interrupt" Message-Id: <39C042C5-9800-464C-84AC-677DB45DA1C1@dsl-only.net> Date: Fri, 22 Dec 2017 21:26:22 -0800 To: FreeBSD PowerPC ML , FreeBSD Hackers X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Dec 2017 05:26:31 -0000 [Note: I experiment with using clang as the build and system compiler for TARGET_ARCH=3Dpowerpc64 .] I attempted to update a old so-called PowerMac "Quad Core" from head -r326192 to -r328075, noting special instructions that have been published. (This was a non-debug kernel build.) Unfortunately around the: . . . cd0: 66.700MB/s transfers (UDMA4, ATPI 12bytes, PIO 65534bytes) cd0: Attempt Trying to mount from ufs:/dev/ufs/FBSDG5Lrootfs [rw,noatime]. . . There ends up being a repeatable kernel trap: (transcribed from pictures, but with notes added) fatal kernel trap: (NOTE: The above can be the line before the "Trying to mount" line, after the "cd0: Attempt" line.) exception =3D 0x400 (instruction storage interrupt) virtual address =3D 0x3c4c009438427518 srr0 =3D 0x3c4c009438427518 srr1 =3D 0x9000000040009032 lr =3D 0x14234e8 curthread =3D 0x3d52a80 pid =3D 13, comm =3D g_event [ thread pid 13 tid 100019 ] Stopped at 0x3c4c009438427518 It reports: Tracing command geom pid 13 tid 100019 td 0x3d52a80 (CPU 0) 0xC0000000032966b0: at g_new_provider_event+0x144 0xC0000000032966f0: at g_run_events+0x530 0xC000000003296830: at g_event_procbody+0x94 0xC000000003296860: at fork_exit+0xd8 0xC0000000032968f0: at fork_trampoline+0x18 0xC000000003296920: at blocked_loop+0x38 These details do not vary between attempts. =46rom what I gather the code jumped to 0x3c4c009438427518 but that is not from an executable page for the context at the time. On the -r326192 powerpc system /dev/ufs/FBSDG5Lrootfs mounts just fine. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-hackers@freebsd.org Sat Dec 23 05:58:42 2017 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 DF5C0E9AF96 for ; Sat, 23 Dec 2017 05:58:42 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-100.reflexion.net [208.70.210.100]) (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 8BB7C775E3 for ; Sat, 23 Dec 2017 05:58:41 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 2132 invoked from network); 23 Dec 2017 05:58:35 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 23 Dec 2017 05:58:35 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Sat, 23 Dec 2017 00:58:35 -0500 (EST) Received: (qmail 31663 invoked from network); 23 Dec 2017 05:58:34 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 23 Dec 2017 05:58:34 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 1F942EC9398; Fri, 22 Dec 2017 21:58:34 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: TARGET_ARCH=powerpc64 jump from head -r326192 to -r327075: g_event crashes with "instruction storage interrupt" [sidestepped by avoiding use of drive labels] Date: Fri, 22 Dec 2017 21:58:33 -0800 References: <39C042C5-9800-464C-84AC-677DB45DA1C1@dsl-only.net> To: FreeBSD PowerPC ML , FreeBSD Hackers In-Reply-To: <39C042C5-9800-464C-84AC-677DB45DA1C1@dsl-only.net> Message-Id: X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Dec 2017 05:58:43 -0000 [Avoiding referencing partitions via labels avoided the crash.] On 2017-Dec-22, at 9:26 PM, Mark Millard wrote: > [Note: I experiment with using clang as the build and > system compiler for TARGET_ARCH=powerpc64 .] > > I attempted to update a old so-called PowerMac "Quad Core" > from head -r326192 to -r328075, noting special instructions > that have been published. (This was a non-debug kernel > build.) > > Unfortunately around the: > > . . . > cd0: 66.700MB/s transfers (UDMA4, ATPI 12bytes, PIO 65534bytes) > cd0: Attempt > Trying to mount from ufs:/dev/ufs/FBSDG5Lrootfs [rw,noatime]. . . > > There ends up being a repeatable kernel trap: > (transcribed from pictures, but with notes added) > > fatal kernel trap: > (NOTE: The above can be the line before the "Trying to mount" line, > after the "cd0: Attempt" line.) > > exception = 0x400 (instruction storage interrupt) > virtual address = 0x3c4c009438427518 > srr0 = 0x3c4c009438427518 > srr1 = 0x9000000040009032 > lr = 0x14234e8 > curthread = 0x3d52a80 > pid = 13, comm = g_event > > [ thread pid 13 tid 100019 ] > Stopped at 0x3c4c009438427518 > > It reports: > > Tracing command geom pid 13 tid 100019 td 0x3d52a80 (CPU 0) > 0xC0000000032966b0: at g_new_provider_event+0x144 > 0xC0000000032966f0: at g_run_events+0x530 > 0xC000000003296830: at g_event_procbody+0x94 > 0xC000000003296860: at fork_exit+0xd8 > 0xC0000000032968f0: at fork_trampoline+0x18 > 0xC000000003296920: at blocked_loop+0x38 > > These details do not vary between attempts. > > From what I gather the code jumped to 0x3c4c009438427518 > but that is not from an executable page for the context > at the time. > > On the -r326192 powerpc system /dev/ufs/FBSDG5Lrootfs > mounts just fine. > I adjusted: /boot/loader.conf /etc/rc.conf /etc/fstab to avoid use of: geom_label_load="YES" dumpdev="/dev/label/FBSDG5Lswap" /dev/ufs/FBSDG5Lrootfs / ufs rw,noatime 1 1 /dev/label/FBSDG5Lswap none swap sw 0 0 Using instead: dumpdev="/dev/ada0s4" /dev/ada0s3 / ufs rw,noatime 1 1 /dev/ada0s4 none swap sw 0 0 This allowed the boot to work normally. === Mark Millard markmi at dsl-only.net From owner-freebsd-hackers@freebsd.org Sat Dec 23 06:40:43 2017 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 90395E9BFDD for ; Sat, 23 Dec 2017 06:40:43 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-134.reflexion.net [208.70.210.134]) (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 3BCAD787DB for ; Sat, 23 Dec 2017 06:40:42 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 8267 invoked from network); 23 Dec 2017 06:33:56 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 23 Dec 2017 06:33:56 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Sat, 23 Dec 2017 01:33:56 -0500 (EST) Received: (qmail 27336 invoked from network); 23 Dec 2017 06:33:56 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 23 Dec 2017 06:33:56 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 6A259EC95DA; Fri, 22 Dec 2017 22:33:55 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: TARGET_ARCH=powerpc64 jump from head -r326192 to -r327075: g_event crashes with "instruction storage interrupt" [kldload -n filemon crashes the system] Date: Fri, 22 Dec 2017 22:33:54 -0800 References: <39C042C5-9800-464C-84AC-677DB45DA1C1@dsl-only.net> To: Justin Hibbits , Nathan Whitehorn , FreeBSD PowerPC ML , FreeBSD Hackers In-Reply-To: Message-Id: <244D5C85-E1E7-4349-A46A-1D275D54833F@dsl-only.net> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Dec 2017 06:40:43 -0000 [I attempted something that involved kldload -n filemon . That gives a similar system crash (by the virtual address reported and the type of exception). It seems similar to geom_label_load="YES" in /boot/loader.conf getting a crash.] On 2017-Dec-22, at 9:58 PM, Mark Millard wrote: > [Avoiding referencing partitions via labels > avoided the crash.] > > On 2017-Dec-22, at 9:26 PM, Mark Millard wrote: > >> [Note: I experiment with using clang as the build and >> system compiler for TARGET_ARCH=powerpc64 .] >> >> I attempted to update a old so-called PowerMac "Quad Core" >> from head -r326192 to -r328075, noting special instructions >> that have been published. (This was a non-debug kernel >> build.) >> >> Unfortunately around the: >> >> . . . >> cd0: 66.700MB/s transfers (UDMA4, ATPI 12bytes, PIO 65534bytes) >> cd0: Attempt >> Trying to mount from ufs:/dev/ufs/FBSDG5Lrootfs [rw,noatime]. . . >> >> There ends up being a repeatable kernel trap: >> (transcribed from pictures, but with notes added) >> >> fatal kernel trap: >> (NOTE: The above can be the line before the "Trying to mount" line, >> after the "cd0: Attempt" line.) >> >> exception = 0x400 (instruction storage interrupt) >> virtual address = 0x3c4c009438427518 >> srr0 = 0x3c4c009438427518 >> srr1 = 0x9000000040009032 >> lr = 0x14234e8 >> curthread = 0x3d52a80 >> pid = 13, comm = g_event >> >> [ thread pid 13 tid 100019 ] >> Stopped at 0x3c4c009438427518 >> >> It reports: >> >> Tracing command geom pid 13 tid 100019 td 0x3d52a80 (CPU 0) >> 0xC0000000032966b0: at g_new_provider_event+0x144 >> 0xC0000000032966f0: at g_run_events+0x530 >> 0xC000000003296830: at g_event_procbody+0x94 >> 0xC000000003296860: at fork_exit+0xd8 >> 0xC0000000032968f0: at fork_trampoline+0x18 >> 0xC000000003296920: at blocked_loop+0x38 >> >> These details do not vary between attempts. >> >> From what I gather the code jumped to 0x3c4c009438427518 >> but that is not from an executable page for the context >> at the time. >> >> On the -r326192 powerpc system /dev/ufs/FBSDG5Lrootfs >> mounts just fine. >> > > I adjusted: > > /boot/loader.conf > /etc/rc.conf > > /etc/fstab > > to avoid use of: > > geom_label_load="YES" > dumpdev="/dev/label/FBSDG5Lswap" > > /dev/ufs/FBSDG5Lrootfs / ufs rw,noatime 1 1 > /dev/label/FBSDG5Lswap none swap sw 0 0 > > Using instead: > > dumpdev="/dev/ada0s4" > > /dev/ada0s3 / ufs rw,noatime 1 1 > /dev/ada0s4 none swap sw 0 0 > > This allowed the boot to work normally. The use of filemon was tied to buildworld/buildkernel related activity. But it was kldload that was listed in the crash from the attempted kldload -n filemon. This would seem similar to having: geom_label_load="YES" in /boot/loader.conf === Mark Millard markmi at dsl-only.net