View previous topic :: View next topic |
Author |
Message |
Tony0945 Watchman
Joined: 25 Jul 2006 Posts: 5127 Location: Illinois, USA
|
Posted: Sat Jan 26, 2013 1:44 am Post subject: [SOLVED] Request How to downgrade udev |
|
|
I did a system update and struggled through the udev-171 to udev-197 update. Today, lo and behold, there is a news item that tells me that with udev-197 I will have some goofy name for eth0 instead of eth0 which has been around like forever. The news item refers to a bug report which suggests downgrading if one wants to keep eth0. I made the following changes to /etc/portage/package.mask
Code: |
>=sys-fs/udev-197
>=virtual/udev-197
>=sys-fs/udev-init-scripts-19
|
I unmerged sys-fs/udev and /virtual/udev but I still can emerge udev:
Quote: | emerge -auvND --with-bdeps=y --keep-going world
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N ] virtual/udev-171 USE="gudev hwdb introspection keymap (-selinux) -static-libs" 0 kB
[ebuild U #] sys-fs/udev-197-r4 [171-r10] USE="acl%* gudev hwdb introspection keymap kmod%* openrc%* -doc% (-selinux) -static-libs% (-action_modeswitch%) (-build%) (-debug%) (-edd%) (-extras%) (-floppy%) (-rule_generator%*) (-test%)" 0 kB
[ebuild N #] virtual/udev-197 USE="gudev hwdb introspection keymap (-selinux) -static-libs" 0 kB
[ebuild N #] sys-fs/udev-init-scripts-21-r1 5 kB
[blocks B ] <sys-fs/udev-186 ("<sys-fs/udev-186" is blocking sys-fs/udev-init-scripts-21-r1)
Total: 4 packages (1 upgrade, 3 new), Size of downloads: 5 kB
Conflict: 1 block (1 unsatisfied)
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
virtual/udev:0
(virtual/udev-171::gentoo, ebuild scheduled for merge) pulled in by
=virtual/udev-171[gudev] required by (dev-libs/libgusb-0.1.4::gentoo, installed)
(and 14 more with the same problem)
(virtual/udev-197::gentoo, ebuild scheduled for merge) pulled in by
>=virtual/udev-197 required by (sys-fs/udev-197-r4::gentoo, ebuild scheduled for merge)
(and 2 more with the same problem)
sys-fs/udev:0
(sys-fs/udev-171-r10::gentoo, installed) pulled in by
~sys-fs/udev-171[gudev?,hwdb?,introspection?,keymap?,selinux?] required by (virtual/udev-171::gentoo, ebuild scheduled for merge)
(sys-fs/udev-197-r4::gentoo, ebuild scheduled for merge) pulled in by
>=sys-fs/udev-197-r3[gudev?,hwdb?,introspection?,keymap?,selinux?,static-libs?] required by (virtual/udev-197::gentoo, ebuild scheduled for merge)
It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously. If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously.
For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.
The following keyword changes are necessary to proceed:
#required by virtual/udev-197, required by sys-fs/udev-init-scripts-21-r1
=sys-fs/udev-197-r4 ~amd64
#required by sys-fs/udev-197-r4[openrc], required by virtual/udev-197, required by sys-fs/udisks-1.0.4-r4, required by sys-apps/gnome-disk-utility-3.0.2-r201, required by @selected, required by @world (argument)
=sys-fs/udev-init-scripts-21-r1 ~amd64
The following mask changes are necessary to proceed:
#required by virtual/udev-197, required by sys-fs/udev-init-scripts-21-r1
# /etc/portage/package.mask:
#=sys-apps/busybox-1.20.1
=sys-fs/udev-197-r4
#required by x11-misc/colord-0.1.26[udev], required by x11-libs/gtk+-3.4.4[colord], required by x11-misc/xdg-user-dirs-gtk-0.9, required by gnome-base/gnome-session-2.32.1-r3, required by gnome-base/gnome-2.32.1-r2, required by @selected, required by @world (argument)
# /etc/portage/package.mask:
#=sys-apps/busybox-1.20.1
=virtual/udev-197
#required by sys-fs/udev-197-r4[openrc], required by virtual/udev-197, required by sys-fs/udisks-1.0.4-r4, required by sys-apps/gnome-disk-utility-3.0.2-r201, required by @selected, required by @world (argument)
# /etc/portage/package.mask:
#=sys-apps/busybox-1.20.1
=sys-fs/udev-init-scripts-21-r1
NOTE: The --autounmask-keep-masks option will prevent emerge
from creating package.unmask or ** keyword changes.
Use --autounmask-write to write changes to config files (honoring CONFIG_PROTECT).
|
This has turned into a real rat's nest and if I ever reboot, the system will fail. How can I downgrade so that I can have eth0 like (almost) every other Linux system?
Last edited by Tony0945 on Tue Feb 19, 2013 1:35 am; edited 1 time in total |
|
Back to top |
|
|
The Doctor Moderator
Joined: 27 Jul 2010 Posts: 2678
|
Posted: Sat Jan 26, 2013 1:59 am Post subject: |
|
|
You don't need to downgrade. Check the link in the news item.
You need a file in /etc/udev/rules.d/80-net-name-slot.rules
In the file you only need to create the file and add a line Code: | # I don't like change! | See This topic _________________ First things first, but not necessarily in that order.
Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box. |
|
Back to top |
|
|
wcg Guru
Joined: 06 Jan 2009 Posts: 588
|
Posted: Sat Jan 26, 2013 6:35 am Post subject: |
|
|
To stay with udev-171 for the moment:
In /etc/portage/package.mask (or in /etc/portage/package.mask/[category] ):
Code: |
>=sys-fs/udev-181
>=sys-fs/udev-init-scripts-18
>virtual/udev-171
|
In /etc/portage/package.use (or in /etc/portage/package.use/[category] ):
Code: |
sys-fs/udev extras keymap
sys-fs/lvm2 -thin -udev
sys-fs/eudev legacy-libudev
virtual/udev keymap
|
I do not know how long this will hold for, but it works for me for now.
I do not know if you need the USE=extras for udev, I added it at
the suggestion of the xfce4 installation guide. The lvm2 USE="-thin -udev"
avoiding pulling in some extra dependencies that I do not need. I do
not actually have eudev installed, just thinking ahead. If I do install it,
I will want that USE flag, at least at first. _________________ TIA |
|
Back to top |
|
|
Tony0945 Watchman
Joined: 25 Jul 2006 Posts: 5127 Location: Illinois, USA
|
Posted: Sat Jan 26, 2013 11:50 pm Post subject: |
|
|
Thank you for the instructions that I asked for, wcg.
For the doctor, I already had a 80-net-name-slot.rules. I don't know where it came from, but it only holds comments.
Following a suggestion in the bug thread from the emerge notes, I modified 70-persistent-net.rules as follows:
Quote: | # PCI device 0x10de:0x03ef (forcedeth)
#SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1a:4d:71:d2:e3", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:1a:4d:71:d2:e3", NAME="eth0"
|
The last line being added and the previous line which was active being commented out. Then heart in mouth, I rebooted remotely. A minute later, I successfully puttY'd into the system.
The /dev/cdrom exists but not the second dvd rom, but that's for another thread. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|