Linux-Development-Sys Digest #990, Volume #6 Sun, 25 Jul 99 00:13:49 EDT
Contents:
Re: High load average, low cpu usage when /home NFS mounted (Kelly Burkhart)
Help! Cannot set thread's priority under Linux, even not as root! ("Udo Giacomozzi")
Re: HP CD-RW Supported by RH 6.0? (Joerg Schilling)
Re: newbie question (Scott Lanning)
Re: nVidia Riva TNT Drivers ([EMAIL PROTECTED])
Kernel version 2.3.9+ (garypark)
Re: packet modification (Sami Tikka)
Riva TNT Drivers ("Ian Murphy")
Re: How to compile C++ in Linux? (Johan Kullstam)
Re: when will Linux support > 2GB file size??? ("Chad Mulligan")
Re: SCSI emulation for atapi devices (yushi)
18+ ONLY 101373 ([EMAIL PROTECTED])
Sexy Stuff 78563 ([EMAIL PROTECTED])
XXX 83496 ([EMAIL PROTECTED])
Re: HP CD-RW Supported by RH 6.0? (coffee)
Re: when will Linux support > 2GB file size??? (Graffiti)
----------------------------------------------------------------------------
Crossposted-To: comp.os.linux.misc,comp.os.linux.networking
Subject: Re: High load average, low cpu usage when /home NFS mounted
From: Kelly Burkhart <[EMAIL PROTECTED]>
Date: 23 Jul 1999 23:09:44 -0500
[EMAIL PROTECTED] (Paul Kimoto) writes:
> [posted and e-mailed]
>
> In article <[EMAIL PROTECTED]>, Ole Jacob Taraldset wrote:
> > The
> > /home partition is NFS mounted from [an?] SGI. When I take a look at cpu
> > usage i kpm/qps most of the cpu is idle (~85%), but load average reports
> > around 2. Isn't load average a function of cpu usage (only, mostly)? Can
> > it be that some process is running, but not showing in ps/top/kpm? I
> > feel that the system response has been reduced quite a bit after
> > upgrading to RedHat 6.0.
>
> The proc(5) man page says
>
> loadavg
>
> The load average numbers give the number of jobs in
> the run queue averaged over 1, 5 and 15 minutes.
>
> Processes waiting for (slow NFS) disk operations would be in the run
> queue, but not necessarily consuming much CPU.
<snip>
Really? I thought processes waiting on IO were not in the run queue;
only processes that were "ready to run". Am I completely off base?
--
Kelly R. Burkhart
[EMAIL PROTECTED]
[The litigation] industry was, of course, up and running before the
tobacco litigation, but that taught lawyers just how lucrative it
could be to blame individuals' foolishness on, say, Joe Camel.
-- George F. Will
------------------------------
From: "Udo Giacomozzi" <[EMAIL PROTECTED]>
Crossposted-To: comp.programming.threads
Subject: Help! Cannot set thread's priority under Linux, even not as root!
Date: Sat, 24 Jul 1999 18:17:28 +0200
Hi.
I've made a simple LinuxThreads test program (using FreePascal). I can
successfully create new threads but I cannot set the thread's priority. I
tried several methods (setting attribute, changing when thread already
exists, thread changes itself,..), even set explicit parameters. But it
still remains SHED_OTHER at priority 0. I know I must run the program as
'root' but it doesn't help at all. Well, that means, it helps a bit. As
normal user I get some errors when trying to change priority (as expected)
but as 'root' all functions return OK but the priority isn't affected at all
(when checking priority status).
You may say, it's a bug in the program, but someone else tried the same
program on another machine and it worked fine!?
Are there some settings that deny all priority manipulations, even in root
mode?
I'm using SuSE 5.3, Kernel 2.0.35.
On request I can send you the program.
Thank you in advance for any help!
Udo Giacomozzi
--
* http://come.to/jampy
* [EMAIL PROTECTED]
* UIN: 17745247 (@pager.mirabilis.com)
------------------------------
From: [EMAIL PROTECTED] (Joerg Schilling)
Crossposted-To: comp.os.linux.misc
Subject: Re: HP CD-RW Supported by RH 6.0?
Date: 24 Jul 1999 16:50:12 GMT
In article <[EMAIL PROTECTED]>,
David T. Blake <[EMAIL PROTECTED]> wrote:
>Jack Steen <[EMAIL PROTECTED]> wrote:
>> Does anyone know of a
>> reference to HP CD-RW support under Linux?
>
>If cdrecord does not support it, it is unsupported.
>
>However, the maintainers of cdrecord are completely insane
>when it comes to supporting everything they can get specs
>for. To their credit.
Why insane? If I get specs, the drive is usualy supported some time later.
>See
>http://www.fadden.com/cdrfaq/faq.html
>
>and
>
>http://www.fokus.gmd.de/nthp/employees/schilling/cdrecord.html
>http://www.fokus.gmd.de/research/cc/glone/employees/\
>joerg.schilling/private/cdrecord/hp.html
The second web link oints only to areported Inquiry data
and an entry in the inquiry data base does not necessarily
mean that a drive is supported.
--
EMail:[EMAIL PROTECTED] (home) J�rg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni) If you don't have iso-8859-1
[EMAIL PROTECTED] (work) chars I am J"org Schilling
URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix
------------------------------
From: [EMAIL PROTECTED] (Scott Lanning)
Subject: Re: newbie question
Date: 14 Jul 1999 01:59:33 GMT
Azhar Abu Talib ([EMAIL PROTECTED]) wrote:
: #define MODULE
: #include <linux/module.h>
:
: int init_module(void) { printk(" <1>Heelo World \n"); return; }
^
Did you leave this space in your code?
Also, why did you do return (void) rather than "return 0"?
: void cleanup_module { printk("<1>Goodbye Cruel World \n");
:
: i compile the file with gcc -c then try to insmod the module but
: somehow the print statement never came out. Can anybody tell me
: what i am doing wrong .
It worked fine for me. Did you notice the tip about why he
used <1>? That is KERN_ALERT. Otherwise, it defaults to
<6> == KERN_INFO. I wonder if you left the space, then the
kernel sees a blank as the first character in your printk(),
then it thinks level <6> and your message isn't displayed
to the console. Anyway, you shouldn't be sloppy when
programming a kernel module.
--
Scott Lanning: [EMAIL PROTECTED], http://physics.bu.edu/~slanning
"Besides a mathematical inclination, an exceptionally good mastery of
one's native tongue is the most vital asset of a competent programmer."
--Edsger Dijkstra
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: nVidia Riva TNT Drivers
Date: Sat, 24 Jul 1999 16:28:50 GMT
Ian Murphy <[EMAIL PROTECTED]> wrote:
: Does anybody know where I can get X-Windows drivers for my Creative Labs
: Graphics Blaster Riva TNT 16MB AGP Graphics Card?
from http://www.xfree86.org/ - The most recent release(s) support 128
and TNT
Jeff
--
One of the most overlooked advantages to computers is... If they do
foul up, there's no law against whacking them around a little.
-- Joe Martin
------------------------------
From: garypark <[EMAIL PROTECTED]>
Subject: Kernel version 2.3.9+
Date: Wed, 14 Jul 1999 12:09:10 +0000
I was about to ask the same dumb question that Mr. Kuznia asked when I
saw his post I decided to wait to see what the responses would be. Good
thing I did! This way I get to see another shining example of how the
open source communitiy is so supportive and helpful.:
Mr. Kuznia knew someone had to get insulted to extract this bit of
trivia. So, courageously he stood up and took the hit! Am I glad he did
otherwise it might have been me that was so mercylessly slimed for mere
ignorace.
Some people seem to mistake ignorance for stupitdy. Thats OK. Personally
my failing is that I mistake rudeness for stupidity. We all make
mistakes. Including sometimes the people who work on the inner sanctum
of the kernel. In order to correct those mistakes they sometimes have to
make changes that impact the rest of the kernel - such as the file
systems. What better way to get the changes out to the impacted parties?
While I had always understood the difference between development and
stable, I had just never realized, the obvious, that sometimes some
parts of the dev. tree don't even build. Oh yeah! duh... thats how it
gets developed.
A quick grep
[root@ufgood linux-2.3.10]# find . -name '*.[ch]' -exec grep
update_vm_cache {} \; -print
update_vm_cache(inode, *ppos, bh->b_data + (*ppos &
(SECTOR_SIZE-1)), written);
./fs/fat/file.c
update_vm_cache(inode,pos,p,c);
update_vm_cache(inode,pos,p,c);
./fs/affs/file.c
update_vm_cache(inode, pos, p, c);
./fs/qnx4/file.c
update_vm_cache(inode,pos,p,c);
./fs/hfs/file.c
update_vm_cache (p->ino, p->off, dest, len);
./fs/ntfs/fs.c
extern void update_vm_cache(struct inode *, unsigned long, const char *,
int);
shows that not only fat is effected. So the sandbox is currently a
little smaller than before.
Like many people I suppose, I eagerly await the ability to use USB and
so I am willing to risk some instabity
and though I'd give it a try. When it didn't work I shrugged and said to
myself "Guess there's some insider trick to this I don't understand."
Maybe my big mistake was taking this private boys club for a public news
group, where any question is fair,
where some people are to busy with important work to answer. They don't.
Neither do they slime.
------------------------------
From: [EMAIL PROTECTED] (Sami Tikka)
Subject: Re: packet modification
Date: Sun, 25 Jul 1999 00:24:40 +0300
On Mon, 28 Jun 1999 16:57:22 -0500, Paxton Smith <[EMAIL PROTECTED]> wrote:
>Hi experts. I'm new to the linux kernel, so I've
>got a question for someone who has played with
>IP packets. Where do you fiddle with the packet
>contents before the data goes up the IP/TCP
>stack? I'm at the end of my rope!
I guess there is no other way than biting the bullet and adding some code at
the suitable place in the Linux kernel. The following is true at least on
BSD systems, but I think it is true also for Linux:
When a network card generates an interrup, the interrupt handler reads the
packet and arranges ether_input or similar link layer function to be called.
The IP layer begins by the link layer calling a function named ip_input.
You should add your own processing either at the end of the link layer or
beginning of the IP layer.
I don't think there is any way to have e.g. a loadable module attach into
that place without recompiling the kernel with some modifications. I'd be
happy to be proven wrong.
--
Sami Tikka, [EMAIL PROTECTED], http://www.iki.fi/sti/
"One World, One Web, One Program" - Microsoft Promotional Ad
"Ein Volk, Ein Reich, Ein Fuhrer" - Adolf Hitler
------------------------------
From: "Ian Murphy" <[EMAIL PROTECTED]>
Subject: Riva TNT Drivers
Date: Mon, 19 Jul 1999 22:50:36 +0100
Does anybody know of or possess updated drivers for the Riva TNT chipset for
Linux, as I'm having trouble getting X-Windows to recognise my Creative Labs
Graphics Blaster TNT.
------------------------------
Subject: Re: How to compile C++ in Linux?
From: Johan Kullstam <[EMAIL PROTECTED]>
Date: 14 Jul 1999 19:42:46 -0400
[EMAIL PROTECTED] (John McKown) writes:
> On Tue, 13 Jul 1999 22:30:54 -0400, Ryan Michaels wrote:
> >I'm fairly new to Linux development.. most of the time I just use Perl. Is
> >making a C/C++ program in Linux similar to that of Windows (DOS) where you
> >write the program in a file, then compile it, or does Linux interpret it
> >like Perl?
> >
> >I don't mean to ask such simple questions, but I can't seem to find any
> >documentation on the system about this (if so, could you please let me
> >know?).
> >
> >T.I.A.
> >
> >Ryan
> >
>
> C is generally compiled. I know of some interpreters that ran back in the
> old DOS days. I don't know of any for Linux. Every distribution of Linux
> that I've heard of comes with a C/C++ compiler. It is the GNU compiler
> called gcc. The standard used by gcc is that file ending in a small
> "c" are C and one ending in a upper case "C" are C++. I prefer the
> way Borland's compiler did it with "c" vs "cpp". But whatever.
feed C programs to *gcc*; feed C++ programs to *g++*. i call all my
source files <something>.c.
> You'd
> create your C source code using an editor. Whatever you use for perl
> should be OK. Once you've written your code, you'd compile it using gcc.
> For really simple programs, you'd enter something like:
>
> gcc -o program program.c
and for C++, use
g++ -o program program.c
(i am sure .C &c are also valid suffixes)
--
J o h a n K u l l s t a m
[[EMAIL PROTECTED]]
Don't Fear the Penguin!
------------------------------
From: "Chad Mulligan" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.advocacy
Subject: Re: when will Linux support > 2GB file size???
Date: Sat, 24 Jul 1999 17:48:20 -0700
Colin R. Day wrote in message <[EMAIL PROTECTED]>...
>Chad Mulligan wrote:
>
>> This question is a bit off topic but it just occurred to me that: NTFS will
>> support files of these sizes, and the current Linux kernels have support for
NT.
>> Can they read and write to these files if an NTFS file system is used? I'm sure
>> that the whole file couldn't be cashed but a streaming handler should be able
to
>> parse them, shouldn't it?
>
>This may have changed, but the last time I looked, Read-Write support for
>NTFS was termed "experimental" and "dangerous". Or has this been changed?
>
>
Slackware 4 doesn't call it that. And thus far it appears to work OK, They've
even included security work arounds for ACL's. Don't have enough disk to attempt
this sort of test though.
>
>--
>Colin R. Day [EMAIL PROTECTED] alt.atheist #1500
>
>
>
------------------------------
From: yushi <[EMAIL PROTECTED]>
Subject: Re: SCSI emulation for atapi devices
Date: 25 Jul 1999 01:31:14 GMT
Marcin Romaszewicz wrote:
>
> Hi All,
>
> I have a question perhaps someone here can answer; I haven't found an
> answer in any docs.
>
> I've got an ATAPI CD-RW drive, and I am using cdrecord to burn CD's. In
order
> for this to work, I must disable atapi cd-rom support and enable the scsi
> host adapter emulation, generic scsi support, and scsi cdrom support.
>
> Now, this is all well and good, and it works, I can successfully write
CD's,
> but I can not mount CD's. To mount a CD, I either have to recompile the
kernel
> or rmmod all the scsi stuff and insmod the atapi cdrom support.
>
> Is there a way, with scsi emulation and related modules installed, to
mount
> an atapi cdrom as a scsi cdrom? When I try mounting /dev/cdrom (kernel
says
> it detected a cdrom) or /dev/sda I get a message about an unsupported
> command getting sent to hdc (where the cdrom actually lives).
>
>
> Is there another way to mount the cd while the scsi support is present?
I'm
> just looking to be able to burn a CD and mount one on the same kernel
> configuration.
>
> Any ideas?
> Thanks
>
>
>
try this .
cat /proc/devices
the result will look like this (in my case)
Character devices:
1 mem
2 pty
3 ttyp
4 ttyp
5 cua
6 lp
7 vcs
10 misc
14 sound
21 sg
81 video_capture
Block devices:
2 fd
3 ide0
8 sd
11 sr
22 ide1
look at the Block Devices
fd is for floppy disk
sd is for scsi disk (zip)
sr is for scsi-emulation atapi cdr
so try mount your cd using /dev/sr0 or /dev/sr[i] which i=1 ~ 10 .
by the way my atapi cdrw works well using scsi-emulation .
I can write and mount it easily .
BUT there is a problem .
I can't play my vcd anymore .
maybe this atapi cdr with scsi-emulation not support vcd ..
any suggestion ?
================== Posted via SearchLinux ==================
http://www.searchlinux.com
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.hardware,comp.os.linux.misc
Subject: 18+ ONLY 101373
Reply-To: [EMAIL PROTECTED]
Date: Saturday, 24 Jul 1999 18:31:50 -0600
ADULTS ONLY!
http://207.240.225.250/
X\&W_w0T
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.hardware,comp.os.linux.misc
Subject: Sexy Stuff 78563
Reply-To: [EMAIL PROTECTED]
Date: Saturday, 24 Jul 1999 18:31:54 -0600
ADULTS ONLY!
http://207.240.225.250/
^,Q"ng"?
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.hardware,comp.os.linux.misc
Subject: XXX 83496
Reply-To: [EMAIL PROTECTED]
Date: Saturday, 24 Jul 1999 18:31:52 -0600
ADULTS ONLY!
http://207.240.225.250/
52cCaIP#
------------------------------
From: coffee <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Re: HP CD-RW Supported by RH 6.0?
Date: Sat, 24 Jul 1999 22:44:49 -0400
Jack Steen wrote:
>
> I have recently upgraded to RedHat Linux 6.0 with the pre-compiled
> kernel on both my laptop and a newly constructed Pentium II desktop at
> home. The desktop machine has a Hewlett-Packard CD-RW 7200 Plus drive.
> The SW recognizes it as a CD drive, but of course I would like to be
> able to use the CD-R and perhaps the CD-RW capabilities under Linux. I
> have conducted a moderate search of the web, but have not come across
> anything saying that someone had done this. Does anyone know of a
> reference to HP CD-RW support under Linux?
I had a HP cdrw and worked fine. But I think I know what your problem
is.
If the drive is IDE then you have to go in and recompile your kernel and
turn off atapi drive and turn on scsi emulation.
Of course, If its a scsi drive and linux doesnt recognize it I would be
more inclined to check the cabling and stuff on the drive.
--
coffee at indy dot net * ICQ 1614986
Kokomo, Indiana, USA
------------------------------
From: Graffiti <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.advocacy
Subject: Re: when will Linux support > 2GB file size???
Date: 24 Jul 1999 21:00:50 -0700
In article <[EMAIL PROTECTED]>,
Philip Brown <[EMAIL PROTECTED]> wrote:
[snip]
>well, in theory, it is perfectly feasible to implement a filesystem
>WITHOUT using memory mapping. It's just not as fast.
>
>So, the possibilities I see are:
>
>a) maybe the NTFS support doesn't use memory mapping ?
Nononononono, the FILESYSTEM doesn't do memory mapping. The PROGRAMS
your run do. For example, you can mmap() a file, then use a pointer
to run around the file and access it instead of using fseek()/ftell()
and other such. This will break on 32-bit platforms that want to
access files that need more than 32-bits to represent.
Another thing mmap() is used for is shared libraries. You just get
a pointer to the location in memory where a shared library's routine
is instead of using lseek()/read() to grub around in the file.
All of a sudden, you can't do this anymore.
While people can argue that adding a 64-bit API that has to be
called directly will alleviate this problem, unless you're willing
to re-write *ALL* programs, libraries, etc. to explicitly use this
new API (and incurr a rather nasty performance hit for the "common"
case of files that will fit in a 32-bit representation of size),
you can use the new API only in extremely limited circumstances.
have to religiously find ways to keep the 32-bit and 64-bit areas
from interacting, and find a way to "synchronize" them, whatever
that may entail (i.e. keep your buffer cache coherent, etc.).
Of course, this means you break binary compatability all over the
place and have to emulate things like mmap() with code that will
slow it down by quite a bit (speed is one reason mmap() is used over
lseek()/read()).
>b) make an inhouse tweaked ext2 driver that uses simple buffer-to-buffer
> coping instead of memory mapping.
Ext2 can handle 64-bit files. ext2fs does not have to be changed. Even
on 32-bit platforms. Changing ext2fs will not give you 64-bit files on
32-bit systems. ext2fs on 32-bit platforms is the same as ext2fs on
64-bit systems.
-- DN
------------------------------
** 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
******************************
