Linux-Development-Sys Digest #963, Volume #6 Thu, 15 Jul 99 07:13:53 EDT
Contents:
Re: Kernel version 2.3.9+ ("Zachary Kuznia")
One thing Windows has over Linux. (Zach Brown)
Re: Kernel version 2.3.9+ (garypark)
strange debugging line ("D. Stimits")
Re: One thing Windows has over Linux. ("Thomas Steffen")
Re: strange debugging line (Mark Hamstra)
Re: strange debugging line (Mark Tranchant)
Re: Project problem - linux printer port (Peter Allen)
Re: strange debugging line (Joe Pfeiffer)
Re: Help - Deleted /var/log/* from RedHat 5.2 system! ("Oliver D. Bedford")
Re: Unix queues IPC? ([EMAIL PROTECTED])
How can i increase block device buffer cache?
Re: Scheduling issue (Tero A Kauppinen)
Scheduling issue (Tero A Kauppinen)
----------------------------------------------------------------------------
From: "Zachary Kuznia" <[EMAIL PROTECTED]>
Subject: Re: Kernel version 2.3.9+
Date: Wed, 14 Jul 1999 23:10:14 -0400
>
>This is a public newsgroup, but not any question is fair. I have seen
>newsgroups who chose a policy of anything goes. They are now useless,
>and many have died (a dead newsgroup is a sad thing to look at).
>
>It is accepted that development kernels are not discussed unless you
>read the release details and known problems found in other places like
>kernelnotes.org and the linux-kernel mailing list (archived at
>www.progressive-comp.com/Lists). Both colds and linux-kernel are high
>bandwidth, and if linux-kernel were to be allowed to come here too,
>colds would die.
>
>Yes, this was a rude thread, but it is necessary. This is the
>free-software world, feelings don't matter, code and useful discussion
>does. I have been insulted because of my earlier stupid questions, and I
>was upset when it happened, but now I am more experienced and I see it
>was useful. You'll thank us one day ;)
>
>--
>Tristan Wibberley
If this is the Linux system developement newsgroup, and one cannot discuss
developement kernels, then where does one go to discuss developement
kernels? I am reletively new to this, and I was merely looking for the
proper newsgroup or web site to learn more about the nature of my problem.
As the kernel open source, I wished to help to address the problem, or find
the solution if someone had already developed it. I came here as I assumed
that the kernel was part of the system. I understand now that my question
had already appears to have been known and documented, which was what I
sought to learn. However, you seem to be implying that such a question
should not be asked even if the problem has not been probed or even
discovered before. So, again I state my question. In which newsgroup does
one discuss developemental kernels?
Zachary Kuznia
[EMAIL PROTECTED]
------------------------------
From: Zach Brown <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.x,redhat.config
Subject: One thing Windows has over Linux.
Date: 15 Jul 1999 03:31:02 GMT
Any help would be greatly appreciated. No FAQ or newsgroup has the
answer to this one so far. Need help with multiple layouts under X using
Gnome and Enlightenment, and in a command prompt using Redhat 6.0 with a
bash shell. I have many users using the same workstation and would like to
setup the ability to change keyboard layouts by pushing Ctrl + Shift at
anytime (like MS Windows). This means when they get a login prompt they
could press Ctrl + Shift to cycle through keyboard layouts. Is this
possible?
The current solution is to alias loadkeys and xmodmap to commands that use
letters that are the same in the different layouts (i.e. "a" and "m" and
the number keys are the same in Qwerty and in Dvorak). This becomes
tedious because a user can log out and another sits down to use the system
only to find that their username "phil" comes out on the screen "ldcn".
Another possible solution would be to set the keyboard layout to qwerty
every time someone logs out. Then they could look at the keyboard (which
is in qwerty) to login. Is this possible? E-mail would be greatly
appreciated on the subject.
Zach Brown
[EMAIL PROTECTED]
================== Posted via SearchLinux ==================
http://www.searchlinux.com
------------------------------
From: garypark <[EMAIL PROTECTED]>
Subject: Re: Kernel version 2.3.9+
Date: Thu, 15 Jul 1999 04:01:34 +0000
Zachary Kuznia wrote:
> >
> >This is a public newsgroup, but not any question is fair. I have seen
> >newsgroups who chose a policy of anything goes. They are now useless,
> >and many have died (a dead newsgroup is a sad thing to look at).
> >
> >It is accepted that development kernels are not discussed unless you
> >read the release details and known problems found in other places like
> >kernelnotes.org and the linux-kernel mailing list (archived at
> >www.progressive-comp.com/Lists). Both colds and linux-kernel are high
> >bandwidth, and if linux-kernel were to be allowed to come here too,
> >colds would die.
> >
> >Yes, this was a rude thread, but it is necessary. This is the
> >free-software world, feelings don't matter, code and useful discussion
> >does. I have been insulted because of my earlier stupid questions, and I
> >was upset when it happened, but now I am more experienced and I see it
> >was useful. You'll thank us one day ;)
> >
> >--
> >Tristan Wibberley
>
> If this is the Linux system developement newsgroup, and one cannot discuss
> developement kernels, then where does one go to discuss developement
> kernels? I am reletively new to this, and I was merely looking for the
> proper newsgroup or web site to learn more about the nature of my problem.
> As the kernel open source, I wished to help to address the problem, or find
> the solution if someone had already developed it. I came here as I assumed
> that the kernel was part of the system. I understand now that my question
> had already appears to have been known and documented, which was what I
> sought to learn. However, you seem to be implying that such a question
> should not be asked even if the problem has not been probed or even
> discovered before. So, again I state my question. In which newsgroup does
> one discuss developemental kernels?
>
> Zachary Kuznia
> [EMAIL PROTECTED]
Personally, I think I made it clear that I don't approve of the way you were
treated for what I think was a correctly addressed question. This is the
correct news group. They have no right and I doubt they have the power to stop
you from such a question. Just keep your flame retardent garmets handy.
Remeber for any news group: The boyz in the hood may jump you and thump you at
any time for any reason. For reasons of their own, for no reason at all. Just
for the fun of it. At least cyber thumping sdon't leave bruises.
Gary Park
[EMAIL PROTECTED]
------------------------------
Date: Wed, 14 Jul 1999 23:34:24 -0700
From: "D. Stimits" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: strange debugging line
Hi:
While debugging a fairly simple C++ program in gdb, I ran into the strangest line from
the debugger.
It reminded me of a story a professor told about someone finding a bug because his
password kept
showing up at the point where a file kept corrupting.
The line is this:
ostream::operator<< (this=0x8049ab0, s=0x804897b "local: ")
at /home/hjl/jimi/gnu/src/libg++/libio/iostream.cc:706
/home/hjl/jimi/gnu/src/libg++/libio/iostream.cc:706: No such file or directory.
There is no person hjl on this machine, and apparently /home/hjl/jimi/ belongs to
someone involved
in either the standard c++ lib development (currently using g++ 2.7.2.1), or debugging
files. How
would I go about reporting or tracking a bug like this? Anyone know hjl? :P
Thanks
D. Stimits, [EMAIL PROTECTED]
------------------------------
From: "Thomas Steffen" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.x,redhat.config
Subject: Re: One thing Windows has over Linux.
Date: 15 Jul 1999 09:58:25 +0200
Zach Brown <[EMAIL PROTECTED]> writes:
> The current solution is to alias loadkeys and xmodmap to commands that use
> letters that are the same in the different layouts (i.e. "a" and "m" and
> the number keys are the same in Qwerty and in Dvorak). This becomes
> tedious because a user can log out and another sits down to use the system
> only to find that their username "phil" comes out on the screen
> "ldcn".
Then your system is misconfigured, X should restore the default
keyboard after a logout. imho the unix way is to integrate language
selection into xdm, so you can do it by mouse. i think both kde and
gnome have some program to configure the keyboard on a per user basis,
but i haven't found a list of mapping to go through as in windows
yet. maybe you could write a feature request? otoh it shouldn't be
difficult to write a small script and map it to some key combination,
that walks through a fixed set of mappings.
> Another possible solution would be to set the keyboard layout to qwerty
> every time someone logs out.
this should in fact happen. maybe your distribution is broken?
--
linux, linuctis - f, das beste Betriebssystem ;-)
------------------------------
From: Mark Hamstra <[EMAIL PROTECTED]>
Subject: Re: strange debugging line
Date: 15 Jul 1999 02:27:09 -0400
"D. Stimits" <[EMAIL PROTECTED]> writes:
> Hi:
>
> While debugging a fairly simple C++ program in gdb, I ran into the strangest line
>from the debugger.
> It reminded me of a story a professor told about someone finding a bug because his
>password kept
> showing up at the point where a file kept corrupting.
>
> The line is this:
> ostream::operator<< (this=0x8049ab0, s=0x804897b "local: ")
> at /home/hjl/jimi/gnu/src/libg++/libio/iostream.cc:706
> /home/hjl/jimi/gnu/src/libg++/libio/iostream.cc:706: No such file or directory.
>
> There is no person hjl on this machine, and apparently /home/hjl/jimi/ belongs to
>someone involved
> in either the standard c++ lib development (currently using g++ 2.7.2.1), or
>debugging files. How
> would I go about reporting or tracking a bug like this? Anyone know hjl? :P
hjl is H.J. Lu, who is definitely involved in glibc (and libg++)
development.
What bug, though? It looks like you've just stepped into a libg++
call for which the debugger can't find the source code. That's
not so much a bug as just a bit of sloppiness in the library env-
ironment. Afterall, on non-free software systems you'd never be
able to step into the standard libraries in the first place.
--
Mark Hamstra
Bentley Systems, Inc.
------------------------------
From: Mark Tranchant <[EMAIL PROTECTED]>
Subject: Re: strange debugging line
Date: Thu, 15 Jul 1999 07:49:10 +0100
Reply-To: [EMAIL PROTECTED]
That'd be HJ Lu, who was the primary developer of libc5, I believe.
Mark.
D. Stimits wrote:
>
> Hi:
>
> While debugging a fairly simple C++ program in gdb, I ran into the strangest line
>from the debugger.
> It reminded me of a story a professor told about someone finding a bug because his
>password kept
> showing up at the point where a file kept corrupting.
>
> The line is this:
> ostream::operator<< (this=0x8049ab0, s=0x804897b "local: ")
> at /home/hjl/jimi/gnu/src/libg++/libio/iostream.cc:706
> /home/hjl/jimi/gnu/src/libg++/libio/iostream.cc:706: No such file or directory.
>
> There is no person hjl on this machine, and apparently /home/hjl/jimi/ belongs to
>someone involved
> in either the standard c++ lib development (currently using g++ 2.7.2.1), or
>debugging files. How
> would I go about reporting or tracking a bug like this? Anyone know hjl? :P
>
> Thanks
> D. Stimits, [EMAIL PROTECTED]
------------------------------
From: Peter Allen <[EMAIL PROTECTED]>
Subject: Re: Project problem - linux printer port
Date: Thu, 15 Jul 1999 09:19:16 +0100
David B Anderson wrote:
>
> In article <[EMAIL PROTECTED]>,
> Peter Allen <[EMAIL PROTECTED]> wrote:
> >David B Anderson wrote:
> >>
> >> In article <[EMAIL PROTECTED]>,
> >> smith <[EMAIL PROTECTED]> wrote:
> >> >Project problem - linux printer port
> [ ]
> >> You might find the book
> >> Writing Linux Device Drivers
> >> by Alessandro Rubini
> >> Pub by O'Reilly
> >> useful. It seems surprisingly easy to
> [ ]
> >This leads on to my problem brilliantly. Thanks David :-)
> >First I think the original posters problem is that /dev/lp0 is
> >designed to run printers. If you read the source (drivers/char/lp*.c)
> >then it has got things like excepting interupts on the
> >rising pulse rather than on the top. /dev/parport* looked
> >good, except they didn't work for me, so I used the code
> >from WLDD ^^^^^. (It is available from
> >ftp://ftp.oreilly.com/published/oreilly/linux/drivers/
> >
> >I tried to compile it using gcc 2.7.3, which seems
> >to have tightened up its type checking, as I got lots
> >of warnings about incompatible pointer types.
> >Then the killer error,
> >cc -D__KERNEL__ -DMODULE -Wall -O2 -I/usr/include -c short.c -o
> >short.o
> >short.c:177: warning: initialization from incompatible pointer type
> >short.c:178: warning: initialization from incompatible pointer type
> >short.c:184: warning: initialization from incompatible pointer type
> >short.c: In function `short_i_read':
> >short.c:199: wrong type argument to bit-complement
> >short.c: At top level:
> [ ]
> > interruptible_sleep_on(&short_queue);
> > if (current->signal & ~current->blocked) /* a signal arrived */
> >// The error is here ^^^^^^^^^^^^^^^^^^^^^^^^
> > return -ERESTARTSYS; /* tell the fs layer to handle it */
>
> Your friend here is -E
> cc -E -D__KERNEL__ -DMODULE -Wall -O2 -I/usr/include -c short.c >junk
>
> In junk, you will find blocked is a sigset_t, which *used* to be
> a long according to comments,
> but is now a struct containing longs
> (~ of a struct won't work!).
> So the code must just be fixed a bit.
>
> The short.c:177: warning: initialization from incompatible pointer type
> worries me as the signature of the short_read function does not
> match the foperation read pointer
> (say for the read member and the short_read
> function, line 177) type. However, if the call
> used does the right things...
> but I did not follow up on that, so no guarantees from me!
>
> [EMAIL PROTECTED]
Thanks David, that is _brilliant_. Problem sorted. If anyone wants the
modified short.c it is here.
http://www.pallen.dabsol.co.uk/short3.c
I will be loading up more modules as I port them to 2.2 (Eventually
with links from the index page so you don't have to explicitly type the
name :-)) When I have ported the lot I will try and persuade Alessandro
to put the new versions on his ftp site.
Peter Allen
------------------------------
From: Joe Pfeiffer <[EMAIL PROTECTED]>
Subject: Re: strange debugging line
Date: 15 Jul 1999 00:58:53 -0600
"D. Stimits" <[EMAIL PROTECTED]> writes:
>
> The line is this:
> ostream::operator<< (this=0x8049ab0, s=0x804897b "local: ")
> at /home/hjl/jimi/gnu/src/libg++/libio/iostream.cc:706
> /home/hjl/jimi/gnu/src/libg++/libio/iostream.cc:706: No such file or directory.
>
> There is no person hjl on this machine, and apparently /home/hjl/jimi/ belongs to
>someone involved
> in either the standard c++ lib development (currently using g++ 2.7.2.1), or
>debugging files. How
> would I go about reporting or tracking a bug like this? Anyone know hjl? :P
hjl is HJ Lu (Liu? I apologize for not remembering). This is telling
you where in the code he wrote the program is crashing. My
recommendation would be:
1) upgrade. I was never able to get the io stream to work reliably
with g++ before 2.8.1.
2) use the ``up'' gdb command to find out where in *your* code you are
when it's crashing. Is that ``this'' pointer really a valid ostream?
3) (and the only slightly controversial one of the bunch) just chuck
the whole c++ iostream stuff and use printf. It's 100 times simpler,
even if you are doing C++ (that's what I do).
--
Joseph J. Pfeiffer, Jr., Ph.D. Phone -- (505) 646-1605
Department of Computer Science FAX -- (505) 646-1002
New Mexico State University http://www.cs.nmsu.edu/~pfeiffer
------------------------------
From: "Oliver D. Bedford" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,comp.os.linux.setup
Subject: Re: Help - Deleted /var/log/* from RedHat 5.2 system!
Date: Thu, 15 Jul 1999 10:38:14 +0200
Josef M�llers wrote:
>
> Nico Zigouras wrote:
> >
> > Hi folks:
> >
> > I deleted /var/log from my RedHat 5.2 system and all files in that
> > folder. Now all my web server access and error logs are gone and they
> > are not being regenerated. My /etc/httpd/logs folder was also deleted
> > of error_log and access_log. Any help? Thanks.
>
> How would you think that log files be regenerated?
I am not sure what "regenerated" means, but sometimes files have to
exist before the actual logging is done. So you should "touch" all
relevant logfiles (check permissions!).
And perhaps you have to restart syslogd, apache etc. because they are
still writing to the non-existent files.
Oliver
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Unix queues IPC?
Date: Thu, 15 Jul 1999 08:41:29 GMT
Are kernel parameters that regulate number of
messages, total messages size per queue, and per
system configurable as they are on sysV4.2
(unixware 2.1)? There I have settings with max
128K per queue, and 1Meg in total for queues. I
would not mind having more, but less could pose
some problems ;)
Thanks,
Davorin Rusevljan
In article <[EMAIL PROTECTED]>,
Warren Young <[EMAIL PROTECTED]> wrote:
> It supports them and they work well. We have a
set of programs with
> 28,000 LOC between them that use message queues
extensively. The
> program was written on a SysVR4.2 system, but
the IPC bits recompiled
> without even a warning. (TLI versus sockets is
another story, though.
> B-> )
> --
> = Warren -- http://www.cyberport.com/~tangent/
> =
> = ICBM Address: 36.8274040 N, 108.0204086 W,
alt. 1714m
>
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,redhat.kernel.general
Subject: How can i increase block device buffer cache?
Date: Thu, 15 Jul 1999 07:31:01 GMT
Hello.
I want to increase buffer cache of block device. i have 512Mb of RAM and
want to use 400+MB of my memory as a cache buffer.
Can any one help me for increasing this cachr buffer or guide me to some
documentation.
Any help will be appreciated.
Thanks !!
================== Posted via SearchLinux ==================
http://www.searchlinux.com
------------------------------
From: Tero A Kauppinen <[EMAIL PROTECTED]>
Subject: Re: Scheduling issue
Date: 15 Jul 1999 09:51:39 GMT
Tero A Kauppinen <[EMAIL PROTECTED]> wrote:
: If a process gets interrupted by a hardware interrupt, and
: while processing the interrupt, the IRQ handler schedules a task to the
: immediate queue (using mark_bh(IMMEDIATE_BH), etc.), which one (the
: interrupted process or the scheduled task) runs first when the IRQ
: handler returns?
Oops, I forgot to mention that the interrupted process runs in kernel space.
--
tero
------------------------------
From: Tero A Kauppinen <[EMAIL PROTECTED]>
Subject: Scheduling issue
Date: 15 Jul 1999 09:42:36 GMT
If a process gets interrupted by a hardware interrupt, and
while processing the interrupt, the IRQ handler schedules a task to the
immediate queue (using mark_bh(IMMEDIATE_BH), etc.), which one (the
interrupted process or the scheduled task) runs first when the IRQ
handler returns?
--
tero
------------------------------
** 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
******************************
