Re: es1371 and recent kernels (thanks)

2001-06-13 Thread Pierfrancesco Caci
:-> "Kipp" == Kipp Cannon <[EMAIL PROTECTED]> writes: > Hi, > I have an es1371 based sound card (Creative Ensoniq Audio-PCI something > whatever) and it has worked fine for me with both 2.4.2 and 2.4.3. It > looks like other people have already responded to your message but if

Question about signal handling

2001-06-13 Thread John Chris Wren
Hopefully I'm not asking a really stupid question here, but... When setting up a signal handler, using sa_handler, there is a quasi-documented 2nd parameter of 'struct context ctx' passed to the signal handler. This seems to work on 2.2.12, 2.2.18, and 2.4.5-ac2. According to

Are You In Need Of A Lifestyle Change...

2001-06-13 Thread 3k23c2LY4
You have the opportunity to partake in the most extraordinary and powerful wealth building program available! This information has never been offered to the general public, you have been given the opportunity to take a close look. If you're skeptical, that's okay. Just make the call and see

[OT] Re: inetd missing

2001-06-13 Thread J Sloan
Blesson Paul wrote: > hi > I just brought a CD of RedHat 7. Unfortunately I > couldn't find the inetd rpm. wheather it is missing or it is in any other > name It's xinetd - BTW You might think about RH 7.1 since 7.0 was the end of the line for the legacy 2.2. kernel - cu

inetd missing

2001-06-13 Thread Blesson Paul
hi I just brought a CD of RedHat 7. Unfortunately I couldn't find the inetd rpm. wheather it is missing or it is in any other name by Blesson Get free email

Re: obsolete code must die

2001-06-13 Thread Rik van Riel
On Wed, 13 Jun 2001, Stephen Satchell wrote: > At 12:24 AM 6/14/01 -0300, Rik van Riel wrote: > >Everything you propose to get rid of are DRIVERS. They > >do NOT complicate the core kernel, do NOT introduce bugs > >in the core kernel and have absolutely NOTHING to do with > >how simple or

initial ramdisk failure

2001-06-13 Thread D. Stimits
I have been trying for a while now, without luck, to get a kernel with the SGI XFS system to boot as modules. I do fine if I make all scsi and XFS as non-modules, but modules fail for both scsi and XFS (I can make one or the other modular at a time, or both, it fails). According to what I see,

Re: obsolete code must die

2001-06-13 Thread Stephen Satchell
At 12:24 AM 6/14/01 -0300, Rik van Riel wrote: >Everything you propose to get rid of are DRIVERS. They >do NOT complicate the core kernel, do NOT introduce bugs >in the core kernel and have absolutely NOTHING to do with >how simple or maintainable the core kernel is. Not quite. There were two

Re: obsolete code must die

2001-06-13 Thread Arnaldo Carvalho de Melo
Em Wed, Jun 13, 2001 at 09:55:54PM -0400, Horst von Brand escreveu: > "Daniel" <[EMAIL PROTECTED]> said: > > I really think doing a clean up is worthwhile. Maybe while looking for stuff > > to clean up we'll even be able to better comment the existing code. Any > > other features people would

tmscsim.o INQUIRY inconsistency in 2.2.19

2001-06-13 Thread John William
Is this a known bug in tmscsim.o (2.0f, included with 2.2.19): I have the following devices (cat /proc/scsi/scsi) Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: SEAGATE Model: ST15230N Rev: 0638 Type: Direct-AccessANSI SCSI revision: 02 Host:

Re: obsolete code must die

2001-06-13 Thread Horst von Brand
"Daniel" <[EMAIL PROTECTED]> said: [...] > So without further ado here're the features I want to get rid of: > > i386, i486 > The Pentium processor has been around since 1995. Support for these older > processors should go so we can focus on optimizations for the pentium and > better

Re: Eye2Eye a hope for Promise to Join Linux

2001-06-13 Thread Horst von Brand
Andre Hedrick <[EMAIL PROTECTED]> said: > Greetings Craig, [...] Bravissimo! -- Horst von Brand [EMAIL PROTECTED] Casilla 9G, Vin~a del Mar, Chile +56 32 672616 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

Re: obsolete code must die

2001-06-13 Thread Rik van Riel
On Wed, 13 Jun 2001, Daniel wrote: OK, after my earlier troll posting, lets go over Daniel's reasons point by point. Well actually, all of these points fit in one argument. > -- Getting rid of old code can help simplify the kernel. This means > less chance of bugs. > -- Simplifying the kernel

Re: 2.4.6-pre2, pre3 VM Behavior

2001-06-13 Thread Rik van Riel
On Wed, 13 Jun 2001, Tom Sightler wrote: > Quoting Rik van Riel <[EMAIL PROTECTED]>: > > > After the initial burst, the system should stabilise, > > starting the writeout of pages before we run low on > > memory. How to handle the initial burst is something > > I haven't figured out yet ... ;) >

Re: obsolete code must die

2001-06-13 Thread Tom Vier
i have a corvus 20meg drive and a xebec 10meg that both still spin up. those are from mid to late 80s. i have seagate hawks from '94 that still work, but quantums from the same period are all dead. the difference is that newer drives have much tighter tolerances and are much more sensitive to

Re: Download process for a "split kernel" (was: obsolete code must die)

2001-06-13 Thread Jaswinder Singh
> > Or as a simpler design, something like; > > * a copy of the kernel maintained in a CVS tree > * kernel download would pull down: > * the build script > * a file containing the list of filenames depended on by > each config option > * build script builds the

Lecteur CD-ROM

2001-06-13 Thread Seigneur Angmar
Bonsoir, Je vous décrirai le problème du mieux que je peux. Avant tout, je tiens à souligner que, sous les mêmes configurations, le problème ne s'est produit et reproduit que sur les kernels 2.4.X (kernels testés : 2.2.18, 2.2.19, 2.4.0, 2.4.3, 2.4.5). J'ai en ma possession un CD-R

Re: 2.4.6-pre2, pre3 VM Behavior

2001-06-13 Thread Tom Sightler
Quoting Mark Hahn <[EMAIL PROTECTED]>: > > 1. Transfer of the first 100-150MB is very fast (9.8MB/sec via 100Mb > Ethernet, > > close to wire speed). At this point Linux has yet to write the first > byte to > > disk. OK, this might be an exaggerated, but very little disk activity > has > >

Download process for a "split kernel" (was: obsolete code must die)

2001-06-13 Thread David Luyer
> I agree that removing support for any hardware is a bad idea but I question > the idea of putting it all in one monolithic download (tar file). If we're > considering the concern for less developed nations with older hardware, > imagine how you would like to download the whole kernel with an

Re: obsolete code must die

2001-06-13 Thread D. Stimits
Daniel wrote: > > Anyone concerned about the current size of the kernel source code? I am, and > I propose to start cleaning house on the x86 platform. I mean it's all very > well and good to keep adding features, but stuff needs to go if kernel > development is to move forward. Before listing

Re: obsolete code must die

2001-06-13 Thread Mohammad A. Haque
On Wed, 13 Jun 2001, Daniel wrote: > -- Getting rid of old code can help simplify the kernel. This means less > chance of bugs. > -- Simplifying the kernel means that it will be easier for newbies to > understand and perhaps contribute. > -- a simpler, cleaner kernel will also be of more use in

Re: 2.4.6-pre2, pre3 VM Behavior

2001-06-13 Thread Tom Sightler
Quoting Rik van Riel <[EMAIL PROTECTED]>: > After the initial burst, the system should stabilise, > starting the writeout of pages before we run low on > memory. How to handle the initial burst is something > I haven't figured out yet ... ;) Well, at least I know that this is expected with the

RE: obsolete code must die

2001-06-13 Thread Rainer Mager
I agree that removing support for any hardware is a bad idea but I question the idea of putting it all in one monolithic download (tar file). If we're considering the concern for less developed nations with older hardware, imagine how you would like to download the whole kernel with an old 2400

Re: obsolete code must die

2001-06-13 Thread David Luyer
Obsolete code must die. Hardware support must live on. > > ISA, MCA, EISA device drivers > > If support for the buses is gone, there's no point in supporting devices for > > these buses. > > I am not certain if tis is a good idea, for the reason given above. (Not > certain about MCA and

Re: obsolete code must die

2001-06-13 Thread Colonel
In list.kernel, you wrote: >i think we are all missing the ball here: i am happy when i see driver >support for a piece of hardware that i have _NEVER_ heard of and at most >_ONE_ person uses it. why? it means more stuff works in linux. we >dont need to defend how many people use hardware X.

Re: obsolete code must die

2001-06-13 Thread James Stevenson
Hi >-- a simpler, cleaner kernel will also be of more use in an academic >environment. >i386, i486 >The Pentium processor has been around since 1995. Support for these older >processors should go so we can focus on optimizations for the pentium and >better processors. >ISA bus, MCA bus, EISA

Re: obsolete code must die

2001-06-13 Thread Rafael Diniz
> >i386, i486 > >The Pentium processor has been around since 1995. Support for these older > > No. Both of my cheap on-site systems for occasional access are 486s. > Why would I spend money for a system that is hardly ever used? I have 386's that I still use. > >ISA bus, MCA bus, EISA bus >

Re: obsolete code must die

2001-06-13 Thread Justin Guyett
On Wed, 13 Jun 2001, Daniel wrote: > math-emu > If support for i386 and i486 is going away, then so should math emulation. > Every intel processor since the 486DX has an FPU unit built in. In fact > shouldn't FPU support be a userspace responsibility anyway? hmm... what about processors like

Re: obsolete code must die

2001-06-13 Thread Robert Love
On 13 Jun 2001 19:22:38 -0700, Alan Olsen wrote: > On Wed, 13 Jun 2001, Daniel wrote: > > > ISA bus, MCA bus, EISA bus > > PCI is the defacto standard. Get rid of CONFIG_BLK_DEV_ISAPNP, > > CONFIG_ISAPNP, etc > > This I strongly disagree with. > > There are alot of ISA cards still in use. (I

Re: obsolete code must die

2001-06-13 Thread Gary E. Miller
Yo Daniel! On Wed, 13 Jun 2001, Daniel Dickman wrote: > What I'd like to know is this -- will support for the i386, say, ever go > away? What if the hardware is no longer in existence/used by anyone? will > support stay in the kernel? There is an aweful lot of embedded Linux using 386 and 486

Fw: Delivery Status Notification (Failure)

2001-06-13 Thread William Scott Lockwood III
Gee Andre, I guess people who use hotmail don't have an opinion you'd care to read? - Original Message - From: +ADw-postmaster+AEA-mail.hotmail.com+AD4- To: +ADw-thatlinuxguy+AEA-hotmail.com+AD4- Sent: Wednesday, June 13, 2001 8:12 PM Subject: Delivery Status Notification (Failure)

Re: Eye2Eye a hope for Promise to Join Linux

2001-06-13 Thread William Scott Lockwood III
Dear Mr. Lyons, I think it's very exciting to see someone from promise talking to the community. I think the most important thing to remember is that even if the company does not release source, people will reverse engineer the cards anyway - possibly not giving the best support to the

Re: obsolete code must die

2001-06-13 Thread Alan Olsen
On Wed, 13 Jun 2001, Daniel wrote: I agree that some clean up is needed. (The size of the kernel is getting HUGE. Back in the old days, we didn't have kernels larger than a few hundred kbytes. That is because we had to type in the kernel source from source written on papyrus.) > So without

Re: obsolete code must die

2001-06-13 Thread Claudio Martins
On Thursday 14 June 2001 01:44, Daniel wrote: > -- If someone really needs support for this junk, they will always have the > option of using the 2.0.x, 2.2.x or 2.4.x series. > You mean you want 2.5+ series to just stop supporting all older hardware? > So without further ado here're the

RE: obsolete code must die

2001-06-13 Thread John Chris Wren
As an end user who uses cheap laptops for firewalls, I'm pretty much against this. I've got 2.2.18, 2.4.4-ac8, and 2.4.4-ac12 installed as firewall machines on 486 laptops. Why should we (the collective Linux world, not me personnally, since I'm not a kernel developer) limit the class

Re: obsolete code must die

2001-06-13 Thread Rik van Riel
On Wed, 13 Jun 2001, Daniel Dickman wrote: > Thanks for your email. I am aware of the "traditions" of the > Linux kernel, and this is really why I wanted to start a > discussion going about this. OK, so you almost certainly ARE a troll: 1) proposing to remove support for hardware many of us

Re: obsolete code must die

2001-06-13 Thread Colonel
In list.kernel, you wrote: > >Anyone concerned about the current size of the kernel source code? I am, and No. Since you are up to date with the latest in everything, I cannot see why you would be concerned about a few megabytes in your gigabyte drives. >i386, i486 >The Pentium processor has

Re: obsolete code must die

2001-06-13 Thread Daniel Dickman
Hi Andrew, Thanks for your email. I am aware of the "traditions" of the Linux kernel, and this is really why I wanted to start a discussion going about this. Basically one of the things I am wondering is how complex the kernel code can grow to become. All I am proposing is that old features

BUG: Mingetty gets tainted-memory bug in cahced_lookup() durring tty open

2001-06-13 Thread Matthew Cline
[1.] Intermittent tainted-mem error in mingetty in cached_lookup() in tty open code [2.] During bootup, mingetty got a tainted memory bug in cached_lookup() while doing some tty opening stuff; this has only happened once, and I don't know how to reproduce. [3.] tty [4.] Linux version 2.4.5-ac9

Re: obsolete code must die

2001-06-13 Thread Jeff Garzik
Daniel wrote: > > Anyone concerned about the current size of the kernel source code? I am, and > I propose to start cleaning house on the x86 platform. I mean it's all very > well and good to keep adding features, but stuff needs to go if kernel > development is to move forward. Before listing

Re: obsolete code must die

2001-06-13 Thread Jaswinder Singh
Cleanup is a nice idea , but Linux should support old hardware and should not affect them in any way. Jaswinder. - Original Message - From: "Daniel" <[EMAIL PROTECTED]> To: "Linux kernel" <[EMAIL PROTECTED]> Sent: Wednesday, June 13, 2001 5:44 PM Subject: obsolete code must die >

Re: obsolete code must die

2001-06-13 Thread Rik van Riel
On Wed, 13 Jun 2001, Daniel wrote: > So without further ado here're the features I want to get rid of: > > i386, i486 > math-emu > ISA bus, MCA bus, EISA bus > ISA, MCA, EISA device drivers > parallel/serial/game ports ++ | Please, | |don't feed | |

RE: Eye2Eye a hope for Promise to Join Linux

2001-06-13 Thread Craig Lyons
Hi, Andre and I did indeed have a nice conversation on the phone. Thank you again for taking the time to talk with me and offering your assistance. As I stated on the phone, we are making a large commitment of resources to supporting Linux by releasing drivers and utilities for our products,

obsolete code must die

2001-06-13 Thread Daniel
Anyone concerned about the current size of the kernel source code? I am, and I propose to start cleaning house on the x86 platform. I mean it's all very well and good to keep adding features, but stuff needs to go if kernel development is to move forward. Before listing the gunk I want to get rid

Re: Configure.help entries for Bluetooth (updated)

2001-06-13 Thread Maksim Krasnyanskiy
>Okay, I'll bite. Ouch that hurts ;) >What's HCI stand for? >I'm guessing it ends in "Connection Interface", but the H has me stumped. Wrong guess. HCI - Host Controller Interface. People who use Bluetooth would know. HCI is the basic thing in Bluetooth world. I don't think explaining that

Re: 2.4.5 data corruption

2001-06-13 Thread Chris Mason
On Tuesday, June 12, 2001 01:17:49 PM -0700 Larry McVoy <[EMAIL PROTECTED]> wrote: > Folks, I believe I have a reproducible test case which corrupts data in > 2.4.5. > > We do nightly, weekly, and monthly backups by copying our entire /home > partition on the company file server: > >

Re: Configure.help entries for Bluetooth (updated)

2001-06-13 Thread Rob Landley
Okay, I'll bite. What's HCI stand for? I'm guessing it ends in "Connection Interface", but the H has me stumped. Happy? Hostile? Hysterical? Hippopotamus? If we're connecting a bluetooth compliant hippopotamus to Linux, I can only hope there's an RFC somewhere explaining how to do it.

O2 Micro CB bridge problems (was: PCMCIA troubles with an Acer TravelMate 513TE)

2001-06-13 Thread Andreas Bombe
On Mon, Jun 11, 2001 at 10:08:39AM +0100, Paulo E. Abreu wrote: > Greetings, > > I have this laptop and I am having trouble with pcmcia in every 2.4.x > kernel. > Someone suggested that this could be a BIOS bug ... > Below there is the information, that I think is relevant to this problem. If >

Re: AVM A1 pcmcia, kernel 2.4.5-ac11 problem

2001-06-13 Thread Andreas Klein
Hello, On Wed, 13 Jun 2001, Kai Germaschewski wrote: > On Tue, 12 Jun 2001, Boenisch Joerg wrote: > > If you dig it up somewhere and get it working with 2.4.5, it would be nice > if you let me know. We can then work together to integrate it into the > kernel tree - I can't do it myself,

accounting for threads

2001-06-13 Thread J . A . Magallon
Hi. First, sorry if this is a glibc issue. Just chose to ask here first. I want to know the CPU time used by a POSIX-threaded program. I have tried to use getrusage() with RUSAGE_SELF and RUSAGE_CHILDREN. Problem: main thread just do nothing, spawns children and waits. And I get always 0

Re: Changing CPU Speed while running Linux

2001-06-13 Thread Dieter Nützel
Arjan van de Ven wrote: > > Sven Geggus wrote: > > > > Hi there, > > > > on my Elan410 based System it is very easy to change the CPU clock > > speed by means od two outb commands. > > > > I was wondering, if it does some harm to the Kernel if the CPU is > > reprogrammed using a different CPU

Eye2Eye a hope for Promise to Join Linux

2001-06-13 Thread Andre Hedrick
Greetings Craig, I would like to publicly thank you for coming to the table of GNU/GPL with an open perspective. After 90 minutes on the phone, of which 45 minutes were me pointing out issues promblems and complaints w/ 20 minutes on ways to work on solutions in the near and distant future and

Re: [patch] do proper cleanups before requesting irq

2001-06-13 Thread Stas Sergeev
Pavel Machek wrote: > > The problem is that there are comparisons of pointers to task_struct when > > deciding if the task is alive. If one task dies and other one starts, it is > > possible (is it?) that the task structure of the newly created task resides > > at the very address where was the

Re: AVM A1 pcmcia, kernel 2.4.5-ac11 problem

2001-06-13 Thread Kai Germaschewski
On Tue, 12 Jun 2001, Boenisch Joerg wrote: > I hope not to be off topic! (In that case could you tell me where to ask?) You can try [EMAIL PROTECTED] or the newsgroup de.alt.comm.isdn4linux.de, but I can't guarantee success there, either. > Kernel of course is compiled with ISDN support and

RE: bzDisk compression Q; boot debug Q

2001-06-13 Thread Khachaturov, Vassilii
> Question 2, apparently ramdisk uses gzip compression; the name of the > kernel from make bzImage seems to maybe refer to bzip2 compression. Is > the kernel image using gzip or bzip2 compression for bzImage? Would bzImage stands for "big zImage" - this is a format invented for kernels that don't

Re: 2.2.19: eepro100 and cmd_wait issues

2001-06-13 Thread Jason Murphy
I would suggest that you use the e100 driver instead of the eepro100 driver. We switched to the e100 driver from the eepro100 driver, and a number of our FTP, NFS and rsync (IE: High bandwidth apps) problems went away. Our system are mostly 6 Proc boxes with 4 gigs of memeory. -- Jason Murphy

Re: sis630 - help needed debugging in the kernel

2001-06-13 Thread René Rebe
Thanks for the quick reply! On Wed, 13 Jun 2001 09:54:21 -0700 (PDT) James Simmons <[EMAIL PROTECTED]> wrote: > > > I currently try to debug why the sisfb driver crashes my machine. (SIS 630 > > based laptop - linux-2.4.5-ac13). > > You can do one of two things. Post both System.map and the

bzDisk compression Q; boot debug Q

2001-06-13 Thread D. Stimits
First I have a question about the compression of bzDisk. While trying to debug the reason for a modular boot failure versus a successful non-module boot (XFS filesystem for root), I found that I can mount my initial ramdisk on loopback as a means of examining which modules are available to it.

Re: SMP module compilation on UP?

2001-06-13 Thread Khalid Aziz
Mark Mokryn wrote: > > Hi, > > Is it possible to build an SMP module on a machine running a UP kernel > (or vice versa)? We of course get unresolved symbols during module load > due to the smp prefix on the ksyms, and haven't seen how to get around > it. (Defining __SMP__ does not cut it,

RE: Undocumented configuration symbols in 2.4.6pre2

2001-06-13 Thread Maksim Krasnyanskiy
Randy, >Could you make these 5 instances of "Not unsure" be more palatable and less confusing >? Oops, blind cut without reading carefully :). Thanks Max Maksim Krasnyanskiy Senior Kernel Engineer Qualcomm Incorporated [EMAIL PROTECTED] (408) 557-1092 - To unsubscribe from

Configure.help entries for Bluetooth (updated)

2001-06-13 Thread Maksim Krasnyanskiy
CONFIG_BLUEZ Bluetooth is low-cost, low-power, short-range wireless technology. It was designed as a replacement for cables and other short-range technologies like IrDA. Bluetooth operates in personal area range that typically extends up to 10 meters. More information about

Re: PATCH: ethtool MII helpers

2001-06-13 Thread Jeff Garzik
Donald Becker wrote: > I was on vacation, and thus didn't have the opportunity to comment earlier. Thanks a bunch for your comments here. > On Tue, 12 Jun 2001, Jeff Garzik wrote: > > > > - You are proposing some caching for the MII registers. I suppose that you > > > would like to have this

Re: 2.4.6-pre2, pre3 VM Behavior

2001-06-13 Thread Rik van Riel
On Wed, 13 Jun 2001, Tom Sightler wrote: > 1. Transfer of the first 100-150MB is very fast (9.8MB/sec via 100Mb Ethernet, > close to wire speed). At this point Linux has yet to write the first byte to > disk. OK, this might be an exaggerated, but very little disk activity has > occured on my

RE: [PATCH] 2.4.6-pre2 page_launder() improvements

2001-06-13 Thread Marcelo Tosatti
On Wed, 13 Jun 2001, Alok K. Dhir wrote: > > Are these page_launder improvements included in 2.4.6-pre3? Linus > mentions "VM tuning has also happened" in the announcement - but there > doesn't seem to be mention of it in his list of changes from -pre2... Yes, it is. - To unsubscribe from

RE: Undocumented configuration symbols in 2.4.6pre2

2001-06-13 Thread Dunlap, Randy
Hi, Could you make these 5 instances of "Not unsure" be more palatable and less confusing? E.g., "Not sure" or "If not sure". But not the double negative... As is, it basically says: "Sure ? say M." ~Randy > -Original Message- > From: Maksim Krasnyanskiy [mailto:[EMAIL PROTECTED]] >

Re: Has it been done: User Script File System?

2001-06-13 Thread Jeremy Fitzhardinge
Quoting Russ Lewis <[EMAIL PROTECTED]>: > mount -t userfs /etc/myfs.conf /myfs I did this a while ago: I wrote userfs which allowed arbirary filesystems to be implemented in user space. One of these was a filesystem which allowed you to embed scripts in symlinks, such that stdout of the

VEXUS VAR-Business Dealer UpDate Prices List

2001-06-13 Thread Ronald Gonzalez
MEMORY Spectek or Micron lifetime warranty (Min.Qty. Less 100) $ 8.95 32 MB 168pins PC-100 $ 12.75 64 MB 168pins PC-100/PC-133 $ 21.50 128 MB 168pins PC-100/PC-133 $ 41.50 256 MB 168pins PC-100/PC-133 Hard Drive (Min.Qty. Less 50) $ 63.50

Re: net_device list in kernel

2001-06-13 Thread Arnaldo Carvalho de Melo
Em Wed, Jun 13, 2001 at 12:14:18PM -0700, [EMAIL PROTECTED] escreveu: > > Hi, > > I have one doubt. > > There is a list of the devices(net_device{} structures) maintained in kernel which >has all the interfaces initialised by that time. This list is refrenced by dev_base >variable. > >

2.4.6-pre2, pre3 VM Behavior

2001-06-13 Thread Tom Sightler
Hi All, I have been using the 2.4.x kernels since the 2.4.0-test days on my Dell 5000e laptop with 320MB of RAM and have experienced first hand many of the problems other users have reported with the VM system in 2.4. Most of these problems have been only minor anoyances and I have continued

Looking for ifenslave.c

2001-06-13 Thread Guus Sliepen
Hello, The Ethernet bonding module is useless without ifenslave.c. I'm making a Debian package for it, and I have tried to find the "offical" distribution of this small program. I could not find an authorative source, instead a lot of copies and patched versions are scattered around the Internet

net_device list in kernel

2001-06-13 Thread dipi_k
Hi, I have one doubt. There is a list of the devices(net_device{} structures) maintained in kernel which has all the interfaces initialised by that time. This list is refrenced by dev_base variable. I need following info 1) does kernel maintain a global variable which keeps the count

