Hi Matthew,
Matthew Schalit schrieb:
>
> The only downside I've found to booting using remote packages
> for the LEAF box is that my LEAF box is my router and tinydns
> nameserver. So when it's still trying to boot, the internal
> network can't resolve itself and whatnot. When that happens,
> the remote computer that would be serving up the packages to
> the LEAF box is unhappy because it's default route is down and
> it can't resolve names. The lack of nameservice and default
> route makes the loading of packages painfully slow. But if the
> route's up, the packages load like a bat out of h e double hockey
> sticks.
>
> So the only way I like my LEAF is for it to be self
> sufficient.
>
Maybe in your config, where your LEAF Box is the firewall
to the outside world. But imagine n x LEAF Boxes for a
University Class B network protecting some departments
more or less. The LEAF box is fetching some configs
(typically the partial etc.lrp backup) from a server
in the campus backbone.
With this approach you could get rid of the error prone
Floppy's and the adidas network.
And by the way, it's just a feature, not a must, you could
still use your floppy and I could use my network ;-)
Anyway, I will not boot (vmlinuz, initrd) from the network,
I would prefer to have the configs at a central site
especially from shorwall.lrp and etc.lrp, anything else
does not change frequently and I could spend a new CD
after a few monts.
Regards
Charly
--
Karl Gaissmaier Computing Center,University of Ulm,Germany
Email:[EMAIL PROTECTED] Network Administration
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
