Neil Bothwick wrote:
On Sat, 08 Mar 2008 16:36:55 -0600, Dale wrote:
I would stop the service, remove it from any of the run levels and
reboot and see what happens. I guess in theory you could just go to
single user mode but I would reboot if it were me. If everything goes
well then you may be able to remove it and cause no harm.
Just stop the service and remove it from all runlevels, that's it.
The elog message when installing device-mapper is quite clear "If you are
using baselayout-2, be sure to run: # rc-update add device-mapper boot".
As the OP is almost certainly not using baselayout-2, it is masked, this
service should never have been added to any runlevel.
I noticed this tho:
[EMAIL PROTECTED] / # eix device-mapper
[I] sys-fs/device-mapper
Available versions: 1.02.19 1.02.19-r1 ~1.02.22 ~1.02.22-r1
~1.02.22-r3 ~1.02.22-r4 1.02.22-r5 ~1.02.24 ~1.02.24-r1 {selinux}
Installed versions: 1.02.22-r5(05:16:18 AM 11/30/2007)(-selinux)
Homepage: http://sources.redhat.com/dm/
Description: Device mapper ioctl library for use with LVM2
utilities
[EMAIL PROTECTED] / #
If he uses LVM then he may need it. You are right on the baselayout but
this got installed here when I was playing around with LVM. I would
hate for him to be using LVM and not have this when he reboots. I
didn't see any mention of this in the original post. He may not use LVM
but if he does. . . .
Also note, I have not used/installed baselayout to version 2 either but
I still have this installed and it is needed by something else, that I
may not need either. I haven't went that far here.
Dale
:-) :-)
--
gentoo-user@lists.gentoo.org mailing list
