[EMAIL PROTECTED] wrote:
>
> On Tue, Mar 27, 2001 at 12:56:44PM -0800, Matthew Schalit scribbled:
> > Apparently, in 3/26 you changed /etc/fstab so that
> > the /boot --> /mnt specification is now commented out
> > and we can no longer type mount /mnt from a prompt
> > and mount the default d
On Tue, Mar 27, 2001 at 12:56:44PM -0800, Matthew Schalit scribbled:
> Apparently, in 3/26 you changed /etc/fstab so that
> the /boot --> /mnt specification is now commented out
> and we can no longer type mount /mnt from a prompt
> and mount the default diskette devicel, while the
> directi
David Douthitt wrote:
>
> Matthew Schalit wrote:
> The new March 2001 release uses the WORKING format, as you described it.
Thanks for that. I found another issue, and
I thought I'd tack it one here, though, because it's
serious, but not critical.
Apparently, in 3/26 you changed /etc/fst
Matthew Schalit wrote:
>
> David Douthitt wrote:
> >
> > Matthew Schalit wrote:
> > I wonder if it could be a problem in splitting of arguments?
> > Perhaps
>
> I have a feeling that it's either a parsing/IFS issue, or
> more likely it's some hard coded issue with the
> ${foo:+bar} format.
David Douthitt wrote:
>
> Matthew Schalit wrote:
> > $ ifconfig eth0 63.194.213.179 netmask 255.255.255.0
> >
> > The output shows the correct IP and correct MASK, but the
> > BROADCAST was unchanged and still reads 63.255.255.255.0
>
> This is MOST interesting. I'll put in support for IF#_
David Douthitt wrote:
>
> Matthew Schalit wrote:
>
> > I tried this on the Oxygen machine in my own test script and
> > it works my way but fails David's way. Set -x didn't show
> > any difference in the command that was to be run.
>
> I wonder if it could be a problem in splitting of argum
Matthew Schalit wrote:
> Yes I see it now that you quoted the offending command.
> The syntax is crap :)
>
> Wrong
> -
> ifconfig $IFNAME $IPADDR ${MASK:+netmask $MASK} ${ETHER:+hw $ETHER}
>${BROADCAST:+broadcast $BROADCAST} $STATE
>
> Correct
> --
> ifconfig $IFNAME $IPADDR ${
Matthew Schalit wrote:
> So I read your followup that I quoted above, and you mention
> that ifconfig should get it right, "if you specify the nemask
> and the IP address." I tried that and is doesn't use those
> two to calculate the broadcast.
>
> $ ifconfig eth0 63.194.213.179 netmask 255.2
On Sun, 25 Mar 2001, Matthew Schalit wrote:
> So I read your followup that I quoted above, and you mention
> that ifconfig should get it right, "if you specify the nemask
> and the IP address." I tried that and is doesn't use those
> two to calculate the broadcast.
>
> $ ifconfig eth0 63.194.
Mark Seiden wrote:
>
> it is driving me crazy why a seemingly identical command
> is not correctly executed in these two cases. does anyone
> understand the problem?
Yes I see it now that you quoted the offending command.
The syntax is crap :)
Wrong
-
ifconfig $IFNAME $IPADDR ${MASK
it is driving me crazy why a seemingly identical command
is not correctly executed in these two cases. does anyone
understand the problem?
i have no problem with the gateway setting. perhaps you inadvertantly
munged or removed the GATEWAY_IFNAME definition, which is required.
arguably it should
George Metz wrote:
>
> If you specify the netmask and the IP address,
> it will go to the first valid range that includes the netmask and the
> given IP, then figure the broadcast address from there.
>
> Are you seeing the broadcast address being set incorrectly even with the
> netmask correctl
On Sat, 24 Mar 2001, Mark Seiden wrote:
> i had this problem also.
>
> i still don't understand why it's happening.
>
> you might notice that i've added an IF_BROADCAST variable as
> well to network.conf...
>
> i dare say that with a class c netmask and a class a address ifconfig
> will get yo
Mark Seiden wrote:
>
> i had this problem also.
>
> i still don't understand why it's happening.
>
> you might notice that i've added an IF_BROADCAST variable as
> well to network.conf...
>
> i dare say that with a class c netmask and a class a address ifconfig
> will get your broadcast addres
i had this problem also.
i still don't understand why it's happening.
you might notice that i've added an IF_BROADCAST variable as
well to network.conf...
i dare say that with a class c netmask and a class a address ifconfig
will get your broadcast address wrong, also.
here's a bit of code tha
> network: bringing up interface eth0 on 63.194.213.179 with
netmask
255.255.255.0
> netmask 255.255.255.0: Unknown host
> Usage:
> ifconfig [-a] [-i] [-v] .
I am also getting this error message (but with netmask 255.255.255.248).
Any chance of getting
16 matches
Mail list logo
