From owner-freebsd-questions@freebsd.org Sun Jan 7 02:30:47 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 623DEE5DC4C for ; Sun, 7 Jan 2018 02:30:47 +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 1341D6F156 for ; Sun, 7 Jan 2018 02:30:47 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: by mail-ua0-x22a.google.com with SMTP id e39so4827047uae.12 for ; Sat, 06 Jan 2018 18:30:47 -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=VLqTthAYfa6feC4e0sYo8U/OAxZz3KlRLSUBttkayOw=; b=hlmkfvESu5pUyudcc7MEEQyI0QO8HVzJt42k+wb5etX2SCCjC5BX9SR4Z130YNag3X +Pu2fXCOfPwIsRhKuHYO974w5jR47xZ4ZB0VLY1/hW3dwCtONDDgo917qTHu7W9V1m8R nNvx2UgiQgQoMkdSIwYpbfovOpprPGiAzUCyXtWUo8mo3rSYkHNmT7oo1CZqUtYm5XYQ t4Z2rT6tYmlOpbcrON8f/g5LBS7KwWd/lWsF+8wfyYb6lfCOoFKqQdf/1tALMrCv5FIL uGfUA0ujpXNZ46N/PzAd/qxGgabA5GGhpYD6i5c5E6fnXyvd6a7ycPv3a0URkTX3C12D sucA== 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=VLqTthAYfa6feC4e0sYo8U/OAxZz3KlRLSUBttkayOw=; b=P9ejNHHqZy3LnPxTbtV3MPAGSAQoVdLPh787XHzM/5xA02wnTwGDqg+B2rE7W4M59n RDTUco7R18WBFmBe1Wr13Wzn33nXVDIdBIvVzpq2C2OyZmB7suu+AjVqzkdC3DfxC8rr Z7hUviCM/LM/Wg8V3gjlu/ejR/ymqCWUTlDbNfH/wnyVGdBgp/6ILwzxoi03lrRjD8tM +m753Sgy5C9J1YB1Ix+BgnnnA2L1D8hSEwHs8OhzngjRPjeV95OGjeeVCZ/xQG0RHflN r6dpR2/EL7w+ZAN4avC5KyOD/OWKqrhY5s9nwNyAvyZe1bNIqaiQas+K8ReFAlmFq5D9 6o4w== X-Gm-Message-State: AKGB3mLG1bT4zpuu/hTYH31ie2bGhLj0E3UkL3oik31IMhg1kD/iZEni oCjqdM6bFNqY7oA1/uw4J4bOMaZm0WuzAE+n6HU= X-Google-Smtp-Source: ACJfBosSldAJ0FK31vTGDXw75gSMbABzYbL8mbgSCYbEhBxoSL2X7JflF9aKKbDaUW7bThYP2BJyiK8h1yUQM7n1uEo= X-Received: by 10.176.19.201 with SMTP id n9mr7702522uae.16.1515292245723; Sat, 06 Jan 2018 18:30:45 -0800 (PST) MIME-Version: 1.0 References: <35571809-560c-1bbd-376f-45e59789e6cc@yahoo.com> In-Reply-To: <35571809-560c-1bbd-376f-45e59789e6cc@yahoo.com> From: Ben Woods Date: Sun, 07 Jan 2018 02:30:35 +0000 Message-ID: Subject: Re: mount -a problem with /etc/fstab To: Per Gunnarsson Cc: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2018 02:30:47 -0000 On Sat, 6 Jan 2018 at 3:50 am, Per Gunnarsson via freebsd-questions < freebsd-questions@freebsd.org> wrote: > When I try mount -a I get: > > fstab: /etc/fstab:9: Inappropriate file type or format > fstab: /etc/fstab:10: Inappropriate file type or format > > My fstab below: > > > /dev/ada0p2 / ufs rw 1 1 > /dev/ada0p3 none swap sw 0 0 > /dev/ada0p4 /tmp ufs rw 2 2 > /dev/ada0p5 /var ufs rw 2 2 > /dev/ada0p6 /usr ufs rw 2 2 > /dev/ada0p7 /home ufs rw 2 2 > > /dev/linux_lvm/konjak-vg-root /debian/root ext4 > mountprog=3D/usr/local/bin/ext4fuse allow_other,ro 0 0 > > /dev/linux_lvm/konjak-vg-home /debian/home ext4 > mountprog=3D/usr/local/bin/ext4fuse allow_other,ro 0 0 > Whilst I am not sure about the legitimacy of these lines in general, I believe you should have a comma instead of a space between the end of the mountprog option and the allow_other option. See the fstab(5) manpage: https://man.freebsd.org/fstab =E2=80=9Dfields on each line are separated by tabs or spaces.=E2=80=9D =E2=80=9CThe fourth field, (*fs*_*mntops*), describes the mount options ass= ociated with the file system. It is formatted as a comma separated list of options. It contains at least the type of mount (see *fs*_*type* below) plus any additional options appropriate to the file system type. See the options flag (*-o*) in the mount(8) page and the file system specific page, such as mount_nfs(8) , for additional options that may be specified. All options that can be given to the file system specific mount commands can be used in *fstab* as well. They just need to be formatted a bit differently. The arguments of the *-o* option can be used without the preceding *-o* flag. Other options need both the file system specific flag and its argument, separated by an equal sign. For example, mounting an msdosfs(5) filesystem, the options -o sync -o noatime -m 644 -M 755 -u foo -g bar should be written as sync,noatime,-m=3D644,-M=3D755,-u=3Dfoo,-g=3Dbar in the option field of *fstab*.=E2=80=9D Regards, Ben --=20 -- From: Benjamin Woods woodsb02@gmail.com From owner-freebsd-questions@freebsd.org Sun Jan 7 11:26:59 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 876C3E66F83 for ; Sun, 7 Jan 2018 11:26:59 +0000 (UTC) (envelope-from p.gunnarsson@yahoo.com) Received: from sonic308-18.consmr.mail.ir2.yahoo.com (sonic308-18.consmr.mail.ir2.yahoo.com [77.238.178.146]) (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 2601982047 for ; Sun, 7 Jan 2018 11:26:58 +0000 (UTC) (envelope-from p.gunnarsson@yahoo.com) X-YMail-OSG: F2Lgps8VM1kEOrX2gw2QWU4orrrG5LM9Un_giQatme3g0qGdNYoN3_skTevDF.o zvOSE525pL5_bbrZ4yMxS12_6LGY8sQ4Y2gaavdk5oKE2o9u.i9wKZWa0s0p6_Y0IwhRH5BB109t m72ilvtosc3uGM6eOzctYjBDk7XNBzmWO2hURwY1FzwvzM3O01EizoS62BdT41eZGJU051S7Xs66 jkXV8o2hah3or7xpRDrXl1gdGlqcuDG3R0QymJmHd0CP1H.0jfXcCDuEiUxTloMjCzhkQCDpZqMy LSLV2SD.MndSpffLjrqOJJ00UzMFWq5WZ0NvmEPlSirfhUa4ClWetYc2xPYjg7odhTUnVBkTIYPn momyvagWehQpYBEUguwabmL9X54ENyN3W3j.E_loaHDrXqO08NpHKWdkBEznJHCIC3WdFJlSixOI Mpb2miOCFY84ZVsX8it0StYg59jYSSgmsMncGjQ8cJ2O_8x8LgTPGnRXOl6fWdMsVe.eC9BYYbbo FwIlTLcIksb4gDkATeJkRG0itFWOPOgzOgAbfNyk- Received: from sonic.gate.mail.ne1.yahoo.com by sonic308.consmr.mail.ir2.yahoo.com with HTTP; Sun, 7 Jan 2018 11:26:51 +0000 Received: from smtpgate103.mail.ir2.yahoo.com (EHLO [10.0.0.2]) ([217.146.188.6]) by smtp404.mail.ir2.yahoo.com (JAMES SMTP Server ) with ESMTPA ID afaa6e1c347d1b79cf476416c087650e for ; Sun, 07 Jan 2018 11:16:41 +0000 (UTC) Subject: Re: mount -a problem with /etc/fstab To: FreeBSD References: <35571809-560c-1bbd-376f-45e59789e6cc@yahoo.com> From: Per Gunnarsson Message-ID: Date: Sun, 7 Jan 2018 12:16:39 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2018 11:26:59 -0000 Thanks for the information! The last lines of my /etc/fstab now look like this: /dev/linux_lvm/konjak-vg-root   /debian/root ext4 mountprog=/usr/local/bin/ext4fuse,allow_other,ro /dev/linux_lvm/konjak-vg-home   /debian/home ext4 mountprog=/usr/local/bin/ext4fuse,allow_other,ro and now mount -a works :-) On 01/07/18 03:30, Ben Woods wrote: > On Sat, 6 Jan 2018 at 3:50 am, Per Gunnarsson via freebsd-questions > > > wrote: > > When I try mount -a I get: > > fstab: /etc/fstab:9: Inappropriate file type or format > fstab: /etc/fstab:10: Inappropriate file type or format > > My fstab below: > > > /dev/ada0p2     /               ufs     rw      1       1 > /dev/ada0p3     none            swap    sw      0       0 > /dev/ada0p4     /tmp            ufs     rw      2       2 > /dev/ada0p5     /var            ufs     rw      2       2 > /dev/ada0p6     /usr            ufs     rw      2       2 > /dev/ada0p7     /home           ufs     rw      2       2 > > /dev/linux_lvm/konjak-vg-root   /debian/root ext4 > mountprog=/usr/local/bin/ext4fuse allow_other,ro 0 0 > > /dev/linux_lvm/konjak-vg-home   /debian/home ext4 > mountprog=/usr/local/bin/ext4fuse allow_other,ro 0 0 > > > Whilst I am not sure about the legitimacy of these lines in general, I > believe you should have a comma instead of a space between the end of > the mountprog option and the allow_other option. > > See the fstab(5) manpage: > > https://man.freebsd.org/fstab > > ”fields on each line are separated by tabs or spaces.” > > > “The fourth field, (/fs/_/mntops/), describes the mount options > associated with the file system. It is formatted as a comma separated > list of options. It contains at least the type of mount (see > /fs/_/type/below) plus any additional options appropriate to the file > system type. See the options flag (*-o*) in the mount(8) > page > and the file system specific page, such as mount_nfs(8) > , > for additional options that may be specified. All options that can be > given to the file system specific mount commands can be used in > *fstab*as well. They just need to be formatted a bit differently. The > arguments of the *-o*option can be used without the preceding > *-o*flag. Other options need both the file system specific flag and > its argument, separated by an equal sign. > > > For example, mounting an msdosfs(5) > filesystem, > the options > >     -o sync -o noatime -m 644 -M 755 -u foo -g bar > > should be written as > > sync,noatime,-m=644,-M=755,-u=foo,-g=bar > > in the option field of *fstab*.” > > > Regards, > Ben > -- > > -- > From: Benjamin Woods > woodsb02@gmail.com From owner-freebsd-questions@freebsd.org Sun Jan 7 15:30:08 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BAFB1E721DA for ; Sun, 7 Jan 2018 15:30:08 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mail.inka.de (quechua.inka.de [IPv6:2a04:c9c7:0:1073:217:a4ff:fe3b:e77c]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 861376A7B5 for ; Sun, 7 Jan 2018 15:30:08 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mips.inka.de (news@[127.0.0.1]) by mail.inka.de with uucp (rmailwrap 0.5) id 1eYCth-0003r4-Mz; Sun, 07 Jan 2018 16:30:05 +0100 Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.15.2/8.15.2) with ESMTP id w07FSepU082078 for ; Sun, 7 Jan 2018 16:28:40 +0100 (CET) (envelope-from news@lorvorc.mips.inka.de) Received: (from news@localhost) by lorvorc.mips.inka.de (8.15.2/8.15.2/Submit) id w07FSeW4082077 for freebsd-questions@freebsd.org; Sun, 7 Jan 2018 16:28:40 +0100 (CET) (envelope-from news) To: freebsd-questions@freebsd.org From: Christian Weisgerber Newsgroups: list.freebsd.questions Subject: Re: Poor default fonts in Firefox Date: Sun, 7 Jan 2018 15:28:40 -0000 (UTC) Message-ID: References: <20171227194053.GA2237@c720-r314251> <20171228203457.GA3562@c720-r314251> User-Agent: slrn/1.0.3 (FreeBSD) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2018 15:30:08 -0000 On 2017-12-28, Matthias Apitz wrote: >> > I have a normal ports installation and the above page renders fine. >> > Can you please post somewhere a screen of your FF. >> >> http://shell.uugrn.org/~naddy/bbcnews.xwd.xz > > Mine is here: http://www.unixarea.de/my.xwd.gz > > I'm not an expert of fonts and rendering ... comments? Well, that is some vector font and definitely not the bitmap font that you get by default. -- Christian "naddy" Weisgerber naddy@mips.inka.de From owner-freebsd-questions@freebsd.org Sun Jan 7 16:00:07 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4D3D3E738A6 for ; Sun, 7 Jan 2018 16:00:07 +0000 (UTC) (envelope-from naddy@mips.inka.de) Received: from mail.inka.de (quechua.inka.de [IPv6:2a04:c9c7:0:1073:217:a4ff:fe3b:e77c]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 111766C2DC for ; Sun, 7 Jan 2018 16:00:07 +0000 (UTC) (envelope-from naddy@mips.inka.de) Received: from mips.inka.de (naddy@[127.0.0.1]) by mail.inka.de with uucp (rmailwrap 0.5) id 1eYDMj-0004IW-ET; Sun, 07 Jan 2018 17:00:05 +0100 Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.15.2/8.15.2) with ESMTP id w07FwWFA085244; Sun, 7 Jan 2018 16:58:32 +0100 (CET) (envelope-from naddy@lorvorc.mips.inka.de) Received: (from naddy@localhost) by lorvorc.mips.inka.de (8.15.2/8.15.2/Submit) id w07FwWTg085243; Sun, 7 Jan 2018 16:58:32 +0100 (CET) (envelope-from naddy) Date: Sun, 7 Jan 2018 16:58:32 +0100 From: Christian Weisgerber To: Polytropon Cc: freebsd-questions@freebsd.org Subject: Re: Poor default fonts in Firefox Message-ID: <20180107155832.GA84935@lorvorc.mips.inka.de> References: <20171227174525.cc1e9047.freebsd@edvax.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171227174525.cc1e9047.freebsd@edvax.de> User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2018 16:00:07 -0000 Polytropon: > > You install a new FreeBSD machine with a graphics display, install > > the xorg and firefox ports on it, all default options, start browsing > > the web... and you see that some sites (e.g. http://www.bbc.com/news) > > are presented with pixelated fonts like something out of the 1990s. > > > > What do you do? > > You install the recommended font packages. :-) Well, there is no such recommendation. > > My personal solution for the last few years has been to pinch > > OpenBSD's etc/fonts/conf.avail/31-nonmst.conf file... > > This isn't needed as soon as the webfonts package has > been installed. And even the DejaVu fonts need to be > installed manually, if I remember correctly. No, Deja Vu is a standard dependency: x11/xorg -> x11-fonts/xorg-fonts -> x11-fonts/x11-fonts/xorg-fonts-truetype -> x11-fonts/dejavu Installing webfonts does NOT fix the problem. fc-match shows that popular font names like "Helvetica" and "Times" are still mapped to the same bitmap fonts as before and that's what you still get in Firefox. -- Christian "naddy" Weisgerber naddy@mips.inka.de From owner-freebsd-questions@freebsd.org Sun Jan 7 16:25:07 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E508EE74982 for ; Sun, 7 Jan 2018 16:25:07 +0000 (UTC) (envelope-from naddy@mips.inka.de) Received: from mail.inka.de (quechua.inka.de [IPv6:2a04:c9c7:0:1073:217:a4ff:fe3b:e77c]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B014C6D08A for ; Sun, 7 Jan 2018 16:25:07 +0000 (UTC) (envelope-from naddy@mips.inka.de) Received: from mips.inka.de (naddy@[127.0.0.1]) by mail.inka.de with uucp (rmailwrap 0.5) id 1eYDkw-00057R-2B; Sun, 07 Jan 2018 17:25:06 +0100 Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.15.2/8.15.2) with ESMTP id w07GMhm5086015; Sun, 7 Jan 2018 17:22:43 +0100 (CET) (envelope-from naddy@lorvorc.mips.inka.de) Received: (from naddy@localhost) by lorvorc.mips.inka.de (8.15.2/8.15.2/Submit) id w07GMgqR086014; Sun, 7 Jan 2018 17:22:42 +0100 (CET) (envelope-from naddy) Date: Sun, 7 Jan 2018 17:22:42 +0100 From: Christian Weisgerber To: Ken Moffat Cc: freebsd-questions@freebsd.org Subject: Re: Poor default fonts in Firefox Message-ID: <20180107162242.GA85530@lorvorc.mips.inka.de> References: <20171227174525.cc1e9047.freebsd@edvax.de> <20171227191445.GA11759@milliways.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171227191445.GA11759@milliways.localdomain> User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2018 16:25:08 -0000 Ken Moffat: > > > You install a new FreeBSD machine with a graphics display, install > > > the xorg and firefox ports on it, all default options, start browsing > > > the web... and you see that some sites (e.g. http://www.bbc.com/news) > > > are presented with pixelated fonts like something out of the 1990s. > > > > > > What do you do? > > Actually, the choice of *which* fonts to use is a very personal > matter. Yes. It's like when you go into a bookstore and buy a book. You choose your personal font. > For anybody who uses fontconfig, tuning it to match your personal > preferences is the right thing to do. I don't use fontcontig. I mean, Firefox does. Or GTK+3. Or something in the graphics stack. But _I_ don't want to get involved. Like most people, I have no interest in typography. It's background. It's an issue I'm happy for other people to solve and I'll just use the end product. Apart from xterm "fixed", the Deja Vu fonts are probably those I've stared at the most over the last years, and without opening a window and checking I can't tell you what form of 'a' or 'g' they use. I only notice typography when there is something glaringly wrong with it. (Like the font changing partway through a book. Or some idiot typesetting a whole book in some decorative sans-serif font. Or Firefox using bitmap fonts.) Anyway, I guess from your point of view, using OpenBSD's 31-nonmst.conf is exactly the thing I should do. -- Christian "naddy" Weisgerber naddy@mips.inka.de From owner-freebsd-questions@freebsd.org Sun Jan 7 16:42:30 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2D1DE7573E for ; Sun, 7 Jan 2018 16:42:30 +0000 (UTC) (envelope-from p.gunnarsson@yahoo.com) Received: from sonic305-20.consmr.mail.ir2.yahoo.com (sonic305-20.consmr.mail.ir2.yahoo.com [77.238.177.82]) (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 63ACC6DD44 for ; Sun, 7 Jan 2018 16:42:30 +0000 (UTC) (envelope-from p.gunnarsson@yahoo.com) X-YMail-OSG: ltNHbBgVM1n3YQ0Ry8Veapgk2wORuB9Cujm6Q4DFKx9ZTH4f4pFh72E0nvfZ3fv GyUNEo4aUBU5bBwB_h_GbdmSHyNAsbi7zYXXPhd.A.mssK4ox5Qcw.kFQKR06bE16_kq6bTjUjEy E9RVJ0EX1tQ6XOdKmlXFUmRNj2zxCfHudJD93P1GAW6l6gjXyYGiqrVTEVRdRel2aGN7ULjFfkVI FgCWjwcJHtGiuVWqkeViz7ERUFptcwBK_2fsSknElAPosNGOAKi0GShWXXAj5nKyRX1dLBxjdRA_ bSEjNMrp0k4hl_oiZxKJ8MMOLZ2vSXKLqMjQuzU_e.dPj1NnrCYaAIwK9piBoGyOR2TM8K4cqnXm l1dtU90wcEIznKTRNbgQhbDQ56RHHjKMqoIsSwwkHzFp3DFjs5mtFwEgjLCmzALWcnkNj4KEHnxk 3gUpgsIVwrj2v7YxCDSQPUaewzaOPhcw6Vyv46YwO4R3WnOaHkhTxo4lCcUkPNwg2gxD3nC8RZKs GoV0cIjlaXtDmHiBaRf2mhVlC1.VDM2UmuJnujSoST6OQIn4i Received: from sonic.gate.mail.ne1.yahoo.com by sonic305.consmr.mail.ir2.yahoo.com with HTTP; Sun, 7 Jan 2018 16:42:22 +0000 Received: from smtp159.mail.ir2.yahoo.com (EHLO [10.0.0.5]) ([46.228.39.122]) by smtp416.mail.ir2.yahoo.com (JAMES SMTP Server ) with ESMTPA ID c8af4cded4cc6d36ca395d93a51543d2 for ; Sun, 07 Jan 2018 16:42:17 +0000 (UTC) Subject: Re: Static noise with microphone To: freebsd-questions@freebsd.org References: <20180105024415.c10765fc.freebsd@edvax.de> <1e7dd86f-f8e0-7611-c187-34fd7374723c@yahoo.com> From: Per Gunnarsson Message-ID: Date: Sun, 7 Jan 2018 17:42:14 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <1e7dd86f-f8e0-7611-c187-34fd7374723c@yahoo.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2018 16:42:30 -0000 On 01/05/18 07:05, Per Gunnarsson via freebsd-questions wrote: > On 01/05/18 02:44, Polytropon wrote: > >> mixer -f /dev/mixer0 > [per@konjak ~]$ mixer -f /dev/mixer0 > Mixer vol      is currently set to 100:100 > Mixer pcm      is currently set to 100:100 > [per@konjak ~]$ mixer -f /dev/mixer1 > Mixer vol      is currently set to  85:85 > Mixer pcm      is currently set to 100:100 > Mixer speaker  is currently set to  74:74 > Mixer line     is currently set to   1:1 > Mixer mic      is currently set to  90:90 > Mixer mix      is currently set to  74:74 > Mixer rec      is currently set to  85:85 > Mixer igain    is currently set to 100:100 > Mixer ogain    is currently set to 100:100 > Recording source: mic > [per@konjak ~]$ mixer -f /dev/mixer2 > Mixer vol      is currently set to  85:85 > Mixer pcm      is currently set to 100:100 > Mixer rec      is currently set to  37:37 > Mixer igain    is currently set to   0:0 > Mixer monitor  is currently set to  67:67 > Recording source: monitor > > I will try playing around with the mixers. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" I have a pindump below hdaa0: NumGPIO=0 NumGPO=0 NumGPI=0 GPIWake=0 GPIUnsol=0 hdaa0: Dumping AFG pins: hdaa0: nid   0x    as seq device       conn  jack    loc color   misc hdaa0:  4 585600f0 15 0  Digital-out   None  Digital 0x18 Unknown 0 DISA hdaa0:     Caps:    OUT              Sense: 0x00000000 (disconnected) hdaa0:  5 185600f0 15 0  Digital-out   Jack  Digital 0x18 Unknown 0 hdaa0:     Caps:    OUT              Sense: 0xc0000000 (connected, ELD valid) hdaa0:  6 585600f0 15 0  Digital-out   None  Digital 0x18 Unknown 0 DISA hdaa0:     Caps:    OUT              Sense: 0x00000000 (disconnected) hdaa0:  7 585600f0 15 0  Digital-out   None  Digital 0x18 Unknown 0 DISA hdaa0:     Caps:    OUT              Sense: 0x00000000 (disconnected) hdaa0: NumGPIO=0 NumGPO=0 NumGPI=0 GPIWake=0 GPIUnsol=0 hdaa1: Dumping AFG pins: hdaa1: nid   0x    as seq device       conn  jack    loc color   misc hdaa1: 18 40000000 0  0  Line-out      None  Unknown 0x00 Unknown 0 DISA hdaa1:     Caps: IN hdaa1: 20 01014010 1  0  Line-out      Jack  1/8     Rear Green   0 hdaa1:     Caps: IN OUT HP EAPD      Sense: 0x80000000 (connected) hdaa1: 21 90170120 2  0  Speaker       Fixed Analog  Internal Unknown 1 hdaa1:     Caps: IN OUT              Sense: 0x00000000 (disconnected) hdaa1: 22 411111f0 15 0  Speaker       None  1/8     Rear Black   1 DISA hdaa1:     Caps: IN OUT              Sense: 0x00000000 (disconnected) hdaa1: 24 01a19030 3  0  Mic           Jack  1/8     Rear Pink    0 hdaa1:     Caps: IN OUT         VREF Sense: 0x80000000 (connected) hdaa1: 25 02a19040 4  0  Mic           Jack  1/8     Front Pink    0 hdaa1:     Caps: IN OUT HP      VREF Sense: 0x00000000 (disconnected) hdaa1: 26 0181303f 3  15 Line-in       Jack  1/8     Rear Blue    0 hdaa1:     Caps: IN OUT         VREF Sense: 0x00000000 (disconnected) hdaa1: 27 0221401f 1  15 Headphones    Jack  1/8     Front Green   0 hdaa1:     Caps: IN OUT HP EAPD VREF Sense: 0x00000000 (disconnected) hdaa1: 28 411111f0 15 0  Speaker       None  1/8     Rear Black   1 DISA hdaa1:     Caps: IN hdaa1: 30 411111f0 15 0  Speaker       None  1/8     Rear Black   1 DISA hdaa1:     Caps:    OUT hdaa1: NumGPIO=2 NumGPO=0 NumGPI=0 GPIWake=0 GPIUnsol=1 hdaa1:  GPIO0: disabled hdaa1:  GPIO1: disabled From owner-freebsd-questions@freebsd.org Sun Jan 7 17:40:08 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 84C24E77896 for ; Sun, 7 Jan 2018 17:40:08 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mail.inka.de (quechua.inka.de [IPv6:2a04:c9c7:0:1073:217:a4ff:fe3b:e77c]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 500DC6F8A0 for ; Sun, 7 Jan 2018 17:40:08 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mips.inka.de (news@[127.0.0.1]) by mail.inka.de with uucp (rmailwrap 0.5) id 1eYEvW-0007LJ-Cn; Sun, 07 Jan 2018 18:40:06 +0100 Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.15.2/8.15.2) with ESMTP id w07HcHIQ087439 for ; Sun, 7 Jan 2018 18:38:17 +0100 (CET) (envelope-from news@lorvorc.mips.inka.de) Received: (from news@localhost) by lorvorc.mips.inka.de (8.15.2/8.15.2/Submit) id w07HcHtJ087438 for freebsd-questions@freebsd.org; Sun, 7 Jan 2018 18:38:17 +0100 (CET) (envelope-from news) To: freebsd-questions@freebsd.org From: Christian Weisgerber Newsgroups: list.freebsd.questions Subject: Re: Poor default fonts in Firefox Date: Sun, 7 Jan 2018 17:38:17 -0000 (UTC) Message-ID: References: <20171227194053.GA2237@c720-r314251> <20171228203457.GA3562@c720-r314251> User-Agent: slrn/1.0.3 (FreeBSD) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2018 17:40:08 -0000 On 2018-01-07, Christian Weisgerber wrote: >>> > I have a normal ports installation and the above page renders fine. >>> > Can you please post somewhere a screen of your FF. >>> >>> http://shell.uugrn.org/~naddy/bbcnews.xwd.xz >> >> Mine is here: http://www.unixarea.de/my.xwd.gz >> >> I'm not an expert of fonts and rendering ... comments? > > Well, that is some vector font and definitely not the bitmap font > that you get by default. PS: Firefox tells you what font it uses: select a piece of text, right-click, select "Inspect Element", in the bottom right select "Fonts". - Christian "naddy" Weisgerber naddy@mips.inka.de From owner-freebsd-questions@freebsd.org Sun Jan 7 17:40:43 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B5821E77A70 for ; Sun, 7 Jan 2018 17:40:43 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 21B7D6F99F for ; Sun, 7 Jan 2018 17:40:42 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.18.98]) by mrelayeu.kundenserver.de (mreue005 [212.227.15.167]) with ESMTPA (Nemesis) id 0MhPmw-1eBbTX3pRK-00Me4m; Sun, 07 Jan 2018 18:40:34 +0100 Date: Sun, 7 Jan 2018 18:40:33 +0100 From: Polytropon To: Christian Weisgerber Cc: freebsd-questions@freebsd.org Subject: Re: Poor default fonts in Firefox Message-Id: <20180107184033.04b66209.freebsd@edvax.de> In-Reply-To: <20180107155832.GA84935@lorvorc.mips.inka.de> References: <20171227174525.cc1e9047.freebsd@edvax.de> <20180107155832.GA84935@lorvorc.mips.inka.de> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:R7os/X8dqfnQEASW0r5UBE9Ekz0S6kow4tUX39xjxQJAo1W49ar Zrwf1+2OsE4PlM1JEQkHo7dlqjltTZJY3p6V2d9ESMsS6SKZAOv8zHM2OnkIkGXBadMK0kf ThlxhuXNfHnwKfAD7090GeV12LPRlLM1zw4BY6sp0Mx43ugwpkE5VqzAtVbHYvh/bMMOSNk 0jhYuKj+1fuu5PHG5x1ow== X-UI-Out-Filterresults: notjunk:1;V01:K0:WtxtM9ILxpk=:KhPgp4sF3YprOS6DP+YJOI BibXePvZqcDR1LPRujszxFYJae2oaGs6ZYPL6KjCTMvTIcqppDEi14FjTKSo2bPYzKfoYr+g0 SMumal6m28Lx1eegvk4lCwP0sMHD1UsncEqwkREQAqYpxD/WY9bwpdaigXxLiIj+GNUj1pmB8 OO+Sg9LAtlN7E4/FkG3OoruNhQF9IDQ9oijXWGoDc7psBDGNoIln8dOWZQ24eIKmNNrRUWgk9 I1tXMHfEQWKzto5hTx9z37yR2MpyY2N+M/iENDSc+1vwhPFwLn9wYjGv5mFw+SPzDxoRfCh40 HUNNgf7OukyGDW+IFbfmkC1ar6X3FScVbHixL0+9tAdOiE7R/L9v42D83Zg93RvU4YiKmG3uP 6dy9yCtgURR8es88qNlL5TWCitqkyyLH67y8BwLe6WlAJ3UtdHGS7wl31HJcQIr170VC38OJ8 0OYrOg77ZnhzAAKUfOSAg4cHCFy3iNQfPIc9UtbpLpudyxyGGo1m7re9k+uaJL/nd49yUqbdR 064+HMUrna9Y0ucAzuIih+yCliCR0/MfXOovwKG99SHfPBvL2nb16A91B/6o3TkktSkUrqmGD 6mfgHgLVnKYTj2htOknYtiPzV0pbaHsfDbs+9bBKUDZ1Mv9iDngY1rXSqvpDfIXvowAyHHl1P njGZAbdQpW0Ghqa+Pa96ALMu/bdLVmQ8TuSTCnCbsPBfjnQVfvEdw9OcdAhScz08fGLTTH1PE yGhVujZ1636gtjxM6LkPvWeMES9H72SQmLGTCpSYcJkoM9KuYBLGg9Dy5b4= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2018 17:40:43 -0000 On Sun, 7 Jan 2018 16:58:32 +0100, Christian Weisgerber wrote: > Polytropon: > > > > You install a new FreeBSD machine with a graphics display, install > > > the xorg and firefox ports on it, all default options, start browsing > > > the web... and you see that some sites (e.g. http://www.bbc.com/news) > > > are presented with pixelated fonts like something out of the 1990s. > > > > > > What do you do? > > > > You install the recommended font packages. :-) > > Well, there is no such recommendation. It is an "implicit recommendation" which is used so frequently that nobody mentions itanymore . "If you want usable fonts, then go ahead and install them!" ;-) > > > My personal solution for the last few years has been to pinch > > > OpenBSD's etc/fonts/conf.avail/31-nonmst.conf file... > > > > This isn't needed as soon as the webfonts package has > > been installed. And even the DejaVu fonts need to be > > installed manually, if I remember correctly. > > No, Deja Vu is a standard dependency: > x11/xorg > -> x11-fonts/xorg-fonts > -> x11-fonts/x11-fonts/xorg-fonts-truetype > -> x11-fonts/dejavu Good to know. I don't know the exact dependency trees for the different fonts and how they might have changed over time, so maybe my assumption is no longer true. > Installing webfonts does NOT fix the problem. fc-match shows that > popular font names like "Helvetica" and "Times" are still mapped > to the same bitmap fonts as before and that's what you still get > in Firefox. Maybe there is a different problem: Maybe the page in question supplies its own font, and this font just gets rendered in a really terrible manner by the browser's font rendering engine? There could also be a setting within the browser that handles fonts (and prevents the correct usage of a font that is already present on the system). I don't have much experience in "pixel-perfect web publishing as if it was a printed material", because I usually work with printed material. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Sun Jan 7 21:10:02 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41E2EE5D8D6 for ; Sun, 7 Jan 2018 21:10:02 +0000 (UTC) (envelope-from zarniwhoop@ntlworld.com) Received: from know-smtprelay-omc-10.server.virginmedia.net (know-smtprelay-omc-10.server.virginmedia.net [80.0.253.74]) (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 D3FD679014 for ; Sun, 7 Jan 2018 21:10:01 +0000 (UTC) (envelope-from zarniwhoop@ntlworld.com) Received: from localhost.localdomain ([81.97.232.230]) by cmsmtp with ESMTP id YIA6ezOxcKa2WYIA6eCqJ8; Sun, 07 Jan 2018 21:07:22 +0000 X-Originating-IP: [81.97.232.230] X-Authenticated-User: X-Spam: 0 X-Authority: v=2.3 cv=Y7/WTCWN c=1 sm=1 tr=0 a=obylDaYnIsVqxbenyIBF4Q==:117 a=obylDaYnIsVqxbenyIBF4Q==:17 a=IkcTkHD0fZMA:10 a=x7bEGLp0ZPQA:10 a=RgaUWeydRksA:10 a=NLZqzBF-AAAA:8 a=kC5XCjNUAAAA:8 a=iVD6R4xZAAAA:8 a=Br9LfDWDAAAA:8 a=vtwhezT6tufY_whfV0kA:9 a=Y6mZN1FRT3r7mzVK:21 a=5-gGDftlcIETb4lW:21 a=QEXdDO2ut3YA:10 a=_tHamj0Rg94A:10 a=wW_WBVUImv98JQXhvVPZ:22 a=89ZGvdw6miHIuIUErJpX:22 a=ChcFUjjp0OHU96SPM-94:22 a=gR_RJRYUad_6_ruzA8cR:22 Received: by localhost.localdomain (Postfix, from userid 1000) id 0DDE141BDA; Sun, 7 Jan 2018 21:07:22 +0000 (GMT) Date: Sun, 7 Jan 2018 21:07:22 +0000 From: Ken Moffat To: freebsd-questions@freebsd.org Subject: Re: Poor default fonts in Firefox Message-ID: <20180107210722.GA27609@milliways.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline X-Clacks-Overhead: GNU Terry Pratchett Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.9.2 (2017-12-15) X-CMAE-Envelope: MS4wfOjqUw4NZTdyueXkBlMe22EBxz2h3MAPuqw7YbWU0YccLnhS8NeIjVVPhD9B6IYsnQihuksmc/KltJBKkAWGYQEfghAJPgQDUSD6L8MIgRTBJiKvDaOG DFmbDVMJqeefVhQiiVkrKnL0Z76SpE1C5rFSX2zI4QhSSW2G7PbjhLQ/Bw6Foh+vYOTluHkHwSjbB2p5Psav4MzNwgRuUekVKRA= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2018 21:10:02 -0000 I thought this was a private mail, but Christian's other replies copied the list, and I don't think there is anything private in his part, so I'm now forwarding my reply to the list. ----- Forwarded message from Ken Moffat ----- Date: Sun, 7 Jan 2018 19:54:51 +0000 From: Ken Moffat To: Christian Weisgerber Subject: Re: Poor default fonts in Firefox User-Agent: Mutt/1.9.2 (2017-12-15) On Sun, Jan 07, 2018 at 05:30:06PM +0100, Christian Weisgerber wrote: > Ken Moffat: > > > > http://shell.uugrn.org/~naddy/bbcnews.xwd.xz > > > > If you download the current page you will see that it includes > > https://nav.files.bbci.co.uk/orbit/1.0.0-571.15b54a4/css/orb-ltr.min.css > > which uses some BBCReith fonts (Sans and Serif) and these are woff2 > > fonts, so for everything using those fonts you will get the official > > fonts if you allow the page to use them (ISTR somebody mentioned > > overriding that). > > > > If you don't let firefox use them, then I assume you will get whatever > > you have set as the fonts in firefox's preferences. If those are > > merely Sans and Serif then fc-match will tell you what it is using. > > FWIW, Firefox happily tells you what font it uses: select a piece > of text, right-click, select "Inspect Element", in the bottom right > select "Fonts". > Thanks, I didn't know that. > For the BBC web site headlines and article text that comes out as > > Helvetica system > Used as: "Helvetica" > > here. (The Firefox font configuration is the Firefox default.) > Yes, the woff information in the stylesheet turned out to be a red herring for the BBC. On my current machine I prefer TexGyreHeros and clicking on some text at the BBC News page showed it was using the Bold variant (it isn't, the link/headline above that was in bold, and even selecting only the article text I had had an option to open in a new tab!). Going to a different BBC news article and again selecting only some text from the middle of the article, that is apparently in GEL Icons Full Regular - labelled as remote with a link and (woff) after it. Clearly that applies to something else on the page, perhaps the *book and tw?tter icons. Looking at https://wiki.archlinux.org/index.php/Chrony which I happened to have open, the example output in the blue or grey boxes is clearly monospace, but the normal text on a white background is clearly variable width. But when I select some of that normal text it tells me it is I get various reports of Liberation Sans, ... bold, ... mono depending on which short piece of text I inspect. Certainly it is Liberation Sans, because that is how I set my preferences on this machine. This is in ff58.0beta14, and I would be inclined to treat what the inspector tells me with the proverbial grain of salt. ĸen -- Truth, in front of her huge walk-in wardrobe, selected black leather boots with stiletto heels for such a barefaced truth. - Unseen Academicals ----- End forwarded message ----- -- Truth, in front of her huge walk-in wardrobe, selected black leather boots with stiletto heels for such a barefaced truth. - Unseen Academicals From owner-freebsd-questions@freebsd.org Mon Jan 8 02:05:54 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AAFD3E6E99D for ; Mon, 8 Jan 2018 02:05:54 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.231]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7A56B838EA for ; Mon, 8 Jan 2018 02:05:53 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from raspberrypi.bildanet.com ([65.186.67.174]) by cmsmtp with ESMTP id YMovedrGPq4O5YMoxeoKgR; Mon, 08 Jan 2018 02:05:52 +0000 Received: from [192.168.1.143] by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1eYMou-0000jq-TJ for freebsd-questions@freebsd.org; Mon, 08 Jan 2018 02:05:48 +0000 To: FreeBSD Mailing List From: Baho Utot Subject: =?UTF-8?Q?Meltdown_=e2=80=93_Spectre?= Message-ID: Date: Sun, 7 Jan 2018 21:05:40 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfGLC4hE1tMHUB38UV64c9VpWGjxlWYqNfrFFMA46QidlqAj8tdC8g3owELw9go4MMfMj9BXBkXClscFx5O0GNcRiz4Rgqe/ygNkVygw7+fAOJKLmq2aR OjUyZnoEYWMXwQtK0eqJzyjbv9Xww4QeAsk+P6eN3sbTlCZeMpkzeAyPPf242gdtj6bWn9MG7BGe6FJ6LpnW+nueGgyf0s9UoBc= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 02:05:54 -0000 What is freeBSD doing for these attacks? From owner-freebsd-questions@freebsd.org Mon Jan 8 02:11:48 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EC6F8E6F0C6 for ; Mon, 8 Jan 2018 02:11:48 +0000 (UTC) (envelope-from efraindector@motumweb.com) Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AFA4083DA3 for ; Mon, 8 Jan 2018 02:11:48 +0000 (UTC) (envelope-from efraindector@motumweb.com) Received: by mail-io0-x233.google.com with SMTP id e20so11359036iof.12 for ; Sun, 07 Jan 2018 18:11:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=motumweb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DFozCdd65y9G0+9+/8Rdc6e6Eo1RCiVFwGNIrxDHfQc=; b=dqP44oakfkY5GthvfPP3AGrfxK6K2zZVuKnYMN545+sUp6uVUWCf66z5CNuU1Okt3g AbplJPT8rttxLctTZ0mMVoWoMDCqVmmqPcJR9K6aKg8zzeLN1S7imfkwgfAisnWhP2Tx KtlSVhj1X5Tb36qL6TbFxizmLb58CNIf3RUO9oqgXIkCTPfFIBgwqGVjAiEnWSoeLoSk fKIfVlrNgxFbDLHgJNJgRZbN8jLem/Kz7m/u7x2VEf6w+XFb3NV/xgCXZpbSWSQVe+Tf cudytQzvCvRzWTyAQZHuv440nmH3xoi6cFGWicdYebL9eUNyCtFFUhcK+PPFvPlcguRZ 05yQ== 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=DFozCdd65y9G0+9+/8Rdc6e6Eo1RCiVFwGNIrxDHfQc=; b=mcMVCrzqGGxHKdK1XeAaaiXZxj+KWpJFnClscasX8ra5x62kqJ/oU7qpm5JELLTKcz jTL6GLA2qc8/eRH1iMdCpn+qjGgyDWexDqPtw4yg9S2ctg2DuA4YLeEFHqSI1uVrIFgF tdcc0q/W1iBPNIb9C2heGOKQnKe8IbOX1Gx9jV0SUAXQzMr6pGs+2tb5pIt3YV2+5tzw dJY0WrqTDHs9ETyX5mZFZHfF6UXt2H5PkYzDUQPmHVhamy5uWx2qwdpPq5YHCxrUPZAS RfTZPCiDm1h97lWI9zTAn79JQJ3adj5SI1cgGc4FAX92u/avWRJ7M3W+J4e4eXoFA5Fo 4syg== X-Gm-Message-State: AKGB3mJi8+MERcso+dFQlmDZVjC+Mz9j+DJTRyBr3nNYAXJjA0BLHg65 7U1Bx1sLOW24C8zOFnNiOJ8C8dFTiNhZtBZMgYC/ X-Google-Smtp-Source: ACJfBouVUbDe+uv0xV2sd2xnE0ejR9okBdusI5r/yoIOFvJOng8QkVvBeEzGlBawNTGcp9Jy3Ui65yHbYDc5SnV1fBw= X-Received: by 10.107.20.197 with SMTP id 188mr9488959iou.127.1515377507037; Sun, 07 Jan 2018 18:11:47 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.134.130 with HTTP; Sun, 7 Jan 2018 18:11:46 -0800 (PST) X-Originating-IP: [177.232.82.142] Received: by 10.107.134.130 with HTTP; Sun, 7 Jan 2018 18:11:46 -0800 (PST) In-Reply-To: References: From: Efrain Dector Date: Sun, 7 Jan 2018 20:11:46 -0600 Message-ID: Subject: =?UTF-8?B?UmU6IE1lbHRkb3duIOKAkyBTcGVjdHJl?= To: Baho Utot Cc: FreeBSD Questions Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 02:11:49 -0000 Hi. Read about it here: https://www.freebsd.org/news/newsflash.html#event20180104:01 Cheers El 7 ene. 2018 8:06 p. m., "Baho Utot" escribi= =C3=B3: > What is freeBSD doing for these attacks? > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe > @freebsd.org" > From owner-freebsd-questions@freebsd.org Mon Jan 8 02:15:06 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7BDCCE6F39E for ; Mon, 8 Jan 2018 02:15:06 +0000 (UTC) (envelope-from lists@nerdbynature.de) Received: from trent.utfs.org (trent.utfs.org [IPv6:2a03:3680:0:3::67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47FE683F77 for ; Mon, 8 Jan 2018 02:15:06 +0000 (UTC) (envelope-from lists@nerdbynature.de) Received: from localhost (localhost [IPv6:::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by trent.utfs.org (Postfix) with ESMTPS id 2E6C3600BB; Mon, 8 Jan 2018 03:15:03 +0100 (CET) Date: Sun, 7 Jan 2018 18:15:03 -0800 (PST) From: Christian Kujau To: Baho Utot cc: FreeBSD Mailing List Subject: =?UTF-8?Q?Re=3A_Meltdown_=E2=80=93_Spectre?= In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21.9 (DEB 223 2017-09-30) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 02:15:06 -0000 On Sun, 7 Jan 2018, Baho Utot wrote: > What is freeBSD doing for these attacks? Please see the news section before posting: https://www.freebsd.org/news/newsflash.html#event20180104:01 C. -- BOFH excuse #99: SIMM crosstalk. From owner-freebsd-questions@freebsd.org Mon Jan 8 02:18:31 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B2641E6F611 for ; Mon, 8 Jan 2018 02:18:31 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7971A103 for ; Mon, 8 Jan 2018 02:18:30 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from raspberrypi.bildanet.com ([65.186.67.174]) by cmsmtp with ESMTP id YN18ee5IUq4O5YN1BeoPm5; Mon, 08 Jan 2018 02:18:29 +0000 Received: from [192.168.1.143] by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1eYN18-0000kP-L5 for freebsd-questions@freebsd.org; Mon, 08 Jan 2018 02:18:26 +0000 Subject: =?UTF-8?Q?Re:_Meltdown_=e2=80=93_Spectre?= To: FreeBSD Questions References: From: Baho Utot Message-ID: Date: Sun, 7 Jan 2018 21:18:18 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfNcdSO18u7b+ymx9BAE077Lvv0HMz9iUYlKODDidfHfD9lVWLN9BeSTXpGptQl2aNGnymsR9bHuZu4yREE3Fl7SEstn9xXCeUhde8Jfe7ZPGbE8yd4jo l5ZHB518qLZg5t8TExPHLdjvPUcvRivIv2qipFWhXUoYYH78YQrJJVzYlQ68r5Q3flVM2YdhEItdc914rnSCflVCzLzHdhqftzw= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 02:18:31 -0000 On 1/7/2018 9:11 PM, Efrain Dector wrote: > Hi. > > Read about it here: > https://www.freebsd.org/news/newsflash.html#event20180104:01 > > Cheers > > El 7 ene. 2018 8:06 p. m., "Baho Utot" > escribió: > > What is freeBSD doing for these attacks? > _______________________________________________ Ok thanks, It looks like the linux folks is more on top of this as they already have code released for the 4.4 4.9 with the 4.15 kernels being at release candidate. From owner-freebsd-questions@freebsd.org Mon Jan 8 07:30:09 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2C028E7D3BE for ; Mon, 8 Jan 2018 07:30:09 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from relay2.tomsk.ru (mail.sibptus.tomsk.ru [212.73.124.5]) by mx1.freebsd.org (Postfix) with ESMTP id 99BBD6DD01 for ; Mon, 8 Jan 2018 07:30:07 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) X-Virus-Scanned: by clamd daemon 0.98.5_1 for FreeBSD at relay2.tomsk.ru Received: from [212.73.125.240] (HELO admin.sibptus.transneft.ru) by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.16) with ESMTPS id 39907972; Mon, 08 Jan 2018 13:25:18 +0600 Received: from admin.sibptus.transneft.ru (sudakov@localhost [127.0.0.1]) by admin.sibptus.transneft.ru (8.15.2/8.15.2) with ESMTP id w087U4ss052728; Mon, 8 Jan 2018 14:30:04 +0700 (+07) (envelope-from vas@mpeks.tomsk.su) Received: (from sudakov@localhost) by admin.sibptus.transneft.ru (8.15.2/8.15.2/Submit) id w087TxId052698; Mon, 8 Jan 2018 14:29:59 +0700 (+07) (envelope-from vas@mpeks.tomsk.su) X-Authentication-Warning: admin.sibptus.transneft.ru: sudakov set sender to vas@mpeks.tomsk.su using -f Date: Mon, 8 Jan 2018 14:29:59 +0700 From: Victor Sudakov To: Polytropon Cc: FreeBSD Mailing List , Ultima Subject: Re: Convert .flac and .ape to mp3 Message-ID: <20180108072958.GA52639@admin.sibptus.transneft.ru> References: <20180104163421.GA15692@admin.sibptus.transneft.ru> <20180104175156.440fa0c2.freebsd@edvax.de> <20180106063934.GA32231@admin.sibptus.transneft.ru> <20180106085528.GA33117@admin.sibptus.transneft.ru> <20180106150753.GA35605@admin.sibptus.transneft.ru> <20180106170352.ce49b320.freebsd@edvax.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180106170352.ce49b320.freebsd@edvax.de> Organization: AO "Svyaztransneft", SibPTUS X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 07:30:09 -0000 Polytropon wrote: > On Sat, 6 Jan 2018 22:07:53 +0700, Victor Sudakov wrote: > > Ultima wrote: > > > Actually, that wont work either. I decided to go look at some of my scripts > > > where I had to do something similar, the solution was setting IFS. > > > > > > IFS=$'\n' > > > > What's the dollar sign here for? Why not IFS='\n'? > > It can be seen as "evaluation symbol" (as known from $FOO > being "FOO evaluated"), or "value of" ($FOO = the value > of FOO). > > Another way (convenient, but doesn't look good" is to do > something like this: > > IFS=" > " > > This is a newline as well. In the case above, you want to > set IFS to an _actual_ newline, not to \n. Remember _when_ > the shell evaluates something: Variables like $IFS will > be evaluated when being accessed, not when they are being > declared (even with an initial value). The $'\n' makes > sure that IFS will be assigned an actual (non-escaped) > newline, so when constructs like for() or while read > access $IFS, they find a "real" newline there. The world is full of wonders. Indeed, from sh, echo $'\n' produces a real newline, while echo '\n' produces just a literal "\n". Thank you. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN AS43859 From owner-freebsd-questions@freebsd.org Mon Jan 8 07:39:09 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0CC5BE7DADF for ; Mon, 8 Jan 2018 07:39:09 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from relay2.tomsk.ru (mail.sibptus.tomsk.ru [212.73.124.5]) by mx1.freebsd.org (Postfix) with ESMTP id 73F816E2C8 for ; Mon, 8 Jan 2018 07:39:07 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) X-Virus-Scanned: by clamd daemon 0.98.5_1 for FreeBSD at relay2.tomsk.ru Received: from [212.73.125.240] (HELO admin.sibptus.transneft.ru) by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.16) with ESMTPS id 39907976; Mon, 08 Jan 2018 13:34:18 +0600 Received: from admin.sibptus.transneft.ru (sudakov@localhost [127.0.0.1]) by admin.sibptus.transneft.ru (8.15.2/8.15.2) with ESMTP id w087d4A0052780; Mon, 8 Jan 2018 14:39:06 +0700 (+07) (envelope-from vas@mpeks.tomsk.su) Received: (from sudakov@localhost) by admin.sibptus.transneft.ru (8.15.2/8.15.2/Submit) id w087d0tM052779; Mon, 8 Jan 2018 14:39:00 +0700 (+07) (envelope-from vas@mpeks.tomsk.su) X-Authentication-Warning: admin.sibptus.transneft.ru: sudakov set sender to vas@mpeks.tomsk.su using -f Date: Mon, 8 Jan 2018 14:39:00 +0700 From: Victor Sudakov To: Ultima Cc: Andreas Perstinger , FreeBSD Mailing List Subject: Re: Convert .flac and .ape to mp3 Message-ID: <20180108073900.GB52639@admin.sibptus.transneft.ru> References: <20180104163421.GA15692@admin.sibptus.transneft.ru> <20180104175156.440fa0c2.freebsd@edvax.de> <20180106063934.GA32231@admin.sibptus.transneft.ru> <20180106151754.GA35747@admin.sibptus.transneft.ru> <06f10c10-8e39-ec9b-de84-0c345c8be229@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: AO "Svyaztransneft", SibPTUS X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 07:39:09 -0000 Ultima wrote: > Thanks for the link Andreas, it is a good read. > > Was very tired when I made the reply yesterday so > apologies for not double checking and explaining my > minimal responses. > > I want to also mention if you want to build a more > reliable script, you should also check if the file is > actually the media format suggested by the extension. > > My solution to this problem is first checking if an error > occurs when ffprobe runs the file with -loglevel -8 options. > This will verify that ffmpeg can actually read the file. Next > run it a second time to verify the media format. > > ffprobe is very fast so you don't have to worry about taking > a performance hit. Thanks for you hints Ultima. Returning to the initial question, I still have not found a way to split a large flac/ape file into mp3 tracks, and writing relevant id3 tags into resulting tracks, in accordance with the information in the cue file. I'm still trying to brew a stew from sysutils/bchunk, multimedia/ffmpeg, audio/flac, audio/id3tool, audio/lame, audio/mac, audio/mp3splt, audio/shntool with rather little success. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN AS43859 From owner-freebsd-questions@freebsd.org Mon Jan 8 07:42:19 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 214A6E7DE4F for ; Mon, 8 Jan 2018 07:42:19 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from relay2.tomsk.ru (mail.sibptus.tomsk.ru [212.73.124.5]) by mx1.freebsd.org (Postfix) with ESMTP id 8B6D16E672 for ; Mon, 8 Jan 2018 07:42:17 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) X-Virus-Scanned: by clamd daemon 0.98.5_1 for FreeBSD at relay2.tomsk.ru Received: from [212.73.125.240] (HELO admin.sibptus.transneft.ru) by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.16) with ESMTPS id 39907979; Mon, 08 Jan 2018 13:37:28 +0600 Received: from admin.sibptus.transneft.ru (sudakov@localhost [127.0.0.1]) by admin.sibptus.transneft.ru (8.15.2/8.15.2) with ESMTP id w087gGef052814; Mon, 8 Jan 2018 14:42:16 +0700 (+07) (envelope-from vas@mpeks.tomsk.su) Received: (from sudakov@localhost) by admin.sibptus.transneft.ru (8.15.2/8.15.2/Submit) id w087gEuN052813; Mon, 8 Jan 2018 14:42:14 +0700 (+07) (envelope-from vas@mpeks.tomsk.su) X-Authentication-Warning: admin.sibptus.transneft.ru: sudakov set sender to vas@mpeks.tomsk.su using -f Date: Mon, 8 Jan 2018 14:42:14 +0700 From: Victor Sudakov To: Polytropon Cc: freebsd-questions@freebsd.org Subject: Re: Convert .flac and .ape to mp3 Message-ID: <20180108074214.GC52639@admin.sibptus.transneft.ru> References: <20180104163421.GA15692@admin.sibptus.transneft.ru> <20180104175156.440fa0c2.freebsd@edvax.de> <20180106063934.GA32231@admin.sibptus.transneft.ru> <20180106165220.b722e6f0.freebsd@edvax.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180106165220.b722e6f0.freebsd@edvax.de> Organization: AO "Svyaztransneft", SibPTUS X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 07:42:19 -0000 Polytropon wrote: > On Sat, 6 Jan 2018 13:39:34 +0700, Victor Sudakov wrote: > > Polytropon wrote: > > > > What do you convert ape and flac audio files to mp3 with? > > > > > > > > multimedia/ffmpeg does not seem to support encoding to mp3 (only > > > > decoding), what else could I try? > > > > > > Huh? I'm using ffmpeg regularly to convert from mp4 or flv _to_ mp3, > > > this works quite well. Maybe you need to install an additional encoder, > > > plugin, or library if you're lacking mp3 support? > > > > > > % ffmpeg -i example.flv example.mp3 > > > > > > It does what it says on the can. Works for years. :-) > > > > > > With ffmpeg's mp3 support, you should be able to convert from flac > > > or ape in a similar manner. > > > > I'm somewhat disappointed because ffmpeg does not seem to be able to > > split flac/ape files according to cue file, or extract track names > > therefrom and insert them into the mp3 file. > > I wish there would be some "magical MP3 split" that acts upon > a specified silence (for example, 3 seconds) Theoretically you should not need to use magic when you have .cue files at hand. > and splits the > file into "tracks" that could then be renamed... and id3 tags written into them... > > There are two articles which I occassionally refer to, > indead of saying "don't use spaces". :-) > > David A. Wheeler: > Filenames and Pathnames in Shell: How to do it correctly > http://www.dwheeler.com/essays/filenames-in-shell.html > > David A. Wheeler: > Fixing Unix/Linux/POSIX Filenames: > Control Characters (such as Newline), Leading Dashes, and Other Problems > http://www.dwheeler.com/essays/fixing-unix-linux-filenames.html > > Those articles will provide you with the most robust > solution - and: no, just adding "quotes" isn't sufficient > in most cases. :-) Thanks, I'll read those. > > Also note: If you're starting to extract information from > an ID3 tag and want to turn that into a directory and filename > structure, you might find other characters than just spaces > that "misbehave" in shell context. At present I have an opposite task. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN AS43859 From owner-freebsd-questions@freebsd.org Mon Jan 8 07:43:13 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8AA06E7DFA7 for ; Mon, 8 Jan 2018 07:43:13 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from relay2.tomsk.ru (mail.sibptus.tomsk.ru [212.73.124.5]) by mx1.freebsd.org (Postfix) with ESMTP id 044566E791 for ; Mon, 8 Jan 2018 07:43:12 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) X-Virus-Scanned: by clamd daemon 0.98.5_1 for FreeBSD at relay2.tomsk.ru Received: from [212.73.125.240] (HELO admin.sibptus.transneft.ru) by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.16) with ESMTPS id 39907981; Mon, 08 Jan 2018 13:38:23 +0600 Received: from admin.sibptus.transneft.ru (sudakov@localhost [127.0.0.1]) by admin.sibptus.transneft.ru (8.15.2/8.15.2) with ESMTP id w087hB1M052827; Mon, 8 Jan 2018 14:43:11 +0700 (+07) (envelope-from vas@mpeks.tomsk.su) Received: (from sudakov@localhost) by admin.sibptus.transneft.ru (8.15.2/8.15.2/Submit) id w087h9vd052826; Mon, 8 Jan 2018 14:43:09 +0700 (+07) (envelope-from vas@mpeks.tomsk.su) X-Authentication-Warning: admin.sibptus.transneft.ru: sudakov set sender to vas@mpeks.tomsk.su using -f Date: Mon, 8 Jan 2018 14:43:09 +0700 From: Victor Sudakov To: Dave Cc: freebsd-questions@freebsd.org Subject: Re: Convert .flac and .ape to mp3 Message-ID: <20180108074309.GD52639@admin.sibptus.transneft.ru> References: <20180104163421.GA15692@admin.sibptus.transneft.ru> <1936112.H3c9qehT4n@amd.asgard.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1936112.H3c9qehT4n@amd.asgard.uk> Organization: AO "Svyaztransneft", SibPTUS X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 07:43:13 -0000 Dave wrote: > On Thursday 04 January 2018 23:34:21 Victor Sudakov wrote: > > Dear Colleagues, > > > > What do you convert ape and flac audio files to mp3 with? > > > > multimedia/ffmpeg does not seem to support encoding to mp3 (only > > decoding), what else could I try? > > I prefer audio/sox but, like FFMPeG, you need to compile in mp3 encoding > support from port. Sox is the audio equivalent of FFMPeG, ie very, very > powerful in it's own are of expertise which can be as simple or as complex > to use as you want it to be, eg sox file.flac file.mp3 Can sox read .cue files and split flacs according to cues? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN AS43859 From owner-freebsd-questions@freebsd.org Mon Jan 8 07:47:09 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BFE84E7E2F6 for ; Mon, 8 Jan 2018 07:47:09 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from relay2.tomsk.ru (mail.sibptus.tomsk.ru [212.73.124.5]) by mx1.freebsd.org (Postfix) with ESMTP id 25B866E9C8 for ; Mon, 8 Jan 2018 07:47:08 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) X-Virus-Scanned: by clamd daemon 0.98.5_1 for FreeBSD at relay2.tomsk.ru Received: from [212.73.125.240] (HELO admin.sibptus.transneft.ru) by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.16) with ESMTPS id 39907987; Mon, 08 Jan 2018 13:42:18 +0600 Received: from admin.sibptus.transneft.ru (sudakov@localhost [127.0.0.1]) by admin.sibptus.transneft.ru (8.15.2/8.15.2) with ESMTP id w087l4NM052873; Mon, 8 Jan 2018 14:47:06 +0700 (+07) (envelope-from vas@mpeks.tomsk.su) Received: (from sudakov@localhost) by admin.sibptus.transneft.ru (8.15.2/8.15.2/Submit) id w087l1Dn052871; Mon, 8 Jan 2018 14:47:01 +0700 (+07) (envelope-from vas@mpeks.tomsk.su) X-Authentication-Warning: admin.sibptus.transneft.ru: sudakov set sender to vas@mpeks.tomsk.su using -f Date: Mon, 8 Jan 2018 14:47:01 +0700 From: Victor Sudakov To: Polytropon Cc: freebsd-questions@freebsd.org Subject: Re: Convert .flac and .ape to mp3 Message-ID: <20180108074701.GE52639@admin.sibptus.transneft.ru> References: <20180104163421.GA15692@admin.sibptus.transneft.ru> <20180104175156.440fa0c2.freebsd@edvax.de> <20180106063934.GA32231@admin.sibptus.transneft.ru> <20180106165220.b722e6f0.freebsd@edvax.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180106165220.b722e6f0.freebsd@edvax.de> Organization: AO "Svyaztransneft", SibPTUS X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 07:47:09 -0000 Polytropon wrote: > > I wish there would be some "magical MP3 split" that acts upon > a specified silence (for example, 3 seconds) and splits the > file into "tracks" that could then be renamed... man mp3splt says it can do silence detection: -s Silence mode, to split with silence detection. When you use -s option, mp3splt attempts to detect silence points in all the file (or just in some parts, see -a and -c below for this). To detect silence we need to decode files, so this option can be really slow if used with big files. It accepts some parameters with -p option (see below for a detailed description): threshold level (th) which is the sound level to be considered silence, number of tracks (nt) which is the desired number of tracks, cutpoint offset (off) which is the offset of cutpoint in silence, minimum_length (min) which is the minimum silence length in seconds, remove silence (rm) which allows you to remove the silence between split tracks. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN AS43859 From owner-freebsd-questions@freebsd.org Mon Jan 8 08:17:34 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 66A98E59F61 for ; Mon, 8 Jan 2018 08:17:34 +0000 (UTC) (envelope-from bounce_49254060+a.11a6977c3bd0b8d2_11699e4bfc2eb8c_v51@zcsend.net) Received: from sendera51.zcsend.net (sendera51.zcsend.net [135.84.81.51]) by mx1.freebsd.org (Postfix) with ESMTP id 44E466FB34 for ; Mon, 8 Jan 2018 08:17:33 +0000 (UTC) (envelope-from bounce_49254060+a.11a6977c3bd0b8d2_11699e4bfc2eb8c_v51@zcsend.net) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=zcp024; d=zcsend.net; h=Date:From:Reply-To:To:Message-ID:Subject:MIME-Version:Content-Type:List-Unsubscribe; bh=fx05tvtsbuLy61IeIXNglUYSyz4=; b=g0TG7almUFuV/n5nYFvSPFqrjRvXXV+FE4RE5nNtvli5erolRb6/5EWVw+Yl2U55sprhwl2un5BA 5Hiz7tbdjxtAAbWl/u60hXuEaO43jLFJLj8LPl3bv8rTryrcy1la/gU4vEGYxMWL91U21Fhc8cKs zAvI7Djia0Op7QvMsf8= Received: from [172.25.237.206] (172.25.237.206) by sendera51.zcsend.net id hackhs28epg3 for ; Mon, 8 Jan 2018 00:07:20 -0800 (envelope-from ) Date: Mon, 8 Jan 2018 00:07:20 -0800 (PST) From: "Safety Consultants & Solutions Provider Limited" Reply-To: info@safetysolutionsng.com To: freebsd-questions@freebsd.org Message-ID: Subject: Forensic Fire Investigation MIME-Version: 1.0 X-JID: 11287eca5d2294.11a6977c3bd013c2 X-campaignid: zohocampaigns.11287eca5d2294.zcb.11a6977c3bd0b8d2.11699e4bfc2eb8c X-Zoho-RID: zohocampaigns.11287eca5d2294.zcb.11a6977c3bd0b8d2.11699e4bfc2eb8c X-Mailer: Zoho Campaigns X-Report-Abuse: , Content-Type: text/plain;charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 08:17:34 -0000 Forensic Fire Investigation=20 This refers to the application of scientific methods & techniques to determ= ine the origin and cause of fire once firefighters have extinguished the fi= re.=20 The practice is similar to the examination of crime scenes in that the scen= e must be preserved and evidence collected and analyzed, but with numerous = additional difficulties and dangers. The investigation will include closely= surveying the damaged scene to establish the origin of the fire and eventu= ally establishing the cause.=20 However in order to effectively examine and evaluate a fire scene, it is im= perative that the investigator has a detailed=C2=A0 knowledge of the chemis= try and behavior of fire and its effects.=20 Understanding The Nature & Chemistry of Fire=20 Fire occurs due to the exothermic reaction of combustion (burning), produci= ng heat and light. In order for a fire to occur, three vital components mus= t be present: a fuel source, an oxidant (O 2 ) and a sufficient amount of e= nergy in the form of heat. Together these make up the fire triangle. A four= th factor can also be described =E2=80=93 a self-sustaining chemical chain = reaction =E2=80=93 to produce the fire tetrahedron. The absence of any of t= hese conditions will result in a fire not starting or extinguishing through= smothering (oxygen removal), cooling (heat removal) or starving (fuel remo= val).=20 Solid and liquid materials do not actually combust, but the process of heat= ing causes them to produce vapors which can burn. This is the process of py= rolysis. Through this pyrolysis products will be formed, flammable and vola= tile substances of low molecular weight caused through the decomposition of= materials by fire.=20 Heat produced by a fire can spread in one of three ways; convection, conduc= tion and radiation. Convection is the transfer of heat through air circulat= ion, and only occurs in liquids and gases. An example of convection is the = heat from a fire rising and heating the ceiling of a room. Conduction is th= e transfer of heat through a medium by direct contact, such as a fire heati= ng a metal beam which transfers the heat elsewhere. Radiation is the emissi= on of heat as infrared radiation without a medium, such as a fire heating a= nd igniting a nearby sofa.=20 Fire Investigation=20 The primary purposes of a fire investigation is to establish the origin (se= at) of the fire, determine the likely cause, and thus conclude whether the = incident was accidental, natural or deliberate. It is vital to establish th= e cause to ensure similar events do not occur (in the case of natural or ac= cidental) or to allow a legal investigation to be conducted (in the case of= deliberate fires).=20 Safety=20 The initial concern with regards to a fire incident scene is safety. Such a= scene has an increased risk factor with possible hazards including heated = materials, structural collapse, damaged electricity and gas mains, debris, = asbestos, dangerous combustion products and other toxic substances. A dynam= ic risk assessment should be conducted, the scene must be declared safe and= all individuals entering the scene should wear appropriate protective clot= hing such as hardhats, fire-resistant overalls, steel-capped boots, thick g= loves and, in some cases, a face mask. Supplies of gas and electricity shou= ld be switched off before the investigation begins.=20 Article by Peace Okorogu SCSP HSE Lead=20 http://safetysolutionsng.com/forensic-fire-investigation READMORE ---------------------------------------------------------------------- This email was sent by info@safetysolutionsng.com to freebsd-questions@free= bsd.org Not interested?Unsubscribe - https://zc1.maillist-manage.com/ua/optout?od= =3D11287eca5d2294&rd=3D11a6977c3bd0b8d2&sd=3D11a6977c3bd0200b&n=3D11699e4bf= c2eb8c Update profile - https://zc1.maillist-manage.com/ua/upc?upd=3D11a6977c3bbf= 0bf9&r=3D11a6977c3bd0b8d2&n=3D11699e4bfc2eb8c&od=3D11287eca5d2294 =20 Impressed?Tell-A-Friend - https://zc1.tell-your-friend.com/ua/forward?od=3D= 11287eca5d2294&rd=3D11a6977c3bd0b8d2&sd=3D11a6977c3bd0200b&n=3D11699e4bfc2e= b8c&s=3Df =20 Safety Consultants & Solutions Provider | 12B, Oguntona Crescent, off Oworo= nshoki Express Way First Pedro Bus Stop, Gbagada, Lagos State, Nigeria.=20 From owner-freebsd-questions@freebsd.org Mon Jan 8 08:25:21 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2417AE5A88D for ; Mon, 8 Jan 2018 08:25:21 +0000 (UTC) (envelope-from srs0=+gpj=ed=sigsegv.be=kristof@codepro.be) Received: from venus.codepro.be (venus.codepro.be [IPv6:2a01:4f8:162:1127::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.codepro.be", Issuer "Gandi Standard SSL CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DDF6B7006B for ; Mon, 8 Jan 2018 08:25:20 +0000 (UTC) (envelope-from srs0=+gpj=ed=sigsegv.be=kristof@codepro.be) Received: from [192.168.228.1] (vega.codepro.be [IPv6:2a01:4f8:162:1127::3]) (Authenticated sender: kp) by venus.codepro.be (Postfix) with ESMTPSA id 3BB98B98B; Mon, 8 Jan 2018 09:25:17 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sigsegv.be; s=mail; t=1515399917; bh=zADQDs2BFyDtpU9RGJpXmqEmbHpeerHMP5Ek6x5RyV0=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=JODfeHZxnqJaJSREUxKbqCc6Qnk9qdPSYHwXfcO0cln28Yj2yrE2AwxEoNM2HaI4E /FFWN/FnHZyLMxcg9dSBK3aeFnmNn4IHyYwY5CMBcfrdXaXOQyPpQjdTO17iJSWf19 PlphR6a+zaSgK2nMiMZAztElKJvbuga1fj0B/RaU= From: "Kristof Provost" To: "Baho Utot" Cc: "FreeBSD Questions" Subject: Re: Meltdown =?utf-8?q?=E2=80=93?= Spectre Date: Mon, 08 Jan 2018 09:22:34 +0100 X-Mailer: MailMate (2.0BETAr6102) Message-ID: <3AECDC7F-8838-4C09-AC7F-117DFBAA326C@sigsegv.be> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 08:25:21 -0000 On 8 Jan 2018, at 3:18, Baho Utot wrote: > On 1/7/2018 9:11 PM, Efrain Dector wrote: >> Hi. >> >> Read about it here: >> https://www.freebsd.org/news/newsflash.html#event20180104:01 >> >> Cheers >> >> El 7 ene. 2018 8:06 p. m., "Baho Utot" > > escribió: >> >> What is freeBSD doing for these attacks? >> _______________________________________________ > > Ok thanks, It looks like the linux folks is more on top of this as > they already have code released for the 4.4 4.9 with the 4.15 kernels > being at release candidate. > They have been aware of the problem for 6+ months. FreeBSD was notified in late December. It’s being worked on, but these are non-trivial changes, so it’ll take some time. Regards, Kristof From owner-freebsd-questions@freebsd.org Mon Jan 8 08:58:07 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2EF30E5C453 for ; Mon, 8 Jan 2018 08:58:07 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (mail.dpedia.de [178.254.4.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E0F6B71317 for ; Mon, 8 Jan 2018 08:58:06 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [2.247.252.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 1eYTFl-0000My-Ie for freebsd-questions@freebsd.org; Mon, 08 Jan 2018 09:57:57 +0100 Received: from localhost.my.domain (localhost [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id w088vurq003096 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 8 Jan 2018 09:57:56 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id w088vuX9003095 for freebsd-questions@freebsd.org; Mon, 8 Jan 2018 09:57:56 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Mon, 8 Jan 2018 09:57:56 +0100 From: Matthias Apitz To: freebsd-questions@freebsd.org Subject: Re: Meltdown =?utf-8?B?4oCT?= Spectre Message-ID: <20180108085756.GA3001@c720-r314251> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , freebsd-questions@freebsd.org References: <3AECDC7F-8838-4C09-AC7F-117DFBAA326C@sigsegv.be> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="W/nzBZO5zC0uMSeA" Content-Disposition: inline In-Reply-To: <3AECDC7F-8838-4C09-AC7F-117DFBAA326C@sigsegv.be> X-Operating-System: FreeBSD 12.0-CURRENT r314251 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. User-Agent: Mutt/1.8.0 (2017-02-23) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 2.247.252.239 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 08:58:07 -0000 --W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable El d=C3=ADa lunes, enero 08, 2018 a las 09:22:34a. m. +0100, Kristof Provos= t escribi=C3=B3: > They have been aware of the problem for 6+ months. FreeBSD was notified= =20 > in late December. It=E2=80=99s being worked on, but these are non-trivial= =20 > changes, so it=E2=80=99ll take some time. As I side note, and not related to FreeBSD: My Internet server is run by some webhosting company (www.1blu.de), they use Ubuntu servers and since yesterday they have shutdown SSH access to the servers argumenting that the= y want protect my (all's) servers against attacks of Meltdown and Spectre. Imagine, next time we have to shutdown all IOT gadgets... 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 --W/nzBZO5zC0uMSeA Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEXmn7rBYYViyzy/vBR8z35Hb+nREFAlpTMpEACgkQR8z35Hb+ nRGRJA/+MznMFXZ35R999GIVoRDTOvfQZTSJq/xWmXj+jYRrIYLzxLVS1DN5SNOK nCEIEVjHxYvuHJZMv+V+drlM6MOlWz9kOWsBiOXJO87+M0aJwh8r5OcmPh0U/rIJ jKyM9fH1TMJ3TDEru+/LbqqvsCgF5g5K4xrqzrZL4voGYdV4HCkS+HBBag0LghvY TkX9OXf/O7E8PzFH027yXdxtweOQPgZp+s5JZo6g225oPStW7Med6D1dJCf5r2Vc TKaPHVyIs37lg0+a77YuPge5D4ijid3mS2hlX3EgcnlgwtKWuWHTygyA9tuK8CLk +Ml2s381gwhwFb6sB2MICqWw8ei35EYPZnfacVi/YF874WeE5VSmn58E0CP73Zao xISDi6gAduPXXDF+CEPwm0SwDfyiqIG0uLk1WJHXULjkX2Zai2rWgakZC15FOkAR DV1WXxTWfzVbvprpSTbTEIbdMZ4k6FJi/mGDVAmJ85CdWbce2KinnppVAMOAiyVy URqm4gjaUcRaFW/TdthBujaVK+uzjSRekBJurKR6UgFLD6nVvm/Ol+Jb8o7nYnAb R2V+M4xSUxyAUL+Sp2jlgiI4Xi49ZFWomikT0VWNpGZLvOePZDzl1pusL5zP/aTR E587Mk1VDuv6Cn/Gj0pSWeH6EZzgz4dPs7CyfQu7KzurwR+tnNI= =xAUG -----END PGP SIGNATURE----- --W/nzBZO5zC0uMSeA-- From owner-freebsd-questions@freebsd.org Mon Jan 8 09:15:47 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4795DE5D752 for ; Mon, 8 Jan 2018 09:15:47 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C19871D72 for ; Mon, 8 Jan 2018 09:15:47 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by mail-io0-x233.google.com with SMTP id w188so12239444iod.10 for ; Mon, 08 Jan 2018 01:15:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=xklVfR+ZJ6aQ7vG8bXlTCPn3daaPau37naA1HmUgbkI=; b=qWygvBUe7gwo0uUUJUJWD045d0yNi9YM1M9PjvhnuvfbVYrZsCdOsFpC19XPy8+rYD iiXC1iI5EOt2JqpP4IFihgU+TSK5tfkpRd3Yp66n+KvpbNzoTSPqaNprlLeTwdK13koJ P8x6hEzD4HY5VMpKiq11BTL4FF7jr43WqI8F9SisNiXnt36GOJm9LMHE8W2MVZawyIJJ +SPqmA74bEly9dFF6AZ38Fy4N8eP9zTb7+IZXVikXmZF1WLJITX/F6sCKtwB7nwJroPu M9wA+15SUeORsgGulKx6C4TIET8A1RTADrRIVRiqueUkkRy7zO/zKxfJ2eaRjdGU4YeS wZIA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=xklVfR+ZJ6aQ7vG8bXlTCPn3daaPau37naA1HmUgbkI=; b=o9eGb/1rQgMqS/O7D5UU3H03Da5RshY+wuaWbJC/WLsf+VjUFoQVP1JWY2Om4xaIfs vSiD96rucS2JKZoJjJAfUTZpiIzPxbF4dnJevx/+rFqMrL/ZJ2o4c3yri1wSgwYFLO4b xzQcjr6UsYZe9LKvekyuaxLULuawj2uhVGWytm10NDeCwwvZ7owErnfVrrlMfyvCgBn1 DrNmGDmoRPDnIkmZU/EI1wvZfdT/pgFrYDmHiR5a41TM9ernLFgC84tJXqPeXvMuSv1L Tq/x+IWtlClhCMpEw1ntWj+Ql8r47VZwqqM/H4aLz0al0WMHkZwH66/S4/VLnBxtFv7F 0xpg== X-Gm-Message-State: AKwxytcCDZSkPuXaXrrUNLuLZVh2k71qluwRY2npKYG0ChRbjrt13l+I qg2aIMQX+fqhl6jxZxVSTdZNuLjJl7Y8ojf6aGU= X-Google-Smtp-Source: ACJfBotK6+9VQyi9+KAVscRdwjMeRF3gIxeVZKnbNce4sY8wQJxs6Npm0yd0g9SU3C/SMI83dwpMYT26+YJZz4/mCC8= X-Received: by 10.107.180.200 with SMTP id d191mr10997411iof.249.1515402946489; Mon, 08 Jan 2018 01:15:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.36.105.3 with HTTP; Mon, 8 Jan 2018 01:15:46 -0800 (PST) In-Reply-To: <20180108085756.GA3001@c720-r314251> References: <3AECDC7F-8838-4C09-AC7F-117DFBAA326C@sigsegv.be> <20180108085756.GA3001@c720-r314251> From: Aryeh Friedman Date: Mon, 8 Jan 2018 04:15:46 -0500 Message-ID: Subject: =?UTF-8?B?UmU6IE1lbHRkb3duIOKAkyBTcGVjdHJl?= To: Matthias Apitz , FreeBSD Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 09:15:47 -0000 On Mon, Jan 8, 2018 at 3:57 AM, Matthias Apitz wrote: > As I side note, and not related to FreeBSD: My Internet server is run by > some webhosting company (www.1blu.de), they use Ubuntu servers and since > yesterday they have shutdown SSH access to the servers argumenting that > they want > protect my (all's) servers against attacks of Meltdown and Spectre. > > Imagine, next time we have to shutdown all IOT gadgets... Not always possible for things like medical test equipment/devices. For example I maintain a specialized EMR for interacting with Dr. prescribed remote cardiac monitors. Having those off line is not an option since they are used to detect if the patient needs something more serious like a pace maker (also almost always a IoT device these days) surgery. The actual monitoring is done on Windows and was attacked by some ransomeware via a bit coin miner that somehow installed it self. Since all the users claim that they don't read email/upload/download executables or any other of the known attack vectors this leaves something like Meltdown or Spectre. We have also detected issues on the CentOS that has the non-medical corporate site on it. The only machine left on touched on the physical server (running some bare metal virtualization tool) is the FreeBSD machine that runs the actual EMR we wrote. TL;DR -- It seems Linux and Windows already have issues with these holes but I have seen little to no evidence that FreeBSD (when run as a host). In general when ever any virtualization issue (like the bleed through on Qemu last year) comes up FreeBSD is the one OS that seems to be immune (thanks to good design of the OS and bhyve). This is the main reason why I chose FreeBSD over Linux as the reference host for PetiteCloud. -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-questions@freebsd.org Mon Jan 8 09:22:16 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 086B8E5DFD1 for ; Mon, 8 Jan 2018 09:22:16 +0000 (UTC) (envelope-from omar.polo@europecom.net) Received: from n1nlsmtp02.shr.prod.ams1.secureserver.net (n1nlsmtp02.prod.ams1.secureserver.net [188.121.43.194]) (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 8F3C9724B1 for ; Mon, 8 Jan 2018 09:22:14 +0000 (UTC) (envelope-from omar.polo@europecom.net) Received: from n3plcpnl0017.prod.ams3.secureserver.net ([160.153.146.67]) by : HOSTING RELAY : with SMTP id YTUseKdakjzE4YTUse4lHi; Mon, 08 Jan 2018 02:13:34 -0700 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=europecom.net; s=default; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=N2SP1oEDUMpv0S6+mDtj6F/OOC5t0KQPDCzvr5pCGZs=; b=SiLrIF5Ib7mi9em2ZYkBXoEvf OO7pJClrhfhBcj+STwIk94Ry5+ZL2xPyLYQ3dlMWWDYyqpNvd2Lni4hrs2nHs8Q9VfOZw7tzsk23Q uY205+eKx/zscQSMKrpIEj1Wdx8URaVJmNc+lH+RryfreMxlTZG2hkLvM2sCKWiDToyi7fuM/UeTo gwSyxp7DrG6vZgvNGYqXV230l7+Qg6FVXM7ZJ4oKY2WEpZvsneAtpyIeAlZPdFx9RgIX0+7jPHGtP BSQEKviVW+Mk0wuBwGfGoDOjrc53ppRHApBY8cs8QTe0mjJ5ppL925/7o+rPPh6r5EguH/OWB4XqL 22YXemK6w==; Received: from 93-41-0-248.ip79.fastwebnet.it ([93.41.0.248]:11232 helo=venera) by n3plcpnl0017.prod.ams3.secureserver.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1eYTUs-0004WF-JB; Mon, 08 Jan 2018 02:13:34 -0700 Date: Mon, 8 Jan 2018 10:13:28 +0100 From: Omar Polo To: freebsd-questions@freebsd.org Cc: Matthias Apitz Subject: Re: client for matrix.org Message-ID: <20180108091328.GA3075@venera> References: <20180104055057.GA2656@c720-r314251> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="sdtB3X0nJg68CQEu" Content-Disposition: inline In-Reply-To: <20180104055057.GA2656@c720-r314251> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - n3plcpnl0017.prod.ams3.secureserver.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - europecom.net X-Get-Message-Sender-Via: n3plcpnl0017.prod.ams3.secureserver.net: authenticated_id: omar.polo@europecom.net X-Authenticated-Sender: n3plcpnl0017.prod.ams3.secureserver.net: omar.polo@europecom.net X-Source: X-Source-Args: X-Source-Dir: X-CMAE-Envelope: MS4wfGaUrtyrFTNiD/LfnT4TA6kVK9RepUYwA4Sq/VudTpAW3NlW2AFTWLDz/1TuvHjHJcYg6NYolv/R2371cQeOT6dHxum1bAehMhaJIbEq+TPy7y8mNadI hcjEIcK0Zk2H1uWDLcimLOeRwJ4UWWGf8f7uNVwEM2sme37w3l3lT7crYU/s0qgyuRhqr7LdGO6rgMjw8NZavs2u5wA2pk0iURFCZTo8RsH27sEWH5LeAWY0 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 09:22:16 -0000 --sdtB3X0nJg68CQEu Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, It seems that elecron is coming to freebsd[1] as well, so maybe soon Riot desktop would be available. However, there is the online version of riot[2] as well as a weechat script[3]. [1]: https://github.com/electron/electron/issues/3797 [2]: https://riot.im/app/ [3]: https://matrix.org/docs/projects/client/weechat.html On Thu, Jan 04, 2018 at 06:50:57AM +0100, Matthias Apitz wrote: >=20 > Hello, >=20 > Anybody knows some client for matrix.org which could run on FreeBSD? > Thanks >=20 > matthias > --=20 > Matthias Apitz, =E2=9C=89 guru@unixarea.de, =E2=8C=82 http://www.unixarea= =2Ede/ =F0=9F=93=B1 +49-176-38902045 > Public GnuPG key: http://www.unixarea.de/key.pub --=20 Omar Polo -- https://omar-polo.github.io/ > No computers were harmed in the making of this email, only free (as in > freedom) software was used My PGP public key: 147F 24EB 977C DFDD 0197 86D3 E483 C355 499D 960D https://omar-polo.github.io/omar-polo.txt --sdtB3X0nJg68CQEu Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEFH8k65d8390Bl4bT5IPDVUmdlg0FAlpTNi8ACgkQ5IPDVUmd lg3OqQf9HD1F7WJobRRMHL+xKMXd/J/Xg8Qrgnv488j0w6BbxsPcB0IFTY+e7oE1 M0vZJ3zRz8o7/f5gBWdbRIEw6JGdP1Ho4AQiI7dUpAXhi32IkbV+lIy5B5Mw2p1d 47Bfojv1QzKC9YlTgYtSEvPswXBgHe53iuM3YfHI0xho2KRW39U+hFAfmQanEeHY IRQTExyULNzihrnbuNShREUeG8jzV8re43Ie91UvPSOtW+X0+HfMrla7DpW/Jx1q cuoIWoShu83ZBnKCHBjuKkXeb/a09QAhV+7o4TNRhX99ha8FeSSffZm9IV24gdAu L2WEgh40z1uvrmM/Xnf/uuC9Vvy5Yw== =bZ5b -----END PGP SIGNATURE----- --sdtB3X0nJg68CQEu-- From owner-freebsd-questions@freebsd.org Mon Jan 8 09:55:25 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0ED30E60BA8 for ; Mon, 8 Jan 2018 09:55:25 +0000 (UTC) (envelope-from fidaj@ukr.net) Received: from frv72.fwdcdn.com (frv72.fwdcdn.com [212.42.77.72]) by mx1.freebsd.org (Postfix) with ESMTP id BDC5373528 for ; Mon, 8 Jan 2018 09:55:23 +0000 (UTC) (envelope-from fidaj@ukr.net) Received: from [10.10.17.75] (helo=frv155.fwdcdn.com) by frv72.fwdcdn.com QID:1eYTnF-000BVW-KY/RC:1; Mon, 08 Jan 2018 11:32:33 +0200 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=fsm; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References: In-Reply-To:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=kIGBgTyN8m+KDikjohJ82bupL+gXdRCYFmCe30jUaGY=; b=XkT2GMyuIPUii9PVDxWbAWzvgW /WKweVEoF7gkBrM1gUc2Ey2G1BqXIzcrmYdjpf6U4D3FzHUg1fNSZjyr+lIbSBIOQTFY6SgerEIuh uIwF5oU1inqkzc04llZ+d3hgFM0drFXQHVT38bXDJcs/SYLjxQ5iYIjkOcMvYzNcLmbI=; Received: from [109.122.32.175] (helo=nonamehost) by frv155.fwdcdn.com with esmtpsa ID 1eYTn6-000A28-PS ; Mon, 08 Jan 2018 11:32:24 +0200 Date: Mon, 8 Jan 2018 11:32:24 +0200 From: Ivan Klymenko To: Aryeh Friedman Cc: Matthias Apitz , FreeBSD Mailing List Subject: Re: Meltdown =?UTF-8?B?4oCT?= Spectre Message-ID: <20180108113224.691d6dd4@nonamehost> In-Reply-To: References: <3AECDC7F-8838-4C09-AC7F-117DFBAA326C@sigsegv.be> <20180108085756.GA3001@c720-r314251> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWpqak/Pz/i4uIfHx8GBwZwcHAQEBA6o92AAAACHElEQVQ4jWWUTY7bMAyF6QzUPSEoa8PFHEBgqwuM4bVVg7MvZOj+R+ijpMTpjIwgkT7z75EKrdfattpXERG6zqvUOtAr2LCRYfEKcB4l/Q+2cc6XjQH7hv+2YZYreIk5nevZEPvuzUzptizHLzgDMnC5Wpbl7ewJlOEqlQF+DlCjgVLki0WV6FMDMsBxjlJiQulIznwZ+DxHiQyDyIg0wN3Oo6o6ZQ5s5AIfar+W2Wlmz+kCcb8tg6j3voMEwNrBQk69dDBDqw/urpqJH+m+Q6u/4QnoAeYpnUXC/s1iup9rhCd6xMgAqdDyAyFegbKkVAHeLCcOulPLawaoUIDos4M88iLNrVkU7uu5ccTDO6naJzWLum51C6Yb7y4HKKbdArLWir0PBiS8glJRBZHeyHl7J9lENpAC6qT9NlNG4u5hsVYDyJP6mlJJtY3oVju4WSUzHal1sDU17NASoBWSk40J2eBLBJhYrVmzC5gVALGpNIAiQgN6eGstOp9Oa6zFbbLTISYi28BGZDRUJKWeroECkCEkzXjUtbmmaKMfAx2RfbT69/cO+tgHcmx6AfyZOmj3NDIah0F0GB66d4CrdIoplNFFGHSpSheRxbo0W4S8azNItEoMWbw3uXAeJgCrmX5joz7CGXqSg6PcryEhnFr/C1C2ntPxBOYbdwY+8dO3+wZJyFlbMX9s8zNnvp/tLwAv03NB4j3HVpn8Awwm+GrlP6MVAAAAAElFTkSuQmCC MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Authentication-Result: IP=109.122.32.175; mail.from=fidaj@ukr.net; dkim=pass; header.d=ukr.net X-Ukrnet-Yellow: 0 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 09:55:25 -0000 =D0=92 Mon, 8 Jan 2018 04:15:46 -0500 Aryeh Friedman =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > TL;DR -- It seems Linux and Windows already have issues with these > holes but I have seen little to no evidence that FreeBSD (when run as > a host). In general when ever any virtualization issue (like the > bleed through on Qemu last year) comes up FreeBSD is the one OS that > seems to be immune (thanks to good design of the OS and bhyve). > This is the main reason why I chose FreeBSD over Linux as the > reference host for PetiteCloud. There are available exploit on the web - could you check their performance on your FreeBSD resources? ;) From owner-freebsd-questions@freebsd.org Mon Jan 8 10:45:59 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BAA90E63614 for ; Mon, 8 Jan 2018 10:45:59 +0000 (UTC) (envelope-from lenzi.sergio@gmail.com) Received: from mail-qt0-x232.google.com (mail-qt0-x232.google.com [IPv6:2607:f8b0:400d:c0d::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 7356575381 for ; Mon, 8 Jan 2018 10:45:59 +0000 (UTC) (envelope-from lenzi.sergio@gmail.com) Received: by mail-qt0-x232.google.com with SMTP id d4so13012710qtj.5 for ; Mon, 08 Jan 2018 02:45:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=pLO7SVEmHGZESn24cnjc1ZFd+Cs0op+QRrPigYdtoDk=; b=Q3zYq9ivadTefl3JFI79wtjbpaX+4y7L1iSIuFuTy2eU8aBWjXKLYi7leB6m4Yqonk Gp1UDLxKfo8sWJlfsgsuo7knyOsmFZSLpZvCG4yr+sGuTtfp9Yke5rvObSYzNvgykMwV 6O44RDB3myhf6Q2EzEMav5SAIC/WOdVZy2u0F1R/YTZAuCALXUlksDDyY6qRAYYUGsfL VsqrIeg1lO1L6j+vVFvVwPMRnU7v8Gd8G1JBgaRJVZi4dRqyx3MXj2a92eoDHxrU3TR0 5Ba0E6yH4Emm6unvbKCEl483RhZPBaqfs7lgV5sxXsPKmzoMMo5az+dNvpLFRGtFkbEs rhcg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=pLO7SVEmHGZESn24cnjc1ZFd+Cs0op+QRrPigYdtoDk=; b=tZZ54dPDyQ6Z6NGt72lK9nqxvu9u01SEtrIDxvj1bSNIdUI4m8iK4SzHOgqYIHzj4N 4tirWCeEn7z2OiwIAmBl0OHDW11Ru8fca1Lo+J/TWJP4Zq2sQpnYcj5Ppk9o3xAff9Gx pdfgYGnR5XZmq75opGj4n4T4r48zJsX4AIflHoRMRHNODnX1zP6qOmnQR1BFw8jJRj+o 2cJUING06Fg2k0MQYvzURL1zHE27DnGRVKiDy6aS3D8C9Y4HZvCUwnddjuyGsggunusu VJ6aT5vbK5797c8Z4wCCHyshlFrH1sS7Oi+0BLsiBK3TyqzFi5GNQtEPxSpU0r+oiZzE j0sw== X-Gm-Message-State: AKwxytcHnUQBMswS201U/l+jSDevwtH6ERG/W2nSa2IW1axY3zKHqSU7 JEPmJyOJx4UkkgMVDw7VPKFQEgIItf80MEX5pq4= X-Google-Smtp-Source: ACJfBosbdDMyECrSeeFwdhzgX+l63yLyTJMuDfNOjY/4J6Ng8+QdWQdf5TI/WR3fQHrN2tpy7e7i9mO1mrCJXNk8b+Q= X-Received: by 10.200.50.169 with SMTP id z38mr16480886qta.333.1515408358509; Mon, 08 Jan 2018 02:45:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.99.3 with HTTP; Mon, 8 Jan 2018 02:45:57 -0800 (PST) Received: by 10.140.99.3 with HTTP; Mon, 8 Jan 2018 02:45:57 -0800 (PST) In-Reply-To: <20180104055057.GA2656@c720-r314251> References: <20180104055057.GA2656@c720-r314251> From: sergio lenzi Date: Mon, 8 Jan 2018 08:45:57 -0200 Message-ID: Subject: Re: client for matrix.org To: Matthias Apitz , freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 10:45:59 -0000 Seems there is a port of in the ports tree in the net-im directory Em 4 de jan de 2018 3:51 AM, "Matthias Apitz" escreveu: > > Hello, > > Anybody knows some client for matrix.org which could run on FreeBSD? > Thanks > > matthias > -- > Matthias Apitz, =E2=9C=89 guru@unixarea.de, =E2=8C=82 http://www.unixarea= .de/ =F0=9F=93=B1 > +49-176-38902045 > Public GnuPG key: http://www.unixarea.de/key.pub > From owner-freebsd-questions@freebsd.org Mon Jan 8 12:28:51 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9382AE69396 for ; Mon, 8 Jan 2018 12:28:51 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.231]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5F10D78BF7 for ; Mon, 8 Jan 2018 12:28:50 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from raspberrypi.bildanet.com ([65.186.67.174]) by cmsmtp with ESMTP id YWXmeoZzwq4O5YWXperLZp; Mon, 08 Jan 2018 12:28:49 +0000 Received: from [192.168.1.143] by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1eYWXm-0000sn-D0 for freebsd-questions@freebsd.org; Mon, 08 Jan 2018 12:28:46 +0000 Subject: =?UTF-8?Q?Re:_Meltdown_=e2=80=93_Spectre?= To: freebsd-questions@freebsd.org References: <3AECDC7F-8838-4C09-AC7F-117DFBAA326C@sigsegv.be> <20180108085756.GA3001@c720-r314251> From: Baho Utot Message-ID: <48211515-cc6b-522b-ccd2-4d0c1f6a2072@columbus.rr.com> Date: Mon, 8 Jan 2018 07:28:41 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfKz0ThTtvprZRVsuVNnklDTXodFT2KIhSSfq/YArQPw/RFXNS7RJC1SS2sRtqofEQeJ7UxUM9NjHYDRDAFT04VNocTG87fSzm/NlSuszqrjWEi9nLoqM jHh/tW/3htr4mIhzPsZ345Y4/xAbpZnJMPv/VLnu80ufKeFcvc5FvNtgrSjxd5B/dOsSmYRVYVr9cyBAuuXKsww/L8De+1+bcwM= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 12:28:51 -0000 On 1/8/2018 4:15 AM, Aryeh Friedman wrote: > On Mon, Jan 8, 2018 at 3:57 AM, Matthias Apitz wrote: > >> As I side note, and not related to FreeBSD: My Internet server is run by >> some webhosting company (www.1blu.de), they use Ubuntu servers and since >> yesterday they have shutdown SSH access to the servers argumenting that >> they want >> protect my (all's) servers against attacks of Meltdown and Spectre. >> >> Imagine, next time we have to shutdown all IOT gadgets... > > > Not always possible for things like medical test equipment/devices. For > example I maintain a specialized EMR for interacting with Dr. prescribed > remote cardiac monitors. Having those off line is not an option since > they are used to detect if the patient needs something more serious like a > pace maker (also almost always a IoT device these days) surgery. > > The actual monitoring is done on Windows and was attacked by some > ransomeware via a bit coin miner that somehow installed it self. Since > all the users claim that they don't read email/upload/download executables > or any other of the known attack vectors this leaves something like > Meltdown or Spectre. We have also detected issues on the CentOS that has > the non-medical corporate site on it. The only machine left on touched on > the physical server (running some bare metal virtualization tool) is the > FreeBSD machine that runs the actual EMR we wrote. > > TL;DR -- It seems Linux and Windows already have issues with these holes > but I have seen little to no evidence that FreeBSD (when run as a host). > In general when ever any virtualization issue (like the bleed through on > Qemu last year) comes up FreeBSD is the one OS that seems to be immune > (thanks to good design of the OS and bhyve). This is the main reason why > I chose FreeBSD over Linux as the reference host for PetiteCloud. > This is not operating system specific, read the papers on theses two. it attacks the cpu, usally through a JIT From owner-freebsd-questions@freebsd.org Mon Jan 8 12:37:35 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 74B84E69AD0 for ; Mon, 8 Jan 2018 12:37:35 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 37BBA790D8 for ; Mon, 8 Jan 2018 12:37:35 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by mail-io0-x236.google.com with SMTP id n14so13258753iob.4 for ; Mon, 08 Jan 2018 04:37:35 -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=toxNgA2Hvor5yKeKAzdMJaXVdXlYMELxH4jW3DAAh+U=; b=N3tRPwCu0Wul8T07RIRD+7GyqOLOJNMPlLwW8/UD5OnRvS4sy8/yz9DNfrE4mG3Y4p g6vcaJ7WioNahM4jeOceltC1ll4uE/dlW7E3L+/LuiBx//DLMy2CeCs9P9ACp+G/KfNc Z49gXsW4VWcpko5sdZulDcu9hKnK7hUpwZjdvf7NeJ8Zrov4txvFyK5Yqs+Lq7JnOObJ nACg2NCBaHfeNNgNxwDcaSr98QljLdRWPsozmhrCsPSrkYW0+VaYMFctf67mw6pHxgwp w9TezT6kWAzfH0HhKumMsDilT33RETtyxpV80ZccZjsqaMQOxe/Vr/KcPajODc+eM9ef y1ag== 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=toxNgA2Hvor5yKeKAzdMJaXVdXlYMELxH4jW3DAAh+U=; b=Ehkbe1vNZXHruc96dTP/N9g8CXlYarREvCKtJuYf4WKQvFyNz79I9JRqz07dAXZG+s rNkncTpfJqfnVO0hj+3TzpWW4Ay8Ov5IePdWR+u7dD+3u5Sq5fgC+MAToVmum8Cep7NC 1CoVeIjKRCfi3mSYmlH7W1PUs0IyT/tNS69LBFb5jQ7bPeMQiWdaGDfbUCbemBwVxgkx h0P2J8rD8ySuHw1/wFzD4YLtmsVunQrv/Moo/RIiWOJMa2aA5c3QnjZzMCTvjR+7+3Oz wETnS4w/nBlIIkvut5lpPmOniCoA0LeSgTU/39+dTzAQij4ZmZ+Nb6+jptfb+9H5GaT9 Oecw== X-Gm-Message-State: AKwxytfE9DKvTdPYi8rEjsCIBVhG/AD1rYPrq2V51Z7SgJTEG8VUan1D ad7fquRyloRreUxFfgmWwD/0OhXXcgzGRmnbcY8= X-Google-Smtp-Source: ACJfBovazIIia3u25gAMxTjp9BZy7xcK2jTtoFIxV4NhnJvrRWxWuTMMP2qSpyFrZ9nypN9pU2Jr9JQzPA52oQPM0hE= X-Received: by 10.107.180.200 with SMTP id d191mr11521467iof.249.1515415054644; Mon, 08 Jan 2018 04:37:34 -0800 (PST) MIME-Version: 1.0 Received: by 10.36.105.3 with HTTP; Mon, 8 Jan 2018 04:37:34 -0800 (PST) In-Reply-To: <48211515-cc6b-522b-ccd2-4d0c1f6a2072@columbus.rr.com> References: <3AECDC7F-8838-4C09-AC7F-117DFBAA326C@sigsegv.be> <20180108085756.GA3001@c720-r314251> <48211515-cc6b-522b-ccd2-4d0c1f6a2072@columbus.rr.com> From: Aryeh Friedman Date: Mon, 8 Jan 2018 07:37:34 -0500 Message-ID: Subject: =?UTF-8?B?UmU6IE1lbHRkb3duIOKAkyBTcGVjdHJl?= To: Baho Utot Cc: FreeBSD Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 12:37:35 -0000 On Mon, Jan 8, 2018 at 7:28 AM, Baho Utot wrote: > > > On 1/8/2018 4:15 AM, Aryeh Friedman wrote: > >> On Mon, Jan 8, 2018 at 3:57 AM, Matthias Apitz wrote: >> >> As I side note, and not related to FreeBSD: My Internet server is run by >>> some webhosting company (www.1blu.de), they use Ubuntu servers and since >>> yesterday they have shutdown SSH access to the servers argumenting that >>> they want >>> protect my (all's) servers against attacks of Meltdown and Spectre. >>> >>> Imagine, next time we have to shutdown all IOT gadgets... >>> >> >> >> Not always possible for things like medical test equipment/devices. For >> example I maintain a specialized EMR for interacting with Dr. prescribed >> remote cardiac monitors. Having those off line is not an option since >> they are used to detect if the patient needs something more serious like a >> pace maker (also almost always a IoT device these days) surgery. >> >> The actual monitoring is done on Windows and was attacked by some >> ransomeware via a bit coin miner that somehow installed it self. Since >> all the users claim that they don't read email/upload/download executables >> or any other of the known attack vectors this leaves something like >> Meltdown or Spectre. We have also detected issues on the CentOS that has >> the non-medical corporate site on it. The only machine left on touched >> on >> the physical server (running some bare metal virtualization tool) is the >> FreeBSD machine that runs the actual EMR we wrote. >> >> TL;DR -- It seems Linux and Windows already have issues with these holes >> but I have seen little to no evidence that FreeBSD (when run as a host). >> In general when ever any virtualization issue (like the bleed through on >> Qemu last year) comes up FreeBSD is the one OS that seems to be immune >> (thanks to good design of the OS and bhyve). This is the main reason why >> I chose FreeBSD over Linux as the reference host for PetiteCloud. >> >> > This is not operating system specific, read the papers on theses two. it > attacks the cpu, usally through a JIT Please learn a little OS design theory before making insane claims. Specifically it *ONLY* effects OS's that rely on the specific CPU architecture (vs. a generic one). Namely if you strictly partition the page table between userland and kernel space (which xxxBSD has always done and Linux has not) and don't use any CPU specific instructions to do so (except for protected vs. unprotected mode in the original 386 design FreeBSD does not do this while yet again microslut and linux do). For more info go read the more technical thread then here in -hackers@ and -current@. From owner-freebsd-questions@freebsd.org Mon Jan 8 12:58:56 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B3CAEE6AD86 for ; Mon, 8 Jan 2018 12:58:56 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.227]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7CE8D79D57 for ; Mon, 8 Jan 2018 12:58:55 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from raspberrypi.bildanet.com ([65.186.67.174]) by cmsmtp with ESMTP id YWsCe2vvRU2piYWsFeeEdB; Mon, 08 Jan 2018 12:49:55 +0000 Received: from [192.168.1.143] by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1eYWw1-0000tw-GE; Mon, 08 Jan 2018 12:53:49 +0000 Subject: =?UTF-8?Q?Re:_Meltdown_=e2=80=93_Spectre?= To: Aryeh Friedman Cc: FreeBSD Mailing List References: <3AECDC7F-8838-4C09-AC7F-117DFBAA326C@sigsegv.be> <20180108085756.GA3001@c720-r314251> <48211515-cc6b-522b-ccd2-4d0c1f6a2072@columbus.rr.com> From: Baho Utot Message-ID: <44279dcb-7b15-865a-ca71-938b3832d0e7@columbus.rr.com> Date: Mon, 8 Jan 2018 07:53:44 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfDQ1UIcoAMrqCGjFU/vqUlTkKEhO5fdHvc17otzfGHnXGeClgsVSDW+tY8XB+ZUeVBJcheh5V/a2GBubi74MSVWzLhp+qHX6UJ4YteiEY5bIbKJKrkCn O90dc1ufL7RwLpmfr7rm4kdapgMSROE7/SqgNjpAbU5w0NkgqU3BLEQx5xBp4cBjqZo4M+ZL/ENCztQj2F88XZtJ5rfIAjRXb4k3UIwJW4nhM8fMXcW+6BW4 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 12:58:56 -0000 On 1/8/2018 7:37 AM, Aryeh Friedman wrote: > > > On Mon, Jan 8, 2018 at 7:28 AM, Baho Utot > wrote: > > > > On 1/8/2018 4:15 AM, Aryeh Friedman wrote: > > On Mon, Jan 8, 2018 at 3:57 AM, Matthias Apitz > wrote: > > As I side note, and not related to FreeBSD: My Internet > server is run by > some webhosting company (www.1blu.de ), > they use Ubuntu servers and since > yesterday they have shutdown SSH access to the servers > argumenting that > they want > protect my (all's) servers against attacks of Meltdown and > Spectre. > > Imagine, next time we have to shutdown all IOT gadgets... > > > >   Not always possible for things like medical test > equipment/devices.  For > example I maintain a specialized EMR for interacting with Dr. > prescribed > remote cardiac monitors.   Having those off line is not an > option since > they are used to detect if the patient needs something more > serious like a > pace maker (also almost always a IoT device these days) surgery. > > The actual monitoring is done on Windows and was attacked by some > ransomeware via a bit coin miner that somehow installed it > self.   Since > all the users claim that they don't read email/upload/download > executables > or any other of the known attack vectors this leaves something like > Meltdown or Spectre.   We have also detected issues on the > CentOS that has > the non-medical corporate site on it.   The only machine left on > touched on > the physical server (running some bare metal virtualization > tool) is the > FreeBSD machine that runs the actual EMR we wrote. > > TL;DR -- It seems Linux and Windows already have issues with > these holes > but I have seen little to no evidence that FreeBSD (when run as > a host). > In general when ever any virtualization issue (like the bleed > through on > Qemu last year) comes up FreeBSD is the one OS that seems to be > immune > (thanks to good design of the OS and bhyve).   This is the main > reason why > I chose FreeBSD over Linux as the reference host for PetiteCloud. > > > This is not operating system specific,  read the papers on theses > two. it attacks the cpu, usally through a JIT > > > Please learn a little OS design theory before making insane claims. > Specifically it *ONLY* effects OS's that rely on the specific CPU > architecture (vs. a generic one).  Namely if you strictly partition the > page table between userland and kernel space (which xxxBSD has always > done and Linux has not) and don't use any CPU specific instructions to > do so (except for protected vs. unprotected mode in the original 386 > design FreeBSD does not do this while yet again microslut and linux do). > > For more info go read the more technical thread then here in -hackers@ > and -current@. Go read the papers Spectre and Meltdown. This attacks Intel and Arm processors, AMD processors seems to not have the issue. Intel is issuing new firmware for their processors. Why is does then Apple have the problem as well? From the papaer Modern processors use branch prediction and speculative execution to maximize performance. For example, if the destination of a branch depends on a memory value that is in the process of being read, CPUs will try guess the destination and attempt to execute ahead. When the memory value finally arrives, the CPU either discards or commits the speculative computation. Speculative logic is unfaithful in how it executes, can access to the victim’s memory and registers, and can perform operations with measurable side effects. Spectre attacks involve inducing a victim to speculatively perform operations that would not occur during correct program execution and which leak the victim’s confidential information via a side channel to the adversary. This paper describes practical attacks that combine methodology from side channel attacks, fault attacks, and return-oriented programming that can read arbitrary memory from the victim’s process. More broadly, the paper shows that speculative execution implementations violate the security assumptions underpinning numerous software security mechanisms, including operating system process separation, static analysis, containerization, just-in-time (JIT) compilation, and countermeasures to cache timing/side-channel attacks. These attacks represent a serious threat to actual systems, since vulnerable speculative execution capabilities are found in microprocessors from Intel, AMD, and ARM that are used in billions of devices. And: Abstract The security of computer systems fundamentally relies on memory isolation, e.g., kernel address ranges are marked as non-accessible and are protected from user access. In this paper, we present Meltdown. Meltdown exploits side effects of out-of-order execution on modern processors to read arbitrary kernel-memory locations including personal data and passwords. Out-of-order execution is an indispensable performance feature and present in a wide range of modern processors. The attack is independent of the operating system, and it does not rely on any software vulnerabilities. Meltdown breaks all security assumptions given by address space isolation as well as paravirtualized environments and, thus, every security mechanism building upon this foundation. On affected systems, Meltdown enables an adversary to read memory of other processes or virtual machines in the cloud without any permissions or privileges, affecting millions of customers and virtually every user of a personal computer. We show that the KAISER defense mechanism for KASLR [8] has the important (but inadvertent) side effect of impeding Meltdown. We stress that KAISER must be deployed immediately to prevent large-scale exploitation of this severe information leakage. One of the central security features of today’s operating systems is memory isolation. Operating systems ensure that user applications cannot access each other’s memories and prevent user applications from reading or writing kernel memory. This isolation is a cornerstone of our computing environments and allows running multiple applications on personal devices or executing processes of multiple users on a single machine in the cloud. On modern processors, the isolation between the kernel and user processes is typically realized by a superviOne of the central security features of today’s operating systems is memory isolation. Operating systems ensure that user applications cannot access each other’s memories and prevent user applications from reading or writing kernel memory. This isolation is a cornerstone of our computing environments and allows running multiple applications on personal devices or executing processes of multiple users on a single machine in the cloud. On modern processors, the isolation between the kernel and user processes is typically realized by a supervisor bit of the processor that defines whether a memory page of the kernel can be accessed or not. The basic idea is that this bit can only be set when entering kernel code and it is cleared when switching to user processes. This hardware feature allows operating systems to map the kernel into the address space of every process and to have very efficient transitions from the user process to the kernel, e.g., for interrupt handling. Consequently, in practice, there is no change of the memory mapping when switching from a user process to the kernel novel attack that allows overcoming memory isolation completely by providing a simple way for any user process to read the entire kernel memory of the machine it executes on, including all physical memory mapped in the kernel region. Meltdown does not exploit any software vulnerability, i.e., it works on all major operating systems. Instead, Meltdown exploits side-channel information available on most modern processors, e.g., modern Intel microarchitectures since 2010 and potentially on other CPUs of other vendors. Notice: Meltdown does not exploit any software vulnerability, i.e., it works on all major operating systems. Your turn From owner-freebsd-questions@freebsd.org Mon Jan 8 12:49:16 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB84CE6A50E for ; Mon, 8 Jan 2018 12:49:16 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.231]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 682BE79667 for ; Mon, 8 Jan 2018 12:49:14 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from raspberrypi.bildanet.com ([65.186.67.174]) by cmsmtp with ESMTP id YWl9e2n1VU2piYWlCeeBCh; Mon, 08 Jan 2018 12:42:39 +0000 Received: from [192.168.1.143] by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1eYWox-0000tf-SJ for freebsd-questions@freebsd.org; Mon, 08 Jan 2018 12:46:32 +0000 Subject: =?UTF-8?Q?Re:_Meltdown_=e2=80=93_Spectre?= To: FreeBSD Mailing List References: <3AECDC7F-8838-4C09-AC7F-117DFBAA326C@sigsegv.be> <20180108085756.GA3001@c720-r314251> <48211515-cc6b-522b-ccd2-4d0c1f6a2072@columbus.rr.com> From: Baho Utot Message-ID: <87b03f62-48fb-3de7-01da-2b90fc79c549@columbus.rr.com> Date: Mon, 8 Jan 2018 07:46:26 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-CMAE-Envelope: MS4wfPint8yM6C/97JMEnLYnE3d9neu8fJ1V6jiHiURF53g2HTiGV8vM84+s9A/k2WfWirnmVKK+sHrF73R+caDlR2k6GKSanaqDCmQaaLy1llnnJCJee9X6 KuuxwD8+mP08N0jBpuxtvzV1vsUO8LajUBxCprPnnfquyNcXBYY2s26qmw09iGTLEKnimWHfZ6jniOhxMUNJx/JZQAFYKFIlGFU= X-Mailman-Approved-At: Mon, 08 Jan 2018 15:12:44 +0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 12:49:16 -0000 On 1/8/2018 7:37 AM, Aryeh Friedman wrote: > > > On Mon, Jan 8, 2018 at 7:28 AM, Baho Utot > wrote: > > > > On 1/8/2018 4:15 AM, Aryeh Friedman wrote: > > On Mon, Jan 8, 2018 at 3:57 AM, Matthias Apitz > wrote: > > As I side note, and not related to FreeBSD: My Internet > server is run by > some webhosting company (www.1blu.de ), > they use Ubuntu servers and since > yesterday they have shutdown SSH access to the servers > argumenting that > they want > protect my (all's) servers against attacks of Meltdown and > Spectre. > > Imagine, next time we have to shutdown all IOT gadgets... > > > >   Not always possible for things like medical test > equipment/devices.  For > example I maintain a specialized EMR for interacting with Dr. > prescribed > remote cardiac monitors.   Having those off line is not an > option since > they are used to detect if the patient needs something more > serious like a > pace maker (also almost always a IoT device these days) surgery. > > The actual monitoring is done on Windows and was attacked by some > ransomeware via a bit coin miner that somehow installed it > self.   Since > all the users claim that they don't read email/upload/download > executables > or any other of the known attack vectors this leaves something like > Meltdown or Spectre.   We have also detected issues on the > CentOS that has > the non-medical corporate site on it.   The only machine left on > touched on > the physical server (running some bare metal virtualization > tool) is the > FreeBSD machine that runs the actual EMR we wrote. > > TL;DR -- It seems Linux and Windows already have issues with > these holes > but I have seen little to no evidence that FreeBSD (when run as > a host). > In general when ever any virtualization issue (like the bleed > through on > Qemu last year) comes up FreeBSD is the one OS that seems to be > immune > (thanks to good design of the OS and bhyve).   This is the main > reason why > I chose FreeBSD over Linux as the reference host for PetiteCloud. > > > This is not operating system specific,  read the papers on theses > two. it attacks the cpu, usally through a JIT > > > Please learn a little OS design theory before making insane claims. > Specifically it *ONLY* effects OS's that rely on the specific CPU > architecture (vs. a generic one).  Namely if you strictly partition the > page table between userland and kernel space (which xxxBSD has always > done and Linux has not) and don't use any CPU specific instructions to > do so (except for protected vs. unprotected mode in the original 386 > design FreeBSD does not do this while yet again microslut and linux do). > > For more info go read the more technical thread then here in -hackers@ > and -current@. From owner-freebsd-questions@freebsd.org Mon Jan 8 16:28:27 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1A51FE75E26 for ; Mon, 8 Jan 2018 16:28:27 +0000 (UTC) (envelope-from andipersti@gmail.com) Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9CD2483A28 for ; Mon, 8 Jan 2018 16:28:26 +0000 (UTC) (envelope-from andipersti@gmail.com) Received: by mail-wr0-x232.google.com with SMTP id p6so11357253wrd.0 for ; Mon, 08 Jan 2018 08:28:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-transfer-encoding; bh=9Rnd5693XlLjnm/smvYvgkQiAHX53P72GPKFtbOC/4A=; b=BV5mKHNDtWSb3qXG38XqNeoxcm9/o+8QUup1EtVA8LbWSMCLhPuUwYxY+W7QCagj4I U0GAo0muQoY4Sk3wqB4hoidtf6JC8R+ibIbC7r3+TL6gPv6O5iAWDfra/VhflQa4qo1d xfULP/M5Qta2ZXf72FQJ7EZcnMTWjWvcSYbQ2MfS301LXlhnKsEfO4PLvFzu5U5IDCVe TJSr4Q6fj8W0LzWpZm0f6BS7ePFL0r7WecuxuJnZW77WbupWsZ5CIttzV7PwwU92CxzE EwLeSyTsR47HVkW6B03FImcM2DnXdDDIyZlD47QLPMGxAdtcpnNQRuzlwuiWbqTtPhxu rebw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=9Rnd5693XlLjnm/smvYvgkQiAHX53P72GPKFtbOC/4A=; b=iRA2EeLnm/BgY+BZ49wFZLfWQ8zzMFKIaVDg1jkvxU4sGwgQ1TePYxCKkZMz6aDga1 SKs9f8Lcjqtoum+Jgai7VIroB7YQBWxWn/5C+OuZTIb8Y27IYHFBD3rXYzGFex3oMRPX mBU+008aOQiuVEOVwMVP1rfsRs395Ti48FlNRfSSUWgUwVkaE2Q2oRc5zyifEC7Hxo1f PXAjOX+7L7tXfIAMY54kgJsciY9wb7AN0knoYnCPpp1a6xxZspCXZg391ejquNufHsyI lthyNfS5I1HSYKt3lzs3tP/+QmciG7EFLY0z9YRUk7kZQmjMb1o1A9OO3lDGtBFAMaIu Urdw== X-Gm-Message-State: AKGB3mLYFUmbU86enweUDjyMFOdfjnfNYzGn0bMUCNJg1W95UBfAcLgE jFSZmlpl6WsirP7LKzhbT5taZw== X-Google-Smtp-Source: ACJfBosNGFMKW8qGhcecWs4RIFbmBG07NvuonXZQxQ1HLb5gNFc8/Iq1Yq4eX63rCMuJHLBmO1sIog== X-Received: by 10.223.153.103 with SMTP id x94mr4119522wrb.210.1515428903999; Mon, 08 Jan 2018 08:28:23 -0800 (PST) Received: from Hof (193-80-0-180.hdsl.highway.telekom.at. [193.80.0.180]) by smtp.gmail.com with ESMTPSA id h16sm8368599wre.43.2018.01.08.08.28.23 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 08 Jan 2018 08:28:23 -0800 (PST) Date: Mon, 8 Jan 2018 17:28:20 +0100 From: Andreas Perstinger To: FreeBSD Mailing List Subject: Re: Convert .flac and .ape to mp3 Message-ID: <20180108172820.594a1f84@Hof> In-Reply-To: <20180108073900.GB52639@admin.sibptus.transneft.ru> References: <20180104163421.GA15692@admin.sibptus.transneft.ru> <20180104175156.440fa0c2.freebsd@edvax.de> <20180106063934.GA32231@admin.sibptus.transneft.ru> <20180106151754.GA35747@admin.sibptus.transneft.ru> <06f10c10-8e39-ec9b-de84-0c345c8be229@gmail.com> <20180108073900.GB52639@admin.sibptus.transneft.ru> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 16:28:27 -0000 Victor Sudakov wrote: >Returning to the initial question, I still have not found a way to >split a large flac/ape file into mp3 tracks, and writing relevant id3 >tags into resulting tracks, in accordance with the information in the >cue file. > >I'm still trying to brew a stew from sysutils/bchunk, >multimedia/ffmpeg, audio/flac, audio/id3tool, audio/lame, audio/mac, >audio/mp3splt, audio/shntool with rather little success. According to https://wiki.archlinux.org/index.php/CUE_Splitting a combination of audio/shntool, audio/lame (for splitting into mp3 files) and audio/cuetools (for tagging) should work. Bye, Andreas From owner-freebsd-questions@freebsd.org Mon Jan 8 17:06:40 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 607EDE78155 for ; Mon, 8 Jan 2018 17:06:40 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::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 E80502DB8 for ; Mon, 8 Jan 2018 17:06:39 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: by mail-lf0-x234.google.com with SMTP id h5so12854304lfj.2 for ; Mon, 08 Jan 2018 09:06: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:content-transfer-encoding; bh=IT8drgiTiZKkClyBm7t0yC3hU/lCJdey1K0L5Abvwow=; b=G+PVIb2rIlpHX1ORjpW4K/gYoOle+92xlbgomouTHwbR8DqURZTJvFMMot7rLy/zZS yodZwl1Bzs1RKoO2RER9whbuz0ihd7fKnLwv7bwwh9gvWM98P12+hmoh2lIUZkdpizHk 1arKWzYJ1Pjmc6aAQQBMgwIDGOQ21Jq//WdJj63ZFPM3UAmTDZZxm8Ovw/nKz61L0w0P iSYosINVaiSUtWbN/oJyYA6PJryjMB81RBoY+Wq7VNBbtSCEKhTqCWdVgpA3XTGdhn63 tpbCT5OKxarPI0PxzuPbDxfBFRGAGwGp/sJBcJYHybucwkVf8gyTUoUSvyIbsoVMkznh aGKg== 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=IT8drgiTiZKkClyBm7t0yC3hU/lCJdey1K0L5Abvwow=; b=W4Yhxvw+o2rS4DfcvVpVBkmxbf50colD48M3CcRLpDFtfqzNH091Cf3QeF3zfngiXA 1Z3qD2jfM7F8QcUwMvlWS/8W2+Tmj0Ey0dPb1PVTyyX2TP8OBT19SlIbS+2ygvR7pG54 2SVpK0XzRN2nBPxFthIYRVd1zABkGShLP2OmQqlIidSpy5Vr2/QVF5DXEZHBXgEJYMvp 8a0vJWdiImQI/xvZrobU8k9O+BPsjL2OOkzNnr/EpuMoGIe+FNZkUGJ9vMm9ZGLtusM8 D8DlXRDJJD0QJGzr4BB+9U/oAMoXDdTnmKF6+WepT5dJ8BktoAiPK4QOxsKGpeYjFaoH Xr+A== X-Gm-Message-State: AKwxyten3oli9aQc3sVXdTwg4d0lBuGxXiWlLG3uUeGdOalYEo8LIpYG 4k5/t4IPcQ9N7Z67HwlJ4FZMHWDM63DNTYmCvG0= X-Google-Smtp-Source: ACJfBovjMDM+hQ1Y0Xu5UKrsaLIDssv28INPMSwMVWoikQatPcWDN7Z2lOM1aSvEdksVMzjOYGs2zlaRsnb9/H/dFYY= X-Received: by 10.25.17.227 with SMTP id 96mr1025388lfr.85.1515431197782; Mon, 08 Jan 2018 09:06:37 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.19.219 with HTTP; Mon, 8 Jan 2018 09:06:36 -0800 (PST) In-Reply-To: References: From: =?UTF-8?Q?Fernando_Apestegu=C3=ADa?= Date: Mon, 8 Jan 2018 18:06:36 +0100 Message-ID: Subject: =?UTF-8?B?UmU6IE1lbHRkb3duIOKAkyBTcGVjdHJl?= To: Baho Utot Cc: FreeBSD Questions Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 17:06:40 -0000 On Mon, Jan 8, 2018 at 3:18 AM, Baho Utot wrote= : > > On 1/7/2018 9:11 PM, Efrain Dector wrote: >> >> Hi. >> >> Read about it here: >> https://www.freebsd.org/news/newsflash.html#event20180104:01 >> >> Cheers >> >> El 7 ene. 2018 8:06 p. m., "Baho Utot" > > escribi=C3=B3: >> >> What is freeBSD doing for these attacks? >> _______________________________________________ > > > Ok thanks, It looks like the linux folks is more on top of this as they > already have code released for the 4.4 4.9 with the 4.15 kernels being at > release candidate. Yes, but issues are not completely clear. See the "Spectre" section of this post by Greg Kroah-Hartman: http://kroah.com/log/blog/2018/01/06/meltdown-status/ > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o= rg" From owner-freebsd-questions@freebsd.org Mon Jan 8 17:10:18 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E16CEE7855B for ; Mon, 8 Jan 2018 17:10:18 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from kicp.uchicago.edu (kicp.uchicago.edu [128.135.20.70]) by mx1.freebsd.org (Postfix) with ESMTP id A412E335A for ; Mon, 8 Jan 2018 17:10:18 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from point.uchicago.edu (point.uchicago.edu [128.135.52.6]) by kicp.uchicago.edu (Postfix) with ESMTP id 2188471803D; Mon, 8 Jan 2018 11:10:12 -0600 (CST) Subject: =?UTF-8?Q?Re:_Meltdown_=e2=80=93_Spectre?= To: Baho Utot , Aryeh Friedman Cc: FreeBSD Mailing List References: <3AECDC7F-8838-4C09-AC7F-117DFBAA326C@sigsegv.be> <20180108085756.GA3001@c720-r314251> <48211515-cc6b-522b-ccd2-4d0c1f6a2072@columbus.rr.com> <44279dcb-7b15-865a-ca71-938b3832d0e7@columbus.rr.com> From: Valeri Galtsev Message-ID: Date: Mon, 8 Jan 2018 11:10:12 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <44279dcb-7b15-865a-ca71-938b3832d0e7@columbus.rr.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 17:10:19 -0000 On 01/08/18 06:53, Baho Utot wrote: > > > On 1/8/2018 7:37 AM, Aryeh Friedman wrote: >> >> >> On Mon, Jan 8, 2018 at 7:28 AM, Baho Utot > > wrote: >> >> >> >>     On 1/8/2018 4:15 AM, Aryeh Friedman wrote: >> >>         On Mon, Jan 8, 2018 at 3:57 AM, Matthias Apitz >         > wrote: >> >>             As I side note, and not related to FreeBSD: My Internet >>             server is run by >>             some webhosting company (www.1blu.de ), >>             they use Ubuntu servers and since >>             yesterday they have shutdown SSH access to the servers >>             argumenting that >>             they want >>             protect my (all's) servers against attacks of Meltdown and >>             Spectre. >> >>             Imagine, next time we have to shutdown all IOT gadgets... >> >> >> >>            Not always possible for things like medical test >>         equipment/devices.  For >>         example I maintain a specialized EMR for interacting with Dr. >>         prescribed >>         remote cardiac monitors.   Having those off line is not an >>         option since >>         they are used to detect if the patient needs something more >>         serious like a >>         pace maker (also almost always a IoT device these days) surgery. >> >>         The actual monitoring is done on Windows and was attacked by some >>         ransomeware via a bit coin miner that somehow installed it >>         self.   Since >>         all the users claim that they don't read email/upload/download >>         executables >>         or any other of the known attack vectors this leaves something >> like >>         Meltdown or Spectre.   We have also detected issues on the >>         CentOS that has >>         the non-medical corporate site on it.   The only machine left on >>         touched on >>         the physical server (running some bare metal virtualization >>         tool) is the >>         FreeBSD machine that runs the actual EMR we wrote. >> >>         TL;DR -- It seems Linux and Windows already have issues with >>         these holes >>         but I have seen little to no evidence that FreeBSD (when run as >>         a host). >>         In general when ever any virtualization issue (like the bleed >>         through on >>         Qemu last year) comes up FreeBSD is the one OS that seems to be >>         immune >>         (thanks to good design of the OS and bhyve).   This is the main >>         reason why >>         I chose FreeBSD over Linux as the reference host for PetiteCloud. >> >> >>     This is not operating system specific,  read the papers on theses >>     two. it attacks the cpu, usally through a JIT >> >> >> Please learn a little OS design theory before making insane claims. >> Specifically it *ONLY* effects OS's that rely on the specific CPU >> architecture (vs. a generic one).  Namely if you strictly partition >> the page table between userland and kernel space (which xxxBSD has >> always done and Linux has not) and don't use any CPU specific >> instructions to do so (except for protected vs. unprotected mode in >> the original 386 design FreeBSD does not do this while yet again >> microslut and linux do). >> >> For more info go read the more technical thread then here in -hackers@ >> and -current@. > > > Go read the papers Spectre and Meltdown. > This attacks Intel and Arm processors, AMD processors seems to not have > the issue.  Intel is issuing new firmware for their processors. > Why is does then Apple have the problem as well? > > From the papaer > > Modern processors use branch prediction and speculative > execution to maximize performance. For example, if > the destination of a branch depends on a memory value > that is in the process of being read, CPUs will try guess > the destination and attempt to execute ahead. When the > memory value finally arrives, the CPU either discards or > commits the speculative computation. Speculative logic > is unfaithful in how it executes, can access to the victim’s > memory and registers, and can perform operations with > measurable side effects. > Spectre attacks involve inducing a victim to speculatively > perform operations that would not occur during > correct program execution and which leak the victim’s > confidential information via a side channel to the adversary. > This paper describes practical attacks that combine > methodology from side channel attacks, fault attacks, > and return-oriented programming that can read arbitrary > memory from the victim’s process. More broadly, the > paper shows that speculative execution implementations > violate the security assumptions underpinning numerous > software security mechanisms, including operating system > process separation, static analysis, containerization, > just-in-time (JIT) compilation, and countermeasures to > cache timing/side-channel attacks. These attacks represent > a serious threat to actual systems, since vulnerable > speculative execution capabilities are found in microprocessors > from Intel, AMD, and ARM that are used in billions > of devices. > > And: > > Abstract > The security of computer systems fundamentally relies > on memory isolation, e.g., kernel address ranges are > marked as non-accessible and are protected from user > access. In this paper, we present Meltdown. Meltdown > exploits side effects of out-of-order execution on modern > processors to read arbitrary kernel-memory locations > including personal data and passwords. Out-of-order > execution is an indispensable performance feature and > present in a wide range of modern processors. The attack > is independent of the operating system, and it does not > rely on any software vulnerabilities. Meltdown breaks > all security assumptions given by address space isolation > as well as paravirtualized environments and, thus, > every security mechanism building upon this foundation. > On affected systems, Meltdown enables an adversary to > read memory of other processes or virtual machines in > the cloud without any permissions or privileges, affecting > millions of customers and virtually every user of a > personal computer. We show that the KAISER defense > mechanism for KASLR [8] has the important (but inadvertent) > side effect of impeding Meltdown. We stress > that KAISER must be deployed immediately to prevent > large-scale exploitation of this severe information leakage. > > > One of the central security features of today’s operating > systems is memory isolation. Operating systems ensure > that user applications cannot access each other’s memories > and prevent user applications from reading or writing > kernel memory. This isolation is a cornerstone of our > computing environments and allows running multiple applications > on personal devices or executing processes of > multiple users on a single machine in the cloud. > On modern processors, the isolation between the kernel > and user processes is typically realized by a superviOne of the central > security features of today’s operating > systems is memory isolation. Operating systems ensure > that user applications cannot access each other’s memories > and prevent user applications from reading or writing > kernel memory. This isolation is a cornerstone of our > computing environments and allows running multiple applications > on personal devices or executing processes of > multiple users on a single machine in the cloud. > On modern processors, the isolation between the kernel > and user processes is typically realized by a supervisor > bit of the processor that defines whether a memory > page of the kernel can be accessed or not. The basic > idea is that this bit can only be set when entering kernel > code and it is cleared when switching to user processes. > This hardware feature allows operating systems to map > the kernel into the address space of every process and > to have very efficient transitions from the user process > to the kernel, e.g., for interrupt handling. Consequently, > in practice, there is no change of the memory mapping > when switching from a user process to the kernel > novel attack that allows overcoming memory isolation > completely by providing a simple way for any user process > to read the entire kernel memory of the machine it > executes on, including all physical memory mapped in > the kernel region. Meltdown does not exploit any software > vulnerability, i.e., it works on all major operating > systems. Instead, Meltdown exploits side-channel information > available on most modern processors, e.g., modern > Intel microarchitectures since 2010 and potentially > on other CPUs of other vendors. > > Notice: > > Meltdown does not exploit any software vulnerability, i.e., it works on > all major operating systems. Hi Baho, This above information aside, your logic somewhat escapes me. On one hand you are expecting kernel fix (are you?) which FreeBSD is working on (the sooner the better!). On the other hand you insist on conclusion that this trouble is independent on operating system, implying, FreeBSD is in the same level of danger than any other operating system. The truth may be somewhere in between. That is: yes, all systems as they are can potentially be impacted. However, depending on architecture, the impact may be different. Someone clever (with deeper knowledge of FreeBSD architecture and better insight into problem) may correct me here. The fact that FreeBSD still works on this problem whereas Microsoft and Linux kernel folks already released their patches to me speaks highly of FreeBSD. FreeBSD appears to do really thorough job. As example, I would mention this: Linux (CentOS aka "binary replica" of RedHat Enterprise) often after releasing kernel patch, releases second kernel patch 2-3 days later. Which makes all who maintain parks of Linux machines and patch them promptly reboot the machines twice in a course of few days. There are special cases sometimes, but mostly this is indication of not thorough enough work. I don't remember similar things happen to FreeBSD. This pretty much reminds me how someone concluded that ATI does more thorough work on drivers compared to NVIDIA, pointing to the fact that ATI releases drivers only twice a year, whereas NVIDIA has to constantly release drivers updates: Monthly. Just my $0.02 Valeri -- ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++ From owner-freebsd-questions@freebsd.org Mon Jan 8 17:15:49 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6957CE78A07 for ; Mon, 8 Jan 2018 17:15:49 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C4BAA3887 for ; Mon, 8 Jan 2018 17:15:48 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: by mail-lf0-x22f.google.com with SMTP id w23so2711908lfd.11 for ; Mon, 08 Jan 2018 09:15:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=eGTw6dvYqXVcwdQzbKoF7TBahtMSVQrMVeW+0jFaDpQ=; b=I9PkOZBgg2hyvA08nbAuS1QALeuPlm/y79bobnXjQB4MYgTODO2oP198+sOd3Qm3Ze 3RYApI1Y/nfVU/4KET48SGeK6omSjkc0B7xZ1hPBvOkKswq83hKWH7DiZDeuwnXFKaCl crXXO5CakkXwnK2FLQdPTN2unp6hIRJq3BPr15KQ37wb76ywBG7BPTtsGDlTLAimGZh/ vveBMFIV7ykH4thNPpvGZI359LjetHfxEvyB92TRp/OtGUP5R1xDk/WSuWm0pFkgkfug Cubdz1GBVbeElIbTXSbTTbVsUzlfoMmkSVy4nhn8fe4r9qotdnbOWU+WfvWWKvEI8UNV pC7A== 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=eGTw6dvYqXVcwdQzbKoF7TBahtMSVQrMVeW+0jFaDpQ=; b=DTRxSnW//xZwY/tKQ5BIq1g3TKsbbehIzVSwEr6u5IF0Tgt9zxFDb9IAXSw+NyDMED sHz1TNalicIHKJfEzDs55LPx5BYAxCFTv1nbpVD91FmaVBvg41Tf3/ZBReJ2OZOPz9TD HakEV+XCND+4GVQDcsvxdnqnC3dxH+m53YkJ8lSJUhIeT+iZBwoZX9o35ocuewfblmDc mfELkGgvlEwOsh5iVAL/u8cpxapwVtTGHYFSZfpXRx8o1nzpPA+CPs42HMBgeflwpbwn ac2XlmQyLlRj70kM8jDZIPsLi7F+y+XTD46mFUMB4np50Fn/j3UE/GbjVwHqwR2+snBa T3fA== X-Gm-Message-State: AKwxytfHD0r8en2UCTRsmQ0JOGRRham3KRdJ8oobNUCcRQ888tjp8D2h X5rrtTCe6dpTD9uLuboTJ3dUYpbfyMbUd9kltWI= X-Google-Smtp-Source: ACJfBovqHwl8cE61EsjfCZPB37oX3WxEVk4mcCUqRaFTac00FhDyeaAl/okaiVhPjemMMQd8gWmpnriiXHuM+OQsoJo= X-Received: by 10.25.216.90 with SMTP id p87mr6446240lfg.11.1515431746717; Mon, 08 Jan 2018 09:15:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.19.219 with HTTP; Mon, 8 Jan 2018 09:15:45 -0800 (PST) Received: by 10.25.19.219 with HTTP; Mon, 8 Jan 2018 09:15:45 -0800 (PST) In-Reply-To: <44279dcb-7b15-865a-ca71-938b3832d0e7@columbus.rr.com> References: <3AECDC7F-8838-4C09-AC7F-117DFBAA326C@sigsegv.be> <20180108085756.GA3001@c720-r314251> <48211515-cc6b-522b-ccd2-4d0c1f6a2072@columbus.rr.com> <44279dcb-7b15-865a-ca71-938b3832d0e7@columbus.rr.com> From: =?UTF-8?Q?Fernando_Apestegu=C3=ADa?= Date: Mon, 8 Jan 2018 18:15:45 +0100 Message-ID: Subject: =?UTF-8?B?UmU6IE1lbHRkb3duIOKAkyBTcGVjdHJl?= To: Baho Utot Cc: Aryeh Friedman , User Questions Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 17:15:49 -0000 On Mon, Jan 8, 2018 at 1:53 PM, Baho Utot wrote= : > > > On 1/8/2018 7:37 AM, Aryeh Friedman wrote: >> >> >> >> On Mon, Jan 8, 2018 at 7:28 AM, Baho Utot > > wrote: >> >> >> >> On 1/8/2018 4:15 AM, Aryeh Friedman wrote: >> >> On Mon, Jan 8, 2018 at 3:57 AM, Matthias Apitz > > wrote: >> >> As I side note, and not related to FreeBSD: My Internet >> server is run by >> some webhosting company (www.1blu.de ), >> >> they use Ubuntu servers and since >> yesterday they have shutdown SSH access to the servers >> argumenting that >> they want >> protect my (all's) servers against attacks of Meltdown and >> Spectre. >> >> Imagine, next time we have to shutdown all IOT gadgets... >> >> >> >> Not always possible for things like medical test >> equipment/devices. For >> example I maintain a specialized EMR for interacting with Dr. >> prescribed >> remote cardiac monitors. Having those off line is not an >> option since >> they are used to detect if the patient needs something more >> serious like a >> pace maker (also almost always a IoT device these days) surgery. >> >> The actual monitoring is done on Windows and was attacked by some >> ransomeware via a bit coin miner that somehow installed it >> self. Since >> all the users claim that they don't read email/upload/download >> executables >> or any other of the known attack vectors this leaves something >> like >> Meltdown or Spectre. We have also detected issues on the >> CentOS that has >> the non-medical corporate site on it. The only machine left on >> touched on >> the physical server (running some bare metal virtualization >> tool) is the >> FreeBSD machine that runs the actual EMR we wrote. >> >> TL;DR -- It seems Linux and Windows already have issues with >> these holes >> but I have seen little to no evidence that FreeBSD (when run as >> a host). >> In general when ever any virtualization issue (like the bleed >> through on >> Qemu last year) comes up FreeBSD is the one OS that seems to be >> immune >> (thanks to good design of the OS and bhyve). This is the main >> reason why >> I chose FreeBSD over Linux as the reference host for PetiteCloud. >> >> >> This is not operating system specific, read the papers on theses >> two. it attacks the cpu, usally through a JIT >> >> >> Please learn a little OS design theory before making insane claims. >> Specifically it *ONLY* effects OS's that rely on the specific CPU >> architecture (vs. a generic one). Namely if you strictly partition the page >> table between userland and kernel space (which xxxBSD has always done an= d >> Linux has not) and don't use any CPU specific instructions to do so (except >> for protected vs. unprotected mode in the original 386 design FreeBSD does >> not do this while yet again microslut and linux do). >> >> For more info go read the more technical thread then here in -hackers@ and >> -current@. > > > > Go read the papers Spectre and Meltdown. > This attacks Intel and Arm processors, AMD processors seems to not have the > issue. Intel is issuing new firmware for their processors. > Why is does then Apple have the problem as well? About AMD, they seem to be affected by at least two variants of these attacks: https://www.amd.com/en/corporate/speculative-execution Cheers > > From the papaer > > Modern processors use branch prediction and speculative > execution to maximize performance. For example, if > the destination of a branch depends on a memory value > that is in the process of being read, CPUs will try guess > the destination and attempt to execute ahead. When the > memory value finally arrives, the CPU either discards or > commits the speculative computation. Speculative logic > is unfaithful in how it executes, can access to the victim=E2=80=99s > memory and registers, and can perform operations with > measurable side effects. > Spectre attacks involve inducing a victim to speculatively > perform operations that would not occur during > correct program execution and which leak the victim=E2=80=99s > confidential information via a side channel to the adversary. > This paper describes practical attacks that combine > methodology from side channel attacks, fault attacks, > and return-oriented programming that can read arbitrary > memory from the victim=E2=80=99s process. More broadly, the > paper shows that speculative execution implementations > violate the security assumptions underpinning numerous > software security mechanisms, including operating system > process separation, static analysis, containerization, > just-in-time (JIT) compilation, and countermeasures to > cache timing/side-channel attacks. These attacks represent > a serious threat to actual systems, since vulnerable > speculative execution capabilities are found in microprocessors > from Intel, AMD, and ARM that are used in billions > of devices. > > And: > > Abstract > The security of computer systems fundamentally relies > on memory isolation, e.g., kernel address ranges are > marked as non-accessible and are protected from user > access. In this paper, we present Meltdown. Meltdown > exploits side effects of out-of-order execution on modern > processors to read arbitrary kernel-memory locations > including personal data and passwords. Out-of-order > execution is an indispensable performance feature and > present in a wide range of modern processors. The attack > is independent of the operating system, and it does not > rely on any software vulnerabilities. Meltdown breaks > all security assumptions given by address space isolation > as well as paravirtualized environments and, thus, > every security mechanism building upon this foundation. > On affected systems, Meltdown enables an adversary to > read memory of other processes or virtual machines in > the cloud without any permissions or privileges, affecting > millions of customers and virtually every user of a > personal computer. We show that the KAISER defense > mechanism for KASLR [8] has the important (but inadvertent) > side effect of impeding Meltdown. We stress > that KAISER must be deployed immediately to prevent > large-scale exploitation of this severe information leakage. > > > One of the central security features of today=E2=80=99s operating > systems is memory isolation. Operating systems ensure > that user applications cannot access each other=E2=80=99s memories > and prevent user applications from reading or writing > kernel memory. This isolation is a cornerstone of our > computing environments and allows running multiple applications > on personal devices or executing processes of > multiple users on a single machine in the cloud. > On modern processors, the isolation between the kernel > and user processes is typically realized by a superviOne of the central > security features of today=E2=80=99s operating > systems is memory isolation. Operating systems ensure > that user applications cannot access each other=E2=80=99s memories > and prevent user applications from reading or writing > kernel memory. This isolation is a cornerstone of our > computing environments and allows running multiple applications > on personal devices or executing processes of > multiple users on a single machine in the cloud. > On modern processors, the isolation between the kernel > and user processes is typically realized by a supervisor > bit of the processor that defines whether a memory > page of the kernel can be accessed or not. The basic > idea is that this bit can only be set when entering kernel > code and it is cleared when switching to user processes. > This hardware feature allows operating systems to map > the kernel into the address space of every process and > to have very efficient transitions from the user process > to the kernel, e.g., for interrupt handling. Consequently, > in practice, there is no change of the memory mapping > when switching from a user process to the kernel > novel attack that allows overcoming memory isolation > completely by providing a simple way for any user process > to read the entire kernel memory of the machine it > executes on, including all physical memory mapped in > the kernel region. Meltdown does not exploit any software > vulnerability, i.e., it works on all major operating > systems. Instead, Meltdown exploits side-channel information > available on most modern processors, e.g., modern > Intel microarchitectures since 2010 and potentially > on other CPUs of other vendors. > > Notice: > > Meltdown does not exploit any software vulnerability, i.e., it works on all > major operating systems. > > Your turn > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " freebsd-questions-unsubscribe@freebsd.org" From owner-freebsd-questions@freebsd.org Mon Jan 8 17:20:45 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B5037E78D37 for ; Mon, 8 Jan 2018 17:20:45 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-cmomta03.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8151D3B14 for ; Mon, 8 Jan 2018 17:20:44 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from raspberrypi.bildanet.com ([65.186.67.174]) by cmsmtp with ESMTP id Yb5TeRzH0Se0pYb5WeajIm; Mon, 08 Jan 2018 17:19:54 +0000 Received: from [192.168.1.143] by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1eYb3j-0000z5-L3 for freebsd-questions@freebsd.org; Mon, 08 Jan 2018 17:18:03 +0000 Subject: =?UTF-8?Q?Re:_Meltdown_=e2=80=93_Spectre?= To: FreeBSD Questions References: From: Baho Utot Message-ID: <703351bd-f0d0-29d6-9149-2e7032a869e5@columbus.rr.com> Date: Mon, 8 Jan 2018 12:17:58 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfBvSSTChSj5MkC/6s/DLJNPuTAmuskpCI5K+cPm/FVLwFFPVK+Sga1P1lrpQImMCU8ZAjrb8SbCq1Bb7zElwdTAE7gdrfQXYOp1dP1o3Df3/E9beK0Ie eVROQ8yCY8IMjtISxXRuwlxtnn53XoG0mgLqD8pMNZAgtL1S/rcqNc5uNqBWwXi+MMjlTwDhsOUG+yTRbgWZz0Ig9/s0ZOSPQk4= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 17:20:45 -0000 On 1/8/2018 12:06 PM, Fernando Apesteguía wrote: > On Mon, Jan 8, 2018 at 3:18 AM, Baho Utot wrote: >> >> On 1/7/2018 9:11 PM, Efrain Dector wrote: >>> >>> Hi. >>> >>> Read about it here: >>> https://www.freebsd.org/news/newsflash.html#event20180104:01 >>> >>> Cheers >>> >>> El 7 ene. 2018 8:06 p. m., "Baho Utot" >> > escribió: >>> >>> What is freeBSD doing for these attacks? >>> _______________________________________________ >> >> >> Ok thanks, It looks like the linux folks is more on top of this as they >> already have code released for the 4.4 4.9 with the 4.15 kernels being at >> release candidate. > > Yes, but issues are not completely clear. See the "Spectre" section of > this post by Greg Kroah-Hartman: > > http://kroah.com/log/blog/2018/01/06/meltdown-status/ > Already did From owner-freebsd-questions@freebsd.org Mon Jan 8 17:25:59 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A4C53E79260 for ; Mon, 8 Jan 2018 17:25:59 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-cmomta03.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5D0A9634D6 for ; Mon, 8 Jan 2018 17:25:58 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from raspberrypi.bildanet.com ([65.186.67.174]) by cmsmtp with ESMTP id YbD4eSEUeSe0pYbD7eaqr3; Mon, 08 Jan 2018 17:27:45 +0000 Received: from [192.168.1.143] by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1eYbBK-0000zI-AE for freebsd-questions@freebsd.org; Mon, 08 Jan 2018 17:25:54 +0000 Subject: =?UTF-8?Q?Re:_Meltdown_=e2=80=93_Spectre?= To: FreeBSD Mailing List References: <3AECDC7F-8838-4C09-AC7F-117DFBAA326C@sigsegv.be> <20180108085756.GA3001@c720-r314251> <48211515-cc6b-522b-ccd2-4d0c1f6a2072@columbus.rr.com> <44279dcb-7b15-865a-ca71-938b3832d0e7@columbus.rr.com> From: Baho Utot Message-ID: Date: Mon, 8 Jan 2018 12:25:49 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfPDHOj38APEMOKAsihgn7vPndFavfNzeTmou+4S90mxc/SDNscm3+yzRSgyhB3iI+Dg3zMWilmrJ9amKBWMcVq8Zr2uRk2eUwLKBA7nsjIGpkIokEShy Uxwo4BHCm29QBQdsV1ezxIqiNm9N7xFQrAHu5cLQ5oc34zcGtKjPnzeIhXnyPCTCoSx5D0W3RxcgoO+jlHnAzGp2wvHdqG8OtM8= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 17:25:59 -0000 On 1/8/2018 12:10 PM, Valeri Galtsev wrote: > > > On 01/08/18 06:53, Baho Utot wrote: >> >> >> On 1/8/2018 7:37 AM, Aryeh Friedman wrote: >>> >>> >>> On Mon, Jan 8, 2018 at 7:28 AM, Baho Utot >> > wrote: >>> >>> >>> >>>     On 1/8/2018 4:15 AM, Aryeh Friedman wrote: >>> >>>         On Mon, Jan 8, 2018 at 3:57 AM, Matthias Apitz >>         > wrote: >>> >>>             As I side note, and not related to FreeBSD: My Internet >>>             server is run by >>>             some webhosting company (www.1blu.de ), >>>             they use Ubuntu servers and since >>>             yesterday they have shutdown SSH access to the servers >>>             argumenting that >>>             they want >>>             protect my (all's) servers against attacks of Meltdown and >>>             Spectre. >>> >>>             Imagine, next time we have to shutdown all IOT gadgets... >>> >>> >>> >>>            Not always possible for things like medical test >>>         equipment/devices.  For >>>         example I maintain a specialized EMR for interacting with Dr. >>>         prescribed >>>         remote cardiac monitors.   Having those off line is not an >>>         option since >>>         they are used to detect if the patient needs something more >>>         serious like a >>>         pace maker (also almost always a IoT device these days) surgery. >>> >>>         The actual monitoring is done on Windows and was attacked by >>> some >>>         ransomeware via a bit coin miner that somehow installed it >>>         self.   Since >>>         all the users claim that they don't read email/upload/download >>>         executables >>>         or any other of the known attack vectors this leaves >>> something like >>>         Meltdown or Spectre.   We have also detected issues on the >>>         CentOS that has >>>         the non-medical corporate site on it.   The only machine left on >>>         touched on >>>         the physical server (running some bare metal virtualization >>>         tool) is the >>>         FreeBSD machine that runs the actual EMR we wrote. >>> >>>         TL;DR -- It seems Linux and Windows already have issues with >>>         these holes >>>         but I have seen little to no evidence that FreeBSD (when run as >>>         a host). >>>         In general when ever any virtualization issue (like the bleed >>>         through on >>>         Qemu last year) comes up FreeBSD is the one OS that seems to be >>>         immune >>>         (thanks to good design of the OS and bhyve).   This is the main >>>         reason why >>>         I chose FreeBSD over Linux as the reference host for >>> PetiteCloud. >>> >>> >>>     This is not operating system specific,  read the papers on theses >>>     two. it attacks the cpu, usally through a JIT >>> >>> >>> Please learn a little OS design theory before making insane claims. >>> Specifically it *ONLY* effects OS's that rely on the specific CPU >>> architecture (vs. a generic one).  Namely if you strictly partition >>> the page table between userland and kernel space (which xxxBSD has >>> always done and Linux has not) and don't use any CPU specific >>> instructions to do so (except for protected vs. unprotected mode in >>> the original 386 design FreeBSD does not do this while yet again >>> microslut and linux do). >>> >>> For more info go read the more technical thread then here in >>> -hackers@ and -current@. >> >> >> Go read the papers Spectre and Meltdown. >> This attacks Intel and Arm processors, AMD processors seems to not >> have the issue.  Intel is issuing new firmware for their processors. >> Why is does then Apple have the problem as well? >> >>  From the papaer >> >> Modern processors use branch prediction and speculative >> execution to maximize performance. For example, if >> the destination of a branch depends on a memory value >> that is in the process of being read, CPUs will try guess >> the destination and attempt to execute ahead. When the >> memory value finally arrives, the CPU either discards or >> commits the speculative computation. Speculative logic >> is unfaithful in how it executes, can access to the victim’s >> memory and registers, and can perform operations with >> measurable side effects. >> Spectre attacks involve inducing a victim to speculatively >> perform operations that would not occur during >> correct program execution and which leak the victim’s >> confidential information via a side channel to the adversary. >> This paper describes practical attacks that combine >> methodology from side channel attacks, fault attacks, >> and return-oriented programming that can read arbitrary >> memory from the victim’s process. More broadly, the >> paper shows that speculative execution implementations >> violate the security assumptions underpinning numerous >> software security mechanisms, including operating system >> process separation, static analysis, containerization, >> just-in-time (JIT) compilation, and countermeasures to >> cache timing/side-channel attacks. These attacks represent >> a serious threat to actual systems, since vulnerable >> speculative execution capabilities are found in microprocessors >> from Intel, AMD, and ARM that are used in billions >> of devices. >> >> And: >> >> Abstract >> The security of computer systems fundamentally relies >> on memory isolation, e.g., kernel address ranges are >> marked as non-accessible and are protected from user >> access. In this paper, we present Meltdown. Meltdown >> exploits side effects of out-of-order execution on modern >> processors to read arbitrary kernel-memory locations >> including personal data and passwords. Out-of-order >> execution is an indispensable performance feature and >> present in a wide range of modern processors. The attack >> is independent of the operating system, and it does not >> rely on any software vulnerabilities. Meltdown breaks >> all security assumptions given by address space isolation >> as well as paravirtualized environments and, thus, >> every security mechanism building upon this foundation. >> On affected systems, Meltdown enables an adversary to >> read memory of other processes or virtual machines in >> the cloud without any permissions or privileges, affecting >> millions of customers and virtually every user of a >> personal computer. We show that the KAISER defense >> mechanism for KASLR [8] has the important (but inadvertent) >> side effect of impeding Meltdown. We stress >> that KAISER must be deployed immediately to prevent >> large-scale exploitation of this severe information leakage. >> >> >> One of the central security features of today’s operating >> systems is memory isolation. Operating systems ensure >> that user applications cannot access each other’s memories >> and prevent user applications from reading or writing >> kernel memory. This isolation is a cornerstone of our >> computing environments and allows running multiple applications >> on personal devices or executing processes of >> multiple users on a single machine in the cloud. >> On modern processors, the isolation between the kernel >> and user processes is typically realized by a superviOne of the >> central security features of today’s operating >> systems is memory isolation. Operating systems ensure >> that user applications cannot access each other’s memories >> and prevent user applications from reading or writing >> kernel memory. This isolation is a cornerstone of our >> computing environments and allows running multiple applications >> on personal devices or executing processes of >> multiple users on a single machine in the cloud. >> On modern processors, the isolation between the kernel >> and user processes is typically realized by a supervisor >> bit of the processor that defines whether a memory >> page of the kernel can be accessed or not. The basic >> idea is that this bit can only be set when entering kernel >> code and it is cleared when switching to user processes. >> This hardware feature allows operating systems to map >> the kernel into the address space of every process and >> to have very efficient transitions from the user process >> to the kernel, e.g., for interrupt handling. Consequently, >> in practice, there is no change of the memory mapping >> when switching from a user process to the kernel >> novel attack that allows overcoming memory isolation >> completely by providing a simple way for any user process >> to read the entire kernel memory of the machine it >> executes on, including all physical memory mapped in >> the kernel region. Meltdown does not exploit any software >> vulnerability, i.e., it works on all major operating >> systems. Instead, Meltdown exploits side-channel information >> available on most modern processors, e.g., modern >> Intel microarchitectures since 2010 and potentially >> on other CPUs of other vendors. >> >> Notice: >> >> Meltdown does not exploit any software vulnerability, i.e., it works >> on all major operating systems. > > Hi Baho, > > This above information aside, your logic somewhat escapes me. On one > hand you are expecting kernel fix (are you?) which FreeBSD is working on > (the sooner the better!). On the other hand you insist on conclusion > that this trouble is independent on operating system, implying, FreeBSD > is in the same level of danger than any other operating system. Don't recall saying I am expecting a kernel fix. The question was and is what is freebsd doing about these > > The truth may be somewhere in between. That is: yes, all systems as they > are can potentially be impacted. However, depending on architecture, the > impact may be different. Someone clever (with deeper knowledge of > FreeBSD architecture and better insight into problem) may correct me here. Read the Specter and Meltdown papers ( pdfs ) > > The fact that FreeBSD still works on this problem whereas Microsoft and > Linux kernel folks already released their patches to me speaks highly of > FreeBSD. FreeBSD appears to do really thorough job. As example, I would > mention this: Linux (CentOS aka "binary replica" of RedHat Enterprise) > often after releasing kernel patch, releases second kernel patch 2-3 > days later. Which makes all who maintain parks of Linux machines and > patch them promptly reboot the machines twice in a course of few days. > There are special cases sometimes, but mostly this is indication of not > thorough enough work. I don't remember similar things happen to FreeBSD. > This pretty much reminds me how someone concluded that ATI does more > thorough work on drivers compared to NVIDIA, pointing to the fact that > ATI releases drivers only twice a year, whereas NVIDIA has to constantly > release drivers updates: Monthly. Don't follow you here...... The question is what is freebsd doing to address this, as I stated before Apple, Android and Linux have some fixes for this, yes they are not complete as this appears to mainly affect Intel CPUs and not AMD. Can you point me to the freebsd fixes? I missed them. > > Just my $0.02 > > Valeri > From owner-freebsd-questions@freebsd.org Mon Jan 8 17:37:10 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 678D9E79C7A for ; Mon, 8 Jan 2018 17:37:10 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2F13063F8C for ; Mon, 8 Jan 2018 17:37:09 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from raspberrypi.bildanet.com ([65.186.67.174]) by cmsmtp with ESMTP id YbIJeBSl0U2piYbIMei6Y5; Mon, 08 Jan 2018 17:33:10 +0000 Received: from [192.168.1.143] by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1eYbM8-0000zr-O3; Mon, 08 Jan 2018 17:37:04 +0000 Subject: =?UTF-8?Q?Re:_Meltdown_=e2=80=93_Spectre?= To: =?UTF-8?Q?Fernando_Apestegu=c3=ada?= Cc: Aryeh Friedman , User Questions References: <3AECDC7F-8838-4C09-AC7F-117DFBAA326C@sigsegv.be> <20180108085756.GA3001@c720-r314251> <48211515-cc6b-522b-ccd2-4d0c1f6a2072@columbus.rr.com> <44279dcb-7b15-865a-ca71-938b3832d0e7@columbus.rr.com> From: Baho Utot Message-ID: Date: Mon, 8 Jan 2018 12:36:59 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfKZJVqmw8E/bFB8ak0QDi5tBItWWo2henEAeQAMGNMlDVCCla0BMJCjHpKi9Xipf9J2s2bbsamfU/rQfbzFlJK4NdQDec+H8TGZCGpOg/0FR70KvO5i/ NcD/scTyicZxPcCqj9NsuQxFgltsQJN/X+Ba5g2K/2GFiFeWqY0XP+scDrWMvLV0zrFnLtwlrfIgsefDQkf67cG1jN4IieWlgEAAZN8e0iIEewDQmNio1tsr aXCsStpNQ8/OgxWoj6mTOKz3Ydkc5EYW4MACgPM3N+a4AK9Kc+NcpxBAIpBIyHEq X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 17:37:10 -0000 On 1/8/2018 12:15 PM, Fernando Apesteguía wrote: > > > On Mon, Jan 8, 2018 at 1:53 PM, Baho Utot > wrote: > > > > > > On 1/8/2018 7:37 AM, Aryeh Friedman wrote: > >> > >> > >> > >> On Mon, Jan 8, 2018 at 7:28 AM, Baho Utot > >> >> wrote: > >> > >> > >> > >> On 1/8/2018 4:15 AM, Aryeh Friedman wrote: > >> > >> On Mon, Jan 8, 2018 at 3:57 AM, Matthias Apitz > >> >> wrote: > >> > >> As I side note, and not related to FreeBSD: My Internet > >> server is run by > >> some webhosting company (www.1blu.de > ), > >> > >> they use Ubuntu servers and since > >> yesterday they have shutdown SSH access to the servers > >> argumenting that > >> they want > >> protect my (all's) servers against attacks of Meltdown and > >> Spectre. > >> > >> Imagine, next time we have to shutdown all IOT gadgets... > >> > >> > >> > >> Not always possible for things like medical test > >> equipment/devices. For > >> example I maintain a specialized EMR for interacting with Dr. > >> prescribed > >> remote cardiac monitors. Having those off line is not an > >> option since > >> they are used to detect if the patient needs something more > >> serious like a > >> pace maker (also almost always a IoT device these days) surgery. > >> > >> The actual monitoring is done on Windows and was attacked by some > >> ransomeware via a bit coin miner that somehow installed it > >> self. Since > >> all the users claim that they don't read email/upload/download > >> executables > >> or any other of the known attack vectors this leaves something > >> like > >> Meltdown or Spectre. We have also detected issues on the > >> CentOS that has > >> the non-medical corporate site on it. The only machine left on > >> touched on > >> the physical server (running some bare metal virtualization > >> tool) is the > >> FreeBSD machine that runs the actual EMR we wrote. > >> > >> TL;DR -- It seems Linux and Windows already have issues with > >> these holes > >> but I have seen little to no evidence that FreeBSD (when run as > >> a host). > >> In general when ever any virtualization issue (like the bleed > >> through on > >> Qemu last year) comes up FreeBSD is the one OS that seems to be > >> immune > >> (thanks to good design of the OS and bhyve). This is the main > >> reason why > >> I chose FreeBSD over Linux as the reference host for PetiteCloud. > >> > >> > >> This is not operating system specific, read the papers on theses > >> two. it attacks the cpu, usally through a JIT > >> > >> > >> Please learn a little OS design theory before making insane claims. > >> Specifically it *ONLY* effects OS's that rely on the specific CPU > >> architecture (vs. a generic one). Namely if you strictly partition > the page > >> table between userland and kernel space (which xxxBSD has always > done and > >> Linux has not) and don't use any CPU specific instructions to do so > (except > >> for protected vs. unprotected mode in the original 386 design > FreeBSD does > >> not do this while yet again microslut and linux do). > >> > >> For more info go read the more technical thread then here in > -hackers@ and > >> -current@. > > > > > > > > Go read the papers Spectre and Meltdown. > > This attacks Intel and Arm processors, AMD processors seems to not > have the > > issue. Intel is issuing new firmware for their processors. > > Why is does then Apple have the problem as well? > > About AMD, they seem to be affected by at least two variants of these > attacks: > > https://www.amd.com/en/corporate/speculative-execution > Variant One Bounds Check Bypass Resolved by software / OS updates to be made available by system vendors and manufacturers. Negligible performance impact expected. Variant Two Branch Target Injection Differences in AMD architecture mean there is a near zero risk of exploitation of this variant. Vulnerability to Variant 2 has not been demonstrated on AMD processors to date. Variant Three Rogue Data Cache Load Zero AMD vulnerability due to AMD architecture differences. For Variant 1 OS fix For Variant 2 and 3 ZERO to near ZERO risk So yes my statement stands From owner-freebsd-questions@freebsd.org Mon Jan 8 17:43:11 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 80B69E7A2A7 for ; Mon, 8 Jan 2018 17:43:11 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::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 D27A76878A for ; Mon, 8 Jan 2018 17:43:08 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: by mail-lf0-x232.google.com with SMTP id j143so12978258lfg.0 for ; Mon, 08 Jan 2018 09:43:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=4qS08vVMFzXHTRe94JYvWf8EsvPx/l73HODqR5SlYV0=; b=lyel2YRYy544O+MqsDJruQNhAQp2FG5IX66Q6jfwQwBNTXheMFQjS4F2wp1v9hc4vH Q1yXdSA3Jt2De8F/dDptIlyPNekSKdgdPGD4GZ12kHcCW7oBJ7e0aJWTDZF2XRzTJ4I2 p/W9hrHVjWJDcyITmEzX/xwjRt+9yDiIrrfFKKS6ylmUVX6G5aQA7nojnfPX1znK+Hb3 qSIGPm9TXJ2gLkhxWXsxXscsPFaEmT8lYmPLSswL6ep00mOcdfLKXytsT8jSlNqeW5Rq 4k2pOAkJGtWZFCr44c4G7+BRfeCP2zgfaL4+EZN/HRsVg2migqdjBfSmDedo0F2PByIe p0WQ== 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=4qS08vVMFzXHTRe94JYvWf8EsvPx/l73HODqR5SlYV0=; b=uH4UlKHXv6c60I+zFFgCvc6souD5J4M1Nbj9Z4ciXWWd8JODB+xFNVbRLUza3kPHKq a0AgxtOYqIwr/Dc8C8UEhLu5psOC5kxq9eHBRSFG4VlGj+IarKPtJSwGhEgbspWX/1gY LRUBlwy98G842j5Or4X/+iNC00OBP3lGewFTuG+BdBfoofsaUis8kxNmfNvZTNilyisz j9/cLoBcZL4rkGWRdnvRo5WWtuwT/vmLLpQNPqkZ9Zufai/S8eb3QPfLj+dJ6HCwYfeD aTx4eyo/4bOmiSGYWEORAI0kc8tqU78Def57kieLzTCnm06flRga1Z9naEpPaNULIRG7 asEg== X-Gm-Message-State: AKGB3mKO65NZ21qVJLEwUrp4mt4pkq2lCEda2LkCEYW2z1b/8YdezMHS fY+Al2ae/WTwVXPEW36D9uLxXixR36rvnkFc1LI= X-Google-Smtp-Source: ACJfBouoxDTrRKQS8eR3h7PzcC1/MoPGMShZl7pz74hZuK9pLry0VGWgzFfV6ibplG8wHbQXqWlyOTBeRGBanTzgiQo= X-Received: by 10.46.7.79 with SMTP id i15mr6838753ljd.42.1515433386451; Mon, 08 Jan 2018 09:43:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.19.219 with HTTP; Mon, 8 Jan 2018 09:43:05 -0800 (PST) In-Reply-To: References: <3AECDC7F-8838-4C09-AC7F-117DFBAA326C@sigsegv.be> <20180108085756.GA3001@c720-r314251> <48211515-cc6b-522b-ccd2-4d0c1f6a2072@columbus.rr.com> <44279dcb-7b15-865a-ca71-938b3832d0e7@columbus.rr.com> From: =?UTF-8?Q?Fernando_Apestegu=C3=ADa?= Date: Mon, 8 Jan 2018 18:43:05 +0100 Message-ID: Subject: =?UTF-8?B?UmU6IE1lbHRkb3duIOKAkyBTcGVjdHJl?= To: Baho Utot Cc: Aryeh Friedman , User Questions Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 17:43:12 -0000 On Mon, Jan 8, 2018 at 6:36 PM, Baho Utot wrote= : > > > On 1/8/2018 12:15 PM, Fernando Apestegu=C3=ADa wrote: >> >> >> >> On Mon, Jan 8, 2018 at 1:53 PM, Baho Utot > > wrote: >> > >> > >> > On 1/8/2018 7:37 AM, Aryeh Friedman wrote: >> >> >> >> >> >> >> >> On Mon, Jan 8, 2018 at 7:28 AM, Baho Utot > >> >> = >> >> wrote: >> >> >> >> >> >> >> >> On 1/8/2018 4:15 AM, Aryeh Friedman wrote: >> >> >> >> On Mon, Jan 8, 2018 at 3:57 AM, Matthias Apitz > >> >> >> wrote: >> >> >> >> As I side note, and not related to FreeBSD: My Internet >> >> server is run by >> >> some webhosting company (www.1blu.de >> ), >> >> >> >> >> they use Ubuntu servers and since >> >> yesterday they have shutdown SSH access to the servers >> >> argumenting that >> >> they want >> >> protect my (all's) servers against attacks of Meltdown and >> >> Spectre. >> >> >> >> Imagine, next time we have to shutdown all IOT gadgets... >> >> >> >> >> >> >> >> Not always possible for things like medical test >> >> equipment/devices. For >> >> example I maintain a specialized EMR for interacting with Dr. >> >> prescribed >> >> remote cardiac monitors. Having those off line is not an >> >> option since >> >> they are used to detect if the patient needs something more >> >> serious like a >> >> pace maker (also almost always a IoT device these days) surgery. >> >> >> >> The actual monitoring is done on Windows and was attacked by some >> >> ransomeware via a bit coin miner that somehow installed it >> >> self. Since >> >> all the users claim that they don't read email/upload/download >> >> executables >> >> or any other of the known attack vectors this leaves something >> >> like >> >> Meltdown or Spectre. We have also detected issues on the >> >> CentOS that has >> >> the non-medical corporate site on it. The only machine left on >> >> touched on >> >> the physical server (running some bare metal virtualization >> >> tool) is the >> >> FreeBSD machine that runs the actual EMR we wrote. >> >> >> >> TL;DR -- It seems Linux and Windows already have issues with >> >> these holes >> >> but I have seen little to no evidence that FreeBSD (when run as >> >> a host). >> >> In general when ever any virtualization issue (like the bleed >> >> through on >> >> Qemu last year) comes up FreeBSD is the one OS that seems to be >> >> immune >> >> (thanks to good design of the OS and bhyve). This is the main >> >> reason why >> >> I chose FreeBSD over Linux as the reference host for PetiteCloud. >> >> >> >> >> >> This is not operating system specific, read the papers on theses >> >> two. it attacks the cpu, usally through a JIT >> >> >> >> >> >> Please learn a little OS design theory before making insane claims. >> >> Specifically it *ONLY* effects OS's that rely on the specific CPU >> >> architecture (vs. a generic one). Namely if you strictly partition t= he >> page >> >> table between userland and kernel space (which xxxBSD has always don= e >> and >> >> Linux has not) and don't use any CPU specific instructions to do so >> (except >> >> for protected vs. unprotected mode in the original 386 design FreeBS= D >> does >> >> not do this while yet again microslut and linux do). >> >> >> >> For more info go read the more technical thread then here in -hacker= s@ >> and >> >> -current@. >> > >> > >> > >> > Go read the papers Spectre and Meltdown. >> > This attacks Intel and Arm processors, AMD processors seems to not ha= ve >> the >> > issue. Intel is issuing new firmware for their processors. >> > Why is does then Apple have the problem as well? >> >> About AMD, they seem to be affected by at least two variants of these >> attacks: >> >> https://www.amd.com/en/corporate/speculative-execution >> > > Variant One Bounds Check Bypass Resolved by software / OS > updates to be made available by > system vendors and > manufacturers. Negligible > performance impact expected. > > Variant Two Branch Target Injection Differences in AMD > architecture mean there > is a near zero risk of > exploitation of this > variant. Vulnerability > to Variant 2 has not > been demonstrated on AMD > processors to date. > > Variant Three Rogue Data Cache Load Zero AMD vulnerability due to > AMD architecture differences. > > For Variant 1 OS fix > > For Variant 2 and 3 ZERO to near ZERO risk > > So yes my statement stands Sorry, I might have misunderstood. The statement was "AMD processors seems to not have the issue". But they acknowledge the issue. In variant 1 it exists and it is fixed by OS (so if it is fixed, it means it affects AMD's processors), in variant 2 exists (nearly zero is not zero), and in variant 3, yes, it is not affected. So it is kind of a 2/3 affected for AMD. Cheers. > > From owner-freebsd-questions@freebsd.org Mon Jan 8 17:54:59 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ADBDFE7ADBC for ; Mon, 8 Jan 2018 17:54:59 +0000 (UTC) (envelope-from markham@ssimicro.com) Received: from barracuda.ssimicro.com (barracuda.ssimicro.com [96.46.39.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.ssimicro.com", Issuer "RapidSSL SHA256 CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 71D0569615 for ; Mon, 8 Jan 2018 17:54:59 +0000 (UTC) (envelope-from markham@ssimicro.com) X-ASG-Debug-ID: 1515433229-08e71748ab3003f0001-jLrpzn Received: from mail.ssimicro.com (mail.ssimicro.com [64.247.129.10]) by barracuda.ssimicro.com with ESMTP id sn0SmBRfiPbYtdos (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 08 Jan 2018 12:40:30 -0500 (EST) X-Barracuda-Envelope-From: markham@ssimicro.com X-Barracuda-Effective-Source-IP: mail.ssimicro.com[64.247.129.10] X-Barracuda-Apparent-Source-IP: 64.247.129.10 Received: from markham.ssimicro.com (markham.ssimicro.com [64.247.130.99]) (authenticated bits=0) by mail.ssimicro.com (8.15.2/8.15.2) with ESMTPSA id w08HeTnt082694 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Mon, 8 Jan 2018 10:40:29 -0700 (MST) (envelope-from markham@ssimicro.com) Subject: =?UTF-8?Q?Re:_Meltdown_=e2=80=93_Spectre?= To: FreeBSD Mailing List X-ASG-Orig-Subj: =?UTF-8?Q?Re:_Meltdown_=e2=80=93_Spectre?= References: <3AECDC7F-8838-4C09-AC7F-117DFBAA326C@sigsegv.be> <20180108085756.GA3001@c720-r314251> <48211515-cc6b-522b-ccd2-4d0c1f6a2072@columbus.rr.com> <44279dcb-7b15-865a-ca71-938b3832d0e7@columbus.rr.com> From: markham breitbach Message-ID: <7844e5a4-2b94-2ada-62ea-4418f088043a@ssimicro.com> Date: Mon, 8 Jan 2018 10:40:29 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-Barracuda-Connect: mail.ssimicro.com[64.247.129.10] X-Barracuda-Start-Time: 1515433229 X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384 X-Barracuda-URL: https://barracuda.ssimicro.com:443/cgi-mod/mark.cgi X-Barracuda-Scan-Msg-Size: 1181 X-Virus-Scanned: by bsmtpd at ssimicro.com X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using per-user scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=5.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.46671 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 17:54:59 -0000 > > The fact that FreeBSD still works on this problem whereas Microsoft > and Linux kernel folks already released their patches to me speaks > highly of FreeBSD. FreeBSD appears to do really thorough job. As > example, I would mention this: Linux (CentOS aka "binary replica" of > RedHat Enterprise) often after releasing kernel patch, releases second > kernel patch 2-3 days later. Which makes all who maintain parks of > Linux machines and patch them promptly reboot the machines twice in a > course of few days. There are special cases sometimes, but mostly this > is indication of not thorough enough work. I don't remember similar > things happen to FreeBSD. This pretty much reminds me how someone > concluded that ATI does more thorough work on drivers compared to > NVIDIA, pointing to the fact that ATI releases drivers only twice a > year, whereas NVIDIA has to constantly release drivers updates: Monthly. > > Just my $0.02 > > Valeri > It also appears that Microsoft and Linux a fair amount of extra lead time.  I understand they were notified about this back in October ort November, while FreeBSD did not get notified until December. -M From owner-freebsd-questions@freebsd.org Mon Jan 8 18:03:04 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F1100E7B605 for ; Mon, 8 Jan 2018 18:03:04 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A5EA869E77 for ; Mon, 8 Jan 2018 18:03:03 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from raspberrypi.bildanet.com ([65.186.67.174]) by cmsmtp with ESMTP id YbhIeCGqBU2piYbhLeiU10; Mon, 08 Jan 2018 17:59:00 +0000 Received: from [192.168.1.143] by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1eYbl8-000110-Hj; Mon, 08 Jan 2018 18:02:54 +0000 Subject: =?UTF-8?Q?Re:_Meltdown_=e2=80=93_Spectre?= To: =?UTF-8?Q?Fernando_Apestegu=c3=ada?= Cc: Aryeh Friedman , User Questions References: <3AECDC7F-8838-4C09-AC7F-117DFBAA326C@sigsegv.be> <20180108085756.GA3001@c720-r314251> <48211515-cc6b-522b-ccd2-4d0c1f6a2072@columbus.rr.com> <44279dcb-7b15-865a-ca71-938b3832d0e7@columbus.rr.com> From: Baho Utot Message-ID: <1e4ce22b-f647-adbc-8f41-93df0a9f9a3a@columbus.rr.com> Date: Mon, 8 Jan 2018 13:02:49 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfOTYQASM2YqDtmnin0Y8SGEqLNPk0Aso9RleyNgVY85tJLRwg/Gn5AEkFIwNdk+k3DcPK8kgSDNe+LnqjtqrjgTjxJS3rQO+nTiOBlLhPKQkJ/mKJIvy duku9mKEEtaR02EO7R6JVfNeyUbcvoleq/YhC3lKt6LeqQci/DxzXhS5bjcgo9vTYQBzQP4ipHL8X+P0eP6uV/Icmb/gCgSTUS1tNLt+XzjIZcK398UlKFj+ XTk7rMJiWjdpdhW/Bk0yzT/HXvUTWonobUkTvy7lRPW9rcpnFqs/X3sRFCQxUndK X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 18:03:05 -0000 On 1/8/2018 12:43 PM, Fernando Apesteguía wrote: > On Mon, Jan 8, 2018 at 6:36 PM, Baho Utot wrote: >> >> >> On 1/8/2018 12:15 PM, Fernando Apesteguía wrote: >>> >>> >>> >>> On Mon, Jan 8, 2018 at 1:53 PM, Baho Utot >> > wrote: >>> > >>> > >>> > On 1/8/2018 7:37 AM, Aryeh Friedman wrote: >>> >> >>> >> >>> >> >>> >> On Mon, Jan 8, 2018 at 7:28 AM, Baho Utot >> >>> >> >> >>> wrote: >>> >> >>> >> >>> >> >>> >> On 1/8/2018 4:15 AM, Aryeh Friedman wrote: >>> >> >>> >> On Mon, Jan 8, 2018 at 3:57 AM, Matthias Apitz >> >>> >> >> wrote: >>> >> >>> >> As I side note, and not related to FreeBSD: My Internet >>> >> server is run by >>> >> some webhosting company (www.1blu.de >>> ), >>> >>> >> >>> >> they use Ubuntu servers and since >>> >> yesterday they have shutdown SSH access to the servers >>> >> argumenting that >>> >> they want >>> >> protect my (all's) servers against attacks of Meltdown and >>> >> Spectre. >>> >> >>> >> Imagine, next time we have to shutdown all IOT gadgets... >>> >> >>> >> >>> >> >>> >> Not always possible for things like medical test >>> >> equipment/devices. For >>> >> example I maintain a specialized EMR for interacting with Dr. >>> >> prescribed >>> >> remote cardiac monitors. Having those off line is not an >>> >> option since >>> >> they are used to detect if the patient needs something more >>> >> serious like a >>> >> pace maker (also almost always a IoT device these days) surgery. >>> >> >>> >> The actual monitoring is done on Windows and was attacked by some >>> >> ransomeware via a bit coin miner that somehow installed it >>> >> self. Since >>> >> all the users claim that they don't read email/upload/download >>> >> executables >>> >> or any other of the known attack vectors this leaves something >>> >> like >>> >> Meltdown or Spectre. We have also detected issues on the >>> >> CentOS that has >>> >> the non-medical corporate site on it. The only machine left on >>> >> touched on >>> >> the physical server (running some bare metal virtualization >>> >> tool) is the >>> >> FreeBSD machine that runs the actual EMR we wrote. >>> >> >>> >> TL;DR -- It seems Linux and Windows already have issues with >>> >> these holes >>> >> but I have seen little to no evidence that FreeBSD (when run as >>> >> a host). >>> >> In general when ever any virtualization issue (like the bleed >>> >> through on >>> >> Qemu last year) comes up FreeBSD is the one OS that seems to be >>> >> immune >>> >> (thanks to good design of the OS and bhyve). This is the main >>> >> reason why >>> >> I chose FreeBSD over Linux as the reference host for PetiteCloud. >>> >> >>> >> >>> >> This is not operating system specific, read the papers on theses >>> >> two. it attacks the cpu, usally through a JIT >>> >> >>> >> >>> >> Please learn a little OS design theory before making insane claims. >>> >> Specifically it *ONLY* effects OS's that rely on the specific CPU >>> >> architecture (vs. a generic one). Namely if you strictly partition the >>> page >>> >> table between userland and kernel space (which xxxBSD has always done >>> and >>> >> Linux has not) and don't use any CPU specific instructions to do so >>> (except >>> >> for protected vs. unprotected mode in the original 386 design FreeBSD >>> does >>> >> not do this while yet again microslut and linux do). >>> >> >>> >> For more info go read the more technical thread then here in -hackers@ >>> and >>> >> -current@. >>> > >>> > >>> > >>> > Go read the papers Spectre and Meltdown. >>> > This attacks Intel and Arm processors, AMD processors seems to not have >>> the >>> > issue. Intel is issuing new firmware for their processors. >>> > Why is does then Apple have the problem as well? >>> >>> About AMD, they seem to be affected by at least two variants of these >>> attacks: >>> >>> https://www.amd.com/en/corporate/speculative-execution >>> >> >> Variant One Bounds Check Bypass Resolved by software / OS >> updates to be made available by >> system vendors and >> manufacturers. Negligible >> performance impact expected. >> >> Variant Two Branch Target Injection Differences in AMD >> architecture mean there >> is a near zero risk of >> exploitation of this >> variant. Vulnerability >> to Variant 2 has not >> been demonstrated on AMD >> processors to date. >> >> Variant Three Rogue Data Cache Load Zero AMD vulnerability due to >> AMD architecture differences. >> >> For Variant 1 OS fix >> >> For Variant 2 and 3 ZERO to near ZERO risk >> >> So yes my statement stands > > Sorry, I might have misunderstood. The statement was "AMD processors > seems to not have the issue". > But they acknowledge the issue. In variant 1 it exists and it is fixed > by OS (so if it is fixed, it means it affects AMD's processors), in > variant 2 exists (nearly zero is not zero), and in variant 3, yes, it > is not affected. > > So it is kind of a 2/3 affected for AMD. > > Cheers. > >> >> Meltdown [27] is a related microarchitectural attack which exploits out-of-order execution in order to leak the target’s physical memory. Meltdown is distinct from Spectre Attacks in two main ways. First, unlike Spectre, Meltdown does not use branch prediction for achieving speculative execution. Instead, it relies on the observation that when an instruction causes a trap, following instructions that were executed out-of-order are aborted. Second, Meltdown exploits a privilege escalation vulnerability specific to Intel processors, due to which speculatively executed instructions can bypass memory protection. Combining these issues, Meltdown accesses kernel memory from user space. This access causes a trap, but before the trap is issued, the code that follows the access leaks the contents of the accessed memory through a cache channel. Unlike Meltdown, the Spectre attack works on non- Intel processors, including AMD and ARM processors. Furthermore, the KAISER patch [19], which has been widely applied as a mitigation to the Meltdown attack, does not protect against Spectre. From owner-freebsd-questions@freebsd.org Mon Jan 8 18:11:42 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B7772E7C066 for ; Mon, 8 Jan 2018 18:11:42 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from kicp.uchicago.edu (kicp.uchicago.edu [128.135.20.70]) by mx1.freebsd.org (Postfix) with ESMTP id 818066A901 for ; Mon, 8 Jan 2018 18:11:41 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from point.uchicago.edu (point.uchicago.edu [128.135.52.6]) by kicp.uchicago.edu (Postfix) with ESMTP id B908F718054; Mon, 8 Jan 2018 12:11:40 -0600 (CST) Subject: =?UTF-8?Q?Re:_Meltdown_=e2=80=93_Spectre?= To: Aryeh Friedman , Baho Utot Cc: FreeBSD Mailing List References: <3AECDC7F-8838-4C09-AC7F-117DFBAA326C@sigsegv.be> <20180108085756.GA3001@c720-r314251> <48211515-cc6b-522b-ccd2-4d0c1f6a2072@columbus.rr.com> From: Valeri Galtsev Message-ID: Date: Mon, 8 Jan 2018 12:11:40 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 18:11:42 -0000 On 01/08/18 06:37, Aryeh Friedman wrote: > On Mon, Jan 8, 2018 at 7:28 AM, Baho Utot wrote: > >> >> >> On 1/8/2018 4:15 AM, Aryeh Friedman wrote: >> >>> On Mon, Jan 8, 2018 at 3:57 AM, Matthias Apitz wrote: >>> >>> As I side note, and not related to FreeBSD: My Internet server is run by >>>> some webhosting company (www.1blu.de), they use Ubuntu servers and since >>>> yesterday they have shutdown SSH access to the servers argumenting that >>>> they want >>>> protect my (all's) servers against attacks of Meltdown and Spectre. >>>> >>>> Imagine, next time we have to shutdown all IOT gadgets... >>>> >>> >>> >>> Not always possible for things like medical test equipment/devices. For >>> example I maintain a specialized EMR for interacting with Dr. prescribed >>> remote cardiac monitors. Having those off line is not an option since >>> they are used to detect if the patient needs something more serious like a >>> pace maker (also almost always a IoT device these days) surgery. >>> >>> The actual monitoring is done on Windows and was attacked by some >>> ransomeware via a bit coin miner that somehow installed it self. Since >>> all the users claim that they don't read email/upload/download executables >>> or any other of the known attack vectors this leaves something like >>> Meltdown or Spectre. We have also detected issues on the CentOS that has >>> the non-medical corporate site on it. The only machine left on touched >>> on >>> the physical server (running some bare metal virtualization tool) is the >>> FreeBSD machine that runs the actual EMR we wrote. >>> >>> TL;DR -- It seems Linux and Windows already have issues with these holes >>> but I have seen little to no evidence that FreeBSD (when run as a host). >>> In general when ever any virtualization issue (like the bleed through on >>> Qemu last year) comes up FreeBSD is the one OS that seems to be immune >>> (thanks to good design of the OS and bhyve). This is the main reason why >>> I chose FreeBSD over Linux as the reference host for PetiteCloud. >>> >>> >> This is not operating system specific, read the papers on theses two. it >> attacks the cpu, usally through a JIT > > > Please learn a little OS design theory before making insane claims. > Specifically it *ONLY* effects OS's that rely on the specific CPU > architecture (vs. a generic one). Namely if you strictly partition the > page table between userland and kernel space (which xxxBSD has always done > and Linux has not) and don't use any CPU specific instructions to do so > (except for protected vs. unprotected mode in the original 386 design > FreeBSD does not do this while yet again microslut and linux do). > > For more info go read the more technical thread then here in -hackers@ and > -current@. Thanks, Aryeh! Your posts made my day today. Valeri ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++ From owner-freebsd-questions@freebsd.org Mon Jan 8 18:17:08 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 70FF8E7C810 for ; Mon, 8 Jan 2018 18:17:08 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [IPv6:2607:f3e0:80:80::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2A4DD6B0ED for ; Mon, 8 Jan 2018 18:17:08 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (lava.sentex.ca [IPv6:2607:f3e0:0:5::11]) by smarthost2.sentex.ca (8.15.2/8.15.2) with ESMTPS id w08IH6ox018735 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 8 Jan 2018 13:17:07 -0500 (EST) (envelope-from mike@sentex.net) Received: from [192.168.43.26] (saphire3.sentex.net [192.168.43.26]) by lava.sentex.ca (8.15.2/8.15.2) with ESMTP id w08IH44W052704; Mon, 8 Jan 2018 13:17:05 -0500 (EST) (envelope-from mike@sentex.net) Subject: =?UTF-8?Q?Re:_Meltdown_=e2=80=93_Spectre?= To: Baho Utot , FreeBSD Mailing List References: From: Mike Tancsa Organization: Sentex Communications Message-ID: <018343d5-f5f0-8bbe-f8e1-e80a6853f7ab@sentex.net> Date: Mon, 8 Jan 2018 13:17:06 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.78 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 18:17:08 -0000 On 1/7/2018 9:05 PM, Baho Utot wrote: > What is freeBSD doing for these attacks? Latest updates at https://lists.freebsd.org/pipermail/freebsd-security/2018-January/009719.html ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-questions@freebsd.org Mon Jan 8 18:24:13 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4D8E0E7CF1D for ; Mon, 8 Jan 2018 18:24:13 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-cmomta03.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 174ED6B6B2 for ; Mon, 8 Jan 2018 18:24:12 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from raspberrypi.bildanet.com ([65.186.67.174]) by cmsmtp with ESMTP id Yc7PeU94aSe0pYc7SebkJW; Mon, 08 Jan 2018 18:25:58 +0000 Received: from [192.168.1.143] by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1eYc5f-00012F-Rv for freebsd-questions@freebsd.org; Mon, 08 Jan 2018 18:24:07 +0000 Subject: =?UTF-8?Q?Re:_Meltdown_=e2=80=93_Spectre?= To: freebsd-questions@freebsd.org References: <3AECDC7F-8838-4C09-AC7F-117DFBAA326C@sigsegv.be> <20180108085756.GA3001@c720-r314251> <48211515-cc6b-522b-ccd2-4d0c1f6a2072@columbus.rr.com> From: Baho Utot Message-ID: <64ee0030-8fef-0380-3b6e-b969d8ddb69f@columbus.rr.com> Date: Mon, 8 Jan 2018 13:24:03 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfGMa5wEweHDXvVmXqY+kkvlgAxRZ8LJozGg9mGdTPXT9IgmOi0mv9dn026AsKIOidsg1M5A28WaQW4O5hESjzc7m5unee99vaM2u64REiyQ7nK7PCZ70 Z13hqtn+C5F90Ee0kIiXxbEQ0hfytFnpUpZhxooGuvCB5GyPMl2DvMwoCWjdUSrHxroRdDxqsqmNi2DU70272bhpMPiyPQRi/WQ= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 18:24:13 -0000 On 1/8/2018 1:11 PM, Valeri Galtsev wrote: > > > On 01/08/18 06:37, Aryeh Friedman wrote: >> On Mon, Jan 8, 2018 at 7:28 AM, Baho Utot >> wrote: >> >>> >>> >>> On 1/8/2018 4:15 AM, Aryeh Friedman wrote: >>> >>>> On Mon, Jan 8, 2018 at 3:57 AM, Matthias Apitz >>>> wrote: >>>> >>>> As I side note, and not related to FreeBSD: My Internet server is >>>> run by >>>>> some webhosting company (www.1blu.de), they use Ubuntu servers and >>>>> since >>>>> yesterday they have shutdown SSH access to the servers argumenting >>>>> that >>>>> they want >>>>> protect my (all's) servers against attacks of Meltdown and Spectre. >>>>> >>>>> Imagine, next time we have to shutdown all IOT gadgets... >>>>> >>>> >>>> >>>>    Not always possible for things like medical test >>>> equipment/devices.  For >>>> example I maintain a specialized EMR for interacting with Dr. >>>> prescribed >>>> remote cardiac monitors.   Having those off line is not an option since >>>> they are used to detect if the patient needs something more serious >>>> like a >>>> pace maker (also almost always a IoT device these days) surgery. >>>> >>>> The actual monitoring is done on Windows and was attacked by some >>>> ransomeware via a bit coin miner that somehow installed it self. >>>> Since >>>> all the users claim that they don't read email/upload/download >>>> executables >>>> or any other of the known attack vectors this leaves something like >>>> Meltdown or Spectre.   We have also detected issues on the CentOS >>>> that has >>>> the non-medical corporate site on it.   The only machine left on >>>> touched >>>> on >>>> the physical server (running some bare metal virtualization tool) is >>>> the >>>> FreeBSD machine that runs the actual EMR we wrote. >>>> >>>> TL;DR -- It seems Linux and Windows already have issues with these >>>> holes >>>> but I have seen little to no evidence that FreeBSD (when run as a >>>> host). >>>> In general when ever any virtualization issue (like the bleed >>>> through on >>>> Qemu last year) comes up FreeBSD is the one OS that seems to be immune >>>> (thanks to good design of the OS and bhyve).   This is the main >>>> reason why >>>> I chose FreeBSD over Linux as the reference host for PetiteCloud. >>>> >>>> >>> This is not operating system specific,  read the papers on theses >>> two. it >>> attacks the cpu, usally through a JIT >> >> >> Please learn a little OS design theory before making insane claims. >> Specifically it *ONLY* effects OS's that rely on the specific CPU >> architecture (vs. a generic one).  Namely if you strictly partition the >> page table between userland and kernel space (which xxxBSD has always >> done >> and Linux has not) and don't use any CPU specific instructions to do so >> (except for protected vs. unprotected mode in the original 386 design >> FreeBSD does not do this while yet again microslut and linux do). >> >> For more info go read the more technical thread then here in -hackers@ >> and >> -current@. > > Thanks, Aryeh! Your posts made my day today. > > Valeri > > CERT states this: http://www.kb.cert.org/vuls/id/584653 FreeBSD Project Affected-05 Jan 2018 From owner-freebsd-questions@freebsd.org Mon Jan 8 18:58:30 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C24BE7EC73 for ; Mon, 8 Jan 2018 18:58:30 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E9A326D3F4 for ; Mon, 8 Jan 2018 18:58:29 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.18.98]) by mrelayeu.kundenserver.de (mreue004 [212.227.15.167]) with ESMTPA (Nemesis) id 0Lm8JB-1f7PHI2vVh-00ZhdA; Mon, 08 Jan 2018 19:58:21 +0100 Date: Mon, 8 Jan 2018 19:58:21 +0100 From: Polytropon To: Matthias Apitz Cc: freebsd-questions@freebsd.org Subject: Re: Meltdown =?UTF-8?B?4oCT?= Spectre Message-Id: <20180108195821.0195794b.freebsd@edvax.de> In-Reply-To: <20180108085756.GA3001@c720-r314251> References: <3AECDC7F-8838-4C09-AC7F-117DFBAA326C@sigsegv.be> <20180108085756.GA3001@c720-r314251> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:1HbKDLqD8Xjw2XzTWHmt3XC3zZk+G9XaC64HmFOcP8amwdHe+Uj 8+K4EusrfmffLl8RvSy6UU00nxyA5vmWXMfUsQL0m41FSjdhC1+dOWefAUubmcnRht3NM3x bz/S+HX8ZA427bgetR2kI7mUJvKtnRXKSMyV9sFOupEZtn5ACSYfTbEnt9qeHsX02/mSKeP vkkTg4ieSjVHkfkRSwWhQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:gMxF1I+qfYU=:h1Ixyw1u9o7Kltp7mEe6WY j3pnY5QZdRktc/bBuZT/o6j0jC7oUbsz8Hla1Xt/sCkKFAR7te0YdriS5en7ZxqfDOCealSyM 02b4tXI1wW3df4laTQmo1z4tS4WxaTp+PhcXSsNkfX5Uapxqhq3aIRraN6Y6UAGOmkMGtq3VY hM/bmTZxJGZu9LAn8z7Ki9D1VVFIduBuBwD9DLouw1tMWHTBTZwUYPI2buE/UGiIuqDgG9F6U vOAS/G4e85kkxDol8yglxmAJT2zXsOzZT5lrqmgapRb/i9R0EG2Wk28JNs74gVa4RCm30PN1w 87ULk47GNIpRgKPYAGm+xydbnv3GqDi4t0bONkV0HWt4hLYHuNlnXVj+FsGkA6updPgH0k1Lj WkNYHeRa23p1cup0LBMnk0QKXavRd4YzVVaiHyOp28A04ixjeVAkcLvybzrInHYxK9l5WLaCk UuRiHqyIJUV88uk4zj0t6kuAfI5mWr4NgYP0nip+vSy8F8BL3dvHywqZp6o3DXUJk8mSR1UZc Jj1dPe1jxMBkivdK2pod15qxUNFOQ+qSri+aW6AZwQtjJMMDUROtwkhB2JHaXnh1gKRg+TDke fNIKgg9gfFSdH4ZG5wusubQt8wA5/O8xj6DGUyn+xOsFJxcaQYJQV8Hi7kva42ODsSUQSLgSz 5om1qlTD/UpdQlXeNRhZ425tWC58EOH2CEbBjrguPktilo1NmFkMTDTnifd6BKau6un57lLh9 U4aqKdgAHAb68ld38yKUDtdxmBmtohgGZ8y8SNzVI25GvqEwHfPq4Eyx05o= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 18:58:30 -0000 On Mon, 8 Jan 2018 09:57:56 +0100, Matthias Apitz wrote: > El día lunes, enero 08, 2018 a las 09:22:34a. m. +0100, Kristof Provost escribió: > > > They have been aware of the problem for 6+ months. FreeBSD was notified > > in late December. It’s being worked on, but these are non-trivial > > changes, so it’ll take some time. > > As I side note, and not related to FreeBSD: My Internet server is run by > some webhosting company (www.1blu.de), they use Ubuntu servers and since > yesterday they have shutdown SSH access to the servers argumenting that they want > protect my (all's) servers against attacks of Meltdown and Spectre. > > Imagine, next time we have to shutdown all IOT gadgets... Additionally, prepare for your bills to increase. The current mitigation concepts, as far as I understand, result in a lower performance (about 20 %) of the patched (!) systems. So when you heavily rely on cloud infrastructures, and you have the magical "[x] upgrade my plan if justified by increased load" enabled, well... When things start costing money, you know who'll always pay... ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Mon Jan 8 21:11:34 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1AEA8E628BA for ; Mon, 8 Jan 2018 21:11:34 +0000 (UTC) (envelope-from adelaide.martin265@topper.wku.edu) Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02hn0244.outbound.protection.outlook.com [104.47.37.244]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B83BA74FEE for ; Mon, 8 Jan 2018 21:11:33 +0000 (UTC) (envelope-from adelaide.martin265@topper.wku.edu) Received: from BN6PR03MB2546.namprd03.prod.outlook.com (10.173.142.149) by BN6SPR00MB251.namprd03.prod.outlook.com (10.168.230.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.386.7; Mon, 8 Jan 2018 21:11:22 +0000 Received: from BN6PR03MB2546.namprd03.prod.outlook.com ([10.173.142.149]) by BN6PR03MB2546.namprd03.prod.outlook.com ([10.173.142.149]) with mapi id 15.20.0386.008; Mon, 8 Jan 2018 21:11:22 +0000 From: "Martin, Adelaide, M" Subject: Project Thread-Topic: Project Thread-Index: AdOIxTxpdGx0r/whrk6N/3wvEB+apg== Date: Mon, 8 Jan 2018 21:11:22 +0000 Message-ID: Reply-To: "kwg009@outlook.kr" Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=adelaide.martin265@topper.wku.edu; x-originating-ip: [105.112.47.58] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; BN6SPR00MB251; 7:z89GdXSbmAMQHn6jobZjrc+Hy1uPPDihkrNmqF+bLPAQzgX03508or9h5oF4K9JKGaJVsMj1g9DjExINGPX1KRcocVNbSuI6cBVNPIdD01XNw7+73+v0vfu9l1yxyN4wvOB7sk4bxVleFEb/Db0FL+wA8CzJn94oXfqwSVSnDwLgK5n/uMdNGhitznLuL80HKJF2i7dmcMXgQYWapPMdolenrFuZhJjMUZgICia1LHFPtxs3BWIc++u4N8Dfb7Wv; 20:JIrpgUDq1oY9sMztVNyrsBnJacsaEysBp9nO1s/FSTInSHo6TlDaDNl8OWFf/WxBgqFqMwirWuR/8T8g0VO8hyxtbofMh75uh2eJCT28aRATtrZq8TWpm8tQaklAgznpcF16dijKasKWIMMTn3Na5jfoDJfydbeJp9n2PYPXv29FWUWQqMGPX0zr4ztavgPBTZcOJomcrqm0jEIxX20CQj/ORPMdmEeWygvwu3Ft6JzGZpjUOc8RgUyvTC+7gbH3 x-ms-office365-filtering-correlation-id: 32c6f258-f392-4ab7-1d1b-08d556dc5ef6 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(4534020)(4602075)(7168020)(4627115)(8989060)(201703031133081)(201702281549075)(8990040)(5600026)(4604075)(3008032)(2017052603307)(7167020)(7153060)(7193020); SRVR:BN6SPR00MB251; x-ms-traffictypediagnostic: BN6SPR00MB251:|BN6SPR00MB251: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(21748063052155); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040470)(2401047)(5005006)(8121501046)(10201501046)(3231023)(11241501184)(1211011)(944501075)(3002001)(93006095)(93001095)(6041268)(20161123560045)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123562045)(20161123564045)(6072148)(201708071742011); SRVR:BN6SPR00MB251; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:BN6SPR00MB251; x-forefront-prvs: 054642504A x-forefront-antispam-report: SFV:SPM; SFS:(10019020)(346002)(396003)(366004)(39380400002)(39860400002)(376002)(189003)(199004)(7406005)(54896002)(8676002)(42882006)(81156014)(8666007)(6306002)(81166006)(7366002)(9686003)(105586002)(106356001)(77096006)(33656002)(7416002)(6436002)(7736002)(53936002)(7336002)(88552002)(7276002)(74316002)(14454004)(102836004)(558084003)(109986005)(2860700003)(55016002)(5660300001)(66066001)(2900100001)(68736007)(7116003)(588024002)(221733001)(3846002)(790700001)(6116002)(3480700004)(478600001)(3660700001)(25786009)(8936002)(2906002)(8796002)(4270600006)(1240700005)(86362001)(8656006)(55236004)(6506007)(3280700002)(7696005)(65686004)(97736004)(786003)(1671002)(316002)(881003)(43066004)(99286004)(75432002)(9050700008); DIR:OUT; SFP:1501; SCL:5; SRVR:BN6SPR00MB251; H:BN6PR03MB2546.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:0; received-spf: None (protection.outlook.com: topper.wku.edu does not designate permitted sender hosts) x-microsoft-antispam-message-info: AdfC9DutrfJeyXvwo0JxpXWVZqwKreRtCe3h/FWfxg5ETpfNdseNEzJwWqRDjAtxcl8xM3Xg/FsOU1nOP5RTVg== spamdiagnosticoutput: 1:22 MIME-Version: 1.0 X-OriginatorOrg: topper.wku.edu X-MS-Exchange-CrossTenant-Network-Message-Id: 32c6f258-f392-4ab7-1d1b-08d556dc5ef6 X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Jan 2018 21:11:22.7524 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 31e7bcf2-fad8-476c-8a24-4e5f33315cfb X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6SPR00MB251 X-Mailman-Approved-At: Mon, 08 Jan 2018 21:21:25 +0000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 21:11:34 -0000 Help me in a project. From owner-freebsd-questions@freebsd.org Mon Jan 8 22:46:56 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C3654E68229 for ; Mon, 8 Jan 2018 22:46:56 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5890E79407 for ; Mon, 8 Jan 2018 22:46:55 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from crayon2.yoonka.com (crayon2.yoonka.com [10.70.7.20]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id w08MkkP1087899 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Mon, 8 Jan 2018 22:46:46 GMT (envelope-from list1@gjunka.com) To: freebsd-questions@freebsd.org From: Grzegorz Junka Subject: NVMe ZFS mount Message-ID: <3f89d154-d878-a267-66a5-e898cc2621f5@gjunka.com> Date: Mon, 8 Jan 2018 22:46:46 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 22:46:56 -0000 Hi, I've two zfs mirrors, one on two SATA drives and one on two NVMe drives. SATA are used to boot the system. I observed that after booting the system zfs datasets on NVMe drives aren't mounted. The pool is imported and I can list the datasets but command mount doesn't show any mounts apart from the system (SATA) drives. Do ZFS datasets on NVMe need any special treatment to be mounted by the system automatically, e.g. an entry in /etc/fstab? Thanks GrzegorzJ From owner-freebsd-questions@freebsd.org Mon Jan 8 22:47:49 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 93D73E683B3 for ; Mon, 8 Jan 2018 22:47:49 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.227]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 604AC79501 for ; Mon, 8 Jan 2018 22:47:48 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from raspberrypi.bildanet.com ([65.186.67.174]) by cmsmtp with ESMTP id Yg8veJpyPU2piYg8yemPLX; Mon, 08 Jan 2018 22:43:48 +0000 Received: from [192.168.1.143] by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1eYgCl-00016o-FU for freebsd-questions@freebsd.org; Mon, 08 Jan 2018 22:47:43 +0000 Subject: =?UTF-8?Q?Re:_Meltdown_=e2=80=93_Spectre?= To: FreeBSD Mailing List References: <018343d5-f5f0-8bbe-f8e1-e80a6853f7ab@sentex.net> From: Baho Utot Message-ID: <932b4c90-672c-985c-f7c0-aae14e32c24f@columbus.rr.com> Date: Mon, 8 Jan 2018 17:47:39 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <018343d5-f5f0-8bbe-f8e1-e80a6853f7ab@sentex.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfNRkmKsivJ/+XTol+GdSmba6Vz92rvwPz5KCM9h7oT17IAJIDtc94u8RcyYYVg/a1lcmJCiB7lyGfO3EkXGOV+49BVTDSFQ9unCRq5BSCIwOjj5JSH+x F2Dd5g5d1/O/fAwNnESFb3Eg/vrb+WLcCuKB5rLval0hePNGgS05g88k5ECTroO8sanso7Tx7CJe5ncX9rjtcfesUFoQ25MaNO0= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 22:47:49 -0000 On 1/8/2018 1:17 PM, Mike Tancsa wrote: > On 1/7/2018 9:05 PM, Baho Utot wrote: >> What is freeBSD doing for these attacks? > > Latest updates at > > https://lists.freebsd.org/pipermail/freebsd-security/2018-January/009719.html > > ---Mike > > > Well, well, kinda says what I got all the shit for. From owner-freebsd-questions@freebsd.org Mon Jan 8 22:58:47 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C3F9E693BA for ; Mon, 8 Jan 2018 22:58:47 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::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 5CD5B79C11 for ; Mon, 8 Jan 2018 22:58:47 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: by mail-vk0-x229.google.com with SMTP id k132so8335476vke.10 for ; Mon, 08 Jan 2018 14:58:47 -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=92l5xxLUgONvc3+jFk6HmoprPbz0E6rIHM4Rhy+5GAA=; b=qriNhfSXQaTqMcRTNHUXPGd3C96bywYHatB1CrNIg4XEI4mOJDXoG5yIiFK48FeMTt 27lMGa5GjMWdJQ5+mDKywQsn95bMsCLgMHVFZQSzcT/6hRF/kGCk9ARYIlDh28riZ0Ty XywYGbdNxJSd2E8Cg6vzSHF3OjLrI9/+N7PHeC5BUnkrt6VWOlXyikhIXRgXKGO9N/dj /lspUZNaRvBTIQv5RPUATOvyixGXY4LcJHTAd1au1GWFqFdgB8GLhKygqAhcBwk/tRK4 ksuSDtg3QBVu7THFVRKBeAfPJiRyRNOd3ptLyq/a+fwhDVQcUUfmQxmFRCM7VqbOy2je IqeQ== 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=92l5xxLUgONvc3+jFk6HmoprPbz0E6rIHM4Rhy+5GAA=; b=VxYQyJNJ9G0ky2P4KfYP/n4mNbcGI6ah9u+cc7CLGzQmWH/fquTohpioN7sFdCJzDb 38HRHSrzIk/+vzgDpxuosIsff/lvSBPV30zey4XE9yJJ+hG2eX0ABB7JG/0tXALrOQlr 1sfIJxfNCnOzMJj86CZTetl3nfzq3F8NP04Yl/d12Clt14q2GvSBCstfc54xcpFjP9SX RQfAxZmwQQ3p1hNnTYLvklNAAXmvn1Y/2gQ6lhf71TrldFGDJYaF73nry2QVwimyBb8+ zI6uw8Cdi3RuUDPQKdkQTk2xWd7ceGiKUduyfe63PKlyJ0karsjsd63GSCEA3EnQ1HQC oVOg== X-Gm-Message-State: AKwxyte1iZDz5NpJcOVPJwpAvMA63TjiUCdHNGB9P61kjppxYvNCSrWo xA2XRkfQl+GS8De7Fdb31SFmDj7W7AySOJpQjWpp9w== X-Google-Smtp-Source: ACJfBouS6w8gNnUO6oJgDhR7I9Lkg9+zXOtJw/nIV6uaYWVHlm6zHtAFX1xzVj00epx6/q644KZ0lX9OYdehi5v1joM= X-Received: by 10.31.181.198 with SMTP id e189mr11736768vkf.122.1515452326165; Mon, 08 Jan 2018 14:58:46 -0800 (PST) MIME-Version: 1.0 References: <3f89d154-d878-a267-66a5-e898cc2621f5@gjunka.com> In-Reply-To: <3f89d154-d878-a267-66a5-e898cc2621f5@gjunka.com> From: Ben Woods Date: Mon, 08 Jan 2018 22:58:35 +0000 Message-ID: Subject: Re: NVMe ZFS mount To: Grzegorz Junka Cc: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 22:58:47 -0000 On Tue, 9 Jan 2018 at 6:47 am, Grzegorz Junka wrote: > Hi, > > I've two zfs mirrors, one on two SATA drives and one on two NVMe drives. > SATA are used to boot the system. I observed that after booting the > system zfs datasets on NVMe drives aren't mounted. The pool is imported > and I can list the datasets but command mount doesn't show any mounts > apart from the system (SATA) drives. > > Do ZFS datasets on NVMe need any special treatment to be mounted by the > system automatically, e.g. an entry in /etc/fstab? > > Thanks > > GrzegorzJ > I don=E2=80=99t believe NVMe needs any special treatment, but I haven=E2=80= =99t used it. What about the boot order... when you watch it boot, do the NVMe devices show up before the /etc/rc.d/zfs script is run? Check the =E2=80=9Ccanmount=E2=80=9D parameter of each of your datasets. zfs get -r canmount,mountpoint,mounted nvmepool Regards, Ben --=20 -- From: Benjamin Woods woodsb02@gmail.com From owner-freebsd-questions@freebsd.org Tue Jan 9 00:20:39 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7BFA8E6E286 for ; Tue, 9 Jan 2018 00:20:39 +0000 (UTC) (envelope-from ralf.mardorf@rocketmail.com) Received: from sonic305-21.consmr.mail.ir2.yahoo.com (sonic305-21.consmr.mail.ir2.yahoo.com [77.238.177.83]) (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 1C1737CE2E for ; Tue, 9 Jan 2018 00:20:38 +0000 (UTC) (envelope-from ralf.mardorf@rocketmail.com) X-YMail-OSG: 0fKvg_kVM1kU25vqpVax4JHkk7WlbPrXNFU2_7PdaczYKxRd_bGmuJqvIogn89Z kyDYKofpnARaMdP0MJFsy0TfQkfvhjdfk6vFuMnwltMGRqKBi3fs6X8.fv54sLhTCf3DV7xGHfiP EvVvn9W_5Bhd0ZVP1AtILDclpYxd5539Ha_zLdd9fxJsR8Ijbqgs8XD_VhZDf0RENizyNJ2BrYWj UtR992Emqvz5W0gpLG1j9Bb9vStqmOtOTrTQMOLQ1MbzN10WPFfMrTv8U7eqcL2bkma1TDNFsqW7 7eeuQIGWxthpkzFUkn.W7vnLQIrhjsu9.KKecOPl5Xm2LVTxNR0YEWJp4yWyBwALdlvlFWIh53PL 3JMoHoKwHALs6jY0Pi_1Ppl.s1Y5BgzbAThp1.fNkPQS8EbG_rBqmBnZ.XBTpH4qdHy_ryzhyN8s TJ8yMrvN8LM56Ltcia69pJmWyM95.hjqEniZK3JAe.BiXwD_v3.wKnSBkElqdJwfnJZ.16B3C5UL OlBGppyG.JS7xpXdkYOi265.m7sKWrFE7EvuUjA-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic305.consmr.mail.ir2.yahoo.com with HTTP; Tue, 9 Jan 2018 00:20:30 +0000 Received: from smtp169.mail.ir2.yahoo.com (EHLO archlinux.localdomain) ([46.228.39.36]) by smtp414.mail.ir2.yahoo.com (JAMES SMTP Server ) with ESMTPA ID f9eb53a83d79643efc3016402fbbf5cc; Tue, 09 Jan 2018 00:20:27 +0000 (UTC) Date: Tue, 9 Jan 2018 01:20:28 +0100 From: Ralf Mardorf To: freebsd-questions@freebsd.org Cc: Polytropon Subject: Re: Meltdown =?UTF-8?B?4oCT?= Spectre Message-ID: <20180109012028.6e9a2471@archlinux.localdomain> In-Reply-To: <20180108195821.0195794b.freebsd@edvax.de> References: <3AECDC7F-8838-4C09-AC7F-117DFBAA326C@sigsegv.be> <20180108085756.GA3001@c720-r314251> <20180108195821.0195794b.freebsd@edvax.de> X-Mailer: Claws Mail 3.16.0git3 (GTK+ 2.24.31; x86_64-arch-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2018 00:20:39 -0000 On Mon, 8 Jan 2018 19:58:21 +0100, Polytropon wrote: >On Mon, 8 Jan 2018 09:57:56 +0100, Matthias Apitz wrote: >> El d=C3=ADa lunes, enero 08, 2018 a las 09:22:34a. m. +0100, Kristof >> Provost escribi=C3=B3:=20 >> > They have been aware of the problem for 6+ months. FreeBSD was >> > notified in late December. It=E2=80=99s being worked on, but these are >> > non-trivial changes, so it=E2=80=99ll take some time. =20 >>=20 >> As I side note, and not related to FreeBSD: My Internet server is >> run by some webhosting company (www.1blu.de), they use Ubuntu >> servers and since yesterday they have shutdown SSH access to the >> servers argumenting that they want protect my (all's) servers >> against attacks of Meltdown and Spectre. >>=20 >> Imagine, next time we have to shutdown all IOT gadgets... =20 > >Additionally, prepare for your bills to increase. The current >mitigation concepts, as far as I understand, result in a lower >performance (about 20 %) of the patched (!) systems. So when >you heavily rely on cloud infrastructures, and you have the >magical "[x] upgrade my plan if justified by increased load" >enabled, well... When things start costing money, you know >who'll always pay... ;-) "KPTI comes with a measurable run-time cost, estimated at about 5%. That is a cost that some users may not want to pay, especially once they get newer processors that lack these problems. There will be a nopti command-line option to disable this mechanism at boot time." - https://lwn.net/Articles/741878/ So for my audio workstation I much likely will boot with nopti and the mentioned Ubuntu server seemingly slows down for around 5% and not around 20% ;). Regards, Ralf --=20 $ pacman -Q linux{,-rt{,-cornflower,-pussytoes}}|awk '{print $2}' 4.14.12-1 4.14.6_rt7-1 4.11.12_rt16-1 4.14.8_rt9-2 From owner-freebsd-questions@freebsd.org Tue Jan 9 11:04:42 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9ABEFE766A9 for ; Tue, 9 Jan 2018 11:04:42 +0000 (UTC) (envelope-from louis@weboptimizes.com) Received: from mail-wr0-x242.google.com (mail-wr0-x242.google.com [IPv6:2a00:1450:400c:c0c::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3051177174 for ; Tue, 9 Jan 2018 11:04:41 +0000 (UTC) (envelope-from louis@weboptimizes.com) Received: by mail-wr0-x242.google.com with SMTP id n9so3825611wrg.2 for ; Tue, 09 Jan 2018 03:04:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=weboptimizes.com; s=google; h=mime-version:sender:from:date:message-id:subject:to; bh=sIxp3GvZZPL+7/dox0LUeTrZ7TBTDwBaIDAt6wvHVKk=; b=EaovTjD7LLeU5OTx52fIFJAWIDPaOlVuYM0EhFgUFVTNUyZPMFV4Dosuc860VsP0tK PryEZxUpZT9HzhATu4Mdz2GrMWqVEr9WHutj8wLBgN93uTbB8Z6KaQkPMxTMvLXuFp9O 9Dcc6qO+ZqnKWUbX4WiKCfIOHQDO8A7GMD9SU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=sIxp3GvZZPL+7/dox0LUeTrZ7TBTDwBaIDAt6wvHVKk=; b=Hn4LW4DBSZ1RehFwyOv44ehTI5cV0qPOiix5n+cXeaSdARC7TuN/sd9cY5uwsB6Va4 ryNMw5F4tlCOx5sC04oo4fkdW0pOBA0Np8f7nV56kRO2M2ocbWAc84mUvLqvqlOykDui j6MHpxLHzYRFV0KfWvPiZ0Wnx9QeQBBPPPttR5AAGM1xOJYC31AkWrouKavBzwvnbHPm WBdH75+mzk0qjauc6XrQVuPJ8vm3OaQxcKARMnwHuVltadabcBzzMzFo9ZjuRdsm0QPi lE8m+hewCKM5BkYYfkMccBycqDUZKLxS0ScsMP3wf1RBdhZOawuOUSOQytGoOxLASSfD F3vg== X-Gm-Message-State: AKGB3mLlmhXS4detKCCpHi9jaz+3Ws0SmOKvQ3Rf9vmrjNgW57PxdNK7 XruTbQW6xkWEhKYmYHVsTPUP55pZ2y4knx5C2TAn2M7Z X-Google-Smtp-Source: ACJfBotMlh3z8yJl8CXXngOXKJXDiTF3ZWBT4DZ6nTsFAQVjB1i44po9aKf07nw66QV/5FzvyTh9FSLSglM1YtBrlrA= X-Received: by 10.223.171.131 with SMTP id s3mr3919012wrc.160.1515495879976; Tue, 09 Jan 2018 03:04:39 -0800 (PST) Received: from 52669349336 named unknown by gmailapi.google.com with HTTPREST; Tue, 9 Jan 2018 12:04:39 +0100 MIME-Version: 1.0 Sender: Louis Parker From: Louis Parker Date: Tue, 9 Jan 2018 12:04:39 +0100 X-Google-Sender-Auth: pCx6O3ImMl4nIEzIa6NJX4qfaco Message-ID: Subject: What has happened to your freebsd.org? To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2018 11:04:42 -0000 Hello Team, *Get your website on Google=E2=80=99s front Page search: * We would like to have a discussion with you regarding the web promotion strategy for your website. We wish to work out a proposal to strengthen the online presence of your website, via, a strategically planned web promotion campaign. In today=E2=80=99s online era, you should be focusing on the new revolutionary ways of generating traffic. We are curious to know if you were are that are a few issues bugging your website. Sorting out these will help you get the best returns out of your website. - Your website seems to be attracting traffic, but this traffic is almost stagnant and limited, which affects potential sales as you move forward. - - Your website doesn't feature in Google's first search page for some of the major keywords in your niche, which affects visibility. - - Your website has been diagnosed with coding issues, which affects ranking. - - Your back links profile is not efficient enough to help your search engine visibility. - - Your website is currently not being properly promoted online, which is affecting your marketing strategy and goals - - Your presence on social media platforms, such as (*Facebook, Twitter, etc.*) is minimal. which is depriving you of a huge market of prospective referral clients. I also prepared a* free website audit report* for your website.If you are *interested* i can show you the report. I'd be happy to send you our package, pricing and past work details, if you'd like to assess our work. Hope to Hear back from you soon. Best Regards, *Louis Parker | Senior Sales Advisor* [image: beacon] From owner-freebsd-questions@freebsd.org Tue Jan 9 12:23:59 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F294E7AC0D for ; Tue, 9 Jan 2018 12:23:59 +0000 (UTC) (envelope-from g8kbvdave@googlemail.com) Received: from mail-wr0-x22e.google.com (mail-wr0-x22e.google.com [IPv6:2a00:1450:400c:c0c::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 B87347A2C4 for ; Tue, 9 Jan 2018 12:23:58 +0000 (UTC) (envelope-from g8kbvdave@googlemail.com) Received: by mail-wr0-x22e.google.com with SMTP id z48so8183736wrz.6 for ; Tue, 09 Jan 2018 04:23:58 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=Dn/kUOjboWiK8EJTIyhJ8ojbYiDjd6jiTf/7p3jIZo8=; b=qnXz+JBRNSe39RWGNojB4YENeRFYq8l7ycn2yFO4784Ztcw0apQVRfViZN2VXn9ZDQ c4fQopim20VahLsESx4MY4vW2JrBanXqNPgWb8kKT6cNPYyKZvgwKWuXr0ACM/U1Z89y mV5t7F3aF+mizk1TYXmm0NflF/QisSaZNgJAq6wFe6ukYY+zpmoV8jDC/1qZl9Zo8+41 3/GMNVQfJh+BDRarbb04LuhQPxMe7omk3c+PjlckyzY835Y1Li6Q20P6fjkY+90RN017 cwehRb8GbBBn034E6OACiq+dIWe/B3MTg707rCY1NAyNCXSPzFaAgQVMb5cJNkBtfGNB tdVw== X-Gm-Message-State: AKGB3mJPxXMZ7+GvOycv50XTbRWDRldTOAxmv9Ddxv+J0EMeIQgcu/Aq 0smWIOUEIDxerZTDRzfL4g90xATg X-Google-Smtp-Source: ACJfBosqzqEKfwhhudKzY1J/NZGDXeBZGtoL25vp6pbt5saX4aLwljedkxlxibfZ1zcYij6CF2DoHw== X-Received: by 10.223.134.219 with SMTP id 27mr14372835wry.227.1515500636700; Tue, 09 Jan 2018 04:23:56 -0800 (PST) Received: from [192.168.2.55] ([217.41.35.220]) by smtp.gmail.com with ESMTPSA id p132sm16996085wmb.0.2018.01.09.04.23.55 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 Jan 2018 04:23:56 -0800 (PST) Subject: =?UTF-8?Q?32_bit_fix=3f_=28Was_Re:_Meltdown_=e2=80=93_Spectre=29?= To: freebsd-questions@freebsd.org References: From: Dave B Message-ID: <2e86bfd9-9141-2872-1946-0e9d26326433@googlemail.com> Date: Tue, 9 Jan 2018 12:23:55 +0000 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-GB Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2018 12:23:59 -0000 When is a patch for i386 (32 bit) versions likely to be available? Regards. Dave B. (I only run non GUI 32 bit instances of FreeBSD, on older hardware, GPSD NTP machines etc.) On 09/01/18 12:00, freebsd-questions-request@freebsd.org wrote: > Subject: > Re: Meltdown Spectre > From: > Mike Tancsa > Date: > 08/01/18 18:17 > > To: > Baho Utot , FreeBSD Mailing List > > > > On 1/7/2018 9:05 PM, Baho Utot wrote: >> What is freeBSD doing for these attacks? > Latest updates at > > https://lists.freebsd.org/pipermail/freebsd-security/2018-January/009719.html > > ---Mike From owner-freebsd-questions@freebsd.org Tue Jan 9 14:47:11 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 28914E9A83E for ; Tue, 9 Jan 2018 14:47:11 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from inet08.hamilton.harte-lyne.ca (inet08.hamilton.harte-lyne.ca [216.185.71.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "inet08.hamilton.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F36F97F84B for ; Tue, 9 Jan 2018 14:47:10 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from localhost (localhost [127.0.0.1]) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTP id 8A62B6229E for ; Tue, 9 Jan 2018 09:38:13 -0500 (EST) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from inet08.hamilton.harte-lyne.ca ([127.0.0.1]) by localhost (inet08.hamilton.harte-lyne.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DJdDWtCY55pe for ; Tue, 9 Jan 2018 09:38:11 -0500 (EST) Received: from webmail.harte-lyne.ca (inet04.hamilton.harte-lyne.ca [216.185.71.24]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTPSA id 679A860FEE for ; Tue, 9 Jan 2018 09:38:11 -0500 (EST) Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Tue, 9 Jan 2018 09:38:11 -0500 Message-ID: <3037cb3560fe970cdfb789a265faf21b.squirrel@webmail.harte-lyne.ca> Date: Tue, 9 Jan 2018 09:38:11 -0500 Subject: Re: Meltdown =?iso-8859-1?Q?=96_Spectre?= From: "James B. Byrne" To: freebsd-questions@freebsd.org Reply-To: byrnejb@harte-lyne.ca User-Agent: SquirrelMail/1.4.22-5.el6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2018 14:47:11 -0000 I have read some accounts which seem to imply that the rate of ssh attacks measurably increased following the announcement of these two flaws. The implication being that there was some cause and effect relationship. I cannot fathom what this could be. I do not wish to exist in a state of blissful ignorance. But, neither do I wish to overestimate the degree of threat these two flaws present to our operations. >From what I have read the impression I obtain is that both of these two security flaws require that unaudited software be allowed to run on the affected hosts. If one is running a private data centre, and if only authorized software is permitted to run therein, then how much of a threat does this development pose to such? It seems to me that public 'cloud' environments is where this sort of stuff would find its most vulnerable targets. Private data systems are no more likely to succumb to attacks along this vector than to any other routinely available rootkit. Is that a fair assessment? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 From owner-freebsd-questions@freebsd.org Tue Jan 9 15:24:47 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9F1BE5BDF0 for ; Tue, 9 Jan 2018 15:24:47 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::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 8FC93811B5 for ; Tue, 9 Jan 2018 15:24:47 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-io0-x22e.google.com with SMTP id w188so18925190iod.10 for ; Tue, 09 Jan 2018 07:24:47 -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=dhHN7dPZ9LF2hgPqS5SwnMFg9qJ3WVV5Jtqiyq9VjHw=; b=MdSq1JyXKqVqlkVVvSZm5HMLZYx6DdngvLjTNb9Dgn07fba2xMZlyfDOGgdogXnQpE hhRPajLUMUT6zr8nlKIRTpAqE07t3hUPrDCjI8ugrWhqzmdNRoPSjhhp4/jCxSdeL54/ Z4qp6SG0GtTU5EASIxmecm1tANivdSFVfW5VzMzCy3UzJxyjuR+Fn4LuajM+k2l3Gye4 U9c2ps65S7SfwkTW35zLQi7kJEFvzIoiF5d5IH6WOXjABo1x2XJlZ+40KeBlZEmCUwm4 vyhdWDhfgYRNHIghDqYKoH60rr8SAPQSZV19L+4/RGBu7OH5PE2d6mV85fIZeJXT5YQG RkMg== 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=dhHN7dPZ9LF2hgPqS5SwnMFg9qJ3WVV5Jtqiyq9VjHw=; b=kRRWnfMqTm3sZpJyiPygDLLJLySoi7OrAjRYwZga7oZnJ9k4bopG1N+S4HzNm4voHz ImDBZ8MiB4b/eBS7KfcPklDPNerdc1hbf7R/N1XRwzMaB8QKJgGHLby9qsriqb+kwA9G xPM3zlRBOMkAO8soQ2FI/T3zTZGm++N/QDtt9FvhUik1XvsE1Dj2edmDOd1rn33XNNbc 0jAYOEMZqgs+49soVNL+w0NhJRdqma4n6/HdJkcyxAdAypltO/OIqZoZ6mibtDBvgBLA TaLRkTlLXJK+rt2f6yzUSJqvNh9RCX2KpnyV0w7ofdcrFzHIvSechxeHyl9HPZZxMLge FtAQ== X-Gm-Message-State: AKwxytd7vmUpAyQarwF+HuM7pTq2UtCKlGNZ4gauTLUKOMQjXVjTr+UY TU4rmlikuIKQZ1U/lLhWDiLUvTvBni+rL26J6Es= X-Google-Smtp-Source: ACJfBotTtir7wUd1/JpRPA5g6ug6OktrR5Epd/tXVy3Ipg66X04HVCLmdHlri6uFa7y4RES8vAzGmGvIPtkoQajcdSE= X-Received: by 10.107.35.145 with SMTP id j139mr16686607ioj.153.1515511486626; Tue, 09 Jan 2018 07:24:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.203 with HTTP; Tue, 9 Jan 2018 07:24:45 -0800 (PST) In-Reply-To: <3037cb3560fe970cdfb789a265faf21b.squirrel@webmail.harte-lyne.ca> References: <3037cb3560fe970cdfb789a265faf21b.squirrel@webmail.harte-lyne.ca> From: blubee blubeeme Date: Tue, 9 Jan 2018 23:24:45 +0800 Message-ID: Subject: =?UTF-8?B?UmU6IE1lbHRkb3duIOKAkyBTcGVjdHJl?= To: byrnejb@harte-lyne.ca Cc: FreeBSD Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2018 15:24:47 -0000 On Tue, Jan 9, 2018 at 10:38 PM, James B. Byrne via freebsd-questions < freebsd-questions@freebsd.org> wrote: > I have read some accounts which seem to imply that the rate of ssh > attacks measurably increased following the announcement of these two > flaws. The implication being that there was some cause and effect > relationship. I cannot fathom what this could be. > > I do not wish to exist in a state of blissful ignorance. But, neither > do I wish to overestimate the degree of threat these two flaws present > to our operations. > > From what I have read the impression I obtain is that both of these > two security flaws require that unaudited software be allowed to run > on the affected hosts. If one is running a private data centre, and > if only authorized software is permitted to run therein, then how much > of a threat does this development pose to such? > > It seems to me that public 'cloud' environments is where this sort of > stuff would find its most vulnerable targets. Private data systems > are no more likely to succumb to attacks along this vector than to any > other routinely available rootkit. Is that a fair assessment? > > > -- > *** e-Mail is NOT a SECURE channel *** > Do NOT transmit sensitive data via e-Mail > Do NOT open attachments nor follow links sent by e-Mail > > James B. Byrne mailto:ByrneJB@Harte-Lyne.ca > Harte & Lyne Limited http://www.harte-lyne.ca > 9 Brockley Drive vox: +1 905 561 1241 > Hamilton, Ontario fax: +1 905 561 0757 > Canada L8E 3C3 > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions- > unsubscribe@freebsd.org" > There was a rowhammer bug that made big news in 2016 https://arstechnica.com/information-technology/2016/10/using-rowhammer-bitflips-to-root-android-phones-is-now-a-thing/ There's a paper, github repo with code and I doubt that those bugs have been patched even up to this day. I think it was around this time when Google started looking into this and a bit later when they discovered the CPU architecture vulnerabilities that they tried to keep under wraps until it was patched. If u saw how big that botnet got, you'll understand the value that shady people can extract from these types of exploits. Right now we're just waiting, my opinion on the matter is that this is just too good for shady teams not to try to exploit. Those patches will be mercilessly attacked because the pot of gold is just too large. Not only that what about users who say, I just cannot accept up to %30 decrease in performance so they actively try to remove the patches? You do not need unauthorized software, any software running on your system can exploit you. A webpage with Javascript could trigger rowhammer exploit: https://motherboard.vice.com/en_us/article/9akpwz/rowhammerjs-is-the-most-ingenious-hack-ive-ever-seen That means a website with javascript can conjure up Spectre or Meltdown. Being scared won't help, but I can't wait to see how atrocious this thing becomes. Cheer up, it's like that comic where the dog is sitting in the burning house drinking coffee, "it's fine" https://cdn.vox-cdn.com/thumbor/2q97YCXcLOlkoR2jKKEMQ-wkG9k=/0x0:900x500/1200x800/filters:focal(378x178:522x322)/cdn.vox-cdn.com/uploads/chorus_image/image/49493993/this-is-fine.0.jpg From owner-freebsd-questions@freebsd.org Tue Jan 9 15:25:28 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 461E3E5BEC6 for ; Tue, 9 Jan 2018 15:25:28 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [IPv6:2607:f3e0:80:80::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 13D44812CC for ; Tue, 9 Jan 2018 15:25:27 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (lava.sentex.ca [IPv6:2607:f3e0:0:5::11]) by smarthost2.sentex.ca (8.15.2/8.15.2) with ESMTPS id w09FPQHN063564 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Tue, 9 Jan 2018 10:25:26 -0500 (EST) (envelope-from mike@sentex.net) Received: from [192.168.43.26] (saphire3.sentex.ca [192.168.43.26]) by lava.sentex.ca (8.15.2/8.15.2) with ESMTP id w09FPOeb059855; Tue, 9 Jan 2018 10:25:24 -0500 (EST) (envelope-from mike@sentex.net) Subject: =?UTF-8?Q?Re:_Meltdown_=e2=80=93_Spectre?= To: byrnejb@harte-lyne.ca, freebsd-questions@freebsd.org References: <3037cb3560fe970cdfb789a265faf21b.squirrel@webmail.harte-lyne.ca> From: Mike Tancsa Organization: Sentex Communications Message-ID: Date: Tue, 9 Jan 2018 10:25:23 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <3037cb3560fe970cdfb789a265faf21b.squirrel@webmail.harte-lyne.ca> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.78 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2018 15:25:28 -0000 On 1/9/2018 9:38 AM, James B. Byrne via freebsd-questions wrote: > I have read some accounts which seem to imply that the rate of ssh > attacks measurably increased following the announcement of these two > flaws. The implication being that there was some cause and effect > relationship. I cannot fathom what this could be. They are up, but I suspect its the normal uptick post holidays. Here is a pretty well sampled view of scanning https://isc.sans.edu/port.html?port=22 I seem to recall similar trends in previous years. > if only authorized software is permitted to run therein, then how much > of a threat does this development pose to such? Well, its hard to say and I guess it depends who the attackers are and what their goals are. If its opportunistic bots just hammering away in brute force at your perimeter, its one thing. If its someone trying to figure out out to get access to your internal network thats another. Breaches of the later I think will often be chained. e.g. use a broken web facing app to allow the attacker to upload and execution of arbitrary code. That code then can work on exploiting other, local vulnerabilities including meltdown/spectre. In that sense, its another (serious) local priv escalation issue to worry about. > > It seems to me that public 'cloud' environments is where this sort of > stuff would find its most vulnerable targets. Private data systems > are no more likely to succumb to attacks along this vector than to any > other routinely available rootkit. Is that a fair assessment? I think what Spectre and Meltdown uniquely bring to the table are ways to attack neighbouring VMs that were previously thought to be relatively safe. A local root kit was a local root kit. With Meltdown, all the VM instances are only as safe as the weakest link on that hardware. There have been bugs in the past that allowed this type of attack, but those were relatively rare and hard to exploit (IIRC). ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-questions@freebsd.org Tue Jan 9 19:01:50 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9E472E6ACEA for ; Tue, 9 Jan 2018 19:01:50 +0000 (UTC) (envelope-from katie.sadowske@accudbpro.com) Received: from IND01-BO1-obe.outbound.protection.outlook.com (mail-bo1ind01on0054.outbound.protection.outlook.com [104.47.101.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT TLS CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EB3066B24B for ; Tue, 9 Jan 2018 19:01:49 +0000 (UTC) (envelope-from katie.sadowske@accudbpro.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=NETORGFT3485838.onmicrosoft.com; s=selector1-accudbpro-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=LwPvN9xiz1Q4L7QBCsqD/ZrzEqQuSYLCOjKHgpn8Hx4=; b=YQbXPwuHAxnWxQ/CDy1DX9u7Vie29/jER9YCg6cloauYIz7015YHiqzFzRN+fu/5T843qhh3AmXSk2ugjCE27IaQOCGYttCYmPaN7DfIvP6zuQowA0hWtd3ApvPzZuFEADNlr/MvInWR7TMfyaSz91sI0qIQyqZJ6441pssT+Hc= Received: from MA1PR0101MB1815.INDPRD01.PROD.OUTLOOK.COM (52.134.142.144) by MA1PR0101MB1815.INDPRD01.PROD.OUTLOOK.COM (52.134.142.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.366.8; Tue, 9 Jan 2018 19:01:46 +0000 Received: from MA1PR0101MB1815.INDPRD01.PROD.OUTLOOK.COM ([fe80::a923:569c:100:a3d8]) by MA1PR0101MB1815.INDPRD01.PROD.OUTLOOK.COM ([fe80::a923:569c:100:a3d8%15]) with mapi id 15.20.0366.011; Tue, 9 Jan 2018 19:01:46 +0000 From: Katie Sadowske To: "freebsd-questions@freebsd.org" Subject: Microsoft Azure Users List Thread-Topic: Microsoft Azure Users List Thread-Index: AdOJe9J/uc6GNfm8SRuhqgsWM85jjQ== Importance: high X-Priority: 1 Date: Tue, 9 Jan 2018 18:59:49 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=katie.sadowske@accudbpro.com; x-originating-ip: [49.207.52.153] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; MA1PR0101MB1815; 7:+u7gw8zE7CH8xeAh3P7pCfgW/8Ir8gtqDEiNGhOhz+KlUPKZ2maN+/hVxEMTPC7osngB4g/724SUFI3LGgUBEMtZeBZmO2aV4ThaYSl/vV0UTrnM9nXZ2JttQ5QF4X4mFY6wdx5n/iq2/evgbfKnYWuwl6YYmzdim0sHmF+cbceplEelWtesAc8viniGmWkYT4mMoK9zxPLp2P7pb7KIM/ZmFqG7zxXuIqdvmOq1p67ESnNl87IQwlekFJfXAYAk x-ms-office365-filtering-correlation-id: e4635531-6334-49c5-1f1c-08d557936e41 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(4534020)(4602075)(4603075)(7168020)(4627115)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:MA1PR0101MB1815; x-ms-traffictypediagnostic: MA1PR0101MB1815: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(28532068793085)(21748063052155); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040470)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(3231023)(2017060905117)(944501075)(6041268)(20161123562045)(2016111802025)(20161123564045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(6043046)(6072148)(201708071742011); SRVR:MA1PR0101MB1815; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:MA1PR0101MB1815; x-forefront-prvs: 0547116B72 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(39380400002)(366004)(39850400004)(346002)(376002)(47530400004)(199004)(189003)(2351001)(74316002)(7736002)(55016002)(2900100001)(81686011)(105586002)(6916009)(55236004)(33656002)(86362001)(97736004)(53936002)(52230400001)(54896002)(106356001)(6306002)(6506007)(7696005)(5660300001)(9686003)(5630700001)(5640700003)(2501003)(99286004)(6436002)(102836004)(66066001)(8676002)(2906002)(8936002)(478600001)(3480700004)(14454004)(68736007)(3280700002)(626008)(45080400002)(5250100002)(81166006)(3846002)(790700001)(316002)(81156014)(6116002)(3660700001)(25786009)(19870200002); DIR:OUT; SFP:1101; SCL:1; SRVR:MA1PR0101MB1815; H:MA1PR0101MB1815.INDPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: accudbpro.com does not designate permitted sender hosts) x-microsoft-antispam-message-info: FravcQyrVzrh05hGa5rECA4H+QEztWudc7kXo/HY1UEQWmePa0W5H0O/Tb9EKgZWoUis6+hTEAamAIM9LI76RQ== spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: accudbpro.com X-MS-Exchange-CrossTenant-Network-Message-Id: e4635531-6334-49c5-1f1c-08d557936e41 X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jan 2018 18:59:49.6073 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: df12b867-6ad1-4afc-9c76-84e279b5179c X-MS-Exchange-Transport-CrossTenantHeadersStamped: MA1PR0101MB1815 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2018 19:01:50 -0000 Hello Good Day, I would like to know if you are interested in acquiring Microsoft Azure Use= rs List. Information fields: Names, Title, Email, Phone, Company Name, Company URL, = Company physical address, SIC Code, Industry, Company Size (Revenue and Emp= loyee). Let me know if you are interested and I will get back to you with the count= s and price list Regards, Katie Sadowske:) Data Consultant If you don't wish to receive emails from us reply back stati= ng "REMOVE" From owner-freebsd-questions@freebsd.org Tue Jan 9 20:42:12 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C04EE71166 for ; Tue, 9 Jan 2018 20:42:12 +0000 (UTC) (envelope-from edward.holland@leadsinsights-boosters.com) Received: from mail-pf0-x22f.google.com (mail-pf0-x22f.google.com [IPv6:2607:f8b0:400e:c00::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2F6786FF3B for ; Tue, 9 Jan 2018 20:42:11 +0000 (UTC) (envelope-from edward.holland@leadsinsights-boosters.com) Received: by mail-pf0-x22f.google.com with SMTP id e3so9405334pfi.10 for ; Tue, 09 Jan 2018 12:42:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadsinsights-boosters-com.20150623.gappssmtp.com; s=20150623; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :thread-index:content-language; bh=yecBWvmQpACHiRGPryRpL2BUxSq0GTo+pTiJ1n1PVVY=; b=EIL0gzivfExFY1m7fA4StHG1B6H7tx36Dyx2rLG+QXgnrN7N+REK/3JGLCKAwoxzEO 7J1cx1VT2zbMvK+v9kJWURuVG577GMhZqaQcKJqqfThLip31dF7SGxDXdebAqvbW+nrc kezyAxsi2wAxpXVzL+4VX3OPBHwTILvQ7T8G3Ly2YXwefPH+wHuE49n6DtxGqaJSPpRt h9468f2B0+I86z7AaRRu+K3irfOzWIN9WdjOBnj5RwY3fWSVOUE5md36nZ2XxuH5ZpHr lDN66UAqS3CuvY4s5Pe/cuLmk/1itfaNc1aDZCam/UQbBPaXJ+bs2348Rf8P7fHdL8EX 1OPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=yecBWvmQpACHiRGPryRpL2BUxSq0GTo+pTiJ1n1PVVY=; b=sOqmQVHHmzOyvDUJio2C9GblfwD/beYmkqLFwEZOG4YmacpxlBCrAgG8cDZRg1i8HJ yvOSmasULuqj75/Owix5vc4OtAhlZMCOJcwaIqP1CqLsi+6EKWFBRBYokwZB9yLfHFis 9jkgmGd4hVTQ0KihvqH+ZODgGc3FtZWWoLmYSqmMOJGOOzOXL+uuu/W6lO2e8JE3JbcC 6HFLOSPeOskBR4BOp8ZjmnHGdRWMWMTxCTB0KVvK9KJrAnNxlgUVikrjpL/2a/JU7JS1 769WUBAO2Ec0cyA1RG8T6UOpa0IJQERqDu2wE+LJNxyQ+iCwtTfxd48LmKJpdVAgfND9 9OkQ== X-Gm-Message-State: AKGB3mKtDSU89sHll7WfAssSMqO056VIm5M4BloTM4DjLpgVXdOlDeyk vjQe8/aRKjA8iKtYCCmxo8EWFgyE X-Google-Smtp-Source: ACJfBovWBrsLQJ5Tw53B2Rs5S+5Nok8BGX4aix7PcdLj75kouYHgUIHisWlRb0eIJqE7/T0sbpe/7Q== X-Received: by 10.159.244.144 with SMTP id y16mr16416830plr.166.1515530531018; Tue, 09 Jan 2018 12:42:11 -0800 (PST) Received: from sunnyPC ([103.210.134.51]) by smtp.gmail.com with ESMTPSA id h13sm28907931pfi.40.2018.01.09.12.42.09 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 09 Jan 2018 12:42:10 -0800 (PST) From: "Edward Holland" To: References: In-Reply-To: Subject: RE: DistribuTECH 2018 Attendees List. Date: Tue, 9 Jan 2018 15:42:07 -0500 Message-ID: <01a201d3898a$51032890$f30979b0$@leadsinsights-boosters.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdNwLBd7vAy2D72hRAOPhZJSeHPQUAZXjhNg Content-Language: en-us Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2018 20:42:12 -0000 Hi, Hope you doing well. This follow email is to check if you had a chance to review my previous email sent which explains about our list services and others for new business prospects. Thanks for your precious time. I would really appreciate if you can reply with your questions or queries. I look forward to your response. Best Regards Ed From: Edward Holland [mailto:edward.holland@leadsinsights-boosters.com] Sent: Friday, December 08, 2017 8:55 AM To: 'freebsd-questions@freebsd.org' Subject: DistribuTECH 2018 Attendees List. Hi, Would you be interested in acquiring the DistribuTECH 2018 (DistribuTECH Annual Electric Power Transmission and Distribution Conference & Exhibition?) Attendees List for your marketing and promotion activities? When: 23 - 25 January 2018. Where: San Antonio, TX, USA. Number of attendees: 12,000 Confirmed Attendees. Attendees Lists include:- Company Name, Contact Name, Title, Address, Web Site, Phone Number, Fax Number, Verified E-mail Address, Employee Size, Revenue size, SIC Code, Industry Type, NAICS Code, E-mail verification result. Please let me know your interest, so that i could send you the pricing. Thank you and I look forward to hear from you. Regards, Edward holland Marketing Consultant Disclaimer: We have clearly mentioned the source email id, also clearly mentioned the subject line and there is no misleading information of any form. We have found your email address through our marketing efforts on the web, if you are not interested, please reply with "Remove" in the subject line and we will ensure that you do not receive any further promotional email from our end. From owner-freebsd-questions@freebsd.org Wed Jan 10 03:29:33 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C1FB7E62851 for ; Wed, 10 Jan 2018 03:29:33 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 88DDE7F92B for ; Wed, 10 Jan 2018 03:29:33 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it0-x235.google.com with SMTP id p124so7151194ite.1 for ; Tue, 09 Jan 2018 19:29:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=aeNCq3vSgqPNbeo+7aVK51tM08anUnmEk8axBw6HV4E=; b=ZfxuX3BwJl/O36T+5sA/4Z69Qup4Sw7fxKrhXSS9/CaHMbV/Yn9xFo+Z3NrVmQl4xL W3DLlHI77V44AMOWxVUTEt6P4ZG+RTQSfJhJNprvkRzxAdLxBSdfc4Smfs4bCQZcZgWq qclt4nIXCY1gCG66ilUQim6G3Dwg0DZfiN7bW6EEhTu6vr76d6VbShGDmTTKoIUfwliI 4Lq01k8TZVbW1FhYKj+bC1yuVdazhUevKUEnPmUdZt8kQ64ohXUKg3LJTlBicFGqD5nL dQXnyTqlrMHTXxNHOV0lzM3x36w9yqpBCNHTYc4k08W+Hs0JdepadWm6Tp4Qyl5XC/ci SCpw== 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=aeNCq3vSgqPNbeo+7aVK51tM08anUnmEk8axBw6HV4E=; b=tPEEBxvP3QGqfz912strt5ztqVhaprsOFYc/UZClIOg28fOsFKgq2ximLgYRtZb8xH 6LMMDindN2gdwQuQ/YSdqm6xdq5WGFrELim6R7EdP/UhhERir8COVi1+kQ1FJHDdAMa+ sLbHpzYsa53NEbLa/YDKMNf6Chlqbj7cpx9ZDm8fRMTpN2LlRJ90284mYA7t2KZyRshp tLl3/Cx+zPLUaxSk3oQ4J125kvsi7tbRnH7NyUb6M5NI0Ne1Gqse/QqPUPHbU8wlAyDc zHZiqncDXMo9T2CujCJtNe0/CD3mmQfEYZOWLa4kfk3vdZApq9127w3O6was+5IbTMaw smRw== X-Gm-Message-State: AKGB3mLb1sql4ruwBFI+lANcPxmtOTpTZ1lwz3WIuwgLFecUpxRC8mOa wdn7Z/CpamlhEh7+DCjImbIJmNbe/iS37wWYbRPN8Q== X-Google-Smtp-Source: ACJfBov2buLAH1+ezJ52GtkuhA1JiJTyw0/fJoAhuebEIaTSdfF+HA7+WooB7hzX4wYBR6W77Pwk3SKb5u6n0n5ZXTI= X-Received: by 10.36.57.8 with SMTP id l8mr16803282ita.20.1515554973037; Tue, 09 Jan 2018 19:29:33 -0800 (PST) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.131.163 with HTTP; Tue, 9 Jan 2018 19:29:12 -0800 (PST) In-Reply-To: <2e86bfd9-9141-2872-1946-0e9d26326433@googlemail.com> References: <2e86bfd9-9141-2872-1946-0e9d26326433@googlemail.com> From: Ed Maste Date: Tue, 9 Jan 2018 22:29:12 -0500 X-Google-Sender-Auth: QCIMwCxoiCf5UXNetInoAG5PnYE Message-ID: Subject: =?UTF-8?Q?Re=3A_32_bit_fix=3F_=28Was_Re=3A_Meltdown_=E2=80=93_Spectre=29?= To: Dave B Cc: FreeBSD Questions Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 03:29:33 -0000 On 9 January 2018 at 07:23, Dave B via freebsd-questions wrote: > When is a patch for i386 (32 bit) versions likely to be available? > > Regards. > > Dave B. > > (I only run non GUI 32 bit instances of FreeBSD, on older hardware, GPSD > NTP machines etc.) Similar techniques can be applied to i386, but they are a lower priority and we don't yet have a timeline. I expect that i386 patches will follow after the full set of mitigations have been applied to amd64. Note that if the "older hardware" is old enough it may predate these issues. From owner-freebsd-questions@freebsd.org Wed Jan 10 07:04:20 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3A9AEE6D859 for ; Wed, 10 Jan 2018 07:04:20 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CFF5E278F for ; Wed, 10 Jan 2018 07:04:19 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (x2f7f2f6.dyn.telefonica.de [2.247.242.246]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id w0A749Yo021696 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 10 Jan 2018 07:04:10 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host x2f7f2f6.dyn.telefonica.de [2.247.242.246] claimed to be ultrabook.yoonka.com Subject: Re: NVMe ZFS mount To: Ben Woods Cc: freebsd-questions@freebsd.org References: <3f89d154-d878-a267-66a5-e898cc2621f5@gjunka.com> From: Grzegorz Junka Message-ID: Date: Wed, 10 Jan 2018 07:04:03 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-GB-large Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 07:04:20 -0000 On 08/01/2018 22:58, Ben Woods wrote: > On Tue, 9 Jan 2018 at 6:47 am, Grzegorz Junka > wrote: > > Hi, > > I've two zfs mirrors, one on two SATA drives and one on two NVMe > drives. > SATA are used to boot the system. I observed that after booting the > system zfs datasets on NVMe drives aren't mounted. The pool is > imported > and I can list the datasets but command mount doesn't show any mounts > apart from the system (SATA) drives. > > Do ZFS datasets on NVMe need any special treatment to be mounted > by the > system automatically, e.g. an entry in /etc/fstab? > > Thanks > > GrzegorzJ > > > I don’t believe NVMe needs any special treatment, but I haven’t used > it. What about the boot order... when you watch it boot, do the NVMe > devices show up before the /etc/rc.d/zfs script is run? > > Check the “canmount” parameter of each of your datasets. > zfs get -r canmount,mountpoint,mounted nvmepool > NVMe devices are enumerated at about the same time as other devices, even slightly before SATA drivers. And much earlier than ZFS tries to mount the root directory. It may not be the same as /etc/rc.d/zfs script. Would this script leave any trace in dmesg? I will check the zfs command you gave when I have access to the system and report back. Thanks GregJ From owner-freebsd-questions@freebsd.org Wed Jan 10 08:11:17 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 589F8E70F45 for ; Wed, 10 Jan 2018 08:11:17 +0000 (UTC) (envelope-from bennett@sdf.org) Received: from mx.sdf.org (mx.sdf.org [205.166.94.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ol.sdf.org", Issuer "ol.sdf.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 40F5A63EC0 for ; Wed, 10 Jan 2018 08:11:16 +0000 (UTC) (envelope-from bennett@sdf.org) Received: from sdf.org (IDENT:bennett@otaku.freeshell.org [205.166.94.9]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id w0A8B6M9007075 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO) for ; Wed, 10 Jan 2018 08:11:06 GMT Received: (from bennett@localhost) by sdf.org (8.15.2/8.12.8/Submit) id w0A8B62K027111 for freebsd-questions@freebsd.org; Wed, 10 Jan 2018 02:11:06 -0600 (CST) From: Scott Bennett Message-Id: <201801100811.w0A8B62K027111@sdf.org> Date: Wed, 10 Jan 2018 02:11:06 -0600 To: freebsd-questions@freebsd.org Subject: ZFS error message questions User-Agent: Heirloom mailx 12.5 6/20/10 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 08:11:17 -0000 After running 11.1-STABLE with root on ZFS for a week and a half or so, I apparently screwed something up such that the system became unusable while trying to enter multi-user mode. It looked like the easiest way to correct the mess would be to wipe it out and re-install. However, I wanted to save the home directory tree because there had been important changes in it since it had been imported from the 10.3-STABLE system with root, /usr/home, and so on on UFS2, so I ran zfs send -ReL -I @15dec2017.freshlyinstalled-11.1S-r236620 zrootx/usr/home@28dec2017 > /mnt/bootdisks/usrhome.28dec2017.zfs-send which is supposed, as I understand it, to have saved a full replication stream, including four snapshots. Now I wish to receive this into the newly re-installed system, but here is what happens. Script started on Sun Jan 7 00:54:39 2018 # zfs recv -dv zrootx /mnt/bootdisks/usrhome on the 10.3-STABLE system, followed by cd /usr/home restore rDf /mnt/bootdisks/usr/home on the 11.1-STABLE system. The rest could be reimported the same as the first time if need be. Please email replies to me directly, as well as to the list, because I am subscribed to the digest form of the list, which means I might not get replies via the list until the next day. Thank you very much in advance for any help! Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at sdf.org *xor* bennett at freeshell.org * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * ********************************************************************** From owner-freebsd-questions@freebsd.org Wed Jan 10 09:41:31 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B19C7E753CB for ; Wed, 10 Jan 2018 09:41:31 +0000 (UTC) (envelope-from g8kbvdave@googlemail.com) Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3BD756B28A; Wed, 10 Jan 2018 09:41:31 +0000 (UTC) (envelope-from g8kbvdave@googlemail.com) Received: by mail-lf0-x235.google.com with SMTP id e27so19062500lfb.9; Wed, 10 Jan 2018 01:41:31 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=hzUZqKmV5hHdGqBkTWZM5xGu1bC92taF56hzescPJPs=; b=WDayDiz98iSVdqWB0DB7u/ktmRoDZyRfkD/0HF/UMkMolUedF9rMFOHrfVPQUo4TNZ 1lbdeuo03wN5j8EUiTvRUQYT9O9iDd3Synp6Bv1WABm78teS4FBR6SjlV1jQNDoZAtYx oc2FpSL3gPKyZ9s+H/MKvbR1GLTJ1ohUDuP7qq69VFCQXj+xtbHF8HtXJyaZLpO5he76 FvP1Q5l+s9V7tmuG+zccNwGPgUzgKrcMKpqgVZQiOhJpSxu7qKSYh2f85qKXpmU+n4s2 pxMjGcLgJsexP1gGteHPJ2h6jx9jlQ2hCUlWCEGGd5R6mJnQ52HF4IoRDWDjCgu4vPDv FgCw== X-Gm-Message-State: AKwxytcFU6h3qpwNSol2NkBFWUT5o/07ev8ejQlKcsuhh/izjUmkORb2 uxBmiinyuZQl98qG5qOCr8fqnNdP X-Google-Smtp-Source: ACJfBot+dMFUow9I+XAsLhGXBTcZHmVUKrh4hU/llZoU7go+vCo6VlVB/1Xdww1ByYndAu4vedTe9Q== X-Received: by 10.25.76.214 with SMTP id z205mr9145966lfa.134.1515577288812; Wed, 10 Jan 2018 01:41:28 -0800 (PST) Received: from [192.168.2.55] ([217.41.35.220]) by smtp.gmail.com with ESMTPSA id r26sm2841637lfd.49.2018.01.10.01.41.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Jan 2018 01:41:27 -0800 (PST) Subject: =?UTF-8?Q?Re:_32_bit_fix=3f_=28Was_Re:_Meltdown_=e2=80=93_Spectre?= =?UTF-8?Q?=29?= To: Ed Maste , freebsd-questions@freebsd.org References: <2e86bfd9-9141-2872-1946-0e9d26326433@googlemail.com> From: Dave B Message-ID: <6523f352-c895-e488-8006-76495907745a@googlemail.com> Date: Wed, 10 Jan 2018 09:41:26 +0000 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-GB X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 09:41:31 -0000 Hi Ed. Understood.   There's "a lot" of FreeBSD based kit out there, running on 32 bit hardware.  A lot of NAS's for one.   (I don’t suppose any of those commercial "appliances" will ever be updated though.) But from my understanding, this problem has probably been present since 1995, and maybe even earlier.  There is a paper published somewhere that documents such issues, dated around 1992!  Awaiting for the SN645 show notes to be published, for that info. (Keep an eye on  https://www.grc.com/securitynow.htm ) The conclusion then, was that it was probably not a problem as would be "too difficult" to manipulate for any gain. The machines I have, are ex Win'2000 boxes, so are probably affected.   One of them was web facing.  It's not now! Best Regards. Dave B. (G0WBX) On 10/01/18 03:29, Ed Maste wrote: > On 9 January 2018 at 07:23, Dave B via freebsd-questions > wrote: >> When is a patch for i386 (32 bit) versions likely to be available? >> >> Regards. >> >> Dave B. >> >> (I only run non GUI 32 bit instances of FreeBSD, on older hardware, GPSD >> NTP machines etc.) > Similar techniques can be applied to i386, but they are a lower > priority and we don't yet have a timeline. I expect that i386 patches > will follow after the full set of mitigations have been applied to > amd64. > > Note that if the "older hardware" is old enough it may predate these issues. From owner-freebsd-questions@freebsd.org Wed Jan 10 09:45:04 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 98837E75796 for ; Wed, 10 Jan 2018 09:45:04 +0000 (UTC) (envelope-from 01000160df27fce5-71307843-becf-4a2f-ac43-83176c1fbb8a-000000@amazonses.com) Received: from a9-46.smtp-out.amazonses.com (a9-46.smtp-out.amazonses.com [54.240.9.46]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 60BC16B556 for ; Wed, 10 Jan 2018 09:45:03 +0000 (UTC) (envelope-from 01000160df27fce5-71307843-becf-4a2f-ac43-83176c1fbb8a-000000@amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=xi2fcwkatebqdkoe6uuutt53jubnl2jy; d=degustatoriacque.com; t=1515572428; h=Subject:Date:From:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; bh=fLloj5vN7g+OkJQFIo20araIoYdQp91zwYrqgm0Yoxc=; b=k3U640h+arVd1Xo0BvB7onSzh4tFuSwLTvEJ6uO8ewK3cUL4tNQJTse+wM63BJCg Uf4OKQnFVCCPzx86X8Tpyulqq6wI+cYHEcvjKhBCewitZ0jMph9D3ARcZlQcu+fuxJV VIE8ndy7ms8TxWAvDjvRULbAee2uQlBb8AM8ftD0= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1515572428; h=Subject:Date:From:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID:Feedback-ID; bh=fLloj5vN7g+OkJQFIo20araIoYdQp91zwYrqgm0Yoxc=; b=QTyhr6MCt1+PwJI9uYdAvkzs48YcpaE/OTllfvYg++2V7Y2Wf7BjxIxE16rqUrYg xj8dbEtiiz0ChXqKLZfEDYtbS0QUDx1SgekhqXu0gZApCatbkppqxV7yHGe9CTN6xlo GDHOQnAYWbbOUGO5h8M3X8zW+XVF3REAI2lU7huM= Subject: =?UTF-8?B?Q29yc2kgcGVyIGxhIGZvcm1hemlvbmUgZGkgSWRyb3NvbW1lbGllciBhIEZvcmzDrC4=?= Date: Wed, 10 Jan 2018 08:20:28 +0000 From: "=?UTF-8?B?QXNzb2NpYXppb25lIERlZ3VzdGF0b3JpIEFjcXVlIE1pbmVyYWxp?=" To: "=?UTF-8?B?ZnJlZWJzZC1xdWVzdGlvbnNAZnJlZWJzZC5vcmc=?=" Message-ID: <01000160df27fce5-71307843-becf-4a2f-ac43-83176c1fbb8a-000000@email.amazonses.com> X-SES-Outgoing: 2018.01.10-54.240.9.46 Feedback-ID: 1.us-east-1.e5k5YvmJu4J2s7EAnCS8JTDvRfkODfY+JU94VVps3Tc=:AmazonSES MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 09:45:04 -0000 From owner-freebsd-questions@freebsd.org Wed Jan 10 11:36:42 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E3B30E7A692 for ; Wed, 10 Jan 2018 11:36:42 +0000 (UTC) (envelope-from g8kbvdave@googlemail.com) Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 774B96F2CA; Wed, 10 Jan 2018 11:36:42 +0000 (UTC) (envelope-from g8kbvdave@googlemail.com) Received: by mail-wm0-x22b.google.com with SMTP id g1so8375623wmg.2; Wed, 10 Jan 2018 03:36:42 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=WKT8HZsb/NYTYunS7mPyesUiS/NSWMcRyeVT4UtuHuA=; b=g7cXSnC+ESzgucjd1aLEe9za8CYr1Jo2zfXx76DA34NmuXizZcQSWNbbeQ82JBQaDM wb0qaB7B3xfogQzIKOiBulZNIOaJ5blTGyqbD5JCqhzRtvG1svqzoI7haNv6RBMajrqS cOCuinUkrcvnqfEJADqLsArlKs9PHed1Fo0A/spkiWOh0EMzfxpHYmHeequoev6oAYAw VJUSlspnpim2YAEZfiLPk3lCQdMfE4LxnzUYQo4wWyjXix+p3Bmm5b2XYVUDvyA+3vFL iConuJEGsrIj7OuFmCKDRbDl8CyYuOWnU6ZcPOqqV0KCd+T3uvVSJEHxxRLjSiHQaijz Eg2A== X-Gm-Message-State: AKwxytfpuf58PiAvQuwlEAxsXhVdbAcuRpg7b27/vlBdYPg8UaqUMQb1 uOfntZvi1IG6scRU/9MrxqGD3N9v X-Google-Smtp-Source: ACJfBotvQ6J2RHywB6dIjoulNXANN3hTIM4HnpKMabXQJWet6PKnen4/nvkDHWKP7AILgkH2Pk4Cjw== X-Received: by 10.80.148.248 with SMTP id t53mr6970408eda.180.1515584200755; Wed, 10 Jan 2018 03:36:40 -0800 (PST) Received: from [192.168.2.55] ([217.41.35.220]) by smtp.gmail.com with ESMTPSA id 26sm9557141eds.67.2018.01.10.03.36.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Jan 2018 03:36:40 -0800 (PST) Subject: =?UTF-8?Q?Re:_32_bit_fix=3f_=28Was_Re:_Meltdown_=e2=80=93_Spectre?= =?UTF-8?Q?=29?= To: Arthur Chance , Ed Maste , freebsd-questions@freebsd.org References: <2e86bfd9-9141-2872-1946-0e9d26326433@googlemail.com> <6523f352-c895-e488-8006-76495907745a@googlemail.com> <49785edc-1ac4-48f3-bff0-19704dadc70b@qeng-ho.org> From: Dave B Message-ID: <0b84bfbb-ef1b-f7d1-ca91-5bbbbb79595a@googlemail.com> Date: Wed, 10 Jan 2018 11:36:39 +0000 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <49785edc-1ac4-48f3-bff0-19704dadc70b@qeng-ho.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-GB X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 11:36:43 -0000 Hi again. When I have more info (re the early CPU's etc)  I'll come back here with it. Agreed re "appliance" NAS devices, "shouldn’t be running arbitrary code".  But see the recent news re most WD MyCloud devices!Hard coded back door's etc, so "some malicious bar steward" could probably plant such if they wished. Do you know about the "Shodan" search engine?   That makes it all too easy to find web facing appliances.  Cameras, drives, printers, PVR's, light bulbs and other IoT "things"...   https://www.shodan.io/   Enjoy! Thanks for now.     Dave B (G0WBX) On 10/01/18 11:23, Arthur Chance wrote: > On 10/01/2018 09:41, Dave B via freebsd-questions wrote: >> Hi Ed. >> >> Understood.   There's "a lot" of FreeBSD based kit out there, running on >> 32 bit hardware.  A lot of NAS's for one.   (I don’t suppose any of >> those commercial "appliances" will ever be updated though.) > An attack requires running code exploiting the vulnerability on the > target machine. NAS type appliances shouldn't allow arbitrary code to be > run. (Emphasis on shouldn't, a lot of appliances seem not to care about > security.) > >> But from my understanding, this problem has probably been present since >> 1995, and maybe even earlier.  There is a paper published somewhere that >> documents such issues, dated around 1992!  Awaiting for the SN645 show >> notes to be published, for that info. > I can't find the article I was reading right now, but it said Intel > chips became vulnerable when the Westmere architecture (the 32 nm > version of Nehalem) was introduced back in 2010. That was the early days > of the Core i[357] CPUs, so Core and Core 2 CPUs are probably too old to > be affected. > >> (Keep an eye on  https://www.grc.com/securitynow.htm ) >> >> The conclusion then, was that it was probably not a problem as would be >> "too difficult" to manipulate for any gain. >> >> The machines I have, are ex Win'2000 boxes, so are probably affected.   >> One of them was web facing.  It's not now! >> >> Best Regards. >> >> Dave B. >> >> (G0WBX) >> >> >> >> On 10/01/18 03:29, Ed Maste wrote: >>> On 9 January 2018 at 07:23, Dave B via freebsd-questions >>> wrote: >>>> When is a patch for i386 (32 bit) versions likely to be available? >>>> >>>> Regards. >>>> >>>> Dave B. >>>> >>>> (I only run non GUI 32 bit instances of FreeBSD, on older hardware, GPSD >>>> NTP machines etc.) >>> Similar techniques can be applied to i386, but they are a lower >>> priority and we don't yet have a timeline. I expect that i386 patches >>> will follow after the full set of mitigations have been applied to >>> amd64. >>> >>> Note that if the "older hardware" is old enough it may predate these issues. >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >> > From owner-freebsd-questions@freebsd.org Wed Jan 10 11:37:04 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 88AF9E7A721 for ; Wed, 10 Jan 2018 11:37:04 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from bede.home.qeng-ho.org (bede.qeng-ho.org [217.155.128.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fileserver.home.qeng-ho.org", Issuer "fileserver.home.qeng-ho.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0A4936F378; Wed, 10 Jan 2018 11:37:03 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from arthur.home.qeng-ho.org (arthur.home.qeng-ho.org [172.23.1.2]) by bede.home.qeng-ho.org (8.15.2/8.15.2) with ESMTP id w0ABNh0w005432; Wed, 10 Jan 2018 11:23:44 GMT (envelope-from freebsd@qeng-ho.org) Subject: =?UTF-8?Q?Re:_32_bit_fix=3f_=28Was_Re:_Meltdown_=e2=80=93_Spectre?= =?UTF-8?Q?=29?= To: Dave B , Ed Maste , freebsd-questions@freebsd.org References: <2e86bfd9-9141-2872-1946-0e9d26326433@googlemail.com> <6523f352-c895-e488-8006-76495907745a@googlemail.com> From: Arthur Chance Message-ID: <49785edc-1ac4-48f3-bff0-19704dadc70b@qeng-ho.org> Date: Wed, 10 Jan 2018 11:23:43 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <6523f352-c895-e488-8006-76495907745a@googlemail.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 11:37:04 -0000 On 10/01/2018 09:41, Dave B via freebsd-questions wrote: > Hi Ed. > > Understood.   There's "a lot" of FreeBSD based kit out there, running on > 32 bit hardware.  A lot of NAS's for one.   (I don’t suppose any of > those commercial "appliances" will ever be updated though.) An attack requires running code exploiting the vulnerability on the target machine. NAS type appliances shouldn't allow arbitrary code to be run. (Emphasis on shouldn't, a lot of appliances seem not to care about security.) > But from my understanding, this problem has probably been present since > 1995, and maybe even earlier.  There is a paper published somewhere that > documents such issues, dated around 1992!  Awaiting for the SN645 show > notes to be published, for that info. I can't find the article I was reading right now, but it said Intel chips became vulnerable when the Westmere architecture (the 32 nm version of Nehalem) was introduced back in 2010. That was the early days of the Core i[357] CPUs, so Core and Core 2 CPUs are probably too old to be affected. > (Keep an eye on  https://www.grc.com/securitynow.htm ) > > The conclusion then, was that it was probably not a problem as would be > "too difficult" to manipulate for any gain. > > The machines I have, are ex Win'2000 boxes, so are probably affected.   > One of them was web facing.  It's not now! > > Best Regards. > > Dave B. > > (G0WBX) > > > > On 10/01/18 03:29, Ed Maste wrote: >> On 9 January 2018 at 07:23, Dave B via freebsd-questions >> wrote: >>> When is a patch for i386 (32 bit) versions likely to be available? >>> >>> Regards. >>> >>> Dave B. >>> >>> (I only run non GUI 32 bit instances of FreeBSD, on older hardware, GPSD >>> NTP machines etc.) >> Similar techniques can be applied to i386, but they are a lower >> priority and we don't yet have a timeline. I expect that i386 patches >> will follow after the full set of mitigations have been applied to >> amd64. >> >> Note that if the "older hardware" is old enough it may predate these issues. > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > -- An amusing coincidence: log2(58) = 5.858 (to 0.0003% accuracy). From owner-freebsd-questions@freebsd.org Wed Jan 10 12:16:37 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6776DE7CD73 for ; Wed, 10 Jan 2018 12:16:37 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from baobab.bilink.net (baobab.bilink.net [212.45.144.44]) by mx1.freebsd.org (Postfix) with ESMTP id 2985671379 for ; Wed, 10 Jan 2018 12:16:36 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from baobab (localhost [127.0.0.1]) by baobab.bilink.it (Postfix) with ESMTP id 3zGnrf4Sgcz3jYpM for ; Wed, 10 Jan 2018 13:10:10 +0100 (CET) X-Virus-Scanned: amavisd-new at mcs.it Received: from baobab.bilink.net ([127.0.0.1]) by baobab (baobab.mcs.it [127.0.0.1]) (amavisd-new, port 11027) with ESMTP id AXhZSQI87lX1 for ; Wed, 10 Jan 2018 13:10:10 +0100 (CET) Received: from hermes.mcs.it (unknown [192.168.132.21]) by baobab.bilink.it (Postfix) with ESMTP id 3zGnrf2wGvz3jYpX for ; Wed, 10 Jan 2018 13:10:10 +0100 (CET) Received: from mordeus (unknown [192.168.45.6]) by hermes.mcs.it (Postfix) with ESMTP id 455931B746D for ; Wed, 10 Jan 2018 13:10:10 +0100 (CET) Date: Wed, 10 Jan 2018 13:10:10 +0100 From: Luciano Mannucci To: FreeBSD Mailing List Subject: 10.4 RELEASE sees only one core X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; amd64-portbld-freebsd10.3) X-Face: 4qPv4GNcD; h<7Q/sK>+GqF4=CR@KmnPkSmwd+#%\F`4yjKO3"C]p'z=(oWRnsYBQGM\5g:4skqQY0NnV'dM:Mm:^/_+I@a"; [-s=ogufdF"9ggQ'=y MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <3zGnrf2wGvz3jYpX@baobab.bilink.it> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 12:16:37 -0000 Hello, I have an Intel 2 CPU with Intel Xeon E5410, that should be quad core, no hyperthread. I expect to see 8 CPUs, though I get: root@baobab:~ # dmesg | head -33 Copyright (c) 1992-2017 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.4-RELEASE #0 r324094: Fri Sep 29 01:45:44 UTC 2017 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 CPU: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz (2327.55-MHz K8-class CPU) Origin="GenuineIntel" Id=0x10676 Family=0x6 Model=0x17 Stepping=6 Features=0xbfebfbff Features2=0xce3bd AMD Features=0x20100800 AMD Features2=0x1 VT-x: (disabled in BIOS) HLT,PAUSE TSC: P-state invariant, performance statistics real memory = 17179869184 (16384 MB) avail memory = 16559685632 (15792 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 2 package(s) x 1 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 4 Is it normal? I'm running: root@baobab:~ # freebsd-version 10.4-RELEASE-p5 What should I do? Thanks to all, Luciano -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster@sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/ From owner-freebsd-questions@freebsd.org Wed Jan 10 12:39:53 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 562E1E7DEAE for ; Wed, 10 Jan 2018 12:39:53 +0000 (UTC) (envelope-from feenberg@nber.org) Received: from mail2.nber.org (mail2.nber.org [198.71.6.79]) by mx1.freebsd.org (Postfix) with ESMTP id DD82171FF3; Wed, 10 Jan 2018 12:39:52 +0000 (UTC) (envelope-from feenberg@nber.org) Received: from sas1.nber.org (sas1.nber.org [198.71.6.89]) by mail2.nber.org (8.15.2/8.15.2) with ESMTPS id w0ACbSiA007104 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 10 Jan 2018 07:37:28 -0500 (EST) (envelope-from feenberg@nber.org) Date: Wed, 10 Jan 2018 07:37:28 -0500 (EST) From: Daniel Feenberg To: Dave B cc: Ed Maste , freebsd-questions@freebsd.org Subject: =?UTF-8?Q?Re=3A_32_bit_fix=3F_=28Was_Re=3A_Meltdown_=E2=80?= =?UTF-8?Q?=93_Spectre=29?= In-Reply-To: <6523f352-c895-e488-8006-76495907745a@googlemail.com> Message-ID: References: <2e86bfd9-9141-2872-1946-0e9d26326433@googlemail.com> <6523f352-c895-e488-8006-76495907745a@googlemail.com> User-Agent: Alpine 2.21 (LRH 202 2017-01-01) MIME-Version: 1.0 X-KLMS-Rule-ID: 1 X-KLMS-Message-Action: clean X-KLMS-AntiSpam-Status: not scanned, disabled by settings X-KLMS-AntiSpam-Interceptor-Info: not scanned X-KLMS-AntiPhishing: Clean, 2018/01/09 16:30:43 X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.721, bases: 2018/01/10 05:31:00 #11562500 X-KLMS-AntiVirus-Status: Clean, skipped Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 12:39:53 -0000 On Wed, 10 Jan 2018, Dave B via freebsd-questions wrote: > Hi Ed. > > Understood.   There's "a lot" of FreeBSD based kit out there, running on > 32 bit hardware.  A lot of NAS's for one.   (I don’t suppose any of > those commercial "appliances" will ever be updated though.) > Are NAS's a worry? Wouldn't the typical NAS login have root already? Why would anyone other than the system admin have a login on the NAS box at all? If the NAS isn't used as a web browser or MUA, how would the malware get to be run by an unprivileged user? I understand that the vulnerability can be demonstrated in Javascript, but this would be an attack on the client running with the privileges of the web browser. That isn't something that would happen on the typical system services appliance such as a NAS box, switch, or router. daniel feenberg NBER From owner-freebsd-questions@freebsd.org Wed Jan 10 13:01:26 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99060E7F0C9 for ; Wed, 10 Jan 2018 13:01:26 +0000 (UTC) (envelope-from v.dol_s@hotmail.com) Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-oln040092064039.outbound.protection.outlook.com [40.92.64.39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0DC1E7369B for ; Wed, 10 Jan 2018 13:01:25 +0000 (UTC) (envelope-from v.dol_s@hotmail.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=rQ+uevW0e5koeZfrhUhArZxdfJRfvvU3f/2zlHYLUVk=; b=iyqEypGFalg8j9EfMaDMDndFTuDM2psKOdzCbldyBwVrZHiUIcOX9Z9oWtHstS5KXo2JGU22hB2W/ouf+fvtcMazEZLud/fk+EwCMay/v+8XryTe+xMkgf07E2Lzk12rneS+YqyoFcRf2P+0o16bWPX7AXawXOzlg/Uke7qoxDUM+Cp9A73q5l7k2z30tS0BTZCuwN0hi4FJkxXY9rfJ9XG8kQNpzp4SBFyOM6aciVZYKgw7Jgm8PqYIVuFbzyZuMMWJzm0ocoZ0OxKk9G3r+e2jupIjWR9zD/N4a0TVfCVMkKKaoNFgfvEx7/dZerKJAGaLGF60EG7F/OWaOH7cQA== Received: from HE1EUR01FT049.eop-EUR01.prod.protection.outlook.com (10.152.0.57) by HE1EUR01HT219.eop-EUR01.prod.protection.outlook.com (10.152.1.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.345.12; Wed, 10 Jan 2018 13:01:23 +0000 Received: from AM5PR0902MB1923.eurprd09.prod.outlook.com (10.152.0.54) by HE1EUR01FT049.mail.protection.outlook.com (10.152.0.221) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.345.12 via Frontend Transport; Wed, 10 Jan 2018 13:01:23 +0000 Received: from AM5PR0902MB1923.eurprd09.prod.outlook.com ([fe80::e4a7:bead:3f27:7fd8]) by AM5PR0902MB1923.eurprd09.prod.outlook.com ([fe80::e4a7:bead:3f27:7fd8%13]) with mapi id 15.20.0386.008; Wed, 10 Jan 2018 13:01:23 +0000 From: Vitalio D To: "freebsd-questions@freebsd.org" Subject: where to find exit(int) function implementation Thread-Topic: where to find exit(int) function implementation Thread-Index: AQHTihKQe0z8Ge0DZk6xf6VVVCNQPA== Date: Wed, 10 Jan 2018 13:01:23 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-incomingtopheadermarker: OriginalChecksum:E0AF2726A4EFD77499AA904362635F6F058D430F2302E29F57D3AD7B74B23B9E; UpperCasedChecksum:318959DC3E7F87EFACB0DC3C5FED35A7BAFAC4094A1A7BDC9FAE374304F610FC; SizeAsReceived:6908; Count:44 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [tpyGuNk9RqruQwYY2uoBnVZAMUVAy/4K] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; HE1EUR01HT219; 6:fW4nLbwFOJqi1jgaKrng8Nvw6mV8nCNk1NNAhySCfVvaPqCBVf1ATmP7sTLEP2hO2xOf0Tm72Gt8jWZtTZslS1VdBocbjKpd0HiYD5SiSV49rKH9pwbN5mBosxkSPKUGLOMcKyB0TNQvWLrGDVBhS4nIUqbgDV7rged+lfjkBDH+tW29Yc2iuU6OC6EJ/tzopBjRfnlkWbb2U/GmRORpxLlRhy/npNGmQ5DUbDQySt1dSEZFGkoVh94MmwSxG+5JLizFEF1ZpbmHmsrkAHLtwN7PdU1BwZRasjfohJ/LKEnCkDg9ESRcikCNtmk29Ow5PMMEE9Exb+srw81fLsqJhVui8Auk1NwbNpe7TF5S6Ts=; 5:KuCxJztEpnKPZNql0QFtMZhig7FtIqxg4P7y1ypa82a2IbizP9t3LAWqeNOtKqicpW2ajtm9mkRt9c3QX5GW1RTkLZBTtO788RHOQDKNYd2S/Uk5UINGvhx2znlvqbl5Eg9lH3lfsEV6LL/7F9IZ6e1P5BuZvG85jKnMGf3UyyA=; 24:xrH5w0wAg1mUVe1whK1pddFGLVRET7zhf/UUPDTF2bpz6U/CvlHxe5px+vxpSpX5y0BQzPoN/dB6bfeg5S5b7O64hrbxme06pVIEkplo6m8=; 7:rS80xCL/dl9itJEDOKOm8kSEMFaEr4WzAosk3B1iDUjX67BowOL+3c1djUBX1dX1owQEJa0V+EmiuzjgongmKSdwb7R81tIFjS9l7czvIfhNdE+WZ5oho73aaSaG4hgndcoy7Qc+4Y2azZYOBOxtWe2gORDos8Cm4fh0MXfmEm7Mcwk9gjE3Ely4M4NFDxnfz6hUF0DVBu0aAB8AOQj1y658NQWf+JDbjeLw2PY6P0mHECeXx4KOUOsKdHgQB5AH x-incomingheadercount: 44 x-eopattributedmessage: 0 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020051)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1603101448)(1601125374)(1701031045); SRVR:HE1EUR01HT219; x-ms-traffictypediagnostic: HE1EUR01HT219: x-ms-office365-filtering-correlation-id: c182c9df-319b-430f-88d5-08d5582a4028 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:HE1EUR01HT219; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:HE1EUR01HT219; x-forefront-prvs: 0548586081 x-forefront-antispam-report: SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:HE1EUR01HT219; H:AM5PR0902MB1923.eurprd09.prod.outlook.com; FPR:; SPF:None; LANG:; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: hotmail.com X-MS-Exchange-CrossTenant-Network-Message-Id: c182c9df-319b-430f-88d5-08d5582a4028 X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jan 2018 13:01:23.0437 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1EUR01HT219 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 13:01:26 -0000 Hello,=0A= =0A= How and where void _exit(int) is implemented? I've started=0A= with exit(int) defined in exit.c un stdlib, but I've got stuck at=0A= unistd.h where void _exit(int) __dead2;=0A= After that I couldn't find anything by running=0A= find /usr/src -name "*.c" -exec grep " _exit(int" /dev/null {} \;=0A= =0A= So I guess there is some unix convention magic involved but=0A= I can't point which one. Can someone be kind and explain or point=0A= out a resource where this trick is explained?=0A= =0A= Regards,=0A= Vitalio= From owner-freebsd-questions@freebsd.org Wed Jan 10 13:13:47 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7639FE7F9F8 for ; Wed, 10 Jan 2018 13:13:47 +0000 (UTC) (envelope-from g8kbvdave@googlemail.com) Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0E8CD73FD8; Wed, 10 Jan 2018 13:13:47 +0000 (UTC) (envelope-from g8kbvdave@googlemail.com) Received: by mail-wm0-x231.google.com with SMTP id t8so26682751wmc.3; Wed, 10 Jan 2018 05:13:46 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=385aq+EEJa3NLonPEKnjDoQSF3PnhJ0j/KY3S4JxW6c=; b=MKS4bl9uuxdGY+oOCojZfXSJMnedtaUhFwMZicw3N2NcuIxF2awghxISed1XzhBvP0 mHGU5345FD8k6CF9JavY2EKWx+UPurTGU57idlhBpI8J6mmBeAcQAixC2Ga1+KaCP6Pi rcXZ5cZljtwS6+FpqgAAvJQmDYOELiQeK+nzlvVa2VD7tXz+YTQ+fUAoUEBxcgFNnYoa NYKgaDeEFXV5pyOXwtwz5ujyTNt7K9K2fJ4ZCcQWvKjP31ImsQs8CcaCeT2zUFINFNKV qOqHD5Vk+B6nzMvQR1N+xsCEPAGzyOEPRyzrx2YbWOrKtQar2z/0eTLRyhWNj9RYJ2rP 1TYQ== X-Gm-Message-State: AKGB3mLJF2JC2YbgQl5pRsGN1crCeT6r0BGZpthp5PzKHPWj1+jxB41G Z21RQfj2rky6ZDkuWB4PU15yx2ir X-Google-Smtp-Source: ACJfBotnTEPK5FUlMZ07yMXN7ulyhryOmKeF94e0b0kYJJ1zojN80riRZzvqFRglTVj0HW3IkwQ4hQ== X-Received: by 10.28.91.10 with SMTP id p10mr15537479wmb.112.1515590025309; Wed, 10 Jan 2018 05:13:45 -0800 (PST) Received: from [192.168.2.55] ([217.41.35.220]) by smtp.gmail.com with ESMTPSA id j14sm9034826wrd.47.2018.01.10.05.13.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Jan 2018 05:13:44 -0800 (PST) Subject: =?UTF-8?Q?Re:_32_bit_fix=3f_=28Was_Re:_Meltdown_=e2=80=93_Spectre?= =?UTF-8?Q?=29?= To: Daniel Feenberg Cc: Ed Maste , freebsd-questions@freebsd.org References: <2e86bfd9-9141-2872-1946-0e9d26326433@googlemail.com> <6523f352-c895-e488-8006-76495907745a@googlemail.com> From: Dave B Message-ID: Date: Wed, 10 Jan 2018 13:13:43 +0000 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-GB X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 13:13:47 -0000 Hi. Many of those appliances are marketed as being able to make your files available to you, even when you're not at home.  (Music, photos etc.)  They come with crude mobile app's (among other things, to monetize the user) and the security/authentication varies from so so, to nil.   (Guess what most users opt for, because "it's difficult" to do it securely.)   Remember, we're talking about Joe Public, not a sysadmin! That, and they either punch holes in the router using UPnP, or people (I know one) place them in a DMZ, again, because it's easy, and "it just works."   What else is then exposed, who knows? The rest as they say, one day will be history.   Using Shodan, it is not difficult to find admin login pages on the public internet, for all sorts of bits of equipment and other gadgetry. Take care. Dave B On 10/01/18 12:37, Daniel Feenberg wrote: > > > On Wed, 10 Jan 2018, Dave B via freebsd-questions wrote: > >> Hi Ed. >> >> Understood.   There's "a lot" of FreeBSD based kit out there, running on >> 32 bit hardware.  A lot of NAS's for one.   (I don’t suppose any of >> those commercial "appliances" will ever be updated though.) >> > > Are NAS's a worry? Wouldn't the typical NAS login have root already? > Why would anyone other than the system admin have a login on the NAS > box at all? If the NAS isn't used as a web browser or MUA, how would > the malware get to be run by an unprivileged user? > > I understand that the vulnerability can be demonstrated in Javascript, > but this would be an attack on the client running with the privileges > of the web browser. That isn't something that would happen on the > typical system services appliance such as a NAS box, switch, or router. > > daniel feenberg > NBER From owner-freebsd-questions@freebsd.org Wed Jan 10 13:16:20 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6FCDBE7FC00; Wed, 10 Jan 2018 13:16:20 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (mail.dpedia.de [178.254.4.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 373FB74129; Wed, 10 Jan 2018 13:16:19 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [178.254.4.75] (helo=webmail.1blu.de) by ms-10.1blu.de with esmtpa (Exim 4.86_2) (envelope-from ) id 1eZGEq-00038K-DK; Wed, 10 Jan 2018 14:16:16 +0100 Received: from orion.oclc.de ([193.31.11.193]) by webmail.1blu.de with HTTP (HTTP/1.1 POST); Wed, 10 Jan 2018 14:16:16 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 10 Jan 2018 14:16:16 +0100 From: Matthias Apitz To: Vitalio D Cc: freebsd-questions@freebsd.org, owner-freebsd-questions@freebsd.org Subject: Re: where to find exit(int) function implementation In-Reply-To: References: Message-ID: <59cdf69e792d5c723fa919abac1d67b6@webmail.1blu.de> X-Sender: guru@unixarea.de User-Agent: 1blu Webmail X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 178.254.4.75 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 13:16:20 -0000 Am 10.01.2018 14:01, schrieb Vitalio D: > Hello, > > How and where void _exit(int) is implemented? I've started > with exit(int) defined in exit.c un stdlib, but I've got stuck at > unistd.h where void _exit(int) __dead2; > After that I couldn't find anything by running > find /usr/src -name "*.c" -exec grep " _exit(int" /dev/null {} \; $ find /usr/src -name *.c | grep exit /usr/src/sys/kern/kern_exit.c /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_onexit.c /usr/src/lib/libc/arm/aeabi/aeabi_atexit.c /usr/src/lib/libc/stdlib/cxa_thread_atexit.c /usr/src/lib/libc/stdlib/cxa_thread_atexit_impl.c /usr/src/lib/libc/stdlib/exit.c ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ /usr/src/lib/libc/stdlib/atexit.c /usr/src/lib/libc/stdlib/quick_exit.c /usr/src/lib/libthr/thread/thr_exit.c /usr/src/contrib/netbsd-tests/lib/libc/stdlib/h_atexit.c /usr/src/contrib/netbsd-tests/lib/libc/stdlib/t_exit.c /usr/src/contrib/netbsd-tests/lib/libpthread/h_atexit.c /usr/src/contrib/netbsd-tests/lib/libpthread/h_exit.c /usr/src/contrib/binutils/libiberty/atexit.c /usr/src/contrib/binutils/libiberty/xatexit.c /usr/src/contrib/binutils/libiberty/xexit.c /usr/src/contrib/tcp_wrappers/clean_exit.c /usr/src/contrib/xz/src/common/tuklib_exit.c /usr/src/contrib/gcclibs/libiberty/atexit.c /usr/src/contrib/gcclibs/libiberty/xatexit.c /usr/src/contrib/gcclibs/libiberty/xexit.c /usr/src/contrib/sendmail/libsm/strexit.c /usr/src/contrib/sendmail/src/sysexits.c /usr/src/contrib/diff/lib/exitfail.c /usr/src/contrib/nvi/vi/v_zexit.c From owner-freebsd-questions@freebsd.org Wed Jan 10 13:26:54 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DAC32E9A221 for ; Wed, 10 Jan 2018 13:26:54 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9DF8274726; Wed, 10 Jan 2018 13:26:54 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by mail-it0-x230.google.com with SMTP id f143so16192689itb.0; Wed, 10 Jan 2018 05:26:54 -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=OHK6w5z8SKiFAMhQCqRLk3P9MLD6NzExAYy/p1pcZ6Y=; b=Tz5x4GyoUxl9wac1xrZC5J1mmF4u8MOTMI4pihl++kiUPRtzuFssKO+dNUieewVJYa Zzo99cGNNTUIwm2xOd3TN0pgs42YBxrmaLIZT5/fHI9lEUdtHmh2+NZAYa+KxzhH/oJl 37Rq+roTqU1QDfeYFpYTlGzq00vxDd9IsES7n+cnwcdV8XAkXKVD1YCcsXJzbJ/jLdzW 75SmG8AkAPQjbGkrAHifbMkYZ5r7V1eF17ENkr8vbyG/MaLvqlX4qhMD8KMsuCGc3fX7 xOfv3omsy2to5ZBvT3uBzDi8pOPCzi320Jj7IO+IfnKrTkw6l2of4JJcVVitdJtPk0hO Q1tA== 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=OHK6w5z8SKiFAMhQCqRLk3P9MLD6NzExAYy/p1pcZ6Y=; b=GqDL+/VDXSPSWj/eSrzge7fwXKKKfR9NtL39WCQ7M0q0vWRHJdLFjUyrZV4GuOL4Lh XDo7tnBEqZ6K3FSNRwxQ9wHUwWgdbwYcwBLCFug635mfSuhVKCLeHSXwqPRMOiXb4Cvz UXOmFXFpqrnK/e0dUc1i/GEEGqB9NvOhJyE91d3u7p+jzK3JBPR0R0s8rLOET9yK8/Id GPIFK+PA2KZLHiwiOT6fJRLn8/z3SdnNgYBDKcW2w0yc6kI6RtN6X1dmrjAPzJ9Fp+qL f9FhoJMLNohGgd7Da55/h1swPHGysj5cC1+eSuN67r5Chf+pUaARJ3KbsFL/xBngRrqc D6yA== X-Gm-Message-State: AKGB3mKt+4h83Hi9zbLQXLtHD/PEHYswAh9LnuLCSnos6LpNUMe7cGqC aVDXy1n85aU6OEwRIpRwJ+FS4G3Jscb/wEWRUiE= X-Google-Smtp-Source: ACJfBotE9zWqBvtDcOS9/mePuOclO3OPoa7wT+5Wp7oVdJL95P02/COgc3gsE0qUrsCHkJJKvfEHd4wu6R1EsrJorqg= X-Received: by 10.36.37.209 with SMTP id g200mr19979804itg.152.1515590814018; Wed, 10 Jan 2018 05:26:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.36.105.3 with HTTP; Wed, 10 Jan 2018 05:26:53 -0800 (PST) In-Reply-To: References: <2e86bfd9-9141-2872-1946-0e9d26326433@googlemail.com> <6523f352-c895-e488-8006-76495907745a@googlemail.com> From: Aryeh Friedman Date: Wed, 10 Jan 2018 08:26:53 -0500 Message-ID: Subject: =?UTF-8?Q?Re=3A_32_bit_fix=3F_=28Was_Re=3A_Meltdown_=E2=80=93_Spectre=29?= To: Dave B Cc: Daniel Feenberg , Ed Maste , FreeBSD Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 13:26:54 -0000 On Wed, Jan 10, 2018 at 8:13 AM, Dave B via freebsd-questions < freebsd-questions@freebsd.org> wrote: > Hi. > > Many of those appliances are marketed as being able to make your files > available to you, even when you're not at home. (Music, photos etc.) > They come with crude mobile app's (among other things, to monetize the > user) and the security/authentication varies from so so, to nil. > (Guess what most users opt for, because "it's difficult" to do it > securely.) Remember, we're talking about Joe Public, not a sysadmin! > Even people who *SHOULD* "know better" do stupid things like use default passwords and disable firewalls, etc. For example many of the doctors that my largest client works need to abide by HIPAA (we even given them advice on how to do this) which among other things has up-to $50k per patient/per breach fine for the unauthorized release of patient health information (PHI). They will then attach these systems to all kinds of devices that are explicitly not HIPAA compliant (nor make any claim to be) as well attach them to semi-public systems like on-line appointment booking and pharmacies (here in NY State for example paper prescriptions are now illegal, they must be filed electronically). In short in today's connect world there is no such thing as an completely isolated/air gaped system. Even more troublesome is the bad guys *KNOW* this and target systems that give the user a false sense of security (like many medical IoT devices do and/or the EMR [electronic medical records]) due to no one reads the fine print of "if we are put in a secure environment we will not break the security" [aka all bets are off in unsecured environment]. -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-questions@freebsd.org Wed Jan 10 13:47:00 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 554A9E9C59C for ; Wed, 10 Jan 2018 13:47:00 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1CE81753FB; Wed, 10 Jan 2018 13:47:00 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: by mail-it0-x233.google.com with SMTP id d137so16249776itc.2; Wed, 10 Jan 2018 05:47:00 -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=0003hZw6ZxMphTq853Q0teYjO+bU7IH63DLDo+/4a2g=; b=bYO58XL4xvYskXwLF8XcKGJbM1qqCX41om4MwzvVOPZrwaTVVB92Oxj8Amn9mYiRHq SLyNiZrrqhzGmK+XKX5nDFYrYCuSNZDYaIUCCpwDnfIvJ+o90YFePLCXo3zwW7bphIqh LhsJFtPbQnLAQ5LlPqChAqgn6f5QrL3cqHhegX3/rT8iR+xOJ+9xFRXahqG4ZLOZUyJb 1SHcQ+PFPMd/CCZVm9Pze/Z0Yn0tzf0Jyjr6t3xAMQgXUxWJ5kG7VwyNZGoKL2/ValfD adLfZ37Pg3tNnZ0HDVntNeqqtiBlMFrYmYqdFPXbh5j3TPa2BFH79UkG+e9FzdJyN9Kh sZ9g== 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=0003hZw6ZxMphTq853Q0teYjO+bU7IH63DLDo+/4a2g=; b=kiD7zTCcnYA8YhRfMALEkclBhNRdr28KaKRQq6p/O/iJpq1g0GG8sGjxgJ8SKwK1+5 /WUhoNwpClIZKCgno5EHg/II6FiVSZ3HoL1W1IbKg2HU6lQ7/X79hXzH2u/YqiMbcZVW XI6EKMGhUDarmLjZ6t+hk6X7DB0sRpYScezDdGS8um4rKOtk9JclfGydK2YIRYMm8+ln 1OYjeNZU0WnvHkGOz6Oghct8EP6FV6A55persc1BywGEqvRImDk+s13k8GfhRHbAVKz7 RpiN0HefrgxnFMz8ShT6AoV/SaCn4Usj+Ijnv+8FE3UlZRYBViGC+1NeaYgTORXQEwrf IkFg== X-Gm-Message-State: AKwxytflvdnBuELHajxkyxCralvzGrHon+zOV5NKyHFwERgD7lOFPY45 O8tOjRYND7aVPKUFGz/DoBLIvEaX7uUP1CS2pZM= X-Google-Smtp-Source: ACJfBot9oIDcl9THdVtxvj4HGCy+dvnoxNnzFtpJFQ2aerOsJ8qgo0v5/LtaEeCo4js+mOZEA5O+7fJzH3IRQNJDHyU= X-Received: by 10.36.73.204 with SMTP id e73mr14176925itd.85.1515592019288; Wed, 10 Jan 2018 05:46:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.112.76 with HTTP; Wed, 10 Jan 2018 05:46:58 -0800 (PST) In-Reply-To: <0b84bfbb-ef1b-f7d1-ca91-5bbbbb79595a@googlemail.com> References: <2e86bfd9-9141-2872-1946-0e9d26326433@googlemail.com> <6523f352-c895-e488-8006-76495907745a@googlemail.com> <49785edc-1ac4-48f3-bff0-19704dadc70b@qeng-ho.org> <0b84bfbb-ef1b-f7d1-ca91-5bbbbb79595a@googlemail.com> From: krad Date: Wed, 10 Jan 2018 13:46:58 +0000 Message-ID: Subject: =?UTF-8?Q?Re=3A_32_bit_fix=3F_=28Was_Re=3A_Meltdown_=E2=80=93_Spectre=29?= To: Dave B Cc: Arthur Chance , Ed Maste , FreeBSD Questions Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 13:47:00 -0000 Ideally no, but most do have the capability these days, as they are multi use systems. Eg freenas can run jails, and vms, unraid doing docker stuff etc...... On 10 January 2018 at 11:36, Dave B via freebsd-questions < freebsd-questions@freebsd.org> wrote: > Hi again. > > When I have more info (re the early CPU's etc) I'll come back here with > it. > > Agreed re "appliance" NAS devices, "shouldn=E2=80=99t be running arbitrar= y > code". But see the recent news re most WD MyCloud devices!Hard coded > back door's etc, so "some malicious bar steward" could probably plant > such if they wished. > > Do you know about the "Shodan" search engine? That makes it all too > easy to find web facing appliances. Cameras, drives, printers, PVR's, > light bulbs and other IoT "things"... https://www.shodan.io/ Enjoy! > > Thanks for now. > > Dave B > > (G0WBX) > > > On 10/01/18 11:23, Arthur Chance wrote: > > On 10/01/2018 09:41, Dave B via freebsd-questions wrote: > >> Hi Ed. > >> > >> Understood. There's "a lot" of FreeBSD based kit out there, running = on > >> 32 bit hardware. A lot of NAS's for one. (I don=E2=80=99t suppose a= ny of > >> those commercial "appliances" will ever be updated though.) > > An attack requires running code exploiting the vulnerability on the > > target machine. NAS type appliances shouldn't allow arbitrary code to b= e > > run. (Emphasis on shouldn't, a lot of appliances seem not to care about > > security.) > > > >> But from my understanding, this problem has probably been present sinc= e > >> 1995, and maybe even earlier. There is a paper published somewhere th= at > >> documents such issues, dated around 1992! Awaiting for the SN645 show > >> notes to be published, for that info. > > I can't find the article I was reading right now, but it said Intel > > chips became vulnerable when the Westmere architecture (the 32 nm > > version of Nehalem) was introduced back in 2010. That was the early day= s > > of the Core i[357] CPUs, so Core and Core 2 CPUs are probably too old t= o > > be affected. > > > >> (Keep an eye on https://www.grc.com/securitynow.htm ) > >> > >> The conclusion then, was that it was probably not a problem as would b= e > >> "too difficult" to manipulate for any gain. > >> > >> The machines I have, are ex Win'2000 boxes, so are probably affected. > >> One of them was web facing. It's not now! > >> > >> Best Regards. > >> > >> Dave B. > >> > >> (G0WBX) > >> > >> > >> > >> On 10/01/18 03:29, Ed Maste wrote: > >>> On 9 January 2018 at 07:23, Dave B via freebsd-questions > >>> wrote: > >>>> When is a patch for i386 (32 bit) versions likely to be available? > >>>> > >>>> Regards. > >>>> > >>>> Dave B. > >>>> > >>>> (I only run non GUI 32 bit instances of FreeBSD, on older hardware, > GPSD > >>>> NTP machines etc.) > >>> Similar techniques can be applied to i386, but they are a lower > >>> priority and we don't yet have a timeline. I expect that i386 patches > >>> will follow after the full set of mitigations have been applied to > >>> amd64. > >>> > >>> Note that if the "older hardware" is old enough it may predate these > issues. > >> _______________________________________________ > >> freebsd-questions@freebsd.org mailing list > >> https://lists.freebsd.org/mailman/listinfo/freebsd-questions > >> To unsubscribe, send any mail to "freebsd-questions- > unsubscribe@freebsd.org" > >> > > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions- > unsubscribe@freebsd.org" > From owner-freebsd-questions@freebsd.org Wed Jan 10 13:49:44 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F352E9C8CA; Wed, 10 Jan 2018 13:49:44 +0000 (UTC) (envelope-from yuripv@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B9A6D75628; Wed, 10 Jan 2018 13:49:43 +0000 (UTC) (envelope-from yuripv@gmx.com) Received: from [192.168.1.2] ([94.233.224.65]) by mail.gmx.com (mrgmx001 [212.227.17.184]) with ESMTPSA (Nemesis) id 0LoEwL-1f6eVL396P-00gK08; Wed, 10 Jan 2018 14:49:35 +0100 Subject: Re: where to find exit(int) function implementation To: Matthias Apitz , Vitalio D Cc: freebsd-questions@freebsd.org, owner-freebsd-questions@freebsd.org References: <59cdf69e792d5c723fa919abac1d67b6@webmail.1blu.de> From: Yuri Pankov Message-ID: <8ef73fb7-dc2f-2fcb-f8e6-e7de02a66b64@gmx.com> Date: Wed, 10 Jan 2018 16:49:33 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <59cdf69e792d5c723fa919abac1d67b6@webmail.1blu.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:jXX14zyBY0eBY4uS9pCKP0H4GX5aU9QJruZYog4K/FAxESksmiP qKoEFYl97c2IlkIf/KXwTv7ZmndCeKR3y73pXClI0FnkFRYEuH1brEfUndj7NroYMX+fVts JrZ2WW1ziK4nh1o6tAJFxlmrB2ynteThwOD/y7zHf4g4ajQ2A+UPqBCTrgygrodyO2UMw4F CItvUJt8qtFnhJ6uEwjkA== X-UI-Out-Filterresults: notjunk:1;V01:K0:aRbc918hCFs=:49Y32iplN2wbf+L9mMcnMK YtG3zRr6XhUXLFWSzvA14H8//RW3l4lpecsfvAtpiiGknynonW07ilBXUZjnNS0CdX0bbmkrd nkOcZuNDAHmSOLdP1cfdafW4q6N9jT1mzqHroFKpAxQqGEVPNmiYoTD4QOg0zOGVSPRuM9XDk SemAph3nFPxyQZ3NSg590ey0p2kqEN94NMSZ4WGBzMWn9oaOiDLxg5p8wY9WWRJDALye3Hv7S aqX3I36r2V9A1ZAauAc9ok4QmT1uX9OXQ2lUr6Djos8j9PKGe2spAQcvTlRnX6FZRfJ0+BgA+ /AAq2/jBj4cQmVgP4EU9Uvd5RpQUFubiT3XUciQPVl1zN06pHjtpul0us271aNkRazRrGKf8w t9dglNu0hqm7Qk+boolh4gjJKeBjtUnzXEJPIYBPNdBscX63yS2svZgmDBNYbmkkQX33uEImd gTdLDLAkZz4NHgFLV1uwZd87JkPfMHGwm6m3PZXhlILBiRPf2W5uuIcWZFxhBapO4NK0vbLrg DLtZ3bpGytxK8a+ek4R3AQXIDFo4NQ+LpfXTQSlr+Z64fqqXaT0BRt38Kwx0K6fgXuBVxuAeb jk/JVSb4SvXPeQ6Qa4Elbrl4WenWE8YpRFbegtgyo1DW2ahOzsIUFcafswKhAmVUohc8mTM3Q PCSeypqRKqhtiS3oQLTRX/9A2US46EjtcU3FrCAfn0lOAdXnoWWQwtEtOj30F9Km1QrAU8nI/ 3oCl9oWFlfuta/Xw5MpzFIkwuBEXfuHEi8hF0Dp8IogvVO9ETdAJciEz3KWs+UcBFFNNmKlMK O2kjZkRMBW73DkdWL2oVVLxvBbZKe1nQcqRxPw364UuFTrle1JqemON4hwVaLkV1sW17Fb8kg DX0t/6QBRXPLjlMsihSRcSnGGwbjCZTfpySAZvK1MoMZ7Km5cwLotShgc1vEBucmGDseMb36s FVmKnQ9CMPQ== X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 13:49:44 -0000 On Wed, Jan 10, 2018 at 02:16:16PM +0100, Matthias Apitz: > Am 10.01.2018 14:01, schrieb Vitalio D: >> Hello, >> >> How and where void _exit(int) is implemented? I've started >> with exit(int) defined in exit.c un stdlib, but I've got stuck at >> unistd.h where void _exit(int) __dead2; >> After that I couldn't find anything by running >> find /usr/src -name "*.c" -exec grep " _exit(int" /dev/null {} \; > > $ find /usr/src -name *.c | grep exit > /usr/src/sys/kern/kern_exit.c > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_onexit.c > /usr/src/lib/libc/arm/aeabi/aeabi_atexit.c > /usr/src/lib/libc/stdlib/cxa_thread_atexit.c > /usr/src/lib/libc/stdlib/cxa_thread_atexit_impl.c > /usr/src/lib/libc/stdlib/exit.c > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The original question was about _exit(2) syscall, not exit(3). WRT the _exit(2), it's marked as "PSEUDO" and relevant PSEUDO macro is defined in lib/libc//SYS.h (if I'm reading it all correctly). From owner-freebsd-questions@freebsd.org Wed Jan 10 14:30:25 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A084E5BC93 for ; Wed, 10 Jan 2018 14:30:25 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3101B775D1 for ; Wed, 10 Jan 2018 14:30:25 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by mail-io0-x233.google.com with SMTP id k18so22612440ioc.11 for ; Wed, 10 Jan 2018 06:30:25 -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=UsCaZ3nLQNp0L9e4dARq7ABc1A9rL14JZXvLZcdqAMk=; b=t8Z3gX8cmq8Srrd+bUrpfwOByqvDgaYSIdZguH99quaHH7fSpWpo2JRVQQc/XuR+Km YROBcLNXARiZUyGQKqr2sF7SYaabwTMXwhHMVid/bpzzEpHk5/kXpKNedPrKuLXvcOkx zKI7iAaBRqPSk5pKzme3K5Jfd5h8mX4FxN9whhaUZI19zocL2QduAslkT8XV7lpgj1o4 dCKBAkKkWyV/kDspwjjpGR/SKsTTIzPPCEPAV/MLyLubav0WYNI9CsBb7p/4UTGUxU7C 2R/sKAmMtGGruyTp2yoyPQ+X+LXMpax2Ak3ySbDMELeSY42azLWzzhP4bqfFbDQhDzMt RpuQ== 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=UsCaZ3nLQNp0L9e4dARq7ABc1A9rL14JZXvLZcdqAMk=; b=bAGGVe2GPzgWCYhRYClwkCjo484tA3cYq6o5v9Kda5Tg3kHnHyoLbA9ggzFML9JhUj aUkux+q4WKABXdlezvdheVfQhFGkMG/WU5zgUuMPsRphCBOMs4JQjrGGjsUv6VEnB96e EIfDl874tS52nxQ7IqLvrePjGWqUgIEpHnvXzKSessdiZ63Zo2+UAXrP+MJET8IOyAtB N/LIkAyKqIDtNrJSTDdk1iKr5r0D0DNlh9xRQqDpqklmaQRE9+cQqghMOQwx9V9CL19/ tQ6Ar4q3D9SWJE0Mb/NyDtEH9aYar/bEoC+lavNYMn75NXCEaN+gfqTKjrcAu0Ho0Kst AcyQ== X-Gm-Message-State: AKwxytcFYLygFelRbniY53mklKtjW/Ae1LPGEzZ8PPYoX6sD2wpsdbwg 5wwxs0pJBS7ZHovVYrc7p7sCq7eZ5R0X+N78dL8= X-Google-Smtp-Source: ACJfBosKNEBqmIJq1ldhAgvUasA6izLrgv3c53y6zyaaHpCXbYbURaMqu4WkVW6zyT6ZDFoB8QTRA+hKCXdh8G/GtFw= X-Received: by 10.107.137.232 with SMTP id t101mr17870818ioi.230.1515594624433; Wed, 10 Jan 2018 06:30:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.86.72 with HTTP; Wed, 10 Jan 2018 06:30:23 -0800 (PST) In-Reply-To: <3zGnrf2wGvz3jYpX@baobab.bilink.it> References: <3zGnrf2wGvz3jYpX@baobab.bilink.it> From: Adam Vande More Date: Wed, 10 Jan 2018 08:30:23 -0600 Message-ID: Subject: Re: 10.4 RELEASE sees only one core To: Luciano Mannucci Cc: FreeBSD Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 14:30:25 -0000 On Wed, Jan 10, 2018 at 6:10 AM, Luciano Mannucci wrote: > > Hello, > > I have an Intel 2 CPU with Intel Xeon E5410, that should be quad core, > no hyperthread. I expect to see 8 CPUs, though I get: > > root@baobab:~ # dmesg | head -33 > Copyright (c) 1992-2017 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 10.4-RELEASE #0 r324094: Fri Sep 29 01:45:44 UTC 2017 > root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 > CPU: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz (2327.55-MHz K8-class > CPU) > Origin="GenuineIntel" Id=0x10676 Family=0x6 Model=0x17 Stepping=6 > Features=0xbfebfbff APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI, > MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > Features2=0xce3bd CX16,xTPR,PDCM,DCA,SSE4.1> > AMD Features=0x20100800 > AMD Features2=0x1 > VT-x: (disabled in BIOS) HLT,PAUSE > TSC: P-state invariant, performance statistics > real memory = 17179869184 (16384 MB) > avail memory = 16559685632 (15792 MB) > Event timer "LAPIC" quality 400 > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > FreeBSD/SMP: 2 package(s) x 1 core(s) > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 4 > > Is it normal? > I'm running: > > root@baobab:~ # freebsd-version > 10.4-RELEASE-p5 > > What should I do? > > Thanks to all, > I think 11.x is better at this but: https://lists.freebsd.org/pipermail/freebsd-current/2014-May/050353.html -- Adam From owner-freebsd-questions@freebsd.org Wed Jan 10 14:59:56 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 556E8E604CB for ; Wed, 10 Jan 2018 14:59:56 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1F3DD78908 for ; Wed, 10 Jan 2018 14:59:56 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by mail-it0-x230.google.com with SMTP id d137so16515648itc.2 for ; Wed, 10 Jan 2018 06:59:56 -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=7y332/hCKTNiU1Tn4B8Y3Hr4lbpiYjcziXdUVHyh/EQ=; b=L5NF9zwT6CUZlHnAFTJR+n5f6l+avhRBEhWRRdC7NlpFdwjfMEeXlG6Ewk0ek7wfY1 +UMsBRjWDP8kM4fQADd89bVioUFqf6RntEF2JhXfV7QgMNWCTtRzCBMk9mnrUwuSBYKm eqvc9AAhkuKB2TOS9GUt1fOxfH2gIf9t8lVwr0oPcIAdO1+Y97/v0pvaG+WCIR/c0BC5 3HMXHbZf0rLCEhGtVnqd30zIOcGgBOn6CDRDic5O5VMf7rCPEluSA752MgtjoE/56qsO GWbce5nV8Uq6AFl2l1AUHkr8ryPcxsi67Z/qqFJu3niRS6TDvPokI+hjLwzPK1WjeEyk rfEg== 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=7y332/hCKTNiU1Tn4B8Y3Hr4lbpiYjcziXdUVHyh/EQ=; b=mIAeulgu0jK3bAiJEoTqPn2UOGRJOn3sgZYelFVg9CiLBSoFbVy2jy7+vLF57y5zrS U1fLet+Tm3KdVD4JZF0Pv9+y5/2h4tRfQq2wWm0MAsx/jq8CNgYJM6ErXjQ1gry6z+pf Wd1zKwrFqydnSm65jPxvo9ZgZjXZWTDYprHDkwceS0402vouuF3/zAep8V+343Zr+OZW qURQDxpoWgsVY0Dea3v7XGx+EV73+6k4BOBzgfArzCr0nJaNO1fB6Ef+7Ajn65afbXEj k6p9QqYqwSZmLqiCQ7xYA11jyqJY8GolCtbuHVdyvC1QwwGPGWZThEUrS1c7FBWhH6pl fyQQ== X-Gm-Message-State: AKGB3mJ8zGMI04hBHLZKrvsfpWEIT6LBinfQUKwSa16S68OdKOYTkxAk Nat04MB5xvNWP0RhjWQLz+qzNlOuw6Vh0f6eF143ng== X-Google-Smtp-Source: ACJfBosnXb6WsFKaBE1wSejYIAxPj8uVTvfavfRh2CtyXmnrfo3EtiuRPGgsbEBFH7iFP8VU9/CRJN9/rpu8Ms7MGWM= X-Received: by 10.36.37.209 with SMTP id g200mr20328228itg.152.1515596395415; Wed, 10 Jan 2018 06:59:55 -0800 (PST) MIME-Version: 1.0 Received: by 10.36.105.3 with HTTP; Wed, 10 Jan 2018 06:59:54 -0800 (PST) From: Aryeh Friedman Date: Wed, 10 Jan 2018 09:59:54 -0500 Message-ID: Subject: OT: Max system physical memory To: FreeBSD Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 14:59:56 -0000 My computer (HP Pavilion P7-1234, FreeBSD 11.1-RELEASE [amd64]) has 2 240 pin DIMM (DDR3, PC3-10600) the manual says the max memory is 8 GB but I see some 16 GB packages (2x8GB). If I put one or two of these in will it see the extra memory? -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-questions@freebsd.org Wed Jan 10 15:30:59 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3C894E62254 for ; Wed, 10 Jan 2018 15:30:59 +0000 (UTC) (envelope-from katie.sadowske@accudbpro.com) Received: from IND01-BO1-obe.outbound.protection.outlook.com (mail-bo1ind01on0087.outbound.protection.outlook.com [104.47.101.87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT TLS CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5F83379D17 for ; Wed, 10 Jan 2018 15:30:57 +0000 (UTC) (envelope-from katie.sadowske@accudbpro.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=NETORGFT3485838.onmicrosoft.com; s=selector1-accudbpro-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ZAyhABh9vmmNQry9LBZwaFvOP8bnciEtUx5U8tpojD4=; b=RPAt2VgbUfnSbO+ws+okTUdOHvMlrS1HuPAFXDclCZFFaovc3EC9GceLjYOduNAtzRfDkIfzGd9q7UsNgXTFt4kB6dYLv1c1Ozilj3W0lM93JMD5zvZH8gN+hz03vFUACqCom196bqS5gSHiwpEJ5/mjdX/GKoMA+AomqCxcMjQ= Received: from MA1PR0101MB1815.INDPRD01.PROD.OUTLOOK.COM (52.134.142.144) by MA1PR0101MB1813.INDPRD01.PROD.OUTLOOK.COM (52.134.142.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.366.8; Wed, 10 Jan 2018 15:30:54 +0000 Received: from MA1PR0101MB1815.INDPRD01.PROD.OUTLOOK.COM ([fe80::a923:569c:100:a3d8]) by MA1PR0101MB1815.INDPRD01.PROD.OUTLOOK.COM ([fe80::a923:569c:100:a3d8%15]) with mapi id 15.20.0366.011; Wed, 10 Jan 2018 15:30:55 +0000 From: Katie Sadowske To: "freebsd-questions@freebsd.org" Subject: Microsoft Azure Users List Thread-Topic: Microsoft Azure Users List Thread-Index: AdOKJ4jBEf5PJoaCQpGLmS9C/BCssg== Importance: high X-Priority: 1 Date: Wed, 10 Jan 2018 15:29:02 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=katie.sadowske@accudbpro.com; x-originating-ip: [49.207.52.153] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; MA1PR0101MB1813; 7:yc7rCjnKRDOQVi7+VTvmDXWu5TfpqNCoxY6mW+Mk7K3JRHPCEVgzjetByn4cQ9SdUKXQ6ObNX2HCEyFkyV9ftCPGgKxGzfBT1s28spP9/o4lgN2jHUAmjeAIrw24XWCjkBvuqU4oz/kGwenXmOzTM1UyaMCLSVTI75kGqkEgpaKBzCiQ8iZYkDglAnzNpqR4A8z0H45xm12K05PJHX5sIpAp0/76Be2X62EYakj0BA3858qGqI9z+N0IBm0ix1Ju x-ms-office365-filtering-correlation-id: d5b7320a-6a0c-446b-4278-08d5583f23e6 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(4534020)(4602075)(4603075)(7168020)(4627115)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:MA1PR0101MB1813; x-ms-traffictypediagnostic: MA1PR0101MB1813: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(28532068793085)(21748063052155); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040470)(2401047)(5005006)(8121501046)(93006095)(93001095)(3002001)(3231023)(2017060905117)(944501075)(10201501046)(6041268)(20161123564045)(20161123562045)(2016111802025)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123558120)(6072148)(6043046)(201708071742011); SRVR:MA1PR0101MB1813; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:MA1PR0101MB1813; x-forefront-prvs: 0548586081 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(39850400004)(376002)(39380400002)(366004)(346002)(47530400004)(189003)(199004)(2501003)(5630700001)(8676002)(55236004)(81166006)(33656002)(6506007)(8936002)(99286004)(7696005)(53936002)(81686011)(2906002)(790700001)(81156014)(3846002)(3660700001)(6116002)(97736004)(3280700002)(5250100002)(66066001)(316002)(6916009)(54896002)(6666003)(45080400002)(52230400001)(55016002)(86362001)(626008)(68736007)(6436002)(9686003)(478600001)(5640700003)(106356001)(7736002)(3480700004)(5660300001)(6306002)(2900100001)(102836004)(105586002)(25786009)(2351001)(14454004)(74316002)(19870200002); DIR:OUT; SFP:1101; SCL:1; SRVR:MA1PR0101MB1813; H:MA1PR0101MB1815.INDPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: accudbpro.com does not designate permitted sender hosts) x-microsoft-antispam-message-info: FHPRb3AqZexcHOCI2fX0vCorU5tXOAuhy/J5BAkEHrO5bJz5YVhxyxD9PayJ0++e/6Kfyd8pDryvLMTHnT3A6Q== spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: accudbpro.com X-MS-Exchange-CrossTenant-Network-Message-Id: d5b7320a-6a0c-446b-4278-08d5583f23e6 X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jan 2018 15:29:02.6573 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: df12b867-6ad1-4afc-9c76-84e279b5179c X-MS-Exchange-Transport-CrossTenantHeadersStamped: MA1PR0101MB1813 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 15:30:59 -0000 Hello Good Day, I would like to know if you are interested in acquiring Microsoft Azure Use= rs List. Information fields: Names, Title, Email, Phone, Company Name, Company URL, = Company physical address, SIC Code, Industry, Company Size (Revenue and Emp= loyee). Let me know if you are interested and I will get back to you with the count= s and price list Regards, Katie Sadowske:) Data Consultant If you don't wish to receive emails from us reply back stati= ng "REMOVE" From owner-freebsd-questions@freebsd.org Wed Jan 10 15:38:12 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D7D44E628D0; Wed, 10 Jan 2018 15:38:12 +0000 (UTC) (envelope-from v.dol_s@hotmail.com) Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-ve1eur02olkn082e.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe06::82e]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5467A7A2C2; Wed, 10 Jan 2018 15:38:12 +0000 (UTC) (envelope-from v.dol_s@hotmail.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=NAxthpABshJXBCGzbTU/ej7I8UKibhlzoxZJ+dPpTgs=; b=OtHxsEam9DkWrS3bImM9KInbYZ6YLGIo6VSoNgfo8i+VOC9ZOwUuc5N14OAhYKEwdTFjttEueHdtXYTwApx7JnN34pk527xmjR0FK9VjIpY39dEKpMWJhcVajriMqE/theq4Q8qxh4ruF1S8ok2mB+zV/H0sCvX478qqaQhJ8AI+aPRBkwpyXr6b7k+MnAN5tgOhc6jtZ0QO/j7M9xV4ImFfyfImqYP6LwCHnGt0cpiOppG9C6sz+zHViJZydpbkQrKfPnqIHUabIbNuEMsNHN5GAgUcvgYufaeKahJcf+iyQbVNaohB5r49pv7B8iQqxBjfXE01hoxTW4YW0VR6dw== Received: from VE1EUR02FT048.eop-EUR02.prod.protection.outlook.com (10.152.12.52) by VE1EUR02HT201.eop-EUR02.prod.protection.outlook.com (10.152.12.201) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.345.12; Wed, 10 Jan 2018 15:38:10 +0000 Received: from AM5PR0902MB1923.eurprd09.prod.outlook.com (10.152.12.51) by VE1EUR02FT048.mail.protection.outlook.com (10.152.13.177) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.345.12 via Frontend Transport; Wed, 10 Jan 2018 15:38:09 +0000 Received: from AM5PR0902MB1923.eurprd09.prod.outlook.com ([fe80::e4a7:bead:3f27:7fd8]) by AM5PR0902MB1923.eurprd09.prod.outlook.com ([fe80::e4a7:bead:3f27:7fd8%13]) with mapi id 15.20.0386.008; Wed, 10 Jan 2018 15:38:09 +0000 From: Vitalio D To: Yuri Pankov , Matthias Apitz CC: "freebsd-questions@freebsd.org" , "owner-freebsd-questions@freebsd.org" Subject: Re: where to find exit(int) function implementation Thread-Topic: where to find exit(int) function implementation Thread-Index: AQHTihKQe0z8Ge0DZk6xf6VVVCNQPKNtFj4AgAAJTYCAABQysA== Date: Wed, 10 Jan 2018 15:38:09 +0000 Message-ID: References: <59cdf69e792d5c723fa919abac1d67b6@webmail.1blu.de>, <8ef73fb7-dc2f-2fcb-f8e6-e7de02a66b64@gmx.com> In-Reply-To: <8ef73fb7-dc2f-2fcb-f8e6-e7de02a66b64@gmx.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-incomingtopheadermarker: OriginalChecksum:562FF8AEF605CB9DC76861AFD6EF2C7B078D59CB87134A03067BAD6EC897F33C; UpperCasedChecksum:C9ADE439B72CFA67D1A7E668FA6A90F0DB5396382A9C2A75577B857C7D3B6EE0; SizeAsReceived:7342; Count:47 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [OGvm6K1/HPZ+UEHRAIlQuDPXDuhCPnjD] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; VE1EUR02HT201; 6:/z2UJuhPNwotR2JwGPWmIgdQe0BijLiR5i1O2HJM6YuaBOx7wU+WqG7Xe1IbBOU1qM9znwY2A0b0N9FPfZDh/bmVTbvl8AulnjHsJZfTh0W6eTFTVAx5IRanTZ8dp2ptQEBqpe/HjPGkzW8bXQVdlikBMkwKqVy3PxLbWPWuXCVb1Wtv7aBFCtik1Z/1uo89nnr8sp+FUKukxs0oiiECco29/nejMdk/md+FOsqI8lXcOzZtaFBTGfFTAUjmxFFleGX9HI43CB65V0rLHSY+t6EndHcFazPz3+u6DRxNXbLx46qP1CuapnFaEKTMRgrD1MPM1g1sQsCc4dNBK2yL5jcEmTAt/pavwsVbz1hBmfk=; 5:yVdBirQW0pZqlJs7oGcbP3pTyXCWRi/Ow6dYWHHpAoVXZvaKF4s+HL+iwqLFaWHSXZX1HAzVrp9M8vuoi6jmyjooUPg8N/csxlCgOIJlxBPcGHPm9Zx9ALjDvKP0nJmkgn1hw04zTUe+Klbncab0cfT8fV4x9gxITvd2Y/zylrs=; 24:1Agzkoqwf9SIkCTWnfBj2NFfYJv9WNtPlbku+H0EFBvOBPClYxUXd9qi3MwZLtQp24eygS2YJpZ6fCs6/Q3L5M+y8hHjVUnQPoVg3ha4iUg=; 7:LjdJqJjQ5zkgwHnF/YhnIkksssoahmyGvd2PXAh7ztfHXk2G/iiIct04tMV4kVKzhqE9eGhrSqOsiISHfScJY0J1tUq2DCcQ+oCVe/QmGRRuSdjDWcCkaXskUFkwt/hYfsCxnS/CUb55jdn/4Psq8quU9zvDrh2dZIJVyyshnjFKkK/uNlnYabJeA4yBQh/RwfeifRFHw73azxlqVvzBNPArTR2auoNHk3DdLAuf8m/IOd5r56AhUeByzULhMG2+ x-incomingheadercount: 47 x-eopattributedmessage: 0 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1601125374)(1603101448)(1701031045); SRVR:VE1EUR02HT201; x-ms-traffictypediagnostic: VE1EUR02HT201: x-ms-office365-filtering-correlation-id: 8e44c927-a2d0-4bac-492d-08d5584026ff x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:VE1EUR02HT201; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:VE1EUR02HT201; x-forefront-prvs: 0548586081 x-forefront-antispam-report: SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:VE1EUR02HT201; H:AM5PR0902MB1923.eurprd09.prod.outlook.com; FPR:; SPF:None; LANG:; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: hotmail.com X-MS-Exchange-CrossTenant-Network-Message-Id: 8e44c927-a2d0-4bac-492d-08d5584026ff X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jan 2018 15:38:09.7584 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1EUR02HT201 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 15:38:12 -0000 Hello, =0A= Indeed I'm interested in _exit syscall.=0A= =0A= Thanks for response Yuri, but i'm a newbie and don't=0A= see any PSEUDO marking in unistd.h at least.=0A= What i see in unisrd.h is =0A= =0A= ...=0A= __BEGIN_DECLS=0A= /* 1003.1-1990 */=0A= void _exit(int) __dead2;=0A= ...=0A= =0A= __BEGIN_DECLS being defined in sys/sys/cdefs.h as exten "C" {=0A= but no PSEUDO. Am i missing something?=0A= =0A= Regards,=0A= ________________________________________=0A= From: Yuri Pankov =0A= Sent: Wednesday, January 10, 2018 14:49=0A= To: Matthias Apitz; Vitalio D=0A= Cc: freebsd-questions@freebsd.org; owner-freebsd-questions@freebsd.org=0A= Subject: Re: where to find exit(int) function implementation=0A= =0A= On Wed, Jan 10, 2018 at 02:16:16PM +0100, Matthias Apitz:=0A= > Am 10.01.2018 14:01, schrieb Vitalio D:=0A= >> Hello,=0A= >>=0A= >> How and where void _exit(int) is implemented? I've started=0A= >> with exit(int) defined in exit.c un stdlib, but I've got stuck at=0A= >> unistd.h where void _exit(int) __dead2;=0A= >> After that I couldn't find anything by running=0A= >> find /usr/src -name "*.c" -exec grep " _exit(int" /dev/null {} \;=0A= >=0A= > $ find /usr/src -name *.c | grep exit=0A= > /usr/src/sys/kern/kern_exit.c=0A= > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_onexit.c=0A= > /usr/src/lib/libc/arm/aeabi/aeabi_atexit.c=0A= > /usr/src/lib/libc/stdlib/cxa_thread_atexit.c=0A= > /usr/src/lib/libc/stdlib/cxa_thread_atexit_impl.c=0A= > /usr/src/lib/libc/stdlib/exit.c=0A= > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=0A= =0A= The original question was about _exit(2) syscall, not exit(3).=0A= =0A= WRT the _exit(2), it's marked as "PSEUDO" and relevant PSEUDO macro is=0A= defined in lib/libc//SYS.h (if I'm reading it all correctly).=0A= From owner-freebsd-questions@freebsd.org Wed Jan 10 15:59:27 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 673BCE6423A for ; Wed, 10 Jan 2018 15:59:27 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from baobab.bilink.net (baobab.bilink.net [212.45.144.44]) by mx1.freebsd.org (Postfix) with ESMTP id 2C0E87B7B2 for ; Wed, 10 Jan 2018 15:59:26 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from baobab (localhost [127.0.0.1]) by baobab.bilink.it (Postfix) with ESMTP id 3zGtx90Nt2z3jZ4R for ; Wed, 10 Jan 2018 16:59:25 +0100 (CET) X-Virus-Scanned: amavisd-new at mcs.it Received: from baobab.bilink.net ([127.0.0.1]) by baobab (baobab.mcs.it [127.0.0.1]) (amavisd-new, port 11027) with ESMTP id TCOzDJjxf-je for ; Wed, 10 Jan 2018 16:59:24 +0100 (CET) Received: from hermes.mcs.it (unknown [192.168.132.21]) by baobab.bilink.it (Postfix) with ESMTP id 3zGtBY1tjWz3jYyh for ; Wed, 10 Jan 2018 16:25:57 +0100 (CET) Received: from mordeus (unknown [192.168.45.6]) by hermes.mcs.it (Postfix) with ESMTP id 26A681B7431 for ; Wed, 10 Jan 2018 16:25:57 +0100 (CET) Date: Wed, 10 Jan 2018 16:25:56 +0100 From: Luciano Mannucci To: freebsd-questions@freebsd.org Subject: Re: 10.4 RELEASE sees only one core In-Reply-To: References: <3zGnrf2wGvz3jYpX@baobab.bilink.it> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; amd64-portbld-freebsd10.3) X-Face: 4qPv4GNcD; h<7Q/sK>+GqF4=CR@KmnPkSmwd+#%\F`4yjKO3"C]p'z=(oWRnsYBQGM\5g:4skqQY0NnV'dM:Mm:^/_+I@a"; [-s=ogufdF"9ggQ'=y MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <3zGtBY1tjWz3jYyh@baobab.bilink.it> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 15:59:27 -0000 On Wed, 10 Jan 2018 08:30:23 -0600 Adam Vande More wrote: > I think 11.x is better at this but: Why? The Xeon E5410 went End Of Life in Q4 2010. Maybe the 9.something looks more apropriate... :) BTW, thanks I've missed that: > https://lists.freebsd.org/pipermail/freebsd-current/2014-May/050353.html tough I have only 8 cores in total, which seems to me way under 64. Interestingly, acpidump -d sees them: root@baobab:~ # acpidump -d | less /* * Intel ACPI Component Architecture * AML/ASL+ Disassembler version 20160527-64 * Copyright (c) 2000 - 2016 Intel Corporation * * Disassembling to symbolic ASL+ operators * * Disassembly of /tmp/acpidump.C4f1lO/acpdump.din, Wed Jan 10 16:24:27 2018 * * Original Table Header: * Signature "DSDT" * Length 0x00006473 (25715) * Revision 0x02 * Checksum 0xB9 * OEM ID "INTEL " * OEM Table ID "S5400SF " * OEM Revision 0x00000008 (8) * Compiler ID "INTL" * Compiler Version 0x01000013 (16777235) */ DefinitionBlock ("", "DSDT", 2, "INTEL ", "S5400SF ", 0x00000008) { Scope (\_PR) { Processor (CPU0, 0x00, 0x00000410, 0x06) {} Processor (CPU1, 0x01, 0x00000410, 0x06) {} Processor (CPU2, 0x02, 0x00000410, 0x06) {} Processor (CPU3, 0x03, 0x00000410, 0x06) {} Processor (CPU4, 0x04, 0x00000410, 0x06) {} Processor (CPU5, 0x05, 0x00000410, 0x06) {} Processor (CPU6, 0x06, 0x00000410, 0x06) {} Processor (CPU7, 0x07, 0x00000410, 0x06) {} } or so I guess... thanks again, Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster@sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/ From owner-freebsd-questions@freebsd.org Wed Jan 10 16:48:24 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1357EE66E4C for ; Wed, 10 Jan 2018 16:48:24 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D648E7DB06 for ; Wed, 10 Jan 2018 16:48:23 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by mail-it0-x231.google.com with SMTP id x42so120728ita.4 for ; Wed, 10 Jan 2018 08:48:23 -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=aVVwjUAf6wZs6O/TdCLb2giGrZo5ytnkkchWDH72o7w=; b=lWaTSqmbn9RDGt0tQchdX+CST6D0ZK10kpvL4rUujG993aEmWxjUbTBCHpQGYm+/Go f9cNXu3PMLyt/EA2o8FtaE6Uj1rWBKD7q0Y+7FYpuTKuKav3vCX7I5HPUVIHbksbkJmL 0axi6chCKEuEyaUrIYmjlOmf6beGp0PXxdpw1hXh/NpWRJZ0jFAAzXgsK/qU0Mz+w0mf FS1E5wvTh4ENKuKiSsyj49SKQq859mTZiIcL37j0O58JI7r2wYjUMKbHHwrNLOB2il9+ DDax0F0UK1CLqxFO5W13+8+Ao3oxFQV802KB6/Gv+LqLsGlYYaQ/IGIgiwi66be7PX8x 1qCw== 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=aVVwjUAf6wZs6O/TdCLb2giGrZo5ytnkkchWDH72o7w=; b=MZoykrZu4y1qyFCKs0d3DJrwNKmz2yFCnI6kl8ZZ/K+uuJPzh2MjSB5JNoP/EbXkSV l07997fAYOjaQA+VhgpRI3WzUgG1w+YuqsewEHofLH3WnKvuN+xHImqW+Kr+JGqaOPM4 lH8PrgyuBaYF/lBKtAW7BKjQrKnQjUXU73wCgCFBS8I/w4PgPOrxrW+NALL/QyTd1uy6 tYazgDzH7prXmFVAc30sLDLZQ6cbYV5mCRhj7+YLMstAwtlX5qra7p1UymxO/b76fRc8 f2gK4f0g9qi1r8Zaz8t7FfQSFDlajU1n7EXgeaSk4weITjsegIJ1LHLNrbyySPLbMmuO zVRA== X-Gm-Message-State: AKGB3mK0lTb7eqtWJaFhMz2RfL1OfnK5G14iibhBNO/DwZnexEDjF+3M Fd+c+hKMsRpuWPY+9RIuQq5bNx52t81vKjFZDBY= X-Google-Smtp-Source: ACJfBoszsc3g9DKJ/QMPf3X3m8jrrmqI8FeqZ6Fc3c5XWNGoXvw3DGyrNL+jRpDKdNFhXRTleuYAzNelqKDxJoSiFXk= X-Received: by 10.36.138.134 with SMTP id v128mr20009269itd.153.1515602903036; Wed, 10 Jan 2018 08:48:23 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.86.72 with HTTP; Wed, 10 Jan 2018 08:48:22 -0800 (PST) In-Reply-To: <3zGtBY1tjWz3jYyh@baobab.bilink.it> References: <3zGnrf2wGvz3jYpX@baobab.bilink.it> <3zGtBY1tjWz3jYyh@baobab.bilink.it> From: Adam Vande More Date: Wed, 10 Jan 2018 10:48:22 -0600 Message-ID: Subject: Re: 10.4 RELEASE sees only one core To: Luciano Mannucci Cc: FreeBSD Questions Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 16:48:24 -0000 On Wed, Jan 10, 2018 at 9:25 AM, Luciano Mannucci wrote: > On Wed, 10 Jan 2018 08:30:23 -0600 > Adam Vande More wrote: > > > I think 11.x is better at this but: > Why? The Xeon E5410 went End Of Life in Q4 2010. Maybe the 9.something > looks more apropriate... :) > It has nothing do with your CPU which in and of itself is fully supported in 10.x > BTW, thanks I've missed that: > > https://lists.freebsd.org/pipermail/freebsd-current/2014-May/050353.html > > tough I have only 8 cores in total, which seems to me way under 64. > I think you assume too much by taking the var name literally. -- Adam From owner-freebsd-questions@freebsd.org Wed Jan 10 18:01:12 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C8BB1E6BA43 for ; Wed, 10 Jan 2018 18:01:12 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 29307823FB for ; Wed, 10 Jan 2018 18:01:11 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.18.98]) by mrelayeu.kundenserver.de (mreue105 [212.227.15.183]) with ESMTPA (Nemesis) id 0M1ohG-1esefZ1KAM-00tgTu; Wed, 10 Jan 2018 18:55:55 +0100 Date: Wed, 10 Jan 2018 18:55:55 +0100 From: Polytropon To: Arthur Chance Cc: Dave B , freebsd-questions@freebsd.org Subject: Re: 32 bit fix? (Was Re: Meltdown =?UTF-8?Q?=E2=80=93?= Spectre) Message-Id: <20180110185555.99326d8d.freebsd@edvax.de> In-Reply-To: <49785edc-1ac4-48f3-bff0-19704dadc70b@qeng-ho.org> References: <2e86bfd9-9141-2872-1946-0e9d26326433@googlemail.com> <6523f352-c895-e488-8006-76495907745a@googlemail.com> <49785edc-1ac4-48f3-bff0-19704dadc70b@qeng-ho.org> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:WcO2+BXVg+ZvgAgZX0rHOBEspGAhFPPzLnaAKIneQtXPrT8XpOU r4/yHrCMug3Izk1kkF1SBvgGUTUEV2xlJ+1ytFZtN3d7meGChhvYepT1jsPj0krqWPb4wzr vNxcjRrNPKUNxYMu1DY9NO8sNvjKo6SfBNj7EaxAhNzvkOEIYU1QnT/I6a0ZlQNH5u/iS3+ V+l7o5mpY1mHqAt5U85Jw== X-UI-Out-Filterresults: notjunk:1;V01:K0:ysHXu+sipj0=:mXWVhxpbFR0T5nL2Nrtbi5 bKT+NpJ4NBU4nc6FDS33cwpubdNdjihrvmIzm86C3J+hhBIQI8u+tyVnx3CgyfJTkS0hLRS1z XRcnQG8xOA1IqpIQ0DIxRgMCibby9pu18BUBfJXywgTtMSQnUuhgwofaQeDe1uDKXd2pQIUuy TtR4H7p0oPAPq+wJ/+fqfMd5OCxqFzatr0FdgcMb5YjF0ZrYTWdGq4fqOmLYDQU6/jSk1lQa+ 8ZjdQXxBeOvOFetHngY0fUoIhB5Xj6EX1Or0V/hGj2BIdwh6EtjtyHk/lE0OOjqQSfiXhz9sk RWRrXJ69ESnFBFZvq5gvm57Fws8GjeAmshUWJApEjlSzTnbhd2lSYG9MFcSOCKVVjhw7AWKAg qh4VJZZ/lmrPyoPNXPZlCCIP4CdKpsiqdwEhf7gi6WxVkKopF/INC1FFZgkjUhgkkb549sEPV CRyCzZvMVbaOulspnmOqj/A1fcl/MZQi5IdYVoIgg3vwOo85mBjICR5I1+sAecj5on3DhBugK /K8XCj08QBAmkIfjCdp19Fy+BOhnWLXFjDYbazdyXIzDC6FEqE9sjYLi60YxN9W+GgdZML8nt g/g6IfoZ1+uSWi5OAcD5O5cUQsxV/qmwsGjeGY1ZdYMU9u+KastHlSu7g35+8fwxYmGmuZHZt qCblrR9nz7HovmxDjD3nre9fmdsY2Ftc3tE84NYV3lu/mOeYL8e837lEhkQZVQYncl2Wp4FZz cL6dqM4aYQywodK1VGD6OCLHXffj4Jl3sD1pGuWeu1E4LUIdj2nCkcA02yQ= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 18:01:12 -0000 On Wed, 10 Jan 2018 11:23:43 +0000, Arthur Chance wrote: > I can't find the article I was reading right now, but it said Intel > chips became vulnerable when the Westmere architecture (the 32 nm > version of Nehalem) was introduced back in 2010. That was the early days > of the Core i[357] CPUs, so Core and Core 2 CPUs are probably too old to > be affected. I'm not entirely sure about that. As we're basically talking about two types of vulnerability here, I seem to remember that one of them also affects "old enough" CPUs from the Pentium 4 era (before Core), in other words, when "HyperThreading" or "HT Technology" arrived in Intel chips. But I'm not convenced that I remember correctly. Further investigation should help. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Wed Jan 10 18:25:29 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 158A4E6D158 for ; Wed, 10 Jan 2018 18:25:29 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from baobab.bilink.net (baobab.bilink.net [212.45.144.44]) by mx1.freebsd.org (Postfix) with ESMTP id CE3F683642 for ; Wed, 10 Jan 2018 18:25:28 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from baobab (localhost [127.0.0.1]) by baobab.bilink.it (Postfix) with ESMTP id 3zGy9g41j7z3jYkh for ; Wed, 10 Jan 2018 19:25:27 +0100 (CET) X-Virus-Scanned: amavisd-new at mcs.it Received: from baobab.bilink.net ([127.0.0.1]) by baobab (baobab.mcs.it [127.0.0.1]) (amavisd-new, port 11027) with ESMTP id hMI3oAC08udP for ; Wed, 10 Jan 2018 19:25:27 +0100 (CET) Received: from hermes.mcs.it (unknown [192.168.132.21]) by baobab.bilink.it (Postfix) with ESMTP id 3zGy9g2yw5z3jYkD for ; Wed, 10 Jan 2018 19:25:27 +0100 (CET) Received: from mordeus (unknown [192.168.45.6]) by hermes.mcs.it (Postfix) with ESMTP id 50E351B72F4 for ; Wed, 10 Jan 2018 19:25:27 +0100 (CET) Date: Wed, 10 Jan 2018 19:25:27 +0100 From: Luciano Mannucci To: freebsd-questions@freebsd.org Subject: Re: 10.4 RELEASE sees only one core (Solved) In-Reply-To: <3zGnrf2wGvz3jYpX@baobab.bilink.it> References: <3zGnrf2wGvz3jYpX@baobab.bilink.it> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; amd64-portbld-freebsd10.3) X-Face: 4qPv4GNcD; h<7Q/sK>+GqF4=CR@KmnPkSmwd+#%\F`4yjKO3"C]p'z=(oWRnsYBQGM\5g:4skqQY0NnV'dM:Mm:^/_+I@a"; [-s=ogufdF"9ggQ'=y MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <3zGy9g2yw5z3jYkD@baobab.bilink.it> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 18:25:29 -0000 On Wed, 10 Jan 2018 13:10:10 +0100 Luciano Mannucci wrote: > I have an Intel 2 CPU with Intel Xeon E5410, that should be quad core, > no hyperthread. I expect to see 8 CPUs, though I get: It was disabled in the bios setup. Sorry for the noise, Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster@sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/ From owner-freebsd-questions@freebsd.org Wed Jan 10 18:28:22 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 13974E6D53D for ; Wed, 10 Jan 2018 18:28:22 +0000 (UTC) (envelope-from do-not-reply@yahoo.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id EE6EA839F8 for ; Wed, 10 Jan 2018 18:28:21 +0000 (UTC) (envelope-from do-not-reply@yahoo.com) Received: by mailman.ysv.freebsd.org (Postfix) id EDB7EE6D53C; Wed, 10 Jan 2018 18:28:21 +0000 (UTC) Delivered-To: questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ED508E6D53B for ; Wed, 10 Jan 2018 18:28:21 +0000 (UTC) (envelope-from do-not-reply@yahoo.com) Received: from sonic332-19.consmr.mail.bf2.yahoo.com (sonic332-19.consmr.mail.bf2.yahoo.com [74.6.130.145]) (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 ACB76839F6 for ; Wed, 10 Jan 2018 18:28:21 +0000 (UTC) (envelope-from do-not-reply@yahoo.com) Received: from sonic.gate.mail.ne1.yahoo.com by sonic332.consmr.mail.bf2.yahoo.com with HTTP; Wed, 10 Jan 2018 18:28:20 +0000 From: "Reverend. SisterMary" To: questions@freebsd.org Message-ID: <1460017074.2486611.1515608898023.JavaMail.yahoo@tardis008.cal.bf1.yahoo.com> Subject: Invitation: Good day,This is Reverend Sister Mary Thomas, @ Wednesday, 10 January 2018 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Wed, 10 Jan 2018 18:28:22 -0000 X-List-Received-Date: Wed, 10 Jan 2018 18:28:22 -0000 From owner-freebsd-questions@freebsd.org Wed Jan 10 19:47:46 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 01CEAE7287D for ; Wed, 10 Jan 2018 19:47:46 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [IPv6:2607:f3e0:80:80::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D3CE76831A for ; Wed, 10 Jan 2018 19:47:45 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (lava.sentex.ca [IPv6:2607:f3e0:0:5::11]) by smarthost2.sentex.ca (8.15.2/8.15.2) with ESMTPS id w0AJliD1002641 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Wed, 10 Jan 2018 14:47:44 -0500 (EST) (envelope-from mike@sentex.net) Received: from [192.168.43.26] (saphire3.sentex.net [192.168.43.26]) by lava.sentex.ca (8.15.2/8.15.2) with ESMTP id w0AJlgUF070669 for ; Wed, 10 Jan 2018 14:47:42 -0500 (EST) (envelope-from mike@sentex.net) To: freebsd-questions From: Mike Tancsa Subject: mmcsd / sdhci_pci errors Organization: Sentex Communications Message-ID: Date: Wed, 10 Jan 2018 14:47:44 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.78 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 19:47:46 -0000 On a couple of PCEngines APU2 and APU3 boxes, I have been having errors on the SD cards when I try to write to them after about a day. If I reboot, mount the sd card rw, make some changes and then remount the card ro, all is fine. Then the next day if I try and do it again, I get errors of this sort below. Is that a bad card ? Bug ? sdhci_pci0-slot0: =========================================== g_vfs_done():mmcsd0s1a[READ(offset=994430976, length=4096)]error = 5 sdhci_pci0-slot0: Got AutoCMD12 error 0x0001, but there is no active command. sdhci_pci0-slot0: ============== REGISTER DUMP ============== sdhci_pci0-slot0: Sys addr: 0x050bd000 | Version: 0x00001001 sdhci_pci0-slot0: Blk size: 0x00000200 | Blk cnt: 0x00000008 sdhci_pci0-slot0: Argument: 0x001e085f | Trn mode: 0x00000037 sdhci_pci0-slot0: Present: 0x01ef0000 | Host ctl: 0x00000007 sdhci_pci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci_pci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000007 sdhci_pci0-slot0: Timeout: 0x0000000d | Int stat: 0x00000000 sdhci_pci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00f3 sdhci_pci0-slot0: AC12 err: 0x00000001 | Host ctl2:0x00000080 sdhci_pci0-slot0: Caps: 0x21fe32b2 | Caps2: 0x00000070 sdhci_pci0-slot0: Max curr: 0x00c80064 | ADMA err: 0x00000000 sdhci_pci0-slot0: ADMA addr:0x00000000 | Slot int: 0x000000ff sdhci_pci0-slot0: =========================================== g_vfs_done():mmcsd0s1a[READ(offset=1007689728, length=4096)]error = 5 sdhci_pci0-slot0: Got AutoCMD12 error 0x0001, but there is no active command. sdhci_pci0-slot0: ============== REGISTER DUMP ============== sdhci_pci0-slot0: Sys addr: 0x050bd000 | Version: 0x00001001 sdhci_pci0-slot0: Blk size: 0x00000200 | Blk cnt: 0x00000008 sdhci_pci0-slot0: Argument: 0x001f37d7 | Trn mode: 0x00000037 sdhci_pci0-slot0: Present: 0x01ef0000 | Host ctl: 0x00000007 sdhci_pci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci_pci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000007 sdhci_pci0-slot0: Timeout: 0x0000000d | Int stat: 0x00608000 sdhci_pci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00f3 sdhci_pci0-slot0: AC12 err: 0x00000001 | Host ctl2:0x00000080 sdhci_pci0-slot0: Caps: 0x21fe32b2 | Caps2: 0x00000070 sdhci_pci0-slot0: Max curr: 0x00c80064 | ADMA err: 0x00000000 sdhci_pci0-slot0: ADMA addr:0x00000000 | Slot int: 0x000000ff sdhci_pci0-slot0: =========================================== sdhci_pci0-slot0: g_vfs_done():Got data interrupt 0x00600000, but there is no active command. sdhci_pci0-slot0: mmcsd0s1a[READ(offset=1047465984, length=4096)]error = 5 ============== REGISTER DUMP ============== sdhci_pci0-slot0: Sys addr: 0x050bd000 | Version: 0x00001001 sdhci_pci0-slot0: Blk size: 0x00000200 | Blk cnt: 0x00000008 sdhci_pci0-slot0: Argument: 0x001f37d7 | Trn mode: 0x00000037 sdhci_pci0-slot0: Present: 0x01ef0000 | Host ctl: 0x00000006 sdhci_pci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci_pci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000007 sdhci_pci0-slot0: Timeout: 0x0000000d | Int stat: 0x00000000 sdhci_pci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00f3 sdhci_pci0-slot0: AC12 err: 0x00000001 | Host ctl2:0x00000080 sdhci_pci0-slot0: Caps: 0x21fe32b2 | Caps2: 0x00000070 sdhci_pci0-slot0: Max curr: 0x00c80064 | ADMA err: 0x00000000 sdhci_pci0-slot0: ADMA addr:0x00000000 | Slot int: 0x000000ff sdhci_pci0-slot0: =========================================== sdhci_pci0-slot0: mmcsd0: Got AutoCMD12 error 0x0001, but there is no active command. sdhci_pci0-slot0: ============== REGISTER DUMP ============== sdhci_pci0-slot0: Sys addr: 0x050bd000 | Version: 0x00001001 sdhci_pci0-slot0: Blk size: 0x00000200 | Blk cnt: 0x00000008 sdhci_pci0-slot0: Argument: 0x001f9cff | Trn mode: 0x00000037 sdhci_pci0-slot0: Present: 0x01ef0000 | Host ctl: 0x00000007 sdhci_pci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci_pci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000007 sdhci_pci0-slot0: Timeout: 0x0000000d | Int stat: 0x00608000 sdhci_pci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00f3 sdhci_pci0-slot0: AC12 err: 0x00000001 | Host ctl2:0x00000080 sdhci_pci0-slot0: Caps: 0x21fe32b2 | Caps2: 0x00000070 sdhci_pci0-slot0: Max curr: 0x00c80064 | ADMA err: 0x00000000 sdhci_pci0-slot0: Error indicated: 1 Timeout ADMA addr:0x00000000 | Slot int: 0x000000ff sdhci_pci0-slot0: =========================================== sdhci_pci0-slot0: Got data interrupt 0x00600000, but there is no active command. sdhci_pci0-slot0: ============== REGISTER DUMP ============== sdhci_pci0-slot0: Sys addr: 0x050bd000 | Version: 0x00001001 sdhci_pci0-slot0: Blk size: 0x00000200 | Blk cnt: 0x00000008 sdhci_pci0-slot0: Argument: 0x001f9cff | Trn mode: 0x00000037 sdhci_pci0-slot0: Present: 0x01ef0000 | Host ctl: 0x00000007 sdhci_pci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci_pci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000007 sdhci_pci0-slot0: Timeout: 0x0000000d | Int stat: 0x00000000 sdhci_pci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00f3 sdhci_pci0-slot0: AC12 err: 0x00000001 | Host ctl2:0x00000080 sdhci_pci0-slot0: Caps: 0x21fe32b2 | Caps2: 0x00000070 sdhci_pci0-slot0: Max curr: 0x00c80064 | ADMA err: 0x00000000 sdhci_pci0-slot0: ADMA addr:0x00000000 | Slot int: 0x000000ff sdhci_pci0-slot0: =========================================== g_vfs_done():mmcsd0s1a[READ(offset=1060724736, length=4096)]error = 5 sdhci_pci0-slot0: mmcsd0: Got AutoCMD12 error 0x0001, but there is no active command. sdhci_pci0-slot0: ============== REGISTER DUMP ============== sdhci_pci0-slot0: Sys addr: 0x050bd000 | Version: 0x00001001 sdhci_pci0-slot0: Blk size: 0x00000200 | Blk cnt: 0x00000008 sdhci_pci0-slot0: Error indicated: 1 Timeout Argument: 0x00200227 | Trn mode: 0x00000037 sdhci_pci0-slot0: Present: 0x01ef0000 | Host ctl: 0x00000007 sdhci_pci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci_pci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000007 sdhci_pci0-slot0: Timeout: 0x0000000d | Int stat: 0x00000000 sdhci_pci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00f3 sdhci_pci0-slot0: AC12 err: 0x00000001 | Host ctl2:0x00000080 sdhci_pci0-slot0: Caps: 0x21fe32b2 | Caps2: 0x00000070 sdhci_pci0-slot0: Max curr: 0x00c80064 | ADMA err: 0x00000000 sdhci_pci0-slot0: ADMA addr:0x00000000 | Slot int: 0x000000ff sdhci_pci0-slot0: =========================================== g_vfs_done():mmcsd0s1a[READ(offset=1073983488, length=4096)]error = 5 sdhci_pci0-slot0: mmcsd0: Got AutoCMD12 error 0x0001, but there is no active command. sdhci_pci0-slot0: Error indicated: 1 Timeout ============== REGISTER DUMP ============== sdhci_pci0-slot0: Sys addr: 0x050bd000 | Version: 0x00001001 sdhci_pci0-slot0: Blk size: 0x00000200 | Blk cnt: 0x00000008 sdhci_pci0-slot0: Argument: 0x0020674f | Trn mode: 0x00000037 sdhci_pci0-slot0: Present: 0x01ef0000 | Host ctl: 0x00000007 sdhci_pci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci_pci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000007 sdhci_pci0-slot0: Timeout: 0x0000000d | Int stat: 0x00000000 sdhci_pci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00f3 sdhci_pci0-slot0: AC12 err: 0x00000001 | Host ctl2:0x00000080 sdhci_pci0-slot0: Caps: 0x21fe32b2 | Caps2: 0x00000070 sdhci_pci0-slot0: Max curr: 0x00c80064 | ADMA err: 0x00000000 sdhci_pci0-slot0: ADMA addr:0x00000000 | Slot int: 0x000000ff sdhci_pci0-slot0: =========================================== g_vfs_done():mmcsd0s1a[READ(offset=1087242240, length=4096)]error = 5 sdhci_pci0-slot0: mmcsd0: Got AutoCMD12 error 0x0001, but there is no active command. sdhci_pci0-slot0: ============== REGISTER DUMP ============== sdhci_pci0-slot0: Sys addr: 0x050bd000 | Version: 0x00001001 sdhci_pci0-slot0: Blk size: 0x00000200 | Blk cnt: 0x00000008 sdhci_pci0-slot0: Argument: 0x0020cc77 | Trn mode: 0x00000037 sdhci_pci0-slot0: Present: 0x01ef0000 | Host ctl: 0x00000007 sdhci_pci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci_pci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000007 sdhci_pci0-slot0: Timeout: 0x0000000d | Int stat: 0x00000000 sdhci_pci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00f3 sdhci_pci0-slot0: AC12 err: 0x00000001 | Host ctl2:0x00000080 sdhci_pci0-slot0: Error indicated: 1 Timeout Caps: 0x21fe32b2 | Caps2: 0x00000070 sdhci_pci0-slot0: Max curr: 0x00c80064 | ADMA err: 0x00000000 sdhci_pci0-slot0: ADMA addr:0x00000000 | Slot int: 0x000000ff sdhci_pci0-slot0: =========================================== g_vfs_done():mmcsd0s1a[READ(offset=1100500992, length=4096)]error = 5 sdhci_pci0-slot0: mmcsd0: Got AutoCMD12 error 0x0001, but there is no active command. sdhci_pci0-slot0: Error indicated: 1 Timeout ============== REGISTER DUMP ============== sdhci_pci0-slot0: Sys addr: 0x050bd000 | Version: 0x00001001 sdhci_pci0-slot0: Blk size: 0x00000200 | Blk cnt: 0x00000008 sdhci_pci0-slot0: Argument: 0x0021319f | Trn mode: 0x00000037 sdhci_pci0-slot0: Present: 0x01ef0000 | Host ctl: 0x00000007 sdhci_pci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci_pci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000007 sdhci_pci0-slot0: Timeout: 0x0000000d | Int stat: 0x00608000 sdhci_pci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00f3 sdhci_pci0-slot0: AC12 err: 0x00000001 | Host ctl2:0x00000080 sdhci_pci0-slot0: Caps: 0x21fe32b2 | Caps2: 0x00000070 sdhci_pci0-slot0: Max curr: 0x00c80064 | ADMA err: 0x00000000 sdhci_pci0-slot0: ADMA addr:0x00000000 | Slot int: 0x000000ff sdhci_pci0-slot0: =========================================== sdhci_pci0-slot0: Got data interrupt 0x00600000, but there is no active command. sdhci_pci0-slot0: ============== REGISTER DUMP ============== sdhci_pci0-slot0: Sys addr: 0x050bd000 | Version: 0x00001001 sdhci_pci0-slot0: Blk size: 0x00000200 | Blk cnt: 0x00000008 sdhci_pci0-slot0: Argument: 0x0021319f | Trn mode: 0x00000037 sdhci_pci0-slot0: Present: 0x01ef0000 | Host ctl: 0x00000007 sdhci_pci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci_pci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000007 sdhci_pci0-slot0: Timeout: 0x0000000d | Int stat: 0x00000000 sdhci_pci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00f3 sdhci_pci0-slot0: AC12 err: 0x00000001 | Host ctl2:0x00000080 sdhci_pci0-slot0: Caps: 0x21fe32b2 | Caps2: 0x00000070 sdhci_pci0-slot0: Max curr: 0x00c80064 | ADMA err: 0x00000000 sdhci_pci0-slot0: ADMA addr:0x00000000 | Slot int: 0x000000ff sdhci_pci0-slot0: =========================================== -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-questions@freebsd.org Thu Jan 11 12:06:41 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 75739EA5215 for ; Thu, 11 Jan 2018 12:06:41 +0000 (UTC) (envelope-from zainco30@gmail.com) Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 335346C796 for ; Thu, 11 Jan 2018 12:06:41 +0000 (UTC) (envelope-from zainco30@gmail.com) Received: by mail-yw0-x235.google.com with SMTP id t201so911428ywf.1 for ; Thu, 11 Jan 2018 04:06:41 -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=aUZMGn9ZgBG1VcoiGWY23tV8TdL87K9Trg93AKO8rt4=; b=ZvD0j36m4s2QX1H/aBtCd7mSmUqNFf8kPY2LcplfmlUX9W00AfpVD8ZzfGwqlxwRqn 6PJ6Qjd4uuBgI61Kp6bFcU8giRlpzHqeNSsrF0INvW4fvqquyolXe29nvkHCrhrRaoy4 fQeR5Obwo8IqFAgySQLA6uJRbu/5I97EfNSRvq/LQJokOnloeKOwAHlZghNnnnn+7gos jR7T3ItYWIEo3NaqfLFO1zLEvBYOWfCa/KqYaUb1lkfkk9dx60uelMh0UEMaxhp3zN2J mh2YhDVbhAn3Pj3axGPR2AlKO2OHKFh1hCjw3+5uYOYCjZ5A8RRJ9rdF+UxE1VmPvnJF h8vg== 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=aUZMGn9ZgBG1VcoiGWY23tV8TdL87K9Trg93AKO8rt4=; b=ta1CHZMFMGBT229Rnn8PxM6dpF/w3Ndg9Ixcg0DGorpH1BecNMXj4ZKhOT8UZhFPDj LKgKM3ULLvAAKlchzEMZmHUir4hysyX/xsa53gVa+lbyKbmFffs+1mwQq91J7cmZjIaR WVD1DaISTLEVGqXVTq2ox8qOA7azjcaytFYqivc0YOhppg5jheoNQvoKu3zkCr4Y5h9y IzrSX9Y3KzxQQ+d9q0UlgirtCVO2GDUQfMcQIw16yvWEWy4vZM1HTdv4gG2Pg+0zMxNX gY8FJJJarzuB2jmgvQz97C9tXtgK/FmeS6CjtU1b53s1CD+wOuykZIQ8KUmurMmJUjO2 umAg== X-Gm-Message-State: AKGB3mIakFzPry+0nz/2eqET1smoZCAgd0GUYZMyXcc2licyrdF+6B40 5oOo7qUvgrdNYd9ZBQfqRhiBaXjAR68BM1WpWoI= X-Google-Smtp-Source: ACJfBov9hMOVRmNwJp9oItChk2Ba9KXkUcEt1Az0AyLpHopOL5N2YB62amdGFNkhD04inX8AOshs7+2iuT7kMU7kJ1c= X-Received: by 10.129.76.141 with SMTP id z135mr19379852ywa.42.1515672399861; Thu, 11 Jan 2018 04:06:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.130.65 with HTTP; Thu, 11 Jan 2018 04:06:39 -0800 (PST) From: "Zainelabdeen S.A Elgraeed" Date: Thu, 11 Jan 2018 15:06:39 +0300 Message-ID: Subject: HAST questions To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2018 12:06:41 -0000 hello, i am Zainelabdeen system administrator at the university of Gezira Sudan. we have a project to use Freebsd as web hosting, we want to use jail for each web server. 1.how can I provide high availability for jail between two host machine? 2. is hast can be used to do this task? thanks From owner-freebsd-questions@freebsd.org Thu Jan 11 12:14:16 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9326CEA5E24 for ; Thu, 11 Jan 2018 12:14:16 +0000 (UTC) (envelope-from g8kbvdave@googlemail.com) Received: from mail-wr0-x22a.google.com (mail-wr0-x22a.google.com [IPv6:2a00:1450:400c:c0c::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 46C9A6CF9A for ; Thu, 11 Jan 2018 12:14:16 +0000 (UTC) (envelope-from g8kbvdave@googlemail.com) Received: by mail-wr0-x22a.google.com with SMTP id s13so1944962wra.10 for ; Thu, 11 Jan 2018 04:14:16 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=S5THLPnku7k9liwkNjsnHmbfvh391XZu9oNG0lDf1CA=; b=VS+ojrqSkxPzAD05tb9E2et+yuVNwT33E2c7q6h/K8doD7kgw6TzIjmDqEOuNFIHh4 zMfbTKYQcz069qqzUAp0lzJaZFpvcXxbFP4cVTUYlpHTriUclCEFoI5J1mbojaKDUh9B Q2XuJSgkrI45mCEsQ/rAtjr9dwtHQeAjhSHzL1oOb5GydsAH1Y85pRbnvemMz+EAV4H3 J6JbqnClinGSDCqgap/sbjVDzkt69o982cxIjt0JLdmvowBlf7rtH7W+CRohPczku8eW BLhTapqwxdLBADqqTwr3JWSlVowWNARjYKuQu8b02/m5M1sA5nK3vqVll/V4lIrV2va1 6bSA== X-Gm-Message-State: AKGB3mKVhUpjdTaSZBgWagbopQogZm0/O0BTszDpUn7iUJNsabGT8bK/ 2BorgWc8cK8U9+KQqkm0ws4o7t6I X-Google-Smtp-Source: ACJfBot6nGgRl9Zb1Yrxy4yWRmsaq+vJfvbkXT+tnAI5qax0BBsq4qjxU40kY0R22tVaorNQjKIBWg== X-Received: by 10.223.199.146 with SMTP id l18mr19504946wrg.166.1515672854410; Thu, 11 Jan 2018 04:14:14 -0800 (PST) Received: from [192.168.2.55] ([217.41.35.220]) by smtp.gmail.com with ESMTPSA id z71sm13804098wrc.11.2018.01.11.04.14.13 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Jan 2018 04:14:13 -0800 (PST) Subject: Re: freebsd-questions Digest, Vol 709, Issue 5 To: freebsd-questions@freebsd.org References: From: Dave B Message-ID: <0bce5e82-97ba-0a73-e261-c91473837737@googlemail.com> Date: Thu, 11 Jan 2018 12:14:13 +0000 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-GB Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2018 12:14:16 -0000 That I suspect depends on how many physical address lines are available for it via the memory management system. If the PC documentation says 8G is the max', then that is probably all that'll be seen by the CPU, even if there is 16G installed. There is only one way to find out for sure, at your expense. Personally, I doubt it, and the info at https://support.hp.com/gb-en/document/c03363664 says it wont. If it does see 16G (or more) best park it in a corner and thrash it with a Live Boot Memtest86 CD for some days, to ensure it's working correctly. (Let it run to full completion, it can take hours for a full test, even for 4G!) But even that, doesnt fully exercise the memory management system in the same way an OS will. Chances are, if it works at all with the large memory modules, it'll only "See" and be able to use 8G. Have Fun. Dave B. On 11/01/18 12:00, freebsd-questions-request@freebsd.org wrote: > Subject: > OT: Max system physical memory > From: > Aryeh Friedman > Date: > 10/01/18 14:59 > > To: > FreeBSD Mailing List > > > My computer (HP Pavilion P7-1234, FreeBSD 11.1-RELEASE [amd64]) has 2 240 > pin DIMM (DDR3, PC3-10600) the manual says the max memory is 8 GB but I see > some 16 GB packages (2x8GB). If I put one or two of these in will it see > the extra memory? From owner-freebsd-questions@freebsd.org Thu Jan 11 12:34:20 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 75D77E5C1E6 for ; Thu, 11 Jan 2018 12:34:20 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0749D6DDD7 for ; Thu, 11 Jan 2018 12:34:19 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTPS id w0BCXxFm006907 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 11 Jan 2018 13:33:59 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id w0BCXx16006904; Thu, 11 Jan 2018 13:33:59 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Thu, 11 Jan 2018 13:33:59 +0100 (CET) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: Vitalio D cc: "freebsd-questions@freebsd.org" Subject: Re: where to find exit(int) function implementation In-Reply-To: Message-ID: References: <59cdf69e792d5c723fa919abac1d67b6@webmail.1blu.de>, <8ef73fb7-dc2f-2fcb-f8e6-e7de02a66b64@gmx.com> User-Agent: Alpine 2.21 (BSF 202 2017-01-01) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-2.2 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.fig.ol.no X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2018 12:34:20 -0000 On Wed, 10 Jan 2018 15:38-0000, Vitalio D wrote: > Hello, > Indeed I'm interested in _exit syscall. > > Thanks for response Yuri, but i'm a newbie and don't > see any PSEUDO marking in unistd.h at least. > What i see in unisrd.h is > > ... > __BEGIN_DECLS > /* 1003.1-1990 */ > void _exit(int) __dead2; > ... > > __BEGIN_DECLS being defined in sys/sys/cdefs.h as exten "C" { > but no PSEUDO. Am i missing something? If you want to see what happens inside the kernel when servicing the exit syscall, have a look at /usr/src/sys/kern/kern_exit.c. -- Trond. From owner-freebsd-questions@freebsd.org Thu Jan 11 12:55:34 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 73EE4E5D52B for ; Thu, 11 Jan 2018 12:55:34 +0000 (UTC) (envelope-from julien@perdition.city) Received: from relay-b01.edpnet.be (relay-b01.edpnet.be [212.71.1.221]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "edpnet.email", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 20DDD6EBE2 for ; Thu, 11 Jan 2018 12:55:33 +0000 (UTC) (envelope-from julien@perdition.city) X-ASG-Debug-ID: 1515674536-0a7ff505ce42da50001-jLrpzn Received: from mordor.lan (77.109.96.175.adsl.dyn.edpnet.net [77.109.96.175]) by relay-b01.edpnet.be with ESMTP id uvWEFYKAmJXPyCKf (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 11 Jan 2018 13:42:17 +0100 (CET) X-Barracuda-Envelope-From: julien@perdition.city X-Barracuda-Effective-Source-IP: 77.109.96.175.adsl.dyn.edpnet.net[77.109.96.175] X-Barracuda-Apparent-Source-IP: 77.109.96.175 Date: Thu, 11 Jan 2018 13:42:16 +0100 From: Julien Cigar To: "Zainelabdeen S.A Elgraeed" Cc: freebsd-questions@freebsd.org Subject: Re: HAST questions Message-ID: <20180111124216.GS72179@mordor.lan> X-ASG-Orig-Subj: Re: HAST questions References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="yQifGgTvVVJcdOYJ" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.2 (2017-04-18) X-Barracuda-Connect: 77.109.96.175.adsl.dyn.edpnet.net[77.109.96.175] X-Barracuda-Start-Time: 1515674536 X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384 X-Barracuda-URL: https://212.71.1.221:443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at edpnet.be X-Barracuda-Scan-Msg-Size: 1305 X-Barracuda-BRTS-Status: 1 X-Barracuda-Bayes: INNOCENT GLOBAL 0.5000 1.0000 0.0100 X-Barracuda-Spam-Score: 0.01 X-Barracuda-Spam-Status: No, SCORE=0.01 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=7.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.46775 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2018 12:55:34 -0000 --yQifGgTvVVJcdOYJ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 11, 2018 at 03:06:39PM +0300, Zainelabdeen S.A Elgraeed wrote: > hello, i am Zainelabdeen system administrator at the university of Gezira > Sudan. >=20 > we have a project to use Freebsd as web hosting, we want to use jail for > each web server. >=20 > 1.how can I provide high availability for jail between two host machine? "high availability" is a general term and happen at various levels of the whole "stack". On the application layer with HTTP you'll probably=20 need at least 4 machines if you want to do HA and LB properly (with HAProxy or ...) > 2. is hast can be used to do this task? >=20 although HAST is no so much used and developed it can somewhat provide=20 drbd-like HA for the storage side (but don't use it with ZFS) if=20 coupled with CARP/devd. > thanks > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o= rg" --=20 Julien Cigar Belgian Biodiversity Platform (http://www.biodiversity.be) PGP fingerprint: EEF9 F697 4B68 D275 7B11 6A25 B2BB 3710 A204 23C0 No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced. --yQifGgTvVVJcdOYJ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEE7vn2l0to0nV7EWolsrs3EKIEI8AFAlpXW6UACgkQsrs3EKIE I8A6fA//cu7Qb48POfZvxhUXnfP0Sq2seXj9Ox5rK5t/fQ8v7Pczt1oZmYkKYf6N yNvmOAw7zJ0b5wKkvZfP1UBCEP3l+/hj8Z6Gn7H8fflyrGUFDey+NKke5jbEQiHj OyT95R4YucVArc8+ENMIPTj0sE0wd02SIGf630+P9rbi1/Myg3nnTHE7MfOSZDz6 j0jlWD8qtXIpWT8yySc7XQGIzRRU3iUi00rg8d++lF7KzPVQFBaWBinfqltVLsPP 5H+XdMtw2dUzcYjTkrxi6k3f1TUdbJScrvUscuJQH+y8Pc4gnQmkVhah91irEOYC 1hvXvaZ+UBsPZb57ZECdJEBwflFDkRkTNSz/Y7gr1YDti+TnbXJqg6PDQrcu/H7k M9LFQB3VBeokfymqWmTgwiN2FFqcriyhxe2/qCyMve97PDoozeRyT0ES5b8bTla1 XEjXXOD0yrpalsnHxe02QIXD59oqBxv7x8SBcCE8DBpVZB+7eV9e1FBcnEpJCscu uRVNobt43oHP776qdslKW7s8d9+ops5Rtuj1OA+emqTXtvq42WynNqltWsOrTf6n 8FyowzJre0vbdpLoD34cs/q927IylL5yYXtqsQ6fz+56OOvuRidY2ax45/vCKDs/ JPkCitouCrD+14xm45uT1c/BvmwVqqhItsFHmnNM8Be+ch2tUOk= =iN1d -----END PGP SIGNATURE----- --yQifGgTvVVJcdOYJ-- From owner-freebsd-questions@freebsd.org Thu Jan 11 13:34:17 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 24F76E61C09 for ; Thu, 11 Jan 2018 13:34:17 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 85F317057E for ; Thu, 11 Jan 2018 13:34:10 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by mail-it0-x22f.google.com with SMTP id r6so4317213itr.3 for ; Thu, 11 Jan 2018 05:34:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ssuhyS84KP2HC+pY6LKRL2JnYWj/tz65TaF5PIB0aHA=; b=ALRt2OwUUay74PX5tOSthiaJLNfb4cNcFcOX0yksF9W4YzqxQNHgXTGb9XvOqIb/wk RvatBsKKPH+/YDm1NRijiUuVfZRIYk4kW5TITY0PZvxrcqh/FisvsUJNdgiKoYimJus/ Bl3QOUegzdf5/FQlVBVAk5F04iB5VMbcewrDgOLa56BB/83ob5E3vNMn3rqbEzpL2XVo dzBeWpuuNkTVdirZPI0epekj5RfJv0n7nFWFD3CYqn/MMKoLNSF9IeSiiebeAM0SaZUl A60qqgWWJtAqX2UkhZnNn1ucsYVJB+LpG6Btv5GIxjuhSKMv7fOnZL0yUMcs1fPiZfB8 Tg6Q== 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=ssuhyS84KP2HC+pY6LKRL2JnYWj/tz65TaF5PIB0aHA=; b=EqWRsdvs0umXS89u2CtkjNY4vsIc5CBeO+GMDPZkWq2IYER+q8oIv1TvNXUdfEqzY0 yRw4Ich8f0MDnwASORBfhi9rE9lDzddqVRes92Iz6z4WAiBOoz2EqQ5m26fX4XLqdYQI dKjcLq17KqWPMGcG0mgyvivsuhTWy96UtSLZZuG5J0ROW24RrELCEUGNQW5WWbW1XPJ8 T85Zk03jATagl6hToE2wR4DY7dd/jgCOc7Pm9YT5DyO2+LE/g6at/agwNP9jPmTjRSsh TWyGt0UpvkSGdQWdWVfvU89NDbdAOefnpBNz7/ylucdalUn07ZhsbKOX8whlQdUJMJd0 ErvA== X-Gm-Message-State: AKwxytec1D/TWdfweV7XUaIZa1VdZOCCEhofezza77IH0uFalcmSUwqJ HnK7bJaXrUnw9w2nKYXp809Erjeic4G7XizYnOy+gg== X-Google-Smtp-Source: ACJfBotElDLR64sCor0PywkFSAw1DfetKJzYd/M2dhtKhkzAqS+Im4GF2DrLogp3MUBEFTku2ZwpAEe/SV8DtM8XVL4= X-Received: by 10.36.37.209 with SMTP id g200mr1355908itg.152.1515677647368; Thu, 11 Jan 2018 05:34:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.36.105.3 with HTTP; Thu, 11 Jan 2018 05:34:06 -0800 (PST) In-Reply-To: <0bce5e82-97ba-0a73-e261-c91473837737@googlemail.com> References: <0bce5e82-97ba-0a73-e261-c91473837737@googlemail.com> From: Aryeh Friedman Date: Thu, 11 Jan 2018 08:34:06 -0500 Message-ID: Subject: Re: freebsd-questions Digest, Vol 709, Issue 5 To: Dave B Cc: FreeBSD Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2018 13:34:17 -0000 On Thu, Jan 11, 2018 at 7:14 AM, Dave B via freebsd-questions < freebsd-questions@freebsd.org> wrote: > That I suspect depends on how many physical address lines are available > for it via the memory management system. > > If the PC documentation says 8G is the max', then that is probably all > that'll be seen by the CPU, even if there is 16G installed. > > There is only one way to find out for sure, at your expense. > > Personally, I doubt it, and the info at > https://support.hp.com/gb-en/document/c03363664 says it wont. > I have bought the memory (I can use it in an other machine worst comes to worst) have not installed it yet but in doing deeper research I got a even stranger disagreement between what it appears the machine can physically handle and what the manual says. Output of sysutils/dmidecode: Handle 0x000A, DMI type 16, 23 bytes Physical Memory Array Location: System Board Or Motherboard Use: System Memory Error Correction Type: None Maximum Capacity: 128 GB Error Information Handle: Not Provided Number Of Devices: 2 Handle 0x000C, DMI type 17, 34 bytes Memory Device Array Handle: 0x000A Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 4096 MB Form Factor: DIMM Set: None Locator: A1_DIMM0 Bank Locator: A1_BANK0 Type: DDR3 Type Detail: Synchronous Speed: 1333 MT/s Manufacturer: Samsung Serial Number: 938D8E07 Asset Tag: A1_AssetTagNum0 Part Number: M378B5273CH0-CH9 Rank: 2 Configured Clock Speed: 667 MT/s Handle 0x000E, DMI type 17, 34 bytes Memory Device Array Handle: 0x000A Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 4096 MB Form Factor: DIMM Set: None Locator: A1_DIMM1 Bank Locator: A1_BANK1 Type: DDR3 Type Detail: Synchronous Speed: 1333 MT/s Manufacturer: Samsung Serial Number: 938D8C71 Asset Tag: A1_AssetTagNum1 Part Number: M378B5273CH0-CH9 Rank: 2 Configured Clock Speed: 667 MT/s -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-questions@freebsd.org Thu Jan 11 13:44:51 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 45749E62A1B for ; Thu, 11 Jan 2018 13:44:51 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from be-well.ilk.org (be-well.ilk.org [23.30.133.173]) by mx1.freebsd.org (Postfix) with ESMTP id F2B3171303 for ; Thu, 11 Jan 2018 13:44:48 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: by be-well.ilk.org (Postfix, from userid 1147) id B439333C3E; Thu, 11 Jan 2018 08:44:43 -0500 (EST) From: Lowell Gilbert To: Aryeh Friedman Cc: FreeBSD Mailing List Subject: Re: OT: Max system physical memory References: Date: Thu, 11 Jan 2018 08:44:43 -0500 In-Reply-To: (Aryeh Friedman's message of "Wed, 10 Jan 2018 09:59:54 -0500") Message-ID: <44wp0ofr1w.fsf@be-well.ilk.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2018 13:44:51 -0000 Aryeh Friedman writes: > My computer (HP Pavilion P7-1234, FreeBSD 11.1-RELEASE [amd64]) has 2 240 > pin DIMM (DDR3, PC3-10600) the manual says the max memory is 8 GB but I see > some 16 GB packages (2x8GB). If I put one or two of these in will it see > the extra memory? Probably not. From owner-freebsd-questions@freebsd.org Thu Jan 11 14:44:57 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A8860E66FAA for ; Thu, 11 Jan 2018 14:44:57 +0000 (UTC) (envelope-from g8kbvdave@googlemail.com) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4532F744B0 for ; Thu, 11 Jan 2018 14:44:57 +0000 (UTC) (envelope-from g8kbvdave@googlemail.com) Received: by mail-wm0-x229.google.com with SMTP id f206so5878456wmf.5 for ; Thu, 11 Jan 2018 06:44:57 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=2xsa2JyQmSYST8KhJ0HFXjWfRQc2804HaGOxx+9yxs0=; b=Uhyn3QY4lJr+OQv8GI7aVq5pY4OCwTTxbW0FpkjH+Z/K+NwTmdSPAnARLnO9heh2Pn Z7fz2bLhadgOeCbZrx3682hx4EBwZuXRHNOl5MdrtwQ4eL1ki6A6ZVazxZg2OzxVQ5IY CPiRTVSsg+mSIFhVm5unNz709GUWz6n0XtTr9TB/3eI+/dzzCUGVdO8+igrD/eGM73ZK 0EA4z39awJpaekFQBtVNEyptwUDiePMxf0GbnAJIFi4bXt5v+JlPwx+3rNSq+19uljuF OqtC4Dz+/paSb3GWDomCfEduai44ZoKBOf8dn3+gxsyBkQHj6MrESAhlyB8i2VTr4HbE 0e4Q== X-Gm-Message-State: AKGB3mI+VKR31KdpuTc57IAfIdUl0C72DdSSQFNYc0woA0A+BAa0h8OV xyqlQlolfoADJUmWmEzKFFIxTXoV X-Google-Smtp-Source: ACJfBotwGyuBNAVmQZF8bJe86DDA1NJ+mJXXiKiIXQomBFuMRXsw8GCUTIfVS9ZPXEZ0aA3n0maUFQ== X-Received: by 10.80.201.75 with SMTP id p11mr31128234edh.199.1515681894961; Thu, 11 Jan 2018 06:44:54 -0800 (PST) Received: from [192.168.2.55] ([217.41.35.220]) by smtp.gmail.com with ESMTPSA id c33sm11562812edd.36.2018.01.11.06.44.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Jan 2018 06:44:53 -0800 (PST) Subject: Re: freebsd-questions Digest, Vol 709, Issue 5 To: Aryeh Friedman Cc: FreeBSD Mailing List References: <0bce5e82-97ba-0a73-e261-c91473837737@googlemail.com> From: Dave B Message-ID: Date: Thu, 11 Jan 2018 14:44:53 +0000 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-GB Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2018 14:44:57 -0000 I'd say go ahead and try it... I'd doubt (though I don’t "know") that any damage would be done by putting "to much" RAM in a system, so lots to gain perhaps, and little to loose if it doesn’t work. Regards. Dave B. On 11/01/18 13:34, Aryeh Friedman wrote: > > > On Thu, Jan 11, 2018 at 7:14 AM, Dave B via freebsd-questions > > > wrote: > > That I suspect depends on how many physical address lines are > available > for it via the memory management system. > > If the PC documentation says 8G is the max', then that is probably all > that'll be seen by the CPU, even if there is 16G installed. > > There is only one way to find out for sure, at your expense. > > Personally, I doubt it, and the info at  > https://support.hp.com/gb-en/document/c03363664 >   says it wont. > > > I have bought the memory (I can use it in an other machine worst comes > to worst) have not installed it yet but in doing deeper research I got > a even stranger disagreement between what it appears the machine can > physically handle and what the manual says.  Output of sysutils/dmidecode: > > Handle 0x000A, DMI type 16, 23 bytes > Physical Memory Array >     Location: System Board Or Motherboard >     Use: System Memory >     Error Correction Type: None >     Maximum Capacity: 128 GB >     Error Information Handle: Not Provided >     Number Of Devices: 2 > > Handle 0x000C, DMI type 17, 34 bytes > Memory Device >     Array Handle: 0x000A >     Error Information Handle: Not Provided >     Total Width: 64 bits >     Data Width: 64 bits >     Size: 4096 MB >     Form Factor: DIMM >     Set: None >     Locator: A1_DIMM0 >     Bank Locator: A1_BANK0 >     Type: DDR3 >     Type Detail: Synchronous >     Speed: 1333 MT/s >     Manufacturer: Samsung         >     Serial Number: 938D8E07  >     Asset Tag: A1_AssetTagNum0 >     Part Number: M378B5273CH0-CH9  >     Rank: 2 >     Configured Clock Speed: 667 MT/s > > Handle 0x000E, DMI type 17, 34 bytes > Memory Device >     Array Handle: 0x000A >     Error Information Handle: Not Provided >     Total Width: 64 bits >     Data Width: 64 bits >     Size: 4096 MB >     Form Factor: DIMM >     Set: None >     Locator: A1_DIMM1 >     Bank Locator: A1_BANK1 >     Type: DDR3 >     Type Detail: Synchronous >     Speed: 1333 MT/s >     Manufacturer: Samsung         >     Serial Number: 938D8C71  >     Asset Tag: A1_AssetTagNum1 >     Part Number: M378B5273CH0-CH9  >     Rank: 2 >     Configured Clock Speed: 667 MT/s > > -- > Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-questions@freebsd.org Thu Jan 11 14:45:12 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C70F6E66FD5 for ; Thu, 11 Jan 2018 14:45:12 +0000 (UTC) (envelope-from teamweb@allteam.com) Received: from mail.petroil.com.mx (mail.petroil.com.mx [50.97.187.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Parallels Panel", Issuer "Parallels Panel" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9623A744EA for ; Thu, 11 Jan 2018 14:45:11 +0000 (UTC) (envelope-from teamweb@allteam.com) Received: (qmail 2952 invoked from network); 11 Jan 2018 06:45:26 -0700 Received: from ec2-54-93-193-110.eu-central-1.compute.amazonaws.com (HELO WIN-LDJNFF6KQ3S) (54.93.193.110) by mail.petroil.com.mx with ESMTPA; 11 Jan 2018 06:45:25 -0700 Message-ID: <03584114-43111-ae445732466667@win-ldjnff6kq3s> Reply-To: "Netflix" From: "Netflix" To: freebsd-questions@freebsd.org Subject: Account Notification Date: Thu, 11 Jan 2018 13:44:29 +0000 X-Priority: 3 X-PPP-Message-ID: <20180111134526.2947.59687@mail.petroil.com.mx> X-PPP-Vhost: petroil.com.mx MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2018 14:45:12 -0000 From owner-freebsd-questions@freebsd.org Thu Jan 11 15:02:14 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 096A7E67EFB for ; Thu, 11 Jan 2018 15:02:14 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.20.71]) by mx1.freebsd.org (Postfix) with ESMTP id E185C7515C for ; Thu, 11 Jan 2018 15:02:13 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id 56A2FCB8D12; Thu, 11 Jan 2018 09:02:07 -0600 (CST) Received: from 108.68.170.208 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Thu, 11 Jan 2018 09:02:07 -0600 (CST) Message-ID: <50615.108.68.170.208.1515682927.squirrel@cosmo.uchicago.edu> In-Reply-To: <44wp0ofr1w.fsf@be-well.ilk.org> References: <44wp0ofr1w.fsf@be-well.ilk.org> Date: Thu, 11 Jan 2018 09:02:07 -0600 (CST) Subject: Re: OT: Max system physical memory From: "Valeri Galtsev" To: "Lowell Gilbert" Cc: "Aryeh Friedman" , "FreeBSD Mailing List" Reply-To: galtsev@kicp.uchicago.edu User-Agent: SquirrelMail/1.4.8-5.el5.centos.7 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2018 15:02:14 -0000 On Thu, January 11, 2018 7:44 am, Lowell Gilbert wrote: > Aryeh Friedman writes: > >> My computer (HP Pavilion P7-1234, FreeBSD 11.1-RELEASE [amd64]) has 2 >> 240 >> pin DIMM (DDR3, PC3-10600) the manual says the max memory is 8 GB but I >> see >> some 16 GB packages (2x8GB). If I put one or two of these in will it >> see >> the extra memory? > > Probably not. > It is hit and miss. It is possible that specifications were written based on largest available modules at the moment of writing. If replacement modules are compatible with memory controller (i.e., say, the same PC3-10600), it is possible they will work. There still is the chance they will not work reliably, _IF_ there are some less trivial specs of memory controller are involved. Such may be: bus amplifiers may only handle up to this capacitive load before signals go out of specs. In general, larger RAM has larger numbers of address inputs connected to given lead, which may entail larger capacitive load. System board layout may have its impact here as well. Apart from that (and maybe some internal schematic specifics of memory controller), there is nothing fundamental about 8 GB RAM limit, so it may work. But chance is it will not. In any case, don't mix RAM modules with different specs (look at timing details like CL as well) on the same memory bus. I hope, this helps. Valeri ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++ From owner-freebsd-questions@freebsd.org Thu Jan 11 15:08:51 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 23E8DE686AB for ; Thu, 11 Jan 2018 15:08:51 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::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 DCEB2755EB for ; Thu, 11 Jan 2018 15:08:50 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by mail-it0-x22c.google.com with SMTP id f143so4997109itb.0 for ; Thu, 11 Jan 2018 07:08:50 -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=PCrVB8uc9xi9M2Wnmt0cAaNHM9AQckVzVCl0w7fyAS0=; b=YegXQ32DmG7+6A98uZQpohqEac3L/yWf2VIcot4Ywbh7pCivH5AJNM68lECExrN5PZ M+xzTDcl8s+jTJa53L4T/3tZY/Qw7xaSycWfsER9ELjS2jytslia8i5753IImDxcs1GN cRCstgKbgIljRMfBHxJ3CUO8ksdV9L1gs9WcJeM8Neu87ks6nsy0+QeCS4nPYNNCZzTp mPCK0rgNR1eTI+v8j8EgcObbwS12JKeeb1ZV7OjMhVCDCADeF0YcvxE1wplPs6dwf5aE 7LkP609QQCnWlU48nWTojj3FLNbHsLIfKO1xNJeNhbMO7U9HsnNeIhgA0MevbLQK2MJr b3tA== 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=PCrVB8uc9xi9M2Wnmt0cAaNHM9AQckVzVCl0w7fyAS0=; b=qyYioEvMzJdxvVkc9id91BtnwL4O99RvZK2h4FXHXcH6cz+IIJo32wjaTEdXlr/n9A DNZp9TCnzF/Q6R1IAFph+sPDqBEwG9mXLollmT6Yy8LDIUWHlqC85niZgooVf0VDS9op o9QBJoSyLCSz74rXLblMlGc6PqumbEWKy+6Hq7SgpERcHUjqvD3p/QYI978kOjkaQWM4 FQ0eYojCx/fNkMgFoi/uXbabWpXgAshmXyMMR7a87DIFycckU83f5ewCv6HuoF46DTk4 o84KtzL7txYtyssyoB6nua5T4156Jt9GmOmcSv4Ftg67WXyCu9muh0/+hSECZKvNUEGf RVqQ== X-Gm-Message-State: AKwxytedQ+zzdGADIT+43ktgFViqnmRG712jWFw2/hmwnVEaXEyTv1g0 pijucVCR8ZYQtmKObaFXS4uz53oh0I90VsJSlEBClA== X-Google-Smtp-Source: ACJfBouDL1LICoDfoVYdDqI8utxCV0IIbeNQcC7/R/usvW+4SVALqimQuUMWbjPNn1liEQe+HX54/cnLJ++/imf54s4= X-Received: by 10.36.39.138 with SMTP id g132mr1516082ita.89.1515683330274; Thu, 11 Jan 2018 07:08:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.36.105.3 with HTTP; Thu, 11 Jan 2018 07:08:49 -0800 (PST) In-Reply-To: <50615.108.68.170.208.1515682927.squirrel@cosmo.uchicago.edu> References: <44wp0ofr1w.fsf@be-well.ilk.org> <50615.108.68.170.208.1515682927.squirrel@cosmo.uchicago.edu> From: Aryeh Friedman Date: Thu, 11 Jan 2018 10:08:49 -0500 Message-ID: Subject: Re: OT: Max system physical memory To: galtsev@kicp.uchicago.edu Cc: Lowell Gilbert , FreeBSD Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2018 15:08:51 -0000 On Thu, Jan 11, 2018 at 10:02 AM, Valeri Galtsev wrote: > > On Thu, January 11, 2018 7:44 am, Lowell Gilbert wrote: > > Aryeh Friedman writes: > > > >> My computer (HP Pavilion P7-1234, FreeBSD 11.1-RELEASE [amd64]) has 2 > >> 240 > >> pin DIMM (DDR3, PC3-10600) the manual says the max memory is 8 GB but I > >> see > >> some 16 GB packages (2x8GB). If I put one or two of these in will it > >> see > >> the extra memory? > > > > Probably not. > > > > It is hit and miss. It is possible that specifications were written based > on largest available modules at the moment of writing. If replacement > modules are compatible with memory controller (i.e., say, the same > PC3-10600), it is possible they will work. There still is the chance they > will not work reliably, _IF_ there are some less trivial specs of memory > controller are involved. Such may be: bus amplifiers may only handle up to > this capacitive load before signals go out of specs. In general, larger > RAM has larger numbers of address inputs connected to given lead, which > may entail larger capacitive load. System board layout may have its impact > here as well. Apart from that (and maybe some internal schematic specifics > of memory controller), there is nothing fundamental about 8 GB RAM limit, > so it may work. But chance is it will not. > > sysutils/dmidecode disagrees with the manual thus deeping my confusion (I bought the memory and use it in an other machine that does support upto 32GB and only has 8 spread across 2 VM's): oot@lilith:~ # dmidecode -t memory # dmidecode 3.1 Scanning /dev/mem for entry point. SMBIOS 2.7 present. Handle 0x000A, DMI type 16, 23 bytes Physical Memory Array Location: System Board Or Motherboard Use: System Memory Error Correction Type: None Maximum Capacity: 128 GB Error Information Handle: Not Provided Number Of Devices: 2 Handle 0x000C, DMI type 17, 34 bytes Memory Device Array Handle: 0x000A Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 4096 MB Form Factor: DIMM Set: None Locator: A1_DIMM0 Bank Locator: A1_BANK0 Type: DDR3 Type Detail: Synchronous Speed: 1333 MT/s Manufacturer: Samsung Serial Number: 938D8E07 Asset Tag: A1_AssetTagNum0 Part Number: M378B5273CH0-CH9 Rank: 2 Configured Clock Speed: 667 MT/s Handle 0x000E, DMI type 17, 34 bytes Memory Device Array Handle: 0x000A Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 4096 MB Form Factor: DIMM Set: None Locator: A1_DIMM1 Bank Locator: A1_BANK1 Type: DDR3 Type Detail: Synchronous Speed: 1333 MT/s Manufacturer: Samsung Serial Number: 938D8C71 Asset Tag: A1_AssetTagNum1 Part Number: M378B5273CH0-CH9 Rank: 2 Configured Clock Speed: 667 MT/s -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-questions@freebsd.org Thu Jan 11 15:57:10 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9EE6BE6B4B7 for ; Thu, 11 Jan 2018 15:57:10 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from kicp.uchicago.edu (kicp.uchicago.edu [128.135.20.70]) by mx1.freebsd.org (Postfix) with ESMTP id 84114776D9 for ; Thu, 11 Jan 2018 15:57:10 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from point.uchicago.edu (point.uchicago.edu [128.135.52.6]) by kicp.uchicago.edu (Postfix) with ESMTP id 8EC7171803D; Thu, 11 Jan 2018 09:57:04 -0600 (CST) Subject: Re: freebsd-questions Digest, Vol 709, Issue 5 To: Dave B , freebsd-questions@freebsd.org References: <0bce5e82-97ba-0a73-e261-c91473837737@googlemail.com> From: Valeri Galtsev Message-ID: Date: Thu, 11 Jan 2018 09:57:04 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <0bce5e82-97ba-0a73-e261-c91473837737@googlemail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2018 15:57:10 -0000 On 01/11/18 06:14, Dave B via freebsd-questions wrote: > That I suspect depends on how many physical address lines are available > for it via the memory management system. > > If the PC documentation says 8G is the max', then that is probably all > that'll be seen by the CPU, even if there is 16G installed. > > There is only one way to find out for sure, at your expense. > > Personally, I doubt it, and the info at > https://support.hp.com/gb-en/document/c03363664 says it wont. > > If it does see 16G (or more) best park it in a corner and thrash it with > a Live Boot Memtest86 CD for some days, to ensure it's working > correctly. (Let it run to full completion, it can take hours for a > full test, even for 4G!) In addition to memtest86 I would also run much more stressful test, namely have the machine booted into system, run multiple CPU and RAM hungry stuff (make buildworld comes to my mind). The reason for that would be: with signals on memory bus marginally out of specs, system stress will help them being pushed to the limit, which "unstressful" memtest86 will not do and may pass, though the failure on stressed system still may happen. Just my $0.02 Valeri > > But even that, doesnt fully exercise the memory management system in > the same way an OS will. > > Chances are, if it works at all with the large memory modules, it'll > only "See" and be able to use 8G. > > Have Fun. > > Dave B. > > > > On 11/01/18 12:00, freebsd-questions-request@freebsd.org wrote: >> Subject: >> OT: Max system physical memory >> From: >> Aryeh Friedman >> Date: >> 10/01/18 14:59 >> >> To: >> FreeBSD Mailing List >> >> >> My computer (HP Pavilion P7-1234, FreeBSD 11.1-RELEASE [amd64]) has 2 240 >> pin DIMM (DDR3, PC3-10600) the manual says the max memory is 8 GB but I see >> some 16 GB packages (2x8GB). If I put one or two of these in will it see >> the extra memory? > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > -- ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++ From owner-freebsd-questions@freebsd.org Thu Jan 11 17:36:53 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A326E711B2 for ; Thu, 11 Jan 2018 17:36:53 +0000 (UTC) (envelope-from g8kbvdave@googlemail.com) Received: from mail-wr0-x22e.google.com (mail-wr0-x22e.google.com [IPv6:2a00:1450:400c:c0c::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 0AE637BC4B for ; Thu, 11 Jan 2018 17:36:53 +0000 (UTC) (envelope-from g8kbvdave@googlemail.com) Received: by mail-wr0-x22e.google.com with SMTP id 36so2959922wrh.1 for ; Thu, 11 Jan 2018 09:36:52 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=7bKIII6vjhIO6fwoN7MvreI6bb/arSEgv9OWIb1V2lM=; b=mW89jWXgV2levU7vAWZS5dHD3zc1uGj6BYPdqsDIEPszFZglgIhuWoIcWmGaRewQgi trYTeIVuQodR7pAIJQP/p0tiy4ctajqHrSujFfDg23u/6cSvlHjAtY0/csXQNRdWx/h3 GPy8A6uP1tvCp7veKE3ciHfKoVxiHhaBEnMi6mixmOUYa0LjnM3jCqAvVDdOyR+sRkcG P0C8Oa5bJSCqeYcRayhYIWwRdA6lSn+ZExNagOW68pCUYRJTn03RJCBjmpX1na7Sup+i 2XkwwRlwBgSMRK0RRfPmenA321cagh/28yWrR9lLdmvSQAQlNnqv1V08LDSyOkADmDxM hZew== X-Gm-Message-State: AKGB3mISI39WT5Pzf3SRBS5QpZAsx9BJ9COZrcN2Tv0g/U4De4IEQiXl nBmpjcR+qIosR/QTKzd23JORv6Oz X-Google-Smtp-Source: ACJfBotYXNvtrjTmwauXp6LvB32ZMM43SSPdTYQE35JWz4Wa1d0QnRRy1N1Zeqq8ZigTC8nkMOYkuw== X-Received: by 10.223.161.65 with SMTP id r1mr19606687wrr.235.1515692211297; Thu, 11 Jan 2018 09:36:51 -0800 (PST) Received: from [192.168.2.55] ([217.41.35.220]) by smtp.gmail.com with ESMTPSA id r74sm827448wme.24.2018.01.11.09.36.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Jan 2018 09:36:50 -0800 (PST) Subject: Re: freebsd-questions Digest, OT: Max system physical memory To: Valeri Galtsev , freebsd-questions@freebsd.org References: <0bce5e82-97ba-0a73-e261-c91473837737@googlemail.com> From: Dave B Message-ID: Date: Thu, 11 Jan 2018 17:36:49 +0000 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Content-Language: en-GB X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2018 17:36:53 -0000 Memtest86 is anything but un-stressfull! It runs a multitude of tests, designed to increase the noise level on the memory cell sense lines by way of specific address and data patterns. DRAM is not unlike older memory technology in that respect, regarding noise on sense lines due to particular data/address patterns. Yes, an OS can stress the RAM, but so can this. That's why it can take an age to complete one full pass. I have in the past found it to be the only tool to find single bit errors in several GByte of RAM. On one (infamous) occasion, a user complained that one OS update wouldnt "take", the system (you know the one) just tried and tried again over and over. Other than that, the "system" as a whole was working just fine. (The use was music and video editing, so not exactly a low stress environment!) When they were able to release the machine to me, after cleaning out all the coolers etc, I ran Memtest86, and eventually, in the last few % of the last test, some hours after starting, it flagged a single bit error. 1 Bit, in over 4G bytes of memory! If you doubt the stress it puts a system under, just monitor the cooling exhaust temperatures, and power consumption when tests are running! Long story short, after identifying which of the 8 memory cards was the buggy one (by selective removal-relocation and retest etc, several days later...) A new part was sourced, installed and tested successfully, all OK. The very next full OS boot, the problematic security update ran and stuck just fine, followed by several others that must have been waiting for a dependency to be satisfied.. Just to be sure, I swapped that suspect card into another similar system, that booted and ran OK, but again Memtest86 eventually found a single bit error, right at the end of the last test. The memory card went for recycling along with a load of other WEEE junk. I'm sure it could happen, but in over 30 years in total that I've been working on this sort of hardware, professionally and at home, I've yet to find any OS fail due to RAM errors, that a "Proper" memory diagnostic tool could not find the cause.. Memtest86 might not be the be all and end all of all RAM tests, and of course its x86 specific, but it's pretty damn close. For the price though, it can't be beaten. I've seen it find and identify problems that paid for diagnostics just ignore. Often allowing me to repair systems that were declared BER by other (so called) professional data system engineers. The downside, is the time it all takes, and of course, time == money. Regards to All. Dave B. >><< On 11/01/18 15:57, Valeri Galtsev wrote: > > > On 01/11/18 06:14, Dave B via freebsd-questions wrote: >> That I suspect depends on how many physical address lines are available >> for it via the memory management system. >> >> If the PC documentation says 8G is the max', then that is probably all >> that'll be seen by the CPU, even if there is 16G installed. >> >> There is only one way to find out for sure, at your expense. >> >> Personally, I doubt it, and the info at >> https://support.hp.com/gb-en/document/c03363664 says it wont. >> >> If it does see 16G (or more) best park it in a corner and thrash it with >> a Live Boot Memtest86 CD for some days, to ensure it's working >> correctly. (Let it run to full completion, it can take hours for a >> full test, even for 4G!) > > In addition to memtest86 I would also run much more stressful test, > namely have the machine booted into system, run multiple CPU and RAM > hungry stuff (make buildworld comes to my mind). The reason for that > would be: with signals on memory bus marginally out of specs, system > stress will help them being pushed to the limit, which "unstressful" > memtest86 will not do and may pass, though the failure on stressed > system still may happen. > > Just my $0.02 > > Valeri > >> >> But even that, doesnt fully exercise the memory management system in >> the same way an OS will. >> >> Chances are, if it works at all with the large memory modules, it'll >> only "See" and be able to use 8G. >> >> Have Fun. >> >> Dave B. >> >> >> >> On 11/01/18 12:00, freebsd-questions-request@freebsd.org wrote: >>> Subject: >>> OT: Max system physical memory >>> From: >>> Aryeh Friedman >>> Date: >>> 10/01/18 14:59 >>> >>> To: >>> FreeBSD Mailing List >>> >>> >>> My computer (HP Pavilion P7-1234, FreeBSD 11.1-RELEASE [amd64]) has >>> 2 240 >>> pin DIMM (DDR3, PC3-10600) the manual says the max memory is 8 GB >>> but I see >>> some 16 GB packages (2x8GB). If I put one or two of these in will >>> it see >>> the extra memory? >> >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" >> > From owner-freebsd-questions@freebsd.org Thu Jan 11 18:05:05 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AFCC5E72A0A for ; Thu, 11 Jan 2018 18:05:05 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-ot0-x22e.google.com (mail-ot0-x22e.google.com [IPv6:2607:f8b0:4003:c0f::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 6F1C47D1A5 for ; Thu, 11 Jan 2018 18:05:05 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-ot0-x22e.google.com with SMTP id d10so2835633oti.7 for ; Thu, 11 Jan 2018 10:05:05 -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=V0CHOSgX4UMctpC8aFC+8LD8CGa5aRazfsyG7LrNGNU=; b=Y1SA2kcWJi6G7rWaLVcsRYC3qMD6xsPo+XAI7oBW/baT12q9eplcIi+sVOquu9xc4h fFh8EYiUkkRtxDWAj7LD8QHBu5pGNx8RVJv+IFUJcP/AZGCa/wy3He8nDfCw9UVxhc4f pqI/URaI4v+rpIv2tqgwKnXsTuIzOUZ2hFbG9A1PAq2wQ3FrYaGTKS+WZxql9zzttj26 tBLzzen+up5cfWPqLSCb3f31PwhZ01SfkbqD1UOlPTQ3jcpyY0o5LWz0sJWTd2TCUo9y 07vzJw5G39agUfQeyAqn3qcvtIMxuFyTK2wvvFwPyiRyM+jMrthC4q/4zCTzrOTFRNPE 2T4g== 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=V0CHOSgX4UMctpC8aFC+8LD8CGa5aRazfsyG7LrNGNU=; b=etyC0mvoS4mXCeiDSAgaACla2OkvRc/O9rfs3CNzfFTunit5QeyNHIIy1hZWhkzIjo KuGglnrfdteTvbLFpvAE8fKl0Eqqe4GDKsfB4nYSYC4JwO0YuIAgD8f1ySNNOrapBOzE q6lbVCQm2HLtKUmIesAj4de67BhTH6QW9msIIdyLZOEgD3IFReKMEdLghrV5Oo6rIp9y 8jbjJnszg+h6/Mk5gW3Ua/3Cl/k9zlpUhzFsYI4dNH+nuoocv9tSu+x/gPKHzbZ2gogl Sz8nqxVCZMUhGe56zdt+KRkzsw03C3lfBu7EzkNVCaOTKljChCetsOhJIisDXvTGjDQB XhxQ== X-Gm-Message-State: AKwxyte+EG5gpEuAKlA4rIaue9a2asomNYwxBhaKLbeQV0/pWO0kx94B lE2GxVqHvnBQMvuVvZTQ9zaxWPqR/hh6mwhmM3Y= X-Google-Smtp-Source: ACJfBotf72eJlxhBj2V39Dvj5ntc3Pt0Jd31o4oQJrC9pWQOJMH6jtpfZjIr+pHix7jfHDldSss7qp4yf8HfNEzplnI= X-Received: by 10.157.9.33 with SMTP id 30mr13008250otp.344.1515693904584; Thu, 11 Jan 2018 10:05:04 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.0.2 with HTTP; Thu, 11 Jan 2018 10:05:03 -0800 (PST) In-Reply-To: References: <44wp0ofr1w.fsf@be-well.ilk.org> <50615.108.68.170.208.1515682927.squirrel@cosmo.uchicago.edu> From: Mehmet Erol Sanliturk Date: Thu, 11 Jan 2018 21:05:03 +0300 Message-ID: Subject: Re: OT: Max system physical memory To: Aryeh Friedman Cc: galtsev@kicp.uchicago.edu, Lowell Gilbert , FreeBSD Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2018 18:05:05 -0000 On Thu, Jan 11, 2018 at 6:08 PM, Aryeh Friedman wrote: > On Thu, Jan 11, 2018 at 10:02 AM, Valeri Galtsev < > galtsev@kicp.uchicago.edu> > wrote: > > > > > On Thu, January 11, 2018 7:44 am, Lowell Gilbert wrote: > > > Aryeh Friedman writes: > > > > > >> My computer (HP Pavilion P7-1234, FreeBSD 11.1-RELEASE [amd64]) has 2 > > >> 240 > > >> pin DIMM (DDR3, PC3-10600) the manual says the max memory is 8 GB but > I > > >> see > > >> some 16 GB packages (2x8GB). If I put one or two of these in will it > > >> see > > >> the extra memory? > > > > > > Probably not. > > > > > > > It is hit and miss. It is possible that specifications were written based > > on largest available modules at the moment of writing. If replacement > > modules are compatible with memory controller (i.e., say, the same > > PC3-10600), it is possible they will work. There still is the chance they > > will not work reliably, _IF_ there are some less trivial specs of memory > > controller are involved. Such may be: bus amplifiers may only handle up > to > > this capacitive load before signals go out of specs. In general, larger > > RAM has larger numbers of address inputs connected to given lead, which > > may entail larger capacitive load. System board layout may have its > impact > > here as well. Apart from that (and maybe some internal schematic > specifics > > of memory controller), there is nothing fundamental about 8 GB RAM limit, > > so it may work. But chance is it will not. > > > > > sysutils/dmidecode disagrees with the manual thus deeping my confusion (I > bought the memory and use it in an other machine that does support upto > 32GB and only has 8 spread across 2 VM's): > > oot@lilith:~ # dmidecode -t memory > # dmidecode 3.1 > Scanning /dev/mem for entry point. > SMBIOS 2.7 present. > > Handle 0x000A, DMI type 16, 23 bytes > Physical Memory Array > Location: System Board Or Motherboard > Use: System Memory > Error Correction Type: None > Maximum Capacity: 128 GB > Error Information Handle: Not Provided > Number Of Devices: 2 > > Handle 0x000C, DMI type 17, 34 bytes > Memory Device > Array Handle: 0x000A > Error Information Handle: Not Provided > Total Width: 64 bits > Data Width: 64 bits > Size: 4096 MB > Form Factor: DIMM > Set: None > Locator: A1_DIMM0 > Bank Locator: A1_BANK0 > Type: DDR3 > Type Detail: Synchronous > Speed: 1333 MT/s > Manufacturer: Samsung > Serial Number: 938D8E07 > Asset Tag: A1_AssetTagNum0 > Part Number: M378B5273CH0-CH9 > Rank: 2 > Configured Clock Speed: 667 MT/s > > Handle 0x000E, DMI type 17, 34 bytes > Memory Device > Array Handle: 0x000A > Error Information Handle: Not Provided > Total Width: 64 bits > Data Width: 64 bits > Size: 4096 MB > Form Factor: DIMM > Set: None > Locator: A1_DIMM1 > Bank Locator: A1_BANK1 > Type: DDR3 > Type Detail: Synchronous > Speed: 1333 MT/s > Manufacturer: Samsung > Serial Number: 938D8C71 > Asset Tag: A1_AssetTagNum1 > Part Number: M378B5273CH0-CH9 > Rank: 2 > Configured Clock Speed: 667 MT/s > > > > -- > Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > _______________________________________________ > > Another problem may be required energy to feed higher capacity memory chips . If the currently available slots are not able to support the required energy , over time they may cause hardware failure and/or memory access errors . Mehmet Erol Sanliturk From owner-freebsd-questions@freebsd.org Thu Jan 11 19:07:13 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7C67AE76313 for ; Thu, 11 Jan 2018 19:07:13 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from kicp.uchicago.edu (kicp.uchicago.edu [128.135.20.70]) by mx1.freebsd.org (Postfix) with ESMTP id 4FB3B80B9A for ; Thu, 11 Jan 2018 19:07:13 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from point.uchicago.edu (point.uchicago.edu [128.135.52.6]) by kicp.uchicago.edu (Postfix) with ESMTP id EA85771803D; Thu, 11 Jan 2018 13:07:11 -0600 (CST) Subject: Re: freebsd-questions Digest, OT: Max system physical memory To: Dave B , freebsd-questions@freebsd.org References: <0bce5e82-97ba-0a73-e261-c91473837737@googlemail.com> From: Valeri Galtsev Message-ID: <5900c538-35b7-33ae-160c-0c070cdea4d2@kicp.uchicago.edu> Date: Thu, 11 Jan 2018 13:07:11 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2018 19:07:13 -0000 On 01/11/18 11:36, Dave B wrote: > Memtest86 is anything but un-stressfull! > > It runs a multitude of tests, designed to increase the noise level on > the memory cell sense lines by way of specific address and data > patterns. DRAM is not unlike older memory technology in that respect, > regarding noise on sense lines due to particular data/address patterns. > > Yes, an OS can stress the RAM, but so can this. That's why it can take > an age to complete one full pass. > > I have in the past found it to be the only tool to find single bit > errors in several GByte of RAM. On one (infamous) occasion, a user > complained that one OS update wouldnt "take", the system (you know the > one) just tried and tried again over and over. Other than that, the > "system" as a whole was working just fine. (The use was music and video > editing, so not exactly a low stress environment!) > > When they were able to release the machine to me, after cleaning out all > the coolers etc, I ran Memtest86, and eventually, in the last few % of > the last test, some hours after starting, it flagged a single bit > error. 1 Bit, in over 4G bytes of memory! > > If you doubt the stress it puts a system under, just monitor the cooling > exhaust temperatures, and power consumption when tests are running! > > Long story short, after identifying which of the 8 memory cards was the > buggy one (by selective removal-relocation and retest etc, several days > later...) A new part was sourced, installed and tested successfully, > all OK. > > The very next full OS boot, the problematic security update ran and > stuck just fine, followed by several others that must have been waiting > for a dependency to be satisfied.. > > Just to be sure, I swapped that suspect card into another similar > system, that booted and ran OK, but again Memtest86 eventually found a > single bit error, right at the end of the last test. The memory card > went for recycling along with a load of other WEEE junk. > > I'm sure it could happen, but in over 30 years in total that I've been > working on this sort of hardware, professionally and at home, I've yet > to find any OS fail due to RAM errors, that a "Proper" memory diagnostic > tool could not find the cause.. > > Memtest86 might not be the be all and end all of all RAM tests, and of > course its x86 specific, but it's pretty damn close. For the price > though, it can't be beaten. I've seen it find and identify problems > that paid for diagnostics just ignore. Often allowing me to repair > systems that were declared BER by other (so called) professional data > system engineers. > > The downside, is the time it all takes, and of course, time == money. Well, it is all well and agreeable. And memtest86 is all you say and is very powerful to catch single bit errors, even those which may only happen trough cross talk between signal lines. No one would attempt to undermine the validity of memtest86. But everything has its limitations, so: What I attempted to say is: memtest86 does not create CPU load. Someone who does know the details of memtest86, chime in, but as far as I know thing didn't change lately and is still valid. And CPU load and high workload of other machine electronic boards (or components on the system board) do affect the operation and signals memory controllers and memory modules produce. Every electrical engineer will tell you that (yes, I do have electrical engineering degree in addition to computer science one). I would try to think of it like this. When you are running memtest64 you are sterilizing the operation room of vet clinic. But when the room actually makes operation on a stray dog that just was brought from the street, the sterility level is quite different. Let me attempt to make my point differently. Memtest86 catches all memory errors that consistently happen. It may catch some errors that are "transient", i.e. sometimes happen sometimes not, but to catch some of them may take extremely large number of loops, and still in may not catch some that still may happen under real system run. Stressing ALL components of computer helps to increase probability of transient errors. Memtest86 is not designed to do so (and it is single thread program as far as I know, and this is how I would program it if I were to achieve the goal memtest86 has). I hope, this time I managed to make my point clear. Valeri > > Regards to All. > > Dave B. > >>> << > > On 11/01/18 15:57, Valeri Galtsev wrote: >> >> >> On 01/11/18 06:14, Dave B via freebsd-questions wrote: >>> That I suspect depends on how many physical address lines are available >>> for it via the memory management system. >>> >>> If the PC documentation says 8G is the max', then that is probably all >>> that'll be seen by the CPU, even if there is 16G installed. >>> >>> There is only one way to find out for sure, at your expense. >>> >>> Personally, I doubt it, and the info at >>> https://support.hp.com/gb-en/document/c03363664 says it wont. >>> >>> If it does see 16G (or more) best park it in a corner and thrash it with >>> a Live Boot Memtest86 CD for some days, to ensure it's working >>> correctly. (Let it run to full completion, it can take hours for a >>> full test, even for 4G!) >> >> In addition to memtest86 I would also run much more stressful test, >> namely have the machine booted into system, run multiple CPU and RAM >> hungry stuff (make buildworld comes to my mind). The reason for that >> would be: with signals on memory bus marginally out of specs, system >> stress will help them being pushed to the limit, which "unstressful" >> memtest86 will not do and may pass, though the failure on stressed >> system still may happen. >> >> Just my $0.02 >> >> Valeri >> >>> >>> But even that, doesnt fully exercise the memory management system in >>> the same way an OS will. >>> >>> Chances are, if it works at all with the large memory modules, it'll >>> only "See" and be able to use 8G. >>> >>> Have Fun. >>> >>> Dave B. >>> >>> >>> >>> On 11/01/18 12:00, freebsd-questions-request@freebsd.org wrote: >>>> Subject: >>>> OT: Max system physical memory >>>> From: >>>> Aryeh Friedman >>>> Date: >>>> 10/01/18 14:59 >>>> >>>> To: >>>> FreeBSD Mailing List >>>> >>>> >>>> My computer (HP Pavilion P7-1234, FreeBSD 11.1-RELEASE [amd64]) has >>>> 2 240 >>>> pin DIMM (DDR3, PC3-10600) the manual says the max memory is 8 GB >>>> but I see >>>> some 16 GB packages (2x8GB). If I put one or two of these in will >>>> it see >>>> the extra memory? >>> >>> _______________________________________________ >>> freebsd-questions@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-questions >>> To unsubscribe, send any mail to >>> "freebsd-questions-unsubscribe@freebsd.org" >>> >> -- ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++ From owner-freebsd-questions@freebsd.org Fri Jan 12 00:43:31 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DDE9DE62F57 for ; Fri, 12 Jan 2018 00:43:31 +0000 (UTC) (envelope-from srs0=dtml=eh=mail.sermon-archive.info=doug@sermon-archive.info) Received: from mail.sermon-archive.info (sermon-archive.info [71.177.216.148]) by mx1.freebsd.org (Postfix) with ESMTP id CCCE46DF93 for ; Fri, 12 Jan 2018 00:43:31 +0000 (UTC) (envelope-from srs0=dtml=eh=mail.sermon-archive.info=doug@sermon-archive.info) Received: from [10.0.1.251] (mini [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 3zHkWQ4ZQwz2fk4r for ; Thu, 11 Jan 2018 16:43:30 -0800 (PST) From: Doug Hardie Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Error in Manual Message-Id: <1EDCB997-7CA9-4229-A939-5F76B4B25952@mail.sermon-archive.info> Date: Thu, 11 Jan 2018 16:43:30 -0800 To: "freebsd-questions@freebsd.org Questions" X-Mailer: Apple Mail (2.3445.5.20) X-Virus-Scanned: clamav-milter 0.99.2 at mail X-Virus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2018 00:43:32 -0000 12.2.3. Stage Three The information on setting a different kernel is incorrect. Took awhile = to figure out that the commands listed: unload load kernel.old should really be: unload load /boot/kernel.old/kernel -- Doug From owner-freebsd-questions@freebsd.org Fri Jan 12 00:49:47 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1DF64E63649 for ; Fri, 12 Jan 2018 00:49:47 +0000 (UTC) (envelope-from srs0=dtml=eh=mail.sermon-archive.info=doug@sermon-archive.info) Received: from mail.sermon-archive.info (sermon-archive.info [71.177.216.148]) by mx1.freebsd.org (Postfix) with ESMTP id 0D8046E221 for ; Fri, 12 Jan 2018 00:49:46 +0000 (UTC) (envelope-from srs0=dtml=eh=mail.sermon-archive.info=doug@sermon-archive.info) Received: from [10.0.1.251] (mini [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 3zHkSs1Lb3z2fk3G for ; Thu, 11 Jan 2018 16:41:17 -0800 (PST) From: Doug Hardie Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Freebsd-update issue Message-Id: <575E10E0-E8FE-49BF-A346-C07BA55CD872@mail.sermon-archive.info> Date: Thu, 11 Jan 2018 16:41:16 -0800 To: "freebsd-questions@freebsd.org Questions" X-Mailer: Apple Mail (2.3445.5.20) X-Virus-Scanned: clamav-milter 0.99.2 at mail X-Virus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2018 00:49:47 -0000 Running 11.0 system. Did Freebsd-update upgrade -r 11.1-RELEASE.=20 All seemed to go fine. However, on the first reboot after the = freebsd-install install command, the system crashes with the following = output: /boot/kernel/kernel text=3D0x14972f8 data=3D0x1384c0+0x4c15e8 = syms=3D[0x8+0x15e8b0+0x8+0x178422] /boot/entropy size=3D0x1000 Booting... Copyright (c) 1992-2017 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights = reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.1-RELEASE-p4 #0: Tue Nov 14 06:12:40 UTC 2017 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC = amd64 FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on = LLVM 4.0.0) VT(vga): resolution 640x480 CPU: Dual-Core AMD Opteron(tm) Processor 2214 HE (2200.04-MHz K8-class = CPU) Origin=3D"AuthenticAMD" Id=3D0x40f13 Family=3D0xf Model=3D0x41 = Stepping=3D3 = Features=3D0x178bfbff Features2=3D0x2001 AMD = Features=3D0xea500800 AMD Features2=3D0x1f SVM: NAsids=3D64 real memory =3D 9495392 (8992 MB) avail memory =3D 8263294976 (7880 MB) Event timer "LAPIC" quality 100 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 2 package(s) x 2 core(s) random: unblocking device. ioapic irqs 0-23 on motherboard SMP: AP CPU # pkkernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid =3D 2; atpic id =3D 02 fault virtual address =3D 0x0 fault code =3D supervisor writte data, page not present instruction pointer =3D 0x20:0xffffffff80ab01dd stack pointer =3D 0x28:0xfffffe01f0328350 frame pointer =3D 0x28:0xfffffe01f0328420 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D resume, IOPL =3D 0 current process =3D 11 (idle: cpu2) trap number =3D 12 panic: page fault cpuid =3D 2 Uptime: 1s Rebooting... =20 It then goes through that same cycle a few times and then hangs = permanently. Trying to revert to previous system. -- Doug From owner-freebsd-questions@freebsd.org Fri Jan 12 01:03:13 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0643AE64294 for ; Fri, 12 Jan 2018 01:03:13 +0000 (UTC) (envelope-from freebsd@theory14.net) Received: from bacon.theory14.net (bacon.theory14.net [45.55.200.27]) by mx1.freebsd.org (Postfix) with ESMTP id D6B1C6EA6A for ; Fri, 12 Jan 2018 01:03:12 +0000 (UTC) (envelope-from freebsd@theory14.net) Received: from remote.theory14.net (remote.theory14.net [173.79.116.36]) by bacon.theory14.net (Postfix) with ESMTPSA id 08AD8125ECD; Thu, 11 Jan 2018 19:55:43 -0500 (EST) Received: from anubis.int.theory14.net (anubis.int.theory14.net [192.168.10.50]) by remote.theory14.net (Postfix) with ESMTPS id A1419CD08; Thu, 11 Jan 2018 19:55:38 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=theory14.net; s=mail; t=1515718538; bh=JUY0AHe+VVY059wYHBA/4znDMp8icdMR5HD97fwLMfo=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=AR1LgiJg+5fcej1Iv/Av0qLDSepEPraEH9ilVmf3ZpMV85+6OV/cr/BHQv8EAVnid hFmvxoPqA1Co1Vq7x/huvWRbUceCqhdYPq/yxxDhXRpseLsM7PxIHtH/N/6nnSFHJ9 Tf5XwAVzGOOpJEIRuZNv2BYS+kbghOUsR8gjcb6k= Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: HAST questions From: Chris Gordon In-Reply-To: Date: Thu, 11 Jan 2018 19:55:36 -0500 Cc: freebsd-questions@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <1DFDF803-4D86-42F8-A22E-4A9077608982@theory14.net> References: To: "Zainelabdeen S.A Elgraeed" X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2018 01:03:13 -0000 There are many different ways to increase the availability of a system. = It really depends on the details of the application on what options you = have and what the best way to do this may be. Are these web servers hosting static content? Is the content read-only = or is there something taking writes? Is there a database involved? =20 If you can provide some details of what is running on these web servers, = we can help guide you on some options you have. Thanks, Chris > On Jan 11, 2018, at 7:06 AM, Zainelabdeen S.A Elgraeed = wrote: >=20 > hello, i am Zainelabdeen system administrator at the university of = Gezira > Sudan. >=20 > we have a project to use Freebsd as web hosting, we want to use jail = for > each web server. >=20 > 1.how can I provide high availability for jail between two host = machine? > 2. is hast can be used to do this task? >=20 > thanks > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to = "freebsd-questions-unsubscribe@freebsd.org" From owner-freebsd-questions@freebsd.org Fri Jan 12 03:06:17 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9EFB4E6B442 for ; Fri, 12 Jan 2018 03:06:17 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0BB5D72E94 for ; Fri, 12 Jan 2018 03:06:16 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.18.98]) by mrelayeu.kundenserver.de (mreue103 [212.227.15.183]) with ESMTPA (Nemesis) id 0Mdo4b-1eD6IG1gmT-00PfiM for ; Fri, 12 Jan 2018 04:06:09 +0100 Date: Fri, 12 Jan 2018 04:06:09 +0100 From: Polytropon To: freebsd-questions@freebsd.org Subject: Re: Error in Manual Message-Id: <20180112040609.5315bf5a.freebsd@edvax.de> In-Reply-To: <1EDCB997-7CA9-4229-A939-5F76B4B25952@mail.sermon-archive.info> References: <1EDCB997-7CA9-4229-A939-5F76B4B25952@mail.sermon-archive.info> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:FCzE7L5BwiPAr/1MxmOj6HnyzNA/CZ5mJAoh3mHZaJsEgshcVSO hO6cY/rhceQlAhbnrSNu/qbDRPEooWBw2nG4rH24nHMeAXIGaH+K3GhelE7mB6ZiG6I3Sn2 PMSzQUtb3tECWGf5nQVgOFJaVEDERBIQDe30zT98ZGk/lRrC1by8xNCEPPUCXxmQg/qkk/6 PDzOZ1+15oqoHfDSG1mUw== X-UI-Out-Filterresults: notjunk:1;V01:K0:dR9YImyk3Ho=:oYwn4tmKZbpbDPLLCVXHtZ 9m5vLCAt0+IBO1LjAvOnN0w1i0Ew447EPSTa0tmCXR1Drf/wWfKwkjdIxwWjij2byDxu4KO0H QztlOBzuVaRpv9MYxsVPQDW1dyhYS/FjTqNXh7lP54zi/d4ih1pJMcY/NuZFqQ7b18eqYbYxC SP0zKndYhI+5EcrNTbQ8KFCeekTp0MakSd+l3yeJj9PFfpiqfnfyjp+z0UJTNr0yKbMVQ5tx/ VDgvkuHaSvnn9FPId5h0cRLCOPyl5GMV/DYj+8hiHAWB3MCFgKeGJtHxdbrNKssEP1vZUsBrk z6/TwF3rQ7rK4PEKi85WvigVsJhR9oEOQorh53Y8RFATI2NsKvkJPkpDXqWIwnSAA0LKDOYHo nFh75GLlTKCI4dYa7fBkekkXmafV+FEko1h8wkkw/4QGuR3PNsMKx1mkeFZFQCOdkcCGzbc5J cC8kRJxMsZ9XkLW8hUfIXPO4Qh6aRZV0OnGfHXizbATXWbOVM8EDMUFlGifhbBtamX5AzkdV+ buDnqpmZ91gmYE04F01pR3dsXPY4k0hsJI/KN6kLBCZeREcGFxH+LDeZTYMaHCvrhOibTCpg/ TrLR5yZxfJQMBBEvee6gkOBKXWEPmf2vmJJ3lyAuOeyUhI8nfNlZdFGd4ocIViJAibYEBiDHi CSPGEuy6OF9FOWmSf5mz3evgquW1lwNvGg8dgCB/xQjq3lNDdRmhXt/uEwaK1xR6KCxObMJYW lOBKgrH4M8Ea2mgWka5gD+E2eYjY7LK89wfCZF2C73QiGB6WB35E/7WmAQ4= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2018 03:06:17 -0000 On Thu, 11 Jan 2018 16:43:30 -0800, Doug Hardie wrote: > 12.2.3. Stage Three > > The information on setting a different kernel is incorrect. Took awhile to figure out that the commands listed: > > unload > load kernel.old > > should really be: > > unload > load /boot/kernel.old/kernel The information isn't entirely incorrect, but it is not up to date. On a FreeBSD system around version 4 and 5, the command listed would be okay (as the files /boot/kernel and /boot/kernel.old would exist). However, it should be updated to match the _current_ state of FreeBSD kernel location. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Fri Jan 12 04:22:09 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A6026E6F90C for ; Fri, 12 Jan 2018 04:22:09 +0000 (UTC) (envelope-from quinefang@gmail.com) Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6C9107594D for ; Fri, 12 Jan 2018 04:22:09 +0000 (UTC) (envelope-from quinefang@gmail.com) Received: by mail-qt0-x236.google.com with SMTP id u10so4623795qtg.2 for ; Thu, 11 Jan 2018 20:22:09 -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=Fji9tNsWAKhaXCTTVGhYDBMDGJjN1FlaozeqjM7UO54=; b=TfqtIj/9ojMv4lX3fZIIY4Ltem2gtpWQC8U0WZQCEUsOirNnnqqUMsXMH8V4sbdSgc TOZekCVANgg38grAkxi9stMHNODzIJ5/UjlJledHOqxoiXoWCAYacHSo7ouT6qR8qBKK cS28bCQEqrUQaf9/5czQUBwG04nn2RxukLlAYzaVbhYxSrtj3fKKaubb5Ugyvio7TUvS rlvytfI5LhoMwwKWTNoGUE8cbUjWi9cJ+/quRDNeP9UTu54C/BqPqdeKr0nr//JYhZ5v ZRWnnjGVG7OWUtK2rbLFdSutQ2tu8WINUbGte3NKC07LjKsM6rlgczCT9uCVvPoJJffp s5/w== 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=Fji9tNsWAKhaXCTTVGhYDBMDGJjN1FlaozeqjM7UO54=; b=bXYbW97PgK4dggcxy70GXJdxK+2EozxCQf9djhtKMtj/SkWDK+Grqm3TWcgilh1tDo QTMwRfFcpt8sXb+IqxzIHsqu4oK0eOntrqe2YP6JUP+9BaDSZJvfnnoR9TMoWoQu4J+R BPt1W+Je2Nl4DLOPF30eWICoUWK5/pkz6qmPkztQRltkhEFilAUFRiyLGUyg9wdKy5tu UJq5/UuKpgOKZuebjO3gnG026W2uLlpUO1oTz+MXrUASX7OXqLtYCKExjkWWngNHpBg0 VVMcU6CQ8Ta633pe8uFhWdkMdPjGSHJhzeXDy6IZO2zTf73KULj7PCBez6GKpAsav1Go WVPA== X-Gm-Message-State: AKwxytcP7cS0gbuDSChe6yTdQnbKfS4U6+Llpmjgt5SNg4WgIzX0CGjz Bl0vlSqIOgYDRdNlhL8CQ3FZFnxxF7EMo+oy8vuP3RAt X-Google-Smtp-Source: ACJfBosdDFqeSRv5bE3FxZ7XRpO2gMhIBxMpD6SV2I2bh6NL429JuT+vdwE5PSx0wKIVVh924MeGkoRt5RUFDAjnzIo= X-Received: by 10.237.46.66 with SMTP id j60mr34635425qtd.168.1515730928340; Thu, 11 Jan 2018 20:22:08 -0800 (PST) MIME-Version: 1.0 Received: by 10.55.79.23 with HTTP; Thu, 11 Jan 2018 20:22:08 -0800 (PST) From: =?UTF-8?B?5pa55Z2k?= Date: Fri, 12 Jan 2018 12:22:08 +0800 Message-ID: Subject: Problems removing orphan packages To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2018 04:22:09 -0000 Last week, I ran `cd /usr/ports/devel/git ; make install clean` to install the Git package, I found that the "/deve/bison", "/shells/bash" and "www/w3m" packages also installed as the "devel/git" package need them. Today I ran `portmaster -s` to uninstall unused packages, I found the "/deve/bison", "/shells/bash" and "www/w3m" packages were on the listed. So I uninstalled all the packages in that list. I didn't understand why portmaster thinks that the "/deve/bison", "/shells/bash" and "www/w3m" packages were unused packages. So I ran `cd /usr/ports/devel/git ; make install clean` again, I found that the "/deve/bison", "/shells/bash" and "www/w3m" packages installed again. Is anyone can teach me why? From owner-freebsd-questions@freebsd.org Fri Jan 12 05:04:37 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2FCEE71E51 for ; Fri, 12 Jan 2018 05:04:37 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 494687744C for ; Fri, 12 Jan 2018 05:04:36 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.18.98]) by mrelayeu.kundenserver.de (mreue101 [212.227.15.183]) with ESMTPA (Nemesis) id 0MaaYD-1eGHEA3j2n-00K7EF; Fri, 12 Jan 2018 06:04:27 +0100 Date: Fri, 12 Jan 2018 06:04:27 +0100 From: Polytropon To: =?UTF-8?B?5pa55Z2k?= Cc: freebsd-questions@freebsd.org Subject: Re: Problems removing orphan packages Message-Id: <20180112060427.b0a1fabc.freebsd@edvax.de> In-Reply-To: References: Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:iaitGM2Un5pv3Kxi7mSTMoQq/T1G9Cj62rHzAZrPnKw8Vslq41F ro8KBCyLfb2d7MbsEgjHXNrlNwNbxeZAiHjBllNuYM5mct81QMBPsrcw2eoGPRxtUWppI4q 8RHJe4w/GKZImT8+VBngE4OYdDdSrQYBk2FSzTTh9UOJCGcAw4xhud6rX0/Z9A4RKD+qqbi pnWn0X/E7GRS98tgtEc5A== X-UI-Out-Filterresults: notjunk:1;V01:K0:sN/xLrxCjOc=:ackQ3r20A4lK1ba18ldzsH +4L/KrjvnBq5di6WUiCLG3Il+ugH/VoO5idWpKWlYiZUIuU1ER7OJm5aamBeQMzxyr+i+nTRr cF5WrZyAiVqX3WUOpq//5kDZ9Ev2dPKQxONrlrJsyYNAy7BWRHFZo5Tf4s1iNO8K5GuNjdxKv 8Bq6eakCXi597Vx5nbPmD9YRmcDmIisJpOnEGHr9Y2GY/7Bb4TJEEbeIhg7WyrIyXjb3yyn5E iQWWcDK/lkjC2FBfx6YJ2oigrPXRglTtjht5KTf0fYz9thay7VgSQdD84eREI5ww4jAWWvAFo gLXVgdZjK3YujoFp6YFNhLx5Uu+zgVHLSK6BnK5LuNQbaje0/s8zeCFo+UWDeRQkN0hSSb730 NhhCSKKSnMJqEet8jrg+4JSaGzJ9oH5xghcMwYmbLKLIZqRVqoE8R9uWQGOcS/5g9nUB9hD/c azIOJl+uec4E/xL8Iqhury4ZZjN4MX8wXaEek24G10LQKnKjeoB9GiakEXDFCd0xxSd5KeGCq b2Pe3TmKGayTAuWYf/sHsnrMhTvj/2QSFG0ZVA/owZSMfmXZSOoI7mmfw2+CQs4J9I6+Cjccm 9j3Jxm159xV1wrUfLJmKhJOxrA0rHUuQu6tboCkChb4nr35k50EvK48Tw7NiQcu35Ey/lVz+x M6iiVq2brQ9JzgpvXTYfEFcd4IK6LTioGzvYLx0q6s/DzamIDyZN0NR3t/oN0xQR+g68jm2H1 QDuxuF9hbc4O/ws/W8ugL6qUXUC9Od9uJ7F8njwbbcdFnejV5U0LU+Shlfg= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2018 05:04:38 -0000 On Fri, 12 Jan 2018 12:22:08 +0800, 方坤 wrote: > Last week, I ran `cd /usr/ports/devel/git ; make install clean` to install > the Git package, > I found that the "/deve/bison", "/shells/bash" and "www/w3m" packages also > installed > as the "devel/git" package need them. > > Today I ran `portmaster -s` to uninstall unused packages, I found the > "/deve/bison", > "/shells/bash" and "www/w3m" packages were on the listed. So I uninstalled > all the > packages in that list. > > I didn't understand why portmaster thinks that the "/deve/bison", > "/shells/bash" and > "www/w3m" packages were unused packages. So I ran > `cd /usr/ports/devel/git ; make install clean` again, I found that the > "/deve/bison", > "/shells/bash" and "www/w3m" packages installed again. > > Is anyone can teach me why? This looks strange. Git's Makefile doesn't specify w3m, bison or bash as a dependency directly (not for running and not for building git, if I read it correctly), so those seem to come from one of Git's dependencies, which are p5-Error, libpcre, p5-Authen-SASL, curl, libexpat, p5-Term-ReadKey, xmlto, and cvsps (depending on actual build configuration). Maybe if you further follow "dependency hell", you'll finally find out where the three port requirements in question originate from. By the way, if you're building with the default configuration, you could try to "pkg install git" and see if the three other ports are installed (as dependencies), which I assume would _not_ be the case. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Fri Jan 12 06:10:38 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27801E74C53 for ; Fri, 12 Jan 2018 06:10:38 +0000 (UTC) (envelope-from zainco30@gmail.com) Received: from mail-yb0-x231.google.com (mail-yb0-x231.google.com [IPv6:2607:f8b0:4002:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D781378F04 for ; Fri, 12 Jan 2018 06:10:37 +0000 (UTC) (envelope-from zainco30@gmail.com) Received: by mail-yb0-x231.google.com with SMTP id a82so2231506ybg.1 for ; Thu, 11 Jan 2018 22:10:37 -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=F6hviXHCp6I1DwFCgId46XZ2Wvn5yYfH2+ujJ0TzwwA=; b=mLhsSFDtKlC0bfmgHJ6P5SnMrK9jXEubzovgU7BfnOUI6908K0UHJTIY7E772YuXjV PXTRkiuQuXdULHOl0qRIY3EOkZ0TSilEzYHNMbxqLG2MaLvteYEyow8bpIyqSA6mIrmx Rtk9ZIGDeMMGeylQrDZG9rU+yvYQiqHtCQ+Tz8jxKv0TLs6OdP8Ffwa1TwCXO9rni/R8 Pxqv1DH5+xGXyoMS2tbu2sgWE5fmrv0227lsrrNKQouW3bTDlWoPmfafWnGSbFImFGLx AsKiiUq4obF9myeUJ0Onz2Tz+7+SnNHt7Q5rM4y/RAJcQpSpb/lGimVP2FadgHONcpXS +Uog== 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=F6hviXHCp6I1DwFCgId46XZ2Wvn5yYfH2+ujJ0TzwwA=; b=j9ZYX4+dz/bTRzim0zYOZvWXCAN69v5M9fQTFk282U6vQ2hGBNlZ48X5edYZ/QxE0/ rp+D1t5DrbbpBoZayw5AZqI6Al51NrIRSZsmLSWxVhGoWCVNhEBbymPnQ1gLzy4/GxMh 82gMXlSACuioiKQGuT8GqCtAdVnazTxhfhCeiwfa6r1wpgVFLMTM9gijyMWfFD34T+Vu 4p5UESzVCzJ7el7bsD4Nskfdxt9XFVQaOs1pE/8dDOA/W4cBkO4vNHm96XvMh3FycYv/ tF8C3e6km8p2uHFVSrx2FxyNBmPCJRmirY7RYW6ZxYer2kP2NeelhyV5hiBmMBTWsV3c 2U2A== X-Gm-Message-State: AKGB3mImmI8leyI+FfgUQeQhQX1d27J1NmwaVSvrnXwMY9WZ9vH0vn06 9HiEI45Xm3+LFprDnnrlfVVC1dWjkIY3/ynbfKyFyQ== X-Google-Smtp-Source: ACJfBotk9WKlbhpOO9lh+d/wWu/N4y+yxzAEsSg/d2P7HngKswrDW9/M1ldvZJREAv1g/a/8WrkaLD9C0Fx8N27krq8= X-Received: by 10.37.35.141 with SMTP id j135mr13061954ybj.489.1515737436781; Thu, 11 Jan 2018 22:10:36 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.130.65 with HTTP; Thu, 11 Jan 2018 22:10:36 -0800 (PST) In-Reply-To: <1DFDF803-4D86-42F8-A22E-4A9077608982@theory14.net> References: <1DFDF803-4D86-42F8-A22E-4A9077608982@theory14.net> From: "Zainelabdeen S.A Elgraeed" Date: Fri, 12 Jan 2018 08:10:36 +0200 Message-ID: Subject: Re: HAST questions To: Chris Gordon Cc: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2018 06:10:38 -0000 > It really depends on the details of the application on what options you have and what the best way to do this may be. we host dynamic content with MySQL databases like Moodle and OJS. I want for storage to be active/active but HAST is master/backup so I can be used for failover only. is HAST support *DRBD* ? or what another technology can use for HA and LB for storage? On 12 January 2018 at 02:55, Chris Gordon wrote: > There are many different ways to increase the availability of a system. > It really depends on the details of the application on what options you > have and what the best way to do this may be. > > Are these web servers hosting static content? Is the content read-only or > is there something taking writes? Is there a database involved? > > If you can provide some details of what is running on these web servers, > we can help guide you on some options you have. > > Thanks, > Chris > > > > On Jan 11, 2018, at 7:06 AM, Zainelabdeen S.A Elgraeed < > zainco30@gmail.com> wrote: > > > > hello, i am Zainelabdeen system administrator at the university of Gezira > > Sudan. > > > > we have a project to use Freebsd as web hosting, we want to use jail for > > each web server. > > > > 1.how can I provide high availability for jail between two host machine? > > 2. is hast can be used to do this task? > > > > thanks > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "freebsd-questions- > unsubscribe@freebsd.org" > > From owner-freebsd-questions@freebsd.org Fri Jan 12 08:34:09 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7D077E7ABFA for ; Fri, 12 Jan 2018 08:34:09 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (mail.dpedia.de [178.254.4.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 311C37DBA4 for ; Fri, 12 Jan 2018 08:34:08 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [2.247.248.217] (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 1eZuml-0002P4-Fl for freebsd-questions@freebsd.org; Fri, 12 Jan 2018 09:33:59 +0100 Received: from localhost.my.domain (localhost [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id w0C8XtDd013705 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 12 Jan 2018 09:33:55 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id w0C8Xsat013704 for freebsd-questions@freebsd.org; Fri, 12 Jan 2018 09:33:54 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Fri, 12 Jan 2018 09:33:53 +0100 From: Matthias Apitz To: freebsd-questions@freebsd.org Subject: eclipse && CDT for C/C++ Message-ID: <20180112083353.GA13670@c720-r314251> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Operating-System: FreeBSD 12.0-CURRENT r314251 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. User-Agent: Mutt/1.8.0 (2017-02-23) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 2.247.248.217 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2018 08:34:09 -0000 Hello, I've some questions/issues with the CDT for C/C++ within eclipse and how to configure correctly the tool chain and CODAN (the Code Analyzer) for using /usr/bin/c++ ... what would be the best mailing list in FreeBSD to discuss this? freebsd-java@ ... ? matthias -- Matthias Apitz, ✉ guru@unixarea.de, ⌂ http://www.unixarea.de/ 📱 +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub From owner-freebsd-questions@freebsd.org Fri Jan 12 08:46:04 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1C220E7B3D7 for ; Fri, 12 Jan 2018 08:46:04 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (mail.dpedia.de [178.254.4.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D27AC7E137 for ; Fri, 12 Jan 2018 08:46:03 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [2.247.248.217] (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 1eZuyO-0005cv-O1 for freebsd-questions@freebsd.org; Fri, 12 Jan 2018 09:46:00 +0100 Received: from localhost.my.domain (localhost [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id w0C8jv4x013860 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 12 Jan 2018 09:45:57 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id w0C8juDX013859 for freebsd-questions@freebsd.org; Fri, 12 Jan 2018 09:45:56 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Fri, 12 Jan 2018 09:45:56 +0100 From: Matthias Apitz To: freebsd-questions@freebsd.org Subject: fetch is waiting on input on stdin Message-ID: <20180112084556.GA13812@c720-r314251> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="5mCyUwZo2JvN/JJP" Content-Disposition: inline X-Operating-System: FreeBSD 12.0-CURRENT r314251 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. User-Agent: Mutt/1.8.0 (2017-02-23) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 2.247.248.217 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2018 08:46:04 -0000 --5mCyUwZo2JvN/JJP Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, This is on: FreeBSD c720-r314251 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r314251M: Fri Jun= 30 08:50:03 CEST 2017 guru@c720-r314251:/usr/obj/usr/src/sys/GENERIC = amd64 Yesterday I was building some port which fetches the disfiles like this command: # fetch ftp://sunsite.informatik.rwth-aachen.de/pub/mirror/eclipse.org/tool= s/cdt/releases/9.0/sr1/features/org.eclipse.cdt.msw_9.0.1.201607151550.jar The fetch was hanging for ever. My first thinking was DNS, but then I monit= ored the fetch cmd with truss(1) and saw, that it was awaiting STDIN input. Only using 'make < /dev/null' was able to fetch all the distfiles. Is this something new or some bug? 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 --5mCyUwZo2JvN/JJP Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEXmn7rBYYViyzy/vBR8z35Hb+nREFAlpYdcIACgkQR8z35Hb+ nRHB5w//QHJrqMF2ZnuKfdja/9tK8q69FgaZyyIcpuZpL9zId+XhtKYyvqTmamHK XAqrTqfGZqay3Q3HzQz1OK5rp6xWD01H3+2+2cUw/89RjqzO/gSFaU2kjC7lYFvg x0UzRb/zUyTDfI1A6YJMbuVeRs7XSKWsRntMs+1QLUNVECi0OnJarulK8aQEoV7M oP0QEtmHEtHq2LYwz5yJAuKkdlWPB9QUyAvRJBzTAUDy099PlVbCTGbZ+diIP791 h89EOyPokxA6IzNB7CzK7Sa01uW3zjwjrWF23Y/Sg4H6zUzcs5rok4f0Ala7BCqY 2P1KJTg7a+yuLKKtvMuKFU2wsFNOVGda5BtejHQ+GZX/PVN/X4peO+QrqtOXYB8w Ye+tfvbnz3SbNsVybn5eGQjwZ8Y2Tm03KHWCC47MBBDNcyFXqTzDpAlgwmLhFpnn WWvWgRZOQl6Jxe4inXR4FGrMVjhqa+tIwE1UhGP4LMwz+Dst7ZVI37mMavaSwHlc 327xbIOk9/Rhiq/HsuwAitVehFpt4jgpVwSU4TMo354ME/Mxv6t+agQYWnzLE5gA 8CBPLHLUn+JQiclA1i7gsr9j8w6/fFkvh8n/fIF2GzHPNGV/zNfj4lQjrtsAkz7O /XrAHw8JJ1hTJ/JGZJ94+ON7HxvVNxYOcd7Loje/L2Ob7UvkBME= =meST -----END PGP SIGNATURE----- --5mCyUwZo2JvN/JJP-- From owner-freebsd-questions@freebsd.org Fri Jan 12 10:01:18 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 71DA4E7EEEB for ; Fri, 12 Jan 2018 10:01:18 +0000 (UTC) (envelope-from parker.louis@weboptimizes.com) Received: from mail-qt0-x241.google.com (mail-qt0-x241.google.com [IPv6:2607:f8b0:400d:c0d::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 3BB28814E6 for ; Fri, 12 Jan 2018 10:01:18 +0000 (UTC) (envelope-from parker.louis@weboptimizes.com) Received: by mail-qt0-x241.google.com with SMTP id d4so5361545qtj.5 for ; Fri, 12 Jan 2018 02:01:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=weboptimizes.com; s=google; h=mime-version:sender:from:date:message-id:subject:to; bh=7ZKdVwi3k90E6FL5gFB7evz6qGW0eBcat6zTQtb7vG4=; b=LfFHPC35xZBsaCrCUeO1cghnv/hgBSky8m3wNcfYn/7fE3wyYDYOnzXFCw0eniYoqI rq8rqXAiC6JY+qw/CADkJnZ7MEC7N1xHFXHGyjlXJort6BBBfu6zUuChw/TwmAxaLWaF FVZP0nGV6QjjVwksokasrkOwoJWcgX+6dSbYQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=7ZKdVwi3k90E6FL5gFB7evz6qGW0eBcat6zTQtb7vG4=; b=mFHYGE89ZcfAohfIVIkUZmA04OsuRbcqxepmWSQ1onYtsazRaYDOEWGGWtb6nKm1zj GhTtmr2Phizfc3vR0KdRosBOPhrG9l/CvsiCg7hQTnXJiWfbX+6gfD4OWt7/iYhqyw6b X7/LRbDMSnlxPkfggcfIKSuHU3IBipqmteHqHZvd9WQCQzD9OGbiQWF1+xjXUaVrFBJ7 0dPkaOm3WdP7ItD0eshNq7Ga9Y3Y3hSHDrGm8ZbBvVw2dNQvkvbYjEpq2faJrIRcOm+3 aXcL9DVoIT25vCpArLdrz0I51k0DWoQPkjp5/v5MPr85fcPtYq9OUWbZMxhJmMcSjjGA A/Rw== X-Gm-Message-State: AKwxytdwI+hnFGtin+oBxtkwgzxdgmZQc4YKAp+IE4aDDLbd8X0SABLZ gUkevpa4QLjkbAu7onIlU3G79Y8HY9x5ipVYqa77A/V/ X-Google-Smtp-Source: ACJfBosnSQUbB4U9TW2G38rFOdXJXUaDstiPFH9wMD5mAN1dc9aUMpefIQJryGWl7He5AevASvg80Txq4KBLZIhvSyM= X-Received: by 10.237.59.131 with SMTP id r3mr35272038qte.231.1515751276856; Fri, 12 Jan 2018 02:01:16 -0800 (PST) Received: from 52669349336 named unknown by gmailapi.google.com with HTTPREST; Fri, 12 Jan 2018 02:01:16 -0800 MIME-Version: 1.0 Sender: Louis Parker From: Louis Parker Date: Fri, 12 Jan 2018 02:01:16 -0800 X-Google-Sender-Auth: oyz5tIIQL8buWdQsy3sM2ZybgBw Message-ID: Subject: New Ways to Improve Your Google Rankings To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2018 10:01:18 -0000 Hello freebsd.org Team, *Get your website on Google=E2=80=99s Front Page search:*We would like to h= ave a discussion with you regarding the web promotion strategy for your website. We wish to work out a proposal to strengthen the online presence of your website, via, a strategically planned web promotion campaign. In today=E2= =80=99s online era, you should be focusing on the new revolutionary ways of generating traffic. We were curious to know if you were aware that are a few issues bugging your website. Sorting out these will help you get the best returns out of your website. Your website seems to be attracting traffic, but this traffic is almost stagnant and limited, which affects potential sales as you move forward. Your website doesn't feature in Google's first search page for some of the major keywords in your niche, which affects visibility. Your website has been diagnosed with coding issues, which affects ranking. Your back links profile is not efficient enough to help your search engine visibility. Your website is currently not being properly promoted online, which is affecting your marketing strategy and goals Your presence in social media platform (*Facebook, Twitter, etc.*) is minimal. This is depriving you of a huge market of prospective referral clients. We excel in running promotional online marketing campaign for websites. We have a host of ethical services and techniques, which you can utilize to improve your website's performance. We could send you more details regarding your present website status; we would be glad to share =E2=80=9C*= PRE SEO REPORT=E2=80=9D* or =E2=80=9C*WEBSITE ANALYSIS REPORT* for *FREE=E2=80=9D*. *Kindly revert back if you are interested, then we can send you more detail about package which will improve your sales & website ranking too.*Hope to get early response. Best Regards, *Louis Parker | Senior Sales Advisor*______________________________ ___________________________________________ *PS1:* Please answer to our email with *=E2=80=9CInterested*=E2=80=9D or *= =E2=80=9CNot Interested*=E2=80=9D so that we will know the status of your inquiry and act accordingly. If you are interested then I will send more details on our *=E2=80=9Ccorporate ide= ntity=E2=80=9D, =E2=80=9Ccompany profile=E2=80=9D, =E2=80=9Cwhy you should choose us?=E2=80= =9D, =E2=80=9CPrice list=E2=80=9D, =E2=80=9Cmoney back guarantee=E2=80=9D*. *PS2:* I found your site using Google search and after having a look over your website I recommend you to implement future technologies such as HTML5 and Responsive Design to make your site more accessible in mobile phone, tablets, desktop etc. From owner-freebsd-questions@freebsd.org Fri Jan 12 12:09:47 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C51DE60313 for ; Fri, 12 Jan 2018 12:09:47 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (mail.dpedia.de [178.254.4.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1C2472E76 for ; Fri, 12 Jan 2018 12:09:46 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [2.247.248.217] (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 1eZy9W-0004Fq-B7 for freebsd-questions@freebsd.org; Fri, 12 Jan 2018 13:09:42 +0100 Received: from localhost.my.domain (localhost [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id w0CC9cIw014763 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 12 Jan 2018 13:09:38 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id w0CC9bNu014762 for freebsd-questions@freebsd.org; Fri, 12 Jan 2018 13:09:37 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Fri, 12 Jan 2018 13:09:37 +0100 From: Matthias Apitz To: freebsd-questions@freebsd.org Subject: Re: fetch is waiting on input on stdin Message-ID: <20180112120937.GA14731@c720-r314251> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , freebsd-questions@freebsd.org References: <20180112084556.GA13812@c720-r314251> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="lrZ03NoBR/3+SXJZ" Content-Disposition: inline In-Reply-To: <20180112084556.GA13812@c720-r314251> X-Operating-System: FreeBSD 12.0-CURRENT r314251 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. User-Agent: Mutt/1.8.0 (2017-02-23) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 2.247.248.217 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2018 12:09:47 -0000 --lrZ03NoBR/3+SXJZ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable El d=C3=ADa viernes, enero 12, 2018 a las 09:45:56a. m. +0100, Matthias Api= tz escribi=C3=B3: >=20 > Hello, >=20 > This is on: >=20 > FreeBSD c720-r314251 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r314251M: Fri J= un 30 08:50:03 CEST 2017 guru@c720-r314251:/usr/obj/usr/src/sys/GENERIC= amd64 >=20 > Yesterday I was building some port which fetches the disfiles like this > command: >=20 >=20 > # fetch ftp://sunsite.informatik.rwth-aachen.de/pub/mirror/eclipse.org/to= ols/cdt/releases/9.0/sr1/features/org.eclipse.cdt.msw_9.0.1.201607151550.jar >=20 > The fetch was hanging for ever. My first thinking was DNS, but then I mon= itored > the fetch cmd with truss(1) and saw, that it was awaiting STDIN input. >=20 > Only using 'make < /dev/null' was able to fetch all the distfiles. Is > this something new or some bug? >=20 I have here the relevant part of the sys calls: - connect to port 21 - FTP server sends greeting - fetch reads from stdin until EOF seen - fetch sends FTP login and password connect(3,{ AF_INET 137.226.34.227:21 },16) =3D 0 (0x0) fcntl(3,F_SETFD,FD_CLOEXEC) =3D 0 (0x0) setsockopt(0x3,0xffff,0x800,0x7fffffffdc7c,0x4) =3D 0 (0x0) read(3,"2",1) =3D 1 (0x1) read(3,"2",1) =3D 1 (0x1) read(3,"0",1) =3D 1 (0x1) read(3," ",1) =3D 1 (0x1) read(3,"W",1) =3D 1 (0x1) read(3,"e",1) =3D 1 (0x1) read(3,"l",1) =3D 1 (0x1) read(3,"c",1) =3D 1 (0x1) read(3,"o",1) =3D 1 (0x1) read(3,"m",1) =3D 1 (0x1) read(3,"e",1) =3D 1 (0x1) read(3," ",1) =3D 1 (0x1) read(3,"t",1) =3D 1 (0x1) read(3,"o",1) =3D 1 (0x1) read(3," ",1) =3D 1 (0x1) read(3,"S",1) =3D 1 (0x1) read(3,"u",1) =3D 1 (0x1) read(3,"n",1) =3D 1 (0x1) read(3,"S",1) =3D 1 (0x1) read(3,"I",1) =3D 1 (0x1) read(3,"T",1) =3D 1 (0x1) read(3,"E",1) =3D 1 (0x1) read(3," ",1) =3D 1 (0x1) read(3,"C",1) =3D 1 (0x1) read(3,"E",1) =3D 1 (0x1) read(3,"U",1) =3D 1 (0x1) read(3,"R",1) =3D 1 (0x1) read(3,"\r",1) =3D 1 (0x1) read(3,"\n",1) =3D 1 (0x1) fcntl(0,F_GETFL,) =3D 2 (0x2) fstat(0,{ mode=3Dcrw--w---- ,inode=3D96,size=3D0,blksize=3D4096 }) =3D 0 (0= x0) ioctl(0,TIOCGETA,0xffffd660) =3D 0 (0x0) lseek(0,0x0,SEEK_SET) =3D 0 (0x0) read(0,0x801a85000,4096) =3D 0 (0x0) close(0) =3D 0 (0x0) poll({ 3/POLLOUT|POLLERR },1,100000) =3D 1 (0x1) writev(0x3,0x7fffffffdb50,0x2) =3D 16 (0x10) (USER anonymous\r\n) read(3,"3",1) =3D 1 (0x1) read(3,"3",1) =3D 1 (0x1) read(3,"1",1) =3D 1 (0x1) read(3," ",1) =3D 1 (0x1) read(3,"P",1) =3D 1 (0x1) read(3,"l",1) =3D 1 (0x1) read(3,"e",1) =3D 1 (0x1) read(3,"a",1) =3D 1 (0x1) read(3,"s",1) =3D 1 (0x1) read(3,"e",1) =3D 1 (0x1) read(3," ",1) =3D 1 (0x1) read(3,"s",1) =3D 1 (0x1) read(3,"p",1) =3D 1 (0x1) read(3,"e",1) =3D 1 (0x1) read(3,"c",1) =3D 1 (0x1) read(3,"i",1) =3D 1 (0x1) read(3,"f",1) =3D 1 (0x1) read(3,"y",1) =3D 1 (0x1) read(3," ",1) =3D 1 (0x1) read(3,"t",1) =3D 1 (0x1) read(3,"h",1) =3D 1 (0x1) read(3,"e",1) =3D 1 (0x1) read(3," ",1) =3D 1 (0x1) read(3,"p",1) =3D 1 (0x1) read(3,"a",1) =3D 1 (0x1) read(3,"s",1) =3D 1 (0x1) read(3,"s",1) =3D 1 (0x1) read(3,"w",1) =3D 1 (0x1) read(3,"o",1) =3D 1 (0x1) read(3,"r",1) =3D 1 (0x1) read(3,"d",1) =3D 1 (0x1) read(3,".",1) =3D 1 (0x1) read(3,"\r",1) =3D 1 (0x1) read(3,"\n",1) =3D 1 (0x1) getlogin(0x800ddfa10,0x21) =3D 0 (0x0) __sysctl(0x7fffffffdc90,0x2,0x7fffffffdd65,0x7fffffffdc88,0x0,0x0) =3D 0 (0= x0) poll({ 3/POLLOUT|POLLERR },1,100000) =3D 1 (0x1) writev(0x3,0x7fffffffdb50,0x2) =3D 25 (0x19) (PASS guru@r314251-amd64\r= \n) read(3,"2",1) =3D 1 (0x1) read(3,"3",1) =3D 1 (0x1) read(3,"0",1) =3D 1 (0x1) read(3," ",1) =3D 1 (0x1) read(3,"L",1) =3D 1 (0x1) read(3,"o",1) =3D 1 (0x1) read(3,"g",1) =3D 1 (0x1) read(3,"i",1) =3D 1 (0x1) read(3,"n",1) =3D 1 (0x1) read(3," ",1) =3D 1 (0x1) read(3,"s",1) =3D 1 (0x1) read(3,"u",1) =3D 1 (0x1) read(3,"c",1) =3D 1 (0x1) read(3,"c",1) =3D 1 (0x1) read(3,"e",1) =3D 1 (0x1) read(3,"s",1) =3D 1 (0x1) read(3,"s",1) =3D 1 (0x1) read(3,"f",1) =3D 1 (0x1) read(3,"u",1) =3D 1 (0x1) read(3,"l",1) =3D 1 (0x1) read(3,".",1) =3D 1 (0x1) read(3,"\r",1) =3D 1 (0x1) read(3,"\n",1) =3D 1 (0x1) --=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 --lrZ03NoBR/3+SXJZ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEXmn7rBYYViyzy/vBR8z35Hb+nREFAlpYpX4ACgkQR8z35Hb+ nRFoSBAAoFBLX55gq153hzMphrzMYFQE57NHPJePl0HOREl8FxS/o+kW4iez/U4h zj3LdqDWZi602jit0AhdDWvcTLxbjA23o0rgDhwUR2rG7cX8IziHF60O3JGxIG+I K10WrHbWBQtsupviK3mom2gy/q1H0rE0rWqZcCX2oSES96B90OGGQv5oDCDfyyFx da2/6rVG6Wf0wZQkNFEdrryox/6P4ryNuYblC0HOIPUns2A10VOogEIzDYnfVm+w XSjzaTQmCEHopcEavb/NJ7qmhS3qZKncPy4oqH0diPFpT1AGSMiuLrDXQNIdCnvE nyo7DWW6zYsmqE5+Zn9lvEvtohcWK7TacDENNj02My0RuZyiRgP5XNceg3pXBVjx 1Wv7hbsdH6GfcTa9AttL3VJkAHEhwUVbTNvxgZSAt63ZPe1GLImVF9/zokB7jQnq duhBftM0dWXQdT4ig+Arx9ypFjhDXKLkl782Rtylwm0eWK9Mv2JUrFfqFOMmy0tv UkeEYaBqZSpjxPAWRL/xnmdbGgYqgPO1PH7FY/h/vaTJaIgNz+x7tt/XXWLxKB4e dpXysxjqwtfbzLEP9kocQ6J/7dOwycn5ARveNcx9h7Npi69mhVtHVsD6FBS7STaE X0fCJVDxVjhYWmyIA8JArmDjPcRWuLxqBpipLX8pyWjvyebO9zU= =ejNJ -----END PGP SIGNATURE----- --lrZ03NoBR/3+SXJZ-- From owner-freebsd-questions@freebsd.org Fri Jan 12 17:08:56 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1459CE706F0 for ; Fri, 12 Jan 2018 17:08:56 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D24757405D for ; Fri, 12 Jan 2018 17:08:55 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-io0-x229.google.com with SMTP id n14so6565461iob.4 for ; Fri, 12 Jan 2018 09:08:55 -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=N7BLcNoyUbdCQ5Owsp81xfBV016XfdHqbx40lRLh1ME=; b=f0oH3jlzhqZNlt4aqpNggvbh2DnIOKBxutncIBQ+H93yi7Ht6QDsQVc3F0Le1/tMCW LZRCaOdj57HJjPBODOcfUM2YOLG679YjE/RgHXtcchG3yIeTDlzL9YjyKU6TyUPX59U7 gN46wRsIo6ZeHhITFKQb37cCCo4skWfDRgn1Rt/I4ysEcR2qh00n9esgQ1eunt0oinER eqMYwSPnFP0k71Rf7QJhnKMQTj3e48Xa3SkgVIkSJCZ+jApoLiBNjt4KMWolB6MCC9EH fiZL809shelb5dQSX5f3FFzI8gWSxJfWL3AU5GDY84LngwtmIZPohn/3EaSfMbANmDtI vf5g== 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=N7BLcNoyUbdCQ5Owsp81xfBV016XfdHqbx40lRLh1ME=; b=ikreiB86g9TExFf0GZhauff4j8jwcwVaO2OZEknOgpD30h7yralRDqcrqNIF349ezp 3OPyvo3aMtJNBIadM3mdImsl6Z4XA8Hy7JR5U1jo5LJiMysZTXYSWKHaQOKWf/EtzlnQ QjmN5Go9AqVdvQrYMlzK/v+j34tV9KtbUs2k4VovYbIe2LKMPNKyssSSx9vXhDNmYaXw 8HiBPriqed72+w8au+9P0VLxFcj+w2TNl9fXMR5zarcYPFgvBgHuuPZ4563yg2KiBFe0 HP1Osgo2bdJfutEFT0ZEvhtIQ8dexullByM1+Kw/aKKzoFR5Q4KSH3v/8KjBPpKf9PQm PsXg== X-Gm-Message-State: AKwxyte+4biZGEM9dmjKiMDBNmlhk421agSarJHB+wMaLiJaNdWHY0rr y7HcumWtUl5YE3IgThR2H8c9EM42VIsRVUGETjpXzg== X-Google-Smtp-Source: ACJfBousi40TTbiUmqLnUiylHaupJv1maZQVXkG3ekQUQSZMtysb2Zpowov6f46HgQJK028sU4/qlqNTDys5nd1XR34= X-Received: by 10.107.16.8 with SMTP id y8mr5370496ioi.213.1515776934498; Fri, 12 Jan 2018 09:08:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.193 with HTTP; Fri, 12 Jan 2018 09:08:53 -0800 (PST) From: blubee blubeeme Date: Sat, 13 Jan 2018 01:08:53 +0800 Message-ID: Subject: msdosfs_iconv issues To: FreeBSD Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2018 17:08:56 -0000 according to man msdosfs I can run a command like this: mount_msdosfs -L en_US.UTF-8 /dev/da0s1 $HOME/usb this always returns operation not permitted. looking into that a bit further it seems that I need to load a msdosfs_iconv.ko and that needs to be root, using /etc/rc.conf or /boot/loader.conf the module is loaded at boot time but I still get operation not permitted. if I remove the locale option from mount_msdosfs the file loads but of course, I cannot read any of my documents. This seems a bit odd but I understand that constantly loading msdosfs_iconv can DDoS the system fine. How can I mount my drives with locale or at least proper utf-8 encoding? From owner-freebsd-questions@freebsd.org Fri Jan 12 20:21:44 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1A5CDE79FC7 for ; Fri, 12 Jan 2018 20:21:44 +0000 (UTC) (envelope-from jd1008@gmail.com) Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::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 DAFCE7DC61 for ; Fri, 12 Jan 2018 20:21:43 +0000 (UTC) (envelope-from jd1008@gmail.com) Received: by mail-io0-x22e.google.com with SMTP id c17so7156454iod.1 for ; Fri, 12 Jan 2018 12:21:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:subject :content-transfer-encoding; bh=4bHLpOyeW6vN4DZfHQyEU6FP4RKGVYW0/bdOG0uUfHE=; b=WpA3yaKE8am7rDu0D0Y+gsPMgmqsrx1xat77fFXdFVK/H3UzEpytNReVTQzlVrGZuR zSKW08XdTQcWUdbskvcR0ANEj0qWSXxIrnNsp0FNJT/Yy9x5cGQQLfY9nvCLn9Y+2CH2 OLKQF39is5nukwhFTpCr27gh46ZyYDt6ApZgBQhAqrWQUBZ2Uc9a2jcQiQAx6bllgIcW edh+DYY3aZjwAUzjXBZwVo8QPOynliiKpzZK3W04LZy7g658LNicHUfpJZmRTQ2LmS/z ocrkzSHbwDiuE+5v8Diz+lvqQjRPjLbR0VrN98aD1EPdYr9nfCk9Ghv638O+vTs9dD2T eT3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:content-transfer-encoding; bh=4bHLpOyeW6vN4DZfHQyEU6FP4RKGVYW0/bdOG0uUfHE=; b=iqS12HIwmv6Lm980y6j7dmpla+EsBQOGtkw8Bj7R3J/1Ru3vjiCKD+R7U3/BFtYvUN KHIP/vmmFvT/lhQtbgQEZvgxkUxJTy4zEIuMJLtLuW3kGvSUI/vO4ao3eTFurd21pHcw KY2Ewm0rtwRVF12NQFdWYBSPpWoQ+ii5exl8BQhlMx5rUIoHR4r8h+wgsFrm5c5UTtGX o/LKoAQcYsG82zqi4VmNvZ+rAZgtxn/EyybzmVtV3MapSjywFQXjlM7qR8tsSD/eHPMw 3FYV6PrvD8QYxohwg1lds9m+pkbV1KX7+MPxKRWuL6MHUpd3VUVfrcKI+X8/CqHnb6W+ IKUQ== X-Gm-Message-State: AKwxyte7P35TIIHO+k9LLP07ggFP7ogexXESNp+VJtvL21AwsPvjTK16 lzbhUsKGN3S7ukF51lrTmKzoRA== X-Google-Smtp-Source: ACJfBounWRIcR9j4g8M4wSBYi86GCwNFn/D/Y5iyZFJMpV9eDgOHkkMOvZqmvg8fJSWYG/alkLuvGw== X-Received: by 10.107.16.71 with SMTP id y68mr339224ioi.266.1515788503014; Fri, 12 Jan 2018 12:21:43 -0800 (PST) Received: from localhost.localdomain (50-243-4-3-static.hfc.comcastbusiness.net. [50.243.4.3]) by smtp.googlemail.com with ESMTPSA id t8sm1687165ite.2.2018.01.12.12.21.41 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Jan 2018 12:21:42 -0800 (PST) Message-ID: <5A5918C9.4060200@gmail.com> Date: Fri, 12 Jan 2018 13:21:29 -0700 From: JD User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: FreeBSD Users Subject: The Intel Management Engine: an attack on computer users' freedom Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2018 20:21:44 -0000 Will *-BSD distro OS'es be able to defeat or disable this attack? -------- Forwarded Message -------- /Read and share online:/ https://www.fsf.org/blogs/sysadmin/the-management-engine-an-attack-on-computer-users-freedom Dear Subscriber, "The Management Engine (frequently abbreviated as ME) is a separate computer within Intel computers, which denies users control over their computers, by forcing them to run nonfree software that cannot be modified or replaced by anyone bu t Intel. This is dangerous and unjust. It is a very serious attack on freedom, privacy, and security of computer users. " So writes Denis GNUtoo Carikli, free software activist and one of the co-founders of the Replicant project in a recent article titled "The Management Engine: an attack on computer users' freedom." Intel ME lives inside every computer with an Intel chipset. As a major producer of home and commercial computing techno logy, Intel ME can seem not just pervasive, but ubiquitous. This infringement of freedom is in homes around the world - - and there's nothing that can be done about it. With security issues like the Spectre and Meltdown vulnerabilities discovered in Intel chips -- the most popular chipse t among x86 users -- it's become more important than ever to talk about the necessity of software freedom in these deep ly embedded technologies. In order to help a larger audience understand Intel Management Engine and the way it affects developers and users alike , Carikli began working on a book, a section of which he shared with the FSF for publication. Free Software Foundation /Read and share online: https://www.fsf.org/blogs/sysadmin/the-management-engine-an-attack-on-computer-users-freedom/ Dear Subscriber, "The Management Engine (frequently abbreviated as ME) is a separate computer within Intel computers, which denies users control over their computers, by forcing them to run nonfree software that cannot be modified or replaced by anyone but Intel. This is dangerous and unjust. It is a very serious attack on freedom, privacy, and security of computer users." So writes Denis GNUtoo Carikli, free software activist and one of the co-founders of the Replicant project in a recent article titled "The Management Engine: an attack on computer users' freedom ." Intel ME lives inside every computer with an Intel chipset. As a major producer of home and commercial computing technology, Intel ME can seem not just pervasive, but ubiquitous. This infringement of freedom is in homes around the world -- and there's nothing that can be done about it. With security issues like the Spectre and Meltdown vulnerabilities discovered in Intel chips -- the most popular chipset among x86 users -- it's become more important than ever to talk about the necessity of software freedom in these deeply embedded technologies. In order to help a larger audience understand Intel Management Engine and the way it affects developers and users alike, Carikli began working on a book, a section of which he shared with the FSF for publication. You can read and share this article online at FSF.org . Cheers, Molly Follow us on GNU social | Subscribe to our blogs via RSS | Join us as an associate member Sent from the Free Software Foundation, 51 Franklin St, Fifth Floor Boston, Massachusetts 02110-1335 UNITED STATES Unsubscribe from this mailing list. Stop all email from the Free Software Foundation, including Defective by Design, and the Free Software Supporter newsletter. From owner-freebsd-questions@freebsd.org Sat Jan 13 02:06:39 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 31E19E67EB9 for ; Sat, 13 Jan 2018 02:06:39 +0000 (UTC) (envelope-from dalescott@shaw.ca) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EE9A06C51C for ; Sat, 13 Jan 2018 02:06:38 +0000 (UTC) (envelope-from dalescott@shaw.ca) Received: from cds143.dcs.int.inet ([10.0.153.165]) by shaw.ca with ESMTP id aBDJeoyWsYy1iaBDKexc6E; Fri, 12 Jan 2018 19:06:32 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shaw.ca; s=s20150330; t=1515809192; bh=odbViB9mNKTZna+0z+JZs5AXNeKRJvaHJuGM9GHe37U=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=DQbRK6cDl8Yx22DfnGw1dIC4fvRwA/A5nuyyW+sRu12RnvrzQyy3WngG3lr+7qcH7 GrFpPPOchcgesbznbM+4d+2xhHYLXUWtz2cNpzrn3wmDJLfwnz3BpmZeAc/WbrI1cV gIYUkLK4o4tdJumHzIJ5jv0jPy43SvynvllYsRr68eBZ5ieDBtJNDs7MnvM6T7sQR9 c08EEiSHetvlKBq0uKy+ojHKPK+PpneL9jk9QkYFHl4nrvCEOgZAglwrUh8EcN8M48 BbpB8tvBRjvmZ9UqQDn40ZENlrOMAptqP0TvK6Udl4yiuhfi2pZmMOAB7WEUYgpNbV /SphuN8W8/kMw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shaw.ca; s=s20150330; t=1515809192; bh=odbViB9mNKTZna+0z+JZs5AXNeKRJvaHJuGM9GHe37U=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=DQbRK6cDl8Yx22DfnGw1dIC4fvRwA/A5nuyyW+sRu12RnvrzQyy3WngG3lr+7qcH7 GrFpPPOchcgesbznbM+4d+2xhHYLXUWtz2cNpzrn3wmDJLfwnz3BpmZeAc/WbrI1cV gIYUkLK4o4tdJumHzIJ5jv0jPy43SvynvllYsRr68eBZ5ieDBtJNDs7MnvM6T7sQR9 c08EEiSHetvlKBq0uKy+ojHKPK+PpneL9jk9QkYFHl4nrvCEOgZAglwrUh8EcN8M48 BbpB8tvBRjvmZ9UqQDn40ZENlrOMAptqP0TvK6Udl4yiuhfi2pZmMOAB7WEUYgpNbV /SphuN8W8/kMw== X-Authority-Analysis: v=2.2 cv=f8g4PK6M c=1 sm=1 tr=0 a=/UpIoJrLhaD689zIoPQAHQ==:117 a=FKkrIqjQGGEA:10 a=x7bEGLp0ZPQA:10 a=-IkFJk6PAAAA:8 a=pGLkceISAAAA:8 a=6I5d2MoRAAAA:8 a=1Qz73_4KnOqQjAFbXXUA:9 a=CjuIK1q_8ugA:10 a=CVJqwcv5tQBIVpD6-AwA:9 a=Xde0q9DYl_jXXEjR:21 a=_W_S_7VecoQA:10 a=QEXdDO2ut3YA:10 a=gRf6Gg_OHQNr-WVqdUp6:22 a=IjZwj45LgO3ly-622nXo:22 MIME-Version: 1.0 Subject: Re: [Shaw Suspected Junk Email]Re: OT: Max system physical memory From: Dale Scott In-Reply-To: <44wp0ofr1w.fsf@be-well.ilk.org> Date: Fri, 12 Jan 2018 19:06:29 -0700 (MST) Cc: Aryeh Friedman , FreeBSD Mailing List Message-Id: <380AC31B-C973-4430-9C24-E36B043665A0@shaw.ca> References: <44wp0ofr1w.fsf@be-well.ilk.org> To: Lowell Gilbert X-Mailer: Zimbra 8.6.0_GA_1200 (MobileSync - Apple-iPad4C4/1503.153) Thread-Topic: Max system physical memory Thread-Index: F48hMnPF4M8tWp9qsT1YoddVXji8Nw== X-CMAE-Envelope: MS4wfBb4nSXkj3w2e5ewmwLs9ddXEvDVFPzwh+PVuzYlfhd+R/h/uArB7k+Z+4EITOScSU9+UkgVMrJaNU+rQQcIS1K5VXHmHe4BmKziUUCX2KMgtd1gT6Q8 T5jQge/OBeR+2MNlneYAUkc7V2zN/8Sd7Zk31jYwU/+QnaCk1kCpRwahn11E8RUydgvpchqnRbyNokbDN0Mpblsprf7HnU0ZZ/k0G03TdMOYv3TU4EbcmIS7 iPksqFD1qhLzi6GJWRBcbw== Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 02:06:39 -0000 Maybe. The manual may indicate what they tested, which met the requirements w= hen the product was released, but not necessarily what the hardware (and BIO= S) support. I have a ThinkPad with more memory in it than the manual says is= supported. Try Google first, but it could still be worth trying.=20 Dale > On Jan 11, 2018, at 6:45 AM, Lowell Gilbert wrote: >=20 > Aryeh Friedman writes: >=20 >> My computer (HP Pavilion P7-1234, FreeBSD 11.1-RELEASE [amd64]) has 2 240= >> pin DIMM (DDR3, PC3-10600) the manual says the max memory is 8 GB but I s= ee >> some 16 GB packages (2x8GB). If I put one or two of these in will it se= e >> the extra memory? >=20 > Probably not. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.or= g" From owner-freebsd-questions@freebsd.org Sat Jan 13 02:38:47 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8F621E6A0BD for ; Sat, 13 Jan 2018 02:38:47 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EA79B6D877 for ; Sat, 13 Jan 2018 02:38:46 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.18.98]) by mrelayeu.kundenserver.de (mreue103 [212.227.15.183]) with ESMTPA (Nemesis) id 0LdL6H-1fI0hG07If-00iVmA; Sat, 13 Jan 2018 03:33:31 +0100 Date: Sat, 13 Jan 2018 03:33:30 +0100 From: Polytropon To: JD Cc: FreeBSD Users Subject: Re: The Intel Management Engine: an attack on computer users' freedom Message-Id: <20180113033330.a9b37f9c.freebsd@edvax.de> In-Reply-To: <5A5918C9.4060200@gmail.com> References: <5A5918C9.4060200@gmail.com> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:FH5bQ4xne6z/i54SC39ZX6MQBkfhCe/eIieWnlFqj1mtKEyQvA/ lufg0tixyMuVXVKElLISQTBaf/2afd/iDDVKp9mLaUfN9s3r0vcp+GbNF+geDmly6rMOTkR tG1bqbbdK65RPcobTLHOiWe9R0FqO9U+lObW+X2A4bpY2bXhME64poJPwuiJNnubZlJ5uoj S73ipY9cU2GO4CUhZAn4w== X-UI-Out-Filterresults: notjunk:1;V01:K0:vEbGvh0CgDw=:kioUu3hmvf6Tw/XPHgJP0Q vjRyZ6dSvwj/BEVQGM4O832+Y/4BkRINn9yLbg9+hexsLIOCeaJJMaXGu5v9pb9xdEl93vZs+ zc6BzShH6JW6rX/1u0fE75rFrry6AyJDaHN6wnYUE6DhxSbZZ9v6qpQlBhmZPSMs0fBfrFIN9 4/f8VW8hD7vog5KeLkPTbFw1/hOiW+7eWINXQkTsDtH83K7xgbEw+GBE1K/BpbtASzYQ1tdQY n64qhB5oDHV78tOMVi/K3cOWipT+haHUVp2wMP864OujykWachKqlU6pXAVtcICgAAMMV25uj ONf4IjXLEVhhuPgfDtt1fA2FJJ3w6q0rpQT3mdb7R4qqhnoOXeYbYjtqBtdh/q2pAuMxtumxZ gmS6x1VIY1i0rjEaqB7CdWVMNVWXVY8BcxItpqboK3gSsTEiQXXxMI5ZOgwr27qXedc+zYVSC oHKaR6r0k0jOg7NahUSflk2EDFQhnPMBZL9JwzFq7xuLDIU9v92jnaIEhfLIw01Swdp1LU596 eLuJn5BuzYCcLVMav+1qboSlAJYPtN4xsiVTPyW7JfDafFzjS2tP6ImNVL1LU1UcliKOJYMmO bzuIck0INX6FAzdKjDz/7Tjc95BQt7U0krZ2POdqa26mO+PsFwUklyHVtxAhSEVJ3mkfu0iwm QT6HqATCi8SkYtQ3ICwlQBdnpXEVFTwsS5Sfy8SXhlR6KN5k2w4+0rr1niSe8uIQYyU8UORpg zMTYxz3p77iIeXmPBz9RpNPL1tUVWNo5iCKzx0O3DU8AxIK73Yn5z39Pbow= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 02:38:47 -0000 On Fri, 12 Jan 2018 13:21:29 -0700, JD wrote: > Will *-BSD distro OS'es be able to defeat or disable this attack? Regarding the Spectre and Meltdown attacks, please refer to the discussion which already took place on this list and on others (check the archives). Also see: https://lists.freebsd.org/pipermail/freebsd-security/2018-January/009719.html https://forums.freebsd.org/threads/63985/#post-371432 https://www.freebsd.org/news/newsflash.html#event20180104:01 To see the presence of the ME as an attack is possible. But as it operates way below the OS level, there is not much the developers of the BSDs can do about that. _You_ need to take action. One option is to remove devices that have Intel ME from your installation and replace them with devices that don't. Additionally take into mind that "below OS" hardware and soft- ware / firmware is also present in smartphones, in hard disks, and in USB sticks - nearly everywhere. What can anybody do about this? Not much, sadly... This illustrates that you can hardly avoid closed-source technology that is effectively in control of your hardware without any OS interfering. Further information about Intel ME details from 2017's 34C3: Maxim Goryachy and Mark Ermolov: Inside Intel Management Engine https://media.ccc.de/v/34c3-8762-inside_intel_management_engine http://cdn.media.ccc.de/congress/2017/h264-sd/34c3-8762-eng-deu-Inside_Intel_Management_Engine_sd.mp4 Igor Skochinsky and Nicola Corna: Intel ME: Myths and reality https://media.ccc.de/v/34c3-8782-intel_me_myths_and_reality http://cdn.media.ccc.de/congress/2017/h264-sd/34c3-8782-eng-deu-fra-Intel_ME_Myths_and_reality_sd.mp4 -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Sat Jan 13 08:18:52 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 34922E7CA78 for ; Sat, 13 Jan 2018 08:18:52 +0000 (UTC) (envelope-from emilia@disroot.org) Received: from disroot.org (bs-one.disroot.org [178.21.23.139]) (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 EF07A7B093 for ; Sat, 13 Jan 2018 08:18:51 +0000 (UTC) (envelope-from emilia@disroot.org) Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id EBAB52AC90 for ; Sat, 13 Jan 2018 09:09:25 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1515830965; bh=6XFwoNQmlZBHI4rO/VzbNUfopfogwdoOJ7c+Bc4QuHw=; h=Date:From:Subject:To; b=UyYjVWk9ezYDVpbLbFcVagg4WO33OWVkRx7tzP7IYMYYFgTVCrrRFlUCBk1EMZHk1 v7yfJZpKe2f+wY3zH+usEyGeoUKkrb5swMkrDxljxTLe9E57TqAnsGMULdn/0JnCjh 0wtvMotiQsnyyI3tocJxL7rR62Ck5oPir9Ou7Dms= X-Virus-Scanned: Debian amavisd-new at disroot.org Received: from disroot.org ([127.0.0.1]) by localhost (mail01.disroot.lan [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T9CcAxmJe5Pd for ; Sat, 13 Jan 2018 09:09:09 +0100 (CET) Mime-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1515830943; bh=6XFwoNQmlZBHI4rO/VzbNUfopfogwdoOJ7c+Bc4QuHw=; h=Date:From:Subject:To; b=c3tQRGri2xRbDHFeKLb04KnFEKwt6fQwjQ9tMyAqKwZQUuxnbcZ2ex8EJRJ9wbNmx dzZAh4r1kubgGc5yIueIWiHq83w9jy2TyZGgOYpgFEB3I+FgemuBaTVw2d+0CnB3rX Ohh6rPvkH1a+CWdRB0Ubw0bvTIvD5qFxDRYhlaGo= Date: Sat, 13 Jan 2018 08:09:01 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: "emilia" Message-ID: Subject: Volume per channel (sound(4)) To: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 08:18:52 -0000 Hello, the sound(4) manpage mentions this:=0A=0A> VPC=0A> FreeBSD support= s independent and individual volume controls for each=0A> active applicat= ion, without touching the master sound volume.[...]=0A=0AI have been sear= ching on how to utilize this but did not find anything on this,=0Acould s= omeone please advise on how i would go about using this?=0A=0Aregards,=0A= emilia From owner-freebsd-questions@freebsd.org Sat Jan 13 11:59:37 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A213E5CA76 for ; Sat, 13 Jan 2018 11:59:37 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 87FE9826DD for ; Sat, 13 Jan 2018 11:59:35 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.18.98]) by mrelayeu.kundenserver.de (mreue001 [212.227.15.167]) with ESMTPA (Nemesis) id 0LvtTJ-1euhTP3uoP-017jgJ; Sat, 13 Jan 2018 12:59:19 +0100 Date: Sat, 13 Jan 2018 12:59:18 +0100 From: Polytropon To: "emilia" Cc: freebsd-questions@freebsd.org Subject: Re: Volume per channel (sound(4)) Message-Id: <20180113125918.17e51713.freebsd@edvax.de> In-Reply-To: References: Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:Jg04j+y/wOg5/Bv57eB5CIdHAjrXO0iriMjwFJH4gX8LwjkixOH x2GvT7nAuY8i2lHTDi57wY/lwQctNbYsLNRksocbkd96+nDO/B/qSA5OWQ8VA71i5aBt990 shrhOoArsNsOgCELQVTfTFL4mLYQGGubLjKbVmKD4TGBltknlD5L0EQ1xyQVgO7wot3AeY8 fF9yltK2j7IS/BDi7zRbA== X-UI-Out-Filterresults: notjunk:1;V01:K0:mUJw+Wdp4rU=:aIWvDeO+nsyf8H7YC5mxA4 UgcjAnbH7H2O/+0TWFIcZiiLD3VJSSCBYOjSuZHX97X5pyznct6Ky8DILD/pSRNkKcSADy4qF uF6CC8KgJGlYaIZpUHFkZDinJeMb+I0HMqc2J1G+uDKX12eJs3fON1Sv4Ixbhgd9lI5wmK5UK DsI2MCK4FWzAizaiHB+OZTsIms5Z0V4EqrGGnyoQeHcU/qA7XOzm6lcV0Zz0GrugQpa9t4DeZ zjgG2C9zDPy3cbNj2DuRHLGOhRB3aNUs/mJiraqbe1BEz53ri9D2vi9kgTDDuFZcITrD1KQoQ W/w1q/D9cERGouAuNGFsZBO8WJAXFfjwybPdhWERUZskM97NJvOY1nwKXZ1r1IcyjXMg6hhpA 9v4Wyq1/mbMxK0SjirOfmQ1tfin0stHGVEn54MaDt80RFYAGHJZExY4dzrEgb1w6/IFkD3v6Y 6srZ3yOxz8lpSCrf61pg2AcP8jOn0X9gEPX4gibStz1ahO5ES/gdpJyWlF6pCBfcm8Dn3Llpz +ifYsrfnOT/IlWN2ynLKjWZuuQAcBTwC1K1UWCmxp2jbSlRCEjMfURSnrPSI7Dk9pyQu649T6 1KrDpSqOPQSnaW4/KUU1Y2OWKdU2TVRsyFO80q1T5lC+whzGabypzn8Ljkla9ldPnkzhEciNj l/GpmaxgMBItd5bMsCEODVxmAaB1xXPBi1+bnBIaOh3+j0+EsVUBpA3ljYi4mWj6lrg7z1YHg +0DE7DqjrJkzn+xDD+APKfG0dv51yT+xfnp6R3FuvZkpI2uXcM7t6IbngNw= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 11:59:37 -0000 On Sat, 13 Jan 2018 08:09:01 +0000, emilia wrote: > Hello, the sound(4) manpage mentions this: > > > VPC > > FreeBSD supports independent and individual volume controls for each > > active application, without touching the master sound volume.[...] > > I have been searching on how to utilize this but did not find anything on this, > could someone please advise on how i would go about using this? If this refers to what I think it does, it is controlled by the applications themselves (e. g., have two instances of mplayer running: changing volume on one doesn't change the volume on the other; then additionally start xmms, its volume can be changed independently from the others which keep their volume). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Sat Jan 13 12:29:48 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 42529E62083 for ; Sat, 13 Jan 2018 12:29:48 +0000 (UTC) (envelope-from web@3dresearch.com) Received: from smtpd.telissant.net (smtpd.telissant.net [104.225.1.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1D2A383A25 for ; Sat, 13 Jan 2018 12:29:47 +0000 (UTC) (envelope-from web@3dresearch.com) Received: from cortina.3dresearch.com (localhost [127.0.0.1]) by smtpd.telissant.net (Postfix) with ESMTP id 9F48D81036B; Sat, 13 Jan 2018 07:11:43 -0500 (EST) X-Virus-Scanned: amavisd-new at telissant.net Received: from smtpd.telissant.net ([127.0.0.1]) by cortina.3dresearch.com (cortina.3dresearch.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2lP6KGk6XnkL; Sat, 13 Jan 2018 07:11:23 -0500 (EST) Received: from elettra.3dresearch.com (unknown [71.112.242.72]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: elettra) by smtpd.telissant.net (Postfix) with ESMTPSA id E09A4810369; Sat, 13 Jan 2018 07:11:23 -0500 (EST) Received: from elettra.3dresearch.com (localhost [127.0.0.1]) by elettra.3dresearch.com (Postfix) with SMTP id 6FB6A319D8E; Sat, 13 Jan 2018 07:11:23 -0500 (EST) Date: Sat, 13 Jan 2018 07:11:12 -0500 From: Janos Dohanics To: Marc G Fournier Cc: FreeBSD Questions Subject: Re: BSDStats: reporting bug fixed Message-Id: <20180113071112.f28592aa4838771503ea6c17@3dresearch.com> In-Reply-To: <485C63BB-690C-4FDF-B4AF-70033ACF804C@hub.org> References: <485C63BB-690C-4FDF-B4AF-70033ACF804C@hub.org> X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.31; amd64-portbld-freebsd10.4) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 12:29:48 -0000 On Thu, 4 Jan 2018 18:57:29 -0800 Marc G Fournier wrote: >=20 > [...] >=20 > To see the statistics themselves, please go to http://bsdstats.org > ? its not just FreeBSD, but all known BSDs > ( although the two biggest *are* FreeBSD and TrueOS/PCBSD ). >=20 > If anyone has any issues with bsdstats-send, or questions, please > feel free to email me directly ? The page http://bsdstats.org/bt/countries.html shows 1,375 FreeBSD installations in the US, which makes my 15 FreeBSD installations (which all do send reports) 1.09% of that total - flattering, but hard to believe. Makes me think that I'm in a small minority of FreeBSD users who also use BSDStats. --=20 Janos Dohanics From owner-freebsd-questions@freebsd.org Sat Jan 13 16:21:33 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41062E713D6; Sat, 13 Jan 2018 16:21:33 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3A8B16B9BF; Sat, 13 Jan 2018 16:21:31 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from crayon2.yoonka.com (crayon2.yoonka.com [10.70.7.20]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id w0DGLOw9003337 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sat, 13 Jan 2018 16:21:24 GMT (envelope-from list1@gjunka.com) To: freebsd-questions@freebsd.org, freebsd-drivers@freebsd.org From: Grzegorz Junka Subject: Server doesn't boot when 3 PCIe slots are populated Message-ID: Date: Sat, 13 Jan 2018 16:21:24 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 16:21:33 -0000 Hello, I am installing a FreeBSD server based on Supermicro H8SML-iF. There are three PCIe slots to which I installed 2 NVMe drives and one network card Intel I350-T4 (with 4 Ethernet slots). I am observing a strange behavior where the system doesn't boot if all three PCIe slots are populated. It shows this message: nvme0: mem 0xfd8fc000-0xfd8fffff irq 24 at device 0.0 on pci1 nvme0: controller ready did not become 1 within 30000 ms nvme0: did not complete shutdown within 5 seconds of notification The I see a kernel panic/dump and the system reboots after 15 seconds. If I remove one card, either one of the NVMe drives or the network card, the system boots fine. Also, if in BIOS I set PnP OS to YES then sometimes it boots (but not always). If I set PnP OS to NO, and all three cards are installed, the system never boots. When the system boots OK I can see that the network card is reported as 4 separate devices on one of the PCIe slots. I tried different NVMe drives as well as changing which device is installed to which slot but the result seems to be the same in any case. What may be the issue? Amount of power drawn by the hardware? Too many devices not supported by the motherboard? Too many interrupts for the FreeBSD kernel to handle? Any help would be greatly appreciated. GregJ From owner-freebsd-questions@freebsd.org Sat Jan 13 16:51:55 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C7845E7296C for ; Sat, 13 Jan 2018 16:51:55 +0000 (UTC) (envelope-from john@johnrshannon.com) Received: from maila.johnrshannon.com (maila.johnrshannon.com [173.198.166.11]) by mx1.freebsd.org (Postfix) with ESMTP id 89A196CB2C for ; Sat, 13 Jan 2018 16:51:54 +0000 (UTC) (envelope-from john@johnrshannon.com) Received: from [192.168.1.42] (michael.internal.johnrshannon.com [192.168.1.42]) by maila.johnrshannon.com (Postfix) with ESMTP id 7191C83E9 for ; Wed, 10 Jan 2018 09:02:07 -0700 (MST) To: "freebsd-questions@freebsd.org" From: "John R. Shannon" Subject: Adaptec AIC7902 SCSI Errors Message-ID: Date: Wed, 10 Jan 2018 09:02:06 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 16:51:55 -0000 Supermicro server with SCSI controller built into motherboard. Relevant ports of dmesg shows: ahd0: port 0x4400-0x44ff,0x4000-0x40ff mem 0xd2102000-0xd2103fff irq 30 at device 2.0 on pci7 ahd1: port 0x4c00-0x4cff,0x4800-0x48ff mem 0xd2104000-0xd2105fff irq 31 at device 2.1 on pci7 ahd0: Invalid Sequencer interrupt occurred. ahd0: Dumping Card State at program address 0x23c Mode 0x0 ahd0: FIFO0 Free, LONGJMP == 0x8000, SCB 0x1f4 ahd0: FIFO1 Free, LONGJMP == 0x8063, SCB 0x1f1 ahd0: LQISTATE = 0x0, LQOSTATE = 0x0, OPTIONMODE = 0x42 ahd0: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x1 ahd0: SAVED_SCSIID = 0x0 SAVED_LUN = 0x0 ahd0: REG0 == 0xbbff, SINDEX = 0x10e, DINDEX = 0x104 ahd0: SCBPTR == 0x1f4, SCB_NEXT == 0xffc0, SCB_NEXT2 == 0x1f2 (probe1:ahd0:0:1:0): inquiry data fails comparison at DV1 step (probe0:ahd0:0:0:0): inquiry data fails comparison at DV1 step (ahd0:A:1:0): refuses synchronous negotiation. Using asynchronous transfers (ahd0:A:0:0): refuses synchronous negotiation. Using asynchronous transfers ... ahd0: Invalid Sequencer interrupt occurred. >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< ahd0: Dumping Card State at program address 0x23c Mode 0x0 Card was paused INTSTAT[0x0] SELOID[0x1] SELID[0x30] HS_MAILBOX[0x0] INTCTL[0x80]:(SWTMINTMASK) SEQINTSTAT[0x0] SAVED_MODE[0x11] DFFSTAT[0x33]:(CURRFIFO_NONE|FIFO0FREE|FIFO1FREE) SCSISIGI[0x0]:(P_DATAOUT) SCSIPHASE[0x0] SCSIBUS[0x0] LASTPHASE[0x1]:(P_DATAOUT|P_BUSFREE) SCSISEQ0[0x0] SCSISEQ1[0x12]:(ENAUTOATNP|ENRSELI) SEQCTL0[0x0] SEQINTCTL[0x6]:(INTMASK1|INTMASK2) SEQ_FLAGS[0x0] SEQ_FLAGS2[0x0] QFREEZE_COUNT[0x4] KERNEL_QFREEZE_COUNT[0x4] MK_MESSAGE_SCB[0xff00] MK_MESSAGE_SCSIID[0xff] SSTAT0[0x0] SSTAT1[0x0] SSTAT2[0x0] SSTAT3[0x0] PERRDIAG[0x0] SIMODE1[0xa4]:(ENSCSIPERR|ENSCSIRST|ENSELTIMO) LQISTAT0[0x0] LQISTAT1[0x0] LQISTAT2[0x0] LQOSTAT0[0x0] LQOSTAT1[0x0] LQOSTAT2[0x0] SCB Count = 512 CMDS_PENDING = 0 LASTSCB 0xffff CURRSCB 0x1f2 NEXTSCB 0xffc0 qinstart = 51 qinfifonext = 52 QINFIFO: 0x1f1 WAITING_TID_QUEUES: Pending list: 497 FIFO_USE[0x0] SCB_CONTROL[0x58]:(STATUS_RCVD|MK_MESSAGE|DISCENB) SCB_SCSIID[0x7] Total 1 Kernel Free SCB lists: Any Device: 498 500 503 499 501 502 504 505 506 507 508 509 510 511 496 495 494 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475 474 473 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 457 456 455 454 453 452 451 450 449 448 447 446 445 444 443 442 441 440 439 438 437 436 435 434 433 432 431 430 429 428 427 426 425 424 423 422 421 420 419 418 417 416 415 414 413 412 411 410 409 408 407 406 405 404 403 402 401 400 399 398 397 396 395 394 393 392 391 390 389 388 387 386 385 384 383 382 381 380 379 378 377 376 375 374 373 372 371 370 369 368 367 366 365 364 363 362 361 360 359 358 357 356 355 354 353 352 351 350 349 348 347 346 345 344 343 342 341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 325 324 323 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 285 284 283 282 281 280 279 278 277 276 275 274 273 272 271 270 269 268 267 266 265 264 263 262 261 260 259 258 257 256 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0Sequencer Complete DMA-inprog list: Sequencer Complete list: Sequencer DMA-Up and Complete list: Sequencer On QFreeze and Complete list: ahd0: FIFO0 Free, LONGJMP == 0x8000, SCB 0x1f4 SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVEPTRS) SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) SG_CACHE_SHADOW[0x2]:(LAST_SEG) SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5]:(FIFOFREE|DLZERO) SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10]:(SG_CACHE_AVAIL) ahd0: FIFO1 Free, LONGJMP == 0x8063, SCB 0x1f1 SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVEPTRS) SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) SG_CACHE_SHADOW[0x2]:(LAST_SEG) SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5]:(FIFOFREE|DLZERO) SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10]:(SG_CACHE_AVAIL) LQIN: 0x8 0x0 0x1 0xf4 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 ahd0: LQISTATE = 0x0, LQOSTATE = 0x0, OPTIONMODE = 0x42 ahd0: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x1 ahd0: SAVED_SCSIID = 0x0 SAVED_LUN = 0x0 SIMODE0[0xc]:(ENOVERRUN|ENIOERR) CCSCBCTL[0x0] ahd0: REG0 == 0xbbff, SINDEX = 0x10e, DINDEX = 0x104 ahd0: SCBPTR == 0x1f4, SCB_NEXT == 0xffc0, SCB_NEXT2 == 0x1f2 CDB 12 0 0 80 8 9e STACK: 0x237 0x2 0x0 0x0 0x0 0x0 0x0 0x0 <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> (probe1:ahd0:0:1:0): inquiry data fails comparison at DV1 step (probe0:ahd0:0:0:0): inquiry data fails comparison at DV1 step (ahd0:A:1:0): refuses synchronous negotiation. Using asynchronous transfers (ahd0:A:0:0): refuses synchronous negotiation. Using asynchronous transfers ses0 at ahd0 bus 0 scbus0 target 6 lun 0 ses0: Fixed Processor SCSI-2 device ses0: 3.300MB/s transfers ses0: SAF-TE Compliant Device ses1 at ahd1 bus 0 scbus1 target 6 lun 0 ses1: Fixed Processor SCSI-2 device ses1: 3.300MB/s transfers da1 at ahd0 bus 0 scbus0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: Serial Number 3LQ0C90X00009727C157 da1: 6.600MB/s transfers (16bit) da1: Command Queueing enabled da1: 70007MB (143374744 512 byte sectors) da2 at ahd0 bus 0 scbus0 target 3 lun 0 da2: Fixed Direct Access SCSI-3 device da2: Serial Number 3LQ0C8Z600009727S9J7 da2: 320.000MB/s transfers (160.000MHz DT, offset 63, 16bit) da2: Command Queueing enabled da2: 70007MB (143374744 512 byte sectors) cd0 at ata0 bus 0 scbus2 target 1 lun 0 cd0: Removable CD-ROM SCSI device cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at ahd0 bus 0 scbus0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: Serial Number 3LQ0KKB500007702X77X da0: 6.600MB/s transfers (16bit) da0: Command Queueing enabled da0: 70007MB (143374744 512 byte sectors) ... and similarly with the CD drive: ugen4.2: at usbus4 umass0 on uhub0 umass0: on usbus4 umass0: 8070i (ATAPI) over Bulk-Only; quirks = 0x4000 umass0:3:0: Attached to scbus3 cd1 at umass-sim0 bus 0 scbus3 target 0 lun 0 cd1: Removable CD-ROM SCSI device cd1: 40.000MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present - tray closed cd1: quirks=0x10<10_BYTE_ONLY> (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 01 00 (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error (cd1:umass-sim0:0:0:0): SCSI status: Check Condition (cd1:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:64,0 (Illegal mode for this track) (cd1:umass-sim0:0:0:0): Error 6, Unretryable error (cd1:umass-sim0:0:0:0): cddone: got error 0x6 back (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 01 00 (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error (cd1:umass-sim0:0:0:0): SCSI status: Check Condition (cd1:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:64,0 (Illegal mode for this track) (cd1:umass-sim0:0:0:0): Error 6, Unretryable error (cd1:umass-sim0:0:0:0): cddone: got error 0x6 back (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 01 00 (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error (cd1:umass-sim0:0:0:0): SCSI status: Check Condition (cd1:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:64,0 (Illegal mode for this track) (cd1:umass-sim0:0:0:0): Error 6, Unretryable error (cd1:umass-sim0:0:0:0): cddone: got error 0x6 back (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 01 00 (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error (cd1:umass-sim0:0:0:0): SCSI status: Check Condition (cd1:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:64,0 (Illegal mode for this track) (cd1:umass-sim0:0:0:0): Error 6, Unretryable error (cd1:umass-sim0:0:0:0): cddone: got error 0x6 back (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 01 00 (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error (cd1:umass-sim0:0:0:0): SCSI status: Check Condition (cd1:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:64,0 (Illegal mode for this track) (cd1:umass-sim0:0:0:0): Error 6, Unretryable error (cd1:umass-sim0:0:0:0): cddone: got error 0x6 back (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 01 00 (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error -- (cd1:umass-sim0:0:0:0): SCSI status: Check Condition (cd1:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:64,0 (Illegal mode for this track) (cd1:umass-sim0:0:0:0): Error 6, Unretryable error (cd1:umass-sim0:0:0:0): cddone: got error 0x6 back (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 01 00 (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error (cd1:umass-sim0:0:0:0): SCSI status: Check Condition (cd1:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:64,0 (Illegal mode for this track) (cd1:umass-sim0:0:0:0): Error 6, Unretryable error (cd1:umass-sim0:0:0:0): cddone: got error 0x6 back (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 01 00 (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error (cd1:umass-sim0:0:0:0): SCSI status: Check Condition (cd1:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:64,0 (Illegal mode for this track) (cd1:umass-sim0:0:0:0): Error 6, Unretryable error (cd1:umass-sim0:0:0:0): cddone: got error 0x6 back (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 01 00 (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error (cd1:umass-sim0:0:0:0): SCSI status: Check Condition (cd1:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:64,0 (Illegal mode for this track) (cd1:umass-sim0:0:0:0): Error 6, Unretryable error (cd1:umass-sim0:0:0:0): cddone: got error 0x6 back ugen4.2: at usbus4 (disconnected) umass0: at uhub0, port 1, addr 2 (disconnected) cd1 at umass-sim0 bus 0 scbus3 target 0 lun 0 cd1: detached (cd1:umass-sim0:0:0:0): Periph destroyed umass0: detached Is the a work-around or fix? John R. Shannon john@johnrshannon.com From owner-freebsd-questions@freebsd.org Sat Jan 13 17:56:09 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 09340E762C2; Sat, 13 Jan 2018 17:56:09 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-ot0-x22c.google.com (mail-ot0-x22c.google.com [IPv6:2607:f8b0:4003:c0f::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 BE8456F814; Sat, 13 Jan 2018 17:56:08 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-ot0-x22c.google.com with SMTP id a24so7607638otd.4; Sat, 13 Jan 2018 09:56:08 -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=KujieS9t0pmshPCmRP9xZnOJBagSIWldVCM1+zesmDU=; b=rsfigNQnCQoqkCjITZ+CeeuNQy5u19g1kjRaChg8l+xMkgCVhg9tMPcXSXpOVqSt+N 7mGyRpqmh1EsenJB/5iFrxk5HAPW8T3Q2g2WkLiYd805+dZUKrntprDuV2uWZql4abUd yFWS1XnfLE9n2yfod497oZ3ScpDVz8FY7d1tnv4AMqwOtsqKps8H2pExnpya/1l3KmpU 7D65eacAXljvE1wSdtf4E4kV1OI1mszHEcT8WZsW/JXUt5YQJvqChPt5Qhp0Qta7nne8 /52anvR4tT9mOMsNaDO1H2DdqOLzPn4eO2Pu7h81YEh6bGZJP2t6ttN3l3lkW5684Mb3 FTAQ== 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=KujieS9t0pmshPCmRP9xZnOJBagSIWldVCM1+zesmDU=; b=UfZW/hUkd+qfaKiDjM8zBNm+0uVf2W4UadPd42SYLvBej1++Nm2EBskEEmyv+26dqU nuN5TAF0vUBxYHBXGClw1JmON3QjQocS64I41eCV6xCP8ylL02kZ/OX2vBWRH5fHC3JI n+YwDh1ZenEa/UboCZpkLbsVpuFij+um50mVCBZWqEeQAdK2rkpO+rClwvXZX28a4bMP adsRH8T5Hp7ihyXY+Q1jlSD11GsXmo9A23MnMSs2dylHoxyY48PKd3lUgXBL7VpwY+Zc bcx2GcKUuOgp+ljAFQBCjNMJWF/5DaTLZbWsU5XnOlaPA1O0+2xniGJVG0w83zkR4CAs t8CA== X-Gm-Message-State: AKwxytexeSBM/gIebGCjG0fB4L5PuNaw5T/xvoEE33azISwABNaSR2RF /BZZHii1wgPDKN9dIkQ8Lm8BbiZ4cdOwLAMHUAw= X-Google-Smtp-Source: ACJfBoue3RcqP8BGWIQRIyPBVyHBd8lhJHC97rE7YYJR3KQOddZNyX6uAyaMNImdE/ODgdqw+55wApQk88k+M4EVh+A= X-Received: by 10.157.55.246 with SMTP id x109mr3424593otb.266.1515866168011; Sat, 13 Jan 2018 09:56:08 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.0.2 with HTTP; Sat, 13 Jan 2018 09:56:07 -0800 (PST) In-Reply-To: References: From: Mehmet Erol Sanliturk Date: Sat, 13 Jan 2018 20:56:07 +0300 Message-ID: Subject: Re: Server doesn't boot when 3 PCIe slots are populated To: Grzegorz Junka Cc: FreeBSD Questions Mailing List , freebsd-drivers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 17:56:09 -0000 On Sat, Jan 13, 2018 at 7:21 PM, Grzegorz Junka wrote: > Hello, > > I am installing a FreeBSD server based on Supermicro H8SML-iF. There are > three PCIe slots to which I installed 2 NVMe drives and one network card > Intel I350-T4 (with 4 Ethernet slots). > > I am observing a strange behavior where the system doesn't boot if all > three PCIe slots are populated. It shows this message: > > nvme0: mem 0xfd8fc000-0xfd8fffff irq 24 at device > 0.0 on pci1 > nvme0: controller ready did not become 1 within 30000 ms > nvme0: did not complete shutdown within 5 seconds of notification > > The I see a kernel panic/dump and the system reboots after 15 seconds. > > If I remove one card, either one of the NVMe drives or the network card, > the system boots fine. Also, if in BIOS I set PnP OS to YES then sometimes > it boots (but not always). If I set PnP OS to NO, and all three cards are > installed, the system never boots. > > When the system boots OK I can see that the network card is reported as 4 > separate devices on one of the PCIe slots. I tried different NVMe drives as > well as changing which device is installed to which slot but the result > seems to be the same in any case. > > What may be the issue? Amount of power drawn by the hardware? Too many > devices not supported by the motherboard? Too many interrupts for the > FreeBSD kernel to handle? > > Any help would be greatly appreciated. > > GregJ > > _______________________________________________ > > >From my experience from other trade marked main boards , an action may be to check manual of your server board to see whether there are rules about use of these slots : Sometimes differently shaped slots are supplied with same ports : If one slot is occupied , the other slot should be left open , or rules about not to insert such a kind of device into a slot , for example , graphic cards . Mehmet Erol Sanliturk From owner-freebsd-questions@freebsd.org Sat Jan 13 18:31:46 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C95AAE7833F; Sat, 13 Jan 2018 18:31:46 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from kicp.uchicago.edu (kicp.uchicago.edu [128.135.20.70]) by mx1.freebsd.org (Postfix) with ESMTP id AE1F271298; Sat, 13 Jan 2018 18:31:46 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from point.uchicago.edu (point.uchicago.edu [128.135.52.6]) by kicp.uchicago.edu (Postfix) with ESMTP id 50C7771803D; Sat, 13 Jan 2018 12:31:40 -0600 (CST) Subject: Re: Server doesn't boot when 3 PCIe slots are populated To: Grzegorz Junka , freebsd-questions@freebsd.org, freebsd-drivers@freebsd.org References: From: Valeri Galtsev Message-ID: <061ccfb3-ee6a-71a7-3926-372bb17b3171@kicp.uchicago.edu> Date: Sat, 13 Jan 2018 12:31:37 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 18:31:46 -0000 On 01/13/18 10:21, Grzegorz Junka wrote: > Hello, > > I am installing a FreeBSD server based on Supermicro H8SML-iF. There are > three PCIe slots to which I installed 2 NVMe drives and one network card > Intel I350-T4 (with 4 Ethernet slots). > > I am observing a strange behavior where the system doesn't boot if all > three PCIe slots are populated. It shows this message: > > nvme0: mem 0xfd8fc000-0xfd8fffff irq 24 at device > 0.0 on pci1 > nvme0: controller ready did not become 1 within 30000 ms > nvme0: did not complete shutdown within 5 seconds of notification > > The I see a kernel panic/dump and the system reboots after 15 seconds. > > If I remove one card, either one of the NVMe drives or the network card, > the system boots fine. Also, if in BIOS I set PnP OS to YES then > sometimes it boots (but not always). If I set PnP OS to NO, and all > three cards are installed, the system never boots. > > When the system boots OK I can see that the network card is reported as > 4 separate devices on one of the PCIe slots. I tried different NVMe > drives as well as changing which device is installed to which slot but > the result seems to be the same in any case. > > What may be the issue? Amount of power drawn by the hardware? Too many > devices not supported by the motherboard? Too many interrupts for the > FreeBSD kernel to handle? That would be my first suspicion. Either total power drawn off the power supply. Or total power drawn off the PCI[whichever it is] bus power leads. Check if any of the add-on cards have extra power port (many video cards do). Card likely will work without extra power connected to it, but connecting extra power on the card may solve your problem. Next: borrow more powerful power supply and see if that resolves the issue. Or temporarily disconnect everything else (like all hard drives), and boot with all three cards off live CD, and see if that doesn't crash, then it is marginally insufficient power supply. I hope this helps. Valeri > > Any help would be greatly appreciated. > > GregJ > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" -- ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++ From owner-freebsd-questions@freebsd.org Sat Jan 13 18:50:20 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 426BEE7922D for ; Sat, 13 Jan 2018 18:50:20 +0000 (UTC) (envelope-from emilia@disroot.org) Received: from disroot.org (bs-one.disroot.org [178.21.23.139]) (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 0658071FC5 for ; Sat, 13 Jan 2018 18:50:19 +0000 (UTC) (envelope-from emilia@disroot.org) Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id 2A6162ACBA for ; Sat, 13 Jan 2018 19:50:16 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1515869416; bh=G91SNsbHHDUQMdxv63M+Gpe5nPtleu/Bpk+A1CHWglw=; h=Date:In-Reply-To:References:Subject:To:From; b=QT1x9szAeLNCKJUfWmoxKn/XNUwC6th3kKatCXQ5/XW2qk3othi+qCdEhl7ZgBzGz SAzB93LpD2fNtNgH4U7Uo4w5jEpV/U8l48lmmx2uJSk5M20zw+BclYhtJGdgm7x9rp BYH23GJDpIaefMB7NTsRHaNp84EzY51zsSlN5E6E= X-Virus-Scanned: Debian amavisd-new at disroot.org Received: from disroot.org ([127.0.0.1]) by localhost (mail01.disroot.lan [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yeqU2jWFwpeT for ; Sat, 13 Jan 2018 19:50:06 +0100 (CET) Date: Sat, 13 Jan 2018 18:49:40 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1515869406; bh=G91SNsbHHDUQMdxv63M+Gpe5nPtleu/Bpk+A1CHWglw=; h=Date:In-Reply-To:References:Subject:To:From; b=HjAHmPI8alaC7o5vqQ5MepI5tL0y2Z/9lsmPvUl8zKfhye6axpm+F+3iB5PqcB5Fy KH21nqyMupLG8FccEkrp37j0sdT7yUSia8/0FJXMNSS9jsHdA9bmrdfv+BwgynTwpb Mr06h434Y8hflgH30yS2LVH+ejtTQWhOGZRC7Kf4= In-Reply-To: <20180108091328.GA3075@venera> References: <20180104055057.GA2656@c720-r314251> <20180108091328.GA3075@venera> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: client for matrix.org To: freebsd-questions@freebsd.org From: emilia Message-ID: X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 18:50:20 -0000 >> Anybody knows some client for matrix=2Eorg which could run on FreeBSD? I am using the quaternion[1] client on a daily basis on freebsd, havent be= en able to make a port yet but it compiles without modifications on 11=2E1 = (requires clang 5 though) [1] https://github=2Ecom/QMatrixClient/Quaternion regards, emilia From owner-freebsd-questions@freebsd.org Sat Jan 13 20:01:41 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2AB26E7CE04 for ; Sat, 13 Jan 2018 20:01:41 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (mail.dpedia.de [178.254.4.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DD997752AD for ; Sat, 13 Jan 2018 20:01:39 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [87.152.190.69] (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 1eaRze-0006mM-51 for freebsd-questions@freebsd.org; Sat, 13 Jan 2018 21:01:30 +0100 Received: from localhost.my.domain (localhost [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id w0DK1TqM009347 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 13 Jan 2018 21:01:29 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id w0DK1TWW009346 for freebsd-questions@freebsd.org; Sat, 13 Jan 2018 21:01:29 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Sat, 13 Jan 2018 21:01:29 +0100 From: Matthias Apitz To: freebsd-questions@freebsd.org Subject: Re: client for matrix.org Message-ID: <20180113200129.GA6848@c720-r314251> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , freebsd-questions@freebsd.org References: <20180104055057.GA2656@c720-r314251> <20180108091328.GA3075@venera> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="lrZ03NoBR/3+SXJZ" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 12.0-CURRENT r314251 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. User-Agent: Mutt/1.8.0 (2017-02-23) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 87.152.190.69 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 20:01:41 -0000 --lrZ03NoBR/3+SXJZ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable El d=C3=ADa s=C3=A1bado, enero 13, 2018 a las 06:49:40p. m. +0000, emilia e= scribi=C3=B3: >=20 >=20 > >> Anybody knows some client for matrix.org which could run on FreeBSD? >=20 > I am using the quaternion[1] client on a daily basis on freebsd, havent b= een able to make a port yet but it compiles without modifications on 11.1 (= requires clang 5 though) >=20 > [1] https://github.com/QMatrixClient/Quaternion Thanks. I followed the instructions in BUILDING.md and it failes on my CURRENT with: [guru@c720-r314251 ~/Quaternion/build_dir]$ cmake --build . --target all ^C ... Generating moc compilation qmatrixclient_automoc.cpp [ 2%] Built target qmatrixclient_automoc Scanning dependencies of target qmatrixclient [ 4%] Building CXX object lib/CMakeFiles/qmatrixclient.dir/networkaccessma= nager.cpp.o [ 5%] Building CXX object lib/CMakeFiles/qmatrixclient.dir/connectiondata.= cpp.o [ 7%] Building CXX object lib/CMakeFiles/qmatrixclient.dir/connection.cpp.o [ 8%] Building CXX object lib/CMakeFiles/qmatrixclient.dir/logging.cpp.o [ 10%] Building CXX object lib/CMakeFiles/qmatrixclient.dir/room.cpp.o /home/guru/Quaternion/lib/room.cpp:513:17: error: use of undeclared identif= ier 'bind' bind(&Private::renameMember, this, _1, _2)); ^ 1 error generated. gmake[2]: *** [lib/CMakeFiles/qmatrixclient.dir/build.make:159: lib/CMakeFi= les/qmatrixclient.dir/room.cpp.o] Error 1 gmake[1]: *** [CMakeFiles/Makefile2:198: lib/CMakeFiles/qmatrixclient.dir/a= ll] Error 2 gmake: *** [Makefile:128: all] Error 2 I modified the call of 'bind(....)' to: std::bind(&Private::renameMember, this, _1, _2)); and it compiled; it starts fine, let me login and shows my rooms. But does not show any text of the messages, only the nickname and the time, but not the text. Any idea? 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 --lrZ03NoBR/3+SXJZ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEXmn7rBYYViyzy/vBR8z35Hb+nREFAlpaZZYACgkQR8z35Hb+ nRFzdQ/+OQ7uvxQBZZhcSUi/9B7DuuOlrx45Plgwh0JCpiaHPvvsARTZdNyJ4HAq IvV4xW+Ux0fbo271DAvJRXBQ+f6SEiFvt54znkOWQJvokvE3+XTZEr4UiSRmZbZt cyOumjVj0PIj2o1HJZnEwprhUDqiokIYqBlmxN5qqdmPp2tvOVv8huCpCApixKlX wG1EII4BeLcBf/TE6QmopqjS5Nsfp5S3V8RZjN29soBqv9J7/mZdLoZF1m/hzCyT ly6VlCRRZhOhm9Kk8ox5lxMjZws/a3NdRq6jxt5pZ3TfnAsP6dlEn6npV01PD6HR QM8Wuyk2Q5RKSVAQZ0bKnaksPNF8z+XXVxpt361YmSdu7g36FuCzKT0vyq9OUIW3 +gmekeJU6v2ABUMpX/qxLeLtoyhLvMXhtd3dSfyWBwxDE5KTxSpTxnLV7mpvByB4 +oOEo5B71j0WEMdBJUl5UocIbOfLMxQ1TXyXjB5IrgqediuqdXrC6Roia//DhjaD zerhicgaLIfufyzumr8tn8dP4Jm3p5RHYXBPRJJfhSW4M/pCq2VCvAyuEp7iaAbt YjCzc/ls12Pz6pGi7mqVFm9LB+BR+/EQD07lEeqO+wCYxMTlQ7sZX+c8VjHziXI/ V/H2uE9l01+/5MRzb/Kv5NVTcXFMB3Ux5Txt3gMxwmS3kb94OaM= =sCXD -----END PGP SIGNATURE----- --lrZ03NoBR/3+SXJZ-- From owner-freebsd-questions@freebsd.org Sat Jan 13 20:40:07 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9B3A2E7EDF6 for ; Sat, 13 Jan 2018 20:40:07 +0000 (UTC) (envelope-from ralf.mardorf@alice-dsl.net) Received: from mail37c50.megamailservers.eu (mail232c50.megamailservers.eu [91.136.10.242]) (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 07C8D76A30 for ; Sat, 13 Jan 2018 20:40:05 +0000 (UTC) (envelope-from ralf.mardorf@alice-dsl.net) X-Authenticated-User: ralf.mardorf.alice-dsl.net Received: from archlinux.localdomain (x4e3215f8.dyn.telefonica.de [78.50.21.248]) (authenticated bits=0) by mail37c50.megamailservers.eu (8.14.9/8.13.1) with ESMTP id w0DJNtBt008148 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Sat, 13 Jan 2018 19:23:57 +0000 Date: Sat, 13 Jan 2018 20:24:01 +0100 From: Ralf Mardorf To: ubuntu-studio-users@lists.ubuntu.com Cc: LAU , FreeBSD questions Subject: Re: Meltdown =?UTF-8?B?4oCT?= Spectre Message-ID: <20180113202401.0b4f90c0@archlinux.localdomain> In-Reply-To: References: <20180113125406.285bf5cb@archlinux.localdomain> X-Mailer: Claws Mail 3.16.0git3 (GTK+ 2.24.32; x86_64-arch-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-CTCH-RefID: str=0001.0A0B0206.5A5A5CCE.002D, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-CTCH-Score: 0.000 X-CTCH-Rules: X-CTCH-Flags: 0 X-CTCH-ScoreCust: 0.000 X-CSC: 0 X-CHA: v=2.2 cv=esev9shX c=1 sm=1 tr=0 a=+/38W5vFYDGaUbky4/S7Pg==:117 a=+/38W5vFYDGaUbky4/S7Pg==:17 a=IkcTkHD0fZMA:10 a=QyXUC8HyAAAA:8 a=JMmPWnB6zA7-vqktouwA:9 a=QEXdDO2ut3YA:10 a=YhjuxmyD_ykA:10 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 20:40:07 -0000 On Sat, 13 Jan 2018 15:29:27 +0000, Pablo Fernandez wrote: >El s=C3=A1b., 13 ene. 2018 13:58, Thomas Pfundt escribi=C3=B3: >> However, this site doesn't list your Celeron G as vulnerable: >> https://security-center.intel.com/advisory.aspx?intelid=3DINTEL-SA-00088= &languageid=3Den-fr >> Do you even need to concern with the patch and performance at this >> point? That is interesting news. I'll forward this, since actually it's claimed that all x86 CPUs since the Pentium Pro from 1995 suffer from this issue. Does anybody know how to value this information from Intel? From owner-freebsd-questions@freebsd.org Sat Jan 13 20:41:16 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BC397E7EF95 for ; Sat, 13 Jan 2018 20:41:16 +0000 (UTC) (envelope-from emilia@disroot.org) Received: from disroot.org (bs-one.disroot.org [178.21.23.139]) (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 8199F76BBB for ; Sat, 13 Jan 2018 20:41:16 +0000 (UTC) (envelope-from emilia@disroot.org) Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id BD8042AC50 for ; Sat, 13 Jan 2018 21:41:13 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1515876073; bh=YLqJrv+wvF2lfO8cEptvEnRY5xWU8K46aTpVdDM0nNs=; h=Date:From:Subject:To:In-Reply-To:References; b=ZnfnTB9lw4ONP9Ofjs3vlsa7DIwBHWJBjKa7zZEoRpJ8YyCrgjd8itSp43QGUMPw+ jh46d+SHJTcxsEu9mhggUq8ilvngbQek9bHCd+x0SasasNtxxq81xTg98p9CDuH3XR PfXubPt0Quj1VxEs0Xq7KzLfqS6ncycI1GgEHCN8= X-Virus-Scanned: Debian amavisd-new at disroot.org Received: from disroot.org ([127.0.0.1]) by localhost (mail01.disroot.lan [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aRrO_Q4ycouO for ; Sat, 13 Jan 2018 21:41:04 +0100 (CET) Mime-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1515876064; bh=YLqJrv+wvF2lfO8cEptvEnRY5xWU8K46aTpVdDM0nNs=; h=Date:From:Subject:To:In-Reply-To:References; b=ZSEHxM9x4hQm86r7UeDZYKWmLFL1NNMZAB/RE2cvjsGGehTrS8szo257S8j5I8YV2 sJfgVIafjRwVYyzM8BxTbMPK86V45fvcVZVDS/vIWWJ1H0TY0AMrkJsiKIxR7SMAcB vHfTdl4v/nnOyuaJCOzKsNtWirQd9hzib0hAgLNU= Date: Sat, 13 Jan 2018 20:41:04 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: "emilia" Message-ID: Subject: Re: Volume per channel (sound(4)) To: freebsd-questions@freebsd.org In-Reply-To: References: <20180113125918.17e51713.freebsd@edvax.de> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 20:41:16 -0000 > If this refers to what I think it does, it is controlled=0A> by the app= lications themselves (e. g., have two instances=0A> of mplayer running: c= hanging volume on one doesn't change=0A> the volume on the other; then ad= ditionally start xmms, its=0A> volume can be changed independently from t= he others which=0A> keep their volume).=0A=0AThat just means that applica= tions can do volume control on their own, there really isn't that much=0A= you could do to prevent this in an OS, it would be fairly wierd to then a= dvertise it as a feature.=0AI understand it as I have controls for the st= reams somewhere where i can change their volume them=0Awithout the applic= ations cooperation, which for me is important since the application i hav= e been=0Atrying to mute did not have a mute button :)=0A=0Aregards,=0Aemi= lia From owner-freebsd-questions@freebsd.org Sat Jan 13 21:08:39 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 250A1EA430A for ; Sat, 13 Jan 2018 21:08:39 +0000 (UTC) (envelope-from emilia@disroot.org) Received: from disroot.org (bs-one.disroot.org [178.21.23.139]) (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 DAB0977925 for ; Sat, 13 Jan 2018 21:08:38 +0000 (UTC) (envelope-from emilia@disroot.org) Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id 435922AC50 for ; Sat, 13 Jan 2018 22:08:35 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1515877715; bh=gbtDQlBbq0ElbbBaanxNsUeGNhhOClmh2PWf4aoMI60=; h=Date:From:Subject:To:In-Reply-To:References; b=ITGbo3yvPl/i0GdBuNhYceVVcVytdTr9PaemgZauCCCh6Z3qh7tyuZTEzZUba5X9Y OgLrj+QuTWTdTn2JI/YaIJs8eILz/V0ZbJOhv85W1rsbEyrIOdg98QXlVv/X+OHMji +bHFeh+5GF/d3A6sOEO5+ZZdMEHLbee+f7kLPvVY= X-Virus-Scanned: Debian amavisd-new at disroot.org Received: from disroot.org ([127.0.0.1]) by localhost (mail01.disroot.lan [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m66hfglKH-FJ for ; Sat, 13 Jan 2018 22:08:28 +0100 (CET) Mime-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1515877708; bh=gbtDQlBbq0ElbbBaanxNsUeGNhhOClmh2PWf4aoMI60=; h=Date:From:Subject:To:In-Reply-To:References; b=hlbdqmq7TTjYwaDAZHHO/rlyVf05s/2N+L42MYk/4lSxXgdMN+inVm6phdMF4CCLY U1VlmjxIPxYzjXXw9kTx3xBTUmxnwFwrq+L4osJXeJZVqy8uiKwPIA1XX3D+SMWXQM ellhw60zJDSlY48On9iOxnCaUUgxqLBsxmCG1UhA= Date: Sat, 13 Jan 2018 21:08:28 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: "emilia" Message-ID: <4cbd23173cc4e76c44cc2e9ded2d16ff@disroot.org> Subject: Re: client for matrix.org To: freebsd-questions@freebsd.org In-Reply-To: <7858505A-0CE2-4347-964A-865CDE124079@disroot.org> References: <7858505A-0CE2-4347-964A-865CDE124079@disroot.org> <20180104055057.GA2656@c720-r314251> <20180108091328.GA3075@venera> <20180113200129.GA6848@c720-r314251> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 21:08:39 -0000 > it starts fine, let me login and shows my rooms. But does not show any= =0A> text of the messages, only the nickname and the time, but not the te= xt.=0A> =0A> Any idea?=0A> =0A> matthias=0A=0Athat build failure should b= e fixed with the latest lib, try to checkout the master branch of the=0Al= ib sudmodule,=0Aif it doesnt work maybe ask kitsune in the #qmatrixclient= :matrix.org channel=0A=0Apersonally i have had some issues trying to comi= le it against qt 5.9 (e.g text area not rendering=0Aat all) i fixed this = by compiling against 5.7 from quarterly ports tree=0A(the textarea is wri= tten with qml)=0A=0A(sorry about sending the email to matthias only befor= e, need to reconfigure my email client)=0Aregards,=0Aemilia From owner-freebsd-questions@freebsd.org Sat Jan 13 21:50:10 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CC5E0EA6D07 for ; Sat, 13 Jan 2018 21:50:10 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-cmomta03.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 98B2079877 for ; Sat, 13 Jan 2018 21:50:10 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from raspberrypi.bildanet.com ([65.186.67.174]) by cmsmtp with ESMTP id aTiSeluvbJDNIaTiVe6oso; Sat, 13 Jan 2018 21:51:55 +0000 Received: from [192.168.1.143] by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1eaTge-0002qE-2Q for freebsd-questions@freebsd.org; Sat, 13 Jan 2018 21:50:00 +0000 Subject: =?UTF-8?Q?Re:_Meltdown_=e2=80=93_Spectre?= To: freebsd-questions@freebsd.org References: <20180113125406.285bf5cb@archlinux.localdomain> <20180113202401.0b4f90c0@archlinux.localdomain> From: Baho Utot Message-ID: <830b54da-cf10-b58a-f882-e0532d5db4ed@columbus.rr.com> Date: Sat, 13 Jan 2018 16:50:01 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <20180113202401.0b4f90c0@archlinux.localdomain> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfFHaYhDXom1K2/ZYQF9KL7RVFAHVv1gbqDh14to4HVbEYiWxe6bRZUGLGYN8/DVxLozH6B3E8jgkIvCflFJOJIeSiQZmAd3T4Fpl0wPmwbODRcLFdnkM NsqHgicJi1/J1R5nilRz0pLiy1anq9RJslNz/lB5JgfoEa30eMxCLkyI/Hp6LHMj7tS50J/mgaCh28j/koNlx2fydrivzDBmB9Q= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 21:50:10 -0000 On 1/13/2018 2:24 PM, Ralf Mardorf wrote: > On Sat, 13 Jan 2018 15:29:27 +0000, Pablo Fernandez wrote: >> El sáb., 13 ene. 2018 13:58, Thomas Pfundt escribió: >>> However, this site doesn't list your Celeron G as vulnerable: >>> https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00088&languageid=en-fr >>> Do you even need to concern with the patch and performance at this >>> point? > > That is interesting news. I'll forward this, since actually it's > claimed that all x86 CPUs since the Pentium Pro from 1995 suffer from > this issue. > > Does anybody know how to value this information from Intel? It not worth much on the open market since it is readily available from the intels site. ou will not get rich from selling this information