> The code in arch/ppc/config.in looks correct to me.
Yes, to me, too. And to menuconfig and config, but
not to xconfig.
> Please provide more details on how it "doesn't work here":
You've hit on at least one thing; the problem only comes
up in `make xconfig'; under ``General setup'',
Ted and LT,
I think this are the two things you wanted that were located in:
/src/tar-files/testing/direct_add/ht6560b.c
/src/tar-files/testing/direct_add/qd65xx.c
/src/tar-files/testing/direct_add/qd65xx.h
First Petr and Samuel, are these good to go into 2.4.0 ??
Cheers,
Andre Hedrick
The
In page_launder() about halfway down there is this sequence of tests
on LRU pages:
if (!clearedbuf) {
...
} else if (!page->mapping) {
...
} else if (page_count(page) > 1) {
} else /* page->mapping && page_count(page) == 1 */ {
...
}
Above this sequence we've done a page_cache_get. For the
On Wed, 13 Sep 2000, David S. Miller wrote:
>Date: Wed, 13 Sep 2000 18:00:02 -0700 (PDT)
>From: Matthew Jacob <[EMAIL PROTECTED]>
>
>This seems to be an artifact of some OBP implementations for PPC-
>apples in particular.
>
>It assigns both I/O and Mem addrs and IRQs,
Bogus Patch :-(
This is what I did also but more brut force with verification of IO's and
it still craps out..
On Wed, 13 Sep 2000, Daniel Jacobowitz wrote:
> On Wed, Sep 13, 2000 at 05:29:58PM -0700, Andre Hedrick wrote:
> >
> > Okay who can teach me how to force hooks and ram this down the
} > Cort Dougan recently announced he was no longer going to be maintaining
} > the PowerPC Linux tree.
What I'd said was I'm taking a vacation from maintaining the PPC-tree for a
while so I can do some of my real job. I'm not abandoning it in any way -
just spending less time on it for a
> The point is that there's some pollution in arch/ppc/config.in
> that doesn't allow a G4 user (for example) to configure a
> host of PCI devices.
The code in arch/ppc/config.in looks correct to me.
Please provide more details on how it "doesn't work here":
Are you using 'make config',
Hi,
The new VM patch seems has received a major amount of
code cleanup, performance tuning and stability improvement
over the last few days and is now almost production
quality, with the following 4 items left for 2.4:
- improve streaming IO performance
- out of memory handling
- integrate Ben
Hi Bartlomiej,
> - Moved $(IDE_OBJS) (now $(ide-obj-y)) from MIX_OBJS to MI_OBJS
> due the fact that they don't export any symbols (I hope).
They don't export any symbols.
> - Removed $(LD_RFLAG), I can't find any definition of it in the
> kernel source tree and LD docs. WTF it is (was)
Peter Christy wrote:
> A quick fix has been to put "alias sd_mod sd" in modules.conf, but then I
> have to rem it out if I use the old kernel.
/etc/modules.conf
if `kernelversion` == 2.4
alias sd_mod sd
endif
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On Wed, 13 Sep 2000, Marco d'Itri wrote:
> On Sep 13, [EMAIL PROTECTED] wrote:
>
> > * Innd data corruption, probably caused by bug truncation bug (Rik
> > van Riel)
> This bug has not been fixed, I can still reproduce it (but not every
> time). This is how it happens:
>
> - INN
Peter Christy wrote:
>
> OK, after a LOT of head scratching, I 've found the problem. At some point
> in its development, the name for the scsi sd module has changed from sd_mod
> to plain sd. Now I haven't seen this mentioned anywhere in the
> documentation, and its caught my system out
On Thu, 14 Sep 2000, Tulika Pradhan wrote:
> i want to build a kernel without virtual memory support. this is
> for a ppc based embbedded system. i read somewhere that VM can
> be disabled by setting the swap space size to 0. But where do i
> do this ?
Does the system have an MMU or not?
If it
hi !
i want to build a kernel without virtual memory support. this is for
a ppc based embbedded system. i read somewhere that VM can be disabled
by setting the swap space size to 0. But where do i do this ?
please help,
tulika
On Wed, 13 Sep 2000 23:35:55 -0300,
Gianluca Brigandi <[EMAIL PROTECTED]> wrote:
>I just installed succesfully the RedHat 6.2 in a 1000Mhz AMD server.
>After I reboot, being finished the installation, the kernel starts and
>crashes in
>the following panic:
>
>disabling CPUID serial number
Sorry to send the letter to the wrong place.Specially thanks to
R.B.Johnson,B.Halley,S.Vandevender,M.Kreen,dave,E.Mouw.I'll never do this
stupid thing.
BTW:Could you read this message correctly?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
Hi,
I just installed succesfully the RedHat 6.2 in a 1000Mhz AMD server.
After I reboot, being finished the installation, the kernel starts and
crashes in
the following panic:
disabling CPUID serial number general protection fault:
(...reg dump...)
Kernel panic: attempted to kill the idle
Sorry, this is a test
-
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 http://www.tux.org/lkml/
Twice now I have experienced this crash, but I do not know how to
replicate it. The system was under normal load (netscape, xmms, and few
other minor programs) First, xmms stopped playing. Then, the screen
went black and the system speaker began beeping feverously. I reached
to hit the
On Wed, 13 Sep 2000, Stephen Frazier wrote:
> Does *BSD run on S390?
Ummm, hello, NO they do not. This is at least PART of the point. I
believe now is my chance to get out my clue-by-four.
FreeBSD has a GREAT idea(and really NetBSD as well). We might want to
consider adopting that idea. In
On Wed, Sep 13, 2000 at 08:08:12PM -0300, Rik van Riel wrote:
> On Thu, 14 Sep 2000, Ragnar Kjørstad wrote:
> > On Wed, Sep 13, 2000 at 06:57:21PM -0300, Rik van Riel wrote:
> > > > Another potentially stupid question:
> > > > When the queue gets too long/old, new requests should be put in
> > >
Date: Wed, 13 Sep 2000 10:32:03 -0400
From: "Theodore Y. Ts'o" <[EMAIL PROTECTED]>
In the long run, it will make your life easier, to the extent that
having an up-to-date bug list is easier, and because then I won't
have to continually pester people about whether certain bugs have
On Wed, 13 Sep 2000, David S. Miller wrote:
>Date: Wed, 13 Sep 2000 18:00:02 -0700 (PDT)
>From: Matthew Jacob <[EMAIL PROTECTED]>
>
>This seems to be an artifact of some OBP implementations for PPC-
>apples in particular.
>
>It assigns both I/O and Mem addrs and IRQs,
Paul Mackerras wrote:
> I don't think this is actually correct; I believe what Cort said is
> that he is no longer maintaining the http://www.ppc.linux.org/ web
> site.
That is the way I read it as well. Of course, I have been reading
things differently than others, lately :-).
> He is
Date:Wed, 13 Sep 2000 18:00:02 -0700 (PDT)
From: Matthew Jacob <[EMAIL PROTECTED]>
This seems to be an artifact of some OBP implementations for PPC-
apples in particular.
It assigns both I/O and Mem addrs and IRQs, but doesn't enable
either memory or I/O. So you have
My name is Kirti Desai. I am trying to write a new
console driver.
Hence I was going through the source code and I need
your
help in understanding it. I would be obliged if you
can help
me out. I am working on Redgar Linux 2.2-14.12 on
Celeron 400.
* Is console related to a tty_driver? We
This seems to be an artifact of some OBP implementations for PPC- apples in
particular.
It assigns both I/O and Mem addrs and IRQs, but doesn't enable either memory
or I/O. So you have to do it for it.
On Wed, 13 Sep 2000, Andre Hedrick wrote:
>
> Okay who can teach me how to force hooks and
On Wed, Sep 13, 2000 at 05:29:58PM -0700, Andre Hedrick wrote:
>
> Okay who can teach me how to force hooks and ram this down the PPC
>
> pci_write_config_word(dev, PCI_COMMAND, 0x05);
>
> I have all the address registered.
> My new PPC G3 (7600/132) toy is not allowing IO's on PCI cards to
On Thu, 14 Sep 2000, Keith Owens wrote:
> On Thu, 14 Sep 2000 01:11:57 +0200 (CEST),
> Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> wrote:
> >- Removed $(LD_RFLAG), I can't find any definition of it in the
> > kernel source tree and LD docs. WTF it is (was) used for?
>
> LD_RFLAG was
The last version I've spotted was for mid-2.2 and was filled with gcc 2.7-isms
in the assembler code. I was curious if anyone has updated this to version 2.4
at all because it makes all the difference in the world for me with my P60. Now
that the memcpy stuff is somewhat modularized (with the
Okay who can teach me how to force hooks and ram this down the PPC
pci_write_config_word(dev, PCI_COMMAND, 0x05);
I have all the address registered.
My new PPC G3 (7600/132) toy is not allowing IO's on PCI cards to come
alive. Thus I get some of the most beuatiful lockups ever.
I suspect that
On Wed, Sep 13, 2000 at 11:56:56PM +0200, Trond Myklebust wrote:
> After consultation with the appropriate authorities, it turns out that
> the Sun-code based clients do in fact turn off data caching entirely
> when using NLM file locking.
Entirely? That's interesting, because for our
> patch: malformed patch at line 9027: \ No newline at end of file
> I check patch-2.0.39-pre8 at 9027 line.
You need patch v2.5 or higher.
-
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
On Wed, 13 Sep 2000, David S. Miller wrote:
> Known bug, Linus just hasn't made a pre-patch in a long
> time with the fix. Here is the fix:
I'd like to confirm that this patch is /needed/ to keep
my system running with 2.4.0-test8...
> --- vanilla/linux/fs/buffer.c Wed Sep 6 08:29:45 2000
>
On Thu, 14 Sep 2000 01:11:57 +0200 (CEST),
Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> wrote:
>- Removed $(LD_RFLAG), I can't find any definition of it in the
> kernel source tree and LD docs. WTF it is (was) used for?
LD_RFLAG was obviously intended to be extra ld flags but only when
doing
Dear.
I am Seiichi Nakashima in Japan.
I tested linux-2.0.39-pre-8, but compile error
occured.
(1) Patch error ( maybe waring only )
I execute
# tar zxf linux-2.0.38.tar.gz
# mv linux linux-2.0.38
# patch -s -p0 < patch-2.0.39-pre8
Then error occured
patch: malformed patch
On my system, in ./arch/i386/kernel/time.c, set_rtc_mmss is outputting the
messages
Sep 13 15:40:04 newton kernel: set_rtc_mmss: can't update from 57 to 10
Sep 13 15:41:05 newton kernel: set_rtc_mmss: can't update from 57 to 11
Sep 13 16:04:08 newton kernel: set_rtc_mmss: can't update from 53
Dwayne Grant McConnell ([EMAIL PROTECTED]) writes:
> Cort Dougan recently announced he was no longer going to be maintaining
> the PowerPC Linux tree.
I don't think this is actually correct; I believe what Cort said is
that he is no longer maintaining the http://www.ppc.linux.org/ web
site. I
> The second patch that Matt refers to inserts that logic into st so
> it does not try to support these drives and fails due to the drive
> particulars. Since SCSI, USB and IDE versions of these drives exist,
> patching st is more appropriate than ide-scsi.
Okay I am a mushroom, keep feeding me
Andre Hedrick wrote:
>
> On Wed, 13 Sep 2000, Matthew Dharm wrote:
>
> > Attached is a patch to ide-scsi.c against 2.4.0-test8. Please consider
> > applying it.
> >
> > This patch removes the logic which causes ide-scsi to refuse to attach
> > itself to an IDE OnStream drive. While these
On Tue, 12 Sep 2000, Vojtech Pavlik wrote:
> Anyone interested, please test this out, if it is as problemless as
> version 2.1, I'll send this to Linus for inclusion in the kernel.
Seems to be ok. Works ok. Please consider appling *crappy* patch
which corrects one entry in /proc/ide/via and
On Wed, Sep 13, 2000 at 03:53:13PM -0700, Andre Hedrick wrote:
>
> On Wed, 13 Sep 2000, Matthew Dharm wrote:
>
> > Attached is a patch to ide-scsi.c against 2.4.0-test8. Please consider
> > applying it.
> >
> > This patch removes the logic which causes ide-scsi to refuse to attach
> > itself
"Theodore Y. Ts'o" wrote:
>Date: Tue, 12 Sep 2000 23:55:55 -0700
>From: David Ford <[EMAIL PROTECTED]>
>
>Please add 'APM resume returns the machine to the first tty, crashes
>X' This appeared w/ test8. If this is intended, I'd be very happy to
>know if so and I can write in
I think that both the NFS server changes that Trond is suggesting and the
NFS client changes that I am suggesting have their place.
The fact that the tuple (mtime, size) is used to test to test for
unchangedness of a file indicates that the people who designed NFS
understood that just using
Trond Myklebust writes:
> > " " == Albert D Cahalan <[EMAIL PROTECTED]> writes:
>> 20 bits * 3 timestamps == 60 bits 60 bits <= 8 bytes
>>
>> So you do need 8 bytes.
>
> Yes. Assuming that you want to implement the microseconds field on
> all 3 timestamps. For NFS I would only need that
"Theodore Y. Ts'o" wrote:
>Date: Tue, 12 Sep 2000 23:37:57 -0700
>From: David Ford <[EMAIL PROTECTED]>
>
>> > 4. Boot Time Failures
>> >
>> > * Use PCI DMA 'lost interrupt' problem with some hw [which ?] (NEC
>> >Versa LX with PIIX tuning)
>>
>> If
Mark Kettenis wrote:
>From: Ulrich Drepper <[EMAIL PROTECTED]>
>Date: 2000-09-13 6:35:16
>
>[EMAIL PROTECTED] writes:
>
>> I didn't realize things had changed that broke the old threading model.
>> Did Linus do more than add support for the new thread groups? I didn't
>>
On Thu, 14 Sep 2000, Ragnar Kjørstad wrote:
> On Wed, Sep 13, 2000 at 06:57:21PM -0300, Rik van Riel wrote:
> > > Another potentially stupid question:
> > > When the queue gets too long/old, new requests should be put in
> > > a new queue to avoid starvation for the ones in the current
> > >
Michael Elizabeth Chastain wrote:
>
> > and then I made the soft link to point to the new directory.
>
> If you are talking about a soft link named "linux", just completely
> delete it and reset it to the value that it had when you installed
> your distribution and then never touch it again.
>
Despite rewritting it to use lists I have changed two things:
- Moved $(IDE_OBJS) (now $(ide-obj-y)) from MIX_OBJS to MI_OBJS
due the fact that they don't export any symbols (I hope).
- Removed $(LD_RFLAG), I can't find any definition of it in the
kernel source tree and LD docs. WTF it is
On Tue, Sep 12, 2000 at 11:37:46AM +0100, Alan Cox wrote:
> That code example can in theory deadlock without any patches if the CPU's
> end up locked in sync with each other and the same one always wins the test.
> It isnt likely on current x86 but other processors are a different story
If seen
On Tue, Sep 12, 2000 at 12:21:16AM +0200, Jamie Lokier wrote:
> > Other than the initial repository create (aka cvs checkout), BK
> > *never* moves an entire file across the wire. Never means never and
> > includes the process of deciding what to do. CVS moves whole files
> > just to discover
Title: Kernel oops on 2.4.0-test4 and test5 (and later): kmem_cache_grow
Hi,
I've been having kernel oopses with the 2.4.0-test series and am including ksymoops processed output from both test4 and test5 kernels. The same oops happens in later kernels too (I've tested test6 and test7).
> that bitkeeper has. The problem with bitkeeper is that it's **so**
> different from CVS that it takes time to learn --- I spent a day getting
> my head wrapped around it, and I still wouldn't call myself an expert;
Another problem is that bitkeeper has not been through a security audit.
>
Hello,
I am working on a project that is going to find the current limit of
16-bits for device numbers to be a pain. While looking around in the
linux-kernel archive, I found a series of e-mails about this from late
last year in which was discussed the introduction of the kdev_t type
and the
On Wed, 13 Sep 2000, Matthew Dharm wrote:
> Attached is a patch to ide-scsi.c against 2.4.0-test8. Please consider
> applying it.
>
> This patch removes the logic which causes ide-scsi to refuse to attach
> itself to an IDE OnStream drive. While these drives are not supported by
> the
On Wed, Sep 13, 2000 at 06:57:21PM -0300, Rik van Riel wrote:
> > Another potentially stupid question:
> > When the queue gets too long/old, new requests should be put in
> > a new queue to avoid starvation for the ones in the current
> > queue, right?
>
> Indeed. That would solve the problem...
Attached is a patch to ide-scsi.c against 2.4.0-test8. Please consider
applying it.
This patch removes the logic which causes ide-scsi to refuse to attach
itself to an IDE OnStream drive. While these drives are not supported by
the standard st.c driver, there is userspace support (using the sg
On Wed, Sep 13, 2000 at 08:08:51PM -0400, Giuliano Pochini wrote:
> > And if so, in what unit do you want to measure
> > latency if it isn't time?
>
> I had a look at the new elevator. I hope I'm not wrong here... Requests
> are added to the queue scanning it starting from the tail. When the
>
Hello Torben , My manual edit of drivers/scsi/sr.c was the same
as your patch . And yes I am now running the 2.4-test8 .
Tnx , JimL
root@test:~# uname -a
Linux test 2.4.0-test8 #2 Wed Sep 13 14:28:35 PDT 2000 i586 unknown
root@test:~# sh
On Wed, 13 Sep 2000, Chip Salzenberg wrote:
> According to Andre Hedrick:
> So I've noticed. Do you not believe in its technical future, or are
> you just conserving what's left of your free time?
I would be attending an ice skating party below before I would see this
included, and I am short
** Reply to message from Keith Owens <[EMAIL PROTECTED]> on Thu, 14 Sep 2000
08:49:50 +1100
> (5) Easier for kernel beginners to learn the kernel internals. Having
> worked on 10+ operating systems over the years, I can testify that
> some form of kernel/OS tracing facility is
On Wed, 13 Sep 2000, Ragnar Kjørstad wrote:
> On Wed, Sep 13, 2000 at 11:22:16AM -0400, Michael T. Babcock wrote:
> > If I may ask a potentially stupid question, how can request latency be
> > anything but a factor of time? Latency is how /long/ you (or the computer)
> > /waits/ for something.
Hi,
> "kuznet" == kuznet <[EMAIL PROTECTED]> writes:
>> Anyway, it seems that I can already make use the lock_sock()
>> infrastructure for fixing the output serialization, even
>> without making the whole protocol stack SMP-aware at once.
kuznet> Actually, the last task
> " " == Andi Kleen <[EMAIL PROTECTED]> writes:
> Steal a couple of bytes from what ?
>From the 32-bit storage area currently allocated to i_generation on
the on-disk ext2fs inode (as per Ted's suggestion). With current
disk/computing speeds, you probably don't need the full 32 bits to
Amen Brother
Jeff
Keith Owens wrote:
>
> Resend, this time with cc: torvalds.
>
> This note puts the case for including a kernel debugger in the master
> tarballs. These points do not only apply to kdb, they apply to any
> kernel debugger. Comments about the perceived deficiencies of
> " " == Jeff Epler <[EMAIL PROTECTED]> writes:
> But "ctime and file size are the same" does not prove that the
> file is unchanged. That's the root of this problem, and why
> NFS_CACHEINV(inode) is not enough to ensure coherency.
> Furthermore, according to NFSv4,
On Wed, Sep 13 2000, Mr. James W. Laferriere wrote:
>
> Hello Torben ,
> Has anyone caught this one yet . I assume it is just the same
> patch added (manually) to sr.c/h as well ? Tia , JimL
>
> drivers/scsi/scsidrv.o: In function `init_sr':
>
Resend, this time with cc: torvalds.
This note puts the case for including a kernel debugger in the master
tarballs. These points do not only apply to kdb, they apply to any
kernel debugger. Comments about the perceived deficiencies of kdb,
kgdb, xmon or any other debugger are not relevant
On Wed, Sep 13, 2000 at 11:22:16AM -0400, Michael T. Babcock wrote:
> If I may ask a potentially stupid question, how can request latency be
> anything but a factor of time? Latency is how /long/ you (or the computer)
> /waits/ for something. That defines it as a function of time.
Latency is
> " " == Theodore Y Ts'o <[EMAIL PROTECTED]> writes:
> Why? i_generation is a field which is only used by the NFS
> server. As far as ext2 is concerned, it's a black box value.
> Currently, as I understand things (and you're much more the
> export on the NFS code than I
On Wed, 13 Sep 2000 09:33:02 +0800, Pan Renzi wrote:
> This is a multi-part message in MIME format.
>
> --=_NextPart_000_00D6_01C01D65.9CA16860
> Content-Type: text/plain;
> charset="gb2312"
> Content-Transfer-Encoding: base64
>
>
On 13 Sep 2000, Ralf Gerbig wrote:
> * Chip Salzenberg writes:
>
> Hi Chip,
>
> > According to Ralf Gerbig:
> >> but SuSe and I believe RedHat etc. etc. _do_ ship patched kernels.
>
> > You've just made L-K's understatement of the day.
>
> [...]
>
> so I rest my case vs shrink wrap.
>
Hello Torben ,
Has anyone caught this one yet . I assume it is just the same
patch added (manually) to sr.c/h as well ? Tia , JimL
drivers/scsi/scsidrv.o: In function `init_sr':
drivers/scsi/scsidrv.o(.text+0x1cfce): undefined reference to
`scsi_register_module'
It isn't when you are not using persistent super blocks, and if it were
doing so that would definitely be a bug IMO.
And anyway, it occurs without using the md driver as well (on a normal
partition as I described in my original post...).
Andries Brouwer's reply/post offered the AFAICS correct
On Wed, Sep 13, 2000 at 10:35:10PM +0200, Trond Myklebust wrote:
> > No, it does not help. i_generation is only in the NFS file
> > handle, but not in the fattr/file id this is used for cache
> > checks. The NFS file handle has to stay identical anyways, as
> > long as the
Does *BSD run on S390?
Stephen Frazier
Oklahoma Department of Corrections
-Original Message-
On Wed, 13 Sep 2000, Geert Uytterhoeven wrote:
I just thought I would remind all the nay-sayers that the *BSD world has
been doing something along this line since at least 1990. While some of
On Wed, Sep 13, 2000 at 12:42:15PM +0200, Trond Myklebust wrote:
>
> Is there any 'standard' function for reading the microseconds fields
> in userland? I couldn't find anything with a brief search in the
> X/Open docs.
>
Both Digital OSF/1 and Solaris use 3 undocumented spare fields in the
Date: Wed, 13 Sep 2000 22:35:10 +0200 (CEST)
From: Trond Myklebust <[EMAIL PROTECTED]>
You might be able to steal a couple of bytes and then rewrite ext2fs
to mask those out from the 'i_generation' field, but it would mean that
you could no longer boot your old 2.2.16 kernel
* Chip Salzenberg writes:
Hi Chip,
> According to Ralf Gerbig:
>> but SuSe and I believe RedHat etc. etc. _do_ ship patched kernels.
> You've just made L-K's understatement of the day.
[...]
so I rest my case vs shrink wrap.
OTOH one of the first things I do after trying a new distribution
On Wed, 13 Sep 2000, Joseph Carter wrote:
> I've been fighting with this for a couple of days now. I've been trying
> under lilo, syslinux, and grub to get the kernel to follow the documented
> behavior of executing /linuxrc if you tell it to load an initrd as it did
> back in 2.0.35 (which was
I found by an experiment that an Alpha with a device which provides
its own PCI bridge, and if that device is on a PCI bus 0, will stop
booting right after "Partition check" messages. The only way out is
through a power switch. One can still boot if the device in question
is plugged in a slot
> "rasmus" == Rasmus Andersen <[EMAIL PROTECTED]> writes:
rasmus> Hi.
rasmus> This patch does minor and strightforward cleanup in mm/swapfile.c.
Please, don't apply, SWP_WRITEOK is defined as two bits:
#define SWP_WRITEOK 3
that means that
((p->flags & SWP_WRITEOK) == SWP_WRITEOK) !=
I've been fighting with this for a couple of days now. I've been trying
under lilo, syslinux, and grub to get the kernel to follow the documented
behavior of executing /linuxrc if you tell it to load an initrd as it did
back in 2.0.35 (which was the last time I actually tried to use an initrd
> " " == Andi Kleen <[EMAIL PROTECTED]> writes:
> On Wed, Sep 13, 2000 at 11:51:45AM -0400, Theodore Y. Ts'o
> wrote:
>>
>> So this is a really stupid question, but I'll ask it anyway.
>> If you just need a cookie, is there any way that you might be
>> able to steal
Just discovered that if you try to compile 2.4.0-test8 without module
support then the compilation (or linking to be more exact) fails at:
drivers/scsi/scsidrv.o: In function 'init_sd':
drivers/scsi/scsidrv.o(.text+0x1efa): undefined reference to
'scsi_register_module'
drivers/scsi/scsidrv.o:
> " " == Albert D Cahalan <[EMAIL PROTECTED]> writes:
> 20 bits * 3 timestamps == 60 bits 60 bits <= 8 bytes
> So you do need 8 bytes.
Yes. Assuming that you want to implement the microseconds field on all
3 timestamps. For NFS I would only need that precision on mtime.
Does
On Wed, 13 Sep 2000, Miquel van Smoorenburg wrote:
> Stick a setsid() before the tty stuff.
Have you tried it? There is a good reason why I put the setsid() call so
early in kernel's init(). Once the initialization is done, init will have
several kernel threads as part of its process group,
Mitchell Blank Jr wrote:
>
> Alan Cox wrote:
> > Humans will generally get a weird report from sending Linus a message wonder
> > what all this field stuff is and mail someone else instead.
>
> If they're able to create a patch, hopefully they'd be able to fill in
> a simple email template (and
hi,
some people reported problems in eepro boards with 2.2.17
driver. please apply this patch over 2.2.17 version.
warning: this is a _test_ patch! i've tested with etherexpress 10 (the
only board supported by this driver that i have here - donations are very
welcome ;)) and it works very
Andrey Panin wrote:
>
> Hi all,
>
> I recently returned from Sea Launch homeport and already made a new patch :))
>
> This patch fixes bothering problem with ACPI interpreter Makefile.
>
> Without this patch ACPI interpreter will unconditionaly recompiled
> every kernel build.
>
> Hope it
On Wed, 13 Sep 2000, Rasmus Andersen wrote:
> Hi.
>
> This patch does minor and strightforward cleanup in mm/swapfile.c.
SWP_WRITEOK is defined as 3, so if (foo & SWP_WRITEOK) is not equivalent
to if ((foo & SWP_WRITEOK) == SWP_WRITEOK). Cheers,
-ben
-
To unsubscribe from
"Theodore Y. Ts'o" wrote:
>
>Date:Wed, 13 Sep 2000 08:46:00 +0200
>From: Harald Dunkel <[EMAIL PROTECTED]>
>
>How can I submit a bug report to be added to this list?
>
> I *try* to follow bug reports sent to Linux-kernel, but if you want to
> be sure, send it directly to me
From: "Dunlap, Randy" <[EMAIL PROTECTED]>
Date: Wed, 13 Sep 2000 09:17:55 -0700
I appreciate Alan and you doing the kernel Status/TODO lists,
but I think that you ought to simplify it for yourself at
least (not that this would help Linus) by having maintainers
do it instead of
On Wed, Sep 13, 2000 at 08:52:54PM +0200, Rasmus Andersen wrote:
> Hi.
>
> This patch does minor and strightforward cleanup in mm/swapfile.c.
I have been corrected on this and retract it. Sorry to bother you all.
--
Regards,
Rasmus([EMAIL PROTECTED])
I am two fools, I know, for
-BEGIN PGP SIGNED MESSAGE-
I had the same thought.
have you considered doing this as a front-end for bitkeeper?
something along the lines of it will accept bitkeeper changesets, or if it
receives a patch as you describe (and it applies cleanly) it creates a
bitkeeper changeset for it.
On Tue, 12 Sep 2000, Ralf Baechle wrote:
> 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
"Jeff V. Merkey" <[EMAIL PROTECTED]> said:
[...]
> I have concluded that Linux will only progress as fast as Linus does. Linux
> has forked twice now, and the new variants are not named "Linux" anymore, so
> these types of changes may occur more quickly since there will be independent
>
On Sep 13, [EMAIL PROTECTED] wrote:
> * Innd data corruption, probably caused by bug truncation bug (Rik
> van Riel)
This bug has not been fixed, I can still reproduce it (but not every
time). This is how it happens:
- INN (1.7.2+insync+other patches, the debian package I maintain)
Hello,
I have a heavy workload to benchmark a proxy server and it generates over
1000 simultaneous sessions requesting files of different sizes.
I have two seperate problems that I would like clarified:
1. On the newer versions of the kernel, 2.4.XXX I see way too many connect
requests timing
1 - 100 of 455 matches
Mail list logo
