>Here is the patch.
Sorry, at least most of the patch was there. Here is the rest:
diff -r -u -N -b linux-2.4.5.ac16/include/linux/fs.h
linux-2.4.5.ac16.patched/include/linux/fs.h
--- linux-2.4.5.ac16/include/linux/fs.h Tue Jun 19 15:12:50 2001
+++ linux-2.4.5.ac16.patched/include/linux/fs.h
In article <[EMAIL PROTECTED]>,
Zack Weinberg <[EMAIL PROTECTED]> wrote:
>On Tue, Jun 19, 2001 at 07:52:25PM -0700, David S. Miller wrote:
>>
>> Zack Weinberg writes:
>> > It *has* been fixed in 2.4, though. Some sort of compatibility issue?
>>
>> No, some kind of "it doesn't matter" issue.
>
depmod: *** Unresolved symbols in /lib/modules/2.4.5-ac16/kernel/drivers/net/wan/comx.o
depmod: proc_get_inode
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Hi,
I have written this patch so that /dev/raw now appears in a devfs
filesystem. I haven't tried to support the /dev/rawN devices because
I'm not sure that it would be worthwhile. (Seeing as you need to bind
them by hand manually anyway.)
Cheers,
Chris
--- linux-2.4.5/drivers/char/raw.c.orig
Daniel Phillips writes:
> I never realized how much I didn't like the good old 5 second delay
> between saving an edit and actually getting it written to disk until
> it went away. Now the question is, did I lose any performance in
> doing that. What I wrote in the previous email turned out to
On Tue, Jun 19, 2001 at 07:52:25PM -0700, David S. Miller wrote:
>
> Zack Weinberg writes:
> > It *has* been fixed in 2.4, though. Some sort of compatibility issue?
>
> No, some kind of "it doesn't matter" issue.
I can demonstrate user code that behaves differently under 2.2 than
2.4. The
On Wed, Jun 20, 2001 at 01:33:19PM +1000, Paul Mackerras wrote:
> Well, I object to the "without thinking" bit. [..]
agreed, apologies.
> BHs disabled is buggy - why would you want to do that? And if we do
tasklet_schedule
> want to allow that, shouldn't we put the check in raise_softirq or
Andrea Arcangeli writes:
> With pre3 there are bugs introduced into mainline that are getting
> extended to all architectures.
>
> First of all nucking the handle_softirq from entry.S is wrong. ppc
> copied without thinking and we'll need to resurrect it too for example
Well, I object to the
On Tue, Jun 19, 2001 at 08:04:42PM -0700, Larry McVoy wrote:
> On the other hand, the fact that it doesn't exist on other platforms sort
> of means that it isn't going anywhere. In a sick sort of way, the most
> likely way to make this happen is to get Microsoft to do it and then Linux
> will do
On Tue, Jun 19, 2001 at 10:57:38PM -0400, Michael Rothwell wrote:
> On 19 Jun 2001 20:01:56 +0100, Alan Cox wrote:
>
> > Linux inherits several unix properties which are not friendly to good state
> > based programming - lack of good AIO for one.
>
> Oh, how I would love for select() and poll()
Dear All;
I can fire up XFree4.1.0 on one or several virtual
consoles, and switch between them, and text consoles to my hearts
content. However, if the X server exits everything is still fine,
_except_ any attempt to switch consoles at this point will lock
up the machine
On 19 Jun 2001 20:01:56 +0100, Alan Cox wrote:
> Linux inherits several unix properties which are not friendly to good state
> based programming - lack of good AIO for one.
Oh, how I would love for select() and poll() to work on files... or for
any other working AIO mothods to be present.
What
On Tue, Jun 19, 2001 at 10:23:47PM -0400, John Weber wrote:
> On a related note... is System.map also necessary? Anyone care to explain
Debugging. ksymoops and klogd can both make use of it.
mrc
--
Mike Castle [EMAIL PROTECTED] www.netcom.com/~dalgoda/
We are all of us
Zack Weinberg writes:
> It *has* been fixed in 2.4, though. Some sort of compatibility issue?
No, some kind of "it doesn't matter" issue.
Later,
David S. Miller
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
On Tue, Jun 19, 2001 at 07:16:23PM -0700, David S. Miller wrote:
>
> Zack Weinberg writes:
> > The anonymous pipe code in 2.2 does not check the return value of
> > copy_*_user. This can lead to silent loss of data.
>
> I remember Andrew Tridgell (cc:'d) spotting this a long time
> ago, and
Alan Cox wrote:
>>I am trying to compile the 2.2.19 kernel one one machine for installation
>>on another. I believe I need to do more than just copy over bzImage and
>>modify lilo.conf, but I don't know what. Is there documentation somewhere
>>on how to do this? Thanks.
>>
>
> Other than
On Tue, Jun 19, 2001 at 06:30:54PM -0700, Ben Greear wrote:
> Yeah, and we are young and prolific too, so you better watch out! :)
Prolific != competent.
--
Mike Castle [EMAIL PROTECTED] www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
The anonymous pipe code in 2.2 does not check the return value of
copy_*_user. This can lead to silent loss of data.
The appended patch fixes the bug. It has been in continuous use on my
machine since May 13 (2.2.19) with no problems. It will apply to any
2.2 kernel from at least 2.2.18,
I never realized how much I didn't like the good old 5 second delay between
saving an edit and actually getting it written to disk until it went away.
Now the question is, did I lose any performance in doing that. What I wrote
in the previous email turned out to be pretty accurate, so I'll
Larry McVoy wrote:
>
> Good question but I doubt we're going to get anywhere. Anyone who thinks
> that 73MB of RAM is an OK thing to waste on window system is probably a
> died-in-the-wool Java programmer and could care less about performance,
> system design, or any elegance whatsoever.
Hi, Al. Here's an oddity I just ran across with VFS bindings:
# mkfifo /dev/modem (BTW: it would be nice not to have to make the node)
# mount --bind /dev/tts/0 /dev/modem
# kermit
kermit> set line /dev/modem
kermit> set speed 4800
?Sorry, you must SET LINE first
The reason this is
the 'compile in one place and export the product via nfs' mentality
really kicks in under *bsd, where you may have a server farm and want to
upgrade all at once...the tarball idea works for one machine, but for
multiples, its all about exporting it... just my 2 cents. --gabe
,[ On Tue, Jun
setuid(2) differs from the OpenBSD setuid(2) in that -EPERM is
returned by the syscall even if the euid of the process matches the
uid passed to it.
Either I am non compos or the thing is very wrong. The docs
(man-pages-1.35) say
ERRORS
EPERM The user is not the super-user, and uid
On Tue, Jun 19, 2001 at 05:19:45PM -0700, Mike Castle wrote:
> On Tue, Jun 19, 2001 at 04:56:16PM -0700, Jonathan Lundell wrote:
> > But so what? That's $16 worth of DRAM (I just checked). Not so bad
> > *if* threads are otherwise a great solution. I grant that one might
> > have a pretty tough
Hi,
Ben Greear wrote:
> > > > Should VLANs be devices or some other thing?
> I found it to be the easiest way to implement things. It allowed
> me to not have to touch any of layer 3, and I did not have to patch
> any user-space program like ip or ifconfig.
I faced the same issue when
The following diff tries to improve on the efficiency of try_to_unuse(). It
removes the potential O(|swap_map|^2) business and makes it linear time.
I'm not sure what this means in terms of overall change, but Linus seemed
interested in the innefficiency in that code. Test with caution.
Gabriel Rocha wrote:
> you could always compile on one machine and nfs mount the /usr/src/linux
> and do a make modules_install from the nfs mounted directory...
The way I've always managed this sort of thing is to tar up your kernel source,
transfer it to the "compile box" however you please,
On Tue, Jun 19, 2001 at 04:56:16PM -0700, Jonathan Lundell wrote:
> But so what? That's $16 worth of DRAM (I just checked). Not so bad
> *if* threads are otherwise a great solution. I grant that one might
> have a pretty tough time making the case, but again, for the right
> application, say
On Tue, 19 Jun 2001, David S. Miller wrote:
>
>
> Don't believe me that Solaris sucks here? Run this experiment under
> Solaris-latest and Linux on a sparc64 system (using lmbench):
>
> Under Solaris: ./lat_proc fork
> Under Linux: strace -f ./lat_proc fork
>
> I bet the Linux case does better
I was running my VLAN test, which creates 4000 VLAN interfaces,
sets their IP/mask, and then later tears them down...
However, my box is seeing 300 processes running and a load
of around 47.00. Most of these processes are 'ifconfig'
and net.agent. I am not running ifconfig in my script, so
I
** Reply to message from Rob Landley <[EMAIL PROTECTED]> on Tue, 19 Jun
2001 14:18:03 -0400
> 2) Not only did Linux not have threads (at all), it didn't plan to have
> threads, and anybody who brought up the idea of threads was dismissed.
> Considering this was long before clone, and SMP
Dear all,
The ac-kernel series include a check in default_llseek()
to not set the file position beyond the file systems
maximum file size.
This check should be done only for regular files, e.g. for
a device special file the test does not make sense.
Alan suggested that we remove the check from
On Tuesday 19 June 2001 12:52, Larry McVoy wrote:
> On Tue, Jun 19, 2001 at 05:26:09PM +0100, Matthew Kirkwood wrote:
> > On Tue, 19 Jun 2001, Larry McVoy wrote:
> > > ``Think of it this way: threads are like salt, not like pasta. You
> > > like salt, I like salt, we all like salt. But we
2.4.5-ac14 on an Asus A7A266 w/ Athlon:
...
Jun 19 16:14:21 pollux kernel: probable hardware bug: clock timer
configuration lost - probably a VIA686a motherboard.
Jun 19 16:14:21 pollux kernel: probable hardware bug: restoring chip
configuration.
...
According to the documentation, this is an
Robert Love wrote:
> > Can you give the CVS driver a try? Snapshots are available here:
> > http://opensource.creative.com/snapshot.html
> >
> > The driver in the kernel is based on a CVS snapshot from last summer, the
> > problem may be fixed in CVS. Also, the CVS driver is a common driver for
>
The attached diff adds devfs support to the rio500 driver, so that
/dev/usb/rio500 gets created automagically. It was generated against
2.4.5, but probably applies fine against any recent kernel. Comments
are welcome (but be gentle, this is my first attempt at a kernel
patch :-).
Cheers!
On Tue, 19 Jun 2001, Ben Greear wrote:
> I have had a good discussion with Dave Miller today, and there
> is one outstanding issue to clear up before my 802.1Q VLAN patch may
> be considered for acceptance into the kernel:
>
> Should VLANs be devices or some other thing?
I would vote that VLANs
On Tue, Jun 19, 2001 at 04:45:24PM -0500, Eli Carter wrote:
> Gabriel Rocha wrote:
> > you could always compile on one machine and nfs mount the /usr/src/linux
> > and do a make modules_install from the nfs mounted directory...
>
> Which would require exporting that filesystem with root
I tried 2.4.5-ac16 on my Asus A7A266 w/ Athlon because the fixnotes
sounded like it might address the simplex vs. DMA problem that I
reported a while back, but I get a kernel panic early in the boot
sequence every time I try to boot.
FYI, 2.4.5-ac14 boots and runs OK, except for the disabled
Philip Blundell wrote:
> I don't think -fno-builtin has any bearing on whether gcc will emit calls to
> memcpy;
Good point. The subject was about the compiler adding function calls to
code, and I started talking about the compiler removing them...
--
Jeff Garzik | Andre the Giant has a
Alan Cox wrote:
> > why not always -fno-builtin,
> > and then call __builtin_foo when we really want the compiler's version..
> That may well be the right thing to do. Of course we rely on the compiler
> providing some of them too
true, it wouldn't be a completely transparent switchover, but it
>> It wont build with gcc 3.0 yet. To start with gcc 3.0 will assume it can
>> insert calls to 'memcpy'
>
>IMHO omitting -fno-builtin when compiling the kernel was always a risky
>proposition... Since we provide our own copies of many of the builtins
>[which are used in the kernel] anyway... why
> IMHO omitting -fno-builtin when compiling the kernel was always a risky
> proposition... Since we provide our own copies of many of the builtins
> [which are used in the kernel] anyway... why not always -fno-builtin,
> and then call __builtin_foo when we really want the compiler's version..
hey, how and where you export the filesystem is an exercise left for the
reader, i have no problem exporting nfs filesystems in my internal
network, what you do or dont, is up to you. and there is always
cfs...
,[ On Tue, Jun 19, at 04:45PM, Eli Carter wrote: ]--
| Gabriel Rocha
Hi,
I am experiencing intermittent hangs running LinuxThreads programs from a shell
script. This happens with any combination of stock RH 7.1 SMP kernel (2.4.2) or my
own 2.4.5 kernel and stock RH 7.1 libc (2.2.2), redhat rawhide libc (2.2.3) and my own
2.2.3 libc.
If I run, for example,
On Sun, 17 Jun 2001, Walter Hofmann wrote:
> I had already two crashes with ac15. The system was still ping-able, but
> login over the network didn't work anymore.
>
> The first crash happened after I started xosview and noticed that the
> system almost used up the swap (for no apparent
Quoting Tom Diehl <[EMAIL PROTECTED]> from ml.linux.kernel:
:What is the best way to install the modules? Is there a directory _all_ of
:the modules exist in b4 you do "make modules_install". I usually end up
:setting EXTRAVERSION to something unique and doing a make modules_install.
:That way it
Larry McVoy writes:
> Great, then we are in violent agreement on the single abstraction.
> On the second part, I stand by my previous statements that threads or
> processes should be used sparingly.
>
> All I'm doing is trying to counter all the "threads are great" hype.
> This is a pretty
Johannes Erdfelt wrote:
> Could you load uhci with the debug=1 option?
I did an 'insmod uhci.o debug=1' but the dmesg output did not alter.
My easy steps to reproduce it is to 'delete selected images' in gphoto such
that there will be no images in the camera left when the operation is done.
At
On Tue, Jun 19, 2001 at 04:55:10PM -0400, Tom Diehl wrote:
> What is the best way to install the modules? Is there a directory _all_ of
> the modules exist in b4 you do "make modules_install". I usually end up
> setting EXTRAVERSION to something unique and doing a make modules_install.
> That way
-Original Message-
From: Tom Diehl [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 19, 2001 4:55 PM
To: [EMAIL PROTECTED]
Subject:Re: How to compile on one machine and install on another?
On Tue, 19 Jun 2001, Alan Cox wrote:
> Other than making sure you configure it
Are you sure about bad memory?
Single-bit errors will be corrected; double-bit errors will generate NMI.
You can also find memory errors with an exerciser. Unfortunately,
trusty memtest86 bombs on my ServerWorks machine. Instead I use
http://www.qcc.sk.ca/~charlesc/software/memtester/
On Tue, 19 Jun 2001, Alan Cox wrote:
> Other than making sure you configure it for the box it will eventually run
> on - nope you have it all sorted. If you use modules you'll want to install
> the modules on the target machine too
What is the best way to install the modules? Is there a
Hello,
(for all who are interested)
I finally obtained access to a linux platform running 2.2.17 on a 2x500
Mhz alpha machine (Compaq's testdrive program).
Below are my results:
Linux 2.2.17 on 2x500 Mhz Celerons: parallel app = 1.48 times faster than
sequential one.
Linux 2.4 on a 2x1 Ghz
Hi,
the ac series include a check in default_llseek() to not set the
file position beyond the file systems maximum file size.
This check should be done only for regular files, e.g. for
a device special file the test does not make sense.
Either we change the check or we have to write a llseek
I am trying to compile the 2.2.19 kernel one one machine for installation
on another. I believe I need to do more than just copy over bzImage and
modify lilo.conf, but I don't know what. Is there documentation somewhere
on how to do this? Thanks.
-
To unsubscribe from this list: send the
> linux_booted_ok(), called from init/main.c is not implemented on
> other architectures than Intel.
Yeah. I just need to drop null functions in. Im still not sure if that should
in fact be invoked from user space - say on hitting run level 3
-
To unsubscribe from this list: send the line
> On Tue, 19 Jun 2001, Alan Cox wrote:
> [..]
> > o Fix refclock build with newer gcc (Jari Ruusu)
>
> Is it mean now kernel 2.2 with prepatch is (or will be) gcc 3.0 ready ?
> If not what must be fixed/chenged to be ready ?
It wont build with gcc 3.0 yet. To start with gcc 3.0
On Tue, Jun 19, 2001 at 03:38:34PM -0400, Georg Nikodym wrote:
> > "GN" == Georg Nikodym <[EMAIL PROTECTED]> writes:
>
> > "MC" == Mike Castle <[EMAIL PROTECTED]> writes:
> MC> What about the "UNIX is starting to smell bad" comment? :->
>
> GN> I believe that it comes from a paper
> But that foregoes the point that the code is far more complex and
> harder to make 'obviously correct', a concept that *does* translate
> well to userspace.
Check the state threads library from SGI:
http://oss.sgi.com/projects/state-threads/
It should provide the code clarity one is used
On Tue, Jun 19, 2001 at 08:18:59PM +0100, Alan Cox wrote:
> > But that foregoes the point that the code is far more complex and harder to
> > make 'obviously correct', a concept that *does* translate well to userspace.
>
> There I disagree. Threads introduce parallelism that the majority of
> "GN" == Georg Nikodym <[EMAIL PROTECTED]> writes:
> "MC" == Mike Castle <[EMAIL PROTECTED]> writes:
MC> What about the "UNIX is starting to smell bad" comment? :->
GN> I believe that it comes from a paper that Pike presented at a
GN> OSDI (or the Usenix general) last year on the
On Tue, 19 Jun 2001, Larry McVoy wrote:
> OK, my corruption is back and this time I'm saving the data. Al, send some
> email when you are around, we can talk about access to the data. I'm tarring
Doing that.
> up both good & bad right now. I've looked at a few files and they look
>
> Which clearly marks you as a typical kernel-side developer :-) It never
> ceases to amaze me how different a userland perspective can be from that of
> people who live in kernel space.
I've been writing multiuser games since 1987. I'm not just a kernel hacker
> But that foregoes the point
With pre3 there are bugs introduced into mainline that are getting
extended to all architectures.
First of all nucking the handle_softirq from entry.S is wrong. ppc
copied without thinking and we'll need to resurrect it too for example
so please arch maintainers don't kill that check (alpha in
> Sometimes it takes either the kernel tree or our website some time to get
> in 'sync' with the latest driver version. The latest driver version is
> 1.02.00.007.
>
> There may be DAC960 like /proc support at some point for GUI haters.
Publishing enough info to let people write a GPL non
> How about "If you think you need threads, stop programming with closed
> sourced libraries where the documentation doesn't give you a clue how
> you might make things work within a state machine way"
Linux inherits several unix properties which are not friendly to good state
based programming
> how do the inode->i_dev, i_rdev fit into this?
These are what you see with stat(2).
i_dev gives the device the file is on
i_rdev is usually undefined, but for device special files
it gives the real device.
> Is there a set rule on when/where one should use a buffer head's
> b_dev and
Hi List,
Is there a way for a driver to ask kernel to
give DMA'able memory within 4GB ? I read about
pci_alloc_consistent(). But I could not find out
whether that guarantees the DMA'able memory to be
within 4GB or not. Is there any other kernel routine
that I should call from Driver to get such
> > I've got a strange situation, and I'm looking for a little direction.
> > Quick summary: I get sporadic lockups running 2.4.5-ac13 on a
> > ServerWorks HE-SL board (SuperMicro 370DE6), 2 800MHz Coppermine CPUs,
> > 512M RAM, 512M+ swap. Machine has 8 active disks, two as RAID 1,
> > 6 as
On Tue, Jun 19, 2001 at 08:01:00PM +0200, Kai Henningsen wrote:
> The funny thing here, Larry, is that to most people (who aren't OS gurus),
> Linux' clone or Plan 9's rfork *are* threads.
>
> I certainly agree that you don't necessarily need two different kernel-
> level kinds of things, but
Hi,
I have been working on a small patch to add support for AMD756 PCI IRQ
Routing with linux-2.4.5
This has been tested with a Gigabyte 7IXE 7F board and several PCI cards,
including a SMC-Lucent PCI Cardbus Bridge which doesn't get an IRQ
assigned by the BIOS.
If anybody has a board based
On Tue, 19 Jun 2001 [EMAIL PROTECTED] wrote:
> All of the md code looks like it copies the buffer head, setting
> b_dev=b_rdev="real device" in the new bh and leaving b_dev==b_rdev="logical
> device" in the original bh. I'm assuming they do this for a reason, but
> it would be nice from a
These are probably dumb questions but I haven't been able to find
definitive answers...
Is there a set rule on when/where one should use a buffer head's b_dev
and when/where one should use b_rdev?
I'm been tracing through the kernel source quite a bit and it seems like
above ll_rw_blk.c's
> "MC" == Mike Castle <[EMAIL PROTECTED]> writes:
MC> What about the "UNIX is starting to smell bad" comment? :->
I believe that it comes from a paper that Pike presented at a OSDI (or
the Usenix general) last year on the theme of OS Research being dead.
Links to it were also posted on /.
[EMAIL PROTECTED] (Larry McVoy) wrote on 19.06.01 in
<[EMAIL PROTECTED]>:
> Another one that I can't believe I forgot is from Rob Pike:
>
> "If you think you need threads then your processes are too fat"
>
> And one from me:
>
> ``Think of it this way: threads are like salt, not like
On 19 Jun 01 at 13:21, Richard B. Johnson wrote:
> On Tue, 19 Jun 2001, Timur Tabi wrote:
> > Oh, I see the problem. You could do something like this:
> >
> > cli
> > mov %0, %%eax
> > inc %%eax
> > mov %%eax, %0
> > sti
> >
> > and then return eax, but that won't work on SMP (whereas the
It was posted by Alan Cox where I now add my 0.02 EUR...
> > I was trying to compile 2.4.5 with gcc 3.0 but there is a problem
> > (conflicting type) between kernel/timer.c and include/linux/sched.h
> > Apparently the problem solves with this oneline workarond:
>
> Yep. Its fixed in the
Larry McVoy wrote:
>
> On Tue, Jun 19, 2001 at 10:20:37AM -0700, Mike Castle wrote:
> > On Tue, Jun 19, 2001 at 09:09:56AM -0700, Larry McVoy wrote:
> > > Another one that I can't believe I forgot is from Rob Pike:
> > >
> > > "If you think you need threads then your processes are too fat"
>
On Tue, Jun 19, 2001 at 10:37:12AM -0700, Larry McVoy wrote:
> On Tue, Jun 19, 2001 at 10:20:37AM -0700, Mike Castle wrote:
> > Also, I could never actually find the "too fat" quote anywhere.
>
> I can personally vouch for the too fat comment, I've heard him say it in
> person.
What about the
On Tue, Jun 19, 2001 at 10:36:00AM -0700, Jonathan Lundell wrote:
> At 9:09 AM -0700 2001-06-19, Larry McVoy wrote:
> >Don't you think it is funny that Sun doesn't publish numbers comparing
> >their thread performance to process performance? Sure, you can find
> >context switch benchmarks where
On Tue, Jun 19, 2001 at 10:20:37AM -0700, Mike Castle wrote:
> On Tue, Jun 19, 2001 at 09:09:56AM -0700, Larry McVoy wrote:
> > Another one that I can't believe I forgot is from Rob Pike:
> >
> > "If you think you need threads then your processes are too fat"
>
> Also, I could never
On Wed, Jun 20, 2001 at 12:43:02AM +1000, Keith Owens wrote:
> On Tue, 19 Jun 2001 16:35:20 +0200,
> Vojtech Pavlik <[EMAIL PROTECTED]> wrote:
> >On Wed, Jun 20, 2001 at 12:30:05AM +1000, Keith Owens wrote:
> >> Gameports and joysticks should not be available unless input core
> >> support is
At 9:09 AM -0700 2001-06-19, Larry McVoy wrote:
>Don't you think it is funny that Sun doesn't publish numbers comparing
>their thread performance to process performance? Sure, you can find
>context switch benchmarks where they have user level switching going on
>but those are a red herring. The
ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
Intermediate diffs are available from
http://www.bzimage.org
2.4.5-ac16
o Drop the shmem/removepage changes to see if they(me)
are cuaisng the instabilities in ac15
o Fix
On Tue, 19 Jun 2001, Timur Tabi wrote:
> ** Reply to message from "Petr Vandrovec" <[EMAIL PROTECTED]> on Tue, 19 Jun
> 2001 01:36:26 MET-1
>
>
> > No. Another CPU might increment value between LOCK INCL and
> > fetching v->counter. On ia32 architecture you are almost out of
> > luck. You can
On Tue, Jun 19, 2001 at 09:09:56AM -0700, Larry McVoy wrote:
> Another one that I can't believe I forgot is from Rob Pike:
>
> "If you think you need threads then your processes are too fat"
Pike also to have said, "Not only is UNIX dead, it's starting to smell bad."
Also, I could never
Hi !
I have a program that need to have a precision better than 1ms.
Is there any way to change the "tick" field of the "adjtimex" function
to reduce it under 1000 (reprogramming the RTC) ?
Friendly
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
I can understand the opinnions expressed by these quotes.
Having seen how horribly certain CORBA monsters work, I am sure
that the basic idea of threads is lost somewhere along the way...
On Tue, Jun 19, 2001 at 09:09:56AM -0700, Larry McVoy wrote:
> > > >--
> > > > "A Computer is a state
>
>Justin,
>When free memory is low, I get a series of aic7xxx messages followed by
>panic. It appears to be a race condition in the code.
Its actually a logic error, not a race condition. You should never
enter ahc_linux_run_device_queue() while the device is still on the
run queue. The real
On Tue, Jun 19, 2001 at 05:26:09PM +0100, Matthew Kirkwood wrote:
> On Tue, 19 Jun 2001, Larry McVoy wrote:
>
> > ``Think of it this way: threads are like salt, not like pasta. You
> > like salt, I like salt, we all like salt. But we eat more pasta.''
>
> This is oft-quoted but has,
[EMAIL PROTECTED] wrote:
>hi:
> I write a serial driver for linux , and have a personal test . I went
>to patch this driver into kernel
>but I don't know how to contact serial.c author ..
>can any one help me ?
> rich.liu
>
For
> patching file `drivers/scsi/sym53c8xx_defs.h'
> The next patch would create the file `drivers/sound/ad1848.c',
> which already exists! Assume -R? [n]
My error - just skip the ad1848.c segment
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Hi again,
On 19 Jun 2001, Jochen Striepe <[EMAIL PROTECTED]> wrote:
>
> Now it stops with
OK, this resolved to nothing (my mistake). Now it works fine. Until it
reaches
ld -m elf_i386 -T /usr/src/linux/arch/i386/vmlinux.lds -e stext
arch/i386/kernel/head.o
Le Tue, Jun 19, 2001 at 07:44:52PM +0400, Alexandr Andreev écrivait :
> David L. Parsley wrote
>
> Possibly, some symlinks are broken, or some libraries are missed, on my
> rootfs...
> But it is very strange, that ext2fs ramdisk image works with the same
> rootfs on it.
> I'll try to
Hi,
While I apply the patch pre-patch-2.2.20-4 to a clean 2.2.19 tree, I get
the following error :
patching file `drivers/scsi/sd_ioctl.c'
patching file `drivers/scsi/sym53c8xx.c'
patching file `drivers/scsi/sym53c8xx_defs.h'
The next patch would create the file `drivers/sound/ad1848.c',
which
Hi,
On 19 Jun 2001, Alan Cox <[EMAIL PROTECTED]> wrote:
>
> > sched.c:52: conflicting types for `xtime'
> > /usr/src/linux/include/linux/sched.h:509: previous declaration of `xtime'
>
> Stick a volatile in the declaration. Thats a real bug it found
Um...
I made it
extern volatile
** Reply to message from Alexander Viro <[EMAIL PROTECTED]> on Mon, 18 Jun 2001
19:45:11 -0400 (EDT)
> It depends on what kind of use 2.2 code had for it. There are several
> situations in which it used to be called and proper replacements depend
> on the context. Details, please...
We'll yes it's true you can program everything
like a state machine if the correct OS interfaces are
there. I don't think they are though ATM. Also
some things are more elegantly implemented using
threads, whereas others are better as state machines.
Padraig.
David S. Miller wrote:
>Dan Kegel
On Tue, Jun 19, 2001 at 08:58:20AM -0700, Dan Kegel wrote:
> [EMAIL PROTECTED] wrote:
> >
> > On an unrelated note:
> >
> > I noticed the quote below in your message. Is this a true quote or just a
> > joke going around? I have tried believing it is just a joke but I am
> > scared it is not.
>
1 - 100 of 310 matches
Mail list logo
