Linux-Development-Sys Digest #320, Volume #6     Sat, 23 Jan 99 09:13:50 EST

Contents:
  Re: BeOS and Linux (Arthur Chiu)
  source code. (dvoils)
  Re: kernel: VFS: No free inodes - contact Linus (Ingo Saitz)
  Re: How do apps access time_t?  (Y2K+38 expiry question.) (TGAPE!)
  Configuring system to have multiple ethernet addresses (Amey Laud)
  Re: Why I'm dumping Linux, going back to Windblows (Jay)
  Re: How to tell current kernel config? (J.M. Paden)
  Re: Changing Ethernet address (Phil Howard)
  Re: Linux Sound Engine (Peter Steiner)
  Re: How can I build a Linux system from scratch - NO distribution? (Brady Montz)
  Re: Kernel v2.2 (Talon Karrde)
  Re: pre7 and 3dfx/glide/Mesa (gpasa)
  Re: pre7 and 3dfx/glide/Mesa -- here's the sysmessages (gpasa)
  Direct Sound? ("Dr. Unk")

----------------------------------------------------------------------------

From: Arthur Chiu <[EMAIL PROTECTED]>
Subject: Re: BeOS and Linux
Date: Sat, 23 Jan 1999 10:52:33 +0800

Do you mean setting up a cross-platform source level standard?


------------------------------

From: dvoils <[EMAIL PROTECTED]>
Subject: source code.
Date: Thu, 21 Jan 1999 11:20:54 -0800

I am using debian linux. Does anyone know where the kernel source code
is? How about the code for all the drivers?

Thanks,
Danny


------------------------------

From: Ingo Saitz <[EMAIL PROTECTED]>
Subject: Re: kernel: VFS: No free inodes - contact Linus
Date: Thu, 21 Jan 1999 20:40:57 +0100

MoiN

On Thu, 21 Jan 1999, Matt Corddry wrote:

> Well... the subject really explains my problem. I get hundreds of
> thousands of these at console and in /var/log/messages.

It seems your filesystem has gone out of inodes. This can happen if you
use to have a lot of small files in one partition. The solution is to find
the dirs which contain many small files (usually /tmp or under /var) and
increase the inodes in that partition. ext2fs defaults to one inode per
4096 bytes of drive space. So you sould use "mkfs.ext2 -i 2048" or even
"mkfs.ext2 -i 1024" on that partition *back up your data first!*

    Ingo
--
Starting Java...


------------------------------

From: [EMAIL PROTECTED] (TGAPE!)
Subject: Re: How do apps access time_t?  (Y2K+38 expiry question.)
Date: Thu, 21 Jan 1999 20:32:56 GMT

In article <786k1g$1o2$[EMAIL PROTECTED]>,
Bloody Viking  <[EMAIL PROTECTED]> wrote:
>
>I'm curious, how do UNIX apps access time_t to get the date? I'm curious
>about this in relation to the Y2K+38 expiry of time_t and I'd like to try
>my hand at remediation. I've got 40 years to figure it out! :) Are there
>any Linux time_t remediation packages? 

A long time ago in a linux kernel far obsolete, there was
nanotimer-0.1.1.tar.gz.  This patch supposedly increased the resolution
of the Linux timer, decreased the overhead, and put off Y2K+38 by a
thousand years as a side-effect.  By the time I got around to looking at
it, my Jaz drive failed, losing me all of /usr/src.  One side-effect of
applying the patch is that everything that uses time() needs to be
re-compiled before it will work, and they all have to use time_t, not
int or long for their time return type.

There probably have been other remediation packages.

Ed Grimm

------------------------------

From: Amey Laud <[EMAIL PROTECTED]>
Crossposted-To: 
comp.dcom.lans.ethernet,comp.os.linux.networking,comp.os.ms-windows.programmer.networks,comp.os.ms-windows.programmer.nt.kernel-mode,comp.protocols.tcp-ip
Subject: Configuring system to have multiple ethernet addresses
Date: Sat, 23 Jan 1999 13:18:55 +0800