Re: Linux-2.4.6-pre3

2001-06-13 Thread José Luis Domingo López
On Tuesday, 12 June 2001, at 18:42:45 -0700, Linus Torvalds wrote: > > User-noticeable things: if you are tired of not being able to NFS-export > your reiserfs tree, this should make you happy. > > VM tuning has also happened, with Rik van Riel, Mike Galbraith, Marcelo > Tosatti and Andrew

Re: threading question

2001-06-13 Thread Hubertus Franke
>I got that response too. When I pressed kernel people for details it turns >out that they think having hundreds of runnable threads/processes (mostly >the same thing under Linux) is wasteful. The scheduler is just not optimised >for that. Try out the http://lse.sourceforge.net/scheduling

Re: Has it been done: User Script File System?

2001-06-13 Thread Peter Makholm
[EMAIL PROTECTED] (Russ Lewis) writes: > Is there any filesystem in Linux that uses user scripts/executables to > implement the various function calls? What I'm thinking of is something It has been done before. http://www.ibiblio.org/pub/Linux/ALPHA/userfs/userfs.lsm describes a patch/kernel

2.4.4 Oops in ext2 and strange /proc/ksyms

2001-06-13 Thread Roland Kuhn
Hi folks! After seeing the Oops below (and rebooting), I looked into /proc/ksyms (because ksymoops complained about mismatches), and I could not find system_call, do_page_fault, etc. Shouldn't they be there? When doing ksymoops with /proc/ksyms I found recursive calling of do_brk, which for sure

