[PATCH] DocBook Makefile, kernel 2.4.0-test8

Small patch to fix the DocBook Makefile. It looks like videodev.c moved from $(TOPDIR)/drivers/char/videodev.c to $(TOPDIR)/drivers/media/video/videodev.c kernel-2.4.0-test8 -- Bob Tanner <[EMAIL PROTECTED]> | Phone : (612)943-8700 http://www.mn-linux.org | Fax :

Re: byte order of IDE identify data on ppc, sparc etc

Hi Andries, I truly understand the pain, with my new PPC that was a gift from a PPC user that want ATA native and strong it is a mess. I am fearing the task that you are wanting to chase, but if you can streamline it and it works :-), you know that you have me backing the change. Cheers,

Update Linux 2.4 Status/TODO list

OK, here's the updated Linux 2.4 bug list. I let myself get a bit behind, so it took me a while to process through all of my backlogged l-k mail archives to assemble this list. As always, it's complete as I can make it, but it's not perfect. In particualar, some bugs listed on this page may

Centralising the duplicated do_profile functions

Hi gang, I'd like to submit a patch to Alan which removes the duplication of identical 'do_profile' functions in the 2.2 kernel, and adds the missing call to make kernel profiling work on the PPC architecture. Once 2.2 is done, I'll look at 2.4, which currently suffers the same problem, only

Re: Availability of kdb

On Tue, 12 Sep 2000, Jeff V. Merkey wrote: > > Ted, > > I am looking at these sources as well. One thing I went back and looked > at was related to a comment from Mike G. I believe regarding drivers > conflicts with int 0x13 requests potentially hosing the IDE driver. In Hmm.. must be a

Re: 2.2.18pre* CONFIG_AGP=Y compile problem

