[gentoo-user] no network "eth0" after upgrade.

[gentoo-user] no network "eth0" after upgrade.

[thelma]

I just upgraded one of my systems and upon boot there is no network:

/etc/init.d/net.eth0 start
* Mounting local filesystems ...
mount: mount point /proc/bus/usb does not exist
* Some local filesystem failed to start
ERROR: localmount failed to start
ERROR: cannot start net.eth0 as localmount would not start

rc-status sysinit
sysfs   [  started  ]
dmesg   [  started  ]
devfs  [  started  ]
tmpfiles.dev  [  started  ]
udev   [  started


I can not even ssh to the system as network is not working.
What to check next?

-- 
Thelma

Re: [gentoo-user] no network "eth0" after upgrade.

[thelma]

On 12/19/2015 12:10 PM, thelma@sys-concept.com wrote:
> I just upgraded one of my systems and upon boot there is no network:
> 
> /etc/init.d/net.eth0 start
> * Mounting local filesystems ...
> mount: mount point /proc/bus/usb does not exist
> * Some local filesystem failed to start
> ERROR: localmount failed to start
> ERROR: cannot start net.eth0 as localmount would not start
> 
> rc-status sysinit
> sysfs   [  started  ]
> dmesg   [  started  ]
> devfs  [  started  ]
> tmpfiles.dev  [  started  ]
> udev   [  started
> 
> 
> I can not even ssh to the system as network is not working.
> What to check next?
> 
It seems I'm not the only one:
https://forums.gentoo.org/viewtopic-t-1034770-highlight-localmount.html

"The problem was openrc-0.18.4. When I downgraded to openrc-0.16.4 the
problem went away."

Now, I can not downgrade without eth0 working.
Do I need to boot strap and downgrade or is there is easier solution?

--
Thelma

Re: [gentoo-user] no network "eth0" after upgrade.

[Alexander Kapshuk]

[-- Attachment #1: Type: text/plain, Size: 1895 bytes --]

On Sat, Dec 19, 2015 at 9:24 PM, <thelma@sys-concept.com> wrote:

>
> On 12/19/2015 12:10 PM, thelma@sys-concept.com wrote:
> > I just upgraded one of my systems and upon boot there is no network:
> >
> > /etc/init.d/net.eth0 start
> > * Mounting local filesystems ...
> > mount: mount point /proc/bus/usb does not exist
> > * Some local filesystem failed to start
> > ERROR: localmount failed to start
> > ERROR: cannot start net.eth0 as localmount would not start
> >
> > rc-status sysinit
> > sysfs   [  started  ]
> > dmesg   [  started  ]
> > devfs  [  started  ]
> > tmpfiles.dev  [  started  ]
> > udev   [  started
> >
> >
> > I can not even ssh to the system as network is not working.
> > What to check next?
> >
> It seems I'm not the only one:
> https://forums.gentoo.org/viewtopic-t-1034770-highlight-localmount.html
>
> "The problem was openrc-0.18.4. When I downgraded to openrc-0.16.4 the
> problem went away."
>
> Now, I can not downgrade without eth0 working.
> Do I need to boot strap and downgrade or is there is easier solution?
>
> --
> Thelma
>
>
>
Here is a news item that explains the situation.

2015-10-07-openrc-0-18-localmount-and-netmount-changes
  Title                     OpenRC-0.18 localmount and netmount changes
  Author                    William Hubbs <williamh@gentoo.org>
  Posted                    2015-10-07
  Revision                  1

The behaviour of localmount and netmount is changing on Linux systems.
In the past, these services always started successfully. However, now they
will fail if a file system they attempt to mount cannot be mounted.

If you have file systems listed in fstab which should not be mounted at
boot time, make sure to add noauto to the mount options. If you have
file systems that you want to attempt to mount at boot time but failure
should be allowed, add nofail to the mount options for these file
systems in fstab.

[-- Attachment #2: Type: text/html, Size: 2780 bytes --]

Re: [gentoo-user] no network "eth0" after upgrade.

[Alexander Kapshuk]

[-- Attachment #1: Type: text/plain, Size: 2965 bytes --]

On Sat, Dec 19, 2015 at 9:57 PM, Alexander Kapshuk <
alexander.kapshuk@gmail.com> wrote:

> On Sat, Dec 19, 2015 at 9:24 PM, <thelma@sys-concept.com> wrote:
>
>>
>> On 12/19/2015 12:10 PM, thelma@sys-concept.com wrote:
>> > I just upgraded one of my systems and upon boot there is no network:
>> >
>> > /etc/init.d/net.eth0 start
>> > * Mounting local filesystems ...
>> > mount: mount point /proc/bus/usb does not exist
>> > * Some local filesystem failed to start
>> > ERROR: localmount failed to start
>> > ERROR: cannot start net.eth0 as localmount would not start
>> >
>> > rc-status sysinit
>> > sysfs   [  started  ]
>> > dmesg   [  started  ]
>> > devfs  [  started  ]
>> > tmpfiles.dev  [  started  ]
>> > udev   [  started
>> >
>> >
>> > I can not even ssh to the system as network is not working.
>> > What to check next?
>> >
>> It seems I'm not the only one:
>> https://forums.gentoo.org/viewtopic-t-1034770-highlight-localmount.html
>>
>> "The problem was openrc-0.18.4. When I downgraded to openrc-0.16.4 the
>> problem went away."
>>
>> Now, I can not downgrade without eth0 working.
>> Do I need to boot strap and downgrade or is there is easier solution?
>>
>> --
>> Thelma
>>
>>
>>
> Here is a news item that explains the situation.
>
> 2015-10-07-openrc-0-18-localmount-and-netmount-changes
>   Title                     OpenRC-0.18 localmount and netmount changes
>   Author                    William Hubbs <williamh@gentoo.org>
>   Posted                    2015-10-07
>   Revision                  1
>
> The behaviour of localmount and netmount is changing on Linux systems.
> In the past, these services always started successfully. However, now they
> will fail if a file system they attempt to mount cannot be mounted.
>
> If you have file systems listed in fstab which should not be mounted at
> boot time, make sure to add noauto to the mount options. If you have
> file systems that you want to attempt to mount at boot time but failure
> should be allowed, add nofail to the mount options for these file
> systems in fstab.
>
>
>
As a follow up, here is a postinst message generated for openrc that might
come in handy as well:
>>> Messages generated by process 3631 on 2015-12-03 16:53:14 EET for
package sys-apps/openrc-0.18.4:

WARN: postinst
In this version of OpenRC, the loopback interface no longer
satisfies the net virtual.
If you have services now which do not start because of this,
They can be fixed by adding rc_need="!net"
to the /etc/conf.d/<servicename> file.
You should also file a bug against the service asking that
need net be dropped from the dependencies.
The bug you file should block the following tracker:
https://bugs.gentoo.org/show_bug.cgi?id=439092

Bug https://bugs.gentoo.org/show_bug.cgi?id=427996 was not
fixed correctly in earlier versions of OpenRC.
The correct fix is implemented in this version, but that
means netmount needs to be added to the default runlevel if
you are using nfs file systems.

[-- Attachment #2: Type: text/html, Size: 4420 bytes --]

Re: [gentoo-user] no network "eth0" after upgrade.

[thelma]

On 12/19/2015 12:57 PM, Alexander Kapshuk wrote:
[snip]

>>>
>> It seems I'm not the only one:
>> https://forums.gentoo.org/viewtopic-t-1034770-highlight-localmount.html
>>
>> "The problem was openrc-0.18.4. When I downgraded to openrc-0.16.4 the
>> problem went away."
>>
>> Now, I can not downgrade without eth0 working.
>> Do I need to boot strap and downgrade or is there is easier solution?
>>
>> --
>> Thelma
>>
>>
>>
> Here is a news item that explains the situation.
> 
> 2015-10-07-openrc-0-18-localmount-and-netmount-changes
>   Title                     OpenRC-0.18 localmount and netmount changes
>   Author                    William Hubbs <williamh@gentoo.org>
>   Posted                    2015-10-07
>   Revision                  1
> 
> The behaviour of localmount and netmount is changing on Linux systems.
> In the past, these services always started successfully. However, now they
> will fail if a file system they attempt to mount cannot be mounted.
> 
> If you have file systems listed in fstab which should not be mounted at
> boot time, make sure to add noauto to the mount options. If you have
> file systems that you want to attempt to mount at boot time but failure
> should be allowed, add nofail to the mount options for these file
> systems in fstab.
> 

This is my fstab:
/dev/hda1		/boot		ext2		noauto,noatime		1 1
/dev/hda3		/		ext3		noatime			0 1
/dev/hda2		none		swap		sw			0 0
/dev/hda4		/home		ext3		noatime	  		0 1

/dev/hdd		/mnt/cdrom	auto		noauto,ro,users		0 0
/dev/hdd                /mnt/dvdr       auto         noauto,users            0 0

# Scanner
none   /proc/bus/usb   usbfs           defaults,devmode=0666   0 0

none			/proc		proc		defaults		0 0

Does it mean I should add: "nofail" to Scanner and "/proc" line?

--
Thelma

Re: [gentoo-user] no network "eth0" after upgrade.

[John Runyon]

Not proc, but you should add nofail to scanner.

John Runyon
Sent from my phone

On Dec 19, 2015 2:59 PM, thelma@sys-concept.com wrote:
>
> On 12/19/2015 12:57 PM, Alexander Kapshuk wrote: 
> [snip] 
>
> >>> 
> >> It seems I'm not the only one: 
> >> https://forums.gentoo.org/viewtopic-t-1034770-highlight-localmount.html 
> >> 
> >> "The problem was openrc-0.18.4. When I downgraded to openrc-0.16.4 the 
> >> problem went away." 
> >> 
> >> Now, I can not downgrade without eth0 working. 
> >> Do I need to boot strap and downgrade or is there is easier solution? 
> >> 
> >> -- 
> >> Thelma 
> >> 
> >> 
> >> 
> > Here is a news item that explains the situation. 
> > 
> > 2015-10-07-openrc-0-18-localmount-and-netmount-changes 
> >   Title                     OpenRC-0.18 localmount and netmount changes 
> >   Author                    William Hubbs <williamh@gentoo.org> 
> >   Posted                    2015-10-07 
> >   Revision                  1 
> > 
> > The behaviour of localmount and netmount is changing on Linux systems. 
> > In the past, these services always started successfully. However, now they 
> > will fail if a file system they attempt to mount cannot be mounted. 
> > 
> > If you have file systems listed in fstab which should not be mounted at 
> > boot time, make sure to add noauto to the mount options. If you have 
> > file systems that you want to attempt to mount at boot time but failure 
> > should be allowed, add nofail to the mount options for these file 
> > systems in fstab. 
> > 
>
> This is my fstab: 
> /dev/hda1 /boot ext2 noauto,noatime 1 1 
> /dev/hda3 / ext3 noatime 0 1 
> /dev/hda2 none swap sw 0 0 
> /dev/hda4 /home ext3 noatime   0 1 
>
> /dev/hdd /mnt/cdrom auto noauto,ro,users 0 0 
> /dev/hdd                /mnt/dvdr       auto         noauto,users            0 0 
>
> # Scanner 
> none   /proc/bus/usb   usbfs           defaults,devmode=0666   0 0 
>
> none /proc proc defaults 0 0 
>
> Does it mean I should add: "nofail" to Scanner and "/proc" line? 
>
> -- 
> Thelma 
>

Re: [gentoo-user] no network "eth0" after upgrade.

[thelma]

On 12/19/2015 02:04 PM, John Runyon wrote:
> Not proc, but you should add nofail to scanner.
> 
> John Runyon
> Sent from my phone
> 
> On Dec 19, 2015 2:59 PM, thelma@sys-concept.com wrote:
>>
>> On 12/19/2015 12:57 PM, Alexander Kapshuk wrote: 
>> [snip] 
>>
>>>>>
>>>> It seems I'm not the only one: 
>>>> https://forums.gentoo.org/viewtopic-t-1034770-highlight-localmount.html 
>>>>
>>>> "The problem was openrc-0.18.4. When I downgraded to openrc-0.16.4 the 
>>>> problem went away." 
>>>>
>>>> Now, I can not downgrade without eth0 working. 
>>>> Do I need to boot strap and downgrade or is there is easier solution? 
>>>>
>>>> -- 
>>>> Thelma 
>>>>
>>>>
>>>>
>>> Here is a news item that explains the situation. 
>>>
>>> 2015-10-07-openrc-0-18-localmount-and-netmount-changes 
>>>    Title                     OpenRC-0.18 localmount and netmount changes 
>>>    Author                    William Hubbs <williamh@gentoo.org> 
>>>    Posted                    2015-10-07 
>>>    Revision                  1 
>>>
>>> The behaviour of localmount and netmount is changing on Linux systems. 
>>> In the past, these services always started successfully. However, now they 
>>> will fail if a file system they attempt to mount cannot be mounted. 
>>>
>>> If you have file systems listed in fstab which should not be mounted at 
>>> boot time, make sure to add noauto to the mount options. If you have 
>>> file systems that you want to attempt to mount at boot time but failure 
>>> should be allowed, add nofail to the mount options for these file 
>>> systems in fstab. 
>>>
>>
>> This is my fstab: 
>> /dev/hda1 /boot ext2 noauto,noatime 1 1 
>> /dev/hda3 / ext3 noatime 0 1 
>> /dev/hda2 none swap sw 0 0 
>> /dev/hda4 /home ext3 noatime   0 1 
>>
>> /dev/hdd /mnt/cdrom auto noauto,ro,users 0 0 
>> /dev/hdd                /mnt/dvdr       auto         noauto,users            0 0 
>>
>> # Scanner 
>> none   /proc/bus/usb   usbfs           defaults,devmode=0666   0 0 
>>
>> none /proc proc defaults 0 0 
>>
>> Does it mean I should add: "nofail" to Scanner and "/proc" line? 

OK, I've added "nofail" to Scanner, and still no network after boot.

--
Thelma

Re: [gentoo-user] no network "eth0" after upgrade.

[Dale]

thelma@sys-concept.com wrote:
> On 12/19/2015 02:04 PM, John Runyon wrote:
>> Not proc, but you should add nofail to scanner.
>>
>> John Runyon
>> Sent from my phone
>>
>> On Dec 19, 2015 2:59 PM, thelma@sys-concept.com wrote:
>>> On 12/19/2015 12:57 PM, Alexander Kapshuk wrote: 
>>> [snip] 
>>>
>>>>> It seems I'm not the only one: 
>>>>> https://forums.gentoo.org/viewtopic-t-1034770-highlight-localmount.html 
>>>>>
>>>>> "The problem was openrc-0.18.4. When I downgraded to openrc-0.16.4 the 
>>>>> problem went away." 
>>>>>
>>>>> Now, I can not downgrade without eth0 working. 
>>>>> Do I need to boot strap and downgrade or is there is easier solution? 
>>>>>
>>>>> -- 
>>>>> Thelma 
>>>>>
>>>>>
>>>>>
>>>> Here is a news item that explains the situation. 
>>>>
>>>> 2015-10-07-openrc-0-18-localmount-and-netmount-changes 
>>>>    Title                     OpenRC-0.18 localmount and netmount changes 
>>>>    Author                    William Hubbs <williamh@gentoo.org> 
>>>>    Posted                    2015-10-07 
>>>>    Revision                  1 
>>>>
>>>> The behaviour of localmount and netmount is changing on Linux systems. 
>>>> In the past, these services always started successfully. However, now they 
>>>> will fail if a file system they attempt to mount cannot be mounted. 
>>>>
>>>> If you have file systems listed in fstab which should not be mounted at 
>>>> boot time, make sure to add noauto to the mount options. If you have 
>>>> file systems that you want to attempt to mount at boot time but failure 
>>>> should be allowed, add nofail to the mount options for these file 
>>>> systems in fstab. 
>>>>
>>> This is my fstab: 
>>> /dev/hda1 /boot ext2 noauto,noatime 1 1 
>>> /dev/hda3 / ext3 noatime 0 1 
>>> /dev/hda2 none swap sw 0 0 
>>> /dev/hda4 /home ext3 noatime   0 1 
>>>
>>> /dev/hdd /mnt/cdrom auto noauto,ro,users 0 0 
>>> /dev/hdd                /mnt/dvdr       auto         noauto,users            0 0 
>>>
>>> # Scanner 
>>> none   /proc/bus/usb   usbfs           defaults,devmode=0666   0 0 
>>>
>>> none /proc proc defaults 0 0 
>>>
>>> Does it mean I should add: "nofail" to Scanner and "/proc" line? 
> OK, I've added "nofail" to Scanner, and still no network after boot.
>
> --
> Thelma
>
>


I'd try adding nofail to all except / and /home.  Then remove one at a
time until it fails again and that should be the one that is messing
with you. 

Dale

:-)  :-) 

Re: [gentoo-user] no network "eth0" after upgrade.

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 843 bytes --]

On Sat, 19 Dec 2015 13:59:38 -0700, thelma@sys-concept.com wrote:

> This is my fstab:
> /dev/hda1		/boot		ext2
> noauto,noatime		1
> 1 /dev/hda3		/		ext3
> noatime			0 1 /dev/hda2
> none		swap		sw			0
> 0 /dev/hda4		/home		ext3
> noatime	  		0 1
> 
> /dev/hdd		/mnt/cdrom	auto
> noauto,ro,users		0
> 0 /dev/hdd                /mnt/dvdr       auto
> noauto,users            0 0
> 
> # Scanner
> none   /proc/bus/usb   usbfs           defaults,devmode=0666   0 0
> 
> none			/proc		proc
> defaults		0 0

Just a wild guess, but you're trying to mount /proc/bus/usb before
mounting /proc. systemd takes care of such things but I think with openrc
local mounts are mounted in the order they appear in fstab. Try switching
the lines.


-- 
Neil Bothwick

"I'm Not Sure If I'm Homosexual", Said Tom, Half In Earnest.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] no network "eth0" after upgrade.

[Philip Webb]

151219 Neil Bothwick wrote:
> On Sat, 19 Dec 2015 13:59:38 -0700, thelma@sys-concept.com wrote:
>> This is my fstab:
   ...
>> none   /proc/bus/usb   usbfs           defaults,devmode=0666   0 0
>> none   /proc	          proc            defaults	          0 0
> 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.

That looks like the explanation to me : has Thelma tried this ?

-- 
========================,,============================================
SUPPORT     ___________//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT    `-O----------O---'   purslowatchassdotutorontodotca

Re: [gentoo-user] no network "eth0" after upgrade.

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 722 bytes --]

On Sat, 19 Dec 2015 19:02:54 -0500, Philip Webb wrote:

> >> none   /proc/bus/usb   usbfs           defaults,devmode=0666   0 0
> >> none   /proc	          proc
> >> defaults	          0 0  
> > 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.  
> 
> That looks like the explanation to me : has Thelma tried this ?

Looking at it again, I don't think either of those entries should be in
fstab, certainly not the /proc one.


-- 
Neil Bothwick

If Wile E. Coyote had enough money to buy all that ACME crap, why didn't
he just buy dinner?

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] [SOLVED] no network "eth0" after upgrade.

[thelma]

On 12/19/2015 05:56 PM, Neil Bothwick wrote:
> On Sat, 19 Dec 2015 19:02:54 -0500, Philip Webb wrote:
> 
>>>> none   /proc/bus/usb   usbfs           defaults,devmode=0666   0 0
>>>> none   /proc	          proc
>>>> defaults	          0 0  
>>> 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.  
>>
>> That looks like the explanation to me : has Thelma tried this ?
> 
> Looking at it again, I don't think either of those entries should be in
> fstab, certainly not the /proc one.

Good hint, thank you.
I've removed both lines from fstab:
# Scanner
none   /proc/bus/usb   usbfs           defaults,devmode=0666   0 0
none /proc proc defaults 0 0

and the system booted normally with  openrc-0.18.4

Question, why isn't the line:
none /proc proc defaults 0 0
needed anymore?

All my other systems have this line in fstab.

--
Thelma

Re: [gentoo-user] [SOLVED] no network "eth0" after upgrade.

[Philip Webb]

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 ?

-- 
========================,,============================================
SUPPORT     ___________//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT    `-O----------O---'   purslowatchassdotutorontodotca

Re: [gentoo-user] [SOLVED] no network "eth0" after upgrade.

[thelma]

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

Re: [gentoo-user] [SOLVED] no network "eth0" after upgrade.

[J. Roeleveld]

On 20 December 2015 05:19:13 CET, Philip Webb <purslow@ca.inter.net> 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 ?

It's been deprecated for a while.
Not sure when, think it was in a news item.

It certainly hasn't been in stage3 tarballs for the past 2 years. (Unless it reappeared suddenly)
I know this because that's when I installed my laptop and that line never was there.

--
Joost 
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] [SOLVED] no network "eth0" after upgrade.

[Philip Webb]

151220 J. Roeleveld wrote:
> On 20 December 2015 05:19:13 CET, Philip Webb <purslow@ca.inter.net> wrote:
>> My 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 ?
> It's been deprecated for a while.  Not sure when, it was in a news item.
> It certainly hasn't been in stage3 tarballs for the past 2 years.

I checked the default Fstab which came with Stage 3
& there's no sign of it, so I deleted it, rebooted & everything works.
There were also these lines :
  # >= glibc 2.2 expect tmpfs to be mounted at /dev/shm
  # for POSIX shared memory (shm_open, shm_unlink).
  # tmpfs is a dynamically expandable/shrinkable ramdisk
  # and will use almost no memory if not populated with files.
  # Adding the following line should take care of this:
  none   /dev/shm   tmpfs   defaults   0 0
I deleted them too & it seems to have had no effect.

However, I was amused to see that the Stage 3 Fstab does have the line :
  /dev/fd0    /mnt/floppy   auto   noauto   0 0
Does anyone still use diskettes ?  Today's mobos have no slot for them.

-- 
========================,,============================================
SUPPORT     ___________//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT    `-O----------O---'   purslowatchassdotutorontodotca

Re: [gentoo-user] [SOLVED] no network "eth0" after upgrade.

[J. Roeleveld]

On Sunday, December 20, 2015 05:54:19 AM Philip Webb wrote:
> 151220 J. Roeleveld wrote:
> > On 20 December 2015 05:19:13 CET, Philip Webb <purslow@ca.inter.net> 
wrote:
> >> My 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 ?
> > 
> > It's been deprecated for a while.  Not sure when, it was in a news item.
> > It certainly hasn't been in stage3 tarballs for the past 2 years.
> 
> I checked the default Fstab which came with Stage 3
> & there's no sign of it, so I deleted it, rebooted & everything works.
> There were also these lines :
>   # >= glibc 2.2 expect tmpfs to be mounted at /dev/shm
>   # for POSIX shared memory (shm_open, shm_unlink).
>   # tmpfs is a dynamically expandable/shrinkable ramdisk
>   # and will use almost no memory if not populated with files.
>   # Adding the following line should take care of this:
>   none   /dev/shm   tmpfs   defaults   0 0
> I deleted them too & it seems to have had no effect.
> 
> However, I was amused to see that the Stage 3 Fstab does have the line :
>   /dev/fd0    /mnt/floppy   auto   noauto   0 0
> Does anyone still use diskettes ?  Today's mobos have no slot for them.

I actually still have a drive and some diskettes.
I also have a USB diskdrive somewhere...

Haven't actually checked any mobos for floppy-connectors. Got some old ones 
that do have a connector.

--
Joost

Re: [gentoo-user] [SOLVED] no network "eth0" after upgrade.

[Daniel Frey]

On 12/20/2015 02:54 AM, Philip Webb wrote:
> However, I was amused to see that the Stage 3 Fstab does have the line :
>   /dev/fd0    /mnt/floppy   auto   noauto   0 0
> Does anyone still use diskettes ?  Today's mobos have no slot for them.
> 

I have a USB floppy drive around for those BIOSes that have trouble
updating firmware from USB. I remember once there was a fix in the BIOS
update to make updating from USB work but you either needed a) a Windows
install or b) a floppy drive to apply the update.