I am building a distributed number crunching system, in which a lot of
data needs to be moved between machines.
In order to streamline the process and avoid bottlenecks due to
network/IO latencies, I am considering
using separate networks to handle the input and the output, that is,
each system reads from a different physical network
and writes into a different physical network. This would mean that each
machine have two IP addresses
that are configured on separate ethernet cards and can be addressed and
used explicitly.
1. Is such an arrangement possible? (That is, OS and IP support)
2. Are there existing examples of such a setup?
3. The arrangement might involve heterogenous platforms.
     I am interested specifically on the possibility of such a setup on
NT/Linux running on Intel (Xeon)/Alpha.

4. Are there existing message passing API's (such as MPI) based on
TCP/IP that support such a configuration.

I would glad to get any suggestions in this regard.

Amey Laud.

[EMAIL PROTECTED]

Research Engineer,
Centre for Signal Processing,
Singapore 639798





------------------------------

From: Jay <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,comp.os.linux.development.apps,comp.os.linux.setup
Subject: Re: Why I'm dumping Linux, going back to Windblows
Date: Sat, 23 Jan 1999 00:04:18 -0500

 After spending the 10-12 years doing DOS, WIN3x, WINNT3.5-4.0 (and
everything inbetween), I can understanding your feelings.
But, I have been very pleased with what I have read. (Books & the
bookstore. What a wonderful idea!)
I don't have RedHat running yet (waiting for some parts), but am looking
forward to it.

The only things I haven't found out (maybe someone can help):
  - The maximum size of a C program and the maximum memory addressable by
said program (Like DOS was 640K unless DPMI was involved.)
 - A *GOOD* XWindows book. I'd like to take a 5-year old DOS-DPMI
application from DOS+TCXL to Linux+Xwindows.



Stuart Harris wrote:

> DadKind wrote:
>
> > I only have five days experience with Linux (RH 5.1), and so far it
> > has not been fun! It has been a tough time getting the info that I'm
> > looking for, since I don't even know what I don't know (I see all
> > these posts about recompiling the kernel and I am about freaking!). A
> > graphical interface for finding files, getting help, might seem
> > unimportant to you,
>
> type the following as root..
>
> pico /bin/findfile
>
> paste this into the window pico is in!
>
> #!/bin/bash
>
> if [ $0 == "" ];
> then
>  echo "usage: $0 filename"
> else
> find / -name "$1" -print
> fi
>
> then CTRL + X save it.. bla bla
>
> then type chmod u+rwx,go+rx-w /bin/findfile
>
> (your easy way to find a file..)
>
> Linux/unix isn't that bad.. its like (sortof and don't flame me)
> dos but more useful :)
> soon as you learn the basics you'll never wanna use windows again.
>
> >but for someone like me who's spent the last ten
> > years running WindowsXX, a graphical help system is just a friendly
>
> man pages are MUCH MUCH MUCH MUCH more usefull than window .hlp files
> type man bash for instance
> bet windows help doesent tell you so  much about command.com!
>
> > face in the crowd. I figure that this is just part of learning Linux.
> > Not fun, but part of learning. After all I didn't learn C in a day!
> >
> > And the generic WindowsXX Find box will allow you to do full text
> > searches in executable dialogs, since the text string is part of the
> > RC portion of the EXE or DLL. Unless I misunderstood what you were
> > saying....
> >
> > -tomas (Anyone recommend a good Linux book?)
> > Tomas Vera
> > [EMAIL PROTECTED]
>
> --
> +--------------------------------------------       +
> | Stuart Harris / Unix Sysadmin/Dial Support        .
> .  (M) [EMAIL PROTECTED] / (T) 01494 751882
>      (F) 01494 443374 / (W) http://www.red.net      .
> .      for pgp finger / [EMAIL PROTECTED]     |
> +       --------------------------------------------+




------------------------------

From: [EMAIL PROTECTED] (J.M. Paden)
Subject: Re: How to tell current kernel config?
Date: Thu, 21 Jan 1999 15:06:26 GMT

"Tim Underwood" <[EMAIL PROTECTED]> wrote:

