This might be a bit offtopic, so please forgive me. This command was
executed on a linux-2.0.33 kernel (it's not a fault in the kernel):
rlis6:/root # ping 192.168.33.36
PING 192.168.33.36 (192.168.33.36): 56 data bytes
64 bytes from 192.168.33.36: icmp_seq=0 ttl=32 time=0.7 ms
64 bytes from 192.168.33.36: icmp_seq=1 ttl=32 time=0.6 ms
Now watch ... please notice the change in last octet:
rlis6:/root # ping 192.168.33.036
PING 192.168.33.036 (192.168.33.30): 56 data bytes
^^^^^^^^^^^^^
64 bytes from 192.168.33.30: icmp_seq=0 ttl=60 time=2.6 ms
64 bytes from 192.168.33.30: icmp_seq=1 ttl=60 time=1.5 ms
It's the same on a Windows and a HP-UX box. I guess it's libc or the
shell which is to blame, but why does it incorrectly parse 036 as 30?
I know that 036 in octal is 30, but I didn't specify a backslash.
Is there something I should know?
Best regards,
Brian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu