uot;.
Signed-Off-By: Peter Samuelson <[EMAIL PROTECTED]>
--- drivers/input/mouse/logips2pp.c
+++ drivers/input/mouse/logips2pp.c
@@ -220,6 +220,7 @@
{ 66, PS2PP_KIND_MX, /*
MX3100 reciver */
PS2PP_WHEEL | PS2PP
I know this is a bit late to be reporting this, as it happened before
2.6.18, but my PowerPC CHRP machine (RS/6000 43p-150, 604e CPU) no
longer boots. From the console:
instantiating rtas at 0x1ffe5000 ... done
copying OF device tree ...
Building dt strings...
Building dt structure...
[Peter Samuelson]
> AIX curses.h defines macros 'clear_screen' and 'color_names' but does
> not define 'scroll()'.
I should mention that 'make menuconfig' on AIX 4.3 also required 'ln -s
libxcurses.a /usr/lib/libncurses.a' but a patch to de
AIX curses.h defines macros 'clear_screen' and 'color_names' but does
not define 'scroll()'.
Signed-Off-By: Peter Samuelson <[EMAIL PROTECTED]>
diff -urN 2.6.11-rc5/scripts/lxdialog/checklist.c.old
2.6.11-rc5/scripts/lxdialog/checklist.c
--- 2.6.11-rc5/scri
[Kai Germaschewski]
> However, I don't think it's hard to verify that my patch works as
> well, it's about ten lines added to Rules.make. It's particularly
> easy to verify that it doesn't change behavior for objects listed in
> $(list-multi) at all.
Yes, we can say this, but people are right t
[esr]
> Besides, right now the configurator has a simple invariant. It will
> only accept consistent configurations
So you are saying that the old 'vi .config; make oldconfig' trick is
officially unsupported? That's too bad, it was quite handy.
Peter
-
To unsubscribe from this list: send the
[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
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
@@
[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
[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]
> 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
[Jeff Garzik]
> > It stays "8139too". Donald Becker's rtl8139.c continues to exist
> > outside the kernel.
Honestly, Jeff, I don't see how it matters -- because if you are
downloading an external driver, you are not going through the config
system anyway.
But ... "maintanicus selector est" (
[esr]
> CONFIG_8139TOOCONFIG_RTL8139TOO
> CONFIG_8139TOO_PIOCONFIG_RTL8139TOO_PIO
> CONFIG_8139TOO_TUNE_TWISTER CONFIG_RTL8139TOO_TUNE_TWISTER
The -TOO suffix was to distinguish between this and the former 8139
driver, as the two coexisted in 2.2 and 2.3. A
[kaos]
> In 2.4.2-ac18 there are 130 CONFIG options that are always derived
> from other options, the user has no control over them.
I've thought about these before ... but never got around to doing
anything about them. I agree they should have a separate namespace.
However, I would vote the f
[Jörn Nettingsmeier, quoting Robert Muller]
> Just create a shell script called yacc with the following content
> ---
> #!/bin/sh
> bison --yacc $*
> ---
> i ran into the same problem with a school proiject here yesterday
Why does nobody learn shell anymore? (Jus
[T.L.Madhu]
> I want to add a function defined in my loadeble kernel module as
> system call.
You can't. At least not without hackery -- anything is possible with a
bit of hackery.
And there are at least two good reasons for this. First: adding
syscalls at runtime is a recipe for chaos in ter
[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
[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
[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
[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
[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://
[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
[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 '-
[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
[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
[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
[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
[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
[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
[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_
[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
[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
[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.
[
[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
[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
[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
[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
[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
[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
[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.
[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
[ac]
> Vast amounts of debian included code contains suggestions about use.
I'll not dispute your word because I know you for an objective person.
But I don't remember coming across any such examples at least recently.
Maybe I just don't remember them because they didn't sound like, well,
manif
[Roberto Diaz]
> > I am trying to make a manifesto in order to attach it to all my
> > gpl'd developments..
[Rik van Riel]
> Quoted from the GPL:
> ---
> 6. Each time you redistribute the Program (or any work based on the
> Program), the recipient automatically receives a license from th
[Wakko Warner]
> I have a question, why was this idea even considered?
Al Viro likes Plan9 process-local namespaces. He seems to be trying to
move Linux in that direction. In the past year he has been hacking the
semantics of filesystems and mounting, probably with namespaces as an
eventual go
[Michael D. Crawford]
> I found I could mount three partitions on /mnt
Yes. New feature, appeared in the 2.4.0test series, or shortly before.
> and they'd all show up as mounted at /mnt in the "mount" command, but
> if I unmounted one of them (only tried with the currently visible
> one), then
[Ishikawa <[EMAIL PROTECTED]>]
> I have no idea why I invoked ver_linux using "." : I must have seen
> it somewhere and just followed it somehow.
Who knows. Anyway, the following works in 'bash' at least -- don't
know about other shells -- but it's quite a hack
Peter
--- scripts/ver_linux~
[Ishikawa]
> I just noticed that running
>
> . /usr/src/linux/script/ver_linux
>
> prints out strange libc version
[...]
> I found that if the command "ls" is aliased to "ls -aF"
So ... don't use '.' to execute scripts. If there is some
documentation somewhere that told you to do th
[Admin Mailing Lists]
> i have no bits directory
Really? What version of libc, and on what Linux distro? I thought all
versions of glibc2 had /usr/include/bits/.
If you are using libc4 or libc5, it is not surprising if the BIND
people didn't notice the problem -- they probably didn't try it.
[John Jasen]
> E upon careful reading of the devfs/devfsd documentation,
> you'll find that it says to put /sbin/devfsd /dev in amongst the
> first lines in rc.sysinit.
> In looking through rc.sysinit, / is not mounted rw until much later.
Who said anything about *re*-mounting '/'? We
[Michael J. Dikkema]
> > I went from 2.4.0 to 2.4.1 and was surprised that either the root
> > filesystem wasn't mounted, or it couldn't be read. I'm using devfs.. I'm
> > thinking there might have been a change with regards to the devfs
> > tree.. is the legacy /dev/hda1 still /dev/discs/disc0
[me]
> > Richard Gooch (devfs author, from Australia) to switch to the American
> > spelling of the word, for consistency with the rest of the kernel, and
[ac]
> Pardon
>
> include/linux/console_struct.h: unsigned char vc_palette[16*3]; /*
>Colour palette for VGA+ */
> include/
[William Knop]
> How can DevFS know which devices to add to /dev/scsi/... without
> loading the module and scanning the bus first? Or do you manually
> insert the scsi module when you need it?
If you do 'cd /dev/scsi', the kernel looks it up and finds it missing,
which generates a "lookup" event
[Jeremy M. Dolan]
> Disk is spelled 'disk' except for Compact Disc and Digital Versatile
> Disc. If it wasn't 3:30 in the morning, a patch would be attached.
It wouldn't do any good. Many months ago, Ted Ts'o pleaded with
Richard Gooch (devfs author, from Australia) to switch to the American
sp
[Rupa Schomaker]
> In my case, I have two identical Maxtor drives, but they reported
> different geometry.
[...]
> I'm doing RAID1 and it is really nice to have the same geometry so
> that the partition info is the same between the two drives. Makes
> life easier.
If that's what you needed, you
[David Lang]
> about the third story down is one mentioning SMP athlon boards
> actually starting to show up
Cool! I want one. So ... is there any way to know if and when Linux
kernel support will be available? I assume AMD doesn't follow the MPS
1.x standards.
Peter
-
To unsubscribe from th
[Arjan van de Ven]
> That won't work, unless you also want to force the soundlayer on
> people. Which is unacceptable. period.
I didn't say it was pretty, I said it was possible.
I, too, like your #ifndef solution better.
I suppose yet another hack would be to put a certain amount of #ifdef
an
[Tom Leete]
> No, I'm saying that SMP locking etc. is compatible with Athlon. The
> failure to build is not a workaround but a coding error. SMP builds
> for UP machines are supposed to work.
Yes, but if SMP for Athlons is not supported, what is the point in
allowing CONFIG_SMP + CONFIG_MK7 (o
[Arjan van de Ven]
> Unfortionatly, this is impossible. The miropcm config question is
> asked before the "sound" question, and the aci question is asked
> after that (all in ake config).
"Impossible" is perhaps a poor choice of terms. "Awkward" and "ugly"
are, however, quite descriptive. (:
P
[Tom Leete]
> It's not an incompatibility with the k7 chip, just bad code in
> include/asm-i386/string.h.
So you're saying SMP *is* supported on Athlon? Do motherboards exist?
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PRO
[David Ford]
> Mhm. Is it worth the effort to make a dependancy on the CPU type for
> SMP?
Yes. 'make config' should not allow unsupported configurations, at
least where convenient.
So - are any of the other chip types also incompatible with SMP support
(the Winchips, maybe)?
Peter
--- 2.4.
[Miles Lane]
> I think the problem may be due to usermode tools not handling the new
> "mount multiple devices to a single mount point" feature, but I'm not
> sure.
Yes, quite possibly. Rumor has it that util-linux has recently
acquired some wisdom in this area. (I can't confirm or deny.) Try
[Bernd Eckenfels]
> May even decrease the kernel for systems < 4 busses.
Be careful, though. Users may set this thinking "I have a generic
system with only one PCI bus" without realizing that AGP, cardbus and
some motherboard devices are all counted. Pad the CONFIG option by
about 4 busses and
[Richard B. Johnson]
> Then, simply:
> cp /boot/boot.0800 /dev/whatever
Ah, but that reverts the partition table, which may have been changed
since first installing lilo. To avoid this, just type 'lilo -U', which
does much the same thing but without touching the partition table.
Peter
-
[Richard B. Johnson]
> Bob Tracy found the problem: the second ':' really needs to be
> escaped even though newer versions of make allow what was written.
> -$(MODINCL)/%.ver: CFLAGS := -I./include $(CFLAGS)
> +$(MODINCL)/%.ver: CFLAGS \:= -I./include $(CFLAGS)
No, that's a workaround in that i
[Michael B. Trausch]
> > I've noticed that with some audio devices, I have a Bass and Treble
> > setting that I can play with (and usually do, becuase it makes
> > things sound MUCH better). Why don't I have that in some devices,
> > and is there a way (through the kernel, or through a userspa
[Timur Tabi]
> [ttabi@one DocBook]$ make pdfdocs
> Makefile:140: /Rules.make: No such file or directory
>
> There's no Rules.make anywhere on my hard drive.
There had better be one in '../..'. Do the 'make pdfdocs' from the top
level of the kernel source tree.
Peter
-
To unsubscribe from this
[James Sutherland]
> That depends what you mean by "retry"; I wanted the ability to
> attempt a non-ECN connection. i.e. if I'm a mailserver, and try
> connecting to one of Hotmail's MX hosts with ECN, I'll get RST every
> time. I would like to be able to retry with ECN disabled for that
> conne
[J. A. Magallon]
> I know Linux will never be compiled with any other thing than
> gcc. But what I do not understand is why if there is a standard C way
> of doing something you have to use an strange extension of gcc.
__attribute__((noreturn)) may do other things besides suppress the "no
return
[J. A. Magallon]
> It is harmless, 'cause the last sentence in the funtion is a panic,
> but it is good to add the 'return 0', just to shut up the compiler.
The correct fix is __attribute__((noreturn)) in the panic() prototype.
As it happens, this has already been done
Peter
--- 2.3.99pre4
[Jonathan Earle]
> Hmm.. so things like routing should be faster then?
Other network traffic too. Say you have an FTP server running and it
wants to send a file out to a client. The old way was for it to read()
the file into memory and then write() it to the network socket. To
avoid having to
[[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
[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
[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
[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
[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
[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
[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 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
[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
[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
[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
[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
[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~
[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
[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
> 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
[Kurt Garloff]
> It should not be world-writeable, IMHO. So the only one who can feed
> entropy there is root, who should know aht (s)he's doing ...
No, it is *good* to allow users to add entropy to the RNG pool, but it
is *bad* to assume that it is in fact entropy.
The beauty of cryptographic
[richard offer]
> Or userland libraries/applications that need to bypass libc and make
> direct kernel calls because libc hasn't yet implemented those new
> kernel calls.
Nah, it's still error-prone because it's too hard to guarantee that the
user compiling your program has up-to-date kernel hea
[Dana Lacoste]
> - I write an external/third party kernel module
> - For various reasons, I must have this kernel module installed to boot
> (i can't compile without my module running)
In that case "compile script for dummies" will probably fail anyway.
If you need it to boot, you probably nee
[Andrea Arcangeli]
> C++ obviously doesn't care about the name of parameters in a function
> too.
Sure it does when they are language keywords. In this case he is
trying to change the parameter name "new".
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the b
[Andries Brouwer]
> (i) I prefer "rootfstype". Indeed, "rootfs" is ambiguous.
> It gives some property of the root filesystem, but which?
> (ii) It is a bad idea to arbitrarily select "ext2".
> (iii) [...] Thus, if the boot option rootfstype is given, I prefer a
> boot failure over a kernel att
[Tigran Aivazian]
> no, because it would cause a "spurious" call to get_fs_type("") which
> we don't want to happen (by default i.e. -- if user _really_ wants it
> that is ok). The default of "ext2" is fine.
I still disagree -- super.c is no place to dictate the default root
filesystem. And I a
[Peter Samuelson]
> > You are changing perfectly legal C.
[Andrea Arcangeli]
> You're right that's not kernel issue and patch can be rejected, but
> he's not really changing anything :). If changing that helps then
> it's a compiler bug.
Not a compile
[Tigran Aivazian]
> +/* this can be set at boot time, e.g. rootfs=ext2
> + * if set to invalid value or if read_super() fails on the specified
> + * filesystem type then mount_root() will go through all registered filesystems.
> + */
> +static char rootfs[128] __initdata = "ext2";
Better that w
[Daiki Matsuda]
> I encounterd the problem that 'cdrdao' is not compilable in 2.2.18 on
> Alpha. And I researched a little.
Then cdrdao has a problem. It should not be including kernel headers
directly. You are changing perfectly legal C.
Peter
-
To unsubscribe from this list: send the line
[J Sloan]
> The module now compiles and gets installed -
> Unfortunately, attempting to load it does not go well:
>
> kernel/drivers/char/drm/tdfx.o: unresolved symbol remap_page_range
> kernel/drivers/char/drm/tdfx.o: unresolved symbol __wake_up
> kernel/drivers/char/drm/tdfx.o: unresolved symb
[Alex Buell]
> I can confirm that this is true for 2.2.x, with "hdx=ide-scsi". Once
> I compiled both statically into the kernel, it works.
>
> Perhaps somone can backport the fixes? It would be nice to change 2.2
> so it can accept "hdx=scsi" for compatiblity with 2.4.
I'm confused. I just lo
[Horst von Brand]
> Would tsort(1) perhaps help?
I'm betting Linus would never go for using tsort to resolve such issues
-- unless tsort output is guaranteed to be stable (the docs for GNU
textutils don't say). This would be for the same reason that he
rejected the partial ordering in the LINK_
[Norbert Breun]
> The problem is, there should be a directory "media" under
> /lib/modules/2.4.0-test12.old/kernel/drivers/ and this is missing in
> test13pre2 and test13pre3. The modules are not built.
Does this help? I think it's right.
Peter
diff -urk.orig 2.4.0test13pre3/drivers/media/Mak
[Peter Samuelson]
> Looks like your symbol versions got out of sync, somehow.
Uh, never mind, I didn't notice that pm.c is not listed as exporting
symbols. Someone else just posted a patch -- add pm.o to the
'export-objs' line in kernel/Makefile.
Peter
-
To unsubscribe fr
1 - 100 of 309 matches
Mail list logo
