[EMAIL PROTECTED] (Martin Dalecki) wrote on 06.09.00 in
<[EMAIL PROTECTED]>:
> Alexander Viro wrote:
> >
> > On Wed, 6 Sep 2000, Martin Dalecki wrote:
> >
> > > Easy - the same way you do for cross compilation. Basically just:
> > >
> > > export CC=g++ --some-magic-long-option-i-dont-remember;
John Levon wrote:
>
> Am I right ? against test8pre1
>
> Also, is it a bug to not set TASK_{UN}INTERRUPTIBLE before doing a
> schedule_timeout() ? What will happen ?
>
Well, first the "timeout" call will return immediately. Next, when the
time out actually happens, if the task is not TASK_RUNN
Greetings...
Of all the bugs i've run into, this is one of the oddest. Hopefully,
i've a) got all the req'd information here and b)a hope of finding a
solution/workaround/a facsimile thereof to the problem.
System Spec's: K6-2/500
64 MB RAM
9.2 Quantum HD
On Wed, 6 Sep 2000, S.J. Black wrote:
>Of all the bugs i've run into, this is one of the oddest. Hopefully,
>i've a) got all the req'd information here and b)a hope of finding a
>solution/workaround/a facsimile thereof to the problem.
>
>System Spec's: K6-2/500
> 64 MB RAM
>
Hi.
Im getting an oops almost right after 'unpacking linux...'. It is from
a RH 6.2 install process boot floppy. I have tried several floppies
to eliminate bad media. So I guess it is bad hw, probably RAM. It
is an old P75 with 32MB RAM. It runs win98 fine, but that is not
saying much ;)
I was
Christoph Hellwig wrote:
> > > + lvm_devfs_handle = devfs_register(
> > > + 0 , "lvm", 0, 0, LVM_CHAR_MAJOR,
> >
> > Does this really have to go into /dev rather than a subdirectory?
>
> Yes. The userlevel tool can't handle other things without recompiling.
> I can't use /dev/lvm, too
> 1. This function is only used in the poorly maintained ftape driver.
>The usage there isn't appriopriate for modern kernels.
The ftape driver isnt exactly poorly maintained. Its just not integrated into
2.3/2.4. Ftape 4.0 is still elsewhere
-
To unsubscribe from this list: send the line "u
# pse|grep defunct
7854 [gftp ] exit_notify
7855 [gftp ] exit_notify
31281 [xmms ] exit_notify
31282 [xmms ] exit_notify
31285 [xmms ] exit_notify
31717 [xmms ] exit_notify
test8-pre5
-d
--
"The difference between 'involvement' and 'commitment' is like an
eggs-and-ham breakfast: the chicken
> As readability - it's definitely at least as readable as
> #if[def]. It also provides more consistent syntax. And when you are
> using ifdef to violate scoping - your code is in need of rewrite anyway.
You still need the #ifdef stuff as well for half of it so I dont see what
it buys you
On Wed, Sep 06, 2000 at 01:28:45PM +1200, Chris Wedgwood wrote:
> else
> a = 5;
> 10: c7 05 00 00 00 00 05movl $0x5,0x0
In current GCC, this is optimised away even at -O0, because it's
generally quicker to do dead code elimination than to emit the dead
code at all.
T
Chip Salzenberg <[EMAIL PROTECTED]> writes:
|> According to Andi Kleen:
|> > You probably don't have a .config.gz that is longer than a page
|> > (4K), because in that case it'll badly corrupt your memory (or you
|> > just haven't noticed the corruption yet ;)
|>
|> Hm... they're all <4K, but a
Heya acme... seems you fixed the sr.c driver a bit too much and
killed an #ifdef MODULE that was needed if you build without
modules (as I do on some of my SPARCs)... this change was made
in 2.4.0-test8-pre5...
drivers/scsi/scsidrv.o: In function `init_sr':
drivers/scsi/scsidrv.o(.text+0x1ece8):
Chris Wedgwood wrote:
[Gcc not eliminating trivial dead code...
did you compile without optimisation?]
Gcc 2.96 does remove the unreached code in your example,
but it still emits string constants.
int func()
{
if (1)
a = "foo";
else
a = "bar";
}
.LC0:
.string "foo"
.LC1:
Linus Torvalds wrote:
> And I'm saying that if people really want to do this, then use the
> computer to do it for you, having more than just "grep", and making your
> tools aware of it.
I'd just like to add, for the benefit of onlookers, that this is
quite easy.
Temporarily change name of `coun
Chris Wedgwood wrote:
> I think would be really cool if all this 'magic' in gcc (whatever
> part of gcc is irrelevant right now) would be exported into a library
> or shared object which editors could then load and use... dynamically
> perhaps.
Sorry, there's a GCC policy decision against putting
Enclosed is a patch that exports some IPv6 specific symbols on 2.4 so that
finally IPv6 is accessible from modules. I bet there are bunch of other
functions that needs to be exported as well but this is a start. There
are also various IPv6 functions in 2.2 that should be exported for the
same r
dean gaudet wrote:
> suppose you're building a threaded server to scale to 20k connections,
> and you want to support fork()/exec() of CGIs dirctly (rather than
> through a separate daemon process).
>
> if you don't use close-on-exec, then after fork before exec you have
> to iterate over the 20k
On Tue, 5 Sep 2000, Alexander Viro wrote:
>
> The _real_ problem is preprocessor abuse. BTW, could we schedule for
> 2.5 the following?
> * things like CONFIG_FOO are _always_ defined. As 0 or 1, that is.
> * #ifdef CONFIG_FOO => if (CONFIG_FOO) in *.c. gcc will kill the unused
[Linus]
> - pre5
> - truncate. Guess what? We threw away the key to the clue-box.
> - simplify signal notification. And remember the spinlock.
> - VIA ide driver update (well, rewrite - the old one was buggy and broken)
Can someone explain this line from the VIA update?
#define F
On Wed, 6 Sep 2000, Peter Samuelson wrote:
> > - VIA ide driver update (well, rewrite - the old one was buggy and broken)
>
> Can someone explain this line from the VIA update?
> #define FIT(v,min,max) (((v)>(max)?(max):(v))<(min)?(min):(v))
> Barring side effects on the variables, it is e
On Tue, Sep 05, 2000 at 12:35:16PM -0400, Kernel Related Emails wrote:
> Has this been integrated into the 2.4.0-testX kernels? And if so which
> version?
No, it hasn't.
A version with a workaround is at
ftp://ftp.sw.com.sg/pub/Linux/people/saw/kernel/v2.3/
It has been submitted it to Linus, but
Hi all
When I'm in user mode and malloc ram this portion of ram is cleared (zeroed)
or?
i think it is!
My question is
who cleared it the kernel or the malloc function in glibc??
(i found some code in glibc but nothing in kernel)
thx
mfg
Frank Peters
-
To unsubscribe from this list: send t
On Tue, 5 Sep 2000, Jeff V. Merkey wrote:
>"Mike A. Harris" wrote:
>
>Here Mike, we need to update your email signature block to reflect your
>new avocation (this is where I try to be your mega-buddy). I think the
>reason I'm so obtuse is that God gave me such a thick skin (or perhaps a
>thick s
[Frank Peters]
> My question is
> who cleared it the kernel or the malloc function in glibc??
> (i found some code in glibc but nothing in kernel)
The kernel. Not to do so would be a security hole. (That memory could
have been used for *anything*.)
Peter
-
To unsubscribe from this list:
argggh couldn't they keep the rutgers.edu to be valid... or keep
redhat.com - it's much easier to remember than kernel.org :)
-- Forwarded message --
Date: Wed, 6 Sep 2000 12:31:06 +0100 (BST)
From: Tigran Aivazian <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: Rik van Riel <[E
On Wed, Sep 06, 2000 at 12:52:42PM +0100,
Tigran Aivazian <[EMAIL PROTECTED]> wrote:
>
> argggh couldn't they keep the rutgers.edu to be valid... or keep
> redhat.com - it's much easier to remember than kernel.org :)
redhat.com easier to remember than kernel.org? We're talking bout the
kerne
Hi!
> > Is anyone using cramfs?
>
> We use cramfs everyday at http://handhelds.org with Linux
> 2.4.0-test6-rmk1-np2-hh1. We have no problems.
I use test4-pre3 from linux-vr tree.
> > I copy cramfs image from nfs onto /dev/ram0, then mount it. It mounts,
> > and first few accesses are okay, bu
Is it / will it be possible to run multiple, or at least two keyboards
before the new linux console code in 2.5?
What we would like to do is to run multiple user sessions off a single
machine. Using either Dualhead graphics cards, or simply using two
graphics cards, the display is not a problem (
On Tue, 5 Sep 2000, Richard Gooch wrote:
> > Yes. The userlevel tool can't handle other things without recompiling.
>
> Don't worry about that. I can add a rule to devfsd so it creates
> appropriate compatibility entries.
But the userlevel tool needs fixed too. Recompiling is fine, as long as
On Wed, Sep 06, 2000 at 09:36:08PM +1100, [EMAIL PROTECTED] wrote:
[...]
>
> Lots of people (myself included) would like to be able to debug and
> generally hack the Linux kernel but cannot due to lack of time and the
> steep learning curve imposed by the lack of a debugger and good
>
On Wed, 6 Sep 2000, Frank Peters wrote:
> My question is who cleared it the kernel or the malloc function in
> glibc?? (i found some code in glibc but nothing in kernel) thx
it's the second clear_user_highpage() in mm/memory.c that does the page
clearing in the typical malloc()-ed memory case.
From: "Ingo Molnar" <[EMAIL PROTECTED]>
> > If the Kernel Debugger creates faulty solutions through lack of
> > thinking, and asking why, then surely printk is at least as bad
> > because it allows somebody to view the operation of the kernel through
> > a keyhole darkly. [...]
>
> i'd like to qu
Alan Cox wrote:
>
> > 1. This function is only used in the poorly maintained ftape driver.
> >The usage there isn't appriopriate for modern kernels.
>
> The ftape driver isnt exactly poorly maintained. Its just not integrated into
> 2.3/2.4. Ftape 4.0 is still elsewhere
This is wrong, since
George Anzinger wrote:
>
> This patch, for 2.4.0-test6, allows the kernel to be built with full
> preemption.
Neat. Congratulations.
> ...
> The measured context switch latencies with this patch
> have been as high as 12 ms, however, we are actively working to
> isolate and fix the areas of t
Em Wed, Sep 06, 2000 at 02:42:02AM -0700, Joshua Uziel escreveu:
> Heya acme... seems you fixed the sr.c driver a bit too much and
> killed an #ifdef MODULE that was needed if you build without
Nope, I didn't touched this, Jens?
- Arnaldo
> modules (as I do on some of my SPARCs)... this change
On Wed, Sep 06 2000, Arnaldo Carvalho de Melo wrote:
> Em Wed, Sep 06, 2000 at 02:42:02AM -0700, Joshua Uziel escreveu:
> > Heya acme... seems you fixed the sr.c driver a bit too much and
> > killed an #ifdef MODULE that was needed if you build without
>
> Nope, I didn't touched this, Jens?
Yeah
>Hi !
>This is a bug reporting, included are the output of various /proc file on
>my system:
>Motherboard: ASUS P2B-F with the latest bios bx2f113.awd (microcode update)
>ISDN: Winbond based card (Hisax type=36)
>Distribution: based on updated SuSE 6.4
>The problem is that if I compile the kernel
On Wed, Sep 06, 2000 at 08:46:46AM +0200, Christoph Hellwig wrote:
> On Tue, Sep 05, 2000 at 11:51:14PM -0600, Richard Gooch wrote:
> > > I can't use /dev/lvm, too because this is the name of the control file
> > > without lvm (and the lvm tools will barf if this is a dircetory.
> >
> > Well, how
Hubert Tonneau wrote:
>
> Benchmarking Pliant (http://pliant.cx/) semaphores led to unexpectedly
> low results. The problem to either kernel bad features or bugs in my
> program since Pliant uses no glue library such as glibc: it calls
> directly kernel funtions.
>
> Not enough scheduling proble
> What IS this urge to be handicapped
> when trying to debug the most important pieces of what gets
> delivered on the distribution CDROMs. Is it, "I'm so hairy chested
> that I can code with one metaphorical arm tied behind my
> equally cliched back?"
There are those that like to visualize thing
On Wed, Sep 06, 2000 at 03:48:53PM +, Heinz J. Mauelshagen wrote:
> > I can add a patch that does full-blown devfs
> > checking to the tools, but this needs a lot of work.
>
> Actually changing the tools to recognize devfs seems fairly simple.
> I am already working on it.
>
> _But_ the LVM M
"J. Dow" <[EMAIL PROTECTED]> said:
[...]
> I note again that the same arguement applies vis a vis printk
> and desk checks with a paper and pencil. The printk leverages
> the capable person's time. The kernel debugger leverages
> the capable person's time. What IS this urge to be handicapped
> w
Hello all,
I feel the need to shed some light on this subject from the viewpoint of
one MUCH less capable than the others here.
Recently I purchased a PPC 7200. It is a beat up old mac that I could pick
up cheap. I have used intels since I was a boy (SysV3.3 on 386!) and saw
some characteristics
On Wed, Sep 06, 2000 at 04:02:15PM +0200, Christoph Hellwig wrote:
> On Wed, Sep 06, 2000 at 03:48:53PM +, Heinz J. Mauelshagen wrote:
> > > I can add a patch that does full-blown devfs
> > > checking to the tools, but this needs a lot of work.
> >
> > Actually changing the tools to recognize
On Mon, 4 Sep 2000, Andi Kleen wrote:
> > /proc/sys/net/ipv4/\"correct\"_arp_reply_interface_selection
> It is called arpfilter. Here is the old 2.2.16 version (applies to 2.4
> with minor changes)
>
> It is useful for various things, one of them being automatic load
> balancing for incoming con
--On 09/05/00 21:35:13 -0400 Chris Mason <[EMAIL PROTECTED]> wrote:
>
> Ok, hopefully this will make sense...
>
> __block_commit_write calls balance_dirty, which might wait on bdflush,
> running all the io on the page. The async_end_io handlers will unlock
> the page once io on all the buffer h
On Tue, Sep 05, 2000 at 07:14:02PM -0700, Linus Torvalds wrote:
> How about this patch?
Got this oops.
Tim.
*/
ksymoops 2.3.3 on i586 2.4.0-test8-pre5+trfix. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.0-test8-pre5+trfi
On Wed, 06 Sep 2000, A Duston wrote:
> Hello,
>
> I am trying to contact the ps2esdi maintainer, as I have
> some questions about the driver. I have an ancient PS/2
> Thinkpad that gives an annoying but cosmetic error when
> it boots.
I can't recall a time where that cosmetic error didn't exist
David S. Miller wrote:
> Alexey tried to do this "fix" and when I tested his change we spotted
> this issue and thus did not put the "fix" in what we sent to Linus.
Is this patch available somewhere on the net? I really need it.
-
To unsubscribe from this list: send the line "unsubscribe lin
Guido Trentalancia schrieb:
Hello Guido,
>
> >Hi !
> >This is a bug reporting, included are the output of various /proc file on
> >my system:
> >Motherboard: ASUS P2B-F with the latest bios bx2f113.awd (microcode update)
> >ISDN: Winbond based card (Hisax type=36)
> >Distribution: based on up
On Tue, 5 Sep 2000, Andrey Savochkin wrote:
> Hello,
>
> On Sun, Sep 03, 2000 at 02:57:54PM -0300, Cesar Eduardo Barros wrote:
> >
> > I'm having endless problem with an eepro100 here. After some trying found out
> > that doing a soft reset (ctrl+alt+del) fixed the problem, and that a power
> >
* Admin Mailing Lists ([EMAIL PROTECTED]) wrote:
> On Tue, 5 Sep 2000, Andrey Savochkin wrote:
>
> > On Sun, Sep 03, 2000 at 02:57:54PM -0300, Cesar Eduardo Barros wrote:
> > >
> > > I'm having endless problem with an eepro100 here. After some trying found out
> > > that doing a soft reset (ctrl
Jamie Lokier writes:
> Chris Wedgwood wrote:
> > I think would be really cool if all this 'magic' in gcc (whatever
> > part of gcc is irrelevant right now) would be exported into a library
> > or shared object which editors could then load and use... dynamically
> > perhaps.
>
> Sorry, there's a
Hi
Here is a patch for the acenic-v0.46 driver relative to whats in
test8-pre4 - it solves a few bugs and cleans up a few minor issues in
the code and comments.
I have been unable to test this patch but looking over the changes I
cannot see any reason why it would cause problems.
Jes
--- ../li
On Wed, 6 Sep 2000, Chris Mason wrote:
>
> Ah, I was missing that __block_prepare_write and __block_write_fullpage
> both set the end_io handler to end_io_sync. In one case, reiserfs is doing
> i/o without properly setting the handler, which is why I was seeing bugs
> caused by the above pr
On Wed, 6 Sep 2000, Tim Waugh wrote:
> On Tue, Sep 05, 2000 at 07:14:02PM -0700, Linus Torvalds wrote:
>
> > How about this patch?
>
> Got this oops.
This one I cannot explain.
It's a bh that is NULL, but it's a new case completely. It looks like you
have a 1kB blocksize, no? It furthermore
On Wed, 6 Sep 2000, Alan Cox wrote:
> > As readability - it's definitely at least as readable as
> > #if[def]. It also provides more consistent syntax. And when you are
> > using ifdef to violate scoping - your code is in need of rewrite anyway.
>
> You still need the #ifdef stuff as well
On Wed, 6 Sep 2000, Rik van Riel wrote:
> Nope. These magic numbers were added as a stopgap
> measure when VM was completely fouled up in 2.1.89.
ok, but at least do you agree that that tunable is unused and therefore
can be thrown away? Or are you saying it is unused today but shall be used
tomo
On Wed, 6 Sep 2000, Martin MaD Douda wrote:
> Problem: every bloody line will go through the parser. There is too many
> lines. Compilation is realy slow today. I'm affraid this approach would
> make it worse. Note that 2.4.0-test7 has more than 2.75 milion lines.
> Or did you mean drivers wil
Mike Jagdis wrote:
> I disagree. No one here is dumb enough to use a wholely inappropriate
> tool for a particular task. But using a debugger is often (but not
> always) like sawing bits off your 2x4 until it happens to fit the
> gap. What you need to do is to understand the problem parameters,
>
On Wed, 6 Sep 2000, Tim Waugh wrote:
> On Tue, Sep 05, 2000 at 07:14:02PM -0700, Linus Torvalds wrote:
>
> > How about this patch?
>
> Got this oops.
> Code; c012cae6<=
>0: 8b 00 movl (%eax),%eax <=
Offset 0 is ->b_next... Huh? It should be ->b_th
On Wed, 6 Sep 2000, Richard Gooch wrote:
> Jamie Lokier writes:
> > Chris Wedgwood wrote:
> > > I think would be really cool if all this 'magic' in gcc (whatever
> > > part of gcc is irrelevant right now) would be exported into a library
> > > or shared object which editors could then load and
On Wed, 6 Sep 2000, Tigran Aivazian wrote:
> On Wed, 6 Sep 2000, Rik van Riel wrote:
> > Nope. These magic numbers were added as a stopgap
> > measure when VM was completely fouled up in 2.1.89.
>
> ok, but at least do you agree that that tunable is unused and
> therefore can be thrown away?
I c
Jes,
I've been debugging a new acenic device for HP and have been using a
linux machine for bring up. One of the problems we encountered was a
need to change the cards MAC address. Under linux ia32, the driver set
an invalid MAC address. If I would
say
ifconfig eth0 hw ether 00:01:23:
Alexander Viro writes:
>
>
>
> On Wed, 6 Sep 2000, Richard Gooch wrote:
>
> > Jamie Lokier writes:
> > > Chris Wedgwood wrote:
> > > > I think would be really cool if all this 'magic' in gcc (whatever
> > > > part of gcc is irrelevant right now) would be exported into a library
> > > > or shar
On Mon, 4 Sep 2000, Tigran Aivazian wrote:
> On Fri, 25 Aug 2000, Arnaldo Carvalho de Melo wrote:
> > now the driver init sequence is not
> > serialized anymore, so races are possible
>
> since when? In 2.4.0-test8-pre2 mod->init and mod->cleanup are called
> under global kernel lock. As for
A reboot with 2.4.0-test7 (on i386 at least) doesn't properly "release"
the card and hang the computer after displaying Linux PCMCIA options, just
before YENTA IRQ is displayed no matter which kernel is then used to boot
or segfault windows 98SE. Only way is to turn down computer. With the
same
Em Wed, Sep 06, 2000 at 05:37:50PM +0100, Tigran Aivazian escreveu:
> On Mon, 4 Sep 2000, Tigran Aivazian wrote:
>
> > On Fri, 25 Aug 2000, Arnaldo Carvalho de Melo wrote:
> > > now the driver init sequence is not
> > > serialized anymore, so races are possible
> >
> > since when? In 2.4.0-t
Also sprach Dan Aloni:
} On Wed, 6 Sep 2000, Peter Samuelson wrote:
}
} > Can someone explain this line from the VIA update?
} > #define FIT(v,min,max) (((v)>(max)?(max):(v))<(min)?(min):(v))
} > Barring side effects on the variables, it is equivalent to
} > #define FIT(v,min,max) ((v)<(min)?
In article <[EMAIL PROTECTED]>,
Andrew Morton <[EMAIL PROTECTED]> wrote:
>
>But still, doing the conditional compilation at compile-time rather than
>preprocessing-time is so *nice* that if you don't have too many literal
>strings floating about it may be justifiable.
>
>In cs89x0.c you reduce th
In article <[EMAIL PROTECTED]>,
Jamie Lokier <[EMAIL PROTECTED]> wrote:
>Linus Torvalds wrote:
>> And I'm saying that if people really want to do this, then use the
>> computer to do it for you, having more than just "grep", and making your
>> tools aware of it.
>
>I'd just like to add, for the b
There is a race condition somewhere in linux-2.2.15 and 2.2.16 that is
demonstrated here.
Cut and save the included 'Makefile'.
Execute:
mkdir zam
mv Makefile zam
cd zam
Make sure you are in the empty directory with only "Makefile"
Execute:
while true ; do make clean ; done
The file, Makefi
In article <8p5u21$r0$[EMAIL PROTECTED]> you wrote:
> However, what I think Al Viro dislikes about this is that it does tend
> to leave code that won't compile, just because some of the accesses are
> in places that the compiler doesn't see due to the pre-processor (or due
> to other build-rules:
We could use some more infrastructure here.
(1) A 'make randomconfig' tool that generates a random configuration.
(2) Make the architecture a configuration variable (!)
(3) A collection of RPM's so that people can download and install
all the cross tools easily.
With this stuff available,
Isn't it time to offer the platitude about working smarter rather than
harder?
Nah, probably not.
Marty
-Original Message-
From: Alan Cox [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 06, 2000 2:20 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECT
On 6 Sep 2000, Linus Torvalds wrote:
> At the same time, there is no question that true #ifdef's have
> advantages, even outside the issue of gcc's inability to forget literal
> strings. They are often required for data structures in general: C does
> not have "conditional data structures". C
On Wed, 6 Sep 2000, Michael Elizabeth Chastain wrote:
> We could use some more infrastructure here.
>
> (1) A 'make randomconfig' tool that generates a random configuration.
>
> (2) Make the architecture a configuration variable (!)
>
> (3) A collection of RPM's so that people can download a
On Wed, 6 Sep 2000, mberglund wrote:
> Recently I purchased a PPC 7200. It is a beat up old mac that I could pick
> up cheap. I have used intels since I was a boy (SysV3.3 on 386!) and saw
> some characteristics of the mac that were lacking in the intel boxes.
>
> Finally, I tried to use the bo
On Wed, 6 Sep 2000, Michael Elizabeth Chastain wrote:
>
> We could use some more infrastructure here.
>
> (1) A 'make randomconfig' tool that generates a random configuration.
There already are people that do this.
The problem is that developers are lazy. All good programmers are lazy.
They w
On 6 Sep 2000, Linus Torvalds wrote:
> However, what I think Al Viro dislikes about this is that it does tend
> to leave code that won't compile, just because some of the accesses are
> in places that the compiler doesn't see due to the pre-processor (or due
> to other build-rules: like in arch
r
> (0) knowledge that CONFIG.FOO15 doesn't affect anything other than set of
> source files being compiled.
The Makefiles already know this. Specifically, mkdep.c analyzes which
C files depend on which options. Look at some of your .depend files.
Michael
-
To unsubscribe from this list: send
Linus writes ...
mec> (2) Make the architecture a configuration variable (!)
linus> Why?
The real reason is that it's the right thing to do. Part of a
configuration is "what machine it's for".
Here are some benefits:
(a) Arjan's testing machinery would catch problems in all architectures,
It appears that SCSI cdroms as modules are broken in 2.4.0-test8.
It works fine 2.4.0-test7.
cat /dev/scd0
cat: /dev/scd0: No such device
Module Size Used by
isofs 20168 0 (autoclean)
sg 21712 0 (unused)
sr_mod 13224
Alexander Viro wrote:
>
> On Wed, 6 Sep 2000, Michael Elizabeth Chastain wrote:
>
> > We could use some more infrastructure here.
> >
> > (1) A 'make randomconfig' tool that generates a random configuration.
> >
> > (2) Make the architecture a configuration variable (!)
> >
> > (3) A collection
On Wed, Sep 06 2000, Lawrence Walton wrote:
> It appears that SCSI cdroms as modules are broken in 2.4.0-test8.
> It works fine 2.4.0-test7.
>
>
> cat /dev/scd0
> cat: /dev/scd0: No such device
Yup, apparently I was a bit too trigger happy.
--
* Jens Axboe <[EMAIL PROTECTED]>
* SuSE Labs
Mike Galbraith wrote:
>
> On Wed, 6 Sep 2000, Damien Miller wrote:
>
> > Tools like a KDB would make the kernel a lot more accessible to the
> > time-poor.
>
> Kdb is available to all. I think it should be _integrated_ mostly
> because of the (potential) improvement in bug report quality.
Wel
On Wed, 6 Sep 2000, Alexander Viro wrote:
>
>
> On 6 Sep 2000, Linus Torvalds wrote:
>
> > However, what I think Al Viro dislikes about this is that it does tend
> > to leave code that won't compile, just because some of the accesses are
> > in places that the compiler doesn't see due to the
I agree completely. I'd love to see it there.
I'd even help break^W fix it.
~Randy
___
|Randy Dunlap Intel Corp., DALSr. SW Engr.|
|randy.dunlap.at.intel.com503-696-2055|
|NOTE: Any views presented here are mine alone |
|and
On Wed, Sep 06 2000, Jens Axboe wrote:
> > It appears that SCSI cdroms as modules are broken in 2.4.0-test8.
> > It works fine 2.4.0-test7.
Bah, try this one instead...
--
* Jens Axboe <[EMAIL PROTECTED]>
* SuSE Labs
--- /opt/kernel/linux-2.4.0-test8-pre5/drivers/scsi/sr.cWed Sep 6 0
Daniel,
very nice monologue, thanks. It would be great to know Linus' opinion. I
mean, I knew Linus' opinion of some years' ago but perhaps it changed? He
is a living being and not some set of rules written in stone so perhaps
current stability/highquality of kdb suggests to Linus that it may be
On Wed, 6 Sep 2000, Martin Dalecki wrote:
>
> So may I just suggest to repleace the usage of cpp at all with something
> more
> suitable for the task at hand and with a much more regular/stringent
> syntax
> better fitting into the syntax of the pure C language like m4 for
> example?
>
No. S
Alan Cox wrote:
> I've spent over 2 years trying to extract eepro100 server docs out of Intel
> and failed.
Sounds familiar :-)
According to group legend here (I wasn't around but will repeat what I
was told), we spent about 1 year trying to get docs on Intel's i960
based gigabit card so we coul
On Wed, 6 Sep 2000, Alexander Viro wrote:
>
> Add "and that broken code gets fixed in utterly bogus ways 20 versions
> down the road, when nobody remembers WTF had happened". Repeat several
> times (and rarely-used parts _will_ accumulate such crap) and you've got
> Lovecraftian beasts lurking
In article <[EMAIL PROTECTED]> you wrote:
> Linus writes ...
> mec> (2) Make the architecture a configuration variable (!)
> linus> Why?
> The real reason is that it's the right thing to do. Part of a
> configuration is "what machine it's for".
> Here are some benefits:
> (a) Arjan's testing
Alexander Viro wrote:
>
> On Wed, 6 Sep 2000, Martin Dalecki wrote:
>
> >
> > So may I just suggest to repleace the usage of cpp at all with something
> > more
> > suitable for the task at hand and with a much more regular/stringent
> > syntax
> > better fitting into the syntax of the pure C la
Alan Cox wrote:
> I've spent over 2 years trying to extract eepro100 server docs out of Intel
> and failed.
[EMAIL PROTECTED] said:
> Sounds familiar :-)
Very familiar. I have a whole development environment for the i960RP
(we use the processor on boards we make) and by looking at pictures
I wa
Hi,
Just installed linux-2.4.0-test7, but I noticed that the modules get
installed
/lib/modules/`uname -r`/kernel/drivers/...
which is different from previous kernels. Do I need to modify modules
path in conf.modules in order that the modules can be found during
boot? or is there an u
Hello!
I'm just trying to compile a kernel for my sparc and found a bug in the
above file:
In line 170:
dev->de = devfs_register (devfs_handle, devname, DEVFS_FL_DEFAULT,
VFC_MAJOR, instance,
S_IFCHR | S_IRUSR | S_IWUSR,
* Jens Axboe <[EMAIL PROTECTED]> [000906 06:32]:
> On Wed, Sep 06 2000, Arnaldo Carvalho de Melo wrote:
> > Em Wed, Sep 06, 2000 at 02:42:02AM -0700, Joshua Uziel escreveu:
> > > Heya acme... seems you fixed the sr.c driver a bit too much and
> > > killed an #ifdef MODULE that was needed if you bu
On Wed, 6 Sep 2000, Arnaldo Carvalho de Melo wrote:
> Em Wed, Sep 06, 2000 at 05:37:50PM +0100, Tigran Aivazian escreveu:
> > On Mon, 4 Sep 2000, Tigran Aivazian wrote:
> >
> > > On Fri, 25 Aug 2000, Arnaldo Carvalho de Melo wrote:
> > > > now the driver init sequence is not
> > > > serializ
1 - 100 of 231 matches
Mail list logo
