That should show a character device. If it is the same on both systems, then you would just need to cd /dev and recreate the symbolic link instead of the current file called /dev/null.
This User Gave Thanks to Scrutinizer For This Post:
I'm a newbie to the Unix world Help!
I have to maintain a host of Sybase database servers sitting on Unix Sun Solaris 8...I've been tasked with finding/creating a way to auto start/stop Unix via unix commands, specifically when the Unix servers need to be restarted we want Sybase to start... (2 Replies)
Hi...all
database - 10g Rs 2 with ASM
platform - Sun Solaris V890 64bit
This is the step i use to auto start the database n ASM: (auto start can start but need to kill lsvcrun first)
1 dbora---script
2 start_shutdown_asm.ksh---script
3. Dbora file must be put under /etc/init.d directory... (0 Replies)
i have two separate scripts that work nicely to curl and generate two files.. one html and one txt so a total of four.
When the script starts up i want it to:
call and run shellscripta
call and run shellscriptb
sleep for about 40 seconds
again run shellscripta
again run shellscriptb
check... (4 Replies)
Hi All,
I would like to develop a shell script for stop & start an application server (1-4) on Solaris box. Here are the user requirements for this task.
1. User will input the option which server they wish to stop.
2. Will clear cache files from specific location.
3. ... (1 Reply)
Hello All,
I am completely new to shell scripting. I had to write a script that starts and stop the queue manager in Websphere MQ. We are on Linux 64-bit patform.
The script should stop the queue manager and all the processes related to websphere MQ. It should be a clean stop. Once the queue... (3 Replies)
Hi,
I need to create a shell script for automated server patching, with the following scenario:
I have two Linux servers Primary and secondary.
Server patching should start on Primary 1st and then secondary.
1st check both servers are up and running.
Then stop primary and patching will... (1 Reply)
Discussion started by: rcroyal88
1 Replies
LEARN ABOUT DEBIAN
dsp
7(16 December 2012) 7(16 December 2012)
NAME
dsp - Open Sound System audio devices
DESCRIPTION
/dev/dsp is the default audio device in the system. It's connected to the main speakers and the primary recording source (such as micro-
phone). The system administrator can set /dev/dsp to be a symbolic link to the desired default device. The ossinfo utility can be used to
list the available audio devices in the system.
/dev/dsp_mmap, /dev/dsp_ac3, /dev/dsp_multich and /dev/dsp_spdifout are default audio devices for specific applications such as games or
media (DVD) players.
DIRECT ACCESS AUDIO DEVICE FILES
OSS 4.0 (and later) will create audio devices under /dev/oss/<device> directory. For example /dev/oss/sblive0/pcm0 is the first audio
device that belongs to the first Sound Blaster Live! or Audigy card in the system. These direct devices are used when an application needs
to access specific audio device (instead of the default one).
You can use the ossinfo(1) utility with the -a option to get a list of the available audio devices in the system.
LEGACY AUDIO DEVICE FILES
Traditionally OSS has created device files like /dev/dsp0 to /dev/dspN for each audio device in the system. OSS 4.0 still supports this
legacy naming. These files are symbolic links to the actual device files located under /dev/oss. The ossdevlinks(8) utility is used to
manage these links and it will be automatically invoked when OSS is started.
COMPATIBILITY
o The /dev/dsp (default() audio device file will be supported by all OSS implementations and versions.
o The special purpose audio default devices (such as /dev/dsp_mmap) are only supported by OSS 4.0 and later.
o The legacy audio device files (such as /dev/dsp1) are supported by all OSS versions and implementations.
o New style audio device files (under /dev/oss) are only supported by OSS 4.0 and later. However some independent OSS implementations may
only support the legacy naming even they are otherwise OSS 4.0 compatible.
o /dev/dsp0 doesn't exist in all Linux systems which use /dev/dsp for the same purpose. In such systems /dev/dsp points to the first audio
device and /dev/dsp1 to the second.
PROGRAMMING INFORMATION
See the Audio Programming section of the OSS Programmer's Guide (DSP(2)) for more info.
OPTIONS
None
FILES
o /dev/dsp
Default audio device
o /dev/dsp_mmap
Default audio device for applications using mmap(2)
o /dev/dsp_ac3
Default audio device for applications sending Dolby Digital (AC3) audio to an external receiver.
o /dev/dsp_multich
Default multichannel (4.0-7.1) audio output device
o /dev/dsp_spdifout
Default digital audio (S/PDIF) output device
o /dev/oss/<driver>/pcmN
Direct access device files for individual audio devices.
o /dev/dsp0 to /dev/dspN
Legacy style direct access audio device files.
AUTHOR
4Front Technologies
OSS Devices 7(16 December 2012)