Re: Going beyond 256 PCI buses

2001-06-13 Thread Tom Gall
"Albert D. Cahalan" wrote: > > Tom Gall writes: > > > I was wondering if there are any other folks out there like me who > > have the 256 PCI bus limit looking at them straight in the face? > > I might. The need to reserve bus numbers for hot-plug looks like > a quick way to waste all 256

Re: Has it been done: User Script File System?

2001-06-13 Thread Jeff Dike
[EMAIL PROTECTED] said: > Is there any filesystem in Linux that uses user scripts/executables to > implement the various function calls? http://uservfs.sourceforge.net Also, have a look at the hostfs filesystem in UML. It implements a virtual filesystem which provides access to the host

Re: [craigl@promise.com: Getting A Patch Into The Kernel] (fwd)

2001-06-13 Thread Andre Hedrick
On Wed, 13 Jun 2001, Rob Landley wrote: > Well, you're maintainer and I'm obviously not, but it's nice to hear you've > kept an open mind on this issue. :) I have seen one version and I got physically sick. > > All I want is the API rules to the signatures and we have them now. > > > > We do

Has it been done: User Script File System?

2001-06-13 Thread Russ Lewis
Is there any filesystem in Linux that uses user scripts/executables to implement the various function calls? What I'm thinking of is something along the lines of a file system module that, when it receives a call from VFS, passes the information out to a user-mode daemon which could then run

