From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [~and64] Headsup for google-chrome users
Date: Fri, 22 May 2015 11:44:15 +0100 [thread overview]
Message-ID: <201505221144.17145.michaelkintzios@gmail.com> (raw)
In-Reply-To: <20150522093846.23cb4d75@digimed.co.uk>
[-- Attachment #1: Type: Text/Plain, Size: 898 bytes --]
On Friday 22 May 2015 09:38:46 Neil Bothwick wrote:
> On Fri, 22 May 2015 02:53:17 -0500, Dale wrote:
> > > So I'm the 3rd one in row to state that I haven't had any deleterious
> > > effects that I noticed.
>
> Make that 4.
>
> > When I first emerge a new kernel, I run make mrproper to get a good
> > clean start.
>
> There's no point in that. When you have just emerged the sources, there is
> nothing for mrproper to remove.
So, coming back to the OP, is it advisable to ignore this message:
* Messages for package www-client/chromium-43.0.2357.65:
[27/1984]
* USER_NS is required for sandbox to work
* Please check to make sure these options are set correctly.
* Failure to do so may cause unexpected problems.
which doesn't even advise where to find USER_NS, or will chromium no longer
work as it did in the past?
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-05-22 10:44 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 12:55 [gentoo-user] [~and64] Headsup for google-chrome users walt
2015-05-21 13:03 ` Alan McKinnon
2015-05-21 14:05 ` Mike Gilbert
2015-05-26 1:27 ` [gentoo-user] " Nikos Chantziaras
2015-05-21 14:57 ` [gentoo-user] " Dale
2015-05-21 15:29 ` Alec Ten Harmsel
2015-05-21 18:29 ` Neil Bothwick
2015-05-21 19:44 ` wabenbau
2015-05-21 20:45 ` Mike Gilbert
2015-05-21 23:49 ` Dale
2015-05-22 7:36 ` Mick
2015-05-22 7:53 ` Dale
2015-05-22 8:38 ` Neil Bothwick
2015-05-22 9:01 ` Dale
2015-05-22 9:19 ` Alan McKinnon
2015-05-22 12:54 ` gottlieb
2015-05-22 14:29 ` Daniel Frey
2015-05-22 17:21 ` Dale
2015-05-22 20:57 ` [gentoo-user] [~and64] Headsup for googled the previous one to vmlinu-chrome users Neil Bothwick
2015-05-22 22:04 ` Dale
2015-05-22 22:13 ` Neil Bothwick
2015-05-22 22:29 ` Mick
2015-05-22 22:58 ` Neil Bothwick
2015-05-23 0:55 ` Tom H
2015-05-23 8:17 ` Neil Bothwick
2015-05-23 0:52 ` Tom H
2015-05-23 4:21 ` Walter Dnes
2015-05-23 3:19 ` Dale
2015-05-22 21:09 ` [gentoo-user] [~and64] Headsup for google-chrome users Daniel Frey
2015-05-22 22:11 ` Dale
2015-05-22 10:44 ` Mick [this message]
2015-05-22 11:09 ` Alan McKinnon
2015-05-22 12:43 ` Mick
2015-05-22 12:47 ` [gentoo-user] " walt
2015-05-22 13:32 ` Mick
2015-05-22 21:13 ` walt
2015-05-22 21:38 ` Tom H
2015-05-22 22:19 ` walt
2015-05-22 23:00 ` Neil Bothwick
2015-05-23 0:30 ` Tom H
2015-05-22 22:25 ` Mick
2015-05-22 10:15 ` Quanyang Liu
2015-05-22 13:28 ` walt
2015-05-22 14:32 ` [gentoo-user] " Behrouz Khosravi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201505221144.17145.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox