public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: thelma@sys-concept.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [SOLVED] no network "eth0" after upgrade.
Date: Sat, 19 Dec 2015 21:26:12 -0700	[thread overview]
Message-ID: <56762DE4.6040106@sys-concept.com> (raw)
In-Reply-To: <20151220041913.GD1245@ca.inter.net>

On 12/19/2015 09:19 PM, Philip Webb wrote:
> 151219 thelma@sys-concept.com wrote:
>> On 12/19/2015 05:56 PM, Neil Bothwick wrote:
>>> On Sat, 19 Dec 2015 19:02:54 -0500, Philip Webb wrote:
> Thelma> none   /proc/bus/usb   usbfs           defaults,devmode=0666   0 0
>> none   /proc	          proc
>> defaults	          0 0  
> Neil> You're trying to mount /proc/bus/usb before mounting /proc.
>> Systemd takes care of such things,  
>> but with Openrc local mounts are mounted in the order they appear in
>> fstab. Try switching the lines.  
> Philip> That looks like the explanation to me : has Thelma tried this ?
> Neil> Looking at it again, I don't think either of those entries
>> should be in fstab, certainly not the /proc one.
> Thelma> Good hint, thank you.  I've removed both lines from fstab:
>> and the system booted normally with openrc-0.18.4
>> Question, why isn't 'none /proc proc defaults 0 0' needed anymore ?
>> All my other systems have this line in fstab.
> 
> My own Fstab has long had these lines :
> 
>   # NB The next line is critical for boot!
>   none   /proc   proc   defaults   0 0
> 
> When did this change & why ?  Does anyone know ?

I would like to know that too!

Indeed I had same comments on some of my other systems, but it seems to
me this line is no longer needed.  I'm compiling two other backup system
and commented these line out from fstab, let see what happens.

--
Thelma



  reply	other threads:[~2015-12-20  4:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-19 19:10 [gentoo-user] no network "eth0" after upgrade thelma
2015-12-19 19:24 ` thelma
2015-12-19 19:57   ` Alexander Kapshuk
2015-12-19 20:03     ` Alexander Kapshuk
2015-12-19 20:59     ` thelma
2015-12-19 21:04       ` John Runyon
2015-12-19 21:10         ` thelma
2015-12-19 21:20           ` Dale
2015-12-19 23:02       ` Neil Bothwick
2015-12-20  0:02         ` Philip Webb
2015-12-20  0:56           ` Neil Bothwick
2015-12-20  1:48             ` [gentoo-user] [SOLVED] " thelma
2015-12-20  4:19               ` Philip Webb
2015-12-20  4:26                 ` thelma [this message]
2015-12-20  5:37                 ` J. Roeleveld
2015-12-20 10:54                   ` Philip Webb
2015-12-20 14:42                     ` J. Roeleveld
2015-12-20 17:01                     ` Daniel Frey
2015-12-19 20:13 ` [gentoo-user] " Alan Mackenzie
2015-12-19 20:46   ` thelma

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=56762DE4.6040106@sys-concept.com \
    --to=thelma@sys-concept.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