From owner-freebsd-questions@freebsd.org Sun Apr 17 00:05:33 2016 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 27143B0A0BE for ; Sun, 17 Apr 2016 00:05:33 +0000 (UTC) (envelope-from vsasjason@gmail.com) Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AB15C104D for ; Sun, 17 Apr 2016 00:05:32 +0000 (UTC) (envelope-from vsasjason@gmail.com) Received: by mail-wm0-x22e.google.com with SMTP id a140so74989288wma.0 for ; Sat, 16 Apr 2016 17:05:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=yMdHnATzSNPWBwsPzzMfZSB4K14nkQMI9l2bbTXFZMY=; b=o3yxv6B+tA6/U0rfaK0WiST/JV3OJCoOWUQj9NSbG6/PdlZKj5cqrB9VwTJKAo/T9q o27cs7AiYcMJD6EyzUToRzWsc7E1VOd96THdAZZmOoA6UGrdH6lv/Kyoz6/AONMPiA4N ZxrFFMXdi0z+yVUiZMzRoKlx6jqDVIABGHMBqaKrPugcfO8JGxqhTjAuZKxz1zJx1tCf cY5+Xz4AheqnOqiPETepiQFHEMk73HgttJFWMkqOXfYSUbHpP7bhWuKZDtWtoXK+LzNF ZBQ9VgPuBTf+z74a4TAZTlJNLnl3iR26IJXBdGjBEPE7kTbPI55Pn5LwS5t3xKIrdKGJ FwYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=yMdHnATzSNPWBwsPzzMfZSB4K14nkQMI9l2bbTXFZMY=; b=Sp2jENVEi+L7d8+RmjjN+BpRX5wNxS8DaHOIidfDe5MIxAqoMgzCoNaEkWHIXXElnF iGnlT1uL6kv9ozL5NGk7pWCjkIRS++1ABJ5abFruFWWPAPBe5G6FDbq8JH15zTU/6yGT h9EHzF/XCZoBzrLEwlpX16PSqnaE/fsx2ZPA1cuCQU8kJN3ouOpiAb0Q6h5dFvzQggeM mILM1/7MyZIsxOGuDIgxzfFp6r+iV+iPE2s9qiUdvDZpXJWd8KtKkt2wnmnMbBW4MejF s8wtE70IdrIDG1FKEvmyz/AbRgsU0H2ZuZxWdi5vGt6oKy7LALFt+qySLgkgAF7WAxUR F65g== X-Gm-Message-State: AOPr4FVg2E8Vsoo0aceBHBINPrwG0EA1G6oUp7smenL7BtQCCejGG+Z0Z+H0eRuBy5ZMl7lhyU6BbPP5jwrqOw== MIME-Version: 1.0 X-Received: by 10.194.175.168 with SMTP id cb8mr28725132wjc.56.1460851530336; Sat, 16 Apr 2016 17:05:30 -0700 (PDT) Received: by 10.194.33.164 with HTTP; Sat, 16 Apr 2016 17:05:30 -0700 (PDT) Received: by 10.194.33.164 with HTTP; Sat, 16 Apr 2016 17:05:30 -0700 (PDT) In-Reply-To: References: <57125647.9050805@bananmonarki.se> <57126AFB.9060303@bananmonarki.se> Date: Sun, 17 Apr 2016 03:05:30 +0300 Message-ID: Subject: Re: Geli and glabel ? From: Anton Sayetsky To: Warren Block Cc: FreeBSD Questions , Bernt Hansson Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 00:05:33 -0000 17 =D0=B0=D0=BF=D1=80. 2016 =D0=B3. 1:58 =D0=BF=D0=BE=D0=BB=D1=8C=D0=B7=D0= =BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C "Warren Block" =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB: > > On Sat, 16 Apr 2016, Bernt Hansson wrote: > >> >> >> On 2016-04-16 18:08, Warren Block wrote: >>> >>> On Sat, 16 Apr 2016, Bernt Hansson wrote: >>> >>>> Hello list. >>>> >>>> I'm wondering about glabel and geli. It seems that one can not have them on the same disc. >>>> >>>> On swap it works nice but not on my home directory. Glabel overwrites the meta data from geli >>>> so the disc can not be mounted. >>>> >>>> Can this scenario work? How? >>> >>> >>> One must be inside the other. Create a glabel device in the GELI one, then refer to the glabel device with /dev/label/xyz. >> >> >> Along this line? >> >> geli attach disc >> password: >> >> glabel label 1213 /dev/disc >> >> Is that correct? > > > No, the /dev/disc device is being used both times. > > geli attach disc > > creates a disc.eli device. Now create the label on *that*: > > glabel label 1213 /dev/disc.eli This just doesn't make any sense bc if device name will change - geli name will change too. So it's really necessary to build reverse - geli on top of glabel. > > Maybe some ASCII art will help: > > ,-disc--------------. > | | > | ,-disc.eli----. | > | | | | > | | ,-1213--. | | > | | | | | | > | | | | | | > | | `-------' | | > | | | | > | `-------------' | > | | > `-------------------' > > ...well, maybe not. From owner-freebsd-questions@freebsd.org Sun Apr 17 00:15:29 2016 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 D2475B0A469 for ; Sun, 17 Apr 2016 00:15:29 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B15213CD for ; Sun, 17 Apr 2016 00:15:29 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id u3H0DCFl092989 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 16 Apr 2016 18:13:12 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id u3H0DCww092986; Sat, 16 Apr 2016 18:13:12 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sat, 16 Apr 2016 18:13:12 -0600 (MDT) From: Warren Block To: Anton Sayetsky cc: FreeBSD Questions , Bernt Hansson Subject: Re: Geli and glabel ? In-Reply-To: Message-ID: References: <57125647.9050805@bananmonarki.se> <57126AFB.9060303@bananmonarki.se> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sat, 16 Apr 2016 18:13:12 -0600 (MDT) Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 00:15:29 -0000 On Sun, 17 Apr 2016, Anton Sayetsky wrote: > > No, the /dev/disc device is being used both times. > > > >   geli attach disc > > > > creates a disc.eli device.  Now create the label on *that*: > > > >   glabel label 1213 /dev/disc.eli > This just doesn't make any sense bc if device name will change - geli name will change too. So it's really necessary to build reverse - geli on top of glabel. The label is only created once. After that, it will be present when the .eli device is created. It's possible there is a misunderstanding about what exactly is going on here, and a concrete example would help. From owner-freebsd-questions@freebsd.org Sun Apr 17 00:21:20 2016 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 6905FB0A7A5 for ; Sun, 17 Apr 2016 00:21:20 +0000 (UTC) (envelope-from vsasjason@gmail.com) Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::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 F028816DA for ; Sun, 17 Apr 2016 00:21:19 +0000 (UTC) (envelope-from vsasjason@gmail.com) Received: by mail-wm0-x22a.google.com with SMTP id n3so78045125wmn.0 for ; Sat, 16 Apr 2016 17:21:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=TNl/oC8jG3NT3vJra68UJRnrjlVYFX+KKmVTPDUugZg=; b=Zt6qwUQqanJPYFqBReoGp6HNrzUgkoLf5g/fp7J3w13SYT+CsKYglNEdCqVNNWLB69 ljLr+zWbTCoGGlB5743UEH+wstZd6iTAyIOYOmXccLYNjBG2gY2+TX8QEukgoZ7Tjf6U 4kL5P2rzelOotPdk4Jh1a+Suls9gAatVkv/bGFtnwymaYm6z6c3KRG/0YLA5JNbfh5MW 0w8UnNS9AUAUjNdgJb5Xp2oPzc4voD+b4B7qjRr1iH8ZjAKmVq55QdAlaRwZvGHbtviO +dzB9gpxwXroFa7hzSJsunnA/dm5JlVOs/FW1avmz6n2hP6D5OSmPARB665UL4Aa43Ov DlpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=TNl/oC8jG3NT3vJra68UJRnrjlVYFX+KKmVTPDUugZg=; b=JRnI5w8ahhnn8k3zhQdZwYr0nmU7sjM423IcVjeGL2TGhlgLdlwNV02v+jTGWPR4h1 4V1PUba7zgz6LutOGsaDfjN7YfsoscRaxkGo99/j6NaWcdsKylHOqyjYJJeQl2vbPcac qdDBp4Z6xqjH2BDJQZoHrlU96fNT4WKqypjj9Q9qxdRy36eQCzy1KoDlXD2MIej6gpmI 1QRYA7nnYzLto/G4j43WtdUcIDO5LZfI9XbYyEkgozpIl0+squu3zgfpyYqSh4Jv1hrV riqbPZym2UR4gout0QcZmIM46BHeuhyjEmaX4wRR1hQT2m/sVTIntGJ7PzHYWjQevkJM YYYQ== X-Gm-Message-State: AOPr4FWiZ8xLbf+BpLH22CFe6R4eyXT2GNfMWbHUKdmCrw3WxP1uKzeLImpsVIbt0Mvhe4U2XaW/bTObGd+fcQ== MIME-Version: 1.0 X-Received: by 10.28.232.140 with SMTP id f12mr11343775wmi.6.1460852478587; Sat, 16 Apr 2016 17:21:18 -0700 (PDT) Received: by 10.194.33.164 with HTTP; Sat, 16 Apr 2016 17:21:18 -0700 (PDT) Received: by 10.194.33.164 with HTTP; Sat, 16 Apr 2016 17:21:18 -0700 (PDT) In-Reply-To: References: <57125647.9050805@bananmonarki.se> <57126AFB.9060303@bananmonarki.se> Date: Sun, 17 Apr 2016 03:21:18 +0300 Message-ID: Subject: Re: Geli and glabel ? From: Anton Sayetsky To: Warren Block Cc: Bernt Hansson , FreeBSD Questions Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 00:21:20 -0000 17 =D0=B0=D0=BF=D1=80. 2016 =D0=B3. 3:15 =D0=BF=D0=BE=D0=BB=D1=8C=D0=B7=D0= =BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C "Warren Block" =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB: > > On Sun, 17 Apr 2016, Anton Sayetsky wrote: > >> > No, the /dev/disc device is being used both times. >> > >> > geli attach disc >> > >> > creates a disc.eli device. Now create the label on *that*: >> > >> > glabel label 1213 /dev/disc.eli >> This just doesn't make any sense bc if device name will change - geli name will change too. So it's really necessary to build reverse - geli on top of glabel. > > > The label is only created once. After that, it will be present when the .eli device is created. I know. But here an example: 1. Insert one disk 2. Create geli and glabel there 3. Pull out that disk and insert it again in random order with hundred of other disks 4. Try to find where geli is located So I can say again - glabel inside geli doesn't make any sense in any situation. But geli inside glabel makes sense almost always. > > It's possible there is a misunderstanding about what exactly is going on here, and a concrete example would help. From owner-freebsd-questions@freebsd.org Sun Apr 17 00:35:10 2016 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 31D2BB0AC46 for ; Sun, 17 Apr 2016 00:35:10 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) Received: from alogt.com (alogt.com [69.36.191.58]) (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 153B11CAE for ; Sun, 17 Apr 2016 00:35:09 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References: In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=ySpm5Dy6rvPNg9l9ZwtFxUcQ0CHlPL7LxmD44a4yMsg=; b=G0jy6mSAI1JI5r8NVu5DUY2QDC rQVyeYgiQkoIo9sGNHHwL63IKFn7XtTuoQT0500E9Zky9U5DyXiR3GyzvPYSellEYRBDvxdeXLoVQ gIblll2Xa29vj1eui5udvSsvvzHxiqFUfFADmgwCYTocEFPhPBe2XjJ8HXZr2pvuVDbI=; Received: from [114.124.37.80] (port=33067 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.86_1) (envelope-from ) id 1arag5-003z5x-LB; Sat, 16 Apr 2016 18:35:06 -0600 Date: Sun, 17 Apr 2016 08:34:59 +0800 From: Erich Dollansky To: Bernt Hansson Cc: freebsd-questions@freebsd.org Subject: Re: Geli and glabel ? Message-ID: <20160417083459.4d47fa53@X220.alogt.com> In-Reply-To: <57126AFB.9060303@bananmonarki.se> References: <57125647.9050805@bananmonarki.se> <57126AFB.9060303@bananmonarki.se> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Authenticated-Sender: sl-508-2.slc.westdc.net: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 00:35:10 -0000 Hi, On Sat, 16 Apr 2016 18:40:27 +0200 Bernt Hansson wrote: > On 2016-04-16 18:08, Warren Block wrote: > > On Sat, 16 Apr 2016, Bernt Hansson wrote: > > > >> Hello list. > >> > >> I'm wondering about glabel and geli. It seems that one can not > >> have them on the same disc. > >> > >> On swap it works nice but not on my home directory. Glabel > >> overwrites the meta data from geli > >> so the disc can not be mounted. > >> > >> Can this scenario work? How? > > > > One must be inside the other. Create a glabel device in the GELI > > one, then refer to the glabel device with /dev/label/xyz. > > Along this line? > > geli attach disc > password: > > glabel label 1213 /dev/disc > > Is that correct? it should work. I do it the other way around. First label the device and then use geli to attach the label. It will not help you much if your label is inside geli as you do not see the label without geli. If you use glabel outside geli you can then tell geli to use the label name instead of the device name. Erich From owner-freebsd-questions@freebsd.org Sun Apr 17 00:56:54 2016 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 87EF4AEE3AC for ; Sun, 17 Apr 2016 00:56:54 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3C6FC14AC for ; Sun, 17 Apr 2016 00:56:53 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id u3H0uMlg004111 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 16 Apr 2016 18:56:22 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id u3H0uLwT004108; Sat, 16 Apr 2016 18:56:22 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sat, 16 Apr 2016 18:56:21 -0600 (MDT) From: Warren Block To: Anton Sayetsky cc: Bernt Hansson , FreeBSD Questions Subject: Re: Geli and glabel ? In-Reply-To: Message-ID: References: <57125647.9050805@bananmonarki.se> <57126AFB.9060303@bananmonarki.se> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sat, 16 Apr 2016 18:56:22 -0600 (MDT) Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 00:56:54 -0000 On Sun, 17 Apr 2016, Anton Sayetsky wrote: > > 17 апр. 2016 г. 3:15 пользователь "Warren Block" написал: > > > > On Sun, 17 Apr 2016, Anton Sayetsky wrote: > > > >> > No, the /dev/disc device is being used both times. > >> > > >> >   geli attach disc > >> > > >> > creates a disc.eli device.  Now create the label on *that*: > >> > > >> >   glabel label 1213 /dev/disc.eli > >> This just doesn't make any sense bc if device name will change - geli name will change too. So it's really necessary to build reverse - geli on top of glabel. > > > > > > The label is only created once.  After that, it will be present when the .eli device is created. > I know. But here an example: > 1. Insert one disk > 2. Create geli and glabel there > 3. Pull out that disk and insert it again in random order with hundred of other disks > 4. Try to find where geli is located > So I can say again - glabel inside geli doesn't make any sense in any situation. But geli inside glabel makes sense almost always. Not any situation? What if I have data partitions on an encrypted drive? That gives a constant name to those partitions, but only after the drive has been mounted with geli. From owner-freebsd-questions@freebsd.org Sun Apr 17 01:23:38 2016 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 B32B6AEF000 for ; Sun, 17 Apr 2016 01:23:38 +0000 (UTC) (envelope-from jhunt@lynden.on.ca) Received: from mail-yw0-x233.google.com (mail-yw0-x233.google.com [IPv6:2607:f8b0:4002:c05::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 7BBB614C7 for ; Sun, 17 Apr 2016 01:23:38 +0000 (UTC) (envelope-from jhunt@lynden.on.ca) Received: by mail-yw0-x233.google.com with SMTP id t10so171451254ywa.0 for ; Sat, 16 Apr 2016 18:23:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lynden-on-ca.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=027xtw5XgfRQvLYCz5mKmF6eibLlqYlXLT1liJBwu4Y=; b=ZBG1e5lWYfAeHXyNI2mB0usmC5h24FEoPhQ28rg7gqRyhYsINuUHKwoXhhHdhXpUFa hjCxpXhATJVMV/i+Pq0lzTLTNCSl9igmtCOH5LB47sAwks0qoyw6WIkx2DXfkbUVlSkW MK6CsZ1x3HOG1oKUKzc4BCrcTdXE/kfmSasUf+YLxk0K5mpSefXpdr1hykK4fb+csok5 0mWmkf6x4/x8TXykQBnKAedBfVPj8WLp85QS7H96tSUnw24uqUVRtk9R6X06JBldsn+V 5KrkV11suvp1qYyokDDXtVQZT2NZMlo5WfO6+GZphhVeKRVtIrABh8baBMiTS8Cd4Kqv h8XQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=027xtw5XgfRQvLYCz5mKmF6eibLlqYlXLT1liJBwu4Y=; b=AueDCWxSRerL6Jly1ACV1WrRk9euhO8cai6lPYkMFq5DhWqvtoEWemKppXD+W9t6iL SfcWk/b+c0e6N+EeiM6cj+IQ3k/YhpdQHljEfczUb/UL0n15+rTyDfoLbuMWNCsYp8Yc nnm1W5Eo40/BPillz1luZRQZmw/RW8ppphYahcV9NbL5GwNpme2wO7Dxdq8IKOeod9wm t0vA++mQ0xjX0Ra1yoelmTPM38RJJDW9xovTwVvEH2hzhZB8MZQVAYJ8kT29bbse4v77 QLsGGwwPIXrpsEaDOK1osSc3T3QR6UfqytvLg04oAn1xfn8Mq6CcZHVkSf7f5Me7+rgk wybg== X-Gm-Message-State: AOPr4FVAvJx2TZA5NgUg6zRng9zcZUrVeJfumeAgRZaDfHFyvSS9XkOex4z04xKzJAo0PrW4fpGE/YWp4LCbUg== MIME-Version: 1.0 X-Received: by 10.37.203.2 with SMTP id b2mr4650910ybg.148.1460856217625; Sat, 16 Apr 2016 18:23:37 -0700 (PDT) Received: by 10.83.87.12 with HTTP; Sat, 16 Apr 2016 18:23:37 -0700 (PDT) X-Originating-IP: [173.33.69.78] In-Reply-To: <20160415180613.c066affb.freebsd@edvax.de> References: <20160416000316.V1139@sola.nimnet.asn.au> <20160415180613.c066affb.freebsd@edvax.de> Date: Sat, 16 Apr 2016 21:23:37 -0400 Message-ID: Subject: Re: Cannot enter sleep mode as non-root user (Operation not permitted) From: Jason Hunt To: Polytropon Cc: Ian Smith , freebsd-questions@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 01:23:38 -0000 On Fri, Apr 15, 2016 at 12:06 PM, Polytropon wrote: > > Being in wheel just means you can su root, and only root can suspend the > > system .. unless you have a suspend button .. or know root's password :) > > That is the key information: The program must be run by root. > Being in the operator or wheel group is not sufficient. > > Thanks. I thought that might be the case but couldn't find anything online which specifically stated root is required. This old post is what got me thinking wheel or operator should be able to do it, but I guess there's some misunderstanding of how XFCE actually performs suspend/shutdown/reboot: https://marc.info/?l=freebsd-questions&m=139039546710646&w=2 In the past I've always used full-blown DE's like XFCE and had to set the rights in PolicyKit, but now using cwm so I need to use commands for these types of tasks, and just kind of assumed I should be able to do it without root access. > > > > > Does anyone have suggestions for how to troubleshoot this? > > > > Revise expectations or hack acpiconf.c :) > > Or use a program like su, sudo, or super, for example like this: > > % sudo acpiconf -s3 > > which should work as expected. It's possible to assign this command > to a shell alias or even to a key (or key combination). > > > I thought about poking through the acpi code but decided to leave it as a future project :) My solution for now is to install sudo, set the following in /usr/local/etc/sudoers: %operator ALL=(root) NOPASSWD: /usr/sbin/zzz Then set the following in .cshrc: alias zzz /usr/local/bin/sudo /usr/sbin/zzz From owner-freebsd-questions@freebsd.org Sun Apr 17 02:40:23 2016 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 E627BB10AF2 for ; Sun, 17 Apr 2016 02:40:23 +0000 (UTC) (envelope-from nervoso@k1.com.br) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (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 C999D1839 for ; Sun, 17 Apr 2016 02:40:23 +0000 (UTC) (envelope-from nervoso@k1.com.br) X-MHO-User: bcfcfeac-0445-11e6-9fea-b54670b854a5 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 186.228.82.163 X-Mail-Handler: DuoCircle Outbound SMTP Received: from mailserver2.k1.com.br (unknown [186.228.82.163]) by outbound2.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Sun, 17 Apr 2016 02:40:24 +0000 (UTC) Received: from lenzinote.lenzicasa (179.184.51.72.static.gvt.net.br [179.184.51.72] (may be forged)) (authenticated bits=0) by mailserver2.k1.com.br (8.15.2/8.15.2) with ESMTPSA id u3H2eB0f028041 (version=TLSv1.2 cipher=DHE-DSS-AES128-GCM-SHA256 bits=128 verify=NOT); Sat, 16 Apr 2016 23:40:11 -0300 (BRT) (envelope-from nervoso@k1.com.br) Message-ID: <1460860819.81763.41.camel@k1.com.br> Subject: Re: No Sound and Fast You Tube From: =?ISO-8859-1?Q?S=E9rgio?= de Almeida Lenzi To: Jonathan Moore , freebsd-questions@freebsd.org Date: Sat, 16 Apr 2016 23:40:19 -0300 In-Reply-To: References: X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 02:40:24 -0000 Em Sáb, 2016-04-16 às 18:54 -0400, Jonathan Moore escreveu: > Hi > > I'm having trouble with my sound nothing plays on You Tube but when I > turn > up the volume > I hear static. I found this in the forums > https://forums.freebsd.org/threads/53712/ . > > Plus You Tube video plays fast and I really don't want to install > flash. > I'm > using Firefox.Running FreeBSD 10.3 RELEASE. > Mine works..   I use 10.3 STABLE  and it works.... You can test if you want my "port" of firefox Just create a file in the /etc/pkg directory named  xxxxx.conf with ===============cut============== DIST64: {   url: http://dist64.k1.com.br/${ABI},   enabled: yes } ===============cut ============== move the FreeBSD.conf to /root and then pkg install -y firefox BE SHURE to HAVE A BACKUP or make a zfs znapshot first. as this firefox works with the MATE desktop so will pull gnome2 stuff If you want to use the FULL desktop just... pkg install -y mate for office, use pkg install -y libreoffice.. it will install about 1GB from Internet and will use GDM as  the display manager... Just WORKS...  From owner-freebsd-questions@freebsd.org Sun Apr 17 03:32:58 2016 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 7FA3CAED067 for ; Sun, 17 Apr 2016 03:32:58 +0000 (UTC) (envelope-from user8@host-ns-3.basnet.by) Received: from host-ns-3.basnet.by (host-ns-3.basnet.by [80.94.169.4]) (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 3B01012F5 for ; Sun, 17 Apr 2016 03:32:57 +0000 (UTC) (envelope-from user8@host-ns-3.basnet.by) Received: from user8 by host-ns-3.basnet.by with local (Exim 4.86_1) (envelope-from ) id 1arc1y-004JhX-2W for freebsd-questions@freebsd.org; Sun, 17 Apr 2016 05:01:46 +0300 To: freebsd-questions@freebsd.org Subject: Bill Account Confirmation - 0270505992 X-PHP-Script: www.buk.by/technoart/ca.php for 41.140.3.159 From: BILLING CONFIRMATION N:3310 Message-Id: Date: Sun, 17 Apr 2016 05:01:46 +0300 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host-ns-3.basnet.by X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [559 570] / [47 12] X-AntiAbuse: Sender Address Domain - host-ns-3.basnet.by X-Get-Message-Sender-Via: host-ns-3.basnet.by: authenticated_id: user8/primary_hostname/system user X-Authenticated-Sender: host-ns-3.basnet.by: user8 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 03:32:58 -0000 From owner-freebsd-questions@freebsd.org Sun Apr 17 04:31:22 2016 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 7710CB0A79F for ; Sun, 17 Apr 2016 04:31:22 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D51DB10B7 for ; Sun, 17 Apr 2016 04:31:20 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id u3H4UvTF027008; Sun, 17 Apr 2016 14:30:58 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sun, 17 Apr 2016 14:30:57 +1000 (EST) From: Ian Smith To: Jason Hunt cc: Polytropon , freebsd-questions@freebsd.org Subject: Re: Cannot enter sleep mode as non-root user (Operation not permitted) In-Reply-To: Message-ID: <20160417142231.L1139@sola.nimnet.asn.au> References: <20160416000316.V1139@sola.nimnet.asn.au> <20160415180613.c066affb.freebsd@edvax.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 04:31:22 -0000 On Sat, 16 Apr 2016 21:23:37 -0400, Jason Hunt wrote: > > > Being in wheel just means you can su root, and only root can suspend the > > > system .. unless you have a suspend button .. or know root's password :) I mentioned the suspend button kind-of jokingly, but now I'm curious: What make/model of laptop does not have a suspend (aka sleep) button? Or is it that yours does not work properly? cheers, Ian From owner-freebsd-questions@freebsd.org Sun Apr 17 07:26:52 2016 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 4BEC8B116B6 for ; Sun, 17 Apr 2016 07:26:52 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0B36716DA for ; Sun, 17 Apr 2016 07:26:51 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [62.216.197.7] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1arh6Q-0001rT-Lr for freebsd-questions@freebsd.org; Sun, 17 Apr 2016 09:26:42 +0200 Received: from localhost.my.domain (c720-r292778-amd64 [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id u3H7QfH6002394 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sun, 17 Apr 2016 09:26:41 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id u3H7Qf6M002393 for freebsd-questions@freebsd.org; Sun, 17 Apr 2016 09:26:41 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Sun, 17 Apr 2016 09:26:41 +0200 From: Matthias Apitz To: freebsd-questions@freebsd.org Subject: tool for mapping away bad blocks on an external disk Message-ID: <20160417072641.GA2358@c720-r292778-amd64> 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 11.0-CURRENT r292778 (amd64) User-Agent: Mutt/1.5.24 (2015-08-30) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 62.216.197.7 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 07:26:52 -0000 Hello, I have an older external disk, connected through USB, which has bad blocks: Apr 17 09:16:38 c720-r292778-amd64 kernel: ugen0.3: at usbus0 Apr 17 09:16:38 c720-r292778-amd64 kernel: umass0: on usbus0 Apr 17 09:16:38 c720-r292778-amd64 kernel: umass0: SCSI over Bulk-Only; quirks = 0x0100 Apr 17 09:16:38 c720-r292778-amd64 kernel: umass0:1:0: Attached to scbus1 Apr 17 09:16:38 c720-r292778-amd64 kernel: da0 at umass-sim0 bus 0 scbus1 target 0 lun 0 Apr 17 09:16:38 c720-r292778-amd64 kernel: da0: Fixed Direct Access SCSI-2 device Apr 17 09:16:38 c720-r292778-amd64 kernel: da0: Serial Number FAFFFFF0FDF1F6F90FA46017 Apr 17 09:16:38 c720-r292778-amd64 kernel: da0: 40.000MB/s transfers Apr 17 09:16:38 c720-r292778-amd64 kernel: da0: 1430799MB (2930277168 512 byte sectors) Apr 17 09:16:38 c720-r292778-amd64 kernel: da0: quirks=0x2 # fsck /dev/da0s1a ** /dev/da0s1a ** Last Mounted on / ** Phase 1 - Check Blocks and Sizes CANNOT READ BLK: 1512063104 CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 1512063180, 1512063219, CANNOT READ BLK: 1794212160 CONTINUE? [yn] Do we have some good tool to perform an analyse of the full disk and map away all bad blocks? There is no important data on this disk and if I can not get rid of the bad blocks I must throw it to dustbin. Thanks matthias -- Matthias Apitz, ✉ guru@unixarea.de, ⌂ http://www.unixarea.de/ ☎ +49-176-38902045 From owner-freebsd-questions@freebsd.org Sun Apr 17 07:52:22 2016 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 E8313B11DC4 for ; Sun, 17 Apr 2016 07:52:22 +0000 (UTC) (envelope-from xxjack12xx@gmail.com) Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::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 C5A91101C for ; Sun, 17 Apr 2016 07:52:22 +0000 (UTC) (envelope-from xxjack12xx@gmail.com) Received: by mail-ig0-x233.google.com with SMTP id g8so57725360igr.0 for ; Sun, 17 Apr 2016 00:52:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-transfer-encoding; bh=3840Exx9wy1PinwQSfYhpYQqBrHZCiTYUgt8zbe+UoA=; b=OwNdy69juxIdm29EHjd8mksUpzmhVKwLbbIpNGsHpOGtBrabWvS9YHFsmNkOBX9XQN ykXValuPg2Q/h85B5fG1RnzFLUHiQsPGAeA9OsWyF4deR7RJ6bWKP1JTedFMRs1e3F7Z 9E+B+C24z3JabEUePhSgnGoEKkGzjd9Pugeh/mPdizDCTmhbuOI4Ww+NUlqhM9Inxg91 zRyOToHmaWMjDZBApoZXzUjoMHmAYjOwvMhpOPSh27kWTyAVHDrFyWKmGmOFt3Qr5lRa Bgb/RgcBlwZFefTlJxQeYqJJTZTlUruV4WqGE64wRpSVdqwhEQ+W1YU4DiBt6mzJIbTN TEKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=3840Exx9wy1PinwQSfYhpYQqBrHZCiTYUgt8zbe+UoA=; b=VTwlX60G3pdN8EvUfQOZeKF7+dSgyLlu2xVUhmJQO+jt2ypB+unHTYbrDNQDMFDAsh +OoroaMm8Puu8CzhYEv4xTARuy0dqXf6k+YFdhTr+2jb0ouP3PChK5jdCl9PEsVw/3jB 4AQcZZiKiEb5VwQBuvIAmy90S+etnes+mEXSn3nPvcWyrVkQ5ZRD1jSQkVAIKWTaB+9R 0Oox1NR1NJCczTuvRkptZeDgObbDyNC+OH+0xynPEyOn5YnE8n33e/D+0k5mw0zYMdqO /WR/mi7nDYzsfmGq8RH2Iz7KJmb/RwFMpzV1iTtoCnanCYQ/+7ww1C4tizpamAeaDrKL MToA== X-Gm-Message-State: AOPr4FWhBd7JJGNnhuyEzgp17hasO//HitN8mNIcchuzf2/1N2Rxf8HYOVzK6PGQQuxDprzyBe8REmPyXpGqiA== X-Received: by 10.50.92.37 with SMTP id cj5mr13528294igb.91.1460879542079; Sun, 17 Apr 2016 00:52:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.41.129 with HTTP; Sun, 17 Apr 2016 00:51:42 -0700 (PDT) In-Reply-To: <20160417072641.GA2358@c720-r292778-amd64> References: <20160417072641.GA2358@c720-r292778-amd64> From: "Jack L." Date: Sun, 17 Apr 2016 00:51:42 -0700 Message-ID: Subject: Re: tool for mapping away bad blocks on an external disk To: Matthias Apitz , "freebsd-questions@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 07:52:23 -0000 IMO, any drive with bad blocks aren't worth keeping around. Once bad blocks start developing, more usually follow shortly after until it turns into SMART Health Status: HARDWARE IMPENDING FAILURE TOO MANY BLOCK REASSIGNS [asc=3D5d, ascq=3D14] On Sun, Apr 17, 2016 at 12:26 AM, Matthias Apitz wrote: > > Hello, > > I have an older external disk, connected through USB, which has bad > blocks: > > Apr 17 09:16:38 c720-r292778-amd64 kernel: ugen0.3: at usbus0 > Apr 17 09:16:38 c720-r292778-amd64 kernel: umass0: = on usbus0 > Apr 17 09:16:38 c720-r292778-amd64 kernel: umass0: SCSI over Bulk-Only; = quirks =3D 0x0100 > Apr 17 09:16:38 c720-r292778-amd64 kernel: umass0:1:0: Attached to scbus1 > Apr 17 09:16:38 c720-r292778-amd64 kernel: da0 at umass-sim0 bus 0 scbus1= target 0 lun 0 > Apr 17 09:16:38 c720-r292778-amd64 kernel: da0: Fixed Direct Access SCSI-2 device > Apr 17 09:16:38 c720-r292778-amd64 kernel: da0: Serial Number FAFFFFF0FDF= 1F6F90FA46017 > Apr 17 09:16:38 c720-r292778-amd64 kernel: da0: 40.000MB/s transfers > Apr 17 09:16:38 c720-r292778-amd64 kernel: da0: 1430799MB (2930277168 512= byte sectors) > Apr 17 09:16:38 c720-r292778-amd64 kernel: da0: quirks=3D0x2 > > > # fsck /dev/da0s1a > ** /dev/da0s1a > ** Last Mounted on / > ** Phase 1 - Check Blocks and Sizes > > CANNOT READ BLK: 1512063104 > CONTINUE? [yn] y > > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 1512063180, 1512063219, > > CANNOT READ BLK: 1794212160 > CONTINUE? [yn] > > Do we have some good tool to perform an analyse of the full disk and map > away all bad blocks? There is no important data on this disk and if I > can not get rid of the bad blocks I must throw it to dustbin. > > Thanks > > matthias > > -- > Matthias Apitz, =E2=9C=89 guru@unixarea.de, =E2=8C=82 http://www.unixarea= .de/ =E2=98=8E +49-176-38902045 > _______________________________________________ > 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 Sun Apr 17 08:40:23 2016 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 5FF18AEE0E2 for ; Sun, 17 Apr 2016 08:40:23 +0000 (UTC) (envelope-from steve@sohara.org) Received: from uk1mail2513.mymailbank.co.uk (UK1MAIL2513-PERMANET.IE.mymailbank.co.uk [217.69.47.44]) by mx1.freebsd.org (Postfix) with ESMTP id D52B71070 for ; Sun, 17 Apr 2016 08:40:21 +0000 (UTC) (envelope-from steve@sohara.org) Received: from smtp.lan.sohara.org (UnknownHost [88.151.27.41]) by uk1mail2513-d.mymailbank.co.uk with SMTP; Sun, 17 Apr 2016 09:40:03 +0100 Received: from [192.168.63.1] (helo=steve.lan.sohara.org) by smtp.lan.sohara.org with smtp (Exim 4.86 (FreeBSD)) (envelope-from ) id 1ariFK-0004Dk-Gk; Sun, 17 Apr 2016 08:39:58 +0000 Date: Sun, 17 Apr 2016 09:39:57 +0100 From: Steve O'Hara-Smith To: Matthias Apitz Cc: freebsd-questions@freebsd.org Subject: Re: tool for mapping away bad blocks on an external disk Message-Id: <20160417093957.0b1acb4c37d7c15a4b06af88@sohara.org> In-Reply-To: <20160417072641.GA2358@c720-r292778-amd64> References: <20160417072641.GA2358@c720-r292778-amd64> X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) X-Clacks-Overhead: "GNU Terry Pratchett" 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 08:40:23 -0000 On Sun, 17 Apr 2016 09:26:41 +0200 Matthias Apitz wrote: > > Hello, > > I have an older external disk, connected through USB, which has bad > blocks: The tool you're looking for is badsect - I'm moderately surprised it's still around, the last time I used it was on FreeBSD 1.1.5.1 but it is still in FreeBSD 10.3. It doesn't do the analysis though - you'll have to do that with the filesystem unmounted and just used dd conv=noerror if= of=/dev/null to read the whole device and pull the duff sectors out of the error messages. However it's been a *long* time since this was worth doing except perhaps as a last ditch data recovery exercise, drives have had internal sector remapping for a long time now and when that stops working they are well and truly banjaxed. -- Steve O'Hara-Smith From owner-freebsd-questions@freebsd.org Sun Apr 17 09:22:24 2016 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 DB2EBB103FF for ; Sun, 17 Apr 2016 09:22:24 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from anny.lostinspace.de (anny.lostinspace.de [IPv6:2001:608:a02::33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A3F321696 for ; Sun, 17 Apr 2016 09:22:24 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from server.idefix.lan (aftr-88-217-181-72.dynamic.mnet-online.de [88.217.181.72]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: idefix@fechner.net) by anny.lostinspace.de (Postfix) with ESMTPSA id 6C8BC3889EC for ; Sun, 17 Apr 2016 11:22:20 +0200 (CEST) DMARC-Filter: OpenDMARC Filter v1.3.1 anny.lostinspace.de 6C8BC3889EC Authentication-Results: anny.lostinspace.de; dmarc=none header.from=fechner.net DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=fechner.net; s=default; t=1460884940; bh=UGnXH2UDnKMfgVChoIaaXuO37XXMgKNKX4fzZqjWebk=; h=To:From:Subject:Date; b=CejDKaOWROUCWAPnL/Jm3HNJSa+q0Z/j/TWtknu2cz3Q7hY/kt9DhfaZzy5kl7YBG b5rnrcdeXTnP4AgbIGG8KQy74WELwVG/nheU+XkN9Q3/qIn6/Y2MZMhNHwlBj9LxAB /R44JjIPWQXaYmVfLA9YwyXYgQZwkbwm15ypHolU= Received: from [192.168.0.151] (aftr-88-217-181-72.dynamic.mnet-online.de [88.217.181.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by server.idefix.lan (Postfix) with ESMTPSA id 96453252CCD for ; Sun, 17 Apr 2016 11:22:19 +0200 (CEST) To: "freebsd-questions@freebsd.org" From: Matthias Fechner Subject: Convert ipfw rule to pf Message-ID: Date: Sun, 17 Apr 2016 11:22:05 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 09:22:25 -0000 Dear all, I use sslh to have a transparent proxy for ssh/https in place. The transparent proxy support of sslh requires ipfw rules to work. I'm not sure if sslh is doing something in the background and that is the reason why it is not working with pf. Maybe we have here a pf guru on the list that can ensure the the rule itself is correct. The ipfw rule looks like: # https ipfw add 20000 fwd 192.168.0.251,443 log tcp from 192.168.0.251 8443 to any out ipfw add 20001 fwd 192.168.200.6,443 log tcp from 192.168.200.6 8443 to any out # ssh ipfw add 20003 fwd 192.168.200.6,443 log tcp from 192.168.200.6 22 to any out In pf they look like: rdr pass log inet proto tcp from 192.168.0.251 port 8443 to any -> 192.168.0.251 port 443 rdr pass log inet proto tcp from 192.168.200.6 port 8443 to any -> 192.168.200.6 port 443 rdr pass log inet proto tcp from 192.168.200.6 port 22 to any -> 192.168.200.6 port 443 Thanks. Gruß Matthias -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook From owner-freebsd-questions@freebsd.org Sun Apr 17 09:31:09 2016 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 95B82B10653 for ; Sun, 17 Apr 2016 09:31:09 +0000 (UTC) (envelope-from reko.turja@liukuma.net) Received: from cerebro.liukuma.net (unknown [IPv6:2a00:d1e0:1000:1b00::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5B2CC1869 for ; Sun, 17 Apr 2016 09:31:09 +0000 (UTC) (envelope-from reko.turja@liukuma.net) Received: from cerebro.liukuma.net (localhost [127.0.0.1]) by cerebro.liukuma.net (Postfix) with ESMTP id 841408B1789 for ; Sun, 17 Apr 2016 12:30:59 +0300 (EEST) DKIM-Filter: OpenDKIM Filter v2.10.3 cerebro.liukuma.net 841408B1789 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=liukuma.net; s=liukudkim; t=1460885459; bh=Ul2ezuLWd1cwrOLyso2qMmAsUOWj6UqLG4ASqPNV4s8=; h=From:To:References:In-Reply-To:Subject:Date; b=i6lpIlt/bQiR0uuRiNKIpQPFpiXkxvE8dHne2ViyXFJZuT+0/LAA0q+dSaAID6SbL jt0QNvrmoj4m4iwVEoynThxQmN3JuI60e8iT41P3Gl3SfIFEYdZPoBpJJ58vYtrLL7 pl4b9iExA0uBa8orPAgHAs5rWzRgpHHSfds5Etpo= X-Virus-Scanned: amavisd-new at liukuma.net Received: from cerebro.liukuma.net ([127.0.0.1]) by cerebro.liukuma.net (cerebro.liukuma.net [127.0.0.1]) (amavisd-new, port 10027) with LMTP id MRrskLl9y5FX for ; Sun, 17 Apr 2016 12:30:58 +0300 (EEST) Received: from Rivendell (dsl-kmibrasgw1-50dfdd-193.dhcp.inet.fi [80.223.221.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: ignatz@cerebro.liukuma.net) by cerebro.liukuma.net (Postfix) with ESMTPSA id 1FF9F8B174F for ; Sun, 17 Apr 2016 12:30:58 +0300 (EEST) DKIM-Filter: OpenDKIM Filter v2.10.3 cerebro.liukuma.net 1FF9F8B174F Message-ID: From: "Reko Turja" To: References: In-Reply-To: Subject: Re: Bill Account Confirmation - 0270505992 Date: Sun, 17 Apr 2016 12:30:57 +0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 16.4.3564.1216 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3564.1216 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 09:31:09 -0000 liukuma.net. IN SPF "v=spf1 a mx -all" Just saying... -Reko -----Original Message----- From: BILLING@liukuma.net ; CONFIRMATION@liukuma.net ; NX@liukuma.net:3310 Sent: Sunday, April 17, 2016 5:01 AM To: freebsd-questions@freebsd.org Subject: Bill Account Confirmation - 0270505992 _______________________________________________ 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 Sun Apr 17 09:53:27 2016 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 D129EB10F83 for ; Sun, 17 Apr 2016 09:53:27 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from anny.lostinspace.de (anny.lostinspace.de [IPv6:2001:608:a02::33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 98A8212F5; Sun, 17 Apr 2016 09:53:27 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from server.idefix.lan (unknown [IPv6:2001:a61:12a4:a501:dacb:8aff:febf:62dd]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: idefix@fechner.net) by anny.lostinspace.de (Postfix) with ESMTPSA id D818C38871A; Sun, 17 Apr 2016 11:53:17 +0200 (CEST) DMARC-Filter: OpenDMARC Filter v1.3.1 anny.lostinspace.de D818C38871A Authentication-Results: anny.lostinspace.de; dmarc=none header.from=fechner.net DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=fechner.net; s=default; t=1460886797; bh=07RuGL1WTWuAFlqhnxczpp/MJ8o71G7Q0VWJoKIyE+c=; h=Subject:To:References:Cc:From:Date:In-Reply-To; b=txDu5eSOQt2dEb5wzOFtyyOHjEldVFZ2q/Kh9+KdxpbsBMxuScRQn9DWz/AHiJrNv P0Q5WKhS4whHgVkM50W+/QgQUhszPjMGvXFGjefgpgZtuEdysGH6tNvCJdB2WFgbiK mydtxeBcF4XJ8Lodr9R/r9vg1W9goN6KOTDEUU20= Received: from [192.168.0.151] (aftr-88-217-181-72.dynamic.mnet-online.de [88.217.181.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by server.idefix.lan (Postfix) with ESMTPSA id 4CD78252E3A; Sun, 17 Apr 2016 11:53:16 +0200 (CEST) Subject: Re: Bill Account Confirmation - 0270505992 To: freebsd-questions@freebsd.org References: Cc: postmaster@freebsd.org From: Matthias Fechner Message-ID: Date: Sun, 17 Apr 2016 11:53:02 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 09:53:27 -0000 Am 17.04.2016 um 11:30 schrieb Reko Turja: > liukuma.net. IN SPF "v=spf1 a mx -all" > > Just saying... yes it seems that freebsd does not check the SPF record. Just saw this morning a forged mail from my domain as well: host -t SPF fechner.net fechner.net has SPF record "v=spf1 a mx a:anny.lostinspace.de -all" Would be nice if the postmaster would add a SPF check. Thanks Matthias -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook From owner-freebsd-questions@freebsd.org Sun Apr 17 12:56:02 2016 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 D4F0BB109D8 for ; Sun, 17 Apr 2016 12:56:02 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9CB371E93 for ; Sun, 17 Apr 2016 12:56:01 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de (port-92-195-71-243.dynamic.qsc.de [92.195.71.243]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 766043CD82; Sun, 17 Apr 2016 14:55:57 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id u3HCtusf002160; Sun, 17 Apr 2016 14:55:56 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sun, 17 Apr 2016 14:55:56 +0200 From: Polytropon To: Jason Hunt Cc: freebsd-questions@freebsd.org Subject: Re: Cannot enter sleep mode as non-root user (Operation not permitted) Message-Id: <20160417145556.08614f61.freebsd@edvax.de> In-Reply-To: References: <20160416000316.V1139@sola.nimnet.asn.au> <20160415180613.c066affb.freebsd@edvax.de> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 12:56:02 -0000 On Sat, 16 Apr 2016 21:23:37 -0400, Jason Hunt wrote: > On Fri, Apr 15, 2016 at 12:06 PM, Polytropon wrote: > > > > Being in wheel just means you can su root, and only root can suspend the > > > system .. unless you have a suspend button .. or know root's password :) > > > > That is the key information: The program must be run by root. > > Being in the operator or wheel group is not sufficient. > > > > > Thanks. I thought that might be the case but couldn't find anything online > which specifically stated root is required. > > This old post is what got me thinking wheel or operator should be able to > do it, but I guess there's some misunderstanding of how XFCE actually > performs suspend/shutdown/reboot: > https://marc.info/?l=freebsd-questions&m=139039546710646&w=2 > > In the past I've always used full-blown DE's like XFCE and had to set the > rights in PolicyKit, but now using cwm so I need to use commands for these > types of tasks, and just kind of assumed I should be able to do it without > root access. The problem with those DEs is that it's hard to understand how things are done, and when they stop working, it's almost impossible to state _what_ went wrong. :-) > > > > Does anyone have suggestions for how to troubleshoot this? > > > > > > Revise expectations or hack acpiconf.c :) > > > > Or use a program like su, sudo, or super, for example like this: > > > > % sudo acpiconf -s3 > > > > which should work as expected. It's possible to assign this command > > to a shell alias or even to a key (or key combination). > > > > > > > I thought about poking through the acpi code but decided to leave it as a > future project :) Probably not a good idea: The security barrier within the program is well intended and desired. > My solution for now is to install sudo, set the following in > /usr/local/etc/sudoers: > > %operator ALL=(root) NOPASSWD: /usr/sbin/zzz > > Then set the following in .cshrc: > > alias zzz /usr/local/bin/sudo /usr/sbin/zzz That should work (if "zzz" should select -s 3 as intended). You could also assign that command to a key (or key combination) on your keyboard, so a simple keypress will send the system to sleep. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Sun Apr 17 13:07:33 2016 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 E842CB10DAD for ; Sun, 17 Apr 2016 13:07:33 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id CA018121C for ; Sun, 17 Apr 2016 13:07:33 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id C58CEB10DAC; Sun, 17 Apr 2016 13:07:33 +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 C5316B10DAB for ; Sun, 17 Apr 2016 13:07:33 +0000 (UTC) (envelope-from luzar722@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 91226121B for ; Sun, 17 Apr 2016 13:07:33 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-io0-x236.google.com with SMTP id g185so173458466ioa.2 for ; Sun, 17 Apr 2016 06:07:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-transfer-encoding; bh=620GxwJkXHADNILUZMlyoGIXjlMeOywOKxc5d/gprzc=; b=c/jdt5HR/ppGV4eGYsJbO6V7SIrCPa6Fk2FIsFezDr8viVkHyuNxZO2t7aYnh/dDR+ n2Vlc9+zwi/UiMOmSIJLA4g/0kVwW+XFOG1nit7GDxvv0DxELzmWDjkEpIQ3n1Fe82O+ UcvlOLBx4FpbnDU/buAgsGjvYpWZVr/HRyPRKd1cn0WIoZtaOGzQOoqVKxWVURQqURsR 1m5lQuXPV+jS2DcqEg3f0iCU7we5Cir8s3TGBVIr/KsuZnPci0ZxWamcG5G2H3n2+TfM rdcM+JDQY4t80/0ZLksZglgWxrtv8+aE0/JPTgrcw9tHUf8Qk2iUtCbvNVFGMhQVUQp5 MpsQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:content-transfer-encoding; bh=620GxwJkXHADNILUZMlyoGIXjlMeOywOKxc5d/gprzc=; b=caKXXwdDemfG1AaqeHUsAYBUz1atHIQjNz9EAlD3cXaDivK3L5wfmbR7uPvYuoFvdr ld1It/cwueVFGRflLCGcaz7dy8tb1uDn09d2UuM5PAt7vUSihfsYgpnQ55FkroFnvwKV FSPABakKNQMybXvJJGkoQ+N85KEwltwhBevGZK461aZ5h3WrQSgkACDKL+hA/VZhsFKt zaEGh1Nvvz+vLwUP6P4Ta/2PXBvArxOW9YzE98zCP5XzR0whxqpyvBHQQ4qRqVumNPyp sAuWL7kxS6emujP09g88aaaV3Btlu5GcqHEMSRAMxiYfcaXsNtRUcFhxx5iMcU7Za++y Bqjg== X-Gm-Message-State: AOPr4FVumwikOa3pvBsw+CEZpv5cCx6JQ2JWLDEryV0fyPHK6xcuavT42/EIHOBWh0wBeg== X-Received: by 10.107.26.203 with SMTP id a194mr36008331ioa.115.1460898452934; Sun, 17 Apr 2016 06:07:32 -0700 (PDT) Received: from [10.0.10.3] (cpe-76-190-244-6.neo.res.rr.com. [76.190.244.6]) by smtp.googlemail.com with ESMTPSA id l80sm32987935iod.14.2016.04.17.06.07.32 for (version=TLSv1/SSLv3 cipher=OTHER); Sun, 17 Apr 2016 06:07:32 -0700 (PDT) Message-ID: <57138A98.4050601@gmail.com> Date: Sun, 17 Apr 2016 09:07:36 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: questions@freebsd.org Subject: Security - is my system penetrated? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 13:07:34 -0000 Hello list; In this morning's "daily run output" I have these messages which I have never seen before. > Mail in local queue: > -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient------- > 19A8C13CB2 1046 Sat Apr 16 04:02:05 root@dir21 > (connect to dir21[198.105.244.228]:25: Network is unreachable) > root@dir21 > > 1BA9913CB7 2928 Sat Apr 16 17:44:14 MAILER-DAEMON > (connect to dir20[198.105.244.228]:25: Network is unreachable) > root@dir20 > > 0FDC013CB1 1106 Sat Apr 16 08:16:04 root@dir21 > (connect to dir21[198.105.254.228]:25: Network is unreachable) > root@dir21 > > DF3A513CB4 1046 Sun Apr 17 04:01:14 root@dir21 > (connect to dir21[198.105.244.228]:25: Network is unreachable) > root@dir21 > > BB6CE13CBA 1046 Sun Apr 17 04:01:52 root@dir20 > (connect to dir20[198.105.254.228]:25: Network is unreachable) > root@dir20 > > 6532F13CA9 2868 Sun Apr 17 04:49:14 MAILER-DAEMON > (connect to dir20[198.105.244.228]:25: Network is unreachable) > root@dir20 > > -- 9 Kbytes in 6 Requests. To me this looks like received inbound mail trying to commutate with my jails. This is why I think my system has been penetrated. This system has only been running 4 days now. I installed 10.3 from scratch. sendmail is turned off and running postfix. Port 25 is blocked in ipf firewall. Run fetchmail against my domain mail service provided by my domain register. dir20 and dir21 are jails which only became active on Apr 15 around 9am. Have 4 xp systems & one win7 system on LAN behind the host. I can not see how an outsider could know about the jails with out having admin authority to the host system. Could one of the LAN boxes be infected in such a way as to allow remote user to access the host FBSD system? I know that I can delete those queued postfix emails, but is there a way to read them from the host instead? Desire suggestions on ways to investigate and determine what is happing. Thanks for your help From owner-freebsd-questions@freebsd.org Sun Apr 17 13:41:12 2016 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 351B4B11690 for ; Sun, 17 Apr 2016 13:41:12 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 2415C1EF0 for ; Sun, 17 Apr 2016 13:41:12 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by mailman.ysv.freebsd.org (Postfix) id 1FA8DB1168F; Sun, 17 Apr 2016 13:41:12 +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 1F4A7B1168E for ; Sun, 17 Apr 2016 13:41:12 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.70.90]) by mx1.freebsd.org (Postfix) with ESMTP id D31B31EEF for ; Sun, 17 Apr 2016 13:41:11 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id A9D31CB8CA2; Sun, 17 Apr 2016 08:41:10 -0500 (CDT) Received: from 76.193.16.109 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Sun, 17 Apr 2016 08:41:10 -0500 (CDT) Message-ID: <54382.76.193.16.109.1460900470.squirrel@cosmo.uchicago.edu> In-Reply-To: <57138A98.4050601@gmail.com> References: <57138A98.4050601@gmail.com> Date: Sun, 17 Apr 2016 08:41:10 -0500 (CDT) Subject: Re: Security - is my system penetrated? From: "Valeri Galtsev" To: "Ernie Luzar" Cc: questions@freebsd.org 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 13:41:12 -0000 On Sun, April 17, 2016 8:07 am, Ernie Luzar wrote: > Hello list; > > In this morning's "daily run output" I have these messages which I have > never seen before. > >> Mail in local queue: >> -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient------- >> 19A8C13CB2 1046 Sat Apr 16 04:02:05 root@dir21 >> (connect to dir21[198.105.244.228]:25: Network is >> unreachable) >> root@dir21 >> >> 1BA9913CB7 2928 Sat Apr 16 17:44:14 MAILER-DAEMON >> (connect to dir20[198.105.244.228]:25: Network is >> unreachable) >> root@dir20 >> >> 0FDC013CB1 1106 Sat Apr 16 08:16:04 root@dir21 >> (connect to dir21[198.105.254.228]:25: Network is >> unreachable) >> root@dir21 >> >> DF3A513CB4 1046 Sun Apr 17 04:01:14 root@dir21 >> (connect to dir21[198.105.244.228]:25: Network is >> unreachable) >> root@dir21 >> >> BB6CE13CBA 1046 Sun Apr 17 04:01:52 root@dir20 >> (connect to dir20[198.105.254.228]:25: Network is >> unreachable) >> root@dir20 >> >> 6532F13CA9 2868 Sun Apr 17 04:49:14 MAILER-DAEMON >> (connect to dir20[198.105.244.228]:25: Network is >> unreachable) >> root@dir20 >> >> -- 9 Kbytes in 6 Requests. > > To me this looks like received inbound mail trying to commutate with my > jails. This is why I think my system has been penetrated. > > This system has only been running 4 days now. I installed 10.3 from > scratch. sendmail is turned off and running postfix. Port 25 is blocked > in ipf firewall. Run fetchmail against my domain mail service provided > by my domain register. dir20 and dir21 are jails which only became > active on Apr 15 around 9am. Have 4 xp systems & one win7 system on LAN > behind the host. > > I can not see how an outsider could know about the jails with out having > admin authority to the host system. > > Could one of the LAN boxes be infected in such a way as to allow remote > user to access the host FBSD system? > > I know that I can delete those queued postfix emails, but is there a way > to read them from the host instead? Postfix keeps each message in a queue as a files, and filename is just message ID postfix assigned to message. You can use "find" command to find each of these files where postfix keeps queues, then use "postcat" postfix command to display the message. Say, you found location of first message with ID 19A8C13CB2. You can: postcat /path/to/the/file/19A8C13CB2 | less It is hard to have a judgement what could be going on without knowing details of your setup. But you are right, reading messages may give you some clues. Good luck! Valeri > > Desire suggestions on ways to investigate and determine what is happing. > > Thanks for your help > _______________________________________________ > 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 Sun Apr 17 16:33:43 2016 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 A7B65B12E4D for ; Sun, 17 Apr 2016 16:33:43 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5887619B6 for ; Sun, 17 Apr 2016 16:33:43 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id u3HGXft0044724 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 17 Apr 2016 10:33:41 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id u3HGXfF4044721; Sun, 17 Apr 2016 10:33:41 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 17 Apr 2016 10:33:40 -0600 (MDT) From: Warren Block To: "Steve O'Hara-Smith" cc: Matthias Apitz , freebsd-questions@freebsd.org Subject: Re: tool for mapping away bad blocks on an external disk In-Reply-To: <20160417093957.0b1acb4c37d7c15a4b06af88@sohara.org> Message-ID: References: <20160417072641.GA2358@c720-r292778-amd64> <20160417093957.0b1acb4c37d7c15a4b06af88@sohara.org> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 17 Apr 2016 10:33:41 -0600 (MDT) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 16:33:43 -0000 On Sun, 17 Apr 2016, Steve O'Hara-Smith wrote: > On Sun, 17 Apr 2016 09:26:41 +0200 > Matthias Apitz wrote: > >> >> Hello, >> >> I have an older external disk, connected through USB, which has bad >> blocks: > > The tool you're looking for is badsect - I'm moderately surprised > it's still around, the last time I used it was on FreeBSD 1.1.5.1 but it is > still in FreeBSD 10.3. > > It doesn't do the analysis though - you'll have to do that with the > filesystem unmounted and just used dd conv=noerror if= of=/dev/null > to read the whole device and pull the duff sectors out of the error > messages. That won't remap them, though. > However it's been a *long* time since this was worth doing except > perhaps as a last ditch data recovery exercise, drives have had internal > sector remapping for a long time now and when that stops working they are > well and truly banjaxed. True. But this is not (yet :) a data recovery problem, just a desire to make the disk usable again. Bad blocks are only remapped on a write. I think that a SMART long test (smartctl -tlong) writes every block and will do remapping as a side effect, but have not verified it. The even more brute-force method would be to just manually write every block on the disk with dd. A bs= of 64K or 128K or more will help speed that up. Retries on bad writes might slow it down again. The drive could use up all available spares during that process, or continue to grow new bad blocks. That makes the decision to scrap it easy. If it successfully maps out the bad blocks and does not appear to be creating new ones, then using it becomes a judgement call. As they say, choose wisely. From owner-freebsd-questions@freebsd.org Sun Apr 17 17:04:03 2016 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 7AB90AED9E9 for ; Sun, 17 Apr 2016 17:04:03 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F1C7118FB for ; Sun, 17 Apr 2016 17:04:02 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (liminal.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3636:3bff:fed4:b0d6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id D05FF11816 for ; Sun, 17 Apr 2016 17:03:51 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/D05FF11816; dkim=none; dkim-atps=neutral Subject: Re: Bill Account Confirmation - 0270505992 To: freebsd-questions@freebsd.org References: From: Matthew Seaman Message-ID: <5713C1ED.6090708@FreeBSD.org> Date: Sun, 17 Apr 2016 18:03:41 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="6sAInlLVwQbCic6PBo7BefviTIbJC2I3e" X-Virus-Scanned: clamav-milter 0.99.1 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 17:04:03 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --6sAInlLVwQbCic6PBo7BefviTIbJC2I3e Content-Type: multipart/mixed; boundary="GkVnDfKCeLX10AecGpE1SjI2aW5hoJbkv" From: Matthew Seaman To: freebsd-questions@freebsd.org Message-ID: <5713C1ED.6090708@FreeBSD.org> Subject: Re: Bill Account Confirmation - 0270505992 References: In-Reply-To: --GkVnDfKCeLX10AecGpE1SjI2aW5hoJbkv Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 17/04/2016 10:53, Matthias Fechner wrote: > Am 17.04.2016 um 11:30 schrieb Reko Turja: >> liukuma.net. IN SPF "v=3Dspf1 a mx -all" >> >> Just saying... >=20 > yes it seems that freebsd does not check the SPF record. > Just saw this morning a forged mail from my domain as well: > host -t SPF fechner.net > fechner.net has SPF record "v=3Dspf1 a mx a:anny.lostinspace.de -all" >=20 > Would be nice if the postmaster would add a SPF check. There used to be a very nice integrated SPF checking facility that was available as a set of patches to the FreeBSD postfix port (postfix being what the FreeBSD mail system runs on), but it wasn't compatible with the latest stable version of postfix and got dropped. Upstream would not accept the patches for reasons I don't entirely understand, although there would have been some extra work to do, given this seems to me to be a natural addition to postfix's new-ish postscreen process. Instead to get SPF checking nowadays you need to implement either milter-sid (which was intended primarily to support the now largely abandoned SPFv2 stuff that Microsoft tried to introduce) or else one of the postfix-policyd-spf implementations (you get to choose from either perl or python there.) Cheers, Matthew --GkVnDfKCeLX10AecGpE1SjI2aW5hoJbkv-- --6sAInlLVwQbCic6PBo7BefviTIbJC2I3e Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJXE8HzXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATq5wP/1XoLwjTwULMwk9gC20QSmbO 3bht2mP+Tg+mCs2MdXht0yiIR0PkkrEgw6axAO3+UUGeYvi6kmz4WtqDomjVviUV HzDRwryff0opsytXsu+zLK9+bmrHU81fwmP+3MDGqQyVlPvaooRAfbqPs70yP+Uz XUsc5NEhLy4kFOGjiIegNp94XjhZVq73+HnJ7dQY5m3w1UFcT5We1ukxatInACxO pPlRdCSH64qWp1nXIKQaKCobv3lN4YQoMMGHkEyEv5oPsQlJnCMFkeHhmcpAYGUU MXfqt9ItA1qTy9DCSofltn+ObamuUUnTlz8vl7rKvCNibH5FxsDGa2jfo3tMrHos R9pNPmWMf/vYeubHM05v0qlNXmmGwNFh61MIOlRbxTYc85mOTTrMbSmuVFySo4CB nFYFnDFq/kguCIDCll07ASoU3KpVtkglNKVUOu9/FUu7dRzdCzFKzbPnAFx/GI8u C2CLpBfkIH/tBSTyeSczxEZ5LdY1YCQzdE9BMudEX6vjrz3/MFBcJyIm46IwwOR+ zgHq9CzlZL2cG2j8VQGvXv37BCyZP8/0OIzYEAL+rcHIKVGPWkdNXnwTiN0Q6RaL eOWherpCoRgPUuXnOth25Wy6u5jBdmenZj6eZslcfTNSNVJfdXOec6x9Lg7lX3jU vWXKkRBNq292ZOmSQe1O =xxgN -----END PGP SIGNATURE----- --6sAInlLVwQbCic6PBo7BefviTIbJC2I3e-- From owner-freebsd-questions@freebsd.org Sun Apr 17 17:10:53 2016 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 4123CAEDBF4 for ; Sun, 17 Apr 2016 17:10:53 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::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 D25A91B37 for ; Sun, 17 Apr 2016 17:10:52 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: by mail-wm0-x230.google.com with SMTP id l6so17605172wml.1 for ; Sun, 17 Apr 2016 10:10:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=m13ruIQGnxhUnK2Hs3FFyPvuf0pmvHKeTHeJQYz3300=; b=nFKjjhe3ViBBdaArs6ViLNIZIgEMexXAnlLes4YFfP+pBQBs2xbh1g9DLnXX/ENu3v j+51snA0cYaBWj9rKIPUPr2mmymky+IoJRBn2Wjl7bY1A8/EZEt/ye/zQP6d0tz57UQG MpE/ywKMut0LoCrA06vZ2DoPSag8e4iMDxxlVMwGjt/TvcEnnQU9VomMakTpJZEhIEXC y+YKvWMy2mWnT30OOnQ1kGE8wZgWl/b0eq6dxuO7yw7Q+X9Ms0aFxLZnZytVHM7HQMdz 9F+xHcRxnn5/h7N4xgGX3bBCLr0IXEPKGF7BllTt16pbB9bJ+CB/sLcnf3tgwYxYisxG rv+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=m13ruIQGnxhUnK2Hs3FFyPvuf0pmvHKeTHeJQYz3300=; b=HvFsqi61z6Z2zntHkMpXEoAVjoYbAf6amHU8QK1l6cvlU/nL5Eb7WjTLN0pLO0OWJF cLCZywHEa815STr66c6MYJoQSqnXH8JdR3UAYxX8Scn2CuyJSMmxiHX/yFAv7vDTi7cu nBULfYZg+IhwzUaofTlO0CfTMGRLBrA4C2DCIO+s/72QMcuTBo64e9Na/3280ew73qqT hfYWLN+Lqt0IvyHzYGk3B0+V4diVyMXXswVg3BNPi5D/HdJd0QypnjF6AExXRnbptzZR 7Svfsdj6KVsq2IB2/MKIR6S5wCXr3N7Dbxj9tY8zCO86ioe4iuf0iuyZiL0WHceYTdx7 NxnQ== X-Gm-Message-State: AOPr4FV+5bCkzbAQkH+zs0nmWuP46CoXxdm3WxybasGES18IMffE+8zFImsCGZoiuYlHJU2ukuBBgvktiE0mgA== X-Received: by 10.194.231.196 with SMTP id ti4mr23646920wjc.41.1460913051086; Sun, 17 Apr 2016 10:10:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.103.233 with HTTP; Sun, 17 Apr 2016 10:10:11 -0700 (PDT) From: Odhiambo Washington Date: Sun, 17 Apr 2016 20:10:11 +0300 Message-ID: Subject: rm -rf -Mitigating the dangers To: User Questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 17:10:53 -0000 I am wondering if I should place a feature request on this or just do it my way:) With great power comes great responsibility and as such I think there should be a wrapper around rm to warn sysadmins that what they are about to do with -rf is dangerous, yes? Read input from sysadmin 3 times, looking strictly for their confirmation before effecting the `rm -rf`. Could it be that what I am smoking/drinking is the issue here or I have your support? LOL -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft." From owner-freebsd-questions@freebsd.org Sun Apr 17 17:27:10 2016 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 A1703B10284 for ; Sun, 17 Apr 2016 17:27:10 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 663A4123C for ; Sun, 17 Apr 2016 17:27:09 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1arqTM-0002Wa-0z for freebsd-questions@freebsd.org; Sun, 17 Apr 2016 19:27:00 +0200 Received: from pool-72-66-1-32.washdc.fios.verizon.net ([72.66.1.32]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 17 Apr 2016 19:27:00 +0200 Received: from nightrecon by pool-72-66-1-32.washdc.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 17 Apr 2016 19:27:00 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Michael Powell Subject: Re: tool for mapping away bad blocks on an external disk Date: Sun, 17 Apr 2016 13:28:03 -0400 Lines: 57 Message-ID: References: <20160417072641.GA2358@c720-r292778-amd64> <20160417093957.0b1acb4c37d7c15a4b06af88@sohara.org> Reply-To: nightrecon@hotmail.com Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pool-72-66-1-32.washdc.fios.verizon.net X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 17:27:10 -0000 Warren Block wrote: > On Sun, 17 Apr 2016, Steve O'Hara-Smith wrote: > >> On Sun, 17 Apr 2016 09:26:41 +0200 >> Matthias Apitz wrote: >> >>> >>> Hello, >>> >>> I have an older external disk, connected through USB, which has bad >>> blocks: >> >> The tool you're looking for is badsect - I'm moderately surprised >> it's still around, the last time I used it was on FreeBSD 1.1.5.1 but it >> is still in FreeBSD 10.3. >> >> It doesn't do the analysis though - you'll have to do that with the >> filesystem unmounted and just used dd conv=noerror if= >> of=/dev/null to read the whole device and pull the duff sectors out of >> the error messages. > > That won't remap them, though. > >> However it's been a *long* time since this was worth doing except >> perhaps as a last ditch data recovery exercise, drives have had internal >> sector remapping for a long time now and when that stops working they are >> well and truly banjaxed. > > True. But this is not (yet :) a data recovery problem, just a desire to > make the disk usable again. Bad blocks are only remapped on a write. > I think that a SMART long test (smartctl -tlong) writes every block > and will do remapping as a side effect, but have not verified it. > > The even more brute-force method would be to just manually write every > block on the disk with dd. A bs= of 64K or 128K or more will help speed > that up. Retries on bad writes might slow it down again. > > The drive could use up all available spares during that process, or > continue to grow new bad blocks. That makes the decision to scrap it > easy. If it successfully maps out the bad blocks and does not appear to > be creating new ones, then using it becomes a judgement call. As they > say, choose wisely. Back in the day (Fixed Direct Access SCSI-2 device) you could use the controller BIOS to do what used to be known as a "low level format" of SCSI drives in order to attempt to squeak a little more life from them. And if new bad spots did not begin to pop again right away you might be good to go for a while. If they did it indicated mass media failure that would just avalanche. The old Adaptec 1540 and 2940 controllers come to mind (Ctrl-A to enter the controller BIOS during POST). Can't do this through a USB subsystem. -Mike From owner-freebsd-questions@freebsd.org Sun Apr 17 17:28:39 2016 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 94D3CB1036E for ; Sun, 17 Apr 2016 17:28:39 +0000 (UTC) (envelope-from emorrasg@yahoo.es) Received: from nm26-vm7.bullet.mail.ir2.yahoo.com (nm26-vm7.bullet.mail.ir2.yahoo.com [212.82.97.49]) (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 EE269130B for ; Sun, 17 Apr 2016 17:28:38 +0000 (UTC) (envelope-from emorrasg@yahoo.es) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.es; s=s2048; t=1460913955; bh=gpM9to/yTkNYO9ZWDBdaQ3i6GgkonFclWOSi/pBod08=; h=Date:From:To:Subject:In-Reply-To:References:From:Subject; b=UvtOp7aGWbLG15/a+QNCipRyG31MvaeoYEbScXmCtqpdMiHOlmqlWDVDqzsUfbRL3ZyhTOoJPwu4CEfT/IN5sqLzm3bpczdogKdXSBQUX5E7ECs+YVYFa+bOdQm3vdP6w4/pCC6odvfMuxxZNYz+/nogLnS9Ew7pn2yc+u/bwsHNXSZ7pkaXVU5dYJKnFq05DDvj27cEEJVWYUljBKdqOIji/P5c3oUzSZJipkxjeTMyR8gbtRGXsM8xjUt7sQTctyW0mgMW8OkD2CHWMu9+vdxmA/Y8SawEzHMBwVuTsrvXM17WQqFW+cAU/BnQhpMMiMpv77CCkaJSxmAxaa1gTA== Received: from [212.82.98.57] by nm26.bullet.mail.ir2.yahoo.com with NNFMP; 17 Apr 2016 17:25:55 -0000 Received: from [46.228.39.84] by tm10.bullet.mail.ir2.yahoo.com with NNFMP; 17 Apr 2016 17:25:55 -0000 Received: from [127.0.0.1] by smtp121.mail.ir2.yahoo.com with NNFMP; 17 Apr 2016 17:25:55 -0000 X-Yahoo-Newman-Id: 89168.40992.bm@smtp121.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 7CZj_I8VM1na21C_YsuyVAOc3Nfy1ctcjxkCyduQKZX8ql3 hy_1cGShRvL3mnL0uPmUVtAGNyx9_501F.MfVVniXCJu.1pI45VNWjxn2Edq _yTg4OrwK8luD2MnLU0GNkHPTWMnVzGrZwwW1h_20lYnlIBgAhQIuokkziDm 1f4B2c3AKWbUl20A2N2W1xUufvFXr09LOvojE1szVaTspR7MS5UY7Nly.p6b tyKCtxsI7dx4.97tqQDndeT1kfHyvHLT6rTweYNMauLjyuejiX5kbl0kSPYV 1C9gBmv.IK_LC3.kEe2TrrI_av5n4Ky4dChN_0l79_wp8SH3p_VW4hKVk2_M 9IAsOsyhFSSOuNtTZN4Kg0FD5Khcr5Kbu70JswPrLN5HhZm5RBKYbsdlUEyL tiQVvJlyogym93uEDBSozPazAOALP2m8luwfTSRYtMXvxwDwtAQN6RBYQrtq WErclaEjyMsUb_Qxk3vyoKYoM9TX6ATdZyCnWdHBUMir5g2ZxiEAT1ZPTfwq OpJ6DTqK3amKeV4Kia7CZ9g-- X-Yahoo-SMTP: mX392iiswBAeJNdO_s.EW62LZDJR Date: Sun, 17 Apr 2016 19:25:57 +0200 From: Eduardo Morras To: freebsd-questions@freebsd.org Subject: Re: rm -rf -Mitigating the dangers Message-Id: <20160417192557.eaa6429c5c00d136b974bbf6@yahoo.es> In-Reply-To: References: X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 17:28:39 -0000 On Sun, 17 Apr 2016 20:10:11 +0300 Odhiambo Washington wrote: > I am wondering if I should place a feature request on this or just do > it my way:) > > With great power comes great responsibility and as such I think there > should be a wrapper around rm to warn sysadmins that what they are > about to do with -rf is dangerous, yes? > > Read input from sysadmin 3 times, looking strictly for their > confirmation before effecting the `rm -rf`. > > Could it be that what I am smoking/drinking is the issue here or I > have your support? LOL Fork rm code, rename one to areyoureallysure that honors -rf and classic rm without -rf. But remember, no risk, no fun. --- --- Eduardo Morras From owner-freebsd-questions@freebsd.org Sun Apr 17 17:36:21 2016 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 257BDB10884 for ; Sun, 17 Apr 2016 17:36:21 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DA9C7182F for ; Sun, 17 Apr 2016 17:36:19 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de (port-92-195-71-243.dynamic.qsc.de [92.195.71.243]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id 2D51A24D92; Sun, 17 Apr 2016 19:36:10 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id u3HHaAjm003505; Sun, 17 Apr 2016 19:36:10 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sun, 17 Apr 2016 19:36:10 +0200 From: Polytropon To: Odhiambo Washington Cc: User Questions Subject: Re: rm -rf -Mitigating the dangers Message-Id: <20160417193610.b5437205.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-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 17:36:21 -0000 On Sun, 17 Apr 2016 20:10:11 +0300, Odhiambo Washington wrote: > With great power comes great responsibility and as such I think there > should be a wrapper around rm to warn sysadmins that what they are about to > do with -rf is dangerous, yes? If you see that the command line contains -f, "force", then you should already know what you're doing, as you're _intendedly_ avoiding any safety belts. A person _responsible_ for a system who starts entering the "rm" command line should know what he's doing, especially when operating in an environment where the command line is being used (instead of a TUI or GUI file manager that makes it less easier to do something stupid). But no matter what you do, there simply is no universal protection against fat fingers, lazy eyes, and tired brain cells. I know what I'm talking about. ;-) > Read input from sysadmin 3 times, looking strictly for their confirmation > before effecting the `rm -rf`. Lazy sysadmins annoyed by this security measure will write a wrapper around it, call it "rm", and make sure the command line arguments are provided three times identically. Problem solved. :-) A nice idea is to use "echo" instead of "rm" first, and check the output, if that is _really_ what you want to delete, and then, and _only then_, replace "echo" with "rm". > Could it be that what I am smoking/drinking is the issue here or I have > your support? LOL Is this because of the recent "rm -rf hoax"? http://serverfault.com/questions/587102/monday-morning-mistake-sudo-rm-rf-no-preserve-root http://meta.serverfault.com/questions/8696/what-to-do-with-the-rm-rf-hoax-question Because people love car analogies... we don't have spikes in the streets infront of traffic lights that empty the tires of a driver who wants to surpass the red light, and forcing him to exchange the tires when he _insists_ on crossing the red light doesn't make the idea any better. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Sun Apr 17 17:40:06 2016 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 149B3B109DD for ; Sun, 17 Apr 2016 17:40:06 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D13A31974 for ; Sun, 17 Apr 2016 17:40:05 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de (port-92-195-71-243.dynamic.qsc.de [92.195.71.243]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id 5589824C05; Sun, 17 Apr 2016 19:40:03 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id u3HHe2Tb003517; Sun, 17 Apr 2016 19:40:02 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sun, 17 Apr 2016 19:40:02 +0200 From: Polytropon To: nightrecon@hotmail.com Cc: freebsd-questions@freebsd.org Subject: Re: tool for mapping away bad blocks on an external disk Message-Id: <20160417194002.11619573.freebsd@edvax.de> In-Reply-To: References: <20160417072641.GA2358@c720-r292778-amd64> <20160417093957.0b1acb4c37d7c15a4b06af88@sohara.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-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 17:40:06 -0000 On Sun, 17 Apr 2016 13:28:03 -0400, Michael Powell wrote: > Back in the day (Fixed Direct Access SCSI-2 device) you could use the > controller BIOS to do what used to be known as a "low level format" of SCSI > drives in order to attempt to squeak a little more life from them. This was also possible with PATA ("IDE") disks and a PC BIOS that had the feature "media analysis" and "low level format". Additionally, when you could locate the position of the damaged blocks, you could "format the disk smaller" by changing some of the CHS values - the disk became smaller, and the defective sectors outside of its new geometry weren't touched anymore. I remember having dealt with a faulty 80 MB disk, reformatted to 40 MB, which didn't show any kind of problems afterwards, for years. This was when hard disks were expensive and low level access was possible. :-) > The old Adaptec 1540 and 2940 controllers come to mind (Ctrl-A to > enter the controller BIOS during POST). Yes, the 2940s had this feature. > Can't do this through a USB subsystem. Result of "making easy things hard, and clever things impossible"... :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Sun Apr 17 17:49:15 2016 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 0CF1BB10D58 for ; Sun, 17 Apr 2016 17:49:15 +0000 (UTC) (envelope-from jpmamu@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id DCB921D1C for ; Sun, 17 Apr 2016 17:49:14 +0000 (UTC) (envelope-from jpmamu@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id D890CB10D55; Sun, 17 Apr 2016 17:49:14 +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 D5F19B10D54 for ; Sun, 17 Apr 2016 17:49:14 +0000 (UTC) (envelope-from jpmamu@gmail.com) Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::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 9F9D91D1B for ; Sun, 17 Apr 2016 17:49:14 +0000 (UTC) (envelope-from jpmamu@gmail.com) Received: by mail-pf0-x236.google.com with SMTP id n1so72883921pfn.2 for ; Sun, 17 Apr 2016 10:49:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:errors-to:list-owner:list-unsubscribe:list-help :precedence:list-id:mime-version:from:to:reply-to:subject; bh=RDq13uQrD+1L4eIcVmJTuCjX8QXI20/C2pu6tSXrecA=; b=ELs1qsZkqdAgW+nEDfTnSTlghnscfueTqbn+1/XhWXaR0mRLbtXGRdDfrjr9FT5iym bLquPiof3rVogmTZ6zW4dMUlunUKBd6O7dtrDZLHjUkNkPJneY1Pity1OYOrTVzkGYwd bVKHQgUKXItA9Yp0ZbupFg1CXhS1rRBkoi9ZG/cMfPP0LhwtgE2FNp+StRhMyZAt3z6z fAmk64mzeakcwwuh2Zk+ulh2hlk8U0Giib2FclkgSSsc0tSjp/GUdrIAiIKPM8gXAvbg MA2hCd+tU+GX1bPR8KCtbmSiGAUInwwoXEB+2MBp2Ck0Zb8YVYm9HQyuvJw9iFx5uGzj ugnQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:errors-to:list-owner :list-unsubscribe:list-help:precedence:list-id:mime-version:from:to :reply-to:subject; bh=RDq13uQrD+1L4eIcVmJTuCjX8QXI20/C2pu6tSXrecA=; b=ir45GIgJ7sz45oHo/8CRekR/6YN3shKu43jRK5KVm26pOT1ja84kiDk6SstgTfDC+w goEQ0BVNj7sPrCF2qWg1VhulFV1PvPwc8T1mw+acbL16FQkeH6J8NW2+ff+mRquTuBpc ZUNGNpCFemFwlSRqJyg+B1k/t26xYE6Lt8ai1cBswrSlXr6WF/SZJZ2N2Vy2y9dJ4Ova DlNozZ1jo+Erta1nYo0KGXWuRCI7jf5Xailbbj0OUp4bI0/p2bT8S05IjVrFFmaXVv0G 2C0cG5SZlOoRCy9szNYb14QiVUpLkQsjR5IK1TQEy/iBJ3U7VO8t5UQ6envnr2rcddy9 OJxQ== X-Gm-Message-State: AOPr4FU4n1QFa95CnvqOSFZfEKSs29g3BiryYUUvcf3LyCZkk9UPmkc3f/FQOUc2sUvHQQ== X-Received: by 10.98.70.27 with SMTP id t27mr43637498pfa.107.1460915353917; Sun, 17 Apr 2016 10:49:13 -0700 (PDT) Received: from PrakashKhanduri ([117.207.223.116]) by smtp.gmail.com with ESMTPSA id q72sm77982943pfa.70.2016.04.17.10.49.11 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 17 Apr 2016 10:49:13 -0700 (PDT) Message-ID: <5713cc99.4b43620a.330c2.50c5@mx.google.com> Date: Sun, 17 Apr 2016 10:49:13 -0700 (PDT) X-Google-Original-Date: 17 Apr 2016 23:19:12 +0530 X-Subscribe-Email: jascowebs@gmail.com X-Abuse-Reports-To: jascowebs@gmail.com Errors-To: jascowebs@gmail.com List-Owner: jascowebs@gmail.com X-Organization: yksvysasxkapq1266 X-Author: yksvysasxkapq1267 Precedence: bulk MIME-Version: 1.0 From: "IMGuru" To: questions@freebsd.org Reply-To: "IMGuru" Subject: AprilDhamalFataafat4U Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 17:49:15 -0000 PGh0bWw+PGJvZHk+PFA+VGhpcyBpcyB0ZXN0IG1haWwgdG8gdmFyaWZ5IHlvdXIgYmxv ZzwvUD4NCjxQPldQRGVhbHM8L1A+DQo8UD4jMjM1ZmF0YWZhdGEkMTAxIzIwMTYqJDEw NTcyPC9QPjwvYm9keT48L2h0bWw+ From owner-freebsd-questions@freebsd.org Sun Apr 17 17:55:14 2016 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 46F12B11068 for ; Sun, 17 Apr 2016 17:55:14 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 18E251132 for ; Sun, 17 Apr 2016 17:55:13 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id u3HHtCOA065635 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 17 Apr 2016 11:55:12 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id u3HHtCWD065632; Sun, 17 Apr 2016 11:55:12 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 17 Apr 2016 11:55:12 -0600 (MDT) From: Warren Block To: Michael Powell cc: freebsd-questions@freebsd.org Subject: Re: tool for mapping away bad blocks on an external disk In-Reply-To: Message-ID: References: <20160417072641.GA2358@c720-r292778-amd64> <20160417093957.0b1acb4c37d7c15a4b06af88@sohara.org> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 17 Apr 2016 11:55:12 -0600 (MDT) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 17:55:14 -0000 On Sun, 17 Apr 2016, Michael Powell wrote: > Back in the day (Fixed Direct Access SCSI-2 device) you could use the > controller BIOS to do what used to be known as a "low level format" of SCSI > drives in order to attempt to squeak a little more life from them. And if > new bad spots did not begin to pop again right away you might be good to go > for a while. If they did it indicated mass media failure that would just > avalanche. The old Adaptec 1540 and 2940 controllers come to mind (Ctrl-A to > enter the controller BIOS during POST). > > Can't do this through a USB subsystem. Or to pretty much any drive any more. They will accept the low-level format command, but return immediately. Or that's what happened the last time I tried it, years ago. It's been a long time since hard drives gave any direct access to the media. Everything goes through the controller on the drive now, which handles all that transparently. So blocks that appeared bad might be already mapped out by the drive. From owner-freebsd-questions@freebsd.org Sun Apr 17 18:13:24 2016 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 90344B11641 for ; Sun, 17 Apr 2016 18:13:24 +0000 (UTC) (envelope-from jhunt@lynden.on.ca) Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::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 57B551A33 for ; Sun, 17 Apr 2016 18:13:24 +0000 (UTC) (envelope-from jhunt@lynden.on.ca) Received: by mail-yw0-x22b.google.com with SMTP id t10so182531645ywa.0 for ; Sun, 17 Apr 2016 11:13:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lynden-on-ca.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=v1Xo1C21At5xfYGnPh2oSU58jGprRq82f1XrEvjODPI=; b=G5a2d1YsRAP/0SlYPgWqX9Xt9xSoX9tEeycl7m+CjypCn6/iYmOteHvXFplX5TIbwN 8brVlB/GTyA6tC7Fq3+9vIQaCklQivWmdmjDZhlwXPxbBOiDPKLqF0HlFJSD+ukFOssr 8wCOBqNvoiCR+wVyKdUzVGZXYYgkvtdGinpCRQmtK3eQuBDVifg+AzDgdlEH4rDMbaig yi0ltpXv6uFOVUyI0sAytAFHuhCKSPMXP01Mq3TNxmQyXMIhg6pXKQGmFB3c3ZtgSmNp HfnRolsCQdEcuC7e+oEBDMhWmBQQWqW1g3cx+hZntFXze0cmGta7uu1lycl6Y16LBa2J bcdg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=v1Xo1C21At5xfYGnPh2oSU58jGprRq82f1XrEvjODPI=; b=VmUHc+gCRbeq1s/IILZ6DyshzX4wiRwJMVkbehy8Uj1YyjsSV6EQ8SZpbX7Zh2GlIm axRnObo3iOJvFn5iFnPkSK4IXwMitkaP2oZ74zVhhNw9oeJs1N0ssK05XzgZKGn7gIdM czOetuHzlI/mNLYOVDvTbOQZkzJ0NhiBdVCM9R+SxgOiRK8QRcSMSj214W6FFBYAYby4 EBsZXZ+vlQfJZuwth/ijlw8VVRCyAT5WCZ+jizmFXkPFsQscmQWJb2QSasd6cUlDXVOJ 4SAbIWTo+Ek/e8LsECL9ulu731LsA3nIZojrUhhnqbRwMIxEGUKfTg748fWMw252CZGL 2JuA== X-Gm-Message-State: AOPr4FUVGb5fAuFAqM9IjNO3pEXbxBpeWaarpNEjkdIcI7f9IJeNWFsee33PcyDPLC/JiCiXwmREzIy6OhvmAA== MIME-Version: 1.0 X-Received: by 10.37.203.2 with SMTP id b2mr6163390ybg.148.1460916803204; Sun, 17 Apr 2016 11:13:23 -0700 (PDT) Received: by 10.83.87.12 with HTTP; Sun, 17 Apr 2016 11:13:23 -0700 (PDT) X-Originating-IP: [173.33.69.78] In-Reply-To: <20160417142231.L1139@sola.nimnet.asn.au> References: <20160416000316.V1139@sola.nimnet.asn.au> <20160415180613.c066affb.freebsd@edvax.de> <20160417142231.L1139@sola.nimnet.asn.au> Date: Sun, 17 Apr 2016 14:13:23 -0400 Message-ID: Subject: Re: Cannot enter sleep mode as non-root user (Operation not permitted) From: Jason Hunt To: Ian Smith Cc: Polytropon , freebsd-questions@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 18:13:24 -0000 On Sun, Apr 17, 2016 at 12:30 AM, Ian Smith wrote: > > I mentioned the suspend button kind-of jokingly, but now I'm curious: > > What make/model of laptop does not have a suspend (aka sleep) button? > > Or is it that yours does not work properly? > It's a Thinkpad x230 and I actually kind of forgot about the "sleep" (quarter moon) icon on the F4 key; sure enough pressing Fn-F4 triggers sleep mode. Although within the last couple days I've discovered and set hw.acpi.lid_switch_state=S3 so now I'm just closing the lid to trigger sleep (which is how I normally configure it on other OS's/DE's, and works for me since I never close the lid unless it's not in use.) On the desktop there's no suspend button so I'm still using the "zzz" shortcut there. Although as I'm writing this I noticed hw.acpi.power_button_state in acpi(4); setting this to S3 on the laptop doesn't work (but I'm not worried about it as I already have three other ways to suspend), but it works perfectly on the desktop (Asus P8B75-M motherboard.) From owner-freebsd-questions@freebsd.org Sun Apr 17 19:03:07 2016 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 2CAAEB12966 for ; Sun, 17 Apr 2016 19:03:07 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.70.90]) by mx1.freebsd.org (Postfix) with ESMTP id 0E0A71F09 for ; Sun, 17 Apr 2016 19:03:06 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id D026DCB8CA6; Sun, 17 Apr 2016 14:02:59 -0500 (CDT) Received: from 76.193.16.109 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Sun, 17 Apr 2016 14:02:59 -0500 (CDT) Message-ID: <61642.76.193.16.109.1460919779.squirrel@cosmo.uchicago.edu> In-Reply-To: References: Date: Sun, 17 Apr 2016 14:02:59 -0500 (CDT) Subject: Re: rm -rf -Mitigating the dangers From: "Valeri Galtsev" To: "Odhiambo Washington" Cc: "User Questions" Reply-To: galtsev@kicp.uchicago.edu User-Agent: SquirrelMail/1.4.8-5.el5.centos.7 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 19:03:07 -0000 On Sun, April 17, 2016 12:10 pm, Odhiambo Washington wrote: > I am wondering if I should place a feature request on this or just do it > my > way:) > > With great power comes great responsibility and as such I think there > should be a wrapper around rm to warn sysadmins that what they are about > to > do with -rf is dangerous, yes? > > Read input from sysadmin 3 times, looking strictly for their confirmation > before effecting the `rm -rf`. This reminds me MS Windows of really old times asking you over and over again: Are you sure?, Are you really-really truly-truly sure? ;-) The great thing is: in FreeBSD those who want this can make it this way for themselves (as it was suggested by others) - without affecting those who don't want it. And as wise person once told: my plan is I have a good backup. Valeri > > Could it be that what I am smoking/drinking is the issue here or I have > your support? LOL > > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft." > _______________________________________________ > 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 Sun Apr 17 19:13:55 2016 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 278A8B12CD2 for ; Sun, 17 Apr 2016 19:13:55 +0000 (UTC) (envelope-from businesswritings@academy.edu.sg) Received: from wp.asm.edu.sg (wp.asm.edu.sg [103.237.168.138]) (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 BD6131434 for ; Sun, 17 Apr 2016 19:13:54 +0000 (UTC) (envelope-from businesswritings@academy.edu.sg) Received: from AVENTISAA-PC (unknown [182.55.215.239]) by wp.asm.edu.sg (Postfix) with ESMTPA id 877F7A9888 for ; Mon, 18 Apr 2016 03:13:51 +0800 (SGT) Reply-To: "Communication Coach, Emma Jones (MBA Imperial College)" From: "Business Writing Essentials" To: "For All Executives and Senior Officers" Subject: 5 Writing Tips that will help you write like a Pro in Just 2 Days. Date: Mon, 18 Apr 2016 03:13:50 +0800 Importance: Normal X-Priority: 3 (Normal) MIME-Version: 1.0 X-Mailer: Mach 5 Mailer version 4 RI{51d25-4a54a} Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 19:13:55 -0000 Essentials of Basic Business Writing workshop Clear and Simple Ways to Strengthen Writing Skills in the Workplace with Native English Speaker and Communications Coach Emma Jarman-Jones Take the fear out of writing professional business documents Writing effectively will allows you to express your ideas and messages clearly, from persuasive memos to complaint letters, sales letters to executive summaries, this workshop will help you develop a higly efficient and effective writing style. With the right training, you can write and engage with confident, clarity and ease. This is a must have, step-by-step guide that helps you overcome writer's block and write clearly and in a professional format, style and tone. Filled with lots of examples, templates and sharing by Communication Coach, Ms Emma Jones, whom will show how to organize messages for maximum impact across your business communication, e-mails, memos, letters and reports Key Takeaways - Over 30 successful runs in Singapore alone This business writing course reviews the correct use of business writing and grammar with a focus on areas where Asian users of English often differ from Standard English. Held over two days, this course will help you Write and design Presentations that move ideas and action Create emails and letters that send across the right message Draft company memos and minutes get things done Create Business Plans and reports which includes accountability and call for actions Professionally crafted sales and marketing letters Script Speeches that carrys across the right points with clarity Who Must Attend? Designed to respond to the growing needs of organisations and their employees, this foundation course is suitable for administrators, executives, senior officers and managers. Those interested to refresh and fine-tune their business writing skills are also most welcome because they will be able to increase their knowledge of the finer points of writing at their workplace. Raving Testimonials "We continue to receive very positive comments about Emma's courses from my staff members. Several people, including our internal communication manager, said that Emma provided the best one-day training courses. Many thanks for providing insights, tips and factoids that will enable our company to write and communicate even better to our bosses and stakeholders." - Cynthia Zhuang, Marketing Manager, NETS Singapore "Great business courses by Emma! I walk away with some great tips and insights which are not just ideas that have no practical consideration. The spirit of spontaneity and engagement is also very encouraging for my learning. Every trainer should be able to keep the attention of the class just like she has." - Jess Tang-Xin, Senior Admin Executive, Singapore Workforce Development Agency I loved Emms presentation style. She shares stories to help everyone relate to the business scenarios that we may encounter at work. She also simplifies concepts for everyone to understand easily. One of the best professional development courses I have been to. I will recommend my colleagues to join me for one of her other upcoming courses.” - Razline Maria, Senior Business Associate, Shangri-la Hotel Singapore Presenting Internationally Renowned Communications Coach: Emma Jarman-Jones (MBA, Imperial College London in UK) Emma Jarman-Jones specialises in developing and enhancing workplace communication skills. This work includes writing, speaking, interpersonal and management skills training. She has over 15 years of experience training in Singapore, as well as regionally in Malaysia, Thailand, Indonesia and Vietnam. Emma has worked as an external consultant and trainer with both private and public sectors, designing, customising and delivering programmes, and coaching individuals. She believes in the potential of every person and is dedicated to providing the highest quality of training that will benefit the individual, as well as the organisation. Emma holds an MBA from the Imperial College London in United Kingdom. She has also completed a Diploma in Human Resource Development at the Singapore Institute of Management, and is a certified People Developer Consultant. Register Now to Avoid Disappointment Date: 12 & 13 May 2016 (Thu & Fri) | 9am - 5pm Venue: 100 Orchard Road, #04-100, Concorde Hotel, Singapore 238840 Course Fees:Only $395.20 (After 60% PIC Grant) Inclusive of buffet lunch and 2 light refreshments To register, you can either register online or download a hardcopy registration form Contact Details: Ms Amelia Lim | amelia@aventisglobal.edu.sg | 6720-3333 | phone Key Topics covered includes 1. Introduction to Business Writing To discuss the importance of writing well; To establish a more systematic approach to writing in order to speed up and increase effectiveness. 2. Grammar Concerns To identify common mistakes (based on their own writing samples); To ensure participants are able to use the different tenses correctly; To understand the differences between Singapore and standard English. 3. Planning and Organising Your Writing To consider the different readers and purposes before beginning to write; To ensure sentences and paragraphs are structured correctly. 4. Style and Tone To write using a reader-friendly tone; To identify and avoid using old-fashioned English; To identify the key elements of Email Etiquette; To practice the key elements covered through a writing task; To edit documents accurately. From owner-freebsd-questions@freebsd.org Sun Apr 17 19:32:48 2016 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 20F98B102F5 for ; Sun, 17 Apr 2016 19:32:48 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AF3141F74 for ; Sun, 17 Apr 2016 19:32:47 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: by mail-wm0-x22c.google.com with SMTP id v188so92952496wme.1 for ; Sun, 17 Apr 2016 12:32:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=s7WYaj2Sl5k8ljvgEa6HW7Ugyf3FKvhnnyfwg5sgkOo=; b=dgPC8X92e+3ctAyx9cMuWq22JlCWrGiykouv6miH21Rqly1xmMiNlh/Q0qctpysuwO tVWDb+hSwPKFsbJRV4MekT0R21fVhrdgxQ4mazWm8wgiWW5O2ak26mILPmfKBAj0n/rF vhb8Vt6Bueg+lDdYc3kDsSWP7fMIPwtAijag3YqEpcDwnpcOlxdKjOzq+CjZx+6xeXY7 ZGlpx6n4rAaOgxAYboarA0o1S0Em6a62aP1iLOgvvA3DhKI+dRgaKVbWvVC88Lk9+5Je Deloe0V4F0OC04kXAkg8tZwd6kRy04lNyohrtuLH+85xOIrBFl2fn8BzSVbw1SC3h5X1 vG/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=s7WYaj2Sl5k8ljvgEa6HW7Ugyf3FKvhnnyfwg5sgkOo=; b=EU7mhVLzU+qKYYlL8/aD8gk2XirH4RdyVYiTB0iPa5ZXqPWmNUP2+v73tF3aZYRBhB 8K9KfL4V9mSmLoO7r/+PSNchEATEi9c5gna1z7TUdgspp7lYQgyd2maMguEXpaRcUEWB xsZz6j48kLe2FeLq9DWxk31j+cdzuBP4QbnihLRT+NsjtHPAOuCZ7WF2h/RKXd5KL4G+ pEpi0YapxJQysjxMiDjP9y32SBYhw/yftWbcXb4u39YO+csxdY39+ohPWlinHiFi59aQ SyAEoyQP74fJ3yEc9RdXyFBePyr6nEC1oiWKMWuIjcA4qV9nkAO2Ds+ignTT1uyY1iFH EZQw== X-Gm-Message-State: AOPr4FXRbVn+xySKnpUdEJl+y2u/Z7QiZyQxiPKTif5tyLIWQiPZdepfHQXtEO8j3JVZads/a7XDcbe6v/hbtg== X-Received: by 10.194.61.19 with SMTP id l19mr14686wjr.4.1460921566362; Sun, 17 Apr 2016 12:32:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.103.233 with HTTP; Sun, 17 Apr 2016 12:32:06 -0700 (PDT) In-Reply-To: <20160417193610.b5437205.freebsd@edvax.de> References: <20160417193610.b5437205.freebsd@edvax.de> From: Odhiambo Washington Date: Sun, 17 Apr 2016 22:32:06 +0300 Message-ID: Subject: Re: rm -rf -Mitigating the dangers To: Polytropon Cc: User Questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 19:32:48 -0000 On 17 April 2016 at 20:36, Polytropon wrote: > On Sun, 17 Apr 2016 20:10:11 +0300, Odhiambo Washington wrote: > > With great power comes great responsibility and as such I think there > > should be a wrapper around rm to warn sysadmins that what they are about > to > > do with -rf is dangerous, yes? > > If you see that the command line contains -f, "force", then you > should already know what you're doing, as you're _intendedly_ > avoiding any safety belts. A person _responsible_ for a system > who starts entering the "rm" command line should know what he's > doing, especially when operating in an environment where the > command line is being used (instead of a TUI or GUI file manager > that makes it less easier to do something stupid). > > But no matter what you do, there simply is no universal protection > against fat fingers, lazy eyes, and tired brain cells. I know what > I'm talking about. ;-) > > > > > Read input from sysadmin 3 times, looking strictly for their confirmation > > before effecting the `rm -rf`. > > Lazy sysadmins annoyed by this security measure will write a > wrapper around it, call it "rm", and make sure the command line > arguments are provided three times identically. Problem solved. :-) > > A nice idea is to use "echo" instead of "rm" first, and check the > output, if that is _really_ what you want to delete, and then, > and _only then_, replace "echo" with "rm". > > > > > Could it be that what I am smoking/drinking is the issue here or I have > > your support? LOL > > Is this because of the recent "rm -rf hoax"? > > > http://serverfault.com/questions/587102/monday-morning-mistake-sudo-rm-rf-no-preserve-root > > > http://meta.serverfault.com/questions/8696/what-to-do-with-the-rm-rf-hoax-question > > Because people love car analogies... we don't have spikes in the > streets infront of traffic lights that empty the tires of a driver > who wants to surpass the red light, and forcing him to exchange > the tires when he _insists_ on crossing the red light doesn't make > the idea any better. :-) > > I love your radical views, ever since:-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft." From owner-freebsd-questions@freebsd.org Sun Apr 17 20:02:08 2016 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 A187FB10D7E for ; Sun, 17 Apr 2016 20:02:08 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6714E1BF9 for ; Sun, 17 Apr 2016 20:02:08 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1arstR-0007Sm-1M for freebsd-questions@freebsd.org; Sun, 17 Apr 2016 22:02:05 +0200 Received: from pool-72-66-1-32.washdc.fios.verizon.net ([72.66.1.32]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 17 Apr 2016 22:02:05 +0200 Received: from nightrecon by pool-72-66-1-32.washdc.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 17 Apr 2016 22:02:05 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Michael Powell Subject: Re: tool for mapping away bad blocks on an external disk Date: Sun, 17 Apr 2016 16:03:03 -0400 Lines: 47 Message-ID: References: <20160417072641.GA2358@c720-r292778-amd64> <20160417093957.0b1acb4c37d7c15a4b06af88@sohara.org> Reply-To: nightrecon@hotmail.com Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pool-72-66-1-32.washdc.fios.verizon.net X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 20:02:08 -0000 Warren Block wrote: > On Sun, 17 Apr 2016, Michael Powell wrote: > >> Back in the day (Fixed Direct Access SCSI-2 device) you could use the >> controller BIOS to do what used to be known as a "low level format" of >> SCSI drives in order to attempt to squeak a little more life from them. >> And if new bad spots did not begin to pop again right away you might be >> good to go for a while. If they did it indicated mass media failure that >> would just avalanche. The old Adaptec 1540 and 2940 controllers come to >> mind (Ctrl-A to enter the controller BIOS during POST). >> >> Can't do this through a USB subsystem. > > Or to pretty much any drive any more. They will accept the low-level > format command, but return immediately. Or that's what happened the > last time I tried it, years ago. Most of the time when low-level format was discussed wrt to IDE drives it was fake. All it really did was fill the drive with zeros. It is possible to low-level an IDE, but generally the manufacturers would not release the ability to the public. They could low-level a drive but they didn't want end users doing it; they would rather sell you another drive. A true low-level regenerates the remap zone in tandem. It isn't that it isn't possible, per se, but that's it's so dangerous to actually try it with an IDE drive the mfr does not want the end user to be able to even try. Hence the 'fake' write zeros to all media and call it "low-level" as a marketing gimmick. When you low-level a SCSI drive it's the real thing. > It's been a long time since hard drives gave any direct access to the > media. Everything goes through the controller on the drive now, which > handles all that transparently. So blocks that appeared bad might be > already mapped out by the drive. In IDE the remap zone is finite. As long as it's not full the end user won't see errors as the drive is handling this behind the scene. Once the remap zone becomes full, then the errors have no place to remap to, and you begin to see the dead sectors. Low-leveling a SCSI drive wiped everything and reinitialized the bad sector table to reflect the current status, which could be repeated. To do this with an IDE drive it really can only be done by the manufacturer, and they won't. It's "buy a new drive time." -Mike From owner-freebsd-questions@freebsd.org Sun Apr 17 22:33:37 2016 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 7EF3AB11256 for ; Sun, 17 Apr 2016 22:33:37 +0000 (UTC) (envelope-from dpchrist@holgerdanske.com) Received: from holgerdanske.com (holgerdanske.com [184.105.128.27]) by mx1.freebsd.org (Postfix) with SMTP id 637D41FEC for ; Sun, 17 Apr 2016 22:33:37 +0000 (UTC) (envelope-from dpchrist@holgerdanske.com) Received: from ::ffff:99.100.19.101 ([99.100.19.101]) by holgerdanske.com for ; Sun, 17 Apr 2016 15:30:51 -0700 Subject: Re: rm -rf -Mitigating the dangers To: freebsd-questions@freebsd.org References: From: David Christensen Message-ID: <57140EA2.6020503@holgerdanske.com> Date: Sun, 17 Apr 2016 15:30:58 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 22:33:37 -0000 On 04/17/2016 10:10 AM, Odhiambo Washington wrote: > I am wondering if I should place a feature request on this or just do it my > way:) > > With great power comes great responsibility and as such I think there > should be a wrapper around rm to warn sysadmins that what they are about to > do with -rf is dangerous, yes? > > Read input from sysadmin 3 times, looking strictly for their confirmation > before effecting the `rm -rf`. > > Could it be that what I am smoking/drinking is the issue here or I have > your support? LOL I have this in my .bashrc: alias rm='rm -i --one-file-system' So, an accidental 'rm -rf' should limit destruction to one file system. Perhaps what you're looking for is a command-line equivalent of desktop trash cans. STFW this is not a new idea and there are existing solutions. David From owner-freebsd-questions@freebsd.org Sun Apr 17 23:00:08 2016 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 5BC38B119A9 for ; Sun, 17 Apr 2016 23:00:08 +0000 (UTC) (envelope-from milios@ccsys.com) Received: from cargobay.net (cargobay.net [198.178.123.147]) (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 3BF251AE2 for ; Sun, 17 Apr 2016 23:00:07 +0000 (UTC) (envelope-from milios@ccsys.com) Received: from [10.58.132.62] (mobile-166-172-120-117.mycingular.net [166.172.120.117]) by cargobay.net (Postfix) with ESMTPSA id B4D2A1DA; Sun, 17 Apr 2016 22:48:26 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: rm -rf -Mitigating the dangers From: Jake X-Mailer: iPhone Mail (13E238) In-Reply-To: <57140EA2.6020503@holgerdanske.com> Date: Sun, 17 Apr 2016 18:53:57 -0400 Cc: freebsd-questions@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <6743C8AB-D9FA-44C5-826F-1D7C094A9DBE@ccsys.com> References: <57140EA2.6020503@holgerdanske.com> To: David Christensen X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 23:00:08 -0000 > On Apr 17, 2016, at 6:30 PM, David Christensen = wrote: >=20 >> On 04/17/2016 10:10 AM, Odhiambo Washington wrote: >> I am wondering if I should place a feature request on this or just do it m= y >> way:) >>=20 >> With great power comes great responsibility and as such I think there >> should be a wrapper around rm to warn sysadmins that what they are about t= o >> do with -rf is dangerous, yes? >>=20 >> Read input from sysadmin 3 times, looking strictly for their confirmation= >> before effecting the `rm -rf`. >>=20 >> Could it be that what I am smoking/drinking is the issue here or I have >> your support? LOL >=20 > I have this in my .bashrc: >=20 > alias rm=3D'rm -i --one-file-system' >=20 > So, an accidental 'rm -rf' should limit destruction to one file system. >=20 >=20 > Perhaps what you're looking for is a command-line equivalent of desktop tr= ash cans. STFW this is not a new idea and there are existing solutions. >=20 >=20 > David I for one cherish my God given constitutionally protected right to blast my d= arned foot clear off my bloody leg with one twitch of a hair trigger. :) A wrapper would be problematic. Too many scripts rely on rm doing what it's m= eant to do. Even testing for a tty on stdin or stdout cannot offer any strai= ghtforward way to guarantee adherence to expected behavior in times it's nec= essary. Perhaps a wrapper that simply sleeps for a few seconds first is viab= le but more complex logic would be necessary to avoid a horrific slowdown wh= en used within some sort of loop. An alias or function which is only sourced by your shell when entering inter= active mode would indeed be a good spot to place the proposed hypothetical s= olution.= From owner-freebsd-questions@freebsd.org Mon Apr 18 04:51:04 2016 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 2CF68B11571 for ; Mon, 18 Apr 2016 04:51:04 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F02ED134E for ; Mon, 18 Apr 2016 04:51:03 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id u3I4p2Pn032703 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 17 Apr 2016 22:51:02 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id u3I4p2vJ032700; Sun, 17 Apr 2016 22:51:02 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 17 Apr 2016 22:51:02 -0600 (MDT) From: Warren Block To: "Kevin P. Neal" cc: freebsd-questions@freebsd.org Subject: Re: rm -rf -Mitigating the dangers In-Reply-To: <20160418001110.GA82868@neutralgood.org> Message-ID: References: <57140EA2.6020503@holgerdanske.com> <20160418001110.GA82868@neutralgood.org> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 17 Apr 2016 22:51:02 -0600 (MDT) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 04:51:04 -0000 On Sun, 17 Apr 2016, Kevin P. Neal wrote: > On Sun, Apr 17, 2016 at 03:30:58PM -0700, David Christensen wrote: >> On 04/17/2016 10:10 AM, Odhiambo Washington wrote: >>> I am wondering if I should place a feature request on this or just do it my >>> way:) >>> >>> With great power comes great responsibility and as such I think there >>> should be a wrapper around rm to warn sysadmins that what they are about to >>> do with -rf is dangerous, yes? >>> >>> Read input from sysadmin 3 times, looking strictly for their confirmation >>> before effecting the `rm -rf`. >>> >>> Could it be that what I am smoking/drinking is the issue here or I have >>> your support? LOL >> >> I have this in my .bashrc: >> >> alias rm='rm -i --one-file-system' >> >> So, an accidental 'rm -rf' should limit destruction to one file system. > > And, for those occasions where your job is on the line, it is important > to know that "pwd" and "/bin/pwd" do _not_ work the same. If you really > want to know where you are before you do a "rm -rf *" then you must use > the "/bin/pwd" command. I suggest to never give rm -rf an unqualified "*". Using a path with rm -rf doesn't make it safe, but it does make it safer. It's a good protective habit to develop. From owner-freebsd-questions@freebsd.org Mon Apr 18 06:55:44 2016 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 E18C3B124DA for ; Mon, 18 Apr 2016 06:55:44 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A54761A45 for ; Mon, 18 Apr 2016 06:55:44 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [89.15.236.164] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1as35w-00006I-7Q for freebsd-questions@freebsd.org; Mon, 18 Apr 2016 08:55:40 +0200 Received: from localhost.my.domain (c720-r292778-amd64 [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id u3I6taL6002232 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 18 Apr 2016 08:55:36 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id u3I6tZRb002231 for freebsd-questions@freebsd.org; Mon, 18 Apr 2016 08:55:35 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Mon, 18 Apr 2016 08:55:34 +0200 From: Matthias Apitz To: freebsd-questions@freebsd.org Subject: Re: tool for mapping away bad blocks on an external disk Message-ID: <20160418065534.GA2198@c720-r292778-amd64> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , freebsd-questions@freebsd.org References: <20160417072641.GA2358@c720-r292778-amd64> <20160417093957.0b1acb4c37d7c15a4b06af88@sohara.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT r292778 (amd64) User-Agent: Mutt/1.5.24 (2015-08-30) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 89.15.236.164 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 06:55:45 -0000 Thanks for all the hints; I started last night with overwriting the full disk with: # dd conv=noerror if=/dev/zero of=/dev/da0 bs=1m after 12 hours it has already done 2/3 of it: full disk: 2930277168 * 512 = 1.500.301.910.016 bytes to write 06:30: 1.028.246.208.512 bytes done (980.612 blocks of 1M) When after the procedure the problems remain, the disk will go to the dustbin; matthias -- Matthias Apitz, ✉ guru@unixarea.de, ⌂ http://www.unixarea.de/ ☎ +49-176-38902045 ¡Dios querido denos otra vez los problemas de ayer, los que tuvimos en la RDA! My Lord, give us back the problems of yesterday, those we have had in the GDR. From owner-freebsd-questions@freebsd.org Mon Apr 18 08:10:05 2016 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 A7403B1178F for ; Mon, 18 Apr 2016 08:10:05 +0000 (UTC) (envelope-from allan.kapoma@zamnet.zm) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 8B9B0188D for ; Mon, 18 Apr 2016 08:10:05 +0000 (UTC) (envelope-from allan.kapoma@zamnet.zm) Received: by mailman.ysv.freebsd.org (Postfix) id 8AE40B1178E; Mon, 18 Apr 2016 08:10:05 +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 8A7B2B1178D for ; Mon, 18 Apr 2016 08:10:05 +0000 (UTC) (envelope-from allan.kapoma@zamnet.zm) Received: from bsf-o-2.zamnet.zm (bsf-o-2.zamnet.zm [196.46.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id D0E25188C for ; Mon, 18 Apr 2016 08:10:04 +0000 (UTC) (envelope-from allan.kapoma@zamnet.zm) X-ASG-Debug-ID: 1460966994-054b875ac01b550001-YuSLm7 Received: from smtp.zamnet.zm (smtp.zamnet.zm [196.46.192.20]) by bsf-o-2.zamnet.zm with ESMTP id K3Bpf4lj5IiXFENH for ; Mon, 18 Apr 2016 10:09:54 +0200 (CAT) X-Barracuda-Envelope-From: allan.kapoma@zamnet.zm X-Barracuda-Apparent-Source-IP: 196.46.192.20 Received: from allan (pc5-lk.zamnet.zm [196.46.212.69]) by smtp.zamnet.zm (Rockliffe SMTPRA 9.4.1) with ESMTP id ; Mon, 18 Apr 2016 10:09:56 +0200 From: "Allan Kapoma" To: "'Erich Dollansky'" Cc: , "'Nalumino Moola'" References: <003401d196ee$258ee680$70acb380$@zamnet.zm> <20160416094349.77f6a883@X220.alogt.com> In-Reply-To: <20160416094349.77f6a883@X220.alogt.com> Subject: RE: Upgrading from FreeBSD 4.1 Date: Mon, 18 Apr 2016 10:09:42 +0200 X-ASG-Orig-Subj: RE: Upgrading from FreeBSD 4.1 Message-ID: <00bf01d19949$a9c69080$fd53b180$@zamnet.zm> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQF+Uj+tw+qXgStbtLO+Zz8AExV1BQEOt2vRoC14OIA= Content-Language: en-gb X-Barracuda-Connect: smtp.zamnet.zm[196.46.192.20] X-Barracuda-Start-Time: 1460966994 X-Barracuda-URL: http://196.46.192.45:8000/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at zamnet.zm X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.23 X-Barracuda-Spam-Status: No, SCORE=0.23 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=5.0 tests=BSF_SC0_MISMATCH_TO, SH_BIG5_05413_BODY_104, THREAD_INDEX X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.28837 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.01 THREAD_INDEX thread-index: AcO7Y8iR61tzADqsRmmc5wNiFHEOig== 0.00 BSF_SC0_MISMATCH_TO Envelope rcpt doesn't match header 0.21 SH_BIG5_05413_BODY_104 BODY: Body: contain "UNSUBSCRIBE" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 08:10:05 -0000 Hello Erich What command(s) did you used to move from version 4 to 5.21 Regards Allan Kapoma|Head of Networks| ZAMNET Communication Systems Limited | Mobile: +260 962 235839 | Office: +260 211 220736| Fax: +260 211 224775 = | COMESA =A0Center | Ben Bella Road | P.O Box 38299=A0=A0 | Lusaka, 10101 = ZAMBIA |Email: allan.kapoma@zamnet.zm=A0| Website:=A0 www.zamnet.zm. Nobody Delivers IT Better -----Original Message----- From: Erich Dollansky [mailto:erichsfreebsdlist@alogt.com]=20 Sent: 16 April 2016 03:44 To: Allan Kapoma Cc: questions@freebsd.org; 'Nalumino Moola' Subject: Re: Upgrading from FreeBSD 4.1 Hi, On Fri, 15 Apr 2016 10:09:34 +0200 "Allan Kapoma" wrote: > I'm running FreeBSD 4.10 and I want to upgrade the system to a later=20 > version of FreeBSD. >=20 this is from 2004 and still running. I wonder if you can even update to = the latest version. I have had a notebook, I never brought to 8 as its = hardware was not supported from 8 onward. If you really want to update, use sources to move from version to = version. I would move to 5.21 first and the 6.0, 7.0 ... It will not be possible to compile new versions with the old compiler = you have. The binary upgrade came later. When you have reached that version, you = can go via binary upgrades. Of course, you can have a try and move directly to the oldest version supporting binary upgrades. I only doubt that your old compiler will = support this. Good luck. Erich > =20 >=20 > However, whenever I run commands to update the system (#=20 > freebsd-update), or install portsnap, or install portmanager, or pkg=20 > commands, portsnap fetch extract, I'm getting the message that command = > not found >=20 > =20 >=20 > The my output for uname -a is shown below >=20 > =20 >=20 > relay# uname -a >=20 > FreeBSD relay.zamnet.zm 4.10-RELEASE FreeBSD 4.10-RELEASE #1: Fri Nov > 12 06:54:4 =20 >=20 > =20 >=20 > I'm asking for assistance on how I can enable the system (FreeBSD > 4.10) to run these commands and hopefully update my system and=20 > packages on it >=20 > =20 >=20 > Regards >=20 > =20 >=20 > Allan Kapoma|Head of Networks| ZAMNET Communication Systems Limited | >=20 > Mobile: +260 962 235839 | Office: +260 211 220736| Fax: +260 211 > 224775 | >=20 > COMESA Center | Ben Bella Road | P.O Box 38299 | Lusaka, 10101 > ZAMBIA |Email: allan.kapoma@zamnet.zm = > | Website: www.zamnet.zm. >=20 >=20 >=20 > Nobody Delivers IT Better >=20 > =20 >=20 > =20 >=20 > _______________________________________________ > freebsd-questions@freebsd.org mailing list=20 > 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 Apr 18 08:20:16 2016 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 C1DFFB11B53 for ; Mon, 18 Apr 2016 08:20:16 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5BF921D56 for ; Mon, 18 Apr 2016 08:20:16 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: by mail-wm0-x235.google.com with SMTP id n3so112214629wmn.0 for ; Mon, 18 Apr 2016 01:20:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=sFbT2aJs0jazVDJIwFfLgZUCN3YhrmgkxQW40d5X640=; b=YNUQ72yLIgbLPnpPrrWgHYWr4CM1SsQjEt+ku+PAtXHxDy30LlV/hSScnTG4SgSklL Z5L5oEiXGeOlcl3pn9BX/Mg6rna+MkoGq98mcLtVFixAKQoo1lV72WXWTqbFb+IVQ9KZ 1GPoEUoetSmKdLlqZQocXGk78IdAsMwGTwWavHTP8bJX0NvLa6ACHc2kKj1kqpbtaTqu qwVyaQqPfcmgTJLpmNuTxrLqwcTwMUxY2uNotjKIbb0yTEKVVY0XNFoMpYhMDBJbdtuB A7cTBcvBXMbnUGRajPBEfnm0UbMyxeiAn3/N8STzPWJ9hvkg6VQA9ZraKWdsbgyUAcHj zMPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=sFbT2aJs0jazVDJIwFfLgZUCN3YhrmgkxQW40d5X640=; b=VtltXd2gHNPWquMu8eETmxVCBJo3nED8MikDQkHMbQ3bC5sv0Kj2s0AH+XKztYoCV1 X/TBrv6Mh/5rOXNckwm6GEFZMDpVq1DV8rgBOlyC3xXBDfTZteG7u28oo8iy6qa8TLSQ KkYyoq4a4POistL1jWTh/sOmnHQENRWl5+l5v7UpmLKI2+jcAFUyoKjc25OLfEZmMQ09 6PK1CikWFAKUxVh/yHTWQh7BpasJFfBE7UnpYw6j29t7yo61/5ESpAp1vOKVP3WY3ZvM ezlDPOuwiTW2A716hVQOpRxXguTo6gGwBnabLDA9gBqDVQVrr9/i6csNiimBu968Pi6b 896A== X-Gm-Message-State: AOPr4FXkFHaLgbGzbni2E+wuHa2i50lvWQIq09NbsrHX0nX7nVaT8ZFSR9MTXmsszSPEFLsaXgKZKXUoIf+cIA== MIME-Version: 1.0 X-Received: by 10.194.175.168 with SMTP id cb8mr34684068wjc.56.1460967614986; Mon, 18 Apr 2016 01:20:14 -0700 (PDT) Received: by 10.28.46.67 with HTTP; Mon, 18 Apr 2016 01:20:14 -0700 (PDT) In-Reply-To: References: Date: Mon, 18 Apr 2016 09:20:14 +0100 Message-ID: Subject: Re: Convert ipfw rule to pf From: krad To: Matthias Fechner 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.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 08:20:16 -0000 you need the relevant pass rules as well as the rdrs On 17 April 2016 at 10:22, Matthias Fechner wrote: > Dear all, > > I use sslh to have a transparent proxy for ssh/https in place. > The transparent proxy support of sslh requires ipfw rules to work. > > I'm not sure if sslh is doing something in the background and that is the > reason why it is not working with pf. > > Maybe we have here a pf guru on the list that can ensure the the rule > itself is correct. > > The ipfw rule looks like: > # https > ipfw add 20000 fwd 192.168.0.251,443 log tcp from 192.168.0.251 8443 to > any out > ipfw add 20001 fwd 192.168.200.6,443 log tcp from 192.168.200.6 8443 to > any out > # ssh > ipfw add 20003 fwd 192.168.200.6,443 log tcp from 192.168.200.6 22 to any > out > > In pf they look like: > rdr pass log inet proto tcp from 192.168.0.251 port 8443 to any -> > 192.168.0.251 port 443 > rdr pass log inet proto tcp from 192.168.200.6 port 8443 to any -> > 192.168.200.6 port 443 > rdr pass log inet proto tcp from 192.168.200.6 port 22 to any -> > 192.168.200.6 port 443 > > Thanks. > > Gru=C3=9F > Matthias > > -- > > "Programming today is a race between software engineers striving to > build bigger and better idiot-proof programs, and the universe trying to > produce bigger and better idiots. So far, the universe is winning." -- > Rich Cook > _______________________________________________ > 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 Apr 18 08:22:53 2016 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 3F240B11D95 for ; Mon, 18 Apr 2016 08:22:53 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 201D21057 for ; Mon, 18 Apr 2016 08:22:53 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 1F6EBB11D92; Mon, 18 Apr 2016 08:22:53 +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 1F10BB11D91 for ; Mon, 18 Apr 2016 08:22:53 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::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 AD4921053 for ; Mon, 18 Apr 2016 08:22:52 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: by mail-wm0-x234.google.com with SMTP id u206so111869062wme.1 for ; Mon, 18 Apr 2016 01:22:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=Tqjc4/O0+z2ERaPGSVyX9/OUcX2hhXX5DszGKxB92js=; b=pANJzf7dJu/Ql86qcPNaN7FhaU5oaO+57FLS93AeLp0TkPKgIN5BLDMRde4ZfUeMIb 35zvqZsRKI5iZaCs+rqrhM+RXEmvPicfHa55KSAjFighflghYylQabaFW8HwwFs2PO8s KC/pCnOSUgMOevKIdS3TOFchnCpEUUNsjs9UhnxOmz8Ngcx2FrLDSFtKKO40qbVyqNSM XTnJ7peSe+kxFNiuQA7hJHh89lVM4nIgZ4p5T2y+AYWH+OB8nL4RZ6v168UJmdQtkAuS LxmoxooFZ/vJX6Cb3SuFzzauvB4i5ggcE125eWgV3i8/sQ1eGv6fx/Hu0I1h8vaaeUXr joEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=Tqjc4/O0+z2ERaPGSVyX9/OUcX2hhXX5DszGKxB92js=; b=PaFNs0RHmb/Whh0r5eVtf+tTg7pqDivhTrBhTssijP1wAoeZUqQmzQa83rpsbxV8EH pzJSd6tZoj+f1jDCco3o0SiaOBPaxnCnAJlnHMykkfDAQXfHZ6l8lNuu4jED0Gc8FINI /UhwCDrEeQDT3vNggP5L4fIds3aWEWWp4ngE84eBqdN1F27dNaFRpRVEaK8afSko+Hxj tMa+sVCheiJ+cq3EEzub4ihsfvUv46JqZfX3YdwNsE82dvF46Wpd14VX7yWIqQ8sLxMm vnAY0OEaKbnRfBRGDMzAD5UDjYcChNX43p0cYyItLidHK1S5IxAfKoH77gOZ0VGJFqeX B9bQ== X-Gm-Message-State: AOPr4FVsa120rNQPYWy9nQMhQz+rpebMt4Tt+Gy8pXpVOLB0kh14SVFuyzhGe6xwhG6jvOJI9WDqMFhPp7GBLw== MIME-Version: 1.0 X-Received: by 10.194.83.42 with SMTP id n10mr34831333wjy.20.1460967771339; Mon, 18 Apr 2016 01:22:51 -0700 (PDT) Received: by 10.28.46.67 with HTTP; Mon, 18 Apr 2016 01:22:51 -0700 (PDT) In-Reply-To: References: Date: Mon, 18 Apr 2016 09:22:51 +0100 Message-ID: Subject: Re: Upgrading FreeBSD 4.10 From: krad To: Allan Kapoma Cc: questions@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 08:22:53 -0000 4->5 was a big jump as loads of stuff in RC changed IIRC, and from there to 10 or even 8 is a big jump. You would be far better placed to build a brand new machine based on your selected version of freebsd (probably 10.3), and then port your applications one by one On 15 April 2016 at 11:11, Allan Kapoma wrote: > Hello > > > > I=E2=80=99m running FreeBSD 4.10 and I want to upgrade the system to a la= ter > version of FreeBSD. > > > > However, whenever I run commands to update the system (# freebsd-update), > or install portsnap, or install portmanager, or pkg commands, or portsnap > fetch extract, I=E2=80=99m getting the message that command not found > > > > The my output for uname =E2=80=93a is shown below > > > > relay# uname -a > > FreeBSD relay.zamnet.zm 4.10-RELEASE FreeBSD 4.10-RELEASE #1: Fri Nov 12 > 06:54:4 > > > > I=E2=80=99m asking for assistance on how I can enable the system (FreeBSD= 4.10) to > run these commands and hopefully update my system and packages on it > > > > Regards > _______________________________________________ > 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 Apr 18 13:30:15 2016 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 9A10CB13CA9 for ; Mon, 18 Apr 2016 13:30:15 +0000 (UTC) (envelope-from feenberg@nber.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 84829170E for ; Mon, 18 Apr 2016 13:30:15 +0000 (UTC) (envelope-from feenberg@nber.org) Received: by mailman.ysv.freebsd.org (Postfix) id 7FCDCB13CA8; Mon, 18 Apr 2016 13:30:15 +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 7F5F9B13CA7 for ; Mon, 18 Apr 2016 13:30:15 +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 312DE170D for ; Mon, 18 Apr 2016 13:30:14 +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.14.9) with ESMTPS id u3IDGLLt072730 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 18 Apr 2016 09:16:21 -0400 (EDT) (envelope-from feenberg@nber.org) Date: Mon, 18 Apr 2016 09:16:21 -0400 (EDT) From: Daniel Feenberg To: Wayne Sierke cc: krad , Olivier Nicole , questions@freebsd.org Subject: Re: [Phishing]Re: Anti-virus for FreeBSD In-Reply-To: <1458712914.1578.37.camel@au.dyndns.ws> Message-ID: References: <1458712914.1578.37.camel@au.dyndns.ws> User-Agent: Alpine 2.20 (LRH 67 2015-01-07) 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, 2016/04/15 08:21:31 X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.721, bases: 2016/04/17 23:27:00 #7565430 X-KLMS-AntiVirus-Status: Clean, skipped Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 13:30:15 -0000 A late follow-up to the question of Windows anti-virus running on FreeBSD I wrote to my vendor, who obtained this from Kaspersky in Russia. Reading between the lines, it is possible that support may cease, but there are no such plans. I have been unable to locate anything that can detect executable docx or pdf. dan feenberg =============================================================================== On 4/8/16, 9:04 AM, "Julian Garcia" wrote: >Hi Stefan, > >I heard back from HQ. > >FreeBSD support and development will continue; with FreeBSD is supported >in KLMS up to version 10.1 (32\64) with Version 10.2 (86 / 64) support >scheduled in MP2 for this autumn. > > >Thank you. > >Regards, >Julian > > > > >Julian Garcia | Pre-Sales Engineer | >www.kaspersky.com | www.threatpost.com | www.securelist.com | > From owner-freebsd-questions@freebsd.org Mon Apr 18 14:00:54 2016 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 7B92CB11FFF for ; Mon, 18 Apr 2016 14:00:54 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5E50818F2 for ; Mon, 18 Apr 2016 14:00:54 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 5DBDBB11FF3; Mon, 18 Apr 2016 14:00:54 +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 5D4BDB11FEE; Mon, 18 Apr 2016 14:00:54 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-ig0-x244.google.com (mail-ig0-x244.google.com [IPv6:2607:f8b0:4001:c05::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 29F2218F1; Mon, 18 Apr 2016 14:00:54 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-ig0-x244.google.com with SMTP id fn8so11012245igb.2; Mon, 18 Apr 2016 07:00:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-transfer-encoding; bh=9pugJovbhlrI3aewCAYmKEhvwvYgI0gCxjd7UsYC1Rc=; b=q7Dc7JnCVf8dhNXGm2KCnJ2C/01glqm5BUJS994bZQro4dR7vobgl6rUv3TZiwwDgx lhwmOoZaLnzmsvacc9HOMkEBCrCnHpEuNvRqFKvAm+DhgtkgYRdr8we6+cl2psMVcwRj mrCK1FgO381nmLl5xMYRd2v/pxgz/4LDSsQezWJ0a+RGW+G+O8kYDj7w2aGfZ8NyUdhS lBT/evaMau4D9ZujEM3wCJlQPdZ8xEqWhAigU0WxFptVGFswqdu6Qpn68gOGu5Wre9Jf lcx1zL527Xd7p2F2mdbWraNkUHrBYQEIFGF0LiUkt44LttM2Jq8wOjgNLa6/tREgVTZI ahgQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:content-transfer-encoding; bh=9pugJovbhlrI3aewCAYmKEhvwvYgI0gCxjd7UsYC1Rc=; b=dkKOQ4jkCUxJsMU38TfRy/cjsbGHaNm5eID40UJINI1g33M2vhIn9teicGVRhyN6L6 +szBN9LKDom6EfkwaivfujLWt6VxWDkIjkEIVd7JsFqdp1CATx7SMzC9ZMAg3zpmjGQ+ T6+nS8qCBdwSPPb6/k/dhP8zsCQjPu9/mHRjYo7ewbUAWG1H9Szdy3EJwDJpXDnKhiRJ VZnSy4HmzeApvUhomLczKLVVaBaflm/g+M1sUNiToe5JGMEVmLh9HQ0O3kum4tS7n1SY pEsIABwmpcXfzttWcM58Fdj+g57LHvvp/i2L67q5yOntxiysEj9lRymGo/XntX2Z/q6T Dxfg== X-Gm-Message-State: AOPr4FWiiayceyq+ga5ycv08HoG2jz2rNDjsmjHok5Tma6e+tHZHJmT05C9iwvEW7h7R3g== X-Received: by 10.50.118.225 with SMTP id kp1mr20283406igb.9.1460988052634; Mon, 18 Apr 2016 07:00:52 -0700 (PDT) Received: from [10.0.10.3] (cpe-76-190-244-6.neo.res.rr.com. [76.190.244.6]) by smtp.googlemail.com with ESMTPSA id s8sm38024167iod.40.2016.04.18.07.00.51 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 18 Apr 2016 07:00:51 -0700 (PDT) Message-ID: <5714E89A.8000807@gmail.com> Date: Mon, 18 Apr 2016 10:00:58 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: questions@freebsd.org, freebsd-current@freebsd.org Subject: 11.0-RELEASE pkg base & base.txz file Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 14:00:54 -0000 11.0 will have pkg base, thats ok, but what does than mean for the base.txz file? It it going to stay as part of FBSD install? I have many scripts for creating jails which depend on the base.txz file. From owner-freebsd-questions@freebsd.org Mon Apr 18 14:04:25 2016 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 45F01B123C2 for ; Mon, 18 Apr 2016 14:04:25 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 32A961DA6 for ; Mon, 18 Apr 2016 14:04:25 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by mailman.ysv.freebsd.org (Postfix) id 31F72B123C1; Mon, 18 Apr 2016 14:04:25 +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 3198CB123BE for ; Mon, 18 Apr 2016 14:04:25 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.70.90]) by mx1.freebsd.org (Postfix) with ESMTP id 112AF1DA4 for ; Mon, 18 Apr 2016 14:04:24 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id A6BE5CB8CA6; Mon, 18 Apr 2016 09:04:23 -0500 (CDT) Received: from 10.150.49.110 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Mon, 18 Apr 2016 09:04:23 -0500 (CDT) Message-ID: <52971.10.150.49.110.1460988263.squirrel@cosmo.uchicago.edu> In-Reply-To: References: <1458712914.1578.37.camel@au.dyndns.ws> Date: Mon, 18 Apr 2016 09:04:23 -0500 (CDT) Subject: Re: [Phishing]Re: Anti-virus for FreeBSD From: "Valeri Galtsev" To: "Daniel Feenberg" Cc: "Wayne Sierke" , "Olivier Nicole" , questions@freebsd.org, "krad" 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 14:04:25 -0000 On Mon, April 18, 2016 8:16 am, Daniel Feenberg wrote: > > A late follow-up to the question of Windows anti-virus running on FreeBSD > I wrote to my vendor, who obtained this from Kaspersky in Russia. And as I keep mentioning Kaspersky is KGB guy (there is no "was" in intelligence "community"), so everybody do your own trust assessment for yourself. Valeri > Reading > between the lines, it is possible that support may cease, but there are no > such plans. I have been unable to locate anything that can detect > executable docx or pdf. > > dan feenberg > > =============================================================================== > On 4/8/16, 9:04 AM, "Julian Garcia" wrote: > >>Hi Stefan, >> >>I heard back from HQ. >> >>FreeBSD support and development will continue; with FreeBSD is supported >>in KLMS up to version 10.1 (32\64) with Version 10.2 (86 / 64) support >>scheduled in MP2 for this autumn. >> >> >>Thank you. >> >>Regards, >>Julian >> >> >> >> >>Julian Garcia | Pre-Sales Engineer | > >>www.kaspersky.com | www.threatpost.com | www.securelist.com | >> > _______________________________________________ > 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 Mon Apr 18 14:28:24 2016 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 7F1B9B131BD for ; Mon, 18 Apr 2016 14:28:24 +0000 (UTC) (envelope-from shahzaib.cb@gmail.com) Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 475AC1CE7 for ; Mon, 18 Apr 2016 14:28:24 +0000 (UTC) (envelope-from shahzaib.cb@gmail.com) Received: by mail-io0-x22d.google.com with SMTP id g185so196180748ioa.2 for ; Mon, 18 Apr 2016 07:28:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=xAc87yaJokJ3+PePaA+egzDL8vskGObOfT1rkN/yeno=; b=o2Jy4KrBQhgLKvCNGJo/lSVKqO9kJFyJamnnOBPxoN9QO58xi+G2GDHr716le6uOY3 Cyv09wbPXrl9BTvuDMBrNjp8ekaqKZcuxbl5ZgMl+37YQjYzoXQ5HNM7kcwPVftbW+wI qFisyNYDlyRfDZZq7TveoQXQmKUgBzh/U2GkmvlTNrcqy1yfYH4DOYCyFO04V7L4rtjv DSs/Ze26tg3I0QoZABtKsNWqkVJZAgSX0c4ZXH4PCptZAxO43A7yBs1VXZlZv3LbSFBe 2vwD5RzYnIo5yAFv+zm/zdseOarcoYTerqU9fC+daYgVAlffjnm/JBxKdzO6bnFdkB0q by7g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=xAc87yaJokJ3+PePaA+egzDL8vskGObOfT1rkN/yeno=; b=hbIjwIIG+PvwdgogeoJtHSq8z6PFEIeLQzaFgN/8XNL4+i2gHvDzUvcb4FTAt02oxu VtLk5mKm5h8r+2xzDkw18Uy9HFAR5BJtbB2RqyL0WQz68ToTecb6kjRZQfEBdPG1GWt4 xMGLu4sPoK8Tx4qVfcc4SBAWulV76o+kqz9ZokKpOMweMnnDjCPY4bQFEHaZXxTjjlTo A2fk3WPjPIgn5KM1QV8Flipk3XmZYiRvJfxJwu87rfjhaKYfm7f/6p1gMSQnYszwcaMu WKfukJhvczF+VRfmzMQHpgEjc9S4nytwHLmemgXsSwlGrxx0kR46iZ44BSlNtjRsnsiW RiiQ== X-Gm-Message-State: AOPr4FWQzWw92CeM4QJ/U8+duISJwgBLqY4NqdLDswGkoH+L9VGnUAZ3MnJCCqRUlnr4WLP5r4CzEt1j5G9n7w== MIME-Version: 1.0 X-Received: by 10.107.14.142 with SMTP id 136mr34535626ioo.94.1460989703034; Mon, 18 Apr 2016 07:28:23 -0700 (PDT) Received: by 10.79.111.77 with HTTP; Mon, 18 Apr 2016 07:28:22 -0700 (PDT) In-Reply-To: References: <56E2E9AC.1040902@gmx.de> <33444.128.135.52.6.1457712900.squirrel@cosmo.uchicago.edu> <56E2F586.9000108@gmx.de> Date: Mon, 18 Apr 2016 19:28:22 +0500 Message-ID: Subject: Re: FreeBSD Crashes Intermittently !! From: shahzaib mushtaq To: "lokadamus@gmx.de" Cc: galtsev@kicp.uchicago.edu, freebsd-questions@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 14:28:24 -0000 Hi again, got back after a long time. So yes, we've move to new Dell R510 Hardware now. Here is the specs : DELL R510 2 x L5520 64GB RAM 12x3TB Raid stripping+mirroring (HBA LSI-9211-fw version 19.00) FreeBSD cw009.tunefiles.com 10.2-RELEASE-p14 FreeBSD 10.2-RELEASE-p14 #0: Wed Mar 16 20:46:12 UTC 2016 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 After 9days of uptime, server again got crashed with following error in crash log : http://pastebin.com/baShWuMP I am so much depressed now, there's much pressure on me from my company. Pl= ease help us resolving this crash issue . :( On Mon, Mar 14, 2016 at 10:37 PM, shahzaib shahzaib wrote: > Hi, > > Well, we've some messages in kernel logs each time the server boots up > which are : > > (probe0:mps0:0:3:7): CAM status: CCB request completed with an error > (probe0:mps0:0:3:7): Retrying command > (probe0:mps0:0:3:7): INQUIRY. CDB: 12 e0 00 00 24 00 > (probe0:mps0:0:3:7): CAM status: CCB request completed with an error > (probe0:mps0:0:3:7): Retrying command > (probe0:mps0:0:3:7): INQUIRY. CDB: 12 e0 00 00 24 00 > (probe0:mps0:0:3:7): CAM status: CCB request completed with an error > > In following post it is written that : > > these are due to a mismatch between firmware and driver version > > . FreeBSD 9 > = ships > with driver version 16 and FreeBSD 10 > = includes > version 19. Linux > currently > has version 18. So make sure that in step 11, you always flash the versio= n > that matches your operating system=E2=80=99s driver version, don=E2=80=99= t blindly go with > version P20 or the latest version > > Here is the link to that Post : > > > http://blog.michael.kuron-germany.de/2014/11/crossflashing-dell-perc-h200= -to-lsi-9211-8i/comment-page-1/ > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > It looks like that it might be the issue of crash as we're using LSI-9211 > controller and maybe due to mismatch between firmware and driver version > this crash occurs. > > On Fri, Mar 11, 2016 at 9:42 PM, lokadamus@gmx.de > wrote: > >> On 03/11/16 17:15, Valeri Galtsev wrote: >> >>> http://pastebin.com/042SJ11c >> >> Have you look for bios update? >> >> http://www.supermicro.com/products/motherboard/QPI/5500/X8DT3.cfm >> >> Version R 2.1 is the last one. >> > >> > In my humble opinion, the _need_ to install BIOS update is extremely b= ad >> > flag on hardware manufacturer reputation. For ages I used Tyan system >> > boards ("motherboard" jargon became the name for system board decades >> > ago...) >> Ok, never use DELL. You will never be happy with it. >> I work some month for a big company and most server problems can only be >> solved with a bios update. >> >> And never look for microcode updates, that will fix things and problems. >> Greetings >> > > From owner-freebsd-questions@freebsd.org Mon Apr 18 14:59:07 2016 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 811E9B13F64 for ; Mon, 18 Apr 2016 14:59:07 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2157D1732 for ; Mon, 18 Apr 2016 14:59:07 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from ox-dell39.ox.adestra.com (unknown [85.199.232.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id C24FB11C14 for ; Mon, 18 Apr 2016 14:59:02 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/C24FB11C14; dkim=none; dkim-atps=neutral Subject: Re: FreeBSD Crashes Intermittently !! To: freebsd-questions@freebsd.org References: <56E2E9AC.1040902@gmx.de> <33444.128.135.52.6.1457712900.squirrel@cosmo.uchicago.edu> <56E2F586.9000108@gmx.de> From: Matthew Seaman Message-ID: Date: Mon, 18 Apr 2016 15:58:56 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ntLkTImdkjEBPXD7tb3mpPbj4vd05b02t" X-Virus-Scanned: clamav-milter 0.99.1 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-0.4 required=5.0 tests=BAYES_00,RDNS_NONE, SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 14:59:07 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ntLkTImdkjEBPXD7tb3mpPbj4vd05b02t Content-Type: multipart/mixed; boundary="tXvPUEkg1L9RWjFIxQ3VoXrLmoAmrFCsf" From: Matthew Seaman To: freebsd-questions@freebsd.org Message-ID: Subject: Re: FreeBSD Crashes Intermittently !! References: <56E2E9AC.1040902@gmx.de> <33444.128.135.52.6.1457712900.squirrel@cosmo.uchicago.edu> <56E2F586.9000108@gmx.de> In-Reply-To: --tXvPUEkg1L9RWjFIxQ3VoXrLmoAmrFCsf Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 04/18/16 15:28, shahzaib mushtaq wrote: > Hi again, got back after a long time. So yes, we've move to new Dell R5= 10 > Hardware now. Here is the specs : >=20 > DELL R510 > 2 x L5520 > 64GB RAM > 12x3TB Raid stripping+mirroring (HBA LSI-9211-fw version 19.00) > FreeBSD cw009.tunefiles.com 10.2-RELEASE-p14 FreeBSD 10.2-RELEASE-p14 #= 0: > Wed Mar 16 20:46:12 UTC 2016 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC > amd64 >=20 > After 9days of uptime, server again got crashed with following error in= > crash log : See where it says this in your crash log: Hardware event. This is not a software error Unfortunately your 'new' server is broken. I say 'new' because the R510 is an 11th generation product no longer available from Dell (they're on 13th generation kit now) -- it must be several years old at least. Try running memtest86 on it and see how long it survives. If memtest86 says something is broken, then it's pretty definitive. (Although when memtest86 doesn't say 'broken', that doesn't necessarily mean it is OK -- there are failure conditions that memtest86 doesn't pick up on.) According to the output you posted one of the CPUs has gone kaput. If this machine has multiple physical CPU packages, you might be able to get it to run reliably by taking out the broken one. Identifying which one that is might be tricky, but if all else fails you can do it be a process of elimination. Be aware though that removing a CPU pacckage may mean you need to juggle the RAM about, as it's fairly common for some of the RAM slots to be tied to a specific CPU package. Cheers, Matthew --tXvPUEkg1L9RWjFIxQ3VoXrLmoAmrFCsf-- --ntLkTImdkjEBPXD7tb3mpPbj4vd05b02t Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJXFPYwAAoJEABRPxDgqeTn5sUP/A2MMtIXDaa37KaYfPSNJpL1 3Vz8RCFTwhLqn+jyfbEYPEAwXQ+f23bnSAxtflVqF9NbPkZVqFTCU3USfPc7ed5V ml3nSQh5l6k3sFYu2EMtD/mFzNzucWpYlnAD8LIZmGvjg5YrC9Xf/GnX7D/3jG+f K9onlWD6+62wCOGQI1UEVY+3KRcmJcrovIVV1nEGZSRkuFbsiaiSFV//CUnfQQdf rX/+0LFWtkF/I+qdmFIubOUHA0BaPDJ8DXGQJJgu7Gq/nFT9aHYhPmlNmXcIWiqf 6UUNAs0QTAqFvm5CaV4MGKHfC3wVcx04bqpaetAOePJfF+T5My7e3wDKGf/j0ftO XWhyIRr6t3Lppu2Q+SNAftlT97MHdZZLAu6mPDdYG9CnsuXcL4UVbaQY2HPD8wJW gnGROJ4iNCRq5zDp+7qFyQMQe1iKW6/b00wLVTLGTue0pFr2uyLH05h/enFPzWed LBCqQf74HcGspLD4Wh77i6WTa+mfMcEl+u3R9pnNAqaVp8Ic0p1QATq8NlAg3OUT 6J0C1Pk1P/ty1N5mYoVCxwsy5mIje7hgeIp7UZ0Ta44WXCdv5wonJcIyqVukn7hG SQP8UNgmo2fP6WrVCRdgIi0shZQ4R7FNfKGdP3SsavnGL/lyA4GFX7o/nSzEFhjn BzS0wFjwCkCFVi68nYst =7405 -----END PGP SIGNATURE----- --ntLkTImdkjEBPXD7tb3mpPbj4vd05b02t-- From owner-freebsd-questions@freebsd.org Mon Apr 18 16:50:15 2016 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 C6A2FB13E61 for ; Mon, 18 Apr 2016 16:50:15 +0000 (UTC) (envelope-from jd1008@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 8F63D170B for ; Mon, 18 Apr 2016 16:50:15 +0000 (UTC) (envelope-from jd1008@gmail.com) Received: by mail-io0-x236.google.com with SMTP id o126so200568528iod.0 for ; Mon, 18 Apr 2016 09:50:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=ybpMYB13ocja6mJvbcadLKa6a3rUB6RA9WTtI9u/vrY=; b=ZBDCJvO8nWVEK/IyR1HMcc+kVgms2Sk8BEvexyqy5CL8w2scpr4fdxrl4rcnggewDA oMiD5eyVtPv8VGxLGErRR+6KUfDDwc37BhFvRZh5VjcfqkKGQs47BoRZ6Hp74aaI1DBi uNOyGAqOQWx9N4QwDOTm0tQjQZR8e0YkU2iN8RC0ajQgTWeN7Ri9d+SZkNE6L9suoHji san5MZiU6pKDxcD5Bw/lz47KWVIVGBmFzC57N/uKq77yaGvDdQRNydv4NPIeaOkorAO7 Q3lMzQcmpR3NE7MzffkhdX5Gqi3TlowpN/mWXEc9iuf+oUU3X9L6qKwnuV09/V5eL2Ta QT0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=ybpMYB13ocja6mJvbcadLKa6a3rUB6RA9WTtI9u/vrY=; b=JzZ7X3ep/4SfUH5qVqEQbTL73Ry3KBs0Xy/9lv5WbVNx8EGXmGMNwL45rYeXkdOW1z /90DQxG/aqfy3f96j0p0aET3bDj/zqTHTbO4bubM/dAhRACQgPuQkb2eKnc/M242P35R hOyvkRM0SsjVg9a1zFtnTLtGx2WE+DyoVl0qw1RTmQCoEgew1T1ae6repbwFIAhq5Qig KQmX4TsQjZqnvFgjO1YnAYsNgr11+KcAAmlTj+6IHnOwIi6o7Qra4jWhqkbb8dkaaYSe Iijh5eRXWc9reoWyhLsuBR15prYYTwq+uHkHLrB3OOCvLZj0p2YQA0vFfxM5kmEwo9fZ zxaQ== X-Gm-Message-State: AOPr4FW27EyaMCMjz67SBx/KLbnxzKZtjr5bnfbhLBOhhmTWkliG7hpCWVQYrvEjYM/1mQ== X-Received: by 10.107.12.224 with SMTP id 93mr39110096iom.70.1460998214867; Mon, 18 Apr 2016 09:50:14 -0700 (PDT) Received: from localhost.localdomain ([50.243.6.59]) by smtp.googlemail.com with ESMTPSA id j40sm38276240iod.31.2016.04.18.09.50.13 for (version=TLSv1/SSLv3 cipher=OTHER); Mon, 18 Apr 2016 09:50:13 -0700 (PDT) Subject: Re: Upgrading FreeBSD 4.10 To: freebsd-questions@freebsd.org References: From: jd1008 Message-ID: <5715103F.5050503@gmail.com> Date: Mon, 18 Apr 2016 10:50:07 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 16:50:15 -0000 +1 Good advice. On 04/18/2016 02:22 AM, krad wrote: > 4->5 was a big jump as loads of stuff in RC changed IIRC, and from there to > 10 or even 8 is a big jump. You would be far better placed to build a brand > new machine based on your selected version of freebsd (probably 10.3), and > then port your applications one by one > > On 15 April 2016 at 11:11, Allan Kapoma wrote: > >> Hello >> >> >> >> I’m running FreeBSD 4.10 and I want to upgrade the system to a later >> version of FreeBSD. >> >> >> >> However, whenever I run commands to update the system (# freebsd-update), >> or install portsnap, or install portmanager, or pkg commands, or portsnap >> fetch extract, I’m getting the message that command not found >> >> >> >> The my output for uname –a is shown below >> >> >> >> relay# uname -a >> >> FreeBSD relay.zamnet.zm 4.10-RELEASE FreeBSD 4.10-RELEASE #1: Fri Nov 12 >> 06:54:4 >> >> >> >> I’m asking for assistance on how I can enable the system (FreeBSD 4.10) to >> run these commands and hopefully update my system and packages on it >> >> >> >> Regards >> _______________________________________________ >> 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 Mon Apr 18 19:22:41 2016 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 2036FB13C64 for ; Mon, 18 Apr 2016 19:22:41 +0000 (UTC) (envelope-from bah@bananmonarki.se) Received: from feeder.usenet4all.se (1-1-1-38a.far.sth.bostream.se [82.182.32.53]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9DDC6150B for ; Mon, 18 Apr 2016 19:22:38 +0000 (UTC) (envelope-from bah@bananmonarki.se) Received: from testbox.news4all.se (testbox.usenet4all.se [10.0.0.3]) by feeder.usenet4all.se (8.13.1/8.13.1) with ESMTP id u3IJMSrY002681 for ; Mon, 18 Apr 2016 21:22:29 +0200 (CEST) (envelope-from bah@bananmonarki.se) To: "freebsd-questions@freebsd.org" From: Bernt Hansson Subject: Raid 1+0 Message-ID: <571533F4.8040406@bananmonarki.se> Date: Mon, 18 Apr 2016 21:22:28 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 19:22:41 -0000 Hello list My motherboard has a raid chip on it (AMD SB750), so my plan was to use it. Since i never used the chip for raid, i thought i might try. So far this has been done. Set up 2 arrays with 2 discs in each array with raid1 on both. Boot up freebsd 10.3-R. Both arrays are found GEOM_RAID: Promise: Disk ada0 state changed from NONE to ACTIVE. GEOM_RAID: Promise: Subdisk RAID 1 LD 1:0-ada0 state changed from NONE to ACTIVE. GEOM_RAID: Promise: Disk ada1 state changed from NONE to ACTIVE. GEOM_RAID: Promise: Subdisk RAID 1 LD 1:1-ada1 state changed from NONE to ACTIVE. GEOM_RAID: Promise: Volume started. GEOM_RAID: Promise: Volume RAID 1 LD 1 state changed from STARTING to OPTIMAL. GEOM_RAID: Promise: Provider raid/r0 for volume RAID 1 LD 1 created. GEOM_RAID: Promise: Disk ada2 state changed from NONE to ACTIVE. GEOM_RAID: Promise: Subdisk RAID 1 LD 2:0-ada2 state changed from NONE to ACTIVE. GEOM_RAID: Promise: Disk ada3 state changed from NONE to ACTIVE. GEOM_RAID: Promise: Subdisk RAID 1 LD 2:1-ada3 state changed from NONE to ACTIVE. GEOM_RAID: Promise: Volume started. GEOM_RAID: Promise: Volume RAID 1 LD 2 state changed from STARTING to OPTIMAL. GEOM_RAID: Promise: Provider raid/r1 for volume RAID 1 LD 2 created. Used gstripe to stripe the arrays raid/r0 + r1 into stripe0 Newfs/mount all work. My question, is this a raid 1+0 or 0+1? More info can be posted if need be. # graid list Geom name: Promise State: OPTIMAL Metadata: Promise Providers: 1. Name: raid/r0 Mediasize: 999999995904 (931G) Sectorsize: 512 Mode: r1w1e2 Subdisks: ada0 (ACTIVE), ada1 (ACTIVE) Dirty: No State: OPTIMAL Strip: 65536 Components: 2 Transformation: RAID1 RAIDLevel: RAID1 Label: RAID 1 LD 1 descr: Promise RAID1 volume 2. Name: raid/r1 Mediasize: 999999995904 (931G) Sectorsize: 512 Mode: r1w1e2 Subdisks: ada2 (ACTIVE), ada3 (ACTIVE) Dirty: No State: OPTIMAL Strip: 65536 Components: 2 Transformation: RAID1 RAIDLevel: RAID1 Label: RAID 1 LD 2 descr: Promise RAID1 volume Consumers: 1. Name: ada0 Mediasize: 1000204886016 (932G) Sectorsize: 512 Mode: r1w1e1 ReadErrors: 0 Subdisks: r0(RAID 1 LD 1):0@0 State: ACTIVE (ACTIVE) 2. Name: ada1 Mediasize: 1000204886016 (932G) Sectorsize: 512 Mode: r1w1e1 ReadErrors: 0 Subdisks: r0(RAID 1 LD 1):1@0 State: ACTIVE (ACTIVE) 3. Name: ada2 Mediasize: 1000204886016 (932G) Sectorsize: 512 Mode: r1w1e1 ReadErrors: 0 Subdisks: r1(RAID 1 LD 2):0@0 State: ACTIVE (ACTIVE) 4. Name: ada3 Mediasize: 1000204886016 (932G) Sectorsize: 512 Mode: r1w1e1 ReadErrors: 0 Subdisks: r1(RAID 1 LD 2):1@0 State: ACTIVE (ACTIVE) graid status Name Status Components raid/r0 OPTIMAL ada0 (ACTIVE (ACTIVE)) ada1 (ACTIVE (ACTIVE)) ada2 (ACTIVE (ACTIVE)) ada3 (ACTIVE (ACTIVE)) raid/r1 OPTIMAL ada0 (ACTIVE (ACTIVE)) ada1 (ACTIVE (ACTIVE)) ada2 (ACTIVE (ACTIVE)) ada3 (ACTIVE (ACTIVE)) # gstripe status Name Status Components stripe/stripe0 UP raid/r0 raid/r1 root@testbox:/usr/home/bernt # gstripe list Geom name: stripe0 State: UP Status: Total=2, Online=2 Type: AUTOMATIC Stripesize: 65536 ID: 364832905 Providers: 1. Name: stripe/stripe0 Mediasize: 1999999860736 (1.8T) Sectorsize: 512 Stripesize: 65536 Stripeoffset: 0 Mode: r1w1e1 Consumers: 1. Name: raid/r0 Mediasize: 999999995904 (931G) Sectorsize: 512 Mode: r1w1e2 Number: 0 2. Name: raid/r1 Mediasize: 999999995904 (931G) Sectorsize: 512 Mode: r1w1e2 Number: 1 From owner-freebsd-questions@freebsd.org Mon Apr 18 19:26:36 2016 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 25225B13DBF for ; Mon, 18 Apr 2016 19:26:36 +0000 (UTC) (envelope-from xxjack12xx@gmail.com) Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com [IPv6:2607:f8b0:4001:c05::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 E684917A4 for ; Mon, 18 Apr 2016 19:26:35 +0000 (UTC) (envelope-from xxjack12xx@gmail.com) Received: by mail-ig0-x230.google.com with SMTP id gy3so81953185igb.0 for ; Mon, 18 Apr 2016 12:26:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=gH2JuX5CO0KTUeT4Ezw/GwYor43FGzaaLHP/nYvOy/w=; b=zdcNfPqQROIN8NVH8Oi1kWzxdziBaSbJIBDrli9T7MIADOB1tXH+C2METYQPX/f841 V/85GXl7nQ4RA2vCz5JQhcgoadFrYdXmtS7XRxUf0Mia3sMPrnnQ8w9JoDlV3rgwsSDQ XZj44VZ0/DfhyO6BMlyXbdjEDju8jTTJgRa/c1Kv89Pm2Nl2OHRpNFJM4g49SZFSLqmu 8pWOuwaI/jCRh3+NAdqRtJesIZzhN6WLPqHDFB0samofr0eI1H4jeLLHuh1WSOPFhZKn kqRUDV3pjwlbsFYsvB5lLEpK3mP2jzIu9v1BxAslabnNF/ugALkthhHaKDv5QSEJtp0b VKsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=gH2JuX5CO0KTUeT4Ezw/GwYor43FGzaaLHP/nYvOy/w=; b=eoDlclxCN4o8czD6i2Sa7lsOiBfd9ZOLGQ9iPM0rxcvt/SiPEr7rGEk8wffou0MoA3 JS+VYEKD2eHtnDBs8HI/nLqUA6uk3RUwXi1aEjJhPiQ0opDkxK/pHM+iKh7s0FPAcaQG Fj+Gm03jeSRba0fQUlfIgZSuZRs4Q7GVh0hxBMfaddJMWvvLYkRiiTmCyTpo1k2qIefM ZXEM6rP0/arqVISoW/suhsrQF/bluQDqQwpdXtxMfqgDFee+hcgRuTQYKpUlddLhl1Fu O/5EXtG0jjbH2DPvcCw6QTnUJkg79kCpEV92Od+Qq74s4amifhdLeNZa3ImCIOkPGeYG 5zjw== X-Gm-Message-State: AOPr4FVLEGt7UrD/5795dRx+xeCTTFQinecEyTL5FPv7g7ElmG7hwwVosrxoyCJ1xwl2a572Y/lUqCtabbFtYA== X-Received: by 10.50.92.37 with SMTP id cj5mr21553479igb.91.1461007595319; Mon, 18 Apr 2016 12:26:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.41.129 with HTTP; Mon, 18 Apr 2016 12:25:55 -0700 (PDT) In-Reply-To: <571533F4.8040406@bananmonarki.se> References: <571533F4.8040406@bananmonarki.se> From: "Jack L." Date: Mon, 18 Apr 2016 12:25:55 -0700 Message-ID: Subject: Re: Raid 1+0 To: Bernt Hansson Cc: "freebsd-questions@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 19:26:36 -0000 What size are the disks? That should give a hint on what raid level that is. On Mon, Apr 18, 2016 at 12:22 PM, Bernt Hansson wrote: > Hello list > > My motherboard has a raid chip on it (AMD SB750), so my plan was to use it. > Since i never used the chip for raid, i thought i might try. > > So far this has been done. > > Set up 2 arrays with 2 discs in each array with raid1 on both. > > Boot up freebsd 10.3-R. Both arrays are found > > GEOM_RAID: Promise: Disk ada0 state changed from NONE to ACTIVE. > GEOM_RAID: Promise: Subdisk RAID 1 LD 1:0-ada0 state changed from NONE to > ACTIVE. > GEOM_RAID: Promise: Disk ada1 state changed from NONE to ACTIVE. > GEOM_RAID: Promise: Subdisk RAID 1 LD 1:1-ada1 state changed from NONE to > ACTIVE. > GEOM_RAID: Promise: Volume started. > GEOM_RAID: Promise: Volume RAID 1 LD 1 state changed from STARTING to > OPTIMAL. > GEOM_RAID: Promise: Provider raid/r0 for volume RAID 1 LD 1 created. > GEOM_RAID: Promise: Disk ada2 state changed from NONE to ACTIVE. > GEOM_RAID: Promise: Subdisk RAID 1 LD 2:0-ada2 state changed from NONE to > ACTIVE. > GEOM_RAID: Promise: Disk ada3 state changed from NONE to ACTIVE. > GEOM_RAID: Promise: Subdisk RAID 1 LD 2:1-ada3 state changed from NONE to > ACTIVE. > GEOM_RAID: Promise: Volume started. > GEOM_RAID: Promise: Volume RAID 1 LD 2 state changed from STARTING to > OPTIMAL. > GEOM_RAID: Promise: Provider raid/r1 for volume RAID 1 LD 2 created. > > Used gstripe to stripe the arrays raid/r0 + r1 into stripe0 > > Newfs/mount all work. My question, is this a raid 1+0 or 0+1? > More info can be posted if need be. > > # graid list > Geom name: Promise > State: OPTIMAL > Metadata: Promise > Providers: > 1. Name: raid/r0 > Mediasize: 999999995904 (931G) > Sectorsize: 512 > Mode: r1w1e2 > Subdisks: ada0 (ACTIVE), ada1 (ACTIVE) > Dirty: No > State: OPTIMAL > Strip: 65536 > Components: 2 > Transformation: RAID1 > RAIDLevel: RAID1 > Label: RAID 1 LD 1 > descr: Promise RAID1 volume > 2. Name: raid/r1 > Mediasize: 999999995904 (931G) > Sectorsize: 512 > Mode: r1w1e2 > Subdisks: ada2 (ACTIVE), ada3 (ACTIVE) > Dirty: No > State: OPTIMAL > Strip: 65536 > Components: 2 > Transformation: RAID1 > RAIDLevel: RAID1 > Label: RAID 1 LD 2 > descr: Promise RAID1 volume > Consumers: > 1. Name: ada0 > Mediasize: 1000204886016 (932G) > Sectorsize: 512 > Mode: r1w1e1 > ReadErrors: 0 > Subdisks: r0(RAID 1 LD 1):0@0 > State: ACTIVE (ACTIVE) > 2. Name: ada1 > Mediasize: 1000204886016 (932G) > Sectorsize: 512 > Mode: r1w1e1 > ReadErrors: 0 > Subdisks: r0(RAID 1 LD 1):1@0 > State: ACTIVE (ACTIVE) > 3. Name: ada2 > Mediasize: 1000204886016 (932G) > Sectorsize: 512 > Mode: r1w1e1 > ReadErrors: 0 > Subdisks: r1(RAID 1 LD 2):0@0 > State: ACTIVE (ACTIVE) > 4. Name: ada3 > Mediasize: 1000204886016 (932G) > Sectorsize: 512 > Mode: r1w1e1 > ReadErrors: 0 > Subdisks: r1(RAID 1 LD 2):1@0 > State: ACTIVE (ACTIVE) > > graid status > Name Status Components > raid/r0 OPTIMAL ada0 (ACTIVE (ACTIVE)) > ada1 (ACTIVE (ACTIVE)) > ada2 (ACTIVE (ACTIVE)) > ada3 (ACTIVE (ACTIVE)) > raid/r1 OPTIMAL ada0 (ACTIVE (ACTIVE)) > ada1 (ACTIVE (ACTIVE)) > ada2 (ACTIVE (ACTIVE)) > ada3 (ACTIVE (ACTIVE)) > > # gstripe status > Name Status Components > stripe/stripe0 UP raid/r0 > raid/r1 > root@testbox:/usr/home/bernt # gstripe list > Geom name: stripe0 > State: UP > Status: Total=2, Online=2 > Type: AUTOMATIC > Stripesize: 65536 > ID: 364832905 > Providers: > 1. Name: stripe/stripe0 > Mediasize: 1999999860736 (1.8T) > Sectorsize: 512 > Stripesize: 65536 > Stripeoffset: 0 > Mode: r1w1e1 > Consumers: > 1. Name: raid/r0 > Mediasize: 999999995904 (931G) > Sectorsize: 512 > Mode: r1w1e2 > Number: 0 > 2. Name: raid/r1 > Mediasize: 999999995904 (931G) > Sectorsize: 512 > Mode: r1w1e2 > Number: 1 > > _______________________________________________ > 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 Apr 18 19:33:09 2016 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 ED860B131DE for ; Mon, 18 Apr 2016 19:33:09 +0000 (UTC) (envelope-from bah@bananmonarki.se) Received: from feeder.usenet4all.se (1-1-1-38a.far.sth.bostream.se [82.182.32.53]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7C67F1EA5 for ; Mon, 18 Apr 2016 19:33:08 +0000 (UTC) (envelope-from bah@bananmonarki.se) Received: from testbox.news4all.se (testbox.usenet4all.se [10.0.0.3]) by feeder.usenet4all.se (8.13.1/8.13.1) with ESMTP id u3IJX5CD002847; Mon, 18 Apr 2016 21:33:05 +0200 (CEST) (envelope-from bah@bananmonarki.se) Subject: Re: Raid 1+0 To: "Jack L." References: <571533F4.8040406@bananmonarki.se> Cc: "freebsd-questions@freebsd.org" From: Bernt Hansson Message-ID: <57153671.3050602@bananmonarki.se> Date: Mon, 18 Apr 2016 21:33:05 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 19:33:10 -0000 On 2016-04-18 21:25, Jack L. wrote: > What size are the disks? That should give a hint on what raid level that is. They are all 1Tb dics. The reported size is 1,8 Tb. > On Mon, Apr 18, 2016 at 12:22 PM, Bernt Hansson wrote: >> Hello list >> >> My motherboard has a raid chip on it (AMD SB750), so my plan was to use it. >> Since i never used the chip for raid, i thought i might try. >> >> So far this has been done. >> >> Set up 2 arrays with 2 discs in each array with raid1 on both. >> >> Boot up freebsd 10.3-R. Both arrays are found >> >> GEOM_RAID: Promise: Disk ada0 state changed from NONE to ACTIVE. >> GEOM_RAID: Promise: Subdisk RAID 1 LD 1:0-ada0 state changed from NONE to >> ACTIVE. >> GEOM_RAID: Promise: Disk ada1 state changed from NONE to ACTIVE. >> GEOM_RAID: Promise: Subdisk RAID 1 LD 1:1-ada1 state changed from NONE to >> ACTIVE. >> GEOM_RAID: Promise: Volume started. >> GEOM_RAID: Promise: Volume RAID 1 LD 1 state changed from STARTING to >> OPTIMAL. >> GEOM_RAID: Promise: Provider raid/r0 for volume RAID 1 LD 1 created. >> GEOM_RAID: Promise: Disk ada2 state changed from NONE to ACTIVE. >> GEOM_RAID: Promise: Subdisk RAID 1 LD 2:0-ada2 state changed from NONE to >> ACTIVE. >> GEOM_RAID: Promise: Disk ada3 state changed from NONE to ACTIVE. >> GEOM_RAID: Promise: Subdisk RAID 1 LD 2:1-ada3 state changed from NONE to >> ACTIVE. >> GEOM_RAID: Promise: Volume started. >> GEOM_RAID: Promise: Volume RAID 1 LD 2 state changed from STARTING to >> OPTIMAL. >> GEOM_RAID: Promise: Provider raid/r1 for volume RAID 1 LD 2 created. >> >> Used gstripe to stripe the arrays raid/r0 + r1 into stripe0 >> >> Newfs/mount all work. My question, is this a raid 1+0 or 0+1? >> More info can be posted if need be. >> >> # graid list >> Geom name: Promise >> State: OPTIMAL >> Metadata: Promise >> Providers: >> 1. Name: raid/r0 >> Mediasize: 999999995904 (931G) >> Sectorsize: 512 >> Mode: r1w1e2 >> Subdisks: ada0 (ACTIVE), ada1 (ACTIVE) >> Dirty: No >> State: OPTIMAL >> Strip: 65536 >> Components: 2 >> Transformation: RAID1 >> RAIDLevel: RAID1 >> Label: RAID 1 LD 1 >> descr: Promise RAID1 volume >> 2. Name: raid/r1 >> Mediasize: 999999995904 (931G) >> Sectorsize: 512 >> Mode: r1w1e2 >> Subdisks: ada2 (ACTIVE), ada3 (ACTIVE) >> Dirty: No >> State: OPTIMAL >> Strip: 65536 >> Components: 2 >> Transformation: RAID1 >> RAIDLevel: RAID1 >> Label: RAID 1 LD 2 >> descr: Promise RAID1 volume >> Consumers: >> 1. Name: ada0 >> Mediasize: 1000204886016 (932G) >> Sectorsize: 512 >> Mode: r1w1e1 >> ReadErrors: 0 >> Subdisks: r0(RAID 1 LD 1):0@0 >> State: ACTIVE (ACTIVE) >> 2. Name: ada1 >> Mediasize: 1000204886016 (932G) >> Sectorsize: 512 >> Mode: r1w1e1 >> ReadErrors: 0 >> Subdisks: r0(RAID 1 LD 1):1@0 >> State: ACTIVE (ACTIVE) >> 3. Name: ada2 >> Mediasize: 1000204886016 (932G) >> Sectorsize: 512 >> Mode: r1w1e1 >> ReadErrors: 0 >> Subdisks: r1(RAID 1 LD 2):0@0 >> State: ACTIVE (ACTIVE) >> 4. Name: ada3 >> Mediasize: 1000204886016 (932G) >> Sectorsize: 512 >> Mode: r1w1e1 >> ReadErrors: 0 >> Subdisks: r1(RAID 1 LD 2):1@0 >> State: ACTIVE (ACTIVE) >> >> graid status >> Name Status Components >> raid/r0 OPTIMAL ada0 (ACTIVE (ACTIVE)) >> ada1 (ACTIVE (ACTIVE)) >> ada2 (ACTIVE (ACTIVE)) >> ada3 (ACTIVE (ACTIVE)) >> raid/r1 OPTIMAL ada0 (ACTIVE (ACTIVE)) >> ada1 (ACTIVE (ACTIVE)) >> ada2 (ACTIVE (ACTIVE)) >> ada3 (ACTIVE (ACTIVE)) >> >> # gstripe status >> Name Status Components >> stripe/stripe0 UP raid/r0 >> raid/r1 >> root@testbox:/usr/home/bernt # gstripe list >> Geom name: stripe0 >> State: UP >> Status: Total=2, Online=2 >> Type: AUTOMATIC >> Stripesize: 65536 >> ID: 364832905 >> Providers: >> 1. Name: stripe/stripe0 >> Mediasize: 1999999860736 (1.8T) >> Sectorsize: 512 >> Stripesize: 65536 >> Stripeoffset: 0 >> Mode: r1w1e1 >> Consumers: >> 1. Name: raid/r0 >> Mediasize: 999999995904 (931G) >> Sectorsize: 512 >> Mode: r1w1e2 >> Number: 0 >> 2. Name: raid/r1 >> Mediasize: 999999995904 (931G) >> Sectorsize: 512 >> Mode: r1w1e2 >> Number: 1 > From owner-freebsd-questions@freebsd.org Mon Apr 18 19:42:01 2016 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 7995EB135DC for ; Mon, 18 Apr 2016 19:42:01 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5850B14FF for ; Mon, 18 Apr 2016 19:42:01 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 5740CB135D8; Mon, 18 Apr 2016 19:42:01 +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 56B01B135D7; Mon, 18 Apr 2016 19:42:01 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-ig0-x241.google.com (mail-ig0-x241.google.com [IPv6:2607:f8b0:4001:c05::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 1F01C14F3; Mon, 18 Apr 2016 19:42:01 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-ig0-x241.google.com with SMTP id qu10so12222397igc.1; Mon, 18 Apr 2016 12:42:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=XwTdXNr1N3kNzCG86Gxk9LjxBJW6x6aWT/7m4YQ2/Os=; b=yDmjjh1NaGeoCChF+JWfUmQUQMli0JLIoVxnOT8LXsxAuJzcwz/8cAvF5EenWDoxaM qqIpW/Xd7BZDLaL78Q/srtqxOQ7lzilwwC4l/74HpE1qXG+yG+fm9M0MGi+O6A1vOKg/ xcH2KL9/LoVQ6WcHImSUt7bnrxHIoynLnK+qnFJDiT9mZaFr/CaPQSGLuthBKC/SOhhR jgP6slVMJYRowTCbUTguiZrYxBM7rKrjVotP7CBkj+DHmDONABhhE3qVbtoz29s8UWlH gkv0c9ImoSdacZ9m4v5TITU/ImoXuz7e44ejielwYVHuLLeshlE6qMrppULOv2KbOcjC FcBw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=XwTdXNr1N3kNzCG86Gxk9LjxBJW6x6aWT/7m4YQ2/Os=; b=dCK008aguslB3T1oSq2rAqshXWBi0NZfxDnYb3OZuInNBfEmwmY6OmsH14GQB+zg+H yF7h9AR0gW6cD3gcr8xbNpbIPZSt0Bj+MZJSWrqkl9hgbdqif3aZPBnVJIep8YEHODqr Vtp1a7z3lUOBP6rWwcyAULkiFQ74nI1W2GpZ0YYsfLygiKklIswZ4djS60cKngF08y7A 9DCU0cTMyQ6bV2FOVzlszOkokvCVxz+hET840OqQ1uRZS7d2dSDnUtMepCSqUISHkrC7 vP6TOccRtZUjfQfaXdB8eqy1p4IYvpDl7Czab6PHKH9Zn69LnisziEG6N0ClKyNSJMEr OacQ== X-Gm-Message-State: AOPr4FXuhvPp+t9VfEkDk3oLJ8Be7+Xw8TZiFT/ZFMu5dGT2oqX1iThna8cFtthSGX5pmQ== X-Received: by 10.50.93.138 with SMTP id cu10mr20979974igb.96.1461008520280; Mon, 18 Apr 2016 12:42:00 -0700 (PDT) Received: from [10.0.10.3] (cpe-76-190-244-6.neo.res.rr.com. [76.190.244.6]) by smtp.googlemail.com with ESMTPSA id yf9sm209568igc.16.2016.04.18.12.41.59 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 18 Apr 2016 12:41:59 -0700 (PDT) Message-ID: <5715389C.9090502@gmail.com> Date: Mon, 18 Apr 2016 15:42:20 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Slawa Olhovchenkov CC: Baptiste Daroussin , freebsd-current@freebsd.org, freebsd-pkgbase@freebsd.org, questions@freebsd.org Subject: Re: 11.0-RELEASE pkg base & base.txz file References: <5714E89A.8000807@gmail.com> <20160418141454.GX4841@zxy.spb.ru> <20160418141601.GA26116@ivaldir.etoilebsd.net> <20160418142709.GY4841@zxy.spb.ru> <20160418150325.GZ4841@zxy.spb.ru> In-Reply-To: <20160418150325.GZ4841@zxy.spb.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 19:42:01 -0000 Slawa Olhovchenkov wrote: > On Mon, Apr 18, 2016 at 05:27:09PM +0300, Slawa Olhovchenkov wrote: > >> On Mon, Apr 18, 2016 at 04:16:01PM +0200, Baptiste Daroussin wrote: >> >>> On Mon, Apr 18, 2016 at 05:14:54PM +0300, Slawa Olhovchenkov wrote: >>>> On Mon, Apr 18, 2016 at 10:05:12AM -0400, Nikolai Lifanov wrote: >>>> >>>>> On 04/18/16 10:00, Ernie Luzar wrote: >>>>>> 11.0 will have pkg base, thats ok, but what does than mean for the >>>>>> base.txz file? >>>>>> >>>>>> It it going to stay as part of FBSD install? >>>>>> >>>>>> I have many scripts for creating jails which depend on the base.txz file. >>>>> It's even easier now: >>>>> >>>>> # mkdir -p /usr/jails/new >>>>> # pkg -r /usr/jails/new install -r base -g '*' >>>> And where /etc now? >>> What do you mean? >> At Jan 27 no package containing files from distributeworld. > > At Mar 02 > >> r298107 change this? >> You have NOT answered the original question, what's going to happen to the base.txz file in 11.0? From owner-freebsd-questions@freebsd.org Mon Apr 18 20:03:53 2016 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 0ACB6B13E34 for ; Mon, 18 Apr 2016 20:03:53 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id EC091110A for ; Mon, 18 Apr 2016 20:03:52 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: by mailman.ysv.freebsd.org (Postfix) id E7802B13E33; Mon, 18 Apr 2016 20:03:52 +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 E49D1B13E32; Mon, 18 Apr 2016 20:03:52 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 A51EB1107; Mon, 18 Apr 2016 20:03:52 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1asFOk-000700-Hx; Mon, 18 Apr 2016 23:03:54 +0300 Date: Mon, 18 Apr 2016 23:03:54 +0300 From: Slawa Olhovchenkov To: Ernie Luzar Cc: Baptiste Daroussin , freebsd-current@freebsd.org, freebsd-pkgbase@freebsd.org, questions@freebsd.org Subject: Re: 11.0-RELEASE pkg base & base.txz file Message-ID: <20160418200354.GB4841@zxy.spb.ru> References: <5714E89A.8000807@gmail.com> <20160418141454.GX4841@zxy.spb.ru> <20160418141601.GA26116@ivaldir.etoilebsd.net> <20160418142709.GY4841@zxy.spb.ru> <20160418150325.GZ4841@zxy.spb.ru> <5715389C.9090502@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5715389C.9090502@gmail.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 20:03:53 -0000 On Mon, Apr 18, 2016 at 03:42:20PM -0400, Ernie Luzar wrote: > Slawa Olhovchenkov wrote: > > On Mon, Apr 18, 2016 at 05:27:09PM +0300, Slawa Olhovchenkov wrote: > > > >> On Mon, Apr 18, 2016 at 04:16:01PM +0200, Baptiste Daroussin wrote: > >> > >>> On Mon, Apr 18, 2016 at 05:14:54PM +0300, Slawa Olhovchenkov wrote: > >>>> On Mon, Apr 18, 2016 at 10:05:12AM -0400, Nikolai Lifanov wrote: > >>>> > >>>>> On 04/18/16 10:00, Ernie Luzar wrote: > >>>>>> 11.0 will have pkg base, thats ok, but what does than mean for the > >>>>>> base.txz file? > >>>>>> > >>>>>> It it going to stay as part of FBSD install? > >>>>>> > >>>>>> I have many scripts for creating jails which depend on the base.txz file. > >>>>> It's even easier now: > >>>>> > >>>>> # mkdir -p /usr/jails/new > >>>>> # pkg -r /usr/jails/new install -r base -g '*' > >>>> And where /etc now? > >>> What do you mean? > >> At Jan 27 no package containing files from distributeworld. > > > > At Mar 02 > > > >> r298107 change this? > >> > > You have NOT answered the original question, what's going to happen to > the base.txz file in 11.0? Spliting to 800 packages, as I understund. From owner-freebsd-questions@freebsd.org Mon Apr 18 20:07:12 2016 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 74E89B131AA for ; Mon, 18 Apr 2016 20:07:12 +0000 (UTC) (envelope-from shamim.shahriar@gmail.com) Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D2A2C1898 for ; Mon, 18 Apr 2016 20:07:11 +0000 (UTC) (envelope-from shamim.shahriar@gmail.com) Received: by mail-wm0-x22d.google.com with SMTP id a140so135988463wma.0 for ; Mon, 18 Apr 2016 13:07:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=/IW4TJ6QgIYT4KSbPkfZhMV7lHIrUj/sb0ng/Grh7Ng=; b=0AQZtC5UW/rYpBbRWigWG2Y8QPXA0baF7UhtW2CsnrZkvcl3xynNZfvedL2gRLPtid 79mviBDfKjZNCsjjoEGEKdjPu1db4HsPFe9o6JlktFRMB5nGtTZcaUJr8CUAJIpeDIuS r/02d85G1q5UiSLtuIodMqcUlWeDnEQ3HPYxFavJ4Jtl6Lp64rOUROGd4l0nctQRXCoY U9X7zwjIHIc//8fAjsr6PpSVL+vrRBBTlQJvgKMfoM7ML3fhXgrlCGApDjrBNfXpr+tG LLIEDEUdiCCAR2yO4xsCh4xgv4Crn30B0t7g1thnGLB1VeU/fDBiNX3KT1ZtnlF+p+i5 0J7g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=/IW4TJ6QgIYT4KSbPkfZhMV7lHIrUj/sb0ng/Grh7Ng=; b=StIouvqL8pF0if666FUjAm0yqa4RqEsVxkH5qiH+HutqH9Kqy70yqOEbaA2GyMURIQ ieBnkYavg7/VU/87e6BCP4PhMUhcnVIcQZOT381ISYZg+t5qx055RlLOmLDicLPM1c/L 9RE7Y90eTz9Mj02oiXbeVIZd/W1Nw3e/z4eH17A/lYWpveIp172W9ZmTx37pHDAEV6c7 FjDWrE7I6YTzgvfw+aOpPqLnBt7bXCo1FYiFCJWkDbGgc75I0bRqLkWqf324eMdCGRnA w6SVZKemVaE+cvAN03CfLzrlKOpG4NGnm6JDlwUPfE5RSOlXoUvSqgsqshgu0w4Zs1Pu ti4Q== X-Gm-Message-State: AOPr4FXaWJ0bak9HMom8XRGdQCl7sgMvQx1mExRBuvrTiBmrf83Sk47nPygPdLURrEsfSw== X-Received: by 10.194.19.197 with SMTP id h5mr6814135wje.139.1461010028953; Mon, 18 Apr 2016 13:07:08 -0700 (PDT) Received: from osk.homenet ([2001:470:196e:13:f2de:f1ff:fed1:783c]) by smtp.googlemail.com with ESMTPSA id r10sm53691729wjf.2.2016.04.18.13.07.08 for (version=TLSv1/SSLv3 cipher=OTHER); Mon, 18 Apr 2016 13:07:08 -0700 (PDT) Subject: Re: Raid 1+0 To: freebsd-questions@freebsd.org References: <571533F4.8040406@bananmonarki.se> From: Shamim Shahriar Message-ID: <57153E6B.6090200@gmail.com> Date: Mon, 18 Apr 2016 21:07:07 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <571533F4.8040406@bananmonarki.se> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 20:07:12 -0000 On 18/04/2016 20:22, Bernt Hansson wrote: > Hello list > > > Used gstripe to stripe the arrays raid/r0 + r1 into stripe0 > Hi I'm sure there are people with more expertise than I am, and they can confirm either ways. But in my mind, given that you used RAID1 first (mirror) and then used those two RAID1 to create a RAID0, this is logically RAID 1+0. In other words, if you lose one disc from each of the RAID1 you are still safe. If you lose both from one single mirror array (highly unlikely), the stripe is unlikely to be of any use. Hope this helps From owner-freebsd-questions@freebsd.org Mon Apr 18 20:56:11 2016 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 DB52CB13614 for ; Mon, 18 Apr 2016 20:56:11 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.70.90]) by mx1.freebsd.org (Postfix) with ESMTP id B3BA819BC for ; Mon, 18 Apr 2016 20:56:11 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id 3C17CCB8CA2; Mon, 18 Apr 2016 15:56:05 -0500 (CDT) Received: from 128.135.52.6 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Mon, 18 Apr 2016 15:56:05 -0500 (CDT) Message-ID: <31454.128.135.52.6.1461012965.squirrel@cosmo.uchicago.edu> In-Reply-To: <20160418204526.GA86917@neutralgood.org> References: <20160417072641.GA2358@c720-r292778-amd64> <20160417093957.0b1acb4c37d7c15a4b06af88@sohara.org> <20160418065534.GA2198@c720-r292778-amd64> <20160418204526.GA86917@neutralgood.org> Date: Mon, 18 Apr 2016 15:56:05 -0500 (CDT) Subject: Re: tool for mapping away bad blocks on an external disk From: "Valeri Galtsev" To: "Kevin P. Neal" Cc: freebsd-questions@freebsd.org 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 20:56:12 -0000 On Mon, April 18, 2016 3:45 pm, Kevin P. Neal wrote: > On Mon, Apr 18, 2016 at 08:55:34AM +0200, Matthias Apitz wrote: >> >> Thanks for all the hints; I started last night with overwriting the full >> disk with: >> >> # dd conv=noerror if=/dev/zero of=/dev/da0 bs=1m > > Just curious: Does anyone know what happens when there is not enough space > at the end of a disk (or tape) to write the entire block? Does a partial > block get written, or does no block get written? As far as I understand, block device (/dev/da0) operations are "quantized" in size of blocks the device reports to the system. (which are either 512 bytes or 4kbytes on most modern 4kn drives) So, the last thing that will happen is: last writable block will be fully written, then as next block is beyond the device border error will be reported. So, you will never have "few bits at the end of drive" not overwritten by dd command above. Valeri > > It is because I don't know what happens that I usually pick a block size > that is mathematically factored out from the number of blocks on the disk > (and then multiplied by the number of bytes in a block obviously). > -- > Kevin P. Neal http://www.pobox.com/~kpn/ > > "Good grief, I've just noticed I've typed in a rant. Sorry chaps!" > Keir Finlow Bates, circa 1998 > _______________________________________________ > 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 Mon Apr 18 21:33:34 2016 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 DA8BFB13595 for ; Mon, 18 Apr 2016 21:33:34 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::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 70EC31952 for ; Mon, 18 Apr 2016 21:33:34 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wm0-x234.google.com with SMTP id u206so355538wme.1 for ; Mon, 18 Apr 2016 14:33:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-transfer-encoding; bh=lD6IvDXRODbtMGvny7J6oCVmb+lnc24QmYQvtPkiAvE=; b=waEDQuxWMb5L7D71fVHRc2D0N0/PzAK+pcO0FY39n9NYhkcHaKsN1wG1261hpFrMmx dtqN91lkmshUQois4uWnn9BxhTrwV5BbBvyiyiE+K0ybMzpWwKJHnfXQY+mYn0aRdsYa 5ZJumtFguIsdzyHseUUASQtKwpW0htQJ6F4IB8SzV/KCGzwNdp+XvVpHu6unbaS/FysP 4TbzUGhjGFUh5yzcF3TWIDznntvNcQpCzgIsHFXPn2ohz30E/luxM49xsDA37tBDdOUV M8dA2JLaN9vXrBfG2SKTYmnnH1temoX5oaK69vnTtp6E5BZIoJCXsrDhj7B7rlU3miKr PgQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=lD6IvDXRODbtMGvny7J6oCVmb+lnc24QmYQvtPkiAvE=; b=S0ZxRDwwlg018fSblRIj5HbHctbz/0rT+YKLt7Ev3acT9pp7xQqRQwfh/S3/Ayjl87 qdFUjoNNLY0cyXOQ25abenqUhsBxLRdgbr++cN6QWdV616UHY2kSs4MWl4CjPd+fRkmA Dt1zV/GcJ+aknJnwjSFlCJmJHXnc3yfHVHVyP5AC9oew7v40RMnuMgVnoqTwZniqUx0I 1hO6wmeIjG9XX6p35aCpPCu8PevFHMqJGpx8j8USS/4JAw5dYpNSwuUJ18Wkx5ql2fYe PRDncQwXEmICHZiOrVKfK0q+ZcPoHrGPxDJgoZsnZvd4hH5nuik3Wk/QTEyl1WSV3ph3 AjHQ== X-Gm-Message-State: AOPr4FUvYafc8ztwrAOJQLLw2x/gi8QnWOhu16mU3ZZnIPAZ/XvnM5/lzJWlf1GdQBELBw== X-Received: by 10.194.107.74 with SMTP id ha10mr37846714wjb.24.1461015212702; Mon, 18 Apr 2016 14:33:32 -0700 (PDT) Received: from gumby.homeunix.com ([90.195.213.141]) by smtp.gmail.com with ESMTPSA id c187sm788437wme.16.2016.04.18.14.33.31 for (version=TLSv1/SSLv3 cipher=OTHER); Mon, 18 Apr 2016 14:33:31 -0700 (PDT) Date: Mon, 18 Apr 2016 22:33:30 +0100 From: RW To: freebsd-questions@freebsd.org Subject: Re: tool for mapping away bad blocks on an external disk Message-ID: <20160418223330.48d246e3@gumby.homeunix.com> In-Reply-To: <31454.128.135.52.6.1461012965.squirrel@cosmo.uchicago.edu> References: <20160417072641.GA2358@c720-r292778-amd64> <20160417093957.0b1acb4c37d7c15a4b06af88@sohara.org> <20160418065534.GA2198@c720-r292778-amd64> <20160418204526.GA86917@neutralgood.org> <31454.128.135.52.6.1461012965.squirrel@cosmo.uchicago.edu> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd10.2) 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 21:33:35 -0000 On Mon, 18 Apr 2016 15:56:05 -0500 (CDT) Valeri Galtsev wrote: > On Mon, April 18, 2016 3:45 pm, Kevin P. Neal wrote: > > On Mon, Apr 18, 2016 at 08:55:34AM +0200, Matthias Apitz wrote: > >> > >> Thanks for all the hints; I started last night with overwriting > >> the full disk with: > >> > >> # dd conv=noerror if=/dev/zero of=/dev/da0 bs=1m > > > > Just curious: Does anyone know what happens when there is not > > enough space at the end of a disk (or tape) to write the entire > > block? Does a partial block get written, or does no block get > > written? > > As far as I understand, block device (/dev/da0) operations are > "quantized" in size of blocks the device reports to the system. > (which are either 512 bytes or 4kbytes on most modern 4kn drives) FWIW FreeBSD hasn't had block devices for a long time. It's true that drives don't have fractional sectors, but I think the block referred to is the block size in the dd command. The dd man page does refer to writing partial blocks: "A partial output block is one where less than the output block size was written. Partial output blocks to tape devices are considered fatal errors. Otherwise, the rest of the block will be written. Partial output blocks to character devices will produce a warning message." From owner-freebsd-questions@freebsd.org Mon Apr 18 22:05:23 2016 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 E89DDB132BA for ; Mon, 18 Apr 2016 22:05:23 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.70.90]) by mx1.freebsd.org (Postfix) with ESMTP id AF1491D59 for ; Mon, 18 Apr 2016 22:05:23 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id 841D8CB8CA2; Mon, 18 Apr 2016 17:05:22 -0500 (CDT) Received: from 128.135.52.6 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Mon, 18 Apr 2016 17:05:22 -0500 (CDT) Message-ID: <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> In-Reply-To: <20160418210257.GB86917@neutralgood.org> References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> Date: Mon, 18 Apr 2016 17:05:22 -0500 (CDT) Subject: Re: Raid 1+0 From: "Valeri Galtsev" To: "Kevin P. Neal" Cc: "Shamim Shahriar" , freebsd-questions@freebsd.org 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 22:05:24 -0000 On Mon, April 18, 2016 4:02 pm, Kevin P. Neal wrote: > On Mon, Apr 18, 2016 at 09:07:07PM +0100, Shamim Shahriar wrote: >> On 18/04/2016 20:22, Bernt Hansson wrote: >> > Hello list >> > >> > >> > Used gstripe to stripe the arrays raid/r0 + r1 into stripe0 >> > >> Hi >> >> I'm sure there are people with more expertise than I am, and they can >> confirm either ways. But in my mind, given that you used RAID1 first >> (mirror) and then used those two RAID1 to create a RAID0, this is >> logically RAID 1+0. In other words, if you lose one disc from each of >> the RAID1 you are still safe. If you lose both from one single mirror >> array (highly unlikely), the stripe is unlikely to be of any use. > > Not that unlikely. If you take identical disks from the same company and > subject them to identical load then the probability that they will fail > around the same time is much higher than random. Not correct. First of all, in most of the cases, failure of each of the drives are independent events (unless you do weird thing such as you have huge RAID with many drives and you never scan the whole surface of each drive, then failure of one drive and the need to rebuild RAID may trigger discovery of another "bad" drive but strictly speaking, the other drive was in that bad state earlier, say with huge bad area you never tried to access, so these events are not simultaneous, and situation can be avoided by correct RAID configuration: scan surface of drives periodically!). Now, let's take a look at the event of simultaneous failure of two drives. Let me call "simultaneous" a failure of second drive within time interval necessary to rebuild array after first drive failure. Let's consider this time to be as long as 3 days (my RAIDs rebuild much faster). Now, let's deal with RAID array with 6 years old drives. What percentage of drives that die between their 6th and 7th years in service? Let's take really big number: 1%. (I'm lucky, my drive longevity is better). So probability that a drive dies during particular 3 days near its 6 years of age will be 0.01 * 3 (days) / 365 (days) so it is about ten to minus fourth power (0.0001). Now, probability of two drives dying simultaneously (or rather second drive dying within 3 days of first drive), as these two events are independent, is just a product of probabilities of each of events, so it is probability of single event squared. That will be ten to minus 8th power (0.00000001) Note that while the event of single drive though not that likely, still is observable, the event of two drives dying simultaneously (we estimated it for one withing 3 days of another) is way less likely. So, I would say, provided RAID configured well, it is quite unlikely you will have two drives die on you (be are the same manufacturer/model/batch or something absolutely different). The RAID horror stories - which I have heard myself not once including from people who it happened to - when several drives die "simultaneously" are under further scrutiny just poorly configured RAIDs. Namely, several drives are sort of dead and sit like that waiting the moment one drive is actually kicked out of array, triggering array rebuild, and thus triggering access to the whole surface of all drives, and discovery of other drives that were sitting "almost dead" undiscovered just because "raid verification" was not run every so often. I find even with verification of drive full surface scan as rare as 1 Month I am reasonably safe from hitting multiple drives die leading to data loss. Somebody with better knowledge of probability theory will correct me if I'm wrong some place. This, of course, has nothing to do with occasional "small" data loss if no other measures but just having data on RAID are taken. What I mean here is, RAID has no ultimately reliable mechanism to discover which of drives gives corrupted stripe on read (due to not correctly recovered by drive firmware content of bad block) - if checksum doesn't match in RAID-5 there is no way to figure mathematically which stripe is corrupted (one could suspect particular drive if its response time is slower, as its firmware might be busy attempting to recover data by multiple read and superimposition of results). With RAID-6 situation is better, as excluding one of the drives at a time you can discover self - consistent group of N-1 drives, thus knowing the stripe on which drive you need to correct. But I'm not sure RAID adapter firmware indeed does it. Which leads us to conclusion: we need to take advantage of filesystems ensuring data integrity (zfs comes to my mind). Valeri > > That's why when I set up a mirror I always build it with drives from > different companies. And I make it a three way mirror if I can. > -- > Kevin P. Neal http://www.pobox.com/~kpn/ > > "Good grief, I've just noticed I've typed in a rant. Sorry chaps!" > Keir Finlow Bates, circa 1998 > _______________________________________________ > 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 Mon Apr 18 22:05:51 2016 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 ED996B13346 for ; Mon, 18 Apr 2016 22:05:51 +0000 (UTC) (envelope-from brandon.wandersee@gmail.com) Received: from mail-io0-f169.google.com (mail-io0-f169.google.com [209.85.223.169]) (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 C654E1E0F for ; Mon, 18 Apr 2016 22:05:51 +0000 (UTC) (envelope-from brandon.wandersee@gmail.com) Received: by mail-io0-f169.google.com with SMTP id u185so894354iod.3 for ; Mon, 18 Apr 2016 15:05:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:user-agent:from:to:cc:subject :in-reply-to:date:message-id:mime-version; bh=LuzIaBh/izUkqVoCaLORrHp+hH8uSJ1CBfJFYrmxUwY=; b=d0hkxdD3LWYXeyJCqrYjBAUAtsICB2o4Wv/WZqKOhMIOLx98sjwxGSDa4uK6WlsSdd tBvX3uRaMc17TRbcbXe+roP5X6t3hwu8MT7+WCinNjuW+0+zZpemMgSwXN124ja9QHOr ElOEltsrRonHLMFe4OTvWiDeUUzhQmcGyNlJaDJS8eGRZtrZqG+fY1+FjXYyQTBIcEYY Fpg1VSfLwCLUKr/NNcq9p9wGJQK4P5nrwii4iYTPvTRkO70M1eOZLcKF1ofYJFtmiwKY agKp80+v3XorUy/0UKimjX8O/9I3oxlmWdvgHwDLR4DEmy5kwvVUu+yYrampoI/o3/HJ CWEQ== X-Gm-Message-State: AOPr4FXBWCQlAWkvLeldJwYlV5JHQ8ccgR+b1n+XveFyUAqJ9KC9H3+VFLiaZfpmv3/svA== X-Received: by 10.107.52.12 with SMTP id b12mr175195ioa.6.1461017145146; Mon, 18 Apr 2016 15:05:45 -0700 (PDT) Received: from WorkBox.Home.gmail.com (97-116-17-82.mpls.qwest.net. [97.116.17.82]) by smtp.gmail.com with ESMTPSA id zy9sm504675igc.13.2016.04.18.15.05.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Apr 2016 15:05:44 -0700 (PDT) References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> User-agent: mu4e 0.9.16; emacs 24.5.1 From: Brandon J. Wandersee To: "Kevin P. Neal" Cc: Shamim Shahriar , freebsd-questions@freebsd.org Subject: Re: Raid 1+0 In-reply-to: <20160418210257.GB86917@neutralgood.org> Date: Mon, 18 Apr 2016 17:05:44 -0500 Message-ID: <86k2jupo7b.fsf@WorkBox.Home> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 22:05:52 -0000 Kevin P. Neal writes: > On Mon, Apr 18, 2016 at 09:07:07PM +0100, Shamim Shahriar wrote: >> On 18/04/2016 20:22, Bernt Hansson wrote: >> > Hello list >> > >> > >> > Used gstripe to stripe the arrays raid/r0 + r1 into stripe0 >> > >> Hi >> >> I'm sure there are people with more expertise than I am, and they can >> confirm either ways. But in my mind, given that you used RAID1 first >> (mirror) and then used those two RAID1 to create a RAID0, this is >> logically RAID 1+0. In other words, if you lose one disc from each of >> the RAID1 you are still safe. If you lose both from one single mirror >> array (highly unlikely), the stripe is unlikely to be of any use. > > Not that unlikely. If you take identical disks from the same company and > subject them to identical load then the probability that they will fail > around the same time is much higher than random. > > That's why when I set up a mirror I always build it with drives from > different companies. And I make it a three way mirror if I can. Sorry to drag this off-topic, but I've heard this advice more than once now, and have to ask: when you say "same company," do you mean same vendor or same manufacturer? I thought having all disks be of the same make and model was ideal, as it avoids problems arising from the different ways each manufacturer fudges their total disk capacity. If I'm wrong, how so? If you mean buying disks of the same make and model from different vendors is ideal, what's the reasoning there? -- :: Brandon J. Wandersee :: brandon.wandersee@gmail.com :: -------------------------------------------------- :: 'The best design is as little design as possible.' :: --- Dieter Rams ---------------------------------- From owner-freebsd-questions@freebsd.org Mon Apr 18 22:21:28 2016 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 3047EB1380F for ; Mon, 18 Apr 2016 22:21:28 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E911618B3 for ; Mon, 18 Apr 2016 22:21:27 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id u3IMLQ7x004137 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 18 Apr 2016 16:21:26 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id u3IMLQx6004134; Mon, 18 Apr 2016 16:21:26 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 18 Apr 2016 16:21:26 -0600 (MDT) From: Warren Block To: "Kevin P. Neal" cc: freebsd-questions@freebsd.org Subject: Re: tool for mapping away bad blocks on an external disk In-Reply-To: <20160418204526.GA86917@neutralgood.org> Message-ID: References: <20160417072641.GA2358@c720-r292778-amd64> <20160417093957.0b1acb4c37d7c15a4b06af88@sohara.org> <20160418065534.GA2198@c720-r292778-amd64> <20160418204526.GA86917@neutralgood.org> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Mon, 18 Apr 2016 16:21:26 -0600 (MDT) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 22:21:28 -0000 On Mon, 18 Apr 2016, Kevin P. Neal wrote: > On Mon, Apr 18, 2016 at 08:55:34AM +0200, Matthias Apitz wrote: >> >> Thanks for all the hints; I started last night with overwriting the full >> disk with: >> >> # dd conv=noerror if=/dev/zero of=/dev/da0 bs=1m > > Just curious: Does anyone know what happens when there is not enough space > at the end of a disk (or tape) to write the entire block? Does a partial > block get written, or does no block get written? It writes the partial block. Or at least I've never bothered doing anything special, and the checksums work out. > It is because I don't know what happens that I usually pick a block size > that is mathematically factored out from the number of blocks on the disk > (and then multiplied by the number of bytes in a block obviously). You work too hard. :) From owner-freebsd-questions@freebsd.org Mon Apr 18 22:26:38 2016 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 29B26B13A5D for ; Mon, 18 Apr 2016 22:26:38 +0000 (UTC) (envelope-from shamim.shahriar@gmail.com) Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A9F041B52 for ; Mon, 18 Apr 2016 22:26:37 +0000 (UTC) (envelope-from shamim.shahriar@gmail.com) Received: by mail-wm0-x231.google.com with SMTP id 127so1151448wmz.0 for ; Mon, 18 Apr 2016 15:26:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=aKvoZPMWa5P/q4fNH8HrYntvzzY3Q6+AAVZEos1Zrq4=; b=HTsDWHxlHVmE7D4WEfiT3LvgqOk5gDZsluN58Xts/DIWuxl6vLPhng+/qaKV6iqfFt EMAwaw2Xm2ukGvkG4/xqiVE8Rx9cXUjqpAOO6PTpabUjSYG5I9A8wkTkCdAajPX8Rlfe Y3qgRg4IXXL7BCSOBFjo6Mu/cCgLALVp6oruk9MbcnQ64jSsFD5JLzS4icwt7+XsEWYC W0kzseRRBHmIiL13M4d/7N2q2EYUg7pQ3EflUcykdIafeW6uO1ygzGVgkwqMhxcSx4K+ lFFRwk5V3NP4VSpFeFdVW1oQURwJGvQUAYGfzwZEDPkiasiGQ7METX31q+PgHljc9WxY fNEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=aKvoZPMWa5P/q4fNH8HrYntvzzY3Q6+AAVZEos1Zrq4=; b=OVQNO4mslYm0ih2sKMiF9yNq6PWOGhhjUEw2728udXmW2Xn2Cc4wI4wjf1stebjNkj ynS+Jj04JwXAqN8qjZN1FCXwk5AbvhUtSSwjZoAjhXKstKm4oszd7O1gmNv8nAm2GoRy eOkEwE9QdOPkWauZIkfXm5VAFJ2gjWoABAQt9EFG+B4b7+Eo6s/wHNW+oxM6hkCSjIIC bBeDiXw7IgXbm4WQtuBgj5jtUH5y/gRwraF07fMap4mVBz0/xioQqAbFw/8ihk88tUts XNsMnKaL0HrSasR7qThhI4cHwKOHsArbNVEJfHLUZvjwKRVbRHvI8xVOwn9pPvNjM7KT ZBPA== X-Gm-Message-State: AOPr4FWt+bVBp2Oz1B8HKhcNaLyCim9o5Hqc4YaHsZ5GNFrHM1wCkq/G4etPgfKgnU8CBg== X-Received: by 10.28.144.8 with SMTP id s8mr20111373wmd.39.1461018395382; Mon, 18 Apr 2016 15:26:35 -0700 (PDT) Received: from osk.homenet ([2001:470:196e:13:f2de:f1ff:fed1:783c]) by smtp.googlemail.com with ESMTPSA id kq9sm66276064wjc.26.2016.04.18.15.26.34 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 18 Apr 2016 15:26:34 -0700 (PDT) Subject: Re: Raid 1+0 To: "Brandon J. Wandersee" , "Kevin P. Neal" References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <86k2jupo7b.fsf@WorkBox.Home> Cc: freebsd-questions@freebsd.org From: Shamim Shahriar X-Enigmail-Draft-Status: N1110 Message-ID: <57155F19.6090203@gmail.com> Date: Mon, 18 Apr 2016 23:26:33 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <86k2jupo7b.fsf@WorkBox.Home> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 22:26:38 -0000 On 18/04/2016 23:05, Brandon J. Wandersee wrote: > Kevin P. Neal writes: > >> On Mon, Apr 18, 2016 at 09:07:07PM +0100, Shamim Shahriar wrote: >>> On 18/04/2016 20:22, Bernt Hansson wrote: >>>> Hello list >>>> >>>> >>>> Used gstripe to stripe the arrays raid/r0 + r1 into stripe0 >>>> >>> Hi >>> >>> I'm sure there are people with more expertise than I am, and they can >>> confirm either ways. But in my mind, given that you used RAID1 first >>> (mirror) and then used those two RAID1 to create a RAID0, this is >>> logically RAID 1+0. In other words, if you lose one disc from each of >>> the RAID1 you are still safe. If you lose both from one single mirror >>> array (highly unlikely), the stripe is unlikely to be of any use. >> Not that unlikely. If you take identical disks from the same company and >> subject them to identical load then the probability that they will fail >> around the same time is much higher than random. >> >> That's why when I set up a mirror I always build it with drives from >> different companies. And I make it a three way mirror if I can. > Sorry to drag this off-topic, but I've heard this advice more than once > now, and have to ask: when you say "same company," do you mean same > vendor or same manufacturer? I thought having all disks be of the same > make and model was ideal, as it avoids problems arising from the different > ways each manufacturer fudges their total disk capacity. If I'm wrong, > how so? If you mean buying disks of the same make and model from > different vendors is ideal, what's the reasoning there? > > Oh No! now you have initiated what we call a "holy war" :P :P :P There are schools that advocate on either sides. Personally, I am yet to encounter any issues arising from drives from the same vendor same batch same shipment -- and that is over the last thirty odd years. I generally tend to change the drives from the array every 3 years (if not earlier), keep additional backup (when it is practical) -- and have not had any issues. On the other hand, I'm sure plenty of people on this list had issues and have vowed never to use identical drives on their array. As for drive failure probability -- as the probability theory says -- the chance might be infinitesimally small, but never zero. So yes, you /might/ loose a disc due to solar radiation, higher temperature on the server cabinet, misconfiguration on your array (different sized drive can sometimes be confusing, you accommodate for the lowest size, but the bigger one has no way of automagically distribute data for the areas it is not using) -- and so many unpredictable/unforeseen/unaccounted for reasons. But those situations aside, as stated, I have lost drives for various other reasons, but not from a raid array and definitely not because they were from the same batch/make/model. And again, with all due respect, I know there are people who did lose drive and eventually the data, and have vowed never to use drives from same vendor/supplier in the same array, and I respect that. Just stating I never had that issue. Hope this helps. From owner-freebsd-questions@freebsd.org Tue Apr 19 03:23:05 2016 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 2A8EEB13BEC for ; Tue, 19 Apr 2016 03:23:05 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E661610E7 for ; Tue, 19 Apr 2016 03:23:04 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1asMFc-0003gP-57 for freebsd-questions@freebsd.org; Tue, 19 Apr 2016 05:22:56 +0200 Received: from pool-72-66-1-32.washdc.fios.verizon.net ([72.66.1.32]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 19 Apr 2016 05:22:56 +0200 Received: from nightrecon by pool-72-66-1-32.washdc.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 19 Apr 2016 05:22:56 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Michael Powell Subject: Re: Raid 1+0 Date: Mon, 18 Apr 2016 23:23:54 -0400 Lines: 49 Message-ID: References: <571533F4.8040406@bananmonarki.se> Reply-To: nightrecon@hotmail.com Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pool-72-66-1-32.washdc.fios.verizon.net X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 03:23:05 -0000 Bernt Hansson wrote: > Hello list > > My motherboard has a raid chip on it (AMD SB750), so my plan was to use > it. Since i never used the chip for raid, i thought i might try. > > So far this has been done. > > Set up 2 arrays with 2 discs in each array with raid1 on both. > > Boot up freebsd 10.3-R. Both arrays are found > > GEOM_RAID: Promise: Disk ada0 state changed from NONE to ACTIVE. > GEOM_RAID: Promise: Subdisk RAID 1 LD 1:0-ada0 state changed from > NONE to ACTIVE. > GEOM_RAID: Promise: Disk ada1 state changed from NONE to ACTIVE. > GEOM_RAID: Promise: Subdisk RAID 1 LD 1:1-ada1 state changed from > NONE to ACTIVE. > GEOM_RAID: Promise: Volume started. > GEOM_RAID: Promise: Volume RAID 1 LD 1 state changed from STARTING to > OPTIMAL. > GEOM_RAID: Promise: Provider raid/r0 for volume RAID 1 LD 1 created. > GEOM_RAID: Promise: Disk ada2 state changed from NONE to ACTIVE. > GEOM_RAID: Promise: Subdisk RAID 1 LD 2:0-ada2 state changed from > NONE to ACTIVE. > GEOM_RAID: Promise: Disk ada3 state changed from NONE to ACTIVE. > GEOM_RAID: Promise: Subdisk RAID 1 LD 2:1-ada3 state changed from > NONE to ACTIVE. > GEOM_RAID: Promise: Volume started. > GEOM_RAID: Promise: Volume RAID 1 LD 2 state changed from STARTING to > OPTIMAL. > GEOM_RAID: Promise: Provider raid/r1 for volume RAID 1 LD 2 created. > > Used gstripe to stripe the arrays raid/r0 + r1 into stripe0 > > Newfs/mount all work. My question, is this a raid 1+0 or 0+1? This is RAID 1+0. Characteristics of such gives better I/O performance for lots of small random reads/writes such as the way a database server uses disk. The flip side of this (RAID 0+1) will have better performance for sequential throughput for use such as file server for storing backups and other large files. -Mike From owner-freebsd-questions@freebsd.org Tue Apr 19 07:32:40 2016 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 AF182B1341F for ; Tue, 19 Apr 2016 07:32:40 +0000 (UTC) (envelope-from lokadamus@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 11D8817C5 for ; Tue, 19 Apr 2016 07:32:39 +0000 (UTC) (envelope-from lokadamus@gmx.de) Received: from [192.168.0.143] ([95.91.224.149]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0LgqEs-1bVLGx2agA-00oDYy; Tue, 19 Apr 2016 09:32:33 +0200 Subject: Re: FreeBSD Crashes Intermittently !! To: shahzaib mushtaq References: <56E2E9AC.1040902@gmx.de> <33444.128.135.52.6.1457712900.squirrel@cosmo.uchicago.edu> <56E2F586.9000108@gmx.de> Cc: freebsd-questions@freebsd.org, galtsev@kicp.uchicago.edu From: "lokadamus@gmx.de" Message-ID: <5715DF0F.4090808@gmx.de> Date: Tue, 19 Apr 2016 09:32:31 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:FCdMo2uueml5DOmKzWr9S27nX4DhUwwjJ9m13y2NlWyZxBO75Jk 6mGArnUG8T7kxy5CIHfCFg6CrLSUAzWc1u9NsQzfQAtM4nzI1AYGNgrbIiwc2YAHKWNO2oZ V/sLMSxS0/4faAw6DSvamHEa+FX/x/3Z9VrQeyh44nj7UcFCoUC/xPZaxwUTxs6oEScCdOO Ecsh/hk94ZTUmDH9BP+Hw== X-UI-Out-Filterresults: notjunk:1;V01:K0:nMbQ0RyMAa0=:4COYMIorrxYJLabF8S7QEs N3FyTah7iJld1Wz1d4DldIMCXxmN0QscWvkRISdXNFtrjRCpPYG9aaX+qDWpRHNP3vMokS54P DuozPe5XpnCEUmgyTYDST3T2yAFptAD7Xd1d0ZjkJmaUzBevx4/Nh8aRaXoi3tUkid8WiqvCC yFGPeA9sWB0rXlM3G7zGKsbSqXwb+7avpQBNtXQBnKon3oTyzllZr9ng1wSjRLh7jwZZR5qio sbDB58xskbT7M5v0Vecd5OPntZhHNCmnLZ8TnzhF6lDzBFFUNjReLgQ8X9lkzpUiMQoI4qEvX TVkmjvr5tRD09E0woEUt+W5FVz8LS6MXzO5zVRnDN6BKOM9P7NPZpzuV2ugrSJTePDVIeyfDK 6KxfjMeGMrZL2TUB8aXH3jabTjtO+C6uTzS12nwomwqtgHK1CA2Oz94r198S3ZcXuU1pJqxdc 4kRI8FBQ/3XHsv7XsFZrt+jgcNhLgSF9uLG8SjW7PCIko1NcMSHkCk4rPY9rjCO12bMukMspx QtQeAKwHuFicqbu01JuzOPvUeDyMDx/MY6rVqDqy0sghbFiiwpWzy6TU3k0rS/wRv//+HJQBB LUCRwimaAVAkEcq7k3869Q9fAhusPZ+eoTEW0M4DbKxtoga4oF/ZAryx24F7gL2n/8VENYhV0 G3sv9QsPB9JzLK7ZDcJBLFkAWmUWR3UHUzSWjrn9QztgI5TmvUgJuL7tldn6Yo0wa3m4M7VBY AtcjlMVc7rgL3cytK4rR/bCFGLFpeTNySnttVdczNEZdro/ODPwUe4NhqgWFcneXO39pzVV9S 1xHtH0PQnV5veXLp0UJY+8f1DTBKg== X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 07:32:40 -0000 On 04/18/16 16:28, shahzaib mushtaq wrote: > Hi again, got back after a long time. So yes, we've move to new Dell R510 > Hardware now. Here is the specs : > > DELL R510 > 2 x L5520 > 64GB RAM > 12x3TB Raid stripping+mirroring (HBA LSI-9211-fw version 19.00) > FreeBSD cw009.tunefiles.com 10.2-RELEASE-p14 FreeBSD 10.2-RELEASE-p14 #0: > Wed Mar 16 20:46:12 UTC 2016 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC > amd64 > > After 9days of uptime, server again got crashed with following error in > crash log : > > http://pastebin.com/baShWuMP > > I am so much depressed now, there's much pressure on me from my company. Please > help us resolving this crash issue . :( Which CPU Model is installed? Is it one or more? There where some microcode updates for some models. Greeting From owner-freebsd-questions@freebsd.org Tue Apr 19 07:35:27 2016 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 3CD39B136D2 for ; Tue, 19 Apr 2016 07:35:27 +0000 (UTC) (envelope-from shahzaib.cb@gmail.com) Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 05FCF1D1B for ; Tue, 19 Apr 2016 07:35:27 +0000 (UTC) (envelope-from shahzaib.cb@gmail.com) Received: by mail-ig0-x234.google.com with SMTP id g8so9503593igr.0 for ; Tue, 19 Apr 2016 00:35:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=lLjmhGva9tWvVloFAbQa81xCw07wpmUE27bhPIvP6S4=; b=yRqFzVhKNyF3YqbABNdixW/3T0KJaiPzCjBaF2MtC6x7e2JI5CZPHxlkl3oWPsdfXU VA6pVYejn3L9bvFKauW35XjvqCQNdnZaTScuAZiifmJaZbGJOHsoaT5mVQwDunBaX6wf ZA8IFXphN3I3hm3uu+nfYo+Ke7GGpsODt9jDFMLGvSaIibKm5LMkd+LU2KMtOoq+ZIGh 5Y3FudnKNU9J6dmYiNYT3ai8o3lSy8aLcDvqytoFcsE9EpCUrzfWNOWYSq5iPfpeUkDY cjqXfD2DUenN4XlxRxDBkVZUesgXglUGgJYXVKnJsydEoSmguvGU2zMb/+Q0avg/A8sT l2Uw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=lLjmhGva9tWvVloFAbQa81xCw07wpmUE27bhPIvP6S4=; b=Z5DEBsFVoZwfiW5R0ZqVTXHAgxFcsH0Qb5rMiK+KsPiwLR5ExT4WIUdsKjAGi1MmKs SMkcEsJybhoMMm6xKs/dB5ynn+kJwkcttpU8kaPPYqeUCfKvEqJytlU3J8wz25FTor90 xB6BQQrZlHYs69Rq5poFExNo9wVe/KSsnws3Cv4vw6IZDQsbGdQroEZf7+HMekZg4eQj 27/nVrfDqDPT45j6Ugq0UIVUgEkHd9cfbJl2meYEPJJJM2RB4bGFB6xYo7ndMWMAR3Hx 82E3eXJXfNKwOrN4hhTc803y4+yveQTlSkK6T1vCBqfir1VSzbru6J3LQvpf4n5Ftbv6 gbdQ== X-Gm-Message-State: AOPr4FXi4KPd79FYko2CY5XPuQtV+RAyFBjRkeHFxdiBBpcTyXDz6YGa33m2yaebEBaV6IQ2ABMSUcUx6G4zjw== MIME-Version: 1.0 X-Received: by 10.50.58.6 with SMTP id m6mr23638464igq.47.1461051326324; Tue, 19 Apr 2016 00:35:26 -0700 (PDT) Received: by 10.79.18.66 with HTTP; Tue, 19 Apr 2016 00:35:26 -0700 (PDT) In-Reply-To: <5715DF0F.4090808@gmx.de> References: <56E2E9AC.1040902@gmx.de> <33444.128.135.52.6.1457712900.squirrel@cosmo.uchicago.edu> <56E2F586.9000108@gmx.de> <5715DF0F.4090808@gmx.de> Date: Tue, 19 Apr 2016 12:35:26 +0500 Message-ID: Subject: Re: FreeBSD Crashes Intermittently !! From: shahzaib mushtaq To: "lokadamus@gmx.de" Cc: freebsd-questions@freebsd.org, galtsev@kicp.uchicago.edu Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 07:35:27 -0000 Hi, sorry for the mistake, cpus are : 2 x Intel(R) Xeon(R) CPU L5640 @ 2.27GHz5640 (12 cores, 24 threads) On Tue, Apr 19, 2016 at 12:32 PM, lokadamus@gmx.de wrote: > On 04/18/16 16:28, shahzaib mushtaq wrote: > > Hi again, got back after a long time. So yes, we've move to new Dell R510 > > Hardware now. Here is the specs : > > > > DELL R510 > > 2 x L5520 > > 64GB RAM > > 12x3TB Raid stripping+mirroring (HBA LSI-9211-fw version 19.00) > > FreeBSD cw009.tunefiles.com 10.2-RELEASE-p14 FreeBSD 10.2-RELEASE-p14 > #0: > > Wed Mar 16 20:46:12 UTC 2016 > > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC > > amd64 > > > > After 9days of uptime, server again got crashed with following error in > > crash log : > > > > http://pastebin.com/baShWuMP > > > > I am so much depressed now, there's much pressure on me from my company. > Please > > help us resolving this crash issue . :( > Which CPU Model is installed? Is it one or more? > > There where some microcode updates for some models. > > Greeting > From owner-freebsd-questions@freebsd.org Tue Apr 19 07:40:57 2016 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 C17E6B13AE1 for ; Tue, 19 Apr 2016 07:40:57 +0000 (UTC) (envelope-from lokadamus@gmx.de) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A64061085 for ; Tue, 19 Apr 2016 07:40:57 +0000 (UTC) (envelope-from lokadamus@gmx.de) Received: by mailman.ysv.freebsd.org (Postfix) id A214DB13AE0; Tue, 19 Apr 2016 07:40:57 +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 9E329B13ADD for ; Tue, 19 Apr 2016 07:40:57 +0000 (UTC) (envelope-from lokadamus@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1560B1083 for ; Tue, 19 Apr 2016 07:40:56 +0000 (UTC) (envelope-from lokadamus@gmx.de) Received: from [192.168.0.143] ([95.91.224.149]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0MBnvD-1b0N1h08Kl-00AmR1; Tue, 19 Apr 2016 09:40:02 +0200 Subject: Re: Upgrading from FreeBSD 4.1 To: Allan Kapoma , 'Erich Dollansky' References: <003401d196ee$258ee680$70acb380$@zamnet.zm> <20160416094349.77f6a883@X220.alogt.com> <00bf01d19949$a9c69080$fd53b180$@zamnet.zm> Cc: 'Nalumino Moola' , questions@freebsd.org From: "lokadamus@gmx.de" Message-ID: <5715E0CD.7090802@gmx.de> Date: Tue, 19 Apr 2016 09:39:57 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: <00bf01d19949$a9c69080$fd53b180$@zamnet.zm> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:3VuRJF6+yKJ/dv64EqZeA2few0JBIw3UO57IzCZ+A+PWliqBaCo 6m+PTlOp5XGLS41F9UNCq7JbRsUUU0cgZySAHkRDgiEJgU+h4JD1KaFuILDCou2wo19qBpz o2Fu1eDhOypmwRB+MlCcnlkU/X7OVQKiNAjQKvG4TddCSY+75cjQCoQ1fgWa7I46frG/Vow J+R+iTZjnXxlAJZnv+4OA== X-UI-Out-Filterresults: notjunk:1;V01:K0:6HXwFK9NXrI=:QYdv9188yIzF4HxLx0UjDS 5C1E3y3OQvFZDti52jPRRqlCxzhArfvQAKIaXv2Xs6YZzrObXNLfDrOsLbtrVS/C3Wz+eFga9 Spy+P7zuEUNMscJ5Ep/VyLk8kEg6ftzKQd1o9ttjBc7V/ksp8FMTca9JgXUpM2Jz4na/TjhRs e2AGuR179cJpIqVSACwM7WVvueVB3RtbJoZiN5jrIDBU4MM+hqJqFKF/pF5OpdFO49ob3F+tD Bd/xs7LiqGRILePCGOKVYM0AUlwxIx2J0Ax9ZoGrDAtrZYE9HzVhvdFVU/1KdpTIFWm3fZBm1 isGKpVXGDrg01jxtDXwMuQlHhC1DDqmjEWQZfYnvP/2FoEa/NEkyH5dI1Dc4VYRPyDdfQ1umD amL9C0fEArulY/dtebyKlLL3vjycCgIWx5LjM2m4McOUTLUv5I7bAPvZT97FpQFAdHkLuAcRF OUIi/04sOZ3bt8XDg3JNv+wTXBmAUC7zREQFI1sn1tSgI5wL9MpYXrBuKFnqoLlNK0Cs/Eqj1 ZuYSnzWVcpCTut9L/JP4hmuCffJbHIr9ABu0v5qoJib65YqWl0vo6Yt5dlo/Yws358i0b2o2Y Ttq5w3SWvGff9Kixgw/EYnoR/6PuUYSwvNLm+n6I1epYFCnff2mqCrkIkBbL4ujIlKukiXf1f M8Jq0XB1ge87X3hEo3v+MMoGM8z7cV0AnTOm+3VCeoMrQ3iEgHEpGA/CjJf+ou6rprB7E8AMO adFF4cAob1k8vDKq/NRLlziqnmc5RaDt46xWp92ZRrgPdvsuXrnuKm6OPxErowuQVA01qml/s svvlNt9l38l2uZxC4wP018ryuKPcA== X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 07:40:57 -0000 Hello Allan, I think he use this methode (make buildworld, make installworld ...) https://www.freebsd.org/doc/handbook/synching.html Regards On 04/18/16 10:09, Allan Kapoma wrote: > Hello Erich > > What command(s) did you used to move from version 4 to 5.21 > > Regards > > > Allan Kapoma|Head of Networks| ZAMNET Communication Systems Limited | > Mobile: +260 962 235839 | Office: +260 211 220736| Fax: +260 211 224775 | > COMESA Center | Ben Bella Road | P.O Box 38299 | Lusaka, 10101 ZAMBIA > |Email: allan.kapoma@zamnet.zm | Website: www.zamnet.zm. > > Nobody Delivers IT Better > > > -----Original Message----- > From: Erich Dollansky [mailto:erichsfreebsdlist@alogt.com] > Sent: 16 April 2016 03:44 > To: Allan Kapoma > Cc: questions@freebsd.org; 'Nalumino Moola' > Subject: Re: Upgrading from FreeBSD 4.1 > > Hi, > > On Fri, 15 Apr 2016 10:09:34 +0200 > "Allan Kapoma" wrote: > >> I'm running FreeBSD 4.10 and I want to upgrade the system to a later >> version of FreeBSD. >> > this is from 2004 and still running. I wonder if you can even update to the > latest version. I have had a notebook, I never brought to 8 as its hardware > was not supported from 8 onward. > > If you really want to update, use sources to move from version to version. I > would move to 5.21 first and the 6.0, 7.0 ... > > It will not be possible to compile new versions with the old compiler you > have. > > The binary upgrade came later. When you have reached that version, you can > go via binary upgrades. > > Of course, you can have a try and move directly to the oldest version > supporting binary upgrades. I only doubt that your old compiler will support > this. > > Good luck. > > Erich > > >> >> >> However, whenever I run commands to update the system (# >> freebsd-update), or install portsnap, or install portmanager, or pkg >> commands, portsnap fetch extract, I'm getting the message that command >> not found >> >> >> >> The my output for uname -a is shown below >> >> >> >> relay# uname -a >> >> FreeBSD relay.zamnet.zm 4.10-RELEASE FreeBSD 4.10-RELEASE #1: Fri Nov >> 12 06:54:4 >> >> >> >> I'm asking for assistance on how I can enable the system (FreeBSD >> 4.10) to run these commands and hopefully update my system and >> packages on it >> >> >> >> Regards >> >> >> >> Allan Kapoma|Head of Networks| ZAMNET Communication Systems Limited | >> >> Mobile: +260 962 235839 | Office: +260 211 220736| Fax: +260 211 >> 224775 | >> >> COMESA Center | Ben Bella Road | P.O Box 38299 | Lusaka, 10101 >> ZAMBIA |Email: allan.kapoma@zamnet.zm >> | Website: www.zamnet.zm. >> >> >> >> Nobody Delivers IT Better >> >> >> >> >> >> _______________________________________________ >> 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 Tue Apr 19 08:27:20 2016 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 0777FB1110A for ; Tue, 19 Apr 2016 08:27:20 +0000 (UTC) (envelope-from lokadamus@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6B2B61E2D for ; Tue, 19 Apr 2016 08:27:18 +0000 (UTC) (envelope-from lokadamus@gmx.de) Received: from [192.168.0.143] ([95.91.224.149]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0LdHLB-1bZz1m4BVJ-00iSud; Tue, 19 Apr 2016 10:27:08 +0200 Subject: Re: FreeBSD Crashes Intermittently !! To: shahzaib mushtaq References: <56E2E9AC.1040902@gmx.de> <33444.128.135.52.6.1457712900.squirrel@cosmo.uchicago.edu> <56E2F586.9000108@gmx.de> <5715DF0F.4090808@gmx.de> Cc: freebsd-questions@freebsd.org, galtsev@kicp.uchicago.edu From: "lokadamus@gmx.de" Message-ID: <5715EBDA.10907@gmx.de> Date: Tue, 19 Apr 2016 10:27:06 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:CTOanJGIiXvYRhFGSliJIGlRi+N/gkujfX/2C6Rg1Mnx9zXMZL1 ujZw/S0IDgcq36b1r+dnSmMRK+kh2Q8amJpRFD8qAhHKQ83opSs01ddlWHBsApjqeVE6nf+ 175D+g/Yd+ifsqVSFnQSB+/L50q8swBPGXjmfwEVTIkbZyHdC/aXGJqyzZWaN0/PjzPfDcR WjB/PhSUoBCHV09f93DFA== X-UI-Out-Filterresults: notjunk:1;V01:K0:vX+PC4cRNSQ=:3mCMY5iw9CTKWFM6ZQwBxM QQDmf3gZgjJR73Jvevf1bPVARK8SziG+btZCM5xk7jwPnM3gBL21EfhNCsBHwCddVY0Ypk9r1 OalkS67i7feLxZoUKGoSJ3vzYrkD+j/HJD4e5wiHH2eSRz4voyBRbFPFy4dZ0vynTCq9/0sUR LUFOmw+1ax2BBO3Oob23FrK01tUJ963y4GI3pcNLZgfoogFOXaWYlTHfFiT//OSjTEiaxY+1l RBInc6C+RzZm6ZlFo7VheeIGE7aSVMN08n7xUWlWGWmmx1qH+ELIRZSemULbf791yhsEOboM/ LCtfMYDS8xzpFYhNG/kqJYFu4b+dGjyvqtttUIhXew6NI3V+oHGjo+BFrb1AouU3Co8E6PnwV oAIeSVRcOiMFaSmj2kM2412f9bGY0b9G7+X79W2xIZn3cLFfwOJVHB//ysolca2WLBjDQV+cG L6WdRwlyMkumOG5o65i+5XgsuRJoG5Wm6GasC7ub3EHoUT9sPAPHFR4442BZbJZhh1BJg3lyP IprEwT9VGW/wxkPmdwdT1l7kC8w9L5uBDTgzCbEY9E9VQHgIlIVUJKnHKlv7dDYXqWNzfoJfv GnqjDFW6ut//7e1J+Bp7YHASuxk9h6O2Z2qyhvUr2XP3sMrbE/w/70892+V/IdIZbch43UI3c p4E9TvO/lmFmJnHgnlSm6QJxq/5O1mLWy0X/Hnkq9phww9sBSoGrg/b3NxwnLsBA4S118mex4 Fesh0ugqvKkFqJ27nnqvsh/3SAQRzHOl7JTbm2xUS9lQ01j4JQ9tDu5ppAE1oJa5yMHGZP8bz V6JAlW8sGikdtiGe3/KOk1dUy4PYQ== X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 08:27:20 -0000 Hi, I think about the error lines: Hardware event. This is not a software error. CPU 23 BANK 5 MISC 0 ADDR 805613c60 MCG status:MCIP STATUS be00000000800400 MCGSTATUS 4 .... Hardware event. This is not a software error. CPU 22 BANK 5 https://en.wikipedia.org/wiki/Machine-check_exception Looks like a hardware problem from the second cpu. Thinks, what can be done: - Is it possible to read cpu heat infos from bios? - Disable HTT and look, if the error comes again - Remove the second cpu and look, if ... - Install microcode updates and hope, it will fix it Intel offers for many CPUs an microcode update. https://downloadcenter.intel.com/download/25512/Linux-Processor-Microcode-Data-File?v=t Can you test a cpu in another system? https://www.freebsd.org/cgi/ports.cgi?query=cpuburn&stype=all Regards On 04/19/16 09:35, shahzaib mushtaq wrote: > Hi, sorry for the mistake, cpus are : > > 2 x Intel(R) Xeon(R) CPU L5640 @ 2.27GHz5640 (12 cores, 24 threads) > > On Tue, Apr 19, 2016 at 12:32 PM, lokadamus@gmx.de wrote: > >> On 04/18/16 16:28, shahzaib mushtaq wrote: >>> Hi again, got back after a long time. So yes, we've move to new Dell R510 >>> Hardware now. Here is the specs : >>> >>> DELL R510 >>> 2 x L5520 >>> 64GB RAM >>> 12x3TB Raid stripping+mirroring (HBA LSI-9211-fw version 19.00) >>> FreeBSD cw009.tunefiles.com 10.2-RELEASE-p14 FreeBSD 10.2-RELEASE-p14 >> #0: >>> Wed Mar 16 20:46:12 UTC 2016 >>> root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC >>> amd64 >>> >>> After 9days of uptime, server again got crashed with following error in >>> crash log : >>> >>> http://pastebin.com/baShWuMP >>> >>> I am so much depressed now, there's much pressure on me from my company. >> Please >>> help us resolving this crash issue . :( >> Which CPU Model is installed? Is it one or more? >> >> There where some microcode updates for some models. >> >> Greeting >> > _______________________________________________ > 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 Tue Apr 19 08:40:03 2016 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 052EFB11578 for ; Tue, 19 Apr 2016 08:40:03 +0000 (UTC) (envelope-from shahzaib.cb@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 C14CF1382 for ; Tue, 19 Apr 2016 08:40:02 +0000 (UTC) (envelope-from shahzaib.cb@gmail.com) Received: by mail-io0-x229.google.com with SMTP id u185so11109131iod.3 for ; Tue, 19 Apr 2016 01:40:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=ZudRbmQibrpSHUkNSc1L2OAyHa08kRQJoCamCaa1pJE=; b=uSSM05AJ4DLiLVYFPp1BH0v1SY9Bu/3vYJ4Y1tfYfnY1EaYwvO0N1VodVuxY/tL0Te PGP3DkaV7gQfbMdd8rYd5h94DyxTjXzb+LBUHdiA3WmxxGX5rGp3UUuJ0WBDpY5u1fv7 36+Sd2jjwDelNHTtOVEHl/Evaabo7wh+jzkcy+V28AFqeWhJF9custiSn5iOJgL0lp30 GGFNBQtsj16Jxc+Ti8cPGSxrllGUiHZli5X+XWB71XndvmWfrnIzP72ZMY+l7GxBOIkZ P48DXbWTQAcSv2R05XLg+xhU3yl/KcbOlB2liGXo06X/ahGW1Z/e/1D+o3dpeWYdu4yb 6qRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=ZudRbmQibrpSHUkNSc1L2OAyHa08kRQJoCamCaa1pJE=; b=BOV0P5F1BN61AmOdo+ZhPedtJvCeE+xq+qf4VeFINuGGyHv6sxJgK/MrD+CPIIatbW VX9jNebH63bIkTEwEAIGfTl1p4Byvfm5FKiz20vmMhdUprHtRSL/Bb7LlqSqZqPL0Zhm WGATiDVSpMS7aDrBU0iO8VVdlLKCTwiarPwG0Of6NQ00Gqw3/zlDmh2p9SqKwhL8iBMc 38Gi9RnaLitwgttNXMuc6K8QaTstHaoJ48UGNuSdBLytsWFjW69jgTatuMgStg5LGuDm zYOsvaS/hRc9oomKYwjTHQM8L8zohycROUih0raanLM7T/hMpRCER3W6r9wEIZHU8jZ2 WE+Q== X-Gm-Message-State: AOPr4FXIOIl9XEeTcxL7hflTAqvFBfCCWWYOD0XEyMC5NXOWEANWlce/5haLVInc3wTkSIPgkLW43aP1sVa5dw== MIME-Version: 1.0 X-Received: by 10.107.18.227 with SMTP id 96mr2215913ios.174.1461055202113; Tue, 19 Apr 2016 01:40:02 -0700 (PDT) Received: by 10.79.18.66 with HTTP; Tue, 19 Apr 2016 01:40:02 -0700 (PDT) In-Reply-To: <5715EBDA.10907@gmx.de> References: <56E2E9AC.1040902@gmx.de> <33444.128.135.52.6.1457712900.squirrel@cosmo.uchicago.edu> <56E2F586.9000108@gmx.de> <5715DF0F.4090808@gmx.de> <5715EBDA.10907@gmx.de> Date: Tue, 19 Apr 2016 13:40:02 +0500 Message-ID: Subject: Re: FreeBSD Crashes Intermittently !! From: shahzaib mushtaq To: "lokadamus@gmx.de" Cc: freebsd-questions@freebsd.org, galtsev@kicp.uchicago.edu Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 08:40:03 -0000 Hi, We don't think its related to heat because L5640 only use 60W. Can we update microcode on FreeBSD? Because intel has not stated this OS when performing microcode update. Regards. On Tue, Apr 19, 2016 at 1:27 PM, lokadamus@gmx.de wrote: > Hi, > > I think about the error lines: > Hardware event. This is not a software error. > CPU 23 BANK 5 > MISC 0 ADDR 805613c60 > MCG status:MCIP > STATUS be00000000800400 MCGSTATUS 4 > .... > Hardware event. This is not a software error. > CPU 22 BANK 5 > > https://en.wikipedia.org/wiki/Machine-check_exception > > Looks like a hardware problem from the second cpu. > Thinks, what can be done: > - Is it possible to read cpu heat infos from bios? > - Disable HTT and look, if the error comes again > - Remove the second cpu and look, if ... > - Install microcode updates and hope, it will fix it > > Intel offers for many CPUs an microcode update. > > https://downloadcenter.intel.com/download/25512/Linux-Processor-Microcode-Data-File?v=t > > Can you test a cpu in another system? > https://www.freebsd.org/cgi/ports.cgi?query=cpuburn&stype=all > > > Regards > > On 04/19/16 09:35, shahzaib mushtaq wrote: > > Hi, sorry for the mistake, cpus are : > > > > 2 x Intel(R) Xeon(R) CPU L5640 @ 2.27GHz5640 (12 cores, 24 threads) > > > > On Tue, Apr 19, 2016 at 12:32 PM, lokadamus@gmx.de > wrote: > > > >> On 04/18/16 16:28, shahzaib mushtaq wrote: > >>> Hi again, got back after a long time. So yes, we've move to new Dell > R510 > >>> Hardware now. Here is the specs : > >>> > >>> DELL R510 > >>> 2 x L5520 > >>> 64GB RAM > >>> 12x3TB Raid stripping+mirroring (HBA LSI-9211-fw version 19.00) > >>> FreeBSD cw009.tunefiles.com 10.2-RELEASE-p14 FreeBSD 10.2-RELEASE-p14 > >> #0: > >>> Wed Mar 16 20:46:12 UTC 2016 > >>> root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC > >>> amd64 > >>> > >>> After 9days of uptime, server again got crashed with following error in > >>> crash log : > >>> > >>> http://pastebin.com/baShWuMP > >>> > >>> I am so much depressed now, there's much pressure on me from my > company. > >> Please > >>> help us resolving this crash issue . :( > >> Which CPU Model is installed? Is it one or more? > >> > >> There where some microcode updates for some models. > >> > >> Greeting > >> > > _______________________________________________ > > 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 Tue Apr 19 09:05:03 2016 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 D481EB125BF for ; Tue, 19 Apr 2016 09:05:03 +0000 (UTC) (envelope-from bourne.identity@hotmail.com) Received: from BLU004-OMC4S8.hotmail.com (blu004-omc4s8.hotmail.com [65.55.111.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 95E181674 for ; Tue, 19 Apr 2016 09:05:03 +0000 (UTC) (envelope-from bourne.identity@hotmail.com) Received: from BLU436-SMTP116 ([65.55.111.136]) by BLU004-OMC4S8.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Tue, 19 Apr 2016 02:03:56 -0700 X-TMN: [RbrBj+3BlsHOHik/RQW/zauPDvnCMl2Z] X-Originating-Email: [bourne.identity@hotmail.com] Message-ID: To: freebsd-questions@freebsd.org From: Manish Jain Subject: Does HP DeskJet 1112 work with lpd on FreeBSD 10.2 amd64 ? Date: Tue, 19 Apr 2016 14:33:00 +0530 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 X-OriginalArrivalTime: 19 Apr 2016 09:03:54.0218 (UTC) FILETIME=[66097CA0:01D19A1A] Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 09:05:03 -0000 Hi, I wished to enquire whether someone has successfully got anHP DeskJet 1112 to work with lpr/lpd on a FreeBSD 10.2 amd64 box. I can't get CUPS to do anything on my system and would like to to use lpd. I am trying to buy a cheap printer and this one fits my budget. Thanks & Regards Manish Jain From owner-freebsd-questions@freebsd.org Tue Apr 19 09:11:34 2016 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 EE121B12854 for ; Tue, 19 Apr 2016 09:11:34 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B30FE1C1B for ; Tue, 19 Apr 2016 09:11:34 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [89.204.138.181] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1asRgp-0004wQ-Su for freebsd-questions@freebsd.org; Tue, 19 Apr 2016 11:11:24 +0200 Received: from localhost.my.domain (c720-r292778-amd64 [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id u3J9BI7R002911 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 19 Apr 2016 11:11:18 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id u3J9BHQv002910 for freebsd-questions@freebsd.org; Tue, 19 Apr 2016 11:11:17 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Tue, 19 Apr 2016 11:11:16 +0200 From: Matthias Apitz To: freebsd-questions@freebsd.org Subject: Re: Does HP DeskJet 1112 work with lpd on FreeBSD 10.2 amd64 ? Message-ID: <20160419091116.GA2877@c720-r292778-amd64> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , freebsd-questions@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT r292778 (amd64) User-Agent: Mutt/1.5.24 (2015-08-30) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 89.204.138.181 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 09:11:35 -0000 El día Tuesday, April 19, 2016 a las 02:33:00PM +0530, Manish Jain escribió: > Hi, > > I wished to enquire whether someone has successfully got anHP DeskJet > 1112 to work with lpr/lpd on a FreeBSD 10.2 amd64 box. I can't get CUPS > to do anything on my system and would like to to use lpd. CUPS works nice for many years on my FreeBSD systems, actually CURRENT. Why you can't get it to do anything on your system? matthias -- Matthias Apitz, ✉ guru@unixarea.de, ⌂ http://www.unixarea.de/ ☎ +49-176-38902045 ¡Dios querido denos otra vez los problemas de ayer, los que tuvimos en la RDA! My Lord, give us back the problems of yesterday, those we have had in the GDR. From owner-freebsd-questions@freebsd.org Tue Apr 19 10:58:31 2016 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 83D03B136CE for ; Tue, 19 Apr 2016 10:58:31 +0000 (UTC) (envelope-from paul@ifdnrg.com) Received: from outbound.ifdnrg.com (outbound.ifdnrg.com [193.200.98.38]) by mx1.freebsd.org (Postfix) with ESMTP id 3071B1AFC for ; Tue, 19 Apr 2016 10:58:30 +0000 (UTC) (envelope-from paul@ifdnrg.com) Received: from [192.168.0.106] (cpc14-sgyl28-2-0-cust626.18-2.cable.virginm.net [82.39.86.115]) (authenticated bits=0) by outbound.ifdnrg.com (8.15.2/8.14.9) with ESMTPSA id u3JAmHf1044359 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Tue, 19 Apr 2016 11:48:45 +0100 (BST) (envelope-from paul@ifdnrg.com) X-Authentication-Warning: outbound.ifdnrg.com: Host cpc14-sgyl28-2-0-cust626.18-2.cable.virginm.net [82.39.86.115] claimed to be [192.168.0.106] To: freebsd-questions@freebsd.org From: Paul Macdonald Subject: oops zfs exec=off (on everything) Message-ID: Date: Tue, 19 Apr 2016 11:48:12 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 10:58:31 -0000 Hi, i just set exec=off on the parent file system on a zfs boot system, and all filesystems are now non executable. suggestions welcome! thanks Paul. -- ------------------------- Paul Macdonald IFDNRG Ltd Web and video hosting ------------------------- t: 0131 5548070 m: 07970339546 e: paul@ifdnrg.com w: http://www.ifdnrg.com ------------------------- IFDNRG 40 Maritime Street Edinburgh EH6 6SA ---------------------------------------------------- Virtual Servers from £50.00pm High specification Dedicated Servers from £150.00pm ---------------------------------------------------- From owner-freebsd-questions@freebsd.org Tue Apr 19 11:01:08 2016 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 37E68B138A3 for ; Tue, 19 Apr 2016 11:01:08 +0000 (UTC) (envelope-from allan.kapoma@zamnet.zm) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 1B9CF1D66 for ; Tue, 19 Apr 2016 11:01:08 +0000 (UTC) (envelope-from allan.kapoma@zamnet.zm) Received: by mailman.ysv.freebsd.org (Postfix) id 1AB81B138A2; Tue, 19 Apr 2016 11:01:08 +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 1A5B2B138A1 for ; Tue, 19 Apr 2016 11:01:08 +0000 (UTC) (envelope-from allan.kapoma@zamnet.zm) Received: from bsf-o-2.zamnet.zm (bsf-o-2.zamnet.zm [196.46.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 5202F1D63 for ; Tue, 19 Apr 2016 11:01:06 +0000 (UTC) (envelope-from allan.kapoma@zamnet.zm) X-ASG-Debug-ID: 1461063655-054b875ac032bc0001-YuSLm7 Received: from smtp.zamnet.zm (smtp.zamnet.zm [196.46.192.20]) by bsf-o-2.zamnet.zm with ESMTP id JMFBqUaA6CYUys7M for ; Tue, 19 Apr 2016 13:00:55 +0200 (CAT) X-Barracuda-Envelope-From: allan.kapoma@zamnet.zm X-Barracuda-Apparent-Source-IP: 196.46.192.20 Received: from allan (pc6-lk.zamnet.zm [196.46.212.70]) by smtp.zamnet.zm (Rockliffe SMTPRA 9.4.1) with ESMTP id ; Tue, 19 Apr 2016 13:00:59 +0200 From: "Allan Kapoma" To: , "'Erich Dollansky'" Cc: "'Nalumino Moola'" , References: <003401d196ee$258ee680$70acb380$@zamnet.zm> <20160416094349.77f6a883@X220.alogt.com> <00bf01d19949$a9c69080$fd53b180$@zamnet.zm> <5715E0CD.7090802@gmx.de> In-Reply-To: <5715E0CD.7090802@gmx.de> Subject: RE: Upgrading from FreeBSD 4.1 Date: Tue, 19 Apr 2016 13:00:46 +0200 X-ASG-Orig-Subj: RE: Upgrading from FreeBSD 4.1 Message-ID: <00ba01d19a2a$b9ac8450$2d058cf0$@zamnet.zm> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQF+Uj+tw+qXgStbtLO+Zz8AExV1BQEOt2vRASIWnOMB+Oi9IKAWYwbQ Content-Language: en-gb X-Barracuda-Connect: smtp.zamnet.zm[196.46.192.20] X-Barracuda-Start-Time: 1461063655 X-Barracuda-URL: http://196.46.192.45:8000/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at zamnet.zm X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.23 X-Barracuda-Spam-Status: No, SCORE=0.23 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=5.0 tests=BSF_SC0_MISMATCH_TO, SH_BIG5_05413_BODY_104, THREAD_INDEX X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.28872 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.01 THREAD_INDEX thread-index: AcO7Y8iR61tzADqsRmmc5wNiFHEOig== 0.00 BSF_SC0_MISMATCH_TO Envelope rcpt doesn't match header 0.21 SH_BIG5_05413_BODY_104 BODY: Body: contain "UNSUBSCRIBE" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 11:01:08 -0000 Thank you, I will look at it give it try Allan Kapoma|Head of Networks| ZAMNET Communication Systems Limited | Mobile: +260 962 235839 | Office: +260 211 220736| Fax: +260 211 224775 = | COMESA =A0Center | Ben Bella Road | P.O Box 38299=A0=A0 | Lusaka, 10101 = ZAMBIA |Email: allan.kapoma@zamnet.zm=A0| Website:=A0 www.zamnet.zm. Nobody Delivers IT Better -----Original Message----- From: lokadamus@gmx.de [mailto:lokadamus@gmx.de]=20 Sent: 19 April 2016 09:40 To: Allan Kapoma ; 'Erich Dollansky' Cc: 'Nalumino Moola' ; questions@freebsd.org Subject: Re: Upgrading from FreeBSD 4.1 Hello Allan, I think he use this methode (make buildworld, make installworld ...) https://www.freebsd.org/doc/handbook/synching.html Regards On 04/18/16 10:09, Allan Kapoma wrote: > Hello Erich >=20 > What command(s) did you used to move from version 4 to 5.21 >=20 > Regards >=20 >=20 > Allan Kapoma|Head of Networks| ZAMNET Communication Systems Limited | > Mobile: +260 962 235839 | Office: +260 211 220736| Fax: +260 211 = 224775 | > COMESA Center | Ben Bella Road | P.O Box 38299 | Lusaka, 10101 = ZAMBIA > |Email: allan.kapoma@zamnet.zm | Website: www.zamnet.zm. >=20 > Nobody Delivers IT Better >=20 >=20 > -----Original Message----- > From: Erich Dollansky [mailto:erichsfreebsdlist@alogt.com] > Sent: 16 April 2016 03:44 > To: Allan Kapoma > Cc: questions@freebsd.org; 'Nalumino Moola' > Subject: Re: Upgrading from FreeBSD 4.1 >=20 > Hi, >=20 > On Fri, 15 Apr 2016 10:09:34 +0200 > "Allan Kapoma" wrote: >=20 >> I'm running FreeBSD 4.10 and I want to upgrade the system to a later=20 >> version of FreeBSD. >> > this is from 2004 and still running. I wonder if you can even update=20 > to the latest version. I have had a notebook, I never brought to 8 as=20 > its hardware was not supported from 8 onward. >=20 > If you really want to update, use sources to move from version to=20 > version. I would move to 5.21 first and the 6.0, 7.0 ... >=20 > It will not be possible to compile new versions with the old compiler=20 > you have. >=20 > The binary upgrade came later. When you have reached that version, you = > can go via binary upgrades. >=20 > Of course, you can have a try and move directly to the oldest version=20 > supporting binary upgrades. I only doubt that your old compiler will=20 > support this. >=20 > Good luck. >=20 > Erich >=20 >=20 >> =20 >> >> However, whenever I run commands to update the system (#=20 >> freebsd-update), or install portsnap, or install portmanager, or pkg=20 >> commands, portsnap fetch extract, I'm getting the message that=20 >> command not found >> >> =20 >> >> The my output for uname -a is shown below >> >> =20 >> >> relay# uname -a >> >> FreeBSD relay.zamnet.zm 4.10-RELEASE FreeBSD 4.10-RELEASE #1: Fri Nov >> 12 06:54:4 =20 >> >> =20 >> >> I'm asking for assistance on how I can enable the system (FreeBSD >> 4.10) to run these commands and hopefully update my system and=20 >> packages on it >> >> =20 >> >> Regards >> >> =20 >> >> Allan Kapoma|Head of Networks| ZAMNET Communication Systems Limited | >> >> Mobile: +260 962 235839 | Office: +260 211 220736| Fax: +260 211 >> 224775 | >> >> COMESA Center | Ben Bella Road | P.O Box 38299 | Lusaka, 10101 >> ZAMBIA |Email: =20 >> allan.kapoma@zamnet.zm >> | Website: www.zamnet.zm. >> >> >> >> Nobody Delivers IT Better >> >> =20 >> >> =20 >> >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list=20 >> https://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" >=20 >=20 > _______________________________________________ > freebsd-questions@freebsd.org mailing list=20 > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >=20 From owner-freebsd-questions@freebsd.org Tue Apr 19 11:09:25 2016 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 48AF4B13C2C for ; Tue, 19 Apr 2016 11:09:25 +0000 (UTC) (envelope-from vsasjason@gmail.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::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 D5ACA12D8 for ; Tue, 19 Apr 2016 11:09:24 +0000 (UTC) (envelope-from vsasjason@gmail.com) Received: by mail-wm0-x233.google.com with SMTP id n3so23431998wmn.0 for ; Tue, 19 Apr 2016 04:09:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=+PP3T9lOWmpWxWsk+QyN4m5ayYDTJGJh+iYMMn1cQVc=; b=D0GCkb+r1lcdo8eIS43ydpYlv4gYBp6gb6e/XfjtlGBs/6ILq1dOEPu/+jhrJwp9XA VK8OyWf+qh9VpNNp33A6thXcC52AYSFZoXFvV4oQnsvhtM3zDo0nlQNlryodsRm5jiW0 9uOA7C4EQxBstVJqlb6bzTYlOstE1rAgJCa7Nhwx+L6WxLxODtkszA/i3FVBwRsusRJ7 JVAauOmQS6YaAq+Q0COtJRB+D5WRvCFe3iN/S7NLsxa8/ROItn98BTahL+E30PJjq4PJ +Vlp5OdpP5i+ZHV+i2rJBRtAaU7HKDDFc6zbKSYQztBJ6xLl5ZzjOSog/uQi+Chcrm3p FQNQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=+PP3T9lOWmpWxWsk+QyN4m5ayYDTJGJh+iYMMn1cQVc=; b=RcClfYli4JvqKpY7FkaKy2jrIdRMT3k4FKmElWmrPih5IRU13beGJL+2XimtoG2nnx h6AF19lL8XvyzamBGfa6shXfKaPhQ6/na27PEeILVNXtjV4zEVDTTADpr5EsyXZZsw5F Dsl85y6Zg4vTJez5pQjOLAdUpa2EHzYT7V70lQGyyC3leuj6kpaYmi56k+ShWn0VGJsN /AHPV39dnYgIBf7rzjsQrKhQTlr32UPrfEs8o0O1VVIgjGB38V5vjZLBkR1Z++SVIUo8 YsbIuAmRdfjYIq+PcYY8YfOpDW7mL8WSu/i3XYJClDT8lLvy80KVs/Rh9iicQ9dO8RaD WovQ== X-Gm-Message-State: AOPr4FUczQxhlX2cZmD1X7syFU7dAah8TpjNcSKjRI8hysCcTP4OqYegKYaHclbPN1kgw1CH7409lBkMgppZWA== MIME-Version: 1.0 X-Received: by 10.28.211.75 with SMTP id k72mr19763187wmg.77.1461064163450; Tue, 19 Apr 2016 04:09:23 -0700 (PDT) Received: by 10.194.33.164 with HTTP; Tue, 19 Apr 2016 04:09:23 -0700 (PDT) Received: by 10.194.33.164 with HTTP; Tue, 19 Apr 2016 04:09:23 -0700 (PDT) In-Reply-To: References: Date: Tue, 19 Apr 2016 14:09:23 +0300 Message-ID: Subject: Re: oops zfs exec=off (on everything) From: Anton Sayetsky To: Paul Macdonald Cc: FreeBSD Questions Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 11:09:25 -0000 19 =D0=B0=D0=BF=D1=80. 2016 =D0=B3. 13:58 =D0=BF=D0=BE=D0=BB=D1=8C=D0=B7=D0= =BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C "Paul Macdonald" =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB: > > > Hi, > > i just set exec=3Doff on the parent file system on a zfs boot system, and all filesystems are now non executable. > > suggestions welcome! Boot from installation media, import pool & set exec to on back. From owner-freebsd-questions@freebsd.org Tue Apr 19 11:12:24 2016 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 DE7CFB13F3D for ; Tue, 19 Apr 2016 11:12:24 +0000 (UTC) (envelope-from steve@sohara.org) Received: from uk1mail2513.mymailbank.co.uk (UK1MAIL2513-PERMANET.IE.mymailbank.co.uk [217.69.47.44]) by mx1.freebsd.org (Postfix) with ESMTP id 4C5261795 for ; Tue, 19 Apr 2016 11:12:23 +0000 (UTC) (envelope-from steve@sohara.org) Received: from smtp.lan.sohara.org (UnknownHost [88.151.27.41]) by uk1mail2513-d.mymailbank.co.uk with SMTP; Tue, 19 Apr 2016 12:06:23 +0100 Received: from [192.168.63.1] (helo=steve.lan.sohara.org) by smtp.lan.sohara.org with smtp (Exim 4.86 (FreeBSD)) (envelope-from ) id 1asTUB-000OAk-Qp for freebsd-questions@freebsd.org; Tue, 19 Apr 2016 11:06:27 +0000 Date: Tue, 19 Apr 2016 12:06:26 +0100 From: Steve O'Hara-Smith To: freebsd-questions@freebsd.org Subject: Re: oops zfs exec=off (on everything) Message-Id: <20160419120626.0c9cfbdbd643a3377b2a2ad5@sohara.org> In-Reply-To: References: X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) X-Clacks-Overhead: "GNU Terry Pratchett" 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 11:12:25 -0000 On Tue, 19 Apr 2016 11:48:12 +0100 Paul Macdonald wrote: > Hi, > > i just set exec=off on the parent file system on a zfs boot system, and > all filesystems are now non executable. Boot from optical or USB and turn exec back on. -- Steve O'Hara-Smith From owner-freebsd-questions@freebsd.org Tue Apr 19 11:20:15 2016 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 0F371B14275 for ; Tue, 19 Apr 2016 11:20:15 +0000 (UTC) (envelope-from k.shesternin@gmail.com) Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9D28C1B2B for ; Tue, 19 Apr 2016 11:20:14 +0000 (UTC) (envelope-from k.shesternin@gmail.com) Received: by mail-wm0-x231.google.com with SMTP id l6so27515328wml.1 for ; Tue, 19 Apr 2016 04:20:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=1PcnN1wzTtTZbbBwJoo4bHzHLO2anf+Vpbe86Il+Eo0=; b=XeVovnknTYe5dvJbJsZwrpv7dZRHaBtk3CrP5xN0BdYha32NEtuB1UuWKqk/c+KPuw y1dj+egC4VnSGrNnbEG2EgiTiLo/Txapz5Vlv+vYiSgeUmVLJvldCTkqIzruRRwCzN8/ vweqRy3z9lZPosTh7vKvSQlHRl/4jhInXxoC+nyEOHvxAtCPdkzzU40qS7P+VgcjuT72 EpfxeFqAt0t37/tnj+gdAuREHoQAJa8dLE/d88UqOn2X3b2Vk+KMefJKoDUFJ2vTbwaQ 896wqBbT2Wao26lcz0psyi3REJJymqsOoR2HfSMY/prf+8NHqlVYlbMsiywB5rXfhlYn 0gcg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=1PcnN1wzTtTZbbBwJoo4bHzHLO2anf+Vpbe86Il+Eo0=; b=EL7vM8J7dHuXtcB6J3VIf4uFzee2xDy0SHxwxPoD4CdxlIuG2GDwySYjHeKyMEgNyU jVeJsBm/Dx8bDCXHyUb3lkJPIG7t2d8luFKuHvei3WkmHh13SCs5g29vTcBZhYHDnpZu jvWnGFUU//V7QA0kvWOD+zvqE0l3ag1NwWLmS7Rh3/wl+2xReoEvrPfRfzT7rn1QZ59P zQityRzSdTyqYdsPG02FA5VIeuMrRGqKOGeBcLGl4pVWJupSn5QsaQ6zCpHGpxipoPgr oeOYU4TM9D9MFU3bhfrKrHlBq85DLyuxGOuyyS5SjEPNObmRyUqbJWdXb3U30TSxAUVD w0UA== X-Gm-Message-State: AOPr4FXKIql8xH6ncj/f2VyO3Rt/kbXgY3vNzCkAfCVkBpZiGBuVNzk72Zf9BL8OU70NjpAKT/pJcQobGJUSPA== MIME-Version: 1.0 X-Received: by 10.28.68.70 with SMTP id r67mr3153841wma.80.1461064812866; Tue, 19 Apr 2016 04:20:12 -0700 (PDT) Received: by 10.28.36.193 with HTTP; Tue, 19 Apr 2016 04:20:12 -0700 (PDT) In-Reply-To: References: Date: Tue, 19 Apr 2016 14:20:12 +0300 Message-ID: Subject: Re: oops zfs exec=off (on everything) From: Konstantin To: Paul Macdonald 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.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 11:20:15 -0000 Hi. You can boot from usb live system and say-as-root: zpool import zfs set exec=3Don Then reboot. 2016-04-19 13:48 GMT+03:00 Paul Macdonald : > > Hi, > > i just set exec=3Doff on the parent file system on a zfs boot system, and > all filesystems are now non executable. > > suggestions welcome! > > thanks > > Paul. > > > > -- > ------------------------- > Paul Macdonald > IFDNRG Ltd > Web and video hosting > ------------------------- > t: 0131 5548070 > m: 07970339546 > e: paul@ifdnrg.com > w: http://www.ifdnrg.com > ------------------------- > IFDNRG > 40 Maritime Street > Edinburgh > EH6 6SA > ---------------------------------------------------- > > Virtual Servers from =C2=A350.00pm > High specification Dedicated Servers from =C2=A3150.00pm > > ---------------------------------------------------- > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" --=20 =D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC, =D0=9A=D0=BE=D0=BD=D1=81=D1=82=D0=B0=D0=BD=D1=82=D0=B8=D0=BD =D0=A8=D0=B5= =D1=81=D1=82=D0=B5=D1=80=D0=BD=D0=B8=D0=BD From owner-freebsd-questions@freebsd.org Tue Apr 19 11:24:36 2016 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 65C06B145B2 for ; Tue, 19 Apr 2016 11:24:36 +0000 (UTC) (envelope-from shahzaib.cb@gmail.com) Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2C8CD1EC1 for ; Tue, 19 Apr 2016 11:24:36 +0000 (UTC) (envelope-from shahzaib.cb@gmail.com) Received: by mail-io0-x22d.google.com with SMTP id f89so5708458ioi.0 for ; Tue, 19 Apr 2016 04:24:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=AekrbN5Nxi+P8MGebgl0L1oMGcLl3ParVomS1b9gELg=; b=yB4ZMYvFbehfOvBbK2cnb69flG0Ts0v0okrr6XnpkS3HWbkZqacFdtPtFyS4gshvmT /yV8ZZwLKpZIQmc9q4oj19CamNQC42kvEhUcrc25hRcMCbjusK/QiHmxjXMwgOiHv9Vn WTdO4SSaGN8+10P1T/8JcrDSl4KVVM2G2bmsxnObTLBmf5TCmsAM3XJYjcpmZ8RQXbEx IfghH+m46qcTv3bmMIV3ZxemkvLu7YBnlLJLtPYA/M47HipoIK3YygyJcSFuxpJ+//VZ u6XUsIcmGmaWyuZ67ihBNt8ntwvzkhPtyK4vQwhwaNKByygfAn66M3s0AKTzHwo9oLCs aMaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=AekrbN5Nxi+P8MGebgl0L1oMGcLl3ParVomS1b9gELg=; b=Ede/wuMSJdYL7byAF3INZslYk/9OdLAF1c5ykhxWX29XpOdM6RWqkcToiNSlv7Q+59 TZdGYn43ixcH2quNSGLW3RLebQYYuq4IPpELN2TmYxOB1tVyMdWn1aq6gG03CjcXGhLm +70YNf8qedUhKx3by2nUPxMcSVZSPiVwCauZruuRZ8HLA24lJg+58tITaRE9qAqIACH9 FRxDnahle6si47qeLI9fV4/BsUB53EjJJwJoautFokyAJbhNPfUI4Jt+OL9z6UKPTghN zLgFeut5k8Rs403UtySVbTYdR/cwOk6DcCDMYgvewq+WPhBbvhgK0HpVytLAgNEb24he nXVg== X-Gm-Message-State: AOPr4FU+Fw815ginUoaZ+ZQoXktWsntjb11ZoKSMaUhyPWXjLxGAOEMuA3O/ASatgD6zZUm2u9RueQkiTo31Jw== MIME-Version: 1.0 X-Received: by 10.107.14.142 with SMTP id 136mr2894992ioo.94.1461065075594; Tue, 19 Apr 2016 04:24:35 -0700 (PDT) Received: by 10.79.18.66 with HTTP; Tue, 19 Apr 2016 04:24:35 -0700 (PDT) In-Reply-To: References: <56E2E9AC.1040902@gmx.de> <33444.128.135.52.6.1457712900.squirrel@cosmo.uchicago.edu> <56E2F586.9000108@gmx.de> <5715DF0F.4090808@gmx.de> <5715EBDA.10907@gmx.de> Date: Tue, 19 Apr 2016 16:24:35 +0500 Message-ID: Subject: Re: FreeBSD Crashes Intermittently !! From: shahzaib mushtaq To: "lokadamus@gmx.de" Cc: freebsd-questions@freebsd.org, galtsev@kicp.uchicago.edu Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 11:24:36 -0000 Hi, Can we use following freebsd guide to update microcode ? : Install sysutils/devcpu-data , then add: microcode_update_enable="YES" ===================================================== https://www.freebsd.org/doc/faq/compatibility-processors.html On Tue, Apr 19, 2016 at 1:40 PM, shahzaib mushtaq wrote: > Hi, > > We don't think its related to heat because L5640 only use 60W. Can we > update microcode on FreeBSD? Because intel has not stated this OS when > performing microcode update. > > Regards. > > On Tue, Apr 19, 2016 at 1:27 PM, lokadamus@gmx.de > wrote: > >> Hi, >> >> I think about the error lines: >> Hardware event. This is not a software error. >> CPU 23 BANK 5 >> MISC 0 ADDR 805613c60 >> MCG status:MCIP >> STATUS be00000000800400 MCGSTATUS 4 >> .... >> Hardware event. This is not a software error. >> CPU 22 BANK 5 >> >> https://en.wikipedia.org/wiki/Machine-check_exception >> >> Looks like a hardware problem from the second cpu. >> Thinks, what can be done: >> - Is it possible to read cpu heat infos from bios? >> - Disable HTT and look, if the error comes again >> - Remove the second cpu and look, if ... >> - Install microcode updates and hope, it will fix it >> >> Intel offers for many CPUs an microcode update. >> >> https://downloadcenter.intel.com/download/25512/Linux-Processor-Microcode-Data-File?v=t >> >> Can you test a cpu in another system? >> https://www.freebsd.org/cgi/ports.cgi?query=cpuburn&stype=all >> >> >> Regards >> >> On 04/19/16 09:35, shahzaib mushtaq wrote: >> > Hi, sorry for the mistake, cpus are : >> > >> > 2 x Intel(R) Xeon(R) CPU L5640 @ 2.27GHz5640 (12 cores, 24 threads) >> > >> > On Tue, Apr 19, 2016 at 12:32 PM, lokadamus@gmx.de >> wrote: >> > >> >> On 04/18/16 16:28, shahzaib mushtaq wrote: >> >>> Hi again, got back after a long time. So yes, we've move to new Dell >> R510 >> >>> Hardware now. Here is the specs : >> >>> >> >>> DELL R510 >> >>> 2 x L5520 >> >>> 64GB RAM >> >>> 12x3TB Raid stripping+mirroring (HBA LSI-9211-fw version 19.00) >> >>> FreeBSD cw009.tunefiles.com 10.2-RELEASE-p14 FreeBSD 10.2-RELEASE-p14 >> >> #0: >> >>> Wed Mar 16 20:46:12 UTC 2016 >> >>> root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC >> >>> amd64 >> >>> >> >>> After 9days of uptime, server again got crashed with following error >> in >> >>> crash log : >> >>> >> >>> http://pastebin.com/baShWuMP >> >>> >> >>> I am so much depressed now, there's much pressure on me from my >> company. >> >> Please >> >>> help us resolving this crash issue . :( >> >> Which CPU Model is installed? Is it one or more? >> >> >> >> There where some microcode updates for some models. >> >> >> >> Greeting >> >> >> > _______________________________________________ >> > 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 Tue Apr 19 11:50:54 2016 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 AC78DB13006 for ; Tue, 19 Apr 2016 11:50:54 +0000 (UTC) (envelope-from lokadamus@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2349E1EFC for ; Tue, 19 Apr 2016 11:50:53 +0000 (UTC) (envelope-from lokadamus@gmx.de) Received: from [192.168.0.143] ([95.91.224.125]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0Lrviw-1bsrk12c5m-013iNR; Tue, 19 Apr 2016 13:50:47 +0200 Subject: Re: FreeBSD Crashes Intermittently !! To: shahzaib mushtaq References: <56E2E9AC.1040902@gmx.de> <33444.128.135.52.6.1457712900.squirrel@cosmo.uchicago.edu> <56E2F586.9000108@gmx.de> <5715DF0F.4090808@gmx.de> <5715EBDA.10907@gmx.de> Cc: freebsd-questions@freebsd.org, galtsev@kicp.uchicago.edu From: "lokadamus@gmx.de" Message-ID: <57161B95.9020802@gmx.de> Date: Tue, 19 Apr 2016 13:50:45 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:PGlD7O/8ZYxNTzPrRVtUYcdtR8KYbl2Q6YU3xOYb/kpIaT9qeDe GCW8bNJAFQJ1zNbzBok8sOvyo2xdw9u2Bh7zOEyfMi0FlVEhedB0CIe7CbLsOtJJNhUaupw UJxpFY4+LypvPY24QrFMff2nlZLPEzxiTICU0wBB3eN7gjQizWcNAo9L1sk+sbpBusDKJnX O0F5R0b165qRUrvzgjLPw== X-UI-Out-Filterresults: notjunk:1;V01:K0:QVidGEuqEps=:wnQlGUqoafPbNd3usPyXxd EtwFDFbKKftfQqptD/3TKGqgwEMWZ0SxAZd1OU50kra0lzUE969E3C3wxcuT6NiCtihZKmbDw Y8BUrTt5bniXwzL0hUcrBsIML8Fr2DyIeGk1nL1fUibvQHfEVS/Z9uRqTeNUp7j7hE+Y+R29I YmteTehmQVrsKzV/Dvt3NqJW/tGUGB6m6qMMuuZWueU2nGkmdf36SXEFzFvm5JSG5cuzFYRLT 1zB2IzRxZyDdkX8RcUK1zcTk8kmCHliNqR3EG4Ruzj6XYnaNIuPa9PfD9QJPtcs9kjkEkKvpn MFMm0RTi2UynpJB4KeGGPlGvZl6eO9gv8uXSXQ2Yz0ecS0qrj+/1YlAH3LzoHZWi2D6i9krQo dAV03n4rVbfu8ZRnVsxRMFVA1PaBbmF5RcFvo/QeDTVG0TnvbEDi2LfNO6UD7rxLchkiWlYRd XI9C+RoO1ldGTcAq0mJ8taqYxUjRcZYaBpxW8HvZPRc6npkggjp82BzuFt0hBja08hnynLZmo WRoiXiTm4SKRJFX/Nw3ObSQQUldxkzUqJw3uBRsRbPlVMRnz1GA1cOzf6zzfPRL7Z0Ed4NmIf P0qJg9lw9DIA0cc0ud3M/v6glFcU9CRtctQBrdQUzojgaLH+BG6x9ABAuXJgf/mem3Ep9zorw Ikn3BuhTJzltWdZYl4uY0Ne/3b+Mk0Basew3pht7GfRF+5+dB+2EEqxoTp1C0DqdaP09d0EWK EHSpsq/C2puoh4vJ4jf9kNFm4u92VoEhd/T3zCDivrxP0KVddMa6j9FfCBJHcENv7gMPLCjmH +DaiXsu X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 11:50:54 -0000 Yes, this is the port. I tested it on my old system. After reboot it will start /usr/local/etc/rc.d/microcode-update and show a little message. My system is too old for an update. I'm wondering. i've never heard that lower 80w are protecting for overheating. Can you test this? http://www.cyberciti.biz/faq/freebsd-determine-processor-cpu-temperature-command/ On 04/19/16 13:24, shahzaib mushtaq wrote: > Hi, > > Can we use following freebsd guide to update microcode ? : > > Install sysutils/devcpu-data > , > then add: > > microcode_update_enable="YES" > > > ===================================================== > > https://www.freebsd.org/doc/faq/compatibility-processors.html > > On Tue, Apr 19, 2016 at 1:40 PM, shahzaib mushtaq > wrote: > >> Hi, >> >> We don't think its related to heat because L5640 only use 60W. Can we >> update microcode on FreeBSD? Because intel has not stated this OS when >> performing microcode update. >> >> Regards. >> >> On Tue, Apr 19, 2016 at 1:27 PM, lokadamus@gmx.de >> wrote: >> >>> Hi, >>> >>> I think about the error lines: >>> Hardware event. This is not a software error. >>> CPU 23 BANK 5 >>> MISC 0 ADDR 805613c60 >>> MCG status:MCIP >>> STATUS be00000000800400 MCGSTATUS 4 >>> .... >>> Hardware event. This is not a software error. >>> CPU 22 BANK 5 >>> >>> https://en.wikipedia.org/wiki/Machine-check_exception >>> >>> Looks like a hardware problem from the second cpu. >>> Thinks, what can be done: >>> - Is it possible to read cpu heat infos from bios? >>> - Disable HTT and look, if the error comes again >>> - Remove the second cpu and look, if ... >>> - Install microcode updates and hope, it will fix it >>> >>> Intel offers for many CPUs an microcode update. >>> >>> https://downloadcenter.intel.com/download/25512/Linux-Processor-Microcode-Data-File?v=t >>> >>> Can you test a cpu in another system? >>> https://www.freebsd.org/cgi/ports.cgi?query=cpuburn&stype=all >>> >>> >>> Regards >>> >>> On 04/19/16 09:35, shahzaib mushtaq wrote: >>>> Hi, sorry for the mistake, cpus are : >>>> >>>> 2 x Intel(R) Xeon(R) CPU L5640 @ 2.27GHz5640 (12 cores, 24 threads) >>>> >>>> On Tue, Apr 19, 2016 at 12:32 PM, lokadamus@gmx.de >>> wrote: >>>> >>>>> On 04/18/16 16:28, shahzaib mushtaq wrote: >>>>>> Hi again, got back after a long time. So yes, we've move to new Dell >>> R510 >>>>>> Hardware now. Here is the specs : >>>>>> >>>>>> DELL R510 >>>>>> 2 x L5520 >>>>>> 64GB RAM >>>>>> 12x3TB Raid stripping+mirroring (HBA LSI-9211-fw version 19.00) >>>>>> FreeBSD cw009.tunefiles.com 10.2-RELEASE-p14 FreeBSD 10.2-RELEASE-p14 >>>>> #0: >>>>>> Wed Mar 16 20:46:12 UTC 2016 >>>>>> root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC >>>>>> amd64 >>>>>> >>>>>> After 9days of uptime, server again got crashed with following error >>> in >>>>>> crash log : >>>>>> >>>>>> http://pastebin.com/baShWuMP >>>>>> >>>>>> I am so much depressed now, there's much pressure on me from my >>> company. >>>>> Please >>>>>> help us resolving this crash issue . :( >>>>> Which CPU Model is installed? Is it one or more? >>>>> >>>>> There where some microcode updates for some models. >>>>> >>>>> Greeting >>>>> >>>> _______________________________________________ >>>> 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 Tue Apr 19 11:56:28 2016 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 30899B132C7 for ; Tue, 19 Apr 2016 11:56:28 +0000 (UTC) (envelope-from shahzaib.cb@gmail.com) Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com [IPv6:2607:f8b0:4001:c05::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 EA6ED11F2 for ; Tue, 19 Apr 2016 11:56:27 +0000 (UTC) (envelope-from shahzaib.cb@gmail.com) Received: by mail-ig0-x230.google.com with SMTP id g8so13650731igr.0 for ; Tue, 19 Apr 2016 04:56:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=DgdBtPjMMQ7L2kgU2HfAnrTeGXLclSP2wlRcxdtfwLA=; b=xDNBKxjm+3pLZ0U6U336CVYiJLzvz/mTZgfb9KXNaONg6LWOO5gJDer6BywlRYMG9+ YsyWm12NJSVr+IMy1EsL9Ozu6UkjooDeBJK8d2AyOC7qfitXjcJk6tA1KwnBoxisJE1O Vgmwk+9G3ErUgvocuDpcI/og8JhPjhPt1rzFcFRBKy4xo3LNaMMqutPpMna6oiZWhLUB W1q1XbgwX4tCRwDP/L92CKAoKq6WSpItc+L64hFcXyi8/ZuUQ5wZs5Pl7G49I1nE95Rv v69FXHtuSobHWzL6YxGMEaH2ELwqS8nvnJVxooh1Pij9fW3MUv36TsmLLCmLfjeGV8lF sHDA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=DgdBtPjMMQ7L2kgU2HfAnrTeGXLclSP2wlRcxdtfwLA=; b=OURPr68U+89CPjUF5ELff7I+hn4eMwGfLVGHK13Hx8s5SsEt9P5QeYG8jF3ucWZOom 2z32KWZFLOKTF/KxJ5LSS7MC08jR7Sf0P/wISR8D8FdfcPkexNxORARSTydi4L9QAAio aaLDJlq/W2h5l2xUDLHapYvyO0AxLA3MfP2ZA5zee7OJgnBHgQ+MYq3gzUrcglFzoBfs giRN2WIxTNR0N7ELO/PrE7ToyJZt3F4m3LBMcTf4FKQNxCQj3zGk0wG0A1HkoOZckrGV iq6kp6jmfKQsYBWMUxTQXrYt3omphw0A8BxffELxcWsHwu5zZsjL/NEijwG+SNmObg2P 7hsw== X-Gm-Message-State: AOPr4FXEFD3wb2o7OaB/Wr8C+zHcS+vCY1KH7atTAlbEvduOC30no3pErC6LagEOywNPFf8USERlVRjFbitkog== MIME-Version: 1.0 X-Received: by 10.50.112.42 with SMTP id in10mr23693602igb.1.1461066987206; Tue, 19 Apr 2016 04:56:27 -0700 (PDT) Received: by 10.79.18.66 with HTTP; Tue, 19 Apr 2016 04:56:27 -0700 (PDT) In-Reply-To: <57161B95.9020802@gmx.de> References: <56E2E9AC.1040902@gmx.de> <33444.128.135.52.6.1457712900.squirrel@cosmo.uchicago.edu> <56E2F586.9000108@gmx.de> <5715DF0F.4090808@gmx.de> <5715EBDA.10907@gmx.de> <57161B95.9020802@gmx.de> Date: Tue, 19 Apr 2016 16:56:27 +0500 Message-ID: Subject: Re: FreeBSD Crashes Intermittently !! From: shahzaib mushtaq To: "lokadamus@gmx.de" Cc: freebsd-questions@freebsd.org, galtsev@kicp.uchicago.edu Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 11:56:28 -0000 Hi, Currently 2 x ffmpeg processes are running and the temp is : http://prntscr.com/au4wrm Well, it looks like restart is not necessary for microcode, you can simply start microcode using command "service microcode_update start". Regards. On Tue, Apr 19, 2016 at 4:50 PM, lokadamus@gmx.de wrote: > Yes, this is the port. I tested it on my old system. > After reboot it will start /usr/local/etc/rc.d/microcode-update and show > a little message. > My system is too old for an update. > > I'm wondering. i've never heard that lower 80w are protecting for > overheating. > Can you test this? > > http://www.cyberciti.biz/faq/freebsd-determine-processor-cpu-temperature-command/ > > On 04/19/16 13:24, shahzaib mushtaq wrote: > > Hi, > > > > Can we use following freebsd guide to update microcode ? : > > > > Install sysutils/devcpu-data > > >, > > then add: > > > > microcode_update_enable="YES" > > > > > > ===================================================== > > > > https://www.freebsd.org/doc/faq/compatibility-processors.html > > > > On Tue, Apr 19, 2016 at 1:40 PM, shahzaib mushtaq > > > wrote: > > > >> Hi, > >> > >> We don't think its related to heat because L5640 only use 60W. Can we > >> update microcode on FreeBSD? Because intel has not stated this OS when > >> performing microcode update. > >> > >> Regards. > >> > >> On Tue, Apr 19, 2016 at 1:27 PM, lokadamus@gmx.de > >> wrote: > >> > >>> Hi, > >>> > >>> I think about the error lines: > >>> Hardware event. This is not a software error. > >>> CPU 23 BANK 5 > >>> MISC 0 ADDR 805613c60 > >>> MCG status:MCIP > >>> STATUS be00000000800400 MCGSTATUS 4 > >>> .... > >>> Hardware event. This is not a software error. > >>> CPU 22 BANK 5 > >>> > >>> https://en.wikipedia.org/wiki/Machine-check_exception > >>> > >>> Looks like a hardware problem from the second cpu. > >>> Thinks, what can be done: > >>> - Is it possible to read cpu heat infos from bios? > >>> - Disable HTT and look, if the error comes again > >>> - Remove the second cpu and look, if ... > >>> - Install microcode updates and hope, it will fix it > >>> > >>> Intel offers for many CPUs an microcode update. > >>> > >>> > https://downloadcenter.intel.com/download/25512/Linux-Processor-Microcode-Data-File?v=t > >>> > >>> Can you test a cpu in another system? > >>> https://www.freebsd.org/cgi/ports.cgi?query=cpuburn&stype=all > >>> > >>> > >>> Regards > >>> > >>> On 04/19/16 09:35, shahzaib mushtaq wrote: > >>>> Hi, sorry for the mistake, cpus are : > >>>> > >>>> 2 x Intel(R) Xeon(R) CPU L5640 @ 2.27GHz5640 (12 cores, 24 threads) > >>>> > >>>> On Tue, Apr 19, 2016 at 12:32 PM, lokadamus@gmx.de > >>> wrote: > >>>> > >>>>> On 04/18/16 16:28, shahzaib mushtaq wrote: > >>>>>> Hi again, got back after a long time. So yes, we've move to new Dell > >>> R510 > >>>>>> Hardware now. Here is the specs : > >>>>>> > >>>>>> DELL R510 > >>>>>> 2 x L5520 > >>>>>> 64GB RAM > >>>>>> 12x3TB Raid stripping+mirroring (HBA LSI-9211-fw version 19.00) > >>>>>> FreeBSD cw009.tunefiles.com 10.2-RELEASE-p14 FreeBSD > 10.2-RELEASE-p14 > >>>>> #0: > >>>>>> Wed Mar 16 20:46:12 UTC 2016 > >>>>>> root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC > >>>>>> amd64 > >>>>>> > >>>>>> After 9days of uptime, server again got crashed with following error > >>> in > >>>>>> crash log : > >>>>>> > >>>>>> http://pastebin.com/baShWuMP > >>>>>> > >>>>>> I am so much depressed now, there's much pressure on me from my > >>> company. > >>>>> Please > >>>>>> help us resolving this crash issue . :( > >>>>> Which CPU Model is installed? Is it one or more? > >>>>> > >>>>> There where some microcode updates for some models. > >>>>> > >>>>> Greeting > >>>>> > >>>> _______________________________________________ > >>>> 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 Tue Apr 19 12:10:53 2016 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 038A8B14002 for ; Tue, 19 Apr 2016 12:10: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 AAA731CE0 for ; Tue, 19 Apr 2016 12:10:51 +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.14.9) with ESMTPS id u3JCAoFQ040658 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 19 Apr 2016 08:10:50 -0400 (EDT) (envelope-from feenberg@nber.org) Date: Tue, 19 Apr 2016 08:10:50 -0400 (EDT) From: Daniel Feenberg To: Valeri Galtsev cc: "Kevin P. Neal" , Shamim Shahriar , freebsd-questions@freebsd.org Subject: Re: [Phishing]Re: Raid 1+0 In-Reply-To: <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> Message-ID: References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> User-Agent: Alpine 2.20 (LRH 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed 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, 2016/04/15 08:21:31 X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.721, bases: 2016/04/19 05:32:00 #7588058 X-KLMS-AntiVirus-Status: Clean, skipped X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 12:10:53 -0000 Why do drive failures come in pairs? [The following is based on Linux experience when the largest drives were 300GB - I think ZFS will do much better.] Most of drives we have claim a MTBF of 500,000 hours. That's about 2% per year. With three drives the chance of at least one failing is a little less than 6%. (1-(1-.98)^3). Our experience is that such numbers are at least a reasonable approximation of reality (but see Schroeder and Gibson ,2007). Suppose you have three drives in a RAID 5. If it takes 24 hours to replace and reconstruct a failed drive, one is tempted to calculate that the chance of a second drive failing before full redundancy is established is about .02/365, or about one in a hundred thousand. The total probability of a double failure seems like it should be about 6 in a million per year. Our double failure rate is worse than that - the many single drive failures are followed by a second drive failure before redundancy is established. This prevents rebuilding the array with a new drive replacing the original failed drive, however you can probably recover most files if you stay in degraded mode and copy the files to a different location. It isn't that failures are correlated because drives are from the same batch, or the controller is at fault, or the environment is bad (common electrical spike or heat problem). The fault lies with the Linux md driver, which stops rebuilding parity after a drive failure at the first point it encounters a uncorrectable read error on the remaining "good" drives. Of course with two drives unavailable, there isn't an unambiguous reconstruction of the bad sector, so it might be best to go to the backups instead of continuing. At least that is the apparently the reason for the decision. Alternatively, if the first drive failed was readable on that sector, (even if not reading some other sectors) it should be possible to fully recover all the data with a high degree of confidence even if a second drive is failed later. Since that is far from an unusual situation (a drive will be failed for a single uncorrectable error even if further reads are possible on other sectors) it isn't clear to us why that isn't done. [Lack of a slot for the bad drive?] Even if that sector isn't readable, logging the bad block, writing something recognizable to the targets, and going on might be better than simply giving up. A single unreadable sector isn't unusual among the tens of millions of sectors on a modern drive. If the sector has never been written to, there is no occasion for the drive electronics or the OS to even know it is bad. If the OS tried to write to it, the drive would automatically remap the sector and no damage would be done - not even a log entry. But that one bad sector will render the entire array unrecoverable no matter where on the disk it is if one other drive has already been failed. Let's repeat the reliability calculation with our new knowledge of the situation. In our experience perhaps half of drives have at least one unreadable sector in the first year. Again assume a 6 percent chance of a single failure. The chance of at least one of the remaining two drives having a bad sector is 75% (1-(1-.5)^2). So the RAID 5 failure rate is about 4.5%/year, which is .5% MORE than the 4% failure rate one would expect from a two drive RAID 0 with the same capacity. Alternatively, if you just had two drives with a partition on each and no RAID of any kind, the chance of a failure would still be 4%/year but only half the data loss per incident, which is considerably better than the RAID 5 can even hope for under the current reconstruction policy even with the most expensive hardware. The 3ware controller, has a "continue on error" rebuild policy available as an option in the array setup. But we would really like to know more about just what that means. What do the apparently similar RAID controllers from Mylex, LSI Logic and Adaptec do about this? A look at their web sites reveals no information. For some time now we have stuck with software raid, because it renders the drives pretty much hardware independent and there doesn't appear to be much of a performance loss. daniel feenberg From owner-freebsd-questions@freebsd.org Tue Apr 19 12:23:38 2016 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 7BAE7B14919 for ; Tue, 19 Apr 2016 12:23:38 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 5DDE41BCA for ; Tue, 19 Apr 2016 12:23:38 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 597EDB14918; Tue, 19 Apr 2016 12:23:38 +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 59215B14917 for ; Tue, 19 Apr 2016 12:23:38 +0000 (UTC) (envelope-from luzar722@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 250C01BC8 for ; Tue, 19 Apr 2016 12:23:38 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-io0-x233.google.com with SMTP id f89so6956164ioi.0 for ; Tue, 19 Apr 2016 05:23:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-transfer-encoding; bh=HnFyCnpCIjNMwZaHiDHkX1lSDuqz2AwRiCgBTkMaRp4=; b=kC6Yj7aYcQXRnwGkvBNgTgG2C8wh71scpohtfopSSDwPtLNuYjIyKnKHA4JTKzj/zZ ZcH9QGkY8JjDwFjJNnz8Hl6RoL+8MKp9btWnT6+DYvxxvH3tx5uQiNswh5IvvxoiE/+y LkRh3f2i4jNT7yUYMpod9aLBCYhW/fEuZi/5oePdORUn/M6T5GHU/7NbtdsoNbUyJnF6 eYiLMLGyWpjhN4P1vG1YjOhmvhhM7ifMlTGK86pJqd/2wb1UMdb5lxXg79WGbF55iY5/ r/jKh33ZCBV5j/7fZJ7j3GgrmomgKF8LScTsyWd6xaPT+PMpdcNZI3m9uPetdRg8wjYs TsPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:content-transfer-encoding; bh=HnFyCnpCIjNMwZaHiDHkX1lSDuqz2AwRiCgBTkMaRp4=; b=M+/0qHEsUpZ9QieHbQKe3bLLmsTpsq8wfaVCgGoc+MWbeLJ8Tp73UV6NUx8he1KVSu /mFgPTE04AxZXpUecLTslWnpHrsLs8xCp81XjtIX4X6hBHS6vW/Lx/uIP0b+19q8imo1 8nffHtj/SeHLWSP/GyqNgKYpQ39mtXHPYncOh4HBvjgLTAk/bNBDPV1P568Xy71r6VR9 syurxeLp7Viogp0U/H2cYkv4MmxLGVvcVOVZ27YRbw7knSiEPIXsCjKfvMGX0WCe3Fxe iWrRyawh2aUh23G7yJwy55EUShd+D8lXpjnvC0QYqcq0y9dM8UIjpm4wZGc1h7sLngFC Mh9g== X-Gm-Message-State: AOPr4FXJyJAbd6rK4bq8jbAixgxPNtI0NpEfLSZJu40x8OJu4+pqmTr5Qv8/Xc6NVX2H/g== X-Received: by 10.107.9.28 with SMTP id j28mr3363991ioi.104.1461068617442; Tue, 19 Apr 2016 05:23:37 -0700 (PDT) Received: from [10.0.10.3] (cpe-76-190-244-6.neo.res.rr.com. [76.190.244.6]) by smtp.googlemail.com with ESMTPSA id zp20sm1675924igc.13.2016.04.19.05.23.36 for (version=TLSv1/SSLv3 cipher=OTHER); Tue, 19 Apr 2016 05:23:36 -0700 (PDT) Message-ID: <5716234C.1020900@gmail.com> Date: Tue, 19 Apr 2016 08:23:40 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: questions@freebsd.org Subject: daily security run output - Checking setuid Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 12:23:38 -0000 This morning the "daily security run output" lists a lot of files under the heading of Checking setuid files & devices. I have never seen this before. What does this mean? Has my system been breached? Where is the "daily security run output" documented? Thanks From owner-freebsd-questions@freebsd.org Tue Apr 19 13:14:05 2016 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 3E33AB13C42 for ; Tue, 19 Apr 2016 13:14:05 +0000 (UTC) (envelope-from bourne.identity@hotmail.com) Received: from BLU004-OMC1S36.hotmail.com (blu004-omc1s36.hotmail.com [65.55.116.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 913D81D8D for ; Tue, 19 Apr 2016 13:14:04 +0000 (UTC) (envelope-from bourne.identity@hotmail.com) Received: from BLU436-SMTP56 ([65.55.116.8]) by BLU004-OMC1S36.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Tue, 19 Apr 2016 06:12:57 -0700 X-TMN: [VnIiW9tTmjxK6IPqD1yNvFeJEAUe1qdq] X-Originating-Email: [bourne.identity@hotmail.com] Message-ID: Subject: Re: Does HP DeskJet 1112 work with lpd on FreeBSD 10.2 amd64 ? To: freebsd-questions@freebsd.org, guru@unixarea.de References: From: Manish Jain Date: Tue, 19 Apr 2016 18:42:01 +0530 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 19 Apr 2016 13:12:54.0879 (UTC) FILETIME=[2F5D6EF0:01D19A3D] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 13:14:05 -0000 << CUPS works nice for many years on my FreeBSD systems, actually CURRENT. Why you can't get it to do anything on your system? matthias >> Thanks for responding. So my question becomes "Has anyne got HP DeskJet 1112 to work with CUPS on a FreeBSD 10.2 amd64 box ?" Regards Manish Jain From owner-freebsd-questions@freebsd.org Tue Apr 19 13:17:47 2016 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 BEF87B13DC4 for ; Tue, 19 Apr 2016 13:17:47 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id AAD8B105C for ; Tue, 19 Apr 2016 13:17:47 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: by mailman.ysv.freebsd.org (Postfix) id A6725B13DC3; Tue, 19 Apr 2016 13:17:47 +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 A617BB13DC2 for ; Tue, 19 Apr 2016 13:17:47 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 72466105B for ; Tue, 19 Apr 2016 13:17:47 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de (port-92-195-102-31.dynamic.qsc.de [92.195.102.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id D686827726; Tue, 19 Apr 2016 15:17:38 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id u3JDHcCQ001990; Tue, 19 Apr 2016 15:17:38 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Tue, 19 Apr 2016 15:17:38 +0200 From: Polytropon To: "Allan Kapoma" Cc: questions@freebsd.org Subject: Re: Upgrading from FreeBSD 4.1 Message-Id: <20160419151738.42f3f66b.freebsd@edvax.de> In-Reply-To: <00ba01d19a2a$b9ac8450$2d058cf0$@zamnet.zm> References: <003401d196ee$258ee680$70acb380$@zamnet.zm> <20160416094349.77f6a883@X220.alogt.com> <00bf01d19949$a9c69080$fd53b180$@zamnet.zm> <5715E0CD.7090802@gmx.de> <00ba01d19a2a$b9ac8450$2d058cf0$@zamnet.zm> 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-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 13:17:47 -0000 On Tue, 19 Apr 2016 13:00:46 +0200, Allan Kapoma wrote: > Thank you, I will look at it give it try Also make sure you follow the suggested procedure for updates in /usr/src/Makefile's comment header and check the UPDATING text information when it is available. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Tue Apr 19 14:12:20 2016 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 51F08B132B4 for ; Tue, 19 Apr 2016 14:12:20 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1640910AC for ; Tue, 19 Apr 2016 14:12:19 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [62.216.198.54] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1asWNy-0000er-Pn for freebsd-questions@freebsd.org; Tue, 19 Apr 2016 16:12:15 +0200 Received: from localhost.my.domain (c720-r292778-amd64 [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id u3JECAlm002845 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 19 Apr 2016 16:12:11 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id u3JEC8K9002844 for freebsd-questions@freebsd.org; Tue, 19 Apr 2016 16:12:08 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Tue, 19 Apr 2016 16:12:07 +0200 From: Matthias Apitz To: freebsd-questions@freebsd.org Subject: Re: Does HP DeskJet 1112 work with lpd on FreeBSD 10.2 amd64 ? Message-ID: <20160419141207.GA2799@c720-r292778-amd64.oa.oclc.org> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , freebsd-questions@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT r292778 (amd64) User-Agent: Mutt/1.5.24 (2015-08-30) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 62.216.198.54 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 14:12:20 -0000 El día Tuesday, April 19, 2016 a las 06:42:01PM +0530, Manish Jain escribió: > << > CUPS works nice for many years on my FreeBSD systems, actually CURRENT. > Why you can't get it to do anything on your system? matthias > >> > > Thanks for responding. So my question becomes "Has anyne got HP DeskJet > 1112 to work with CUPS on a FreeBSD 10.2 amd64 box ?" I have set it up through the web interface as: Driver: HP Deskjet 1100 hpijs, 3.14.10 (color) Connection: lpd://192.168.2.102/LPD Defaults: job-sheets=none, none media=iso_a4_210x297mm sides=one-sided Ofc, as a network printer (you said nothing about how this printer is connected physically); and one needs a pkg 'hplip' installed in addition to the CUPS packages: hplip-3.14.10_1 Drivers and utilities for HP Printers and All-in-One devices and: I do not have such printer and can not test it; matthias -- Matthias Apitz, ✉ guru@unixarea.de, ⌂ http://www.unixarea.de/ ☎ +49-176-38902045 ¡Dios querido denos otra vez los problemas de ayer, los que tuvimos en la RDA! My Lord, give us back the problems of yesterday, those we have had in the GDR. From owner-freebsd-questions@freebsd.org Tue Apr 19 14:26:02 2016 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 7D93EB139A2 for ; Tue, 19 Apr 2016 14:26:02 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0A4CA1CD2 for ; Tue, 19 Apr 2016 14:26:02 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from zero-gravitas.local (unknown [85.199.232.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 7FCA1110E4 for ; Tue, 19 Apr 2016 14:25:58 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/7FCA1110E4; dkim=none; dkim-atps=neutral Subject: Re: daily security run output - Checking setuid To: freebsd-questions@freebsd.org References: <5716234C.1020900@gmail.com> From: Matthew Seaman Message-ID: <5716401C.2000606@FreeBSD.org> Date: Tue, 19 Apr 2016 15:26:36 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <5716234C.1020900@gmail.com> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="INSajpeGBSqi6rPt1qMS99pbWddasl0cV" X-Virus-Scanned: clamav-milter 0.99.1 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-0.4 required=5.0 tests=BAYES_00,RDNS_NONE, SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 14:26:02 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --INSajpeGBSqi6rPt1qMS99pbWddasl0cV Content-Type: multipart/mixed; boundary="S6pbM5UnOE54JrPKP9BabLHrb0WlqBJCP" From: Matthew Seaman To: freebsd-questions@freebsd.org Message-ID: <5716401C.2000606@FreeBSD.org> Subject: Re: daily security run output - Checking setuid References: <5716234C.1020900@gmail.com> In-Reply-To: <5716234C.1020900@gmail.com> --S6pbM5UnOE54JrPKP9BabLHrb0WlqBJCP Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2016/04/19 13:23, Ernie Luzar wrote: > This morning the "daily security run output" lists a lot of files under= > the heading of Checking setuid files & devices. I have never seen this > before. >=20 > What does this mean? > Has my system been breached? > Where is the "daily security run output" documented? The output usually shows any changes to the lists of setuid or setgid files on your system. Take note of the leading '+' or '-' characters in that output. Suddenly adding one or a few new setuid files is suspicious. Adding write permissions to those files is frequently suspicious. However adding or removing /lots/ of setuid or setgid files all at once is more likely to be down to operator error. The daily script depends on keeping a list of all the known setuid / setgid files in (by default) /var/log/setuid.today and /var/log/setuid.yesterday. If one or both of those files get deleted or modified, or that partition fills up while the security/100.chksetuid script is running, you'll get spurious output. Setuid programs are often viewed as a security problem by inexperienced administrators, and some even go as far as turning off the setuid functionality. That, however, is one of those mistakes you only make once. Properly implemented, setuid and setgid *improves* your system security, and it's necessary for the system to function normally. Cheers, Matthew --S6pbM5UnOE54JrPKP9BabLHrb0WlqBJCP-- --INSajpeGBSqi6rPt1qMS99pbWddasl0cV Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJXFkAjXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnwsIP/0qpTUyNTlTWr4AzNLuZg4/Y LHyOFunWlZTWcS6b+BiajbFguhANYiGypWcfl9WRCabDtsozMSv6D7p/OtS6op8U xmZ8ffyVan2UrY8fhlsjsIdtC7txXvCm2mUfSE/CM3XoGM4Pl2FsLgb9TLwEN3wD BhjmmZfvjfnGLtKuHqOA39h2sg4/JbnxdHG3buvxFdyaS5Ir4UAHx4Uxw/rF8B4k W0Q8cu6HeuC981jZrNmAr9Z3DYf6ev+i80LSQikEX5o4PG4NaVVA4fpspDlsvZyy qEMZBnflNQhCqxI8jqN24sJbqySpECxYlGx5QElF7JfjHBCVcjBivbw5jCOLd04a VvMqC34ejlC00lQBhY5aMzcLVv3TmSXge8oJBg48c+uSE0OFdmRwsG0wkDeuO9Oe JYEtwe9VFLBoDVVSCV16tt/2OSY7uxaKKfISlXr3rz/30E1X5N/NyW4BHM9EU2UZ NZcQ8G9u1LMfFTTFIn5h6rwUVIk5oGlhA+zWci9ZYVxGmMfvRq0BFQnIPUe4VaJL lAV4QTjDEQW0uHIbX1HRQV550dz52VJtswL1cNtSm9+JlmNR/e9zulPaqSmIVbfj Kp/QoTTjPjk2P00XU6yQJSdrTlyK8NuZ2mnwngkNZDoKBaGJ0hOpOggwIpsJ8WWk uf8HT03kNUe+yi5U0X6Z =M6Ab -----END PGP SIGNATURE----- --INSajpeGBSqi6rPt1qMS99pbWddasl0cV-- From owner-freebsd-questions@freebsd.org Tue Apr 19 14:31:39 2016 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 71436B13CCC for ; Tue, 19 Apr 2016 14:31:39 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.70.90]) by mx1.freebsd.org (Postfix) with ESMTP id 3821610E7 for ; Tue, 19 Apr 2016 14:31:38 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id BF98BCB8C9D; Tue, 19 Apr 2016 09:31:37 -0500 (CDT) Received: from 128.135.52.6 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Tue, 19 Apr 2016 09:31:37 -0500 (CDT) Message-ID: <30732.128.135.52.6.1461076297.squirrel@cosmo.uchicago.edu> In-Reply-To: References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> Date: Tue, 19 Apr 2016 09:31:37 -0500 (CDT) Subject: Re: [Phishing]Re: Raid 1+0 From: "Valeri Galtsev" To: "Daniel Feenberg" Cc: "Valeri Galtsev" , "Kevin P. Neal" , "Shamim Shahriar" , freebsd-questions@freebsd.org 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 14:31:39 -0000 Daniel, nice writeup. We definitely think along the same lines. (sorry about top post) On Tue, April 19, 2016 7:10 am, Daniel Feenberg wrote: > > Why do drive failures come in pairs? With second failure of the same drive it will be physical spot of platter covering more that one block, more than one track... > > [The following is based on Linux experience when the largest drives were > 300GB - I think ZFS will do much better.] > > Most of drives we have claim a MTBF of 500,000 hours. That's about 2% per > year. With three drives the chance of at least one failing is a little > less than 6%. (1-(1-.98)^3). Our experience is that such numbers are at > least a reasonable approximation of reality (but see Schroeder and Gibson > ,2007). > > Suppose you have three drives in a RAID 5. If it takes 24 hours to replace > and reconstruct a failed drive, one is tempted to calculate that the > chance of a second drive failing before full redundancy is established is > about .02/365, or about one in a hundred thousand. The total probability > of a double failure seems like it should be about 6 in a million per year. Yes, to the contrary to me you didn't forget to multiply probability of single drive failure by the number of drives in array! My rusted brain needs cleaning... > > Our double failure rate is worse than that - the many single drive > failures are followed by a second drive failure before redundancy is > established. And here comes the question. Were all derives "surface scanned" withing a week before failure event? By that I mean anything from: 1. RAID verify operation - which reads all stripes and compares to the result of redundant stripe (or stripes in case of RAID-6)? This usually just a read operation, read of all blocks of each drive, and thanks to CRC, even read usually discovers newly developed bad blocks (although I agree, write-read-compare is better) 2. Drive surface scan run on all derives? Some hardware RAID units (like Infortrend) have that. It is not explicitly disclosed what is that, but most probably it is read (and remember) drive sector, write to sector, read sector and compare with what was written, then write original content of sector If neither of the above is scheduled to be performed routinely, then I would consider RAID not well configured. And second failure of another drive probably has nothing to do with first failure that triggered RAID rebuild, it was just something that happened during long period of time and was sitting not discovered. This resolves in my mind mystery that "drive failures come in pairs" which probability theory tells us is unlikely. Of course, rebuild is a stress, which may shift the probability somewhat, but you had the same stress a week ago, and two weeks ago and so on - when you were doing RAID verification or drive surface scan. Incidentally, if you allow rebuild with drive that failed not fatally, like I do, you will notice the same drive may fail during first rebuild attempt, (and maybe during second, and maybe third), but finally rebuild may succeed. And this failure with the same drive is most likely due to some bad spot on physical surface covering several sectors/tracks. Raid rebuild forces discovery of them one at a time, but once all of them discovered and relocated, all goes well (that comes from my 3ware based RAIDs). > This prevents rebuilding the array with a new drive replacing > the original failed drive, however you can probably recover most files if > you stay in degraded mode and copy the files to a different location. It > isn't that failures are correlated because drives are from the same batch, > or the controller is at fault, or the environment is bad (common > electrical spike or heat problem). The fault lies with the Linux md > driver, which stops rebuilding parity after a drive failure at the first > point it encounters a uncorrectable read error on the remaining "good" > drives. Of course with two drives unavailable, there isn't an unambiguous > reconstruction of the bad sector, so it might be best to go to the backups > instead of continuing. At least that is the apparently the reason for the > decision. > Alternatively, if the first drive failed was readable on that sector, > (even if not reading some other sectors) it should be possible to fully > recover all the data with a high degree of confidence even if a second > drive is failed later. Since that is far from an unusual situation (a > drive will be failed for a single uncorrectable error even if further > reads are possible on other sectors) it isn't clear to us why that isn't > done. [Lack of a slot for the bad drive?] Even if that sector isn't > readable, logging the bad block, writing something recognizable to the > targets, and going on might be better than simply giving up. Agree, bad stripe from one drive shouldn't necessarily kick out this whole drive, as when there is bad stripe from another drive elsewhere this first dive may give good resembling stripe. Not 100% safe to assume, but still decently safe. > > > A single unreadable sector isn't unusual among the tens of millions of > sectors on a modern drive. If the sector has never been written to, there > is no occasion for the drive electronics or the OS to even know it is bad. > If the OS tried to write to it, the drive would automatically remap the > sector and no damage would be done - not even a log entry. But that one > bad sector will render the entire array unrecoverable no matter where on > the disk it is if one other drive has already been failed. > > Let's repeat the reliability calculation with our new knowledge of the > situation. In our experience perhaps half of drives have at least one > unreadable sector in the first year. Again assume a 6 percent chance of a > single failure. The chance of at least one of the remaining two drives > having a bad sector is 75% (1-(1-.5)^2). So the RAID 5 failure rate is > about 4.5%/year, which is .5% MORE than the 4% failure rate one would > expect from a two drive RAID 0 with the same capacity. Alternatively, if > you just had two drives with a partition on each and no RAID of any kind, > the chance of a failure would still be 4%/year but only half the data loss > per incident, which is considerably better than the RAID 5 can even hope > for under the current reconstruction policy even with the most expensive > hardware. > > The 3ware controller, has a "continue on error" rebuild policy available > as an option in the array setup. But we would really like to know more > about just what that means. What do the apparently similar RAID > controllers from Mylex, LSI Logic and Adaptec do about this? A look at > their web sites reveals no information. For some time > now we have stuck with software raid, because it renders the drives pretty > much hardware independent and there doesn't appear to be much of a > performance loss. Daniel, I enjoyed the reading! Thanks! I have noticed that I observe lower drive failure rate on my boxes than numbers you mention. How do you get the drives? Do you stick with particular manufacturers, drive models, vendors? Or all is random? I'm trying to figure out if the fact that I am very picky about hard drives (and this is almost the only computer component I am picky about) really pays off in my case. I do my best to stick to manufacturers with best reliability record, I avoid all "green" drives of any sort, if drive of particular model is manufactured in different sizes, I always go with largest size (I noticed some time ago, they run production of smaller drive sizes on poorer production lines they own, whereas they don't dare to do the same about largest in size drives of particular model). I do my best to get drives (or avoid drives) based on geographical location of production line they made on whenever I can (if you know what I mean). Sometimes cost may be 5% or so higher (pricegrabber is your enemy here), but cost for my Department of my time not wasted on dealing with failures one can avoid justifies that IMHO. I really would love everybody's comments on this last paragraph. Valeri > > daniel feenberg > ++++++++++++++++++++++++++++++++++++++++ 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 Tue Apr 19 14:34:31 2016 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 51445B14090 for ; Tue, 19 Apr 2016 14:34:31 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C03B91A14 for ; Tue, 19 Apr 2016 14:34:30 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from zero-gravitas.local (unknown [85.199.232.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 7DFD61110A for ; Tue, 19 Apr 2016 14:34:27 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=infracaninophile.co.uk DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=infracaninophile.co.uk; s=201601-infracaninophile; t=1461076467; bh=Lf9pzIV1icFbNhkDljKmnP1heP48xD754ld4B3t99p4=; h=Subject:To:References:From:Date:In-Reply-To; z=Subject:=20Re:=20Raid=201+0|To:=20freebsd-questions@freebsd.org|R eferences:=20<571533F4.8040406@bananmonarki.se>|From:=20Matthew=20 Seaman=20|Date:=20Tue,=2019=20Apr =202016=2015:35:12=20+0100|In-Reply-To:=20<571533F4.8040406@bananm onarki.se>; b=GHo7vLgIW9zkVJ9lXzypMUjwSSNsCvzXJG8smldZ1eCAFqU78Dc24Mcx2IMPQFetj p2UEbT14TF8ervzoWQO3uJC93Kg77qAXWIx0wGh4E5Yst0pBuKPMXd0/cofd9w0Vpw JQTwx1p+7sLwvky2ofjaGFKtgEjo416IeYO0Q8c4= Subject: Re: Raid 1+0 To: freebsd-questions@freebsd.org References: <571533F4.8040406@bananmonarki.se> From: Matthew Seaman Message-ID: <57164220.2000806@infracaninophile.co.uk> Date: Tue, 19 Apr 2016 15:35:12 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <571533F4.8040406@bananmonarki.se> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="CX3b2iGKK8aIsBgs1vggipEiNAGXJbUWA" X-Virus-Scanned: clamav-milter 0.99.1 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,RDNS_NONE,SPF_FAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 14:34:31 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --CX3b2iGKK8aIsBgs1vggipEiNAGXJbUWA Content-Type: multipart/mixed; boundary="wkT1DrqnmKEiPAiiIsDQg0Cafd6F7T9pD" From: Matthew Seaman To: freebsd-questions@freebsd.org Message-ID: <57164220.2000806@infracaninophile.co.uk> Subject: Re: Raid 1+0 References: <571533F4.8040406@bananmonarki.se> In-Reply-To: <571533F4.8040406@bananmonarki.se> --wkT1DrqnmKEiPAiiIsDQg0Cafd6F7T9pD Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2016/04/18 20:22, Bernt Hansson wrote: > Newfs/mount all work. My question, is this a raid 1+0 or 0+1? > More info can be posted if need be. This is a RAID 10 setup. That's the good way round. For some reason these RAID setups are referred to as 'RAID 10' (striped mirrors, good) or 'RAID 0+1' (mirrored stripes, bad). No idea why one gets a '+' and the other not... Note that on-board ATA Raid is often pretty simplistic. It's basically a software RAID setup without any benefit of hardware acceleration. There's no real benefit to using it over using gmirror(8), and typically a fairly big lack of support for hot swapping drives or resync'ing the mirror without taking the system down, all of which you do get with gmirror(8). Cheers, Matthew --wkT1DrqnmKEiPAiiIsDQg0Cafd6F7T9pD-- --CX3b2iGKK8aIsBgs1vggipEiNAGXJbUWA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJXFkIgXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnPOcP/1vu7vu/EW0qQnVeYT0DhQ2k mOtWZBaZKbfBAEnik8r9eGchXW7G4CtgzmCIlqTzi2dSiW0CgP2kij5vxqQS62Co L+ta/sn+zAzLpJnwWstD1Yq+gNFFEJ/dJmboe0TSfYzAhurJZb7DwiZusPvH4+8d Q1hrHuGbZ4wu3ucA7Mmw309V0bRhaCyuiZgQWB/xMwMs/0d7YOEMqNSnaryrLku4 26rAPVRsr6jsCYj0btWN2+04NRCR5v/c2k6rqi1FZvNrnVfFuAw7qtjq8xstkpgT MVxNfkxGM2TdUqCp+3vMpkq5s4Dz2ZSnASa3hep4PwBqof9qIrUfOGDC3jfDe1Q2 WdSu3cJpfzR+mU0GvgUaFMytjes8Kzt1D/0Wl5i5wTwONWzi1nkWB2X4yjfdS+N5 i0VN2kSMwl/+yisRDVCV+Cw0dVq5h/rUOmouEBeVY302NGYlgjq23mujWazxWwDz z7qiFauxVM14ik49bZoFvcHmzhTtEKkjVGGAHoa+xPrsO4VPf/E8eEhqZXRIY4/W MMDJXKbeWj+zzDzJ4LcD9jc/mrtWp6KOKf74sq6OoG1xmPQ1D7YW7LzAjZahBMl+ Xfh1MY/oE6JskvBD+pj1/mwILCPR36Y/CKUWSFzYU+RpeJ3hWH3NWRn9g/vYQ7vX mqcVMtZn3szC5OlnFKtZ =NHqT -----END PGP SIGNATURE----- --CX3b2iGKK8aIsBgs1vggipEiNAGXJbUWA-- From owner-freebsd-questions@freebsd.org Tue Apr 19 14:47:56 2016 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 5D2D8B14973 for ; Tue, 19 Apr 2016 14:47:56 +0000 (UTC) (envelope-from allan@physics.umn.edu) Received: from mail.physics.umn.edu (smtp.spa.umn.edu [128.101.220.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 39F4619FF for ; Tue, 19 Apr 2016 14:47:55 +0000 (UTC) (envelope-from allan@physics.umn.edu) Received: from c-66-41-25-68.hsd1.mn.comcast.net ([66.41.25.68] helo=[192.168.0.115]) by mail.physics.umn.edu with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1asWbY-0003oP-4F for freebsd-questions@freebsd.org; Tue, 19 Apr 2016 09:26:16 -0500 Subject: Re: FreeBSD Crashes Intermittently !! To: freebsd-questions@freebsd.org References: <56E2E9AC.1040902@gmx.de> <33444.128.135.52.6.1457712900.squirrel@cosmo.uchicago.edu> <56E2F586.9000108@gmx.de> <5715DF0F.4090808@gmx.de> <5715EBDA.10907@gmx.de> From: Graham Allan Message-ID: <57163FFE.2010700@physics.umn.edu> Date: Tue, 19 Apr 2016 09:26:06 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <5715EBDA.10907@gmx.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 19 Apr 2016 16:02:09 +0000 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 14:47:56 -0000 I think also that if you update the R510 BIOS, Dell often include microcode updates in that (though checking their release notes should confirm that). Does the server have an iDRAC or BMC? Checking the event log in that might possibly show more clues. You could install ipmitool to query the BMC log from within FreeBSD. G. From owner-freebsd-questions@freebsd.org Tue Apr 19 16:13:51 2016 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 B35FDB1448F for ; Tue, 19 Apr 2016 16:13:51 +0000 (UTC) (envelope-from steve@sohara.org) Received: from uk1mail2513.mymailbank.co.uk (UK1MAIL2513-PERMANET.IE.mymailbank.co.uk [217.69.47.44]) by mx1.freebsd.org (Postfix) with ESMTP id 37CCE1DFA for ; Tue, 19 Apr 2016 16:13:50 +0000 (UTC) (envelope-from steve@sohara.org) Received: from smtp.lan.sohara.org (UnknownHost [88.151.27.41]) by uk1mail2513-d.mymailbank.co.uk with SMTP; Tue, 19 Apr 2016 15:35:49 +0100 Received: from [192.168.63.1] (helo=steve.lan.sohara.org) by smtp.lan.sohara.org with smtp (Exim 4.86 (FreeBSD)) (envelope-from ) id 1asWks-000Pgk-GJ for freebsd-questions@freebsd.org; Tue, 19 Apr 2016 14:35:54 +0000 Date: Tue, 19 Apr 2016 15:35:53 +0100 From: Steve O'Hara-Smith To: freebsd-questions@freebsd.org Subject: Re: Raid 1+0 Message-Id: <20160419153553.86e9a2990094cfcbc1302915@sohara.org> In-Reply-To: <20160418210257.GB86917@neutralgood.org> References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) X-Clacks-Overhead: "GNU Terry Pratchett" 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 16:13:51 -0000 On Mon, 18 Apr 2016 17:02:57 -0400 "Kevin P. Neal" wrote: > On Mon, Apr 18, 2016 at 09:07:07PM +0100, Shamim Shahriar wrote: > > On 18/04/2016 20:22, Bernt Hansson wrote: > > > Hello list > > > > > > > > > Used gstripe to stripe the arrays raid/r0 + r1 into stripe0 > > > > > Hi > > > > I'm sure there are people with more expertise than I am, and they can > > confirm either ways. But in my mind, given that you used RAID1 first > > (mirror) and then used those two RAID1 to create a RAID0, this is > > logically RAID 1+0. In other words, if you lose one disc from each of > > the RAID1 you are still safe. If you lose both from one single mirror > > array (highly unlikely), the stripe is unlikely to be of any use. > > Not that unlikely. If you take identical disks from the same company and > subject them to identical load then the probability that they will fail > around the same time is much higher than random. The classic case is not so much same model and same company but same batch which (at least in the early days of RAID) was quite likely. The more similar the drives and their long term load the more likely they are to fail at around the same time especially under the added load of replacing the first to fail. Perturbing that similarity is the goal. > That's why when I set up a mirror I always build it with drives from > different companies. And I make it a three way mirror if I can. I like to use a variety of drives and ages if I can, and yes two drives of redundancy either three way mirror or some variant of RAID6 (I like RAIDZ2). -- Steve O'Hara-Smith From owner-freebsd-questions@freebsd.org Tue Apr 19 16:16:48 2016 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 117BBB145B3 for ; Tue, 19 Apr 2016 16:16:48 +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 E593B1F3C for ; Tue, 19 Apr 2016 16:16:47 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: by be-well.ilk.org (Postfix, from userid 1147) id 8382533C27; Tue, 19 Apr 2016 12:16:44 -0400 (EDT) From: Lowell Gilbert To: "Valeri Galtsev" Cc: "Kevin P. Neal" , Shamim Shahriar , freebsd-questions@freebsd.org Subject: Re: Raid 1+0 References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> Date: Tue, 19 Apr 2016 12:16:44 -0400 In-Reply-To: <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> (Valeri Galtsev's message of "Mon, 18 Apr 2016 17:05:22 -0500 (CDT)") Message-ID: <441t61efpv.fsf@be-well.ilk.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 16:16:48 -0000 "Valeri Galtsev" writes: > Somebody with better knowledge of probability theory will correct me if > I'm wrong some place. Well, you are assuming that the probabilities of two drives failing are entirely independent of each other. The person to whom you are responding asserted that this is not the case. Neither of you presented any evidence directly to that point. From owner-freebsd-questions@freebsd.org Tue Apr 19 16:22:31 2016 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 9C61FB14907 for ; Tue, 19 Apr 2016 16:22:31 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.70.90]) by mx1.freebsd.org (Postfix) with ESMTP id 7D71813A8 for ; Tue, 19 Apr 2016 16:22:31 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id 77A2ECB8CA4; Tue, 19 Apr 2016 11:22:30 -0500 (CDT) Received: from 128.135.52.6 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Tue, 19 Apr 2016 11:22:30 -0500 (CDT) Message-ID: <59485.128.135.52.6.1461082950.squirrel@cosmo.uchicago.edu> In-Reply-To: <20160419153553.86e9a2990094cfcbc1302915@sohara.org> References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <20160419153553.86e9a2990094cfcbc1302915@sohara.org> Date: Tue, 19 Apr 2016 11:22:30 -0500 (CDT) Subject: Re: Raid 1+0 From: "Valeri Galtsev" To: "Steve O'Hara-Smith" Cc: freebsd-questions@freebsd.org 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 16:22:31 -0000 On Tue, April 19, 2016 9:35 am, Steve O'Hara-Smith wrote: > On Mon, 18 Apr 2016 17:02:57 -0400 > "Kevin P. Neal" wrote: > >> On Mon, Apr 18, 2016 at 09:07:07PM +0100, Shamim Shahriar wrote: >> > On 18/04/2016 20:22, Bernt Hansson wrote: >> > > Hello list >> > > >> > > >> > > Used gstripe to stripe the arrays raid/r0 + r1 into stripe0 >> > > >> > Hi >> > >> > I'm sure there are people with more expertise than I am, and they can >> > confirm either ways. But in my mind, given that you used RAID1 first >> > (mirror) and then used those two RAID1 to create a RAID0, this is >> > logically RAID 1+0. In other words, if you lose one disc from each of >> > the RAID1 you are still safe. If you lose both from one single mirror >> > array (highly unlikely), the stripe is unlikely to be of any use. >> >> Not that unlikely. If you take identical disks from the same company and >> subject them to identical load then the probability that they will fail >> around the same time is much higher than random. > > The classic case is not so much same model and same company but > same batch which (at least in the early days of RAID) was quite likely. > The > more similar the drives and their long term load the more likely they are > to fail at around the same time especially under the added load of > replacing the first to fail. Never happens to me that way. So my own small statistics of only a couple of dozens or RAIDs used over decade and a half time is kind ofin agreement with probability theory which IMHO says "double failure event" is much less likely than single failure event. (See my longer post about what I do to avoid apparent "double failure event", which are not actually such). Valeri > Perturbing that similarity is the goal. > >> That's why when I set up a mirror I always build it with drives from >> different companies. And I make it a three way mirror if I can. > > I like to use a variety of drives and ages if I can, and yes two > drives of redundancy either three way mirror or some variant of RAID6 (I > like RAIDZ2). > > -- > Steve O'Hara-Smith > > _______________________________________________ > 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 Tue Apr 19 16:52:21 2016 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 B47B6B13965 for ; Tue, 19 Apr 2016 16:52:21 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.70.90]) by mx1.freebsd.org (Postfix) with ESMTP id 73FCB1E66 for ; Tue, 19 Apr 2016 16:52:21 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id 7C6D3CB8C9E; Tue, 19 Apr 2016 11:52:20 -0500 (CDT) Received: from 128.135.52.6 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Tue, 19 Apr 2016 11:52:20 -0500 (CDT) Message-ID: <13260.128.135.52.6.1461084740.squirrel@cosmo.uchicago.edu> In-Reply-To: <441t61efpv.fsf@be-well.ilk.org> References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> <441t61efpv.fsf@be-well.ilk.org> Date: Tue, 19 Apr 2016 11:52:20 -0500 (CDT) Subject: Re: Raid 1+0 From: "Valeri Galtsev" To: "Lowell Gilbert" Cc: "Valeri Galtsev" , "Shamim Shahriar" , "Kevin P. Neal" , freebsd-questions@freebsd.org 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 16:52:21 -0000 On Tue, April 19, 2016 11:16 am, Lowell Gilbert wrote: > "Valeri Galtsev" writes: > >> Somebody with better knowledge of probability theory will correct me if >> I'm wrong some place. > > Well, you are assuming that the probabilities of two drives failing > are entirely independent of each other. The person to whom you are > responding asserted that this is not the case. Neither of you > presented any evidence directly to that point. Correct, we didn't hear proof of one or another. I, however, can not think of any physical mechanism that can be involved which will lead in case of failure of one drive to failure of another. That is why I assume events are (pretty much) independent. What can cause drive failure? 1. Pure mechanical reasons: head broke off, huge spot on platter surface deteriorated, new big scratch of platter was made, dirt particle left by manufacturer inside drive unstuck and started flying around,... None of these will suddenly affect drives sitting in the same enclosure 2. Electric problems: drive electronics burned out,... I safely assume that other drives, even sitting on the same power lines, are unlikely to be affected. It usually is a small brave piece of semiconductor that burs out and saves everybody else on the same power lines because short circuit behind it becomes disconnected, and burning away a piece of semiconductor doesn't require awful amount of power, and there is plenty where it comes from to feed many drives. So far I don't see any physical scenario by which failure of one drive can change probability of failure of another drive. To prove the events are not independent one needs some physical mechanism responsible for that. Without that events are independent in my opinion (exactly as I observe in my server room for over a decade and a half). But if someone observes different things (or even observed once) in one's server room, I really would like to know all the details. If they prove me wrong, I will learn something and change my hardware policies to make our equipment more reliable. I was keen getting this information whenever I was coming across these stories, but so far all "multiple failures" stories boiled down to one failure that happened long ago, and another failure that triggered merely a discovery of older failure, not the failure itself. So, "double failure" stories with all details are something that would be great to study closely. But if someone can suggest (purely theoretically) physical mechanism how one drive failure can induce (grossly increase probability of) another drive failure it will be really great to hear. 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 Tue Apr 19 18:27:38 2016 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 B7B77B15F9D for ; Tue, 19 Apr 2016 18:27:38 +0000 (UTC) (envelope-from jon@radel.com) Received: from radel.com (fly.radel.com [70.184.242.170]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "*.radel.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 66F5C1EEF for ; Tue, 19 Apr 2016 18:27:37 +0000 (UTC) (envelope-from jon@radel.com) X-CGP-ClamAV-Result: CLEAN X-VirusScanner: Niversoft's CGPClamav Helper v1.18.7 (ClamAV engine v0.98.7) Received: from [2001:470:880a:4389:cd3f:351a:239d:ef64] (account jon@radel.com HELO gravenstein.local) by radel.com (CommuniGate Pro SMTP 6.1.2 _community_) with ESMTPSA id 1039384; Tue, 19 Apr 2016 17:27:28 +0000 Subject: Re: Raid 1+0 To: galtsev@kicp.uchicago.edu References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> <441t61efpv.fsf@be-well.ilk.org> <13260.128.135.52.6.1461084740.squirrel@cosmo.uchicago.edu> Cc: freebsd-questions@freebsd.org From: Jon Radel Message-ID: <57166A7F.2030104@radel.com> Date: Tue, 19 Apr 2016 13:27:27 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <13260.128.135.52.6.1461084740.squirrel@cosmo.uchicago.edu> Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms030207010000000203090407" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 18:27:38 -0000 This is a cryptographically signed message in MIME format. --------------ms030207010000000203090407 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable On 4/19/16 12:52 PM, Valeri Galtsev wrote: > Correct, we didn't hear proof of one or another. I, however, can not th= ink > of any physical mechanism that can be involved which will lead in case = of > failure of one drive to failure of another. That is why I assume events= > are (pretty much) independent. > > Personally I think you're thinking about it all wrong. I didn't catch=20 anyone claiming that failure of one drive caused the failure of another=20 (though I've not slogged through the whole thread). Only that failure=20 of drives from the same manufacturing batch have a tendency to have=20 similar lifespans, and therefore there is some correlation as to when=20 they die. They have the same design flaws. They have the same=20 substandard components. Etc., etc. Why do you think that drives=20 come with MTBF figures, and that they're not all the same for every=20 drive? That's the summary output of somebody's best estimation of the=20 failure curve for that particular model. Personally I've never had a clear cut example with disk drives, though I = did own enough 750 mb drives from brand X some years ago to learn that=20 the involved mechanism, on average, sucked compared to other brand X=20 drives, and they were not to be trusted long term. However, I once saw=20 this very clearly in LCD monitors where I had multiples of the same=20 model. Turns out that they were caught up in the big "counterfeit"=20 capacitor scandal way back when, when due to imperfect industrial=20 espionage, a manufacturer only thought they'd stolen the formula for a=20 nice electrolyte. Turns out there was one little factor they'd missed,=20 the stabilizer that kept the capacitor from dropping dead at pretty much = the same age as every other capacitor of that model. There most=20 certainly was correlation on those monitors failing. Luckily they were=20 all still in warranty. :-) --Jon Radel jon@radel.com --------------ms030207010000000203090407 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC Cq8wggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4 dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290 MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak +FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC 4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb 4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ 26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT 9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl tukWeh95FPZKEBom+nyK+5swggX4MIIE4KADAgECAhBzVOU8fWu0zQ1gaQ38zgEbMA0GCSqG SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h aWwgQ0EwHhcNMTUwMzMwMDAwMDAwWhcNMTgwMzI5MjM1OTU5WjCB+jELMAkGA1UEBhMCVVMx DjAMBgNVBBETBTIyMTUwMQswCQYDVQQIEwJWQTEUMBIGA1UEBxMLU3ByaW5nZmllbGQxGjAY BgNVBAkTETY5MTcgUmlkZ2V3YXkgRHIuMRUwEwYDVQQKEwxKb24gVC4gUmFkZWwxMjAwBgNV BAsTKUlzc3VlZCB0aHJvdWdoIEpvbiBULiBSYWRlbCBFLVBLSSBNYW5hZ2VyMR8wHQYDVQQL ExZDb3Jwb3JhdGUgU2VjdXJlIEVtYWlsMRIwEAYDVQQDEwlKb24gUmFkZWwxHDAaBgkqhkiG 9w0BCQEWDWpvbkByYWRlbC5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDe 1Rth9hbQqaODn++C5dVAQH9nM2VH3oPazZufOwmIG2SXI/v3PuemcQQ3JkhmpQ06gYszyXbk TCLsqvEfalYj81jdt/K5lT4aVdj0LfJIWyTcU95V2rsCuHsSvn/PnIcsEtXg53rCtqS4EOtJ 9u3rY2hP8YCiyz1yY3mn4nKJs93MHG4AkXYuVpzfaIADETcVrA+razvXEfnDJXXDZZ9ZuuV1 06yIovOvhYWSlaVu8nrSHJjXFZI2IXwgIeVBoMih3yu6LLj14I/YdZ0rIA8K+UNB+NW6Ri3u wHXBbr4jh3ZqkrqIVUrf1VeybhdrJcdqXdMNHjKDSlCoaxYRbLy1AgMBAAGjggHVMIIB0TAf BgNVHSMEGDAWgBSSYWuC4aKgqk/sZ/HCo/e0gADB7DAdBgNVHQ4EFgQUz9YB10WEfBNHskRw o/0vh8qaQuwwDgYDVR0PAQH/BAQDAgWgMAwGA1UdEwEB/wQCMAAwHQYDVR0lBBYwFAYIKwYB BQUHAwQGCCsGAQUFBwMCMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQMFMCswKQYIKwYBBQUH AgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMF0GA1UdHwRWMFQwUqBQoE6GTGh0 dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET1NIQTI1NkNsaWVudEF1dGhlbnRpY2F0aW9u YW5kU2VjdXJlRW1haWxDQS5jcmwwgZAGCCsGAQUFBwEBBIGDMIGAMFgGCCsGAQUFBzAChkxo dHRwOi8vY3J0LmNvbW9kb2NhLmNvbS9DT01PRE9TSEEyNTZDbGllbnRBdXRoZW50aWNhdGlv bmFuZFNlY3VyZUVtYWlsQ0EuY3J0MCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5jb21vZG9j YS5jb20wGAYDVR0RBBEwD4ENam9uQHJhZGVsLmNvbTANBgkqhkiG9w0BAQsFAAOCAQEAS1Pe +gBgP+SQ/a5I5e7zX0Rg0DhH378LHlZixJgS6LfCPL2edKMUQi3Th9GXfLjdeyeWuMWoz925 ZzBHcPwkBeH+iM/AEhu0Dhi0kop/p66g9tEPJUZ/KDsqxddNDrD0Typn3/33pHTjJEDqydzA gwB0Nn8blpMbqSwT+j8wuPakfLsj1cSDzXrTLLsmIQB7auAyaYXdWyW8Yqw336rLUCvjOUfn qOOyjVsieTw/0PLoOHJaGyez+VtV4eyi6p1SNiX32A+fvxBMzKQLCokE43cXItc9Okzq//f2 fuvGp17r8mpm4OjjM5E2kwsg9bBPUBMR4/sxosKVLn0o9rxlozGCBEEwggQ9AgEBMIGwMIGb MQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdT YWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UEAxM4Q09NT0RPIFNI QS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEHNU5Tx9 a7TNDWBpDfzOARswDQYJYIZIAWUDBAIBBQCgggJhMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0B BwEwHAYJKoZIhvcNAQkFMQ8XDTE2MDQxOTE3MjcyN1owLwYJKoZIhvcNAQkEMSIEILL6hXbP /x4SMVSGEjjcyRw0ic/hYunan9RB8fK9OT+RMGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUD BAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcN AwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgcEGCSsGAQQBgjcQBDGBszCBsDCBmzEL MAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2Fs Zm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxQTA/BgNVBAMTOENPTU9ETyBTSEEt MjU2IENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhBzVOU8fWu0 zQ1gaQ38zgEbMIHDBgsqhkiG9w0BCRACCzGBs6CBsDCBmzELMAkGA1UEBhMCR0IxGzAZBgNV BAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09N T0RPIENBIExpbWl0ZWQxQTA/BgNVBAMTOENPTU9ETyBTSEEtMjU2IENsaWVudCBBdXRoZW50 aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhBzVOU8fWu0zQ1gaQ38zgEbMA0GCSqGSIb3 DQEBAQUABIIBAGfOuB1PGkdr6lsTZhTzhWtWQslOYLnAKCe+YP6VP72zBJQohLb5GL0Y/U2K GTo9nvnDCW2052q4kG09snTVy6vUZo8/rP0E+HMkktUM9ojABILmOd8bbpvL+3rTEe+JAcM7 Abfpi2/VTUsxv7GLKfl+hDr/lyaoeKkaP+uZD9XfC1gHDGj8Jlsixejd1KuTOxj3Knp3lTdz Bow4df1P7JZ4yyAB2kzDlnSayZYGXymcnP45sivxQZN2bMDqcYj3BQUMFWewKZHehcQXmozQ SPLzz9mFtB/4dfjWWqlPGHOUIfwpPezCGj9JL0K8qMgW0Mssat+pwPQ8r6XloS/gdVwAAAAA AAA= --------------ms030207010000000203090407-- From owner-freebsd-questions@freebsd.org Tue Apr 19 18:44:38 2016 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 48F74B137FE for ; Tue, 19 Apr 2016 18:44:38 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.70.90]) by mx1.freebsd.org (Postfix) with ESMTP id AAF271BCC for ; Tue, 19 Apr 2016 18:44:37 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id 38219CB8C9E; Tue, 19 Apr 2016 13:44:36 -0500 (CDT) Received: from 128.135.52.6 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Tue, 19 Apr 2016 13:44:36 -0500 (CDT) Message-ID: <44929.128.135.52.6.1461091476.squirrel@cosmo.uchicago.edu> In-Reply-To: <57166A7F.2030104@radel.com> References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> <441t61efpv.fsf@be-well.ilk.org> <13260.128.135.52.6.1461084740.squirrel@cosmo.uchicago.edu> <57166A7F.2030104@radel.com> Date: Tue, 19 Apr 2016 13:44:36 -0500 (CDT) Subject: Re: Raid 1+0 From: "Valeri Galtsev" To: "Jon Radel" Cc: freebsd-questions@freebsd.org 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 18:44:38 -0000 On Tue, April 19, 2016 12:27 pm, Jon Radel wrote: > On 4/19/16 12:52 PM, Valeri Galtsev wrote: >> Correct, we didn't hear proof of one or another. I, however, can not >> think >> of any physical mechanism that can be involved which will lead in case >> of >> failure of one drive to failure of another. That is why I assume events >> are (pretty much) independent. >> >> > Personally I think you're thinking about it all wrong. I didn't catch > anyone claiming that failure of one drive caused the failure of another > (though I've not slogged through the whole thread). Only that failure > of drives from the same manufacturing batch have a tendency to have > similar lifespans, and therefore there is some correlation as to when > they die. They have the same design flaws. They have the same > substandard components. Etc., etc. Why do you think that drives > come with MTBF figures, and that they're not all the same for every > drive? That's the summary output of somebody's best estimation of the > failure curve for that particular model. Jon, the reason for OP to never use "identical" drives in the same RAID array was that in his opinion there is higher likelyhood of two drives dies simultaneously (causing data loss) is high. My opinion is, the above is not correct, I will not repeat my lengthy post where I explained why. My opinion that your conclusion that the drives having the same MTBF (or similar lifespans) are likely to die simultaneously contradicts my understanding of probability theory (or statistics basics). People life expectancy in some country is 75 years. Likelyhood that two _given_ people will die at age 40 is negligible. Even twin brothers are unlikely to die during the same week or Month. This one is between fundamental assumptions statistics is based on. Just my humble opinion. Valeri > > Personally I've never had a clear cut example with disk drives, though I > did own enough 750 mb drives from brand X some years ago to learn that > the involved mechanism, on average, sucked compared to other brand X > drives, and they were not to be trusted long term. However, I once saw > this very clearly in LCD monitors where I had multiples of the same > model. Turns out that they were caught up in the big "counterfeit" > capacitor scandal way back when, when due to imperfect industrial > espionage, a manufacturer only thought they'd stolen the formula for a > nice electrolyte. Turns out there was one little factor they'd missed, > the stabilizer that kept the capacitor from dropping dead at pretty much > the same age as every other capacitor of that model. There most > certainly was correlation on those monitors failing. Luckily they were > all still in warranty. :-) > > --Jon Radel > jon@radel.com > > ++++++++++++++++++++++++++++++++++++++++ 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 Tue Apr 19 18:56:52 2016 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 0DBE0B13D98 for ; Tue, 19 Apr 2016 18:56:52 +0000 (UTC) (envelope-from steve@sohara.org) Received: from uk1mail2513.mymailbank.co.uk (UK1MAIL2513-PERMANET.IE.mymailbank.co.uk [217.69.47.44]) by mx1.freebsd.org (Postfix) with ESMTP id 7DF8B12D3 for ; Tue, 19 Apr 2016 18:56:50 +0000 (UTC) (envelope-from steve@sohara.org) Received: from smtp.lan.sohara.org (UnknownHost [88.151.27.41]) by uk1mail2513-d.mymailbank.co.uk with SMTP; Tue, 19 Apr 2016 15:38:19 +0100 Received: from [192.168.63.1] (helo=steve.lan.sohara.org) by smtp.lan.sohara.org with smtp (Exim 4.86 (FreeBSD)) (envelope-from ) id 1asWnI-000Pgp-FC; Tue, 19 Apr 2016 14:38:24 +0000 Date: Tue, 19 Apr 2016 15:38:24 +0100 From: Steve O'Hara-Smith To: freebsd-questions@freebsd.org Cc: galtsev@kicp.uchicago.edu Subject: Re: Raid 1+0 Message-Id: <20160419153824.7b679129f82a3cd0b18b9740@sohara.org> In-Reply-To: <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) X-Clacks-Overhead: "GNU Terry Pratchett" 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 18:56:52 -0000 On Mon, 18 Apr 2016 17:05:22 -0500 (CDT) "Valeri Galtsev" wrote: > Not correct. First of all, in most of the cases, failure of each of the > drives are independent events If only that were so. When the drives are as near identical as manufacturing can make them and have had very similar histories they can be expected to have very similar wear and be similarly close to failure at all times, which makes it likely that the load imposed by one failing will push another over. -- Steve O'Hara-Smith From owner-freebsd-questions@freebsd.org Tue Apr 19 19:19:49 2016 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 B3818B14927 for ; Tue, 19 Apr 2016 19:19:49 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6FFF21AA7 for ; Tue, 19 Apr 2016 19:19:49 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (dynamic-216-186-226-44.knology.net [216.186.226.44] (may be forged)) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id u3JJJf0V026170 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Tue, 19 Apr 2016 14:19:42 -0500 To: FreeBSD Questions !!!! From: "William A. Mahaffey III" Subject: Ports upgrade .... Message-ID: <571684CD.2070800@hiwaay.net> Date: Tue, 19 Apr 2016 14:25:11 -0453.75 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 19:19:49 -0000 .... I did a 'portsnap fetch update' This A.M.: [root@kabini1, /etc, 10:33:58am] 366 % portsnap fetch update Looking up portsnap.FreeBSD.org mirrors... 7 mirrors found. Fetching snapshot tag from your-org.portsnap.freebsd.org... done. Fetching snapshot metadata... done. Updating from Wed Mar 30 15:47:21 MCDT 2016 to Tue Apr 19 10:21:43 MCDT 2016. Fetching 4 metadata patches... done. Applying metadata patches... done. Fetching 4 metadata files... done. Fetching 13922 patches.....10....20....30....40....50....60....70....80....90....100....110....120....130....140....150....160....170....180....190....200....210....2 It brought down almost 14K updates for 3-ish weeks .... I know the ports effort is a feverish hive of productivity, but that sounded a bit high :-) .... Is that number anomalous, maybe coincident w/ new quarter, something else ? More question than problem, but curious. TIA & have a good one. -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr. From owner-freebsd-questions@freebsd.org Tue Apr 19 19:27:52 2016 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 2ED84B14E2A for ; Tue, 19 Apr 2016 19:27:52 +0000 (UTC) (envelope-from steve@sohara.org) Received: from uk1mail2513.mymailbank.co.uk (UK1MAIL2513-PERMANET.IE.mymailbank.co.uk [217.69.47.44]) by mx1.freebsd.org (Postfix) with ESMTP id A1ED6173D for ; Tue, 19 Apr 2016 19:27:50 +0000 (UTC) (envelope-from steve@sohara.org) Received: from smtp.lan.sohara.org (UnknownHost [88.151.27.41]) by uk1mail2513-d.mymailbank.co.uk with SMTP; Tue, 19 Apr 2016 18:07:10 +0100 Received: from [192.168.63.1] (helo=steve.lan.sohara.org) by smtp.lan.sohara.org with smtp (Exim 4.86 (FreeBSD)) (envelope-from ) id 1asZ7M-0000f6-3Q; Tue, 19 Apr 2016 17:07:16 +0000 Date: Tue, 19 Apr 2016 18:07:15 +0100 From: Steve O'Hara-Smith To: freebsd-questions@freebsd.org Cc: galtsev@kicp.uchicago.edu Subject: Re: Raid 1+0 Message-Id: <20160419180715.f788945fb67388a707c60ee7@sohara.org> In-Reply-To: <13260.128.135.52.6.1461084740.squirrel@cosmo.uchicago.edu> References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> <441t61efpv.fsf@be-well.ilk.org> <13260.128.135.52.6.1461084740.squirrel@cosmo.uchicago.edu> X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) X-Clacks-Overhead: "GNU Terry Pratchett" 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 19:27:52 -0000 On Tue, 19 Apr 2016 11:52:20 -0500 (CDT) "Valeri Galtsev" wrote: > > On Tue, April 19, 2016 11:16 am, Lowell Gilbert wrote: > > "Valeri Galtsev" writes: > > > >> Somebody with better knowledge of probability theory will correct me if > >> I'm wrong some place. > > > > Well, you are assuming that the probabilities of two drives failing > > are entirely independent of each other. The person to whom you are > > responding asserted that this is not the case. Neither of you > > presented any evidence directly to that point. > > Correct, we didn't hear proof of one or another. I, however, can not think > of any physical mechanism that can be involved which will lead in case of > failure of one drive to failure of another. That is why I assume events > are (pretty much) independent. The increased load caused by populating the replacement drive is one such physical mechanism. Probability of failure in a period of time is affected by how busy the drive has been in that period. Next Look at the curves for failure probability against age (or total activity) and note that the classic bathtub shape and consider what happens when your whole array is on the steep bit at the end and the first drive failure happens. Yes random drive failures well within the expected life are pretty much independent but the coupling gets stronger as the drives get older due to the increasing tendency of load induced failures. -- Steve O'Hara-Smith From owner-freebsd-questions@freebsd.org Tue Apr 19 19:46:25 2016 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 3AB73B0A437 for ; Tue, 19 Apr 2016 19:46:25 +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 1B32812A2 for ; Tue, 19 Apr 2016 19:46:24 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: by be-well.ilk.org (Postfix, from userid 1147) id C188933C28; Tue, 19 Apr 2016 15:46:22 -0400 (EDT) From: Lowell Gilbert To: "William A. Mahaffey III" Cc: Subject: Re: Ports upgrade .... References: <571684CD.2070800@hiwaay.net> Date: Tue, 19 Apr 2016 15:46:22 -0400 In-Reply-To: <571684CD.2070800@hiwaay.net> (William A. Mahaffey, III's message of "Tue, 19 Apr 2016 14:25:11 -0453.75") Message-ID: <44oa95crg1.fsf@be-well.ilk.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 19:46:25 -0000 "William A. Mahaffey III" writes: > It brought down almost 14K updates for 3-ish weeks .... I know the > ports effort is a feverish hive of productivity, but that sounded a > bit high :-) .... Is that number anomalous, maybe coincident w/ new > quarter, something else ? More question than problem, but curious. TIA > & have a good one. If you're switching from one quarterly branch to the next, then sure, you've pretty much got three months worth of updates at once. From owner-freebsd-questions@freebsd.org Tue Apr 19 19:51:29 2016 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 DEC3DB0A697 for ; Tue, 19 Apr 2016 19:51:29 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A66851820 for ; Tue, 19 Apr 2016 19:51:29 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1asbgA-0002e3-WB for freebsd-questions@freebsd.org; Tue, 19 Apr 2016 21:51:23 +0200 Received: from pool-72-66-1-32.washdc.fios.verizon.net ([72.66.1.32]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 19 Apr 2016 21:51:22 +0200 Received: from nightrecon by pool-72-66-1-32.washdc.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 19 Apr 2016 21:51:22 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Michael Powell Subject: Re: Raid 1+0 Date: Tue, 19 Apr 2016 15:52:22 -0400 Lines: 47 Message-ID: References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> <20160419153824.7b679129f82a3cd0b18b9740@sohara.org> Reply-To: nightrecon@hotmail.com Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pool-72-66-1-32.washdc.fios.verizon.net X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 19:51:30 -0000 Steve O'Hara-Smith wrote: > On Mon, 18 Apr 2016 17:05:22 -0500 (CDT) > "Valeri Galtsev" wrote: > >> Not correct. First of all, in most of the cases, failure of each of the >> drives are independent events > > If only that were so. When the drives are as near identical as > manufacturing can make them and have had very similar histories they can > be expected to have very similar wear and be similarly close to failure at > all times, which makes it likely that the load imposed by one failing will > push another over. > And the more of them you place in the same physical enclosure, the more vibration patterns and platter skew from either perfectly horizontal or perfectly vertical mounting generate complex interference patterns. The vibrational characteristics of the enclosure matter. In airframe superstructure testing vibration sensors (think seismology) are scattered throughout, then they use something that resembles a gun or an air hammer to bang on a point in order to map out how the resulting vibration will flow through the airframe. (Not my field of endeavor, something I learned from my dad). I'm certainly not qualified to debate probability theory. My experience is anecdotal at best, but many sysadmins have witnessed various forms of drive failure(s) in raid arrays. Most have noticed over the years that it seems to occur most often when all drives come from the same manufacturing batch run and lot number. After enough of these a sysadmin will respond by shuffling the drives so they are not all from the same shipment, as well as when one does fail, get it swapped out ASAP before another goes and you lose the whole array. Another pattern is simple age. I've seen drives that had run for so many years that all assumptions are they are OK. Power them down, and poof - just like that they don't come back. I've had arrays where one drive failed and when powered down some of the others would not come back up after power up. The answer to this is hot spare plus hot swap. Anecdotal experience is no substitute for rigorous scientific proofs. Most sysadmins are not concerned with such, but rather keeping servers running and data flowing, almost to the point of superstition. Whatever works - use it. -Mike From owner-freebsd-questions@freebsd.org Tue Apr 19 20:13:45 2016 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 DBAF3B1414E for ; Tue, 19 Apr 2016 20:13:45 +0000 (UTC) (envelope-from brandon.wandersee@gmail.com) Received: from mail-io0-f176.google.com (mail-io0-f176.google.com [209.85.223.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B40131C90 for ; Tue, 19 Apr 2016 20:13:45 +0000 (UTC) (envelope-from brandon.wandersee@gmail.com) Received: by mail-io0-f176.google.com with SMTP id u185so31124748iod.3 for ; Tue, 19 Apr 2016 13:13:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:user-agent:from:to:cc:subject :in-reply-to:date:message-id:mime-version; bh=qThu9mXPAqAI+C0PUJsj0bMVZ+agXrgCubmq2dH5/lM=; b=gwIzjNEHuHQfmiNoLEo4G7RHc9oRSjV3LKZj6WdN6F09PbdWWuab2DBSrKs73GxVbK QhmXtnPSkpD3fioVTaqjFP/F9UDmPD+ltUrZhUQLvDrm09eacYRD0lpys+sZYpDofNBp s413w8zxcZpzLtY02YVQaDf5/91QgFD6WDmBR+BK+J8q/d8/OGSMYKBRM0/6vawnvDww rN9vaHhM53ArZLnbIAL64BMjzXjat3BnfN6DxUguR+6gK3EzHf2DHutIUCsO5iouZYuR lX1oOWLtYsxL4+0nSHzVHl+NI1OtNhc9Y1R/S0DUbqhWtLpfj0o0QNP7pcxFoe/YCXuW mCZQ== X-Gm-Message-State: AOPr4FU63MR0MrwgsKXE7cUvT3lAm++AooauN3+IVGLQLeulaxDKVLOto8AaKlBQMx/Quw== X-Received: by 10.107.15.23 with SMTP id x23mr5803494ioi.154.1461096819629; Tue, 19 Apr 2016 13:13:39 -0700 (PDT) Received: from WorkBox.Home.gmail.com (97-116-17-82.mpls.qwest.net. [97.116.17.82]) by smtp.gmail.com with ESMTPSA id b64sm948321iob.8.2016.04.19.13.13.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Apr 2016 13:13:38 -0700 (PDT) References: <571684CD.2070800@hiwaay.net> <44oa95crg1.fsf@be-well.ilk.org> User-agent: mu4e 0.9.16; emacs 24.5.1 From: Brandon J. Wandersee To: Lowell Gilbert Cc: "William A. Mahaffey III" , freebsd-questions@freebsd.org Subject: Re: Ports upgrade .... In-reply-to: <44oa95crg1.fsf@be-well.ilk.org> Date: Tue, 19 Apr 2016 15:13:39 -0500 Message-ID: <86d1pl2w7g.fsf@WorkBox.Home> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 20:13:46 -0000 Lowell Gilbert writes: > "William A. Mahaffey III" writes: > >> It brought down almost 14K updates for 3-ish weeks .... I know the >> ports effort is a feverish hive of productivity, but that sounded a >> bit high :-) .... Is that number anomalous, maybe coincident w/ new >> quarter, something else ? More question than problem, but curious. TIA >> & have a good one. > > If you're switching from one quarterly branch to the next, then sure, > you've pretty much got three months worth of updates at once. I thought portsnap couldn't fetch from the quarterly branches? Or did my caffeine-starved brain just misread something? :P -- :: Brandon J. Wandersee :: brandon.wandersee@gmail.com :: -------------------------------------------------- :: 'The best design is as little design as possible.' :: --- Dieter Rams ---------------------------------- From owner-freebsd-questions@freebsd.org Tue Apr 19 20:30:43 2016 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 7ECD7B14DFE for ; Tue, 19 Apr 2016 20:30:43 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.70.90]) by mx1.freebsd.org (Postfix) with ESMTP id 61E0D12CB for ; Tue, 19 Apr 2016 20:30:42 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id 499F7CB8CA4; Tue, 19 Apr 2016 15:30:42 -0500 (CDT) Received: from 128.135.52.6 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Tue, 19 Apr 2016 15:30:42 -0500 (CDT) Message-ID: <43635.128.135.52.6.1461097842.squirrel@cosmo.uchicago.edu> Date: Tue, 19 Apr 2016 15:30:42 -0500 (CDT) Subject: Re: Raid 1+0 From: "Valeri Galtsev" To: "Steve O'Hara-Smith" Cc: freebsd-questions@freebsd.org 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 20:30:43 -0000 On Tue, April 19, 2016 12:07 pm, Steve O'Hara-Smith wrote: > On Tue, 19 Apr 2016 11:52:20 -0500 (CDT) > "Valeri Galtsev" wrote: > >> >> On Tue, April 19, 2016 11:16 am, Lowell Gilbert wrote: >> > "Valeri Galtsev" writes: >> > >> >> Somebody with better knowledge of probability theory will correct me >> if >> >> I'm wrong some place. >> > >> > Well, you are assuming that the probabilities of two drives failing are entirely independent of each other. The person to whom you are responding asserted that this is not the case. Neither of you presented any evidence directly to that point. >> >> Correct, we didn't hear proof of one or another. I, however, can not think >> of any physical mechanism that can be involved which will lead in case of >> failure of one drive to failure of another. That is why I assume events are (pretty much) independent. > > The increased load caused by populating the replacement drive is > one such physical mechanism. Probability of failure in a period of time is affected by how busy the drive has been in that period. As I said, it affects a bit, but not as grossly as you think. Because you apply the same excessive load every week when you run RAID verification. Still you don't have all your drives dead even after 3 years (which means it over 150 verifications). > > Next Look at the curves for failure probability against age (or > total activity) and note that the classic bathtub shape and consider what happens when your whole array is on the steep bit at the end and the first drive failure happens. > > Yes random drive failures well within the expected life are pretty > much independent Thank you! Valeri > but the coupling gets stronger as the drives get older > due > to the increasing tendency of load induced failures. > > -- > Steve O'Hara-Smith > > _______________________________________________ > 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 ++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++ 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 Tue Apr 19 20:35:49 2016 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 9D8C5B15139 for ; Tue, 19 Apr 2016 20:35:49 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.70.90]) by mx1.freebsd.org (Postfix) with ESMTP id 7E0A41864 for ; Tue, 19 Apr 2016 20:35:49 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id A459ACB8CA4; Tue, 19 Apr 2016 15:35:48 -0500 (CDT) Received: from 128.135.52.6 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Tue, 19 Apr 2016 15:35:48 -0500 (CDT) Message-ID: <40267.128.135.52.6.1461098148.squirrel@cosmo.uchicago.edu> In-Reply-To: <20160419153824.7b679129f82a3cd0b18b9740@sohara.org> References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> <20160419153824.7b679129f82a3cd0b18b9740@sohara.org> Date: Tue, 19 Apr 2016 15:35:48 -0500 (CDT) Subject: Re: Raid 1+0 From: "Valeri Galtsev" To: "Steve O'Hara-Smith" Cc: freebsd-questions@freebsd.org, galtsev@kicp.uchicago.edu 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 20:35:49 -0000 On Tue, April 19, 2016 9:38 am, Steve O'Hara-Smith wrote: > On Mon, 18 Apr 2016 17:05:22 -0500 (CDT) > "Valeri Galtsev" wrote: > >> Not correct. First of all, in most of the cases, failure of each of the >> drives are independent events > > If only that were so. When the drives are as near identical as > manufacturing can make them and have had very similar histories they can > be > expected to have very similar wear and be similarly close to failure at > all > times, which makes it likely that the load imposed by one failing will > push > another over. Sigh. You need suggest some physics that will make one drive affect another (aged or not aged doesn't matter for me). Then you will have me in your team. Valeri > > -- > Steve O'Hara-Smith > ++++++++++++++++++++++++++++++++++++++++ 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 Tue Apr 19 20:42:48 2016 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 542E9B15637 for ; Tue, 19 Apr 2016 20:42:48 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1B9211A54 for ; Tue, 19 Apr 2016 20:42:47 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ascTs-00011l-6x for freebsd-questions@freebsd.org; Tue, 19 Apr 2016 22:42:44 +0200 Received: from pool-72-66-1-32.washdc.fios.verizon.net ([72.66.1.32]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 19 Apr 2016 22:42:44 +0200 Received: from nightrecon by pool-72-66-1-32.washdc.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 19 Apr 2016 22:42:44 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Michael Powell Subject: Re: Raid 1+0 Date: Tue, 19 Apr 2016 16:43:37 -0400 Lines: 29 Message-ID: References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> <20160419153824.7b679129f82a3cd0b18b9740@sohara.org> <40267.128.135.52.6.1461098148.squirrel@cosmo.uchicago.edu> Reply-To: nightrecon@hotmail.com Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pool-72-66-1-32.washdc.fios.verizon.net X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 20:42:48 -0000 Valeri Galtsev wrote: > > > On Tue, April 19, 2016 9:38 am, Steve O'Hara-Smith wrote: >> On Mon, 18 Apr 2016 17:05:22 -0500 (CDT) >> "Valeri Galtsev" wrote: >> >>> Not correct. First of all, in most of the cases, failure of each of the >>> drives are independent events >> >> If only that were so. When the drives are as near identical as >> manufacturing can make them and have had very similar histories they can >> be >> expected to have very similar wear and be similarly close to failure at >> all >> times, which makes it likely that the load imposed by one failing will >> push >> another over. > > Sigh. You need suggest some physics that will make one drive affect > another (aged or not aged doesn't matter for me). Then you will have me in > your team. Vibration is kinetic energy. :-) -Mike From owner-freebsd-questions@freebsd.org Tue Apr 19 20:43:44 2016 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 87FD4B15755 for ; Tue, 19 Apr 2016 20:43:44 +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 65DD61E13 for ; Tue, 19 Apr 2016 20:43:44 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: by be-well.ilk.org (Postfix, from userid 1147) id 4766733C28; Tue, 19 Apr 2016 16:43:38 -0400 (EDT) From: Lowell Gilbert To: Brandon J. Wandersee Cc: Lowell Gilbert , "William A. Mahaffey III" , freebsd-questions@freebsd.org Subject: Re: Ports upgrade .... References: <571684CD.2070800@hiwaay.net> <44oa95crg1.fsf@be-well.ilk.org> <86d1pl2w7g.fsf@WorkBox.Home> Reply-To: freebsd-questions@freebsd.org Date: Tue, 19 Apr 2016 16:43:38 -0400 In-Reply-To: <86d1pl2w7g.fsf@WorkBox.Home> (Brandon J. Wandersee's message of "Tue, 19 Apr 2016 15:13:39 -0500") Message-ID: <44h9excosl.fsf@be-well.ilk.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 20:43:44 -0000 Brandon J. Wandersee writes: > Lowell Gilbert writes: > >> "William A. Mahaffey III" writes: >> >>> It brought down almost 14K updates for 3-ish weeks .... I know the >>> ports effort is a feverish hive of productivity, but that sounded a >>> bit high :-) .... Is that number anomalous, maybe coincident w/ new >>> quarter, something else ? More question than problem, but curious. TIA >>> & have a good one. >> >> If you're switching from one quarterly branch to the next, then sure, >> you've pretty much got three months worth of updates at once. > > I thought portsnap couldn't fetch from the quarterly branches? Or did my > caffeine-starved brain just misread something? :P Or I could just be wrong. I took a quick look at the documentation and the code and I'm not sure. From owner-freebsd-questions@freebsd.org Tue Apr 19 20:57:59 2016 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 A820BB15C6C for ; Tue, 19 Apr 2016 20:57:59 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.70.90]) by mx1.freebsd.org (Postfix) with ESMTP id 884FE1BB7 for ; Tue, 19 Apr 2016 20:57:59 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id 4ED52CB8C9C; Tue, 19 Apr 2016 15:57:53 -0500 (CDT) Received: from 128.135.52.6 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Tue, 19 Apr 2016 15:57:53 -0500 (CDT) Message-ID: <33157.128.135.52.6.1461099473.squirrel@cosmo.uchicago.edu> In-Reply-To: References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> <20160419153824.7b679129f82a3cd0b18b9740@sohara.org> <40267.128.135.52.6.1461098148.squirrel@cosmo.uchicago.edu> Date: Tue, 19 Apr 2016 15:57:53 -0500 (CDT) Subject: Re: Raid 1+0 From: "Valeri Galtsev" To: nightrecon@hotmail.com Cc: freebsd-questions@freebsd.org 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 20:57:59 -0000 On Tue, April 19, 2016 3:43 pm, Michael Powell wrote: > Valeri Galtsev wrote: > >> >> >> On Tue, April 19, 2016 9:38 am, Steve O'Hara-Smith wrote: >>> On Mon, 18 Apr 2016 17:05:22 -0500 (CDT) >>> "Valeri Galtsev" wrote: >>> >>>> Not correct. First of all, in most of the cases, failure of each of >>>> the >>>> drives are independent events >>> >>> If only that were so. When the drives are as near identical as >>> manufacturing can make them and have had very similar histories they >>> can >>> be >>> expected to have very similar wear and be similarly close to failure at >>> all >>> times, which makes it likely that the load imposed by one failing will >>> push >>> another over. >> >> Sigh. You need suggest some physics that will make one drive affect >> another (aged or not aged doesn't matter for me). Then you will have me >> in >> your team. > > Vibration is kinetic energy. :-) Cool! No I don't think drives in my enclosures resonate in unison. Fans give enclosure much more vibration IMHO. Further, how died drive changes that vibration pattern and causes another drive go bad with him!? I guess, you go to your church and I go to mine (read: University Physics or Mathematics class instead of church ;-) Valeri > > -Mike > > > > _______________________________________________ > 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 Tue Apr 19 21:10:26 2016 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 96288B140D2 for ; Tue, 19 Apr 2016 21:10:26 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 593FA134A for ; Tue, 19 Apr 2016 21:10:26 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ascua-000192-Up for freebsd-questions@freebsd.org; Tue, 19 Apr 2016 23:10:21 +0200 Received: from pool-72-66-1-32.washdc.fios.verizon.net ([72.66.1.32]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 19 Apr 2016 23:10:20 +0200 Received: from nightrecon by pool-72-66-1-32.washdc.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 19 Apr 2016 23:10:20 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Michael Powell Subject: Re: Raid 1+0 Date: Tue, 19 Apr 2016 17:11:13 -0400 Lines: 19 Message-ID: References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> <441t61efpv.fsf@be-well.ilk.org> <13260.128.135.52.6.1461084740.squirrel@cosmo.uchicago.edu> <57166A7F.2030104@radel.com> <44929.128.135.52.6.1461091476.squirrel@cosmo.uchicago.edu> Reply-To: nightrecon@hotmail.com Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pool-72-66-1-32.washdc.fios.verizon.net X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 21:10:26 -0000 Valeri Galtsev wrote: [snip] > Even twin brothers are unlikely to die > during the same week or Month. This one is between fundamental assumptions > statistics is based on. > And yet I knew two identical twin brothers that did die at the same time! They were together in the same car when they were obliterated by an out of control jack-knifed tractor trailer truck. Was a long time ago, but it happened. Just because probability may, or may not, predict a thing does not mean it can or cannot happen. -Mike From owner-freebsd-questions@freebsd.org Tue Apr 19 21:31:44 2016 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 597F1B14923 for ; Tue, 19 Apr 2016 21:31:44 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.70.90]) by mx1.freebsd.org (Postfix) with ESMTP id 386EF103E for ; Tue, 19 Apr 2016 21:31:43 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id 38D33CB8CA0; Tue, 19 Apr 2016 16:31:43 -0500 (CDT) Received: from 128.135.52.6 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Tue, 19 Apr 2016 16:31:43 -0500 (CDT) Message-ID: <36540.128.135.52.6.1461101503.squirrel@cosmo.uchicago.edu> In-Reply-To: References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> <441t61efpv.fsf@be-well.ilk.org> <13260.128.135.52.6.1461084740.squirrel@cosmo.uchicago.edu> <57166A7F.2030104@radel.com> <44929.128.135.52.6.1461091476.squirrel@cosmo.uchicago.edu> Date: Tue, 19 Apr 2016 16:31:43 -0500 (CDT) Subject: Re: Raid 1+0 From: "Valeri Galtsev" To: nightrecon@hotmail.com Cc: freebsd-questions@freebsd.org 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 21:31:44 -0000 On Tue, April 19, 2016 4:11 pm, Michael Powell wrote: > Valeri Galtsev wrote: > > [snip] >> Even twin brothers are unlikely to die >> during the same week or Month. This one is between fundamental >> assumptions >> statistics is based on. >> > > And yet I knew two identical twin brothers that did die at the same time! > They were together in the same car You see, this makes these two events not independent but correlated by the fact they were in the same car... Do we really need to continue this? On the other hand, two clowns may be giving public good entertainment ;-) Valeri > when they were obliterated by an out of > control jack-knifed tractor trailer truck. Was a long time ago, but it > happened. > > Just because probability may, or may not, predict a thing does not mean it > can or cannot happen. Nobody said it can not. One only mentioned that if single event has probability P. probability of two such events if they are independent is P squared, which (for small P) is much smaller than probability of single event. I guess from now on I really need to go and put on a clown makeup ;-) > > -Mike > > > > _______________________________________________ > 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 Tue Apr 19 21:33:26 2016 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 331ECB14A13 for ; Tue, 19 Apr 2016 21:33:26 +0000 (UTC) (envelope-from jon@radel.com) Received: from radel.com (fly.radel.com [70.184.242.170]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "*.radel.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D561911BA for ; Tue, 19 Apr 2016 21:33:25 +0000 (UTC) (envelope-from jon@radel.com) X-CGP-ClamAV-Result: CLEAN X-VirusScanner: Niversoft's CGPClamav Helper v1.18.7 (ClamAV engine v0.98.7) Received: from [2001:470:880a:4389:cd3f:351a:239d:ef64] (account jon@radel.com HELO gravenstein.local) by radel.com (CommuniGate Pro SMTP 6.1.2 _community_) with ESMTPSA id 1039553; Tue, 19 Apr 2016 21:33:23 +0000 Subject: Re: Raid 1+0 To: galtsev@kicp.uchicago.edu References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> <441t61efpv.fsf@be-well.ilk.org> <13260.128.135.52.6.1461084740.squirrel@cosmo.uchicago.edu> <57166A7F.2030104@radel.com> <44929.128.135.52.6.1461091476.squirrel@cosmo.uchicago.edu> Cc: freebsd-questions@freebsd.org From: Jon Radel Message-ID: <5716A422.6000707@radel.com> Date: Tue, 19 Apr 2016 17:33:22 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <44929.128.135.52.6.1461091476.squirrel@cosmo.uchicago.edu> Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms050409040707030607010608" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 21:33:26 -0000 This is a cryptographically signed message in MIME format. --------------ms050409040707030607010608 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable On 4/19/16 2:44 PM, Valeri Galtsev wrote: > My opinion that your conclusion that the drives having the same MTBF=20 > (or similar lifespans) are likely to die simultaneously contradicts my = > understanding of probability theory (or statistics basics). People=20 > life expectancy in some country is 75 years. Likelyhood that two=20 > _given_ people will die at age 40 is negligible. Even twin brothers=20 > are unlikely to die during the same week or Month. This one is between = > fundamental assumptions statistics is based on. Just my humble=20 > opinion. Valeri You're confusing presence of correlation with a layman's "really, really = likely." Of course the probability that two people of the same age will die in=20 the same month is higher than the probability that two randomly selected = people will die in the same month. Likelihood of death is not constant=20 throughout life. Frankly I take the actuaries that suggest my insurance = company up my life insurance premiums every 5 years waaaaaay more=20 seriously than you. If you assume away all the interesting bits, your conclusions get pretty = useless. Actually, people study this stuff. See, for example: http://biomedgerontology.oxfordjournals.org/content/53A/6/M441.full.pdf --Jon Radel jon@radel.com --------------ms050409040707030607010608 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC Cq8wggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4 dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290 MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak +FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC 4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb 4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ 26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT 9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl tukWeh95FPZKEBom+nyK+5swggX4MIIE4KADAgECAhBzVOU8fWu0zQ1gaQ38zgEbMA0GCSqG SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h aWwgQ0EwHhcNMTUwMzMwMDAwMDAwWhcNMTgwMzI5MjM1OTU5WjCB+jELMAkGA1UEBhMCVVMx DjAMBgNVBBETBTIyMTUwMQswCQYDVQQIEwJWQTEUMBIGA1UEBxMLU3ByaW5nZmllbGQxGjAY BgNVBAkTETY5MTcgUmlkZ2V3YXkgRHIuMRUwEwYDVQQKEwxKb24gVC4gUmFkZWwxMjAwBgNV BAsTKUlzc3VlZCB0aHJvdWdoIEpvbiBULiBSYWRlbCBFLVBLSSBNYW5hZ2VyMR8wHQYDVQQL ExZDb3Jwb3JhdGUgU2VjdXJlIEVtYWlsMRIwEAYDVQQDEwlKb24gUmFkZWwxHDAaBgkqhkiG 9w0BCQEWDWpvbkByYWRlbC5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDe 1Rth9hbQqaODn++C5dVAQH9nM2VH3oPazZufOwmIG2SXI/v3PuemcQQ3JkhmpQ06gYszyXbk TCLsqvEfalYj81jdt/K5lT4aVdj0LfJIWyTcU95V2rsCuHsSvn/PnIcsEtXg53rCtqS4EOtJ 9u3rY2hP8YCiyz1yY3mn4nKJs93MHG4AkXYuVpzfaIADETcVrA+razvXEfnDJXXDZZ9ZuuV1 06yIovOvhYWSlaVu8nrSHJjXFZI2IXwgIeVBoMih3yu6LLj14I/YdZ0rIA8K+UNB+NW6Ri3u wHXBbr4jh3ZqkrqIVUrf1VeybhdrJcdqXdMNHjKDSlCoaxYRbLy1AgMBAAGjggHVMIIB0TAf BgNVHSMEGDAWgBSSYWuC4aKgqk/sZ/HCo/e0gADB7DAdBgNVHQ4EFgQUz9YB10WEfBNHskRw o/0vh8qaQuwwDgYDVR0PAQH/BAQDAgWgMAwGA1UdEwEB/wQCMAAwHQYDVR0lBBYwFAYIKwYB BQUHAwQGCCsGAQUFBwMCMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQMFMCswKQYIKwYBBQUH AgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMF0GA1UdHwRWMFQwUqBQoE6GTGh0 dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET1NIQTI1NkNsaWVudEF1dGhlbnRpY2F0aW9u YW5kU2VjdXJlRW1haWxDQS5jcmwwgZAGCCsGAQUFBwEBBIGDMIGAMFgGCCsGAQUFBzAChkxo dHRwOi8vY3J0LmNvbW9kb2NhLmNvbS9DT01PRE9TSEEyNTZDbGllbnRBdXRoZW50aWNhdGlv bmFuZFNlY3VyZUVtYWlsQ0EuY3J0MCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5jb21vZG9j YS5jb20wGAYDVR0RBBEwD4ENam9uQHJhZGVsLmNvbTANBgkqhkiG9w0BAQsFAAOCAQEAS1Pe +gBgP+SQ/a5I5e7zX0Rg0DhH378LHlZixJgS6LfCPL2edKMUQi3Th9GXfLjdeyeWuMWoz925 ZzBHcPwkBeH+iM/AEhu0Dhi0kop/p66g9tEPJUZ/KDsqxddNDrD0Typn3/33pHTjJEDqydzA gwB0Nn8blpMbqSwT+j8wuPakfLsj1cSDzXrTLLsmIQB7auAyaYXdWyW8Yqw336rLUCvjOUfn qOOyjVsieTw/0PLoOHJaGyez+VtV4eyi6p1SNiX32A+fvxBMzKQLCokE43cXItc9Okzq//f2 fuvGp17r8mpm4OjjM5E2kwsg9bBPUBMR4/sxosKVLn0o9rxlozGCBEEwggQ9AgEBMIGwMIGb MQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdT YWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UEAxM4Q09NT0RPIFNI QS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEHNU5Tx9 a7TNDWBpDfzOARswDQYJYIZIAWUDBAIBBQCgggJhMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0B BwEwHAYJKoZIhvcNAQkFMQ8XDTE2MDQxOTIxMzMyMlowLwYJKoZIhvcNAQkEMSIEIEFPdTGI eE0/XZ+bqN4g55RKJ0jXXsP+M7ZzkB3zpfbQMGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUD BAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcN AwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgcEGCSsGAQQBgjcQBDGBszCBsDCBmzEL MAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2Fs Zm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxQTA/BgNVBAMTOENPTU9ETyBTSEEt MjU2IENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhBzVOU8fWu0 zQ1gaQ38zgEbMIHDBgsqhkiG9w0BCRACCzGBs6CBsDCBmzELMAkGA1UEBhMCR0IxGzAZBgNV BAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09N T0RPIENBIExpbWl0ZWQxQTA/BgNVBAMTOENPTU9ETyBTSEEtMjU2IENsaWVudCBBdXRoZW50 aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhBzVOU8fWu0zQ1gaQ38zgEbMA0GCSqGSIb3 DQEBAQUABIIBAMah4LFJ/xJtNSEUpJ7+xdxCADE1bpf6a6m/1vyCorljLX38y6FaRPJuUy4W nRpc3HBJO2S6sVt/heZFpViMCw0q835A8A/R6Oc8tUi709LeViSveV3HioVHQ9oTNf5SfBEM RdlWLukunKQKqEEcckSqXW75uTm/TnjAPf625CJQdyt613tTNs0+SOYY4sdQZhZDLgfgTF63 meKoIh30Nx3kzEa60vjFfEP9DpP90tMyLQ1pXYPsh574SKvrbMQwVduD+az7q+8lYBHFoENW B80Z4jMHWNSz/nB6rC9GD4AfLUHnwmv7SwZSbPerIjnLAixbEwu0GHzLRb4lh5N72EUAAAAA AAA= --------------ms050409040707030607010608-- From owner-freebsd-questions@freebsd.org Tue Apr 19 21:38:32 2016 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 79EFFB14C46 for ; Tue, 19 Apr 2016 21:38:32 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 042B5165C for ; Tue, 19 Apr 2016 21:38:31 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (liminal.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3636:3bff:fed4:b0d6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id EFB5311311 for ; Tue, 19 Apr 2016 21:38:21 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/EFB5311311; dkim=none; dkim-atps=neutral Subject: Re: Ports upgrade .... To: freebsd-questions@freebsd.org References: <571684CD.2070800@hiwaay.net> From: Matthew Seaman Message-ID: <5716A547.6030504@FreeBSD.org> Date: Tue, 19 Apr 2016 22:38:15 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <571684CD.2070800@hiwaay.net> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="eeVXmAnd7bTLH6VGUpTeLa0o7OM1JIrNq" X-Virus-Scanned: clamav-milter 0.99.1 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 21:38:32 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --eeVXmAnd7bTLH6VGUpTeLa0o7OM1JIrNq Content-Type: multipart/mixed; boundary="5DivdcA3D6S5kxo4VsollI4C5V9iEcBQP" From: Matthew Seaman To: freebsd-questions@freebsd.org Message-ID: <5716A547.6030504@FreeBSD.org> Subject: Re: Ports upgrade .... References: <571684CD.2070800@hiwaay.net> In-Reply-To: <571684CD.2070800@hiwaay.net> --5DivdcA3D6S5kxo4VsollI4C5V9iEcBQP Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 19/04/2016 20:18, William A. Mahaffey III wrote: > It brought down almost 14K updates for 3-ish weeks .... I know the port= s > effort is a feverish hive of productivity, but that sounded a bit high > :-) .... Is that number anomalous, maybe coincident w/ new quarter, > something else ? More question than problem, but curious. TIA & have a > good one. Yes. There was a change to the format of DEPENDS lines which has affected every ports Makefile. However, this does not mean that you'll need to recompile every port you have installed -- it doesn't affect the output from compiling the port in any way. It's coincident with the change of quarter, because modifying all the DEPENDS settings in the middle of a quarter would have made it impossible subsequently to MFH anything to the quarterly branch. Cheers, Matthew --5DivdcA3D6S5kxo4VsollI4C5V9iEcBQP-- --eeVXmAnd7bTLH6VGUpTeLa0o7OM1JIrNq Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJXFqVNXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATHrMQAIme+HI/9yJbWQFabCZJahtz LV5nMKNAAr89/AlcfmQQiSIWAMvrYe4ftbfUrev/TZScKBwzKDe+u4qg8uI24r5J eZm4KJHmO3BJGbMKY73Gx7J4hDcgVoWNKkZ9LNy/57EEr6AedXeC4ZDlDthwSD4f 8UVPPHh2uggnCH2x/bWRizn9zigdXg6fu/72drmXUftOr0CeZaYaTG2fId1G4k2S 9bhwREdqX5ZKTfQrokAMfnAmbYnBtVX16Ftcezde8xrwBCUxj6E+H4awX0P4Lss8 kKWClxOfko1o5KFUBmsjWHgU76u55MiOo4zmAWSl0R242cCCQiOM9nq3yEEfWXI8 O4RST9X4oUhRSGn9Y92FhPtKvJs3CpmNQcg+sxdQ8VGpXjjzeERpTblHhPY4by4O 7qVs6lxKgQnk+ppq16yPYm/VEg5+fzTOd90dYS7VkYa/ApCRcqXFSmJtFqaPYcVi ZQaE2cs0TBHdm6w/DJBHAuIAKha6titRC2jrSTGG/snP1FFVdEHSFXC9ns7ISQM+ n3VRst4ZdwJfEL0EYVTmjbhHs56OVZz9cWpzpGGCvOmgz7IBuwQINU8sUGNFjWRC jkiQ4XOBtZtKSO7HihQVq8skJBg3JBoDDGaORIXT9IbsNLBsy1sb8oTcV4NsDvgh u9fbAf7yRSjjzhD4/ft7 =4LVX -----END PGP SIGNATURE----- --eeVXmAnd7bTLH6VGUpTeLa0o7OM1JIrNq-- From owner-freebsd-questions@freebsd.org Tue Apr 19 21:43:22 2016 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 A6BA7B131AF for ; Tue, 19 Apr 2016 21:43:22 +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 842A91AD5 for ; Tue, 19 Apr 2016 21:43:22 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: by be-well.ilk.org (Postfix, from userid 1147) id B5C7F33C27; Tue, 19 Apr 2016 17:43:19 -0400 (EDT) From: Lowell Gilbert To: "Valeri Galtsev" Cc: "Steve O'Hara-Smith" , freebsd-questions@freebsd.org Subject: Re: Raid 1+0 References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> <20160419153824.7b679129f82a3cd0b18b9740@sohara.org> <40267.128.135.52.6.1461098148.squirrel@cosmo.uchicago.edu> Reply-To: freebsd-questions@freebsd.org Date: Tue, 19 Apr 2016 17:43:19 -0400 In-Reply-To: <40267.128.135.52.6.1461098148.squirrel@cosmo.uchicago.edu> (Valeri Galtsev's message of "Tue, 19 Apr 2016 15:35:48 -0500 (CDT)") Message-ID: <44a8kpcm14.fsf@be-well.ilk.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 21:43:22 -0000 "Valeri Galtsev" writes: > On Tue, April 19, 2016 9:38 am, Steve O'Hara-Smith wrote: >> On Mon, 18 Apr 2016 17:05:22 -0500 (CDT) >> "Valeri Galtsev" wrote: >> >>> Not correct. First of all, in most of the cases, failure of each of the >>> drives are independent events >> >> If only that were so. When the drives are as near identical as >> manufacturing can make them and have had very similar histories they >> can be expected to have very similar wear and be similarly close to >> failure at all times, which makes it likely that the load imposed by >> one failing will push another over. > > Sigh. You need suggest some physics that will make one drive affect > another (aged or not aged doesn't matter for me). Then you will have me in > your team. Correlation is not causation. It's not a big stretch to imagine that two nearly identical mechanical devices, operated in nearly identical conditions, might wear out in a nearly identical way at about the same time. There is no need for one drive to affect the other. A fair number of people believe that this in fact occurs. I've looked for evidence on the subject, and I haven't found anything (beyond anecdotes) for or against the possibility. From owner-freebsd-questions@freebsd.org Tue Apr 19 21:45:14 2016 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 D6A24B13338 for ; Tue, 19 Apr 2016 21:45:14 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.70.90]) by mx1.freebsd.org (Postfix) with ESMTP id B5A061C13 for ; Tue, 19 Apr 2016 21:45:14 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id DFC39CB8C99; Tue, 19 Apr 2016 16:45:13 -0500 (CDT) Received: from 128.135.52.6 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Tue, 19 Apr 2016 16:45:13 -0500 (CDT) Message-ID: <26823.128.135.52.6.1461102313.squirrel@cosmo.uchicago.edu> In-Reply-To: <5716A422.6000707@radel.com> References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> <441t61efpv.fsf@be-well.ilk.org> <13260.128.135.52.6.1461084740.squirrel@cosmo.uchicago.edu> <57166A7F.2030104@radel.com> <44929.128.135.52.6.1461091476.squirrel@cosmo.uchicago.edu> <5716A422.6000707@radel.com> Date: Tue, 19 Apr 2016 16:45:13 -0500 (CDT) Subject: Re: Raid 1+0 From: "Valeri Galtsev" To: "Jon Radel" Cc: galtsev@kicp.uchicago.edu, freebsd-questions@freebsd.org 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 21:45:14 -0000 On Tue, April 19, 2016 4:33 pm, Jon Radel wrote: > On 4/19/16 2:44 PM, Valeri Galtsev wrote: >> My opinion that your conclusion that the drives having the same MTBF >> (or similar lifespans) are likely to die simultaneously contradicts my >> understanding of probability theory (or statistics basics). People >> life expectancy in some country is 75 years. Likelyhood that two >> _given_ people will die at age 40 is negligible. Even twin brothers >> are unlikely to die during the same week or Month. This one is between >> fundamental assumptions statistics is based on. Just my humble >> opinion. Valeri > You're confusing presence of correlation with a layman's "really, really > likely." > > Of course the probability that two people of the same age will die in > the same month is higher than the probability that two randomly selected > people will die in the same month. Likelihood of death is not constant > throughout life. Frankly I take the actuaries that suggest my insurance > company up my life insurance premiums every 5 years waaaaaay more > seriously than you. > > If you assume away all the interesting bits, your conclusions get pretty > useless. > > Actually, people study this stuff. See, for example: > > http://biomedgerontology.oxfordjournals.org/content/53A/6/M441.full.pdf I give up. My mathematics professor would call it "existence theorem": Whatever way you will find to simplify your point for digest by one person, there exists another person that will ridicule that sort of presentation. Going back to where it started. This still doesn't convince me that hard drives in my server room will start (or do already) die in pairs. Nope. Doesn't happen. And there are many of them made by same manufacturer, same model, same production date, same batch. Valeri > > --Jon Radel > jon@radel.com > > ++++++++++++++++++++++++++++++++++++++++ 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 Tue Apr 19 21:57:42 2016 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 06125B138A6 for ; Tue, 19 Apr 2016 21:57:42 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-io0-x242.google.com (mail-io0-x242.google.com [IPv6:2607:f8b0:4001:c06::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 C463A11AF; Tue, 19 Apr 2016 21:57:41 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-io0-x242.google.com with SMTP id u185so4528320iod.2; Tue, 19 Apr 2016 14:57:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=I6xrXhe7mEJkIppp7Y7g4kiUM+6Hq5WmwK4UWxpMNM8=; b=wnXke8eDiZaudkTBhlXe9N8IQlhcnK/BSs/5e71tZLMTob03NKQ2YNTqBWAE/6Wcsx xBemKsireo1pjPRdEQQzT6sNzm5JsVJdEsE8QD2pL4zIvN6SjvUyE1biRgMWLyfQdqL6 AWMP4eT1I9wPUQJ22R1LnrkfXO22x4U/QXObXrfwcTDmjA3Ih17CBZoO0WAkiN4Lmc/b 3wS1UXbFhvXL+m9Rh0aH7uaQF1dyZFJkb3dmRIseaoBjbRZGD36T2fYcFMvQYcG4cr23 7P7Tg1//4rv0TDM5gm+TsLqcgYCFJCSvRsX+d9eTN1RkFv5rzHJVXPMbPGrMU3eux6pn 6Itg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=I6xrXhe7mEJkIppp7Y7g4kiUM+6Hq5WmwK4UWxpMNM8=; b=ZxS16WXFnheH5Kan6somS64iJh6N+bcnJFQvWytJJH6BSPjNb5T4JexNrZQanuntvS W8gQ85JSa11WEZavcoEv5iD9OJw9YttPlbIQB4NcwGdayCJmvKhl6fb/juZmtLtueiL9 j9r6Wuaj7Kc7Ey6Oz9IhCZtDhy8aXNbAjB78LTLowyuy3hJz6Px5cHmHN0nCUmFF8XWv eHXovzJyhzwNf9OMFTZoSUVkQ3vBpV4RW/wlKeMyinbcl4ManUF1VRFbMesk6442wQj+ SDppCB54Zhku4JTSUSZ9kMpAxBLO78mVBI756Jnh/c+tuDiz78ioyXabRiCtXnRXnXf7 ZttA== X-Gm-Message-State: AOPr4FWV24oc5iZh0itFaN+X0JCM7QlEJdaKsZIIlqRT1GgYsrLGN4QhzhNwuPxZo9KWOA== X-Received: by 10.107.17.19 with SMTP id z19mr6363568ioi.43.1461103061126; Tue, 19 Apr 2016 14:57:41 -0700 (PDT) Received: from [10.0.10.3] (cpe-76-190-244-6.neo.res.rr.com. [76.190.244.6]) by smtp.googlemail.com with ESMTPSA id l80sm1161900iod.14.2016.04.19.14.57.40 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 19 Apr 2016 14:57:40 -0700 (PDT) Message-ID: <5716A9D9.4040102@gmail.com> Date: Tue, 19 Apr 2016 17:57:45 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Matthew Seaman CC: freebsd-questions@freebsd.org Subject: Re: daily security run output - Checking setuid References: <5716234C.1020900@gmail.com> <5716401C.2000606@FreeBSD.org> In-Reply-To: <5716401C.2000606@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 21:57:42 -0000 Matthew Seaman wrote: > On 2016/04/19 13:23, Ernie Luzar wrote: >> This morning the "daily security run output" lists a lot of files under >> the heading of Checking setuid files & devices. I have never seen this >> before. >> >> What does this mean? >> Has my system been breached? >> Where is the "daily security run output" documented? > > The output usually shows any changes to the lists of setuid or setgid > files on your system. Take note of the leading '+' or '-' characters in > that output. Suddenly adding one or a few new setuid files is > suspicious. Adding write permissions to those files is frequently > suspicious. However adding or removing /lots/ of setuid or setgid files > all at once is more likely to be down to operator error. > > The daily script depends on keeping a list of all the known setuid / > setgid files in (by default) /var/log/setuid.today and > /var/log/setuid.yesterday. If one or both of those files get deleted or > modified, or that partition fills up while the security/100.chksetuid > script is running, you'll get spurious output. > > Setuid programs are often viewed as a security problem by inexperienced > administrators, and some even go as far as turning off the setuid > functionality. That, however, is one of those mistakes you only make > once. Properly implemented, setuid and setgid *improves* your system > security, and it's necessary for the system to function normally. > > Cheers, > > Matthew > Thank you Matthew for your reply. I am well aware of the security concerns of fies showing up on this report. My problem is I can not find any documentation describing what the meaning of the report columns are. Like what does the leading + or - characters really mean. If the changing of the setuid or setgid caused the file to show up on the report, how do I know what they were before and what they are now? I sure don't see anything labeled setuid or setgid on the report. Here is some of the report I got as example. 570967 -r-sr-xr-x 6 root wheel 18320 Mar 24 23:52:23 2016 /usr/bin/ypchpass 570967 -r-sr-xr-x 6 root wheel 18320 Mar 24 23:52:23 2016 /usr/bin/ypchsh 571182 -r-sr-xr-x 2 root wheel 6516 Mar 24 23:52:27 2016 /usr/bin/yppasswd - 804930 -r-sr-xr-x 1 root wheel 18912 Mar 24 23:51:54 2016 /usr/jails/sharedfs/bin/rcp - 805128 -r-sr-xr-- 1 root operator 7716 Mar 24 23:52:06 2016 /usr/jails/sharedfs/sbin/mksnap_ffs - 805089 -r-sr-xr-x 1 root wheel 25700 Mar 24 23:52:06 2016 /usr/jails/sharedfs/sbin/ping - 805082 -r-sr-xr-x 1 root wheel 33836 Mar 24 23:52:06 2016 /usr/jails/sharedfs/sbin/ping6 - 805062 -r-sr-xr-- 2 root operator 10952 Mar 24 23:52:07 2016 /usr/jails/sharedfs/sbin/poweroff - 805062 -r-sr-xr-- 2 root operator 10952 Mar 24 23:52:07 2016 /usr/jails/sharedfs/sbin/shutdown - 804915 -r-sr-xr-x 4 root wheel 23312 Mar 24 23:52:22 2016 /usr/jails/sharedfs/usr/bin/at - 804915 -r-sr-xr-x 4 root wheel 23312 Mar 24 23:52:22 2016 /usr/jails/sharedfs/usr/bin/atq Thanks for any help. From owner-freebsd-questions@freebsd.org Tue Apr 19 22:01:07 2016 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 6A499B13B5A for ; Tue, 19 Apr 2016 22:01:07 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2EEFE14B1 for ; Tue, 19 Apr 2016 22:01:06 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1asdhg-00064N-CX for freebsd-questions@freebsd.org; Wed, 20 Apr 2016 00:01:04 +0200 Received: from pool-72-66-1-32.washdc.fios.verizon.net ([72.66.1.32]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 20 Apr 2016 00:01:04 +0200 Received: from nightrecon by pool-72-66-1-32.washdc.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 20 Apr 2016 00:01:04 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Michael Powell Subject: Re: Raid 1+0 Date: Tue, 19 Apr 2016 18:02:02 -0400 Lines: 15 Message-ID: References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> <441t61efpv.fsf@be-well.ilk.org> <13260.128.135.52.6.1461084740.squirrel@cosmo.uchicago.edu> <57166A7F.2030104@radel.com> <44929.128.135.52.6.1461091476.squirrel@cosmo.uchicago.edu> <36540.128.135.52.6.1461101503.squirrel@cosmo.uchicago.edu> Reply-To: nightrecon@hotmail.com Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pool-72-66-1-32.washdc.fios.verizon.net X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 22:01:07 -0000 Valeri Galtsev wrote: [snip] > Do we really need to continue this? On the other hand, two clowns may be > giving public good entertainment ;-) No. You're absolutely right. Was just in a bikeshedding mood after seeing how far astray everything went from the original OP question. Sometimes it's funny to see how far it can go, but you're absolutely right that at some point it needs to stop. Best wishes and kindly regards -Mike From owner-freebsd-questions@freebsd.org Tue Apr 19 22:05:54 2016 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 94DBCB13D02 for ; Tue, 19 Apr 2016 22:05:54 +0000 (UTC) (envelope-from johnl@iecc.com) Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "miucha.iecc.com", Issuer "StartCom Class 1 DV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2B52D18E3 for ; Tue, 19 Apr 2016 22:05:54 +0000 (UTC) (envelope-from johnl@iecc.com) Received: (qmail 89966 invoked from network); 19 Apr 2016 22:05:52 -0000 Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 19 Apr 2016 22:05:52 -0000 Date: 19 Apr 2016 22:05:30 -0000 Message-ID: <20160419220530.14065.qmail@ary.lan> From: "John Levine" To: freebsd-questions@freebsd.org Cc: steve@sohara.org Subject: Re: Raid 1+0 In-Reply-To: <20160419180715.f788945fb67388a707c60ee7@sohara.org> Organization: X-Headerized: yes Mime-Version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 22:05:54 -0000 > Next Look at the curves for failure probability against age (or >total activity) and note that the classic bathtub shape and consider what >happens when your whole array is on the steep bit at the end and the first >drive failure happens. Drive makers, not being totally dim, try to design their drives so that they won't fail during the warranty period, but who cares after that. So it's not surprising that the failure rate goes up a lot shortly after the warranty expires. Also, if you buy a bunch of identical drives and slap them into a RAID, they're likely from the same production run and will have similar failure characteristics. I try to mix drives from different manufacturers, or at least with dates at least a month apart so they're not from the same production run. R's, John From owner-freebsd-questions@freebsd.org Tue Apr 19 23:15:58 2016 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 13E3AB1560A for ; Tue, 19 Apr 2016 23:15:58 +0000 (UTC) (envelope-from Lowell@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 C50EE1160; Tue, 19 Apr 2016 23:15:57 +0000 (UTC) (envelope-from Lowell@Be-Well.Ilk.Org) Received: from lowell-desk.lan (router.lan [172.30.250.2]) by be-well.ilk.org (Postfix) with ESMTP id C1D1833C27; Tue, 19 Apr 2016 19:15:44 -0400 (EDT) Received: by lowell-desk.lan (Postfix, from userid 1147) id AC2983981C; Tue, 19 Apr 2016 19:15:43 -0400 (EDT) From: Lowell Gilbert To: Ernie Luzar Cc: Matthew Seaman , freebsd-questions@freebsd.org Subject: Re: daily security run output - Checking setuid References: <5716234C.1020900@gmail.com> <5716401C.2000606@FreeBSD.org> <5716A9D9.4040102@gmail.com> Reply-To: freebsd-questions@freebsd.org Date: Tue, 19 Apr 2016 19:15:43 -0400 In-Reply-To: <5716A9D9.4040102@gmail.com> (Ernie Luzar's message of "Tue, 19 Apr 2016 17:57:45 -0400") Message-ID: <44mvopkx5s.fsf@lowell-desk.lan> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 23:15:58 -0000 Ernie Luzar writes: > Matthew Seaman wrote: >> On 2016/04/19 13:23, Ernie Luzar wrote: >>> This morning the "daily security run output" lists a lot of files under >>> the heading of Checking setuid files & devices. I have never seen this >>> before. >>> >>> What does this mean? >>> Has my system been breached? >>> Where is the "daily security run output" documented? >> >> The output usually shows any changes to the lists of setuid or setgid >> files on your system. Take note of the leading '+' or '-' characters in >> that output. Suddenly adding one or a few new setuid files is >> suspicious. Adding write permissions to those files is frequently >> suspicious. However adding or removing /lots/ of setuid or setgid files >> all at once is more likely to be down to operator error. >> >> The daily script depends on keeping a list of all the known setuid / >> setgid files in (by default) /var/log/setuid.today and >> /var/log/setuid.yesterday. If one or both of those files get deleted or >> modified, or that partition fills up while the security/100.chksetuid >> script is running, you'll get spurious output. >> >> Setuid programs are often viewed as a security problem by inexperienced >> administrators, and some even go as far as turning off the setuid >> functionality. That, however, is one of those mistakes you only make >> once. Properly implemented, setuid and setgid *improves* your system >> security, and it's necessary for the system to function normally. >> >> Cheers, >> >> Matthew >> > Thank you Matthew for your reply. I am well aware of the security > concerns of fies showing up on this report. My problem is I can not > find any documentation describing what the meaning of the report > columns are. > > Like what does the leading + or - characters really mean. > > If the changing of the setuid or setgid caused the file to show up on > the report, how do I know what they were before and what they are now? > I sure don't see anything labeled setuid or setgid on the report. > Here is some of the report I got as example. > > 570967 -r-sr-xr-x 6 root wheel 18320 Mar 24 23:52:23 2016 /usr/bin/ypchpass > 570967 -r-sr-xr-x 6 root wheel 18320 Mar 24 23:52:23 2016 /usr/bin/ypchsh > 571182 -r-sr-xr-x 2 root wheel 6516 Mar 24 23:52:27 2016 /usr/bin/yppasswd > - 804930 -r-sr-xr-x 1 root wheel 18912 Mar 24 23:51:54 2016 /usr/jails/sharedfs/bin/rcp > - 805128 -r-sr-xr-- 1 root operator 7716 Mar 24 23:52:06 2016 /usr/jails/sharedfs/sbin/mksnap_ffs > - 805089 -r-sr-xr-x 1 root wheel 25700 Mar 24 23:52:06 2016 /usr/jails/sharedfs/sbin/ping > - 805082 -r-sr-xr-x 1 root wheel 33836 Mar 24 23:52:06 2016 /usr/jails/sharedfs/sbin/ping6 > - 805062 -r-sr-xr-- 2 root operator 10952 Mar 24 23:52:07 2016 /usr/jails/sharedfs/sbin/poweroff > - 805062 -r-sr-xr-- 2 root operator 10952 Mar 24 23:52:07 2016 /usr/jails/sharedfs/sbin/shutdown > - 804915 -r-sr-xr-x 4 root wheel 23312 Mar 24 23:52:22 2016 /usr/jails/sharedfs/usr/bin/at > - 804915 -r-sr-xr-x 4 root wheel 23312 Mar 24 23:52:22 2016 /usr/jails/sharedfs/usr/bin/atq It's a diff(1) of the output of 'ls -liTd' of these files from the previous day to the present day. The leading '-' tells you that these are all files that have either been removed since yesterday or are still present but no longer have their setuid bit set. Many system administrators will find this intuitive, but those who don't will figure it out by looking at /etc/periodic/security/ and determining that the 100.chksetuid script is the one that checks setuid settings. From owner-freebsd-questions@freebsd.org Wed Apr 20 00:05:28 2016 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 0D45BB1583C for ; Wed, 20 Apr 2016 00:05:28 +0000 (UTC) (envelope-from xxjack12xx@gmail.com) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DA73A10BD for ; Wed, 20 Apr 2016 00:05:27 +0000 (UTC) (envelope-from xxjack12xx@gmail.com) Received: by mail-io0-x22c.google.com with SMTP id f89so24216509ioi.0 for ; Tue, 19 Apr 2016 17:05:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=v1IoO7oc4T2pY8l5K/uAi3ZLMCxMjfOPNoMDLNfRDyU=; b=wJGPUTEuuob17ErWGg6g2GiCQPduAkgWq/jJlf/dTy1mynpTlhZ+lwtgxB9+vLHBoU GoBrZwRSwIgbHuYYguTyo4uMbGaKoTps+T22he0GrBARVuzwFDqIkzgBE2yRwC5ao3Xd vp1ckJSntFNbLsnG+612RsRSbvpU9OkFZhedVUgNpsQ06FJ8YaIQ/teWnJSbkxILlL8d k8MzFf2Y2jWUTSa6YHafQxuDA3Vh7UsyUUNmVN6DoIt4Zk81VEfoCnfQ+NoVXCbUZRPt mDrXjTfGq1uLLWK8kYVdTUfsisEBKnE0qxEHX5+7Ci5CL61nFA4tCwBRJWsvB0S6MXt8 ZLkg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=v1IoO7oc4T2pY8l5K/uAi3ZLMCxMjfOPNoMDLNfRDyU=; b=NC4vwmRR6IjtlLIkQeNHpOXV+qx1Qja9n0KHaQCUHbkJT/wbZndoyrZe4t2C3jb7Z+ 3xWTzcepqm9rjsHlpjWXX47Dq9T+igpY5m51v+lZHl93q8UsuezdefSnPeDBa5ILDBVZ mcjae4pDDLBA7zY0B7TyFMMJEh/ykKTUfREdUCi+b0tPPR7YEz3B7EUOOUTD0a/8hNxS II+lpRspZXTggw2O6CiQCNTZrdR7m5trpN2t7QEEvYh4MCbZVP7Ncfe0m0ol0B9OyrV9 6JNHOAZv7BbFJf6WKKmgGdoAMbG8o1CX/yL4rLvbEhbjNjQmz5EUV8240AZZgnykBYPd vy4A== X-Gm-Message-State: AOPr4FU5RjfdLG40XCgXJ13/TM7+4VMLBOszV5N4M25yUZoXLD4ZLBWM6wA+fITgfdIYPyFQaoDHeoIy2QN45g== X-Received: by 10.107.59.85 with SMTP id i82mr6743688ioa.134.1461110727317; Tue, 19 Apr 2016 17:05:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.41.129 with HTTP; Tue, 19 Apr 2016 17:04:47 -0700 (PDT) In-Reply-To: <44a8kpcm14.fsf@be-well.ilk.org> References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> <20160419153824.7b679129f82a3cd0b18b9740@sohara.org> <40267.128.135.52.6.1461098148.squirrel@cosmo.uchicago.edu> <44a8kpcm14.fsf@be-well.ilk.org> From: "Jack L." Date: Tue, 19 Apr 2016 17:04:47 -0700 Message-ID: Subject: Re: Raid 1+0 To: "freebsd-questions@freebsd.org" Cc: Valeri Galtsev , "Steve O'Hara-Smith" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 00:05:28 -0000 On Tue, Apr 19, 2016 at 2:43 PM, Lowell Gilbert wrote: > "Valeri Galtsev" writes: > >> On Tue, April 19, 2016 9:38 am, Steve O'Hara-Smith wrote: >>> On Mon, 18 Apr 2016 17:05:22 -0500 (CDT) >>> "Valeri Galtsev" wrote: >>> >>>> Not correct. First of all, in most of the cases, failure of each of the >>>> drives are independent events >>> >>> If only that were so. When the drives are as near identical as >>> manufacturing can make them and have had very similar histories they >>> can be expected to have very similar wear and be similarly close to >>> failure at all times, which makes it likely that the load imposed by >>> one failing will push another over. >> >> Sigh. You need suggest some physics that will make one drive affect >> another (aged or not aged doesn't matter for me). Then you will have me in >> your team. > > Correlation is not causation. > > It's not a big stretch to imagine that two nearly identical mechanical > devices, operated in nearly identical conditions, might wear out in a > nearly identical way at about the same time. There is no need for one > drive to affect the other. > > A fair number of people believe that this in fact occurs. I've looked > for evidence on the subject, and I haven't found anything (beyond > anecdotes) for or against the possibility. I think all hard drives are garbage and can die at any unpredictable time. Doesn't matter what brand, what model, what type, they all die unexpectedly. With that, I just make sure I have good backups just in case there's multiple drive failures in a raid set. From owner-freebsd-questions@freebsd.org Wed Apr 20 00:20:35 2016 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 7ADC5B15CF7 for ; Wed, 20 Apr 2016 00:20:35 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3389619DA for ; Wed, 20 Apr 2016 00:20:34 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id u3K0KXwW006072 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 19 Apr 2016 18:20:33 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id u3K0KX6a006069; Tue, 19 Apr 2016 18:20:33 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Tue, 19 Apr 2016 18:20:33 -0600 (MDT) From: Warren Block To: "Brandon J. Wandersee" cc: freebsd-questions@freebsd.org Subject: Re: Simple devd.conf rule has no effect In-Reply-To: <86bn552vga.fsf@WorkBox.Home> Message-ID: References: <86fuuywldn.fsf@WorkBox.Home> <86bn552vga.fsf@WorkBox.Home> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Tue, 19 Apr 2016 18:20:33 -0600 (MDT) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 00:20:35 -0000 On Tue, 19 Apr 2016, Brandon J. Wandersee wrote: > > Warren Block writes: > >> On Wed, 6 Apr 2016, Brandon J. Wandersee wrote: >> >>> >>> Hi, folks. I'm trying to get my laptop screen to lock when the lid >>> closes, using x11/slock. I've created the file /etc/devd/lidlock.conf >>> with the following rule: >>> >>> | notify 0 { >>> | match "system" "ACPI"; >>> | match "subsystem" "Lid"; >>> | match "notify" "0x00"; >>> | action "/usr/local/bin/slock"; >>> | }; >>> >>> This is really just a slight variation on the example from the >>> devd.conf(5) man page. Now when I close the lid, the screen fails to >>> lock, yet /var/log/messages displays the message "devd: Executing >>> 'slock'". Any advice on what to look into to figure out why the program >>> is not actually executed? Thanks in advace. >> >> devd(8) stuff runs as root, I think. So it probably does not have >> $DISPLAY set. Maybe use su to switch to the normal X user and execute >> the command: >> >> su -l xusername -c 'setenv DISPLAY :0.0 && /usr/local/bin/slock' > > Thanks for the response, Warren; sorry for the lateness of mine. Your > solution works when run from a shell, but devd still doesn't properly > execute it. I also tried changing the quotes around, adapting it for my > user shell (changing 'setenv' to 'export DISPLAY='), and putting it in a > shell script and executing the script from the devd config file. No > luck. Guess I'll just keep messing with it when the mood strikes, see if > anything clicks. This was actually a good time for a reply, as I needed to set up something similar. The idea was to run xlock before suspending so text on the screen is not visible when it wakes up. This, based on your example, finally worked: notify 20 { match "system" "ACPI"; match "subsystem" "Lid"; match "notify" "0x00"; action "/usr/bin/su wblock -c '/usr/local/bin/xlock -display :0.0 -mode qix & /bin/sleep 2'"' action "acpiconf -s3"; }; Running xlock as my unprivileged user might not be necessary, but seems safer. The 'sleep 2' might not be required, either, but it didn't want to work correctly until I did that. More experimentation is needed. The second action runs as root to suspend the machine. There is /etc/rc.suspend, but X already seemed to be stopped by the time that executed. Or something prevented running xlock from in there. From owner-freebsd-questions@freebsd.org Wed Apr 20 00:36:06 2016 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 D6EAAB13454 for ; Wed, 20 Apr 2016 00:36:06 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A122810B5 for ; Wed, 20 Apr 2016 00:36:06 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id u3K0a54W010027 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 19 Apr 2016 18:36:05 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id u3K0a5DI010024; Tue, 19 Apr 2016 18:36:05 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Tue, 19 Apr 2016 18:36:05 -0600 (MDT) From: Warren Block To: "Brandon J. Wandersee" cc: freebsd-questions@freebsd.org Subject: Re: Simple devd.conf rule has no effect In-Reply-To: Message-ID: References: <86fuuywldn.fsf@WorkBox.Home> <86bn552vga.fsf@WorkBox.Home> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Tue, 19 Apr 2016 18:36:05 -0600 (MDT) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 00:36:06 -0000 Quick followup with an improvement: notify 20 { match "system" "ACPI"; match "subsystem" "Lid"; match "notify" "0x00"; action "/usr/bin/su wblock -c '/usr/local/bin/xlock -display :0.0 -mode qix &'"' action "acpiconf -s3"; }; It was backgrounding xlock that was important, not a delay after it started. From owner-freebsd-questions@freebsd.org Wed Apr 20 02:17:57 2016 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 2AD43B150D0 for ; Wed, 20 Apr 2016 02:17:57 +0000 (UTC) (envelope-from sales7@meritvendor.com) Received: from mail-oi0-x248.google.com (mail-oi0-x248.google.com [IPv6:2607:f8b0:4003:c06::248]) (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 F3A2F1EAE for ; Wed, 20 Apr 2016 02:17:56 +0000 (UTC) (envelope-from sales7@meritvendor.com) Received: by mail-oi0-x248.google.com with SMTP id f63so44288910oig.1 for ; Tue, 19 Apr 2016 19:17:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=meritvendor.com; s=google; h=mime-version:message-id:date:subject:from:to; bh=s2PLsUsiE7v2COYOy4z87WVqLu+6eIsfu4UzhyjAbRs=; b=GS2MElBFwbOa9hM5HW7TPQoaR+LYJjtLXbHq5RHmO1qXYqYPNWaRcrPvBb+/4YLmYa M9r3AN8nuPvJVEOHQd1ZC0F9TRwwAlAmQQYhZ9oUy/+2RC7FiFqslI55N4J6OB6aGCT4 7AO9IqvkC95VMqrL/AaL0N479GGyydbsBv5F0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:message-id:date:subject:from:to; bh=s2PLsUsiE7v2COYOy4z87WVqLu+6eIsfu4UzhyjAbRs=; b=KTrtd1J7Z1skRk7cPB9/T7b3qY8KhYG4y6FX2rjE08PGkTnXnHoU2UC2VKPsclX0Fz xB/fctiz79urmxRif3TYRqf1VSx06rzb3CW15i5RwPzeH/qR42wTfHI9jStIhHzUzrX1 eNAjz81jelsvwQ8BdwFnsGIXSMXI4amAzG61Cyn4w0geFC7ddv572yFEKvLWoVMd2bpX 6tIYmLNAkNmtUATEBA9xil4xLmxwiVy0HEZ09VlnlWNUtPP9RAEN+4E9DYsd75+2S1n6 pqFkGGV/7y2iDQcVHpdRx7R1A/w6M4uNCUBYF1DSLhzFkhOUnbXYjEbDVeeqOkMguEG4 16/A== X-Gm-Message-State: AOPr4FXkLNTAaksAybOgaxzMspc87IH5DgaEy12fZb0fDEnIGkl3LT8kyixNEaJTQ/iCm4eT6Fz8r9s8LugDlog9 MIME-Version: 1.0 X-Received: by 10.157.37.144 with SMTP id q16mr3967064ota.39.1461118676040; Tue, 19 Apr 2016 19:17:56 -0700 (PDT) Message-ID: <001a11454a7ca9042c0530e13342@google.com> Date: Wed, 20 Apr 2016 02:17:56 +0000 Subject: Attention required: Your website may be in trouble: lemis.com From: Paulo Climachauska To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 02:17:57 -0000 Hi lemis.com Team, I trust you are doing splendidly. I have gone through your website and I comprehend that it's well built, but can be improved in several ways to get better sales and revenue from the site. If you would like me to send you a complete list of upgrades and improvements we could do to your site then kindly let me know so that I can send you the brief quotation for your website. After in-depth research about your website and analyzing the targeted market for your business to prevail, we also execute effective online marketing campaigns by targeting not only local markets but also provincial and international markets as well. However you will be getting *all-in-one services* when contacting us. Search engine optimization is one of the best ways to create targeted traffic for your website. Without traffic, you don't have anybody visiting your site to turn into buyers. It's only search engine tricks that need to keep changing when the ranking algorithm changes. We will help you to increase your visibility in all the major search engines by *improving keyword rankings* and *boosting your real time website traffic* with lots of back links which are always done through *White Hat* techniques. Indeed you position your website properly to be found at the most critical points in the buying process or when people need your site. Our aim is to provide you with complete web marketing solutions to help your website rank high on the search engines. Before moving on further, we will have a consultation phase where we will discuss what your website goals are and how we can accomplish them. In addition, we may ask you certain questions that may be concerning on the website structure and strategic foundation for your social media marketing. Should you have any questions, please let us know. To improve the search engine visibility of your website, we look forward to hearing from you after you have had time to read our proposal. Best Regards, *Paulo Climachauska* From owner-freebsd-questions@freebsd.org Wed Apr 20 04:28:21 2016 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 59A3BB0DBF1 for ; Wed, 20 Apr 2016 04:28:21 +0000 (UTC) (envelope-from nervoso@k1.com.br) Received: from erouter6.ore.mailhop.org (erouter6.ore.mailhop.org [54.187.213.119]) (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 306481310 for ; Wed, 20 Apr 2016 04:28:20 +0000 (UTC) (envelope-from nervoso@k1.com.br) X-MHO-User: 45e51645-06b0-11e6-b8f9-33a5b3560672 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 186.228.82.163 X-Mail-Handler: DuoCircle Outbound SMTP Received: from mailserver2.k1.com.br (unknown [186.228.82.163]) by outbound3.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Wed, 20 Apr 2016 04:28:03 +0000 (UTC) Received: from lenzinote.lenzicasa (179.184.51.72.static.gvt.net.br [179.184.51.72] (may be forged)) (authenticated bits=0) by mailserver2.k1.com.br (8.15.2/8.15.2) with ESMTPSA id u3K4SDJ0020609 (version=TLSv1.2 cipher=DHE-DSS-AES128-GCM-SHA256 bits=128 verify=NOT); Wed, 20 Apr 2016 01:28:14 -0300 (BRT) (envelope-from nervoso@k1.com.br) Message-ID: <1461126503.80865.3.camel@k1.com.br> Subject: Re: Does HP DeskJet 1112 work with lpd on FreeBSD 10.2 amd64 ? From: =?ISO-8859-1?Q?S=E9rgio?= de Almeida Lenzi To: Matthias Apitz , freebsd-questions@freebsd.org Date: Wed, 20 Apr 2016 01:28:23 -0300 In-Reply-To: <20160419141207.GA2799@c720-r292778-amd64.oa.oclc.org> References: <20160419141207.GA2799@c720-r292778-amd64.oa.oclc.org> X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 04:28:21 -0000 I have it working but only on previous version of cups here I have... hplip-3.14.10_1                Drivers and utilities for HP Printers and All-in-One devices hplip-plugin-3.14.10           Binary plugin for some HP Printers and All-in-One devices and hplip built with the following dependecies: pkg info -qd hplip        py27-qt4-gui-4.11.4,1 python27-2.7.11_1 cups-filters-1.8.3 py27-pillow-3.1.1_1 sane-backends-1.0.25 jpeg-8_6 py27-gobject-2.28.6_6 usbutils-0.86_2 net-snmp-5.7.3_11 ghostscript9-agpl-base-9.16_5 cups-pstoraster-8.15.4_8 cups-2.1.3_2 py27-qt4-dbussupport-4.11.4_1 py27-dbus-1.2.0_1 dbus-1.8.20,1 xsane-0.999_5 glib-2.46.2 xdg-utils-1.1.1 If you are interested I can send you the link for installing from one of our servers... via pkg install -y hplip-plugin ##SELECTION_END## From owner-freebsd-questions@freebsd.org Wed Apr 20 05:37:10 2016 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 2E047B15903 for ; Wed, 20 Apr 2016 05:37:10 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 012D01E92 for ; Wed, 20 Apr 2016 05:37:09 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (dynamic-216-186-226-44.knology.net [216.186.226.44] (may be forged)) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id u3K5b7gv029595 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Wed, 20 Apr 2016 00:37:08 -0500 Subject: Re: Ports upgrade .... To: freebsd-questions@freebsd.org References: <571684CD.2070800@hiwaay.net> <5716A547.6030504@FreeBSD.org> From: "William A. Mahaffey III" Message-ID: <1c3c340b-f110-ceb4-55f2-d2f05062ce37@hiwaay.net> Date: Wed, 20 Apr 2016 00:42:37 -0453.75 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <5716A547.6030504@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 05:37:10 -0000 On 04/19/16 16:44, Matthew Seaman wrote: > On 19/04/2016 20:18, William A. Mahaffey III wrote: >> It brought down almost 14K updates for 3-ish weeks .... I know the ports >> effort is a feverish hive of productivity, but that sounded a bit high >> :-) .... Is that number anomalous, maybe coincident w/ new quarter, >> something else ? More question than problem, but curious. TIA & have a >> good one. > Yes. There was a change to the format of DEPENDS lines which has > affected every ports Makefile. However, this does not mean that you'll > need to recompile every port you have installed -- it doesn't affect the > output from compiling the port in any way. > > It's coincident with the change of quarter, because modifying all the > DEPENDS settings in the middle of a quarter would have made it > impossible subsequently to MFH anything to the quarterly branch. > > Cheers, > > Matthew > > *Boooyah* !!! I pretty much figured as much, just curious .... -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr. From owner-freebsd-questions@freebsd.org Wed Apr 20 09:11:30 2016 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 D626BB15615 for ; Wed, 20 Apr 2016 09:11:30 +0000 (UTC) (envelope-from brandon.wandersee@gmail.com) Received: from mail-ig0-f193.google.com (mail-ig0-f193.google.com [209.85.213.193]) (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 AEF821C68 for ; Wed, 20 Apr 2016 09:11:30 +0000 (UTC) (envelope-from brandon.wandersee@gmail.com) Received: by mail-ig0-f193.google.com with SMTP id kb1so5825671igb.3 for ; Wed, 20 Apr 2016 02:11:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:user-agent:from:to:cc:subject :in-reply-to:date:message-id:mime-version; bh=SgtVY6ECnNfI4CcQW41flOeJQXzdI4ZFO4SKbzSn9lo=; b=BSeJDCoTa+Aeot7qqp371r7mWndysCZms94gz0+gDAD7lxVe4SK1/1IFRREUhGlvUR jI0O/+AI+5qFAe9xxq8IIl+inQRVZ/gDm1KdgIxMMrj1aKBioiwxIjbjZLlSFVOsgMkN hBLH9Dlzss+KIRNVs1u89MTVq1rPBWrehCNvQEOzZwt1DBPgUJ0NIzC4ldxbVcFN1XsB 5OYyk37Xi5aiojWG87W+G/FJFmt/qHc+eecotEsPTTiT5RBU+pKlKIg0s7Dg54+j0gys AymwVRdGcjTtdCXyFHpG+JlnlTF/bSQclRnbnnQzq4m7LopHZYLqKV9sbBpVyXRHxurs 7IhA== X-Gm-Message-State: AOPr4FVM97xgIoB9U6lAqkT2zENBxit2klwGIW/rf+VlFPizWA4zpPpeKQV8JB1AExxdGA== X-Received: by 10.50.8.40 with SMTP id o8mr6059912iga.17.1461097797470; Tue, 19 Apr 2016 13:29:57 -0700 (PDT) Received: from WorkBox.Home.gmail.com (97-116-17-82.mpls.qwest.net. [97.116.17.82]) by smtp.gmail.com with ESMTPSA id f71sm987511iof.1.2016.04.19.13.29.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Apr 2016 13:29:56 -0700 (PDT) References: <86fuuywldn.fsf@WorkBox.Home> User-agent: mu4e 0.9.16; emacs 24.5.1 From: Brandon J. Wandersee To: Warren Block Cc: freebsd-questions@freebsd.org Subject: Re: Simple devd.conf rule has no effect In-reply-to: Date: Tue, 19 Apr 2016 15:29:57 -0500 Message-ID: <86bn552vga.fsf@WorkBox.Home> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 09:11:30 -0000 Warren Block writes: > On Wed, 6 Apr 2016, Brandon J. Wandersee wrote: > >> >> Hi, folks. I'm trying to get my laptop screen to lock when the lid >> closes, using x11/slock. I've created the file /etc/devd/lidlock.conf >> with the following rule: >> >> | notify 0 { >> | match "system" "ACPI"; >> | match "subsystem" "Lid"; >> | match "notify" "0x00"; >> | action "/usr/local/bin/slock"; >> | }; >> >> This is really just a slight variation on the example from the >> devd.conf(5) man page. Now when I close the lid, the screen fails to >> lock, yet /var/log/messages displays the message "devd: Executing >> 'slock'". Any advice on what to look into to figure out why the program >> is not actually executed? Thanks in advace. > > devd(8) stuff runs as root, I think. So it probably does not have > $DISPLAY set. Maybe use su to switch to the normal X user and execute > the command: > > su -l xusername -c 'setenv DISPLAY :0.0 && /usr/local/bin/slock' Thanks for the response, Warren; sorry for the lateness of mine. Your solution works when run from a shell, but devd still doesn't properly execute it. I also tried changing the quotes around, adapting it for my user shell (changing 'setenv' to 'export DISPLAY='), and putting it in a shell script and executing the script from the devd config file. No luck. Guess I'll just keep messing with it when the mood strikes, see if anything clicks. -- :: Brandon J. Wandersee :: brandon.wandersee@gmail.com :: -------------------------------------------------- :: 'The best design is as little design as possible.' :: --- Dieter Rams ---------------------------------- From owner-freebsd-questions@freebsd.org Wed Apr 20 09:23:20 2016 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 0446DB15ADD for ; Wed, 20 Apr 2016 09:23:20 +0000 (UTC) (envelope-from tijl@coosemans.org) Received: from mailrelay106.isp.belgacom.be (mailrelay106.isp.belgacom.be [195.238.20.133]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (Client CN "relay.skynet.be", Issuer "GlobalSign Organization Validation CA - SHA256 - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6C3541206 for ; Wed, 20 Apr 2016 09:23:19 +0000 (UTC) (envelope-from tijl@coosemans.org) X-Belgacom-Dynamic: yes X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2DnAgDkSBdX/0issFtVCYM4U32pC4UDi10BDYFxhggEAgKBOjkUAQEBAQEBAWUnhEIBAQQ6HCMQCw4KCSUPKh4GE4gUAxa9fAEBAQEBAQQBAQEBARuCIIhMgkGBVYV/AQSXXjGMH4Frb44rh0+HXh4BAUKDajowiEcBAQE Received: from 72.172-176-91.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([91.176.172.72]) by relay.skynet.be with ESMTP; 20 Apr 2016 11:22:06 +0200 Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org [127.0.0.1]) by kalimero.tijl.coosemans.org (8.15.2/8.15.2) with ESMTP id u3K9M46f001833; Wed, 20 Apr 2016 11:22:05 +0200 (CEST) (envelope-from tijl@coosemans.org) Date: Wed, 20 Apr 2016 11:22:03 +0200 From: Tijl Coosemans To: Manish Jain Cc: freebsd-questions@freebsd.org, guru@unixarea.de Subject: Re: Does HP DeskJet 1112 work with lpd on FreeBSD 10.2 amd64 ? Message-ID: <20160420112203.3244f4ea@kalimero.tijl.coosemans.org> In-Reply-To: References: 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 09:23:20 -0000 On Tue, 19 Apr 2016 18:42:01 +0530 Manish Jain wrote: > << > CUPS works nice for many years on my FreeBSD systems, actually CURRENT. > Why you can't get it to do anything on your system? matthias > >> > > Thanks for responding. So my question becomes "Has anyne got HP DeskJet > 1112 to work with CUPS on a FreeBSD 10.2 amd64 box ?" You need to install print/hplip. Then you can either use the graphical setup tool HP Device Manager, or the CUPS web interface at http://localhost:631/. If you use the CUPS interface you need to select the printer model at some point. Your printer will be listed as "HP Deskjet 1110 Series, hpcups 3.16.2". From owner-freebsd-questions@freebsd.org Wed Apr 20 09:23:49 2016 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 17126B15B4D for ; Wed, 20 Apr 2016 09:23:49 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 960EE12CA for ; Wed, 20 Apr 2016 09:23:48 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from ox-dell39.ox.adestra.com (unknown [85.199.232.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 257641152B for ; Wed, 20 Apr 2016 09:23:44 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/257641152B; dkim=none; dkim-atps=neutral Subject: Re: Raid 1+0 To: freebsd-questions@freebsd.org References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> <20160419153824.7b679129f82a3cd0b18b9740@sohara.org> <40267.128.135.52.6.1461098148.squirrel@cosmo.uchicago.edu> <44a8kpcm14.fsf@be-well.ilk.org> From: Matthew Seaman Message-ID: <5027ef1b-fd33-5e07-3a8d-fe0ce9732b29@freebsd.org> Date: Wed, 20 Apr 2016 10:23:31 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <44a8kpcm14.fsf@be-well.ilk.org> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="8JPBdPjffXrHQaBHhtwNnxDBAv7ScOJOb" X-Virus-Scanned: clamav-milter 0.99.1 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-0.4 required=5.0 tests=BAYES_00,RDNS_NONE, SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 09:23:49 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --8JPBdPjffXrHQaBHhtwNnxDBAv7ScOJOb Content-Type: multipart/mixed; boundary="AlJjkGSRPRdAPP0imDvgQgnbX8EdmxIEv" From: Matthew Seaman To: freebsd-questions@freebsd.org Message-ID: <5027ef1b-fd33-5e07-3a8d-fe0ce9732b29@freebsd.org> Subject: Re: Raid 1+0 References: <571533F4.8040406@bananmonarki.se> <57153E6B.6090200@gmail.com> <20160418210257.GB86917@neutralgood.org> <64031.128.135.52.6.1461017122.squirrel@cosmo.uchicago.edu> <20160419153824.7b679129f82a3cd0b18b9740@sohara.org> <40267.128.135.52.6.1461098148.squirrel@cosmo.uchicago.edu> <44a8kpcm14.fsf@be-well.ilk.org> In-Reply-To: <44a8kpcm14.fsf@be-well.ilk.org> --AlJjkGSRPRdAPP0imDvgQgnbX8EdmxIEv Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 04/19/16 22:43, Lowell Gilbert wrote: > Correlation is not causation. >=20 > It's not a big stretch to imagine that two nearly identical mechanical > devices, operated in nearly identical conditions, might wear out in a > nearly identical way at about the same time. There is no need for one > drive to affect the other. Interestingly this argument is quite a bit stronger when applied to SSD's rather than spinning disk drives. SSDs we know have a limited number of refresh cycles for any one memory cell. As members of a RAID array, they're going to see very similar patterns of activity over their lifetimes, so they're actually quite likely to wear out at a similar time= =2E > A fair number of people believe that this in fact occurs. I've looked > for evidence on the subject, and I haven't found anything (beyond > anecdotes) for or against the possibility. Mechanical drives are a lot more affected by external differences like vibration or temperature changes, which will act to increase the variability in their lifetimes. SSDs are intrinsically /more/ reliable during their working life, but their lifetime tends to come to a much more sharply defined end. Cheers, Matthew (who has been spending far too much time going to the datacentre to replace drives recently.) --AlJjkGSRPRdAPP0imDvgQgnbX8EdmxIEv-- --8JPBdPjffXrHQaBHhtwNnxDBAv7ScOJOb Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJXF0qaAAoJEABRPxDgqeTnKA4P/R1mtBargXP3BrpJyKtI3KLS pVS/26BAuLfPxVq/U/EK8wp5dEsUziCIh9lrZgwLS8OxTYaB3kfZO11kM49XMu/Y B8wQmnnVjeG18HlYaHRPcvJ1ELDe8TD334t/RzXTK4clnYqMmJl5Df6UZbOXUCIL dAbzW0nNhcsClqpZV4xBvGn1ZAGfK9aFTmofqN+4eZUqd+A9YROjBqzzpFzRCnDR BDJ9tuVctVlnt/iMiG+bvlrWkw7m2X8HEajGLjnLYz659xUp2S+WsK+KvKaXOcql oqZWTKYV1CmeAbBxYov9vxesewfMhFmfK9Mdg/318+IDxzY4V0mPdNM0qROBQJG4 O8bWfyrV+bm0y3aC4dkLj+GzC2RtRXAIH4p2Q6bzKnrU8HHlv4dSKRSzpPH1/948 /IbkHby3wnZZmwhoJYRGGVo0EJbNLDaCkjzUBKgw1zO6yxAqvyIeIfdtbsjjGDnJ 6zABr0wvQkg6s2GVR1kGYmaeJkoVJndH6Ez0mg26NRQOlwTElJgTWPMvTtaLns0q pOIAj57fLTXiOccK5codnzab3j4HLf9oYkNi8Jm2TjcpFsO5tpbFuBDJ2ZAomRez LIEJffXPwAOAdyMhJ0ljW2HHMrtl1Ib7dcxjYBFxNWvrxz+RFXYZ18p+CAj01LRU tbtT+KZIGIV70g7TN6ev =hjLE -----END PGP SIGNATURE----- --8JPBdPjffXrHQaBHhtwNnxDBAv7ScOJOb-- From owner-freebsd-questions@freebsd.org Wed Apr 20 09:25:21 2016 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 6A616B15C45 for ; Wed, 20 Apr 2016 09:25:21 +0000 (UTC) (envelope-from tijl@freebsd.org) Received: from mailrelay106.isp.belgacom.be (mailrelay106.isp.belgacom.be [195.238.20.133]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (Client CN "relay.skynet.be", Issuer "GlobalSign Organization Validation CA - SHA256 - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BEAA313C5 for ; Wed, 20 Apr 2016 09:25:20 +0000 (UTC) (envelope-from tijl@freebsd.org) X-Belgacom-Dynamic: yes X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2BzBwA1ShdX/0issFtegziBULtqhgQEBAICgTo9EAEBAQEBAQFlJ4RBAQEBAwEjMyMFCwkCGAICBSECAg8qHgYTiCEMjyKdF5FFAQEBAQYBAQEBARt8gSSITIQ9gwKCVgEEmA+OCm9rjUCPLTcrg2o6MIhHAQEB Received: from 72.172-176-91.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([91.176.172.72]) by relay.skynet.be with ESMTP; 20 Apr 2016 11:25:15 +0200 Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org [127.0.0.1]) by kalimero.tijl.coosemans.org (8.15.2/8.15.2) with ESMTP id u3K9PDsQ001851; Wed, 20 Apr 2016 11:25:14 +0200 (CEST) (envelope-from tijl@FreeBSD.org) Date: Wed, 20 Apr 2016 11:25:13 +0200 From: Tijl Coosemans To: =?UTF-8?B?U8Opcmdpbw==?= de Almeida Lenzi Cc: Matthias Apitz , freebsd-questions@freebsd.org Subject: Re: Does HP DeskJet 1112 work with lpd on FreeBSD 10.2 amd64 ? Message-ID: <20160420112513.4afa595a@kalimero.tijl.coosemans.org> In-Reply-To: <1461126503.80865.3.camel@k1.com.br> References: <20160419141207.GA2799@c720-r292778-amd64.oa.oclc.org> <1461126503.80865.3.camel@k1.com.br> 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 09:25:21 -0000 On Wed, 20 Apr 2016 01:28:23 -0300 S=C3=A9rgio de Almeida Lenzi wrote: > I have it working but only on previous version of cups What is the problem with newer versions? > here I have... > hplip-3.14.10_1=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0Drivers and utilities for HP Printers > and All-in-One devices > hplip-plugin-3.14.10=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0Binary plugin for some HP Printers and > All-in-One devices The Deskjet 1112 shouldn't need hplip-plugin. From owner-freebsd-questions@freebsd.org Wed Apr 20 09:42:13 2016 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 78624B147C3 for ; Wed, 20 Apr 2016 09:42:13 +0000 (UTC) (envelope-from garga.bsd@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5436C1ED4 for ; Wed, 20 Apr 2016 09:42:13 +0000 (UTC) (envelope-from garga.bsd@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 5390CB147C0; Wed, 20 Apr 2016 09:42:13 +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 53014B147BF; Wed, 20 Apr 2016 09:42:13 +0000 (UTC) (envelope-from garga.bsd@gmail.com) Received: from mail-qg0-x241.google.com (mail-qg0-x241.google.com [IPv6:2607:f8b0:400d:c04::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 0C06B1E3D; Wed, 20 Apr 2016 09:42:13 +0000 (UTC) (envelope-from garga.bsd@gmail.com) Received: by mail-qg0-x241.google.com with SMTP id 7so4255149qgj.0; Wed, 20 Apr 2016 02:42:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=EjqACbNQNUDocwC+rD6nqgCJDQUmKBEYafgg9qtZ3fc=; b=0Ud8ESMQmsl8XVIyaUc1DHTmIFjrmInLO/ElHX2UNTnME+qwmNVFWwWv/6y0DT2587 VlLzBj6cZ1+Yips6zAOjtLQtk7OT5nv2QmxIQf5Tsz9KX8xWxOWFXrPhw2HvYT1Qm79m uF6wgzRTUqhbg4bHf+EFRP6XQA5x3fUy8p61uS+Eg9sDyYqLWFZlmKUdtBrADXVZRmuu FPSyXi1zxmSN00dVxdtiRda7cXihgqr3+gtJR2w/E5/x1iOtf9LnO2/L/V/dZQkSFSXw ucna8FPLRNMkEt3WjRxjoaJ8jqJWvsEw79VHcuKkYyWoFdvPbEHgUvHcF6fvvxqe6tbu hnkg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:mime-version:subject:from:in-reply-to :date:cc:content-transfer-encoding:message-id:references:to; bh=EjqACbNQNUDocwC+rD6nqgCJDQUmKBEYafgg9qtZ3fc=; b=SveQjxgrqQBjKfcxd8u0UyAfdkSNY7ox7O8fY1SNn0Q38O4nUk7SjKeKRu1ZUQbKFH 5MnsJS7/G500fv7nP4UUQjkHlvIhyuGgQI6xFIrdS3t/kTSTiMtEIgK/K99KBbde5TDA YMR7piUOwWR8dPRwKj1Jup09DUL5UQCfr+Aq2LH9UewSjsrcbfg/WHhUdWcgEc2pyyOV 8s1GYCOHjo69R5fV7rxPyCYmPd8IzDxmDWNkWnFTmAU0hnEjsxNIRxhpR/JFzAzZ4O91 a1lPNrLI1evJ5vwHIWThtS2N4cP8i8ii3PvgwILtwDIaRM2nCY8qrTfF4QUqrnB8tsZW rTYg== X-Gm-Message-State: AOPr4FWaJStVOmAvmoqxW/3C8qoW1A3UeC4WNG72WZvCsks2r4amAQvc0CizFSnFfe/REg== X-Received: by 10.140.181.137 with SMTP id c131mr9967944qha.94.1461145332272; Wed, 20 Apr 2016 02:42:12 -0700 (PDT) Received: from mbp.home (179-125-130-37.desktop.com.br. [179.125.130.37]) by smtp.gmail.com with ESMTPSA id f83sm30978104qkb.25.2016.04.20.02.42.09 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 20 Apr 2016 02:42:11 -0700 (PDT) Sender: Renato Botelho Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: 11.0-RELEASE pkg base & base.txz file From: Renato Botelho In-Reply-To: Date: Wed, 20 Apr 2016 06:42:06 -0300 Cc: Slawa Olhovchenkov , questions@freebsd.org, freebsd-pkgbase@freebsd.org, Ernie Luzar , freebsd-current Content-Transfer-Encoding: 7bit Message-Id: <0E16B4D4-DB5D-4ABD-9D00-6AF819452724@FreeBSD.org> References: <5714E89A.8000807@gmail.com> <20160418141454.GX4841@zxy.spb.ru> <20160418141601.GA26116@ivaldir.etoilebsd.net> <20160418142709.GY4841@zxy.spb.ru> <20160418150325.GZ4841@zxy.spb.ru> <5715389C.9090502@gmail.com> <20160418200354.GB4841@zxy.spb.ru> To: krad X-Mailer: Apple Mail (2.3124) X-Mailman-Approved-At: Wed, 20 Apr 2016 11:09:37 +0000 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 09:42:13 -0000 > On Apr 20, 2016, at 03:54, krad wrote: > > will it still be buildable though from source? Yes -- Renato Botelho From owner-freebsd-questions@freebsd.org Wed Apr 20 14:48:31 2016 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 E5388B154CC for ; Wed, 20 Apr 2016 14:48:31 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A88F9168B for ; Wed, 20 Apr 2016 14:48:31 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [62.216.202.58] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1astQS-0002j7-PH for freebsd-questions@freebsd.org; Wed, 20 Apr 2016 16:48:21 +0200 Received: from localhost.my.domain (c720-r292778-amd64 [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id u3KEmJ30002509 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 20 Apr 2016 16:48:19 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id u3KEmJhe002508 for freebsd-questions@freebsd.org; Wed, 20 Apr 2016 16:48:19 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Wed, 20 Apr 2016 16:48:19 +0200 From: Matthias Apitz To: freebsd-questions@freebsd.org Subject: Re: tool for mapping away bad blocks on an external disk Message-ID: <20160420144819.GA2481@c720-r292778-amd64> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , freebsd-questions@freebsd.org References: <20160417072641.GA2358@c720-r292778-amd64> <20160417093957.0b1acb4c37d7c15a4b06af88@sohara.org> <20160418065534.GA2198@c720-r292778-amd64> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20160418065534.GA2198@c720-r292778-amd64> X-Operating-System: FreeBSD 11.0-CURRENT r292778 (amd64) User-Agent: Mutt/1.5.24 (2015-08-30) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 62.216.202.58 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 14:48:32 -0000 El día Monday, April 18, 2016 a las 08:55:34AM +0200, Matthias Apitz escribió: > > Thanks for all the hints; I started last night with overwriting the full > disk with: > > # dd conv=noerror if=/dev/zero of=/dev/da0 bs=1m > > ... The dd ended as. I issued from time to time a kill -INFO to the dd to see its progress: # tail nohup.out ... 885016+0 records in 885016+0 records out 928006537216 bytes transferred in 35244.495687 secs (26330538 bytes/sec) 980612+0 records in 980612+0 records out 1028246208512 bytes transferred in 39028.251450 secs (26346202 bytes/sec) dd: /dev/da0: Input/output error 1154078+0 records in 1154077+0 records out 1210137444352 bytes transferred in 45969.382123 secs (26324858 bytes/sec) Does this mean I could use the first 1154077 blocks of 1m as partition, i.e. shrink it to this size and just ignore the rest? matthias -- Matthias Apitz, ✉ guru@unixarea.de, ⌂ http://www.unixarea.de/ ☎ +49-176-38902045 From owner-freebsd-questions@freebsd.org Wed Apr 20 15:29:25 2016 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 11DC2B16A10 for ; Wed, 20 Apr 2016 15:29:25 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D37BE1A01 for ; Wed, 20 Apr 2016 15:29:24 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id u3KFTMLE008754 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 20 Apr 2016 09:29:22 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id u3KFTM2c008747; Wed, 20 Apr 2016 09:29:22 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Wed, 20 Apr 2016 09:29:22 -0600 (MDT) From: Warren Block To: Matthias Apitz cc: freebsd-questions@freebsd.org Subject: Re: tool for mapping away bad blocks on an external disk In-Reply-To: <20160420144819.GA2481@c720-r292778-amd64> Message-ID: References: <20160417072641.GA2358@c720-r292778-amd64> <20160417093957.0b1acb4c37d7c15a4b06af88@sohara.org> <20160418065534.GA2198@c720-r292778-amd64> <20160420144819.GA2481@c720-r292778-amd64> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Wed, 20 Apr 2016 09:29:23 -0600 (MDT) Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 15:29:25 -0000 On Wed, 20 Apr 2016, Matthias Apitz wrote: > El día Monday, April 18, 2016 a las 08:55:34AM +0200, Matthias Apitz escribió: > >> >> Thanks for all the hints; I started last night with overwriting the full >> disk with: >> >> # dd conv=noerror if=/dev/zero of=/dev/da0 bs=1m >> >> ... > > The dd ended as. I issued from time to time a kill -INFO to the dd to > see its progress: > > # tail nohup.out > ... > 885016+0 records in > 885016+0 records out > 928006537216 bytes transferred in 35244.495687 secs (26330538 bytes/sec) > 980612+0 records in > 980612+0 records out > 1028246208512 bytes transferred in 39028.251450 secs (26346202 bytes/sec) > dd: /dev/da0: Input/output error > 1154078+0 records in > 1154077+0 records out > 1210137444352 bytes transferred in 45969.382123 secs (26324858 bytes/sec) > > Does this mean I could use the first 1154077 blocks of 1m as partition, > i.e. shrink it to this size and just ignore the rest? Maybe. Best to check the SMART data, then run a long test and see if the reallocated blocks have grown. Don't count on the SMART data saying the drive is good to be trustworthy. The manufacturers usually have it set so the drive is long past safe use by the time the SMART data actually admits it. From owner-freebsd-questions@freebsd.org Wed Apr 20 15:30:26 2016 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 EE915B16AE0 for ; Wed, 20 Apr 2016 15:30:26 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B4FEE1B2A for ; Wed, 20 Apr 2016 15:30:26 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1asu51-0003Mj-1h for freebsd-questions@freebsd.org; Wed, 20 Apr 2016 17:30:15 +0200 Received: from pool-72-66-1-32.washdc.fios.verizon.net ([72.66.1.32]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 20 Apr 2016 17:30:15 +0200 Received: from nightrecon by pool-72-66-1-32.washdc.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 20 Apr 2016 17:30:15 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Michael Powell Subject: Re: tool for mapping away bad blocks on an external disk Date: Wed, 20 Apr 2016 11:31:13 -0400 Lines: 53 Message-ID: References: <20160417072641.GA2358@c720-r292778-amd64> <20160417093957.0b1acb4c37d7c15a4b06af88@sohara.org> <20160418065534.GA2198@c720-r292778-amd64> <20160420144819.GA2481@c720-r292778-amd64> Reply-To: nightrecon@hotmail.com Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8Bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pool-72-66-1-32.washdc.fios.verizon.net X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 15:30:27 -0000 Matthias Apitz wrote: > El día Monday, April 18, 2016 a las 08:55:34AM +0200, Matthias Apitz > escribió: > >> >> Thanks for all the hints; I started last night with overwriting the full >> disk with: >> >> # dd conv=noerror if=/dev/zero of=/dev/da0 bs=1m >> >> ... > > The dd ended as. I issued from time to time a kill -INFO to the dd to > see its progress: > > # tail nohup.out > ... > 885016+0 records in > 885016+0 records out > 928006537216 bytes transferred in 35244.495687 secs (26330538 bytes/sec) > 980612+0 records in > 980612+0 records out > 1028246208512 bytes transferred in 39028.251450 secs (26346202 bytes/sec) > dd: /dev/da0: Input/output error > 1154078+0 records in > 1154077+0 records out > 1210137444352 bytes transferred in 45969.382123 secs (26324858 bytes/sec) > > Does this mean I could use the first 1154077 blocks of 1m as partition, > i.e. shrink it to this size and just ignore the rest? > I have done that on occasion; I actually have the extra storage drive in my webdev box partitioned that way now. It had a bad spot which the mfr's utility corrected, then a few months later a few more, then a large number of them splatted out but they were all in about the same 400MB space in the middle of the drive. So I have a small partition in front (with a few hundred MB cushion on either side) and a larger partition behind it, with the bad space in between unpartitioned. Not a recommended way to go about things, but I get to use the drive until I buy a replacement. I've procrastinated on that as it has now been stable for almost a year like that. Generally when you start seeing dead sectors the remap zone is full and the first few sectors going bad begin to snowball into larger numbers fairly quickly. Failing magnetic media is nothing to waste time over as it is only going to cause data loss. But you can do this - I just don't really recommend it as it generally is a waste of time because once the media begins to fail it will continue to do so. ymmv -Mike From owner-freebsd-questions@freebsd.org Wed Apr 20 17:44:25 2016 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 0D039B16714 for ; Wed, 20 Apr 2016 17:44:25 +0000 (UTC) (envelope-from jennyj@switchdigitalpros.com) Received: from smtp124.ord1c.emailsrvr.com (smtp124.ord1c.emailsrvr.com [108.166.43.124]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E37851A18 for ; Wed, 20 Apr 2016 17:44:24 +0000 (UTC) (envelope-from jennyj@switchdigitalpros.com) Received: from smtp8.relay.ord1c.emailsrvr.com (localhost.localdomain [127.0.0.1]) by smtp8.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id EE39080443 for ; Wed, 20 Apr 2016 13:44:22 -0400 (EDT) X-Auth-ID: jennyj@switchdigitalpros.com Received: by smtp8.relay.ord1c.emailsrvr.com (Authenticated sender: jennyj-AT-switchdigitalpros.com) with ESMTPSA id 686808022D for ; Wed, 20 Apr 2016 13:44:22 -0400 (EDT) X-Sender-Id: jennyj@switchdigitalpros.com Received: from [127.0.0.1] ([UNAVAILABLE]. [103.6.157.159]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA) by 0.0.0.0:465 (trex/5.5.4); Wed, 20 Apr 2016 13:44:22 -0400 To: freebsd-questions@freebsd.org Subject: Soccer Enthusiasts List From: Jenny Jordan Message-ID: <5717BE4E.7040605@switchdigitalpros.com> Date: Wed, 20 Apr 2016 13:37:18 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.3; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Antivirus: avast! (VPS 160420-0, 04/20/2016), Outbound message X-Antivirus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 17:44:25 -0000 Hi, Would you be interested in acquiring an Email list of "Soccer Enthusiasts" from USA? Each record in the list contains First Name, Last Name, Address, City, State, Zip, Source, List Type and Opt-in email address. We also have data for Golfers, Football Enthusiasts, Baseball Enthusiasts, Basketball Enthusiasts, Tennis Enthusiasts, spa and resorts Visitors, Skiers, Poker Players, Casino Players, Accessories and Apparel Buyers, On-line Gamers, On-line Shoppers, Women’s List, All Mobile Users Students and many more... Please let me know your thoughts towards procuring the "Soccer Enthusiasts List" . Look forward to your prompt response. Thanks & Regards Jenny Jordan Research Analyst --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From owner-freebsd-questions@freebsd.org Wed Apr 20 21:47:14 2016 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 B1794B1615C for ; Wed, 20 Apr 2016 21:47:14 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 93AB41DC3 for ; Wed, 20 Apr 2016 21:47:14 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 92F5AB1615B; Wed, 20 Apr 2016 21:47:14 +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 92954B1615A for ; Wed, 20 Apr 2016 21:47:14 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::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 5ED4A1DC0 for ; Wed, 20 Apr 2016 21:47:14 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-ig0-x236.google.com with SMTP id gy3so26482716igb.1 for ; Wed, 20 Apr 2016 14:47:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-transfer-encoding; bh=FgFIiM9xaZqWtoc04kDj3FD7QiOCmOTpx/xt+oYK0LM=; b=Kdcg4q3WIjhmNNg8YUW6HHExw2BOrhd7BjJVSM6Uts3D/J4IHc24xKcV0FRRk4DsXG +3lA/sVdaEopMW76b0TyWXWXn/gN7HYSa8w3a1pb2vIvk4AYG6M5VoGys6Oox5cf96Fv ItPYZ9D3/lvMvUFqqjpk2tEHawmeXfNyiD/GS8ZaOFAwBMJjc4+pN3QwxWhgc2ZJxGjT EyoGn3/C+8Yg+jHc0Fk7z71i0+FUBYiE4Dkcst9SvodigIOFpAJerYMm6mgGKAzZj5zb TF/STekNq9RvwtlZR2MFtsQNO+nZkKWUb/+QtTP+mVfnLJLxmNXWx+cRpLTHzOIGS8mc XtMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:content-transfer-encoding; bh=FgFIiM9xaZqWtoc04kDj3FD7QiOCmOTpx/xt+oYK0LM=; b=lCB4NDe4ZpPPST18FRCqJAwrlazBe/4YOswLh3bqHXQoS2AL9vQ4Xz/R4YFsKOIb/0 Dhy7yqXug0brcfTLOteV7bAqRDg3pHDdcLwn+2vCmijueCqCpPAmw7g1T55S/jPMmafp YcRBIfyyWWGNGE3GWdZN3+SKm19NMl9mkGsniOnIbNyjkg1zNQDhZcAmNy8YQeXRCb9K XQJ9JNqeoXazKWqRGWCP/hm4RkhVTYgKnPh9Q0FgzcEB3FDw4M73fMesZnoSWBxf3/iN Q5KgvsOC1t7S5GKv4SU4DpkWImQoBw/BERMHQrpzd8oyNJi7eWPxjnyvrOYDkngGYrnD Ozfg== X-Gm-Message-State: AOPr4FWc4/buYgrnrbjqJQAkhz0952t8bIyf4K2I1Dc9ImwbrW2+OOLu5uHyQ6CSNv6A0g== X-Received: by 10.50.30.101 with SMTP id r5mr6359540igh.2.1461188833777; Wed, 20 Apr 2016 14:47:13 -0700 (PDT) Received: from [10.0.10.3] (cpe-184-56-210-236.neo.res.rr.com. [184.56.210.236]) by smtp.googlemail.com with ESMTPSA id i74sm3720535ioe.37.2016.04.20.14.47.12 for (version=TLSv1/SSLv3 cipher=OTHER); Wed, 20 Apr 2016 14:47:13 -0700 (PDT) Message-ID: <5717F8E3.6050903@gmail.com> Date: Wed, 20 Apr 2016 17:47:15 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: questions@freebsd.org Subject: ssh host_key error Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 21:47:14 -0000 Hello list Just completed installing 10.3 from scratch to a empty disk. The first time I tried to remotely ssh into host I got these error messages. sshd[1347]: error: Could not load host key: /etc/ssh/ssh_host_rsa_key sshd[1347]: error: Could not load host key: /etc/ssh/ssh_host_dsa_key sshd[1347]: error: Could not load host key: /etc/ssh/ssh_host_ecdsa_key sshd[1347]: error: Could not load host key: /etc/ssh/ssh_host_ed25519_key If I remember correctly these keys were populated on the first boot of a newly installed system. Does ssh have some job to populate those keys that I can manually run? Thanks list From owner-freebsd-questions@freebsd.org Wed Apr 20 23:45:59 2016 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 5BC92B16A69 for ; Wed, 20 Apr 2016 23:45:59 +0000 (UTC) (envelope-from kudzu@tenebras.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 3D9791384 for ; Wed, 20 Apr 2016 23:45:59 +0000 (UTC) (envelope-from kudzu@tenebras.com) Received: by mailman.ysv.freebsd.org (Postfix) id 39349B16A67; Wed, 20 Apr 2016 23:45:59 +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 38CC0B16A64 for ; Wed, 20 Apr 2016 23:45:59 +0000 (UTC) (envelope-from kudzu@tenebras.com) Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::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 119421383 for ; Wed, 20 Apr 2016 23:45:58 +0000 (UTC) (envelope-from kudzu@tenebras.com) Received: by mail-yw0-x22c.google.com with SMTP id j74so63316664ywg.1 for ; Wed, 20 Apr 2016 16:45:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tenebras-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=9SuzayxPKbYyJdkod3pMEQoW2qFkzeE3VezEWYOfj4Q=; b=x3fi9JUEmUJVnJfzfCKwSFZkiALG25yfgWsfFROir4xB7ccnSP8W2aQ+POZnbzfuF7 Knxq7HXmA3PbY1OwarWpFSG6jR4oEpu9t21ndXqBLKbLNR9mMlgfPUORxIsLJr4g4vVd e8N8OuZD+q+37+f9C7GCbdFr8rCII8DwB4SKffS562P7ja5EYbNCK3pPlL1Daloj/wKc 6bQ5OCrzoONXNLyyTvrljhpwhnt59WNpmvdyWsUm/pd38E3LWXHtSPfWc8u1f28DOmO/ GfftxjCXpB4e1A2Odp5cXo89ppi051A3NVHee9y61tzGcd0lKdoHdx6wa+DYYLggraGx iieg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=9SuzayxPKbYyJdkod3pMEQoW2qFkzeE3VezEWYOfj4Q=; b=NvZsrQwzsdami15B7Fj4D7DaOOqsAimSNRYXg7eajALTiB+dcbEsKSUs+XUeRewOph +gjtJAY/NbMdky5O+KgLKhYlILlF8iTH7YF8ObVyyZ7ONijYLLBirA50heGZfcDp+0++ O4TDk0iXFijzMn9flaU1bnmzDwdOOi6v6hZSjGcgE7o9pPGbmZCj+nM6RO/pkCQP7Z9K KvfPFsr9yESp3UKlvBK0LLuVPNOVsXEhMpiSZie88rgLgzmqOCnZ1JZNxLyb4tK7FdW0 u8NXBA1E5vYFsNddnhdt34w/6YVqqpAqyZPCsnRhlrUW6nvvZRd7H3PCjVbt8+DPuU+R qb+g== X-Gm-Message-State: AOPr4FX6/Eb8TPsToH+hyema5rn0SmFEWcGfPf7zE4ojlMNcDvrymYPBcf67pzJEswcn1oiI4UwvJ6+vfmQDVF7f MIME-Version: 1.0 X-Received: by 10.13.213.83 with SMTP id x80mr3229607ywd.253.1461195958180; Wed, 20 Apr 2016 16:45:58 -0700 (PDT) Received: by 10.37.97.199 with HTTP; Wed, 20 Apr 2016 16:45:58 -0700 (PDT) In-Reply-To: <5717F8E3.6050903@gmail.com> References: <5717F8E3.6050903@gmail.com> Date: Wed, 20 Apr 2016 16:45:58 -0700 Message-ID: Subject: Re: ssh host_key error From: Michael Sierchio To: Ernie Luzar Cc: "questions@FreeBSD.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 23:45:59 -0000 /etc/rc.d/sshd will create these if they don't exist. On Wed, Apr 20, 2016 at 2:47 PM, Ernie Luzar wrote: > Hello list > > Just completed installing 10.3 from scratch to a empty disk. > The first time I tried to remotely ssh into host I got these error > messages. > > sshd[1347]: error: Could not load host key: /etc/ssh/ssh_host_rsa_key > sshd[1347]: error: Could not load host key: /etc/ssh/ssh_host_dsa_key > sshd[1347]: error: Could not load host key: /etc/ssh/ssh_host_ecdsa_key > sshd[1347]: error: Could not load host key: /etc/ssh/ssh_host_ed25519_key > > > If I remember correctly these keys were populated on the first boot of a > newly installed system. Does ssh have some job to populate those keys that > I can manually run? > > Thanks list > > _______________________________________________ > 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 Apr 21 00:04:50 2016 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 A8D08B1529C for ; Thu, 21 Apr 2016 00:04:50 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 8934F1E71 for ; Thu, 21 Apr 2016 00:04:50 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 84D76B1529A; Thu, 21 Apr 2016 00:04:50 +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 84742B15299 for ; Thu, 21 Apr 2016 00:04:50 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-io0-x244.google.com (mail-io0-x244.google.com [IPv6:2607:f8b0:4001:c06::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6039E1E70 for ; Thu, 21 Apr 2016 00:04:50 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-io0-x244.google.com with SMTP id g185so8897470ioa.0 for ; Wed, 20 Apr 2016 17:04:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-transfer-encoding; bh=axjsvIklJrwzC/grR2LDdSwSZkgE1rjky3KoTL+/rwU=; b=t4NqefxIHPcfxQSB82iGKMwzm98IvgE70vs8zn9qLvZuyINmxaszlpovTlkrRvT1ak vfAP4zvrFUnfzo+7K8WFeQRW3rgZuOsO2raVnSjEL+NQRLs4+1J9OECn5UQhMBfwHnxI i5lavfO7XAuOKlnInQ2vIW7MeCvpFKY41nKVvb3FaopvYag9/9Q0GFlYCcpelgvtgxqQ H+EAu1ld3hFdUx6pJl+ml9oFDFB1t6Kyv5IzJXcszZwknIFPOd7XEjj/kUpI75wbSTgj +h/3xsZJyjwAW2gLH5N4sg8HRoS+TWzNmVDPOJvu5qEJGueGagGG0/l0DuPsVEgkn+I0 kCiQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-transfer-encoding; bh=axjsvIklJrwzC/grR2LDdSwSZkgE1rjky3KoTL+/rwU=; b=SJs0IAVyWyk75TgriOhmKh2453VVixxNoJVeCbm5el2xwtHp4gDCn6IPTvrUpqh68A cXUepmm/sQKuV8+F8LjBIAQ6/pOi9XZqgjMDPL2SVY1JhYBQfYTs7hcUN/WtXaPwM6ks soFu8vKM4XxWn0ZOdk1aEKse3EcvPS2vo+jMPErw77yk6UKWU7ZtYc+M6bIQZ6Ddfgpd 5Ah1v1oqqsnuiGbjrji8bZSinRxwbGWKcM9u+ijxaCupx+m1nZkEnR2Tf/aLI9vxSlyB fa4/OeHoh6GLeYFOlLb8uHMWsjPxWu1XlZpp8P9rUdvd7Xggm1+ALbMe649FkyXaLA4j LjfA== X-Gm-Message-State: AOPr4FVel+XOvbCqqrR7tb394MB9zN1WbwQJBv33Jn4kFqXPIc9hnnov1yiG3UF4q7gIFQ== X-Received: by 10.107.16.104 with SMTP id y101mr12209897ioi.148.1461197089617; Wed, 20 Apr 2016 17:04:49 -0700 (PDT) Received: from [10.0.10.3] (cpe-184-56-210-236.neo.res.rr.com. [184.56.210.236]) by smtp.googlemail.com with ESMTPSA id m143sm243525ioe.43.2016.04.20.17.04.48 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 20 Apr 2016 17:04:49 -0700 (PDT) Message-ID: <57181929.40809@gmail.com> Date: Wed, 20 Apr 2016 20:04:57 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: david.robison@fisglobal.com, questions@freebsd.org Subject: Re: ssh host_key error References: <5717F8E3.6050903@gmail.com> <57180A4A.3000003@fisglobal.com> In-Reply-To: <57180A4A.3000003@fisglobal.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2016 00:04:50 -0000 Robison, Dave wrote: > On 04/20/16 02:47 PM, Ernie Luzar wrote: >> Hello list >> >> Just completed installing 10.3 from scratch to a empty disk. >> The first time I tried to remotely ssh into host I got these error messages. >> >> sshd[1347]: error: Could not load host key: /etc/ssh/ssh_host_rsa_key >> sshd[1347]: error: Could not load host key: /etc/ssh/ssh_host_dsa_key >> sshd[1347]: error: Could not load host key: /etc/ssh/ssh_host_ecdsa_key >> sshd[1347]: error: Could not load host key: /etc/ssh/ssh_host_ed25519_key >> >> >> If I remember correctly these keys were populated on the first boot of a newly installed system. Does ssh have some job to populate those keys that I can manually run? >> >> Thanks list >> >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.freebsd.org_mailman_listinfo_freebsd-2Dquestions&d=BQICAg&c=3BfiSO86x5iKjpl2b39jud9R1NrKYqPq2js90dwBswk&r=xejns4hCLY4pkxk_Fns5Pg&m=x3sBbIAx3C0zb9JpbibPIYCIeUHW69zI56o-wr_NRhc&s=D7ypGz0vlaZn39U0V1XHQE68lHYmrDi4YTyQOuQOwzU&e= To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >> > > edit /etc/ssh/sshd_config to reflect which key you want to use. I use rsa. > > # HostKey for protocol version 1 > #HostKey /etc/ssh/ssh_host_key > # HostKeys for protocol version 2 > HostKey /etc/ssh/ssh_host_rsa_key > #HostKey /etc/ssh/ssh_host_dsa_key > #HostKey /etc/ssh/ssh_host_ecdsa_key > #HostKey /etc/ssh/ssh_host_ed25519_key > > Then do, as root: > > ssh-keygen -t rsa -b 4096 > > I used 4096 because I am paranoid. > > then: > > service sshd restart > > should work > > > The ssh-keygen command is the hint I needed. Used ssh-keygen -A which builds all the host keys by default. That fixed the problem. Thanks From owner-freebsd-questions@freebsd.org Thu Apr 21 05:53:16 2016 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 33CA5B1751F for ; Thu, 21 Apr 2016 05:53:16 +0000 (UTC) (envelope-from pagaled@saifunguo.com) Received: from m97115.qiye.163.com (m97115.qiye.163.com [220.181.97.115]) by mx1.freebsd.org (Postfix) with ESMTP id 247091D5A for ; Thu, 21 Apr 2016 05:53:11 +0000 (UTC) (envelope-from pagaled@saifunguo.com) Received: from pagaled$saifunguo.com ( [218.17.44.42] ) by ajax-webmail-wmsvr11 (Coremail) ; Thu, 21 Apr 2016 13:30:46 +0800 (CST) X-Originating-IP: [218.17.44.42] Date: Thu, 21 Apr 2016 13:30:46 +0800 (CST) From: pagaled To: freebsd-questions@FreeBSD.org Subject: Enquiry Paragliding X-Priority: 3 X-Mailer: Coremail Webmail Server Version SP_ntes V3.5 build 20150911(74783.7961) Copyright (c) 2002-2016 www.mailtech.cn 163-hosting MIME-Version: 1.0 Message-ID: <3d22b2ae.97e7.154374c95ff.Coremail.pagaled@saifunguo.com> X-CM-TRANSID: c+CowEBp40WHZRhX85gCAA--.2863W X-CM-SenderInfo: hhruzv2r6vtx5ixqw33rof0z/1tbiQgJSx1bdFBVyKwAFsD X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU== Content-Type: text/plain; charset=GBK Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2016 05:53:16 -0000 RGVhciBDRU8sCiAgICAgICAKUGxlYXNlIHNlZSB0aGUgYXR0YWNobWVudCBvZiBQYXJhZ2xpZGlu Zy4KCgoKCi0tCgpCZXN0IHJlZ2FyZHMKCgoKClVzaGVyIENhZ2UKClRlbKO6IDAwODYtNzU1LTM2 NjIxNzM2CgpNb2IgIDowMDg2LTE1OSA4OTQ0IDExNzUKCkUtbWFpbDogYWRtaW5AcGFnYWxlZC5j b20KCiAgICAgICAgICAgICB1c2hlckBwZWdhbGVkLmNvbQ== From owner-freebsd-questions@freebsd.org Thu Apr 21 06:26:03 2016 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 0DE1EB1637C for ; Thu, 21 Apr 2016 06:26:03 +0000 (UTC) (envelope-from Alexander.Holte.Davidsen@kulturit.no) Received: from mx2.kulturit.no (mx2.kulturit.no [195.159.218.104]) by mx1.freebsd.org (Postfix) with ESMTP id 839B21753 for ; Thu, 21 Apr 2016 06:26:01 +0000 (UTC) (envelope-from Alexander.Holte.Davidsen@kulturit.no) X-AuditID: ac10ad3d-f79a76d000000b05-14-57186eed6715 Received: from SKIEX-002.mid.no ( [10.11.1.91]) by mx2.kulturit.no (Symantec Messaging Gateway) with SMTP id 91.71.02821.DEE68175; Thu, 21 Apr 2016 08:10:54 +0200 (CEST) Received: from SKIEX-100.mid.no ([fe80::f009:d543:74e3:208b]) by SKIEX-002.mid.no ([::1]) with mapi id 14.03.0195.001; Thu, 21 Apr 2016 08:10:53 +0200 From: Alexander Holte-Davidsen To: "freebsd-questions@freebsd.org" Subject: Loss of disk made zfs pool unavailable Thread-Topic: Loss of disk made zfs pool unavailable Thread-Index: AQHRm5SPE2POMNFRAE+vLPsFvsQ32w== Date: Thu, 21 Apr 2016 06:10:52 +0000 Message-ID: <20160421061052.GA31812@fonzie.mid.no> Accept-Language: en-US, nb-NO Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [195.159.218.126] Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="9jxsPFA5p3P2qPhR" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrILMWRmVeSWpSXmKPExsXCxc0YrfsuTyLcoP0bi8XLr5tYHBg9Znya zxLAGMVlk5Kak1mWWqRvl8CV8e3sAeaCXomKI59SGxhXiXQxcnBICJhIzDyl28XICWSKSVy4 t56ti5GLQ0hgNaPE4sObWSGcWYwSLWfmMYNUsQm4Ssya2MECYosIOEusPvObFcQWFtCX2HJx HjtE3ESiffsjZghbT2JRwzcmEJtFQFVi4fM9YPW8AkYS83cfZAOxGQVkJVa1vgOrYRYQl7j1 ZD4TxEUiEg8vnmaDsEUlXj7+xwphK0scODiNGaK+TOLZ+YnMEDMFJU7OfMIygVFoFpJRs5CU zUJSBhHXkrjx7yVQDQeQLS2x/B8HRNhWYt269ywLGNlWMYoFe3sG55YU+JeW6BoYGOnlZqbo peRWbWIEBv4agbW2OxivfHc6xCjAwajEw7tBRiJciDWxrLgy9xCjCtCgRxtWX2CUYsnLz0tV EuE1yQJK86YkVlalFuXHF5XmpBYfYpTmYFES530+jT1cSCA9sSQ1OzW1ILUIJsvEwSnVwLhO sm67QFLGuhe1dWYmtyYr3fzyY5q8zBHjY//LezJ/CYckySQlsB5Q+jBj9g9jp/2/VnxT/3Jl pSpzXLifj+3Ue2dXMs/z9/2u5p3je+6944u7H/9w9H4yPblbgjWrjuWM9JkZSl91t+kE9QtE nKubfFD6jcrj77r1j7XPXBR+vvKD+iHTUH4lluKMREMt5qLiRACjmtaZhAIAAA== X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2016 06:26:03 -0000 --9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi all, Yesterday I lost one disk in one of our zfs pools. dmesg shows the following output: Apr 20 16:07:37 sto01 kernel: (noperiph:mpr0:0:4294967295:0): SMID 1 Aborting command 0xfffffe00015db000 Apr 20 16:07:37 sto01 kernel: mpr0: Sending reset from mprsas_send_abort for target ID 49 Apr 20 16:07:40 sto01 kernel: mpr0: mprsas_prepare_remove: Sending reset for target ID 49 Apr 20 16:07:40 sto01 kernel: da22 at mpr0 bus 0 scbus12 target 49 lun 0 Apr 20 16:07:40 sto01 kernel: da22: s/n Z1Z9QZJB detached Apr 20 16:07:41 sto01 kernel: (da22:mpr0:0:49:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 00 00 00 Apr 20 16:07:41 sto01 kernel: mpr0: (da22:mpr0:0:49:0): CAM status: Command timeout Apr 20 16:07:41 sto01 kernel: IOCStatus = 0x4b while resetting device 0x1d Apr 20 16:07:41 sto01 kernel: (da22:mpr0: mpr0:0:Unfreezing devq for target ID 49 Apr 20 16:07:41 sto01 kernel: 49:0): Error 5, Periph was invalidated Apr 20 16:07:41 sto01 kernel: mpr0: Unfreezing devq for target ID 49 Apr 20 16:07:41 sto01 kernel: (da22:mpr0:0:49:0): Periph destroyed Apr 20 16:07:41 sto01 devd: Executing 'logger -p kern.notice -t ZFS 'vdev is removed, pool_guid=8487159098644794736 vdev_guid=5745784146163956924'' Apr 20 16:07:41 sto01 ZFS: vdev is removed, pool_guid=8487159098644794736 vdev_guid=5745784146163956924 This disk was part of a raidz1. This is not really a problem, I expect disks to crash, that's why we are using zfs in this first place. What I did not expect was the pool to become unusable and having to reboot the server to be able to replace the disk. After the disk crashed all zpool and zfs command where just hanging, no output at all. The clients connected to this server also lost their ability to read and write to the pool. Is this the expected behavior or was I just unlucky? I see that the zpool property failmode is set to "wait", would using "continue" solved the issue with the server hanging? When the server was rebooted I was able to replace the disk with a spare, resilvering and scrub finished without any errors. Some system info; #freebsd-version -ku 10.3-RELEASE 10.3-RELEASE #uname -a FreeBSD sto01 10.3-RELEASE FreeBSD 10.3-RELEASE #0 r297264: Fri Mar 25 02:10:02 UTC 2016 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 Regards, Alexander --9jxsPFA5p3P2qPhR Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXGG7sAAoJEIWqNN0T0iPS9bgH/Ah5lR4NR2M0JIH3OAVVaak8 T2LJEw19KkcE7lcZj8SLpt0NWUbfpx3djNQ3Hhh7sxw3EqjcmVhyb0Ket8P45VQU HUdrwjUsb/cZv+gtwnI+DB638n1YW4hA1Ekw3F+xSBTGzmOoF6XpUry391Z6VvUE zzMdgiKgyI+Qv8tadFPWJSy7IVBUdAPLXt8JUltznUsnL4yEb+HWKotEqZifsYX2 Bqhy3yo4UfnL+89HB/+u7f3qHZ7xZdYeEVJXCQVMH46huNoBzVcEnkTpQIrA10Xj nbU8dClp93b5IoFUCr2ioQ7ye2HGYioy6esWbr0nHZe4I9fi0jgZ8d8SWqyrcks= =sfWN -----END PGP SIGNATURE----- --9jxsPFA5p3P2qPhR-- From owner-freebsd-questions@freebsd.org Thu Apr 21 06:27:28 2016 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 88E9CB16485 for ; Thu, 21 Apr 2016 06:27:28 +0000 (UTC) (envelope-from ml@netfence.it) Received: from smtp207.alice.it (smtp207.alice.it [82.57.200.103]) by mx1.freebsd.org (Postfix) with ESMTP id 27B4119ED for ; Thu, 21 Apr 2016 06:27:27 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.ventu (79.32.5.200) by smtp207.alice.it (8.6.060.28) (authenticated as acanedi@alice.it) id 57175E92003CD461 for freebsd-questions@freebsd.org; Thu, 21 Apr 2016 08:27:14 +0200 Received: from alamar.ventu (alamar.ventu [10.1.2.18]) by soth.ventu (8.15.2/8.14.9) with ESMTP id u3L6RIvm042724 for ; Thu, 21 Apr 2016 08:27:18 +0200 (CEST) (envelope-from ml@netfence.it) To: freebsd-questions@freebsd.org From: Andrea Venturoli Subject: External HD not working Message-ID: <41b7ddf8-8679-a5d8-5837-b306895081de@netfence.it> Date: Thu, 21 Apr 2016 08:27:18 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2016 06:27:28 -0000 Hello. I'm not sure this is a FreeBSD problem (as opposed to an hardware problem), since I've had no chance to test on different OSes... I've got a WD RED 3TB SATA drive and it won't work if attached as an external drive. I first tried with an USB-to-SATA adapter (which has always worked with different HDs) on a 10.2/i386 and I got: > Apr 16 09:04:51 alamar kernel: da7 at umass-sim1 bus 1 scbus10 target 0 lun 0 > Apr 16 09:04:51 alamar kernel: da7: Fixed Direct Access SPC-3 SCSI device > Apr 16 09:04:51 alamar kernel: da7: Serial Number 000001D91CC4 > Apr 16 09:04:51 alamar kernel: da7: 40.000MB/s transfers > Apr 16 09:04:51 alamar kernel: da7: 2861588MB (5860533168 512 byte sectors: 255H 63S/T 364801C) > Apr 16 09:04:51 alamar kernel: da7: quirks=0xa > ... > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): READ(10). CDB: 28 00 00 00 00 80 00 00 10 00 > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): CAM status: CCB request completed with an error > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): Retrying command > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): READ(10). CDB: 28 00 00 00 00 80 00 00 10 00 > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): CAM status: CCB request completed with an error > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): Retrying command > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): READ(10). CDB: 28 00 00 00 00 80 00 00 10 00 > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): CAM status: CCB request completed with an error > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): Retrying command > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): READ(10). CDB: 28 00 00 00 00 80 00 00 10 00 > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): CAM status: CCB request completed with an error > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): Retrying command > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): READ(10). CDB: 28 00 00 00 00 80 00 00 10 00 > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): CAM status: CCB request completed with an error > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): Error 5, Retries exhausted > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): READ(10). CDB: 28 00 00 00 00 10 00 00 10 00 > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): CAM status: CCB request completed with an error > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): Retrying command > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): READ(10). CDB: 28 00 00 00 00 10 00 00 10 00 > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): CAM status: CCB request completed with an error > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): Retrying command > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): READ(10). CDB: 28 00 00 00 00 10 00 00 10 00 > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): CAM status: CCB request completed with an error > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): Retrying command > (repeat ad lib until I disconneted it or the box wouldn't boot) > Apr 16 09:04:51 alamar kernel: da7 at umass-sim1 bus 1 scbus10 target 0 lun 0 > Apr 16 09:04:51 alamar kernel: da7: s/n 000001D91CC4 detached > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): Periph destroyed So I tried a eSATA-to-SATA adapter on a 9.3/i386 box, but connecting it didn't trigger anything: everything was like I didn't even plug it in (I heard the drive spinning, though). The drive works perfectly on three different computers if connected on the SATA controller on the MB. Any hint? At least knowing if it's an hardware or FreeBSD limitation could help me get on the right track. bye & Thanks av. From owner-freebsd-questions@freebsd.org Thu Apr 21 06:41:51 2016 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 24764B16C88 for ; Thu, 21 Apr 2016 06:41:51 +0000 (UTC) (envelope-from markoml@markoturk.info) Received: from vps.markoturk.info (vps.markoturk.info [95.154.208.14]) by mx1.freebsd.org (Postfix) with ESMTP id D15B412C9 for ; Thu, 21 Apr 2016 06:41:50 +0000 (UTC) (envelope-from markoml@markoturk.info) Received: from vps.markoturk.info (localhost [127.0.0.1]) by vps.markoturk.info (Postfix) with ESMTP id 41ACB2B830; Thu, 21 Apr 2016 08:33:15 +0200 (CEST) Date: Thu, 21 Apr 2016 08:33:14 +0200 From: Marko Turk To: Andrea Venturoli Cc: freebsd-questions@freebsd.org Subject: Re: External HD not working Message-ID: <20160421063313.GA2034@vps.markoturk.info> References: <41b7ddf8-8679-a5d8-5837-b306895081de@netfence.it> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="sm4nu43k4a2Rpi4c" Content-Disposition: inline In-Reply-To: <41b7ddf8-8679-a5d8-5837-b306895081de@netfence.it> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2016 06:41:51 -0000 --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Thu, Apr 21, 2016 at 08:27:18AM +0200, Andrea Venturoli wrote: > Hello. >=20 > I'm not sure this is a FreeBSD problem (as opposed to an hardware=20 > problem), since I've had no chance to test on different OSes... >=20 > I've got a WD RED 3TB SATA drive and it won't work if attached as an=20 > external drive. >=20 >=20 >=20 > I first tried with an USB-to-SATA adapter (which has always worked with= =20 > different HDs) on a 10.2/i386 and I got: On which USB port did you connect it? I got similar errors when I connected it to front USB port but when I connected it to the back USB port (the one directly connected to motherboard) it worked. -Marko > > Apr 16 09:04:51 alamar kernel: da7 at umass-sim1 bus 1 scbus10 target 0= lun 0 > > Apr 16 09:04:51 alamar kernel: da7: Fixed Dire= ct Access SPC-3 SCSI device > > Apr 16 09:04:51 alamar kernel: da7: Serial Number 000001D91CC4 > > Apr 16 09:04:51 alamar kernel: da7: 40.000MB/s transfers > > Apr 16 09:04:51 alamar kernel: da7: 2861588MB (5860533168 512 byte sect= ors: 255H 63S/T 364801C) > > Apr 16 09:04:51 alamar kernel: da7: quirks=3D0xa > > ... > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): READ(10). CDB: 2= 8 00 00 00 00 80 00 00 10 00 > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): CAM status: CCB = request completed with an error > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): Retrying command > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): READ(10). CDB: 2= 8 00 00 00 00 80 00 00 10 00 > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): CAM status: CCB = request completed with an error > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): Retrying command > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): READ(10). CDB: 2= 8 00 00 00 00 80 00 00 10 00 > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): CAM status: CCB = request completed with an error > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): Retrying command > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): READ(10). CDB: 2= 8 00 00 00 00 80 00 00 10 00 > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): CAM status: CCB = request completed with an error > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): Retrying command > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): READ(10). CDB: 2= 8 00 00 00 00 80 00 00 10 00 > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): CAM status: CCB = request completed with an error > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): Error 5, Retries= exhausted > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): READ(10). CDB: 2= 8 00 00 00 00 10 00 00 10 00 > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): CAM status: CCB = request completed with an error > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): Retrying command > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): READ(10). CDB: 2= 8 00 00 00 00 10 00 00 10 00 > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): CAM status: CCB = request completed with an error > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): Retrying command > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): READ(10). CDB: 2= 8 00 00 00 00 10 00 00 10 00 > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): CAM status: CCB = request completed with an error > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): Retrying command > > (repeat ad lib until I disconneted it or the box wouldn't boot) > > Apr 16 09:04:51 alamar kernel: da7 at umass-sim1 bus 1 scbus10 target 0= lun 0 > > Apr 16 09:04:51 alamar kernel: da7: s/n 000001= D91CC4 detached > > Apr 16 09:04:51 alamar kernel: (da7:umass-sim1:1:0:0): Periph destroyed >=20 >=20 >=20 > So I tried a eSATA-to-SATA adapter on a 9.3/i386 box, but connecting it= =20 > didn't trigger anything: everything was like I didn't even plug it in (I= =20 > heard the drive spinning, though). >=20 >=20 >=20 > The drive works perfectly on three different computers if connected on=20 > the SATA controller on the MB. >=20 >=20 >=20 > Any hint? > At least knowing if it's an hardware or FreeBSD limitation could help me= =20 > get on the right track. >=20 >=20 >=20 > bye & Thanks > av. > _______________________________________________ > 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" --sm4nu43k4a2Rpi4c Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXGHQoAAoJEHg6bF2mqM2IRQMQAMXBFN9EMG3M1zXz9EIoYBBM LO+js/cHuC1HrA/YaJEKkHloCYFmOXPWSnj+2IMKtLiHnKmIDyAOsesE8abQ8OwK 6SWi5Fuin+BdjfQYZeGsUQRkqax96bmnQXyFGUlhkjCDuwlP25m/+KRUbRrkMjYg Y0Llr5ObhTh6Rr6VYUyptWLLtL40j3K27W4QiZjWYxRomtr/MeUGp+wyZ67GDfei wbNCHs9vBhV7PLv7qOr3nDRNMgXfW46eVvS8/XyYzUH1/+4l+uOqpLRjtwwfwOFY 6cBd/+mW+9GCrzSAq3naR7MyB7UgVu+P2k3t00EI+vTOT14wqg8yXnYs5TIkhqGD gMoJy3FZAK4ySqL2dhROb9IJZ3yj9rpLy5ANgNcEYVnXGeXZltFL3/pFP+9MadwQ tpPz7QguORmO3bVPzfFxfQ6kj1+kKyvWa5yvUOvrrq1KP/8ic88HU8Tf3IEyXQTa Ry72zhtvy0S0JXLlrJkSdb18oWXRAon7UXPSYa45axqZ4LVXen1dJ/gs56K3idgy 5YSSny0Q2BFL9Ia+lRF+zbXuvQEorfIGdsAme2tiPRovOWSeOULhybzVZKCFOLXR u5BWfVluGMzaIrMy241M/ev5c7lmY1AjBwuvBWddn/tYtyGswGtx/rDErDjqLsOE 1+D9I6RC+KJ7ZHpiLXHS =OMbz -----END PGP SIGNATURE----- --sm4nu43k4a2Rpi4c-- From owner-freebsd-questions@freebsd.org Thu Apr 21 13:17:04 2016 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 C906EB16B6B for ; Thu, 21 Apr 2016 13:17:04 +0000 (UTC) (envelope-from www-data@vps20012.ovh.net) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id B69071ED3 for ; Thu, 21 Apr 2016 13:17:04 +0000 (UTC) (envelope-from www-data@vps20012.ovh.net) Received: by mailman.ysv.freebsd.org (Postfix) id B2264B16B6A; Thu, 21 Apr 2016 13:17:04 +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 B1BFFB16B69 for ; Thu, 21 Apr 2016 13:17:04 +0000 (UTC) (envelope-from www-data@vps20012.ovh.net) Received: from vps43779.vps.ovh.ca (unknown [IPv6:2607:5300:100:100::36d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8F6C71ED2 for ; Thu, 21 Apr 2016 13:17:04 +0000 (UTC) (envelope-from www-data@vps20012.ovh.net) Received: from www-data by vps43779.vps.ovh.ca with local (Exim 4.80) (envelope-from ) id 1atEaT-0007TS-2X for questions@freebsd.org; Thu, 21 Apr 2016 09:24:05 -0400 To: questions@freebsd.org Subject: QUEST, Notice to appear in Court #00297337 X-PHP-Originating-Script: 33:post.php(5) : regexp code(1) : eval()'d code(17) : eval()'d code Date: Thu, 21 Apr 2016 13:24:05 +0000 From: "District Court" Reply-To: "District Court" Message-ID: <55281a86fbb4abdead423a2b22f47780@lecturesdenicholas.com> X-Priority: 3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2016 13:17:04 -0000 Dear Quest, This is to inform you to appear in the Court on the April 25 for your case hearing. Please, do not forget to bring all the documents related to the case. Note: The case will be heard by the judge in your absence if you do not come. You can find the Court Notice is in the attachment. Kind regards, Julian Peterson, Clerk of Court. From owner-freebsd-questions@freebsd.org Thu Apr 21 14:21:57 2016 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 8D658B16521 for ; Thu, 21 Apr 2016 14:21:57 +0000 (UTC) (envelope-from wodfer@gmail.com) Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::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 32CF612D6 for ; Thu, 21 Apr 2016 14:21:57 +0000 (UTC) (envelope-from wodfer@gmail.com) Received: by mail-wm0-x230.google.com with SMTP id u206so135364830wme.1 for ; Thu, 21 Apr 2016 07:21:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=0uLHwXJZF9PDnc4J+kiOiW8CvvyM9cSsCSnXiANnk7w=; b=kLKNgqcM79lGvmdzm5WsyAWwXRwKzjnsNinMqufMPa+/vXOCCvRLdIHbKhbi2q39w4 /yjo38W1/J/Bek4LDGrDxdcJmh0w4YzEhOhhR7tJojCe7y0Af1cGSgwtQDpc9ExD4KHE uVzN8LFIQtJyDeI2j12SrQT6z5yQZ6bCKyReCwDrRgyCNyPQbf4Nkfrun3vyTeTpX7wk tKkZclzZ84Ljw8ax7bC1jKVm1sX/WQTRskZqMMQyC4ruO/1EddNiQpQyx17RiCcVk/MA aH+wbYpT8FBZiFWfD+kns/2W3FnkCfTUWDmhqu7r4u+lGu1iFg/jahKp6xkhDziUqsp0 xnjQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=0uLHwXJZF9PDnc4J+kiOiW8CvvyM9cSsCSnXiANnk7w=; b=mKIu24hT2aYZzETYQa6QOSbsrvjKKZ9e2pT1aU7ShTCE8rYbQ8TTE7fqDZEufe9Li8 Enri8zjT/S8qtV384KbS2PnlG+y8WoKh835s9CHHCqT2rsDaOfduCm6casE7t12PX9Bi QpQwPtTdCuN5Y/axqtC0sGAvVC3rBrVnaOucCVVhrXY6l+f73Idc4794EiIORajFpuFZ +e6aYlI4iwI3eYq0vqShlCwyr2ziGgzRJRQPhz6pGWE5lLBVlXmixmWlHOqNs8krLUx4 V+uWlo+ro4xDkjlipj7sjEVFpUEewqrcu7AvtZ4XCP6JUDKvtccZt4qhweQtL9+m8x56 8kxA== X-Gm-Message-State: AOPr4FVPmB745ZOFxREWSbl9g+WObba1MsfOmd7+s+oMYgVT+aCOwJxI0f6LmRL8K3L+4Rr3QwK3wM4EvltFqQ== MIME-Version: 1.0 X-Received: by 10.28.58.77 with SMTP id h74mr36893898wma.82.1461248514808; Thu, 21 Apr 2016 07:21:54 -0700 (PDT) Received: by 10.28.107.143 with HTTP; Thu, 21 Apr 2016 07:21:54 -0700 (PDT) Date: Thu, 21 Apr 2016 16:21:54 +0200 Message-ID: Subject: php7 and pecl-pdflib fails From: Andy Wodfer To: freebsd-questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2016 14:21:57 -0000 Hi, I recently upgraded to 10.3 REL on a test server. I'm trying to install all the latest versions for Apache, mysql, php and so on. php7 is installed and works perfectly with apache. However, I couldn't install the extension pecl-pdflib from the php7 extensions port, it fails with the message doesn't supprt php7. ===> phpMyAdmin-4.6.0 depends on file: /usr/local/lib/php/20151012/openssl.so - found ===> Returning to build of phpMyAdmin-4.6.0 ===> phpMyAdmin-4.6.0 depends on file: /usr/local/lib/php/20151012/pdf.so - not found ===> pecl-pdflib-3.0.4 cannot be installed: doesn't work with lang/php70 port (doesn't support PHP 70). *** Error code 1 Stop. make[2]: stopped in /usr/ports/print/pecl-pdflib *** Error code 1 Stop. make[1]: stopped in /usr/ports/databases/phpmyadmin *** Error code 1 Stop. make: stopped in /usr/ports/databases/phpmyadmin Does this mean I can't install phpmyadmin for now or is there a way around this? pecl-pdflib hasn't been updated for a couple of years it seems.. Anyone? Thanks, Andy From owner-freebsd-questions@freebsd.org Thu Apr 21 14:43:08 2016 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 1CD95B17028 for ; Thu, 21 Apr 2016 14:43:08 +0000 (UTC) (envelope-from arminkale666@gmail.com) Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com [IPv6:2a00:1450:400c:c09::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 ACAB31F40 for ; Thu, 21 Apr 2016 14:43:07 +0000 (UTC) (envelope-from arminkale666@gmail.com) Received: by mail-wm0-x242.google.com with SMTP id l6so22039313wml.3 for ; Thu, 21 Apr 2016 07:43:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-transfer-encoding:mime-version:date:subject:message-id :to; bh=4ht9G50SlYlr7BPTCuy+KjNotHQlLEXbSKghIYlF3TI=; b=WRoGSbJC49NxyU069o/S1+fhW2Zf1SvTQsKen2WK1XkXw54dKuG+bOEnGCctu45wtZ 8KzmGuEbVohjZ38q2BpX6BSCkZvHRhB0FQPLBFMJs0Z/9br67kcA8jyjDSjLvdd2vggv t0jnwCO09ll1emdFccbcPzvuwhjqsRl3TlsU+yJmchAaTgN33h2GGUYrQrmxlniX9h9u xhfiPN5qTKOSrNhrzxZujN/Gv2DXXdiBYLJbxsthIFEyMIBc1ZQwR/jRtpE6gEes4ZQ8 urlooZrUQ81zvISzdNrpfETUAgr9/eXbI6/Ljw3Xa1sJAAq+c7oK6EIe8WJuJqnTQPcE Zf7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-transfer-encoding:mime-version:date :subject:message-id:to; bh=4ht9G50SlYlr7BPTCuy+KjNotHQlLEXbSKghIYlF3TI=; b=aysrv9shxooVw+wKdUNYC94te9W/90xXOr1qXVmLrY1SRVvsSE7zIVd0EJsZSE8DBw Yrzl67DNJh2T+C7JV/Z8aj8/RoJYBwVJTxJjNyq2QJBq2b6JM+ucOcvbXm2JfznK+dgi BU+iY9hfBDPefOxl+RWeDODrKJchNlHSyFRAUbxI91wZbPhnUSlIb971CmQ4ov39gFS/ oCQeT+Pny8szChWdFzZsCSN0zJkYBbyZREtycz1yF07XAzy1od++Is8aF8MBgCyzzSu7 XVBTkXulJOXlbqV8GhN0a+ppzdMP7xoPibBaq9ouMQyBmJ7JP2J1Jw6Ec0HthGVFpMUt GxPQ== X-Gm-Message-State: AOPr4FWVJO2P0JSZLEYdbUy5W76eCwxIn+M5VawX1in+DX/kKe94a3aT++LrcDlhJnDAwA== X-Received: by 10.194.14.6 with SMTP id l6mr5962903wjc.48.1461249786355; Thu, 21 Apr 2016 07:43:06 -0700 (PDT) Received: from [10.8.1.102] ([94.242.239.38]) by smtp.gmail.com with ESMTPSA id t4sm3615097wmf.8.2016.04.21.07.43.05 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 21 Apr 2016 07:43:05 -0700 (PDT) From: armin armin Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (1.0) Date: Thu, 21 Apr 2016 19:13:02 +0430 Subject: F Message-Id: To: freebsd-questions@FreeBSD.org X-Mailer: iPhone Mail (13E238) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2016 14:43:08 -0000 Sent from my iPhone From owner-freebsd-questions@freebsd.org Thu Apr 21 14:58:18 2016 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 D29B6B1782D for ; Thu, 21 Apr 2016 14:58:18 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7B2311B32 for ; Thu, 21 Apr 2016 14:58:18 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from zero-gravitas.local (unknown [85.199.232.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 956BC11A76 for ; Thu, 21 Apr 2016 14:58:13 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/956BC11A76; dkim=none; dkim-atps=neutral Subject: Re: php7 and pecl-pdflib fails To: freebsd-questions@freebsd.org References: From: Matthew Seaman Message-ID: <5718EAAF.5050604@FreeBSD.org> Date: Thu, 21 Apr 2016 15:58:55 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="FOsW7Xddnde9G1DMttH7WQjsir7XTEJEK" X-Virus-Scanned: clamav-milter 0.99.1 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-0.4 required=5.0 tests=BAYES_00,RDNS_NONE, SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2016 14:58:18 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --FOsW7Xddnde9G1DMttH7WQjsir7XTEJEK Content-Type: multipart/mixed; boundary="MUqvEjNo1et7p5rCnjcmhojVtAxTDOrpJ" From: Matthew Seaman To: freebsd-questions@freebsd.org Message-ID: <5718EAAF.5050604@FreeBSD.org> Subject: Re: php7 and pecl-pdflib fails References: In-Reply-To: --MUqvEjNo1et7p5rCnjcmhojVtAxTDOrpJ Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2016/04/21 15:21, Andy Wodfer wrote: > Hi, > I recently upgraded to 10.3 REL on a test server. I'm trying to install= all > the latest versions for Apache, mysql, php and so on. >=20 > php7 is installed and works perfectly with apache. However, I couldn't > install the extension pecl-pdflib from the php7 extensions port, it fai= ls > with the message doesn't supprt php7. >=20 > =3D=3D=3D> phpMyAdmin-4.6.0 depends on file: > /usr/local/lib/php/20151012/openssl.so - found > =3D=3D=3D> Returning to build of phpMyAdmin-4.6.0 > =3D=3D=3D> phpMyAdmin-4.6.0 depends on file: /usr/local/lib/php/20151= 012/pdf.so > - not found > =3D=3D=3D> pecl-pdflib-3.0.4 cannot be installed: doesn't work with la= ng/php70 > port (doesn't support PHP 70). > *** Error code 1 >=20 > Stop. > make[2]: stopped in /usr/ports/print/pecl-pdflib > *** Error code 1 >=20 > Stop. > make[1]: stopped in /usr/ports/databases/phpmyadmin > *** Error code 1 >=20 > Stop. > make: stopped in /usr/ports/databases/phpmyadmin >=20 > Does this mean I can't install phpmyadmin for now or is there a way aro= und > this? pecl-pdflib hasn't been updated for a couple of years it seems.. >=20 > Anyone? I believe phpMyAdmin itself is compatible with php7 -- but I haven't personally tested that. Even though I'm the maintainer for phpMyAdmin, I don't use it that often nowadays: most of my database needs are served by postgresql at the moment. pecl-pdflib as you have found out is not compatible with php7. You should be able to get phpMyAdmin to install by turning off the PDF option. (typing: 'make config' in ${PORTSDIR}/databases/phpmyadmin is one way to do that.) In fact, all that option setting does is tell the packaging system that PMA does or doesn't depend on the PDF modules used by PHP. You get exactly the same content for the PMA application either way and it will autodetect the lack of a PDF module and adjust accordingly. Without PDF support you can't export your DB schema as a nicely formatted PDF document. AFAIR that's pretty much all the effect of not having it. Cheers, Matthew --MUqvEjNo1et7p5rCnjcmhojVtAxTDOrpJ-- --FOsW7Xddnde9G1DMttH7WQjsir7XTEJEK Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJXGOq3XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnYzUP+QGdAbTNLqY8edxDID0p50oO 1cGzd27+jKTq1rlcc+sYLL5/1zXgPGhSPdNLWLYGZysYAs2tW8ORG0ANaylr7KEZ 08A5tMIDOhF9VL6cte5ZDBeEfpXdWT31ykILaZAWv2hq8H2MY6gpaM2DkHjpeO8w HxeL7fG8sfOCrcEgGwT1lb/d4cy8B4ocQz79uKAsJG1ETI5BZ5YJmLbhd5hwOwwy bP0xqDSsr+u9kP3/dn4HutGMj6FHSmMy84Dml72e8jotvIquIUOmrP8YzABhriMG DtxWFvixqqoXjsZ8mKgSel9vd3vOioOa6FlBv8cfWgabDYi5q2RjyxIodNNRzfnJ aspS8mh4fVl3VlYMTlE29CoGFreGhGcQSpyIuf9i6hKl5C1JqQiM9hXRJHJcNmjA YitS5o+uw5/iozp9BX+QvkjNnu5KHW7ERRkJMkk+saR9NE2XYpzKrkIGMv/3igV0 y1L1mG0ZL4aTLK9K2mJAmCLN4RL6TSDsWvM3HZ0kRVgO3ut1i8TxYrjY0B92YlTP 1wNRV+yIzZxOqlUUjXvxbMmecysvR+SkM6bM522G9ciNjKkV5nTH07ddtHsBE4br e5LE8oV1hYhzLwhndrpV2syUaThTnfQLjOPpiPjJatu9HbKoh4ZgdDIa7Ljn1bDC xVAn3Wb53CuqARElaxmW =8gxN -----END PGP SIGNATURE----- --FOsW7Xddnde9G1DMttH7WQjsir7XTEJEK-- From owner-freebsd-questions@freebsd.org Thu Apr 21 15:11:11 2016 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 A5A16B150D4 for ; Thu, 21 Apr 2016 15:11:11 +0000 (UTC) (envelope-from wodfer@gmail.com) Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::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 3FF161C69 for ; Thu, 21 Apr 2016 15:11:11 +0000 (UTC) (envelope-from wodfer@gmail.com) Received: by mail-wm0-x22a.google.com with SMTP id n3so138433525wmn.0 for ; Thu, 21 Apr 2016 08:11:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=O/W21/Skv5+VchLYvex0U0eTqwdie53tRcqpou1PZtQ=; b=uQMPBbBWsslLa/5so2C/NZl/fGuP24WH9l3tDV4ZfTNM0hRW5l5nfJ+WxUF3Z9YBZR +xPncBeD8gURS/if558XNyA15tdh3Edwrrm6S2CNhaxb7W2U/1J+CANo2ad34s7lgM4L RY/s2hQIcLVfAZdBQt0ToLlmx5/Tmc1plIplh7BIhDTTGP4gIji6b9vfVsllUzwOsBU0 gCqHLMHX6k3oTXQx+Qsh/k/+4QqE0i8tNe7jG/5Qkm3966j0vkejwKiASbZMf4W+vunV 5VOyIN/IbCbVUnAngHBdd/aMlV4Uu2mIBTR7DYbtapIJn81sw5Ns6DBOQRKvMPHfWF2U pQbQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=O/W21/Skv5+VchLYvex0U0eTqwdie53tRcqpou1PZtQ=; b=BwBgXEI7cg2yJISU1eLQrxrsYTcmVC5561DvIVEF8pr5RlPMzNLLcvfktO2FxXjNoY IiR6dwnD9YzJG/ZS4IS65LmgkKyRF1TGlbOh+PSlcLhGBLtvdTOVnT5yDW3y1NdKXddg mBo+ZWeU45IPARugeaVjRJDD0pWhHVt+i4cjySkhTxcSKxCI6KeBZhI3TLzYLN1bgUQz 9+IyrTuQ89aobkudAj7yXhQpspaflcxKRK+XtSQbbsUEU3bWnUgr1gBibVzNaKebn/HF BSSUwHIU/E3UnO8f1sF623IScQFogzAd0Wb3zqWP9gKFZ3wL/xfuwTMEy8tO+mtBF+pD Ubiw== X-Gm-Message-State: AOPr4FVASM1KnbtBuUirdYuFimL4J6DaYHWlJUx337mHrahsBhIxiYYWqo0X5tug0cNi+DBMH32WpsZxio456A== MIME-Version: 1.0 X-Received: by 10.194.104.135 with SMTP id ge7mr14967268wjb.15.1461251469790; Thu, 21 Apr 2016 08:11:09 -0700 (PDT) Received: by 10.28.107.143 with HTTP; Thu, 21 Apr 2016 08:11:09 -0700 (PDT) In-Reply-To: <5718EAAF.5050604@FreeBSD.org> References: <5718EAAF.5050604@FreeBSD.org> Date: Thu, 21 Apr 2016 17:11:09 +0200 Message-ID: Subject: Re: php7 and pecl-pdflib fails From: Andy Wodfer To: freebsd-questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2016 15:11:11 -0000 Thanks Matthew! That fixed it. I never export to PDF anyways so this is perfect. Thanks for your help! Best, Andy On Thu, Apr 21, 2016 at 4:58 PM, Matthew Seaman wrote: > On 2016/04/21 15:21, Andy Wodfer wrote: > > Hi, > > I recently upgraded to 10.3 REL on a test server. I'm trying to install > all > > the latest versions for Apache, mysql, php and so on. > > > > php7 is installed and works perfectly with apache. However, I couldn't > > install the extension pecl-pdflib from the php7 extensions port, it fails > > with the message doesn't supprt php7. > > > > ===> phpMyAdmin-4.6.0 depends on file: > > /usr/local/lib/php/20151012/openssl.so - found > > ===> Returning to build of phpMyAdmin-4.6.0 > > ===> phpMyAdmin-4.6.0 depends on file: > /usr/local/lib/php/20151012/pdf.so > > - not found > > ===> pecl-pdflib-3.0.4 cannot be installed: doesn't work with lang/php70 > > port (doesn't support PHP 70). > > *** Error code 1 > > > > Stop. > > make[2]: stopped in /usr/ports/print/pecl-pdflib > > *** Error code 1 > > > > Stop. > > make[1]: stopped in /usr/ports/databases/phpmyadmin > > *** Error code 1 > > > > Stop. > > make: stopped in /usr/ports/databases/phpmyadmin > > > > Does this mean I can't install phpmyadmin for now or is there a way > around > > this? pecl-pdflib hasn't been updated for a couple of years it seems.. > > > > Anyone? > > I believe phpMyAdmin itself is compatible with php7 -- but I haven't > personally tested that. Even though I'm the maintainer for phpMyAdmin, > I don't use it that often nowadays: most of my database needs are served > by postgresql at the moment. > > pecl-pdflib as you have found out is not compatible with php7. You > should be able to get phpMyAdmin to install by turning off the PDF > option. (typing: 'make config' in ${PORTSDIR}/databases/phpmyadmin is > one way to do that.) > > In fact, all that option setting does is tell the packaging system that > PMA does or doesn't depend on the PDF modules used by PHP. You get > exactly the same content for the PMA application either way and it will > autodetect the lack of a PDF module and adjust accordingly. Without PDF > support you can't export your DB schema as a nicely formatted PDF > document. AFAIR that's pretty much all the effect of not having it. > > Cheers, > > Matthew > > > > From owner-freebsd-questions@freebsd.org Thu Apr 21 17:19:33 2016 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 B7EABB17659 for ; Thu, 21 Apr 2016 17:19:33 +0000 (UTC) (envelope-from sean@siobud.com) Received: from siobud.com (siobud.com [104.236.58.159]) by mx1.freebsd.org (Postfix) with ESMTP id 9636B11D1 for ; Thu, 21 Apr 2016 17:19:33 +0000 (UTC) (envelope-from sean@siobud.com) Received: from SeanLaptop (c-73-8-76-141.hsd1.il.comcast.net [73.8.76.141]) by siobud.com (Postfix) with ESMTPSA id 9E036D7E7D; Thu, 21 Apr 2016 17:12:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=siobud.com; s=mail; t=1461258722; bh=p+luc+hSeWZq5PS+ZIXKoGEk3XvYX/suBjUE/XZ3x4A=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=2x6rkRMRXLDi2Op9pb2y6jlpEfoCXdAAnU7J6dQrtxyTJZXAEkFExVumAeP/r76+r kcVo4iPJyi0DeQg6SM4Nl1zyyPXM5Hfyyc5eGQlUOA4I2vFW3+zEH9hrpuc9D2AXGP aLcrasfn4nO+hRffBsEiylOeM0/Ve0dwLb9f+aXw= Date: Thu, 21 Apr 2016 12:12:00 -0500 From: Sean DuBois To: Andy Wodfer Cc: freebsd-questions Subject: Re: php7 and pecl-pdflib fails Message-ID: <20160421171200.GA967@SeanLaptop> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2016 17:19:33 -0000 On Thu, Apr 21, 2016 at 04:21:54PM +0200, Andy Wodfer wrote: > Hi, > I recently upgraded to 10.3 REL on a test server. I'm trying to install all > the latest versions for Apache, mysql, php and so on. > > php7 is installed and works perfectly with apache. However, I couldn't > install the extension pecl-pdflib from the php7 extensions port, it fails > with the message doesn't supprt php7. > > ===> phpMyAdmin-4.6.0 depends on file: > /usr/local/lib/php/20151012/openssl.so - found > ===> Returning to build of phpMyAdmin-4.6.0 > ===> phpMyAdmin-4.6.0 depends on file: /usr/local/lib/php/20151012/pdf.so > - not found > ===> pecl-pdflib-3.0.4 cannot be installed: doesn't work with lang/php70 > port (doesn't support PHP 70). > *** Error code 1 > > Stop. > make[2]: stopped in /usr/ports/print/pecl-pdflib > *** Error code 1 > > Stop. > make[1]: stopped in /usr/ports/databases/phpmyadmin > *** Error code 1 > > Stop. > make: stopped in /usr/ports/databases/phpmyadmin > > Does this mean I can't install phpmyadmin for now or is there a way around > this? pecl-pdflib hasn't been updated for a couple of years it seems.. > > Anyone? > > Thanks, > Andy Hi Andy! I do php-src/extension development[0] and would love to port pecl-pdflib to PHP 7 if you need it/can confirm everything works. thanks [0] http://pecl.php.net/user/seander From owner-freebsd-questions@freebsd.org Thu Apr 21 23:06:24 2016 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 42AF8B18E2C for ; Thu, 21 Apr 2016 23:06:24 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 30CB110E0 for ; Thu, 21 Apr 2016 23:06:24 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: by mailman.ysv.freebsd.org (Postfix) id 3027CB18E2A; Thu, 21 Apr 2016 23:06:24 +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 2FA17B18E29; Thu, 21 Apr 2016 23:06:24 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EAC8710DF; Thu, 21 Apr 2016 23:06:23 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from [10.9.9.241] (helo=rmm6prod02.runbox.com) by bars.runbox.com with esmtp (Exim 4.71) (envelope-from ) id 1atNfw-0004Wt-Aq; Fri, 22 Apr 2016 01:06:20 +0200 Received: from mail by rmm6prod02.runbox.com with local (Exim 4.76) (envelope-from ) id 1atNfw-0006cx-AS; Fri, 22 Apr 2016 01:06:20 +0200 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (846156)] by runbox.com with http (RMM6); Thu, 21 Apr 2016 23:06:20 GMT From: "Jeffrey Bouquet" Reply-To: jbtakk@iherebuywisely.com To: "stable" CC: "questions" Subject: Curious about loader.conf variables that I had to edit out Date: Thu, 21 Apr 2016 16:06:20 -0700 (PDT) X-Mailer: RMM6 Message-Id: X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2016 23:06:24 -0000 Cross-posting two thee lists (here latter two, so more who may know may read...) These settings removed, from /boot/loader.conf, fixed a hosed current/custom kernel bootup (v11 of April 2016) that was a showstopper here... so one of those lines below may be an obvious problem someone knows about (either the sysctl, or value assigned to it...)=20 Otherwise, some/all may be fodder for one's own loader.conf if they are viable; each had a reason per a website or blog or wiki or list email obviously, at one time. (twelve years in compilation altogether so far...) # out snd_pcm_load=3D"YES" # out snd_acm_load=3D"YES" # out kern.msgbufsize=3D"130000" # out kern.ipc.shmmni=3D"1024" # out kern.ipc.shmseg=3D"1024" # out hw.snd.maxautovchans=3D"4" # out hw.snd.targetirqrate=3D"36"=20=20=20=20 # out hint.pcm.0.buffersize=3D"65536"=20 # out hw.snd.verbose=3D"3" # out kern.ipc.semmns=3D"240" # out kern.ipc.semume=3D"40" # out kern.ipc.semmnu=3D"120" # out vfs.read_max=3D"128"=20=20=20=20 # out kern.randompid=3D"1" # out kern.ipc.shmmax=3D"67108864"=20 # out kern.ipc.shmall=3D"32768" # out vm.kmem_size=3D"700M"=20=20=20=20 # out vm.kmem_size_max=3D"700M"=20=20 # out vfs.zfs.arc_max=3D"250M" # out kern.sched.preempt_thresh=3D"224" # out vfs.usermount=3D"1"=20=20=20 # out kern.geom.part.check_integrity=3D"0"=20=20 # out vm.overcommit=3D"1" # out kern.maxfilesperproc=3D"65536" # out kern.ipc.somaxconn=3D"1024" # out kern.ipc.nmbclusters=3D"81920" # out kern.fallback_elf_brand=3D"3" # out vfs.write_behind=3D"0" Not urgent but may save some time and trouble if I am careless upon uncommenting the line and it all goes south... from a PBKAC or similar.= From owner-freebsd-questions@freebsd.org Fri Apr 22 08:02:47 2016 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 116AFB1871A for ; Fri, 22 Apr 2016 08:02:47 +0000 (UTC) (envelope-from zmey20000@yahoo.com) Received: from nm32-vm1.bullet.mail.gq1.yahoo.com (nm32-vm1.bullet.mail.gq1.yahoo.com [98.136.216.224]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D6E1E1D03 for ; Fri, 22 Apr 2016 08:02:46 +0000 (UTC) (envelope-from zmey20000@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1461312054; bh=T9ulL47pMGotUudmMdVV78aX4SUDn+eluXdjqKbr+A8=; h=Date:From:Reply-To:To:Subject:References:From:Subject; b=i/FWGraDJOnzY59Dn7JNBB4Xpj211TgGYNT+h0nSGvNlAp7kpcUCcvRFwZCL0P/RanyZ0Rb/GphZjgiM/4YqpqtBDcrNT6a77yRgyqCU5cEI3Hu8grGmhWNg5ORiKbvpaCqF9AsVzGcmvwbrCE4ieppZeq/PBUmuRQQh+GxcOHtav1lP4019COi4QeqGqBZ4fzEsw0+0l1L6jWeAhEiB6Sj4heDRSGz9Xkwx1Xh8WeY+4p1wF0uG+j99VEB919s1BhXeq8U/N+osLgPeXzEdEzwei6VL/WO3zrhLtEfxF/CEVzNoUJr96dkATLkDpxwBA84hGtwkTJ18t/q85XN5qg== Received: from [127.0.0.1] by nm32.bullet.mail.gq1.yahoo.com with NNFMP; 22 Apr 2016 08:00:54 -0000 Received: from [216.39.60.180] by nm32.bullet.mail.gq1.yahoo.com with NNFMP; 22 Apr 2016 07:58:02 -0000 Received: from [98.139.215.143] by tm16.bullet.mail.gq1.yahoo.com with NNFMP; 22 Apr 2016 07:58:02 -0000 Received: from [98.139.212.198] by tm14.bullet.mail.bf1.yahoo.com with NNFMP; 22 Apr 2016 07:58:02 -0000 Received: from [127.0.0.1] by omp1007.mail.bf1.yahoo.com with NNFMP; 22 Apr 2016 07:58:02 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 208396.18433.bm@omp1007.mail.bf1.yahoo.com X-YMail-OSG: 4ihOxsIVM1n4qYfr7_Gwl28BJPWIvjQaaoIkhoHbDIwUWfId2Sh5sfzFcg9XqAM ZAF47IaT367Df5cjIgBkuwIxwqBSdvMyOuldKBSUCvJnJtA2Dj4FqTEEDzu7ruBEYjE3bhTnAf0b rDl0Uoten6YjJqtMgN1zUgS3kKtr0PHnWHP9oW4WPRzSJ_N9wIpnMINNB6uRQ4cdXx7upFp9aQk5 4WAMgiorGei.AxeJw5Lm5Ayj6SlULgDluKPXcMpxtGEsjU5rxlyskQq1nwNwnjwfuMaxflNZskeX X5eGHqXpnzFQTPyuhWI.FkSbmvovgVZBNLzqO68sNeKL0ZuW_mPLeAgRiwauBHfmJGLaJi23kIHo 6qHt_8db65GYpcCc_Svgl.IzYLovRlQNwC34YcEye5faYb388JbcGZl1AJ2nnRkbyk_FMnSvwkeU bbfHSOnY9qybmzuzXTRtd4FINMl79XlBkW1JIZPY8qLztEJaR9mnhW7u2YU8NzzHVM6DToOHE3uF M0e6k46T7R1mhZPT..gkaZmd.2byAalE- Received: by 66.196.80.116; Fri, 22 Apr 2016 07:58:01 +0000 Date: Fri, 22 Apr 2016 07:58:01 +0000 (UTC) From: Mikhail Zakharov Reply-To: Mikhail Zakharov To: "freebsd-questions@freebsd.org" Message-ID: <1362535907.181503.1461311881501.JavaMail.yahoo@mail.yahoo.com> Subject: FreeBSD based dual-controller storage system concept MIME-Version: 1.0 References: <1362535907.181503.1461311881501.JavaMail.yahoo.ref@mail.yahoo.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2016 08:02:47 -0000 Hi Community, I=E2=80=99m testing FreeBSD as the OS for a reliable dual-controller storag= e system with ZFS, mirrored cache and etc. I have some progress on it and m= y notes on the model are already took 30 of A4 format pages and their numbe= r is still growing. Looks like I need to publish it somehow to show the mod= el to the guys who may be interested. Do you know where is the best place t= o start? From owner-freebsd-questions@freebsd.org Fri Apr 22 13:07:40 2016 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 9BDF0B189DA for ; Fri, 22 Apr 2016 13:07:40 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 54D431A88 for ; Fri, 22 Apr 2016 13:07:39 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [62.216.201.207] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1atanx-0000n1-CK; Fri, 22 Apr 2016 15:07:30 +0200 Received: from localhost.my.domain (c720-r292778-amd64 [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id u3MD7QFI002533 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 22 Apr 2016 15:07:26 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id u3MD7Pbc002532; Fri, 22 Apr 2016 15:07:25 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Fri, 22 Apr 2016 15:07:24 +0200 From: Matthias Apitz To: freebsd-questions@freebsd.org Cc: kde-freebsd@kde.org Subject: QML hello.qml Message-ID: <20160422130724.GA2488@c720-r292778-amd64.oa.oclc.org> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , freebsd-questions@freebsd.org, kde-freebsd@kde.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Operating-System: FreeBSD 11.0-CURRENT r292778 (amd64) User-Agent: Mutt/1.5.24 (2015-08-30) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 62.216.201.207 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2016 13:07:40 -0000 Hello, I'm doing first steps in QML and follow the tutorial. The system is CURRENT on amd64 with qt5 from ports head: # pkg info | grep '^qt5-' qt5-core-5.4.1_2 Qt core non-graphical module qt5-dbus-5.4.1 Qt D-Bus inter-process communication module qt5-gui-5.4.1_3 Qt graphical user interface module qt5-imageformats-5.4.1 Qt plugins for additional image formats qt5-network-5.4.1 Qt network module qt5-opengl-5.4.1 Qt 5-compatible OpenGL support module qt5-printsupport-5.4.1 Qt print support module qt5-qml-5.4.1 Qt QML and JavaScript language module qt5-quick-5.4.1 Qt declarative framework for dynamic user interfaces qt5-sql-5.4.1 Qt SQL database integration module qt5-svg-5.4.1 Qt SVG support module qt5-testlib-5.4.1 Qt unit testing module qt5-webkit-5.4.1_2 Qt WebKit implementation qt5-widgets-5.4.1 Qt C++ widgets module qt5-xml-5.4.1 Qt SAX and DOM implementations qt5-xmlpatterns-5.4.1 Qt support for XPath, XQuery, XSLT and XML Schema With the example below the command $ /usr/local/lib/qt5/bin/qmlscene hello.qml gives only a grey box, but no text in it. What do I wrong? Thanks matthias // http://doc.qt.io/qt-5/qml-tutorial1.html // import QtQuick 2.0 Rectangle { id: page width: 320; height: 480 color: "lightgray" Text { id: helloText text: "Hello world!" y: 30 anchors.horizontalCenter: page.horizontalCenter font.pointSize: 24; font.bold: true } } -- Matthias Apitz, ✉ guru@unixarea.de, ⌂ http://www.unixarea.de/ ☎ +49-176-38902045 ¡Dios querido denos otra vez los problemas de ayer, los que tuvimos en la RDA! My Lord, give us back the problems of yesterday, those we have had in the GDR. From owner-freebsd-questions@freebsd.org Fri Apr 22 13:21:19 2016 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 1F3FAB18EFC for ; Fri, 22 Apr 2016 13:21:19 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E33311065 for ; Fri, 22 Apr 2016 13:21:18 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id u3MDLH1w012960 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 22 Apr 2016 07:21:17 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id u3MDLHaj012957; Fri, 22 Apr 2016 07:21:17 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Fri, 22 Apr 2016 07:21:17 -0600 (MDT) From: Warren Block To: Mikhail Zakharov cc: "freebsd-questions@freebsd.org" Subject: Re: FreeBSD based dual-controller storage system concept In-Reply-To: <1362535907.181503.1461311881501.JavaMail.yahoo@mail.yahoo.com> Message-ID: References: <1362535907.181503.1461311881501.JavaMail.yahoo.ref@mail.yahoo.com> <1362535907.181503.1461311881501.JavaMail.yahoo@mail.yahoo.com> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Fri, 22 Apr 2016 07:21:17 -0600 (MDT) Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2016 13:21:19 -0000 On Fri, 22 Apr 2016, Mikhail Zakharov via freebsd-questions wrote: > I’m testing FreeBSD as the OS for a reliable dual-controller storage > system with ZFS, mirrored cache and etc. I have some progress on it > and my notes on the model are already took 30 of A4 format pages and > their number is still growing. Looks like I need to publish it somehow > to show the model to the guys who may be interested. Do you know where > is the best place to start? The FreeBSD Journal, possibly: https://www.freebsdfoundation.org/journal/ There are also a number of conferences that are looking for papers. Too late for BSDCan this year, but EuroBSDCon is coming up in September: https://2016.eurobsdcon.org/call-for-papers/ From owner-freebsd-questions@freebsd.org Fri Apr 22 13:59:45 2016 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 6A6EEB17F78 for ; Fri, 22 Apr 2016 13:59:45 +0000 (UTC) (envelope-from zmey20000@yahoo.com) Received: from nm50-vm5.bullet.mail.ne1.yahoo.com (nm50-vm5.bullet.mail.ne1.yahoo.com [98.138.121.149]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3CE321B9E for ; Fri, 22 Apr 2016 13:59:45 +0000 (UTC) (envelope-from zmey20000@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1461333452; bh=Y2F/PVGAgPMVkPSYqzfiKUOF0CPsg8urLVnIYRCLZHw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=h7x/Fgn5JHD1lZATSKIObPyjpXxF2aWWZuYmoBPWr/0PbPP6xxShOXvKa5p4jzUxtwkkVJxkEEkx4Fzs7FYoKfR732hGZol0ndweRs92b0550QQZIIqtSjv33lzq2r9RdEHoppyyVIigbTD6iSdJKYNY2mVgVrhdrojei+vwrdM4IzPBBs4OLOZPxnevJg52TzCliZZUANDHy2PIqa9tcyPkPkTbgjupPDRTaG46OCrdRU0mNJsloO9hjbqtcVWFLxjYKU8RcHZqrIj9e/tk33LUwsxLm6/GHeX8O0DjXHrCzDx8JP3oiNK6z/aKnZp4gdvyvtrIgOz1gfQolqjpIg== Received: from [127.0.0.1] by nm50.bullet.mail.ne1.yahoo.com with NNFMP; 22 Apr 2016 13:57:32 -0000 Received: from [98.138.101.128] by nm50.bullet.mail.ne1.yahoo.com with NNFMP; 22 Apr 2016 13:54:33 -0000 Received: from [98.139.214.32] by tm16.bullet.mail.ne1.yahoo.com with NNFMP; 22 Apr 2016 13:54:33 -0000 Received: from [98.139.212.245] by tm15.bullet.mail.bf1.yahoo.com with NNFMP; 22 Apr 2016 13:54:33 -0000 Received: from [127.0.0.1] by omp1054.mail.bf1.yahoo.com with NNFMP; 22 Apr 2016 13:54:33 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 639276.26215.bm@omp1054.mail.bf1.yahoo.com X-YMail-OSG: Fr8TIiMVM1nnGhjOmi7_TfaovxdDxH3e4_CVMvIFGYY.S2rRnFEufEvxo8HAW57 MuyxTuC3.UDNTgfLMlUpR5sCvZWRAGOxX60pzRgTypS5afsfnomqiUQ7abjzSLOvoY9nWPOHI_ej 7hj0Z8QD7eJSqSIwBxvt.qRiF6jQypmZXOVe.sosd7CiSdxH.Vtpeq1scPd4ATZxhA9XII8QiRCO .6PL.4pjJ3F0j2sRIf7zpsGU446ucGXjQHtyUutin9sv9mghgGzy6QYapqkJGZ09Z_TQnYtrluVY 87yuzAuZlZD3E0490XAGmT5IGR3qKG3WbMoMYxxo7ObEO9wmw4oaOx3is3tG0tT7U2uE8DZjF2vs VM6vrYiOKiAbOZ_YffaR7A_1zszQLHZ_Tpbl1lXXMAtIzerAZksYNQMIYf6EY3lhC2yHy85g7VzU NJPMjZLnthjRaKybFfnz3ZWiDJIdVkR1v1QxnI7rd3T5oI.MwlaMfPR3NqfpixkyWt1iSDKKhuAj 7.nOWgnDJYfpCn68aPoAc Received: by 76.13.26.138; Fri, 22 Apr 2016 13:54:33 +0000 Date: Fri, 22 Apr 2016 13:54:32 +0000 (UTC) From: Mikhail Zakharov Reply-To: Mikhail Zakharov To: Warren Block Cc: "freebsd-questions@freebsd.org" Message-ID: <1601710472.301257.1461333272851.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: References: Subject: =?UTF-8?Q?=D0=9E=D1=82=D0=B2:_FreeBSD_based_dual-cont?= =?UTF-8?Q?roller_storage_system_concept?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2016 13:59:45 -0000 I'm not sure about the EuroBSDCon, but the Journal looks like one of the go= od places to start.Thank you! --Mike =20 =D0=BF=D1=8F=D1=82=D0=BD=D0=B8=D1=86=D0=B0, 22 =D0=B0=D0=BF=D1=80=D0=B5= =D0=BB=D1=8F 2016 15:21 Warren Block =D0=BF=D0=B8=D1= =81=D0=B0=D0=BB(=D0=B0): =20 On Fri, 22 Apr 2016, Mikhail Zakharov via freebsd-questions wrote: > I=E2=80=99m testing FreeBSD as the OS for a reliable dual-controller stor= age=20 > system with ZFS, mirrored cache and etc. I have some progress on it=20 > and my notes on the model are already took 30 of A4 format pages and=20 > their number is still growing. Looks like I need to publish it somehow=20 > to show the model to the guys who may be interested. Do you know where=20 > is the best place to start? The FreeBSD Journal, possibly:=20 https://www.freebsdfoundation.org/journal/ There are also a number of conferences that are looking for papers.=C2=A0 T= oo=20 late for BSDCan this year, but EuroBSDCon is coming up in September: https://2016.eurobsdcon.org/call-for-papers/ From owner-freebsd-questions@freebsd.org Fri Apr 22 16:09:54 2016 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 9EAF2B19273 for ; Fri, 22 Apr 2016 16:09:54 +0000 (UTC) (envelope-from sathiyarajmca@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 82499174C for ; Fri, 22 Apr 2016 16:09:54 +0000 (UTC) (envelope-from sathiyarajmca@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 7DE83B19271; Fri, 22 Apr 2016 16:09:54 +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 7D8E0B1926F for ; Fri, 22 Apr 2016 16:09:54 +0000 (UTC) (envelope-from sathiyarajmca@gmail.com) Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3B4A4174B for ; Fri, 22 Apr 2016 16:09:54 +0000 (UTC) (envelope-from sathiyarajmca@gmail.com) Received: by mail-vk0-x234.google.com with SMTP id t129so142195761vkg.2 for ; Fri, 22 Apr 2016 09:09:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=G+kH9X+CPDGobTqhvdYLtiXK7UVxicR5wmAPR1h0Y58=; b=q6hpX/UK4Ej5Npe2aby8ejMiQHIWfvUDu3I5+Fk3cMRntP2uYt8VbKE/WjFuulkoos C4nMBvNLn8BqOq9MAUZfmIh5SLKPiV/+qNjkB4TADs6R4Da5hWhU8hKORJQSKIxpFhh+ ux01XJS99Au3C3IVYuFSZTNHb7MZc8IsP6UTiS640cIjBP2M5n5NvEFbiNvEFTTwfIiA A/khcNayzwqtFQwtkFSOVVuCpy9aLsIFfG25U95D5f6hyqjBqepv53Ub6jSTUj0CU2tb nE9BhU9oW/xU2J1FZKspzEZhGB+3eBSNCE2S+02IPAnqKfXErSHn5/4BrVN5svGYi9vD LxqQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=G+kH9X+CPDGobTqhvdYLtiXK7UVxicR5wmAPR1h0Y58=; b=jGc2e/p35jrpJ4cujnxzzHh9HzGYqpPzkd+HYT4mKbHliIYzjyPmoZYMbEuI+ASxXM ySymhBe+h8y4wamp144ZXfJ8HNQAbU7immMg9QttGRzzWWiqkalTlvchem3P5fo6RMJw djoitjhSiZSpepqyUK+7iNNGbwq3CGjiHVV5ImRoicOqSgiBqbFZEtIAIsxgx/r3eo8g Hzqkf3GQKX0fBvtqLCLc0HRY18Lydd/+5c2d3Uj1n+/uDbTi7/yH1ppJn4sz1RKso20t Fch45U6adX/VfzsukVcbSEyNf8GKFvaFNxrpv4R44t7M4FmcoJlqW8Juf+UFZY393rRL K4+w== X-Gm-Message-State: AOPr4FUBnmcrDE8oqwFlstmQwGKj2TuKvkLr23KDwM35kTy+PeC/U5EkR0ZKuI2T7UoQUUBPLTU9xj4t8nLJNg== MIME-Version: 1.0 X-Received: by 10.31.108.152 with SMTP id j24mr7135716vki.105.1461341393184; Fri, 22 Apr 2016 09:09:53 -0700 (PDT) Received: by 10.176.3.14 with HTTP; Fri, 22 Apr 2016 09:09:53 -0700 (PDT) Date: Fri, 22 Apr 2016 21:39:53 +0530 Message-ID: Subject: IPFW rules From: sathiyaraj v To: questions@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2016 16:09:54 -0000 Hi Team, I want to understand the IP firewall rules. Consider the below rule ipfw allow tcp/udp from any to me What this rule will do? what "me" refers here? Is it IP address of my system that apply firewall rules? or MAC address of the interface? I am using 4.2 freebsd stack. I am trying to deny the packets which doesn't contain the IP and port of my destiantion. My source IP is 171.21.47.100 My Destination IP is : 171.21.47.128 I want to deny the tcp/udp packets which does not contain destination IP? What rule should I use to deny the packets? Already I have tried to configure the flags ACCEPT ,DSTMSK, dstip and port number as well. But the packets are not getting dropped. Can you please help me to achieve the above scenario? What flag I need to set to achieve this? if you want the source code of my rule setting I can share. Thanks in advance. Sathya. From owner-freebsd-questions@freebsd.org Fri Apr 22 19:16:51 2016 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 B100DB1977E for ; Fri, 22 Apr 2016 19:16:51 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 91FE611F5 for ; Fri, 22 Apr 2016 19:16:51 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 9152EB1977D; Fri, 22 Apr 2016 19:16:51 +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 90F26B1977C for ; Fri, 22 Apr 2016 19:16:51 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 202C011F4 for ; Fri, 22 Apr 2016 19:16:51 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: by mail-wm0-x231.google.com with SMTP id n3so40965512wmn.0 for ; Fri, 22 Apr 2016 12:16:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=2O7wfgzG0tYBU7BAhUQrfZMmg8MetlncPNc6BaCtV7g=; b=Ed7+OssoFeDSfV9QOXAT8p7jPgDBD7D/5+Ar9W0OV5jAGkmULoHv621Y/dvTZxFIM6 YJKn/zmYnfcPez8zlmCvx7qDg7/oQP4GMnCfCGGS/GT/UTlFQPjSWHlhI0Xine/sGPzA lb2+x0+l9czk9z/nlrgTqo3g8KUdG+sawJ5j0dNXoi1daBiQq1RXp0YCA5iPnOkO2+e3 0YCrkFubZOR6v8qgWelnFTWi5vZdudKrQMDGLdoQ28aVUFGeUiXgmjbRXwCmF+Nfxn3H MXw1Vaapp4bdls9Rr5ai5PmAJ/uUDR3A+K0duT74wX/gARXubN2ysDZNtxDdqSrfvtka 7Zkg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=2O7wfgzG0tYBU7BAhUQrfZMmg8MetlncPNc6BaCtV7g=; b=Wm6mmd0dnia8OXtxcP0FuGeq1XO8gfldAvvetmLQ6AiycdylM+mlBiX/0z7ijYH4hy uDUDKbAfKsjMdUfvl6H+XYvJYdSxkajb1R0D6u/8+qIPSHQ/ALrgIAiGATefL4mH/1WC 0g9YJ6V78Z16aPiGkV0HU64KjWHFAOSb3udv6w3ziQ6pxqg0ytVfhVUEQRYCTG4XfP7p 8nvCqzvUGMzWYKCDi/tB/G/RGEfQS68mwicrJKYfnfEf5OxdzTHXviZmrjMPz0jb4yoi MfyM3K4BLiJXvaZxo2pj8QGNay0mM4ELTNlxtYHhob0/V9ZHXrz8Q227MPfC+mBtMdq3 L08A== X-Gm-Message-State: AOPr4FURp6ce9zsjblkvTgltsxPWuGRd8MocXmOsLq1ZNuhYRPctwwGrH8TP36eyLjJun1mmRHt3U7q1jt/Mxw== X-Received: by 10.28.236.88 with SMTP id k85mr5592831wmh.53.1461352609733; Fri, 22 Apr 2016 12:16:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.103.233 with HTTP; Fri, 22 Apr 2016 12:16:10 -0700 (PDT) In-Reply-To: References: From: Odhiambo Washington Date: Fri, 22 Apr 2016 22:16:10 +0300 Message-ID: Subject: Re: IPFW rules To: sathiyaraj v Cc: questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2016 19:16:51 -0000 On 22 April 2016 at 19:09, sathiyaraj v wrote: > Hi Team, > > I want to understand the IP firewall rules. Consider the below > rule > > ipfw allow tcp/udp from any to me > What this rule will do? what "me" refers here? Is it IP address of my > system that apply firewall rules? or MAC address of the interface? > It will allow all packets from the wild destined to your IP address. Your public IP address in this case. Assumming you do not need to protect your host from your LAN hosts. > > I am using 4.2 freebsd stack. > I don't know what that is, sorry. Is it FreeBSD 4.2 or IPFW version? > > I am trying to deny the packets which doesn't contain the IP and port of my > destiantion. > You do not have to worry about those. They will NOT reach your host if they con't contain it's IP address! > > My source IP is 171.21.47.100 > My Destination IP is : 171.21.47.128 > What does that mean? Is .128 your default gateway or another host on the same subnet you want to reach from .100? > > I want to deny the tcp/udp packets which does not contain destination IP? > Wuah! > What rule should I use to deny the packets? > ipfw deny tcp/udp from any to !171.21.47.128 > > Already I have tried to configure the flags ACCEPT ,DSTMSK, dstip and port > number as well. But the packets are not getting dropped. > Can you please help me to achieve the above scenario? What flag I need to > set to achieve this? > > if you want the source code of my rule setting I can share. > > You really must RTFM. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft." From owner-freebsd-questions@freebsd.org Fri Apr 22 19:17:12 2016 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 31101B197B9 for ; Fri, 22 Apr 2016 19:17:12 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.70.90]) by mx1.freebsd.org (Postfix) with ESMTP id EC0931293 for ; Fri, 22 Apr 2016 19:17:11 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id 86198CB8C9A; Fri, 22 Apr 2016 14:17:05 -0500 (CDT) Received: from 128.135.52.6 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Fri, 22 Apr 2016 14:17:05 -0500 (CDT) Message-ID: <29462.128.135.52.6.1461352625.squirrel@cosmo.uchicago.edu> Date: Fri, 22 Apr 2016 14:17:05 -0500 (CDT) Subject: Storage cluster advise, anybody? From: "Valeri Galtsev" To: freebsd-questions@freebsd.org 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 References: In-Reply-To: X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2016 19:17:12 -0000 Dear Experts, I would like to ask everybody: what would you advise to use as a storage cluster, or as a distributed filesystem. I made my own research of what I can do, but I hit a snag with my seemingly best choice, so I decided to stay away from it finally, and ask clever people what they would use. My requirements are: 1. I would like to have one big (say, comparable to petabyte) filesystem, accessible on more than one machine, composed of disk space leftovers on a bunch of machines having 1 gigabit per second ethernet connections 2. It can be a bit slow, as filesystem one would need for backups onto it (say, using bacula or bareos), and/or for long term storage of large datasets, portions of which can be copied over to faster storage for processing if necessary. I would be thinking in 1-2 TB of data written to it daily. 3. It would be great to have it single machine failure/reboot resilient 4. metadata machines should be redundant (or at least backup medatada host should be manually convertible into master metadata host if fatal failure to master or corruption of its data happens) What I would like to avoid/exclude: 1. Proprietary commercial solutions, as: a. I would like to stay on as minimal budget as possible b. I want to be able to predict that it will exist for long time, and I have better experience with my predictions of this sort about open source projects as opposed to proprietary ones 2. Open source solutions using portions of proprietary closed source binaries/libraries (e.g., I would like to stay away from google proprietary code/binaries/libraries/modules) 3. Kernel level modifications. I really would like to have this independent of OS as much as I can, or rather available on multiple OSes (though I do not like Java based things - just my personal experience with some of them). I have a bunch of Linux boxes and a bunch of FreeBSD boxes, and I do not want to exclude neither of them if possible. Also, the need to have custom Linux kernel specifically scares me: Linux kernels get critical updates often, and having customizations lagging behind the need of critical update is as unpleasant as rebooting the machine because of kernel update is. I'm not too scared of a "split nature" projects: proprietary projects having open source satellite. I have mixed experience with those, using open source satellite I mean. Some of them are indeed not neglected, and even though you may be missing some features commercial counterpart has, some are really great ones: they are just missing commercial support, and maybe having a bit sparse documentation, thus making you to invest more effort into making it work, which I don't mind: I can earn my sysadmin's salary here. I would say I more often had good experience with those than bad one (and I have a list of early indications of potential bad outcome, so I can more or less predict my future with this kind of projects). I really didn't mean to write this, but I figure it probably will surface once I start getting your advices, so here it is. I did my research having my requirements in mind and came up with the solution: moosefs. It is not reviewed much, no reviews with criticism at all, and not much you can ("I could" I should say) find howtos about customizations, performance tuning etc. It installs without a hitch. It runs well, until you start stress writing a lot to it in parallel, then it started performing exponentially badly for me. Here is where extensive attempts to find performance tuning documentation faces lack of success. What made my decision to never ever use it in a future was the following. I started migrating data back from moosefs to local UFS (that is FreeBSD box) filesystem using rsync command. What I observed was: source files after they have been touched by rsync changed their timestamps. As if instead of creation timestamp it is an access timestamp on moosefs. This renders rsync from moosefs useless, as you can not re-run failed rsync, and you obliterate some of metadata of the source ("creation" timestamp). I wrote e-mail to sourceforge moosefs mail list, mentioning all this and the fact that I am using open source moosefs. Next day they replied asking whether I use version 3."this" or version 3."that", as they want to know in which of them they have a bug. Whereas latest open source version they have everywhere, including sourceforge is older version: 2.0.88. Basically, my decision was made. Sorry for venting it out here, but I figured, it will happen some moment when I will get your advises. Thanks a lot for all your advises! 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 Fri Apr 22 19:38:29 2016 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 4E364B19E61 for ; Fri, 22 Apr 2016 19:38:29 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 135181CD2 for ; Fri, 22 Apr 2016 19:38:29 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-oi0-x230.google.com with SMTP id p188so143703518oih.2 for ; Fri, 22 Apr 2016 12:38:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=RS2ET7CCQTUo2gHWG3+9NlhmuTMWWREjc8qMa5b5WG0=; b=XpvIU5uNou0s6ecY13g3Su6dVD9qX8OovZhjOAREPRXc8cbW/JmKBwUw0NlJ1Aq/XX REfg3d6VqC9jh0gofc95FyzLQm5AZpOVwL/fyCFASnZ4RcUc7yVmnoL9LmZ+0Fe3uhDI BV1udhLdK5Rf4AmPo24L3UhV4d8vi7YZh4rcTlGCElJ6t/BPcSDqzNdjo8Kes9Wr5DI/ zmevuX3l9K/dl+u1inuxKh7reRHHfrcobgJf5VJFbLaWTe898eZTy4iDY+8yTZDWeIac Pku8KK8lX7CnrJH+StHi24EJY64K38tYk4GAkMhbhZdV12lkCDOpg36LABqn7p/iJ9LZ PjFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=RS2ET7CCQTUo2gHWG3+9NlhmuTMWWREjc8qMa5b5WG0=; b=SgpZbjUpVPEEsFhmcIBTWyDm3grEhebr/X/uDJlBGyLsc4py9w+ugjt8yyhEJHKLHL K+/HpzzOnjjVAASH/ZtEE2t/lFUYZeUj/nQEgY5/isezxFBcJLg++Lrmz3FEMsTpdI5S NvgOsBPEKc7Y3fVQehmIYI/LuV9pBNSF80kw4Lrxu6hucit6Wb4YkrB7sYzWaH3rRzX/ 0/6h7NrUvzf8nK1dQ0TsB+l10r8zOD16q+OxQplPjXTvGUlsZHOiBnHayvHdtSwL2YTY VuyDnHcDr6ZP6nBDOPGOuqehoU+JMev0ryAU6IqFz50lCLk9n/xZkKvwqV9fGwh+hVi7 2MEQ== X-Gm-Message-State: AOPr4FXTt5VARCKAnFQQNqi7j3RnsKy8nE1HFdEvJissOyWgBDzEP8PDxrQYKFw1gFO4QYHVfV8B3MvR2CN8Hw== MIME-Version: 1.0 X-Received: by 10.202.80.74 with SMTP id e71mr9452784oib.64.1461353908387; Fri, 22 Apr 2016 12:38:28 -0700 (PDT) Received: by 10.157.45.194 with HTTP; Fri, 22 Apr 2016 12:38:28 -0700 (PDT) In-Reply-To: <29462.128.135.52.6.1461352625.squirrel@cosmo.uchicago.edu> References: <29462.128.135.52.6.1461352625.squirrel@cosmo.uchicago.edu> Date: Fri, 22 Apr 2016 12:38:28 -0700 Message-ID: Subject: Re: Storage cluster advise, anybody? From: Mehmet Erol Sanliturk To: galtsev@kicp.uchicago.edu Cc: FreeBSD Questions Mailing List Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2016 19:38:29 -0000 On Fri, Apr 22, 2016 at 12:17 PM, Valeri Galtsev wrote: > Dear Experts, > > I would like to ask everybody: what would you advise to use as a storage > cluster, or as a distributed filesystem. > > I made my own research of what I can do, but I hit a snag with my > seemingly best choice, so I decided to stay away from it finally, and ask > clever people what they would use. > > My requirements are: > > 1. I would like to have one big (say, comparable to petabyte) filesystem, > accessible on more than one machine, composed of disk space leftovers on a > bunch of machines having 1 gigabit per second ethernet connections > > 2. It can be a bit slow, as filesystem one would need for backups onto it > (say, using bacula or bareos), and/or for long term storage of large > datasets, portions of which can be copied over to faster storage for > processing if necessary. I would be thinking in 1-2 TB of data written to > it daily. > > 3. It would be great to have it single machine failure/reboot resilient > > 4. metadata machines should be redundant (or at least backup medatada host > should be manually convertible into master metadata host if fatal failure > to master or corruption of its data happens) > > > What I would like to avoid/exclude: > > 1. Proprietary commercial solutions, as: > > a. I would like to stay on as minimal budget as possible > b. I want to be able to predict that it will exist for long time, and I > have better experience with my predictions of this sort about open source > projects as opposed to proprietary ones > > 2. Open source solutions using portions of proprietary closed source > binaries/libraries (e.g., I would like to stay away from google > proprietary code/binaries/libraries/modules) > > 3. Kernel level modifications. I really would like to have this > independent of OS as much as I can, or rather available on multiple OSes > (though I do not like Java based things - just my personal experience with > some of them). I have a bunch of Linux boxes and a bunch of FreeBSD boxes, > and I do not want to exclude neither of them if possible. Also, the need > to have custom Linux kernel specifically scares me: Linux kernels get > critical updates often, and having customizations lagging behind the need > of critical update is as unpleasant as rebooting the machine because of > kernel update is. > > I'm not too scared of a "split nature" projects: proprietary projects > having open source satellite. I have mixed experience with those, using > open source satellite I mean. Some of them are indeed not neglected, and > even though you may be missing some features commercial counterpart has, > some are really great ones: they are just missing commercial support, and > maybe having a bit sparse documentation, thus making you to invest more > effort into making it work, which I don't mind: I can earn my sysadmin's > salary here. I would say I more often had good experience with those than > bad one (and I have a list of early indications of potential bad outcome, > so I can more or less predict my future with this kind of projects). > > > I really didn't mean to write this, but I figure it probably will surface > once I start getting your advices, so here it is. I did my research having > my requirements in mind and came up with the solution: moosefs. It is not > reviewed much, no reviews with criticism at all, and not much you can ("I > could" I should say) find howtos about customizations, performance tuning > etc. It installs without a hitch. It runs well, until you start stress > writing a lot to it in parallel, then it started performing exponentially > badly for me. Here is where extensive attempts to find performance tuning > documentation faces lack of success. What made my decision to never ever > use it in a future was the following. I started migrating data back from > moosefs to local UFS (that is FreeBSD box) filesystem using rsync command. > What I observed was: source files after they have been touched by rsync > changed their timestamps. As if instead of creation timestamp it is an > access timestamp on moosefs. This renders rsync from moosefs useless, as > you can not re-run failed rsync, and you obliterate some of metadata of > the source ("creation" timestamp). I wrote e-mail to sourceforge moosefs > mail list, mentioning all this and the fact that I am using open source > moosefs. Next day they replied asking whether I use version 3."this" or > version 3."that", as they want to know in which of them they have a bug. > Whereas latest open source version they have everywhere, including > sourceforge is older version: 2.0.88. > Basically, my decision was made. Sorry for venting it out here, but I > figured, it will happen some moment when I will get your advises. > > > Thanks a lot for all your advises! > > Valeri > > ++++++++++++++++++++++++++++++++++++++++ > Valeri Galtsev > Sr System Administrator > Department of Astronomy and Astrophysics > Kavli Institute for Cosmological Physics > University of Chicago > Phone: 773-702-4247 > ++++++++++++++++++++++++++++++++++++++++ > > > > > _______________________________________________ > > > In page : http://moosefs.org/download.html there are the following lines with download links : Current release version 3.0.73-1 (GPLv2) 2016-03-04 Current release version 3.0.69-1 (GPLv2) 2016-01-12 Current release version 3.0.55-1 (GPLv2) 2015-10-21 Current release version 3.0.37-1 (GPLv2) 2015-05-15 Current release version 3.0.17-1 (GPLv2) 2015-04-21 . . . Perhaps they assumed you are using one of them . Mehmet Erol Sanliturk From owner-freebsd-questions@freebsd.org Fri Apr 22 19:42:44 2016 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 C7AFEB18124 for ; Fri, 22 Apr 2016 19:42:44 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 89A7E1FF1 for ; Fri, 22 Apr 2016 19:42:44 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-oi0-x232.google.com with SMTP id k142so126675991oib.1 for ; Fri, 22 Apr 2016 12:42:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=K/tUNAdMcDIKJqv7Yh6dmauR2/lxddTarJ/JdojyN7o=; b=mdgJxEKkatfKh8dX8YUu1SsN8SFETGZLc5QxbtXfKebq1fJNl4oLR4B97JwwHZzSW6 kPlJXq//GWH//yMIdlztO/hOfXsr6vjMR0tAhYtEJ1gj7AagLBvLSl9XFJ8BFPSR/RRv nDqcUHgPgssbZPJmhZP70qdlhUByvAChtzwNwZakAiZf8PTJqNdfWd7SGI4tMugL7kyV 3nQo69oBPAmsjB7/X2griAv2RJMwR7WeJ9HkpshPy1ugaBytrWGK7hb/KqJRMzch8lOu 9BcEiNE6AMdTpicCHc/1gjivR2RCGhI4dSgcUpzgtTJ6CfcGe5X07RmJjY5E/ek2mXld OJ1Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=K/tUNAdMcDIKJqv7Yh6dmauR2/lxddTarJ/JdojyN7o=; b=LfIy/e9eHAWLBZode82DNheiSsoiHhkeLL2VGcw/lrOaafa6MRqeujPoVIHtR8wdtB JB3IvnDuNnl4B4vUT01PCbw0apy8KtCxj9KPsu9X1AKKmrLuvbXev33Ij47O2zkm4kef X31TP5I1a7WJAiLjLC2CJ3MtH/yc3ZEg/wkj2mQmMNx2VxAaNCHvwRMdnxCa4+O6Fn1u Et8ER7G4Lwn70LS5YHT2G8GSNuUYcaroTBiDZ27KvKV9+PyLv4UTPHSHnXh6NTIL5Xjf Hyp5O8jBkbhS5sR0VFuSIDXOU1gDwhR2aTCFgONCjRNgZ2GQigwGSWdQie4hfqMudsuW hvXg== X-Gm-Message-State: AOPr4FUyvIRB62xn7zgphtF0+nFxdaT12e+d0L3udmjbJfqXtT9qWbHBjvzqPFflUN3rQiyafVB0BDVWHC9Y+w== MIME-Version: 1.0 X-Received: by 10.157.4.72 with SMTP id 66mr10223965otc.141.1461354163837; Fri, 22 Apr 2016 12:42:43 -0700 (PDT) Received: by 10.157.45.194 with HTTP; Fri, 22 Apr 2016 12:42:43 -0700 (PDT) In-Reply-To: <29462.128.135.52.6.1461352625.squirrel@cosmo.uchicago.edu> References: <29462.128.135.52.6.1461352625.squirrel@cosmo.uchicago.edu> Date: Fri, 22 Apr 2016 12:42:43 -0700 Message-ID: Subject: Re: Storage cluster advise, anybody? From: Mehmet Erol Sanliturk To: galtsev@kicp.uchicago.edu Cc: FreeBSD Questions Mailing List Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2016 19:42:44 -0000 On Fri, Apr 22, 2016 at 12:17 PM, Valeri Galtsev wrote: > Dear Experts, > > I would like to ask everybody: what would you advise to use as a storage > cluster, or as a distributed filesystem. > > I made my own research of what I can do, but I hit a snag with my > seemingly best choice, so I decided to stay away from it finally, and ask > clever people what they would use. > > My requirements are: > > 1. I would like to have one big (say, comparable to petabyte) filesystem, > accessible on more than one machine, composed of disk space leftovers on a > bunch of machines having 1 gigabit per second ethernet connections > > 2. It can be a bit slow, as filesystem one would need for backups onto it > (say, using bacula or bareos), and/or for long term storage of large > datasets, portions of which can be copied over to faster storage for > processing if necessary. I would be thinking in 1-2 TB of data written to > it daily. > > 3. It would be great to have it single machine failure/reboot resilient > > 4. metadata machines should be redundant (or at least backup medatada host > should be manually convertible into master metadata host if fatal failure > to master or corruption of its data happens) > > > What I would like to avoid/exclude: > > 1. Proprietary commercial solutions, as: > > a. I would like to stay on as minimal budget as possible > b. I want to be able to predict that it will exist for long time, and I > have better experience with my predictions of this sort about open source > projects as opposed to proprietary ones > > 2. Open source solutions using portions of proprietary closed source > binaries/libraries (e.g., I would like to stay away from google > proprietary code/binaries/libraries/modules) > > 3. Kernel level modifications. I really would like to have this > independent of OS as much as I can, or rather available on multiple OSes > (though I do not like Java based things - just my personal experience with > some of them). I have a bunch of Linux boxes and a bunch of FreeBSD boxes, > and I do not want to exclude neither of them if possible. Also, the need > to have custom Linux kernel specifically scares me: Linux kernels get > critical updates often, and having customizations lagging behind the need > of critical update is as unpleasant as rebooting the machine because of > kernel update is. > > I'm not too scared of a "split nature" projects: proprietary projects > having open source satellite. I have mixed experience with those, using > open source satellite I mean. Some of them are indeed not neglected, and > even though you may be missing some features commercial counterpart has, > some are really great ones: they are just missing commercial support, and > maybe having a bit sparse documentation, thus making you to invest more > effort into making it work, which I don't mind: I can earn my sysadmin's > salary here. I would say I more often had good experience with those than > bad one (and I have a list of early indications of potential bad outcome, > so I can more or less predict my future with this kind of projects). > > > I really didn't mean to write this, but I figure it probably will surface > once I start getting your advices, so here it is. I did my research having > my requirements in mind and came up with the solution: moosefs. It is not > reviewed much, no reviews with criticism at all, and not much you can ("I > could" I should say) find howtos about customizations, performance tuning > etc. It installs without a hitch. It runs well, until you start stress > writing a lot to it in parallel, then it started performing exponentially > badly for me. Here is where extensive attempts to find performance tuning > documentation faces lack of success. What made my decision to never ever > use it in a future was the following. I started migrating data back from > moosefs to local UFS (that is FreeBSD box) filesystem using rsync command. > What I observed was: source files after they have been touched by rsync > changed their timestamps. As if instead of creation timestamp it is an > access timestamp on moosefs. This renders rsync from moosefs useless, as > you can not re-run failed rsync, and you obliterate some of metadata of > the source ("creation" timestamp). I wrote e-mail to sourceforge moosefs > mail list, mentioning all this and the fact that I am using open source > moosefs. Next day they replied asking whether I use version 3."this" or > version 3."that", as they want to know in which of them they have a bug. > Whereas latest open source version they have everywhere, including > sourceforge is older version: 2.0.88. > Basically, my decision was made. Sorry for venting it out here, but I > figured, it will happen some moment when I will get your advises. > > > Thanks a lot for all your advises! > > Valeri > > ++++++++++++++++++++++++++++++++++++++++ > Valeri Galtsev > Sr System Administrator > Department of Astronomy and Astrophysics > Kavli Institute for Cosmological Physics > University of Chicago > Phone: 773-702-4247 > ++++++++++++++++++++++++++++++++++++++++ > > > > > _______________________________________________ > > > Another alternative may be https://www.gluster.org/ https://en.wikipedia.org/wiki/GlusterFS https://en.wikipedia.org/wiki/List_of_file_systems#Distributed_parallel_fault-tolerant_file_systems https://en.wikipedia.org/wiki/Comparison_of_distributed_file_systems Mehmet Erol Sanliturk From owner-freebsd-questions@freebsd.org Fri Apr 22 21:57:40 2016 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 CB99AB1914C for ; Fri, 22 Apr 2016 21:57:40 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.70.90]) by mx1.freebsd.org (Postfix) with ESMTP id 868A81DF3 for ; Fri, 22 Apr 2016 21:57:40 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id 02630CB8C9D; Fri, 22 Apr 2016 16:57:38 -0500 (CDT) Received: from 128.135.52.6 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Fri, 22 Apr 2016 16:57:38 -0500 (CDT) Message-ID: <52604.128.135.52.6.1461362258.squirrel@cosmo.uchicago.edu> Date: Fri, 22 Apr 2016 16:57:38 -0500 (CDT) Subject: Re: Storage cluster advise, anybody? From: "Valeri Galtsev" To: "Mehmet Erol Sanliturk" Cc: "FreeBSD Questions 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 References: <29462.128.135.52.6.1461352625.squirrel@cosmo.uchicago.edu> In-Reply-To: X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2016 21:57:40 -0000 On Fri, April 22, 2016 2:38 pm, Mehmet Erol Sanliturk wrote: > On Fri, Apr 22, 2016 at 12:17 PM, Valeri Galtsev > > wrote: > >> Dear Experts, >> I would like to ask everybody: what would you advise to use as a storage >> cluster, or as a distributed filesystem. >> >> I really didn't mean to write this, but I figure it probably will surface >> once I start getting your advices, so here it is. I did my research having >> my requirements in mind and came up with the solution: moosefs. It is not >> reviewed much, no reviews with criticism at all, and not much you can ("I >> could" I should say) find howtos about customizations, performance tuning >> etc. It installs without a hitch. It runs well, until you start stress writing a lot to it in parallel, then it started performing >> exponentially >> badly for me. Here is where extensive attempts to find performance tuning >> documentation faces lack of success. What made my decision to never ever >> use it in a future was the following. I started migrating data back from >> moosefs to local UFS (that is FreeBSD box) filesystem using rsync command. >> What I observed was: source files after they have been touched by rsync changed their timestamps. As if instead of creation timestamp it is an access timestamp on moosefs. This renders rsync from moosefs useless, as >> you can not re-run failed rsync, and you obliterate some of metadata of the source ("creation" timestamp). I wrote e-mail to sourceforge moosefs >> mail list, mentioning all this and the fact that I am using open source moosefs. Next day they replied asking whether I use version 3."this" or version 3."that", as they want to know in which of them they have a bug. >> Whereas latest open source version they have everywhere, including sourceforge is older version: 2.0.88. >> Basically, my decision was made. Sorry for venting it out here, but I figured, it will happen some moment when I will get your advises. >> Thanks a lot for all your advises! >> Valeri > In page : > http://moosefs.org/download.html > > there are the following lines with download links : > > Current release version 3.0.73-1 (GPLv2) 2016-03-04 > Current release version 3.0.69-1 (GPLv2) 2016-01-12 > Current release version 3.0.55-1 (GPLv2) 2015-10-21 > Current release version 3.0.37-1 (GPLv2) 2015-05-15 > Current release version 3.0.17-1 (GPLv2) 2015-04-21 > . > . > . > > > > Perhaps they assumed you are using one of them . Thanks for pointing that out. I see now that they are there under the name "current" as opposed to 2.0.88 "stable" - pretty much consistent with what FreeBSD terminology would be. So, 2.0.88 _is_ the latest "stable". No, I'm using "stable" on all production everything (my laptop doesn't count). And the weirdness I see is in production version (built on my machine from port I must admit). Thanks! Valeri > > > Mehmet Erol Sanliturk > ++++++++++++++++++++++++++++++++++++++++ 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 Apr 23 01:55:13 2016 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 971DDB19323 for ; Sat, 23 Apr 2016 01:55:13 +0000 (UTC) (envelope-from dpchrist@holgerdanske.com) Received: from holgerdanske.com (holgerdanske.com [184.105.128.27]) by mx1.freebsd.org (Postfix) with SMTP id 8B98D105C for ; Sat, 23 Apr 2016 01:55:13 +0000 (UTC) (envelope-from dpchrist@holgerdanske.com) Received: from ::ffff:99.100.19.101 ([99.100.19.101]) by holgerdanske.com for ; Fri, 22 Apr 2016 18:55:01 -0700 Subject: Re: Storage cluster advise, anybody? To: freebsd-questions@freebsd.org References: <29462.128.135.52.6.1461352625.squirrel@cosmo.uchicago.edu> From: David Christensen Message-ID: <571AD606.4000203@holgerdanske.com> Date: Fri, 22 Apr 2016 18:55:18 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.7.0 MIME-Version: 1.0 In-Reply-To: <29462.128.135.52.6.1461352625.squirrel@cosmo.uchicago.edu> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 01:55:13 -0000 On 04/22/2016 12:17 PM, Valeri Galtsev wrote: > I would like to ask everybody: what would you advise to use as a storage > cluster, or as a distributed filesystem. ... > My requirements are: > > 1. I would like to have one big (say, comparable to petabyte) filesystem, > accessible on more than one machine, composed of disk space leftovers on a > bunch of machines having 1 gigabit per second ethernet connections > > 2. It can be a bit slow, as filesystem one would need for backups onto it > (say, using bacula or bareos), and/or for long term storage of large > datasets, portions of which can be copied over to faster storage for > processing if necessary. I would be thinking in 1-2 TB of data written to > it daily. > > 3. It would be great to have it single machine failure/reboot resilient > > 4. metadata machines should be redundant (or at least backup medatada host > should be manually convertible into master metadata host if fatal failure > to master or corruption of its data happens) > > > What I would like to avoid/exclude: > > 1. Proprietary commercial solutions, as: > > a. I would like to stay on as minimal budget as possible > b. I want to be able to predict that it will exist for long time, and I > have better experience with my predictions of this sort about open source > projects as opposed to proprietary ones > > 2. Open source solutions using portions of proprietary closed source > binaries/libraries (e.g., I would like to stay away from google > proprietary code/binaries/libraries/modules) > > 3. Kernel level modifications. I really would like to have this > independent of OS as much as I can, or rather available on multiple OSes > (though I do not like Java based things - just my personal experience with > some of them). I have a bunch of Linux boxes and a bunch of FreeBSD boxes, > and I do not want to exclude neither of them if possible. Also, the need > to have custom Linux kernel specifically scares me: Linux kernels get > critical updates often, and having customizations lagging behind the need > of critical update is as unpleasant as rebooting the machine because of > kernel update is. > > I'm not too scared of a "split nature" projects: proprietary projects > having open source satellite. I have mixed experience with those, using > open source satellite I mean. Some of them are indeed not neglected, and > even though you may be missing some features commercial counterpart has, > some are really great ones: they are just missing commercial support, and > maybe having a bit sparse documentation, thus making you to invest more > effort into making it work, which I don't mind: I can earn my sysadmin's > salary here. I would say I more often had good experience with those than > bad one (and I have a list of early indications of potential bad outcome, > so I can more or less predict my future with this kind of projects). > > ... moosefs. ... If you want solution that works on both BSD and Linux, FUSE comes to mind: https://en.wikipedia.org/wiki/Filesystem_in_Userspace Are all the file system storage member computers located in one room? In one building? In one campus? You say "composed of disk space leftovers on a bunch of machines". How many machines? What form of leftovers -- whole disks, whole partitions, block-contiguous files, non-contiguous files? Do you need checksumming, mirroring, RAID, caching, whatever? What are your degradation expectations in the face of missing/ unresponsive member machines? Failing drives/ files? Are you going to serve the file system via NFS? Samba? Other? You indicate 1-2 TB/day of writes, expected to be backups and dataset archives. What sort of read traffic do you expect? How many connected clients? How many hitting it at the same time? Any usage spikes (say, everyone downloading files at work start, everyone uploading or backing up at quiting time)? David From owner-freebsd-questions@freebsd.org Sat Apr 23 03:34:01 2016 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 736BEB18409 for ; Sat, 23 Apr 2016 03:34:01 +0000 (UTC) (envelope-from poopneo.rr.com@gmail.com) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::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 345C81085 for ; Sat, 23 Apr 2016 03:34:01 +0000 (UTC) (envelope-from poopneo.rr.com@gmail.com) Received: by mail-io0-x22a.google.com with SMTP id f89so110834362ioi.0 for ; Fri, 22 Apr 2016 20:34:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:message-id:from:to:subject:mime-version :content-transfer-encoding; bh=pkTIweuJdK4PyUuWDGxSeTy1t57ITiyuWCLAUUwYmgs=; b=CJ5QDPXTdz2EOwK2prBYdZiyDLrCjw3tlGd7lheejStqgttxUNba0WObb1us24b8Al 60seDImjd0Gm270VemyXNlz75UQa9YxgsKjvqfY1FaUVt7jvqzOfVlsZdOZwxLkgFL36 M34r9Kp87PknSmzmWGeWNDEPShzi/yLtZ2wZwGnqCVBJcgL53xPtyFbHsWU4IvlvxCK+ 816DUlt93zbWYplH87h4xaijCYKBx2Fr2HYWL7odK1NGW8JirlDlvrnLwf9vFfEI3ePZ MCuzHWgALE2Jq20DuNopptH5WYMyabZezCHTjX/fUn1PKO5L8aQcBc6jLLyQaTK9KPvg cGcg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:message-id:from:to:subject:mime-version :content-transfer-encoding; bh=pkTIweuJdK4PyUuWDGxSeTy1t57ITiyuWCLAUUwYmgs=; b=dkTneyAFmWXn4iNv5MC8YK/bFyLiH6GHZOqEu768L71JUchXedUyXEoLIi6RKSnisb +w9yEnJElCbzJR8J0mS0O5XCCl0qwoZffW+F9RzfRiFfjgUDwkkoYlfnqiqAc7o5FICx Glp6G4JQQfLEZMT6k4fWEjSmGD510qYB6VtEmJbL60llQvBigUVaZPMNiGBjuCoRFOS0 OxasPoN/TQMPxzaYvn6S1V43PIGGWwcDlVW1aAaOFTGHDljZSAytNG5qiJEswhmS2ebP TRrEAnYQdXV7rDdT00GRsjOmDn4e8iPcZnjZi1U6d2vu9TgS+ZOO6cuw9Gku8WDju6en qYWw== X-Gm-Message-State: AOPr4FWVgaAWFr/VwwQjVOfl9NR4eHORP9Q9AEP5qfiry0ZyK2qY+LeUuZepaRYWozoZWA== X-Received: by 10.107.131.136 with SMTP id n8mr25824741ioi.132.1461382440580; Fri, 22 Apr 2016 20:34:00 -0700 (PDT) Received: from 127.0.0.1 (cpe-174-100-129-171.neo.res.rr.com. [174.100.129.171]) by smtp.gmail.com with ESMTPSA id w3sm3179950igz.18.2016.04.22.20.33.59 for (version=TLSv1/SSLv3 cipher=OTHER); Fri, 22 Apr 2016 20:33:59 -0700 (PDT) Date: Fri, 22 Apr 2016 20:33:59 -0700 (PDT) X-Google-Original-Date: Sat, 23 Apr 2016 3:34:4 +0000 Message-ID: From: "=?UTF-8?B?QXVzdGluIFdhbGtlcg==?=" To: Subject: =?UTF-8?B?SG93IHRvIHVzZSBmcmVlYnNkIGluIHNvbnkncyBQUyBWaXRh?= MIME-Version: 1.0 X-Mailer: PlayStation(R)Vita Email (3.60) Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 03:34:01 -0000 SG93IGNhbiBJIHVzZSB0aGUgcGtnIHBhY2thZ2UgaW5zdGFsbGVyIGluIHNvbnlzIHBzIHZpdGEg YW5kIGhvdw0KZG8gaSBhY2Nlc3MgaXQgcGxlYXNlIHJlcGx5IDsp From owner-freebsd-questions@freebsd.org Sat Apr 23 06:53:07 2016 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 59DCEB18D09 for ; Sat, 23 Apr 2016 06:53:07 +0000 (UTC) (envelope-from nazari.s11@gmail.com) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1.freebsd.org (Postfix) with ESMTP id 44D14126A for ; Sat, 23 Apr 2016 06:53:06 +0000 (UTC) (envelope-from nazari.s11@gmail.com) Received: from msam.nabble.com (unknown [162.253.133.85]) by mbob.nabble.com (Postfix) with ESMTP id 1B75B25F3816 for ; Fri, 22 Apr 2016 23:39:17 -0700 (PDT) Date: Fri, 22 Apr 2016 23:53:06 -0700 (MST) From: samira To: freebsd-questions@freebsd.org Message-ID: <1461394386173-6093662.post@n5.nabble.com> Subject: Whether ALTQ generates " No buffer space available " error or IPFW ? 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 06:53:07 -0000 Hi everyone, I using FreeBSD9.2 and defining a rule in ipfw that divert tcp packets on port 80 to port 8000 and by suricata will be reviewed. ipfw list: 01901 divert 8000 tcp from any to any dst-port 80 And then the packets is sent by altq to queue defined ipfw list: 03009 skipto 3011 tcp from any to any dst-port 80 03010 skipto 3012 ip from any to any 03011 allow altq http-gbeth3-out ip from any to any via gbeth3 out And we limit bandwidth in pf.conf for http traffic pf.conf: queue http-gbeth3-out bandwidth 50Kb hfsc ( upperlimit 50Kb ) When the transmission of huge amounts of http packets and pf action is to drop packets, suricata crash and the following message appears in the suricata.log file: - [ERRCODE: SC_WARN_IPFW_XMIT(84)] - Write to ipfw divert socket failed: No buffer space available Has anyone dealt with this issue? There is a similar problem: By sending ICMP packets to the queue and send ping from the interface also seen this problem and the following message is displayed: ping: sendto: No buffer space available If the specified bandwidth increased and not drop any packets, this problem does not occur. Thank you for all of your comments and help -- View this message in context: http://freebsd.1045724.n5.nabble.com/Whether-ALTQ-generates-No-buffer-space-available-error-or-IPFW-tp6093662.html Sent from the freebsd-questions mailing list archive at Nabble.com. From owner-freebsd-questions@freebsd.org Sat Apr 23 09:28:40 2016 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 566E0B1AFB9 for ; Sat, 23 Apr 2016 09:28:40 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from BLU004-OMC4S30.hotmail.com (blu004-omc4s30.hotmail.com [65.55.111.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 03D2612C7 for ; Sat, 23 Apr 2016 09:28:39 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from BLU436-SMTP217 ([65.55.111.135]) by BLU004-OMC4S30.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Sat, 23 Apr 2016 02:27:32 -0700 X-TMN: [ZgSkxNNvc8VfXMkQuMQ/jpV+h2oG/7a0] X-Originating-Email: [carmel_ny@outlook.com] Message-ID: Date: Sat, 23 Apr 2016 05:27:29 -0400 From: Carmel To: freebsd-questions@freebsd.org Subject: daily run output Organization: Seibercom NET X-Mailer: Claws Mail 3.13.2-dirty (GTK+ 2.24.28; i686-w64-mingw32) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Apr 2016 09:27:31.0775 (UTC) FILETIME=[5C9E84F0:01D19D42] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 09:28:40 -0000 The "daily run output" has been displaying this message: mailwrapper: no mapping in /usr/local/etc/mail/mailer.conf This is the mailer.conf file: # # Execute the Postfix sendmail program, named /usr/local/sbin/sendmail # sendmail /usr/local/sbin/sendmail send-mail /usr/local/sbin/sendmail mailq /usr/local/sbin/sendmail newaliases /usr/local/sbin/sendmail I a running postfix without any problems on a FreeBSD-11 machine. Is this something I should worry about? -- Carmel From owner-freebsd-questions@freebsd.org Sat Apr 23 10:30:16 2016 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 2311CB19A23 for ; Sat, 23 Apr 2016 10:30:16 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from anny.lostinspace.de (anny.lostinspace.de [195.30.95.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D78B91128 for ; Sat, 23 Apr 2016 10:30:15 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from server.idefix.lan (aftr-185-17-205-232.dynamic.mnet-online.de [185.17.205.232]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: idefix@fechner.net) by anny.lostinspace.de (Postfix) with ESMTPSA id 896833B05B4; Sat, 23 Apr 2016 12:30:05 +0200 (CEST) DMARC-Filter: OpenDMARC Filter v1.3.1 anny.lostinspace.de 896833B05B4 Authentication-Results: anny.lostinspace.de; dmarc=none header.from=fechner.net DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=fechner.net; s=default; t=1461407405; bh=BEzEOusxK1VJcGwvZtDj+9K+4PxsrXd4D91cqrQMxwI=; h=Subject:To:References:Cc:From:Date:In-Reply-To; b=qKDgy2RcUU69Y/T6Y9s9RNkTnvimjhuGX7mI/sr4AhplFk6jMnq8Rf8lJWkdQNMaK jVfKHSfiv7Z86bNbn/oN1FtZWX8KoCJ6XDIv1IG3ho+NqKn8FqQQsgTbTa7hYU/DPR gLj26Zn6wtNAzs7vxzlmAZAyvqmHish7JGapb3No= Received: from [192.168.0.151] (aftr-185-17-205-232.dynamic.mnet-online.de [185.17.205.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by server.idefix.lan (Postfix) with ESMTPSA id E7F3C272D50; Sat, 23 Apr 2016 12:30:04 +0200 (CEST) Subject: Re: Convert ipfw rule to pf To: krad References: Cc: "freebsd-questions@freebsd.org" From: Matthias Fechner Message-ID: Date: Sat, 23 Apr 2016 12:29:44 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 10:30:16 -0000 Am 18.04.2016 um 10:20 schrieb krad: > you need the relevant pass rules as well as the rdrs but if my deny all rule has a log flag and the package is blocked by this rule, it should get logged or? (all my block/drop rules have the log flag set) I cannot see that any packet is blocked (at least no packets that should match this rule, I see some other blocks). Could it be, if the application uses transparent proxy it is customized to ipfw and will not work with pf? Thanks Matthias -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook From owner-freebsd-questions@freebsd.org Sat Apr 23 11:04:22 2016 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 38EB3B1A3E2 for ; Sat, 23 Apr 2016 11:04:22 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B82E31F40 for ; Sat, 23 Apr 2016 11:04:21 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: by mail-wm0-x232.google.com with SMTP id n3so60715115wmn.0 for ; Sat, 23 Apr 2016 04:04:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=ce18jAV4DbQnCpqRUyCL8QnTMHLxIfekRi3Msh4+Zcg=; b=mdeeC7fGLbmrNZUx71/G7kEdc7WJZn2hNRE2gyWyO21+d3FNqCdNu0R6KLeaMqsvcz ouoQYS1wJfKeF4Ap+qA+LFejnxohBgGD37B4Bc9dOGlfIejK1/XBprpj935Fply8MjC1 m9pr2U8/Rh+9+TxaXHucz0eML8c6XFTa2fIOqYUpkQ/LgKApYwNperARSpvl/RYplFuR L7nUPGtPwCp7pdEdOqFMpvudTBsKwjLvJjZlTF5i/mCcd5clie+dDXcYOy418ureBxLU plRE+fCqYANhRaPsetSAppyRgLOo9+iMl9iwPweQ6qImC3wgZOGyfppo788zyFbZiDgx o/Kg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=ce18jAV4DbQnCpqRUyCL8QnTMHLxIfekRi3Msh4+Zcg=; b=GO52VRW7Zd/j5OACF6uoO+a1kGsCV0DKUsYy+peKlqO/+XKwEOjBc6HFoyHVFtctyv LYT7tvV67snmYRq5ewxTfDLbed9e3OWHrR1P9JVFzQeyS7u1MEMbHjx/dtuxxaE65yuo T+NIKWHgajQXgbj20+GwnVPClPerDw98W4VfTPVCpJ249NLav5IsrA420WRyVJP2/S6B NKkFCyPoF7q3skXoq/UVbn/ANr9S1Rif/A8/kZPNyJd5/EAikFB6Mn0a1yXsYV9J9FPM UQyB45spOvt9xQ7682kMXwvcE8WpiZkL0EnWAtJZgN1mIdPTI/eTAM7pkd5Q+to7M6n4 fWzw== X-Gm-Message-State: AOPr4FXTaYKjltGUrVB/hAlR1gWW5kbXWlO1+u01WSqtE/xwNZO6zthL0u9GPqZSWfaVCEIvjRnmQcq8qh94wA== X-Received: by 10.28.131.195 with SMTP id f186mr1970592wmd.97.1461409459509; Sat, 23 Apr 2016 04:04:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.103.233 with HTTP; Sat, 23 Apr 2016 04:03:40 -0700 (PDT) From: Odhiambo Washington Date: Sat, 23 Apr 2016 14:03:40 +0300 Message-ID: Subject: Sane way to resolve potential conflicts in the system To: User Questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 11:04:22 -0000 I quite often get the following warning: /usr/bin/ld: warning: libz.so.5, needed by /usr/local/lib/libcurl.so, may conflict with libz.so.6 /usr/bin/ld: warning: libz.so.4, needed by /usr/local/lib/libssh2.so.1, may conflict with libz.so.6 What is the best way to resolve the two? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft." From owner-freebsd-questions@freebsd.org Sat Apr 23 11:22:55 2016 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 B106BB1AAC4 for ; Sat, 23 Apr 2016 11:22:55 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3F0671A4F for ; Sat, 23 Apr 2016 11:22:54 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (liminal.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3636:3bff:fed4:b0d6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id B22D1111E5; Sat, 23 Apr 2016 11:22:44 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/B22D1111E5; dkim=none; dkim-atps=neutral Subject: Re: How to use freebsd in sony's PS Vita To: freebsd-questions@freebsd.org, poopneo.rr.com@gmail.com References: From: Matthew Seaman Message-ID: <571B5B04.7040001@FreeBSD.org> Date: Sat, 23 Apr 2016 12:22:44 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="cax3lIUSShOiv4iAxo9FrECcWspLiWHDM" X-Virus-Scanned: clamav-milter 0.99.1 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 11:22:55 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --cax3lIUSShOiv4iAxo9FrECcWspLiWHDM Content-Type: multipart/mixed; boundary="fQ0rpmkMmoD1x7nDIKN1NGPODO0noHFIu" From: Matthew Seaman To: freebsd-questions@freebsd.org, poopneo.rr.com@gmail.com Message-ID: <571B5B04.7040001@FreeBSD.org> Subject: Re: How to use freebsd in sony's PS Vita References: In-Reply-To: --fQ0rpmkMmoD1x7nDIKN1NGPODO0noHFIu Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 23/04/2016 04:33, Austin Walker wrote: > How can I use the pkg package installer in sonys ps vita and how > do i access it please reply ;) As far as I know, there is no official support for pkg-style packages in Sony's FreeBSD based devices. Neither have I heard any reports of anyone porting pkg to that platform. So if you want to use pkg to install packages there, it looks like you'ld have to do the work of porting it there yourself. Bringing up pkg on a new platform is not a trivial thing -- the first thing you'll need is a compilation environment where you can build programs that will run on the Sony device. Which means you'll need a compiler toolchain, make, perl, autoconf and probably a few other applications. Many of these are orders of magnitude more complex to deal with than just pkg. Also, even if you did have a copy of pkg that worked on a Sony device, what would you do with it? You can't just install standard FreeBSD packages there and expect them to work. Of course, once you could compile pkg for sony, then you could probably compile a whole lot of other stuff with relatively little effort. If you could bring that off, you'ld be doing very well indeed. Cheers, Matthew --fQ0rpmkMmoD1x7nDIKN1NGPODO0noHFIu-- --cax3lIUSShOiv4iAxo9FrECcWspLiWHDM Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJXG1sEXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATPM0QAILqgW77L6OffulT0Z1ekMrV R8dYcpLrbCdB2rrm5owihByT1Q5WcyuvSE8/y40BX/eCKKsBx0pAFJfNkmwNTPfw zBGdCWAKEKDyHs1Xq/jJrl0ollirLIxYrjjV4jS52rDdkaT3ivDxI0k8TvRdaUCM xAjUYTxCW+UfyLA8BsAUaNgVj6/j859/5zBPg2u/5LDldrM7tm/m8fG0f/TWYGL4 gQslY7Kz8hyuM2rWZU5iJCDP8mXyRwyhyjuZaYyTgPOSu1BdphqeeWkJ58wCa2Ww G+Nyb2PDdw86OrHb20C+Jl92REcRmIW/ckLZHjXhULps502Kpx1kSIw5WcafIVcb N79qi9UEdseYw9q4biJd9mGhaENTUnf09cQSGgapnOLa8bv5YCTITWr/Ve0/opZd bJCvsFcHWC+rfjOhoGPhedP95WxVUScfDELVawcQsJECifvmHVwxr7QJ7PQYx4XZ am8wuQC1YBCvKdc8+wTnaxeim/9hXrTjDScQS5/eFpiCm7kSkxQPb7m1cEFWDRiO R4ZQozHig9JvOf8wpLvnmPUr5P3sw5vOOmgjvnhikCDSLQOF1nh5scbQ3GLNpnJ8 bKqVqv5d2o4xmvM2cOY1Sv6OEZoiuGTRIAU4AwumibM7rqLOJdAddbNe+He74XrL CQPkIK3r+UTo+OSE22JC =cGQ+ -----END PGP SIGNATURE----- --cax3lIUSShOiv4iAxo9FrECcWspLiWHDM-- From owner-freebsd-questions@freebsd.org Sat Apr 23 11:29:15 2016 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 EAE3FB1ABBE for ; Sat, 23 Apr 2016 11:29:15 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 76EF31BAF for ; Sat, 23 Apr 2016 11:29:15 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (liminal.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3636:3bff:fed4:b0d6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 195C8111E9 for ; Sat, 23 Apr 2016 11:29:12 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/195C8111E9; dkim=none; dkim-atps=neutral Subject: Re: daily run output To: freebsd-questions@freebsd.org References: From: Matthew Seaman Message-ID: <571B5C87.4090504@FreeBSD.org> Date: Sat, 23 Apr 2016 12:29:11 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="eLJ0qbbUSa0s5jhdMf5NAT4UVVQCu0pIO" X-Virus-Scanned: clamav-milter 0.99.1 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 11:29:16 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --eLJ0qbbUSa0s5jhdMf5NAT4UVVQCu0pIO Content-Type: multipart/mixed; boundary="QkWbePQd9DXA32AScmSuS6vw2O32djv96" From: Matthew Seaman To: freebsd-questions@freebsd.org Message-ID: <571B5C87.4090504@FreeBSD.org> Subject: Re: daily run output References: In-Reply-To: --QkWbePQd9DXA32AScmSuS6vw2O32djv96 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 23/04/2016 10:27, Carmel wrote: > The "daily run output" has been displaying this message: >=20 > mailwrapper: no mapping in /usr/local/etc/mail/mailer.conf >=20 > This is the mailer.conf file: >=20 > # > # Execute the Postfix sendmail program, named /usr/local/sbin/sendmail > # > sendmail /usr/local/sbin/sendmail > send-mail /usr/local/sbin/sendmail > mailq /usr/local/sbin/sendmail > newaliases /usr/local/sbin/sendmail >=20 > I a running postfix without any problems on a FreeBSD-11 machine. Is > this something I should worry about? As I recall, this is to do with a change from ports modifying /etc/mail/mailer.conf in the base system, instead moving that file to /usr/local/sbin/mail/mailer.conf It's a new thing, and only in 11-CURRENT so far. Looks like there are still a few rough edges -- but if postfix is working for you, then I don't think this message is anything more than an annoyance. You should come to expect these sort of things if you run the bleeding edge development version of the OS. Cheers, Matthew --QkWbePQd9DXA32AScmSuS6vw2O32djv96-- --eLJ0qbbUSa0s5jhdMf5NAT4UVVQCu0pIO Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJXG1yHXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATHaUQAIm6htvVWqFYL8kEsMMMIUna +tOsHbj4ye5V1KzKa5LYXkyy+3L0uAIKmZgHeY4QiRv3TQEfZorDSKNrQ0Hn7+bO LAf9S8oZcKyxpFuR9fRF05wD7rzlu6bG84r7x0rPk5qehAWEnjG3bqHFCUc5cjNr tJhGqGtb0e+tn/gwEvar3o748qrpXWikCzSRmxWxxDK1zQhtZfrwfh2U9IRD73HM /Ecq4MZOlbScwWlCTD8lm21gYvlW+P2PCYXuFODkp7jkE74hQ9I6K9dLJajNWKe3 AwhOoMqj10EGmaFNNL32ilXbRJ6RAFVG06f3PiG/zsPZ2eoYJGofEBh+pAnJLQqS fK9KgnKx4bE14vlB7YXRn5fBSguyO5Ou850NItueQYj9YItIkpf6FaGuZCXihxVN hcHoseGzPW7DcytHWklW0kjNdozHPMLFdEYKQ1p/X5xU7/klM3ReAMKKp3fU2Vw9 3NooBz9gBmialokOJknlCuEQ+wYepbq7mfYuQhKE2dylEmpSFDlhtDsxkqqICtbT e9D4h/xwtCUb/aBdlGZOuabrbF8kGKII9XoP7Cw5OKFAH0HvT+zJBbW/O1egYpSP yA3Fj5G5tdIR5rj47I2C1rOHg183EZ3Kqw7QzCA5x3c/euEHY04JK6BzbBjwp83t G3d2flcbmorznHpQBmvm =nyL0 -----END PGP SIGNATURE----- --eLJ0qbbUSa0s5jhdMf5NAT4UVVQCu0pIO-- From owner-freebsd-questions@freebsd.org Sat Apr 23 11:35:01 2016 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 D574DB1AE06 for ; Sat, 23 Apr 2016 11:35:01 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F9291038 for ; Sat, 23 Apr 2016 11:35:01 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: by mail-wm0-x231.google.com with SMTP id u206so61216544wme.1 for ; Sat, 23 Apr 2016 04:35:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=GRvNYsQTcKU5EnPTw91AcuedOI2nMIr4JV+1J7zPPDM=; b=cxPoRBOudIjwCB4UN7s0yBWpI+TyhCskdJOspFPH1jsHDmzJ6n+sfOf5m3h3AjkSap GMLc6v0c5ZgjD5njUE9wAjItbrO4blzcCp9RyrzsQkogyG/sitfhuuvLClNV//dhvhQk ETzoatgrX4FkY4mDNtM27H+5fSNrCbY2C37gtNwgQOIk2LULkmUH0Mo8T/auIlMMQFpt iWQCv1WrCXravleLFSlK3lNWonlxrMhkOuHz7FWJj6lH6gapiQH2BKmukS7wj3n0xYAy q025jjzDKLJMr8gHTGj2aegSjzQnLtcNgEHimXcXkfyQTwC1tZ+xjLQLI77s2y5VfIEW Cg1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=GRvNYsQTcKU5EnPTw91AcuedOI2nMIr4JV+1J7zPPDM=; b=Mrp6pBbNUEaQuq1ot5mMJT9zXm6khXa+Qejrz0+33od4tg2uglYRBgKinZwOSYTIUH kSK64Z8qznAJCdb14xc3F8OupH6g/lwymf9SmssH4xOpDkxKfARy6LBPHuFzPOa+VAn1 JFr9WBBgiiXyMg/65RTx8tvjMyv5TakBsvjIsCSsSLoCfODzDHiKfOD6CMikJUELy4GX fATfNA88KQCLk3wEUoxGjuIuIASaKv5J9s6nxQRoSdQYXvJFklmNxcNs3RHQ8ZYd8AyZ 2sQrJwkFqeAsQLilYigQ36ar1u0i03hnmenh6xCeDoR/0hXRBRlMMEQWtrR4C3ny3QC6 oqcg== X-Gm-Message-State: AOPr4FXSIE1RsCUedcBJMtWQRT8RQ03WS4baDcl4gch87LlQ+XTBDiBBEbTwl/HQpPUW4+zCi0oJlR6B+qNWPw== MIME-Version: 1.0 X-Received: by 10.28.165.216 with SMTP id o207mr2092497wme.31.1461411300117; Sat, 23 Apr 2016 04:35:00 -0700 (PDT) Received: by 10.194.42.41 with HTTP; Sat, 23 Apr 2016 04:35:00 -0700 (PDT) In-Reply-To: References: Date: Sat, 23 Apr 2016 13:35:00 +0200 Message-ID: Subject: Re: Sane way to resolve potential conflicts in the system From: Ben Woods To: Odhiambo Washington Cc: User Questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 11:35:01 -0000 On 23 April 2016 at 13:03, Odhiambo Washington wrote: > I quite often get the following warning: > > /usr/bin/ld: warning: libz.so.5, needed by /usr/local/lib/libcurl.so, may > conflict with libz.so.6 > /usr/bin/ld: warning: libz.so.4, needed by /usr/local/lib/libssh2.so.1, may > conflict with libz.so.6 > > What is the best way to resolve the two? It looks like you have not been removing old libraries when updating your base system. Have you been updating from source? If so, one of the last steps you should follow (after reboot and rebuilding all packages to suit the new system), you should be using: $ cd /usr/src $ make check-old-libs $ make delete-old-libs Beware - if you haven't rebuild your packages on the new source tree, they may be linking to old base system libraries, and break if you now remove them. Rebuild all packages first. Regards, Ben From owner-freebsd-questions@freebsd.org Sat Apr 23 12:00:52 2016 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 8E2DDB19ABF for ; Sat, 23 Apr 2016 12:00:52 +0000 (UTC) (envelope-from odhiambo@gmail.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 2FBAE102D for ; Sat, 23 Apr 2016 12:00:52 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: by mail-wm0-x229.google.com with SMTP id u206so61775225wme.1 for ; Sat, 23 Apr 2016 05:00:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=6sRYDNMxKBnoBzLzq8uw23N3A7ZPUtPWSrzYLlUaCnE=; b=FxX4IQqfThKcfbF3r/zSfhccozW3mfj7fC4vNRXVdJsE0DtjY8alz9HcIJOS32lbXg Od1y5iHEAsmDKYOsXFqdVcT0hlHvop1IZH207vHftE7R5EwZE+4BD4ym3qPdC7cloN9e +Xm4uZI/R2Sv4ls/x1hKpQD3FPp3IhiqT1pSAbVR6YPmG8mHJBU/KnER6whB30EzuK4C H7lql0cG2w8GPIq9U8ok/689mA0xx45utlbIW4cpv4UbjcyJUD/YE4k5eeMBmM9WLHP/ Hdn+Jtn7oTWu9HqZomgP7bnZjZDtwRIlPG2iuxgprPVVnH8AAq6MBARkNbRCVa+YJCxR cOqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=6sRYDNMxKBnoBzLzq8uw23N3A7ZPUtPWSrzYLlUaCnE=; b=FLUF4FLMidaqXTUvbollDPIty4QzJBVPVCOV6HZt9lwmTPBnwuD4YMGFC7zpKQpjbw J6ZVEvhmhYEACQQG/JTv6EIShzcfXlQaVjmk5WK7NWUwEySXE4DWCuTiq4rew5+yZb6g 8yD7vwDGAZYOEPI6KGLxyrJLLfivbiqbOLOlgAxah9iKE4OrAAMeBW0nzSZGHuoPzwNu ijuOlx/r9JOLLYH7I5vlplaORqGBGf910VMqxnHkfu2LjI/7pQzvaIGkfOnb9++SxMvd nVlez6FKmTffqPy7mRVhlNfqLqzPueX4fQQj+hUjCg/q7Gmyea+I++fGEWY5aLM/3lgK OFZA== X-Gm-Message-State: AOPr4FVZ1cVySQo3rPOqbq/8oRb4ww5MzsldLJlupXFwRZWpqoMqTWyukNWkN5jSl47siMsCN6gvE8hoFbwL6g== X-Received: by 10.28.236.88 with SMTP id k85mr2369417wmh.53.1461412850521; Sat, 23 Apr 2016 05:00:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.103.233 with HTTP; Sat, 23 Apr 2016 05:00:10 -0700 (PDT) In-Reply-To: References: From: Odhiambo Washington Date: Sat, 23 Apr 2016 15:00:10 +0300 Message-ID: Subject: Re: Sane way to resolve potential conflicts in the system To: Ben Woods Cc: User Questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 12:00:52 -0000 On 23 April 2016 at 14:35, Ben Woods wrote: > On 23 April 2016 at 13:03, Odhiambo Washington wrote: > >> I quite often get the following warning: >> >> /usr/bin/ld: warning: libz.so.5, needed by /usr/local/lib/libcurl.so, may >> conflict with libz.so.6 >> /usr/bin/ld: warning: libz.so.4, needed by /usr/local/lib/libssh2.so.1, >> may >> conflict with libz.so.6 >> >> What is the best way to resolve the two? > > > It looks like you have not been removing old libraries when updating your > base system. Have you been updating from source? If so, one of the last > steps you should follow (after reboot and rebuilding all packages to suit > the new system), you should be using: > $ cd /usr/src > $ make check-old-libs > $ make delete-old-libs > I always do that. > > Beware - if you haven't rebuild your packages on the new source tree, they > may be linking to old base system libraries, and break if you now remove > them. Rebuild all packages first. > I believe that explains it. I should plan a portupgrade -a one of these days I suppose. However, doing that on a production server (from remote) is such a scary thing:) Is there a way to address just these two cases for now? > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft." From owner-freebsd-questions@freebsd.org Sat Apr 23 12:04:57 2016 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 0838AB19DDE for ; Sat, 23 Apr 2016 12:04:57 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 989251454 for ; Sat, 23 Apr 2016 12:04:56 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: by mail-wm0-x22e.google.com with SMTP id n3so62047804wmn.0 for ; Sat, 23 Apr 2016 05:04:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc; bh=TI5lgKg4sJK2vXKbiZh+dWQURXl1TNi0a47YgVpS010=; b=B/WuXt/WXYLtPy6F1qBvcLt6Zdn0ubuTROkzvuNfXyqFhsDfOhLOGqpGn2IYFYjK4c LMMzCoPAHKuZcInXc+AZumkQThZebU1x4lg84uHeQt5Wyvnrc0m4QFoi0cYUjQXxflEc zVf5QRscJz5jNzmhspMt6AD0a7cu0RD/HPZQ6Day8iEz5fZsYBCMVgaSZIimoR1UGy1s nuQrUiXJkG8zp1Ecyw3JLYC3whh3TJTQc8vEC4uFDMaBcPVd9Pw9Mx42bBFrKbxNOs9i yOdZ+gdHjcsRhBI2pO+A+5eL1FPUuMZaq4EthC19ddsVkt0rMxAXwfLxSz+A4SgviDoP I95g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=TI5lgKg4sJK2vXKbiZh+dWQURXl1TNi0a47YgVpS010=; b=EPzzCxsJEbH0RWr1ngMoPPnQMZv9/j9M4bVGGy1yKoCDCSa5l2jQ0SMaYehKWVOxYh y5Zj939eP+8/+C0NJlqDwyBO3TEHtlvMIBo29GHKAFmuyDpw8+YqW5fLjglttUX7ZMHd 7nUj0N3OIfHvGmoPzT8lDga5jCCDh4SokQUPUSHs8GDf7hSHVILLyVeCQw62wVn+chdt dwdWUh2DL2szodSXnBehyKY+6SczCAUlOVQLMTc+kOoINZ/PlejVLF9t4RchIM7kANBi vu/A/BIMOWse4/cTQv4kx9dPy+OWG1abPYgWQTYQAf4bv0BtaKGYRWNUPahQD765BG/g scNg== X-Gm-Message-State: AOPr4FWdOKdw5LOxYyBZylEGqyJQUwxPSrPGadIjp02oiZ1VpPqCJkZHFAfCzhmGrDuB4ocbZiL/zeu2gOYUfA== X-Received: by 10.28.131.195 with SMTP id f186mr2180718wmd.97.1461413094839; Sat, 23 Apr 2016 05:04:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.103.233 with HTTP; Sat, 23 Apr 2016 05:04:15 -0700 (PDT) From: Odhiambo Washington Date: Sat, 23 Apr 2016 15:04:15 +0300 Message-ID: Subject: About different ABI between gcc and clang To: User Questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 12:04:57 -0000 I am looking at this page: http://wiki.squid-cache.org/BuildFarm/FreeBsdInstall There is something that I don't quite understand and would appreciate the help of the experts, like Matthew:-) due to different ABI between gcc and clang, libcppunit needs to be installed twice, one with the g++ ABI and one with clang's. The default compiler for freebsd-9 is gcc; to setup the version for clang, configure it as CC=clang35 CXX=clang++35 ./configure --prefix=/usr/local/clang-abi Can someone explain that portion to me? What is the writer suggesting I do? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft." From owner-freebsd-questions@freebsd.org Sat Apr 23 12:08:19 2016 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 40A99B19F3F for ; Sat, 23 Apr 2016 12:08:19 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from BLU004-OMC4S14.hotmail.com (blu004-omc4s14.hotmail.com [65.55.111.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 006271712 for ; Sat, 23 Apr 2016 12:08:18 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from BLU436-SMTP39 ([65.55.111.136]) by BLU004-OMC4S14.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Sat, 23 Apr 2016 05:07:12 -0700 X-TMN: [ZYHPXJblsu0uKtRsRLh+bNhvetLRWcql] X-Originating-Email: [carmel_ny@outlook.com] Message-ID: Date: Sat, 23 Apr 2016 08:07:09 -0400 From: Carmel To: freebsd-questions@freebsd.org Subject: Re: daily run output In-Reply-To: <571B5C87.4090504@FreeBSD.org> References: <571B5C87.4090504@FreeBSD.org> Organization: Seibercom NET X-Mailer: Claws Mail 3.13.2-dirty (GTK+ 2.24.28; i686-w64-mingw32) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Apr 2016 12:07:11.0604 (UTC) FILETIME=[AAA46B40:01D19D58] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 12:08:19 -0000 On Sat, 23 Apr 2016 12:29:11 +0100, Matthew Seaman stated: >On 23/04/2016 10:27, Carmel wrote: >> The "daily run output" has been displaying this message: >> >> mailwrapper: no mapping in /usr/local/etc/mail/mailer.conf >> >> This is the mailer.conf file: >> >> # >> # Execute the Postfix sendmail program, >> named /usr/local/sbin/sendmail # >> sendmail /usr/local/sbin/sendmail >> send-mail /usr/local/sbin/sendmail >> mailq /usr/local/sbin/sendmail >> newaliases /usr/local/sbin/sendmail >> >> I a running postfix without any problems on a FreeBSD-11 machine. Is >> this something I should worry about? > >As I recall, this is to do with a change from ports modifying >/etc/mail/mailer.conf in the base system, instead moving that file to >/usr/local/sbin/mail/mailer.conf It's a new thing, and only in >11-CURRENT so far. Looks like there are still a few rough edges -- but >if postfix is working for you, then I don't think this message is >anything more than an annoyance. You should come to expect these sort >of things if you run the bleeding edge development version of the OS. Okay, let me see if I am following you correctly. This is the "/etc/mail/mailer.conf" file: # $FreeBSD: head/etc/mail/mailer.conf 93858 2002-04-05 04:25:14Z gshapiro $ # # Execute the "real" sendmail program, named /usr/libexec/sendmail/sendmail # sendmail /usr/libexec/sendmail/sendmail send-mail /usr/libexec/sendmail/sendmail mailq /usr/libexec/sendmail/sendmail newaliases /usr/libexec/sendmail/sendmail hoststat /usr/libexec/sendmail/sendmail purgestat /usr/libexec/sendmail/sendmail And this is the "/usr/local/etc/mail/mailer.conf" file: # # Execute the Postfix sendmail program, named /usr/local/sbin/sendmail # sendmail /usr/local/sbin/sendmail send-mail /usr/local/sbin/sendmail mailq /usr/local/sbin/sendmail newaliases /usr/local/sbin/sendmail So, it is obvious that the port modified the "/usr/local/etc/mail/mailer.conf" file. Are you impling that I should replace the "/etc/mail/mailer.conf" file with the "/usr/local/etc/mail/mailer.conf" file? -- Carmel From owner-freebsd-questions@freebsd.org Sat Apr 23 12:14:24 2016 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 1374DB1A144 for ; Sat, 23 Apr 2016 12:14:24 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::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 A28AF1AB7; Sat, 23 Apr 2016 12:14:23 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: by mail-wm0-x22a.google.com with SMTP id e201so42202448wme.0; Sat, 23 Apr 2016 05:14:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=F8hbkE+JmfJdaXHFykAX+ETrSCs/Zlnaao1/+OKIWmU=; b=JDiPWg/G3fUIYPRLDmCo9INZucm3QapPNqca+Saco5IIc8Hv/FLXtf6JJCTP4V50Qm voR8T64BKeqY+e+D27ErWeT9xnzgN6sKatw2XhvbTUA6adKmTaojqAASGQnQsp2li22+ sjNt4pllAIa8EYFOfH4WFCDndosJzpw1oLptZgm+AT8V8e2tW2gGpBkvLkCu/2PrutN5 nWwprkm5o39I0WRP2bzCinbuXXTJCfty3BaxYcmLygupHUhMIv3flfunSmaDL2dnOgED IrIkv1HYJ7mOciE/r2yXO9WjNhhmoh5OJ6Ddkmj2RWaj4FHtbtY7ajR1IUXq6d0T7SVN NbyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=F8hbkE+JmfJdaXHFykAX+ETrSCs/Zlnaao1/+OKIWmU=; b=l2oFDL4xTpInhiY0obXV1zeRu70VFMGLse+e2P5gT/H56uf2KdDBEb6gnNUAOsNAuF uZ2bWBraaAErEzbTWeE0gJAFek/noS1ojdkMeoPjqVlEpy3TTrD5NefUBdxTjN4EKxhr +iBAyUomsi5JBIix5z1bdLnbr2s5c4jyPOJ/ElOYfih9uq5vOObJOlXU4SzBb3pqnrMG zXSGIYZtgDOfJP8cg1wZPO3cvcbEO5McUWSX9Wiccu29ULowAAJFGMUaeROXYmFN03Q/ n45PoRKd5hIxPlCrpnvByb2ahbzsac3m36ksPu5hgPn5K9yf8asWwUx6PUP2cocUcBVu ShQQ== X-Gm-Message-State: AOPr4FXbKAoABJkGhS3bZ6UeAb2f4PCLwG3AMeTaC59zHTKlpyQA6kVW8xU1OJCvfmubWRlJ4n/0OoJXzcsx3w== X-Received: by 10.194.87.103 with SMTP id w7mr25081898wjz.13.1461413662164; Sat, 23 Apr 2016 05:14:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.103.233 with HTTP; Sat, 23 Apr 2016 05:13:42 -0700 (PDT) In-Reply-To: <571B5C87.4090504@FreeBSD.org> References: <571B5C87.4090504@FreeBSD.org> From: Odhiambo Washington Date: Sat, 23 Apr 2016 15:13:42 +0300 Message-ID: Subject: Re: daily run output To: Matthew Seaman Cc: User Questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 12:14:24 -0000 On 23 April 2016 at 14:29, Matthew Seaman wrote: > On 23/04/2016 10:27, Carmel wrote: > > The "daily run output" has been displaying this message: > > > > mailwrapper: no mapping in /usr/local/etc/mail/mailer.conf > > > > This is the mailer.conf file: > > > > # > > # Execute the Postfix sendmail program, named /usr/local/sbin/sendmail > > # > > sendmail /usr/local/sbin/sendmail > > send-mail /usr/local/sbin/sendmail > > mailq /usr/local/sbin/sendmail > > newaliases /usr/local/sbin/sendmail > > > > I a running postfix without any problems on a FreeBSD-11 machine. Is > > this something I should worry about? > > As I recall, this is to do with a change from ports modifying > /etc/mail/mailer.conf in the base system, instead moving that file to > /usr/local/sbin/mail/mailer.conf It's a new thing, and only in > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ You mean /usr/local/etc/mail/mailer.conf?? > 11-CURRENT so far. Looks like there are still a few rough edges -- but > if postfix is working for you, then I don't think this message is > anything more than an annoyance. You should come to expect these sort > of things if you run the bleeding edge development version of the OS. At leaset I am now aware that I will not be looking at /etc/mail/mailer.conf in FreeBSD-11. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft." From owner-freebsd-questions@freebsd.org Sat Apr 23 12:19:52 2016 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 04EACB1A274 for ; Sat, 23 Apr 2016 12:19:52 +0000 (UTC) (envelope-from bourne.identity@hotmail.com) Received: from BLU004-OMC1S14.hotmail.com (blu004-omc1s14.hotmail.com [65.55.116.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B522A1BF9 for ; Sat, 23 Apr 2016 12:19:51 +0000 (UTC) (envelope-from bourne.identity@hotmail.com) Received: from BLU437-SMTP97 ([65.55.116.9]) by BLU004-OMC1S14.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Sat, 23 Apr 2016 05:18:43 -0700 X-TMN: [yusXY2f1xCS6/R09jTe6atJ8T8nlpuss] X-Originating-Email: [bourne.identity@hotmail.com] Message-ID: Subject: Re: Does HP DeskJet 1112 work with lpd on FreeBSD 10.2 amd64 ? To: Tijl Coosemans References: <20160420112203.3244f4ea@kalimero.tijl.coosemans.org> CC: freebsd-questions@freebsd.org, guru@unixarea.de From: Manish Jain Date: Sat, 23 Apr 2016 17:47:33 +0530 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <20160420112203.3244f4ea@kalimero.tijl.coosemans.org> X-OriginalArrivalTime: 23 Apr 2016 12:18:41.0599 (UTC) FILETIME=[45E94CF0:01D19D5A] Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 12:19:52 -0000 On 04/20/16 14:52, Tijl Coosemans wrote: > On Tue, 19 Apr 2016 18:42:01 +0530 Manish Jain wrote: >> << >> CUPS works nice for many years on my FreeBSD systems, actually CURRENT. >> Why you can't get it to do anything on your system? matthias >> >> >> >> Thanks for responding. So my question becomes "Has anyne got HP DeskJet >> 1112 to work with CUPS on a FreeBSD 10.2 amd64 box ?" > You need to install print/hplip. Then you can either use the graphical > setup tool HP Device Manager, or the CUPS web interface at > http://localhost:631/. If you use the CUPS interface you need to select > the printer model at some point. Your printer will be listed as > "HP Deskjet 1110 Series, hpcups 3.16.2". > > Hi Tijl/Others, Thanks for replying. This is what I get when I try to open up the cups web interface in my browser even after installing apache24 : > Chromium's connection attempt to*localhost*was rejected What could I be missing here ? hplip package was installed, along with all its dependencies. This is what I get in dmesg : ulpt0: on usbus2 ulpt0: using bi-directional mode So the printer is being detected, just as you stated. A little bit more help, and I could fire up my printout page. Perhaps something to do with httpd.conf ? Or perhaps /usr/local/etc/cups/cupsd.conf ? Thanks again & Regards Manish Jain From owner-freebsd-questions@freebsd.org Sat Apr 23 12:31:19 2016 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 28D85B1A74E for ; Sat, 23 Apr 2016 12:31:19 +0000 (UTC) (envelope-from tijl@coosemans.org) Received: from mailrelay112.isp.belgacom.be (mailrelay112.isp.belgacom.be [195.238.20.139]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (Client CN "relay.skynet.be", Issuer "GlobalSign Organization Validation CA - SHA256 - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5B5FB1248 for ; Sat, 23 Apr 2016 12:31:16 +0000 (UTC) (envelope-from tijl@coosemans.org) X-Belgacom-Dynamic: yes X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2CRCAAoahtX/4pJsVtVCYM4U32pJYUDi10BDYF1hg4CgSE5FAEBAQEBAQFlJ0EBAQEBAQEBBwICg28BAQQ6HCMQCw4KCSUPKh4GE4gVAxa/JAEBAQEBAQQBAQEBARuCIIhMgkGBVRGFbgEEh36HB4hZMYwfgWtvjiuHUIdfHgEBQoNtOjCBJ4MZEIIgggsBAQE Received: from 138.73-177-91.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([91.177.73.138]) by relay.skynet.be with ESMTP; 23 Apr 2016 14:30:02 +0200 Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org [127.0.0.1]) by kalimero.tijl.coosemans.org (8.15.2/8.15.2) with ESMTP id u3NCU0mi002360; Sat, 23 Apr 2016 14:30:01 +0200 (CEST) (envelope-from tijl@coosemans.org) Date: Sat, 23 Apr 2016 14:29:59 +0200 From: Tijl Coosemans To: Manish Jain Cc: freebsd-questions@freebsd.org, guru@unixarea.de Subject: Re: Does HP DeskJet 1112 work with lpd on FreeBSD 10.2 amd64 ? Message-ID: <20160423142959.2d0093a4@kalimero.tijl.coosemans.org> In-Reply-To: References: <20160420112203.3244f4ea@kalimero.tijl.coosemans.org> 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 12:31:19 -0000 On Sat, 23 Apr 2016 17:47:33 +0530 Manish Jain wrote: > On 04/20/16 14:52, Tijl Coosemans wrote: >> On Tue, 19 Apr 2016 18:42:01 +0530 Manish Jain wrote: >>>> CUPS works nice for many years on my FreeBSD systems, actually CURRENT. >>>> Why you can't get it to do anything on your system? matthias >>> >>> Thanks for responding. So my question becomes "Has anyne got HP DeskJet >>> 1112 to work with CUPS on a FreeBSD 10.2 amd64 box ?" >> You need to install print/hplip. Then you can either use the graphical >> setup tool HP Device Manager, or the CUPS web interface at >> http://localhost:631/. If you use the CUPS interface you need to select >> the printer model at some point. Your printer will be listed as >> "HP Deskjet 1110 Series, hpcups 3.16.2". > > This is what I get when I try to open up the cups web interface in my > browser even after installing apache24 : > >> Chromium's connection attempt to*localhost*was rejected > > What could I be missing here ? hplip package was installed, along with > all its dependencies. > > This is what I get in dmesg : > > ulpt0: on usbus2 > ulpt0: using bi-directional mode > > So the printer is being detected, just as you stated. A little bit more > help, and I could fire up my printout page. Perhaps something to do with > httpd.conf ? Or perhaps /usr/local/etc/cups/cupsd.conf ? Is the CUPS daemon actually running? Add cupsd_enable="YES" to /etc/rc.conf and run 'service cupsd start'. Also, CUPS uses its own http server so you don't need Apache. From owner-freebsd-questions@freebsd.org Sat Apr 23 13:20:32 2016 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 976FCB120D4 for ; Sat, 23 Apr 2016 13:20:32 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 266951A6E for ; Sat, 23 Apr 2016 13:20:32 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (liminal.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3636:3bff:fed4:b0d6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 556C9DF31; Sat, 23 Apr 2016 13:20:26 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/556C9DF31; dkim=none; dkim-atps=neutral Subject: Re: About different ABI between gcc and clang To: Odhiambo Washington , User Questions References: From: Matthew Seaman Message-ID: <571B7694.5050006@FreeBSD.org> Date: Sat, 23 Apr 2016 14:20:20 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="X8vnPAcJvxC50dguboAwuUDDfiFojx0Jg" X-Virus-Scanned: clamav-milter 0.99.1 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 13:20:32 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --X8vnPAcJvxC50dguboAwuUDDfiFojx0Jg Content-Type: multipart/mixed; boundary="kgERqdphWMD7j0uiiKC147L1OX0dU9Qkf" From: Matthew Seaman To: Odhiambo Washington , User Questions Message-ID: <571B7694.5050006@FreeBSD.org> Subject: Re: About different ABI between gcc and clang References: In-Reply-To: --kgERqdphWMD7j0uiiKC147L1OX0dU9Qkf Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 23/04/2016 13:04, Odhiambo Washington wrote: > I am looking at this page: > http://wiki.squid-cache.org/BuildFarm/FreeBsdInstall >=20 > There is something that I don't quite understand and would appreciate t= he > help of the experts, like Matthew:-) >=20 > > due to different ABI between gcc and clang, libcppunit needs to be > installed twice, one with the g++ ABI and one with clang's. The default= > compiler for freebsd-9 is gcc; to setup the version for clang, configur= e it > as CC=3Dclang35 CXX=3Dclang++35 ./configure --prefix=3D/usr/local/clan= g-abi > >=20 > Can someone explain that portion to me? What is the writer suggesting I= do? Well, I claim no particular expertise with compiler toolchains. However, yes, the page is right to state that the base system compiler on 9.x cannot deal with the C++11 standard for C++ code. You need to use an external toolchain for that. There are a number of C compilers available from ports which would do the job but primarily the choice is between one of the gcc versions or one of the llvm (ie. clang) versions. You don't need to install both. In fact, you're better off picking one and sticking with it, because if you compile some of libraries squid depends on with one, and some with the other, you can run into problems. (Note: this only applies to C++ code: plain C code can mix use of either compiler quite happily.) The problem is that the runtime support for C++ programs is supplied as a shared library, and the versions of that library that come with gcc are incompatible with the ones that come with the llvm suite. Plain C uses a staticly linked library, so the whole question doesn't arise. If this seems like a lot of faff to you, then just build squid from ports, where people have made available to you the fruit of their efforts in sorting out just these sort of questions. Cheers, Matthew --kgERqdphWMD7j0uiiKC147L1OX0dU9Qkf-- --X8vnPAcJvxC50dguboAwuUDDfiFojx0Jg Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJXG3aaXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATXcIP/1kDkPolJOsUkuhlwCTvts3m BlxJTHpUDU9naWn7GddSN2w5q5psRj1ST84H3mz8kFbmHcsyZXSmv7gsTy14QJFU 2ZcAbEBLr+RVIcLUbM/xjhNJ4CVxvikaaAOnQiYmzDERv5LpdWlGnS8tXHzKMn50 jVp/SzU+/kuO1/ZGTDdjloH8xeVhuSjbLdhisd77IaaYfAHOUVhKMBzr3b1o5SBh f0RoZovWUM9l8VSY1FC8NZ/LiX0UaExLnaXkle0CljauAeerMzAdvdEexV+GjdJb 8YI1A6iVcIWxOZcAMTZUXVrCsJqqH7r4tMTJbuJR7g4Buom5EwVq3u468QE2vN0e UBWjZqYzkWeygKspTdWQV3Is7+Hqv29C41fk0qqZX3yhWEeRQkipefymPe4DOqyc abOHjHN2nU+rbfjDxvcX8dC0dWvykUHm7uVKvje4h9TC6e/hbG1hnb3K9i1j8cKN NEEYVyX30i489t4aiMBvaz71r6P60e+SbRplDHPeNKKIxu+N6yoqGOnSv5AT1kfp A4FB1KdMM+z08trKYRdInmnpmfcAiotJdzyrI4cAxVNv+daIW+IUsnyr5Ucfo4Wb gthRaHve8/cmL+TS9Rk5RnEuCeZcq/nscwBZOaTWWMdD5iazvXwyrd0v8MBPcLO5 z9aq7zcso3P8NX+hoFPW =2chX -----END PGP SIGNATURE----- --X8vnPAcJvxC50dguboAwuUDDfiFojx0Jg-- From owner-freebsd-questions@freebsd.org Sat Apr 23 13:22:15 2016 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 03FDEB12266 for ; Sat, 23 Apr 2016 13:22:15 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9F5261C96 for ; Sat, 23 Apr 2016 13:22:14 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (liminal.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3636:3bff:fed4:b0d6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id B843FDF35 for ; Sat, 23 Apr 2016 13:22:11 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/B843FDF35; dkim=none; dkim-atps=neutral Subject: Re: daily run output To: freebsd-questions@freebsd.org References: <571B5C87.4090504@FreeBSD.org> From: Matthew Seaman Message-ID: <571B7703.4000903@FreeBSD.org> Date: Sat, 23 Apr 2016 14:22:11 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="CJdV2sBmaVPMaHOsE1HnHQGn6qv4G60dW" X-Virus-Scanned: clamav-milter 0.99.1 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 13:22:15 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --CJdV2sBmaVPMaHOsE1HnHQGn6qv4G60dW Content-Type: multipart/mixed; boundary="D58qckTmIKDkVwsukR289C7iE38fnBXj5" From: Matthew Seaman To: freebsd-questions@freebsd.org Message-ID: <571B7703.4000903@FreeBSD.org> Subject: Re: daily run output References: <571B5C87.4090504@FreeBSD.org> In-Reply-To: --D58qckTmIKDkVwsukR289C7iE38fnBXj5 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 23/04/2016 13:07, Carmel wrote: > On Sat, 23 Apr 2016 12:29:11 +0100, Matthew Seaman stated: >=20 >> On 23/04/2016 10:27, Carmel wrote: >>> The "daily run output" has been displaying this message: >>> >>> mailwrapper: no mapping in /usr/local/etc/mail/mailer.conf >>> >>> This is the mailer.conf file: >>> >>> # >>> # Execute the Postfix sendmail program, >>> named /usr/local/sbin/sendmail # >>> sendmail /usr/local/sbin/sendmail >>> send-mail /usr/local/sbin/sendmail >>> mailq /usr/local/sbin/sendmail >>> newaliases /usr/local/sbin/sendmail >>> >>> I a running postfix without any problems on a FreeBSD-11 machine. Is >>> this something I should worry about? =20 >> >> As I recall, this is to do with a change from ports modifying >> /etc/mail/mailer.conf in the base system, instead moving that file to= >> /usr/local/sbin/mail/mailer.conf It's a new thing, and only in >> 11-CURRENT so far. Looks like there are still a few rough edges -- bu= t >> if postfix is working for you, then I don't think this message is >> anything more than an annoyance. You should come to expect these sort= >> of things if you run the bleeding edge development version of the OS. >=20 > Okay, let me see if I am following you correctly. >=20 > This is the "/etc/mail/mailer.conf" file: >=20 > # $FreeBSD: head/etc/mail/mailer.conf 93858 2002-04-05 04:25:14Z > gshapiro $ # > # Execute the "real" sendmail program, > named /usr/libexec/sendmail/sendmail # > sendmail /usr/libexec/sendmail/sendmail > send-mail /usr/libexec/sendmail/sendmail > mailq /usr/libexec/sendmail/sendmail > newaliases /usr/libexec/sendmail/sendmail > hoststat /usr/libexec/sendmail/sendmail > purgestat /usr/libexec/sendmail/sendmail >=20 > And this is the "/usr/local/etc/mail/mailer.conf" file: > # > # Execute the Postfix sendmail program, named /usr/local/sbin/sendmail > # > sendmail /usr/local/sbin/sendmail > send-mail /usr/local/sbin/sendmail > mailq /usr/local/sbin/sendmail > newaliases /usr/local/sbin/sendmail >=20 > So, it is obvious that the port modified the > "/usr/local/etc/mail/mailer.conf" file. Are you impling that I should > replace the "/etc/mail/mailer.conf" file with the > "/usr/local/etc/mail/mailer.conf" file? >=20 No. You can do what you like with the mailer.conf files, but you don't *need* to do anything. All I am stating is that you can ignore the warning message. Matthew --D58qckTmIKDkVwsukR289C7iE38fnBXj5-- --CJdV2sBmaVPMaHOsE1HnHQGn6qv4G60dW Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJXG3cDXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATrrQQAIVU7ttAFOMYRamp0UoypRZQ okA5EpY78lP/80GO2JNfBHhVy62WC76nq8kAQWKSWU6UrIKhsOiPqijRTrKqTosO FqZXSx1uI4bEj1y0WaA8y1CJKGXOB33w9I8U5GXVxRx6xmC+FXsiKdouFjE5DmDt f7DXtJcEcUU2GFBJuIX/yatcgrp4vdUNjjtk4AvaweAHREySL5UQpvsWmcZm/VPJ q0Lcmnav8viWT9cZWNdlKdpdIKrCO2kOSU86TtvwVZzYDcAyKdgzo8mPeZom1A+u SDTLsEJlR5YuPvJIZaKXh+4+lhLHHU/0AZO87S2thzeunPiBZvQQw3wxfkHj7iLz h/GXSxEQvHoCYuk6yS/I4+MEIMA2FcYftjCqujCgjnFTPn8Ba4Vzz3UUsKiPvOMP 5f14B4qPQaJVpubF+EaYZuVuhPBuxrP9Lv9f8G3by/NKUOQpUTJntD3cntO38KKv VG0X8iflhXZnVNLpg0T0R3w12DPorjrTRCJJw7B2G287Inb/Dlj0W2fvl+zxsLhP F1ucArI2IzN5HzOz7zdu8X5GPxCZn76RjI5cLEeP5ADaL2QKL4nzRTGQJJ6RAFWA RCvj6ZYqhcgGFHLldskELqlv/HTtEJAZqBOCs3GnwOiVKC319havV7QJS4qvySD7 1p3k02w46+L1Gpy31gyQ =pzI/ -----END PGP SIGNATURE----- --CJdV2sBmaVPMaHOsE1HnHQGn6qv4G60dW-- From owner-freebsd-questions@freebsd.org Sat Apr 23 13:59:58 2016 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 68603B12CF2 for ; Sat, 23 Apr 2016 13:59:58 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::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 ECF7F115D; Sat, 23 Apr 2016 13:59:57 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: by mail-wm0-x233.google.com with SMTP id e201so43771417wme.0; Sat, 23 Apr 2016 06:59:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1zJf5cPAicpV1pSHlRoLzSM4D3DTiJZdJXcV3+ORXU8=; b=b4os0adW0Bh3zJg+OlKrcsTQkHwajel6BvyT98+aCwTJ3JhQgZGcSzEDaIXLUj3rs6 5kz6DZQXxUSPOq4vxWUhRkmrWyRQ9nxXkY8Fv87l84MzVj411bHUUr9ALJb1bc88k/7J EDV7JK8J7Xqd+kL8q9HYBuDRJBG5cOgPVSIf/sE06N5UhlAcK+uCxOlffLNQrveuH8ch PIEiCKtT8LsTnARQ4QllbDFe681uZAmQZLNLxIl0cMq/UEFfZbgY++LCe/yhLQH3vjDG 7zsoD3i9ClXDycGIynhbgQPyj1cXnG9IVufnUFuF30vANnMZFaIrUB210+80WxWdcwb9 xqkA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=1zJf5cPAicpV1pSHlRoLzSM4D3DTiJZdJXcV3+ORXU8=; b=AF3KQJ5PeKYYkhkgeZNXSrNwlUs2IMiMludGFMxcFlHx4o3ElluE3/CFvm+Hk9wuzG hXASkCx2CW/nBF1rPrs7oQkUHTjisT10smLM26dXEX+p+Dn6SGEqGxre+eaD8v7r8bnK HYi7Kg64pDza5XNG9wMQS0cc3hnSjpzGkDAbZdQY47Zo75QfG0EkbigJonSVDa/omjZx TTVDMOCQwoMxryygeR5Ntel8NnBKRlJ7olv4kiORj68sp5g+ptbKvTuGDK9vlZ41N1PY 6XNfOaxg6b31b87fPtx/fgyvVIT2Jbil0BJdu2zQAZDNz/Cdl1gtagOBpuKJysoxUyU3 x5/Q== X-Gm-Message-State: AOPr4FVU0AvkUOZnw+ApeTK+cr8Kq8PgKQFsnhEaowzkGKHvi+REn6keUFjRRRVU8/eISHDZxnOoGzNttOy9mw== X-Received: by 10.28.73.66 with SMTP id w63mr2835372wma.53.1461419996555; Sat, 23 Apr 2016 06:59:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.103.233 with HTTP; Sat, 23 Apr 2016 06:59:16 -0700 (PDT) In-Reply-To: <571B7694.5050006@FreeBSD.org> References: <571B7694.5050006@FreeBSD.org> From: Odhiambo Washington Date: Sat, 23 Apr 2016 16:59:16 +0300 Message-ID: Subject: Re: About different ABI between gcc and clang To: Matthew Seaman Cc: User Questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 13:59:58 -0000 On 23 April 2016 at 16:20, Matthew Seaman wrote: > On 23/04/2016 13:04, Odhiambo Washington wrote: > > I am looking at this page: > > http://wiki.squid-cache.org/BuildFarm/FreeBsdInstall > > > > There is something that I don't quite understand and would appreciate the > > help of the experts, like Matthew:-) > > > > > > due to different ABI between gcc and clang, libcppunit needs to be > > installed twice, one with the g++ ABI and one with clang's. The default > > compiler for freebsd-9 is gcc; to setup the version for clang, configure > it > > as CC=clang35 CXX=clang++35 ./configure --prefix=/usr/local/clang-abi > > > > > > Can someone explain that portion to me? What is the writer suggesting I > do? > > Well, I claim no particular expertise with compiler toolchains. > > However, yes, the page is right to state that the base system compiler > on 9.x cannot deal with the C++11 standard for C++ code. You need to > use an external toolchain for that. There are a number of C compilers > available from ports which would do the job but primarily the choice is > between one of the gcc versions or one of the llvm (ie. clang) versions. > > You don't need to install both. In fact, you're better off picking one > and sticking with it, because if you compile some of libraries squid > depends on with one, and some with the other, you can run into problems. > (Note: this only applies to C++ code: plain C code can mix use of either > compiler quite happily.) > > The problem is that the runtime support for C++ programs is supplied as > a shared library, and the versions of that library that come with gcc > are incompatible with the ones that come with the llvm suite. Plain C > uses a staticly linked library, so the whole question doesn't arise. > > If this seems like a lot of faff to you, then just build squid from > ports, where people have made available to you the fruit of their > efforts in sorting out just these sort of questions. > > Cheers, > > Matthew > > Hello Matthew, Thank you for taking time off your weekend to answer this. I however need to 'do something' as suggested in the page, but which one is it? On my box, I have: root@gw:/usr/home/wash # `which clang` --version FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 Target: i386-unknown-freebsd9.3 Thread model: posix root@gw:/usr/home/wash # clang --version FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 Target: i386-unknown-freebsd9.3 Thread model: posix root@gw:/usr/home/wash # gcc --version gcc (GCC) 4.2.1 20070831 patched [FreeBSD] Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. root@gw:/usr/home/wash # which gcc /usr/bin/gcc root@gw:/usr/home/wash # /usr/bin/gcc --version gcc (GCC) 4.2.1 20070831 patched [FreeBSD] Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Any suggestion on what I should do? I am trying to compile squid-4.0.9 which isn't in the ports. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft." From owner-freebsd-questions@freebsd.org Sat Apr 23 14:02:11 2016 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 67C71B12EA0 for ; Sat, 23 Apr 2016 14:02:11 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003: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 2F0C513F0; Sat, 23 Apr 2016 14:02:11 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-oi0-x233.google.com with SMTP id k142so140915409oib.1; Sat, 23 Apr 2016 07:02:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=f2zRTlA8MREn7UtcRWtsmL1DFezf9Qyj3m2Vn17BrFY=; b=wcAVLf5dbqFZhRaEPiiHECRSEiNfcUfo/pf1go5kY52u26UKzDOQIDNDhJSUrNAZZp /AcWcR6RU4c31fSLC5OL0mWXuQ83ZcvCjt9dkY4xBuQ7hhFFZ7JKKZxnqQTXcgQx4f1a lHDV7as6lsPRlb8hkDz2KF3MWDltiXVLivLJnkc150sYl8eUwdH0w/aMIs2LGAtdeDHE E+utN2uXQbYkiheqD/zn220lgB5e7gAMUd0Ke5JdpZWyzLUWWjl5RPSYsl3Hbzd7M40i Fhf7mOJaFaT++tDQVc5FXcq8nkVJgbONSupDwX4hczB4pLah1BLZc0ay3of5E5rSq2s7 h0hA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=f2zRTlA8MREn7UtcRWtsmL1DFezf9Qyj3m2Vn17BrFY=; b=irLXR87t5O7vbErk2/87yfFnf6gRGlfHdwX1MKUEULW+h4FLUsX8+is5ciTpeHLMCN FyC96iClb1pWsH5J6Xe6ozab1C4JShQDezVxd/MCM09aYxZGnsjcKlLq+U2F6QAWND8B 74xBMe/IXhVzvZn9IlcpcTnT1GXt2I7yav2T0Vo4orAjRT2JqNFx1/We9Gn2zGjFgQAv 08AzUOVmjUacBBcjTGUNVocQaRe/jo27bRqXAcZecQ+v8Dj1NC/RJ8kAqoAJNsAxKY9s 4RQWo3OIz2hsBdwrZrbGgmuDe5qP5jhotZEit2X+A8Vt/SXIHH7n+duHm3flv0Or65gi KMdw== X-Gm-Message-State: AOPr4FVUN47UCl524BIarTLj26+7PT+Cj5y+oDvBmo3zUAkw2P+pbWGD6/T2gOxgvUKGTz6ZAzkl3ibnZ52ABA== MIME-Version: 1.0 X-Received: by 10.157.32.114 with SMTP id n105mr11543286ota.108.1461420130438; Sat, 23 Apr 2016 07:02:10 -0700 (PDT) Received: by 10.157.45.194 with HTTP; Sat, 23 Apr 2016 07:02:10 -0700 (PDT) In-Reply-To: <571B5B04.7040001@FreeBSD.org> References: <571B5B04.7040001@FreeBSD.org> Date: Sat, 23 Apr 2016 07:02:10 -0700 Message-ID: Subject: Re: How to use freebsd in sony's PS Vita From: Mehmet Erol Sanliturk To: Matthew Seaman Cc: FreeBSD Questions Mailing List , poopneo.rr.com@gmail.com Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 14:02:11 -0000 On Sat, Apr 23, 2016 at 4:22 AM, Matthew Seaman wrote: > On 23/04/2016 04:33, Austin Walker wrote: > > How can I use the pkg package installer in sonys ps vita and how > > do i access it please reply ;) > > As far as I know, there is no official support for pkg-style packages in > Sony's FreeBSD based devices. Neither have I heard any reports of > anyone porting pkg to that platform. So if you want to use pkg to > install packages there, it looks like you'ld have to do the work of > porting it there yourself. Bringing up pkg on a new platform is not a > trivial thing -- the first thing you'll need is a compilation > environment where you can build programs that will run on the Sony > device. Which means you'll need a compiler toolchain, make, perl, > autoconf and probably a few other applications. Many of these are > orders of magnitude more complex to deal with than just pkg. > > Also, even if you did have a copy of pkg that worked on a Sony device, > what would you do with it? You can't just install standard FreeBSD > packages there and expect them to work. Of course, once you could > compile pkg for sony, then you could probably compile a whole lot of > other stuff with relatively little effort. If you could bring that off, > you'ld be doing very well indeed. > > Cheers, > > Matthew > > > My knowledge is that Sony prevented running software on Playstation devices other than Sony prepared software , mainly games . Therefore , use of any external software on Playstation is not possible . At the beginning such a work was possible , even to construct clusters of Playstations . Later on Sony has prevented such usages . Mehmet Erol Sanliturk From owner-freebsd-questions@freebsd.org Sat Apr 23 14:06:43 2016 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 30185B12F52 for ; Sat, 23 Apr 2016 14:06:43 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DCEEF16A0 for ; Sat, 23 Apr 2016 14:06:42 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-oi0-x230.google.com with SMTP id x201so140736107oif.3 for ; Sat, 23 Apr 2016 07:06:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=HvN2lj1sFmzrmrp0TO6mPk3UYpg5wPcJhWMVdhIOec8=; b=0OtGSEDYsWYM5Mk77t82Mm/5QHIXgIXpb88SnsyGXsm5N0DIoEbrGHw9uGZUtH6/Vm oxBhcYlimEIruMr/VodyVzXq7fpoJ1qusrC1ckqD6nTNTL6Vv4df7xCb/sV4ObO2yUtp /KdZ/SRY6GlDWaNUuT0I8aGbd1EAG24Zaz11MuQB1aJEDx6b5UqTpieEB49X869je/NI +Bn0xuhin7Ny8Ep5mJI3lQ0H4tIaiYq6+WjUEHrGOQEEKsx16LKIzETz63j5OcJZf17E MJi0XLWm6cTmmB/2VNPJEA7k5d8v34VXa8/lGOOin43aV9mmwHsEflzJXWPRBzbt3woh H1XA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=HvN2lj1sFmzrmrp0TO6mPk3UYpg5wPcJhWMVdhIOec8=; b=RlgzJZ02cCbODVCbdMMaNN4Fekk3TA8xTlUlCRS2+GBjv1z8MKV+CE1V8WXXk8dOBZ gQakSVMcYvL22qn2E31/c2gdNMIsAXQak1j3x7sQtc1pIjCLLhVsOuJ84f7i0S6k1yMl ZlASCXL+j29ATUFLVZwm6Z3RK8epvpMh1Rp7ytQ2oBZgJV+sHm/3viWG50Qks4G3bc8W 6HILSMK/QyJY1vmq+k9BzwqfJ5v3rNVwzEN6IHqgg2X+jVmAxo5fwXhhr4bf666Ekltd ck1LDBSrtegRGijs5cgSt0COXNJ99n3ug99lmXjlcT4NOlGifxvTMWUPbSx6xfG0ZmOT +Jog== X-Gm-Message-State: AOPr4FV48oP5xykeI0vuEA20BLs2rZgIoarZKoxYVhWBJ9/TjCoMQHG9weoW8PMLW5fpDxVd/ZJyetR8a8Ox4w== MIME-Version: 1.0 X-Received: by 10.157.39.193 with SMTP id c59mr11916598otb.111.1461420402348; Sat, 23 Apr 2016 07:06:42 -0700 (PDT) Received: by 10.157.45.194 with HTTP; Sat, 23 Apr 2016 07:06:42 -0700 (PDT) In-Reply-To: References: Date: Sat, 23 Apr 2016 07:06:42 -0700 Message-ID: Subject: Re: About different ABI between gcc and clang From: Mehmet Erol Sanliturk To: Odhiambo Washington Cc: User Questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 14:06:43 -0000 On Sat, Apr 23, 2016 at 5:04 AM, Odhiambo Washington wrote: > I am looking at this page: > http://wiki.squid-cache.org/BuildFarm/FreeBsdInstall > > There is something that I don't quite understand and would appreciate the > help of the experts, like Matthew:-) > > > due to different ABI between gcc and clang, libcppunit needs to be > installed twice, one with the g++ ABI and one with clang's. The default > compiler for freebsd-9 is gcc; to setup the version for clang, configure it > as CC=clang35 CXX=clang++35 ./configure --prefix=/usr/local/clang-abi > > > Can someone explain that portion to me? What is the writer suggesting I do? > > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft." > _______________________________________________ > > > This means clang should be installed in its own directory , not in an upper , common directory because its files to install have conflicts with the files in upper directory of --prefix= , for example , they have the same name but with different structure , i.e. , they are not compliant . Mehmet Erol Sanliturk From owner-freebsd-questions@freebsd.org Sat Apr 23 14:13:06 2016 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 5295DB191F0 for ; Sat, 23 Apr 2016 14:13:06 +0000 (UTC) (envelope-from bourne.identity@hotmail.com) Received: from BLU004-OMC4S37.hotmail.com (blu004-omc4s37.hotmail.com [65.55.111.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1D0AD1C6A for ; Sat, 23 Apr 2016 14:13:05 +0000 (UTC) (envelope-from bourne.identity@hotmail.com) Received: from BLU436-SMTP74 ([65.55.111.135]) by BLU004-OMC4S37.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Sat, 23 Apr 2016 07:11:58 -0700 X-TMN: [wOlmZoMe4hqnjF6JKrETlhzFmnp39ojg] X-Originating-Email: [bourne.identity@hotmail.com] Message-ID: Subject: Re: Does HP DeskJet 1112 work with lpd on FreeBSD 10.2 amd64 ? To: Tijl Coosemans References: <20160420112203.3244f4ea@kalimero.tijl.coosemans.org> <20160423143300.40d7c478@kalimero.tijl.coosemans.org> From: Manish Jain CC: freebsd-questions@freebsd.org Date: Sat, 23 Apr 2016 19:40:28 +0530 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <20160423143300.40d7c478@kalimero.tijl.coosemans.org> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Apr 2016 14:11:35.0335 (UTC) FILETIME=[0B5F6370:01D19D6A] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 14:13:06 -0000 Regards, Manish Jain +91-70731-76333 On 04/23/16 18:03, Tijl Coosemans wrote: > On Sat, 23 Apr 2016 17:47:33 +0530 Manish Jain wrote: >> On 04/20/16 14:52, Tijl Coosemans wrote: >>> On Tue, 19 Apr 2016 18:42:01 +0530 Manish Jain wrote: >>>>> CUPS works nice for many years on my FreeBSD systems, actually CURRENT. >>>>> Why you can't get it to do anything on your system? matthias >>>> Thanks for responding. So my question becomes "Has anyne got HP DeskJet >>>> 1112 to work with CUPS on a FreeBSD 10.2 amd64 box ?" >>> You need to install print/hplip. Then you can either use the graphical >>> setup tool HP Device Manager, or the CUPS web interface at >>> http://localhost:631/. If you use the CUPS interface you need to select >>> the printer model at some point. Your printer will be listed as >>> "HP Deskjet 1110 Series, hpcups 3.16.2". >> This is what I get when I try to open up the cups web interface in my >> browser even after installing apache24 : >> >>> Chromium's connection attempt to*localhost*was rejected >> What could I be missing here ? hplip package was installed, along with >> all its dependencies. >> >> This is what I get in dmesg : >> >> ulpt0: on usbus2 >> ulpt0: using bi-directional mode >> >> So the printer is being detected, just as you stated. A little bit more >> help, and I could fire up my printout page. Perhaps something to do with >> httpd.conf ? Or perhaps /usr/local/etc/cups/cupsd.conf ? > Is the CUPS daemon actually running? Add cupsd_enable="YES" to /etc/rc.conf > and run 'service cupsd start'. Also, CUPS uses its own http server so you > don't need Apache. > > Hi Tijl, Thanks for replying. My /etc/rc.conf does have : cupsd_enable="YES" So I presume cupsd is getting started at boot time. This is what I have in /usr/local/etc/cups/cupsd.conf : LogLevel info # Administrator user group... SystemGroup wheel # Listen for connections on Port 631. Port 631 #Listen localhost:631 Listen /var/run/cups.sock # Show shared printers on the local network. Browsing On BrowseOrder allow,deny #BrowseAllow @LOCAL BrowseAllow 192.168.1.* # change to local LAN settings BrowseAddress 192.168.1.* # change to local LAN settings # Default authentication type, when authentication is required... DefaultAuthType Basic DefaultEncryption Never # comment this line to allow encryption # Allow access to the server from any machine on the LAN Order allow,deny #Allow localhost Allow 192.168.1.* # change to local LAN settings # Allow access to the admin pages from any machine on the LAN #Encryption Required Order allow,deny #Allow localhost Allow 192.168.1.* # change to local LAN settings # Allow access to configuration files from any machine on the LAN AuthType Basic Require user @SYSTEM Order allow,deny #Allow localhost Allow 192.168.1.* # change to local LAN settings # Set the default printer/job policies... # Job-related operations must be done by the owner or an administrator... Require user @OWNER @SYSTEM Order deny,allow # All administration operations require an administrator to authenticate... AuthType Basic Require user @SYSTEM Order deny,allow # Only the owner or an administrator can cancel or authenticate a job... Require user @OWNER @SYSTEM Order deny,allow Order deny,allow Regards Manish Jain From owner-freebsd-questions@freebsd.org Sat Apr 23 14:13:11 2016 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 E2541B19209 for ; Sat, 23 Apr 2016 14:13:11 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 726331C93 for ; Sat, 23 Apr 2016 14:13:11 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: by mail-wm0-x231.google.com with SMTP id n3so64925030wmn.0 for ; Sat, 23 Apr 2016 07:13:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=CptOIrfTLUHXqecMrTggVAiV/QVQIzbZB7KJFnSy7Cc=; b=kYSkOTnxw+487vFLeAXmC1k7mUzH6q+D8VjZ4JNHwBHZQvSIoXZGrIhtG9IC/W2rRE 154J/8g1CrEfGGa9rzHq1dl897Y/cpUKy/9dzJiaRLiZKICWpsKftzz7v8+xN7/aKSCw zodmrKJ/HTGcgYelazGFA/X6/3BEIZT58Qrd7mAGlz7FOzSU1EwkbAL2/fe7wBnfuJQl 6nn7KuDOPLzQ3OgkVSDubECQWR7zeHdfZjA377XJlAUxeGs1o7bk1lQRu5LsIra/jRLF AeNKg9UEYVUegQqN4o5gHDHGrgi87uTfj//7NroGWpyORyx4tZl5iRyXJ7n+XvLBIr8N Xjqw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=CptOIrfTLUHXqecMrTggVAiV/QVQIzbZB7KJFnSy7Cc=; b=DKamXzW7o4psAIImT4g8toY7DRJCty5rNES7yWpZP+8fWROhlirIkksDd4daXqY0+P AkBKssTwSCMzQrnf494ZDqZcSHMse2esPTU4bQslxlriKgO+1HFqBtY91x5wmJJvnMDF Yd/CYwyiNWsGofp4+qWLLwhVOjlZEYUoFjiykB/OVHHHFuE69Vm6R4UCAmlRMVy/oCq6 uAlEKR0NICfdtE+VPS5mJLSvdEsLEuVrnnOeprDrnCeNat/qtTWeBr8x4QxTqc7NEX2c c5vhWJ3zuIMTxmrYdEQiNHuB2RUxqDFJvA9yQ9yghfPMzD3NFnJ3BrH1jY67NTQ0SM9v Q0mg== X-Gm-Message-State: AOPr4FWW9ExyyzvPMQDVEms1iKfLSdzcxhxsL2LHplhV/bm3C/wjEQ9PcWndLa7anuNtkyPBP5uVTlFEJBhkpA== X-Received: by 10.28.171.8 with SMTP id u8mr2647973wme.97.1461420789503; Sat, 23 Apr 2016 07:13:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.103.233 with HTTP; Sat, 23 Apr 2016 07:12:29 -0700 (PDT) In-Reply-To: References: From: Odhiambo Washington Date: Sat, 23 Apr 2016 17:12:29 +0300 Message-ID: Subject: Re: About different ABI between gcc and clang To: Mehmet Erol Sanliturk Cc: User Questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 14:13:12 -0000 On 23 April 2016 at 17:06, Mehmet Erol Sanliturk wrote: > > > On Sat, Apr 23, 2016 at 5:04 AM, Odhiambo Washington > wrote: > >> I am looking at this page: >> http://wiki.squid-cache.org/BuildFarm/FreeBsdInstall >> >> There is something that I don't quite understand and would appreciate the >> help of the experts, like Matthew:-) >> >> >> due to different ABI between gcc and clang, libcppunit needs to be >> installed twice, one with the g++ ABI and one with clang's. The default >> compiler for freebsd-9 is gcc; to setup the version for clang, configure >> it >> as CC=clang35 CXX=clang++35 ./configure --prefix=/usr/local/clang-abi >> >> >> Can someone explain that portion to me? What is the writer suggesting I >> do? >> >> >> >> -- >> Best regards, >> Odhiambo WASHINGTON, >> Nairobi,KE >> +254 7 3200 0004/+254 7 2274 3223 >> "Oh, the cruft." >> _______________________________________________ >> >> >> > > This means clang should be installed in its own directory , not in an > upper , common directory because its files to install have conflicts with > the files in upper directory of --prefix= , for example , they have the > same name but with different structure , i.e. , they are not compliant . > > Mehmet Erol Sanliturk > How do I do that for a port?? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft." From owner-freebsd-questions@freebsd.org Sat Apr 23 14:18:50 2016 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 C5FF1B19395 for ; Sat, 23 Apr 2016 14:18:50 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8403E1E67 for ; Sat, 23 Apr 2016 14:18:50 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-oi0-x232.google.com with SMTP id k142so141147402oib.1 for ; Sat, 23 Apr 2016 07:18:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=69s0dFDcYmRorzYSN+WL/4JkRKKVNRT43u0w3v0gG/0=; b=kp6iE9DzUnVvmdCyRKxDrPXkhaxArfQkegzaON5Chq+yeGXVDJ7Wdyynqj5MQqK2H1 cnLD0xcdUwNs5npCsU4LS9K+90qI4hImyibTCbpzyRA6SdgiDU65rikm8Mft1eWBtWDN fA2iJdutC3WIectQBsMWrZFCT0tf8EYaN+yTE+aZQ2jA/Vdu6c/KoTsGldmhuY9y1DWt O8Z5TvYOuZVqh6VDA2Ydyj+Z9bfDE5bKWGfe8A9nhPQ2FFJgyW+SMNDj2qGOTbRAItaC iGiXFlUFxi7HoA0yiAlzluEopiC7GywbkiU+Jhb8qBTnRU4h+YHlYgpKyCuZh9XUCogb M4WA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=69s0dFDcYmRorzYSN+WL/4JkRKKVNRT43u0w3v0gG/0=; b=VGooV8VNP53LsCeOLRyI9meOeqGH+J8WOfkc/aWS/5sUPjZZ6hvGupCYO973RTdf9O 5esX/hvbn3TH2Rp13/Pk3sD+rXQeQtEMsfyXBC9HqCTxxMMeS0+y7zyqdaqCdO4uO2S0 oRDr0OHrwKqQANPpLRyhsOO2Vrjurv6L5bXivgZN1CpGqCrl0rsgnFE4j3y5Ra6RlBDu X0mfJ6XLQ2XkQNM0Sn+e+sO+q/sV8YT5Td9ncx9yMd1spCwc+ZIVxw2jONO93RkTTJIR JaQ/p68FPpXm/kh4rrrGBas+fQB0lt0G/YpOZP+LIkp7T79QRt8w0ruZFMzdWEGRflh0 4ABA== X-Gm-Message-State: AOPr4FUxeABc5STWgNhx3pY5WsKsrUr0XBlRjZZJcQT0xPyDRqd2Bf0XANDdnWLm9tO9fXyWPeu2wE5GqTQIbg== MIME-Version: 1.0 X-Received: by 10.202.98.133 with SMTP id w127mr9582614oib.136.1461421129827; Sat, 23 Apr 2016 07:18:49 -0700 (PDT) Received: by 10.157.45.194 with HTTP; Sat, 23 Apr 2016 07:18:49 -0700 (PDT) In-Reply-To: References: Date: Sat, 23 Apr 2016 07:18:49 -0700 Message-ID: Subject: Re: About different ABI between gcc and clang From: Mehmet Erol Sanliturk To: Odhiambo Washington Cc: User Questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 14:18:50 -0000 On Sat, Apr 23, 2016 at 7:12 AM, Odhiambo Washington wrote: > > > On 23 April 2016 at 17:06, Mehmet Erol Sanliturk > wrote: > >> >> >> On Sat, Apr 23, 2016 at 5:04 AM, Odhiambo Washington >> wrote: >> >>> I am looking at this page: >>> http://wiki.squid-cache.org/BuildFarm/FreeBsdInstall >>> >>> There is something that I don't quite understand and would appreciate the >>> help of the experts, like Matthew:-) >>> >>> >>> due to different ABI between gcc and clang, libcppunit needs to be >>> installed twice, one with the g++ ABI and one with clang's. The default >>> compiler for freebsd-9 is gcc; to setup the version for clang, configure >>> it >>> as CC=clang35 CXX=clang++35 ./configure --prefix=/usr/local/clang-abi >>> >>> >>> Can someone explain that portion to me? What is the writer suggesting I >>> do? >>> >>> >>> >>> -- >>> Best regards, >>> Odhiambo WASHINGTON, >>> Nairobi,KE >>> +254 7 3200 0004/+254 7 2274 3223 >>> "Oh, the cruft." >>> _______________________________________________ >>> >>> >>> >> >> This means clang should be installed in its own directory , not in an >> upper , common directory because its files to install have conflicts with >> the files in upper directory of --prefix= , for example , they have the >> same name but with different structure , i.e. , they are not compliant . >> >> Mehmet Erol Sanliturk >> > > How do I do that for a port?? > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft." > In page https://www.freebsd.org/doc/handbook/ports-using.html see "4.5.1.1. Customizing Ports Installation" . Mehmet Erol Sanliturk From owner-freebsd-questions@freebsd.org Sat Apr 23 14:18:58 2016 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 E8304B193B0 for ; Sat, 23 Apr 2016 14:18:58 +0000 (UTC) (envelope-from bourne.identity@hotmail.com) Received: from BLU004-OMC4S6.hotmail.com (blu004-omc4s6.hotmail.com [65.55.111.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B3A411EA0 for ; Sat, 23 Apr 2016 14:18:58 +0000 (UTC) (envelope-from bourne.identity@hotmail.com) Received: from BLU436-SMTP41 ([65.55.111.136]) by BLU004-OMC4S6.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Sat, 23 Apr 2016 07:17:50 -0700 X-TMN: [hDmYyXI6+AtWXT2CjA+nPpvMZw3OfzI6] X-Originating-Email: [bourne.identity@hotmail.com] Message-ID: Subject: Re: Does HP DeskJet 1112 work with lpd on FreeBSD 10.2 amd64 ? To: Tijl Coosemans References: <20160420112203.3244f4ea@kalimero.tijl.coosemans.org> <20160423143300.40d7c478@kalimero.tijl.coosemans.org> <571B8254.7080201@hotmail.com> CC: freebsd-questions@freebsd.org From: Manish Jain Date: Sat, 23 Apr 2016 19:46:39 +0530 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <571B8254.7080201@hotmail.com> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Apr 2016 14:17:47.0413 (UTC) FILETIME=[E925FC50:01D19D6A] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 14:18:59 -0000 Regards, Manish Jain +91-70731-76333 On 04/23/16 19:40, Manish Jain wrote: > > Regards, > > Manish Jain > +91-70731-76333 > > On 04/23/16 18:03, Tijl Coosemans wrote: >> On Sat, 23 Apr 2016 17:47:33 +0530 Manish Jain >> wrote: >>> On 04/20/16 14:52, Tijl Coosemans wrote: >>>> On Tue, 19 Apr 2016 18:42:01 +0530 Manish Jain >>>> wrote: >>>>>> CUPS works nice for many years on my FreeBSD systems, actually >>>>>> CURRENT. >>>>>> Why you can't get it to do anything on your system? matthias >>>>> Thanks for responding. So my question becomes "Has anyne got HP >>>>> DeskJet >>>>> 1112 to work with CUPS on a FreeBSD 10.2 amd64 box ?" >>>> You need to install print/hplip. Then you can either use the >>>> graphical >>>> setup tool HP Device Manager, or the CUPS web interface at >>>> http://localhost:631/. If you use the CUPS interface you need to >>>> select >>>> the printer model at some point. Your printer will be listed as >>>> "HP Deskjet 1110 Series, hpcups 3.16.2". >>> This is what I get when I try to open up the cups web interface in my >>> browser even after installing apache24 : >>> >>>> Chromium's connection attempt to*localhost*was rejected >>> What could I be missing here ? hplip package was installed, along with >>> all its dependencies. >>> >>> This is what I get in dmesg : >>> >>> ulpt0: on >>> usbus2 >>> ulpt0: using bi-directional mode >>> >>> So the printer is being detected, just as you stated. A little bit more >>> help, and I could fire up my printout page. Perhaps something to do >>> with >>> httpd.conf ? Or perhaps /usr/local/etc/cups/cupsd.conf ? >> Is the CUPS daemon actually running? Add cupsd_enable="YES" to >> /etc/rc.conf >> and run 'service cupsd start'. Also, CUPS uses its own http server >> so you >> don't need Apache. >> >> > > > Hi Tijl, > > Thanks for replying. > > My /etc/rc.conf does have : > > cupsd_enable="YES" > > So I presume cupsd is getting started at boot time. > > This is what I have in /usr/local/etc/cups/cupsd.conf : > > LogLevel info > > # Administrator user group... > SystemGroup wheel > > # Listen for connections on Port 631. > Port 631 > #Listen localhost:631 > Listen /var/run/cups.sock > > # Show shared printers on the local network. > Browsing On > BrowseOrder allow,deny > #BrowseAllow @LOCAL > BrowseAllow 192.168.1.* # change to local LAN settings > BrowseAddress 192.168.1.* # change to local LAN settings > > # Default authentication type, when authentication is required... > DefaultAuthType Basic > DefaultEncryption Never # comment this line to allow encryption > > # Allow access to the server from any machine on the LAN > > Order allow,deny > #Allow localhost > Allow 192.168.1.* # change to local LAN settings > > > # Allow access to the admin pages from any machine on the LAN > > #Encryption Required > Order allow,deny > #Allow localhost > Allow 192.168.1.* # change to local LAN settings > > > # Allow access to configuration files from any machine on the LAN > > AuthType Basic > Require user @SYSTEM > Order allow,deny > #Allow localhost > Allow 192.168.1.* # change to local LAN settings > > > # Set the default printer/job policies... > > # Job-related operations must be done by the owner or an > administrator... > Purge-Jobs \ > Set-Job-Attributes Create-Job-Subscription Renew-Subscription > Cancel-Subscription \ > Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job > Resume-Job \ > CUPS-Move-Job> > Require user @OWNER @SYSTEM > Order deny,allow > > > # All administration operations require an administrator to > authenticate... > Enable-Printer \ > Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs > Release-Held-New-Jobs \ > Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer > Startup-Printer \ > Promote-Job Schedule-Job-After CUPS-Add-Printer CUPS-Delete-Printer > CUPS-Add-Class \ > CUPS-Delete-Class CUPS-Accept-Jobs CUPS-Reject-Jobs CUPS-Set-Default> > AuthType Basic > Require user @SYSTEM > Order deny,allow > > > # Only the owner or an administrator can cancel or authenticate a > job... > > Require user @OWNER @SYSTEM > Order deny,allow > > > > Order deny,allow > > > > Regards > Manish Jain > Some more diagnostics : This is what I get when I run hp-setup : warning: Fax setup disabled - Python 2.3+ required. Searching... (bus=usb, search=(None), desc=0) error: Failed to run the /usr/local/sbin/lsusb command error: No devices found on bus: usb Regards Manish Jain From owner-freebsd-questions@freebsd.org Sat Apr 23 14:24:57 2016 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 2273DB1967B for ; Sat, 23 Apr 2016 14:24:57 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A21AE1245 for ; Sat, 23 Apr 2016 14:24:56 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (liminal.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3636:3bff:fed4:b0d6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 54A83DF80; Sat, 23 Apr 2016 14:24:53 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/54A83DF80; dkim=none; dkim-atps=neutral Subject: Re: About different ABI between gcc and clang To: Odhiambo Washington References: <571B7694.5050006@FreeBSD.org> Cc: User Questions From: Matthew Seaman Message-ID: <571B85AE.1000003@FreeBSD.org> Date: Sat, 23 Apr 2016 15:24:46 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="VnNVOj2KQT2E9lfmuGwuDNgNImawOqHgQ" X-Virus-Scanned: clamav-milter 0.99.1 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 14:24:57 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --VnNVOj2KQT2E9lfmuGwuDNgNImawOqHgQ Content-Type: multipart/mixed; boundary="GmOf4mfGOVEUQ1DLqJgXSQohGpAjgBiBI" From: Matthew Seaman To: Odhiambo Washington Cc: User Questions Message-ID: <571B85AE.1000003@FreeBSD.org> Subject: Re: About different ABI between gcc and clang References: <571B7694.5050006@FreeBSD.org> In-Reply-To: --GmOf4mfGOVEUQ1DLqJgXSQohGpAjgBiBI Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 23/04/2016 14:59, Odhiambo Washington wrote: > On my box, I have: >=20 > root@gw:/usr/home/wash # `which clang` --version > FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 2014051= 2 > Target: i386-unknown-freebsd9.3 > Thread model: posix > root@gw:/usr/home/wash # clang --version > FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 2014051= 2 > Target: i386-unknown-freebsd9.3 > Thread model: posix >=20 > root@gw:/usr/home/wash # gcc --version > gcc (GCC) 4.2.1 20070831 patched [FreeBSD] > Copyright (C) 2007 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is= NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURP= OSE. >=20 > root@gw:/usr/home/wash # which gcc > /usr/bin/gcc > root@gw:/usr/home/wash # /usr/bin/gcc --version > gcc (GCC) 4.2.1 20070831 patched [FreeBSD] > Copyright (C) 2007 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is= NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURP= OSE. >=20 > Any suggestion on what I should do? Those are the compilers that come with the base system. Try installing something more recent from ports. > I am trying to compile squid-4.0.9 which isn't in the ports. >=20 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203860 Not sure why that hasn't been committed yet. Cheers, Matthew --GmOf4mfGOVEUQ1DLqJgXSQohGpAjgBiBI-- --VnNVOj2KQT2E9lfmuGwuDNgNImawOqHgQ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJXG4W0XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATeOIP/RfGaX05iaLatlA6dmGUptxC JpMqR8J9ZAwoH2SFFTEOHYqRV4gXZ7U5NNZvf1RzCXc/9dLzEYDb+Rb8wOKlqNY6 BsbV4Xcz//4Snte42WXyCmODUTBxfaM6veRkut7v5UXTPTJ3lDo9X2O5LdYAlMsK QWXVL/mRN8n/toUM0gz9LcouiOxROR6r5R+tmIykMH/1+aKngqlxbd65QhTfpeQC zXXZ1X0Q3ZpWfWDZAR6RjV5MKSFELwaewDKQzp0M66unFBTf0t9P7G7W64GrKPfq UTJKX9o3q7zS0+QetB9lAua/Zmb7rrV+GDZej0/IzRF+FFL76oEo04vWwim9zGZ1 xkDoZvKo1O/Ctd+msfwJQpjCh+U76SdRlg/fq1ArWaYJUn9UPKDouh/jSHPSTQTj qHel6pLl53CIjTZs0XOIBez5YG+RsBXZl/3rRV9+LEsaWFr2gSVn71CUYHt2tf2M fjt+5xm8/3wWEBo0YhKjGLKdX++/WEA8qm0iDg4dkmnREHyptuCkAbMO5XbrW3RX yuxNkhz52TMSULZlthVtFSRzae1EDavWDrUfdZb89o7A1FW46wrhYCydWMXbILxX Eq3MnBhMFgwD7vAllAR1R8e7UnXI90tn85ev/qTO3N1KtUaza3N+xY+QwtXXX1+C dbbGX8CsbVTNFQ5+o5Zy =ufY4 -----END PGP SIGNATURE----- --VnNVOj2KQT2E9lfmuGwuDNgNImawOqHgQ-- From owner-freebsd-questions@freebsd.org Sat Apr 23 14:39:02 2016 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 C8A9EB19B31 for ; Sat, 23 Apr 2016 14:39:02 +0000 (UTC) (envelope-from user8@host-ns-3.basnet.by) Received: from host-ns-3.basnet.by (host-ns-1.basnet.by [80.94.169.4]) (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 8857F19C5 for ; Sat, 23 Apr 2016 14:39:01 +0000 (UTC) (envelope-from user8@host-ns-3.basnet.by) Received: from user8 by host-ns-3.basnet.by with local (Exim 4.86_1) (envelope-from ) id 1atyhu-001o0V-BO for freebsd-questions@freebsd.org; Sat, 23 Apr 2016 17:38:50 +0300 To: freebsd-questions@freebsd.org Subject: Customer Satisfaction Survey! Win 50$, X-PHP-Script: www.buk.by/temp/e.php for 41.249.103.232 From: Woolworths Message-Id: Date: Sat, 23 Apr 2016 17:38:50 +0300 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host-ns-3.basnet.by X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [559 570] / [47 12] X-AntiAbuse: Sender Address Domain - host-ns-3.basnet.by X-Get-Message-Sender-Via: host-ns-3.basnet.by: authenticated_id: user8/only user confirmed/virtual account not confirmed X-Authenticated-Sender: host-ns-3.basnet.by: user8 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 14:39:02 -0000 From owner-freebsd-questions@freebsd.org Sat Apr 23 14:39:28 2016 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 38A63B19B9D for ; Sat, 23 Apr 2016 14:39:28 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.70.90]) by mx1.freebsd.org (Postfix) with ESMTP id F35D01A96 for ; Sat, 23 Apr 2016 14:39:27 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id 3211DCB8CA1; Sat, 23 Apr 2016 09:39:27 -0500 (CDT) Received: from 76.193.16.109 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Sat, 23 Apr 2016 09:39:27 -0500 (CDT) Message-ID: <54220.76.193.16.109.1461422367.squirrel@cosmo.uchicago.edu> In-Reply-To: <571AD606.4000203@holgerdanske.com> References: <29462.128.135.52.6.1461352625.squirrel@cosmo.uchicago.edu> <571AD606.4000203@holgerdanske.com> Date: Sat, 23 Apr 2016 09:39:27 -0500 (CDT) Subject: Re: Storage cluster advise, anybody? From: "Valeri Galtsev" To: "David Christensen" Cc: freebsd-questions@freebsd.org 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 14:39:28 -0000 On Fri, April 22, 2016 8:55 pm, David Christensen wrote: > On 04/22/2016 12:17 PM, Valeri Galtsev wrote: >> I would like to ask everybody: what would you advise to use as a storage >> cluster, or as a distributed filesystem. > ... >> My requirements are: >> >> 1. I would like to have one big (say, comparable to petabyte) >> filesystem, >> accessible on more than one machine, composed of disk space leftovers on >> a >> bunch of machines having 1 gigabit per second ethernet connections >> >> 2. It can be a bit slow, as filesystem one would need for backups onto >> it >> (say, using bacula or bareos), and/or for long term storage of large >> datasets, portions of which can be copied over to faster storage for >> processing if necessary. I would be thinking in 1-2 TB of data written >> to >> it daily. >> >> 3. It would be great to have it single machine failure/reboot resilient >> >> 4. metadata machines should be redundant (or at least backup medatada >> host >> should be manually convertible into master metadata host if fatal >> failure >> to master or corruption of its data happens) >> >> >> What I would like to avoid/exclude: >> >> 1. Proprietary commercial solutions, as: >> >> a. I would like to stay on as minimal budget as possible >> b. I want to be able to predict that it will exist for long time, and I >> have better experience with my predictions of this sort about open >> source >> projects as opposed to proprietary ones >> >> 2. Open source solutions using portions of proprietary closed source >> binaries/libraries (e.g., I would like to stay away from google >> proprietary code/binaries/libraries/modules) >> >> 3. Kernel level modifications. I really would like to have this >> independent of OS as much as I can, or rather available on multiple OSes >> (though I do not like Java based things - just my personal experience >> with >> some of them). I have a bunch of Linux boxes and a bunch of FreeBSD >> boxes, >> and I do not want to exclude neither of them if possible. Also, the need >> to have custom Linux kernel specifically scares me: Linux kernels get >> critical updates often, and having customizations lagging behind the >> need >> of critical update is as unpleasant as rebooting the machine because of >> kernel update is. >> >> I'm not too scared of a "split nature" projects: proprietary projects >> having open source satellite. I have mixed experience with those, using >> open source satellite I mean. Some of them are indeed not neglected, and >> even though you may be missing some features commercial counterpart has, >> some are really great ones: they are just missing commercial support, >> and >> maybe having a bit sparse documentation, thus making you to invest more >> effort into making it work, which I don't mind: I can earn my sysadmin's >> salary here. I would say I more often had good experience with those >> than >> bad one (and I have a list of early indications of potential bad >> outcome, >> so I can more or less predict my future with this kind of projects). >> >> ... moosefs. ... > > If you want solution that works on both BSD and Linux, FUSE comes to mind: > > https://en.wikipedia.org/wiki/Filesystem_in_Userspace > Indeed. That is what moosefs is taking advantage of. Though I'm through with moosefs (at least for quite some time). > > Are all the file system storage member computers located in one room? > In one building? In one campus? > Yes. Same group of racks, connected to the same stack of switches (1 gbps connections). > > You say "composed of disk space leftovers on a bunch of machines". How > many machines? What form of leftovers -- whole disks, whole partitions, > block-contiguous files, non-contiguous files? > About a dozen currently. Mostly large partitions on RAIDs, sometimes whole RAIDS or whole disks. Majority of them are different in size. > > Do you need checksumming, mirroring, RAID, caching, whatever? > Yes if possible, not a must (so I didn't list it in my "requirements"). Yes for RAID (RAID is kind of subset of my "fault tolerance to one machine failure or reboot" requirement) > > What are your degradation expectations in the face of missing/ > unresponsive member machines? Failing drives/ files? > I expect to only have one trouble at a time, meaning one machine at a time. If machine adds more than one "chunk of space" to the bucket, all of these chunks excluded from the bucket simultaneously shouldn't be catastrophic. (Moosefs is pretty good about that as I understand. If you set "goal" 2 meaning each chunk of data has two copies somewhere it makes sure these two copies live on different physical machines) > > Are you going to serve the file system via NFS? Samba? Other? > Doesn't matter. Whichever it is able to do, I will use it. > > You indicate 1-2 TB/day of writes, expected to be backups and dataset > archives. What sort of read traffic do you expect? How many connected > clients? How many hitting it at the same time? Any usage spikes (say, > everyone downloading files at work start, everyone uploading or backing > up at quiting time)? > Write pattern is mostly randomly spread over time, as you usually do with backup scheduling. Read pattern: sometimes small portions of data will be accessed at the best available read rate (as when you recover small directories from backup), and sometimes there may be steady longer read most likely 1-10TB in size to faster storage for processing - at available read speed. Thanks for asking. I didn't mention these details to not overburden my question with details that are of less priority for me and with which I will live once the main goals are met. Valeri > > David > > _______________________________________________ > 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 Apr 23 14:40:18 2016 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 7CB0CB19E46 for ; Sat, 23 Apr 2016 14:40:18 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::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 0C14C1C6F for ; Sat, 23 Apr 2016 14:40:18 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: by mail-wm0-x234.google.com with SMTP id e201so44373233wme.0 for ; Sat, 23 Apr 2016 07:40:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=69wB7GXcj/CUGSpQ1xgtrTCHQtoHU28itnpzmkwyZSY=; b=tlZAZtbFAcC3b7f+xh2iSMhV+PghChNnmK3vBQKuy4eCzARzqGINglkU8Fm74Ws5ev m7VSYXIBp3m5RTFEbIFdykLKXkw8UNhRwRAl6pBbvH6W899EpAleqz6/299leiG3qhiz I6AeZWcN2GxbMpQM6wQdCcdlnPRQwK9dgemkmpR8xB2+YHR0+t24mN6T7MvL8wn317oA zkcnxuM5QWpgMjU/nDu0OePIEQqdKrnEiD92I5Ibo/8cPRYiH9nzIw2skyThDXVU/cGT IIBnoQHwjBiVKiSGQcelXakfGJEuKFtJ1Kjt54D1gmYSZ+1kigo7mpyceKyQCVrYWeeI EdeA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=69wB7GXcj/CUGSpQ1xgtrTCHQtoHU28itnpzmkwyZSY=; b=BalnafWg/atV1Dv+8S+D9ixLC/K/Q5/SXnwYnpshVaaHvWdJFXr8mauknzgGVM2Vq1 xFRtIiWtPF3OT+9t2jOL7XTJQUNDKHDB5l5pZnrohHqQLCOhHhN9cq0X8EfQd1yUS89y PTXz0km6APOrqLeF7JhYFCNUSZaTtzXe7bqnCHvDLL5nto86PTvtNnkVkBzSVIm4kjpl CmM2Y613Hf7xE57IXv9ZknmHPyifWVwkKzFvQkd3AUOdwAAZocXN2iha3F8bsPmGglfQ 7+7EATEGoALdqN3RAaGT1JCz/2kzcHRARXdOM5eHSHte12l9r0OXJcZ4Ckp4gJ0ce2sH m72Q== X-Gm-Message-State: AOPr4FXy+3eynILYjQjzevDGewMKz7maopehxMHiO9Qj89PNuEFtAwyVpEKl2Tv9n9SEFNYnVTd9O87qU4dnlQ== X-Received: by 10.28.215.197 with SMTP id o188mr3088850wmg.14.1461422416406; Sat, 23 Apr 2016 07:40:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.103.233 with HTTP; Sat, 23 Apr 2016 07:39:36 -0700 (PDT) In-Reply-To: References: From: Odhiambo Washington Date: Sat, 23 Apr 2016 17:39:36 +0300 Message-ID: Subject: Re: About different ABI between gcc and clang To: Mehmet Erol Sanliturk Cc: User Questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 14:40:18 -0000 On 23 April 2016 at 17:18, Mehmet Erol Sanliturk wrote: > > > On Sat, Apr 23, 2016 at 7:12 AM, Odhiambo Washington > wrote: > >> >> >> On 23 April 2016 at 17:06, Mehmet Erol Sanliturk > > wrote: >> >>> >>> >>> On Sat, Apr 23, 2016 at 5:04 AM, Odhiambo Washington >> > wrote: >>> >>>> I am looking at this page: >>>> http://wiki.squid-cache.org/BuildFarm/FreeBsdInstall >>>> >>>> There is something that I don't quite understand and would appreciate >>>> the >>>> help of the experts, like Matthew:-) >>>> >>>> >>>> due to different ABI between gcc and clang, libcppunit needs to be >>>> installed twice, one with the g++ ABI and one with clang's. The default >>>> compiler for freebsd-9 is gcc; to setup the version for clang, >>>> configure it >>>> as CC=clang35 CXX=clang++35 ./configure --prefix=/usr/local/clang-abi >>>> >>>> >>>> Can someone explain that portion to me? What is the writer suggesting I >>>> do? >>>> >>>> >>>> >>>> -- >>>> Best regards, >>>> Odhiambo WASHINGTON, >>>> Nairobi,KE >>>> +254 7 3200 0004/+254 7 2274 3223 >>>> "Oh, the cruft." >>>> _______________________________________________ >>>> >>>> >>>> >>> >>> This means clang should be installed in its own directory , not in an >>> upper , common directory because its files to install have conflicts with >>> the files in upper directory of --prefix= , for example , they have the >>> same name but with different structure , i.e. , they are not compliant . >>> >>> Mehmet Erol Sanliturk >>> >> >> How do I do that for a port?? >> >> >> -- >> Best regards, >> Odhiambo WASHINGTON, >> Nairobi,KE >> +254 7 3200 0004/+254 7 2274 3223 >> "Oh, the cruft." >> > > > In page > https://www.freebsd.org/doc/handbook/ports-using.html > > see > > "4.5.1.1. Customizing Ports Installation" > . > > > Mehmet Erol Sanliturk > Wonderful!!!! Thank you for that. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft." From owner-freebsd-questions@freebsd.org Sat Apr 23 14:41:31 2016 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 8EB3EB1A006 for ; Sat, 23 Apr 2016 14:41:31 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::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 DDE721E69; Sat, 23 Apr 2016 14:41:28 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: by mail-wm0-x233.google.com with SMTP id v188so50799667wme.1; Sat, 23 Apr 2016 07:41:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hoSy2O4ZdEsTGu9ibUZ2XFaciBQh5sG6jR+suCjB3N0=; b=tfHXnMS90CJUrjFrxVE7QUcWnSx2sWAuI8/0Shbjy4xxhJlNohzw4RAvCkMgU0avG7 tSNC4OfO9Oc9egi7uOcwv3Jj3RLexMkYnixgeWsxxHnpaDRQg6dfSPqv75RZILZiy6UG 22fJDEjYb+k0cvuEzLylsFRMBFoMlHKbiPMDnrwA36ZOQa2gGnWKfhZeXPC5Jj9brK72 Of0Fz0CGDIxeWFQuzip5Uxtaca/Aq1bW1DrmXT1T3A4QFhTosK3i9Nyfns8Zo0gdtFhW 0Q1R86T2SIXX1V7X6WmHsf2icwnmLLqBiz/x9STPvHjgs0XWKkVJZD2GOt7oW65oSERa Kxiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=hoSy2O4ZdEsTGu9ibUZ2XFaciBQh5sG6jR+suCjB3N0=; b=ea1QCbxGt7WWN8cUM14DuUY0EEkiE09eEaBZmZK/Nk385iuYF3ThRYU7RV8lIm1AFM oLGM1txI856SweI8aa3cp1PP+9dZYv/vWHrgqqlfpQTecmn7HH+YvlFi7RmwPciCj1xC kse7982A8c7pgZbuCx7aOtNS1qqjx6SDxfRkRBlUnsT5R8mYPU3Tgg7mhNJKZb+g2T6O 0ZxQn11cuy6M5JvOF8Kc0As5ykGcKwc8r3fRvMJYfOD17v2W2pPw+C1fYx6wyjOWMQxH VXL7mJlGzP7hJwmoA0a2RABwG8uG33Zf917tVMyfSl/i5iZfl3MypPn736NLrG2K+j9u A3fw== X-Gm-Message-State: AOPr4FVLiz+f/svSetwEhifkYFbg2+Te4dfuiE2BTRvXQD6jOxzah0Cuj7NwGnZyycSNPCX8ql6oyYRGIzho9Q== X-Received: by 10.194.61.19 with SMTP id l19mr25099434wjr.4.1461422486948; Sat, 23 Apr 2016 07:41:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.103.233 with HTTP; Sat, 23 Apr 2016 07:40:47 -0700 (PDT) In-Reply-To: <571B85AE.1000003@FreeBSD.org> References: <571B7694.5050006@FreeBSD.org> <571B85AE.1000003@FreeBSD.org> From: Odhiambo Washington Date: Sat, 23 Apr 2016 17:40:47 +0300 Message-ID: Subject: Re: About different ABI between gcc and clang To: Matthew Seaman Cc: User Questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 14:41:31 -0000 On 23 April 2016 at 17:24, Matthew Seaman wrote: > On 23/04/2016 14:59, Odhiambo Washington wrote: > > On my box, I have: > > > > root@gw:/usr/home/wash # `which clang` --version > > FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 > > Target: i386-unknown-freebsd9.3 > > Thread model: posix > > root@gw:/usr/home/wash # clang --version > > FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 > > Target: i386-unknown-freebsd9.3 > > Thread model: posix > > > > root@gw:/usr/home/wash # gcc --version > > gcc (GCC) 4.2.1 20070831 patched [FreeBSD] > > Copyright (C) 2007 Free Software Foundation, Inc. > > This is free software; see the source for copying conditions. There is > NO > > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR > PURPOSE. > > > > root@gw:/usr/home/wash # which gcc > > /usr/bin/gcc > > root@gw:/usr/home/wash # /usr/bin/gcc --version > > gcc (GCC) 4.2.1 20070831 patched [FreeBSD] > > Copyright (C) 2007 Free Software Foundation, Inc. > > This is free software; see the source for copying conditions. There is > NO > > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR > PURPOSE. > > > > Any suggestion on what I should do? > > Those are the compilers that come with the base system. Try installing > something more recent from ports. > > > I am trying to compile squid-4.0.9 which isn't in the ports. > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203860 > > Not sure why that hasn't been committed yet. > > Cheers, > > Matthew > > Heheee, I knew with you I can never go wrong! Now I am smiling from cheek to cheek!! Have a blessed one, and may you live long!!!! -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft." From owner-freebsd-questions@freebsd.org Sat Apr 23 15:00:19 2016 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 A68B8B1A6E6 for ; Sat, 23 Apr 2016 15:00:19 +0000 (UTC) (envelope-from tijl@coosemans.org) Received: from mailrelay110.isp.belgacom.be (mailrelay110.isp.belgacom.be [195.238.20.137]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (Client CN "relay.skynet.be", Issuer "GlobalSign Organization Validation CA - SHA256 - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EF7101A28 for ; Sat, 23 Apr 2016 15:00:18 +0000 (UTC) (envelope-from tijl@coosemans.org) X-Belgacom-Dynamic: yes X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2BOCQCVjBtX/4pJsVtEEQmDOFN9qSWFA4tdAQ2BdSKFbAKBHDkUAQEBAQEBAWUnQQEBAQEBAQEHAgKDbwEBBDocIxALDgoJJQ8qHgYTiBUDFgosvnkBAQEBAQEBAwEBAQEBAQEVBIIgiEyCQYFVEYVuBYd+hweIWTGMH4Frb44rh1CHXx4BAUKDbTowAQEBgSSDGRCCIIILAQEB Received: from 138.73-177-91.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([91.177.73.138]) by relay.skynet.be with ESMTP; 23 Apr 2016 16:59:04 +0200 Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org [127.0.0.1]) by kalimero.tijl.coosemans.org (8.15.2/8.15.2) with ESMTP id u3NEx330003579; Sat, 23 Apr 2016 16:59:03 +0200 (CEST) (envelope-from tijl@coosemans.org) Date: Sat, 23 Apr 2016 16:59:02 +0200 From: Tijl Coosemans To: Manish Jain Cc: freebsd-questions@freebsd.org Subject: Re: Does HP DeskJet 1112 work with lpd on FreeBSD 10.2 amd64 ? Message-ID: <20160423165902.29d9950c@kalimero.tijl.coosemans.org> In-Reply-To: References: <20160420112203.3244f4ea@kalimero.tijl.coosemans.org> <20160423143300.40d7c478@kalimero.tijl.coosemans.org> 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.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 15:00:19 -0000 On Sat, 23 Apr 2016 19:40:28 +0530 Manish Jain wrote: > On 04/23/16 18:03, Tijl Coosemans wrote: >> On Sat, 23 Apr 2016 17:47:33 +0530 Manish Jain wrote: >>> On 04/20/16 14:52, Tijl Coosemans wrote: >>>> On Tue, 19 Apr 2016 18:42:01 +0530 Manish Jain wrote: >>>>>> CUPS works nice for many years on my FreeBSD systems, actually CURRENT. >>>>>> Why you can't get it to do anything on your system? matthias >>>>> Thanks for responding. So my question becomes "Has anyne got HP DeskJet >>>>> 1112 to work with CUPS on a FreeBSD 10.2 amd64 box ?" >>>> You need to install print/hplip. Then you can either use the graphical >>>> setup tool HP Device Manager, or the CUPS web interface at >>>> http://localhost:631/. If you use the CUPS interface you need to select >>>> the printer model at some point. Your printer will be listed as >>>> "HP Deskjet 1110 Series, hpcups 3.16.2". >>> This is what I get when I try to open up the cups web interface in my >>> browser even after installing apache24 : >>> >>>> Chromium's connection attempt to*localhost*was rejected > >> What could I be missing here ? hplip package was installed, along with >>> all its dependencies. >>> >>> This is what I get in dmesg : >>> >>> ulpt0: on usbus2 >>> ulpt0: using bi-directional mode >>> >>> So the printer is being detected, just as you stated. A little bit more >>> help, and I could fire up my printout page. Perhaps something to do with >>> httpd.conf ? Or perhaps /usr/local/etc/cups/cupsd.conf ? >> Is the CUPS daemon actually running? Add cupsd_enable="YES" to /etc/rc.conf >> and run 'service cupsd start'. Also, CUPS uses its own http server so you >> don't need Apache. > > Thanks for replying. > > My /etc/rc.conf does have : > > cupsd_enable="YES" > > So I presume cupsd is getting started at boot time. > > This is what I have in /usr/local/etc/cups/cupsd.conf : I suspect this is for an older version of CUPS. Try renaming this file for now and copy cupsd.conf.sample (in the same directory) to cupsd.conf. Then restart cupsd using 'service cupsd restart'. If that works you can enable printer sharing as documented here: https://www.cups.org/documentation.php/doc-2.1/sharing.html From owner-freebsd-questions@freebsd.org Sat Apr 23 15:29:21 2016 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 C545AB195E7 for ; Sat, 23 Apr 2016 15:29:21 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from avasout07.plus.net (avasout07.plus.net [84.93.230.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 372311F39 for ; Sat, 23 Apr 2016 15:29:20 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from curlew.milibyte.co.uk ([80.229.31.82]) by avasout07 with smtp id lrVA1s0021mJoLY01rVBYd; Sat, 23 Apr 2016 16:29:11 +0100 X-CM-Score: 0.00 X-CNFS-Analysis: v=2.1 cv=QqujpgGd c=1 sm=1 tr=0 a=cd0K7rcWwnZFf6xQxRobyA==:117 a=cd0K7rcWwnZFf6xQxRobyA==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=kj9zAlcOel0A:10 a=kziv93cY1bsA:10 a=pGLkceISAAAA:8 a=81MeYnvjy3Jm1pB2S1QA:9 a=CjuIK1q_8ugA:10 a=Dk2oHeJtc58A:10 a=9z9xzJy2P04A:10 Received: from curlew.lan ([192.168.1.13]) by curlew.milibyte.co.uk with esmtp (Exim 4.86_2) (envelope-from ) id 1atzUc-0001bB-7c; Sat, 23 Apr 2016 16:29:10 +0100 Date: Sat, 23 Apr 2016 16:29:10 +0100 From: Mike Clarke Cc: Ben Woods , User Questions Message-ID: <20160423162910.7cd2ede2@curlew.lan> In-Reply-To: References: X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) MIME-Version: 1.0 X-SA-Exim-Connect-IP: 192.168.1.13 X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on curlew.lan X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, MISSING_HEADERS autolearn=no autolearn_force=no version=3.4.1 Subject: Re: Sane way to resolve potential conflicts in the system Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on curlew.milibyte.co.uk) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 15:29:21 -0000 On Sat, 23 Apr 2016 15:00:10 +0300 Odhiambo Washington wrote: > I believe that explains it. I should plan a portupgrade -a one of these > days I suppose. You also need to make sure your ports tree is up to date first. -- Mike Clarke From owner-freebsd-questions@freebsd.org Sat Apr 23 15:42:03 2016 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 1B507B19CE6 for ; Sat, 23 Apr 2016 15:42:03 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from BLU004-OMC4S5.hotmail.com (blu004-omc4s5.hotmail.com [65.55.111.144]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D073F1714 for ; Sat, 23 Apr 2016 15:42:02 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from BLU436-SMTP13 ([65.55.111.136]) by BLU004-OMC4S5.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Sat, 23 Apr 2016 08:40:54 -0700 X-TMN: [f+rkY+Uba5r9ImMf8ueZoDvwyRO3/Te1] X-Originating-Email: [carmel_ny@outlook.com] Message-ID: Date: Sat, 23 Apr 2016 11:40:52 -0400 From: Carmel To: freebsd-questions@freebsd.org Subject: Re: Sane way to resolve potential conflicts in the system In-Reply-To: <20160423162910.7cd2ede2@curlew.lan> References: <20160423162910.7cd2ede2@curlew.lan> Organization: Seibercom NET X-Mailer: Claws Mail 3.13.2-dirty (GTK+ 2.24.28; i686-w64-mingw32) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Apr 2016 15:40:54.0486 (UTC) FILETIME=[85ACEF60:01D19D76] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 15:42:03 -0000 On Sat, 23 Apr 2016 16:29:10 +0100, Mike Clarke stated: >On Sat, 23 Apr 2016 15:00:10 +0300 >Odhiambo Washington wrote: > >> I believe that explains it. I should plan a portupgrade -a one of >> these days I suppose. > >You also need to make sure your ports tree is up to date first. Try doing a "portupgrade -af". That should ensure all of your ports are linked to the correct libraries. -- Carmel From owner-freebsd-questions@freebsd.org Sat Apr 23 16:02:55 2016 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 6054AB1A3A3 for ; Sat, 23 Apr 2016 16:02:55 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ECFA010C9 for ; Sat, 23 Apr 2016 16:02:54 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: by mail-wm0-x22f.google.com with SMTP id n3so67343515wmn.0 for ; Sat, 23 Apr 2016 09:02:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=UovqVBhYbbiW/LAClbgC2sf2M1d1LKAoEVwhXWw+LOs=; b=mSdd9UVs6Fr6Xn1yqaEN2TIvj4iULKPux4DVCcdYILwuPTXPQIOKazCINX3WmfrmKE Xi5WRZC1XO1XvyfQ+FoSvTXHFqRBkJkr6IPNJq7tK8s200nD1Zb9uwTaUwpfztFo/m8o ig2JFGnySnj/pdJoikjzSCjz2sl9IHgsRLMisZjzgFqIV2ETdNXKWYXqU3NynF6WL2MU f4YKcNdHBf4QzjOvhAPyJ/Vyam0ubQfOSiqgwETjDWGHhPFc18W47ajZpRHh/h9ECyjG F/bWZZRn5xkAO/rWCq0svxJl2v3KP5iVwwVW8Kc+CQhA96iv2hcfyt4y0/jLbNwnvlTj c4Sg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=UovqVBhYbbiW/LAClbgC2sf2M1d1LKAoEVwhXWw+LOs=; b=kOKEQjZZNolkC5IlL5vI1BTcCtez5EK2/nolblIiur+N8I0oA8zCQifdfenNI7/mhY qX53wSss2A8t/jiGxpl2DThN9RALy6pxbBp8tTADpQXV5glA0bMAISK/53yLbPvbKZwD b7bp1mj58VsBh7LtyfbGHr8LG1qwnja6OZaOR4VGsHiSyzSpG8n5Hdw0ho9czVslGImU yCs067AbYwFNbFJeHq0qfmBDH9FKahzvZ0RcYKdMoDb0zF3Zll/yrnJURcA2q8l0fKiJ TWAthNwZxcmhfogCFsU8DxHTu0EZ2Jh04XArEzAkgcmAI9BbO+kTUVUIxbntLKyQauwT 5AXQ== X-Gm-Message-State: AOPr4FWnVhoX16GP49JwOHE9cTHeI6AKtKLEZrVUGHyjakdg1EIM7bt1CWBiow9uG6NhCloGuBxhOBLlQeVALA== X-Received: by 10.28.73.66 with SMTP id w63mr3281228wma.53.1461427373510; Sat, 23 Apr 2016 09:02:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.103.233 with HTTP; Sat, 23 Apr 2016 09:02:13 -0700 (PDT) In-Reply-To: References: <20160423162910.7cd2ede2@curlew.lan> From: Odhiambo Washington Date: Sat, 23 Apr 2016 19:02:13 +0300 Message-ID: Subject: Re: Sane way to resolve potential conflicts in the system To: Carmel Cc: User Questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 16:02:55 -0000 On 23 April 2016 at 18:40, Carmel wrote: > On Sat, 23 Apr 2016 16:29:10 +0100, Mike Clarke stated: > > >On Sat, 23 Apr 2016 15:00:10 +0300 > >Odhiambo Washington wrote: > > > >> I believe that explains it. I should plan a portupgrade -a one of > >> these days I suppose. > > > >You also need to make sure your ports tree is up to date first. > > Try doing a "portupgrade -af". That should ensure all of your ports are > linked to the correct libraries. > > -- > Carmel > I will need to look into this because I use a mixture of portupgrade and pkg on this system. Scary? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft." From owner-freebsd-questions@freebsd.org Sat Apr 23 16:25:19 2016 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 228A1B1A90E for ; Sat, 23 Apr 2016 16:25:19 +0000 (UTC) (envelope-from lokadamus@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 788101F50 for ; Sat, 23 Apr 2016 16:25:18 +0000 (UTC) (envelope-from lokadamus@gmx.de) Received: from [192.168.0.143] ([95.91.224.46]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0Mb7pT-1b8enx41cp-00Kiup; Sat, 23 Apr 2016 18:25:07 +0200 Subject: Re: FreeBSD Crashes Intermittently !! To: shahzaib mushtaq References: <56E2E9AC.1040902@gmx.de> <33444.128.135.52.6.1457712900.squirrel@cosmo.uchicago.edu> <56E2F586.9000108@gmx.de> <5715DF0F.4090808@gmx.de> <5715EBDA.10907@gmx.de> <57161B95.9020802@gmx.de> Cc: freebsd-questions@freebsd.org, galtsev@kicp.uchicago.edu From: "lokadamus@gmx.de" Message-ID: <571BA1E1.5020809@gmx.de> Date: Sat, 23 Apr 2016 18:25:05 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:pYSC0VGAh3TG689t+KWo0fGV1fEu7HVFwWfsCfftXWwNkjlseQm KG6/1BnrgmOq1JJi605ULsczQHOSjXQ9sMo/EzA4TcuUanW8kAN8q/bpjSBKjM14xlvBJO6 aWAwoSJ1Tp5jh9jX/YABylOjSP0YUiodvtC7VNPI7p9oj6un7F3P//PJb3uru9DLQNz/dJy 5S+TYwkcs+RuYWUwzoNcQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:gHjbltdETlU=:hgnf07ZBE7QOeFnhLPp5aH /E39MwtMvNRSjVnC3bj+8y/LdhvYfQclzGv1Vu3Tld/nQQvf9TRWdzrRO+IkCeI3bY04IiNAB uGw+IvD0c4JPzNPyNuVan8lD/l9E8bKet/PQygeaKZOHZskGhL/YJ2g0+sEtSkpfjtVc8WwFV M9j3IHmtAOA3Kyvud/lw4mvWAXEJHi0k3pqKUm9nDSH2FM5FYykPFAG5nu90usF0nP0+Yd+eT +7HHRU4JP4+tKzQQUkkh9vtbfWTyu7IFRkZD4lB9jgJltMr+KRl7WkB0kQ/7ElhDweeB1Ybfc uie9r+ObKRiOR5a8K6zvs/fPPmDQusq06Hqb39ycShxLfkg2MSDGy+LaiqLpgY4NMw5j8jXog 2LIMyW+ChepTIPa65mK8Kkvgtra4yUWJ0m5ijPBNqXEiqlhbmQk1rgXpp/heio0XkwcaZxrFe Xf4WvuCgTDjqxOovUn39X6xRi/svSuHiA6cq7E9uKi3EPzewYwn5BWHR87MitP4S6eUJRLckm cDlLkyXXApfZ/Vr+EoWGckHx1vXIvSrb0yXI/FSyC6RTYjVIsvdcpvWnRxF13npJdOTw2b8Vw jjAT0rQTjyUyEhu28d7n9Mgc19AtzIAsLYrbVXbcLyeXfcl5tuqNCcHJ0MNr/bX/iFKeo7LO0 gc50aqQuX/0Mff/YxUOvuBZItodjK7tvKHHtHgyirl5EVhfhHM6n690lauP5U+ELi+fp2cGU8 wMbQ/xTLKsVqS7qs6G9g4oco0wBvx5YoamHFJMcDxnUthBKhpiwvzYHSsMN1y40HkrRJDGszp tkNIb1yAG40VZNglkLM4rBVywJlbw== X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 16:25:19 -0000 Hi, Temp looks ok, but is the server working hard? I think about to disable core 22 and 23, but found your older mails and see, that different cores makes this error. http://pastebin.com/baShWuMP <-- from now http://pastebin.com/042SJ11c <-- 9th march https://lists.freebsd.org/pipermail/freebsd-current/2016-January/059148.html <-- januar I'm confused. Regards On 04/19/16 13:56, shahzaib mushtaq wrote: > Hi, > > Currently 2 x ffmpeg processes are running and the temp is : > > http://prntscr.com/au4wrm > > Well, it looks like restart is not necessary for microcode, you can simply > start microcode using command "service microcode_update start". > > Regards. > > On Tue, Apr 19, 2016 at 4:50 PM, lokadamus@gmx.de wrote: > >> Yes, this is the port. I tested it on my old system. >> After reboot it will start /usr/local/etc/rc.d/microcode-update and show >> a little message. >> My system is too old for an update. >> >> I'm wondering. i've never heard that lower 80w are protecting for >> overheating. >> Can you test this? >> >> http://www.cyberciti.biz/faq/freebsd-determine-processor-cpu-temperature-command/ >> >> On 04/19/16 13:24, shahzaib mushtaq wrote: >>> Hi, >>> >>> Can we use following freebsd guide to update microcode ? : >>> >>> Install sysutils/devcpu-data >>> >> , >>> then add: >>> >>> microcode_update_enable="YES" >>> >>> >>> ===================================================== >>> >>> https://www.freebsd.org/doc/faq/compatibility-processors.html >>> >>> On Tue, Apr 19, 2016 at 1:40 PM, shahzaib mushtaq >> >>> wrote: >>> >>>> Hi, >>>> >>>> We don't think its related to heat because L5640 only use 60W. Can we >>>> update microcode on FreeBSD? Because intel has not stated this OS when >>>> performing microcode update. >>>> >>>> Regards. >>>> >>>> On Tue, Apr 19, 2016 at 1:27 PM, lokadamus@gmx.de >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> I think about the error lines: >>>>> Hardware event. This is not a software error. >>>>> CPU 23 BANK 5 >>>>> MISC 0 ADDR 805613c60 >>>>> MCG status:MCIP >>>>> STATUS be00000000800400 MCGSTATUS 4 >>>>> .... >>>>> Hardware event. This is not a software error. >>>>> CPU 22 BANK 5 >>>>> >>>>> https://en.wikipedia.org/wiki/Machine-check_exception >>>>> >>>>> Looks like a hardware problem from the second cpu. >>>>> Thinks, what can be done: >>>>> - Is it possible to read cpu heat infos from bios? >>>>> - Disable HTT and look, if the error comes again >>>>> - Remove the second cpu and look, if ... >>>>> - Install microcode updates and hope, it will fix it >>>>> >>>>> Intel offers for many CPUs an microcode update. >>>>> >>>>> >> https://downloadcenter.intel.com/download/25512/Linux-Processor-Microcode-Data-File?v=t >>>>> >>>>> Can you test a cpu in another system? >>>>> https://www.freebsd.org/cgi/ports.cgi?query=cpuburn&stype=all >>>>> >>>>> >>>>> Regards >>>>> >>>>> On 04/19/16 09:35, shahzaib mushtaq wrote: >>>>>> Hi, sorry for the mistake, cpus are : >>>>>> >>>>>> 2 x Intel(R) Xeon(R) CPU L5640 @ 2.27GHz5640 (12 cores, 24 threads) >>>>>> >>>>>> On Tue, Apr 19, 2016 at 12:32 PM, lokadamus@gmx.de >>>>> wrote: >>>>>> >>>>>>> On 04/18/16 16:28, shahzaib mushtaq wrote: >>>>>>>> Hi again, got back after a long time. So yes, we've move to new Dell >>>>> R510 >>>>>>>> Hardware now. Here is the specs : >>>>>>>> >>>>>>>> DELL R510 >>>>>>>> 2 x L5520 >>>>>>>> 64GB RAM >>>>>>>> 12x3TB Raid stripping+mirroring (HBA LSI-9211-fw version 19.00) >>>>>>>> FreeBSD cw009.tunefiles.com 10.2-RELEASE-p14 FreeBSD >> 10.2-RELEASE-p14 >>>>>>> #0: >>>>>>>> Wed Mar 16 20:46:12 UTC 2016 >>>>>>>> root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC >>>>>>>> amd64 >>>>>>>> >>>>>>>> After 9days of uptime, server again got crashed with following error >>>>> in >>>>>>>> crash log : >>>>>>>> >>>>>>>> http://pastebin.com/baShWuMP >>>>>>>> >>>>>>>> I am so much depressed now, there's much pressure on me from my >>>>> company. >>>>>>> Please >>>>>>>> help us resolving this crash issue . :( >>>>>>> Which CPU Model is installed? Is it one or more? >>>>>>> >>>>>>> There where some microcode updates for some models. >>>>>>> >>>>>>> Greeting >>>>>>> >>>>>> _______________________________________________ >>>>>> 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 Sat Apr 23 16:28:29 2016 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 76579B1A9C9 for ; Sat, 23 Apr 2016 16:28:29 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from BLU004-OMC4S5.hotmail.com (blu004-omc4s5.hotmail.com [65.55.111.144]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 362DE1046 for ; Sat, 23 Apr 2016 16:28:28 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from BLU436-SMTP216 ([65.55.111.136]) by BLU004-OMC4S5.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Sat, 23 Apr 2016 09:28:27 -0700 X-TMN: [BHosc1Xbheu9AlwAZ2Fq/hlxNzAUcf92] X-Originating-Email: [carmel_ny@outlook.com] Message-ID: Date: Sat, 23 Apr 2016 12:28:24 -0400 From: Carmel To: freebsd-questions@freebsd.org Subject: Re: Sane way to resolve potential conflicts in the system In-Reply-To: References: <20160423162910.7cd2ede2@curlew.lan> Organization: Seibercom NET X-Mailer: Claws Mail 3.13.2-dirty (GTK+ 2.24.28; i686-w64-mingw32) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Apr 2016 16:28:27.0070 (UTC) FILETIME=[29F2B5E0:01D19D7D] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 16:28:29 -0000 On Sat, 23 Apr 2016 19:02:13 +0300, Odhiambo Washington stated: >I will need to look into this because I use a mixture of portupgrade >and pkg on this system. Scary? That is one of the reasons I avoid packages. I have several ports that require custom configurations, such as Postfix, Dovecot and a few others. It just doesn't pay for me to mix packages and ports. There just isn't any upside. The package system is just to juvenile right now. Until it matures, I will stay with ports. -- Carmel From owner-freebsd-questions@freebsd.org Sat Apr 23 17:01:47 2016 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 27DFFB1A348 for ; Sat, 23 Apr 2016 17:01:47 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E6ABE16EF for ; Sat, 23 Apr 2016 17:01:46 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de (port-92-195-199-72.dynamic.qsc.de [92.195.199.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id 0FB7724D7E; Sat, 23 Apr 2016 19:01:37 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id u3NH1aMr002131; Sat, 23 Apr 2016 19:01:36 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sat, 23 Apr 2016 19:01:36 +0200 From: Polytropon To: Manish Jain Cc: freebsd-questions@freebsd.org Subject: Re: Does HP DeskJet 1112 work with lpd on FreeBSD 10.2 amd64 ? Message-Id: <20160423190136.e92c98e3.freebsd@edvax.de> In-Reply-To: References: <20160420112203.3244f4ea@kalimero.tijl.coosemans.org> <20160423143300.40d7c478@kalimero.tijl.coosemans.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-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 17:01:47 -0000 On Sat, 23 Apr 2016 19:40:28 +0530, Manish Jain wrote: > My /etc/rc.conf does have : > > cupsd_enable="YES" > > So I presume cupsd is getting started at boot time. Don't presume. Verify. :-) > This is what I have in /usr/local/etc/cups/cupsd.conf : > > LogLevel info > > # Administrator user group... > SystemGroup wheel > > # Listen for connections on Port 631. > Port 631 > #Listen localhost:631 > Listen /var/run/cups.sock Those lines should probably be the following: Listen localhost:631 Listen /var/run/cups.sock That's probably the reason why you cannot access the CUPS web interface. Keep in mind there are also CLI tools: lpadmin, cupsenable, cupsaccept and so on. I got a HP Deskjet F380 all-in-one working with CUPS few years ago, and all components (even the scanner) work. Make sure CUPS is actually really running. There's also a /var/log/cups directory with log files where you can check the events. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Sat Apr 23 18:21:18 2016 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 4CAEFB1A4D8 for ; Sat, 23 Apr 2016 18:21:18 +0000 (UTC) (envelope-from ghappar@tofino.directrouter.com) Received: from tofino.directrouter.com (tofino.directrouter.com [72.249.106.68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 342981FD5 for ; Sat, 23 Apr 2016 18:21:18 +0000 (UTC) (envelope-from ghappar@tofino.directrouter.com) Received: from ghappar by tofino.directrouter.com with local (Exim 4.86_1) (envelope-from ) id 1au1lh-0000zC-Oa for freebsd-questions@freebsd.org; Sat, 23 Apr 2016 12:54:57 -0500 To: freebsd-questions@freebsd.org Subject: Support : Account need to update X-PHP-Script: ghapparel.com/media/w.php for 105.101.42.53 From: Service Inc Message-Id: Date: Sat, 23 Apr 2016 12:54:57 -0500 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - tofino.directrouter.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [2334 32008] / [47 12] X-AntiAbuse: Sender Address Domain - tofino.directrouter.com X-Get-Message-Sender-Via: tofino.directrouter.com: authenticated_id: ghappar/primary_hostname/system user X-Authenticated-Sender: tofino.directrouter.com: ghappar X-Source: X-Source-Args: X-Source-Dir: MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 18:21:18 -0000 From owner-freebsd-questions@freebsd.org Sat Apr 23 18:37:39 2016 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 418E0B1AB17 for ; Sat, 23 Apr 2016 18:37:39 +0000 (UTC) (envelope-from odhiambo@gmail.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 CD44B1CA5 for ; Sat, 23 Apr 2016 18:37:38 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: by mail-wm0-x22b.google.com with SMTP id v188so54658475wme.1 for ; Sat, 23 Apr 2016 11:37:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yeKywRF4wyjzyer6QZt2gvEjM6m1c7EBVaSuYJ8YsEA=; b=Nqgsulm7c6ZBX8SJAjY5lytKzNGb6lafMjOZ91L4e6jrSkvp5CwT7pWArJmmRU5EwM 6o9R4cTvZmBHoxgaR7WhViCLfKc5OqGgqs7jE6MamQ0+xpjW13hobJJQGO3AMQG5lMeG FsNmB7hiHxBmBocRV6BZqDY9X/2t1nV3Rv8rVQz1TX1+vWjQf7360ZVu481/FM4yFNV+ ktFRAf0Vwj0+jf5GexoHaWlw7oxMFdrK940OKsfrp7ZiHS+ALrp2oEVJ8BUS+MO6UWoE b4WBNlB4ziKaQHNes+cqPcO9DaY9j848bxJ01KN4pZR9CijQI+OX1Xvs6EO3DGEC7nnq l3Sw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=yeKywRF4wyjzyer6QZt2gvEjM6m1c7EBVaSuYJ8YsEA=; b=m6ITvnGqXSG6+giNW3wFQlEDEnRhTNpfCyKDeAyECmqGdsa0APeuE8hKSS/nG/7y9p UwpynFwyyqRP3eksxwi2h7GRdNBgyjFwRYolMKWld6nbw/hRNIFmzYLtvuetYBgS87o7 yjkiTk8gj4b9gIVaTg4yeBAkSp3B7nz0waf2B7CgINyhQ+OQRpVxSS0ZTBFDPPWwwFu4 mjscFfNWktNopfzHlbDRqKS5wZZbUXHaOxYotdghoAqDMgl3soECvawH5E0qviKN23hl F2w4u326H5jzJWOa1ENxMTU81RJ70d9nlC4/VdhuP+vUY/imeMcnmT3M/SQoKyKyYTlU 5aLQ== X-Gm-Message-State: AOPr4FWWPczj/KGtuc8TrulVEs/220AcAsdtNPjJ7Wjvfm4ZcVJFpRheiwtIncnbVzTJGBsOcB7+LQ8eTGs8+A== X-Received: by 10.194.231.196 with SMTP id ti4mr28760352wjc.41.1461436656270; Sat, 23 Apr 2016 11:37:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.103.233 with HTTP; Sat, 23 Apr 2016 11:36:56 -0700 (PDT) In-Reply-To: References: <20160423162910.7cd2ede2@curlew.lan> From: Odhiambo Washington Date: Sat, 23 Apr 2016 21:36:56 +0300 Message-ID: Subject: Re: Sane way to resolve potential conflicts in the system To: Carmel Cc: User Questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 18:37:39 -0000 On 23 April 2016 at 19:28, Carmel wrote: > On Sat, 23 Apr 2016 19:02:13 +0300, Odhiambo Washington stated: > > >I will need to look into this because I use a mixture of portupgrade > >and pkg on this system. Scary? > > That is one of the reasons I avoid packages. I have several ports that > require custom configurations, such as Postfix, Dovecot and a few > others. It just doesn't pay for me to mix packages and ports. There > just isn't any upside. The package system is just to juvenile right now. > Until it matures, I will stay with ports. > > I wouldn't say it's juvenile, but when it doesn't give me the option to customize (like make config) then I am afraid - very afraid - of it. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft." From owner-freebsd-questions@freebsd.org Sat Apr 23 20:49:43 2016 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 7E94AB1ABFE for ; Sat, 23 Apr 2016 20:49:43 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DEFE142A for ; Sat, 23 Apr 2016 20:49:42 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (dynamic-216-186-226-44.knology.net [216.186.226.44] (may be forged)) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id u3NKnZv1022005 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Sat, 23 Apr 2016 15:49:36 -0500 Subject: Re: Sane way to resolve potential conflicts in the system References: <20160423162910.7cd2ede2@curlew.lan> Cc: User Questions From: "William A. Mahaffey III" Message-ID: <9ed38de6-0089-9645-9798-7cdf767d3047@hiwaay.net> Date: Sat, 23 Apr 2016 15:55:05 -0453.75 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 20:49:43 -0000 On 04/23/16 13:43, Odhiambo Washington wrote: > On 23 April 2016 at 19:28, Carmel wrote: > >> On Sat, 23 Apr 2016 19:02:13 +0300, Odhiambo Washington stated: >> >>> I will need to look into this because I use a mixture of portupgrade >>> and pkg on this system. Scary? >> That is one of the reasons I avoid packages. I have several ports that >> require custom configurations, such as Postfix, Dovecot and a few >> others. It just doesn't pay for me to mix packages and ports. There >> just isn't any upside. The package system is just to juvenile right now. >> Until it matures, I will stay with ports. >> >> > I wouldn't say it's juvenile, but when it doesn't give me the option to > customize (like make config) then I am afraid - very afraid - of it. > > > Packages necessarily don't give you that option. They aren't supposed to. You accept whatever options the builder/maintainer selected & install/upgrade. Where it might take hours to rebuild a bunch of ports, it often takes just a few min. to install/upgrade packages. You pick your option (ports or packages) & (hopefully) are happy w/ it. I maintain this box w/ packages almost exclusively, except for flash support in the browsers, which must be compiled up in ports due to licensing issues. When I was getting started w/ FreeBSD, summer of 2014, I built iceweasel in ports per list advice, took 5 1/2 hrs. (!!!!!). I upgraded it a few weeks later w/ pkg, took less than 30 sec. -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr. From owner-freebsd-questions@freebsd.org Sat Apr 23 21:42:30 2016 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 17721B1A71C for ; Sat, 23 Apr 2016 21:42:30 +0000 (UTC) (envelope-from ekarkkai@pp.htv.fi) Received: from welho-filter1.welho.com (welho-filter1.welho.com [83.102.41.23]) by mx1.freebsd.org (Postfix) with ESMTP id C771E1D21 for ; Sat, 23 Apr 2016 21:42:29 +0000 (UTC) (envelope-from ekarkkai@pp.htv.fi) Received: from localhost (localhost [127.0.0.1]) by welho-filter1.welho.com (Postfix) with ESMTP id 26FAB29A9 for ; Sun, 24 Apr 2016 00:42:21 +0300 (EEST) X-Virus-Scanned: Debian amavisd-new at pp.htv.fi Received: from welho-smtp1.welho.com ([IPv6:::ffff:83.102.41.84]) by localhost (welho-filter1.welho.com [::ffff:83.102.41.23]) (amavisd-new, port 10024) with ESMTP id 5YYXaoynKlQP for ; Sun, 24 Apr 2016 00:42:20 +0300 (EEST) Received: from zero.my.domain (87-100-138-79.bb.dnainternet.fi [87.100.138.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by welho-smtp1.welho.com (Postfix) with ESMTPS id EEF27C4 for ; Sun, 24 Apr 2016 00:42:19 +0300 (EEST) Received: from thunderbolt.my.domain (thunderbolt.my.domain [10.192.168.30]) by zero.my.domain (8.15.2/8.15.2) with ESMTPS id u3NLg6VN076439 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Sun, 24 Apr 2016 00:42:11 +0300 (EEST) (envelope-from ekarkkai@pp.htv.fi) Received: from thunderbolt.my.domain (localhost [127.0.0.1]) by thunderbolt.my.domain (8.15.2/8.15.2) with ESMTPS id u3NLg64G016217 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sun, 24 Apr 2016 00:42:06 +0300 (EEST) (envelope-from ejk@thunderbolt.my.domain) Received: (from ejk@localhost) by thunderbolt.my.domain (8.15.2/8.15.2/Submit) id u3NLg5UA016216 for freebsd-questions@freebsd.org; Sun, 24 Apr 2016 00:42:05 +0300 (EEST) (envelope-from ejk) Date: Sun, 24 Apr 2016 00:42:05 +0300 From: Esa Karkkainen To: freebsd-questions@freebsd.org Subject: Re: Storage cluster advise, anybody? Message-ID: <20160423214205.GA1117@pp.htv.fi> Mail-Followup-To: Esa Karkkainen , freebsd-questions@freebsd.org References: <29462.128.135.52.6.1461352625.squirrel@cosmo.uchicago.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <29462.128.135.52.6.1461352625.squirrel@cosmo.uchicago.edu> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 21:42:30 -0000 On Fri, Apr 22, 2016 at 02:17:05PM -0500, Valeri Galtsev wrote: > I would like to ask everybody: what would you advise to use as a storage > cluster, or as a distributed filesystem. I ran into this blog post some time ago. http://bryanapperson.com/blog/the-definitive-guide-ceph-cluster-on-raspberry-pi/ The software defined storage in question is Ceph. http://ceph.com/ceph-storage/ I do not know if it runs on FreeBSD, but it looks like the source code is buildable on AIX, Solaris and on number of Linux distros. Regards, Esa -- "In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move." -- Douglas Adams 1952 - 2001