1 |
On Thursday, 6 December 2018 10:35:19 GMT Peter Humphrey wrote: |
2 |
> On Wednesday, 5 December 2018 11:11:06 GMT Mick wrote: |
3 |
> > On Wednesday, 5 December 2018 10:12:10 GMT Peter Humphrey wrote: |
4 |
> > > The main reason I've ditched chrome and chromium altogether is that they |
5 |
> > > insist on redirecting me to their mobile site - and this is a 27-inch |
6 |
> > > screen! But I'm also uncomfortable with the privacy concerns such as you |
7 |
> > > mention. |
8 |
> > |
9 |
> > I haven't noticed something like this here. Is there a particular site |
10 |
> > that causes this you could share? |
11 |
> |
12 |
> I'd like to check, but today I can't compile chromium; it throws a lot of |
13 |
> errors about an end of file coming before the end of data. I suppose it's |
14 |
> running out of space, though there seems to be plenty. I'll look into it. |
15 |
> |
16 |
> As far as I can remember though, it was the google.com home page. I didn't |
17 |
> get any further than that before complaining to google, waiting for the |
18 |
> inevitably absent reply, then giving up and ditching it. |
19 |
|
20 |
Well, I did manage to compile chromium in 165 minutes, but I had to switch off |
21 |
jumbo-build to do it. I'd have thought that 32GB RAM and 38GB swap would be |
22 |
enough for anything reasonable, but perhaps chromium isn't reasonable. |
23 |
|
24 |
And today, of course, there's an upgrade. That's another reason I ditched it. |
25 |
Is there a way to force chromium to be not ~amd64 on a ~amd64 system? |
26 |
|
27 |
-- |
28 |
Regards, |
29 |
Peter. |