| View previous topic :: View next topic |
| Author |
Message |
pjp
Administrator
Joined: 16 Apr 2002
Posts: 20067
|
 Posted: Tue May 14, 2002 11:02 pm Post subject: *PROVIDE: "warning?" hmm... |
 |
|
I see this now on bootup. Been a while since I've rebooted, but I think it started after sound started to "sort of" work.
| Code: | * Caching dependencies...
*PROVIDE: it is usually not a good idea to have more than one
service provide the same virtual service (alsa-modules)! [ok] |
I only have soundcore in my modules.autoload file... what else is there besides /etc/modules.d/alsa? |
|
| Back to top |
|
 |
pjp
Administrator
Joined: 16 Apr 2002
Posts: 20067
|
| Posted: Wed May 15, 2002 4:55 am Post subject: |
|
|
| /etc/init.d/depscan.sh seems to be the script that reports the problem. I think its a bit advanced for my deciphering abilities. |
|
| Back to top |
|
|
tomte
Tux's lil' helper
Joined: 08 May 2002
Posts: 122
|
| Posted: Wed May 15, 2002 5:48 am Post subject: |
|
|
| kanuslupus wrote: | | /etc/init.d/depscan.sh seems to be the script that reports the problem. I think its a bit advanced for my deciphering abilities. |
it means that you have (at least) two files in /etc/init.d that include
| Code: |
depend() {
...
provide alsa-modules
...
}
|
I assume you are safe with alsa-modules, as long as not both are active in the same runlevel; otherwise just move the one you are not using to a safe place.
I had had same warning with 'logger' and ignored it, I had only one logger in my runlevels; but dependencies lead to the point where both attampted to start at boot after I installed exim, so moving the unused one may be a good idea anyway,
correct me if i'm wrong
regards,
tom |
|
| Back to top |
|
|
Guest
|
| Posted: Wed May 15, 2002 7:34 am Post subject: |
|
|
| It is kind of weird, the file it is refering to can not be removed, and neither can the newer file. I had this problem with Alsa also, I had to rename a file to alsa, cant remember. I just redid my computer and will let you know if it comes up again. |
|
| Back to top |
|
|
pjp
Administrator
Joined: 16 Apr 2002
Posts: 20067
|
| Posted: Wed May 15, 2002 4:14 pm Post subject: |
|
|
All grep turned up were alsasound and an alsasound.old. The .old version was one I saved after
emerge told me I had files to update. Wonder if that did it. Will reboot later to find out. |
|
| Back to top |
|
|
rieger
Tux's lil' helper
Joined: 14 Jun 2002
Posts: 136
Location: The Netherlands
|
| Posted: Wed Jul 17, 2002 7:01 pm Post subject: |
|
|
I've had the same problem. Installed
1.3b again from scratch (finally
good, this time) and when I did emerge metalog and
rc-update add metalog default, I've got the same
"PROVIDE, blabla virtual service " warning.
I seemed that and dcron and vcron where in /mnt/.init.d/provide/cron, so I removed dcron and when I did rc-update metalog again, the warning was gone.
maybe this helps.
(If this message is rather messy, it's because of my non-skills of Lynx; emerging gnome right now  )
_________________
haree |
|
| Back to top |
|
|
Vanquirius
Retired Dev
Joined: 14 Jun 2002
Posts: 1297
Location: Ethereal plains
|
| Posted: Wed Aug 21, 2002 7:30 pm Post subject: |
|
|
I had this same problem, using dcron and then fcron...
Mine was kinda nasty because after I deleted /mnt/.init.d/provide/cron/dcron, it was automatically re-created for some reason I'm too lazy to figure out.
I solved the problem by verifying that both dcron and fcron were properly unmerged, then I deleted the files dcron and fcron from /etc/init.d, as well as the folder cron from /mnt/init.d/provide, and emerged fcron again.
Thanks for the help, its always good to find your question answered without having to post it 
_________________
Hello. |
|
| Back to top |
|
|
|
Other Things Gentoo
