From owner-freebsd-doc@FreeBSD.ORG Thu Jul 17 21:13:20 2014 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A2B45BD; Thu, 17 Jul 2014 21:13:20 +0000 (UTC) Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 99564223F; Thu, 17 Jul 2014 21:13:19 +0000 (UTC) Received: by mail-wg0-f46.google.com with SMTP id m15so2540443wgh.17 for ; Thu, 17 Jul 2014 14:13:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=dN26qToEZOOiPYkJdKXiOhQWiFXuk6UUK7VK2MINUoM=; b=0hr4Q+4cLzGglSF7oaBep/P3iXPtUzPloEl/YzsHP8xzHO+XOf4abNEgcV06NwMRre NNYLbcexkM6D4hse95PFhrdAUDVaWO0UmJLvOjRCQ+pcepxtgRA0nI88pA1tiXmo3NDd 1wALFxdGcr8E2OjJJZHnFbZUw3vwzhpcCTZHzElkNZ29BNTpNSqx15kzDbIFmg5cOD2X ocTZ3E1eC66KXvMSjzQgTA78ZHxnHGreXeWVYE5M3Ng7gMCN7NbTo2qMHMLak//Jjr2u az+tDcVkMGg2fXY4oFAgiq1rXU2Kg8sQ455yB7TQYlQp6JQp4KeVhuKqkNp1sL6/UpGH Q/Jw== X-Received: by 10.181.13.112 with SMTP id ex16mr25444517wid.58.1405631597746; Thu, 17 Jul 2014 14:13:17 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id di7sm8861163wjb.34.2014.07.17.14.13.16 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 Jul 2014 14:13:16 -0700 (PDT) Sender: Baptiste Daroussin Date: Thu, 17 Jul 2014 23:13:14 +0200 From: Baptiste Daroussin To: Andreas Nilsson Subject: Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg? Message-ID: <20140717211314.GG28314@ivaldir.etoilebsd.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="m972NQjnE83KvVa/" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Craig Rodrigues , Adrian Chadd , freebsd-current Current , freebsd-doc@freebsd.org, ports X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2014 21:13:20 -0000 --m972NQjnE83KvVa/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 17, 2014 at 09:57:44PM +0200, Andreas Nilsson wrote: > On Thu, Jul 17, 2014 at 9:28 PM, Adrian Chadd wrote: >=20 > > Hi! > > > > 3) The binary packages need to work out of the box > > 4) .. which means, when you do things like pkg install apache, it > > can't just be installed and not be enabled, because that's a bit of a > > problem; > > > I disagree on this. For network services on linux ( apart from ssh ), I > want that started very seldom. But I do want the package installed so that > when I need it, it is there. Having it autostart as part of being install= ed > is breaking KISS and in some way unix philosophy: I asked for something to > be installed, not installed and autostarted. >=20 > > 5) .. and then we need examples of actually deploying useful > > scenarios, like "so here's what you type to get django working right", > > "here's how you get a default memcached that works well", "here's how > > you bring up node.js", etc. > > > Oh yes. I think that quite a few packages have default options that make > them unsuitable for out-of-box usage, ie some lack the sane default > dbi-stuff and so on. >=20 Reporting them is very much needed, we try to change this but without repor= t it is hard, as much as I can I use vanilla packages now, and I discovered that= they are now pretty much sane, a few example has been found and modified recently like nginx not supporting https by default, so do not hesitate to report any unsuitable options for out-of-box usage. regards, Bapt --m972NQjnE83KvVa/ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlPIPGoACgkQ8kTtMUmk6EwnGwCghpAb7hNsedG1Vq3nKxIpXsFn ausAn1PcYrU9sQrXC2LUnJM47PUA8tU+ =E4Du -----END PGP SIGNATURE----- --m972NQjnE83KvVa/--