dear all:
i have some trouble with my sound card which is via82c686 and embeded
in my mainboard.
i run "sndconfig" in RedHat6.1, when it try to play a sound sample,it says:
The following error occurred running the modprope program:
/lib/modules/2.2.12-20/misc/sb.o: init_modu
Peter:
You can read /proc filesystem for that
Try info /proc for more information
Ariel Lopez
On Tue, 21 Nov 2000, Peter Pilgrim wrote:
>
>
> Hi
>
> I am considering writing a JNI to the process list.
> How do you do this in Linux/Unix?
>
> --
> Peter Pilgrim
> G.O.A.T
>
Yep that's one way.
How do you find out what process details (uid, gid, terminal id, command line,
environment variables)
are apart from just `ls /proc'
I should have said a UNIX system api call like the "mntent()" call that
exists that allows you to read UNIX mount table environment.
Is ther
Peter Pilgrim wrote:
> Hi
>
> I am considering writing a JNI to the process list.
> How do you do this in Linux/Unix?
Most such things are done on Linux using information available from the /proc
filesystem - you should be able to write a very thorough ps, just by reading from that
filesystem
Peter:
Inside /proc/ there are a couple files. Within them you find
the information that you want e.g. in cmdline you find the command that
start this process.
Check out info /proc to see a detailed description
Ariel
On Tue, 21 Nov 2000, Peter Pilgrim wrote:
>
> Yep that's one way.
>
>
Ok you've convinced me to look at `info proc' or `man proc' latter tonight.
[OT]: How on earth do they this on Solaris?
--
Peter Pilgrim
G.O.A.T
"The Greatest of All Time"
Message History
On Tue, Nov 21, 2000 at 01:21:38PM +, Peter Pilgrim wrote:
>
> Yep that's one way.
>
> How do you find out what process details (uid, gid, terminal id, command line,
>environment variables)
> are apart from just `ls /proc'
There's lots of info in the /proc man page. For example, each proce
On Tue, Nov 21, 2000 at 03:37:48PM +, Peter Pilgrim wrote:
>
> Ok you've convinced me to look at `info proc' or `man proc' latter tonight.
> [OT]: How on earth do they this on Solaris?
There's no standard solution - not surprising, given this data's tight
coupling with the kernel. Various Un
This what I thought.
I had an inquiry/ feature request about how to do this for my JavaUnix project.
Looks pretty easy on LINUX. Damn if I know how to do on Solaris tho.
You said some directories in /proc//* are in accessible, ok just try it.
I could also default to `/usr/sbin/ps -afe' or `/us
Peter Pilgrim wrote:
>
> I am considering writing a JNI to the process list.
> How do you do this in Linux/Unix?
You open files in the "/proc" filesystem. (We are going around in
circles now.)
--
Weiqi Gao
[EMAIL PROTECTED]
> "Joi" == Joi Ellis <[EMAIL PROTECTED]> writes:
Joi> On Mon, 20 Nov 2000, Joseph Shraibman wrote:
>> Nathan Meyers wrote:
>> >
>> > [EMAIL PROTECTED] wrote:
>> >
>> > > dear all
>> > >how can i get the localhost ip in java .
>> >
>> > InetAddres
On 22 Nov 2000, Juergen Kreileder wrote:
> It's not that easy. A host may have several IP addresses and other
> hosts may have to use different addresses to reach it. E.g. hosts on
> the intranet may have to use 192.168.0.100, but external machines may
> have to use 65.123.66.124.
This is true
I don't know if anyone else can verify this, but the bug listed below
seems to be BSD socket related (ie OS related)
I hacked some code together from an online example and included what
Java does on the server side , compile cc -o serv serv.c and
test with the Broadcaster client from the bug rep
> "Weiqi" == Weiqi Gao <[EMAIL PROTECTED]> writes:
Weiqi> Peter Pilgrim wrote:
>> I am considering writing a JNI to the process list.
>> How do you do this in Linux/Unix?
Weiqi> You open files in the "/proc" filesystem. (We are going around in
Weiqi> circles now.)
It ma
- Original Message -
From: "noisebrain" <[EMAIL PROTECTED]>
Sent: Monday, 13 November, 2000 6:32 PM
Subject: Re: java developer feedback
> There's been progress on this recently with caldera/turbolinux/etc.,
> but RedHat, by far the biggest linux distrib, does not include
> anything ot
On Tue, 21 Nov 2000, Joi Ellis wrote:
> On 22 Nov 2000, Juergen Kreileder wrote:
>
> > It's not that easy. A host may have several IP addresses and other
> > hosts may have to use different addresses to reach it. E.g. hosts on
> > the intranet may have to use 192.168.0.100, but external machin
16 matches
Mail list logo
