From owner-freebsd-questions@freebsd.org Sun Apr 8 06:34:04 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AEB35F870BD; Sun, 8 Apr 2018 06:34:04 +0000 (UTC) (envelope-from mayuresh@kathe.in) Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [217.70.183.196]) (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 201EA6C65F; Sun, 8 Apr 2018 06:34:02 +0000 (UTC) (envelope-from mayuresh@kathe.in) Received: from webmail.gandi.net (unknown [10.200.201.4]) (Authenticated sender: mayuresh@kathe.in) by relay4-d.mail.gandi.net (Postfix) with ESMTPA id 8640CE0009; Sun, 8 Apr 2018 08:33:55 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sun, 08 Apr 2018 12:03:54 +0530 From: Mayuresh Kathe To: Polytropon Cc: freebsd-questions@freebsd.org, owner-freebsd-questions@freebsd.org Subject: Re: swi-pl : minimalist edition Reply-To: mayuresh@kathe.in Mail-Reply-To: mayuresh@kathe.in In-Reply-To: <20180407142728.235d7af2.freebsd@edvax.de> References: <4651cc3af73323df69b574a07eb7dbe2@kathe.in> <20180407142728.235d7af2.freebsd@edvax.de> Message-ID: X-Sender: mayuresh@kathe.in User-Agent: Roundcube Webmail/1.1.2 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Apr 2018 06:34:04 -0000 On 2018-04-07 05:57 PM, Polytropon wrote: > On Sat, 07 Apr 2018 16:10:53 +0530, Mayuresh Kathe wrote: >> i tried sending mail to johans@freebsd.org, failed. > > Maybe try to address the ports team directly? > sure, dang, it never occurred to me. >> i am have been evaluating options to target my expert help system. >> have tinkered with netbsd and openbsd, but didn't feel comfortable. > > That is intended. ;-) 'rotflmao'. :-D >> i liked prolog and was pleasantly surprised to see a port of swi-pl >> under freebsd. >> there's one hitch though, the swi-pl port has too many dependencies. >> would there be some way to _also_ have a minimalist edition of swi-pl? > > That's hard to say... > > The port's description says there are no options to configure, > so I'd guess you cannot get rid of the X dependencies (if you > don't use X). i ended up tinkering with ubuntu 16.0, and guess what, they have a "no x" version in their package repository. so, eliminating 'x' dependencies is possible, similarly, building a small, tight core should be possible too. ~mayuresh From owner-freebsd-questions@freebsd.org Sun Apr 8 08:56:28 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3F42AF90527 for ; Sun, 8 Apr 2018 08:56:28 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7F3FF79701 for ; Sun, 8 Apr 2018 08:56:26 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.30.67]) by mrelayeu.kundenserver.de (mreue004 [212.227.15.167]) with ESMTPA (Nemesis) id 0MbLRw-1eoWYm3t6C-00IiaA; Sun, 08 Apr 2018 10:51:05 +0200 Date: Sun, 8 Apr 2018 10:51:04 +0200 From: Polytropon To: mayuresh@kathe.in Cc: freebsd-questions@freebsd.org Subject: Re: swi-pl : minimalist edition Message-Id: <20180408105104.8c5da199.freebsd@edvax.de> In-Reply-To: References: <4651cc3af73323df69b574a07eb7dbe2@kathe.in> <20180407142728.235d7af2.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-Provags-ID: V03:K1:36L+BCtPUO2AsFT2ntxRxbl+4GDOz+ZmoadOf4b2Zm+zUuVunDO SdaI06mNA+LdnWl6nvtY89zdZHHn6T8xJVN5OH9pEosKspiR0Xrabj76Eyhn2W+freIUte6 zr8KfGXF7AQ8Swym5p+SSNE6YxRfV8WX/OmuDzOicPAUXCDIxO/yoangJ31mEzQwx+AbgwF Vv278rKg5RIJO8sQ9Fs5w== X-UI-Out-Filterresults: notjunk:1;V01:K0:XxwGm4o+KSU=:ouXPCD0rpi3zJLfaxqvwNI vxnXBfd1jcc+g6O9ovMf4MKQAe9qwckSPGBJ7ujMcmZO04nmy1Eux6dEi0ViacouvuxPW+umr ktGHwLNqGY/c/I4pyoqfPG+vvFQzHB5P3pGayD5RGNc1WYS9BIACrh8QYP2N5FsROAhG56gVO fbJD0t5MOryQXO15Zb8zVddVIu0ukLHxHW0zunq2S5NKQUbMHr9lQJLFJTv+wf7lZXKUm7fie HI7pDOXQ+phlPfV4W3/TT8HHaGK5zmeKM9F3okKtwQpKaG4gz2qLHlwgJk5Li7/CIkb7fEwFO 1jGwy2atbH6MiHExWgMEy28AhUbqJKbwxgMflnMfZgE2pAuR0s+4iIJW45QQ/YGfYqCUBpouk x9fk7se0IH0hu3wkg1FrAwm/5SZZd0s9huUhujZtqLZYohe3tYUBpandARPr1bppS6qzOSs9U Iu8xjFu+x2bAq6JVK/bkjaCFbKO6r9p7zMgAg1Rc8om4dYutcyb1S9tn8Wemk8lt/A7pEpXMy 9e1KKXVuc6NLxQpBJFgTtOF02C3/XhUSdJuOXFvrlnFqqhGjNlQJwe2TiA/RJeBukccsVd3Hw 6UZjyNQo2iMiyHtMNetNespg7eCKxdgRtRdpPYo9l/LWug5cMZZuWbkf2bxaj23uWDtQpD/4B IAkjX8G4AYbDLnH7OUbjbM56C2KatwgKnHVfkTwvhbMkGUDeil3Wl9af1F2gLYaOoncDOGEN2 jRDQpKMUfqg95kVJbGPH7uDJRx3pt0XBAgLmmUEBdDdVhfQecX3GSxAY7r0= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Apr 2018 08:56:28 -0000 On Sun, 08 Apr 2018 12:03:54 +0530, Mayuresh Kathe wrote: > On 2018-04-07 05:57 PM, Polytropon wrote: > > On Sat, 07 Apr 2018 16:10:53 +0530, Mayuresh Kathe wrote: > >> i liked prolog and was pleasantly surprised to see a port of swi-pl > >> under freebsd. > >> there's one hitch though, the swi-pl port has too many dependencies. > >> would there be some way to _also_ have a minimalist edition of swi-pl? > > > > That's hard to say... > > > > The port's description says there are no options to configure, > > so I'd guess you cannot get rid of the X dependencies (if you > > don't use X). > > i ended up tinkering with ubuntu 16.0, and guess what, they have > a "no x" version in their package repository. > so, eliminating 'x' dependencies is possible, similarly, building a > small, tight core should be possible too. Great finding! Even though the port itself does not offer the ability to configure it without X, you should be able to at least manually tweak the configuration and see if you can remove the X dependencies. If you succeed, suggest a -without-x11 port (or whatever they are called today) of swi-pl to be published - so it can be installed with "pkg install" on a system with no X. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Sun Apr 8 11:19:38 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4DAF0F9A906 for ; Sun, 8 Apr 2018 11:19:38 +0000 (UTC) (envelope-from kristaps.civkulis@gmail.com) Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AFB817F3F9 for ; Sun, 8 Apr 2018 11:19:37 +0000 (UTC) (envelope-from kristaps.civkulis@gmail.com) Received: by mail-wr0-x232.google.com with SMTP id s18so5508540wrg.9 for ; Sun, 08 Apr 2018 04:19:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:mime-version:content-disposition :user-agent; bh=FbAG6cAGCwRlPURuti4N0Bs2vpqpbkOeCxYzdOZSxXs=; b=TJo9auquHwejdg3ED2fKcO4pmsKcjENohcVlVfgOwW+83o2+JITOhpuArs98cVYan6 O2MBimqlv9tBLQ8LWFDAPJ4xyc7uUiyfQb7cc8MB1IavX53QUAK5hhr5rsIyyfzv1LiD gwWIsDQPy74zmZDjgWQoZk2aX0NyFNOB4aq0ifeaUWqhtQJdQC4sRAaIi9JjpCBfL79x cwCl9IgUDQQpoLBQ3zEvlCJikkA28tDKppEBGcaHwzzqjApaABXlulAMjnQDKSO+nJqu uW/54uWeisEI7wDTGno9hr3C5xoaQ6o2hqqbPLSUq9y460IbW96b2HworVKrHNYAWRka AzDA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition:user-agent; bh=FbAG6cAGCwRlPURuti4N0Bs2vpqpbkOeCxYzdOZSxXs=; b=Vtbt2nHoXQlzGGZWAI0vNSf5NOXYzCKuhWWq2zG3zO/lD8z8ZqGMqugQicqjCzEb4X xINrTNxTidgdYWaM63vNQG/zgS1UFK/5AQBQptPT6+PMLY4Y7XNwpnauM6NkBVGihPLd oSgaqfJdjttn7C9MCt/W1gNpB5JKl1lbnIwrhxKP0tNiBk1el5dny7ZJbLkfxudEBywQ gL+hMHLTXFciiI/js6ZkfEpX0OnX07q3RDCsjUpu4mexfN9paFkFCz0wN+92J6Xnb9e3 PgS0Fn47Vhwp6h9olZknHoUt10y71/yeNj3XEQuSMTrvqezf091wNfSxtvjxB1I8Keok /wVg== X-Gm-Message-State: ALQs6tBxAU7Ny5XQtYN+fhj5gvdmvbuE+uMzr+pumH7KBJOgFRYryiZL eoeh6b2kiPltEGpVnwPBX/usRmIO X-Google-Smtp-Source: AIpwx49Lb/W8qlkvaUsNgFrzMdq9QEpfIGA11/DdHAEcVlPq3QkE4BorJcLi6RJfei1lZUu54YhKrA== X-Received: by 2002:a19:54cb:: with SMTP id b72-v6mr4193680lfl.33.1523186375778; Sun, 08 Apr 2018 04:19:35 -0700 (PDT) Received: from dankpad.localdomain ([212.3.195.141]) by smtp.gmail.com with ESMTPSA id i89-v6sm2960228lfk.12.2018.04.08.04.19.34 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 08 Apr 2018 04:19:34 -0700 (PDT) Date: Sun, 8 Apr 2018 16:19:14 +0300 From: Kristaps Civkulis To: freebsd-questions@freebsd.org Subject: Error while compiling FreeBSD kernel Message-ID: <20180408131914.GA4329@dankpad.localdomain> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="n8g4imXOkfNTN/H1" Content-Disposition: inline User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Apr 2018 11:19:38 -0000 --n8g4imXOkfNTN/H1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, I have errors while compiling FreeBSD 11 Stable on fresh installation on x86_64 (am64) architecture. After make buildkernel KERNCONF=GENERIC I have the following errors: /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:829:2: error: unknown directive .altmacro ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :3:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :8:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ ... Note that I didn't store source code under /usr/src. I used default GENERIC config file. I attached full error message. Kristaps --n8g4imXOkfNTN/H1 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="output.txt" /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:829:2: error: unknown directive .altmacro ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :3:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :8:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :13:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :18:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :23:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :28:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :33:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :38:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :43:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :48:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :53:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :58:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :63:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :68:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :73:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :78:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :83:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :88:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :93:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :98:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :103:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :108:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :113:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :118:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :123:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :128:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :133:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :138:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :143:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :148:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :153:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ :1:13: error: invalid register name handle_ibrs_%(ll): ^~ :158:2: note: while in macro instantiation ibrs_seq_label %(ll) ^ :2:2: note: while in macro instantiation .rept 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:858:2: note: while in macro instantiation ibrs_seq 32 ^ /usr/home/kristaps/FreeBSD_stable/11/sys/amd64/amd64/support.S:891:2: error: unknown directive .noaltmacro ^ *** Error code 1 Stop. make[2]: stopped in /usr/obj/usr/home/kristaps/FreeBSD_stable/11/sys/GENERIC *** Error code 1 Stop. make[1]: stopped in /usr/home/kristaps/FreeBSD_stable/11 *** Error code 1 Stop. make: stopped in /usr/home/kristaps/FreeBSD_stable/11 --n8g4imXOkfNTN/H1-- From owner-freebsd-questions@freebsd.org Mon Apr 9 05:22:17 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C46EDF80E11 for ; Mon, 9 Apr 2018 05:22:16 +0000 (UTC) (envelope-from info@wadalplastics.xyz) Received: from srvr.wadalplastics.xyz (srvr.wadalplastics.xyz [IPv6:2400:8500:2500:627:163:44:121:122]) (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 31B756FBE3 for ; Mon, 9 Apr 2018 05:22:16 +0000 (UTC) (envelope-from info@wadalplastics.xyz) Received: from authenticated-user (srvr.wadalplastics.xyz [163.44.121.122]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by srvr.wadalplastics.xyz (Postfix) with ESMTPSA id 721F2102237 for ; Mon, 9 Apr 2018 13:22:06 +0800 (+08) MIME-Version: 1.0 Subject: PO#43001677 To: freebsd-questions@freebsd.org From: "Nick Garrido" Date: Sun, 08 Apr 2018 22:22:02 -0700 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Description: Mail message body X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2018 05:22:17 -0000 = My Best Regards, = = Nick L. Garrido = = Blisam Trading Corp. = 2nd Floor, Bldg. 1 Office, Technical & Training Center Governors Drive, Brgy. Sabang, Naic, Cavite Mobile Globe:+63-917-149-0461 / 0927-064-7626 Mobile Sun : 0942-064-7626 Landline : 775-1784 E-mail=FF1Anicasio.garrido@blisam.com = = PO#43001677 Mackenzie.doc~1.5 MBShow Download my message... From owner-freebsd-questions@freebsd.org Mon Apr 9 07:11:54 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A6458F89089; Mon, 9 Apr 2018 07:11:54 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::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 3E7456BAD3; Mon, 9 Apr 2018 07:11:54 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: by mail-it0-x236.google.com with SMTP id r19-v6so9602991itc.0; Mon, 09 Apr 2018 00:11:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=EotH3329C82H2wehW4tudUUhHUMf80OTGnVNiyXynxc=; b=tnDuOA7THbcVFSfgl7VpD2StY9EZnWjUgUD2KXSsZOEs28fqa0yfdGRJrv2AUsg921 Sb0qg7fdsgTWQ4DjSzCGJP5oeEoosGKxBJCfND/2xDFnNRhByfrysgVq4SlYS1iKM/Xi CXupT+aUadldt2fMzQ9nQHPnSoO3vocDeHRJ6oGNf14iduIgdK9MtLbZFoaLjC89P4St PoUjVYMjfwDnBRQ2qigBlHO9GHmZME9+NDtqVTfBIrJMvl5RGjUb8eFcGXF/ujHql/Bp GaacxBCZaZ7OeW5XtpFibTvlGsBgdM0ndJsdnGTP0fZyKGy6SB/Xhgu+kCawUK3RX+9J eYfA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=EotH3329C82H2wehW4tudUUhHUMf80OTGnVNiyXynxc=; b=HI3WrKSQBAWp9BTEJVfMqcVXN1hMzJ9ZFXCKVPovdZGf5NgO4j8i7V3xS6HrhO0LwS 8GNciZhxj/ZFaERZ27SqzUtSFjWOgt4nakG/1EgmOTywx+2tjH4u5xvKE9o2V+TjYeRF vpoyHYz5v3qj85vJv8AhMWOrfFWRkHvteUx9Q4jtGGnn0jjBK1tUHQ6DH+gTTONGjoC/ m/hPsVJIcqhTAP8mUnO++8nEI9vjDBJt0JFUYmi/5oq5sfwMcdA5Bj3MFNz9DWH6nGk3 Q35XDvmTVNGfIbHM1wFcJQ3EV1CaN7PCA7Tp5IyO+ogDi5iCZmI7e8NqM5pJ49nJlAZ1 AszQ== X-Gm-Message-State: ALQs6tDkkAtgF9GiLtrvYSV9UzuG33bm8K/vX0I2NfZgI/LKByDdznyN tnZ6d3mWFMYDc5ZcwdBVCCRgRKDQLGaXmdHcENg= X-Google-Smtp-Source: AIpwx48bNrx8wQanyxXIZrbiUyI7fiUa01dp0/Wb4OjptohrJxgGg2R+RdJOr16aCBovFZDOnQEqiFjk1TVi3A+A81Y= X-Received: by 2002:a24:e147:: with SMTP id n68-v6mr28793043ith.41.1523257913196; Mon, 09 Apr 2018 00:11:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.2.79.215 with HTTP; Mon, 9 Apr 2018 00:11:52 -0700 (PDT) In-Reply-To: References: From: krad Date: Mon, 9 Apr 2018 08:11:52 +0100 Message-ID: Subject: Fwd: Build freebsd 11 stable packages To: freebsd-pkgbase@freebsd.org, FreeBSD Questions Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2018 07:11:55 -0000 Hi should building of freebsd11 base packages still work? I realise pkgbase is probably not going released until 12.something so issues are to be expected, however I used to be able to build 11 fine. Sometime in the last 6 months it stopped (for me anyway), and I was lead to believe that it should only work on 12. However revisiting the issue and reading the project page over the bank holiday, it still seems to indicate it should work with freebsd 11. Am i reading this correct or is the project page out of date? https://wiki.freebsd.org/PkgBase From owner-freebsd-questions@freebsd.org Mon Apr 9 07:32:16 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A4824F8AA41; Mon, 9 Apr 2018 07:32:16 +0000 (UTC) (envelope-from mayuresh@kathe.in) Received: from relay6-d.mail.gandi.net (relay6-d.mail.gandi.net [217.70.183.198]) (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 1C7B376FB2; Mon, 9 Apr 2018 07:32:15 +0000 (UTC) (envelope-from mayuresh@kathe.in) Received: from webmail.gandi.net (unknown [10.200.201.8]) (Authenticated sender: mayuresh@kathe.in) by relay6-d.mail.gandi.net (Postfix) with ESMTPA id 70794C0025; Mon, 9 Apr 2018 09:32:07 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 09 Apr 2018 13:02:06 +0530 From: Mayuresh Kathe To: Polytropon Cc: freebsd-questions@freebsd.org, owner-freebsd-questions@freebsd.org Subject: Re: swi-pl : minimalist edition Reply-To: mayuresh@kathe.in Mail-Reply-To: mayuresh@kathe.in In-Reply-To: <20180408105104.8c5da199.freebsd@edvax.de> References: <4651cc3af73323df69b574a07eb7dbe2@kathe.in> <20180407142728.235d7af2.freebsd@edvax.de> <20180408105104.8c5da199.freebsd@edvax.de> Message-ID: X-Sender: mayuresh@kathe.in User-Agent: Roundcube Webmail/1.1.2 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2018 07:32:16 -0000 On 2018-04-08 02:21 PM, Polytropon wrote: > On Sun, 08 Apr 2018 12:03:54 +0530, Mayuresh Kathe wrote: >> On 2018-04-07 05:57 PM, Polytropon wrote: >> > On Sat, 07 Apr 2018 16:10:53 +0530, Mayuresh Kathe wrote: >> >> i liked prolog and was pleasantly surprised to see a port of swi-pl >> >> under freebsd. >> >> there's one hitch though, the swi-pl port has too many dependencies. >> >> would there be some way to _also_ have a minimalist edition of swi-pl? >> > >> > That's hard to say... >> > >> > The port's description says there are no options to configure, >> > so I'd guess you cannot get rid of the X dependencies (if you >> > don't use X). >> >> i ended up tinkering with ubuntu 16.0, and guess what, they have >> a "no x" version in their package repository. >> so, eliminating 'x' dependencies is possible, similarly, building a >> small, tight core should be possible too. > > Great finding! > > Even though the port itself does not offer the ability to > configure it without X, you should be able to at least > manually tweak the configuration and see if you can remove > the X dependencies. If you succeed, suggest a -without-x11 > port (or whatever they are called today) of swi-pl to be > published - so it can be installed with "pkg install" on > a system with no X. :-) alrighty, i tried, failed, and resorted to asking for advice on the swipl mailing list. i got the following; If you really want to go minimal, just install "SWI-Prolog lite", as described in the link I posted above: http://eu.swi-prolog.org/build/unix.html Follow the instruction under "Doing it in multiple steps" and see if this is good enough. If you use build.templ just add the package names you don't want to the DISABLE_PKGS variable. For example, to skip a bunch of things, including the GUI (xpce): export DISABLE_PKGS="jpl xpce chr cql protobufs odbc ssl RDF semweb" and so on. You can look under packages to see what are the names of the packages. can i now approach the "ports" mailing list with a request to also provide swipl-lite? ~mayuresh From owner-freebsd-questions@freebsd.org Mon Apr 9 10:42:58 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E82C5F9847E for ; Mon, 9 Apr 2018 10:42:57 +0000 (UTC) (envelope-from mgamsjager@gmail.com) Received: from mail-yb0-x230.google.com (mail-yb0-x230.google.com [IPv6:2607:f8b0:4002: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 86E3F7F5F3 for ; Mon, 9 Apr 2018 10:42:57 +0000 (UTC) (envelope-from mgamsjager@gmail.com) Received: by mail-yb0-x230.google.com with SMTP id e5-v6so2807715ybq.13 for ; Mon, 09 Apr 2018 03:42:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=ExNdqWVr3nqiY8UxEasWLNeUG1hFS5K68KTK8zBQuvg=; b=cPaSwBQARlKP94WtW+lwtISxsj3tFS4Jn3IPD9cBAJ4GYo+BIbPGvIfX/QH6MPbNkw IfzjtOuRcwLMI6sMYxurBgP+511BH4rZ/MEivw6TPfuaS16D3F23EzCJ+6V+6P4dtOIn WrlBx7jzTrZo5pAirZudqzXLYe92CRyte7Ob5MxAFPbW3lQDyGht7DbzSM1W5E6Af+Q2 a/MniQmZ0h/IwRH30zxQ6Vm+HTj6aLJkJQVDvMg2V/AbN91V3aXjBQvQHaGc7MiqN7NU JngZsPMPIezlcAdNa/8Y+HoIU5Ldd3X4604sAeNBze0MRy+ArbzNimn8kgXc3Zz5aF2Q UKvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=ExNdqWVr3nqiY8UxEasWLNeUG1hFS5K68KTK8zBQuvg=; b=caXQXlgmhCTjPRz4l/fm1rbVh+ktV2gyCYjs5gb/OZ0W2xbX2NY+Ta7seoHGnj1PCM p3D/ddtWvgotcX57zmf2YUid/OSP1yhb3bHqn5Rn0dY6v2jtJtjhjTSV1yHCXJgEHczJ +7h23OtftlNzFs/6awUa523FUr688ssBxehpfV9nNpujT8ZO6qMzr+og4gFO3rXBI/xM wggbqVxIbuKp2yurfAb0DQLnr5y1ZOguFTUuyObS4fZ3l/JaOPfveTp8OADn1x1E407u GqZjqL+ORPCxoAfR4yul5iVnABDFyC/fcnP1XDHwYVRYQLFCyYGiAzlj0zBYl586jZHu Kcrg== X-Gm-Message-State: AElRT7FueZQF57lKQOl5b3YbD7g5//WgZgyQPYOaPeS90EtJf2gUSnq2 yYyVKvVOGlI+lC+Lzd7jjKObP+gf9JxBo8wIidzFBQ== X-Google-Smtp-Source: AIpwx4+wh8kwtciW6YjRIb4BlikfXsqpDlyy3gSD/ZK+a1VYt9TK2RNi/VBHxIrLQwASspK5cu2zvVpZHdknuZ+oZAU= X-Received: by 2002:a25:6b06:: with SMTP id g6-v6mr18034461ybc.246.1523270576607; Mon, 09 Apr 2018 03:42:56 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:a303:0:0:0:0:0 with HTTP; Mon, 9 Apr 2018 03:42:26 -0700 (PDT) In-Reply-To: <20180406142425.GA4593@jail0199.vps.exonetric.net> References: <201804061418.w36EIN8g011268@scm-men-p0.men.bris.ac.uk> <20180406142425.GA4593@jail0199.vps.exonetric.net> From: Matthias Gamsjager Date: Mon, 9 Apr 2018 12:42:26 +0200 Message-ID: Subject: Re: Dell Precision 3520 laptop - help with dual graphics card To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2018 10:42:58 -0000 > > > Just spoke to Dell support on the phone - > not possible to disable one of the cards via BIOS > in this model. > > So I guess I need to go the X config file route... > > Would still be grateful for any advice. > > Anton > I never got it to work on my XPS 15. But post you xorg,conf anyway. If I remember correctly there is a git repo/script to disable the nvidia card via acpi. So afer that you could try with kms-next From owner-freebsd-questions@freebsd.org Mon Apr 9 10:44:41 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 47C6CF985F3 for ; Mon, 9 Apr 2018 10:44:41 +0000 (UTC) (envelope-from mgamsjager@gmail.com) Received: from mail-yb0-x22f.google.com (mail-yb0-x22f.google.com [IPv6:2607:f8b0:4002: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 D19C88050F for ; Mon, 9 Apr 2018 10:44:40 +0000 (UTC) (envelope-from mgamsjager@gmail.com) Received: by mail-yb0-x22f.google.com with SMTP id p126-v6so2812808ybg.8 for ; Mon, 09 Apr 2018 03:44:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=en5zNrmw1mfSh0KdXONQ2kmpOIc2SjrTHhWSqx/ptWU=; b=cQMlMEm+moPCbc7SBj4IIxYiUEHdxDbml5iCsREwnqIfTjq+OEpj9Nw39Tn6WQtESS RDqI7R1/7LPXoZzGIEDcZUeHmR2vnW/16avxO/jNF0zaxbznqBdQE8RZ04VcYz7BCNlN hpiywVA8ZSmDK5rCDF8qHfuOtW37q/aBb2zPgg4b863OUla97F241sveuYpyCnjvFeUd cRaNbBE8dOUxuKwlPU+eFw59ZLGjZ3ywsbjn8hv0OTfXKqEUgp12olwN8DPzm7E+mPKN 7zBH2u/vdOvTMDrUPDRCdPVxA5oVwgJZ1+ykpXlBfq6H1PuoSV+JJf9yS18PAk7VM7RO eelw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=en5zNrmw1mfSh0KdXONQ2kmpOIc2SjrTHhWSqx/ptWU=; b=Eu+MiRERButPORvN1yIgvP+/7NoOHDkv9yqtapkQeKvEP9m/6eGgmhjQMcY6/P7LDM d3AeWGgLQaI2XkTwWo8vmAuDdjrY2Amjv6FFI7N1A+bAypNZdAfXXjSukKJqSXiJfWgQ m6jggpMsBJPvWUGxi/uY+BS4s7YnOt5NC6afTS+BGQ1BIxsa7iLS0FXsTt39QovY9vvh uiyGxF2S45OKdQrSEZ3L8AgCl+N0M03D19dV6HoAXyuVTYcZJZCnCqsbEk2+BEV7agtz D701NXNGBVl6L9miR5Q7IHJNQ2gt2zGNx9qWNnOi4pHT3ULK3XLGNBZNM2n0SCZcPx/E Vysw== X-Gm-Message-State: ALQs6tC/W+x3hZ+yfBa4rw3fAv162fi7CoPU3QeDy7hwmmDC2FqA+S59 fyK84+MNsIm7YliwubbHdO+OjY1Yp9MpaeO3zOT8ZLiB X-Google-Smtp-Source: AIpwx49HCgo51/dHL0tg0Gog2BQJEJANh/QAvflcln1Kgf0UIrqcLA/yOnpC1ozz/BiDZDrNVlLJDvphF143ZG6vqDg= X-Received: by 2002:a25:aa82:: with SMTP id t2-v6mr19042821ybi.430.1523270679861; Mon, 09 Apr 2018 03:44:39 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:a303:0:0:0:0:0 with HTTP; Mon, 9 Apr 2018 03:44:09 -0700 (PDT) In-Reply-To: References: <201804061418.w36EIN8g011268@scm-men-p0.men.bris.ac.uk> <20180406142425.GA4593@jail0199.vps.exonetric.net> From: Matthias Gamsjager Date: Mon, 9 Apr 2018 12:44:09 +0200 Message-ID: Subject: Re: Dell Precision 3520 laptop - help with dual graphics card To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2018 10:44:41 -0000 found it: https://github.com/ahacking/freebsd-gpu-off On 9 April 2018 at 12:42, Matthias Gamsjager wrote: > >> Just spoke to Dell support on the phone - >> not possible to disable one of the cards via BIOS >> in this model. >> >> So I guess I need to go the X config file route... >> >> Would still be grateful for any advice. >> >> Anton >> > > I never got it to work on my XPS 15. But post you xorg,conf anyway. > > If I remember correctly there is a git repo/script to disable the nvidia > card via acpi. So afer that you could try with kms-next > From owner-freebsd-questions@freebsd.org Mon Apr 9 11:28:42 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 336A0F9B935 for ; Mon, 9 Apr 2018 11:28:42 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from baobab.bilink.net (baobab.bilink.net [212.45.144.44]) by mx1.freebsd.org (Postfix) with ESMTP id C070C783F3 for ; Mon, 9 Apr 2018 11:28:41 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from baobab.bilink.net (localhost [127.0.0.1]) by baobab.bilink.it (Postfix) with ESMTP id 40KSXG19vVz3jYp1 for ; Mon, 9 Apr 2018 13:20:30 +0200 (CEST) Received: from hermes.mcs.it (hermes.mcs.it [192.168.132.21]) by baobab.bilink.it (Postfix) with ESMTP id 40KSXG0NnTz3jYlq for ; Mon, 9 Apr 2018 13:20:30 +0200 (CEST) Received: from mordeus (unknown [192.168.45.6]) by hermes.mcs.it (Postfix) with ESMTP id E4E899A804 for ; Mon, 9 Apr 2018 13:20:29 +0200 (CEST) Date: Mon, 9 Apr 2018 13:20:29 +0200 From: Luciano Mannucci To: freebsd-questions@freebsd.org Subject: Re: Dell Precision 3520 laptop - help with dual graphics card In-Reply-To: <20180406142425.GA4593@jail0199.vps.exonetric.net> References: <201804061418.w36EIN8g011268@scm-men-p0.men.bris.ac.uk> <20180406142425.GA4593@jail0199.vps.exonetric.net> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd10.3) X-Face: 4qPv4GNcD; h<7Q/sK>+GqF4=CR@KmnPkSmwd+#%\F`4yjKO3"C]p'z=(oWRnsYBQGM\5g:4skqQY0NnV'dM:Mm:^/_+I@a"; [-s=ogufdF"9ggQ'=y MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <40KSXG0NnTz3jYlq@baobab.bilink.it> X-Virus-Scanned: PippoLillo, ClamAV using ClamSMTP X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2018 11:28:42 -0000 On Fri, 6 Apr 2018 14:24:25 +0000 Anton Shterenlikht wrote: > Just spoke to Dell support on the phone - > not possible to disable one of the cards via BIOS > in this model. > > So I guess I need to go the X config file route... > > Would still be grateful for any advice. Well, I had a similar problem with my Toshiba Satellite laptop. I burned a Linux "Live" distro (Like Knoppix, though it was another one), booted it and copied the xorg automatic config that was working. I had to wait for the same verion of xorg to be available for freeBSD to see it somehow working... Hope it helps, Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster@sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/ From owner-freebsd-questions@freebsd.org Mon Apr 9 13:07:07 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CA4AEFA2ECE; Mon, 9 Apr 2018 13:07:07 +0000 (UTC) (envelope-from dweimer@dweimer.net) Received: from webmail.dweimer.net (24-240-198-186.static.stls.mo.charter.com [24.240.198.186]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "dweimer.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6BCBC6EAF9; Mon, 9 Apr 2018 13:07:07 +0000 (UTC) (envelope-from dweimer@dweimer.net) Received: from www.dweimer.net (pfSense.dweimer.local [10.9.5.1]) (authenticated bits=0) by webmail.dweimer.net (8.15.2/8.15.2) with ESMTPSA id w39D6xTH058559 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 9 Apr 2018 08:06:59 -0500 (CDT) (envelope-from dweimer@dweimer.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dweimer.net; s=2017.01.31; t=1523279219; bh=LUnmEKgLVXvoJ2ZAbbhXMPBfCY88FJ7OoK11OA2nsdU=; h=Date:From:To:Cc:Subject:Reply-To:In-Reply-To:References; b=S5HZ3bDlQPxG/gDot/N2TMHo9Y1qo+L6zQlIEXrfnzXUE97K42KIa2cpFz6QvO5Wo G8gJqw3/hY43aZI//wVkIUvG3S0je8dn9KjNgMpd9AlS+UWy5r2cHEt1nZlmIG731l Wa0OAcd7YLwZOT6994fhtStj4DFOZ/LU04qFt66DJbMYtqTNXKgr7v2jcmFDHf3su7 F5ejim9bpyHrYgOOQaCsXby9FeqkSz/XbAp0B9jodB8JzScviTtN1DfRmQJGzBcWzs X4eI6KVbDYzWEdU+odzgYxa0U8miV6lzv5k32CQHJPSjIy187a1HcGrPjxdPq4Qj8U A0ab3kR9vDX2A== MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 09 Apr 2018 08:06:53 -0500 From: "Dean E. Weimer" To: FreeBSD Questions Cc: owner-freebsd-questions@freebsd.org Subject: Re: Jail unable to access some network devices Organization: dweimer.net Reply-To: dweimer@dweimer.net Mail-Reply-To: dweimer@dweimer.net In-Reply-To: <7f30fe692d049949bbd74c5d4c136f16@dweimer.net> References: <7f30fe692d049949bbd74c5d4c136f16@dweimer.net> Message-ID: <3a458ec53b672322a65aaa1364f9d697@dweimer.net> X-Sender: dweimer@dweimer.net User-Agent: Roundcube Webmail/1.3.5 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2018 13:07:08 -0000 On 2018-04-06 1:32 pm, Dean E. Weimer wrote: > I am trying to setup some jails on a server utilizing multiple routing > fib tables I have a few jails already running some of them in > different fibs, one in the same fib as the host. But this last one I > added has caused some problems. Its the first one I am trying to build > in this fib. Below is sections from the fib routing setup and the > jail. > > ## Set up the DMZ[1] routing table > # Interface route(s) > setfib 1 route add -net 10.50.0.0/16 -iface lagg0.4 > setfib 1 route add -net 10.52.0.0/16 -iface lagg0.4 > setfib 1 route add -net 172.17.0.0/25 -iface lagg0.900 > # Default route > setfib 1 route add default 10.50.110.9 > > # Default Jail Options > allow.mount.devfs; > mount.devfs; > devfs_ruleset = '4'; > allow.sysvipc; > allow.dying; > exec.start = "/bin/sh /etc/rc"; > exec.stop = "/bin/sh /etc/rc.shutdown"; > exec.consolelog = "/jails/${name}/console.log"; > > proxy2 { > exec.fib=1; > allow.raw_sockets = 1; > ip4.addr = 'lagg0.4|10.50.20.42/16'; > ip4.addr += 'lagg0.4|10.52.20.42/16'; > ip4.addr += 'lagg0.900|172.17.0.5/25'; > } > > The jail can talk to every host on the 172.17.0.0/25 subnet, and can > talk to every hos tin the 10.52.0.0/16 subnet. I can't talk to some > things in the 10.50.0.0/16 subnet though. The 3 devices I can't talk > to also have 10.52.0.0/16 addresses on the same adapter as the > 10.50.0.0/16 I can talk to their 10.52 address but receive an invalid > argument error when attempting to connect via 10.50 address. > > Below the 10.50.20.4 and 10.52.20.4 are the same device, an older > FreeBSD server that this jail is intending to replace. > > root@fbsdhost2:/jails/proxy2 # proxy2 > root@proxy2-temp:/ # ping 10.52.20.4 > PING 10.52.20.4 (10.52.20.4): 56 data bytes > 64 bytes from 10.52.20.4: icmp_seq=0 ttl=64 time=0.749 ms > 64 bytes from 10.52.20.4: icmp_seq=1 ttl=64 time=0.311 ms > ^C > --- 10.52.20.4 ping statistics --- > 2 packets transmitted, 2 packets received, 0.0% packet loss > round-trip min/avg/max/stddev = 0.311/0.530/0.749/0.219 ms > root@proxy2-temp:/ # ping 10.50.20.4 > PING 10.50.20.4 (10.50.20.4): 56 data bytes > ping: sendto: Invalid argument > ping: sendto: Invalid argument > ^C > --- 10.50.20.4 ping statistics --- > 2 packets transmitted, 0 packets received, 100.0% packet loss > root@proxy2-temp:/ # ping 10.50.110.9 > PING 10.50.110.9 (10.50.110.9): 56 data bytes > 64 bytes from 10.50.110.9: icmp_seq=0 ttl=255 time=0.599 ms > 64 bytes from 10.50.110.9: icmp_seq=1 ttl=255 time=0.253 ms > ^C > --- 10.50.110.9 ping statistics --- > 2 packets transmitted, 2 packets received, 0.0% packet loss > round-trip min/avg/max/stddev = 0.253/0.426/0.599/0.173 ms > > root@fbsdhost2:/jails/proxy2 # setfib 1 netstat -rnf inet > Routing tables (fib: 1) > > Internet: > Destination Gateway Flags Netif Expire > default 10.50.110.9 UGS lagg0.4 > 10.50.0.0/16 84:2b:2b:4d:6e:08 US lagg0.4 > 10.52.0.0/16 84:2b:2b:4d:6e:08 US lagg0.4 > 127.0.0.1 lo0 UHS lo0 > 172.17.0.0/25 84:2b:2b:4d:6e:08 US lagg0.90 > > I know it has to be something on the jail configuration, as it doesn't > even attempt to send the traffic to the interface, watched on host > adapter. If I ping this jail address from the other system the echo > requests do show up, on that adapter. Can anyone see anything in the > above configuration that I have missed, or got wrong? I noticed these in the nightly emails over the weekend. +arpresolve: can't allocate llinfo for 10.50.20.4 on lagg0.4 Didn't think to look at the dmesg output for errors last Friday. After searching on that I tried a reboot. The system is now talking to everything. Perhaps something to do with the fact that the main host is getting NTP currently from the devices I was having difficulty connecting to for a while before the other fib routing table was used. Looks like I have a chicken before the egg issue, the host had an arp entry for these devices already assigned to its other interface through a route. when the lagg0.4 interface had the new IP address added for the jail (previously no IP was defined on that interface) the arp entry no longer matched the correct routing interface. Short term defining an IP on the host in that subnet on the adapter will keep it from occurring long term though I may need to find a more secure solution. As this creates a path around the external firewall that is controlling the traffic going from the DMZ to the LAN where the host is located. -- Thanks, Dean E. Weimer http://www.dweimer.net/ From owner-freebsd-questions@freebsd.org Tue Apr 10 06:16:26 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 90A37FA4A77 for ; Tue, 10 Apr 2018 06:16:26 +0000 (UTC) (envelope-from kremels@kreme.com) Received: from mail.covisp.net (www.covisp.net [65.121.55.45]) (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 37FDB6A693 for ; Tue, 10 Apr 2018 06:16:25 +0000 (UTC) (envelope-from kremels@kreme.com) From: "@lbutlr" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Re: I broke my Apache 2.4 install and I need help! Date: Tue, 10 Apr 2018 00:16:17 -0600 References: <20180402204202.GA3145@gmail.com> <20180402213311.GB3145@gmail.com> <22AED507-651D-4FF5-9D3F-73F41F57AC24@kreme.com> <458eb0bf-dbd8-01c2-4eac-96546e61dec1@gmail.com> To: freebsd-questions@freebsd.org In-Reply-To: <458eb0bf-dbd8-01c2-4eac-96546e61dec1@gmail.com> Message-Id: X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2018 06:16:26 -0000 On 2018-04-03 (12:32 MDT), Johan Hendriks = wrote: >=20 > Op 03/04/2018 om 00:56 schreef @lbutlr: >> On 2018-04-02 (16:40 MDT), William Dudley wrote: >> This is what a virtual host looks like for me in apache24. I never = put any hosts into http.conf other than a base name that is actually = unused for web access. Everything is in user/name.conf or = extras/httpd-vhosts.conf >>=20 >> >> ServerName oursite.example.net >> DocumentRoot /usr/local/www/oursite >> SSLEngine on >> SSLCertificateFile = /usr/local/etc/dehydrated/certs/covisp.net/cert.pem >> SSLCertificateKeyFile = /usr/local/etc/dehydrated/certs/covisp.net/privkey.pem >> SSLCertificateChainFile = /usr/local/etc/dehydrated/certs/covisp.net/chain.pem >> SSLProtocol all -SSLv2 -SSLv3 -TLSv1 -TLSv1.1 >> SSLHonorCipherOrder on >> # I am not sure this is needed or best for TLSv1.2, but it works = for us >> SSLCipherSuite = ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:D= H+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS >> Header always set Strict-Transport-Security "max-age=3D15638400; = includeSubdomains;" >> =20 >>=20 > The documentation of apache states that SSLCertificateChainFile is > deprecated and SSLCertificateFile will handle your cert and chain in = one > file. See apache docs > = http://httpd.apache.org/docs/current/mod/mod_ssl.html#sslcertificatechainf= ile > I do not think this helps with your problem but it is cleaner to not = use > deprecated configs. I am not the OP with the problem, I was just sharing the configuration = that I have that works. it looks like I should change that to=20 SSLCertificateFile /usr/local/etc/dehydrated/certs/covisp.net/chain.pem I'll give that a try next time I'm editing configs. --=20 Don't congratulate yourself too much, or berate yourself either. You choices are half chance; so are everybody else's. From owner-freebsd-questions@freebsd.org Tue Apr 10 07:06:00 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 40A9BF82AF8 for ; Tue, 10 Apr 2018 07:06:00 +0000 (UTC) (envelope-from mailing-2391621-150459050-de03db90c4@mailpv.net) Received: from eur-kvi158.lnmailer.net (eur-kvi158.lnmailer.net [213.139.173.158]) (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 96F50735B2 for ; Tue, 10 Apr 2018 07:05:59 +0000 (UTC) (envelope-from mailing-2391621-150459050-de03db90c4@mailpv.net) Received: from eur-kvi158.vdk.fi (localhost [127.0.0.1]) by eur-kvi158.lnmailer.net (Postfix) with ESMTP id 91A9A676DA for ; Tue, 10 Apr 2018 10:05:45 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=mailpv.net; h= list-unsubscribe:mime-version:reply-to:to:subject:from:date; s= a.mailpv; bh=BraW/dF6pc7+juG7JjoKK07QIys=; b=MNBZahwhk9Q1n56/g4h 44CyKYfr4IFtqYQxyEvPme7v816+jKe7XfEnKqS16t6PFXDr94zKaSB4Wsia0Vce /R/0TMDjYE49X+6mHVqVwuRymENkg7mKW9m3qt+KoRjAiHYIQhpcMzI0uIWZ4Zh1 fKLrnHh/qs4RYw+ykBsxW8mA= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=mailpv.net; h= list-unsubscribe:mime-version:reply-to:to:subject:from:date; s= newsletter; bh=BraW/dF6pc7+juG7JjoKK07QIys=; b=kgx45D6At7GcF1mOZ xhesGYV0xvjOV+7q7o/gTa9ESENaL/4Wgrj5Wi1ak7YCQqnr4zbcWvBjCZEA6F4O Ci7TuqPzcJ3i4N6IOhmQTHBzez/iqmyDPdjBsturOA4bzyO0SdD45EA7kurFT/Wp my6yrl9AYp6iQYM3Z6mr9ZqCdU= MIME-Version: 1.0 Reply-To: info@reo.ae To: freebsd-questions@freebsd.org Subject: 4% DLD Waiver on Apartments, Villa & Townhouses by Dubai Properties From: "REO (Real Estate Opportunity)" Message-Id: <0000005acc6249-4-13a-os1xpv-2391621-150459050@mailpv.net> Date: Tue, 10 Apr 2018 10:00:00 +0400 (+04) Content-Type: text/plain; charset=ascii Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2018 07:06:00 -0000 Click here to open in your browser http://al-ruwad-new.mailpv.net/a/s/15045= 9050-f17235621a75232f57b963d879ded567/2435935=20 LIMITED TIME OFFER ON PROJECTS BY DUBAI PROPERTIES "4% Dubai Land Departmen= t Waiver on Below Projects" No Commission | Direct Sale=20 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Dubai Wharf Apartments at Culture Village +++++++++++++++++++++++++++++++++++++++++ PRICING 1 Bedroom Starting @AED 1.388 Million 3 Bedroom Starting @AED 2.864 Million 4 Bedroom Starting @AED 4.701 Million PAYMENT PLAN 20% on Booking | 80% upon Hand Over Ready to Move Apartment! [Are you Interested? Book a Viewing] http://al-ruwad-new.mailpv.net/go/1456= 5904-1004362-150459050=20 Bellevue Towers Apartments at Business BayPRICING1 Bedroom Starting @AED 1.= 297 Million 2 Bedroom Starting @AED 1.876 Million 3 Bedroom Starting @AED = 3.032 MillionPAYMENT PLAN10% on Down Payment, followed by 35% construction = linked at regular intervals of 5% each, followed by 60% upon Hand Over (Q4 = 2019*)OFF Plan Project![Are you Interested? Click Here] http://al-ruwad-new= .mailpv.net/go/14565904-1004362-150459050=20 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= ++++++++++++++++++++++++++++++++++++++++++++++++++++ Remraam Apartments at DubailandPRICING ++++++++++++++++++++++++++++++++++++++ 1 Bedroom Starting @AED 685K 2 Bedroom Starting @AED 972KPAYMENT PLAN5% on = Down Payment, followed by 35% construction linked, followed by 60% upon Han= d Over (Q4 2019*)OFF Plan Project![Are you Interested? Click Here] http://a= l-ruwad-new.mailpv.net/go/14565904-1004362-150459050=20 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Villanova - La Quinta Independent Villas at DubailandPRICING ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 3 Bedroom + Maid's Starting @AED 2.193 Million 4 Bedroom + Maid's Starting = @AED 2.791 Million 5 Bedroom + Maid's Starting @AED 3.302 MillionPAYMENT PL= AN5% on Down Payment, followed by 35% construction linked at regular interv= als of 5% each, followed by 60% upon Hand Over (Q2 2020*)OFF Plan Project![= Are you Interested? Click Here] http://al-ruwad-new.mailpv.net/go/14565904= -1004362-150459050=20 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= +++++++++++++++++++++++++++++ Serena-Bella Casa/ Casa Dora/ Casa Viva Townhouses at DubailandPRICING ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 Bedroom + Maid's Starting @AED 1.385 Million 3 Bedroom + Maid's Starting = @AED 1.666 Million 4 Bedroom + Maid's Starting @AED 1.751 MillionPAYMENT PL= AN5% on Down Payment, followed by 35% construction linked at regular interv= als of 5% each, followed by 60% upon Hand Over (Q2 2020*)OFF Plan Project![= Are you Interested? Click Here] http://al-ruwad-new.mailpv.net/go/14565904= -1004362-150459050=20 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= +++++++++++++++++++++++++++++ No Commission | 4% DLD Waiver | Direct Sale CALL/Whatsapp: +971508747474 ht= tp://al-ruwad-new.mailpv.net/go/14565905-627339-150459050 FOR A CONSULTAT= ION +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Let's Talk =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Tel: +9714 343 0111 tel:+97143430111 Mob: +971 50874 7474 tel:+971508747474 info@alruwad.ae mailto:info@alruwad.ae Al Ruwad Real Estate RERA Reg. No. 12803 =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 Click here to unsubscribe http://al-ruwad-new.mailpv.net/account/150459050-= 0ea5354ff164c3b793a30a9385579790-1062523/2391621 . From owner-freebsd-questions@freebsd.org Tue Apr 10 18:22:36 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A934F8D587 for ; Tue, 10 Apr 2018 18:22:36 +0000 (UTC) (envelope-from chode128@gmail.com) Received: from mail-it0-x244.google.com (mail-it0-x244.google.com [IPv6:2607:f8b0:4001:c0b::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 C94A975860 for ; Tue, 10 Apr 2018 18:22:35 +0000 (UTC) (envelope-from chode128@gmail.com) Received: by mail-it0-x244.google.com with SMTP id 71-v6so16014433ith.2 for ; Tue, 10 Apr 2018 11:22:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=E+psrWLnmYOlrhJ+0nNtfXzMzzZ0Lx8OQ75yVDZswcM=; b=ZzGQFFe0BcWWDZjJhelIgJcXxfv2mqpL5v7DBzlDrGT3fsCbobsSlCHHlb3cP1BYMQ QaI/Ba3MXNG3MZ8cXU197mcRt9tbEnbP+iMYPE+vMsSQCTpSUzN+Zj5AZHiBzFSWCDBi 3xiV3rV3bk7bidZodz/5TH0Q4/Aj6mCjVoqlK2q4e1Sh/kgXfnr16DL7ehlWrh+wRuyl 8f67xJKU0bvt0qHV0Zx63q4FYjzy8rJti42p5neGOucTBA4IZFQdOj61AFHCg/47SSSb Uwu0Rn3aWlgGAlcuL7H3vuJhsjQMl2f6/rmjzCPj/fNEJ2ptW6UbMzx1X1jAlvF7UFBL OCUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=E+psrWLnmYOlrhJ+0nNtfXzMzzZ0Lx8OQ75yVDZswcM=; b=YlOuwsnhRQr4yHC+tDyChEG+3uLFzXLxpol3NHITxmAnE/WuH5sgSUFMz8I2BfPXVM 0Kf6e6lLLUTmRTFXLQlDD8zpPvMAzQYCdgGGJDOCBJnCN2U53mfl28QjhypDZjS1g5U2 OXkyIDuwSe31V1WZj26kRClVSyCaOgGh/isAEn/yPNN8xxZcApzXHXr23vKyShBTzL1w BEpRwbD3RfkxVTKcEmQphP/6Zve+adx+XMyMGsdJs6tbdCW4zPS1Ilr7A16QBsuBfawB CwWxhPCa+XsRSEk/SUKLKi6EUDwC2obpcvYPY+12dUiC9gIN/qz/NC7PXZeY503m+fzd kC6A== X-Gm-Message-State: ALQs6tCAUn8LBRHFzzvxUGOlvZ626wqPrOX+0YcizcOeyuQ+nUoRCLSW 4JnO6W4RqYpf6foTO3o0IX86sUI/+shGnTNQFAt0LpxS8g== X-Google-Smtp-Source: AIpwx4+pIRRVti8svhPa7uTsWyvaH1SEuryzuhDMoWESUEiinI30S4hInnte124QmwsFJi/RfElnv3A8nY2AVSwNKzk= X-Received: by 2002:a24:79cf:: with SMTP id z198-v6mr689024itc.60.1523384554830; Tue, 10 Apr 2018 11:22:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.213.83.200 with HTTP; Tue, 10 Apr 2018 11:22:34 -0700 (PDT) From: Francis Bacon Date: Tue, 10 Apr 2018 12:22:34 -0600 Message-ID: Subject: sshd virtual memory usage on different hardware To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2018 18:22:37 -0000 Hi guys, I was trying to find out why sshd uses more memory on different hardware. All machines are running 11.1-STABLE, but some use 4M some 12M, and some 22M. It's not dependant on what ssh is doing, as on all of these machines it's doing the same thing. Looking at the virtual memory of the sshd processes it appears different linked libraries are using more virtual memory different hardware. The biggest offender is /usr/lib/libgssapi_spnego.so.10. Below are the virtual memory usages, and it appears it uses 2235, 9925, and 20295. Can anyone help me understand why? Is there anyway to make sshd use the same amount of memory? Thanks! Machine1: PID START END PRT RES PRES REF SHD FLAG TP PATH 3124 0x80440e000 0x80440f000 rw- 1 0 2 0 CN-- vn /usr/lib/libgssapi_spnego.so.10 3124 0x804600000 0x805000000 rw- 2235 0 1 0 C-S- df Machine2: PID START END PRT RES PRES REF SHD FLAG TP PATH 44052 0x80440e000 0x80440f000 rw- 1 0 2 0 CN-- vn /usr/lib/libgssapi_spnego.so.10 44052 0x804600000 0x806e00000 rw- 9925 0 1 0 C-S- df Machine3: PID START END PRT RES PRES REF SHD FLAG TP PATH 36973 0x80440e000 0x80440f000 rw- 1 0 2 0 CN-- vn /usr/lib/libgssapi_spnego.so.10 36973 0x804600000 0x809800000 rw- 20295 0 From owner-freebsd-questions@freebsd.org Tue Apr 10 20:00:19 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 701A5F94CD3 for ; Tue, 10 Apr 2018 20:00:19 +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 F3FA16F613 for ; Tue, 10 Apr 2018 20:00:18 +0000 (UTC) (envelope-from feenberg@nber.org) Received: from sas1.nber.org (sas1.nber.org [198.71.6.89]) by mail2.nber.org (8.15.2/8.15.2) with ESMTPS id w3AJdEa5086257 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 10 Apr 2018 15:39:14 -0400 (EDT) (envelope-from feenberg@nber.org) Date: Tue, 10 Apr 2018 15:39:14 -0400 (EDT) From: Daniel Feenberg To: Francis Bacon cc: freebsd-questions@freebsd.org Subject: Re: sshd virtual memory usage on different hardware In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21 (LRH 202 2017-01-01) 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, 2018/04/09 17:26:31 X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.721, bases: 2018/04/10 12:49:00 #8387652 X-KLMS-AntiVirus-Status: Clean, skipped X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2018 20:00:19 -0000 On Tue, 10 Apr 2018, Francis Bacon wrote: > Hi guys, > > I was trying to find out why sshd uses more memory on different hardware. > All machines are running 11.1-STABLE, but some use 4M some 12M, and > some 22M. It's not dependant on what ssh is doing, as on all of these > machines > it's doing the same thing. > > Looking at the virtual memory of the sshd processes it appears different > linked libraries are using more virtual memory different hardware. > The biggest offender is /usr/lib/libgssapi_spnego.so.10. Below are the > virtual memory usages, and it appears it uses 2235, 9925, and 20295. The figure under "RES" is resident memory, not virtual memory. How much of the library was resident would depend on how much real memory was available, how much competition for memory there was, and might depend on what other processes were using that library. daniel feenberg > > Can anyone help me understand why? > Is there anyway to make sshd use the same amount of memory? > > Thanks! > > Machine1: > PID START END PRT RES PRES REF SHD FLAG TP > PATH > 3124 0x80440e000 0x80440f000 rw- 1 0 2 0 CN-- vn > /usr/lib/libgssapi_spnego.so.10 > 3124 0x804600000 0x805000000 rw- 2235 0 1 0 C-S- df > > Machine2: > PID START END PRT RES PRES REF SHD FLAG TP > PATH > 44052 0x80440e000 0x80440f000 rw- 1 0 2 0 CN-- vn > /usr/lib/libgssapi_spnego.so.10 > 44052 0x804600000 0x806e00000 rw- 9925 0 1 0 C-S- df > > Machine3: > PID START END PRT RES PRES REF SHD FLAG TP > PATH > 36973 0x80440e000 0x80440f000 rw- 1 0 2 0 CN-- vn > /usr/lib/libgssapi_spnego.so.10 > 36973 0x804600000 0x809800000 rw- 20295 0 > _______________________________________________ > 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 10 20:25:39 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E1C17F9696D for ; Tue, 10 Apr 2018 20:25:38 +0000 (UTC) (envelope-from chode128@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 75C3274078 for ; Tue, 10 Apr 2018 20:25:38 +0000 (UTC) (envelope-from chode128@gmail.com) Received: by mail-io0-x244.google.com with SMTP id o4so15190773iod.3 for ; Tue, 10 Apr 2018 13:25:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7srWG736NlCA+FlZDUKYtBkAPJDZb8W8221AP/qsp3o=; b=NDR88uZQ6mtjWV8s5lRr0VUvVaC5xQwsHDJxc7tQA0jFfda/1CQv8BzSha+nhtSSwz ctteMX7ZIQmU+rpxrpfkESDHbUERWFivlCXSeNGZkatyQ+G3zzKLpsMdgvjmyNA7p/B0 gs2vKASCmGDHCnBLAvRef6WTiKJViKV/f5sIG3vHRjshCctOGbyoMifC4LwnXzEiSdxR sL+11t+GZHSiegS3K89WOT7cGBT0/FGkurpAk5yZyrwVM5/mhbOvaj8AC5H19OcGYbjL rUqYSFUZP3VN1U114DQF92p4+RsvnlAth79UGZDvAq3la+IgaP0aYBW/uWsMcwDnU5s1 O0Og== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7srWG736NlCA+FlZDUKYtBkAPJDZb8W8221AP/qsp3o=; b=lhmBE/HynheWBW8F3Tn3t6ByTQacjpMypKs4nrOrCvxRspHZgP4HSC7EMRZFMrW0sW /FODbXxg6gPR8FXtBqPlzpD/5lT41Eko9Eb8byFfJ/gtCQLpix3uCZEcZDBS5LdKejWZ 4pxgGniu9I+qEpP5g1PxiM+Oj4PG6/dS6+AkvUj3KHvQPYUsBem4R3aOj3mQNcI4+XCh 1EVHxPv7unWKxI3hBwHeUlEZh2LTep6O2X5ryjBdHIe5NjTdQ02iqx4y3wvTzcRD8/r0 EL2AspvQHQItY7r7PVoDAEjLeHh9tQpU+ohhf8HSQoNAlf3LBQkjzFZz7CGJEsOXBgtN SfsA== X-Gm-Message-State: ALQs6tDKx6sQZIFVW8Vl8+c1bVRkNbeAiuBWKhcKKkS4+6kMH1iS9HIL I47S7rleZ8A9Zwy/19otGaZxZYd5drtDuSVcFA== X-Google-Smtp-Source: AIpwx4/3bcKjCmg6QfSuFQQDYJEDKRZ9cldRCm7ycS573wbbjkpEgAwku4++kzB2aHlB1LgQeCdVPaU4KHjEGIbwcjU= X-Received: by 10.107.132.97 with SMTP id g94mr2060843iod.46.1523391937966; Tue, 10 Apr 2018 13:25:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.213.83.200 with HTTP; Tue, 10 Apr 2018 13:25:37 -0700 (PDT) In-Reply-To: References: From: Francis Bacon Date: Tue, 10 Apr 2018 14:25:37 -0600 Message-ID: Subject: Re: sshd virtual memory usage on different hardware To: Daniel Feenberg Cc: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2018 20:25:39 -0000 > >> Looking at the virtual memory of the sshd processes it appears different >> linked libraries are using more virtual memory different hardware. >> The biggest offender is /usr/lib/libgssapi_spnego.so.10. Below are the >> virtual memory usages, and it appears it uses 2235, 9925, and 20295. >> > > The figure under "RES" is resident memory, not virtual memory. How much of > the library was resident would depend on how much real memory was > available, how much competition for memory there was, and might depend on > what other processes were using that library. > Why the amount of real memory would change how much memory a library would have resident? In my examples, Machine1 had 8G, Machine2 32G, and Machine3 64G. Thanks! From owner-freebsd-questions@freebsd.org Wed Apr 11 00:14:39 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97408F81A9F for ; Wed, 11 Apr 2018 00:14:39 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001: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 3802368F32 for ; Wed, 11 Apr 2018 00:14:39 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-io0-x230.google.com with SMTP id v13so451052iob.6 for ; Tue, 10 Apr 2018 17:14:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:subject :content-transfer-encoding; bh=GKtO8bmU7FgRWthMfd7vZMj6vVxHSV+q4af5KG1/lns=; b=ujI3mdmDL3U4TsAfRUc4ccDTdNLwoUnrje6ZkEWaIOSf8MGkJGrw14k9RMN8U327yX W7OsprmgVOuU4OXKgFSRdP0AdSUWq6bT8HizaxxZ+eUwfLYuvzQMtat4G5fA8cXpB8+J J7A/ceDCJTpAPyVi6kEx4SMxPBoH5oyYeLCp5pURL2oNRVI5xdGWvTuu8fgK2vSJQpUx AQlHA+62hTQfB1C09Uumkh3+Uz8cbR8dV0ZjlfEXPtan9VkVz88J2T7gmKQypxSTPggR HdS2HeOMANTMl2HAkXXgrahvaUSBEzEYmSxazOReh9hd6gsHbnewKVH1BqAiQxHaWFrN Tk0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:content-transfer-encoding; bh=GKtO8bmU7FgRWthMfd7vZMj6vVxHSV+q4af5KG1/lns=; b=W7g6buPQ4JVmokFd6XGh8XxbeunC8YILGXoLTOFSjW2De5H5jZqCeQVsjkSulqzJuA 9Q1Wpa2MksbRZydMebsueqTq9nhaeXgTXQaZ/h9oUVzQ7B/ZhUju6HCIQgArmNJglczu WLEuCVY4DyWxiXUAHvgLRQ0FAChQzSICifRksGhgTm2hh2NXMsgSaDqIkdh7qeFtLjAN 6tUKR9JED04m8faZbB3G0xRU+6/cdXosVgJEWdjC9CcAchElF+5zFSFpsLW6TPSDfVek +kQvB9UdUoTudbxoYBxtDcohVQuqwP0jrVexnkcPGsHPL2LYHcX/35l3iiuyHpQ+CR0l cmwg== X-Gm-Message-State: ALQs6tAYul9gGZXWqWH6OaLDEM8153oaDl55na43Lu8wUG4UIlAbsBaT wOiaOxy8EjCHv77HmoZr1e5i+g== X-Google-Smtp-Source: AIpwx4+a1MhcSX4Xa1D6jJb3de6aMVGy66Y5eEP2FvQHQlkbCRtBFV73p6mrjynaAUD9KaesOOYTlA== X-Received: by 10.107.31.193 with SMTP id f184mr2767996iof.291.1523405678393; Tue, 10 Apr 2018 17:14:38 -0700 (PDT) Received: from [10.0.10.7] (cpe-65-25-48-31.neo.res.rr.com. [65.25.48.31]) by smtp.googlemail.com with ESMTPSA id 134-v6sm86133itl.34.2018.04.10.17.14.37 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 10 Apr 2018 17:14:37 -0700 (PDT) Message-ID: <5ACD536C.5010407@gmail.com> Date: Tue, 10 Apr 2018 20:14:36 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: "freebsd-questions@freebsd.org" Subject: Recover directory tree with files from win10 HD 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 00:14:39 -0000 Hello List; My mothers win10 pc has external usb 3tb sata drive with 600gb of data that has hardware data problems. It will not mount on win10 pc. My mother has her whole digital life on the external drive. I can not find any win10 software to recover the data from a drive that will not mount. I am thinking about using FreeBSD to recover the directory structure and the files contained in them. Asking anyone if they know of a port that will recover the data with their full file names in their directories? Thanks in advance for your help From owner-freebsd-questions@freebsd.org Wed Apr 11 01:57:18 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D810F8968A for ; Wed, 11 Apr 2018 01:57:18 +0000 (UTC) (envelope-from drew@mykitchentable.net) 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 E49C3828E2 for ; Wed, 11 Apr 2018 01:57:17 +0000 (UTC) (envelope-from drew@mykitchentable.net) Received: by mailman.ysv.freebsd.org (Postfix) id A596CF89685; Wed, 11 Apr 2018 01:57:17 +0000 (UTC) Delivered-To: questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 818FBF8967E for ; Wed, 11 Apr 2018 01:57:17 +0000 (UTC) (envelope-from drew@mykitchentable.net) Received: from NAM04-CO1-obe.outbound.protection.outlook.com (mail-co1nam04olkn080a.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe4d::80a]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT TLS CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E17C0828E1 for ; Wed, 11 Apr 2018 01:57:16 +0000 (UTC) (envelope-from drew@mykitchentable.net) Received: from SN1NAM04FT017.eop-NAM04.prod.protection.outlook.com (10.152.88.57) by SN1NAM04HT111.eop-NAM04.prod.protection.outlook.com (10.152.89.172) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.631.7; Wed, 11 Apr 2018 01:24:54 +0000 Received: from MW2PR20MB2188.namprd20.prod.outlook.com (10.152.88.58) by SN1NAM04FT017.mail.protection.outlook.com (10.152.88.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.653.8 via Frontend Transport; Wed, 11 Apr 2018 01:24:54 +0000 Received: from MW2PR20MB2188.namprd20.prod.outlook.com ([fe80::d5a7:b3ed:2490:1c0d]) by MW2PR20MB2188.namprd20.prod.outlook.com ([fe80::d5a7:b3ed:2490:1c0d%13]) with mapi id 15.20.0653.015; Wed, 11 Apr 2018 01:24:54 +0000 From: Drew Tomlinson To: "questions@freebsd.org" Subject: How To Update From 9.1? Thread-Topic: How To Update From 9.1? Thread-Index: AdPRMr1SNI3ecYaHRbWppmUZaaNH+g== Date: Wed, 11 Apr 2018 01:24:54 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-incomingtopheadermarker: OriginalChecksum:3C53EFAD07AF1355C6248DBADAA74A64DD4335F2ED8C83B36DC82C3A53A46BFE; UpperCasedChecksum:63CF01E2125E6D7FD42227FAADDED21ABB87B09BA5B58F85BDF3FAC2E33D2E21; SizeAsReceived:6794; Count:43 x-tmn: [Me3ApVhSU/EDfVe4Bub6m67ut7a8Pmtw] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; SN1NAM04HT111; 7:VJaWwEUiTsssoYhHLtri7zp65CiiYewmDCE9kbXUSDSp4usDDRdtXjfetZg1r7C1FuJTeLiY+oCSvgGqh6XGhjqzDcR1YkoncUGBsRG3JLu0VeACQntCenlGcEkfV86B8vQP4hnsdLNUectfrai3HGzIVu+zynsqpJZz7qx2fQqxt/c9sVnqtTd/p8ySyHAnq6H+eBZ0e/6Ya5SbpQz1ET5dkabJnsJAH++u8oNU5z0aQt77qF0P/jRCDPcj0s+b x-incomingheadercount: 43 x-eopattributedmessage: 0 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1603101448)(1601125374)(1701031045); SRVR:SN1NAM04HT111; x-ms-traffictypediagnostic: SN1NAM04HT111: x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:SN1NAM04HT111; BCL:0; PCL:0; RULEID:; SRVR:SN1NAM04HT111; x-forefront-prvs: 0639027A9E x-forefront-antispam-report: SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:SN1NAM04HT111; H:MW2PR20MB2188.namprd20.prod.outlook.com; FPR:; SPF:None; LANG:; x-microsoft-antispam-message-info: Gg7LTGz3gtEcCdqO9ev6f/X5yYij2nU7dduaXEgmP5V1GJscoze/IlCZKUUavuxFUYuy4dTxK76Pqyx4GOkF7eY7mX9txpcTbAxhVh0xeS8CvN6A/SV7RxrANv5m3CdGMbWs5AqWKcA6GZNMJ1Sk9Y4W9kV9xS+uXcfnBdn8cMLUKxoGnPwxPemkNnGLZSEX Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Office365-Filtering-Correlation-Id: 02f706de-0bb4-4f6a-cba9-08d59f4b07dc X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 02f706de-0bb4-4f6a-cba9-08d59f4b07dc X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Apr 2018 01:24:54.5286 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1NAM04HT111 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 01:57:18 -0000 I've got an old system I'm trying to get current. # uname -a FreeBSD vm.mykitchentable.net 9.1-RELEASE-p1 FreeBSD 9.1-RELEASE-p1 #0: Tue= May 9 09:19:33 PDT 2017 drew@vm.mykitchentable.net:/usr/obj/usr/src/s= ys/GENERIC amd64 So I consult the handbook and various list posts and find that I should be = able to use freebsd-update. Specifically I've done: ---BEGIN--- # freebsd-update fetch install Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching public key from update5.freebsd.org... done. Fetching metadata signature for 9.1-RELEASE from update5.freebsd.org... don= e. Fetching metadata index... done. Fetching 2 metadata files... done. Inspecting system... done. Preparing to download files... done. Fetching 5 files... done. The following files will be added as part of updating to 9.1-RELEASE-p24: /usr/src/contrib/bind9/lib/isc/counter.c /usr/src/contrib/bind9/lib/isc/include/isc/counter.h /usr/src/contrib/tzdata/leap-seconds.list /usr/src/contrib/tzdata/zone1970.tab /usr/src/crypto/openssl/ssl/s3_cbc.c WARNING: FreeBSD 9.1-RELEASE-p1 HAS PASSED ITS END-OF-LIFE DATE. Any security issues discovered after Wed Dec 31 16:00:00 PST 2014 will not have been corrected. ---END--- And then trying to upgrade incrementally, I'm starting with 9.3-RELEASE. ---BEGIN--- # freebsd-update -r 9.3-RELEASE upgrade Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata signature for 9.1-RELEASE from update6.freebsd.org... don= e. Fetching metadata index... done. Inspecting system... done. The following components of FreeBSD seem to be installed: The following components of FreeBSD do not seem to be installed: src/src Does this look reasonable (y/n)? y Fetching metadata signature for 9.3-RELEASE from update6.freebsd.org... don= e. Fetching metadata index... done. The update metadata is correctly signed, but failed an integrity check. Cowardly refusing to proceed any further. ---END--- I've tried deleting /var/db/freebsd-update and doing the 'fetch install' ov= er. I've tried deleting /usr/src and downloading a new copy of 9.3 source = code. Overall, I really don't know what I need to do as I've never done a binary = update before. I don't even know if 'src/src' looks reasonable but I thoug= ht I'd give it a try. Can anyone point me in the right direction? I'd app= reciate the nudge. Cheers, Drew Like card tricks? Visit the Alchemist's Warehouse to learn card magic secrets for free! http://alchemistswarehouse.com From owner-freebsd-questions@freebsd.org Wed Apr 11 05:25:33 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A5FE2F9749F for ; Wed, 11 Apr 2018 05:25:33 +0000 (UTC) (envelope-from srs0=l3hk=ha=mail.sermon-archive.info=doug@sermon-archive.info) 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 3F2496FA68 for ; Wed, 11 Apr 2018 05:25:33 +0000 (UTC) (envelope-from srs0=l3hk=ha=mail.sermon-archive.info=doug@sermon-archive.info) Received: by mailman.ysv.freebsd.org (Postfix) id 00855F9749E; Wed, 11 Apr 2018 05:25:33 +0000 (UTC) Delivered-To: questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E0F24F9749D for ; Wed, 11 Apr 2018 05:25:32 +0000 (UTC) (envelope-from srs0=l3hk=ha=mail.sermon-archive.info=doug@sermon-archive.info) Received: from mail.sermon-archive.info (sermon-archive.info [71.177.216.148]) by mx1.freebsd.org (Postfix) with ESMTP id 7C8446FA4A for ; Wed, 11 Apr 2018 05:25:32 +0000 (UTC) (envelope-from srs0=l3hk=ha=mail.sermon-archive.info=doug@sermon-archive.info) Received: from [10.0.1.251] (mini [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 40LXPP4rB3z2fjQZ; Tue, 10 Apr 2018 22:18:17 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: How To Update From 9.1? From: Doug Hardie In-Reply-To: Date: Tue, 10 Apr 2018 22:18:17 -0700 Cc: "questions@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Drew Tomlinson X-Mailer: Apple Mail (2.3445.6.18) X-Virus-Scanned: clamav-milter 0.99.4 at mail X-Virus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 05:25:33 -0000 > On 10 April 2018, at 18:24, Drew Tomlinson = wrote: >=20 > I've got an old system I'm trying to get current. >=20 > # uname -a > FreeBSD vm.mykitchentable.net 9.1-RELEASE-p1 FreeBSD 9.1-RELEASE-p1 = #0: Tue May 9 09:19:33 PDT 2017 = drew@vm.mykitchentable.net:/usr/obj/usr/src/sys/GENERIC amd64 >=20 > So I consult the handbook and various list posts and find that I = should be able to use freebsd-update. Specifically I've done: >=20 > I've tried deleting /var/db/freebsd-update and doing the 'fetch = install' over. I've tried deleting /usr/src and downloading a new copy = of 9.3 source code. >=20 > Overall, I really don't know what I need to do as I've never done a = binary update before. I don't even know if 'src/src' looks reasonable = but I thought I'd give it a try. Can anyone point me in the right = direction? I'd appreciate the nudge. This is a common issue for 9 and earlier systems. I understand it may = also affect some 10s. Basically there are some patches available in = various postings to bug reports. If you find both of them, it should = work, but you have to manually update as line numbers are not = consistent. The easier approach is probably to get a copy of = freebsd-update from a newer system. It's a script so that works fine. = I have used the script from 11.0 to upgrade some 9.x systems. -- Doug From owner-freebsd-questions@freebsd.org Wed Apr 11 09:37:49 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1A353F83AFA for ; Wed, 11 Apr 2018 09:37:49 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7D6B4884DE for ; Wed, 11 Apr 2018 09:37:48 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.30.67]) by mrelayeu.kundenserver.de (mreue004 [212.227.15.167]) with ESMTPA (Nemesis) id 0LpAhs-1ea8hc2qJw-00euCi; Wed, 11 Apr 2018 11:37:40 +0200 Date: Wed, 11 Apr 2018 11:37:40 +0200 From: Polytropon To: Ernie Luzar Cc: "freebsd-questions@freebsd.org" Subject: Re: Recover directory tree with files from win10 HD Message-Id: <20180411113740.2b245110.freebsd@edvax.de> In-Reply-To: <5ACD536C.5010407@gmail.com> References: <5ACD536C.5010407@gmail.com> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:mPBCQ8HhizozbqcLUFv6jE6FEgRWr97wEZV3+lZHYyYWBfgaM6e ktlP1C3nq1kDlodr7nK3lo598BQ8pDIVh2DgP9KhvEf64DIzcI4KQP4TpzcH/x1rVZB2+tE brZ5N3+cIjqZDBQXl7seARXJsGqKFZwj0TdySAGyzIKcnYv+/JXc0tThUbexJpRTM4a1E50 ganSrRozyqrhswNW7Wy6g== X-UI-Out-Filterresults: notjunk:1;V01:K0:c4QkQAfqcSw=:R1rfUGVc4bZF/3bieROYDc ONpaE2wCISBfoBe7Rzq3i4C4D9onkSwYQuvaFjTinx3DOyKk8G35yekPn47Ih918S9VflZUj9 /UCWvpK1xnQG895MJw7ENQj2vuqNcLcDf2dhR4j7LMKH7XcEy9sB0emCOuYHYq2jbXuYf4sI8 fw7wbCscgvuFDAXXOGCLZSOOYPxoXoKMFejimnOGFX5NtMKHqMdvJJkHUY4pyps47b5AXt2U2 +AJH6+Jz01COq7yHE6zWTSQCpJjKQgC0n3Eb8YqWUU3lI8ib26bWl/Df9g25vv1vYRxrf+bh1 i+O4PdPu4i7aa5RN6D3LVErXmYWoD9LfsRsRHQqrWYm0Kwj5idPm7t1CLy986L6P7sahNXOdn yWJll2M0rXmP10qHy+4FKPsfeM3M7TR/ipR/ZWAQONXdWh0e7pPFfJkDaqi4bykk0KEUOLHeK 900EUXqsTSsC+EAgG8ICoyMC+NWrqED/4R4KYzKrUjZzrUWZn2wydtZpRb1ybsDKWU9ouC0md 1dw4h65f2Q/HHYt81diDFZYXGH4EyGnmGG938mRYwM+tN/1BkGDDIb413ORNY+qiauYYxMwNx tJ9WwOmHgcDxK2Krr5yu/aAKaBfmUsnPPymw+pL9zHYP6krKW7xSg9Sg3S1XcMFPUqsTtTVFZ vGYLMJxJp+/BB6v4l1Exas9QSQKfjbO4JNGYuYvjTrP1wSIdSJHvMfo5MDFReL+tT8nBVn8k4 Mjy9HA1eEFofNTOq0OSpw+7h9o4dorKoKV/puPnIRKQzF9QRCYAsNEOowpE= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 09:37:49 -0000 On Tue, 10 Apr 2018 20:14:36 -0400, Ernie Luzar wrote: > My mothers win10 pc has external usb 3tb sata drive with 600gb of data > that has hardware data problems. It will not mount on win10 pc. Do not try any further with "Windows", it could do more damage. On "Windows 10", they use NTFS or FAT as file systems, and both are known to do the "funniest things" when getting into some inconsistent state ("silent" data corruption, data loss, no access due to damaged hiberfile, etc.). > My > mother has her whole digital life on the external drive. Just restore from backup! Sorry, couldn'r resist... ;-) > I can not find > any win10 software to recover the data from a drive that will not mount. First of all, use tools that work with a copy of the damaged disk (or partition). Create this 1:1 copy first in a read-only manner, then work with the image. Do not try to repair the data "on-disk", it will probably destroy more data and reduce the chances of getting the "whole digital life" back. Seriously. I'm not making this up - I learned from my own faults. Check the mailing list archives for the terrible truth. :-) Do not use "Windows" any further without knowing _exactly_ what the problem is. > I am thinking about using FreeBSD to recover the directory structure and > the files contained in them. Asking anyone if they know of a port that > will recover the data with their full file names in their directories? That depends on the actual damage. This is how you should proceed: 1. Make a 1:1 copy of the disk or partition. Use that copy in all further steps. (Two copies are handy, in case you mess up one.) 2. Examine the data. What has happened? Can you use FUSE's NTFS mount program to mount it read-only? Can you use tools from the ntfs-tools package to repair things like the MFT. Or is it a FAT drive? Try mount_msdos instead, maybe even fsck_msdosfs. It could be sufficient to copy all the data (cp -R). 3. No luck getting the partition to mount? Assume the data is still there. Make yourself familiar with professional forensic tools. Start with the easy ones. If they get back what you expect to recover, well done. If not, use the more complex ones. On this mailing list, I have published my "famous list of data recovery tools" from time to time. Note that in order to make use of that list, you'll have to learn (!) about lower-level file system design, because you _must_ understand what you're doing. Here is this list. Note that I've added a few comments that might help in your specific situation (damaged FAT or NTFS drive): System: dd <- for making 1:1 copy fsck_ffs clri fsdb fetch -rR recoverdisk Ports: ddrescue <- if 1:1 copy is hard dd_rescue <- same ffs2recov magicrescue <- get data back (no structure) testdisk The Sleuth Kit: fls dls ils autopsy scan_ffs recoverjpeg foremost photorec fatback <- FAT ntfs-tools <- NTFS (ntfsfix, ntfsinfo, ntfsmount) Keep in mind: It will take time. There is no "one size fits all" GUI solution where you just click and icon and then have all your files (and the directory structure) back. IN worst case, what you're searching for has already been overwritten by "Windows" attempting to "repair" it. Your alternative: Take $500-3000 and ship the disk to a recovery business. If a "whole digital life" is worth that much money, you can give them a change. Note that there is absolutely no guarantee that they will succeed. Good luck! -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Wed Apr 11 12:53:26 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 713CAF92619 for ; Wed, 11 Apr 2018 12:53:26 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C58F6EE31 for ; Wed, 11 Apr 2018 12:53:25 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-it0-x235.google.com with SMTP id t192-v6so17764547itc.1 for ; Wed, 11 Apr 2018 05:53:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=Zbhyaw+gouB0erACMMiiyjpoZVU+acSEiD1OvSw0/H4=; b=UnpEz85xBMxPqmotaJ1EPv4Z5NKYIm8TJnnv1O1MmtmMK5MJb4Xzr+g1+15qfB9KCC j5MU9he/kRw7z2w/YFtFC3Ws2vr0arrI40WU7ti5EVqYTfuYNC/2t5E2F+YIbqFMHk2w pfIUoP9MLuB3PZo1gznlSgefkUXBPLd6vFYKpq+yztvMZx7mFf7H0snOEmLwa2/kq8Fv IpTEXSS9JMRVNlT3L/ZGap6gDIksYcjnlQhZs5fk4Tk5aAXffzmovGEFk/0RsjDPpnL+ Tcf3X+9J5nLpzYlGOeITCnEC5FB/+oeZOCaj1L1iG+N4XLR/JTT+KGy9U9kXnGuSTqhZ bz2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=Zbhyaw+gouB0erACMMiiyjpoZVU+acSEiD1OvSw0/H4=; b=Y714m0+QKpnIMWaTSCtx4GvvczPv9ecy35th5SUr7fHqSR2mfSRR+5aK6sylsiNyT6 q7bVIWxCTxhKQY7Bmk5KM6O5AMNtNudrJ9cCSCOUIxG90g5PrzJSgd+DM0sE1BwDqKMn QcSPm70EQl6kI41RDp5M2uTnXoa8GVMmh9zS9phjlRKdRJL1EluJuaj06cVyg7vNahgN IKwVM+inlqyz6zC3seqHQg3X1oA3jRjQSoZ5Dlo8t39O/7SxKEV2nHuTWodqLH7+eqSs wZBjamQbCapgNG8aNCNBNAKjUMAdPQYTxEy4s8ya6qzZHFtAQoLXIg71SS7JrbOMpBY+ 3a9Q== X-Gm-Message-State: ALQs6tDEg51FSk7iB993ajhfEpGXlB+Rw3tVMcPHunPYCUvaL0f3Fo5Y u1zkkzpxv77Y+N08p7Sd0BUYmQ== X-Google-Smtp-Source: AIpwx4+NpqcwhlzlGwuXb3H0vxwaWIW6eI8IwyUImqL/F7k6U6c2fCbNgdmNXjien50uLz8n3zKLMQ== X-Received: by 2002:a24:7b86:: with SMTP id q128-v6mr3756649itc.145.1523451205348; Wed, 11 Apr 2018 05:53:25 -0700 (PDT) Received: from [10.0.10.7] (cpe-65-25-48-31.neo.res.rr.com. [65.25.48.31]) by smtp.googlemail.com with ESMTPSA id 74-v6sm677159ith.17.2018.04.11.05.53.23 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 11 Apr 2018 05:53:24 -0700 (PDT) Message-ID: <5ACE0543.7030607@gmail.com> Date: Wed, 11 Apr 2018 08:53:23 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Polytropon CC: "freebsd-questions@freebsd.org" Subject: Re: Recover directory tree with files from win10 HD References: <5ACD536C.5010407@gmail.com> <20180411113740.2b245110.freebsd@edvax.de> In-Reply-To: <20180411113740.2b245110.freebsd@edvax.de> 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 12:53:26 -0000 Polytropon wrote: > On Tue, 10 Apr 2018 20:14:36 -0400, Ernie Luzar wrote: >> My mothers win10 pc has external usb 3tb sata drive with 600gb of data >> that has hardware data problems. It will not mount on win10 pc. > > Do not try any further with "Windows", it could do more damage. > On "Windows 10", they use NTFS or FAT as file systems, and both > are known to do the "funniest things" when getting into some > inconsistent state ("silent" data corruption, data loss, no > access due to damaged hiberfile, etc.). > > > >> My >> mother has her whole digital life on the external drive. > > Just restore from backup! Sorry, couldn'r resist... ;-) > > > >> I can not find >> any win10 software to recover the data from a drive that will not mount. > > First of all, use tools that work with a copy of the damaged > disk (or partition). Create this 1:1 copy first in a read-only > manner, then work with the image. Do not try to repair the > data "on-disk", it will probably destroy more data and reduce > the chances of getting the "whole digital life" back. > > Seriously. I'm not making this up - I learned from my own > faults. Check the mailing list archives for the terrible > truth. :-) > > Do not use "Windows" any further without knowing _exactly_ > what the problem is. > > > >> I am thinking about using FreeBSD to recover the directory structure and >> the files contained in them. Asking anyone if they know of a port that >> will recover the data with their full file names in their directories? > > That depends on the actual damage. This is how you should > proceed: > > 1. Make a 1:1 copy of the disk or partition. Use that copy > in all further steps. (Two copies are handy, in case you > mess up one.) > > 2. Examine the data. What has happened? Can you use FUSE's > NTFS mount program to mount it read-only? Can you use > tools from the ntfs-tools package to repair things like > the MFT. Or is it a FAT drive? Try mount_msdos instead, > maybe even fsck_msdosfs. It could be sufficient to copy > all the data (cp -R). > > 3. No luck getting the partition to mount? Assume the data > is still there. Make yourself familiar with professional > forensic tools. Start with the easy ones. If they get > back what you expect to recover, well done. If not, use > the more complex ones. > > On this mailing list, I have published my "famous list of > data recovery tools" from time to time. Note that in order > to make use of that list, you'll have to learn (!) about > lower-level file system design, because you _must_ understand > what you're doing. > > Here is this list. Note that I've added a few comments that > might help in your specific situation (damaged FAT or NTFS > drive): > > System: > dd <- for making 1:1 copy > fsck_ffs > clri > fsdb > fetch -rR > recoverdisk > > Ports: > ddrescue <- if 1:1 copy is hard > dd_rescue <- same > ffs2recov > magicrescue <- get data back (no structure) > testdisk > The Sleuth Kit: > fls > dls > ils > autopsy > scan_ffs > recoverjpeg > foremost > photorec > fatback <- FAT > ntfs-tools <- NTFS (ntfsfix, ntfsinfo, ntfsmount) > > Keep in mind: It will take time. There is no "one size fits > all" GUI solution where you just click and icon and then have > all your files (and the directory structure) back. IN worst > case, what you're searching for has already been overwritten > by "Windows" attempting to "repair" it. > > Your alternative: Take $500-3000 and ship the disk to a > recovery business. If a "whole digital life" is worth that > much money, you can give them a change. Note that there is > absolutely no guarantee that they will succeed. > > Good luck! > Thank you for your post. Lets talk about making a copy to work with. Question is about unused space. Disk is 3TB with 600GB used. How do I reduce the working copy size to the data only size of 600GB? Using the dd command I don't see any way to tell it to ignore coping empty space. Do I need another 3TB disk to hold the working copy? Do I dd the bad HD to another HD of same size making a complete image copy resulting in 2 ntfs hard drives? Or should I have the dd command create a single flat file of the bad disk on the target disk? From owner-freebsd-questions@freebsd.org Wed Apr 11 12:54:16 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ECF94F926BA for ; Wed, 11 Apr 2018 12:54:15 +0000 (UTC) (envelope-from g8kbvdave@googlemail.com) Received: from mail-wr0-x234.google.com (mail-wr0-x234.google.com [IPv6:2a00:1450:400c:c0c::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 68D926F555 for ; Wed, 11 Apr 2018 12:54:15 +0000 (UTC) (envelope-from g8kbvdave@googlemail.com) Received: by mail-wr0-x234.google.com with SMTP id y7so1663200wrh.10 for ; Wed, 11 Apr 2018 05:54:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=oWso7btleDgJlYAgja5owscEgeY/nGjM2Pwub24dntU=; b=CqRqsc7tyvUgeE69jBPG70w5hWSQrWWetDbFUJLECfkzlPv2z103lCT5L8ClG11U28 hk6HV1OKqp5ROI7F5S1jKrP85ZdyfO5/CSfeCJRqw84+HI7vKA8FiS7n4mhatXQ1ZTsk X7v0rY4CFDq6h7IqPdqHrkdoeX2wo9A6uR3OHW7UpqibpULPPpspOVVKjKCVNsOUAPhf AyLqqI2vA/gXVR+z/KqndWlJz4OyuRDNb+1FEDxzgCGeEgKrY6pASwI9aX+1cZNSEc/7 ZQxTYkP9tNrbWPjksTkQAgCU0B7myYYkZ1pOIV3OU5omYi3VIjJL1F5aLkAsCF5haXxW Xe0w== X-Gm-Message-State: ALQs6tBFhpfBLBX4dHTJbAYHk+/RAXbW4voggXg4Wrv+CbEktdJGj168 Gec/Isqmsh3D4PeG9sD0jJLLJo6E X-Google-Smtp-Source: AIpwx49ZeCKIlEg9SKnWcr/nH+mLRzuASvFmSgPO4/DrJW5MvK8X7ZPRvLPi+cViBoFMyDf2iePBbg== X-Received: by 10.223.166.179 with SMTP id t48mr3347825wrc.161.1523451253560; Wed, 11 Apr 2018 05:54:13 -0700 (PDT) Received: from [192.168.2.55] ([217.41.35.220]) by smtp.gmail.com with ESMTPSA id l34sm1185605wre.14.2018.04.11.05.54.12 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Apr 2018 05:54:12 -0700 (PDT) Subject: Re: Recover directory tree with files from win10 HD To: freebsd-questions@freebsd.org References: From: Dave B Message-ID: <2e3003c1-047e-7609-162b-f65a50c7a124@googlemail.com> Date: Wed, 11 Apr 2018 13:54:12 +0100 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Content-Language: en-GB X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 12:54:16 -0000 On 11/04/18 13:00, freebsd-questions-request@freebsd.org wrote: > Keep in mind: It will take time. There is no "one size fits > all" GUI solution where you just click and icon and then have > all your files (and the directory structure) back. IN worst > case, what you're searching for has already been overwritten > by "Windows" attempting to "repair" it. > > Your alternative: Take $500-3000 and ship the disk to a > recovery business. If a "whole digital life" is worth that > much money, you can give them a change. Note that there is > absolutely no guarantee that they will succeed. > > Good luck! What happened to the drive to cause it to fail?   Power spike, got dropped while running, or "user finger trouble" from within the OS? Assuming it's "just" a corrupted media issue, often called "bit rot", causing read errors so the OS gives up... I've also had times where trying to make a bit for bit backup copy of a suspect drive fails due to read errors.  In such cases... https://grc.com/spinrite  Is likely to be able to help.  So long as the PC BIOS (or whatever low level software that runs before Win10) can "See the drive" and identify it correctly, it is likely to be able to do the job.    It runs from a bootable CD or USB drive, so no pre-existing OS is needed. If you have to resort to paid for tools, at $89 it is MUCH less than the above figures...   Plus, you get to keep it for future needs.  (They will do money back too on a case by case basis, if it can't do the job where the drive is not physically damaged so it can't be seen by the software...) It's often the first tool the pro's use anyway, before needing to get the big guns, tool-kits and specialist HD Foo knowledge, clean rooms and so on... It is OS agnostic, just working on individual sectors, having no knowledge of any file-system format, so works on just about any spinning magnetic media.    In extreme cases, it will recover what it can, often enough when a sector is not full, but damaged in the "empty" area. If however, the drive itself has mechanical or electrical problems, failed spindle motor driver, bearings, or head positioner servo, or read/write electronic problems, then all bets are off. No affiliation, other than as a happy owner/user for some years myself, so can vouch for it's abilities on Windows drives, Linux & FreeBSD systems, and the drive from my Humax PVR!  (It can also refresh/recover floppy disks.) If it can be recovered, it will be, but it can take some time (I forget the record, but with a UPS powered system, Months have been mentioned in the past before it completed, successfully...) Laptops and some external cased drives often need extra cooling while it's running, due to the workload imposed on the drive. Regards to All. Dave B. PS:  I actually test new drives with spinrite.  When (not if!)  Faults are found, just mentioning spinrite results in instant money back, or a free replacement, no other questions asked.   I was one time asked to send a screen photo showing what it found.   Got a free replacement and carriage costs refunded too! -- Created on and sent from a Unix like PC running and using free and open source software. : From owner-freebsd-questions@freebsd.org Wed Apr 11 13:27:20 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6FC9CF9465F for ; Wed, 11 Apr 2018 13:27:20 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-ot0-x232.google.com (mail-ot0-x232.google.com [IPv6:2607:f8b0:4003:c0f::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E349175B7C for ; Wed, 11 Apr 2018 13:27:19 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-ot0-x232.google.com with SMTP id a14-v6so1950267otf.6 for ; Wed, 11 Apr 2018 06:27:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=cf64qduouAK2y/kW+N0371swrM8t1e4veZnpmwVkWr8=; b=Jg2RwXzs1hhh6vvi/AeBYeTs+ScrVjOn1fjzKKqd7qgZTFUEivgXTX6sPQI0lqoKsL hpPExPLAlztHx8FsgDAVfYQcF8HFQWrhlLb5/cCoQn9Sbx6wuA24RktYlIchliBn94ox c5HrlCCJxT7N4HrE9altdz91Pwu8UFdeENFBNnYwqBAqG0bgBgLVyP+reNo3D5tAnrm8 xPQa+qyh1ABff+vJ34e9FEbQLXgAx5h3MXF4ak1TDV1FpmSHlG7esUt6NZYYaLtG5Xg5 iDLdgy40vIHeFb03km7wPQEkR4hCWgX69tN9WRc1PlkCVov55XPbxWeDEl2qb0z3q2yr pZww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=cf64qduouAK2y/kW+N0371swrM8t1e4veZnpmwVkWr8=; b=shUNV/UWb40DeqHqqqqCtzfNrkn+yQRvs7mtlZYx2/dkaq5ODH1kAXytBPIxQqJvNV fm5D5oMVE/jsUl15cwqEwnlP/Wb2x2Bq2/qRx8dVDqlepawvv07fvtpbakQNWP0Najha v6bFlNpbzFi67Mvj8NmSPXQq2bPHT0j/aqU7H/NcUHWpJdEcWtEOf+L1M7zdBYjy5C1o ST97zINjlMx2LvbhOtcKI5JdLRdEuqo16IFaf7iBld5sxmQX9YrObDggH6aczuVwkLFR CICw18YlkGm+LpCw/g0HamsPadaXfL2rXydxsvDll56/LeCjG3bJeJhnvNNtZUTgA9v7 BV0A== X-Gm-Message-State: ALQs6tCjIIeq5lPVpccsmQ+ywK2Nl1x6aXQMPowFFtrXK5ZbR3Ay3jjI xCMWOUO8Ny/CastREIcW4zy2HtpdvpRijvBBzVV+ig== X-Google-Smtp-Source: AIpwx494SNa0R7vPGZ5rEvCtcLuSGSfXj3AqVY4daZURUmMX/9qMkdD3JchLX0y2pXI99yjjMEM4wSW/mp4lXrN0RIE= X-Received: by 2002:a9d:16f3:: with SMTP id s48-v6mr3229235ots.304.1523453239046; Wed, 11 Apr 2018 06:27:19 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a9d:1a1:0:0:0:0:0 with HTTP; Wed, 11 Apr 2018 06:26:38 -0700 (PDT) In-Reply-To: <5ACE0543.7030607@gmail.com> References: <5ACD536C.5010407@gmail.com> <20180411113740.2b245110.freebsd@edvax.de> <5ACE0543.7030607@gmail.com> From: Mehmet Erol Sanliturk Date: Wed, 11 Apr 2018 16:26:38 +0300 Message-ID: Subject: Re: Recover directory tree with files from win10 HD To: Ernie Luzar Cc: Polytropon , "freebsd-questions@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 13:27:20 -0000 On Wed, Apr 11, 2018 at 3:53 PM, Ernie Luzar wrote: > Polytropon wrote: > >> On Tue, 10 Apr 2018 20:14:36 -0400, Ernie Luzar wrote: >> >>> My mothers win10 pc has external usb 3tb sata drive with 600gb of data >>> that has hardware data problems. It will not mount on win10 pc. >>> >> >> Do not try any further with "Windows", it could do more damage. >> On "Windows 10", they use NTFS or FAT as file systems, and both >> are known to do the "funniest things" when getting into some >> inconsistent state ("silent" data corruption, data loss, no >> access due to damaged hiberfile, etc.). >> >> >> >> My mother has her whole digital life on the external drive. >>> >> >> Just restore from backup! Sorry, couldn'r resist... ;-) >> >> >> >> I can not find any win10 software to recover the data from a drive that >>> will not mount. >>> >> >> First of all, use tools that work with a copy of the damaged >> disk (or partition). Create this 1:1 copy first in a read-only >> manner, then work with the image. Do not try to repair the >> data "on-disk", it will probably destroy more data and reduce >> the chances of getting the "whole digital life" back. >> >> Seriously. I'm not making this up - I learned from my own >> faults. Check the mailing list archives for the terrible >> truth. :-) >> >> Do not use "Windows" any further without knowing _exactly_ >> what the problem is. >> >> >> >> I am thinking about using FreeBSD to recover the directory structure and >>> the files contained in them. Asking anyone if they know of a port that will >>> recover the data with their full file names in their directories? >>> >> >> That depends on the actual damage. This is how you should >> proceed: >> >> 1. Make a 1:1 copy of the disk or partition. Use that copy >> in all further steps. (Two copies are handy, in case you >> mess up one.) >> >> 2. Examine the data. What has happened? Can you use FUSE's >> NTFS mount program to mount it read-only? Can you use >> tools from the ntfs-tools package to repair things like >> the MFT. Or is it a FAT drive? Try mount_msdos instead, >> maybe even fsck_msdosfs. It could be sufficient to copy >> all the data (cp -R). >> >> 3. No luck getting the partition to mount? Assume the data >> is still there. Make yourself familiar with professional >> forensic tools. Start with the easy ones. If they get >> back what you expect to recover, well done. If not, use >> the more complex ones. >> >> On this mailing list, I have published my "famous list of >> data recovery tools" from time to time. Note that in order >> to make use of that list, you'll have to learn (!) about >> lower-level file system design, because you _must_ understand >> what you're doing. >> >> Here is this list. Note that I've added a few comments that >> might help in your specific situation (damaged FAT or NTFS >> drive): >> >> System: >> dd <- for making 1:1 copy >> fsck_ffs >> clri >> fsdb >> fetch -rR >> recoverdisk >> >> Ports: >> ddrescue <- if 1:1 copy is hard >> dd_rescue <- same >> ffs2recov >> magicrescue <- get data back (no structure) >> testdisk >> The Sleuth Kit: >> fls >> dls >> ils >> autopsy >> scan_ffs >> recoverjpeg >> foremost >> photorec >> fatback <- FAT >> ntfs-tools <- NTFS (ntfsfix, ntfsinfo, ntfsmount) >> >> Keep in mind: It will take time. There is no "one size fits >> all" GUI solution where you just click and icon and then have >> all your files (and the directory structure) back. IN worst >> case, what you're searching for has already been overwritten >> by "Windows" attempting to "repair" it. >> >> Your alternative: Take $500-3000 and ship the disk to a >> recovery business. If a "whole digital life" is worth that >> much money, you can give them a change. Note that there is >> absolutely no guarantee that they will succeed. >> >> Good luck! >> >> > > Thank you for your post. > > Lets talk about making a copy to work with. > Question is about unused space. Disk is 3TB with 600GB used. > How do I reduce the working copy size to the data only size of 600GB? > Using the dd command I don't see any way to tell it to ignore coping empty > space. > > Do I need another 3TB disk to hold the working copy? > Do I dd the bad HD to another HD of same size making a complete image copy > resulting in 2 ntfs hard drives? > > Or should I have the dd command create a single flat file of the bad disk > on the target disk? > > _______________________________________________ > > You may try http://www.system-rescue-cd.org/ SystemRescueCd is a Linux *system rescue disk* available as a bootable CD-ROM or USB stick for administrating or repairing your system and data after a crash. This is a Live Cd , without installing it , you can mount supported file system ( there are many including ntfs ) and copy files , etc. from that file system . I think , the most useful tool is this Live CD . It can be used in Linux and Windows computers . My suggestion is to learn how to use it before attempting any repair on the damaged disk . First try to copy files into another disk . http://www.system-rescue-cd.org/Download/ http://www.system-rescue-cd.org/manual/Backup_data_from_an_unbootable_windows_computer/ Backup data from an unbootable windows computer http://www.system-rescue-cd.org/manual/Backup_and_transfer_your_data_using_rsync/ Backup and transfer your data using rsync Thank you very much . Mehmet Erol Sanliturk From owner-freebsd-questions@freebsd.org Wed Apr 11 14:01:46 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE7EBF96E2A for ; Wed, 11 Apr 2018 14:01:45 +0000 (UTC) (envelope-from hasse@bara1.se) Received: from mail36c50.megamailservers.eu (mail226c50.megamailservers.eu [91.136.10.236]) (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 76C557CB2F for ; Wed, 11 Apr 2018 14:01:44 +0000 (UTC) (envelope-from hasse@bara1.se) X-POP-User: g.svalland@bredband.net Received: from ymer.bara1.se (ua-85-227-12-184.cust.bredbandsbolaget.se [85.227.12.184]) by mail36c50.megamailservers.eu (8.14.9/8.13.1) with ESMTP id w3BDcvPq012466 for ; Wed, 11 Apr 2018 13:38:59 +0000 Received: by ymer.bara1.se (Postfix, from userid 1001) id 671C6AD2FA; Wed, 11 Apr 2018 15:38:57 +0200 (CEST) Date: Wed, 11 Apr 2018 15:38:57 +0200 From: User Hasse To: freebsd-questions@freebsd.org Subject: dovecot error on boot up Message-ID: <20180411133857.GA29340@ymer.bara1.se> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="qMm9M+Fa2AknHoGS" Content-Disposition: inline X-PGP-Key: https://www.bara1.se/pubkey.asc User-Agent: Mutt/1.9.4 (2018-02-28) X-CTCH-RefID: str=0001.0A0B0205.5ACE0FF3.004E, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-CTCH-Score: 0.000 X-CTCH-Rules: X-CTCH-Flags: 0 X-CTCH-ScoreCust: 0.000 X-CSC: 0 X-CHA: v=2.2 cv=HrIGIwbS c=1 sm=1 tr=0 a=Vi41peb4gFDKnZJxK0Rnyg==:117 a=Vi41peb4gFDKnZJxK0Rnyg==:17 a=Kd1tUaAdevIA:10 a=Vt2AcnKqAAAA:8 a=mjMI4m5sAAAA:8 a=2HCHtqFq1r8g5XJJocwA:9 a=oH3q1eiL11crG4xX:21 a=5JwYw11sugywvXgk:21 a=CjuIK1q_8ugA:10 a=PErRU38B79oSvmQ9N7gA:9 a=ONNS8QRKHyMA:10 a=v10HlyRyNeVhbzM4Lqgd:22 a=8n7z28U-j86TceegZjyo:22 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 14:01:46 -0000 --qMm9M+Fa2AknHoGS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hello After latest update/upgrade I get this for me strange error on the boot up screen : dovecot error:t_readlink(var/run/dovecot//dovecot.conf) failed: readlink() failed: No such file or directory Then : Starting dovecot Dovecot seems to work as usual and I can't find anything in any logfiles. Googled it, and found this : https://www.mail-archive.com/dovecot@dovecot.org/msg73108.html Anybody else experienced this ? Or know how to fix ? Best Regards Geir Svalland hasse@ymer:/var/log % sudo dovecot -n # 2.3.1 (8e2f634): /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 11.1-RELEASE-p9 amd64 # Hostname: ymer auth_mechanisms = plain login base_dir = /var/run/dovecot/ disable_plaintext_auth = no first_valid_gid = 150 first_valid_uid = 150 last_valid_gid = 150 last_valid_uid = 150 log_path = /var/log/maillog log_timestamp = %Y-%m-%d %H:%M:%S mail_access_groups = mail mail_location = maildir:~/Maildir namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } passdb { args = /usr/local/etc/dovecot/dovecot-mysql.conf driver = sql } protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { address = * port = 143 } } service pop3-login { inet_listener pop3 { address = * port = 110 } } ssl_cert = Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 241D0F98306 for ; Wed, 11 Apr 2018 14:21:17 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 879E37FBC9 for ; Wed, 11 Apr 2018 14:21:16 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.30.67]) by mrelayeu.kundenserver.de (mreue002 [212.227.15.167]) with ESMTPA (Nemesis) id 0M0H6r-1eCe6036Jp-00uZBT; Wed, 11 Apr 2018 16:21:13 +0200 Date: Wed, 11 Apr 2018 16:21:13 +0200 From: Polytropon To: Ernie Luzar Cc: "freebsd-questions@freebsd.org" Subject: Re: Recover directory tree with files from win10 HD Message-Id: <20180411162113.e2b96a5a.freebsd@edvax.de> In-Reply-To: <5ACE0543.7030607@gmail.com> References: <5ACD536C.5010407@gmail.com> <20180411113740.2b245110.freebsd@edvax.de> <5ACE0543.7030607@gmail.com> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:jC3oxXJgdTClYggqgA69dw9eUSh3K+aieKQIFu9EVEKwUCa6vJc +aTdI/i5832ztN9B/USkfwDA+JmOv11wxm27YzGK7cqxDrv2Rn8MnTZoGEqSNwgQxNlEmGL l8XFWHhdG2lZVD3mzoyTFrRfYD4AV45Tib7QW1i2wKCcCoGA6G9y0OhO5WX12QjzSHa+m/x Nzbw4Ci53UMp4fDhsbZ3Q== X-UI-Out-Filterresults: notjunk:1;V01:K0:/CiSAKSRLPM=:/4WITodcybtR1SXwXtxjFk yFng8iA/Sqnx4f+dgg8cFzsM30KXa6Z7aWM0x9H/ebuUEfDp/RKl3wTL6uEV9GWu6TzjwT0yy h7jIrQ9dJnO4sNTvVvJwF0C2cHy9k3ptePVMIvCZ2rinrX4KQfCZr3e0CHV/qj3/1XbJbEh1M xJo8H0Mce020NdWvPT+gVmRS9pYgmGcj4IYj15GNoIRQlPYu6laXoUchgl9xncKKYpqoMZSLq RQvvQ7IHKTxmjkFp8PlwUXN7z4fatL69GjN7QsyimGbV2WueerBj3Ld0bNH1ytzlvEe6QeW3P m2RBjWpqF+ZOyrPlnUUsulw929LNLer/hw/wVI0VeCch7aolglCNoVcY4UzRzhfRItD+2dWGp fQz/kbq+ti3tRbmNt6aW8lUtohZNHvAz0uG3jAKulrr2zxax74FOyaBpr/XYh6H/5XKa0Zpld Lg2MJHOmaJCCgO4lcnDktouIex7wqULiRPDbVU7t4wxkUpG405O1kN9kYARuodJ2DDEvAv5/y mrlaph77xGyRLxuVRGS/GHn1S1J2QiQKh+PxjDOY7JYRQdD0CIYYBrL9uuGAPbPiaNVjsuYbc lRUVzCN0W3kYcFZBx20xK6p/imEK38xZL0VtrP8So50UUBGA0p8EbIsyg2rv/tvzfNbQgXXPB 0VBY1v0fZMT7579Y8sCe68lhg4YD7A1ReKaMFx0O6Hc7SeINleTgR2jLNOH8QqFTnnrrGR7Bu AQK1lQauAVnzVjHg6yyfDgtCN/NAxdvejBA+0BufvXYh89PmLTODRBZWU5U= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 14:21:17 -0000 On Wed, 11 Apr 2018 08:53:23 -0400, Ernie Luzar wrote: > Polytropon wrote: > > On Tue, 10 Apr 2018 20:14:36 -0400, Ernie Luzar wrote: > >> My mothers win10 pc has external usb 3tb sata drive with 600gb of data > >> that has hardware data problems. It will not mount on win10 pc. > > > > Do not try any further with "Windows", it could do more damage. > > On "Windows 10", they use NTFS or FAT as file systems, and both > > are known to do the "funniest things" when getting into some > > inconsistent state ("silent" data corruption, data loss, no > > access due to damaged hiberfile, etc.). > > > > > > > >> My > >> mother has her whole digital life on the external drive. > > > > Just restore from backup! Sorry, couldn'r resist... ;-) > > > > > > > >> I can not find > >> any win10 software to recover the data from a drive that will not mount. > > > > First of all, use tools that work with a copy of the damaged > > disk (or partition). Create this 1:1 copy first in a read-only > > manner, then work with the image. Do not try to repair the > > data "on-disk", it will probably destroy more data and reduce > > the chances of getting the "whole digital life" back. > > > > Seriously. I'm not making this up - I learned from my own > > faults. Check the mailing list archives for the terrible > > truth. :-) > > > > Do not use "Windows" any further without knowing _exactly_ > > what the problem is. > > > > > > > >> I am thinking about using FreeBSD to recover the directory structure and > >> the files contained in them. Asking anyone if they know of a port that > >> will recover the data with their full file names in their directories? > > > > That depends on the actual damage. This is how you should > > proceed: > > > > 1. Make a 1:1 copy of the disk or partition. Use that copy > > in all further steps. (Two copies are handy, in case you > > mess up one.) > > > > 2. Examine the data. What has happened? Can you use FUSE's > > NTFS mount program to mount it read-only? Can you use > > tools from the ntfs-tools package to repair things like > > the MFT. Or is it a FAT drive? Try mount_msdos instead, > > maybe even fsck_msdosfs. It could be sufficient to copy > > all the data (cp -R). > > > > 3. No luck getting the partition to mount? Assume the data > > is still there. Make yourself familiar with professional > > forensic tools. Start with the easy ones. If they get > > back what you expect to recover, well done. If not, use > > the more complex ones. > > > > On this mailing list, I have published my "famous list of > > data recovery tools" from time to time. Note that in order > > to make use of that list, you'll have to learn (!) about > > lower-level file system design, because you _must_ understand > > what you're doing. > > > > Here is this list. Note that I've added a few comments that > > might help in your specific situation (damaged FAT or NTFS > > drive): > > > > System: > > dd <- for making 1:1 copy > > fsck_ffs > > clri > > fsdb > > fetch -rR > > recoverdisk > > > > Ports: > > ddrescue <- if 1:1 copy is hard > > dd_rescue <- same > > ffs2recov > > magicrescue <- get data back (no structure) > > testdisk > > The Sleuth Kit: > > fls > > dls > > ils > > autopsy > > scan_ffs > > recoverjpeg > > foremost > > photorec > > fatback <- FAT > > ntfs-tools <- NTFS (ntfsfix, ntfsinfo, ntfsmount) > > > > Keep in mind: It will take time. There is no "one size fits > > all" GUI solution where you just click and icon and then have > > all your files (and the directory structure) back. IN worst > > case, what you're searching for has already been overwritten > > by "Windows" attempting to "repair" it. > > > > Your alternative: Take $500-3000 and ship the disk to a > > recovery business. If a "whole digital life" is worth that > > much money, you can give them a change. Note that there is > > absolutely no guarantee that they will succeed. > > > > Good luck! > > > > > Thank you for your post. > > Lets talk about making a copy to work with. > Question is about unused space. Disk is 3TB with 600GB used. > How do I reduce the working copy size to the data only size of 600GB? > Using the dd command I don't see any way to tell it to ignore coping > empty space. If I remember correctly, dd will deal with trailing zeroes just fine. However, it matters how the data is placed on the disk (as contiguous used space - or fragmented across a bigger amount of available storage). > Do I need another 3TB disk to hold the working copy? That would be good, especially because for n bytes to recover, you'll need at least 2*n bytes (1 for the copy to work with, 1 for the recovered data). Having 3*n bytes (additional 1 for a "master copy" in case you messed up your initial copy) is never a bad idea. > Do I dd the bad HD to another HD of same size making a complete image > copy resulting in 2 ntfs hard drives? That is possible, but there is a much easier way: Initialize the new hard disk (for example as a simple UFS volume) and then create the image onto that drive (using a temporary mountpoint). Let's say da0 is the defective disk, da1 is your new disk. Then you can do something like this (possible optimization left aside for now): # newfs da1 # mount -t ufs /dev/da1 /mnt # dd if=/dev/da0s1 of=/mnt/win10.img bs=1m You can vary the bs= parameter to a better value (to saturate what the drive connections provide), maybe 10m or even 100m will work. In this example, da0s1 refers to the first (and probably only) NTFS partition. In case you get reading errors (check console log!), cancel the operation and use dd_rescue (or ddrescue) instead. If you succeeded getting an image file, connect it to a virtual node and try to mount it: # mdconfig -a -t vnode -u 0 /mnt/win10.img # mkdir /try # mount_ntfs -r /dev/md0 /try ... copy data ... # umount /try # mdconfig -d -u 0 Pay attention to try a read-only mount first. > Or should I have the dd command create a single flat file of the bad > disk on the target disk? Exactly that. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Wed Apr 11 14:29:44 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0809F98C85 for ; Wed, 11 Apr 2018 14:29:44 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 14B758233F for ; Wed, 11 Apr 2018 14:29:43 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.30.67]) by mrelayeu.kundenserver.de (mreue006 [212.227.15.167]) with ESMTPA (Nemesis) id 0MRNhj-1etzYU0VSh-00UdVO; Wed, 11 Apr 2018 16:24:25 +0200 Date: Wed, 11 Apr 2018 16:24:24 +0200 From: Polytropon To: Mehmet Erol Sanliturk Cc: Ernie Luzar , Polytropon , "freebsd-questions@freebsd.org" Subject: Re: Recover directory tree with files from win10 HD Message-Id: <20180411162424.de298baa.freebsd@edvax.de> In-Reply-To: References: <5ACD536C.5010407@gmail.com> <20180411113740.2b245110.freebsd@edvax.de> <5ACE0543.7030607@gmail.com> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:PkS7wtanp+edSKTIpTJJIr57Oo+7va0jQxdwEewnXtWCHrd9iRC b1yLSHl80GrJ2E1LL2Mqzm3V7ZAhi6xXU275Nstm7Xskd7S/+gPRUlPqu7Y2Uxz75Z6fFVC AHHTGJHGwsPN9lII//BqedT4paNsRooGxFbojI5MpcTLOvevGHHbOCEIaOh4T+MulVbmdzn tFBPEmrywlo/ar8z++hlQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:zQVUfgrCfFA=:fQOU4mEAmCMIfHQe+RhwaT RIxoYr4O+bvzuIrrSWquTWqIdlXmadDwTti3fHFsj4bmETZoaJQCozc7qx5r8riD22CXkjmy/ +S8X5FOTkHENXkiILIOsKFoKiHoj8Y7Gebfpx/LGNVBDvYUZL0Ts92sXKkLqOU5k1+VUvaIu0 x0TteOCwG2eJFBue60a5wORzERYP2GamxehD9rJtl1DBjvtDKroljTndCbNh8YyeC/CgTCrJ8 42WM/FINPXr75DsmVY8U6QYbkevFuNjZUbTTW83AxdHdcVOQItSo5sDSQu3jY222REPMnH8d7 FyLMQMroqmQm2UP5FGmLOQkVwbyRMfENbCyg0zk5uC7mHjETdhyS9MpGFoY4uqcsCsHHvweIn vuaIRsRXFL1TkLWGS2vB0ACPeEWok948FgykXpm+5COF6Ht/1BzfzEeKXD/Z1DXVRc5rT1Yis 2g5KcMM/3Bl+e/zO3FLNpl6l33k0vLMxx8znSJBA0mK9ahvEHgIv84dGgHj4phVyG3MhjNGLa F772QmdSO2ARrZFR8G6eo3EOymgAjMSUEynaUfuKuQI+udEmYvpPdB58GbC86jj+Mo50C+jz9 HvNxoL/lgQZZ78wcrmj9tFWWIpzea3omiGL3d1ec6r7oIQANEp4vSefyW7ADVGTHAVsseRMfU Ms7RbrQYPSRxwSiXN8zdzuq7rEWmOJIdqOSLrQxWW66Eo8iDQlEGY6u50INucwC4oOLYDKVDE gHQXx9YLAw4o/AeRHeLEXBUhBWvA2vuYrNSlNQp64Hnyh9Bxj+Q6koRft+I= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 14:29:45 -0000 On Wed, 11 Apr 2018 16:26:38 +0300, Mehmet Erol Sanliturk wrote: > You may try > > > > http://www.system-rescue-cd.org/ > > > SystemRescueCd is a Linux *system rescue disk* available as a bootable > CD-ROM or USB stick > > for administrating or repairing your system and data after a crash. > > > This is a Live Cd , without installing it , you can mount supported file > system ( there are many including ntfs ) and copy files , etc. from that > file system . > I think , the most useful tool is this Live CD . It can be used in Linux > and Windows computers . > > My suggestion is to learn how to use it before attempting any repair on the > damaged disk . First try to copy files into another disk . This is also a possible way. Two things to note here: Make sure you have free disk space on a different disk in the system, or maybe a NAS you can access, to write your result files to. This live CD works very well for smaller problems that can be fixed "on-disk" / "in-place" where no additional copy needs to be created. But be very careful with such an assumption. Additionally, I'd like to mention that Kali Linux also has a (smaller) set of data recovery tools and further means of diagnostics which can be used to initially check what the problem is. Without knowing the problem, repair is "trial & error", and doing this with the only copy of the disk can lead to a complete data loss. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Wed Apr 11 14:38:10 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9BD3AF99756 for ; Wed, 11 Apr 2018 14:38:10 +0000 (UTC) (envelope-from drew@mykitchentable.net) 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 3169784B6F for ; Wed, 11 Apr 2018 14:38:10 +0000 (UTC) (envelope-from drew@mykitchentable.net) Received: by mailman.ysv.freebsd.org (Postfix) id E3633F99753; Wed, 11 Apr 2018 14:38:09 +0000 (UTC) Delivered-To: questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C11C3F99752 for ; Wed, 11 Apr 2018 14:38:09 +0000 (UTC) (envelope-from drew@mykitchentable.net) Received: from ewout01.mycci.net (ewout01.mycci.net [66.60.130.50]) by mx1.freebsd.org (Postfix) with ESMTP id 4E57484B6C for ; Wed, 11 Apr 2018 14:38:08 +0000 (UTC) (envelope-from drew@mykitchentable.net) Received: from smtp1.surewest.net ([66.60.130.145]) by ewout01.mycci.net ({dfaaa318-551d-4a0a-8038-7c31cf31c4f6}) via TCP (outbound) with ESMTP id 20180411143442948_0000; Wed, 11 Apr 2018 07:34:42 -0700 X-RC-FROM: Received: from ca01-cl01-vpl-nges-mailq-002.localdomain (mailq.mycci.net [66.60.130.61]) by smtp1.surewest.net (Postfix) with ESMTP id 7DF5C895F0; Wed, 11 Apr 2018 07:28:26 -0700 (PDT) Received: from blacklamb.mykitchentable.net (mykitchentable.net [207.231.88.111]) (Authenticated sender: imacamper1@surewest.net) by ca01-cl01-vpl-nges-mailq-002.localdomain (Postfix) with ESMTPSA id CC668DC0017; Wed, 11 Apr 2018 07:34:41 -0700 (PDT) Received: from [127.0.0.1] (blacksheep.mykitchentable.net [192.168.1.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: drew) by blacklamb.mykitchentable.net (Postfix) with ESMTPSA id E7AF8D7E0C; Wed, 11 Apr 2018 07:34:19 -0700 (PDT) Subject: Re: How To Update From 9.1? To: Doug Hardie Cc: "questions@freebsd.org" References: From: Drew Tomlinson Message-ID: Date: Wed, 11 Apr 2018 07:34:15 -0700 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-MAG-OUTBOUND: surewest.redcondor.net@66.60.130.145/32 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 14:38:10 -0000 On 4/10/2018 10:18 PM, Doug Hardie wrote: >> On 10 April 2018, at 18:24, Drew Tomlinson wrote: >> >> I've got an old system I'm trying to get current. >> >> # uname -a >> FreeBSD vm.mykitchentable.net 9.1-RELEASE-p1 FreeBSD 9.1-RELEASE-p1 #0: Tue May 9 09:19:33 PDT 2017 drew@vm.mykitchentable.net:/usr/obj/usr/src/sys/GENERIC amd64 >> >> So I consult the handbook and various list posts and find that I should be able to use freebsd-update. Specifically I've done: >> >> I've tried deleting /var/db/freebsd-update and doing the 'fetch install' over. I've tried deleting /usr/src and downloading a new copy of 9.3 source code. >> >> Overall, I really don't know what I need to do as I've never done a binary update before. I don't even know if 'src/src' looks reasonable but I thought I'd give it a try. Can anyone point me in the right direction? I'd appreciate the nudge. > This is a common issue for 9 and earlier systems. I understand it may also affect some 10s. Basically there are some patches available in various postings to bug reports. If you find both of them, it should work, but you have to manually update as line numbers are not consistent. The easier approach is probably to get a copy of freebsd-update from a newer system. It's a script so that works fine. I have used the script from 11.0 to upgrade some 9.x systems. > > -- Doug Thank you for your reply.  I grabbed a copy of freebsd-update from an 11.1 system that I have and copied it to /usr/sbin/freebsd-update.  However, no joy.  After deleting the contents of /var/db/freebsd-update, I did the following: ---BEGIN--- # freebsd-update fetch install src component not installed, skipped Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching public key from update6.freebsd.org... done. Fetching metadata signature for 9.1-RELEASE from update6.freebsd.org... done. Fetching metadata index... done. Fetching 2 metadata files... done. Inspecting system... done. Preparing to download files... done. No updates needed to update system to 9.1-RELEASE-p24. WARNING: FreeBSD 9.1-RELEASE-p1 HAS PASSED ITS END-OF-LIFE DATE. Any security issues discovered after Wed Dec 31 16:00:00 PST 2014 will not have been corrected.  # freebsd-update -r 9.3-RELEASE upgrade src component not installed, skipped Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata signature for 9.1-RELEASE from update5.freebsd.org... done. Fetching metadata index... done. Fetching 1 metadata files... done. Inspecting system... done. The following components of FreeBSD seem to be installed: The following components of FreeBSD do not seem to be installed: Does this look reasonable (y/n)? y Fetching metadata signature for 9.3-RELEASE from update5.freebsd.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Inspecting system... done. Preparing to download files... done. No updates needed to update system to 9.3-RELEASE-p53. touch: f465c3739385890c221dff1a05e578c6cae0d0430e46996d319db7439f884336-install/kernelfirst: No such file or directory To install the downloaded upgrades, run "/usr/sbin/freebsd-update install". ---END--- I got similar results when attempting to go to 10.4-RELEASE as well.  Any other ideas?  Or is my best bet at this point to just build the GENERIC kernel from source?  If so, can I go straight to 11.1 and recompile all my ports?  Or should I take some intermediate steps? Thanks for your help, Drew -- Like card tricks? Visit The Alchemist's Warehouse to learn card magic secrets for free! http://alchemistswarehouse.com From owner-freebsd-questions@freebsd.org Wed Apr 11 15:05:16 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8099F9BCBA for ; Wed, 11 Apr 2018 15:05:15 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-oln040092007082.outbound.protection.outlook.com [40.92.7.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT TLS CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5A2D86CEED for ; Wed, 11 Apr 2018 15:05:14 +0000 (UTC) (envelope-from carmel_ny@outlook.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=CKifpWujbzsCa816ERvllMEgencABqkcGSC7fsNRPqE=; b=byfXYYrlRlMXc76KpL4+jjom656MvGd9YbcUFEbTu4vVSa6+jKnCeOnZBvqnIBNVWYYYZhlZCC599tLgX8mXvK8S7ZoHBXimTWHAulsDWuttCbLeZ8wRtEWACQQx6jN+hcGRCdIauAJXNAUxXL3g6INrDZa7mviITiU2DsaZbQedjgmCRiEcx3XW29pKQRe62dfGH0Hj0vSMHTc2/uu7w7yyUE+hvTG3xz/bh49qSH8JNfMoo/zBEsuk1R+eR4uyGowq5hNH4T7iO0MTxuv716tDUmP0DOIE+9Zv/kRPhPsIJVEvqTJWPjcLtNZN5ZsA+hTomOznGci/A54t8jbc0w== Received: from BY2NAM03FT061.eop-NAM03.prod.protection.outlook.com (10.152.84.51) by BY2NAM03HT240.eop-NAM03.prod.protection.outlook.com (10.152.85.252) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.653.8; Wed, 11 Apr 2018 15:05:13 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com (10.152.84.55) by BY2NAM03FT061.mail.protection.outlook.com (10.152.85.107) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.653.8 via Frontend Transport; Wed, 11 Apr 2018 15:05:13 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com ([fe80::f020:88a4:c0b7:3c5b]) by BN6PR2001MB1730.namprd20.prod.outlook.com ([fe80::f020:88a4:c0b7:3c5b%5]) with mapi id 15.20.0675.009; Wed, 11 Apr 2018 15:05:13 +0000 From: Carmel NY To: FreeBSD Subject: Re: dovecot error on boot up Thread-Topic: dovecot error on boot up Thread-Index: AQHT0aZ9H5qs/l+YxEyg+g+VEPo68g== Date: Wed, 11 Apr 2018 15:05:13 +0000 Message-ID: References: <20180411133857.GA29340@ymer.bara1.se> In-Reply-To: <20180411133857.GA29340@ymer.bara1.se> Reply-To: FreeBSD Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-incomingtopheadermarker: OriginalChecksum:478E4C61DFFD595A1E1D65E039F7D4FDDDE0E2C30F20FBCC32658D07D80704BD; UpperCasedChecksum:788F1FA7288BCB7517B1A631A2BE5378F02250234BEA5DD04681D6D4D79CD8D5; SizeAsReceived:7015; Count:47 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [v3Z3UZl2O4G1apJfcWlaoX5Qmej6JW4t] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; BY2NAM03HT240; 7:oY3AOJyyS20QliuD68wDIJ0AN145Qzlml3S08FdoJ7aphoCjwXQJxs0vTiCU93lzrs7KON8O8upFUiB3R7N3d7gl484qCVXW03u8o5zL4RLQeR1W+qTe3RY6Nmzp9hy4P3gyJwVKDGhd3Ur4XgxIkX9W6Dc3XXea0dmLLoweINOadaBnPad6e9/I3m1OEibfuDDskIWUxwMwa9hgzVygRbFJEXxILTETOGqqW0ypBePo3Igxij+2HWv7WG/MWRU6 x-incomingheadercount: 47 x-eopattributedmessage: 0 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1601125374)(1603101448)(1701031045); SRVR:BY2NAM03HT240; x-ms-traffictypediagnostic: BY2NAM03HT240: x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:BY2NAM03HT240; BCL:0; PCL:0; RULEID:; SRVR:BY2NAM03HT240; x-forefront-prvs: 0639027A9E x-forefront-antispam-report: SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:BY2NAM03HT240; H:BN6PR2001MB1730.namprd20.prod.outlook.com; FPR:; SPF:None; LANG:; x-microsoft-antispam-message-info: NciVHeXUCLwOPZchJ9w0kog03Li5kHgbgI1n1ppWjxeutrgZrbn9sxR+1RZ9VT39whcVKO6ku8y2pX4BIgQ5zgfof3mIQ03FvK5xW05gAxk+YwAnsLl1KbETOKio2aSLYwCIwIbOoGO0PAc2O74DCsexdhpKYc4fJXOFaAzy5pnRR8uric7dTNulIdLJD6Zd Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Office365-Filtering-Correlation-Id: 6bece703-9204-4a7a-15c3-08d59fbd9fe0 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 9a4e3081-9524-43cf-bfc3-dcaef82d5da1 X-MS-Exchange-CrossTenant-Network-Message-Id: 6bece703-9204-4a7a-15c3-08d59fbd9fe0 X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 9a4e3081-9524-43cf-bfc3-dcaef82d5da1 X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Apr 2018 15:05:13.2759 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2NAM03HT240 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 15:05:16 -0000 On Wed, 11 Apr 2018 15:38:57 +0200, User Hasse stated: >Hello >After latest update/upgrade I get this for me strange error on the >boot up screen : > >dovecot error:t_readlink(var/run/dovecot//dovecot.conf) failed: readlink() >failed: No such file or directory Then : Starting dovecot > >Dovecot seems to work as usual and I can't find anything in any logfiles. > >Googled it, and found this : >https://www.mail-archive.com/dovecot@dovecot.org/msg73108.html > >Anybody else experienced this ? Or know how to fix ? > >Best Regards >Geir Svalland > >hasse@ymer:/var/log % sudo dovecot -n ># 2.3.1 (8e2f634): /usr/local/etc/dovecot/dovecot.conf ># OS: FreeBSD 11.1-RELEASE-p9 amd64 ># Hostname: ymer >auth_mechanisms =3D plain login >base_dir =3D /var/run/dovecot/ >disable_plaintext_auth =3D no >first_valid_gid =3D 150 >first_valid_uid =3D 150 >last_valid_gid =3D 150 >last_valid_uid =3D 150 >log_path =3D /var/log/maillog >log_timestamp =3D %Y-%m-%d %H:%M:%S >mail_access_groups =3D mail >mail_location =3D maildir:~/Maildir >namespace inbox { > inbox =3D yes > location =3D > mailbox Drafts { > special_use =3D \Drafts > } > mailbox Junk { > special_use =3D \Junk > } > mailbox Sent { > special_use =3D \Sent > } > mailbox "Sent Messages" { > special_use =3D \Sent > } > mailbox Trash { > special_use =3D \Trash > } > prefix =3D >} >passdb { > driver =3D pam >} >passdb { > args =3D /usr/local/etc/dovecot/dovecot-mysql.conf > driver =3D sql >} >protocols =3D imap >service auth { > unix_listener /var/spool/postfix/private/auth { > group =3D postfix > mode =3D 0660 > user =3D postfix > } >} >service imap-login { > inet_listener imap { > address =3D * > port =3D 143 > } >} >service pop3-login { > inet_listener pop3 { > address =3D * > port =3D 110 > } >} >ssl_cert =3D ssl_dh =3D # hidden, use -P to show it >ssl_key =3D # hidden, use -P to show it >userdb { > driver =3D passwd >} > Yes, I have the same problem with a FreeBSD 11.1-RELEASE-p9 amd64. I am als= o using ZFS if that makes any difference, and I cannot see how it would. --=20 Carmel From owner-freebsd-questions@freebsd.org Wed Apr 11 15:26:00 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7C5CEF9D384 for ; Wed, 11 Apr 2018 15:26:00 +0000 (UTC) (envelope-from dave.mehler@gmail.com) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E926470D08 for ; Wed, 11 Apr 2018 15:25:59 +0000 (UTC) (envelope-from dave.mehler@gmail.com) Received: by mail-wm0-x236.google.com with SMTP id t67so5085662wmt.0 for ; Wed, 11 Apr 2018 08:25:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=h/zm2YDe0ooKinA4NR9yeWUcqo7mQoP6/F6itp6p8pE=; b=LQFKLvHuqTlagOG1GV3d7BulGyyBNz6fqBHOfg0kHGrreIRiI0n8p+5lPAsBlxqVVz M2oVaGpOPolN/MkJWi6Qvs21EfYshRE//l3LBZtQvg6A0H7GW3wVrePtgmexE/Aj9YwE uYHjxlWo3D2Wf+KKNAKcpHMHP4005xLYDyz1TjAmyZiORhi/cyXI5eG42d2vZhID9iDr y76aY/RLj26R8lR9ZvdVvJUZlT/kSPBGMqJ/cYaxCaa/MstOXIm+MDTWiGigcMeePqIk dJbNA+A+UzMaPfzJeSoO07yJwQRvPCOyO9/8JpCwmI9iOD1tue3WcCsvLXrJvrhKjyHe 9coQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=h/zm2YDe0ooKinA4NR9yeWUcqo7mQoP6/F6itp6p8pE=; b=or/ngvphOKqQurYSIXIqZ5mBzc5mfym5zRT/64wNZDkva5BJT5iIOkyuPZYmlK6Dgl EkSQ4UrCO+2ym7GwV5piEPIagBeqV+6tT+w6S6J33RTO4ZPsLFg4mQXMB40jhHLSw4YZ 32FNF97r2SgRMVtsYD44q+WKjW3FGs0JkQ8PtvM1reGbC7rQdbXdQCoFEEcFyyXn+hjF wMUx2mxX5ekYJiMO6Zha13USyW5j3DC3xTI+7ZJkSketZc2CChK+5HZ0VOYxj2aLwVyf GswH+MTttNy6L6wS575ZMPJGKeSem9rhFeKzfstqJ9OkpYh2rbcewUvIxaViy7Y4VfUz /RIQ== X-Gm-Message-State: ALQs6tBHdWTjV5YJjbG3vNVIT8KEeOaTf7PZ1ecEzeJ9QKBqdbu3bdVu v6kTVfiDjg1kqv/JMSJ6E3XR+hEagG8Bbp9d3SQ= X-Google-Smtp-Source: AIpwx49X9+bfzJYQm43saLxqSJT/FIumXvqnKNBTB4XuPdwL2Sry7yWCVGAuJAWZJZxrUYvsobB5Qsir+vMGRZjctZo= X-Received: by 10.28.153.12 with SMTP id b12mr3164144wme.104.1523460358572; Wed, 11 Apr 2018 08:25:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.131.197 with HTTP; Wed, 11 Apr 2018 08:25:57 -0700 (PDT) In-Reply-To: References: <20180411133857.GA29340@ymer.bara1.se> From: David Mehler Date: Wed, 11 Apr 2018 11:25:57 -0400 Message-ID: Subject: Re: dovecot error on boot up To: FreeBSD Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 15:26:00 -0000 Hello, I'm using FreeBSD 11.1 amd64 p9 and Dovecot latest from ports and not having this issue. I am not using ZFS I don't know if that helps or not. Hth Dave. On 4/11/18, Carmel NY wrote: > On Wed, 11 Apr 2018 15:38:57 +0200, User Hasse stated: > >>Hello >>After latest update/upgrade I get this for me strange error on the >>boot up screen : >> >>dovecot error:t_readlink(var/run/dovecot//dovecot.conf) failed: readlink() >>failed: No such file or directory Then : Starting dovecot >> >>Dovecot seems to work as usual and I can't find anything in any logfiles. >> >>Googled it, and found this : >>https://www.mail-archive.com/dovecot@dovecot.org/msg73108.html >> >>Anybody else experienced this ? Or know how to fix ? >> >>Best Regards >>Geir Svalland >> >>hasse@ymer:/var/log % sudo dovecot -n >># 2.3.1 (8e2f634): /usr/local/etc/dovecot/dovecot.conf >># OS: FreeBSD 11.1-RELEASE-p9 amd64 >># Hostname: ymer >>auth_mechanisms = plain login >>base_dir = /var/run/dovecot/ >>disable_plaintext_auth = no >>first_valid_gid = 150 >>first_valid_uid = 150 >>last_valid_gid = 150 >>last_valid_uid = 150 >>log_path = /var/log/maillog >>log_timestamp = %Y-%m-%d %H:%M:%S >>mail_access_groups = mail >>mail_location = maildir:~/Maildir >>namespace inbox { >> inbox = yes >> location = >> mailbox Drafts { >> special_use = \Drafts >> } >> mailbox Junk { >> special_use = \Junk >> } >> mailbox Sent { >> special_use = \Sent >> } >> mailbox "Sent Messages" { >> special_use = \Sent >> } >> mailbox Trash { >> special_use = \Trash >> } >> prefix = >>} >>passdb { >> driver = pam >>} >>passdb { >> args = /usr/local/etc/dovecot/dovecot-mysql.conf >> driver = sql >>} >>protocols = imap >>service auth { >> unix_listener /var/spool/postfix/private/auth { >> group = postfix >> mode = 0660 >> user = postfix >> } >>} >>service imap-login { >> inet_listener imap { >> address = * >> port = 143 >> } >>} >>service pop3-login { >> inet_listener pop3 { >> address = * >> port = 110 >> } >>} >>ssl_cert = >ssl_dh = # hidden, use -P to show it >>ssl_key = # hidden, use -P to show it >>userdb { >> driver = passwd >>} >> > > Yes, I have the same problem with a FreeBSD 11.1-RELEASE-p9 amd64. I am > also > using ZFS if that makes any difference, and I cannot see how it would. > > -- > Carmel > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > From owner-freebsd-questions@freebsd.org Wed Apr 11 15:54:37 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D23FAF9F469 for ; Wed, 11 Apr 2018 15:54:36 +0000 (UTC) (envelope-from m.e.sanliturk@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 5DCE378CBF for ; Wed, 11 Apr 2018 15:54:36 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 21BE5F9F468; Wed, 11 Apr 2018 15:54:36 +0000 (UTC) Delivered-To: questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F10E1F9F467 for ; Wed, 11 Apr 2018 15:54:35 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-ot0-x230.google.com (mail-ot0-x230.google.com [IPv6:2607:f8b0:4003:c0f::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 80F4878CBB for ; Wed, 11 Apr 2018 15:54:35 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-ot0-x230.google.com with SMTP id v6-v6so2529615otj.12 for ; Wed, 11 Apr 2018 08:54:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=14EP/VYbmRqntNtVxMJJTaf3BuEyMp05EKzPuBQFkvQ=; b=HXNjt+kxdnncvYc6wF1biqabMcO/Q3qHR/0oBzzn/3s/CKNlavrL5Zbymd/JslSY3j 2zCQqZRpf4tEETk6vof4IA9rGkYxWb+A4y1nSEj5FmLTN3uM/VlRVa9rtCj+U/dmxthP oS+GGBSmvUxlg8ZpUHVmlZlGbIcutCD/6pJXuva5mMwu9Plam5KE49ShzHEBeO+wsOXc zQLuMzpbNGJKWRHOkE42oLLgUi1cM1tcOXQ4imsUofqMeMaEo9ZOBDYHSkOHLt+Hbpp1 Mv+9esEDU/8rL0qSfh0TtqhdPK3JhKije3iRZIxqNefSkSNvKhOkKOFx5DsLLk4VaY/O s9Ug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=14EP/VYbmRqntNtVxMJJTaf3BuEyMp05EKzPuBQFkvQ=; b=bunxR86GMzrbnFOmRQUWeR3TASvMKFY+2iFQ50d7tw+dfhqAlMyaRci+F4PnOJ1SS/ kvqKPm0JMIo604IkdjUP70QpLX1ho1FaUIhZEjk2/easbXor+4zKtXZtXAJip6GRV4+a 1JVAwXSFYz0/l1bL8Ajj3iHZRsNbK26CYeHepDueZkcc/HS9yw2ZVkd8fTNH75a8QUwe waeWzdMAeN38EGzWXEVJmSUV6CbMbQRJdR16qbJi0OtqbH1Ip1HSVkYFV0jx+uZyWPLe xE/6zXuBAoe0uC0j4uaavEFo8Sd193Npo1aybjFW2rTKBibK4h8B0rqkDE92YkrTW4Ai +GiQ== X-Gm-Message-State: ALQs6tCAlnmre2P6lPGCwb5ms6dtkrP9u/yZmuc1I6tyOreIjgjI3wnE 7qKH4hgWGMV2wI7RfIXxxchbgP8/DXnVWA0Dx/Y= X-Google-Smtp-Source: AIpwx48QZq8WZu/cHaXto0PPeh85fSCr7d/5NhMWBG2OlEqqBjwcd9nhQcJZgrSedjsSfceJ3asZBMdeUznWKE7hU3Q= X-Received: by 2002:a9d:184c:: with SMTP id t12-v6mr3400378ott.6.1523462074992; Wed, 11 Apr 2018 08:54:34 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a9d:1a1:0:0:0:0:0 with HTTP; Wed, 11 Apr 2018 08:53:54 -0700 (PDT) In-Reply-To: References: From: Mehmet Erol Sanliturk Date: Wed, 11 Apr 2018 18:53:54 +0300 Message-ID: Subject: Re: How To Update From 9.1? To: Drew Tomlinson Cc: Doug Hardie , "questions@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 15:54:37 -0000 On Wed, Apr 11, 2018 at 5:34 PM, Drew Tomlinson wrote: > > On 4/10/2018 10:18 PM, Doug Hardie wrote: > >> On 10 April 2018, at 18:24, Drew Tomlinson >>> wrote: >>> >>> I've got an old system I'm trying to get current. >>> >>> # uname -a >>> FreeBSD vm.mykitchentable.net 9.1-RELEASE-p1 FreeBSD 9.1-RELEASE-p1 #0: >>> Tue May 9 09:19:33 PDT 2017 drew@vm.mykitchentable.net:/usr/obj/usr/src/sys/GENERIC >>> amd64 >>> >>> So I consult the handbook and various list posts and find that I should >>> be able to use freebsd-update. Specifically I've done: >>> >>> I've tried deleting /var/db/freebsd-update and doing the 'fetch install' >>> over. I've tried deleting /usr/src and downloading a new copy of 9.3 >>> source code. >>> >>> Overall, I really don't know what I need to do as I've never done a >>> binary update before. I don't even know if 'src/src' looks reasonable but >>> I thought I'd give it a try. Can anyone point me in the right direction? >>> I'd appreciate the nudge. >>> >> This is a common issue for 9 and earlier systems. I understand it may >> also affect some 10s. Basically there are some patches available in >> various postings to bug reports. If you find both of them, it should work, >> but you have to manually update as line numbers are not consistent. The >> easier approach is probably to get a copy of freebsd-update from a newer >> system. It's a script so that works fine. I have used the script from >> 11.0 to upgrade some 9.x systems. >> >> -- Doug >> > > Thank you for your reply. I grabbed a copy of freebsd-update from an 11.1 > system that I have and copied it to /usr/sbin/freebsd-update. However, no > joy. After deleting the contents of /var/db/freebsd-update, I did the > following: > > ---BEGIN--- > # freebsd-update fetch install > src component not installed, skipped > Looking up update.FreeBSD.org mirrors... 3 mirrors found. > Fetching public key from update6.freebsd.org... done. > Fetching metadata signature for 9.1-RELEASE from update6.freebsd.org... > done. > Fetching metadata index... done. > Fetching 2 metadata files... done. > Inspecting system... done. > Preparing to download files... done. > > No updates needed to update system to 9.1-RELEASE-p24. > > WARNING: FreeBSD 9.1-RELEASE-p1 HAS PASSED ITS END-OF-LIFE DATE. > Any security issues discovered after Wed Dec 31 16:00:00 PST 2014 > will not have been corrected. > > # freebsd-update -r 9.3-RELEASE upgrade > src component not installed, skipped > Looking up update.FreeBSD.org mirrors... 3 mirrors found. > Fetching metadata signature for 9.1-RELEASE from update5.freebsd.org... > done. > Fetching metadata index... done. > Fetching 1 metadata files... done. > Inspecting system... done. > > The following components of FreeBSD seem to be installed: > > The following components of FreeBSD do not seem to be installed: > > Does this look reasonable (y/n)? y > > Fetching metadata signature for 9.3-RELEASE from update5.freebsd.org... > done. > Fetching metadata index... done. > Fetching 1 metadata patches. done. > Applying metadata patches... done. > Fetching 1 metadata files... done. > Inspecting system... done. > Preparing to download files... done. > > No updates needed to update system to 9.3-RELEASE-p53. > touch: f465c3739385890c221dff1a05e578c6cae0d0430e46996d319db7439f884336-install/kernelfirst: > No such file or directory > To install the downloaded upgrades, run "/usr/sbin/freebsd-update install". > > ---END--- > > I got similar results when attempting to go to 10.4-RELEASE as well. Any > other ideas? Or is my best bet at this point to just build the GENERIC > kernel from source? If so, can I go straight to 11.1 and recompile all my > ports? Or should I take some intermediate steps? > > > Thanks for your help, > > > Drew > > -- > Like card tricks? > > Visit The Alchemist's Warehouse to > learn card magic secrets for free! > > http://alchemistswarehouse.com > > > _______________________________________________ > > I do not know whether you considered or not , another way may be to use a NFS server to update your old computer : Connect to a NFS server ( another computer ) from old computer . Copy all of your required files in to a NFS directory ( additional copies may be much useful in case of failure in a single copy ) Install a new ( desired ) OS in to old computer . Connect the old computer to the NFS server . Copy your files to newly installed "old computer" . I think , for far away upgrade , the above steps are more feasible and safe . Thank you very much . Mehmet Erol Sanliturk From owner-freebsd-questions@freebsd.org Wed Apr 11 16:22:07 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C4C65FA0EFE for ; Wed, 11 Apr 2018 16:22:07 +0000 (UTC) (envelope-from matt.xtaz@gmail.com) Received: from mail-wr0-x22f.google.com (mail-wr0-x22f.google.com [IPv6:2a00:1450:400c:c0c::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 415587E9EA for ; Wed, 11 Apr 2018 16:22:07 +0000 (UTC) (envelope-from matt.xtaz@gmail.com) Received: by mail-wr0-x22f.google.com with SMTP id y55so2357493wry.3 for ; Wed, 11 Apr 2018 09:22:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=tQqimr9TDsZOLV1+jPUIiQXcjTwQJg8iKjfVLdsrQ+0=; b=cRPYrkuHqOIkmh+7YriYp4Gw/LUoFvBX/cchrELcdYmL+F1jqJQaoUGjx/DT+i9Ms1 XOadzEifya7veu0ERQoOjY3RDdkLHPSmIjQOeMNnojmz/GGUY68cwXvhXzWsuqiJY4e7 J/WtnzukimVIViIA6gG32Ws7GMu78h+XVsJiCQ5VrQDaIDO+awqgOUyA7tlLvM8RCRae lx3auX8E2A2NUivyMzwbIEX1KFokJWkmnHaQ8annj17i+K2goDpjVZNbuGhfzFGKjs3c 1KaEkSGrLiq+9zSkdIUUfMJXhqpaG/cFF2V+MZfASMxgN5nuawEe+mLBLI+yQM6BviiO msiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=tQqimr9TDsZOLV1+jPUIiQXcjTwQJg8iKjfVLdsrQ+0=; b=dy4lHVSTwpI66CCIiy0hczpDbAQu+w3hUXXIarezomd0aM5etxQtaWeOMURziI3Go9 I+tv6Ty8C9TeIMmZqkSVvWLdrTOJKrJ44qmiEkZzIiygpaa70M8MCCvnAyXAOgo6NQMF OCx4Nv4BXLpsCsWzGDMrov3/BJ4wHx8JcoxW5XAKKnQTJAVXhX14Yeas6JCuGEndLNGe 0zp9wSa01o4EHBd5fURB+f0D+BJF8SQnrmTihtvcRXlQMSXm6jrHELqUcvwZSgx6kzOB s4Mr7tWkCNSOIDds5g8yqs/mD03bppmFQrsmZK29HQMgv8Bq2SgDOEaarTdyqbg4ThT2 UtEg== X-Gm-Message-State: ALQs6tA0VWb+YFT+sOnjIZ2N42Jjird/EurmIx65QUFxQlLfHMO1VHgk 4hFxiqoE5xsf+xeC/0pWk9fj3bI/ X-Google-Smtp-Source: AIpwx4/ChYj8+Qzd/aOjWzVyAbzFBS62TAzYo+B+1v+rZfL6iSuBjFX+TVEMKL21MHSFG6uhI4qiEQ== X-Received: by 10.223.219.16 with SMTP id s16mr4206488wri.123.1523463725542; Wed, 11 Apr 2018 09:22:05 -0700 (PDT) Received: from gmail.com (tao.xtaz.uk. [2001:8b0:fe33::10]) by smtp.gmail.com with ESMTPSA id 19sm3148303wmn.40.2018.04.11.09.22.04 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 11 Apr 2018 09:22:05 -0700 (PDT) Date: Wed, 11 Apr 2018 17:22:02 +0100 From: Matt Smith To: User Hasse Cc: freebsd-questions@freebsd.org Subject: Re: dovecot error on boot up Message-ID: <20180411162202.GB76335@gmail.com> Mail-Followup-To: Matt Smith , User Hasse , freebsd-questions@freebsd.org References: <20180411133857.GA29340@ymer.bara1.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20180411133857.GA29340@ymer.bara1.se> User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 16:22:08 -0000 On Apr 11 15:38, User Hasse wrote: >Hello >After latest update/upgrade I get this for me strange error on the >boot up screen : > >dovecot error:t_readlink(var/run/dovecot//dovecot.conf) failed: readlink() failed: No such file or directory >Then : Starting dovecot > >Dovecot seems to work as usual and I can't find anything in any logfiles. > >Googled it, and found this : https://www.mail-archive.com/dovecot@dovecot.org/msg73108.html > >Anybody else experienced this ? Or know how to fix ? > >Best Regards >Geir Svalland Nobody ever reads /usr/ports/UPDATING do they? :) Though I did exactly this and started from a completely fresh configuration and I saw the error you've mentioned too. But I only saw it the very first time I started dovecot. It has never been seen on the second restart or since. 20180401: AFFECTS: users of mail/dovecot and mail/dovecot-pigeonhole AUTHOR: adamw@FreeBSD.org Dovecot has been upgraded to 2.3.1, and pigeonhole to 0.5.1. Most existing dovecot installations MUST be modified for 2.3, but for most users the modifications are simple. Modify your Dovecot conf.d/ files before spinning up 2.3.1. The upgrading instructions are detailed here: https://wiki2.dovecot.org/Upgrading/2.3 -- Matt From owner-freebsd-questions@freebsd.org Wed Apr 11 16:59:20 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 35B88FA31C0 for ; Wed, 11 Apr 2018 16:59:20 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from NAM04-CO1-obe.outbound.protection.outlook.com (mail-oln040092010081.outbound.protection.outlook.com [40.92.10.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT TLS CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8291F87437 for ; Wed, 11 Apr 2018 16:59:18 +0000 (UTC) (envelope-from carmel_ny@outlook.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=wOcaR2/GY3IgcDWafSwUFLzHIM4lPkSHBuJDpfzLJUQ=; b=kZF7tJllcyHspZTEgFzICzNl6j4mx8gnOmarNU7zskVXMG0MjxN9rGcFlPGGWBDzm7hFf/Y6PZ0/nQyLTvHiuc8wLy8jlovGEyqeej/BwX/F9Kp0k9ik+9Nti5nl9VHJL5aEZ2ObkrXld/WrQbqMDEKfhUb4SOyPQTwjfBBfT8TXf6dA7ZSKpwYle1NBvVQYzsYNrhstpOVKJlDs+P+4M1Eq3nAPx9hqRVUGs7tRHli9CB1BBQP46MmQ5DD8pUn1VYGvAskqFBGPiDhAqbBRRcJ98K3jJ+ZBB8nUhEcLpxcb6ZmIgxvAfaM4nciUFtNmwMvfZvRW0UL1FKHrGAX7qQ== Received: from BN3NAM04FT061.eop-NAM04.prod.protection.outlook.com (10.152.92.56) by BN3NAM04HT230.eop-NAM04.prod.protection.outlook.com (10.152.93.75) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.653.8; Wed, 11 Apr 2018 16:59:16 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com (10.152.92.56) by BN3NAM04FT061.mail.protection.outlook.com (10.152.92.233) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.653.8 via Frontend Transport; Wed, 11 Apr 2018 16:59:16 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com ([fe80::f020:88a4:c0b7:3c5b]) by BN6PR2001MB1730.namprd20.prod.outlook.com ([fe80::f020:88a4:c0b7:3c5b%5]) with mapi id 15.20.0675.009; Wed, 11 Apr 2018 16:59:16 +0000 From: Carmel NY To: FreeBSD Subject: Re: dovecot error on boot up Thread-Topic: dovecot error on boot up Thread-Index: AQHT0bZqH5qs/l+YxEyg+g+VEPo68g== Date: Wed, 11 Apr 2018 16:59:16 +0000 Message-ID: References: <20180411133857.GA29340@ymer.bara1.se> <20180411162202.GB76335@gmail.com> In-Reply-To: <20180411162202.GB76335@gmail.com> Reply-To: FreeBSD Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-incomingtopheadermarker: OriginalChecksum:908C03F1980BE41CCFB08AD66F72818F259FEB6550CD60B002354FD6D18D4F6F; UpperCasedChecksum:DD39CCEB7A0E9C11772694DF358F03019B885270C36973B529C88FDD1BA4BD08; SizeAsReceived:7053; Count:47 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [VUppW7x9UCAIocUomhivFNPi8EqOCS0t] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; BN3NAM04HT230; 7:yhkHCCaH+fcrmdyqRyEQ5EoxMn5au3vJIxRXuG27yc9AXr88//vbQHVq9PAHHx861Y/73CQGdEdu8XGM8stdjY5b2qw2EKmWMUsBDigmR02vcEn/mS3avbbvxTkVk6s0xCvemaiAFLJ/zpuAIr0GEutUwf94xqL2Kt0Ma+k2WFkHYNKLtakXNyIYKSAdPayByS1faoU7HPuPs8tE7kDLZAjXnfql1NlfE67poHc2gv2/pgAPGjO8hV6HjBqYaoSG x-incomingheadercount: 47 x-eopattributedmessage: 0 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1601125374)(1603101448)(1701031045); SRVR:BN3NAM04HT230; x-ms-traffictypediagnostic: BN3NAM04HT230: x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:BN3NAM04HT230; BCL:0; PCL:0; RULEID:; SRVR:BN3NAM04HT230; x-forefront-prvs: 0639027A9E x-forefront-antispam-report: SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:BN3NAM04HT230; H:BN6PR2001MB1730.namprd20.prod.outlook.com; FPR:; SPF:None; LANG:; x-microsoft-antispam-message-info: OS6u73N+T0fci84uQ1TOnmGH6r0tDneekFbqhMJDItB/FRBSKmAGqyyj35gTBasZoy+tN+3KqvjJhbIWDXFc4oUFd2WIIZDxYwQY0UXvjzw/9K1/tkk9eUOs2304iDSTjCxJN9a4cqRvWOjIwuAIiryDs9ir3GNy8AKvALD+e4D8IsGsnZmavssKN8JOZ9Bv Content-Type: text/plain; charset="us-ascii" Content-ID: <9BE02A8FA6D4F8479BD344ED905F2445@namprd20.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Office365-Filtering-Correlation-Id: ecb8d522-99cb-49e3-dc85-08d59fcd8f23 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 9a4e3081-9524-43cf-bfc3-dcaef82d5da1 X-MS-Exchange-CrossTenant-Network-Message-Id: ecb8d522-99cb-49e3-dc85-08d59fcd8f23 X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 9a4e3081-9524-43cf-bfc3-dcaef82d5da1 X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Apr 2018 16:59:16.8123 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3NAM04HT230 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 16:59:20 -0000 On Wed, 11 Apr 2018 17:22:02 +0100, Matt Smith stated: >On Apr 11 15:38, User Hasse wrote: >>Hello >>After latest update/upgrade I get this for me strange error on the >>boot up screen : >> >>dovecot error:t_readlink(var/run/dovecot//dovecot.conf) failed: readlink(= ) >>failed: No such file or directory Then : Starting dovecot >> >>Dovecot seems to work as usual and I can't find anything in any logfiles. >> >>Googled it, and found this : >>https://www.mail-archive.com/dovecot@dovecot.org/msg73108.html >> >>Anybody else experienced this ? Or know how to fix ? >> >>Best Regards >>Geir Svalland =20 > >Nobody ever reads /usr/ports/UPDATING do they? :) > >Though I did exactly this and started from a completely fresh configuratio= n >and I saw the error you've mentioned too. But I only saw it the very first >time I started dovecot. It has never been seen on the second restart or si= nce. > >20180401: > AFFECTS: users of mail/dovecot and mail/dovecot-pigeonhole > AUTHOR: adamw@FreeBSD.org > > Dovecot has been upgraded to 2.3.1, and pigeonhole to 0.5.1. Most > existing dovecot installations MUST be modified for 2.3, but for > most users the modifications are simple. > > Modify your Dovecot conf.d/ files before spinning up 2.3.1. The > upgrading instructions are detailed here: > > https://wiki2.dovecot.org/Upgrading/2.3 I have read it and made all of the changes before I started Dovecot the fir= st time. The only only happens if I reboot the system, not if I shutdown and t= hen restart Dovecot. I see nothing in the "updating" file that would account for this. --=20 Carmel From owner-freebsd-questions@freebsd.org Wed Apr 11 17:34:06 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 01B48F82077 for ; Wed, 11 Apr 2018 17:34:06 +0000 (UTC) (envelope-from matt.xtaz@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 686BF6D16E for ; Wed, 11 Apr 2018 17:34:05 +0000 (UTC) (envelope-from matt.xtaz@gmail.com) Received: by mail-wm0-x22b.google.com with SMTP id b21so5212750wme.4 for ; Wed, 11 Apr 2018 10:34:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=/BZzulfRo+wgUIZGsHBO8Q1uBqlHifiy04wFUbHb9+Q=; b=l/xJwni9tUBqwb7+yH/l2dvql9eVdDbCvG1TJ9FbPE06O72my/5VOILeB5/jFupRfr krEXTIOKZNe13aLQxj2+zQL1sQUcvjJbV5EZyWJRp/sw0I2xdUpfDKdqZMSETt3KnKOP FQsTVc6h+7GxRgPi/7whSGByX4KGsHfy/dFgkcAEoLZatydtsNOfAxz/QRRB9qOcZXCm b6LAL/hOGfJJf4SI7TjjOBceXRTiWXFymdcqfTECfvyu2Zr8GsXqRbOGOAQfSvRuDgiF KtPtJbzdVVNxrfT1ZQ7mX02Ddj0SiL6Wp5GwKVjW+mnWBnhP7ms+Vn8Wb9muOJQbf6aV qTVg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=/BZzulfRo+wgUIZGsHBO8Q1uBqlHifiy04wFUbHb9+Q=; b=OpIjF/0lsu5fGmHIOrd2xBOdagS9VmhaQWE09e3yB6N+uBDX4rTt2BczDDq5hPq0+4 EzHP2sZvtOxj6IXE2+/NdBLhj7LaK5iAjP1865+GIaATmGgT9Q+leNtgjbrEgSve2qGT 5bXbu6ZEHHaPJBwLsLLCsRZA6H7739BW4Yl7JnYtJabmVtdwcLWYC2vY2LDE0q7U/Gml M+vx1tYeWJqNYbbU3IVakfOeXhTmsiaGwZ/Kzo6eNzVDDQ8CMJgaQ85rRkc95EEcfUTe IxcMDZotu/HMrW//d9X5zV7s95fESBOfoRXLIVy/mZ0N5ZM+Z9iX1d4OyzDdIU16H5fI wCSw== X-Gm-Message-State: ALQs6tBtZqqUjNCr/CUi6V05Y2N+qjQ5pewtRFEoicG1ZCPtepUaomM+ vNnpcA2VRx4zW/gX4OS/SZLZSt0s X-Google-Smtp-Source: AIpwx4/FPRIFvmGtqb/y+6qCvhaKhxzMO3BkAUZdtiMuS+1U0yGas+8EF1orsr1mUpKuPULOfnmUTA== X-Received: by 10.28.54.220 with SMTP id y89mr3211184wmh.108.1523468044275; Wed, 11 Apr 2018 10:34:04 -0700 (PDT) Received: from gmail.com (tao.xtaz.uk. [2001:8b0:fe33::10]) by smtp.gmail.com with ESMTPSA id z11sm1663879wre.15.2018.04.11.10.34.03 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 11 Apr 2018 10:34:04 -0700 (PDT) Date: Wed, 11 Apr 2018 18:34:02 +0100 From: Matt Smith To: FreeBSD Subject: Re: dovecot error on boot up Message-ID: <20180411173402.GC76335@gmail.com> Mail-Followup-To: Matt Smith , FreeBSD References: <20180411133857.GA29340@ymer.bara1.se> <20180411162202.GB76335@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 17:34:06 -0000 On Apr 11 16:59, Carmel NY wrote: >On Wed, 11 Apr 2018 17:22:02 +0100, Matt Smith stated: > >>On Apr 11 15:38, User Hasse wrote: >>>Hello >>>After latest update/upgrade I get this for me strange error on the >>>boot up screen : >>> >>>dovecot error:t_readlink(var/run/dovecot//dovecot.conf) failed: readlink() >>>failed: No such file or directory Then : Starting dovecot >>> >>>Dovecot seems to work as usual and I can't find anything in any logfiles. >>> >>>Googled it, and found this : >>>https://www.mail-archive.com/dovecot@dovecot.org/msg73108.html >>> >>>Anybody else experienced this ? Or know how to fix ? >>> >>>Best Regards >>>Geir Svalland >> >>Nobody ever reads /usr/ports/UPDATING do they? :) >> >>Though I did exactly this and started from a completely fresh configuration >>and I saw the error you've mentioned too. But I only saw it the very first >>time I started dovecot. It has never been seen on the second restart or since. >> >>20180401: >> AFFECTS: users of mail/dovecot and mail/dovecot-pigeonhole >> AUTHOR: adamw@FreeBSD.org >> >> Dovecot has been upgraded to 2.3.1, and pigeonhole to 0.5.1. Most >> existing dovecot installations MUST be modified for 2.3, but for >> most users the modifications are simple. >> >> Modify your Dovecot conf.d/ files before spinning up 2.3.1. The >> upgrading instructions are detailed here: >> >> https://wiki2.dovecot.org/Upgrading/2.3 > >I have read it and made all of the changes before I started Dovecot the first >time. The only only happens if I reboot the system, not if I shutdown and then >restart Dovecot. > >I see nothing in the "updating" file that would account for this. > Yes, you're right, sorry. I assumed this wasn't a general issue as I only saw it on the first startup, and have never seen it since. It looks like this may come from the /usr/local/etc/rc.d/dovecot rc script. It looks like that does some kind of check that /var/run/dovecot exists and is populated. And it takes it from running dovecot -a and awking out base_dir etc. This is probably going wrong somewhere for the new version of Dovecot. May need to discuss it with the maintainer and/or raise a PR for it. -- Matt From owner-freebsd-questions@freebsd.org Wed Apr 11 17:39:22 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 40909F8278E for ; Wed, 11 Apr 2018 17:39:22 +0000 (UTC) (envelope-from hasse@bara1.se) Received: from mail92c50.megamailservers.eu (mail70c50.megamailservers.eu [91.136.10.80]) (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 B00636F440 for ; Wed, 11 Apr 2018 17:39:20 +0000 (UTC) (envelope-from hasse@bara1.se) X-POP-User: g.svalland@bredband.net Received: from ymer.bara1.se (ua-85-227-12-184.cust.bredbandsbolaget.se [85.227.12.184]) by mail92c50.megamailservers.eu (8.14.9/8.13.1) with ESMTP id w3BH5qss030351 for ; Wed, 11 Apr 2018 17:05:53 +0000 Received: by ymer.bara1.se (Postfix, from userid 1001) id 2D9913606F; Wed, 11 Apr 2018 19:05:52 +0200 (CEST) Date: Wed, 11 Apr 2018 19:05:52 +0200 From: User Hasse To: FreeBSD Subject: Re: dovecot error on boot up Message-ID: <20180411170551.GA2048@ymer.bara1.se> References: <20180411133857.GA29340@ymer.bara1.se> <20180411162202.GB76335@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="qMm9M+Fa2AknHoGS" Content-Disposition: inline In-Reply-To: X-PGP-Key: https://www.bara1.se/pubkey.asc User-Agent: Mutt/1.9.4 (2018-02-28) X-CTCH-RefID: str=0001.0A0B0206.5ACE4071.013E, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-CTCH-Score: 0.000 X-CTCH-Rules: X-CTCH-Flags: 0 X-CTCH-ScoreCust: 0.000 X-CSC: 0 X-CHA: v=2.2 cv=GqEywg9C c=1 sm=1 tr=0 a=Vi41peb4gFDKnZJxK0Rnyg==:117 a=Vi41peb4gFDKnZJxK0Rnyg==:17 a=Kd1tUaAdevIA:10 a=Vt2AcnKqAAAA:8 a=mjMI4m5sAAAA:8 a=6I5d2MoRAAAA:8 a=1qquuDwpVMzpYYqQOVAA:9 a=CjuIK1q_8ugA:10 a=39lUy_XcDJpa2cqXRUwA:9 a=ONNS8QRKHyMA:10 a=v10HlyRyNeVhbzM4Lqgd:22 a=8n7z28U-j86TceegZjyo:22 a=IjZwj45LgO3ly-622nXo:22 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 17:39:22 -0000 --qMm9M+Fa2AknHoGS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 11, 2018 at 04:59:16PM +0000, Carmel NY wrote: > On Wed, 11 Apr 2018 17:22:02 +0100, Matt Smith stated: >=20 > >On Apr 11 15:38, User Hasse wrote: > >>Hello > >>After latest update/upgrade I get this for me strange error on the > >>boot up screen : > >> > >>dovecot error:t_readlink(var/run/dovecot//dovecot.conf) failed: readlin= k() > >>failed: No such file or directory Then : Starting dovecot > >> > >>Dovecot seems to work as usual and I can't find anything in any logfile= s. > >> > >>Googled it, and found this : > >>https://www.mail-archive.com/dovecot@dovecot.org/msg73108.html > >> > >>Anybody else experienced this ? Or know how to fix ? > >> > >>Best Regards > >>Geir Svalland =20 > > > >Nobody ever reads /usr/ports/UPDATING do they? :) > > > >Though I did exactly this and started from a completely fresh configurat= ion > >and I saw the error you've mentioned too. But I only saw it the very fir= st > >time I started dovecot. It has never been seen on the second restart or = since. > > > >20180401: > > AFFECTS: users of mail/dovecot and mail/dovecot-pigeonhole > > AUTHOR: adamw@FreeBSD.org > > > > Dovecot has been upgraded to 2.3.1, and pigeonhole to 0.5.1. Most > > existing dovecot installations MUST be modified for 2.3, but for > > most users the modifications are simple. > > > > Modify your Dovecot conf.d/ files before spinning up 2.3.1. The > > upgrading instructions are detailed here: > > > > https://wiki2.dovecot.org/Upgrading/2.3 >=20 > I have read it and made all of the changes before I started Dovecot the f= irst > time. The only only happens if I reboot the system, not if I shutdown and= then > restart Dovecot. >=20 > I see nothing in the "updating" file that would account for this. >=20 > --=20 > Carmel > _______________________________________________ > 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" --------------------------------------- Same here. Found no clues in the wiki either --qMm9M+Fa2AknHoGS Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEZmmwl+ajAr4eHVHbDLsBtTa490kFAlrOQGhfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDY2 NjlCMDk3RTZBMzAyQkUxRTFENTFEQjBDQkIwMUI1MzZCOEY3NDkACgkQDLsBtTa4 90mlRwgAlMRXauwA4MPqUrsMA4gGgipeRikl+iZBwv0JWuTOLYclilrRzFL2mxCE VO8fFnlPfeTirrSpEg7CtEQdQBf83ylldGtacqhIv8TYFMmA/N/f2ZxkSV2s7uyy KuoS/A8EbSK4IgTA0aS/NZJWdvQHt0EuNhII+xWbCO4rA3tzpiKstJLdg/BjEcL/ HpOpxN/Ed4MwLLSEb+wKXU9BZzgs7wkDv1s01CYtWPKHsAvRQ3IuSJZpY19PrrjX RkTMuKBdEfCyG5xdyJfaVRNO3QMy2P8iktsy+YQtoUKesw2Q+vlqlZW5lsURLLlX B48nCfHVDeXoinj2EytjdyKkY1lg5w== =bdZA -----END PGP SIGNATURE----- --qMm9M+Fa2AknHoGS-- From owner-freebsd-questions@freebsd.org Wed Apr 11 20:00:56 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1D542F8D126 for ; Wed, 11 Apr 2018 20:00:56 +0000 (UTC) (envelope-from mack63richard@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 A76AE7250F for ; Wed, 11 Apr 2018 20:00:55 +0000 (UTC) (envelope-from mack63richard@gmail.com) Received: by mail-io0-x22c.google.com with SMTP id q80so3720579ioi.13 for ; Wed, 11 Apr 2018 13:00:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Pc/VMkfuQRVV1aawm2EQX00SJshBacbZJwcN7gjh4oA=; b=WReeCrzwpevlIRHD8rvummsCDR5HZDcXSbPc5VSQpxQYJyaY2mkTy0jN44kXOQHNZU tPEPTBzVSjaJBV9KlCbm9s/iuMdbsJM8ZStJfXLBKTVrk8SdsIKTuQsCW+NOILpbvbk2 mcqKRGPhY4TCw+tr7QG8ikquTbszkpo0O6ygZZySRmP6NNRW/b5A2BHuEeHlrpzOiTTc 4DMJxqTbKOCqZFXlKOWfczFem/hzCG3udRVrXxr5OjvXAuOQaU2XUpb5mEnZ+iHkBnR3 KzqPJajVvUeHXZOG8TpLQNaQ+b1k3Rir9Xxo1Xu/FMLknlfjle05JotQq0+70oJp83GE HtzA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Pc/VMkfuQRVV1aawm2EQX00SJshBacbZJwcN7gjh4oA=; b=Mm44SW70QNEIhn5yPZDlhKCVil8Px6uC3HkPY8bFMlQy4Mxdx2SXwg06VezBTb0/aV /pVWbGA/WXupGXAXLO4OMYPfoWhtBGsy7gFQgYSnZ8twVfSc3GrbTl4QNzSgSEqlLErb dDQj0+JDFKurk0sE0C/ZQP8Y6OwHs2bSGIF551gAiqxoD8NudMUB2P052+jNG3pCmKVU Ogdv61Z8z34m5Z7AKHGmkaUbchTBWlFwy8c2Anp0LeQHZbHnd+WtJkvKfCVe+nK4io6W vED1PcH92ZxA14u0GMrNSRCUX8H1e1XfC9lNbvLiSnLDayLCHFcA/0Nj0LWdedsnT2Ve RyVQ== X-Gm-Message-State: ALQs6tA9y5aLcudUxilRGaqGvRYfJN7U3nsckw1jbsok7Ti48WcOOZWK jtkOvrayYH99H6XELGg1csL7pAn4nwaqzvO0i9U= X-Google-Smtp-Source: AIpwx49rjGwZ0DJ9Mf4cc8z5K7+w9eyJNYYAHC1YZDtqCNOqnEU2uaj+KVa/TD0jHdJk/u0/AJRxmvUEqy2+8pQ0XuE= X-Received: by 10.107.146.67 with SMTP id u64mr5647835iod.144.1523476854547; Wed, 11 Apr 2018 13:00:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.16.134 with HTTP; Wed, 11 Apr 2018 13:00:53 -0700 (PDT) From: Richard P Mackerras Date: Wed, 11 Apr 2018 21:00:53 +0100 Message-ID: Subject: Samba on FreeBSD - no AD, just a home network To: Freebsd-Questions Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 20:00:56 -0000 Hi, I have been having trouble with SAMBA on FreeBSD. I have installed FreeBSD 11.1 and installed SAMBA. It is running, SAMBA says it is the master browser for my workgroup. This is a home network. No AD. All I want is for a few W7 and W10 computers and a Mac (iPad/iPhone as well?) to be able to read and write files to the SMB server. I cannot get it to authenticate a user. What is the process I should be following please? Which type of authentication should I use, there seem to be a couple of choices. I don't want to expose my files if anyone hacks my wifi but I don't want to make life difficult for myself. The windows computers are using the HomeGroup thing rather than a workgroup. The FreeBSD guide just seems to be rubbish and out of date. Most discussions seem to centre around AD. Is there anything I need to do to the Windows computers? Cheers, Richard From owner-freebsd-questions@freebsd.org Wed Apr 11 20:06:38 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E73B2F8D880 for ; Wed, 11 Apr 2018 20:06:37 +0000 (UTC) (envelope-from xxjack12xx@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 5B39772A96 for ; Wed, 11 Apr 2018 20:06:37 +0000 (UTC) (envelope-from xxjack12xx@gmail.com) Received: by mail-wm0-x22c.google.com with SMTP id i3so5866365wmf.3 for ; Wed, 11 Apr 2018 13:06:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=jj+e+cuR5tDRErmAAUispLWVnbzHz9js5ztisgsmYmo=; b=qOAramD73UR6wVyiCSxpvZ78S4Kyq7jYqPZ7dz3NRDNM+zAiNrIg5578kLGh38tBrc TRRJbqHSVNoaPGXIaf5hl4NwVVtg2whM5e0XFEHuSAtjkTb5zkuLw8GQ24+clS4uDUtJ xmT4yB2fvFLVE7DpNtH9ZzJ2gK9LXr/AmlCrGlW8znIaE9EfHlUk0mj6fIR58V3lSeXv hQyRRrn/hFIBrocTeKXV0hAn2/RnDooMUE7iE1LU+lJzVTauUos9N35zP7SkYkJzDSLL ELYfIatZFHES+aPslUYTkblpJ8qbQjtFyghnRpY8Qpo3ZmNCles81QrIiZDcHYGbRP7u Kfuw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=jj+e+cuR5tDRErmAAUispLWVnbzHz9js5ztisgsmYmo=; b=I690GinRH1TUtar1yLYVzMhw9UcwD/fha7bZaCp4EaYmullWUBKXv3ZFGwkuO4nq3V CI0VtpCEwigtv5kPCyWDDHK23uf7O/8/V6VI2Gk6PSLjawxukkFFPX+C7pC9qnMHhkwt uFsMccZSypkJX92iOhcWcQSV5vQh4NEOKqyeuRrJyEuEWz5xtdE56m+b8ky9MZ8ZiEec MBaUcKdrjq03XNOJ74cCNKNoVU5UdSybulrrEkHyLNJk8enXTpNskjvjVQ6KZIcD8/fg 5pWS7x0QBs5+zkBSX1xrXeE5rzht8QH2O9FWn/DjDTEDY37j9k9YT2r42cGtR3yoRupx cnzQ== X-Gm-Message-State: ALQs6tDt+N7fHL4jXBBc8tt2txRQ8zXcx5zDUNR7p1LlL7LVLmjVgP3+ wQef0bfZtLeV/Gyvm3DJmnZebRu2bGTYsqT/5vQ= X-Google-Smtp-Source: AIpwx4+A1R5XcT3GpU0ptdaclz07kSdT9xa9Glx/hA0HwA2dnHXL/7iJ+w0558t5yr6Ilz/9XeZSq++tfzh1rDDjwsk= X-Received: by 10.28.213.139 with SMTP id m133mr3352516wmg.144.1523477196182; Wed, 11 Apr 2018 13:06:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.147.130 with HTTP; Wed, 11 Apr 2018 13:05:55 -0700 (PDT) In-Reply-To: References: From: "Jack L." Date: Wed, 11 Apr 2018 13:05:55 -0700 Message-ID: Subject: Re: Samba on FreeBSD - no AD, just a home network To: Richard P Mackerras Cc: Freebsd-Questions Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 20:06:38 -0000 Which version of samba? Did you add a section in your samba/smb4.conf with the username and smbpasswd -a username? On Wed, Apr 11, 2018 at 1:00 PM, Richard P Mackerras wrote: > Hi, > > I have been having trouble with SAMBA on FreeBSD. > I have installed FreeBSD 11.1 and installed SAMBA. It is running, SAMBA > says it is the master browser for my workgroup. > > This is a home network. No AD. > All I want is for a few W7 and W10 computers and a Mac (iPad/iPhone as > well?) to be able to read and write files to the SMB server. > > I cannot get it to authenticate a user. > > What is the process I should be following please? > Which type of authentication should I use, there seem to be a couple of > choices. > I don't want to expose my files if anyone hacks my wifi but I don't want to > make life difficult for myself. > > The windows computers are using the HomeGroup thing rather than a workgroup. > > The FreeBSD guide just seems to be rubbish and out of date. Most > discussions seem to centre around AD. > > Is there anything I need to do to the Windows computers? > > Cheers, > > Richard > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" From owner-freebsd-questions@freebsd.org Wed Apr 11 21:49:47 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 82DC7F945DF for ; Wed, 11 Apr 2018 21:49:47 +0000 (UTC) (envelope-from andrei693@gmail.com) Received: from mail-pl0-x22d.google.com (mail-pl0-x22d.google.com [IPv6:2607:f8b0:400e:c01::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 0888C69A9B for ; Wed, 11 Apr 2018 21:49:47 +0000 (UTC) (envelope-from andrei693@gmail.com) Received: by mail-pl0-x22d.google.com with SMTP id c7-v6so2368288plr.5 for ; Wed, 11 Apr 2018 14:49:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=vQ0+CXwf1hzp7zhh3sCuqwCUslrZ/eh1Qy6pMg6zg3w=; b=XIMdrjN9JfebRH28cgkpIKUGek+ujaQtl3/hAmlzGUGPLuhoPW390Z2yi9umUU/6Xb EATeSpAuHzpJOKThRVeBcTZ2FwyVZb/zqgwAPJDTNrvtXw2XPIIwVeD61Onf7H/n8N+c xajQzwYP8aylFoAxVxcepyempk4zFrKgrg5NErXfNfIU4IRACvSaG+XgsifG8jSxGFwN H/5w5s8JyNEupz3woyPSUDcgmV74c8ciXajMP6Em5BwG6Ssc7gRFA2c/utjYC3l3YtNk p/ikmEwR+eoH87lLogdt8MHhRUtUCDIRFQMimT+MZYtcgjS8k3CjMUc52ttxCH/LFv/+ 3MZw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=vQ0+CXwf1hzp7zhh3sCuqwCUslrZ/eh1Qy6pMg6zg3w=; b=VnUrk2Gxrj8uX8jS0YjoMfegwPV1MrZq1OdaBpqc5i+SeM/57s492VgPpDZO3xlNYw TApPxKcYl3uAQMLu+CI0I8EFTFEeMDOl8PU8oGqhL1aTOpbDDdnZLYUSbkL7XICMijJv JuuIgzvvCpgYVeRtR6plnlf1ApXmweyF/XTLtNs9e4snfQ/jnsBvGtHI9JZTTbYWR3Hl VenSHHyP0/0Al0laiJmPlodBoVu4d5cJFydLVeYF6PM9v/Wm3XO/SUtGnAyaorfWNMzF ZqF9zs63lpFx0Ri5Fnj3/jDYUhXOG0+LP/ZdCCtjyDJrv6334wiFF2T5f7re9PbKBTDl kJ4A== X-Gm-Message-State: ALQs6tCRDpO4kmHVv7a7X4UW0MXpOvm5eKuzO728EItZSGVs5xxWDWt5 XfAzha60r+rXD+KB54NTEkKQ5uaF X-Google-Smtp-Source: AIpwx49xh6GGsCT4OD95m2fL+P3UlGZls+6g2pk3Du2nPLpIxOC826lY47mSN2bYjJZWMUvWLnwAhw== X-Received: by 2002:a17:902:bd03:: with SMTP id p3-v6mr7006825pls.236.1523483385921; Wed, 11 Apr 2018 14:49:45 -0700 (PDT) Received: from [10.0.11.188] ([84.80.170.191]) by smtp.googlemail.com with ESMTPSA id a10sm4108165pfo.131.2018.04.11.14.49.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Apr 2018 14:49:45 -0700 (PDT) Subject: Re: Samba on FreeBSD - no AD, just a home network To: freebsd-questions@freebsd.org References: From: Andrei Brezan Message-ID: <198cd0ae-d851-5514-803e-4b50bdcbfb92@gmail.com> Date: Wed, 11 Apr 2018 23:49:42 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 21:49:47 -0000 On 11/04/18 22:00, Richard P Mackerras wrote: > Hi, Hi, > > I have been having trouble with SAMBA on FreeBSD. > I have installed FreeBSD 11.1 and installed SAMBA. It is running, SAMBA > says it is the master browser for my workgroup. > > This is a home network. No AD. > All I want is for a few W7 and W10 computers and a Mac (iPad/iPhone as > well?) to be able to read and write files to the SMB server. > > I cannot get it to authenticate a user. > > What is the process I should be following please? > Which type of authentication should I use, there seem to be a couple of > choices. > I don't want to expose my files if anyone hacks my wifi but I don't want to > make life difficult for myself. > > The windows computers are using the HomeGroup thing rather than a workgroup. > > The FreeBSD guide just seems to be rubbish and out of date. Most > discussions seem to centre around AD. > https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-samba.html And you can use "smbpasswd -a username" or "pdbedit -a username" to add the users to tbdsam. "pdbedit -L" to list users. > Is there anything I need to do to the Windows computers? If your windows boxes are Home edition they might not want to use the workgroup you're creating with Samba, don't have any around to test, works fine with Win7 Pro clients and samba48. > > Cheers, > > Richard -- Andrei From owner-freebsd-questions@freebsd.org Thu Apr 12 03:09:43 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7B0BAF875D8 for ; Thu, 12 Apr 2018 03:09:43 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 0E1B770FA6 for ; Thu, 12 Apr 2018 03:09:42 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id E38203AEF8 for ; Wed, 11 Apr 2018 20:03:07 -0700 (PDT) From: "Ronald F. Guilmette" To: freebsd-questions@freebsd.org Subject: Two questions --- SSD block sizes and buffering Date: Wed, 11 Apr 2018 20:03:07 -0700 Message-ID: <23423.1523502187@segfault.tristatelogic.com> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2018 03:09:43 -0000 Two rather simple questions: 1) I don't know much, generally speaking, but I have certainly read that the underyling hardware of flash memory products (which I guess includes both USB sticks and also SSDs) all effectively have "physical" block sizes on the order of 128 KiB. So anyway, I'm just curious to know to what extent, if any, FreeBSD, when running with, on, or from any such (flash-memory based) mass storage device does things specifically with these larger physical block sizes (of flash memory) in mind. Does FreeBSD automagically sense that it is dealing with an SSD, and does it then adjust the way it operates on the relevant filesystem(s) accordingly, for maximal performance? Or must the system administrator tweek something explicitly (e.g. tunefs parameters, or perhaps newfs parameters) in order to get optimal performance on/with an SSD? 2) I have written some modest C programs that output lots and lots of very short little tidbits of data, one per line. In some cases these programs output millions of lines. For reasons that I can explain, these programs explicitly call setvbuf() on stdout during startup, and they set the buffering type for stdout to _IOLBF (i.e. line buffering). My question is just this: Assme that one of these programs is called "xyz". Now, if I run the program thusly: xyz > xyz.output i.e. so that stdout is redirected to a file, will there be one actual write to disk for each and every line that is written to stdout by xyz? In other words, will my act of explicitly setting line buffering (for stdout) in a case like this cause the xyz program to beat the living hell out of my disk drive? I hope not, but I'd like to know if it will, or know why it won't, if it won't. From owner-freebsd-questions@freebsd.org Thu Apr 12 07:38:01 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 15941F9D601 for ; Thu, 12 Apr 2018 07:38:01 +0000 (UTC) (envelope-from niels@kobschaetzki.net) Received: from hatchetman.psychedelicpirate.com (unknown [IPv6:2001:1560:a000:2:1313:d6dc:9261:d983]) (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 7989F6F363 for ; Thu, 12 Apr 2018 07:38:00 +0000 (UTC) (envelope-from niels@kobschaetzki.net) Received: from hatchetman.psychedelicpirate.com (localhost [127.0.0.1]) by hatchetman.psychedelicpirate.com (OpenSMTPD) with ESMTP id a308a93a for ; Thu, 12 Apr 2018 09:37:53 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=kobschaetzki.net; h=from :content-type:content-transfer-encoding:mime-version:date :subject:message-id:to; s=selector1; bh=VyVtgY8HYCuMsjAJwz9EOKun J2E=; b=jrG93rwohsrCBDdLIaXaMHinLwmqwOLk5GvBiHy2H9a29smHrFqHsXVo aux2Yeqtwq2tVSk1ICfpWOy6Cd9b3M5XDS7bxyHjzucctMYXHmH5l1w4V2qnzcBd ZibNiYk+KV08eIB/q0RqYiWM/QHlm5uW8NvbtnJt0HbgWPe/7es= DomainKey-Signature: a=rsa-sha1; c=nofws; d=kobschaetzki.net; h=from :content-type:content-transfer-encoding:mime-version:date :subject:message-id:to; q=dns; s=selector1; b=FLeBcurg+eD9LN/EKi 4B4YOxs8LsnfqMSLXOaigezzEeQa0vIBzI7TmRukmjqxZ/7rZuKAA4jgwZs2d6US t6QP5x9pQemhF3mIBzo4ynoyAG1w0PC5dVCj8lQ8yhYeleAjbDjKxj/Y1rcEDsmF N/ZjcLyn3gx+NME3THKn3NhP0= Received: from hatchetman.psychedelicpirate.com (localhost [127.0.0.1]) by hatchetman.psychedelicpirate.com (OpenSMTPD) with ESMTP id 5dec0c1f for ; Thu, 12 Apr 2018 09:37:48 +0200 (CEST) Received: from [10.198.77.16] (tmo-110-167.customers.d1-online.com [80.187.110.167]) by mail.kobschaetzki.net (OpenSMTPD) with ESMTPSA id 612dd0a0 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO) for ; Thu, 12 Apr 2018 09:37:48 +0200 (CEST) From: Niels Kobschaetzki Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Date: Thu, 12 Apr 2018 09:37:46 +0200 Subject: NFS cache misses after upgrading to 11.1 from 10.3 Message-Id: To: freebsd-questions@freebsd.org X-Mailer: iPhone Mail (15E216) X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2018 07:38:01 -0000 Hi, recently I upgraded a machine from 10.3-Prerelease to 11.1-release. Since th= en I see a huge difference in nfs cache misses, especially getattr-misses co= mpared to identical configured machines that are still on 10.3. When I do an= nfsstat -m the options are identical.=20 This leads too less performance and less happy end users. Is there any regre= ssion known? Any defaults that changed? Anything else I should know about th= at could lead to this behavior? I am grateful for any hint.=20 Niels= From owner-freebsd-questions@freebsd.org Thu Apr 12 09:30:17 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 07B8AF81AFA for ; Thu, 12 Apr 2018 09:30:17 +0000 (UTC) (envelope-from msprvs1=17640hMLadrdz=bounces-129987@spmailtechn.com) Received: from mta208.spmta.com (mta208.spmta.com [35.162.172.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.sparkpostmail.com", Issuer "RapidSSL SHA256 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 811F06BB58 for ; Thu, 12 Apr 2018 09:30:16 +0000 (UTC) (envelope-from msprvs1=17640hMLadrdz=bounces-129987@spmailtechn.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=spmailtechn.com; s=ssp0516; t=1523524206; i=@spmailtechn.com; bh=Fo256WalOmQY+Sy0FBIpP/5BfcPFu7/rx3czgUTxrFU=; h=Date:Subject:From:Reply-To:To:List-Unsubscribe:List-Id; b=iM02b8Jjkqg87kAh9f3Um0FAn3Hb8LX7X5aBKndGopEEDlgXBdzRq9WFQDxSK6LeQ FJuYE6JjMvdVY+D/13YTgs9fuvekrFE20Llhc8dUMBdUQQGs8hxCLCqL3IYwbfp2Zu JlAJsWMwhpqd2dZyYxRdEVBbMrj1G0avsg+CIvx4= X-MSFBL: htXIJp/eyPnfXDUEL/43h0dPN/b4usQ4X40yrR8nroE=|eyJzdWJhY2NvdW50X2l kIjoiMCIsInRlbmFudF9pZCI6InNwYyIsInIiOiJmcmVlYnNkLXF1ZXN0aW9uc0B mcmVlYnNkLm9yZyIsIm1lc3NhZ2VfaWQiOiIwMDAwNmQyMmNmNWE2NDVkMzdmMCI sImN1c3RvbWVyX2lkIjoiMTI5OTg3In0= Authentication-Results: b.mta1vsmtp.cc.prd.sparkpost smtp.user=; auth=pass (LOGIN) Received: from [112.196.166.36] ([112.196.166.36:17304] helo=KUNAL) by b.mta1vsmtp.cc.prd.sparkpost (envelope-from ) (ecelerity 4.2.39.63661 r(Core:4.2.39.17)) with ESMTPSA (cipher=ECDHE-RSA-AES128-SHA) id 73/0F-23908-D622FCA5; Thu, 12 Apr 2018 09:10:06 +0000 MIME-Version: 1.0 Date: Thu, 12 Apr 2018 14:39:59 +0530 Subject: Business Services for FreeBSD Inc From: "Abhishek Rathore" Reply-To: "Abhishek Rathore" X-FBL: 1_7_6_0_667265656273642D7175657374696F6E7340467265654253442E6F7267 Message-ID: To: There Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2018 09:30:17 -0000 Hi There,=0D=0A=0D=0AGreetings!=0D=0A=0D=0AHope you doing great. While rese= arching over internet I came across http://post.spmailtechn.com/f/a/Qq92YrX= gwE5qrkl6MTnG1g~~/AAH7wwA~/RgRcsFXtP0QWaHR0cDovL3d3dy5mcmVlYnNkLm9yZ1cDc3Bj= WAQAAAAAQgoAAG0iz1pkXTfwUh1mcmVlYnNkLXF1ZXN0aW9uc0BmcmVlYnNkLm9yZw~~ and=0D= =0Awas wondering if FreeBSD Inc is looking for support in software developm= ent=0D=0Aservices may be immediately or planning for near future; I=E2=80= =99d be happy to=0D=0Aassist you with the services. Here is a glimpse of wh= at we do -=0D=0Ahttp://post.spmailtechn.com/f/a/vlLnOD5-lZOcW9I2Qs5Bgw~~/AA= H7wwA~/RgRcsFXtP0QUaHR0cDovL3NvZnRwb3dlci5jby9XA3NwY1gEAAAAAEIKAABtIs9aZF03= 8FIdZnJlZWJzZC1xdWVzdGlvbnNAZnJlZWJzZC5vcmc~=0D=0A=0D=0ACore Services: Soft= ware Product Development, Custom Application (Web,Mobile &=0D=0AHybrid Apps= ) Development, and IT Staff Augmentation Services to - Start-ups,=0D=0AMicr= o, Small & Medium Enterprises.=0D=0A=0D=0AValue Added Services =E2=80=93 Da= ta Entry, Email List Building, SEO, & WordPress=0D=0Awebsites.=0D=0A=0D=0AV= alue Delivery: Our working methodology help companies save timeout of=0D=0A= recruitment process, deployright candidate, cost reduction up to 40-50% of = local=0D=0Aloaded cost, choosing best technology stack. In a nutshell, we h= elp reduction=0D=0Ainoverall development cost, faster team deployment&quali= ty delivery with=0D=0Aflexi-working models.=0D=0A=0D=0AHourly Rates: Our ho= urly rates for Core Services ranges from US$ 10 to US$ 18=0D=0Adepending up= on developer experience & technology.=0D=0A=0D=0AI=E2=80=99d be happy to ta= lk to you or FreeBSD Inc team member over a con-call to=0D=0Ashare more det= ails. In case, if you are not the right person to talk on the=0D=0Asubject = then please guide me to the right person & I=E2=80=99d be thankful to you.= =0D=0A=0D=0AThanks & Regards=0D=0AAbhishek S. Rathore |Co-Owner & CEO | Sof= tPower Biz=0D=0Aurl: www.SoftPower.co=0D=0A e: abhishek.r@softpower.co=0D=0AMobile: +91 8824 111 628 | Skype: abhish= eksrathore=0D=0A=0D=0AIf you do not wish to receive further email communica= tion, Kindly click =E2=80=98=0D=0ARemove=0D=0A =E2=80=99 to notify us with your email id. =0D=0A=0D=0A=0D=0A From owner-freebsd-questions@freebsd.org Thu Apr 12 11:29:59 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8F869F8C468 for ; Thu, 12 Apr 2018 11:29:59 +0000 (UTC) (envelope-from nancy.smith@weboptimizes.com) Received: from mail-oi0-x244.google.com (mail-oi0-x244.google.com [IPv6:2607:f8b0:4003: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 2102C6A0E1 for ; Thu, 12 Apr 2018 11:29:59 +0000 (UTC) (envelope-from nancy.smith@weboptimizes.com) Received: by mail-oi0-x244.google.com with SMTP id j143-v6so4771212oih.11 for ; Thu, 12 Apr 2018 04:29:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=weboptimizes.com; s=google; h=mime-version:sender:from:date:message-id:subject:to; bh=pibxttolR+AG7vzukDQDTKVnkdYGsMFmcPUgGWY8CUw=; b=DnALM36iF34KdI9wyk8IJP6r8Yv6jEMWcfBle3xZOyEWNfwyBgp0UcJ4t1SBuB6UXb c2w793Ty/JaE+G+BT5bR2TNOb3GITkRVukR9sS/66+W5h/kJQOWYWwhMyLlUg1zFVIJF DnuRXkbUWL1p5UblJt5pNQB8ZJn6/z1xFTL2A= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=pibxttolR+AG7vzukDQDTKVnkdYGsMFmcPUgGWY8CUw=; b=LYZccdvipCWd5t5nz9dsAft/mYy3WGAxVrpkO8EDnhJnMwRCXIr+fFIqv3qM/HIje3 On74ATmKBjC9Iv91/f7rq9qV7FnW8z5/pj4BC3XTwwyuvMYGCDGeExyimsupKGNZLXem YGfBQ7Q3dsMgu72LRMWgCm3SQoYxyvmAvtHWIyQq1FZn0uAVfMM/m7Nw/CR5zhZ/hzIt Pz+6YjqFG3+NYyGUePGaGs7uKQnKFlAUd8Mbc2D+mmCgnH7C7cRvr5t9twbxCCW2lzkO wjwQN72L2Zd3UBwwp22U3eaSFpY7hm76IQeWwG+/2xzDu3+aSny9/FdWmoO0jKwYRxwC PFxw== X-Gm-Message-State: ALQs6tCHw0cSK2HiBpEXC5EIWk+9pRWc+xAkfO95zt7ERnq9uGntHip8 GwXpUy3Bszm92i+NBX6b+G9Mi/wopga5cT0ZcSr3kA== X-Google-Smtp-Source: AIpwx48rjC4MkGTg3Xss5UVN4HO8vU1JLw4T8BOs66FP5LqrH18CyHVBVEoPHEz2ZnYc79L7/uVccL0KfsC0kNVm2GI= X-Received: by 2002:aca:5c05:: with SMTP id q5-v6mr5094767oib.77.1523532598212; Thu, 12 Apr 2018 04:29:58 -0700 (PDT) Received: from 52669349336 named unknown by gmailapi.google.com with HTTPREST; Thu, 12 Apr 2018 04:29:57 -0700 MIME-Version: 1.0 Sender: Nancy Smith From: Nancy Smith Date: Thu, 12 Apr 2018 04:29:57 -0700 X-Google-Sender-Auth: bAU-bCtOyF8Te_-ITXCP5kRioOE Message-ID: Subject: Serious issue found while visiting your website To: Freebsd-Questions Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2018 11:30:00 -0000 *Hi * *freebsd.org * *Team,* Hope this email finds you well. I am *Nancy Smith* I visited your website and found that your website has been diagnosed with many coding issues, which affects your ranking. Promote your website online and increase sales by putting your website top in all search engines. As per the trends in your industry =E2=80=93 over 80% of people search for= your products/services online and buy the same. These rankings also influence other channels of sales as well. It is simple maths=E2=80=94the more people who come to your website, the m= ore potential customers you attract. Don=E2=80=99t wait another moment to drive= more traffic, increase sales, and improve your visual appearance. 1. We have all the best expertise to take the risk and give you what we commit. 2. If you are willing to have more business online and more Return on Investment (ROI) we are just an Email /Phone away. 3. We can increase the number of visitors to your website, and get you on the top searches of all the search engines. 4. Affordable way to market website and get online business. I also prepared a* free website audit report* for your website. If you are *interested* i can show you the report. I'd be happy to send you our package, pricing and past work details, if you'd like to assess our work. I look forward to hearing from you. =E2=80=9CSuccess of our client is the success of our Company.=E2=80=9D *Best Regards,* *Nancy Smith* *SEO-Consultant* [image: beacon] From owner-freebsd-questions@freebsd.org Thu Apr 12 14:44:09 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5351DF9A9BB for ; Thu, 12 Apr 2018 14:44:08 +0000 (UTC) (envelope-from Veronica.Boone@smartsoftwares.info) Received: from mail.smartsoftwares.info (mail.smartsoftwares.info [35.173.26.160]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail", Issuer "mail" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F334C77F71 for ; Thu, 12 Apr 2018 14:44:07 +0000 (UTC) (envelope-from Veronica.Boone@smartsoftwares.info) Received: from mail (127.0.0.1) by mail.smartsoftwares.info (127.0.0.1) with Microsoft SMTP Server id 14.3.123.3; Thu, 12 Apr 2018 09:42:52 -0500 From: Veronica Boone To: X-Priority: 1 Priority: urgent Importance: high Date: Thu, 12 Apr 2018 09:42:52 -0500 Subject: Learning Management System(LMS) Software Pricing Guide for 2018 Message-ID: X-Originating-IP: [127.0.0.1] MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2018 14:44:09 -0000 From owner-freebsd-questions@freebsd.org Thu Apr 12 19:06:22 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB6C7F87CE7 for ; Thu, 12 Apr 2018 19:06:22 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C7709765BE for ; Thu, 12 Apr 2018 19:06:19 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.30.67]) by mrelayeu.kundenserver.de (mreue007 [212.227.15.167]) with ESMTPA (Nemesis) id 0MMLX7-1f7X273e6X-0083zu; Thu, 12 Apr 2018 21:06:11 +0200 Date: Thu, 12 Apr 2018 21:06:10 +0200 From: Polytropon To: "Ronald F. Guilmette" Cc: freebsd-questions@freebsd.org Subject: Re: Two questions --- SSD block sizes and buffering Message-Id: <20180412210610.bafc713b.freebsd@edvax.de> In-Reply-To: <23423.1523502187@segfault.tristatelogic.com> References: <23423.1523502187@segfault.tristatelogic.com> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:qBUFFIRRqq4iKgn7gxviWOjRgB5fllreGtjq80bhXLeh+eVmeXN RYTbNlgn1qjekG3PAHGU6Kqe0pXQF8h1KNglcN5qD3yQ1Z+v3pQclh4BK5r2WcnYE2rFkms fs0WsZsWZ+ejaKWUfxxHiZsUbCFjDxeHuDdp6PUY9/TEp1Cdcjupht9SQgJXKosTKGz5wdw /lQIWQMK+99b8vYzEqJsg== X-UI-Out-Filterresults: notjunk:1;V01:K0:zDNN9MDd3jI=:wLb00d0iLSZVCqn6hfl9aj ElxUq/xEusixz9i/oAVCC+gxbN+6Oo+jQgl49C/SQJfpMxamHc9OFhhRHWa4CU3oU/4zqOLK0 epBHo4y9DKKI61GOuKwePMnJpDCl8N/sNAO4pzCDxA4tjd6twWrbnE0iyhjbFU+4qI4p51IjQ s9Q4wiVSSUE6eXsPaCL6fHutYhyG5Qnb5GrYQp0j0atYZxk52Zbyr+qLnPRrze1BKOX5KnlSL 5vKmcdZpWbk7hdo4kktgNvF9btg+Wg7j6mUi12Ho9ZVALRw3ZG43Wef5AQ70nlkJ5t6IPmc0h x4Ub/UEsGm18CyZwUlgDUefklvyeAVx5MSpNeEXHK4qASgQHck5GvQDshPC16pAnd9UlmbPHX a40vuFxgfddb90pl39QqvQEhPT9Ji+8lZwH6fYRlo0z0je2ukOsdoEBgYU4PAy3ABrKvkSaor Wv1D+vG4tNS8pWuroJogF5h+NpKe3W7uuuOOvye+MLGChi08WPKo34hYWIBsZhoklliLyJLRX i4pWhM4JqK+GIQ7DtMreioGi+NFtzyjRhd1oTUo0959t1sgf0bNxMlHQfImXNI8L5Ls148UW6 2gK9nYjeKRwoDp5h/vjGiXqTLX5vUu8+CqamqCLIoUoX1jBHuP0truoUpVjEVFA99bALdI2+K UtrNo0nDs1/ga/LTb0VOxVyMR3fvWklEs/7XjyJ0kCrHHTHpMrT4nWKCYAl920zkdKAzr/ccO LdT4ppuMFKCkWcaBa9i72sHhC9I70egoJW8gberrZk9kWtqbK8EDQPcPR9w= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2018 19:06:22 -0000 On Wed, 11 Apr 2018 20:03:07 -0700, Ronald F. Guilmette wrote: > > Two rather simple questions: > > 1) I don't know much, generally speaking, but I have certainly read that > the underyling hardware of flash memory products (which I guess > includes both USB sticks and also SSDs) all effectively have > "physical" block sizes on the order of 128 KiB. > > So anyway, I'm just curious to know to what extent, if any, FreeBSD, > when running with, on, or from any such (flash-memory based) mass > storage device does things specifically with these larger physical > block sizes (of flash memory) in mind. No, it just works(TM). :-) > Does FreeBSD automagically sense that it is dealing with an SSD, and > does it then adjust the way it operates on the relevant filesystem(s) > accordingly, for maximal performance? Or must the system administrator > tweek something explicitly (e.g. tunefs parameters, or perhaps newfs > parameters) in order to get optimal performance on/with an SSD? The fragment size is to be applied by the system administrator when initializing the disk, depending on the block size of the device. For example, newfs allows you to do so: # newfs -m 0 -i 16384 -b 16384 -f 4069 -L somelabel \ -t enable -n enable -U /dev/ada0a Note the -f flag; from "man newfs": -f frag-size The fragment size of the file system in bytes. It must be a power of two ranging in value between blocksize/8 and blocksize. The default is 2048 bytes. But as mentioned in many cases: Deviating from the default values should be done for good and educated reasons, and depending on actual requirements. The example above uses a 4k frag size as typically used with newer hard disks. Additionally, slices, partitions and labels should be adjusted to match block size multiples for better performance. > 2) I have written some modest C programs that output lots and lots of > very short little tidbits of data, one per line. In some cases these > programs output millions of lines. > > For reasons that I can explain, these programs explicitly call setvbuf() > on stdout during startup, and they set the buffering type for stdout > to _IOLBF (i.e. line buffering). > > My question is just this: Assme that one of these programs is called > "xyz". Now, if I run the program thusly: > > xyz > xyz.output > > i.e. so that stdout is redirected to a file, will there be one actual > write to disk for each and every line that is written to stdout by xyz? > In other words, will my act of explicitly setting line buffering (for > stdout) in a case like this cause the xyz program to beat the living > hell out of my disk drive? Probably not. The actual write operationg are being issued somewhere "down the line" through the file system driver down to the disk driver. Even a "sync" command issued by the OS will not _immediately_ cause the drive to act. > I hope not, but I'd like to know if it will, or know why it won't, if > it won't. Isn't all output buffered, per default? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Fri Apr 13 04:56:23 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D248F8C156 for ; Fri, 13 Apr 2018 04:56:23 +0000 (UTC) (envelope-from srs0=es5m=hc=mail.sermon-archive.info=doug@sermon-archive.info) 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 BCAEB73148 for ; Fri, 13 Apr 2018 04:56:22 +0000 (UTC) (envelope-from srs0=es5m=hc=mail.sermon-archive.info=doug@sermon-archive.info) Received: by mailman.ysv.freebsd.org (Postfix) id 5AD87F8C154; Fri, 13 Apr 2018 04:56:22 +0000 (UTC) Delivered-To: questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 287E7F8C153 for ; Fri, 13 Apr 2018 04:56:22 +0000 (UTC) (envelope-from srs0=es5m=hc=mail.sermon-archive.info=doug@sermon-archive.info) Received: from mail.sermon-archive.info (sermon-archive.info [71.177.216.148]) by mx1.freebsd.org (Postfix) with ESMTP id 8685A73147 for ; Fri, 13 Apr 2018 04:56:21 +0000 (UTC) (envelope-from srs0=es5m=hc=mail.sermon-archive.info=doug@sermon-archive.info) Received: from [10.0.1.251] (mini [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 40Mlq25NpMz2fjWY; Thu, 12 Apr 2018 21:56:14 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: How To Update From 9.1? From: Doug Hardie In-Reply-To: Date: Thu, 12 Apr 2018 21:56:14 -0700 Cc: "questions@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <78A5D14F-3C96-4635-A6F8-2DA7D582039B@mail.sermon-archive.info> References: To: Drew Tomlinson X-Mailer: Apple Mail (2.3445.6.18) X-Virus-Scanned: clamav-milter 0.99.4 at mail X-Virus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Apr 2018 04:56:23 -0000 > On 11 April 2018, at 07:34, Drew Tomlinson = wrote: >=20 >=20 > On 4/10/2018 10:18 PM, Doug Hardie wrote: >>> On 10 April 2018, at 18:24, Drew Tomlinson = wrote: >>>=20 >>> I've got an old system I'm trying to get current. >>>=20 >>> # uname -a >>> FreeBSD vm.mykitchentable.net 9.1-RELEASE-p1 FreeBSD 9.1-RELEASE-p1 = #0: Tue May 9 09:19:33 PDT 2017 = drew@vm.mykitchentable.net:/usr/obj/usr/src/sys/GENERIC amd64 >>>=20 >>> So I consult the handbook and various list posts and find that I = should be able to use freebsd-update. Specifically I've done: >>>=20 >>> I've tried deleting /var/db/freebsd-update and doing the 'fetch = install' over. I've tried deleting /usr/src and downloading a new copy = of 9.3 source code. >>>=20 >>> Overall, I really don't know what I need to do as I've never done a = binary update before. I don't even know if 'src/src' looks reasonable = but I thought I'd give it a try. Can anyone point me in the right = direction? I'd appreciate the nudge. >> This is a common issue for 9 and earlier systems. I understand it = may also affect some 10s. Basically there are some patches available in = various postings to bug reports. If you find both of them, it should = work, but you have to manually update as line numbers are not = consistent. The easier approach is probably to get a copy of = freebsd-update from a newer system. It's a script so that works fine. = I have used the script from 11.0 to upgrade some 9.x systems. >>=20 >> -- Doug >=20 > Thank you for your reply. I grabbed a copy of freebsd-update from an = 11.1 system that I have and copied it to /usr/sbin/freebsd-update. = However, no joy. After deleting the contents of /var/db/freebsd-update, = I did the following: >=20 > ---BEGIN--- > # freebsd-update fetch install > src component not installed, skipped > Looking up update.FreeBSD.org mirrors... 3 mirrors found. > Fetching public key from update6.freebsd.org... done. > Fetching metadata signature for 9.1-RELEASE from = update6.freebsd.org... done. > Fetching metadata index... done. > Fetching 2 metadata files... done. > Inspecting system... done. > Preparing to download files... done. >=20 > No updates needed to update system to 9.1-RELEASE-p24. >=20 > WARNING: FreeBSD 9.1-RELEASE-p1 HAS PASSED ITS END-OF-LIFE DATE. > Any security issues discovered after Wed Dec 31 16:00:00 PST 2014 > will not have been corrected. >=20 > # freebsd-update -r 9.3-RELEASE upgrade > src component not installed, skipped > Looking up update.FreeBSD.org mirrors... 3 mirrors found. > Fetching metadata signature for 9.1-RELEASE from = update5.freebsd.org... done. > Fetching metadata index... done. > Fetching 1 metadata files... done. > Inspecting system... done. >=20 > The following components of FreeBSD seem to be installed: >=20 > The following components of FreeBSD do not seem to be installed: >=20 > Does this look reasonable (y/n)? y >=20 > Fetching metadata signature for 9.3-RELEASE from = update5.freebsd.org... done. > Fetching metadata index... done. > Fetching 1 metadata patches. done. > Applying metadata patches... done. > Fetching 1 metadata files... done. > Inspecting system... done. > Preparing to download files... done. >=20 > No updates needed to update system to 9.3-RELEASE-p53. > touch: = f465c3739385890c221dff1a05e578c6cae0d0430e46996d319db7439f884336-install/k= ernelfirst: No such file or directory > To install the downloaded upgrades, run "/usr/sbin/freebsd-update = install". >=20 > ---END--- >=20 > I got similar results when attempting to go to 10.4-RELEASE as well. = Any other ideas? Or is my best bet at this point to just build the = GENERIC kernel from source? If so, can I go straight to 11.1 and = recompile all my ports? Or should I take some intermediate steps? >=20 >=20 > Thanks for your help, >=20 >=20 > Drew I never tried to stay in 9. I went direct to 11. Going to 11.1 seems = to me to be the best approach at this point. =20 -- Doug From owner-freebsd-questions@freebsd.org Fri Apr 13 07:33:44 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 349A9F96520 for ; Fri, 13 Apr 2018 07:33:44 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from bede.qeng-ho.org (bede.qeng-ho.org [217.155.128.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 842166EB43 for ; Fri, 13 Apr 2018 07:33:43 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from arthur.home.qeng-ho.org (arthur.home.qeng-ho.org [172.23.1.2]) by bede.qeng-ho.org (Postfix) with ESMTP id 6BB1110377; Fri, 13 Apr 2018 08:27:14 +0100 (BST) Subject: Re: Two questions --- SSD block sizes and buffering To: Polytropon , "Ronald F. Guilmette" Cc: freebsd-questions@freebsd.org References: <23423.1523502187@segfault.tristatelogic.com> <20180412210610.bafc713b.freebsd@edvax.de> From: Arthur Chance Message-ID: <1cc45af6-bd4b-3854-4d37-8e9343786ce6@qeng-ho.org> Date: Fri, 13 Apr 2018 08:27:14 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180412210610.bafc713b.freebsd@edvax.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Apr 2018 07:33:44 -0000 On 12/04/2018 20:06, Polytropon wrote: > On Wed, 11 Apr 2018 20:03:07 -0700, Ronald F. Guilmette wrote: >> >> Two rather simple questions: >> >> 1) I don't know much, generally speaking, but I have certainly read that >> the underyling hardware of flash memory products (which I guess >> includes both USB sticks and also SSDs) all effectively have >> "physical" block sizes on the order of 128 KiB. >> >> So anyway, I'm just curious to know to what extent, if any, FreeBSD, >> when running with, on, or from any such (flash-memory based) mass >> storage device does things specifically with these larger physical >> block sizes (of flash memory) in mind. > > No, it just works(TM). :-) > > > >> Does FreeBSD automagically sense that it is dealing with an SSD, and >> does it then adjust the way it operates on the relevant filesystem(s) >> accordingly, for maximal performance? Or must the system administrator >> tweek something explicitly (e.g. tunefs parameters, or perhaps newfs >> parameters) in order to get optimal performance on/with an SSD? > > The fragment size is to be applied by the system administrator > when initializing the disk, depending on the block size of the > device. For example, newfs allows you to do so: > > # newfs -m 0 -i 16384 -b 16384 -f 4069 -L somelabel \ > -t enable -n enable -U /dev/ada0a > > Note the -f flag; from "man newfs": > > -f frag-size > The fragment size of the file system in bytes. It must be a > power of two ranging in value between blocksize/8 and blocksize. > The default is 2048 bytes. Which revision of FBSD are you running? I'm on 10 (must upgrade) and man newfs says -f frag-size The fragment size of the file system in bytes. It must be a power of two ranging in value between blocksize/8 and blocksize. The default is 4096 bytes. so it's been fixed for 4k disks. > But as mentioned in many cases: Deviating from the default > values should be done for good and educated reasons, and > depending on actual requirements. > > The example above uses a 4k frag size as typically used > with newer hard disks. Additionally, slices, partitions > and labels should be adjusted to match block size multiples > for better performance. It's worth noting that by default the first GPT partition (which is usually the boot partition) starts at block 34, which isn't a multiple of 4k. I always set it to start at block 40 to align with 4k disks and start the second partition at block 2048 so it's 1 MB aligned. > >> 2) I have written some modest C programs that output lots and lots of >> very short little tidbits of data, one per line. In some cases these >> programs output millions of lines. >> >> For reasons that I can explain, these programs explicitly call setvbuf() >> on stdout during startup, and they set the buffering type for stdout >> to _IOLBF (i.e. line buffering). >> >> My question is just this: Assme that one of these programs is called >> "xyz". Now, if I run the program thusly: >> >> xyz > xyz.output >> >> i.e. so that stdout is redirected to a file, will there be one actual >> write to disk for each and every line that is written to stdout by xyz? >> In other words, will my act of explicitly setting line buffering (for >> stdout) in a case like this cause the xyz program to beat the living >> hell out of my disk drive? > > Probably not. The actual write operationg are being issued > somewhere "down the line" through the file system driver > down to the disk driver. Even a "sync" command issued by > the OS will not _immediately_ cause the drive to act. write(2) calls, which underlie stdio, add the data to the disk block image in the VM cache. Unless your machine is under extreme memory pressure or you call fsync or sync the buffers eventually get written out by a kernel task. See man syncer for details. >> I hope not, but I'd like to know if it will, or know why it won't, if >> it won't. > > Isn't all output buffered, per default? There is a magic open flag that prevents it, but that's for those doing raw block io to devices. -- An amusing coincidence: log2(58) = 5.858 (to 0.0003% accuracy). From owner-freebsd-questions@freebsd.org Fri Apr 13 08:45:03 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C04FF9B0B8 for ; Fri, 13 Apr 2018 08:45:03 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 222927E424 for ; Fri, 13 Apr 2018 08:45:02 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 84AA33AEF2 for ; Fri, 13 Apr 2018 01:44:56 -0700 (PDT) From: "Ronald F. Guilmette" cc: freebsd-questions@freebsd.org Subject: Re: Two questions --- SSD block sizes and buffering In-Reply-To: <1cc45af6-bd4b-3854-4d37-8e9343786ce6@qeng-ho.org> Date: Fri, 13 Apr 2018 01:44:56 -0700 Message-ID: <36747.1523609096@segfault.tristatelogic.com> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Apr 2018 08:45:03 -0000 In message <1cc45af6-bd4b-3854-4d37-8e9343786ce6@qeng-ho.org>, Arthur Chance wrote: >... man newfs says > >-f frag-size > The fragment size of the file system in bytes. It must be a > power of two ranging in value between blocksize/8 and blocksize. > The default is 4096 bytes. > >so it's been fixed for 4k disks. Swell. But that may not really do much (in the way of improving performance) if the underlying mass storage device has a "native" block size of, say, 128 KiB. And as I noted, it is my understanding that essentially all flash-based mass storage devices -do- have a native block size of 128 KiB, or perhaps even larger. So.... When installing FreeBSD onto an SSD, would one be well advised to perform all newfs operations with an explicit "-f 131072" option? More to the point, has anyone run any benchmarks to see if that would either help or hurt anything? (There -are- a number of "cloud" providers these days who offer FreeBSD together with SSD mass storage, so it isn't as if my question is merely academic. Modern SSDs have certainly been tuned up in ways so that they can gracefully accomodate almost whatever is thrown at them, even while maintaining decent performance, but that's not to say that even a little better performance couldn't be eeked out of them, with a little help from an accomodating OS/filesystem.) (If the answer to that question is "no", I'd quite frankly be shocked. I've come to expect outstanding quality from FreeBSD generally, and that certainly includes all performance aspects.) >>> My question is just this: Assme that one of these programs is called >>> "xyz". Now, if I run the program thusly: >>> >>> xyz > xyz.output >>> >>> i.e. so that stdout is redirected to a file, will there be one actual >>> write to disk for each and every line that is written to stdout by xyz >? >>> In other words, will my act of explicitly setting line buffering (for >>> stdout) in a case like this cause the xyz program to beat the living >>> hell out of my disk drive? >> >> Probably not. The actual write operationg are being issued >> somewhere "down the line" through the file system driver >> down to the disk driver. Even a "sync" command issued by >> the OS will not _immediately_ cause the drive to act. > >write(2) calls, which underlie stdio, add the data to the disk block >image in the VM cache. Unless your machine is under extreme memory >pressure or you call fsync or sync the buffers eventually get written >out by a kernel task. See man syncer for details. Thank you. That certanly answers my question, and I am greatly relieved to know that I will probably not be materially shorting the life of my hardrive by doing the exact sort of silly thing I am doing. Regards, rfg P.S. There actually -is- a good reason for me to be explicitly setting stdio line buffering on my stdout stream in my program. You see, my program actually spaws a number of child processes and it is those children who are actually writing to stdout. I've found that unless line buffering (for stdout) is set for all of them, sometimes bits and pieces of lines from the different children can get mangled together in the output, creating one big uselessly mangled blob. From owner-freebsd-questions@freebsd.org Fri Apr 13 11:55:48 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CEA6EF81E35 for ; Fri, 13 Apr 2018 11:55:48 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from bede.qeng-ho.org (bede.qeng-ho.org [217.155.128.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 671716C990 for ; Fri, 13 Apr 2018 11:55:48 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from arthur.home.qeng-ho.org (arthur.home.qeng-ho.org [172.23.1.2]) by bede.qeng-ho.org (Postfix) with ESMTP id 7A9CA10377; Fri, 13 Apr 2018 12:55:46 +0100 (BST) Subject: Re: Two questions --- SSD block sizes and buffering To: "Ronald F. Guilmette" Cc: freebsd-questions@freebsd.org References: <36747.1523609096@segfault.tristatelogic.com> From: Arthur Chance Message-ID: <8227b0ec-cdce-db93-9ce1-19019038a036@qeng-ho.org> Date: Fri, 13 Apr 2018 12:55:46 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <36747.1523609096@segfault.tristatelogic.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Apr 2018 11:55:49 -0000 On 13/04/2018 09:44, Ronald F. Guilmette wrote: > > In message <1cc45af6-bd4b-3854-4d37-8e9343786ce6@qeng-ho.org>, > Arthur Chance wrote: > >> ... man newfs says >> >> -f frag-size >> The fragment size of the file system in bytes. It must be a >> power of two ranging in value between blocksize/8 and blocksize. >> The default is 4096 bytes. >> >> so it's been fixed for 4k disks. > > Swell. But that may not really do much (in the way of improving performance) > if the underlying mass storage device has a "native" block size of, say, > 128 KiB. And as I noted, it is my understanding that essentially all > flash-based mass storage devices -do- have a native block size of 128 KiB, > or perhaps even larger. I've not fully researched this subject so my understanding may not even reach quarter baked, never mind half baked, but I believe the larger "block size" has to do with bulk erasure of flash memory, and its exact size depends on the details of the flash memory chips used in the SSD, so could theoretically vary over time even within a manufacturer's model number. Writing to flash can be done efficiently in small(ish) chunks like 4 kiB for compatibility with spinning rust, and wear levelling is handled by the SSD controller - when you "rewrite" a block it may be written to a physically distinct block in which case the logical to physical block map is updated (like log structured file systems). When you "erase" a block via the TRIM operation the memory is left unchanged but is simply marked as free (which should be remembered if you have confidential information stored). Too many writes to flash risk "blurring" the stored bits because of the way flash works, so occasionally the SSD controller will garbage collect a larger block to free all sub-blocks and do a bulk erase which resets the memory to (almost) pristine state. As I said, the exact size of these erasable blocks varies, but Microsoft align their disk partitions on 1 MiB boundaries, which is presumably a power of two larger than any existing SSD needs. That's why I've taken to aligning my partitions to 1 MiB. Given typical disk sizes these days even 1 MiB is minuscule. > So.... When installing FreeBSD onto an SSD, would one be well advised > to perform all newfs operations with an explicit "-f 131072" option? It shouldn't be necessary, but if you want to try it remember you have to set both -b and -f, and the manual recommends the block size is 8 times the fragment size. Personally I use ZFS for everything these days except for one legacy machine with a UFS system disk, so my UFS knowledge is a little rusty. I'm not sure if there's a limit on block size. > More to the point, has anyone run any benchmarks to see if that would > either help or hurt anything? > > (There -are- a number of "cloud" providers these days who offer FreeBSD > together with SSD mass storage, so it isn't as if my question is merely > academic. Modern SSDs have certainly been tuned up in ways so that > they can gracefully accomodate almost whatever is thrown at them, even > while maintaining decent performance, but that's not to say that even > a little better performance couldn't be eeked out of them, with a little > help from an accomodating OS/filesystem.) > > (If the answer to that question is "no", I'd quite frankly be shocked. > I've come to expect outstanding quality from FreeBSD generally, and > that certainly includes all performance aspects.) > >>>> My question is just this: Assme that one of these programs is called >>>> "xyz". Now, if I run the program thusly: >>>> >>>> xyz > xyz.output >>>> >>>> i.e. so that stdout is redirected to a file, will there be one actual >>>> write to disk for each and every line that is written to stdout by xyz >> ? >>>> In other words, will my act of explicitly setting line buffering (for >>>> stdout) in a case like this cause the xyz program to beat the living >>>> hell out of my disk drive? >>> >>> Probably not. The actual write operationg are being issued >>> somewhere "down the line" through the file system driver >>> down to the disk driver. Even a "sync" command issued by >>> the OS will not _immediately_ cause the drive to act. >> >> write(2) calls, which underlie stdio, add the data to the disk block >> image in the VM cache. Unless your machine is under extreme memory >> pressure or you call fsync or sync the buffers eventually get written >> out by a kernel task. See man syncer for details. > > Thank you. That certanly answers my question, and I am greatly relieved > to know that I will probably not be materially shorting the life of my > hardrive by doing the exact sort of silly thing I am doing. > > > Regards, > rfg > > P.S. There actually -is- a good reason for me to be explicitly setting > stdio line buffering on my stdout stream in my program. You see, my > program actually spaws a number of child processes and it is those > children who are actually writing to stdout. I've found that unless > line buffering (for stdout) is set for all of them, sometimes bits and > pieces of lines from the different children can get mangled together > in the output, creating one big uselessly mangled blob. A well known, you might even say classic, problem. stdio and forks don't play terribly well together. I first got bitten by that back in 1979 under Unix V6 and IIRC line buffering wasn't an option then. -- An amusing coincidence: log2(58) = 5.858 (to 0.0003% accuracy). From owner-freebsd-questions@freebsd.org Fri Apr 13 13:22:23 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DA337F88921 for ; Fri, 13 Apr 2018 13:22:23 +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 8F53A7FBED for ; Fri, 13 Apr 2018 13:22:23 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from lowell-desk.lan (router.lan [172.30.250.2]) by be-well.ilk.org (Postfix) with ESMTP id 7282E33C0B; Fri, 13 Apr 2018 09:22:11 -0400 (EDT) Received: by lowell-desk.lan (Postfix, from userid 1147) id 09D4139822; Fri, 13 Apr 2018 09:22:10 -0400 (EDT) From: Lowell Gilbert To: "Ronald F. Guilmette" Cc: freebsd-questions@freebsd.org Subject: Re: Two questions --- SSD block sizes and buffering References: <36747.1523609096@segfault.tristatelogic.com> Date: Fri, 13 Apr 2018 09:22:10 -0400 In-Reply-To: <36747.1523609096@segfault.tristatelogic.com> (Ronald F. Guilmette's message of "Fri, 13 Apr 2018 01:44:56 -0700") Message-ID: <4436zzw8al.fsf@lowell-desk.lan> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Apr 2018 13:22:24 -0000 "Ronald F. Guilmette" writes: > In message <1cc45af6-bd4b-3854-4d37-8e9343786ce6@qeng-ho.org>, > Arthur Chance wrote: > >>... man newfs says >> >>-f frag-size >> The fragment size of the file system in bytes. It must be a >> power of two ranging in value between blocksize/8 and blocksize. >> The default is 4096 bytes. >> >>so it's been fixed for 4k disks. > > Swell. But that may not really do much (in the way of improving performance) > if the underlying mass storage device has a "native" block size of, say, > 128 KiB. And as I noted, it is my understanding that essentially all > flash-based mass storage devices -do- have a native block size of 128 KiB, > or perhaps even larger. That's not really relevant to performance the way it is with a spinning-platter disk, because proximate writes (or, for that matter, reads) aren't particularly more efficient than random ones. The block size really only comes to play when the native block gets re-written, which is handled internally by the device controller -- and we really don't have much insight into the algorithms it uses. > So.... When installing FreeBSD onto an SSD, would one be well advised > to perform all newfs operations with an explicit "-f 131072" option? Probably not, unless the vast majority of your files are multiple megabytes in size. And the difference still won't be in read or write speed. From owner-freebsd-questions@freebsd.org Fri Apr 13 23:06:49 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0FEB3F8A167 for ; Fri, 13 Apr 2018 23:06:49 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7884380E55 for ; Fri, 13 Apr 2018 23:06:48 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.30.67]) by mrelayeu.kundenserver.de (mreue001 [212.227.15.167]) with ESMTPA (Nemesis) id 0MGsGP-1fBCEW3O7t-00DX6b; Sat, 14 Apr 2018 01:06:37 +0200 Date: Sat, 14 Apr 2018 01:06:36 +0200 From: Polytropon To: Arthur Chance Cc: "Ronald F. Guilmette" , freebsd-questions@freebsd.org Subject: Re: Two questions --- SSD block sizes and buffering Message-Id: <20180414010636.18b4e568.freebsd@edvax.de> In-Reply-To: <1cc45af6-bd4b-3854-4d37-8e9343786ce6@qeng-ho.org> References: <23423.1523502187@segfault.tristatelogic.com> <20180412210610.bafc713b.freebsd@edvax.de> <1cc45af6-bd4b-3854-4d37-8e9343786ce6@qeng-ho.org> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:7FOolnKzxKTrOPYZx8QURtNxYBVxxPNjzQIgASJX8yafwYbdXyb cdpvOQs8tU9jnjmM4VYkjv6XTeG1D1hUOEniRnJq1hwwrTUrxW5jU/rP0YLdZXNwty+esBJ tnU0J3XsRCrT2OkwhuYZZ3ZdlGL0umitq3kYEU91pztPuno0NMYuZsnRGYyPjwezS2WQ4z4 aYxfeJ8OwxejoYElrd/lA== X-UI-Out-Filterresults: notjunk:1;V01:K0:VKyD59/bzEA=:R5t/3YjPpu9mvIljvKXFr5 C0loBIxPOmy+FluKMeQ+mw/XKnktwEiJgQrepIy1Pq+Rn4HZTJc/lHg7aMNZoOza8ybHovp8f gOlrD2MAKiXZkBnh6I8Pd10fJVy+/7UOh4fplld5bkMpsT1s2Wjw8YwAZPaaTTYJ2wjaGzdEn hQ+R0sc8Hz01ZdrnsYqgCw+MerqcC6A1xOZIe2NKzvvYXRjMhu4GK7b5vZT3N1pXZtN/GkHbn llKul3SCAelvR4WX5w59t6ICHUOFfEa6erkOHkNA1iBzK63lyelMBu53LoCfDJmEFIUgwsqX3 j5GnX0tJrvLs/cLdL/ceE5GFgmA4rmtKy0EqKmEGgcjdU9qmMIRanvg/iMkcimbQu4K83pzpc oOh7OZuaY73u8l70IhgTKtHzPpjK9vGxKE/RwkqkWt5ZXDacIb0cy+NJrUTa8LZJGOb5Zro4i njVWeEgz5Gm6hmdi08AdjOSqX30V6a4Cr2ZSHWlfo1jpDB37xLImsbDc28yZvRazo+08cGfah 3O9CaC/bj5PXmlS3MmUn6lGN7/Hy2ClU+/TEWQgJ41vzgJlyK1w6nyTLmGVfpW3Sc2g9+EkUr UpHcrkmxy1URwyUhVPO5+aeVksyuga4uNWyI72AqOG5J4UYwX7x9/wV8gySceRfuNlIllGUFo mPz0E0SeWUNT7N00mGm6yIGObKhynS9FYTk6loNIVF5MFEdc+I2G4XTfp7RNtNb/GcYhG6DPd qoW3qd5ORgL26PAeCfYKn4eF74orKhSBnAz+zXMI0VopCPtspGlpl1qkvnA= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Apr 2018 23:06:49 -0000 On Fri, 13 Apr 2018 08:27:14 +0100, Arthur Chance wrote: > On 12/04/2018 20:06, Polytropon wrote: > > On Wed, 11 Apr 2018 20:03:07 -0700, Ronald F. Guilmette wrote: > >> > >> Two rather simple questions: > >> > >> 1) I don't know much, generally speaking, but I have certainly read that > >> the underyling hardware of flash memory products (which I guess > >> includes both USB sticks and also SSDs) all effectively have > >> "physical" block sizes on the order of 128 KiB. > >> > >> So anyway, I'm just curious to know to what extent, if any, FreeBSD, > >> when running with, on, or from any such (flash-memory based) mass > >> storage device does things specifically with these larger physical > >> block sizes (of flash memory) in mind. > > > > No, it just works(TM). :-) > > > > > > > >> Does FreeBSD automagically sense that it is dealing with an SSD, and > >> does it then adjust the way it operates on the relevant filesystem(s) > >> accordingly, for maximal performance? Or must the system administrator > >> tweek something explicitly (e.g. tunefs parameters, or perhaps newfs > >> parameters) in order to get optimal performance on/with an SSD? > > > > The fragment size is to be applied by the system administrator > > when initializing the disk, depending on the block size of the > > device. For example, newfs allows you to do so: > > > > # newfs -m 0 -i 16384 -b 16384 -f 4069 -L somelabel \ > > -t enable -n enable -U /dev/ada0a > > > > Note the -f flag; from "man newfs": > > > > -f frag-size > > The fragment size of the file system in bytes. It must be a > > power of two ranging in value between blocksize/8 and blocksize. > > The default is 2048 bytes. > > Which revision of FBSD are you running? I'm on 10 (must upgrade) and man > newfs says > > -f frag-size > The fragment size of the file system in bytes. It must be a > power of two ranging in value between blocksize/8 and blocksize. > The default is 4096 bytes. > > so it's been fixed for 4k disks. Yes, this has been taken from a 8.x system I was just logged in to. You know, one of those systems that run and run and run and run and run and run... obeying the "never touch a running system" rule. :-) You are correct, 4k became the default frag size, so adjusting it manually is only needed for specific cases now. > > But as mentioned in many cases: Deviating from the default > > values should be done for good and educated reasons, and > > depending on actual requirements. > > > > The example above uses a 4k frag size as typically used > > with newer hard disks. Additionally, slices, partitions > > and labels should be adjusted to match block size multiples > > for better performance. > > It's worth noting that by default the first GPT partition (which is > usually the boot partition) starts at block 34, which isn't a multiple > of 4k. I always set it to start at block 40 to align with 4k disks and > start the second partition at block 2048 so it's 1 MB aligned. Fully agree. Using 1M as factor makes it easy to align the partitions. > >> 2) I have written some modest C programs that output lots and lots of > >> very short little tidbits of data, one per line. In some cases these > >> programs output millions of lines. > >> > >> For reasons that I can explain, these programs explicitly call setvbuf() > >> on stdout during startup, and they set the buffering type for stdout > >> to _IOLBF (i.e. line buffering). > >> > >> My question is just this: Assme that one of these programs is called > >> "xyz". Now, if I run the program thusly: > >> > >> xyz > xyz.output > >> > >> i.e. so that stdout is redirected to a file, will there be one actual > >> write to disk for each and every line that is written to stdout by xyz? > >> In other words, will my act of explicitly setting line buffering (for > >> stdout) in a case like this cause the xyz program to beat the living > >> hell out of my disk drive? > > > > Probably not. The actual write operationg are being issued > > somewhere "down the line" through the file system driver > > down to the disk driver. Even a "sync" command issued by > > the OS will not _immediately_ cause the drive to act. > > write(2) calls, which underlie stdio, add the data to the disk block > image in the VM cache. Unless your machine is under extreme memory > pressure or you call fsync or sync the buffers eventually get written > out by a kernel task. See man syncer for details. > > >> I hope not, but I'd like to know if it will, or know why it won't, if > >> it won't. > > > > Isn't all output buffered, per default? > > There is a magic open flag that prevents it, but that's for those doing > raw block io to devices. Interesting pointer, thanks! I think I found it in "man 2 open". :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Sat Apr 14 14:47:21 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CB4A6FA5433 for ; Sat, 14 Apr 2018 14:47:21 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::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 60FCD6E5BB for ; Sat, 14 Apr 2018 14:47:21 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-it0-x229.google.com with SMTP id u62-v6so6534613ita.5 for ; Sat, 14 Apr 2018 07:47:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=zsgbge3Cl21APChzbzi2pD8fpWOIIGiDO7yIyWDxJNw=; b=ZgfbA7CwYpIhapk354TmCrV+env597UpnGJtdObIQmt12sbQodnw0G7A4Qr52sO5p4 kORvyds42vM2GZQBOxxRi6MZpYYgheT0Bwg+yowe/lxnNcorAzp30m1ggt67y7TAgOnb KaFKXvY7C/I3Qs6Xcu0dRmRmZKO1jw/4Lr2G8ahCw7OYrzLK2pf5BEDTrhYl8SxKAwPr wvfkqDxplnIcKQv4EcxWoXbkh4USKAkqjzD5C4xGdBx2CrVHE394DUJbAx3IfXuK6kbz ft+okM/7YTSjeEwFr+Xl5czrfuj4Jhj65RbZTCUWmysFu/OWAxA/MlovPaMFT2GXr3uz DXaw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=zsgbge3Cl21APChzbzi2pD8fpWOIIGiDO7yIyWDxJNw=; b=IZowaZk3rXCwN2hdztqckJbwaKt0U9QHXJgdjEkV3Ob3aKvTKv1fNiqnq5CI/tLBJw KM55bAKFPjGu7eH45gKluO7LSDTY9SRn5RJwRA49jpdh2mUf+2ar7xHlBF3kaLNf0nyP meEej4HfAW5t752B+P04QYY9KEw/uQ5cP1S1pDwpXNTUB6VwWBKTmy3qRfttcF41C/xQ iG/3OpHDITNzG7+U56wOepwqBAc9LoCEsUQMEmPTDsJwIB4oJKuk37dy8UhvhdIJX8FO rkx2g0sZXTQt/wQHwZqy8+O7vp8ZeBZK/Cn3tFDqT2tcY+363HCy9v9DxJgtKEmbiPK1 B+xg== X-Gm-Message-State: ALQs6tArK+/ZMJqM4PwXQaMyPXZ/MIEs+WfmW7ohpscx15GNDaC1a9FT ZDi2fON1mBcHoykxdat3NICNvQ== X-Google-Smtp-Source: AIpwx4+pqn2ZkXxzCCvuc8YOcmH21mvyOKaYdMzUt+KVs7ZWsiyA5lGKcmO9VA1d5aLZDSY9O5+4sQ== X-Received: by 2002:a24:4153:: with SMTP id x80-v6mr9351708ita.14.1523717240760; Sat, 14 Apr 2018 07:47:20 -0700 (PDT) Received: from [10.0.10.7] (cpe-65-25-48-31.neo.res.rr.com. [65.25.48.31]) by smtp.googlemail.com with ESMTPSA id a79-v6sm2346457itc.11.2018.04.14.07.47.19 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 14 Apr 2018 07:47:19 -0700 (PDT) Message-ID: <5AD21478.4030102@gmail.com> Date: Sat, 14 Apr 2018 10:47:20 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Polytropon CC: "freebsd-questions@freebsd.org" Subject: Re: Recover directory tree with files from win10 HD References: <5ACD536C.5010407@gmail.com> <20180411113740.2b245110.freebsd@edvax.de> In-Reply-To: <20180411113740.2b245110.freebsd@edvax.de> 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.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Apr 2018 14:47:22 -0000 Well I chose to try ddrescue. It's my understanding it will clone the complete source HD to the target HD. That means the mbr & partition table, and all the data space of the source HD to the target HD. The following is what I did. ada1 is 3tb bad drive from win10 ntfs with 600gb data on it ada2 is 3tb newly purchased empty drive thats never been used. Installed these 2 HD to the PC's motherboard with their sata cables and booted the system. /root >ls /dev | grep ada ada0 ada0s1 ada0s1a ada0s1b ada1 ada2 pkg install fusefs-ntfs pkg install ddrecuse ddrescue -nf /dev/ada1 /dev/ada2 /root/mapfile ipos: 646353 MB, non-trimmed: 0 B, current rate: 15872 B/s0 00 0 opos: 646353 MB, non-scraped: 11143 kB, average rate: 84485 kB/s non-tried: 0 B, bad-sector: 57856 B, error rate: 0 B/s rescued: 3000 GB, bad areas: 113, run time: 9h 51m 55s pct rescued: 99.99%, read errors: 363, remaining time: Finished /root >mount -t ntfs-3g /dev/ada2 /mnt mount: /dev/ada2: Operation not supported by device /root >ntfsinfo -m -v /dev/ada2 NTFS signature is missing. Failed to mount '/dev/ada2': Invalid argument The device '/dev/ada2' doesn't have a valid NTFS. Maybe you selected the wrong device? Or the whole disk instead of a partition (e.g. /dev/hda, not /dev/hda1)? Or the other way around? Failed to open '/dev/ada2'. /root >ntfsfix /dev/ada2 Mounting volume... NTFS signature is missing. FAILED Attempting to correct errors... NTFS signature is missing. FAILED Failed to startup volume: Invalid argument NTFS signature is missing. Trying the alternate boot sector Error reading alternate bootsector: Invalid argument Unrecoverable error Volume is corrupt. You should run chkdsk. /root >fdisk /dev/ada2 ******* Working on device /dev/ada2 ******* parameters extracted from in-core disklabel are: cylinders=5814021 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=5814021 heads=16 sectors/track=63 (1008 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 4294966977 (2097151 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 15/ head 15/ sector 63 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: ****************************************************************** To me this looks like my mother's pc caught a virus that changed the contents of the HD mbr and partition table to make the HD unusable. The damaged 2tb HD was formated using a XP laptop that was before gpart and usb3. I know it's a ntfs filesystem with mbr. Are there any tools that I can use to repair these problems without loosing the user data? Change the sysid to windows ntfs and fix the mbr. From owner-freebsd-questions@freebsd.org Sat Apr 14 16:10:39 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3191FF8599F for ; Sat, 14 Apr 2018 16:10:39 +0000 (UTC) (envelope-from a199e59c87e914e7b5fdb9459865d66e@zxas.fi) Received: from box.zxas.fi (box.zxas.fi [185.87.108.237]) (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 AA0047F6E0 for ; Sat, 14 Apr 2018 16:10:38 +0000 (UTC) (envelope-from a199e59c87e914e7b5fdb9459865d66e@zxas.fi) Received: from authenticated-user (box.zxas.fi [185.87.108.237]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by box.zxas.fi (Postfix) with ESMTPSA id 73FA31E356 for ; Sat, 14 Apr 2018 19:03:20 +0300 (EEST) Received: from authenticated-user (box.zxas.fi [185.87.108.237]) by zero.my.domain (Postfix) with ESMTP id D30A033C39 for ; Sat, 14 Apr 2018 19:03:17 +0300 (EEST) Received: from authenticated-user (box.zxas.fi [185.87.108.237]) by thunderbolt.my.domain (8.15.2/8.15.2) with ESMTPS id w3EG3G6x053079 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 14 Apr 2018 19:03:16 +0300 (EEST) (envelope-from ejk@thunderbolt.my.domain) Received: from authenticated-user (box.zxas.fi [185.87.108.237]) by thunderbolt.my.domain (8.15.2/8.15.2/Submit) id w3EG3FdS053078 for freebsd-questions@freebsd.org; Sat, 14 Apr 2018 19:03:15 +0300 (EEST) (envelope-from ejk) Date: Sat, 14 Apr 2018 19:03:15 +0300 From: Esa Karkkainen To: freebsd-questions@freebsd.org Subject: Re: Recover directory tree with files from win10 HD Message-ID: <20180414160315.GB12481@pp.htv.fi> Mail-Followup-To: Esa Karkkainen , freebsd-questions@freebsd.org References: <5ACD536C.5010407@gmail.com> <20180411113740.2b245110.freebsd@edvax.de> <5AD21478.4030102@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5AD21478.4030102@gmail.com> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Apr 2018 16:10:39 -0000 On Sat, Apr 14, 2018 at 10:47:20AM -0400, Ernie Luzar wrote: > Are there any tools that I can use to repair these problems without > loosing the user data? IIRC I've used sysutils/testdisk, contents of pkg-descr file copied below, and I was able to scan a hard disk so I could recreate the partiton table. ---8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8<--- Tool to check and undelete partition Works with the following partitions: - FAT12 FAT16 FAT32 - Linux EXT2/EXT3 - Linux SWAP (version 1 and 2) - NTFS (Windows NT/W2K/XP) - BeFS (BeOS) - UFS (BSD) - Netware - ReiserFS TestDisk is under GNU Public License. You can compile it under Dos with DJGPP or under Linux or BSD with gcc. WWW: http://www.cgsecurity.org/ ---8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8<--- Going though other "sysutils" ports, the sysutils/safecopy might be another option, pkg-descr file content is copied below. ---8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8<--- Safecopy is a data recovery tool which tries to extract as much data as possible from a problematic (i.e. damaged sectors) source - like floppy drives, hard disk partitions, CDs, tape devices etc, ... , where other tools like dd would fail due to I/O errors. Safecopy includes a low level IO layer to read CDROM disks in raw mode, and issue device resets and other helpful low level operations on a number of other device classes. The project also includes a device simulator which can be used to simulate bad media for testing and benchmarking safecopy as well as other data rescue tools. WWW: http://safecopy.sourceforge.net/ ---8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8<--- Few commands I used to find what sysutils ports might be useful: % cd /usr/ports/sysutils % grep -li disk */pkg-descr|xargs grep -li partition % grep -li data */pkg-descr|xargs grep -li recovery The "grep -li disk */pkg-descr" will list all pkg-descr files that have "disk" in the files, search is case insensive, for example files containing either disk or dIsk are the listed. The part after the pipe character does the same exept its looking for partition, so in the end you'll get list of sysutils ports that have pkg-descr files that have disk and partition inside. This cuts down list of possibly useful ports from 1362 to just 22 :) 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