Thanks for this clarification Naren, it was news to me ...

Bish

On Fri, Feb 22, 2002 at 09:59:00AM -0800, Naren Devaiah wrote:
> The /dev/sound/* notation/convention is used by the devfs code.
> The device file system does not quite work the  same way as the 
> earlier /dev stuff.
> 
> Also, not all drivers support devfs fully (if at all!).
> Make sure the drivers you are using know about devfs and make use of
> that. Also, the applications that use the sound device need to be told of
> the different naming conventions.
> 
> Read more about the devfs at
> http://www.atnf.csiro.au/~rgooch/linux/docs/devfs.html
> 
> -Naren
> 
> 
>  On Fri, 22 Feb 2002, USM Bish wrote:
> 
> > On Thu, Feb 21, 2002 at 08:15:24PM +0530, L.V.Gandhi wrote:
> > > For me saytime program was working in  mdk 8.0.  But in mdk 
> > > 8.1 it is not working and msg says  /dev/audio could not be 
> > > found. 
> > 
> > This is strange. Did you re-install or upgrade ?  The  device
> > /dev/audio is usually set up during the installation.
> > 
> > >
> > > I did ln -s /dev/sound/dsp /dev/audio  I am getting garbled 
> > > sound. How to go about to make saytime to work?
> > > 
> > 
> > Did you confirm that /dev/audio  was not present,  before  you
> > took this step ?  In any case, you have no option  now  but to
> > re-make your /dev/audio.  A symlink to /dev/dsp  may not work.
> > I also notice that you have  annotated /dev/sound/dsp. This is
> > perhaps MDK specific ...
> > 
> > On my  Slack box, the /dev/audio and /dev/dsp  can be  created
> > as follows:
> > 
> > #makedev c  0664  root       sys  14  3  dsp
> > #makedev c  0664  root       sys  14  4  audio
> > 
> > Please note that the minor numbers vary. A symlink is unlikely
> > to get the correct kernel responses because of incorrect minor
> > number.
> > 
> > If you have MDK-8.0 somewhere,  check the major/ minor numbers
> > and create the device /dev/audio  using above syntax. In  case
> > you do not, re-confirm the major/ minor  with some other users 
> > of MDK before committing yourself ... my numbers will  NOT  be
> > correct for your system ! Also crosscheck on the ownership.
> > 
> > HTH
> > 
> > Bish
> >  
> > 
> > --
> > :
> > ####[ Linux One Stanza Tip (LOST) ]###########################
> >   
> > Sub : Erasing at the command prompt                  LOST #198
> > 
> > To erase a line you've written at the command prompt, use: 
> > "Ctrl u"
> > 
> > ####<[EMAIL PROTECTED]>########################################
> > :
> > 
> > _______________________________________________
> > linux-india-help mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/linux-india-help
> > 
> 
> 
> 
> _______________________________________________
> linux-india-help mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/linux-india-help
---end quoted text---



:
####[ Linux One Stanza Tip (LOST) ]###########################

Sub : Killing a Process (#3)                         LOST #150

To kill a process by name, use the killall command. To  kill a
failed fetchmail session on tty1 as an user, log  into another 
console, and issue the command "killall fetchmail". Be careful
with this command as root, since all instances of the  program
used by *all* users will be killed !!! 

####<[EMAIL PROTECTED]>####################################
:

_______________________________________________
linux-india-help mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/linux-india-help

Reply via email to