Hahahaha.
Dennis, the only linux network drivers that I have had serious problems
with were yours. They caused kernel panic on 2.0.30+ every 6 hours. Of
course I did not have the source to fix them. In comparision eepro100
works rock solid on all of my machines that use it.
Will I use some
Hahahaha.
Dennis, the only linux network drivers that I have had serious problems
with were yours. They caused kernel panic on 2.0.30+ every 6 hours. Of
course I did not have the source to fix them. In comparision eepro100
works rock solid on all of my machines that use it.
Will I use some
Hello.
Just edit lib/isc/unix/resource.c and find following line:
"typedef quad_t rlim_t"
replace it with
"typedef unsigned long rlim_t"
In my case I had also to #undef HAVE_LINUX_CAPABILITY_H in config.h
after running ./configure
This was enough for my libc5 machine
Hello.
Just edit lib/isc/unix/resource.c and find following line:
"typedef quad_t rlim_t"
replace it with
"typedef unsigned long rlim_t"
In my case I had also to #undef HAVE_LINUX_CAPABILITY_H in config.h
after running ./configure
This was enough for my libc5 machine
Hello.
I read the Linux Capabilities FAQ 2.0 and looked at the source in
/usr/src/linux/fs/exec.c. In function prepare_binprm() I see that fE is
always cleared and set only if EUID == 0 and fI is always cleared
and set only if UID == 0 or EUID == 0. Is there a reason for this
behaviour? I think
Hello.
I read the Linux Capabilities FAQ 2.0 and looked at the source in
/usr/src/linux/fs/exec.c. In function prepare_binprm() I see that fE is
always cleared and set only if EUID == 0 and fI is always cleared
and set only if UID == 0 or EUID == 0. Is there a reason for this
behaviour? I think
6 matches
Mail list logo
