On Mon, 20 May 2002 18:38:55 -0700 Patrick Beart <[EMAIL PROTECTED]> wrote:
> Folks: > > I know this has been touched upon (or even answered) before, > but I still have a problem ... > > at boot up (Enigma), I get the sound server "Informational" > alert that there was a problem initializing the sound driver. Device > "/dev/dsp can't be opened (no such device)", blah, blah, blah. > > I looked on the Red Hat Web site, (searched for "sound") and > found the info on running "sndconfig". Trouble is that following > instructions (to type "sndconfig" at the command line) resulted in > the message ... > "bash: sndconfig: command not found." > > I did a "root" find for sndconfig and found the following > instances of the utility: > /usr/sbin/sndconfig > /usr/share/sndconfig > /sbin/sndconfig > > What's the deal? This is a default install (on an IBM Thinkpad > 600). > > > > > > Patrick echo $PATH I'd bet /usr/sbin isn't in there. And if you logged in as $USER and used su to get to root, /sbin won't be there either. Need to edit ~/.bash_profile (for the user) or /etc/profile (for the system, my preferred method) and add /usr/sbin into the obvious path statement near the top. Neither will get it permanently assigned everywhere until you logout and back in. If you 'su' to root, you don't get root's environment, including paths. If you 'su -' to root, you do. By the same token, if you use $HOME/.bash_profile and add the path for /usr/sbin to it, and don't do the same in /etc/profile (you shouldn't do it in both), if you 'su -' to root, /usr/sbin won't be in the path. If 'su' to root, it will. If you put the path addition in /etc/profile it will always be available whether you 'su' or 'su -' to root. -- c:\windows\run c:\system\crash _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