>I want to recompile the kernel, but want to keep the same options as are
>currently set in the kernel I am using now (RH 5.2 install).  How can I tell
>what options the current kernel has been compiled with?
>
>
Make a copy of the current kernel ".config" file located in
                usr/src/linux/.  Note this is a "dotfile" or one that 
                begins with a period.  You should copy this file
                 because a later        step of "make mrproper" will
                 delete this ".config" file.

                There are two ways to do this:

                A.      cd /usr/src/linux
                        ls -a
                                #This shows files that begin with ".".
                        cp .config /dose/linux/backup
                                #Note the "backup" directory already
                                 exists on my file system, otherwise
                                 create it.
                B.      If you wish to use your old .config file to
                        configure your new kernel,a second and
                        possibly better way to do this is:

                        cd /usr/src/linux
                        cp .config /usr/src/linux/arch/i386/defconfig

                        One of the newsgroups had a posting that said
                         this method would create a default .config
                         file which would be used when you build a new
                         kernel.  I have not tried it so can not vouch

                         for it.
Regards,
[EMAIL PROTECTED]
 "The last temptation is the greatest treason: 
  To do the right deed for the wrong reason." 
  --T.S. Eliot  

------------------------------

From: [EMAIL PROTECTED] (Phil Howard)
Subject: Re: Changing Ethernet address
Date: Sat, 23 Jan 1999 07:29:41 GMT

On Fri, 22 Jan 1999 07:02:50 GMT [EMAIL PROTECTED] wrote:

| Hello! I am of the opinion that when the kernel boots up it uses an attach
| function to read the hardware address from the card interface(ethernet)and
| stores it in arpcom data structure(Ref Richard stevens Vol 2).If it is
| possible to hardcode the hardware address in that function and recompile the
| kernel what effects it shall have on kernel<->card interaction.Thus is it
| possible that i send packets on the network with a specific hardware address.

