Hi all
I\'ve asked this question on a few other email list with no responce, so as a
last resort I\'m posting it here.
I\'m trying to get a system going which has two links to the internet. One has
class C range routed over it and the other will need to be Masq\'d.
I want to route traffic like
Hi,
Over the weekend sometime a Linux machine where I work oops'd. Nobody else
here really understands anything about this stuff so they rang me. I got
them to copy out what was on the screen and then reboot (this was
Monday). Today (Wednesday) I copied in the text and ran it through
ksymoops.
N
Hi there,
I updated my system from RedHat 6.0 -> RedHat 7.0 and Murphy is still
working.
[1]
I can't compile Kernel 2.2.17 since the update.
(make bzImage)
[2]
Error Message:
make[2]: Entering directory '/usr/src/linux-2.2.17/arch/i386/lib'
cc -D__KERNEL__ -I/usr/src/li
he CD drives
in the tower by their individual SCSI target ids from here on out.
This decision came about after the following operating systems were
unable to make any sense of the tower:
SunOS
SCO
Windows 98
Windows 2000
Linux 2.2.17
I figured if _none_ of these could work with the tower, each one
Amit D Chaudhary wrote:
>
> Hi,
>
> When trying to create a patch with linux 2.2.17 sources, I found the
> following files to be of size 0 in linux-2.2.17.tar.gz.
> linux/include/linux/dasd.h
> linux/include/linux/coda_opstats.h
>
> Since the file is the mos
Sorry, I might not been clear enough, I meant the files are of size 0 in
the following file and also it's valinux mirror,
ftp://ftp.kernel.org/pub/linux/kernel/v2.2/linux-2.2.17.tar.gz
I did not patch the sources, I was just extracting the tar file.
Alan or someone who looks in the so
[Jan-Benedict Glaw]
> Your kernel was probably patched te become a 2.2.17. The "problem"
> is diff. It can
> - add lines
> - remove lines
> - add files
> but it *cannot remove files. The only way to "remove" a file is to
> delete all ist contents, but the (empty) file remains...
On Thu, Oct 12, 2000 at 03:58:21AM -0700, Amit D Chaudhary wrote:
> Hi,
>
> When trying to create a patch with linux 2.2.17 sources, I found the
> following files to be of size 0 in linux-2.2.17.tar.gz.
> linux/include/linux/dasd.h
> linux/include/linux/coda_opstats.h
>
Hi,
When trying to create a patch with linux 2.2.17 sources, I found the
following files to be of size 0 in linux-2.2.17.tar.gz.
linux/include/linux/dasd.h
linux/include/linux/coda_opstats.h
Since the file is the most latest in the kernel/v2.2 directory, thought
should point this out.
Amit
On Mon, 9 Oct 2000, Kurt Garloff wrote:
> On Mon, Oct 09, 2000 at 01:05:10PM +0200, Andre Tomt wrote:
> > The sym53c8xx driver handles this card nicely in u160scsi mode using
> > kernel 2.4testX, but I don't want that kernel on this machine. 2.2.17 does
> > not detect the card, and looking at t
At work we recently acquired a used SCSI CD Tower from somewhere else
in the company. I want to hook this up to my Slackware Linux system,
but I'm having a problem with it. It's being detected by the system,
but only partially. There is also a CDR drive on the SCSI chain that
is being detected
On Mon, Oct 09, 2000 at 01:05:10PM +0200, Andre Tomt wrote:
> The sym53c8xx driver handles this card nicely in u160scsi mode using
> kernel 2.4testX, but I don't want that kernel on this machine. 2.2.17 does
> not detect the card, and looking at the source, the chip, nor the speeds
> are not suppo
I'm still looking for a 2.2.17 driver for my Tekram DC390U3W dual channel
scsi card. I found drivers for 2.2.16 and below on the lsi and tekram
ftp-sites, but applying them causes rejects, and manually fixing the
driver makes sg going into an infinite loop during boot. My C knowledge is
very broke
On Fri, 6 Oct 2000, Mario Lorenz wrote:
> Hi folks,
>
> Linux 2.2.17 (only tested version, I assume all other 2.2 series suffer from
> the same problem and possibly 2.4 as well - but I havent even looked at that).
>
> Assuming a configuration with linuxbox1 eth0 has adresses
Hi folks,
Linux 2.2.17 (only tested version, I assume all other 2.2 series suffer from
the same problem and possibly 2.4 as well - but I havent even looked at that).
Assuming a configuration with linuxbox1 eth0 has adresses 192.168.129.1 and
192.168.130.1, and IP forward being enabled, and
On Mon, Sep 04, 2000 at 10:58:09PM +0200, Pedro M. Rodrigues wrote:
>
>The change to eepro100 done in pre16 isn´t listed as being
> restored. Is it still in i/o mode?
The investigation hasn't succeeded yet.
It looks like a timing problem (however, I'm not so sure now).
I spent 3 full evenin
The change to eepro100 done in pre16 isn´t listed as being
restored. Is it still in i/o mode?
Pedro
On 4 Sep 2000, at 19:53, Alan Cox wrote:
> Ok Linux 2.2.17 official is now out. This is the same as 2.2.17pre20 without
> the -pre20 id string
>
[...]
>
> 2.2.17
On Sat, 23 Sep 2000, Horst von Brand wrote:
>Some other funny stuf is happening, I'll try on monday without NFSv3 in
>kernel, and mounting from the PC.
I will add, Solaris ignores the capabilities of mountd and will attempt
an NFSv3 connection if it sees a v3 nfsd registered. You can tell mountd
Chris Pascoe <[EMAIL PROTECTED]> said:
> Is anyone else experiencing an interoperability problem when running the
> nfs-utils 0.1.9.1 or 0.2 on an (unpatched) 2.2.16 or 2.2.17 kernel NFS
> Server, exporting to a Solaris 8 Sparc (patched with recommended patches
> as of 6/Sep/2000) client. (Am I t
Is anyone else experiencing an interoperability problem when running the
nfs-utils 0.1.9.1 or 0.2 on an (unpatched) 2.2.16 or 2.2.17 kernel NFS
Server, exporting to a Solaris 8 Sparc (patched with recommended patches
as of 6/Sep/2000) client. (Am I the only one trying this config?) I had
a brie
k in 2.0.35 (which was the last time I actually tried to use an initrd
> for anything..)
>
> The 2.4.0test kernels work fine. For the record:
>
> -8<-- /usr/src/linux-2.2.17
> :
> CONFIG_BLK_DEV_RAM=y
> CONFIG_BLK_DEV_RAM_SIZE=4096
> CONFIG_BLK_DEV_INITR
an initrd
for anything..)
The 2.4.0test kernels work fine. For the record:
-8<-- /usr/src/linux-2.2.17
:
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
:
--8<--
Any ideas why this isn't working? More importantly, if this is known not
t
Ok Linux 2.2.17 official is now out. This is the same as 2.2.17pre20 without
the -pre20 id string
This is the version waiting Linus. Its in the queue for holy penguin pee so
either it will get peed on or I will get abuse from Linus depending whether
he likes it or not 8)
In the mean time I&#
23 matches
Mail list logo
