Am 07.01.2015 um 14:06 schrieb Alan McKinnon:

> The tricky one is going to be that persistent interface names from udev
> 18 months or so back. When you get to that, you'll probably want to
> re-read the huge threads from that time, as you only get one chance to
> get it right.

One addition:

at the reboot time a fellow IT-guy will be there in front of the console
so if the NIC doesn't come up correctly I will be able to instruct him
to get the box up and reachable for me.

I also use to disable persistent names for such updates  ... and get
good old eth0 UP instead of enpXsY unconfigured ;-)


> I see in your reply to Neil you have glibc conflicts. I don't know what
> will happen if you do it with --nodeps, but I wouldn't try that. The box
> is remote, if something goes wrong...   Rather go with Tomas' suggestion
> of yearly portage snapshots and update in stages.

skip that ... I leave glibc for now and focus on udev and openrc, see below.

> openrc should be seamless. I forget the exact timelines, but IIRC you
> will also hit baselayout-2 migration. That one was very smooth and well
> documented so you shouldn't have much trouble.

openrc needs an updated udev and I am currently working on getting at
least sys-fs/udev-208-r1 installed now (conflicts with lvm2 and stuff ...)

Some circular dep between udev and udev-init-scripts blocks things ... I
fiddled with this and now decided to gor for a "--nodeps"  ... while I
type this udev, lvm2 and udev-init-scripts get emerged OK now.

Phew.

openrc installs now as well ... so now for "dispatch-conf" and
"disabling the persistent nic names"

Seems as if the biggest problems are solved right now?

S

Reply via email to