Hi there, I recently noticed a problem when my Slackware system boots. I see warnings! On boot I see three warnings that look like "WARNING: All config files need .conf: /etc/modprobe.d/sound, it will be ignored in a future release". (they all say /etc/modprobe.d/sound, which I thought was weird because it is the same warning three times) I also see this "WARNING: commands will be executed using /bin/sh"

What exactly is happening? How should I fix it?

No, it's not anything to worry about at this time. Not all the warnings you see are actual problems. Many are just informational or detailing things that only really concern the developers.

modprobe.conf is where configuration settings files for your kernel modules sit. All this warning says is that the naming conventions for the files have changed, and that sometime in the future the changes will be made mandatory. You apparently still have a few files with the old names, but for the time being it's still accepting them.

Even when it does become mandatory it will be mostly your distro's maintainers that have to worry about it. Multiple warnings show because when modules are loaded they often call dependent modules, meaning that sometimes duplicate calls are made. This is harmless. Check out the man pages for modprobe and modprobe.conf for more about it.

I'm not sure about the last part, but again, I don't think it's a problem. Startup scripts should generally be written to posix-compatible .sh standards anyway. As long as everything seems to be working I wouldn't worry about it.

Ok, thank you. I just noticed them and got a little worried about my system. Also, is it normal to have a boot time of 45 seconds? I am even using slackware, so I would assume it should be faster. I already made changes talked about in this thread. (specifically the changes detailed by mokele.) Im relieved that the warnings arent harmful to my system, but there still must be something "off."

45 seconds sounds quite good to me, depending on your hardware and exactly how you're measuring it. It's faster than either of my systems can manage. What about it makes you think something has to be "off"?

There are a lot of factors, both hardware and software, involved in the boot sequence, making any kind of comparison across different systems extremely difficult. Indeed, I find worrying about startup time rather pointless. It only makes up small part of your entire computer use, so what difference does an extra 10-15 seconds here and there make?

Very true, that is a great point. I was just under the assumption that such a minimalistic distro would be able to load up faster than windows. (Windows 7 boots in 20 seconds flat on this same computer... under half the time.) It just seemed to be an abnormally long startup time for this machine as the other distros I have played with booted quickly as well.

Maybe Im just really paranoid about something being wrong with my computer?