From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Fy9la-0002w8-St for garchives@archives.gentoo.org; Wed, 05 Jul 2006 15:58:19 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.7/8.13.6) with SMTP id k65FuR17011949; Wed, 5 Jul 2006 15:56:27 GMT Received: from rwcrmhc15.comcast.net (rwcrmhc15.comcast.net [204.127.192.85]) by robin.gentoo.org (8.13.7/8.13.6) with ESMTP id k65Fq0Lh017823 for ; Wed, 5 Jul 2006 15:52:01 GMT Received: from seldon (c-24-21-135-117.hsd1.or.comcast.net[24.21.135.117]) by comcast.net (rwcrmhc15) with SMTP id <20060705155159m15004et60e>; Wed, 5 Jul 2006 15:51:59 +0000 Date: Wed, 5 Jul 2006 08:51:58 -0700 From: Brian Harring To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: Re: Re: GPL and Source code providing Message-ID: <20060705155158.GC8423@seldon> References: <20060701111437.0ed09223@c1358217.kevquinn.com> <1151848708.9102.10.camel@vertigo.twi-31o2.org> <44AA9076.5010001@gentoo.org> <44AA8A69.7000103@gentoo.org> <1152104430.21775.25.camel@cgianelloni.nuvox.net> <20060705131918.GA8423@seldon> <44ABC0E2.1000407@gentoo.org> <20060705141956.GB8423@seldon> <44ABD4E8.3050205@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DIOMP1UsTsWJauNi" Content-Disposition: inline In-Reply-To: <44ABD4E8.3050205@gentoo.org> User-Agent: Mutt/1.5.11 X-Archives-Salt: 82dd5531-c7f9-4be7-b85b-3b5cadf66747 X-Archives-Hash: 8add6afdaa262d226f7d12a9d0c2ed2d --DIOMP1UsTsWJauNi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 05, 2006 at 10:04:08AM -0500, Lance Albertson wrote: > Brian Harring wrote: >=20 > >> don't see why we need to have a public system setup as long as we can > >> provide the source when asked. As far as a I know, the GPL doesn't > >> dicate that we have to provide the sources in an internet media form. > >> They just need to be available when requested. Perhaps we can have a > >> document that explains a process for getting said sources. I don't see > >> the point of creating a torrent/whatever system just for the rare > >> instances that people want the older source. Way too much overhead for > >> something I don't see being used much. > >=20 > > Files are going to have to be held onto somewhere long term- which is= =20 > > easier, flipping on lighttpd for the storage dir, or having to dick=20 > > around with making requests of infra (waiting for them to respond),=20 > > and requiring infra to do more work? >=20 > Maintaining a service requires more work than just keeping it running. > You have to make sure all the components involved with the service are > running properly, all the security aspects are covered, proper DoS > control is in place, etc. Yes, from your point of view its easy, but > there's a little more involved than just putting something up. Not the only sysadmin around ;) I know bringing up new services can=20 increase maintainence efforts, and potential for risk. That said, y'all _should_ have a fairly vanilla base configuration=20 across all servers (base kernel config, firewalling, grsec config,=20 etc). Further, y'all were running lighttpd last I knew- so y'all=20 should be tracking it for securities concerns already... and this=20 particular setup is pretty damn simple (no dynamic, straight=20 dir_index). So... it's not a herculean task, not something like trying to=20 maintain a secured wiki. > > Upshot of my suggestion, folk have access to the purgatory dir so they= =20 > > can go digging through old files from the mirror tier as needed. >=20 > I have seen zero requests in the time I've been in Gentoo for this. Talk to web crew, stuart in particular. Beyond them (their=20 complaints/issues predate my time of managing the mirror image), folks=20 _do_ screw up and needed to raid files from the mirror (lost patches=20 in particular), requests I used to take care of. Every few months is a rough rate going by memory at 8:30am. Not huge,=20 but as said, if need to provide access to gpl'd sources for bin (not=20 just releng cds btw, people are forgetting we have precompiled pkgs in=20 the tree also), it _is_ a potential route for handling that=20 requirement while killing off another bit of manual work. > I, fail to see where you think there's a sudden demand for this. > I have no > problem getting these files to people. I have a problem with putting > resources into something that doesn't need that kind of resource > allocated to it based on current demand. I don't see the problem with > dealing such things on a case-by-case basis. If demand increases, then > we can change it. Since I see no demand now, this doesn't affect our > workload at all. > I have no problem if we archive them somewhere. I have SAN space at one > our locations which I've started using for archival/backup purposes. > However, I wasn't intending on this machine to become a publically > accessible machine, so I would have to change things around which I > don't want to do unless its needed. I don't see the demand to warrant > such a service. Am I stating there is a 'sudden demand'? I don't see throngs of folks=20 screaming for a fallback tier (am seeing people screaming for=20 patches.g.o, which is inline with this), thing is y'all have to=20 archive this stuff and I'm pointing out a way to make it not suck and=20 provide some extra functionality with minimal cost. > > End result, infra has to maintain archives. My proposal, all infra=20 > > has to do is flip on lighttpd somewhere, and I (or zac) do the=20 > > mirror-dist modifications. >=20 > As stated above, not as simple as it sounds. Looks easy on paper, but > there's more involved in the backend that just flipping on an httpd. I'm > already archiving the master mirror files (including purgatory stuff) > twice a week so that aspect is already done. But as I said earlier, I > don't want this machine to become a publically accessible machine. That > wasn't my intention when I set it up. I do have some options at this > location if we need to make the files more public, but I don't see the > demand to warrant that. Suggest others are given time to weigh in on this rather then=20 restating that you don't think there is demand for it. Nobody yays it, hey, folks have spoken and y'all go with the same=20 non public backup. ~harring --DIOMP1UsTsWJauNi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEq+AevdBxRoA3VU0RAg4vAJ9OJl4CJuSgiVB3+ZsgxA2/qyffQQCgjaok HrIgwfz2ikELDwTAPm8iiU0= =tZL3 -----END PGP SIGNATURE----- --DIOMP1UsTsWJauNi-- -- gentoo-dev@gentoo.org mailing list