Re: [gentoo-user] The device-mapper init script is written for baselayout-2

[Matthias Bethke]

Hi Stroller,
on Fri, Mar 07, 2008 at 12:51:04PM +0000, 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