Dan

Re: [gentoo-user] no network "eth0" after upgrade.

[Alan Mackenzie]

Hello, Thelma.

On Sat, Dec 19, 2015 at 12:10:58PM -0700, thelma@sys-concept.com wrote:
> I just upgraded one of my systems and upon boot there is no network:

> /etc/init.d/net.eth0 start
> * Mounting local filesystems ...
> mount: mount point /proc/bus/usb does not exist
> * Some local filesystem failed to start
> ERROR: localmount failed to start
> ERROR: cannot start net.eth0 as localmount would not start

> rc-status sysinit
> sysfs   [  started  ]
> dmesg   [  started  ]
> devfs  [  started  ]
> tmpfiles.dev  [  started  ]
> udev   [  started


> I can not even ssh to the system as network is not working.
> What to check next?

Have you got CONFIG_FHANDLE set in your kernel config?  This almost
tripped me up when I synched a day or two ago.  The new udev ebuild
output a message saying this was needed.  It wasn't wrong, either.

CONFIG_FHANDLE can be found in General Setup, under the prompt "open by
fhandle syscalls".

> -- 
> Thelma

-- 
Alan Mackenzie (Nuremberg, Germany).

Re: [gentoo-user] no network "eth0" after upgrade.

[thelma]

On 12/19/2015 01:13 PM, Alan Mackenzie wrote:
> Hello, Thelma.
> 
> On Sat, Dec 19, 2015 at 12:10:58PM -0700, thelma@sys-concept.com wrote:
>> I just upgraded one of my systems and upon boot there is no network:
> 
>> /etc/init.d/net.eth0 start
>> * Mounting local filesystems ...
>> mount: mount point /proc/bus/usb does not exist
>> * Some local filesystem failed to start
>> ERROR: localmount failed to start
>> ERROR: cannot start net.eth0 as localmount would not start
> 
>> rc-status sysinit
>> sysfs   [  started  ]
>> dmesg   [  started  ]
>> devfs  [  started  ]
>> tmpfiles.dev  [  started  ]
>> udev   [  started
> 
> 
>> I can not even ssh to the system as network is not working.
>> What to check next?
> 
> Have you got CONFIG_FHANDLE set in your kernel config?  This almost
> tripped me up when I synched a day or two ago.  The new udev ebuild
> output a message saying this was needed.  It wasn't wrong, either.
> 
> CONFIG_FHANDLE can be found in General Setup, under the prompt "open by
> fhandle syscalls".


I had CONFIG_FHANDLE=y in kernel .config

--
Thelma