Re: threading question

2001-06-13 Thread bert hubert
On Tue, Jun 12, 2001 at 12:06:40PM -0700, Kip Macy wrote: > This may sound like flamebait, but its not. Linux threads are basically > just processes that share the same address space. Their performance is > measurably worse than it is on most commercial Unixes and FreeBSD. Thread creation may be

Re: Going beyond 256 PCI buses

2001-06-13 Thread Albert D. Cahalan
Tom Gall writes: > I was wondering if there are any other folks out there like me who > have the 256 PCI bus limit looking at them straight in the face? I might. The need to reserve bus numbers for hot-plug looks like a quick way to waste all 256 bus numbers. > each PHB has an > additional

Re: Gigabit Intel NIC? - Intel Gigabit Ethernet Pro/1000T

2001-06-13 Thread James Sutherland
On Wed, 13 Jun 2001, Ralf Baechle wrote: > On Wed, Jun 13, 2001 at 03:25:22AM -0700, Ion Badulescu wrote: > > Date: Wed, 13 Jun 2001 03:25:22 -0700 > > From: Ion Badulescu <[EMAIL PROTECTED]> > > To: Riley Williams <[EMAIL PROTECTED]> > > Cc: Shawn Starr <[EMAIL PROTECTED]>, <[EMAIL

2.4.5-ac13, APM, and Dell Inspiron 8000

2001-06-13 Thread Georg Nikodym
I've been running 2.4.5 on my new Dell I8000 without too many problems. Last night I built -ac13 (on my porch) and booted it without incident. Later, going inside and re-connecting the AC I notice that the thing's hung. I play around a bit and discover that the act of plugging or unplugging

Re: sis630 - help needed debugging in the kernel

2001-06-13 Thread James Simmons
> I currently try to debug why the sisfb driver crashes my machine. (SIS 630 > based laptop - linux-2.4.5-ac13). You can do one of two things. Post both System.map and the complete oops or you can run ksymoops on the oops. I can find the problem then. Thanks. > On my serial-console I get: >

Re: [PATCH] sockreg2.4.5-06 inet[6]_create() register/unregister table

2001-06-13 Thread David S. Miller
La Monte H.P. Yarroll writes: > Here is the register/unregister inet[6]_create() table patch revised > to disable deregistration and overriding of TCP and UDP. I've applied your patches, thank you. Please enable real tabs in your editor next time though :-) Later, David S. Miller [EMAIL

Re: SMP module compilation on UP?

2001-06-13 Thread Mark Mokryn
Rafael Herrera wrote: > > Mark Mokryn wrote: > > Is it possible to build an SMP module on a machine running a UP kernel > > (or vice versa)? We of course get unresolved symbols during module load > > due to the smp prefix on the ksyms, and haven't seen how to get around > > it. (Defining __SMP__

Re: Client receives TCP packets but does not ACK

2001-06-13 Thread Robert Kleemann
On 13 Jun 2001, Andi Kleen wrote: > The packet likely doesn't fit into the socket buffer and is silently > dropped. The TCP stack doesn't force an ACK in this case, but it > probably should, although it wouldn't solve the deadlock. The deadlock > will be only solved if the local application reads

Going beyond 256 PCI buses

2001-06-13 Thread Tom Gall
Anyway, Hi All, I was wondering if there are any other folks out there like me who have the 256 PCI bus limit looking at them straight in the face? If so, it'd be nice to collaborate and come up with a more general solution that would hopefully work towards the greater good. I live in

Re: [craigl@promise.com: Getting A Patch Into The Kernel] (fwd)

2001-06-13 Thread Rob Landley
On Wednesday 13 June 2001 03:06, Andre Hedrick wrote: > No I would not take their code and apply it. > I might not even want to look at it. Well, you're maintainer and I'm obviously not, but it's nice to hear you've kept an open mind on this issue. :) > All I want is the API rules to the

