On Wed, 18 Aug 1999, root wrote:
> Lars Marowsky-Bree wrote:
> > On 1999-08-18T11:01:10,
> > root <[EMAIL PROTECTED]> said:
> > > > > What do you think cisco's et al run? Most run a Unix like FreeBSD, and
> > > > > now some Linux.
> > > > eh? I thought they ran cisco's IOS..
> > > That is a front end for the underlying routing core. (Kernel, etc)
> > IOS is the kernel too.
> It's a shell. I could compile a shell into linux quite easily.
> Instead we just let it call /sbin/init (or /bin/sh or others)
> when it finishes up main(). That way is just better.
IOS(tm) is the name for the software that runs on Cisco(tm) routers,
switches, and other assorted products. It comprises a user interface,
routing components, and a whole host of other bits and pieces.
> >A Cisco does not run Unix.
> And you know they did not start off with a unix kernel how?
Some of the ideas are based on Unix. Some on TOPS/20 (telnet /source).
Some are Cisco inventions.
> > > I could emulate IOS with LRP, but WTF in their right mind would want to?
> > Because it works. And has the best CLI in existance.
> It doesn't come near the power, flexablity, and widely known bourne
> shell.
> When you can access a cisco via ssh, and can do for loops from IOS let
> me know.
> : >A
B
The CLI for IOS is designed to enable you to configure a Cisco(tm)
router. Why do I want to do loops? SSH would be useful, but that's a
daemon problem, not a CLI one. Note that to backup the entire
configuration of a router, I type:
write net
at the enable prompt. That's powerful. That's what I need to do _to
configure a router_.
If I'm smart, I actually execute this by doing a few SNMP Set
operations, from a cron job.
Key point: A router is not a workstation. The software on a router is
not designed to run a workstation. It's designed to run a router. And it
does (IMHO) a damn fine job of it.
Colin. (who's now going to try and get back on topic........)
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
