[esr]
> If there were already a library in ths stock Python distribution to
> digest .Xdefaults files I might consider this. Perhaps I'll write
> one. But I'm not going to bulk up the CML2 code with this marginal
> feature.
Wait ... I thought you were just using Python bindings to Tk. Are you
[John Cowan]
> The whole point of CML2 is to make kernel configuration something
> that Aunt Tillie (or a reasonable facsimile thereof) can do, and we
> are all Aunt Tillies from time to time. That includes differing
> standards of readability,
Come on, that's absolutely a red herring. There a
[esr]
> > CONFIG_SOUND_YMPCI: arch/ppc/configs/power3_defconfig
>arch/arm/def-configs/footbridge arch/arm/def-configs/rpc arch/arm/def-configs/lart
>arch/arm/def-configs/shark
[jgarzik]
> typo, that should be ...YMFPCI.
Actually it's not a typo (although the fix is the same). The old
"SB-c
Introduced in 2.4.4pre4, I believe. $(export-objs) need not be
conditional, and the if statement was not really correct either,
although in this case it probably worked.
Peter
--- 2.4.4pre6/lib/Makefile~ Mon Apr 23 09:51:17 2001
+++ 2.4.4pre6/lib/Makefile Mon Apr 23 17:11:04 2001
@@
[Peter Samuelson]
> > Introduced in 2.4.4pre4, I believe. $(export-objs) need not be
> > conditional, and the if statement was not really correct either,
> > although in this case it probably worked.
[Tom Rini]
> Er, are you sure changing the test for !"nn" i
[Kai Henningsen]
> > There *is* a good way to do this, and it would be really nice if
> > vger could be taught to do it: add a List-Id: header
> > (draft-chandhok-listid-04.txt RFC-to-be, implemented in lots of
> > mailing list managers already).
[Eli Carter]
> Have you looked at the headers i
[Manfred Spraul]
> > Unless you modify the ABI and pass the array bounds around you won't
> > catch such problems,
[Eric W. Biederman]
> Of course. But this is linux and you have the source. And I did
> mention you needed to recompile the libraries your trusted
> applications depended on.
[Nathan Black]
> This really improved the performance of my dual PIII-866 w/512MB Ram
> and AIC7899 scsi.
[...]
> I would suggest, if at all possible, putting this in the 2.4.2
> kernel.
Have you any idea the breadth of cards and chips that aic7xxx supports?
Sure, Justin's driver does great with
[Dennis]
> For example, if there were six different companies that marketed
> ethernet drivers for the eepro100, you'd have a choice of which one
> to buy..perhaps with different "features" that were of value to
> you. Instead, you have crappy GPL code that locks up under load, and
> its not wort
[Jacob Luna Lundberg]
> Just out of curiosity, why can't the specification be along the lines
> of a vendor data file saying ``if you want the printer to do x then
> say y'' and ``if the printer says x then it means y''. That ought to
> add a lot of functionality right there.
Think about it. A
[Justin Gibbs]
> I've verified the driver's functionality on 25 different cards thus
> far covering the full range of chips from aic7770->aic7899.
That's very good to hear. I know the temptation of only testing on new
hardware; that's why I was concerned.
> Lots of people here at Adaptec look
[BERECZ Szabolcs]
> Here is a new syscall. With this you can change the owner of a running
> procces.
> + if (current->euid)
> + return -EPERM;
Use capable().
> + p = find_task_by_pid(pid);
> + p->fsuid = p->euid = p->suid = p->uid = uid;
Race -- you need to ma
[BERECZ Szabolcs]
> > Race -- you need to make sure the task_struct doesn't disappear out
> > from under you.
>
> Yes, but we need a write_lock, not a read_lock.
No, it's a read_lock because it is locking the task *list*, which is
not being changed. The only thing being changed is data within
[Peter Samuelson]
> > Race -- you need to make sure the task_struct doesn't disappear out
> > from under you.
> >
> > Anyway, why not use the interface 'chown uid /proc/pid'? No new
> > syscall, no arch-dependent part, no user-space tool, etc.
[
[Alan Cox]
> There is an assumption in the kernel that only the task changes its
> own uid and other related data.
Fair enough but could you explain the potential problems? And how is
it different from sys_setpriority?
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-ker
[BERECZ Szabolcs]
> The conclusion: it's cannot be implemented without slowdown.
Or: it cannot be implemented 100% safely and correctly without slowdown.
If you know the use you wish to put this to, and are willing to risk a
permission check somewhere being confused momentarily by a non-atomic
[Peter Bergner]
> Hopefully someone can point me in the right direction here.
> I need to use different CFLAGS options depending on whether
> I'm compiling arch dependent code or arch independent code.
Use the per-directory $(EXTRA_CFLAGS), and/or the per-file
$(CFLAGS_foo.o). See also $(EXTRA_
[Christoph Hellwig]
> It would be really good to have something devfs-like just for LVM in
> setups that don't use LVM, so we could avoid mounting root read/write
^^^devfs?
> for device-creation.
For most people, read/write access to /dev is rarely needed -- how
often do
[John Heil]
> Which -ac series patch does this match up with or superceed ie should
> this be considered superior to -ac19 ?
Neither "supercedes" the other -- they are different trees. The -ac
series has some patches that Linus may never get because they are
experimental, or still buggy.
If yo
[Peter Samuelson]
> > How often do you run MAKEDEV or vgscan?
[Christoph Hellwig]
> On every bootup, _before_ doing mount -a
A mere 'vgchange -ay' works fine for *my* boot processes. Is there a
particular reason to do 'vgscan' every time? (I'm not argui
[Peter Bergner]
> The following is a boot log for a 64 bit port of Linux for IBM's 64
> bit PowerPC processors. This log was made on a pSeries model 270
> which uses a POWER3 microprocessor.
Impressive. One question, though --
> starting cpu /cpus/PowerPC,[EMAIL PROTECTED]
> starting cpu /cpu
[Jon Hart]
> 1. I am unable to mount loopback block devices using kernel 2.4.2.
Apparently fixed in -ac3.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.h
[Drew Bertola]
> Feb 23 20:48:24 babylon modprobe: modprobe: Can't locate module binfmt-464c
> Although I've looked through the documentation, I can't find any
> reference to binfmt-464c.
binfmt-464c is ELF -- it means your kernel came across an ELF
executable and was unable to execute it so it
[Pierfrancesco Caci]
> Hi there, can someone please tell me what's going wrong with my
> compilation of 2.4.2 ?
Change '-oformat' to '--oformat' 4 places in arch/i386/boot/Makefile.
> Binutils 2.10.91.0.2
This version of binutils no longer accepts the old 'ld -oformat' form
of '-
[Ivan Stepnikov]
> I tried to call getrlimit(). It shows only 2G available memory and
> there is no way to increase it.
Right. Architectural limit. There needs to be some room in the
address space for kernel stuff, I/O, etc -- in Linux at least, having
to play with your page tables every singl
[Kai Germaschewski]
> +list-multi := fore_200e
> +fore_200e-objs := fore200e.o $(FORE200E_FW_OBJS)
list-multi := fore_200e.o
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://
[Steven Friedrich]
> The questions I have are difficult to research because so little info
> exists about 2.4 design philosophy.
I guess the ORA "Linux Device Drivers" 2nd edition is due out Real Soon
Now. It will cover 2.4.
Peter
-
To unsubscribe from this list: send the line "unsubscribe lin
[Jeff Coy]
> this issue came up frequently with customers uploading scripts in
> binary mode trying to run #!/usr/bin/perl^M. The solution for me was
> to just do the following:
>
> cd /usr/bin
> sudo ln -s perl^V^M perl
So none of your customers tried '#!/usr/bin/perl -w^M'? (Com
[Dr. Kelsey Hudson]
> umm, last i checked a carriage return wasn't whitespace... space,
> horizontal tab, vertical tab, form feed constitute whitespace IIRC...
Where and when did you check? Several sources disagree with you.
Peter
-
To unsubscribe from this list: send the line "unsubscribe li
[Jeremy Jackson]
> try command 'man mkinitrd' under redhat for hints about initial
> ramdisk.
I have been puzzled about this for quite some time. Why exactly does
everyone always recommend using 'mkinitrd' on Red Hat systems? It
seems to me that if you are compiling a kernel for a specific ser
> Kindly let me know in which part comes the IDE, ext2 and ELF after
> running the command make menuconfig.
Oh come on, these things aren't *that* hard to find. In any case,
judging from the device number 08:01, I suspect you are using SCSI
rather than IDE. Check your SCSI options. You must c
[Russell King]
> Can't you get the source, and whatever relevent files you need to
> build a dpkg and build the source + binary packages yourself (with
> maybe a few minor changes to the dpkg build information)?
Right. No changes at all. modutils_2.3.23-2.diff.gz applies fine,
except for one bi
[David L. Parsley]
> I read the FAQ and SubmittingPatches, but how best to generate a
> patch that moves a file from on dir to another? diff -urNP makes the
> patch a lot longer than it seems like it should be...
A major weakness of the 'patch' command -- you cannot gracefully move
or rename fi
[Mike van Smoorenburg]
> Also calling kwhich with multiple arguments was actually the idea
> behind the script.
Yes, and that's why my optimization patch (in 2.2.19pre3, since
reverted) broke -- it relied on multiple arguments.
Alan, could you put it back in now?
Peter
--- 2.2.19-7/Makefile~
[Felix von Leitner]
> I don't know how Linux does it, but returning the first free file
> descriptor can be implemented as O(1) operation.
How exactly? Maybe I'm being dense today. Having used up the lowest
available fd, how do you find the next-lowest one, the next open()? I
can't think of an
[Achim Herrmann]
> main.o was created using language "C": gcc -c main.c -o main.o
> and
> hwaccess.o was created using assembler: nasm -f elf hwaccess.asm -o
> hwaccess.o
>
> Is there a possibility to combine these two object files, so that I
> have a module which is loadable by insmod?
I'm no
[Ingo Molnar]
> - probably the most radical solution is what i suggested, to
> completely avoid the unique-mapping of file structures to an integer
> range, and use the address of the file structure (and some cookies)
> as an identification.
Careful, these must cast to non-negative integers, with
[Venkatesh Ramamurthy]
> [Venkatesh Ramamurthy] I think there should be a better way to handle
> this , compiling is one of the options, but an end-user should not
> think of compiling. The end user needs to put an another card and
> connect drives and get his system up and running. He should not
[Michael Rothwell]
> It seems that if you move a file with a colon -- "file:colon" -- in
> the name from Ext2 to "StreamFS," you would end up with a file named
> "file" with a stream named "colon". When copying back, you would get
> "file:colon" back.
What if you copy both 'filename' and 'filena
[Peter Samuelson]
> > What if you copy both 'filename' and 'filename:ext' onto the same
> > fs? Do they get combined into one file?
[Michael Rothwell]
> ON Ext2, you get two files. On NTFS, you get one file, and a stream
> on that file.
Yeah. I think
[Michael Meissner]
> Ummm, I just reread the 2.4 Changes file once again just to be sure,
> and it did not cover this issue. So how the *$@% are people supposed
> to "read some docs" to know about this, if the docs don't mention the
> information. I know people have been complaining about this
[Rik van Riel]
> > So do I. I chose to blacklist John O'Donnell and he will never get
> > any kernel help from me again (since I can't see his email).
[John O'Donnell]
> Please tell me I just didn't just see this message??!?!?!?!
> Please??!?!?!? What are you doing?
Hold on. First you go an
[Mo McKinlay]
> We went through this last time around. What happens to directories
> with streams?
Yeah, I agree, 'file/stream' is lousy syntax as well. If it weren't
for the possibility of having streams on directories, it would almost
be acceptible. I still don't know which (':' or '/') is t
[Rogier Wolff]
> I'd prefer an interface that says "copy this fd to that one, and
> optimize that if you can".
So do exactly that in libc.
sendfile () {
if (sys_sendfile() == -1)
return (errno == EINVAL) ? do_slow_sendfile() : -1;
return 0;
}
Peter
-
To unsubscribe from this
[James Bottomley]
> The fundamental problem that we all agree on is that SCSI devices are
> detected in the order that the mid-layer hosts.c file calls their
> detect routines.
That was yesterday. Today they are detected in the order they are
linked into the kernel, cf. the Makefile. But yes, t
[[EMAIL PROTECTED]]
> Multiple bus types... Compaq server with PCI and EISA, for example?
> IIRC the EISA bus is bridged onto one of the PCI busses. Perhaps a
> breadth-first scan; PCI busses first, then bridged devices on PCI,
> then internal non-PCI busses, then external busses.
No, bridging
[Torsten Duwe]
> > "Francis" == Francis Galiegue <[EMAIL PROTECTED]> writes:
>
> >> + if ((*p & 0xdf) >= 'a' && (*p & 0xdf) <= 'z') continue;
>
> Francis> Just in case... Some modules have uppercase letters too :)
>
> That's what the &0xdf is intended for...
It's wrong, then: you'
Note for future reference: please report configuration and build bugs
to [EMAIL PROTECTED] Speaking for myself, I am much more likely
to notice it there, as the volume is a lot lower than l-k. (:
[Stefan Sassenberg]
> When I set CONFIG_MD_BOOT to 'y' and then set neither
> CONFIG_MD_LINEAR nor
[Torsten Duwe]
> + for (p = module_name; *p; p++)
> + {
> + if (isalnum(*p) || *p == '_' || *p == '-')
> + continue;
> +
> + return -EINVAL;
> + }
I think you just broke at least some versions of devfs. I don't
remember if the feature is still around, but I know
[Rasmus Andersen]
> I'm getting oopses on a linux 2.2.17 box when I try to do
> tar cvIf -X /. Reproducably.
Are you excluding /proc? Trying to back up all of /proc is definitely
asking for trouble, although the oops still indicates a kernel bug.
Peter
-
To unsubscribe from this list: send th
[Linda Walsh]
> Under 2217, the xfer speed drops to near 1,000K/s. This is for both
> 'badblocks'
> and a 'dd' if=/dev/hda of=/dev/hdb bs=256k. In both instances, I notice
> a near 90% performance degredation.
Off the top of my head it sounds like you are using the wrong ide i/o
mode. Your ha
[I wrote]
> What chipset does the Inspiron 7500 use? (Probably Intel something.
I just booted an Inspiron 5000. PIIX4. So in the kernel config, read
the help on PIIX support and make sure to turn on 'use dma by default'.
...And you probably still want to at least try Andre's patch.
Peter
-
[Zhiruo Cao]
> Why does bdflush (kupdated and kflushed) writes to disk periodically
> even though the system is apparently idle. I think if no more new
> buffers becomes dirty, kflushed show not write anything to disk.
kill -STOP {your cron process}
mount all ext2 filesystems with '-o noatime'
[Ian Grant]
> In 2.2.x we were able to build a kernel with RAID modules and have it
> autodetect RAID partitions at boot time - so we could use raid root
> partitions.
Really? Funny, because IIRC RAID autodetection does not even exist in
2.2.x kernels. Perhaps you are referring to vendor-patch
[Ian Grant <[EMAIL PROTECTED]>]
> Of course we need an initrd with the raid modules on it before we can
> boot from a RAID root partition.
raidtools can't run from an initrd?
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTE
[Andrzej Krzysztofowicz]
> Note, that as CONFIG_MCA is defined only for i386 the dependencies on
> $CONFIG_MCA are no-op for other architectures (in
> Configure/Menuconfig). Either CONFIG_MCA should be defined for all
> architectures or there should be if ... fi around these lines.
The former,
[Jeff Garzik <[EMAIL PROTECTED]>]
> Oh yeah, another MCA cleanup to consider -- like EISA, there exists a
> 'MCA_bus' variable which is 0 or 1, depending on the absence or presence
> of MCA bus on the current system.
OK, workin' on it..
Peter
-
To unsubscribe from this list: send the line "unsu
[Jeff Garzik <[EMAIL PROTECTED]>]
> For drivers that are 100% MCA, they do not need to test MCA_bus,
> because that test can be done in Config.in.
I think Andrzej was concerned with a driver assuming that just because
CONFIG_MCA is defined, there *is* an MCA bus on the machine. This is
of cours
[Jeff Garzik]
> MYSRC=/devel/linux-2.4
>
> tar xvfz linux-2.4.0-test11.tar.gz
> mv linux linux-vanilla
> diff -urN linux-vanilla $MYSRC > /tmp/patch
You should use an example where $MYSRC is a single directory level
(rather than absolute path) so people can use 'patch -N
[jesse]
> 1. Your server closes all open directory file descriptors and chroots.
> 2. Someone manages to run some exploit code in your process space which--
mkdir("foo")
chroot("foo")
chdir("../../../../../../../../../..")
chroot(".")
mkdir proc
mount -t proc none proc
cd proc/1
This toplevel Makefile change in 11pre6 is wrong:
- $(HOSTCC) $(HOSTCFLAGS) -o scripts/split-include scripts/split-include.c
+ $(HOSTCC) $(HOSTCFLAGS) -I$(HPATH) -o scripts/split-include
+scripts/split-include.c
Many people have proposed this patch over the last few years, to kludg
[I wrote]
> > mkdir("foo")
> > chroot("foo")
[H. Peter Anvin]
> BUG: you *MUST* chdir() into the chroot jail before it does you any
> good at all!
No, it wasn't a bug! It was a demonstration. The above code is
executed not by the application but by the *attacker* who has managed
to 0wn
[Nix <[EMAIL PROTECTED]>]
> I haven't checked this or anything, but it seems to me that all you
> need is a cooperating process outside the jail, that opens some
> world-readable directory
In that case, you are already outside. (: Why bother with the chroot
process at all?
Peter
-
To unsubscri
[Chip Salzenberg]
> --- drivers/char/Makefile.prev
> +++ drivers/char/Makefile Fri Nov 17 13:30:04 2000
> @@ -12,5 +12,5 @@
> SUB_DIRS :=
> MOD_SUB_DIRS := $(SUB_DIRS)
> -ALL_SUB_DIRS := $(SUB_DIRS) rio ftape joystick drm agp
> +ALL_SUB_DIRS := $(SUB_DIRS) rio ftape joystick
>
> #
>
While trying to clean up some code recently (CONFIG_MCA, hi Jeff), I
discovered that gcc 2.95.2 (i386) does not remove dead string
constants:
void foo (void)
{
if (0)
printk(KERN_INFO "bar");
}
Annoyingly, gcc forgets to drop the "<6>bar\0". It shows up in the
object file, need
[[EMAIL PROTECTED]]
> > Udma3 seem to be rock solid though as long as it manages to pass
> > the partition detection during boot up.
[David Woodhouse]
> If it falls over at udma3, perhaps we should blacklist it all the way
> down to udma2?
The way I understood Hakan was: "it boots in udma4, a
[Jakub Jelinek <[EMAIL PROTECTED]>]
> gcc was never dropping such strings, I've commited a patch to fix
> this a week ago into CVS.
Cool! What about block-scoped 'static' variables? Do those get
garbage-collected now as well?
Peter
-
To unsubscribe from this list: send the line "unsubscribe l
[Jeff Garzik]
> Pretty much all ISA and PCI drivers need to be portable and SMP
> safe... if not so, it's a bug. That said, there is certainly more
> motivation to make a popular PCI driver is SMP safe than an older ISA
> driver.
Usually, but you never know...
"o SMP optimised 3c501"
[I wrote]
> > > void foo (void)
> > > {
> > > if (0)
> > > printk(KERN_INFO "bar");
> > > }
> > >
[J . A . Magallon]
> Is it related to opt level ? -O3 does auto-inlining and -O2 does not
> (discovered that here, auto inlining in kernel trashes the cache...)
See for yoursel
[Alan Cox]
> You got it. The module is doing an overlarge delay
Perhaps people would stop asking this question if the symbol were
renamed from __bad_udelay() to, say, __use_mdelay_instead_please().
Sort of like the DNS zone (somewhere at UCLA was it?) where they had
something like 'quit 86400 I
[Neil Brown]
> In drivers/md/Makefile, swap the order of "raid5.o xor.o" to be
> "xor.o raid5.o", recompile, install, reboot.
Don't forget the part about adding a comment saying that xor.c does in
fact need to come before raid5.c. This is the part that most likely
will not happen, so that two m
[Matt D. Robinson]
> Any way we can standardize 'make install' in the kernel? It's
> disturbing to have different install mechanisms per platform ...
> I can make the changes for a few platforms.
2.5 material, already on the todo list.
Peter
-
To unsubscribe from this list: send the line "unsu
[Albert D. Cahalan]
> The infamous LINK_FIRST infrastructure was sort of half-way done.
I disagree: it could handle all cases I could see that we might
reasonably care about. I challenge anyone to come up with a
non-pathological case that could not be taken care of with a single
LINK_FIRST and/
[Alan Cox]
> Changes in 2.4.0test11ac2
> o Work arounds for broken Dell laptop APM (me)
> | If you have an Inspiron 5000e please send
> | me the dmesg of this kernel booting. Thanks
Inspiron 5000, is this close enough?
Linux version 2.4.0-test11-ac2 (peter@kendall) (gcc
[Patrick van de Lageweg]
> diff -u -r --new-file linux-2.4.0-test11.clean/drivers/atm/firestream.c
>linux-2.4.0-test11.fs50+atmrefcount/drivers/atm/firestream.c
Since you are submitting in the form of a source patch, you ought to
include the relevent bits of
drivers/atm/Makefile
drivers/at
[Adam J. Richter]
> +static struct pci_device_id atp870u_pci_tbl[] __initdata = {
> +{vendor: 0x1191, device: 0x8002, subvendor: PCI_ANY_ID, subdevice: PCI_ANY_ID},
> +{vendor: 0x1191, device: 0x8010, subvendor: PCI_ANY_ID, subdevice: PCI_ANY_ID},
> +{vendor: 0x1191, device: 0x8020, subvendor: PC
[Rogier Wolff <[EMAIL PROTECTED]>]
> However, if my code assumes that the compiler needs to initialize the
kernel
> variable one way or another, I want to put in the initialization,
> even if that means an "= 0;" which is already the default.
Well,
[Adam J. Richter]
> +static struct pci_device_id isicom_pci_tbl[] __initdata = {
> + { VENDOR_ID, 0x2028, PCI_ANY_ID, PCI_ANY_ID },
> + { VENDOR_ID, 0x2051, PCI_ANY_ID, PCI_ANY_ID },
> + { VENDOR_ID, 0x2052, PCI_ANY_ID, PCI_ANY_ID },
> + { VENDOR_ID, 0x2053, PCI_ANY_ID, PCI_ANY_ID
[Christian Haul]
> 2.4.0-test11 freezes when writing to FAT SCSI-MO-Drive
I think this is a known problem with FAT vs. large block sizes.
I imagine it will be addressed soon.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PRO
[ChenLi Tien, from http://members.home.net/puresoft/cmedia.html]
> - * Copyright (C) 1999 ChenLi Tien ([EMAIL PROTECTED])
> - *
> - * Based on the PCI drivers by Thomas Sailer ([EMAIL PROTECTED])
> + * Copyright (C) 1999 ChenLi Tien ([EMAIL PROTECTED])
> + * C-
[Rogier Wolff]
> > > +MODULE_PARM(fs_debug, "i");
> >
> > There's no reason to wrap these "MODULE_PARM"s inside an "#ifdef MODULE".
> anymore in 2.4
^^^2.2
Verified in 2.2.0 (the oldest tree I have).
Peter
-
To unsubscribe from this lis
[ChenLi Tien]
> > I don't think the (2,3,0) ifdef is necessary. Just use the labeled
> > initializers for all kernels. See also cm_audio_fops, cm_dsp_fops,
> > cm_midi_fops, cm_dmfm_fops.
>
> Yes, as 2.3.x series is not for end-user, I can remove them. I keep it for
> easy to tell what's diffe
[Alan Cox]
> > Thats because too many things get put on a line then.
> > And because we do [] [] not [][] ?
[Andries Brouwer]
> In the good old times we had foo bar for a total of 8*(8+1) = 72
> positions. Now we have [] [] which takes 8*(8+1+4) = 104
I've got it! Put multiple addresses w
[Martin Dalecki]
> Just a small trivial obviously correct update...
OK, merged into my pending pci_ids.h patch. (This is bigger than
necessary because I converted almost all spaces to tabs.)
Peter
--- 2.4.0test11/include/linux/pci_ids.h.bak Mon Nov 13 01:43:49 2000
+++ 2.4.0test11/include
[Jeff Garzik]
> If you mean preferring 'if ()' over 'ifdef'... Linus. :) And I agree
> with him: code looks -much- more clean without ifdefs. And the
> compiler should be smart enough to completely eliminate code inside
> an 'if (0)' code block.
Plus the advantage/disadvantage of making the co
[Brian Kress]
> 1) Add a function pointer to struct gendisk called hd_name.
>
> 2) Make disk_name in fs/partitions/check.c use that function
> pointer if its non-null.
>
> 3) Change the following drivers to use this method. (adding the
> driver specific method and removing the old co
[Adam J. Richter]
> +#define PCI_VENDOR_ID_ELSA 0x1048
> +#define PCI_DEVICE_ID_ELSA_MIRCOLINK 0x1000
> +#define PCI_DEVICE_ID_ELSA_QS30000x3000
Oh, don't propagate the typo. Spell it MICROLINK here and in
hisax/elsa.c.
> #define PCI_VENDOR_ID_PLX0x10b5
> +#define PC
[Chris Wedgwood]
> taking away -O2 is a 'fix' for now... not a very good one though.
Not if you want function inlining to work. The kernel *won't compile*
without optimization.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PR
> > usb-uhci.c: interrupt, status 3, frame# 212
> > hub.c: already running port 2 disabled by hub (EMI?), re-enabling...
[Greg KH]
> The messages are harmless debug messages. Anyone want to whip up a
> patch to turn them off (like was recently done for 2.4.0-test)?
Is this what you mean?
Pete
[Albert D. Cahalan]
> > Somebody else posted a reasonable hack for the [<>] problem. His
> > proposal involved letting multiple values share the same markers,
> > something like this:
[Russell King]
> Yep, now that is one idea I like!
Me too. (: Keith posed two objections:
1. The >] could
[Tigran Aivazian]
> _BUT_ never let this to be a default option, please. Because there
> are valid cases where a programmer things "this is in .data" and that
> means this should be in .data.
If you are writing the sort of code that cares which section it ends up
in, you need to use __attribute
[Elmer Joandi]
> Oh, and one more point: if linux is going to have nonprofessional
> endusers space comparable to MSWin, then you probably do not want to
> have every bug report, because these will be stupid anyway, with or
> without debug info. But if ideological wars stop development in
> nons
[Jeff V. Merkey]
> I am having trouble getting a 2.4 vmlinuz (bzImage) and initrd image
> onto a 1.44 floppy with all the new stuff.
Check out what Debian did for 2.2 ("potato"). Kernel and syslinux are
on a FAT floppy, and a second floppy holds a raw ext2 image, gzipped.
SYSLINUX.CFG begins li
[Tigran Aivazian]
> First, they are not trivially equivalent. In fact, they are not
> equivalent at all. Any good C book should tell you that one places
> data in "data segment" and another in "bss segment" (with a footnote
> explaining historical meaning of "block started by symbol")
Do you ha
[Remi Turk]
> Do I understand correctly that this means hardlinks to directories
> (except . and ..) are fundamentally impossible in Linux?
Why do you want to be able to do that? Use symlinks or loopback mounts
and stay out of trouble.
> (I'm thinking about trying to write a garbage collected f
[Albert D. Cahalan]
> Choosing an initializer that tends to catch unintended reliance on
> zeroed data would be good. Too bad it is too late to fix.
Why would that be good? Why is it bad to accidentally rely on zeroed
data, if the data is in fact guaranteed to be zeroed? It's not like
this is
[Keith Owens]
> Binary patches against bss on disk cannot work, there is nothing to
> patch.
OK, me dumkopf.
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://www.tux.org/lkml/
[Tigran Aivazian <[EMAIL PROTECTED]>]
> no, I was not talking about ISO C standards but about the normal
> expected C environment under any UNIX. I guess, we just mean
> different things by "trivially equivalent" since neither of us said
> anything about what that actually meant. What I meant by
gcc has a minor bug[1]: __attribute__(("section")) is ignored for the
'.rodata' section. This means that string constants cannot be
__initdata -- we have to use arrays instead. The other workaround is
to use -fwritable-strings, which would be much worse.
[1] OK so it's arguable whether or not
[Neil Brown <[EMAIL PROTECTED]>]
> O_OBJS := $(shell echo $(obj-y) | tr ' ' '\n' | cat -n | sort -u +1 | sort -n | cut
>-f2)
Clever. I like pipelines too. Here is a one-fork equivalent, untested:
nodups = $(shell g=' '; for f in $(1); do case $$g in (*" $$f "*) ;; (*) g="$$g$$f
"; echo $$
1 - 100 of 309 matches
Mail list logo
