Date: Wed, 19 Jan 2011 17:32:06 +0100 From: "Julian H. Stacey" <jhs@berklix.com> To: freebsd-questions@freebsd.org Cc: Chad Perrin <perrin@apotheon.com> Subject: Re: chromium producing constant hdd access Message-ID: <201101191632.p0JGW6lC016002@fire.js.berklix.net> In-Reply-To: Your message "Sun, 16 Jan 2011 18:47:26 MST." <20110117014726.GA25607@guilt.hydra>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi questions@ Chad Perrin wrote: > > --Nq2Wo0NMKNjxTN9z > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Sun, Jan 16, 2011 at 11:51:43AM +0000, Alexander Best wrote: > > hi there, > >=20 > > i noticed chromium is producing a lot of hdd activity. i think it writes = > every > > 1kb of new data directly to disk or so. is there a way to increase chromi= > ums > > download buffer somehow. firefox or opera seem to have a much larger down= > load > > buffer and write bigger chunks to disk. thus they produce a lot less hdd = > writes > > per second. > >=20 > > has anybody experienced the same behavior? > > I haven't used the Chromium browser in months, since a bunch of > vulnerabilities arose and the port maintainer's business model evidently > makes it impossible for him to update the port to fix vulnerabilities > that are less than a year old. > > --=20 > Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] I answered this with a To: ports@ + BCC: questions@, to avoid a double post thread, & split the topic, leaving hdd access on questions, & seconding the issue of Non Maintenance of chromium to ports@. BCC alarmed the anti spam freebsd robot, & though I'm subscribed to questions@, the post to questions@ got referred to moderators, who did not pass it, here it is. I suggest for follow up: Issue: List name: Get Maintainer To Fix Make ports@freebsd.org Disc Access ? questions@freebsd.org ----------- >From owner-freebsd-ports@freebsd.org Mon Jan 17 21:06:00 2011 To: ports@freebsd.org From: "Julian H. Stacey" <jhs@berklix.com> Date: Mon, 17 Jan 2011 20:12:40 +0100 Cc: rene@freebsd.org, Chad Perrin <perrin@apotheon.com>, "Gary Jennejohn \(Home\)" <gljennjohn@googlemail.com> Subject: www/chromium MAINTAINER, was Re: chromium producing constant hdd access Hi ports@freebsd.org & cc GaryJ & rene@ bcc: freebsd-questions@freebsd.org The hdd access thread could continue on questions@ so I left that BCC'd but issue of MAINTAINER of www/chromium best on ports@ list. Reference: > From: Chad Perrin <perrin@apotheon.com> > > On Sun, Jan 16, 2011 at 11:51:43AM +0000, Alexander Best wrote: > > hi there, > >=20 > > i noticed chromium is producing a lot of hdd activity. i think it writes = > every > > 1kb of new data directly to disk or so. is there a way to increase chromi= > ums > > download buffer somehow. firefox or opera seem to have a much larger down= > load > > buffer and write bigger chunks to disk. thus they produce a lot less hdd = > writes > > per second. > >=20 > > has anybody experienced the same behavior? > > I haven't used the Chromium browser in months, since a bunch of > vulnerabilities arose and the port maintainer's business model evidently > makes it impossible for him to update the port to fix vulnerabilities > that are less than a year old. ports/www/chromium "MAINTAINER" rene@ (cc'd) leaves it broken (see mail below), it still won't even compile (I just checked again a week later). A CVS roll back would at least get it compiling again, rene@ has ignored request to roll back. If rene@ resigns, MAINTAINER would revert to ports@freebsd.org so others could fix FreeBSD's current ports/www/chromium -------- ] To: =?ISO-8859-1?Q?Ren=E9_Ladan?= <rene@freebsd.org> ] cc: "Gary Jennejohn (Home)" <gljennjohn@googlemail.com> ] Subject: Re: /pri/FreeBSD/branches/amd64/-current/ports/www/chromium ] From: "Julian H. Stacey" <jhs@berklix.com> ] cc: "Julian H. Stacey" <jhs@berklix.com> ] Date: Mon, 10 Jan 2011 18:51:26 +0100 ] Sender: jhs@berklix.com ] ] Hi, ] Reference: ] > From: =?ISO-8859-1?Q?Ren=E9_Ladan?= <rene@freebsd.org> ] > Date: Mon, 10 Jan 2011 18:06:37 +0100 ] > Message-id: <AANLkTimgs7dVK=6-nmgfNVN18w3wMARdE_VWBKnLp_5S@mail.gmail.com> ] ] =?ISO-8859-1?Q?Ren=E9_Ladan?= wrote: ] > 2011/1/10 Julian H. Stacey <jhs@berklix.com>: ] > > Hi Rene cc Gary, ] > > ] > > =?ISO-8859-1?Q?Ren=E9_Ladan?= wrote: ] > >> 2011/1/10 Julian H. Stacey <jhs@berklix.com>: ] > >> > Hi rene@FreeBSD.org ] > >> > cc Gary J ] > >> > ] > >> > FYI as maintainer of chromium ] > >> > ] > >> > cd /pri/FreeBSD/branches/amd64/-current/ports/www/chromium ] > >> > setenv PORTSDIR /pri/FreeBSD/branches/amd64/-current/ports ] > >> > uname -a ] > >> > FreeBSD fire.js.berklix.net 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Mon Jul 12 00:59:43 CEST 2010 jhs@fire.js.berklix.net:/usr1/src/sys/amd64/compile/FIRE64.small amd64 ] > >> > make ] > >> > ===> chromium-6.0.472.63 cannot install: Unknown component dconf. ] > >> > ] > >> > I have built chromium before on this box, ] > >> > "About" key reports: 6.0.472.63(0) ] > >> > /var/db/pkg/chromium-6.0.472.63 ] > >> > ] > >> > It won't rebuild now though, ] > >> > ( I was trying to rebuild to make package for a friend cc'd Gary ] > >> > who runs current, chrome doesnt build for him too apparently ) ] > >> > ] > >> Currently the version of Chromium in the Ports Collection is marked as ] > >> FORBIDDEN because of security problems, and the source distribution ] > >> tarball is unavailable. ] > >> ] > >> There should be a new version (9.0) available ] > >> soonish though. ] > >> ] > >> Rene ] > > ] > > If chromium generic team fix security issues, ] ] You lost text from my reply, here it is again: ] ] ] ] If chromium generic team fix security issues, but still use ] ] ] dconf, that may still leave you needing to fix the FreeBSD Makefile ] ] ] to fix the dconf build dependency failure ? I have source here if ] ] ] you want it, so you can fix that in parallel to save waiting. ] ] ] ] ] ] 95188168 Nov 12 11:29 chromium-courgette-redacted-6.0.472.63.tar.xz ] ] ] MD5 (chromium-courgette-redacted-6.0.472.63.tar.xz) = adb9186424fa1800eef49cd14329821e ] ] ] ] ] ] My binaries were localy built here by me using current Makefile, so I presume ] ] ] someone broke current Makefile after that, possibly before it was ] ] ] marked forbidden (which I hashed out) ? Unless its eg my local ] ] ] env/ libs or something broke since I built it. ] ] ] ] ] ] Dates of my builds: ] ] ] ] ] ] -r-xr-xr-x 1 root wheel 63947372 Nov 24 09:43 /usr/local/share/chromium/chrome* ] ] ] amd64 ] ] ] ] ] ] -r-xr-xr-x 1 root wheel 56994655 Nov 25 00:57 /usr/local/share/chromium/chrome* ] ] ] i686 ] ] ] > They only fix them for the current stable/beta/dev (8/9/10) ] > versions of Chromium. The old maintainer ported obsolete versions ] ] Which built & runs. ] ] > of Chromium unless you paid for them. ] ] I paid nothing, it built & runs. ] ] > Currently there is no free version of Chromium on FreeBSD. ] ] Who broke ports/www/chromium build some time after 25 Nov 2010 ? ] As Maintainer, please back out CVS commits till it builds again, ] (leave it marked as FORBIDDEN= if you choose), ] only recommit changes when you have sources that build. ------------------- Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail plain text; Not quoted-printable, or HTML or base 64. Avoid top posting, it cripples itemised cumulative responses.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201101191632.p0JGW6lC016002>