3C905B -- EEPROM (i blive so) problem

2001-06-13 Thread L. K.
Hi, I have a 3COM 3C905B ethernet card that has been hit by a power outage for aprox. 0.5 sec. Now, the kernel does not recongnize the card anymore. When I do lspci, I see 3COM Ethernet controller, type unknown 0xff (rev 3x). The bios reports the card as an ethernet card at system boot-up.

Re: SMP module compilation on UP?

2001-06-13 Thread Rafael Herrera
Mark Mokryn wrote: > Is it possible to build an SMP module on a machine running a UP kernel > (or vice versa)? We of course get unresolved symbols during module load > due to the smp prefix on the ksyms, and haven't seen how to get around > it. (Defining __SMP__ does not cut it, though I believe

FYI: ECN approved as Standard

2001-06-13 Thread jamal
The IESG approved ECN as a proposed standard on the 12th of June. That means as of now, anyone blocking ECN bits is considered to be blaspheming. cheers, jamal - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More

sis630 - help needed debugging in the kernel

2001-06-13 Thread René Rebe
Hi all! I currently try to debug why the sisfb driver crashes my machine. (SIS 630 based laptop - linux-2.4.5-ac13). On my serial-console I get: [...] sisfb: framebuffer at 0xe000, mapped to 0xcb80, size 16384k sisfb: MMIO at 0xefce, mapped to 0xcc801000, size 128k sisfb:

