Hello Everyone,

Last time I did this we experience 3 hour downtime, and it was not fun. I
was blue in the face:

[1]   N  2010-08-01  (2010-08-01-as-needed-default - removed?)
  [2]   N  2012-03-16  (2012-03-16-udev-181-unmasking - removed?)
  [3]   N  2012-05-21  Portage config-protect-if-modified default
  [4]   N  2012-09-09  (2012-09-09-make.conf-and-make.profile-move -
removed?)
  [5]   N  2012-11-06  PYTHON_TARGETS deployment
  [6]      2013-03-29  Upgrading udev to version >=200
  [7]      2013-06-07  Portage preserve-libs default
  [8]   N  2013-06-30  Printer browsing in net-print/cups-1.6
  [9]   N  2013-08-23  Language of messages in emerge logs and output
  [10]  N  2013-09-27  Separate /usr on Linux requires initramfs
  [11]  N  2013-10-14  GRUB2 migration
  [12]  N  2013-11-07  python-exec package move
  [13]  N  2014-02-25  Upgrade to >=sys-fs/udev-210
  [14]  N  2014-03-02  Profile EAPI 5 requirement
  [15]  N  2014-03-16  Ruby 1.8 removal; Ruby 1.9/2.0 default
  [16]  N  2014-11-07  Upgrade to udev >= 217 or eudev >= 2.1
  [17]  N  2015-01-28  CPU_FLAGS_X86 introduction


Grub2: Will this bring us down for days? Is it a hard transition
Udev: Oh what a spider web you weave..... We are using udev 204 right now.

Please gents, is there a safe and easy way of doing this? I need to update
the system but want to limit downtime as much as possible. Please help.


N.

Reply via email to