Linux-Development-Sys Digest #662, Volume #6 Thu, 29 Apr 99 15:13:56 EDT
Contents:
pseudo code of asm
Which environment ? (FX)
Re: Help with compiling mico / What is Error 139 (J.H.M. Dassen (Ray))
Re: physical Memory (Robert Kaiser)
RFS? Re: NFS vs DFS (Christopher Browne)
Re: Is Linux Y2K compliant? (Christopher Browne)
Re: Modprobe can't file module char-major-6... ("Andre Malafaya Baptista")
kernels 2.2.x: sound cuts with OPL3-SAx sound driver (David Nowak)
Problem with 2.2.6 and irda: irda.h missing ([EMAIL PROTECTED])
Re: NFS vs DFS (John Hughes)
Re: copy_from_user (Peter Samuelson)
Re: Problem with 2.2.6 and irda: irda.h missing (Peter Samuelson)
Re: Linux system ID, is there such a thing? (Glen Turner)
Halt implementation ("Andre Malafaya Baptista")
What does kernel message mean? (Peter Baker)
Re: Symbolic link and chroot (Kent Friis)
----------------------------------------------------------------------------
From: <[EMAIL PROTECTED]>
Subject: pseudo code of asm
Date: 29 Apr 1999 11:09:02 GMT
Where can I find any documents on assembly pseudo code supported
by gcc ?
Thanks in advance
J.C. Chuang
------------------------------
From: FX <[EMAIL PROTECTED]>
Subject: Which environment ?
Date: Thu, 29 Apr 1999 07:49:19 +0200
Hello,
I'm supposed to write a graphical application running under Linux to log
modem activities ...
But which environment should I choose. I have already some code in C
language !
Some people have advise me to use GTK or TCL/TK ? Are they appropriate ?
Is there graphical environment to build applications in those languages
?
Thanks
FX
------------------------------
From: [EMAIL PROTECTED] (J.H.M. Dassen (Ray))
Subject: Re: Help with compiling mico / What is Error 139
Date: 29 Apr 1999 11:11:53 GMT
Royce <[EMAIL PROTECTED]> wrote:
>/home/mico/./admin/mkdepend -I../include -O -fno-exceptions *.cc >>
>.depend
>make[1]: *** [.depend] Error 139 <---- What is this
Error 139 corresponds to signal 11. This may be cause by hardware troubles;
see the FAQ http://www.bitwizard.nl/sig11/ .
HTH,
Ray
--
J.H.M. Dassen | RUMOUR Believe all you hear. Your world may
[EMAIL PROTECTED] | not be a better one than the one the blocks
| live in but it'll be a sight more vivid.
| - The Hipcrime Vocab by Chad C. Mulligan
------------------------------
From: [EMAIL PROTECTED] (Robert Kaiser)
Subject: Re: physical Memory
Date: 29 Apr 1999 08:34:23 GMT
In article <[EMAIL PROTECTED]>,
Martin Recktenwald <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] (Robert Kaiser) writes:
>
> The following mail might be interesting for anyone interesting in
> doing DMA to user space; it does not explicitly talk about DMA but I
> don't think that makes any difference.
>
This is about accessing user-space memory from an ISR. This can
indeed be done in much the same way as user-space DMA (i.e. with my
patch, one could do it).
I did submit my patch to Linus some time ago suggesting to add it
to the kernel, but he decided against it. I had a similar discussion
with him back then ...
> ---------------------------------------------------------
> Date: Mon, 12 Apr 1999 21:17:11 -0700 (PDT)
> From: Linus Torvalds <[EMAIL PROTECTED]>
> cc: Kernel Mailing List <[EMAIL PROTECTED]>
> Subject: Re: verify_area(...) possible problem.
>
> This keeps coming up, and even sane people like Alan Cox want to do it,
> even though it is fairly obvious that it should not be done that way.
I _really_ would like to see a sane explanation as to why this would be
so obvious. Other OSes do this every day and they achieve throughputs
that you can never get with (unpatched) Linux.
> By the time your interrupt handler is called, the process is long long
> gone and even if it was the current process it might have changed its
> mapping.
Of course, but all of this doesn't matter if the target memory has been
locked and it's physical address is known.
> Basically you should never EVER even consider writing to user space from
> interrupts. EVER!
>
> Basically, you should always use a kernel-space buffer. Just accept that
> as a fundamental notion, and your life suddenly turns a lot easier.
>
As a matter of fact _my_ life was a lot harder before I developed the
patch to circumvent this silly restriction....
> Now, I know about zero-copy. I'm not a big believer in it, but I certainly
> know about it. And having a kernel buffer does not imply that you can't do
> zero-copy. It just means that you can' tdo the initial copy to user space.
>
It also means that you have to do something in a driver that logically
belongs into the application. The result being that the driver has to
do a lot of error-prone bookkeeping (keeping track of which process
owns which DMA buffer -- what if the process suddenly gets killed ?) that
would otherwise be unnecessary.
> Sounds contradictory? Think "mmap()". It works, it's there, and magically
> all the problems go away. Don't make the mountain go to Mohammed. Instead,
> think of your problem the other way around: instead of the kernel writing
> to user space, think of it as user space asking to see a window of a
> kernel buffer. You make a device driver that has a mmap() function, and
> suddenly the device driver can write to kernel memory, and whatever it
> writes magically shows up in user space too.
>
Sure, but this way, a driver will always be forced to use a non-standard,
cryptic protocol (i.e. mmap(), ioctl()) to implement DMA. It can never
hide the fact that DMA is being used. The application has to be written
specifically to match this interface. Basically, the driver is divided
into a kernel part and a user-space part with a kludgy interface in
between.
Look at it this way: the plain simple read() call transfers data
from a device into a user-space buffer. Nobody seems to have a problem
with that. Why on earth does everybody seem to have such a hard time
accepting that there is absolutely no need to change this if the
hardware can do the transfer with DMA ?
Cheers
Rob
================================================================
Robert Kaiser email: rkaiser AT sysgo DOT de
SYSGO RTS GmbH
Mainz / Germany
------------------------------
From: [EMAIL PROTECTED] (Christopher Browne)
Subject: RFS? Re: NFS vs DFS
Reply-To: [EMAIL PROTECTED]
Date: Thu, 29 Apr 1999 13:05:36 GMT
On 28 Apr 1999 17:49:58 +0200, John Hughes <[EMAIL PROTECTED]> wrote:
>"G. Sumner Hayes" <[EMAIL PROTECTED]> writes:
>> AFS, DFS, and Coda are the only networked filesystems I am aware of that
>> are really designed as highly scalable, high-performance solutions. All
>> three use Kerberos for authentication and encryption.
>
>And not a word about RFS. How sad. I'll just go away and cry.
Please don't.
I'm not familiar with it, and I'm sure I'm not alone.
It would be nice to see a precis on it so we may learn something about
it, and whether or not it has merits that are of interest.
--
Now I know someone out there is going to claim, "Well then, UNIX is
intuitive, because you only need to learn 5000 commands, and then
everything else follows from that! Har har har!" (Andy Bates in
comp.os.linux.misc, on "intuitive interfaces", slightly defending
Macs.)
[EMAIL PROTECTED] <http://www.hex.net/~cbbrowne/linuxkernel.html>
------------------------------
From: [EMAIL PROTECTED] (Christopher Browne)
Subject: Re: Is Linux Y2K compliant?
Reply-To: [EMAIL PROTECTED]
Date: Thu, 29 Apr 1999 13:05:52 GMT
On Wed, 28 Apr 1999 15:14:03 -0400, cn <[EMAIL PROTECTED]> wrote:
>Is Linux Y2K compliant? If so, what tools/products are available for
>testing this scenario? Any suggestions? Any help would be much
>appreciated ...
Q: Are *you* Y2K-compliant?
For the most part, it's *programmers* that are, or are not,
Y2K-compliant.
Q: How do *you* define Y2K compliant?
[*I* define it as "Was the program design done competently?"]
Q: How do you define Linux?
- As an OS kernel?
- Based on every piece of software on the Internet that claims to have
a "Linux version"?
- Based on some other metric that lies somewhere between?
[The answers to some analogue to your question vary *vastly* depending
on what you mean...]
Q: Have you actually tried to look for such information on the web so
as to find it without resorting to looking ignorant, instead of merely
asking Yet Another Frequently Asked Question?
See the URL below for a fairly exhaustive set of links to such
information.
[As a matter of fact, yes, I *am* getting irritated at the number of
people that are either unwilling or unable to do *any* research that
keep asking this same question every few days.]
--
Now I know someone out there is going to claim, "Well then, UNIX is
intuitive, because you only need to learn 5000 commands, and then
everything else follows from that! Har har har!" (Andy Bates in
comp.os.linux.misc, on "intuitive interfaces", slightly defending
Macs.)
[EMAIL PROTECTED] <http://www.hex.net/~cbbrowne/linuxy2k.html>
------------------------------
From: "Andre Malafaya Baptista" <[EMAIL PROTECTED]>
Subject: Re: Modprobe can't file module char-major-6...
Date: Thu, 29 Apr 1999 15:42:07 +0100
I don't know if this could be the problem:
In kernels 2.2.x, your parallel port is most probably associated with lp1
and not lp0.
Make sure lp is lp1...
HTH,
Andr�
Robin P. Reagan <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Konrad Mieredorff wrote:
> >
> > "Robin P. Reagan" wrote:
> > >
> > > Hi
> > > I just upgraded my RH5.2 system from kernel 2.0.36 to Kernel 2.2.6 and
> > > all went fine except for two things.
> > >
> > > 1) I can nolonger print from Linux! I have checked all the obvious
> > > things. I can preint fine from my windoz partition.
> > >
> > > 2) I get the following message in the /var/log/messages file
> > >
> > > Apr 23 22:56:10 phobos modprobe: can't locate module char-major-6
> > > Apr 23 22:57:14 phobos last message repeated 2 times
> > >
> > > What is the char-major-6 module used for? It isn't in the modules dir
> > > and I can't find it anywhere?
> > >
> > > I suspect that the two problems are related...
> > >
> > > Anyhelp would be appreciated.
> > >
> > > Robin.
> >
> > The parallel port driver offers the character devices /dev/lp0-3, that's
> > why it is called char-major-6.
> >
> > What you can do is:
> > 1.) Check your kernel configuration.
> > (Option "Chardrivers -> Parallel Printer Support" in make
> > menuconfig)
> > 2.) Recompile the kernel modules.
> > (make modules / make modules_install)
> > 3.) execute "depmod -a"
> > 4.) Check wether the module works.
> > (modprobe lp)
> > 5.) If the problems still there copy the file "lp.o" from
> > /usr/src/linux/modules to /lib/modules/2.2.6
> > (if the file isn't there you messed the configuration -- Start
> > again:-))
> > and do a "depmod -a"
> >
> > Everything as user root of course.
> > Feel free to ask again if my method doesn't work
> >
> > Good luck!
> >
> > - Konrad Mierendorff
>
> I rebuilt my kernel with a new configuration file and it still does not
> work :(
>
> lp.o is in my /lib/modules/2.2.6-ac1/misc/ dir and loaded fine (at least
> modprobe installed it without complaining and when I do A lsmod it shows
> up with 0 users).
>
> when I try to print from the command line I get the following:
>
> [robin@phobos robin]$ lpr monitors.txt
> lpr: connect: Connection refused
> jobs queued, but cannot start daemon.
>
>
> --
> Live Long and Prosper!
> Robin, Katie, Samuel & Erin Reagan
> http://home.sprynet.com/~krreagan/
> ----------------------"...human error!" [HAL9000]
------------------------------
From: David Nowak <[EMAIL PROTECTED]>
Subject: kernels 2.2.x: sound cuts with OPL3-SAx sound driver
Date: Thu, 29 Apr 1999 17:00:48 +0200
It seems that there is a problem with the new sound driver for OPL3-SAx
of kernels 2.2.x: There are sound cuts. Is it a known bug ?
Thank you,
--
David
http://www.irisa.fr/prive/nowak/
------------------------------
From: [EMAIL PROTECTED]
Subject: Problem with 2.2.6 and irda: irda.h missing
Date: 29 Apr 1999 13:32:06 +0200
hi,
yesterday i patched 2.2.3 to 2.2.6 und tried to recompile. during the
modules i got an error saying linux/irda.h not found, followed by a
couple of warning and error messages. obviously,
/usr/src/linux/include/linux/irda.h is expected, but was not created
by the patches (i thing 2.2.5 to 2.2.6). is it just a problem with the
patches, or is the file missing completely?
fortunately, i don't really need irda, so i just compiled without.
--
We regret to announce that Windows 2000 wont be ready before 1901.
------------------------------
From: John Hughes <[EMAIL PROTECTED]>
Subject: Re: NFS vs DFS
Date: 29 Apr 1999 18:09:51 +0200
[EMAIL PROTECTED] (Leslie Mikesell) writes:
> In article <[EMAIL PROTECTED]>,
> John Hughes <[EMAIL PROTECTED]> wrote:
> >And not a word about RFS. How sad. I'll just go away and cry.
>
> It is a sad memory, if you recall how processes that had open files
> or a working directory across a broken mount point were killed
> with no chance to recover.
A mere implementation detail. Not at all required by the protocol.
(admittedly you'd get an error if you tried to read a file on a server
that was down, but I see no reason you should get killed).
--
John Hughes <[EMAIL PROTECTED]>,
Atlantic Technologies Inc. Tel: +33-1-4313-3131
66 rue du Moulin de la Pointe, Fax: +33-1-4313-3139
75013 PARIS.
------------------------------
From: [EMAIL PROTECTED] (Peter Samuelson)
Subject: Re: copy_from_user
Date: 29 Apr 1999 07:27:57 -0500
Reply-To: Peter Samuelson <[EMAIL PROTECTED]>
[Mike Rushford <[EMAIL PROTECTED]>]
> > There is a piece of hardware at the 0xD0000000 location
[...]
> > How do I convince the kernel 2.2.6 that it should allow me to write
> > to the memory at location 0xD0000000
[Arun Sharma <[EMAIL PROTECTED]>]
> Is the address 0xD0000000 virtual or physical ?
Arun's point being that probably what you want to do is go read
Documentation/IO-mapping.txt to learn all about bus_to_virt().
--
Peter Samuelson
<sampo.creighton.edu!psamuels>
------------------------------
From: [EMAIL PROTECTED] (Peter Samuelson)
Subject: Re: Problem with 2.2.6 and irda: irda.h missing
Date: 29 Apr 1999 07:43:11 -0500
Reply-To: Peter Samuelson <[EMAIL PROTECTED]>
[<[EMAIL PROTECTED]>]
> yesterday i patched 2.2.3 to 2.2.6 und tried to recompile. during the
> modules i got an error saying linux/irda.h not found, followed by a
> couple of warning and error messages. obviously,
> /usr/src/linux/include/linux/irda.h is expected, but was not created
> by the patches (i thing 2.2.5 to 2.2.6). is it just a problem with
> the patches, or is the file missing completely?
Yes and yes. (It *is* a problem with the patch, and the file *is*
missing completely.)
Upgrade to 2.2.7.
--
Peter Samuelson
<sampo.creighton.edu!psamuels>
------------------------------
Date: Thu, 29 Apr 1999 22:58:49 +0930
From: Glen Turner <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps
Subject: Re: Linux system ID, is there such a thing?
Walter Lundby wrote:
<huge unfair snip>
> ...IMHO the most interesting potential
> solution are those programs that attempt to call home when started.
> (netscape to www.netscape.com with cookies)
One word: firewall.
All the "call home" schemes do is to move the licensing pain from the
UNIX system administrator to the network administrator.
"Our internet link has gone down" that's why you can't start
program X" is not a win.
To the original poster: I have worked for a few software
companies in my ten years, and the best never had to worry
about dongles or license servers. The users that cared,
paid us. Lots, yearly. And got a lot of good support,
regular upgrades and responses to feature requests.
The users that didn't care, well they didn't get invites
to our user conferences, didn't get our newsletter, couldn't
download the latest manuals or the bug database from our web
site.
And one day they'd want a feature or a bug fix and would
find themselves running version 4 when everyone else
was running version 19. And they'd ring quietly, we'd
welcome them, and send the invoice along with a huge
next-day box of CDs, manuals, product literature and coffee
cups.
The marketing manager of one company was telling me that
copying was our best sales tool. The users that didn't
pay, weren't generally worth the support and care.
------------------------------
From: "Andre Malafaya Baptista" <[EMAIL PROTECTED]>
Subject: Halt implementation
Date: Thu, 29 Apr 1999 15:48:35 +0100
Hi.
I was wondering about the /sbin/halt implementation.
I believe that it first checks whether it is in runlevel 0 or not. If not it
just telinit 0.
Then, it's the runlevel 0 script in rc.d that handles shutdown, right?
The script should call /sbin/halt once again. This time, halt sees that it
is in runlevel 0 and, poof... shuts down.
Is this description correct?
Where can I find the source for halt?
TIA,
Andr�
------------------------------
From: Peter Baker <[EMAIL PROTECTED]>
Subject: What does kernel message mean?
Date: 29 Apr 1999 14:35:35 GMT
Hi
I have 2.2.6 running and every so often I get the meassge below
Message from syslogd@madness2 at Fri Apr 30 00:25:39 1999 ...
madness2 kernel: >5D 1D 81 16 7D 31 86 C4 ]...}1..
It ssems to hang netscape (4.08) but can't see any other problems.
Thanks
Peter
=========================================================================
|| Peter Baker email: [EMAIL PROTECTED] ph: 07 3864 1293 (W) ||
|| Mail: School of Mathematics, Queensland University ||
|| of Technology, GPO Box 2434, Brisbane QLD 4001 ||
=========================================================================
------------------------------
From: Kent Friis <[EMAIL PROTECTED]>
Subject: Re: Symbolic link and chroot
Date: Thu, 29 Apr 1999 20:45:00 +0200
"G. Sumner Hayes" wrote:
>
> For people with root (or chroot capability on a capabilities-
> based system) I don't know what is the current state of affairs. It
> used to be that root could chroot("../../../../../../../../") to get
> out of jail free. If that's an issue for you, you probably ought to
> investigate the current situation.
The ../../../.. thing shouldn't exist anymore (I think), but root
will _ALWAYS_ be able to get out of a chroot'ed directory.
Just mkdir /dev, and mknod the device files. Then you have
full access to any disk in the system, and debugfs can do
some tricks to move files and directories around - it
should even be able to make hard links to directories....
Or grep the raw device for any information needed.
Kent
------------------------------
** 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
******************************