I'm not sure which address you mean, but I suspect you might mean the
ethernet address itself (often called NIC address).  Ethernet work with
it's own set of addresses that are 48-bits in size and every piece of
hardware has a unique address built in.  As long as you are using TCP/IP
you don't need to worry about this address.  You can you IP addresses
alone.  A built in part of the TCP/IP code (call ARP ... type the command
"arp -n" to see it's status) takes care of this and you do not need to
deal with ethernet addresses at all.  No recompile is needed unless you
need to add a kernel driver you do not now have.

--
 --    *-----------------------------*      Phil Howard KA9WGN       *    --
  --   | Inturnet, Inc.              | Director of Internet Services |   --
   --  | Business Internet Solutions |       eng at intur.net        |  --
    -- *-----------------------------*      philh at intur.net       * --

------------------------------

From: [EMAIL PROTECTED] (Peter Steiner)
Subject: Re: Linux Sound Engine
Date: 21 Jan 1999 23:42:59 +0100

In article <782tjf$5cg$[EMAIL PROTECTED]>, Bjorn Wesen wrote:

>One reason you get bad performance with power-hungry kernel drivers is
>because kernel-mode code isn't pre-empted.

The mixer mustn't be pre-empted anyway. This is realtime stuff. It has
to run in realtime priority. And it should be called about at 100-200
times per second to minimize latency. I expect the mixer will need
about 0.5%-3% CPU load per active /dev/leaf on a P100 with 44.1kHz
stereo. So that really shouldn't hurt to much.

>The kernel is absolutely no place for such a mixer, really.

It would be really good to have the mixer in user-space, yes. However,
you will not get performance or "smooth" advantages. And I really don't
want high latency.

>It can be done almost totally in user-mode. You just write a kernel device
>which pipes data from /dev/leaf into for example /dev/leaf0-9 depending on
>how many processes have opened /dev/leaf.

Can you really handle all that ioctl() and mmap features?

>The kernel-mode code required for that wouldn't be much and isn't difficult
>to write.

Great, the mixer itself isn't difficult either.

Ciao,

Peter
-- 
   _   x    ___
  / \_/_\_ /,--'  [EMAIL PROTECTED] (Peter Steiner)
  \/>'~~~~//
    \_____/   signature V0.2 alpha

------------------------------

From: Brady Montz <[EMAIL PROTECTED]>
Subject: Re: How can I build a Linux system from scratch - NO distribution?
Date: 21 Jan 1999 12:41:30 -0700

[EMAIL PROTECTED] (Rick Walker) writes:

> Thomas T. Veldhouse ([EMAIL PROTECTED]) wrote:
> : I would like to build a Linux system from scratch, without using a premade
> : distribution as a starting point.  I don't know exactly where to begin.
> 
> Get a copy of Tom's root/boot distribution.  It is a complete Linux
> system on a single (ultra-high density) floppy.  All the issues that you
> need to build a minimalist system are addressed there.  The
> distribution, tomsrtbt-1.7.102.tar.gz, has scripts to build Tom's
> minimalist system from a running Linux installation.  I believe that
> you can also recursively build the system under Tom's alone.
> 
> That should get you started.
> --
> Rick Walker

URL is: http://www.toms.net/rb/

-- 
 Brady Montz
 [EMAIL PROTECTED]

------------------------------

From: Talon Karrde <[EMAIL PROTECTED]>
Subject: Re: Kernel v2.2
Date: Sat, 16 Jan 1999 14:01:41 GMT

> Where did you get the modules package to compile 2.1.132?Did you find a newer
> modules package in debian somewhere?
> I need the "-k" option of genksyms in the modules package.
> With modules-2.0.0 (in sunsite & tst-11 mirrors), i can't even compile the
> kernel.

Go to http://www.kernel.org/ (or is it kernels.org, try both :-) and get the
2.1.132 tgz file. Kernel.org is the master distribution point (i think), the
source there compiles fine on Debian 2.0 (hamm), and I'm using a frozen release!
I don't know about the modules package, but it should be available there too.


------------------------------

From: gpasa <[EMAIL PROTECTED]>
Subject: Re: pre7 and 3dfx/glide/Mesa
Date: Sat, 23 Jan 1999 14:05:33 +0100

OK, I've built pre9 with SysRq support and I storded the messages and
the SysRq "t" with it when glquake hanged. So the system didn't hanged
right ? but I'm still unable to quit the glquake screen.
I can though SysRq "k" but it doesn't  change the problem.

 Any further clue ?
> 
> Try compiling with ALT-SysRq support in the kernel.
> 
> alt-sysrq-u umount to read-only (all mounted filesystems incl. /)
> alt-sysrq-s to sync the fs
> alt-sysrq-b to (re)boot the system
> 
> in that order. If it works, you avoided any fs damage, and you know
> the kernel isn't hung (which is valuable information for debugging)

-- 
Sincerely yours,
                                Pasa Guglielmo
==================================================================
� homepage: http://www.omedia.ch/pages/gpasa/                    �
�----------------------------------------------------------------�
� e-mail  : [EMAIL PROTECTED]       �  tel. :  +41 (0)24 485 50 40 �
� mailing : Pasa Guglielmo        �  fax  :  +41 (0)24 485 50 44 �
�           Rte des Cases 17A     �                              �      
�        CH-1890 St-Maurice       �  prof.: physicist            �      
�           (Switzerland)         �                              �      
==================================================================
. 

------------------------------

From: gpasa <[EMAIL PROTECTED]>
Subject: Re: pre7 and 3dfx/glide/Mesa -- here's the sysmessages
Date: Sat, 23 Jan 1999 14:13:13 +0100

This is a multi-part message in MIME format.
==============E1425C6C9602C2D06D3A4DE5
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

gpasa wrote:
> 
> OK, I've built pre9 with SysRq support and I storded the messages and
> the SysRq "t" with it when glquake hanged. So the system didn't hanged
> right ? but I'm still unable to quit the glquake screen.
> I can though SysRq "k" but it doesn't  change the problem.
> 
>  Any further clue ?
> >
> > Try compiling with ALT-SysRq support in the kernel.
> >
> > alt-sysrq-u umount to read-only (all mounted filesystems incl. /)
> > alt-sysrq-s to sync the fs
> > alt-sysrq-b to (re)boot the system
> >
> > in that order. If it works, you avoided any fs damage, and you know
> > the kernel isn't hung (which is valuable information for debugging)
> 
> --
> Sincerely yours,
>                                 Pasa Guglielmo
> ------------------------------------------------------------------
> � homepage: http://www.omedia.ch/pages/gpasa/                    �
> �----------------------------------------------------------------�
> � e-mail  : [EMAIL PROTECTED]       �  tel. :  +41 (0)24 485 50 40 �
> � mailing : Pasa Guglielmo        �  fax  :  +41 (0)24 485 50 44 �
> �           Rte des Cases 17A     �                              �
> �        CH-1890 St-Maurice       �  prof.: physicist            �
> �           (Switzerland)         �                              �
> ------------------------------------------------------------------
> .

-- 
Sincerely yours,
                                Pasa Guglielmo
==================================================================
� homepage: http://www.omedia.ch/pages/gpasa/                    �
�----------------------------------------------------------------�
� e-mail  : [EMAIL PROTECTED]       �  tel. :  +41 (0)24 485 50 40 �
� mailing : Pasa Guglielmo        �  fax  :  +41 (0)24 485 50 44 �
�           Rte des Cases 17A     �                              �      
�        CH-1890 St-Maurice       �  prof.: physicist            �      
�           (Switzerland)         �                              �      
==================================================================
. 
==============E1425C6C9602C2D06D3A4DE5
Content-Type: text/plain; charset=us-ascii;
 name="syslog.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="syslog.txt"

Linux version 2.2.0-final (root@niptailaq) (gcc version 2.7.2.3) #3 Sat Jan 23 
13:18:31 CET 1999
Detected 299384350 Hz processor.
Console: colour VGA+ 80x34
Calibrating delay loop... 598.02 BogoMIPS
Memory: 128148k/131072k available (936k kernel code, 408k reserved, 1528k data, 52k 
init)
VFS: Diskquotas version dquot_6.4.0 initialized
CPU: AMD AMD-K6(tm) 3D processor stepping 00
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
PCI: PCI BIOS revision 2.10 entry at 0xf0510
PCI: Using configuration type 1
PCI: Probing PCI hardware
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
Initializing RT netlink socket
Starting kswapd v 1.5 
parport0: PC-style at 0x378 [SPP]
Serial driver version 4.27 with no serial options enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
pty: 256 Unix98 ptys configured
lp0: using parport0 (polling).
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.9)
PIIX4: IDE controller on PCI bus 00 dev 09
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdc:DMA, hdd:pio
hda: IBM-DHEA-36480, ATA DISK drive
hdc: FX320S, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: IBM-DHEA-36480, 6197MB w/476kB Cache, CHS=790/255/63, UDMA
hdc: ATAPI 32X CD-ROM drive, 256kB Cache
Uniform CDROM driver Revision: 2.52
Floppy drive(s): fd0 is 1.44M, fd1 is 1.44M
FDC 0 is a post-1991 82077
(scsi0) <Adaptec AHA-394X Ultra SCSI host adapter> found at PCI 4/0
(scsi0) Wide Channel A, SCSI ID=7, 16/255 SCBs
(scsi0) Warning - detected auto-termination
(scsi0) Please verify driver detected settings are correct.
(scsi0) If not, then please properly set the device termination
(scsi0) in the Adaptec SCSI BIOS by hitting CTRL-A when prompted
(scsi0) during machine bootup.
(scsi0) Cables present (Int-50 NO, Int-68 YES, Ext-68 NO)
(scsi0) Downloading sequencer code... 419 instructions downloaded
(scsi1) <Adaptec AHA-394X Ultra SCSI host adapter> found at PCI 5/0
(scsi1) Wide Channel B, SCSI ID=7, 16/255 SCBs
(scsi1) Warning - detected auto-termination
(scsi1) Please verify driver detected settings are correct.
(scsi1) If not, then please properly set the device termination
(scsi1) in the Adaptec SCSI BIOS by hitting CTRL-A when prompted
(scsi1) during machine bootup.
(scsi1) Cables present (Int-50 NO, Int-68 NO, Ext-68 NO)
(scsi1) Downloading sequencer code... 419 instructions downloaded
scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.10/3.2.4
       <Adaptec AHA-394X Ultra SCSI host adapter>
