On Thu, 14 Jun 2001, Kip Macy wrote:
> As I mentioned previously IP heavy is a euphemism for commodity.
...and 3Com is notoriuos for putting out commodity, cheesy hardware.
Kelsey Hudson [EMAIL PROTECTED]
Software Engineer
Compendium Technologies,
On Thu, 14 Jun 2001 [EMAIL PROTECTED] wrote:
> Erm, that is going to be a problem. Crypto benifits more from open source
> than any other market segment, and binary only drivers for linux are not
> the way to go. I guess I need to get rid of my 5-10 3cr990s and replace
> them with someone
On Thu, 14 Jun 2001 [EMAIL PROTECTED] wrote:
Erm, that is going to be a problem. Crypto benifits more from open source
than any other market segment, and binary only drivers for linux are not
the way to go. I guess I need to get rid of my 5-10 3cr990s and replace
them with someone else's
On Thu, 14 Jun 2001, Kip Macy wrote:
As I mentioned previously IP heavy is a euphemism for commodity.
...and 3Com is notoriuos for putting out commodity, cheesy hardware.
Kelsey Hudson [EMAIL PROTECTED]
Software Engineer
Compendium Technologies,
On 6 Jun 2001, David N. Welton wrote:
>
> [ please CC replies to me ]
>
> Perusing the kernel sources while investigating watchdog drivers, I
> notice that in some places, Fahrenheit is used, and in some places,
> Celsius. It would seem logical to me to have a global config option,
> so that
On 6 Jun 2001, David N. Welton wrote:
[ please CC replies to me ]
Perusing the kernel sources while investigating watchdog drivers, I
notice that in some places, Fahrenheit is used, and in some places,
Celsius. It would seem logical to me to have a global config option,
so that you
On Tue, 29 May 2001, John Chris Wren wrote:
> Should the man pages be changed to reflect reality, or select() fixed to
> act like BSD?
>
BSD should be destroyed :)
Kelsey Hudson [EMAIL PROTECTED]
Software Engineer
Compendium Technologies, Inc
On Tue, 29 May 2001, John Chris Wren wrote:
Should the man pages be changed to reflect reality, or select() fixed to
act like BSD?
BSD should be destroyed :)
Kelsey Hudson [EMAIL PROTECTED]
Software Engineer
Compendium Technologies, Inc
On Thu, 10 May 2001, Geert Uytterhoeven wrote:
> - Political fixes:
> o There were still some penguins left carrying a glass of beer or wine.
> This problem is about 2 years old!
I still don't understand why the penguin holding beer/wine was wrong...
Kelsey Hudson
On Thu, 10 May 2001, Geert Uytterhoeven wrote:
- Political fixes:
o There were still some penguins left carrying a glass of beer or wine.
This problem is about 2 years old!
I still don't understand why the penguin holding beer/wine was wrong...
Kelsey Hudson
cx863877-d% gcc --version
2.95.3
cx863877-d% uptime
3:26pm up 14 days, 15:15, 15 users, load average: 2.01, 2.01, 2.00
cx863877-d% uname -a
Linux cx863877-d.cv1.sdca.home.com 2.4.3 #3 SMP Wed Apr 4 00:06:17 PDT
2001 i686 unknown
No problems at all :)
On Fri, 6 Apr 2001, Jeff Chua wrote:
Um... Looks like when you clock the BX-chipset out of spec (>100MHz FSB)
you get the error. Since BX wasn't ever designed to be run at >100MHz
these errors are *expected*.
You have a couple solutions: Upgrade the motherboard to one of the VIA
133MHz chipsets (I dont care for the VIA chipset so
Um... Looks like when you clock the BX-chipset out of spec (100MHz FSB)
you get the error. Since BX wasn't ever designed to be run at 100MHz
these errors are *expected*.
You have a couple solutions: Upgrade the motherboard to one of the VIA
133MHz chipsets (I dont care for the VIA chipset so
cx863877-d% gcc --version
2.95.3
cx863877-d% uptime
3:26pm up 14 days, 15:15, 15 users, load average: 2.01, 2.01, 2.00
cx863877-d% uname -a
Linux cx863877-d.cv1.sdca.home.com 2.4.3 #3 SMP Wed Apr 4 00:06:17 PDT
2001 i686 unknown
No problems at all :)
On Fri, 6 Apr 2001, Jeff Chua wrote:
On Wed, 4 Apr 2001, Boris Pisarcik wrote:
> I looked a bit at the source of sysrq handling. I've found there is
> rather big difference between sysrq+b and other killers handling.
> Sysrq+b is just called with pretty straitforward fashion - stops other
> processors on SMP and reboots directly
On Wed, 4 Apr 2001, Boris Pisarcik wrote:
I looked a bit at the source of sysrq handling. I've found there is
rather big difference between sysrq+b and other killers handling.
Sysrq+b is just called with pretty straitforward fashion - stops other
processors on SMP and reboots directly
On Sat, 31 Mar 2001, Boris Pisarcik wrote:
> on say tty2. The processes get created pretty fast. After a short while
> I supposed a single solution to this to kill all session by alt+sysrq+k,
> but nothing happened. Under normal averagely loaded situation, this will
> imidiately kill all
On Wed, 28 Mar 2001, Jesse Pollard wrote:
> Sure - very simple. If the execute bit is set on a file, don't allow
> ANY write to the file. This does modify the permission bits slightly
> but I don't think it is an unreasonable thing to have.
Oh, honestly! Think about what you are saying here:
On Wed, 28 Mar 2001, Jesse Pollard wrote:
Sure - very simple. If the execute bit is set on a file, don't allow
ANY write to the file. This does modify the permission bits slightly
but I don't think it is an unreasonable thing to have.
Oh, honestly! Think about what you are saying here:
What
On Sat, 31 Mar 2001, Boris Pisarcik wrote:
on say tty2. The processes get created pretty fast. After a short while
I supposed a single solution to this to kill all session by alt+sysrq+k,
but nothing happened. Under normal averagely loaded situation, this will
imidiately kill all processes on
I've got a DPT SmartCACHE IV with the raid adaptor... I'd like to get it
working eventually. If you point me in the right direction I'll see if I
can get that pesky driver to work, and even port over some code if need
beall someone has to do is point me towards documnentation and I'll
make it
I've got a SmartCACHE IV...This driver seems not to recognize it.
I applied it to 2.4.2...the patch didn't apply cleanly, however.
I was able to manually patch the makefile to build the drivers for the
card however, but it still didn't want to work.
In any case, if you have any insight on this
I've got a DPT SmartCACHE IV with the raid adaptor... I'd like to get it
working eventually. If you point me in the right direction I'll see if I
can get that pesky driver to work, and even port over some code if need
beall someone has to do is point me towards documnentation and I'll
make it
I've got a SmartCACHE IV...This driver seems not to recognize it.
I applied it to 2.4.2...the patch didn't apply cleanly, however.
I was able to manually patch the makefile to build the drivers for the
card however, but it still didn't want to work.
In any case, if you have any insight on this
On Tue, 6 Mar 2001, Peter Samuelson wrote:
> [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 wi
On Tue, 6 Mar 2001, Peter Samuelson wrote:
[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.
a long while ago... i
On Mon, 5 Mar 2001, John Kodis wrote:
> On Mon, Mar 05, 2001 at 08:40:22AM -0500, Richard B. Johnson wrote:
>
> > Somebody must have missed the boat entirely. Unix does not, never
> > has, and never will end a text line with '\r'.
>
> Unix does not, never has, and never will end a text line
On Mon, 5 Mar 2001, John Kodis wrote:
On Mon, Mar 05, 2001 at 08:40:22AM -0500, Richard B. Johnson wrote:
Somebody must have missed the boat entirely. Unix does not, never
has, and never will end a text line with '\r'.
Unix does not, never has, and never will end a text line with ' '
On Thu, 1 Mar 2001, Matilainen Panu (NRC/Helsinki) wrote:
> I've been playing around with 8-way IBM8500R (8x700MHz Xeon) with 4.5GB
> memory & AIC7xxx SCSI-controller. It's perfectly stable with 2.2-kernel
> (from Red Hat 7) but very erratic on all 2.4-kernels I've tried it with
> (2.4.[012],
On Wed, 28 Feb 2001, Boris Dragovic wrote:
> what does negative module use count mean?
That means that there's a bug in someone's driver.
For some reason, the function to decrement the module use is called more
than once when a controlling process releases use of a module.
This will prevent
On Wed, 28 Feb 2001, Boris Dragovic wrote:
what does negative module use count mean?
That means that there's a bug in someone's driver.
For some reason, the function to decrement the module use is called more
than once when a controlling process releases use of a module.
This will prevent you
On Thu, 1 Mar 2001, Matilainen Panu (NRC/Helsinki) wrote:
I've been playing around with 8-way IBM8500R (8x700MHz Xeon) with 4.5GB
memory AIC7xxx SCSI-controller. It's perfectly stable with 2.2-kernel
(from Red Hat 7) but very erratic on all 2.4-kernels I've tried it with
(2.4.[012],
On Wed, 21 Feb 2001, Leif Sawyer wrote:
> > From: Dr. Kelsey Hudson [mailto:[EMAIL PROTECTED]]
> >
> > 'good' in this case was meant to mean working properly, well-coded,
> > does-what-it's-suppossed-to-do, eg not broken in one way or
> > another. English should
On Thu, 22 Feb 2001, Augustin Vidovic wrote:
> On Wed, Feb 21, 2001 at 03:00:26PM -0800, Dr. Kelsey Hudson wrote:
> > By saying this, you are implying that all pieces of code released under
> > the GPL are 'good' pieces of code.
>
> If you want to rephrase it like that,
On Sat, 17 Feb 2001, Torrey Hoffman wrote:
> On the other hand, they make excellent mice. The mouse wheel and
> the new optical mice are truly innovative and Microsoft should be
> commended for them.
The idea of an optical mouse is nothing new: I've got an optical mouse
sitting to the side of
On Sat, 17 Feb 2001, Alan Olsen wrote:
> "You keep using that word. i don't think it means what you think it
> means."
...To quote Indigo Montoya, speaking to Vuzinni, from "The Princess
Bride" :)
One hell of a story :)
Kelsey Hudson [EMAIL
On Sat, 17 Feb 2001, Augustin Vidovic wrote:
> 1- GPL code is the opposite of crap
By saying this, you are implying that all pieces of code released under
the GPL are 'good' pieces of code. I can give you several examples of code
where this is not the case; several I have written for my own
On Sat, 17 Feb 2001, Augustin Vidovic wrote:
1- GPL code is the opposite of crap
By saying this, you are implying that all pieces of code released under
the GPL are 'good' pieces of code. I can give you several examples of code
where this is not the case; several I have written for my own use,
On Sat, 17 Feb 2001, Alan Olsen wrote:
"You keep using that word. i don't think it means what you think it
means."
...To quote Indigo Montoya, speaking to Vuzinni, from "The Princess
Bride" :)
One hell of a story :)
Kelsey Hudson [EMAIL PROTECTED]
On Sat, 17 Feb 2001, Torrey Hoffman wrote:
On the other hand, they make excellent mice. The mouse wheel and
the new optical mice are truly innovative and Microsoft should be
commended for them.
The idea of an optical mouse is nothing new: I've got an optical mouse
sitting to the side of my
On Thu, 22 Feb 2001, Augustin Vidovic wrote:
On Wed, Feb 21, 2001 at 03:00:26PM -0800, Dr. Kelsey Hudson wrote:
By saying this, you are implying that all pieces of code released under
the GPL are 'good' pieces of code.
If you want to rephrase it like that, ok, but then you must not forget
On Wed, 21 Feb 2001, Leif Sawyer wrote:
From: Dr. Kelsey Hudson [mailto:[EMAIL PROTECTED]]
'good' in this case was meant to mean working properly, well-coded,
does-what-it's-suppossed-to-do, eg not broken in one way or
another. English should have a better word that 'good
On Wed, 14 Feb 2001, Mike Harrold wrote:
>
> The sad thing is, 3/4 of the page is an outright lie. It isn't
> a first, W2k is not the de facto standard OS, and the TCO is
> significantly higher than any cluster running Linux.
No shit, not to mention that Linux is going to be faster and better
On Wed, 14 Feb 2001, Mike Harrold wrote:
The sad thing is, 3/4 of the page is an outright lie. It isn't
a first, W2k is not the de facto standard OS, and the TCO is
significantly higher than any cluster running Linux.
No shit, not to mention that Linux is going to be faster and better
On Thu, 1 Feb 2001, Alan Chandler wrote:
> I accidentally built my 2.4.1 kernel with /devfs so had a interesting
> few minutes looking round it to see what it was doing.
>
> The thing that struck me most was the spelling of disc with a 'c'. As
> an Englishman this is the correct spelling for
On Wed, 31 Jan 2001, Scott Laird wrote:
> On Wed, 31 Jan 2001, George wrote:
> > Also account for anything else funny in the system.
> >
> > Then panic on boot if they're wrong (sort of like processor type).
>
> Where do cards with PCI-PCI bridges, like multiport PCI ethernet cards,
> fit into
You might also want to run setiathome with the -nice option...for
instance i *always* run it with -nice 19 so that it lays in the background
consuming otherwise idle cycles. anything wanting cpu time will then take
it from seti.
On Wed, 31 Jan 2001, Alex Deucher wrote:
> Rainer,
>
> I'm
Do you have framebuffer console compiled into your kernel? I noticed
similar behavior on my system when I had framebuffer console compiled in,
ACPI or APM (cant remember which, probably ACPI) compiled in, and bttv as
modules. System would power off when ACPI was loaded. Other times it would
do
Do you have framebuffer console compiled into your kernel? I noticed
similar behavior on my system when I had framebuffer console compiled in,
ACPI or APM (cant remember which, probably ACPI) compiled in, and bttv as
modules. System would power off when ACPI was loaded. Other times it would
do
You might also want to run setiathome with the -nice option...for
instance i *always* run it with -nice 19 so that it lays in the background
consuming otherwise idle cycles. anything wanting cpu time will then take
it from seti.
On Wed, 31 Jan 2001, Alex Deucher wrote:
Rainer,
I'm
On Wed, 31 Jan 2001, Scott Laird wrote:
On Wed, 31 Jan 2001, George wrote:
Also account for anything else funny in the system.
Then panic on boot if they're wrong (sort of like processor type).
Where do cards with PCI-PCI bridges, like multiport PCI ethernet cards,
fit into this? I
On Thu, 1 Feb 2001, Alan Chandler wrote:
I accidentally built my 2.4.1 kernel with /devfs so had a interesting
few minutes looking round it to see what it was doing.
The thing that struck me most was the spelling of disc with a 'c'. As
an Englishman this is the correct spelling for me
On Wed, 17 Jan 2001, Werner Almesberger wrote:
> "no", because you don't have to do it in the kernel. You can mount by
> uuid or label. For the root FS, you do this from an initrd. Problem
> solved.
>
> The only cases when you really need to know the name of a disk is when
> - doing disk-level
On Wed, 17 Jan 2001, Dominik Kubla wrote:
> Just switched to 2.4.0-ac9 (+crypto patches) on our Dual-Pentium MMX
> webserver yesterday. Works fine so far, except i keep seeing those
> APIC erros (about 14 in 12 hrs) indicating receive, send and CS errors.
Make sure your system is free of
On Wed, 17 Jan 2001, Dominik Kubla wrote:
Just switched to 2.4.0-ac9 (+crypto patches) on our Dual-Pentium MMX
webserver yesterday. Works fine so far, except i keep seeing those
APIC erros (about 14 in 12 hrs) indicating receive, send and CS errors.
Make sure your system is free of
On Wed, 17 Jan 2001, Werner Almesberger wrote:
"no", because you don't have to do it in the kernel. You can mount by
uuid or label. For the root FS, you do this from an initrd. Problem
solved.
The only cases when you really need to know the name of a disk is when
- doing disk-level
On Wed, 17 Jan 2001, Stefan Ring wrote:
> 2.0.37+ kernels crash even before I can see the "Uncompressing linux..."
> message. I use the same configuration for 2.0.36 and 2.0.37 (basically
> it's the default configuration without anything interesting changed), and
> the latter just won't work. It
On Wed, 17 Jan 2001, J . A . Magallon wrote:
> You want to make things SOOO easy for a 'dummy' user, and that user will never
> use them. The average user you are targetting says: 'daddy, buy me a PC to
> run Quake and do my school jobs' or 'please, dear vendor, I want a PC to
> do my
On Tue, 16 Jan 2001, Michael Meissner wrote:
> > you're forgetting that in /etc/lilo.conf there is a directive called
> > 'append='... all the user has to do is merely add
> > 'append="scsihosts=whatever,whatever"' into their config file and rerun
> > lilo. problem solved
>
> That's assuming
On Tue, 16 Jan 2001, Venkatesh Ramamurthy wrote:
> [Venkatesh Ramamurthy] Dont you think that mounting and booting
> based on disk label names is better, then relying on device nodes which can
> change when a new card is added?. The existing patch for 2.2.xx is quite
> small and it does
On Tue, 16 Jan 2001, Venkatesh Ramamurthy wrote:
> > This is due to the fixed ordering of the scsi drivers. You can change the
> > order of the scsi hosts with the "scsihosts" kernel parameter. See
> > linux/drivers/scsi/scsi.c
> [Venkatesh Ramamurthy] I think it would be a nice idea if
On Tue, 16 Jan 2001, Michael Meissner wrote:
you're forgetting that in /etc/lilo.conf there is a directive called
'append='... all the user has to do is merely add
'append="scsihosts=whatever,whatever"' into their config file and rerun
lilo. problem solved
That's assuming you are
On Wed, 17 Jan 2001, Stefan Ring wrote:
2.0.37+ kernels crash even before I can see the "Uncompressing linux..."
message. I use the same configuration for 2.0.36 and 2.0.37 (basically
it's the default configuration without anything interesting changed), and
the latter just won't work. It
On Wed, 17 Jan 2001, J . A . Magallon wrote:
You want to make things SOOO easy for a 'dummy' user, and that user will never
use them. The average user you are targetting says: 'daddy, buy me a PC to
run Quake and do my school jobs' or 'please, dear vendor, I want a PC to
do my
On Tue, 16 Jan 2001, Venkatesh Ramamurthy wrote:
This is due to the fixed ordering of the scsi drivers. You can change the
order of the scsi hosts with the "scsihosts" kernel parameter. See
linux/drivers/scsi/scsi.c
[Venkatesh Ramamurthy] I think it would be a nice idea if we can
On Tue, 16 Jan 2001, Venkatesh Ramamurthy wrote:
[Venkatesh Ramamurthy] Dont you think that mounting and booting
based on disk label names is better, then relying on device nodes which can
change when a new card is added?. The existing patch for 2.2.xx is quite
small and it does not
On Sat, 13 Jan 2001, Roeland Th. Jansen wrote:
> you can say about the BP6 what you want but it appears that there are
> (if your vision is right) many other low end SMP boards categorized
> trash. there has been one mistake with it and that's the capacitor
> behind a regulator that may have
This is due to your piece of trash motherboard. The reason that the older
kernel didn't catch these errors is because (IIRC) it wasn't looking for
them; they were there even then. The BP6 is a low-end mainboard and was
engineered very poorly; these errors are due to that fact alone.
Talk to you
This is due to your piece of trash motherboard. The reason that the older
kernel didn't catch these errors is because (IIRC) it wasn't looking for
them; they were there even then. The BP6 is a low-end mainboard and was
engineered very poorly; these errors are due to that fact alone.
Talk to you
append="console=/dev/ttyS0"
that should do the trick
enjoy
-kelsery
On Mon, 8 Jan 2001, Paul Powell wrote:
> Hello,
>
> I am running an unmodified RedHat 6.2 kernel
> (kernel version 2.2.14-5.0)
>
> I am trying to redirect the linux startup messages to
> the serial port. I've added the
On Thu, 14 Dec 2000, David Riley wrote:
> Did I miss a post from Linus on the list, or is there no posted
> changelog for test13-pre1? Nothing's posted at kernel.org yet, either.
>
I musta missed the post too... But then again I went back and looked for
it and couldnt find it so...
i'd like
It looks like you've been r00ted, dude!
Someone installed a r00tk1t and you are now seeing the after-effects of
it. What I'd do, in your case:
back up /usr/local, /home, /etc, then reload the system clean, and replace
teh backups. The system should be in a close state (read: no root kit) to
nope, DVD discs all use UDF.
it'd be nice if they used something more common, but hey...
On Wed, 13 Dec 2000, Gregoire Favre wrote:
> zink wrote:
>
> > The final 2.2.18 is out - I didn't see UDF option under filesystems, altough it
>should
> > have been there - maybe we'll wait (for ages)
nope, DVD discs all use UDF.
it'd be nice if they used something more common, but hey...
On Wed, 13 Dec 2000, Gregoire Favre wrote:
zink wrote:
The final 2.2.18 is out - I didn't see UDF option under filesystems, altough it
should
have been there - maybe we'll wait (for ages)
It looks like you've been r00ted, dude!
Someone installed a r00tk1t and you are now seeing the after-effects of
it. What I'd do, in your case:
back up /usr/local, /home, /etc, then reload the system clean, and replace
teh backups. The system should be in a close state (read: no root kit) to
On Thu, 14 Dec 2000, David Riley wrote:
Did I miss a post from Linus on the list, or is there no posted
changelog for test13-pre1? Nothing's posted at kernel.org yet, either.
I musta missed the post too... But then again I went back and looked for
it and couldnt find it so...
i'd like to
Yeah, get yourself one of those nifty add-in IDE controllers that CAN see
drives greater than 32GB. S'What I did and it works fine.
On Fri, 8 Dec 2000, Matan Ziv-Av wrote:
>
> Hi,
>
>
> I have an IBM drive, DTLA-307075 (75GB), and a bios that hangs with
> large disks. I use a jumper to clip
On Fri, 8 Dec 2000 [EMAIL PROTECTED] wrote:
> On Thu, 7 Dec 2000, Jeff V. Merkey wrote:
>
> > I think there may be a case when a process forks, that the MMU or some
> > other subsystem is either not setting the page bits correctly, or
> > mapping in a bad page. It's a LEVEL I bug in 2.4 is
On Thu, 7 Dec 2000, Peter Samuelson wrote:
>
> [Dick Johnson]
> > Do:
> >
> > char main[]={0xff,0xff,0xff,0xff};
>
> Oh come on, at least pick an *interesting* invalid opcode:
>
> char main[]={0xf0,0x0f,0xc0,0xc8}; /* try also on NT (: */
What's funny, is that this actually executes on
On Thu, 7 Dec 2000, Peter Samuelson wrote:
[Dick Johnson]
Do:
char main[]={0xff,0xff,0xff,0xff};
Oh come on, at least pick an *interesting* invalid opcode:
char main[]={0xf0,0x0f,0xc0,0xc8}; /* try also on NT (: */
What's funny, is that this actually executes on SPARC
On Fri, 8 Dec 2000 [EMAIL PROTECTED] wrote:
On Thu, 7 Dec 2000, Jeff V. Merkey wrote:
I think there may be a case when a process forks, that the MMU or some
other subsystem is either not setting the page bits correctly, or
mapping in a bad page. It's a LEVEL I bug in 2.4 is this is the
It uses the via-rhine driver on my system
On Thu, 7 Dec 2000, James Bourne wrote:
> On Wed, 6 Dec 2000, Mike A. Harris wrote:
>
> > Which ethernet module works with this card? 2.2.17 kernel
>
> Should be the rtl8139 driver.
>
> Regards,
> Jim
>
> >
It uses the via-rhine driver on my system
On Thu, 7 Dec 2000, James Bourne wrote:
On Wed, 6 Dec 2000, Mike A. Harris wrote:
Which ethernet module works with this card? 2.2.17 kernel
Should be the rtl8139 driver.
Regards,
Jim
On Sat, 25 Nov 2000, Henning P. Schmiedehausen wrote:
> No, it does not. Distributing does. You will never get this right. You
> can compile into your kernel anything you like as long as you don't
> give it away.
You are wrong: If you modify the kernel you have to make it available for
anyone
On Sat, 25 Nov 2000, Henning P. Schmiedehausen wrote:
No, it does not. Distributing does. You will never get this right. You
can compile into your kernel anything you like as long as you don't
give it away.
You are wrong: If you modify the kernel you have to make it available for
anyone who
On Sun, 19 Nov 2000, Vincent wrote:
> Using linux-2.4.0-test11-pre7 right now..., here's what i did,
> mount /mnt/cdrom
> cd /mnt/cdrom
> ls
> Segmentation fault
> ls
> *NOT Responding*
> can't kill /sbin/ls
> can't umount /mnt/cdrom
> ps , shows ;
>
> 613 ?D 0:00 /bin/ls
On Sun, 19 Nov 2000, Vincent wrote:
Using linux-2.4.0-test11-pre7 right now..., here's what i did,
mount /mnt/cdrom
cd /mnt/cdrom
ls
Segmentation fault
ls
*NOT Responding*
can't kill /sbin/ls
can't umount /mnt/cdrom
ps , shows ;
613 ?D 0:00 /bin/ls --color=auto -F -b
> This machine isn't even a Xeon, just a PIII CuMine on a ServerWorks HeIII
> chipset.
Strange, I've got a dual Katmai (non-Xeon) and notice the same...
CPU0 CPU1
0: 95135438 95720832IO-APIC-edge timer
1: 579101 572402IO-APIC-edge keyboard
2:
This machine isn't even a Xeon, just a PIII CuMine on a ServerWorks HeIII
chipset.
Strange, I've got a dual Katmai (non-Xeon) and notice the same...
CPU0 CPU1
0: 95135438 95720832IO-APIC-edge timer
1: 579101 572402IO-APIC-edge keyboard
2:
On Fri, 27 Oct 2000 [EMAIL PROTECTED] wrote:
> If Bill said 'screw you' to the blackmailer and made the press release,
> we should see the source on web sites soon. Then we can see how bad it
> really is. Maybe even fix it.
Why bother fixing it? It's too bloated and stupid in the first
On Fri, 27 Oct 2000 [EMAIL PROTECTED] wrote:
If Bill said 'screw you' to the blackmailer and made the press release,
we should see the source on web sites soon. Then we can see how bad it
really is. Maybe even fix it.
Why bother fixing it? It's too bloated and stupid in the first
> Is there a major compelling reason that this patch isn't included
> in the standard kernel tree?
>
>
> --
> Mike A. Harris - Linux advocate - Open source advocate
> Computer Consultant - Capslock
Is there a major compelling reason that this patch isn't included
in the standard kernel tree?
--
Mike A. Harris - Linux advocate - Open source advocate
Computer Consultant - Capslock Consulting
I just had my box completely lock up under 2.4.0-test9. I had insmodded
the dbri.o audio driver, which for some reason was refusing to work, at
all. So I rmmodded it, and at that point, the screen flickered once and
wham, complete lockup, nothing responds at all, no network, no SysRQ,
On Wed, 4 Oct 2000, Jakub Jelinek wrote:
> This does tell nothing if the pcibios thing is fixed or not, because you
> most probably did not configure PCI on your sparc32 (why would you do that,
> when you don't have a JavaStation?).
> So you have to either look at the code or configure PCI in...
On Wed, 4 Oct 2000, Jakub Jelinek wrote:
This does tell nothing if the pcibios thing is fixed or not, because you
most probably did not configure PCI on your sparc32 (why would you do that,
when you don't have a JavaStation?).
So you have to either look at the code or configure PCI in...
Of
I just had my box completely lock up under 2.4.0-test9. I had insmodded
the dbri.o audio driver, which for some reason was refusing to work, at
all. So I rmmodded it, and at that point, the screen flickered once and
wham, complete lockup, nothing responds at all, no network, no SysRQ,
> Question is, is this still broken on -test9-final or did
> the fix Linus merged earlier today get rid of your problems?
Let me try this and find out...
Hmm. I get an error when trying to run 'make xconfig':
gmake[1]: Entering directory `/usr/src/linux-2.4.0-test9/scripts'
cat
> pcic.c: At top level:
> pcic.c:39: redefinition of `pcibios_present'
> /usr/src/linux-2.4.0-test/include/linux/pci.h:562: `pcibios_present' previously
>defined here
> make[1]: *** [pcic.o] Error 1
> make[1]: Leaving directory `/usr/src/linux-2.4.0-test/arch/sparc/kernel'
> make: ***
pcic.c: At top level:
pcic.c:39: redefinition of `pcibios_present'
/usr/src/linux-2.4.0-test/include/linux/pci.h:562: `pcibios_present' previously
defined here
make[1]: *** [pcic.o] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.0-test/arch/sparc/kernel'
make: ***
1 - 100 of 102 matches
Mail list logo