In article <[EMAIL PROTECTED]> you wrote: > Hello ! > There is error during "make bzImage" 2.2.18pre(3,4,5) with CONFIG_AGP=Y. > I have it on both Slackware 7.0 and 7.1. > Error message follows. [snip] > init/main.o: In function `do_basic_setup': > init/main.o(.text.init+0xe02): undefined

Re: Bug in block device read/write!

Date:Fri, 08 Sep 2000 03:41:27 +0100 From: Anton Altaparmakov <[EMAIL PROTECTED]> I have been trying to get the linear md driver to work with NTFS volumes for several months and it never worked. - I was suspecting the NTFS driver (after having fixed linear md and

Re: Signal handling different for root and others

jury gerold <[EMAIL PROTECTED]> wrote: > When i create a connection (telnet a.b.c.d port) the signal is > delivered depending on the user that does the telnet. > If root creates the socket, then only root or another machine > is able to trigger the signal by connecting to the socket. >

Re: Booting into /bin/bash

In article <[EMAIL PROTECTED]> you wrote: > I like this idea a lot (the latter - making /dev/console controlling > tty). On an old SunOS 4 machine I once worked with, a Ctrl-C during the > execution of rc.sysinit would sent it terminate signals. So when the > NFS was hanging on mount because

Re: Linux 2.2.18pre4

In article 8pmnfc$6p1$[EMAIL PROTECTED]> you wrote: > Think Alan has made that clear. The way I read things the nfsv2 stuff needs > to be split out, into sets of small independent patches. This lets Alan > audit and control any bad patches easily. The nfsv3 changes should not > effect

byte order of IDE identify data on ppc, sparc etc

While designing some disk utilities, I found it rather inconvenient that what the kernel gives back with the HDIO_GET_IDENTITY ioctl differs in obscure architecture- dependent ways from what one reads directly from disk. Looking at the kernel code, I find 26kB of byteswapping source code just

Re: 2.2 Backport Terminated ...

On Tue, Sep 12, 2000 at 04:31:07PM -0700, Andre Hedrick wrote: > Do to limits in personal bandwidth and other projects that need to get > done, I can no longer keep up the back port of the ATA code. Bummer. The 2.2.17 ide code doesn't work for me. I used to use 2.2.15pre15 with ide. With

Re: Linux 2.2.18pre4

Horst von Brand wrote: > OK, OK, OK. It is by now abundantly clear that NFSv3 is a high-priority > item for lots of people out there. But just complaining about it not being > in the kernel just generates ill will. Think Alan has made that clear. The way I read things the nfsv2 stuff needs to

Re: Linux 2.2.18pre4

Alan Cox <[EMAIL PROTECTED]> said: > Subject: Re: Linux 2.2.18pre4 > > Return-Path: [EMAIL PROTECTED] > Delivery-Date: Tue Sep 12 20:33:05 2000 > Return-Path: <[EMAIL PROTECTED]> > In-Reply-To: <[EMAIL PROTECTED]> from "Paul > ***Jakma" at Sep 12, 2000 05:12:33 PM > > What are the issues

Re: Booting into /bin/bash

On Tue, 12 Sep 2000, Ion Badulescu wrote: > Maybe I'll play with main.c and see what happens if I force /dev/console > to become the controlling tty for init. Hmm... That could be dangerous for > init. Maybe a better idea would be to hack init so that it gives any > program started from inittab

Question about Bind Souce Code

Hi,all:     I was confused when I read Bind Source Code(9.0.0rc5).     It was in lib/isc/include/isc/types.h,line 62,said like below:     "typedef struct isc_mem isc_mem_t;" but I cant find any information about "struct isc_mem" anywhere,What's wrong?Is there anyone could

Re: elevator code

"Jeff V. Merkey" wrote: > > Martin, > > I'm glad you are not still mad at me. :-) I hope this info was > helpful. Yes it was in fact this one of the more interresting posts in this thread. Thanks for the excellent reading. (However much of it sounded very familiar... maybe they learned the

Re: Test 8 Kernel Unable to get the password prompt?

That's not correct .. the latest until-linux does not appear to fix the problem and there seems to be the same problem with PAM. Gerhard On Tue, 12 Sep 2000, Steven Walter wrote: > > If you're logging in as root, this is probably a result of the VT not > being named in

Re: [ANNOUNCE] Darkstar Development Project

CC: trimmed to just l-k. On Tue, 12 Sep 2000 10:02:59 +0200, Ralf Baechle <[EMAIL PROTECTED]> wrote: >From some random Linux source tree's .hdepend: > >/usr/people/ralf/src/linux/linux/include/asm/sn/sn0/ip27.h: \ > /usr/people/ralf/src/linux/linux/include/asm/mipsregs.h \ >

Re: Using Yarrow in /dev/random

Date:Wed, 13 Sep 2000 01:23:30 +0200 (CEST) From: Igmar Palsenberg <[EMAIL PROTECTED]> > No, not true. The mixing into the entropy pool uses a twisted LFSR, but > all outputs from the pool (to either /dev/random or /dev/urandom) > filters the output through SHA-1 as a

Re: Reorg raid5 block xor routines

On Wed, Sep 13, 2000 at 12:26:39AM +0100, Russell King wrote: > If its 15K, and you're compiling raid as modules, why can't this code > also be compiled as a module in the architecture tree? Last time I > looked, modprobe handled dependencies between modules. With the code as-is, you'd have

Re: 2.2 Backport Terminated ...

I will maintain 2.2 backport on (maybe) regular basis... On Tue, 12 Sep 2000, Andre Hedrick wrote: > > Greetings All, > > Do to limits in personal bandwidth and other projects that need to get > done, I can no longer keep up the back port of the ATA code. > > Things that are before me are : > >

Re: (reiserfs) Re: More on 2.2.18pre2aa2

Alan Cox wrote: > > time, but remember that there are two things measured in time here: > > A. The time for the whole queue of requests to run (this is what Rik is > > proposing using to throttle) > > B. The time an average request takes to process. > > Your perceived latency is based

Re: elevator code

Martin, I'm glad you are not still mad at me. :-) I hope this info was helpful. :-) Jeff Martin Dalecki wrote: > > "Jeff V. Merkey" wrote: > > > lessons learned in live customer accounts. In NetWare, requests are > > merged at A) the boundry between the File Cache and the I/O

Re: (reiserfs) Re: More on 2.2.18pre2aa2

Hans Reiser wrote: > > I really think Rik has it right here. In particular, an MP3 player needs to be able >to say, I have > X milliseconds of buffer so make my worst case latency X milliseconds. The number >of requests is > the wrong metric, because the time required per request depends on

Re: (reiserfs) Re: More on 2.2.18pre2aa2

> time, but remember that there are two things measured in time here: > A. The time for the whole queue of requests to run (this is what Rik is > proposing using to throttle) > B. The time an average request takes to process. Your perceived latency is based entirely on A. > If we limit

Re: elevator code

"Jeff V. Merkey" wrote: > lessons learned in live customer accounts. In NetWare, requests are > merged at A) the boundry between the File Cache and the I/O subsystem, > and B) in the drivers themselves and NOT THE ELEVATOR. Yes that's the proper place to do this. The generic elevator on a

Re: Linux 2.2.18pre6

Alan Cox wrote: > [AH>>] > > larger ide-patch. What is it going to take to just accept it? > > I'd prefer to do it bit by bit, driver by driver without touching the core > and picking the important and stable drivers first. On one machine, I have applied ide-2.2.17.all.2904.patch just to

2.2.18pre6

Alan I don't know if you received my message about ATI Mach64/FB but if not 2.2.17pre14 was the last working kernel for me. FYI only, I can live with pre14. :-) Bob - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please

Re: (reiserfs) Re: More on 2.2.18pre2aa2

Alan Cox wrote: > > Now, I see people trying to introduce the concept of elapsed time into > > that fix, which smells strongly of hack. How will this hack be cobbled > > Actually my brain says that elapsed time based scheduling is the right thing > to do. No, Andrea is right here. The argument

Re: (reiserfs) Re: More on 2.2.18pre2aa2

Andrea Arcangeli wrote: > > On Tue, 12 Sep 2000, Martin Dalecki wrote: > > >First of all: In the case of the mp3 player and such there is already a > >fine > >proper way to give it better chances on getting it's job done smooth - > >RT kernel sceduler priorities and proper IO buffering. I did

2.2 Backport Terminated ...

Greetings All, Do to limits in personal bandwidth and other projects that need to get done, I can no longer keep up the back port of the ATA code. Things that are before me are : Finish Stablity of 2.4.0 Finish CASCADE for 2.4.0 and introduction @ ALS 8 drives

Re: 2.4.0-test8 and ssh (OpenSSH_2.1.1): error: socket: Address family not supported by protocol

It looks like this one's a ssh issue. If you haven't already gotten it resolved, take a look at ... there's a patch which should take care of it. PGP signature

Re: More on 2.2.18pre2aa2 (summary of elevator ideas)

One important point on remirroring I did not mention in my post. In NetWare, remirroring scans the disk BACKWARDS (n0) to prevent artificial starvation while remirring is going on. This was another optimization we learned the hard way by trying numerous approaches to the problem. Jeff Ed

Re: Reorg raid5 block xor routines

On Mon, Sep 11, 2000 at 08:48:24AM -0700, Linus Torvalds wrote: > - Please split this up the same way the checksums were split up: >make the xor routine be an architecture-dependent library thing, with >the "generic" slow one possibly just a regular library thing. This is simple enough

OOPS: [Fwd: 2.4.0-test8 oops in ll_rw_blk.c:711]

Whoops, sent this to the old adress by accident Hi, [1.] Kernel oops while using netscape in X [2.]The following oops occured as netscape messenger was attempting to read my INBOX. Normal X usage (a few xterms, netscape, emacs, xmms), [3.] kernel ll_rw_blk.c [4.] 2.4.0-test8 Using

Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee

Trond Myklebust writes: > Relying on the sub-second timing fields is a much more > implementation-specific. It depends on the capabilities of both the > filesystem and the server OS. > Linux and the knfsd server code could easily be modified to provide > such a service, but the problem (as I've

Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee

On Tue, Sep 12, 2000 at 09:10:56PM +0200, Trond Myklebust wrote: > Making mtime a true 64-bit cookie on Linux servers would be a solution > that works on all clients. Making mtime 64bit would also be useful for local parallel make runs, the current second resolution leads to race conditions on

Re: More on 2.2.18pre2aa2 (summary of elevator ideas)

Hi, Geez, A simple comment on IRC can _really_ generate lots of feedback. (There were over 50 messages about this in my queue - did not help that some were duplicated three times ). I made the comment because I remember back when the discussion was current on linux kernel. I thought Jeff

Re: Test 8 Kernel Unable to get the password prompt?

On Tue, Sep 12, 2000 at 03:34:22PM +, Steven Walter wrote: > If you're logging in as root, this is probably a result of the VT not > being named in /etc/securetty. Devfsd mucks up the names, so you can > either include "1," which would allow root logins from pseudo-terminals > and other

Re: Linux 2.2.18pre6

> I see you parse-pieces for the 2.4 code as backports into 2.2 of the > larger ide-patch. What is it going to take to just accept it? I'd prefer to do it bit by bit, driver by driver without touching the core and picking the important and stable drivers first. > I am considering the pull of

Re: Linux 2.2.18pre4

Paul Jakma wrote: > alan seems to {want,prefer} small incremental/'obvious fix' patches. > but that isn't practically possible anymore. It would mean the NFS > guys would effectively have to redo the entire development cycle of > code they have written over the last year. [...] > So it is now at

Re: Recurring Oops in 2.2.12-20smp plus ext2_free_blocks.

> If it was hardware, say one of the two processors was flaky, wouldn't I > expect to see corrupted pointers being dereferenced in other sections > of code or is the dcache data structure particular susceptible? The dcache has long chains of pointers and tends to show up on things like memory

Re: Linux 2.2.18pre6

Alan, I see you parse-pieces for the 2.4 code as backports into 2.2 of the larger ide-patch. What is it going to take to just accept it? The ali-driver is straight out of 2.4 or ide-patch with parts of cmd646 taken to actively tune the drive and chipsets. If it is the issue of the taskfile

Re: Linux 2.2.18pre4

On Tue, 12 Sep 2000, Horst von Brand wrote: > Better asK: What can _we_ do to assure Alan that NFS is up to snuff? even if it does suck - so what? it can't possibly suck as much as current stock NFS. :) but the general view is that 2.2 with patches is quite useable for NFS serving and as

Re: [ANNOUNCE] Darkstar Development Project

On Mon, Sep 11, 2000 at 02:39:42PM -0700, Larry McVoy wrote: > On the other hand, if you do a > > find . -type f | xargs touch > time cvs update . > > it will melt down your DSL line for what seems forever. I killed it after > 20 minutes, I have better things to do with my bandwidth.

Re: Adding members to task_struct without recompling the kernel

On Tue, 12 Sep 2000 18:17:48 -0400 (EDT), Michael Vines <[EMAIL PROTECTED]> wrote: >I'm writing a kernel module that needs to keep track of a pointer to some >custom module information for every task in the system. Basically I want >to add another member to task_struct but I don't want to have

Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee

On Tue, Sep 12, 2000 at 09:10:56PM +0200, Trond Myklebust wrote: > > " " == Alan Cox <[EMAIL PROTECTED]> writes: > > > Providing everyone is careful to hold a lock I think it is > > > lockf() is a read barrier providing the local cache is flushed, > > the unlock is a write

Re: Notebook disk spindown

On Tue, 12 Sep 2000, Jamie Lokier wrote: > Dave Zarzycki wrote: > > Personally speaking, I always thought it would be nice if the kernel > > flushed dirty buffers right before a disk spins down. It seems silly to me > > that a disk can spin down with writes pending. > > Absolutely. That allows

(reiserfs) Re: More on 2.2.18pre2aa2

On Tue, 12 Sep 2000, Martin Dalecki wrote: >First of all: In the case of the mp3 player and such there is already a >fine >proper way to give it better chances on getting it's job done smooth - >RT kernel sceduler priorities and proper IO buffering. I did something >similiar >to a GDI printer

Re: Notebook disk spindown

Hi! > > On Sat, 9 Sep 2000 [EMAIL PROTECTED] wrote: > > > Would it be possible to detect when the disk spins up, and do the flush then? > > Yes if you had a continuious polling of power status wrt standby. > > I think the following flushing policy would work almost as well, while > remaining

Re: (reiserfs) Re: More on 2.2.18pre2aa2

> Why do you say it's not been fixed? Can you still reproduce hangs long as > a write(2) can write? I certainly can't. I cant reproduce long hangs. Im not seeing as good I/O throughput as before but right now Im quite happy with the tradeoff. If someone can make it better then Im happier still

Re: How to put something in /proc

> > On Sun, 10 Sep 2000, Giuliano Pochini wrote: > > > I need to create a "file" in /proc to monitor some kernel > > > variables from user space. How can I do ? / Where can I > > > get docs ? And how can I do time measurements from > > > inside the kernel ? > > > > Search for proc_register()

Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee

On Tue, Sep 12, 2000 at 07:08:09PM +0200, Trond Myklebust wrote: > This is a known issue, and is not easy to fix. Neither of the > solutions you propose are correct since they will both cause a cache > invalidation. This is not the same as cache coherency checking. > > > The correct solution in

Re: rocket port patch for 2.4

Date: Tue, 5 Sep 2000 19:58:48 -0500 From: Steven Critchfield <[EMAIL PROTECTED]> I have been playing with the rocket port driver in 2.4 trying to make it work. It appears that the driver hasn't been modified in some time, as it did not work at all on the debian potato inbstall

(reiserfs) Re: More on 2.2.18pre2aa2

On Tue, 12 Sep 2000, Andrea Arcangeli wrote: > On Tue, 12 Sep 2000, Rik van Riel wrote: > > >Also, this possibility is /extremely/ remote, if not > >impossible. Well, it could happen at one point in time, > > It's not impossible. Think when you run a backup of you home > directory while you're

Re: Masking out one page of RAM because of bit-errors.

On Tue, Sep 12, 2000 at 06:18:36PM +0200, Patrick Mau wrote: > I have a bad SDRAM chip with exactly one bit error. Memtest86 shows > that the bit error always occurs at the address 0x4eff508. I tried > to calculate the page number and it should be 20223. There is a patch on

(reiserfs) Re: More on 2.2.18pre2aa2

On Tue, 12 Sep 2000, Martin Dalecki wrote: > Second: The concept of time can give you very very nasty > behaviour in even cases. [integer arithmetic] Point taken. > Third: All you try to improve is the boundary case between an > entierly overloaded system and a system which has a huge

No Subject

Hello, I got this OOPS error. Ksymoops output is listed below. It occured when I was starting named and gave the message the error occured in 'chgrp'. OOPS: CPU: 0 EIP: 0010: [] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010202 eax: ebx: c1b25f24 ecx: c1f46380

Re: Using Yarrow in /dev/random

> No, not true. The mixing into the entropy pool uses a twisted LFSR, but > all outputs from the pool (to either /dev/random or /dev/urandom) > filters the output through SHA-1 as a whitener. The key here, though, > and what makes this fundamentally different from yarrow, is that since > we're

Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee

> " " == Alan Cox <[EMAIL PROTECTED]> writes: > Providing everyone is careful to hold a lock I think it is > lockf() is a read barrier providing the local cache is flushed, > the unlock is a write barrier providing the local cache is > flushed first. Providing all users

Re: [RFC] Changes file [was Re: modules directory]

On Tue, 12 Sep 2000, Simon Huggins wrote: > On Tue, Sep 12, 2000 at 01:41:45AM -0500, Oliver Xymoron wrote: > > > > This is similar to my patch-names patch, which lets you add components > > > > to uname too. IIRC, it was rejected because it made things easier. > > > Erm? Not really. Not

Re: I/O statistics per process?

Try the Linux Trace Toolkit. This should provide you with most I/O information you need. www.opersys.com/LTT Hope it helps. Samuli Kaski wrote: > > I know about sar which can deliver what I want for disks and/or > partitions. What about if I want to know how much I/O is caused by >

Re: More on 2.2.18pre2aa2

On Tue, 12 Sep 2000, Jamie Lokier wrote: >Sure the global system is slower. But the "interactive feel" is faster. >If I type "find /" I want it to go quickly. But I still want Emacs to You always want it to go quickly. But when you're in the blockdevice layer you lost all the semantics of

Re: (reiserfs) Re: More on 2.2.18pre2aa2

On Tue, 12 Sep 2000, Chris Evans wrote: >the elevator code. Keep it to a queue management system, and suddenly it >scales to slow or fast devices without any gross device-type specific >tuning. Yep, that was the object. Andrea - To unsubscribe from this list: send the line "unsubscribe

Re: [PATCH] for PAS16 functionality for 2.4

On Sun, 10 Sep 2000, Michael Elizabeth Chastain wrote: > I have written documentation on Rules.make and the interface between > Rules.make and Makefiles. It's here: > > ftp://ftp.shout.net/pub/users/mec/kbuild/x-Dkm-9.diff > > I would really like to see this documentation in the kernel.

Re: Masking out one page of RAM because of bit-errors.

On Tue, 12 Sep 2000, Patrick Mau wrote: > Dear list-readers, > > I have a bad SDRAM chip with exactly one bit error. Memtest86 shows > that the bit error always occurs at the address 0x4eff508. I tried > to calculate the page number and it should be 20223. > You should try Rik van Rein's

(reiserfs) Re: More on 2.2.18pre2aa2

On Tue, 12 Sep 2000, Rik van Riel wrote: >But you don't. Transfer rate is very much dependant on the >kind of load you're putting on the disk... Transfer rate means `hdparm -t` in single user mode. Try it and you'll see you'll get always the same result. >Throughput really isn't that relevant

(reiserfs) Re: More on 2.2.18pre2aa2

On Tue, 12 Sep 2000, Rik van Riel wrote: >Why do you always come up with impossible examples? That's not impossible. impossible != unlikely. A more regular case is when you have an extremely fast device, were a 1/2 second latency is too much, using 100msec could be just enough to provide good

Re: Booting into /bin/bash

Ion Badulescu wrote: > > > Maybe I'll play with main.c and see what happens if I force /dev/console > to become the controlling tty for init. Hmm... That could be dangerous for > init. Maybe a better idea would be to hack init so that it gives any > program started from inittab /dev/console as

Re: Duplicate messages

Vern writes: > Today, I received duplicate messages as posted by Rik van Riel to this > list. Here are the headers from both messages. Other than identical > Message-ID's, I can't discern where the duplicate originated. > Subject: Re: More on 2.2.18pre2aa2 > Subject: (reiserfs) Re: More on

Re: Q: sock output serialization

Hello! > Yes, I see. I did not realize before that the lock_sock and the > sk->backlog framework are not two independent things. They really > seem to be designed for team work only. Did I get this right? Yes. Actually, in 2.4 lock_sock() is also semaphore and in some cases (f.e. for

Re: Linux 2.2.18pre4

> What are the issues with updating NFS code that do not exist with > other drivers, filesystems, etc... in 2.2 for which updates are > accepted? They exist in the same way. You update stuff in controlled careful steps and you change troublesome drivers very early in a patch release - eg never

Re: Linux 2.2.18pre4

On Tue, 12 Sep 2000, Alan Cox wrote: > > ..so it should be at least as well tested as the USB backport in 2.2.18preX, > > if not more so? Or so is implied. :) > > This is the big clue most people are missing > > 2.2.17- USB devices do not work > 2.2.18-

Re: files bigger than 2 GB

On Tue, Sep 12, 2000 at 05:15:52PM +0200, Arnaud Installe wrote: > First of all, thanks to all of you for your responses. :-) I was under > the impression 2.4 still didn't have large file support, as I seem to > recall ssize_t still was 32 bits. The LFS specification defined loff_t

Re: [patch] VIA IDE driver v2.3

Vojtech, How about putting the old credits list back in because if the code base that you started with, please. Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at

Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee

> " " == Jeff Epler <[EMAIL PROTECTED]> writes: > Is there any solution that's available today, and doesn't > depend on using Linux in the server? I suspect that we will > have to distribute a modified nfs client with our app, and > we're prepared to accept the cache

Re: Linux 2.2.18pre4

On Tue, 12 Sep 2000, Alan Cox wrote: > They exist in the same way. You update stuff in controlled careful > steps and you change troublesome drivers very early in a patch > release - eg never touching tulip except early on > true. as i said before i'm glad we have such a 'tight' stable kernel

Re: Test 8 Kernel Unable to get the password prompt?

Miles Lane wrote: On Mon, 11 Sep 2000, David Freedom wrote: > I tried configuring the kernel to the least amount of > configured options to almost none and I still cannot > get the password prompt. > > My system hangs and is unable to do anything. > unfortunetly the only thing I can do is power

Re: [PATCH][RFC] check fib6_lookup_1 return in fib6_lookup_1

Hello! > fib6_lookup_1 can return NULL, please consider applying. Arnaldo, if you decided to play with subtrees, BEWARE! I never debugged this code and commented out it exactly because of this reason. Alexey - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

Re: 2.2.18pre2aa2 and patches for 2.2.18pre3

On Mon, 11 Sep 2000, Andrea Arcangeli wrote: > On Fri, 8 Sep 2000, Matthew Hawkins wrote: > >Something between bigmem and his big VM changes makes reiserfs > >uncompilable. [..] > > It's due LFS. Chris should have a reiserfs patch that compiles on top of > 2.2.18pre2aa2, right? (if not Chris, I

(reiserfs) Re: More on 2.2.18pre2aa2

> That problem: the original elevator code did not schedule I/O particularly > fairly under certain I/O usage patterns. So it got fixed. No it got hacked up a bit. > Now, I see people trying to introduce the concept of elapsed time into > that fix, which smells strongly of hack. How will this

Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee

> " " == Jeff Epler <[EMAIL PROTECTED]> writes: > But "ctime and file size are the same" does not prove that the ^ mtime > file is unchanged. That's the root of this problem, and why > NFS_CACHEINV(inode) is not enough to ensure coherency. Yes, but I just

Re: Using Yarrow in /dev/random

"Theodore Y. Ts'o" wrote: > >Date: Tue, 12 Sep 2000 09:56:12 + >From: Pravir Chandra <[EMAIL PROTECTED]> > >i agree that the yarrow generator does place some faith on the crypto >cipher and the accumulator uses a hash, but current /dev/random >places faith on a crc and

Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee

> If we have a purely Linux-specific hack to ensure cache coherency, > that will still corrupt the cache on those *NIX clients that use > ordinary cache coherency checking (i.e. checking mtime + file size) > rather than cache invalidation. Its what Solaris implements and what SunOS back down to

Re: Availability of kdb

Ted, I am looking at these sources as well. One thing I went back and looked at was related to a comment from Mike G. I believe regarding drivers conflicts with int 0x13 requests potentially hosing the IDE driver. In MANOS, since DOS is resident underneath the OS, I instrumented the code a

Re: Test 8 Kernel Unable to get the password prompt?

If you're logging in as root, this is probably a result of the VT not being named in /etc/securetty. Devfsd mucks up the names, so you can either include "1," which would allow root logins from pseudo-terminals and other insecure places, or upgrade your util-linux to a newer version; I'm not

Re: Recurring Oops in 2.2.12-20smp plus ext2_free_blocks.

Hi, Alan Cox wrote: > > I'd like to find more detail of the rare corruption so I can see if > > it matches what we're experiencing, is it more likely with an SMP > > machine, etc. Is there an archive of patches that go into a > > particular version anywhere? > > No but all pre releases can be

Re: [PATCH *] VM and scheduler patch

On Tue, 12 Sep 2000, Rui Sousa wrote: > Rik van Riel wrote: > > The second patch is a new version of the VM patch, [snip] > > http://www.surriel.com/patches/ > > Gave your patch a try, only the vm one. I applied it against > 2.4.0-test8 (final) with some warnings so the bug report may

Re: [PATCH *] VM and scheduler patch

Rik van Riel wrote: > > Hi, > > last night I made a few new patches. For one there's a > quick scheduler patch which makes the scheduler consider > CPU usage on a somewhat longer term as well as on the > short term, giving CPU time away a bit more fairly when > a process sleeps for a few

Re: Signal handling different for root and others

On Tue, Sep 12, 2000 at 03:09:40PM +0200, jury gerold wrote: > Andi Kleen wrote: > > > > On Tue, Sep 12, 2000 at 11:33:31AM +0100, Alan Cox wrote: > > > > > Normal users are only able to create a SIGIO signal when connecting. > > > > > > > > That's very unlikely. TCP does not propagate gid/uid

Re: files bigger than 2 GB

> Arnaud Installe writes: > First of all, thanks to all of you for your responses. :-) I was under > the impression 2.4 still didn't have large file support, as I seem to > recall ssize_t still was 32 bits. off64_t is the type you want to look at. > On Tue, Sep 12, 2000 at 04:25:02PM

Re: Signal handling different for root and others

Andi Kleen wrote: > > Never mind I found it. > > The patch should fix the problem, could you try it ? > > -Andi It work's now. Nothing is broken at least on this machine. That was quick. 2.4.0-x does not have the problem. Thanks Gerold - To unsubscribe from this list: send the line

2.2.17 & VM: do_try_to_free_pages failed / eepro100

Hello, On a high load server, kernel has some errors: VM: do_try_to_free_pages failed for httpd... VM: do_try_to_free_pages failed for httpd... eth0: Too much work at interrupt, status=0x4050. eth0: Too much work at interrupt, status=0x4050. is there somewhere the new version of driver for

elevator code

Hi Jeff, since I vaguely remember an email from you describing how you spent tweaking and changing the disk IO elevator in Netware, and since we might want to improve the Linux elevator sort a bit, could you give us some hints on what to do and where not to waste our time? ;) thanks, Rik --

Re: [linux-audio-dev] Ingo's lowlatency-test7-A0 excellent latencies (<1msec), but kernel filesync problems ...

On Wed, 13 Sep 2000, Benno Senoner wrote: > Hi folks, > I benchmarked Ingo's lowlatency-2.4.0-test7-A0 kernel > (http://people.redhat.com/mingo/lowlatency-patches/lowlatency-2.4.0-test7-A0) > > I can only say that it looks VERY promising ( < 1msec latencies !) > But there seems to be problems

does anyone have a minimal opendir/readdir/closedir implementation?

For my project "dietlibc" (http://www.fefe.de/dietlibc/) I am looking into implementing directory access now. The kernel interface seems to be: * supply an O_DIRECTORY flag to open() * a getdents system call You don't read on the fd in readdir, you call getdents. getdents reads n struct

Plug-in Schedulers for Linux

A prototype of Plug-in Schedulers for Linux as loadable modules (for 3 Linux versions), white paper, and a sample implementation of plug-in "processor sets" utilities and documents available at : http://resourcemanagement.unixsolutions.hp.com/WaRM/schedpolicy.html Try it out + tell us what you

Duplicate messages

Cc; [EMAIL PROTECTED] Today, I received duplicate messages as posted by Rik van Riel to this list. Here are the headers from both messages. Other than identical Message-ID's, I can't discern where the duplicate originated. Good Luck. First message Received: (from

[linux-audio-dev] Ingo's lowlatency-test7-A0 excellent latencies (<1msec), but kernel filesync problems ...

Hi folks, I benchmarked Ingo's lowlatency-2.4.0-test7-A0 kernel (http://people.redhat.com/mingo/lowlatency-patches/lowlatency-2.4.0-test7-A0) I can only say that it looks VERY promising ( < 1msec latencies !) But there seems to be problems with the kernel disk sync code: After the disk stress

  1   2   3   4   >