Re: 2.4.5 data corruption

2001-06-13 Thread Nathan Straz
On Tue, Jun 12, 2001 at 01:17:49PM -0700, Larry McVoy wrote: > Folks, I believe I have a reproducible test case which corrupts data in > 2.4.5. Why don't you send the test case to the list? I would love to try it out and it would be a good addition to LTP. -- Nate Straz

Re: Hour long timeout to ssh/telnet/ftp to down host?

2001-06-13 Thread Rob Landley
On Wednesday 13 June 2001 05:40, Luigi Genoni wrote: > On Tue, 12 Jun 2001, Ben Greear wrote: > > You can tune things by setting the tcp-timeout probably..I don't > > know exactly where to set this.. > > /proc/sys/net/ipv4/tcp_fin_timeout > > default is 60. Never got that far. My problem was

SMP module compilation on UP?

2001-06-13 Thread Mark Mokryn
Hi, Is it possible to build an SMP module on a machine running a UP kernel (or vice versa)? We of course get unresolved symbols during module load due to the smp prefix on the ksyms, and haven't seen how to get around it. (Defining __SMP__ does not cut it, though I believe this used to work a

Re: threading question

2001-06-13 Thread ognen
Solaris has pset_create() and pset_bind() where you can bind LWPs to specific processors, but I doubt this works on anything else Best regards, Ognen On Wed, 13 Jun 2001, Philips wrote: > BTW. > Question was poping in my mind and finally got negative answer by my mind ;-) > >

Re: [patch] 2.4.6-pre3 unresolved symbol do_softirq

2001-06-13 Thread Russell King
On Wed, Jun 13, 2001 at 04:44:40PM +0200, Andreas Schwab wrote: > Use %c0. *Note Output Templates and Operand Substitution: (gcc)Output > Template. Oh great! I can get rid of some more crap from the ARM tree! Thanks. -- Russell King ([EMAIL PROTECTED])The developer of ARM

Re: [patch] 2.4.6-pre3 unresolved symbol do_softirq

2001-06-13 Thread Russell King
On Wed, Jun 13, 2001 at 07:21:41AM -0700, David S. Miller wrote: > I can't believe there is no reliable way to get rid of that > pesky "$" gcc is adding to the symbol. Oh well... GCC on ARM does a similar thing - all constants in the assembler are prefixed with '#' or '@'. Using the 'i'

Re: [patch] 2.4.6-pre3 unresolved symbol do_softirq

2001-06-13 Thread Andrew Morton
"David S. Miller" wrote: > > Keith Owens writes: > > #define my_symbol my_symbol_versioned > > extern void my_symbol(void); > > > > void foo(void) { __asm__("call %0" : : "i" (my_symbol)); } > > > > # gcc -o x x.c > > /tmp/cclWXduj.s: Assembler messages: > > /tmp/cclWXduj.s:12:

  1   2   3   >