Hi!
> Everyone who says, disk is cheap, ought to donate me one.
> Everyone who says, memory is cheap, has to send me some.
>
> I'm still stuck with a P-133, 56 MB RAM (60-70 ns, some EDO,
> some FPM) and not only Linux but also W2K on a 2.1 and a 0.8 GB
> HDD.
>
> I accept donations in IDE and
WARNING!! Messages to linux-kernel are now being intercepted
(and answered) by this company:
On Fri, 2 Feb 2001 [EMAIL PROTECTED] wrote:
My message was sent directly to linux-kernel, with no cc address.
It should not have gone anywhere else.
On Fri, 2 Feb 2001 [EMAIL PROTECTED] wrote:
> Your
Hi!
> I am asking because I have just ordered a new drive for my Vaio (8.1 gig
> in a 8.45mm drive!) and I want to install 2.4.x on it. (I like getting
8.1GB in under centimeter? That's 8.1GB in compactflash slot?
Pavel
--
I'm [EM
Hi!
This fixes units, and makes format tag: value. Please apply.
Pavel
--- clean/drivers/acpi/cmbatt.c Wed Jan 31 16:14:26 2001
+++ linux/drivers/acpi/cmbatt.c Thu Feb 1 10:55:31 2001
@@ -246,38 +254,32 @@
goto end;
Hi!
> > It's not an incompatibility with the k7 chip, just bad code in
> > include/asm-i386/string.h.
>
> So you're saying SMP *is* supported on Athlon? Do motherboards exist?
Check today's slashdot ;-).
Pavel
--
I'm [EMAIL PROTE
On 2 Feb 01 at 14:44, Richard B. Johnson wrote:
> # rm *
> rm: cannot remove `#1006': Value too large for defined data type
> rm: cannot remove `#1057': Value too large for defined data type
> rm: cannot remove `#1140': Value too large for defined data type
> ls: #588: Value too large for define
On Fri, 2 Feb 2001, Helge Hafting wrote:
> "Michael B. Trausch" wrote:
> [...]
> > DevFSd provides symlinks as follows:
> >
> > /dev/ttyS0 = /dev/tts/0
> > /dev/tty0 = /dev/vc/0
> > /dev/pty* = /dev/pty/*
> >
> > Until programs use the new names (e.g., init should tell g
On Fri, 2 Feb 2001, Petr Vandrovec wrote:
> On 2 Feb 01 at 14:44, Richard B. Johnson wrote:
>
> > # rm *
> > rm: cannot remove `#1006': Value too large for defined data type
> > rm: cannot remove `#1057': Value too large for defined data type
> > rm: cannot remove `#1140': Value too large for d
On Fri, Feb 02, 2001 at 02:51:58PM -0500, Richard B. Johnson wrote:
>
> WARNING!! Messages to linux-kernel are now being intercepted
> (and answered) by this company:
> On Fri, 2 Feb 2001 [EMAIL PROTECTED] wrote:
>
> My message was sent directly to linux-kernel, with no cc address.
> It should n
Hi,
I backup my linux partition once a month from my second IDE drive to an
empty partition
on the first IDE disk. I have about 2.8 Gig to copy, and I use to do the copy.
While cp is copying from the second hard disk to the first hard disk,
I find my system performance
drop VERY sharply
Delta <[EMAIL PROTECTED]> writes:
> While cp is copying from the second hard disk to the first hard disk,
> I find my system performance
> drop VERY sharply. X is sloppy, even bash takes many seconds to
> respond. I using two
> recent IDE disk (Fudjisu 13 gig, Maxtor 20 Gig), so I'm wondering w
Ben,
- first of all, great patch! I've got a conceptual question: exactly how
does the AIO code prevent filesystem-related scheduling in the issuing
process' context? I'd like to use (and test) your AIO code for TUX, but i
do not see where it's guaranteed that the process that does the aio does
On Fri, 2 Feb 2001, Delta wrote:
> Hi,
>
> I backup my linux partition once a month from my second IDE drive to an
> empty partition
> on the first IDE disk. I have about 2.8 Gig to copy, and I use /mnt/hd> to do the copy.
>
# cd / ; nice -n 20 tar -clf - . | (cd /mnt/hd; tar -xpf -)
Will p
Hi,
Following is the current state of my CPU capabilities rework. It
introduces a new global variable, common_x86_capability, which holds the
common set of flags for CPUs. The boot_cpu_data is used appropriately
again, i.e. it's treated as current_cpu_data before smp_store_cpu_info()
is called
> "MBT" == Michael B Trausch <[EMAIL PROTECTED]> writes:
MBT> Is this fixable the "right" way?
On my box, which started its life as a RH7, I've been editing
/etc/security/console.perms as I've discovered problems.
I don't know if this is the right way but thus far I've:
- changed the li
I'm not sure whether this problem is related
to 2.4 kernel.
I've installed kernels 2.4.0-prex to 2.4.1 on
the following machines. All are now running 2.4.1.
Judging from my past experience posting here I'm giving much
information
- compaq prolinea p-90 de4x5 driver 1 gig quantum drive cmd 640
Hi there,
I like what you have done here, but there are a few things...
> diff -up --recursive --new-file linux-2.4.0-ac12.macro/include/asm-i386/bugs.h
>linux-2.4.0-ac12/include/asm-i386/bugs.h
> --- linux-2.4.0-ac12.macro/include/asm-i386/bugs.h Sun Jan 28 09:41:20 2001
> +++ linux-2.4.0
At 1:51 pm + 2/2/2001, Pavel Machek wrote:
>Hi!
>
>> I am asking because I have just ordered a new drive for my Vaio (8.1 gig
>> in a 8.45mm drive!) and I want to install 2.4.x on it. (I like getting
>
>8.1GB in under centimeter? That's 8.1GB in compactflash slot?
In general, i think the nor
Hey Ingo,
On Fri, 2 Feb 2001, Ingo Molnar wrote:
> - first of all, great patch! I've got a conceptual question: exactly how
> does the AIO code prevent filesystem-related scheduling in the issuing
> process' context? I'd like to use (and test) your AIO code for TUX, but i
> do not see where it's
Linux Kernel,
Version 1.1-5 of the Dolphin PCI-SCI (Scalable Coherent Interface) drivers
for Linux kernels 2.2.X and 2.4.X have been posted at
vger.timpanogas.org:/sci. These drivers are freely
available under the GNU public License and are provided in both
RPM and tar.gz format.
NOTES:
On 02.02 Christoph Rohland wrote:
> "H. Peter Anvin" <[EMAIL PROTECTED]> writes:
>
> > What happened with this being a management tool for shared memory
> > segments?!
>
> Unfortunately we lost this ability in the 2.4.0-test series. SYSV shm
> now works only on an internal mounted instance and
On Friday, February 02, 2001 03:36:18 PM -0500 [EMAIL PROTECTED]
wrote:
> I'm not sure whether this problem is related
> to 2.4 kernel.
>
I suspect it is a reiserfs problem, and that you are using lilo older than
21.6. Are you mounting /boot with -o notail?
Regardless, I'm willing to bet up
"J . A . Magallon" wrote:
>
> On 02.02 Christoph Rohland wrote:
> > "H. Peter Anvin" <[EMAIL PROTECTED]> writes:
> >
> > > What happened with this being a management tool for shared memory
> > > segments?!
> >
> > Unfortunately we lost this ability in the 2.4.0-test series. SYSV shm
> > now works
Hi guys,
I guess I'm doing something stupid, so please can somebody point it out
and put me out of my misery ?
Copied a plain 2.4.0 tree to a new directory, patched it to 2.4.1 without
any errors. Then I realised it had all the object files from my last
compile, so I thought "make mrproper" w
On Fri, 2 Feb 2001, Roeland Th. Jansen wrote:
> ok, just loaded 2.4.1 again with Maciej's patch. works fine but here too
> -- flood ping kills the ethernet stuff in a few seconds. in fact, within
> approx 800 interrupts. the god news is that teh system stays alive, just
> as with Alan's -ac1 vers
Can't view pictures in console with zgv or seejpeg
root@virii:/home/virii/images# seejpeg logo.jpg
svgalib: mmap error in paged screen memory.
root@virii:/home/virii/images# zgv logo.jpg
svgalib: mmap error in paged screen memory.
2.4.1 same problem in 2.4.0
svgalib: mmap error in paged scre
Kernel version is 2.4.1. For versions of cdrecord later than 1.6.1
(1.8.1 through the latest 1.10 alpha verified), attempting to burn a
CD results in a SCSI error of some kind. Here's some representative
output from a "dummy" burn session with cdrecord-1.9:
Calling: /usr/local/lib/xcdroast-0.9
On Fri, 2 Feb 2001, Ingo Oeser wrote:
> On Fri, Feb 02, 2001 at 08:24:19PM +0100, Mike Galbraith wrote:
> > On Fri, 2 Feb 2001, Ingo Oeser wrote:
> > > No, so have to unlock it also, if you return -ENOSPC.
> > >
> > > So the correct fix seems to be:
> [...]
> > > This currently works for me (but
On Fri, Feb 02, 2001 at 08:24:19PM +0100, Mike Galbraith wrote:
> On Fri, 2 Feb 2001, Ingo Oeser wrote:
> > No, so have to unlock it also, if you return -ENOSPC.
> >
> > So the correct fix seems to be:
[...]
> > This currently works for me (but using 2.4.0 + dwg-ramfs.patch + this patch)
>
> Have
Alan Cox wrote:
>
> > So, did Linus say no? If not, let's ask him with a patch. Quite simply,
> > neither we nor the users should be burdened with this, and the patch removes
> > the burden.
>
> Since egcs-1.1.2 and gcc 2.95 miscompile the kernel strstr code dont forget
> to stop those being u
On Fri, 2 Feb 2001, Ken Moffat wrote:
> Hi guys,
> I guess I'm doing something stupid, so please can somebody point it out
> and put me out of my misery ?
>
> Copied a plain 2.4.0 tree to a new directory, patched it to 2.4.1 without
> any errors. Then I realised it had all the object files f
On Fri, 2 Feb 2001, Mark Hahn wrote:
> > I guess I'm doing something stupid, so please can somebody point it out
> > and put me out of my misery ?
>
> don't use cp to copy kernel trees unless you use -s.
>
Thanks for the advice, Mark. I'll give it a go in a minute (got to log off
this box and
On Fri, 2 Feb 2001 16:46:45 + (GMT), Alan Cox <[EMAIL PROTECTED]> wrote:
>> :It is the original one. I'll try with the -69:
>> :
>> With 2.96-69 the reiserfs seems to work well.
>> Sorry for the confusion, I forgot to upgrade the gcc on my machine.
>
> Excellent. Im just glad to kno
> Users cannot use gcc 2.96 as shipped in RedHat 7.0 if they want to use
> reiserfs. It is that simple. How can you even consider defending allowing the
> use of it without requiring a positive affirmation by the user that they don't
> know what they are doing and want to do it anyway?:-) I cou
My last comment on this...
It makes sense to refuse to build a piece of the kernel if it break's
a machine - anything else is a timebomb waiting to explode.
I feel politics are at play here...I don't really care who's bug it is -
all I know is using pre 2.96 fixes it and everyone needs to be a
> It makes sense to refuse to build a piece of the kernel if it break's
> a machine - anything else is a timebomb waiting to explode.
The logical conclusion of that is to replace the entire kernel tree with
#error "compiler or program might have a bug. Aborting"
The kernel is NOT some US home
Finally, after many crashes which I have not been able to capture,
here is two Oops'es which I have transfered by hand from my one
machine to another. Solid lockup I am afraid, only thing working
was Alt-SysRq keys.
# Oops #1 follows
Unable to handle kernel paging request at virtual address 5
Linux Kernel,
(Sorry, had one more change that did not make the patch. this release
contains the corrected patch).
Version 1.1-6 of the Dolphin PCI-SCI (Scalable Coherent Interface) drivers
for Linux kernels 2.2.X and 2.4.X have been posted at
vger.timpanogas.org:/sci. These drivers are fre
Lets not go overboard Alan ;-)
> > It makes sense to refuse to build a piece of the kernel if it break's
> > a machine - anything else is a timebomb waiting to explode.
>
> The logical conclusion of that is to replace the entire kernel tree with
>
> #error "compiler or program might have a bug
> Copied a plain 2.4.0 tree to a new directory, patched it to 2.4.1 without
> any errors. Then I realised it had all the object files from my last
> compile, so I thought "make mrproper" was called for. It did a little,
> then
You copied the link and turned it into its contents
> rm: include/as
Dick, and Mark, thanks. It's compiling nicely now. We learn by experience.
Cheers, Ken
> Not to worry. In your new Linux directory tree do:
>
> cd include
> mv asm /tmp # or /usr/src, someplace temporary.
>
> cd .. # Back to Linux
> cp .config .. # Save your configuration
> make mrpro
> Alan, I'm sending it to you and not to Linus, as ac1 contains newer
> matroxfb than Linus tree and doing otherwise would make your work harder
> without any reason. But please make sure that Linus's 2.4.2 will contain
> this fix.
I can try. You might want to send him the stuff too though 8)
-
> As it stands, there is no way to determine programatically whether
> gcc-2.96 is broken or now. The only way to do it is to check the RPM
> version -- which, needless to say, is a bit difficult to do from the
> C code about to be compiled. So I can't really blame Hans if he decides
> to outlaw g
I have a quick question regarding the ethertap device and routing. We're seeing
the contents of the packet coming up through the ethertap device just fine, but
the originating address seems to be overwritten with the ethertap device's
address.
Am I missing something obvious here? I'm positive
Alan Cox wrote:
>
> > Users cannot use gcc 2.96 as shipped in RedHat 7.0 if they want to use
> > reiserfs. It is that simple. How can you even consider defending allowing the
> > use of it without requiring a positive affirmation by the user that they don't
> > know what they are doing and want
On Fri, Feb 02, 2001 at 09:57:39PM +, Alan Cox wrote:
: > As it stands, there is no way to determine programatically whether
: > gcc-2.96 is broken or now. The only way to do it is to check the RPM
: > version -- which, needless to say, is a bit difficult to do from the
: > C code about to be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wednesday, Richard B. Johnson ([EMAIL PROTECTED]) wrote:
> Now just a cotton-picken minute. When was the last time you
> accessed that site? I spent most of last night looking through
> EMPTY directories with files that are invisible to ftp but
Alan Cox wrote:
>
> > As it stands, there is no way to determine programatically whether
> > gcc-2.96 is broken or now. The only way to do it is to check the RPM
> > version -- which, needless to say, is a bit difficult to do from the
> > C code about to be compiled. So I can't really blame Hans
Alan Cox wrote:
>
> > my convenience matters as much as that of the users. I don't want to use
> > #ifdefs, I want it to die explosively and verbosely informatively. make isn't
> > the most natural language for that, but I am sure Yura can find a way.
>
> Run a small shell check and let it fai
> OK, following the reiserfs/compiler thread, I can see now that my bug report
> may have been ignored since I was using a non-kosher compiler (although I
> have used it since late October -99 without any problems). Or, it might not
> have been ignored, just nobody told me he/she wasted some time
- Original Message -
From: "Peter 'Luna' Runestig" <[EMAIL PROTECTED]>
To: "Linux Kernel Mailing list" <[EMAIL PROTECTED]>
Sent: Wednesday, January 24, 2001 7:29 PM
Subject: PROBLEM: 2.2.19pre7 opps on low mem machine
> [1.] One line summary of the problem:
> Oops with 2.2.19pre7 on memo
Hi,
I was trying 2.4.1 kernel but under some IO load (bonnie++)
DMA gets disabled with following messages:
hda: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hda: timeout waiting for DMA
I have a box with:
a couple of analog ISA modem cards in it which have 8 modems a piece
the modems use devices ttyS4-19
a realtek 8039 pci ethernet card (100 mbit)
486 dx
Its running redhat 6.2 and a 2.2.17 kernel with ppp ip-forwarding
ip aliasing and ip masq support.
The kernel is p
> > their kernel, something putting #ifdefs all over it will mean they have to
> > mess around to fix too.
> >
> A moment of precision here. We won't test to see if the right compiler is used,
> we will just test for the wrong one.
Ok that makes a lot more sense
-
To unsubscribe from this list
> my convenience matters as much as that of the users. I don't want to use
> #ifdefs, I want it to die explosively and verbosely informatively. make isn't
> the most natural language for that, but I am sure Yura can find a way.
Run a small shell check and let it fail if the shell stuff errors.
Gérard Roudier wrote:
>
> So, why not using a pure software flag in memory and only tampering the
> things if the offending interrupt is actually delivered ? If the given
> interrupt is delivered and the software mask is set we could simply do:
>
> - MASK the given interrupt
> - EOI it.
> - retu
On Fri, 2 Feb 2001, Alan Cox wrote:
> Oh I can see why Hans wants to cut down his bug reporting load. I can also
> say from experience it wont work. If you put #error in then everyone will
> mail him and complain it doesnt build, if you put #warning in nobody will
> read it and if you dont put an
Alan Cox wrote:
>
> > It makes sense to refuse to build a piece of the kernel if it break's
> > a machine - anything else is a timebomb waiting to explode.
>
> The logical conclusion of that is to replace the entire kernel tree with
>
> #error "compiler or program might have a bug. Aborting"
N
On Fri, 2 Feb 2001, Pavel Machek wrote:
> Hi!
>
> > I am asking because I have just ordered a new drive for my Vaio (8.1 gig
> > in a 8.45mm drive!) and I want to install 2.4.x on it. (I like getting
>
> 8.1GB in under centimeter? That's 8.1GB in compactflash slot?
Standard laptop drive size
Alan Cox wrote:
>
> > > their kernel, something putting #ifdefs all over it will mean they have to
> > > mess around to fix too.
> > >
> > A moment of precision here. We won't test to see if the right compiler is used,
> > we will just test for the wrong one.
>
> Ok that makes a lot more sense
On Fri, 2 Feb 2001 16:39:18 -0500 (EST),
Alan Cox <[EMAIL PROTECTED]> wrote:
>Large numbers of people routinely build the kernel with 'unsupported' compilers
gcc version 2.96-ia64-000717 snap 001117 - works for me doing cross
compile from ia32 to ia64. Anybody adding #ifdef, please include thi
Richard B. Johnson writes:
> WARNING!! Messages to linux-kernel are now being intercepted
> (and answered) by this company:
> On Fri, 2 Feb 2001 [EMAIL PROTECTED] wrote:
>
> My message was sent directly to linux-kernel, with no cc address.
> It should not have gone anywhere else.
I've rem
On Sat, 3 Feb 2001, Hans Reiser wrote:
> That said, my opinion is that bug reporting load is not as important as bug
> avoidance, but I understand your position has merit to it also.
If you do it, at least restrict it to 2.96.0. Maybe Red Hat will see the
light and release a fixed 2.96.1...
Ion
On Sat, Feb 03, 2001 at 01:03:00AM +0300, Hans Reiser wrote:
> My design objective in ReiserFS is not to say that it wasn't my fault they had
> that bug because they are so ignorant about a filesystem that
> really isn't very important to them unless it screws up. My design objective is
> to ensu
Hello,
The system is as follows:
- Intel CA810EAL motherboard (built-in EtherExpress Pro 10/100)
- 128MB RAM
- 10GB IDE HD (Western Digital WD100)
- Linux kernel 2.2.18
Sometimes when I reboot the system, as soon as the eepro100 module is
loaded, I start to get these msgs on the screen:
eth0:
Hello,
The system is as follows:
- Intel CA810EAL motherboard (built-in EtherExpress Pro 10/100)
- 128MB RAM
- 10GB IDE HD (Western Digital WD100)
- Linux kernel 2.2.18
Sometimes when I reboot the system, as soon as the eepro100 module is
loaded, I start to get these msgs on the screen:
eth0:
I had some problems while compiling some applications
with the 2.4.0 kernel.
The problem was a conflict between string.h from the libc
and the one from the kernel, which is included in fs.h
So, using and at the same time
brings some conflicts.
It seems to me that should not be apparent
from u
David Lang writes:
> 1a. for webservers that server static content (and can therefor use
> sendfile) I don't see this as significant becouse as your tests have been
> showing, even a modest machine can saturate your network (unless you are
> useing gigE at which time it takes a skightly large
On Fri, 2 Feb 2001, Benjamin LaHaise wrote:
> Thanks! Right now the code does the page cache lookup allocations and
> lookups in the caller's thread, [...]
(the killer is not the memory allocation(s), if there is enough RAM then
we can get a free page without having to block.)
The real problem
Benjamin LaHaise wrote:
>
> Hey Ingo,
>
> On Fri, 2 Feb 2001, Ingo Molnar wrote:
>
> > - first of all, great patch! I've got a conceptual question: exactly how
> > does the AIO code prevent filesystem-related scheduling in the issuing
> > process' context? I'd like to use (and test) your AIO co
On Sat, 03 Feb 2001 00:04:16 +0100,
Jocelyn Mayer <[EMAIL PROTECTED]> wrote:
>I had some problems while compiling some applications
>with the 2.4.0 kernel.
>The problem was a conflict between string.h from the libc
>and the one from the kernel, which is included in fs.h
Rule 1. Applications mu
On Fri, 2 Feb 2001, Rajagopal Ananthanarayanan wrote:
> Do you really have worker threads? In my reading of the patch it seems
> that the wtd is serviced by keventd. [...]
i think worker threads (or any 'helper' threads) should be avoided. It can
be done without any extra process context, and i
On Fri, 2 Feb 2001 15:01:05 -0800 (PST), Ivan Passos <[EMAIL PROTECTED]> wrote:
> Sometimes when I reboot the system, as soon as the eepro100 module is
> loaded, I start to get these msgs on the screen:
>
> eth0: card reports no resources.
> eth0: card reports no RX buffers.
> eth0: card reports
David Lang writes:
> right, assuming that there is enough sendfile() benifit to overcome the
> write() penalty from the stuff that can't be cached or sent from a file.
>
> my question was basicly are there enough places where sendfile would
> actually be used to make it a net gain.
There a
On 02.02 Hans Reiser wrote:
> Alan Cox wrote:
> > Run a small shell check and let it fail if the shell stuff errors.
> >
> > The fragment you want is
> >
> > if [ -e /bin/rpm ]; then
> > X=`rpm -q gcc`
> > if [ "$X" = "gcc-2.96-54" ]; then
> > echo "*** GCC 2.96-
On Fri, 2 Feb 2001, Maciej W. Rozycki wrote:
>
> Following is the current state of my CPU capabilities rework. It
> introduces a new global variable, common_x86_capability, which holds the
> common set of flags for CPUs. The boot_cpu_data is used appropriately
> again, i.e. it's treated as cur
I would agree with you, and I was about to write something saying that trusting
that rpm is installed is bad, except that then I realized, only RedHat made this
error, and only RedHat installs need this protection.
Now, if we want to have a more general bad gcc's list, and we envision this code
e
On 02.02 H. Peter Anvin wrote:
> "J . A . Magallon" wrote:
> >
> > On 02.02 Christoph Rohland wrote:
> > > "H. Peter Anvin" <[EMAIL PROTECTED]> writes:
> > >
> > > > What happened with this being a management tool for shared memory
> > > > segments?!
> > >
> > > Unfortunately we lost this abilit
On 02.02 Ken Moffat wrote:
> Hi guys,
> I guess I'm doing something stupid, so please can somebody point it out
> and put me out of my misery ?
>
> Copied a plain 2.4.0 tree to a new directory, patched it to 2.4.1 without
> any errors. Then I realised it had all the object files from my last
Michael H. Warfield writes:
> On Fri, Feb 02, 2001 at 03:36:46PM -0800, David S. Miller wrote:
> So block them using the /etc/mail/access database for sendmail
> and do it with a "451" error code. The data will back up on their
> mail server and start clogging their mail spool till they
Hi,
Unfortunately you are too right. It appears that the "!!!HACK,HACK,HACK!!!
2048 is only assumed" line is gone in 2.4.1, but is back in 2.4.1-ac1. Can
this be fixed?
Regards,
infernix
- Original Message -
From: "Kai Germaschewski" <[EMAIL PROTECTED]>
To: "infernix" <[EMAIL PROTECTED
On Sat, Feb 03, 2001 at 12:40:03AM +0100, J . A . Magallon wrote:
> Please, do not do so. That depends on the PACKAGE name and version, and there
> is no standard way of versioning a patched gcc.
> The -54 is a RH'ism, for example Mandrake Cooker includes patches from
> different sources, and gcc
I've countless web searches and linux-kernel archives, but I haven't yet
found the answer to my question.
I'm porting some software to Linux that requires use of a bidirectional,
named pipe. The architecture is as follows: A server creates a named pipe
in the /tmp directory. Any client can th
On Fri, 2 Feb 2001, H. Peter Anvin wrote:
>
> > diff -up --recursive --new-file linux-2.4.0-ac12.macro/include/asm-i386/bugs.h
>linux-2.4.0-ac12/include/asm-i386/bugs.h
> > --- linux-2.4.0-ac12.macro/include/asm-i386/bugs.h Sun Jan 28 09:41:20 2001
> > +++ linux-2.4.0-ac12/include/asm-i386/
Ingo Molnar wrote:
>
> On Fri, 2 Feb 2001, Rajagopal Ananthanarayanan wrote:
>
> > Do you really have worker threads? In my reading of the patch it seems
> > that the wtd is serviced by keventd. [...]
>
> i think worker threads (or any 'helper' threads) should be avoided. It can
> be done witho
On Fri, 2 Feb 2001, David S. Miller wrote:
>
> Richard B. Johnson writes:
> > WARNING!! Messages to linux-kernel are now being intercepted
> > (and answered) by this company:
> > On Fri, 2 Feb 2001 [EMAIL PROTECTED] wrote:
> >
> > My message was sent directly to linux-kernel, with no cc ad
Thanks, that info on sendfile makes sense for the fileserver situation.
for webservers we will have to see (many/most CGI's look at stuff from the
client so I still have doubts as to how much use cacheing will be)
David Lang
On Fri, 2 Feb 2001, David S. Miller wrote:
> Date: Fri, 2 Feb 2001 14:
David Lang writes:
> Thanks, that info on sendfile makes sense for the fileserver situation.
> for webservers we will have to see (many/most CGI's look at stuff from the
> client so I still have doubts as to how much use cacheing will be)
Also note that the decreased CPU utilization resulting
On Fri, Feb 02, 2001 at 02:58:14PM -0800, [EMAIL PROTECTED] wrote:
> Now, it seems to me, as long as the ReiserFS folks are going to be getting the
> bulk of the extra work(/mail/whatever) out of this, and they've been advised
> of the risks to their own person and are ok with that (which they
Perhaps man 2 mkfifo ?
On 02.03 "Miller, Brendan" wrote:
>
> I've countless web searches and linux-kernel archives, but I haven't yet
> found the answer to my question.
>
> I'm porting some software to Linux that requires use of a bidirectional,
> named pipe. The architecture is as follows: A
Hi Udo!
On Thu, 01 Feb 2001, Udo A. Steinberg wrote:
>
> Hi all,
>
> With all the latest kernels (at least since 2.4.0-test12)
> I have had occasional problems with a PS/2 keyboard when
> switching back and forth between X and text consoles.
>
> In most cases the problem occurs when switching
On 2 Feb 2001, at 20:17, Urban Widmark wrote:
>
> > >I did this and compiled it into the kernel. It detects it at boot
> > >(via- rhine v1.08-LK1.1.6 8/9/2000 Donald Becker) but says the
> > >hardware address (mac address?) is 00-00-00-00-00-00.
>
> This is a good example of what is missed by no
right, assuming that there is enough sendfile() benifit to overcome the
write() penalty from the stuff that can't be cached or sent from a file.
my question was basicly are there enough places where sendfile would
actually be used to make it a net gain.
David Lang
On Fri, 2 Feb 2001, David S. M
Let's see all the work being done for clustering would definitely
benefit... all the static images on your webserver--and static images
makes up most of the bandwidth from web servers (images, activeX controls,
java apps, sound clips...)... NFS servers, Samba servers (both of which
are used m
Ok, it seems somebody is running a cron script or similar
to keep resubscribing that [EMAIL PROTECTED] address
to linux-kernel.
So if you see the "moderation" message back from a posting
you make to linux-kernel, please dont' report it to us here
at vger.kernel.org, we know about it.
Later,
Dav
I thought mkfifo was only unidirectional...
Brendan
Please cc: me personally, as I am not subscribed.
-Original Message-
From: J . A . Magallon [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 02, 2001 4:47 PM
To: Miller, Brendan
Cc: 'linux-kernel @ vger . kernel . org'
Subject: Re: bi
Hugh Dickins wrote:
>
> I wonder (you or hpa may very quickly point out why this is stupid
> and impossible), could we move the identify_cpu() calls into
> cpu_init()? I used to think it was called too early for that, but
> now I see it's already using current, smp_processor_id(), printk().
>
On Fri, 2 Feb 2001, Ion Badulescu wrote:
> On Fri, 2 Feb 2001 15:01:05 -0800 (PST), Ivan Passos <[EMAIL PROTECTED]> wrote:
>
> > Sometimes when I reboot the system, as soon as the eepro100 module is
> > loaded, I start to get these msgs on the screen:
> >
> > eth0: card reports no resources.
>
On Fri, Feb 02, 2001 at 03:36:46PM -0800, David S. Miller wrote:
> Ok, it seems somebody is running a cron script or similar
> to keep resubscribing that [EMAIL PROTECTED] address
> to linux-kernel.
So block them using the /etc/mail/access database for sendmail
and do it with a "451" err
On Thu, Feb 01 2001, Anders S. Buch wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello,
>
> It seems that the ide/cdrom/amd756 code can cause some bad lockups, at
> least on my system. I have an Athlon 500 system running the 2.4.1 kernel
> with Redhat 6.1 + updated modutils, etc
101 - 200 of 234 matches
Mail list logo