scsi1 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.10/3.2.4
       <Adaptec AHA-394X Ultra SCSI host adapter>
scsi : 2 hosts.
  Vendor: IBM       Model: DCAS-34330W       Rev: S65A
  Type:   Direct-Access                      ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
(scsi0:0:0:0) Synchronous at 40.0 Mbyte/sec, offset 8.
scsi : detected 1 SCSI disk total.
SCSI device sda: hdwr sector= 512 bytes. Sectors= 8467200 [4134 MB] [4.1 GB]
Partition check:
 sda: sda1 < sda5 sda6 > sda2
 hda: hda1 hda2 < hda5 hda6 >
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 52k freed
Adding Swap: 40124k swap-space (priority -1)
VFS: Disk change detected on device ide1(22,0)
ISO 9660 Extensions: Microsoft Joliet Level 3
ISOFS: changing to secondary root
CSLIP: code copyright 1989 Regents of the University of California
ISDN subsystem Rev: 1.55/1.47/1.55/1.33/1.10/1.2 loaded
HiSax: Driver for Siemens chip set ISDN cards
HiSax: Version 2.8
HiSax: Revisions 2.18/2.7/2.5/2.13/2.7
HiSax: Total 1 card defined
HiSax: Card 1 Protocol EDSS1 Id=Asus (0)
HiSax: Asuscom ISDNLink driver Rev. 1.2
ISDNLink: defined at 0x108 IRQ 11
ISDNLink: resetting card
ISDNLink: ISAC version : 2086/2186 V1.1
ISDNLink: HSCX version A: V2.1  B: V2.1
ISDNLink: IRQ 11 count 0
ISDNLink: IRQ 11 count 3
HiSax: DSS1 Rev. 2.7
HiSax: 2 channels added
HiSax: module installed
HiSax: debugging flags card 1 set to 4
isdn: Verbose-Level is 3
eth0: 3c509 at 0x300 tag 1, BNC port, address  00 60 97 62 a3 6c, IRQ 9.
3c509.c:1.12 6/4/97 [EMAIL PROTECTED]
eth0: Setting Rx mode to 1 addresses.
SysRq: Log level set to 9
Jan 23 13:48:00 niptailaq PAM_pwdb[480]: (login) session opened for user root by 
(uid=0)
Jan 23 13:48:00 niptailaq login[480]: ROOT LOGIN ON tty1
Jan 23 13:48:00 niptailaq PAM_pwdb[480]: (login) session closed for user root
Jan 23 13:50:09 niptailaq kernel: SysRq: Log level set to 9
Jan 23 13:50:38 niptailaq PAM_pwdb[481]: (login) session opened for user root by 
(uid=0)
Jan 23 13:50:38 niptailaq login[481]: ROOT LOGIN ON tty2
Jan 23 13:50:38 niptailaq PAM_pwdb[481]: (login) session closed for user root
Jan 23 13:50:51 niptailaq PAM_pwdb[483]: (login) session opened for user root by 
(uid=0)
Jan 23 13:50:52 niptailaq login[483]: ROOT LOGIN ON tty4
Jan 23 13:50:52 niptailaq PAM_pwdb[483]: (login) session closed for user root
Jan 23 13:52:29 niptailaq kernel: SysRq: Show State
Jan 23 13:52:29 niptailaq kernel: 
Jan 23 13:52:29 niptailaq kernel:                          free                        
sibling
Jan 23 13:52:29 niptailaq kernel:   task             PC    stack   pid father child 
younger older
Jan 23 13:52:29 niptailaq kernel: init       1 S C0202000  3124     1      0   487     
   
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: kflushd    2 S C0202000  7108     2      1           
  3
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: kswapd     3 S C0202000  6812     3      1           
 70     2
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 ffffffffffffffff : X
Jan 23 13:52:29 niptailaq kernel: kerneld    8 S C0202000     0    70      1           
 80     3
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: isdnlog    7 S C0202000     0    80      1           
295    70
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: portmap   10 S C0202000  3124   295      1           
309    80
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: inetd      9 S C0202000  5596   309      1           
320   295
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: syslogd   12 S C0202000    12   320      1           
329   309
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: klogd     11 R C0202000  5596   329      1           
340   320
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: named     14 S C0202000  5644   340      1           
351   329
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: lpd       13 S C0202000     0   351      1           
363   340
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: rpc.mountd  16 S C0202000  5644   363      1         
  376   351
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: rpc.nfsd  18 S C0202000  5148   376      1           
387   363
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: dhcpd     17 S C0202000  5644   387      1           
403   376
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: sendmail  19 S C0202000     0   403      1           
415   387
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: gpm       21 S C0202000   836   415      1           
420   403
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: postmaster   5 S C0202000  5344   420      1         
  478   415
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: efax       4 S C0202000  5596   478      1           
480   420
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: bash       6 S C0202000  5508   480      1           
481   478
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: bash      20 S C0202000  5596   481      1   577     
482   480
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000010000 : X
Jan 23 13:52:29 niptailaq kernel: mingetty  22 S C0202000     0   482      1           
483   481
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: bash      24 S C0202000     0   483      1   576     
484   482
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000010000 : X
Jan 23 13:52:29 niptailaq kernel: mingetty  23 S C0202000  1464   484      1           
485   483
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: mingetty  25 S C0202000   736   485      1           
487   484
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: update    27 S C0202000     8   487      1           
      485
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: tail      15 S C0202000  4940   576    483           
   
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:52:29 niptailaq kernel: glquake   26 S C0202000     0   577    481           
   
