Hello all.
I sent a message a week or so ago asking for assistance. Thank you to all
who gave advise, and to those who considered it. I did try all the angles
advised, but still there is a problem. I then tried following the Red Hat
RH300 training manual, but still no success.
I am attempting
hi,
i'm trying to find out how redhat kernel mods prevent hidden arp patch
(hidden-2.4.5-1.diff) from functioning. I just patched kernel.org 2.4.18
and everything looks fine - i'm not able to ping lo:0 on the net.
the patch:
http://www.linux-vs.org/~julian/hidden-2.4.5-1.diff
arp probl
> Hi,
> I am trying to build kernel2.0.36. Could anyone please
> tell me which version of Redhat supports kernel
> 2.0.36.?? When I tried compiling with Redhat7.0 and
> Redhat 6.1, it gives me lots of compilation errors for
> kernel 2.0.36, but for 2.4, it compiles and builds an
> image fine.
>
Hi,
I am trying to build kernel2.0.36. Could anyone please
tell me which version of Redhat supports kernel
2.0.36.?? When I tried compiling with Redhat7.0 and
Redhat 6.1, it gives me lots of compilation errors for
kernel 2.0.36, but for 2.4, it compiles and builds an
image fine.
Also, Could any
Frank Liu <[EMAIL PROTECTED]> writes:
> This is not runtime, it is compile time.
> (even if it is runtime, how can uname() tell if you are running
> a kernel provided by redhat or downloaded from kernel.org?).
>
> Anyway, the program calls function
> kill_fasync()
> under Redhat's kernel, it re
On Sat, 26 Aug 2000, John Summerfield wrote:
>> It's not as easy as I thought. Not all redhat kernels are equal.
>> Some of them has an extra argument to kill_fasync(). It seems this
>> has been added since 2.2.14 but I don't have all redhat kernels to
>> check. Can somebody comfirm this and tell
his snip from emu10k1 driver Makefile :
ifneq ($(shell grep '__rh_kernel_version_h__'
$(KERNELSOURCE)/include/linux/version.h),)
# redhat kernel headers style
SUB := $(shell grep __BOOT_KERNEL_ /boot/kernel.h 2>/dev/null | grep 1 | cut -d\_
-f5 | tr [:upper:] [:lower:] | cut -d&#x
> It's not as easy as I thought. Not all redhat kernels are equal.
> Some of them has an extra argument to kill_fasync(). It seems this
> has been added since 2.2.14 but I don't have all redhat kernels to
> check. Can somebody comfirm this and tell why this change is necessary?
That sort of probl
> On Thu, 24 Aug 2000, John Summerfield wrote:
>
> Try:
>
> rpm -qf /boot/kernel.h
>
> That tells the truth. Then you know where it came from. If
> nothing shows, then it wasn't installed by RPM.
>
> Just a thought...
I already answered that. It's part of kernel-headers where it exists on
the
> > uname() function.
> >
> > Matt
> >
> > On Wed, Aug 23, 2000 at 02:35:23PM -0500, Frank Liu wrote:
> > >
> > > Since redhat kernel is a bit different from the stock kernel source
On Wed, 23 Aug 2000, Frank Liu wrote:
>> so what the problem ? on the emu machine is not generated for i don't
>> reason, and with the possum machine it generated, and Frank can play
>> with that (actually with version.h who manage to play with kernel.h)
>
>kernel.h is useless because on a redhat
On Thu, 24 Aug 2000, John Summerfield wrote:
>> > [summer@emu summer]$ cat /boot/kernel.h
>> > cat: /boot/kernel.h: No such file or directory
>> > [summer@emu summer]$
>> > It's part of kernel-headers. If you've downloades source from ftp.kernel.or
>> g
>> > or a mirror, the file /boot/kernel.h
On Wed, 23 Aug 2000, Frank Liu wrote:
>Since redhat kernel is a bit different from the stock kernel source.
>In my C source code, I need to do things differently depending on
>what kernel the user has. How can I #ifdef test that?
That isn't much to go on. What kind of code, wh
On 23 Aug 2000, Chmouel Boudjnah wrote:
> John Summerfield <[EMAIL PROTECTED]> writes:
>
> > > > [summer@emu summer]$ cat /boot/kernel.h
> > > > cat: /boot/kernel.h: No such file or directory
>
> [...]
>
> > [summer@possum summer]$ ls -l /boot/kernel.h
> > -rw-r--r-- 1 root 237 Dec
> John Summerfield <[EMAIL PROTECTED]> writes:
>
> > > > [summer@emu summer]$ cat /boot/kernel.h
> > > > cat: /boot/kernel.h: No such file or directory
>
> [...]
>
> > [summer@possum summer]$ ls -l /boot/kernel.h
> > -rw-r--r-- 1 root 237 Dec 6 1999 /boot/kernel.h
>
> so what the
you have a redhat system, but
> doesn't mean you have a redhat kernel. I have systems running
> the kernels that I downlaoded from kernel.org but
> still have /boot/kernel.h file that was generated by
> rc.sysinit.
>
> maybe I should
> #include
>
> and then test
&g
/boot/kernel.h is generated by /etc/rc.d/rc.sysinit at
the boot time if it isn't already there (or CPU changed):
check that file for the detailed logic on when/how to
generate this file.
So /boot/kernel.h may show you have a redhat system, but
doesn't mean you have a redhat kern
John Summerfield <[EMAIL PROTECTED]> writes:
> > > [summer@emu summer]$ cat /boot/kernel.h
> > > cat: /boot/kernel.h: No such file or directory
[...]
> [summer@possum summer]$ ls -l /boot/kernel.h
> -rw-r--r-- 1 root 237 Dec 6 1999 /boot/kernel.h
so what the problem ? on the emu m
> John Summerfield <[EMAIL PROTECTED]> writes:
>
> > [summer@emu summer]$ cat /boot/kernel.h
> > cat: /boot/kernel.h: No such file or directory
> > [summer@emu summer]$
> > It's part of kernel-headers. If you've downloades source from ftp.kernel.or
> g
> > or a mirror, the file /boot/kernel.h m
John Summerfield <[EMAIL PROTECTED]> writes:
> [summer@emu summer]$ cat /boot/kernel.h
> cat: /boot/kernel.h: No such file or directory
> [summer@emu summer]$
> It's part of kernel-headers. If you've downloades source from ftp.kernel.org
> or a mirror, the file /boot/kernel.h may not exist, and
> Frank Liu <[EMAIL PROTECTED]> writes:
>
> > This is not runtime, it is compile time.
> > (even if it is runtime, how can uname() tell if you are running
> > a kernel provided by redhat or downloaded from kernel.org?).
> >
> > Anyway, the program calls function
> > kill_fasync()
> > under Redh
Frank Liu <[EMAIL PROTECTED]> writes:
> This is not runtime, it is compile time.
> (even if it is runtime, how can uname() tell if you are running
> a kernel provided by redhat or downloaded from kernel.org?).
>
> Anyway, the program calls function
> kill_fasync()
> under Redhat's kernel, it re
ending on the running kernel.
>
> You shouldn't #ifdef this, you should use runtime checks using the
> uname() function.
>
> Matt
>
> On Wed, Aug 23, 2000 at 02:35:23PM -0500, Frank Liu wrote:
> >
> > Since redhat kernel is a bit different from the stock
I'd be interested to know what you're coding that would behave
differently depending on the running kernel.
You shouldn't #ifdef this, you should use runtime checks using the
uname() function.
Matt
On Wed, Aug 23, 2000 at 02:35:23PM -0500, Frank Liu wrote:
>
> Sin
Since redhat kernel is a bit different from the stock kernel source.
In my C source code, I need to do things differently depending on
what kernel the user has. How can I #ifdef test that?
Thanks!
Frank
___
Redhat-devel-list mailing list
[EMAIL
25 matches
Mail list logo
