IP Alias / SIOCSIFADDR & SIOCSIFFLAGS: No such device

[Larry James]

I didn't have the following problem until I upgraded from
Slackware version 3.3 to verion 7 build 2.2.13.
When trying to setup an IP alias on an ethernet card using the
command:

ifconfig eth0:1 192.168.0.12

I get the following error:

SIOCSIFADDR: No such device
SIOCSIFFLAGS: No such device

I have the ip alias and the ip network compiled in my system, just
as I had it in version 3 build 2.0.30 of Slackware.
Can someone tell me what else might be causing this error message
and the lack of being able to configure multiple IP addresses on one
card.
Thanks in advance for any suggestions or comments.

-- L. James

--
---------------------------
Larry James
lja...@apollo3.com
http://www.apollo3.com/~ljames

Sent via Deja.com http://www.deja.com/
Before you buy.

[Jay D. Ribak]

Have you compiled your kernel with IP Aliasing support built in? As
of the 2.2.x series of kernels it is no longer included by default.

Larry James <lja...@apollo3.com> wrote in message
news:8aj5as$n4$1...@nnrp1.deja.com...

[Larry James]

In article <scqero...@news.supernews.com>,

"Jay D. Ribak" <ribak@inetsolve . com> wrote:
> Have you compiled your kernel with IP Aliasing support built in? As
> of the 2.2.x series of kernels it is no longer included by default.
>

Thanks Jay. With more detail study, I find that there's a problem
with the size of the Kernel. I made one change, compiled it, and lilo
gives the error message:
Kernel /vmlinux is too big
Is there some special command to use to srink the file? I notice
that the install program creates a vmlinuz file. I know it's
compressed. I used the compress command to compress the vmlinux then
renamed it to vmlinuz and still got the same error message that the
file is too big.
After recompiling what are the special steps to get /sbin/lilo to
work?

[bk...@cornell.edu]

Larry James <lja...@apollo3.com> wrote:
> Thanks Jay. With more detail study, I find that there's a problem
> with the size of the Kernel. I made one change, compiled it, and lilo
> gives the error message:
> Kernel /vmlinux is too big
> Is there some special command to use to srink the file? I notice
> that the install program creates a vmlinuz file. I know it's
> compressed. I used the compress command to compress the vmlinux then
> renamed it to vmlinuz and still got the same error message that the
> file is too big.
> After recompiling what are the special steps to get /sbin/lilo to
> work?

probably not a good idea to use compress. when you make the kernel, use
make zImage
or
make bzImage
then copy /usr/src/linux/arch/i386/boot/zImage (or bzImage) to where you put
your kernel. it doesn't have to be named vmlinuz, but that's often a good
choice. edit lilo.conf to use the new kernel file and run /sbin/lilo.

brian

[Allen Wong]

Larry James wrote:
>
> Thanks Jay. With more detail study, I find that there's a problem
> with the size of the Kernel. I made one change, compiled it, and lilo
> gives the error message:
> Kernel /vmlinux is too big
> Is there some special command to use to srink the file? I notice
> that the install program creates a vmlinuz file. I know it's
> compressed. I used the compress command to compress the vmlinux then
> renamed it to vmlinuz and still got the same error message that the
> file is too big.

The 2.2.x kernels are getting too big. Instead of "make zImage", try
"make bzImage". HTH

Allen
--
Linux: If you're not careful, you might actually learn something.
3:00pm up 6 days, 7:56, 1 user, load average: 1.02, 1.01, 1.00

[Brian]

Hi Larry:

Try;

make bzlilo; make modules; make modules_install <enter>

Then cd to / and move your System.map to /boot.

Best regards,

Brian

Larry James wrote in message <8ajqa7$hij$1...@nnrp1.deja.com>...

>In article <scqero...@news.supernews.com>,
>"Jay D. Ribak" <ribak@inetsolve . com> wrote:
>> Have you compiled your kernel with IP Aliasing support built in? As
>> of the 2.2.x series of kernels it is no longer included by default.
>>

>Thanks Jay. With more detail study, I find that there's a problem
>with the size of the Kernel. I made one change, compiled it, and lilo
>gives the error message:
>Kernel /vmlinux is too big
>Is there some special command to use to srink the file? I notice
>that the install program creates a vmlinuz file. I know it's
>compressed. I used the compress command to compress the vmlinux then
>renamed it to vmlinuz and still got the same error message that the
>file is too big.

>After recompiling what are the special steps to get /sbin/lilo to
>work?