Jan 23 13:52:29 niptailaq kernel:    sig: 0 0000000000000000 0000000000000000 : X
Jan 23 13:53:03 niptailaq kernel: SysRq: Emergency Sync
Jan 23 13:53:03 niptailaq kernel: Syncing device 08:02 ... OK
Jan 23 13:53:03 niptailaq kernel: Syncing device 03:05 ... OK
Jan 23 13:53:03 niptailaq kernel: Syncing device 16:00 ... OK
Jan 23 13:53:03 niptailaq kernel: Syncing device 03:01 ... OK
Jan 23 13:53:03 niptailaq kernel: Syncing device 03:06 ... OK
Jan 23 13:53:03 niptailaq kernel: Syncing device 08:06 ... OK
Jan 23 13:53:03 niptailaq kernel: Done.
Jan 23 13:53:04 niptailaq kernel: SysRq: Emergency Sync
Jan 23 13:53:04 niptailaq kernel: Syncing device 08:02 ... OK
Jan 23 13:53:04 niptailaq kernel: Syncing device 03:05 ... OK
Jan 23 13:53:04 niptailaq kernel: Syncing device 16:00 ... OK
Jan 23 13:53:04 niptailaq kernel: Syncing device 03:01 ... OK
Jan 23 13:53:04 niptailaq kernel: Syncing device 03:06 ... OK
Jan 23 13:53:04 niptailaq kernel: Syncing device 08:06 ... OK
Jan 23 13:53:04 niptailaq kernel: Done.

==============E1425C6C9602C2D06D3A4DE5==


------------------------------

From: "Dr. Unk" <[EMAIL PROTECTED]>
Subject: Direct Sound?
Date: Sat, 23 Jan 1999 05:15:07 -0800

I was wondering if there was any such drivers for sound, like the ones
used in Windows.  I would like to be able to play multiple sounds with
out getting an error like, "Device or Resource Busy."  Is there any
place I can go to get these drivers, or get pointers in making them?

Thanks.


------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: [EMAIL PROTECTED]

You can send mail to the entire list (and comp.os.linux.development.system) via:

    Internet: [EMAIL PROTECTED]

Linux may be obtained via one of these FTP sites:
    ftp.funet.fi                                pub/Linux
    tsx-11.mit.edu                              pub/linux
    sunsite.unc.edu                             pub/Linux

End of Linux-Development-System Digest
******************************

Reply via email to