Re: [gentoo-user] The device-mapper init script is written for baselayout-2
Am Sonntag, 9. März 2008 schrieb Dale: If he uses LVM then he may need it. No. Only if he also uses baselayout 2! He would need the devicemapper package, but NOT the init script that comes with it, because this is written for BL 2. Bye... Dirk signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] The device-mapper init script is written for baselayout-2
On Sunday 09 March 2008, Dale wrote:
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.
This thread is interesting, mostly because I think I'm the only poster
so far that thought to actually read the init script:
=
[EMAIL PROTECTED] ~ $ cat /etc/init.d/device-mapper
#!/sbin/runscript
# Copyright 1999-2007 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
#
$Header:
/var/cvsroot/gentoo-x86/sys-fs/device-mapper/files/device-mapper.rc-1.02.22-r3,v
1.5 2008/02/01 12:39:47 flameeyes Exp $
depend() {
if [ -e /lib/librc.so ]; then
# on baselayout-1 this causes
# a dependency loop with checkroot (before *)
after modules
before checkfs fsck
fi
}
start() {
if [ ! -e /lib/librc.so ]; then
eerror The ${SVCNAME} init script is written for
baselayout-2
eerror Please do not use it with baselayout-1
return 1
fi
start_addon dm
}
/lib/librc.so is not present under baselayout-1. So depend() evaluates
to a null statement and start() WILL exit without running any code.
All the OP needs do is remove device-mapper from his default runlevel.
--
Alan McKinnon
alan dot mckinnon at gmail dot com
--
gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] The device-mapper init script is written for baselayout-2
Dirk Heinrichs wrote: Am Sonntag, 9. März 2008 schrieb Dale: If he uses LVM then he may need it. No. Only if he also uses baselayout 2! He would need the devicemapper package, but NOT the init script that comes with it, because this is written for BL 2. Bye... Dirk Now I wonder how I got this package then. Time to search my logs I guess. Dale :-) :-) -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] The device-mapper init script is written for baselayout-2
On Sat, 08 Mar 2008 18:26:29 -0600, Dale wrote: 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. It seems everyone is getting wound up about nothing here. device-mapper is used for LVM, RAID, dm-crypt and maybe others. No one needs to uninstall anything. One file in the whole of the device-mapper package is an init script for baselayout 2 only. When run under baselayout 1 it does nothing but output a Don't run me warning. You should not uninstall any package, remove any file, pass Go or collect $200, just remove the script from the boot runlevel. The ebuild does not add the script to the runlevel, so the OP must have read the elog output about adding it for baselayout 2, misunderstood (or decided it would be a good idea to add it anyway) and added it to the boot runlevel. This was a mistake and the solution is simply to reverse this action by removing it from the runlevel. The has been a lot of speculation, confusion and misinformation in this thread when all that is needed it to undo one action. Yes Alan, I also know what the ebuild does :) -- Neil Bothwick The world is coming to an end... SAVE YOUR BUFFERS!! signature.asc Description: PGP signature
Re: [gentoo-user] The device-mapper init script is written for baselayout-2
Neil Bothwick wrote: It seems everyone is getting wound up about nothing here. device-mapper is used for LVM, RAID, dm-crypt and maybe others. No one needs to uninstall anything. One file in the whole of the device-mapper package is an init script for baselayout 2 only. When run under baselayout 1 it does nothing but output a Don't run me warning. You should not uninstall any package, remove any file, pass Go or collect $200, just remove the script from the boot runlevel. The ebuild does not add the script to the runlevel, so the OP must have read the elog output about adding it for baselayout 2, misunderstood (or decided it would be a good idea to add it anyway) and added it to the boot runlevel. This was a mistake and the solution is simply to reverse this action by removing it from the runlevel. The has been a lot of speculation, confusion and misinformation in this thread when all that is needed it to undo one action. Yes Alan, I also know what the ebuild does :) I may have misunderstood part of the problem myself and been unclear in what I was posting here. I was talking about removing the package not removing it from the run level. It seemed to me that removing the package may not be a good idea while removing it from a run level may not be to bad. At worst the OP may have to boot a CD or something to add it back. Some of the misunderstanding may be on my part. I have broke things by removing a package before and it is better to be safe than sorry. Sometimes I ask before removing things myself just to be sure. Dale :-) :-) -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] The device-mapper init script is written for baselayout-2
On Sun, 09 Mar 2008 04:46:18 -0500, Dale wrote: I may have misunderstood part of the problem myself and been unclear in what I was posting here. I was talking about removing the package not removing it from the run level. It seemed to me that removing the package may not be a good idea while removing it from a run level may not be to bad. At worst the OP may have to boot a CD or something to add it back. Do not remove the package - emerge -C will warn you about this. Do remove the script from all runlevels, which is what the error message said in the first place. -- Neil Bothwick Committee (noun): A group of people spending hours taking minutes signature.asc Description: PGP signature
Re: [gentoo-user] The device-mapper init script is written for baselayout-2
On 7 Mar 2008, at 19:11, Matthias Bethke wrote: on Fri, Mar 07, 2008 at 12:51:04PM +, you wrote: I'm not sure what this does, either. Someone may come along in a moment with better advice, but as a first step I'd `equery b /etc/initi.d/device-mapper`. If it says that device-mapper doesn't belong to any of your current packages then I think you can safely (remove it from the default runlevel and subsequently) delete it, otherwise I'd reemerge the package to which it belongs. Baselayout has a bunch of init scripts and utilities that all the other init scripts need, plus /etc/conf.d stuff (equery f baselayout can tell you what exactly). You certainly don't want to unmerge that if you ever plan to reboot your system. I wouldn't recommend unmerging it if it were needed, but `equery b / etc/initi.d/device-mapper` should show whether the file belongs to any package or not. If it doesn't belong to any package then it _should_ be safe to delete (but see my commend about removing it from the default runlevel first), and it should be safe to reemerge baselayout, should it belong to that package (or otherwise). Stroller. -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] The device-mapper init script is written for baselayout-2
Stroller wrote: On 7 Mar 2008, at 19:11, Matthias Bethke wrote: on Fri, Mar 07, 2008 at 12:51:04PM +, you wrote: I'm not sure what this does, either. Someone may come along in a moment with better advice, but as a first step I'd `equery b /etc/initi.d/device-mapper`. If it says that device-mapper doesn't belong to any of your current packages then I think you can safely (remove it from the default runlevel and subsequently) delete it, otherwise I'd reemerge the package to which it belongs. Baselayout has a bunch of init scripts and utilities that all the other init scripts need, plus /etc/conf.d stuff (equery f baselayout can tell you what exactly). You certainly don't want to unmerge that if you ever plan to reboot your system. I wouldn't recommend unmerging it if it were needed, but `equery b /etc/initi.d/device-mapper` should show whether the file belongs to any package or not. If it doesn't belong to any package then it _should_ be safe to delete (but see my commend about removing it from the default runlevel first), and it should be safe to reemerge baselayout, should it belong to that package (or otherwise). Stroller. I checked on my system, the device-mapper service is not running here and I don't recall every having it running. So far, everything works here. 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. According to what I am reading, it is used for LVM. Do you use that? I played with it a little bit once so I guess that is how I got it on mine here. That said, it appears something else depends on it: [EMAIL PROTECTED] / # equery depends device-mapper [ Searching for packages depending on device-mapper... ] sys-fs/cryptsetup-luks-1.0.4-r3 (=sys-fs/device-mapper-1.00.07-r1) [EMAIL PROTECTED] / # I would certainly test some things before removing this. Just to be safe. Dale :-) :-) -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] The device-mapper init script is written for baselayout-2
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. -- Neil Bothwick Disc space -- the final frontier! signature.asc Description: PGP signature
Re: [gentoo-user] The device-mapper init script is written for baselayout-2
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
Re: [gentoo-user] The device-mapper init script is written for baselayout-2
On 7 Mar 2008, at 02:29, Daevid Vincent wrote:
...
When I startup my notebook, I see this message:
* The device-mapper init script is written for baselayout-2
* Please do not use it with baselayout-1
locutus ~ # eix baselayout
[I] sys-apps/baselayout
Available versions: 1.11.15-r3 1.12.10-r5 ~1.12.11 1.12.11.1
[M]~2.0.0_rc6-r1 {bootstrap build kernel_FreeBSD kernel_linux pam
static
unicode}
Installed versions: 1.12.11.1(14:20:50 02/29/08)(-bootstrap -
build
-static -unicode)
Since I'm not real sure what this package does, I am unsure if I
should just
unmerge and re-emerge it (perhaps at one time I ran the ~x86
version and so
I have a mixture?)
I'm not sure what this does, either. Someone may come along in a
moment with better advice, but as a first step I'd `equery b /etc/
initi.d/device-mapper`. If it says that device-mapper doesn't belong
to any of your current packages then I think you can safely (remove
it from the default runlevel and subsequently) delete it, otherwise
I'd reemerge the package to which it belongs.
Stroller.
--
gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] The device-mapper init script is written for baselayout-2
I do equery b device-mapper:
I found this:
sys-fs/device-mapper-1.02.22-r5 (/etc/init.d/device-mapper)
sys-fs/device-mapper-1.02.22-r5 (/etc/conf.d/device-mapper)
Le Friday 07 March 2008 13:51:04 Stroller, vous avez écrit :
On 7 Mar 2008, at 02:29, Daevid Vincent wrote:
...
When I startup my notebook, I see this message:
* The device-mapper init script is written for baselayout-2
* Please do not use it with baselayout-1
locutus ~ # eix baselayout
[I] sys-apps/baselayout
Available versions: 1.11.15-r3 1.12.10-r5 ~1.12.11 1.12.11.1
[M]~2.0.0_rc6-r1 {bootstrap build kernel_FreeBSD kernel_linux pam
static
unicode}
Installed versions: 1.12.11.1(14:20:50 02/29/08)(-bootstrap -
build
-static -unicode)
Since I'm not real sure what this package does, I am unsure if I
should just
unmerge and re-emerge it (perhaps at one time I ran the ~x86
version and so
I have a mixture?)
I'm not sure what this does, either. Someone may come along in a
moment with better advice, but as a first step I'd `equery b /etc/
initi.d/device-mapper`. If it says that device-mapper doesn't belong
to any of your current packages then I think you can safely (remove
it from the default runlevel and subsequently) delete it, otherwise
I'd reemerge the package to which it belongs.
Stroller.
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] The device-mapper init script is written for baselayout-2
Hi Stroller, on Fri, Mar 07, 2008 at 12:51:04PM +, you wrote: Since I'm not real sure what this package does, I am unsure if I should just unmerge and re-emerge it (perhaps at one time I ran the ~x86 version and so I have a mixture?) I'm not sure what this does, either. Someone may come along in a moment with better advice, but as a first step I'd `equery b /etc/initi.d/device-mapper`. If it says that device-mapper doesn't belong to any of your current packages then I think you can safely (remove it from the default runlevel and subsequently) delete it, otherwise I'd reemerge the package to which it belongs. Baselayout has a bunch of init scripts and utilities that all the other init scripts need, plus /etc/conf.d stuff (equery f baselayout can tell you what exactly). You certainly don't want to unmerge that if you ever plan to reboot your system. I'm not 100% sure about the device-mapper script but I ran into the same question when I installed my new amd64 system these days. The x86 one didn't have it when I started using encrypted homes so I hadn't noticed it appeared in one of the latest dm-crypt versions. It looks like they just split off some functionality Baselayout-1 has in localmount and checkfs into its own script. Just ignore/remove it for now, there will probably be a fat warning when Baselayout-2 turns stable and you have to re-add it. cheers, Matthias -- I prefer encrypted and signed messages. KeyID: FAC37665 Fingerprint: 8C16 3F0A A6FC DF0D 19B0 8DEF 48D9 1700 FAC3 7665 pgpgWdYUrQfMZ.pgp Description: PGP signature
[gentoo-user] The device-mapper init script is written for baselayout-2
I've noticed this for quite some time and I'm finally getting around to
fixing it, if it even needs to be fixed...
When I startup my notebook, I see this message:
* The device-mapper init script is written for baselayout-2
* Please do not use it with baselayout-1
locutus ~ # eix baselayout
[I] sys-apps/baselayout
Available versions: 1.11.15-r3 1.12.10-r5 ~1.12.11 1.12.11.1
[M]~2.0.0_rc6-r1 {bootstrap build kernel_FreeBSD kernel_linux pam static
unicode}
Installed versions: 1.12.11.1(14:20:50 02/29/08)(-bootstrap -build
-static -unicode)
Since I'm not real sure what this package does, I am unsure if I should just
unmerge and re-emerge it (perhaps at one time I ran the ~x86 version and so
I have a mixture?)
Is there a better way to fix this?
Is it even worth fixing?
I don't *notice* anything wrong other than the warning there, so perhaps
it's just benign.
--
gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] The device-mapper init script is written for baselayout-2
On Friday 07 March 2008, Daevid Vincent wrote:
I've noticed this for quite some time and I'm finally getting around
to fixing it, if it even needs to be fixed...
When I startup my notebook, I see this message:
* The device-mapper init script is written for baselayout-2
* Please do not use it with baselayout-1
locutus ~ # eix baselayout
[I] sys-apps/baselayout
Available versions: 1.11.15-r3 1.12.10-r5 ~1.12.11 1.12.11.1
[M]~2.0.0_rc6-r1 {bootstrap build kernel_FreeBSD kernel_linux pam
static unicode}
Installed versions: 1.12.11.1(14:20:50 02/29/08)(-bootstrap
-build -static -unicode)
Since I'm not real sure what this package does, I am unsure if I
should just unmerge and re-emerge it (perhaps at one time I ran the
~x86 version and so I have a mixture?)
Is there a better way to fix this?
Is it even worth fixing?
I don't *notice* anything wrong other than the warning there, so
perhaps it's just benign.
READ THE ERROR MESSAGE PROPERLY.
It says The device-mapper init script is written for baselayout-2.
Please do not use it with baselayout-1.
What does that mean? It means that you are not using baselayout-2, you
are using baselayout-1, and you are also using the device-mapper init
script which doesn't work right with baselayout-1.
As it turns out, the init-script in this case just exists in this
condition, so you could ignore it. To make the message go away, remove
device-mapper from your runlevel:
sudo rc-update del device-mapper default
--
Alan McKinnon
alan dot mckinnon at gmail dot com
--
gentoo-user@lists.gentoo.org mailing list
