[Android]
> 1) There is a link in /lib/modules/2.4.0.11: build->/usr/src/linuxcreated by the
>Makefile (make modules_install). What for?
Many people limit their e-mail messages to 80 columns. What for?
The 'build' symlink is to make it easier for external module
installation scripts to find th
[Marc Mutz <[EMAIL PROTECTED]>]
> Should that not be first converted to paths that contain no symlinks?
I agree.
--- Makefile~ Tue Nov 28 21:53:31 2000
+++ MakefileFri Dec 1 12:25:28 2000
@@ -10,7 +10,7 @@
CONFIG_SHELL := $(shell if [ -x "$$BASH" ]; then echo $$BASH; \
else if
[Marc Mutz]
> > +TOPDIR := $(shell pwd -P)
> That is specific to the bash builtin 'pwd'. GNU sh-util's pwd does
> not know that option (at least not my version, which is: "pwd (GNU
> sh-utils) 1.16")
It passed my 5-second shell feature portability test (ash). Checking
again, I see that the ash
[Tracy Camp]
> A much cleaner patch prompted after right proper chastisement on the
> sloppy patch I sent a few days back. This one is against 2.4-pre11
Hmmm, I don't like your array thing (also in v.I of the patch),
limiting us to possible root devices, where n==8. A better
approach might be
[I wrote]
> Your patch makes it impossible, in this situation, to override the
> default root device from the syslinux command line. A kludge to make
> it work again would be to process the root devices in reverse.
Better would be to reset the list of root devices with every 'root='
statement,
[Roger Crandell]
> When I boot the machine with the multiprocessor kernel and run
> iptables, the kernel dumps several pages of hex and the final two
> lines of output are:
>
> Killing interrupt handler
> scheduling in interrupt
Look through the "several pages of hex" for any number in square +
[Tracy Camp]
> I was unsure if it was okay to be using kmalloc during early stages
> of init/main.c so I decided to follow the example allready set and
> just use a static array - can anyone advise on being able to do this
> dynamically?
Have a static 'char *' somewhere. In the "root=" callback
[Jamie Manley]
> Yes, modversions was enabled. Should that be affecting the build of
> the kernel proper?
The bug you ran into is that MODVERSIONS messes up the
'get_module_symbol' function, which is a sort of "optional dependency"
mechanism used by a few modules such as DRI (in this case: DRI
[Christopher Friesen]
> I think you should re-read the GPL. You only have to provide source
> to people to whome you have distributed your new binaries, and you
> only have to provide that source if you are asked for it.
Oh, and you have to provide the complete text of the GPL as well, and
for
[Wolfgang Spraul]
> I didn't find the "Transmeta" thread, though.
> In the thread you mentioned, did they post any patches?
http://marc.theaimsgroup.com/?l=linux-kernel&m=97573394612476&w=2
No patch but a description, and Linus will apparently put it in the
next prepatch.
Peter
-
To unsubscrib
[Frédéric L . W . Meunier]
> What's the best way to use make oldconfig with menuconfig?
> oldconfig with config isn't what will make my life easier.
You mean you want menuconfig, but only one small menu with the new
options? Can't be done, currently.
Peter
-
To unsubscribe from this list: send
A patch hunk got duplicated somewhere, it seems.
--- test12pre3/include/linux/pci_ids.h~ Sat Dec 2 19:23:51 2000
+++ test12pre3/include/linux/pci_ids.h Sat Dec 2 20:45:53 2000
@@ -406,10 +406,6 @@
#define PCI_DEVICE_ID_ELSA_MICROLINK 0x1000
#define PCI_DEVICE_ID_ELSA_QS3000 0x3000
[Albert D. Cahalan]
> If one disk works and another one not, one might suspect
> that the wrong DMA mode is being used in the crashing case.
So, what DMA mode do *you* usually set for aic7xxx? (: (:
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
[Pavel Machek]
> Hmm, add special code for GPL into gzip ;-).
Someone on debian-devel thought of this, but went one further: change
the gzip header magic so that only a "GPL-enabled" gzip can decompress
it.
I wonder how the zlib maintainers (zlib is not GPL) would feel about
having to add suppo
[Mohammad A. Haque]
> Cool. Anyone have have a unified patch against pre4 or should I start
> digging through my mail? =)
test12pre5, I guess.
Peter
-
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
Adam, could you check my work here? I haven't done this before It
compiles, but I don't have the hardware to verify anything. And, being
a lousy kernel hacker, I've probably introduced at least one bug.
Peter
diff -urk~ test12pre5/drivers/sound/Config.in~ test12pre5/drivers/sound/Config
[Linus]
> > (otherwise I'll just end up disabling shared mmap - I doubt anybody
> > really uses it anyway, but it would be more polite to just support
> > it).
[Peter Rönnquist]
> I was thinking about using mmap for shared mememory in my program,
> but now I am reconsidering. Is the System V o
[Ivan Passos]
> - One ioctl that passes a pointer to a known structure in
> ifr.ifr_data as its argument.
struct sync_params_ioctl_data {
int opcode;
union {..
Seems straightforward to me. Basically just ioctl numbers within ioctl
numbers.
Peter
-
To unsubscribe from this list: send
[Lukasz Trabinski]
> > I know about it, but the compiler does.
[Mike A. Harris]
> Not sure what you mean however no part of the linux kernel ever uses
> glibc at all. It is not possible to do so in fact.
He means that gcc is linked to libc, so a libc bug could possibly
affect gcc. I have not
[Tigran Aivazian]
> I think 'flags' is what it used to be called ages ago but that is
> irrelevant -- everyone presumably already changed all their software
> to use 'features' (I did, for example) and forgot about the old
> 'flags' forever
Ages ago? s/flags/features/ happened in test11pre5.
[Tigran Aivazian]
> The only reason one could think of was to "hold the lock for as short
> time as possible" but a minute's thought reveals that such reason is
> invalid (i.e. one is more likely to waste time spinning on the lock
> than to save it by dropping/retaking it, given the relative dura
[Peter Samuelson]
> > Whether a memset of 92 bytes (on 32-bit arch), plus an
> > atomic_set(), are worth deserializing, I do not know.
[Tigran Aivazian]
> Of course, they are worth it. Actually, I don't understand how can
> you even doubt it?
Clearly we are talking at
[[EMAIL PROTECTED]]
> dummy.c: In function `dummy_init_module':
> dummy.c:103: invalid type argument of `->'
Known bug. They say the fix is in Linus's patch queue.
--- include/linux/module.h~ Tue Dec 5 00:53:23 2000
+++ include/linux/module.h Tue Dec 5 17:24:47 2000
@@ -345,7 +345,7
[Roberto Ragusa]
> BTW, here is a little patch regarding a silly problem I found
> about RAID partitions naming (/proc/partitions).
> No more "md8" "md9" "md:" "md;" ... but "md8" "md9" "md10" "md11" ...
> Well, this patch should work up to "md99".
This stuff *really* should be split out into th
[Steven Cole]
> The following patch may seem ridiculous
> -o modutils 2.3.18 # insmod -V
> +o modutils 2.3.21 # insmod -V
It's not ridiculous at all. Documentation/Changes definitely needs to
reflect reality.
Peter
-
To unsubscri
[Brian Kress <[EMAIL PROTECTED]>]
> I got resounding silence to posting the patch last time, so I'm not
> sure if anyone actually wants this patch,
Well, I like it, but admittedly it's mostly in the "cleanup" category
(though it does fix the LVM name issue) so at this point in 2.4 I guess
Linus
[Timothy A. DeWees]
> Could someone be so kind to point me to a page where I can find a
> list of parameters I can pass to a kernel on boot.
Documentation/kernel-parameters.txt
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PRO
[Reto Baettig]
> Imagine we have a virtual disk which provides a 64bit (sparse)
> address room. Unfortunately we can not use it as a block device
> because in a lot of places (including buffer_head structure), we're
> using a long or even an int for the block number.
Actually it should be 'unsi
[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
[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:
[Jorge Nerin]
> How can I make a incremental patch of two other patches without
> making two trees?
There do exist tools for this but I have found them limiting. I'm
working on my own utility to do this (and other patch manipulations,
such as cdiff -> udiff) but don't have an ETA. I'll let you
[viro]
> > making the internal API frozen by exposure to library users.
[Gooch]
> An exercise in decent API design. BFD.
^^^
Nah, that's the *de*compilation library.
(Sorry, couldn't resist.)
Peter
-
To unsubscribe from this list: send the line "unsubscrib
[viro]
> 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
> branches just fine.
Notwithstandin
[mec]
> In the .config file, the problem is that the Makefiles source .config
> and then do a lot of "ifdef CONFIG_FOO" tests. There are about 300
> instances of this in 2.4.0-test-7.
Separate issue. We're not talking about emitting n symbols to .config,
or at least I'm not. In this thread.
[Tigran]
> > I like this one even better:
> >
> > "Little children, keep yourselves from idols" -- St John, Ist century.
[rgooch]
> Hm. Does that apply also to all the statues of saints, the virgin
> mother and all those crosses with Jesus that you find in churches,
> hanging off people's nec
[Matthew Kirkwood]
> +ifeq ($(CONFIG_BLK_DEV_MD),y)
> +SUB_DIRS += md
> +MOD_SUB_DIRS += md
> +else
> + ifeq ($(CONFIG_BLK_DEV_MD),m)
> + MOD_SUB_DIRS += md
>endif
> endif
>
Drop the 'else' bit; CONFIG_BLK_DEV_MD cannot be 'm'.
> +obj-n:=
> +obj- :=
These two va
[<[EMAIL PROTECTED]>]
> >I would like to upgrade my kernel which is bundled with Red Hat.
[kaos]
> Ask redhat for the .config, this is not a problem for the
> linux-kernel list.
Also you might make sure you have any relevant RH patches installed.
Not being a RH user, I don't know which ones th
[Mark James]
> That is, can a kernel module open and read files or sockets, call
> libc functions, start processes?
* Read files/sockets: you need a process context. That means if you
are running in an interrupt you are SOL and if you are in an existing
process context, the context owner mig
[Cahalan]
> Well, what do you care about most? The problem can be solved in
> other, more disturbing ways. :-) For example, gcc's computed goto.
[code snipped]
You are sick. (:
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PR
[Jeremy Higdon]
> Is there a little FAQ of C constructions you should not use if you
> are writing kernel code? It took a little doing to figure out that
> it was the switch that was causing trouble and not the shifts and
> arithmetic operations, and I'd like to avoid that in the future :-).
He
[Terence Ang]
> Could anyone kindly tell me how to setup software RAID1 on IDE drives
> under RedHat 6.2?
> I have got one extra PCI IDE card with 2 hard disks (not mentioning
> the existing Linux OS hard disk)
> It seemed that the card could not be detected under Linux.
It looks like you will n
[Mark James <[EMAIL PROTECTED]>]
> In summary:
>
> - Kernel code can't or shouldn't do anything too high-level.
In general, yes. This is why the winmodem driver people (last I heard)
are trying to pull some of the modem functions out into userspace
programs. Sync and cancellation algorithms f
[Andrea]
> LVM and MD have nothing common. They're two completly orthogonal
> piece of code
Right. Functionally they overlap (lvm can do the equivalent of md
linear) but structurally, the md drivers all operate under the md
framework and user-toolset while lvm has its own framework and toolset.
[mec]
> Can you characterize the problem in more detail for me? That is,
> exactly what link order constraints you are trying to obey.
As has been explained, scsi lowlevel (drivers) need to come before scsi
toplevel (sd, sr, st, sg) because sd and sr cannot dynamically resize
arrays of drives --
[I wrote]
> Unfortunately, your drivers/scsi/foo.o actually represents the
> zillions of host drivers we have, so the DRIVERS assignment starts to
> look rather daunting and hackish.
I retract that -- I had forgotten that lowlevel is all pulled into
hosts.o.
Peter
-
To unsubscribe from this lis
[Igmar Palsenberg]
> Patch looks not necessary. The compiler executes the statements until it
> encounters a break.
>
> > - case BTN_EXTRA: if (list->mode > 1) { index = 4; break; }
> > + case BTN_EXTRA: if (list->mode > 1) index = 4; break;
^^^
You
t;, minor);
@@ -775,8 +777,9 @@
return (md_dev[minor].pers->map(md_dev+minor, rdev, rsector, size));
}
-int md_make_request (int minor, int rw, struct buffer_head * bh)
+int md_make_request (struct buffer_head * bh, int rw)
{
+ int minor = MINOR (bh->b_dev);
if (md_dev [mino
[aa]
> Ok, I see your point of grouping them together.
>
> So I think drivers/sm (Storage Management) would be cleaner. LVM and
> MD are two implementations of Storage Management.
But most if not all block drivers, and some char drivers for that
matter, could be considered part of "storage man
[Alvaro Lopes]
> So, I have now the same filesystem mounted in two mountpoints.
>
> Is this OK ? It used not to be.
Yes. Part of Al Viro's vfs overhaul a couple months back.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROT
[Peter Samuelson]
> > "md", on the other hand, is well-established as referring to Linux
> > RAID, but if you add lvm the label is too narrow.
[Linus]
> Yes, we have all thes _historical_ reasons why people think "md"
> refers to the particular RAID
Not that any of us who don't do embedded projects ought to care very
much, but I was curious. I grepped test9pre6 for globals initialized
to 0 or NULL and came up with 2495 lines, first iteration. At 4-byte
alignment this works out to something over 9k of .data that should be
.bss (not that any
[Tigran Aivazian <[EMAIL PROTECTED]>]
> The question you ask can be answered trivially - yes, it is
> definitely a good idea, please make such a patch.
OK, I'll look at it.
> But what is far from being trivial is the magic reg. expression that
> is capable of catching all "globals initialized t
[Wakko Warner]
> While this subject is fresh, what would be wrong with using the
> entire drive as opposed to creating a partition and adding the
> partition to the raid?
Does it autodetect an entire drive? The autodetect logic for
partitions looks at the 'partition type' byte, which of course d
[rth]
> > Which was a nice idea, but it doesn't actually work. Changes
> > in spec file format between versions makes this fall over.
[Dominik Kubla]
> Wow. So much for reading the manual... well, that's considered
> cheating anyway, isn't it?
I know this was true at one time -- egcs couldn'
[Rusty]
> > CC=gcc-2723 make 2.0 kernel
> > CC=gcc-2723 make 2.2 kernel
> > CC=egcs make 2.4 kernel
>
> No, environment doesn't override make variables by default. This
> works on any shell:
>
> make CC=egcs
If you're going to get pedantic, that won't work either -- since the
makefiles
> So which is the recommended compiler for each kernel version 2.2.x,
> 2.4.x(pre?) nowadays?
* 2.91.66 aka egcs 1.1.2. It has been officially blessed for 2.4 and
has been given an informal thumbs-up by Alan for 2.2. (It does NOT
work for 2.0, if you still care about that.)
* 2.7.2.3 work
[Linus]
> In short, we should _remove_ all traces of stuff like
>
> O_OBJS = $(filter-out $(export-objs), $(obj-y))
>
> It's wrong.
>
> We should just have
>
> O_OBJS = $(obj-y)
>
> which is always right.
This part I agree with..
> And it should make all this FIRST/LAST object
[kaos]
> > It still does not document the only real link order constraint in
> > USB. The almost complete lack of documentation on which link
> > orders are required and which are historical is extremely annoying
> > and _must_ be fixed, instead we just propagate the problem.
[Linus]
> We can
[rmk]
> > Take the instance where we need to link a.o first, z.o second, f.o
> > third and p.o fourth. How does LINK_FIRST / LINK_LAST guarantee
> > this?
It does. Read the patch. LINK_FIRST *itself* is not sorted.
> > LINK_FIRST = a.o z.o
> > LINK_LAST = f.o p.o
> >
> > But then what guar
[Vladislav Malyshkin <[EMAIL PROTECTED]>]
> You can easily remove duplicates in object files without sorting.
> You can just use a shell written function.
This is true. That was something I forgot to mention. I have looked
at that as well, and it strikes me as even more of a hack than the
solu
[Linus]
> But it doesn't even WORK.
>
> You need to have
>
> LINK_FIRST1
> LINK_FIRST2
> LINK_FIRST3
> ...
>
> etc to get the proper ordering.
??? No you don't. Perhaps you mean something else. Here's how
LINK_FIRST works:
Say you have foo.o, bar.o, baz.o and lots
[Russell King]
> Since someone kindly enlightened me that LINK_FIRST was unsorted, I'm
> finding it very hard to grasp what the difference is between an
> unsorted LINK_FIRST and unsorted LINK_LAST list, and an unsorted
> obj-y list. From what I understand, obj-y = $(LINK_FIRST)
> $(LINK_LAST) ?
[hpa]
> I was going to ask to what extent we genuinely need sorting, and if
> we might be better off trying to eliminate that need as much as
> possible.
We don't need sorting. We need removing of duplicates. The GNU make
sort function removes duplicates as a side effect, which is why we want
[Peter Samuelson]
> > There are two ways to handle this:
> >
> > obj-$(CONFIG_WD80x3) += wd.o 8390.o
> > obj-$(CONFIG_EL2) += 3c503.o 8390.o
> > obj-$(CONFIG_NE2000) += ne.o 8390.o
> > obj-$(CONFIG_NE2_MCA) += ne2.o 8390.o
> > obj-$(CONFIG_H
[Jeff Merkey]
> > > The numbers don't lie. [...]
> >
[Ingo Molnar]
> > sure ;) I can do infinite context switches! You dont believe? See:
> >
> > #define schedule() do { } while (0)
[Jeff]
> Actually, I think the compiler would optimize this statement
> completely out of the code
[me]
> > So the real question is, how many gettimeofday() per sec can Linux
> > do?
[Larry McVoy]
> Oh, about 3,531,073 on a 1Ghz AM thunderbird running
> Linux disks.bitmover.com 2.4.0-test5.
So, at two "context switches" (Jeff's term) per syscall, we're
somewhere around half the speed of N
[hpa]
> I would tend to agree with Linus on that. If that's truly what
> you're doing, it would be rather nonobvious.
Well, ok, opinion vs. opinion. The thing is, userspace code almost
*never* needs to care about link order -- and, not counting boot loader
magic, kernel code didn't care about
[Vladislav Malyshkin <[EMAIL PROTECTED]>]
> Also, the function remove_duplicates can be written using make rules
> and functions. Using functions "foreach" "if" from make and
> comparison you can easily build a function remove_duplicates in make,
> no shell involved.
Could you please write me t
[Christoph Hellwig <[EMAIL PROTECTED]>]
> +
> +# include a local makefile, if present
> +-include Makefile.local
Why?
> +%.i: %.c
> + $(CPP) $(CFLAGS) $(EXTRA_CFLAGS) $(CFLAGS_$@) $< > $@
Why? Well, I know, it's historical, but does anyone think we actually
need this?
> +%.s: %.S
> +
[TenThumbs]
> I noticed that kwhich is called a lot:
>
> make oldconfig:10
> make dep: 65
> make bzImage modules: 142
Yes indeed, I suggested the ':=' when kwhich first went in, for this
reason. I suspect my mail was either ignored or overlooked.
That whole raft of variab
[matthew]
> ls /proc > killscript
> added "kill -9" to the beginning and "\" to the end of each line,
> ran it as the database user. It worked pretty well.
Sounds like a lot of trouble.
su {oracle} -c 'kill -9 -1'
Or is there some reason that wouldn't have worked in your case?
Peter
-
To u
[Jeff Merkey]
> Is this what is causing the lockup problems on 2.4.0-pre-10 with
> PPro, or something else. Looks like something else.
Yeah, it does, doesn't it. If this particular patch cured a
kernel-side lockup I would be very surprised. Because the only effect
this patch is *supposed* to
[Nitin Dhingra]
> I had got your mail from redhat.com and came to know you are
> working under drivers in Linux.
What you got was a mailing list of probably tens of thousands of
subscribers. Some of us are working on drivers, some are not.
> I am working in a project that involves making a lo
[yes I feed trolls sometimes, it's fun]
[Taco Witte]
> Some days ago, I read about the idea of a completely modular kernel.
> I think it's a very good idea, because it would make it easier to get
> more people work at the same moment, development would go faster.
I contend that the barrier to e
[Jeff V. Merkey <[EMAIL PROTECTED]>]
> I got a little further with the lock up problem, and it is related to
> MPS reporting a 2nd processor being present in some PPro systems when
> in fact only one CPU is really installed (but MPS is reporting
> default table entry 6 with a second CPU as presen
[Dan Aloni]
> > Then you run this script (I got it when Riel pasted it on IRC)
> >
> > for i in `find ./ -name \*.orig` ; do diff -u $i `dirname $i`/`basename $i
> > .orig` ; done
That works, but see http://bugs.debian.org/64958 for my variant: a
fairly trivial diff diff that adds a flag '-k'
[Robert Lynch]
> I've been regularly building kernels in the testXX series, and
> they have been coming out ~ 600K; test10-final and test11-pre1:
>
> -rw-r--r--1 root root 610503 Oct 31 18:39 vmlinuz-t10
> -rw-r--r--1 root root 610568 Nov 7 20:26 vmlinuz-t11p01
>
>
[Chmouel Boudjnah <[EMAIL PROTECTED]>]
> i would recommend to use the orig.el[1] from frederic.lepied with
> Emacs, it save any files before editing with a particuliar prefix
I'll take a look, thanks.
> and you can generate the patch with the gendiff script (included with
> rpm).
I did not kno
[Andrea Arcangeli]
> Can you think at one case where it's better to push the parameter on
> the stack instead of passing them through the callee clobbered
> ebx/eax/edx?
Well it's safer if you are lazy about prototyping varargs functions.
But of course by doing that you're treading on thin ice a
[Peter Anvin]
> At the time the original x86 ABI was created, a lot of C code was
> still K&R, and thus prototypes didn't exist...
True enough. That does explain a lot. But what about the Alpha? From
reading gcc source awhile back I seem to remember that most if not all
parameters are passed
[H. Peter Anvin <[EMAIL PROTECTED]>]
> but the Alpha is a *much* more recent ABI... the x86 ABI really dates
> back to the 16-bit 8086-series CPUs.
Oh, right. Xenix. I'd forgotten.
> We might try again in 2.5 since we now have increased the minimum gcc
> version for kernel compiles. Binutils
[Carlos E. Gorges]
> This fixes the unresolved symbol detect_wf_mpu to module
> wavefront .
>
> Patch attached.
1) Do not use gzipped attachments -- in fact do not use attachments at
all, unless the file you wish to attach is already in binary form, or
is extremely long. Inline text is less tr
[Dick Johnson]
> Do:
>
> char main[]={0xff,0xff,0xff,0xff};
Oh come on, at least pick an *interesting* invalid opcode:
char main[]={0xf0,0x0f,0xc0,0xc8};/* try also on NT (: */
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [E
[AC]
> > [EMAIL PROTECTED] is alive and well however.
[Pavel Roskin]
> You cannot imagine how frustrating it was to search for the archive.
> I couldn't find an up-to-date archive, and www.kernel.org keeps
> silence about mailing lists. I cannot afford subscribing to every
> list just to sligh
[Rajiv Majumdar]
> during an exec it gives the following error message : "Pthread
> internal error : message : __libc__reinit() failed" and creates a
> core dump.
This is libc failing -- please report this through libc channels (see
http://www.gnu.org/software/libc). If it is in fact a kernel b
[Jeff Merkey]
> Do folks not know this NTFS driver will trash hard drives? We need
> to alert folks DO NOT USE WRITE NTFS MODE in those versions we know
> are busted.
Here's an idea: let's make r/w support a separate CONFIG option, and
label it "DANGEROUS".
Oh wait, we already do that.
Perhap
[Michael Warfield]
> This thing is not armed and dangerous due to an act of ommision.
> It's live and active only through three acts of commision.
We could make it *four* acts of commission. (: (: (:
diff -urk~ fs/Config.in
--- fs/Config.in~ Mon Nov 13 01:43:42 2000
+++ fs/Config.in
[Jeff Merkey]
> Please consider the attached patch to make it a little bit harder for
> folks to enable NTFS Write Support under Linux until it can get fixed
> properly.
Hey! It was a joke! A better way would be just to comment out the
CONFIG_NTFS_RW line entirely. Actually, I think that *wou
[Dick Johnson]
> > > char main[]={0xf0,0x0f,0xc0,0xc8};/* try also on NT (: */
> > me2v@reliant DRFDecoder $ ./op
> > Illegal instruction (core dumped)
>
> Yep. And on early Pentinums, the ones with the "f00f" bug, it would
> lock the machine tighter than a witches crotch. Ooops, not
> pol
[Rasmus Andersen]
> -static struct w83977af_ir *dev_self[] = { NULL, NULL, NULL, NULL};
> +static struct w83977af_ir *dev_self[];
How does the compiler know the size of the array?
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
[Pavel Machek]
> I'd say that warning is more acceptable than #ifdef... In cases where
> warnings can be eliminating without ifdefs, that's okay, but this...
In this case it is dead weight in the object file -- and for machines
that can least afford it (CONFIG_PCI=n is mostly for the low end,
ri
[David Feuer]
> Perhaps it would be good to put a check in unlink to make sure that
> this is not the last link to a swapfile.
Much better to add code to /sbin/swapon and /sbin/swapoff to set and
clear immutable bit. Sure it only works on ext2 but how far do you
want to take this thing?
Peter
[Andrew Stubbs]
> Has anyone implemented a /proc device or user program to interrogate
> the enviromental attirbutes (temp, voltage etc) that many
> motherboards provide via their bios's ?
Do a search on 'lm_sensors'.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kerne
[Linus]
> - pre8:
Small thinko in arch/mips64/Makefile, looks like.
--- 2.4.0test12pre8/arch/mips64/Makefile~ Sun Dec 10 20:07:02 2000
+++ 2.4.0test12pre8/arch/mips64/MakefileSun Dec 10 20:13:07 2000
@@ -33,7 +33,7 @@
# machines may also. Since BFD is incredibly buggy with resp
[Anthony Barbachan]
> I am unable to compile the latest kernel. I have attached my kernel
> configuration and a copy of the output of where the compile fails. I
> am looking into what is causing the compile failure, but have not
> been able to figure it out yet. Still looking though.
It looks
[Rasmus Andersen]
> How about this patch? It moves the offending struct to the __init
> function where it is used and inside an existing #ifdef CONFIG_PCI.
H, if you're messing around with the pci device table, why not just
convert it to use new-style PCI init? This is fairly easy to do (I
[John O'Donnell]
> The directory of kernel headers (version 2.2.17) does not match your
> running kernel (version 2.2.18). Consequently, even if the
> compilation of the module wassuccessful, the module would not load
> into the running kernel.
> Upon inspection of /usr/src/linux/include/linux/ve
[Mohammad A. Haque]
> Wasn't there discussion that user space apps shouldn't include kernel
> headers?
Oh, it's been discussed, many times. Here is my executive summary of
why nobody needs to use kernel headers in userspace programs, *EVER*:
Q: I want to #include but I get compile errors, ple
[Paul Fulghum]
> from my scanning of the kernel archives, this is the *all time*
> largest kernel patch (including 2.3/2.4 patches).
And thus it follows that 2.2.18 is the least buggy kernel ever, since
it has gotten the most bug fixes.
Right? (:
Peter
-
To unsubscribe from this list: send the
[Georg Nikodym]
> + case 'x':
> + fprintf(stderr,
> + "klogd: %c option is obsolete. Ignoring\n", ch);
Clearer (IMHO): "klogd: warning: ignoring obsolete option '-%c'\n", ch);
Peter
-
To unsubscribe from this list: send t
101 - 200 of 309 matches
Mail list logo
