On Wed, Aug 10, 2016, at 01:56 AM, Ian Kelling wrote:
> On Tue, Aug 9, 2016, at 07:38 PM, andrew bezella wrote:
> > On Tue, 2016-08-09 at 14:12 -0700, Ian Kelling wrote:
> > >
> > > Yes, I'm following this path. At the top of 30-interface, I have a
> > > condition
> > > for if the os is in a class
On Tue, Aug 9, 2016, at 07:38 PM, andrew bezella wrote:
> On Tue, 2016-08-09 at 14:12 -0700, Ian Kelling wrote:
> >
> > Yes, I'm following this path. At the top of 30-interface, I have a
> > condition
> > for if the os is in a class that uses a persistent name, and inside
> > I have this code:
>
On Tue, 2016-08-09 at 14:12 -0700, Ian Kelling wrote:
>
> Yes, I'm following this path. At the top of 30-interface, I have a
> condition
> for if the os is in a class that uses a persistent name, and inside
> I have this code:
[...]
oh! i like that solution, thanks for sharing...
--
andrew bez
On Thu, Aug 4, 2016, at 08:52 AM, andrew bezella wrote:
>
> why slot and not port:
> > Working from top to bottom, udev takes the first match of:
> >
> > * ID_NET_NAME_FROM_DATABASE
> > * ID_NET_NAME_ONBOARD
> > * ID_NET_NAME_SLOT
> > * ID_NET_NAME_PATH
> > * ID_NET_NAME_MAC
>
> cf.
> https:/
On Fri, Aug 5, 2016, at 06:59 AM, Alexander Thomas wrote:
> This assumes the first interface shown by lshw is the one you want,
> which was the case on the few systems I tried this on. Your mileage
> may vary :)
fyi: on my machine the first is the wrong one.
I have another workaround that allows to use the new network names,
even when doing a pure USB/DVD install with no working network
connection:
In the jessie NFSroot etc/grub.cfg, add “net.ifnames=1 biosdevname=1”
to the kernel command line, to mimic the defaults from Ubuntu.
In scripts/DEBIAN/30-i
On Thu, 2016-08-04 at 22:20 +0200, Thomas Lange wrote:
[...]
> I'm not sure if the kernel version or systemd or both are responsible
> for this. You may want to try a 4.x kernel from backports inside the
> nfsroot. Here's how to install the 4.x kernel inside the nfsroot:
> http://wiki.fai-project.
> On Thu, 4 Aug 2016 17:09:58 +0200, Alexander Thomas
> said:
> I now have the same problem while installing xenial from a jessie
> NFSroot. It defines an interface eth0 in /etc/network/interfaces, but
> when the installed system boots, the interface is named ‘ens3’.
I think
On Thu, 2016-08-04 at 17:09 +0200, Alexander Thomas wrote:
[...]
> Although it feels dirty and unreliable and I don't know why I need to
> use SLOT here instead of PATH, it worked fine, at first. When I try to
> install a VM with a virtio network interface, it breaks. In that case,
> ID_NET_NAME_S
Network naming has been troublesome for a bit. If you want to keep the
classic names, your boot string needs to contain:
net.ifnames=0 biosdevname=0
On Thu, Aug 4, 2016 at 10:09 AM, Alexander Thomas <
alexander.tho...@esaturnus.com> wrote:
> There was a discussion titled “example network scrip
There was a discussion titled “example network script will misname
interface if installing stretch” just a few weeks ago. It ended with:
Thomas Lange wrote:
> > Using jessie as the base os to install stretch.
> > 30-interface will setup /etc/network/interfaces with
> > something like eth0, and if
11 matches
Mail list logo
