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.
Matthew
(now back to salmon restoration :)
guitarlynn wrote:
> On Tuesday 27 August 2002 05:46, Karl Gaissmaier wrote:
>
>>Hi Bering developers && users,
>>
>>has someone already thought about to broaden the PKGPATH concept?
>>
>>It would be very helpful to have a bering CD/FD and download
>>some additional packages via tftp|http|scp|...
>
>
> Oxygen and OpenBrick (Bering/Wisp/dist) support tftp'ing of a boot
> image from a remote server.
>
>
>>Most useful, the backup (partial backup) should use this
>>feature too, to save your changes on a centrally administered
>>server. You could then use one Bering CD for your different
>>Firewalls on the campus with one centrally administered
>>config files.
>
>
> Neat idea!
>
>
>>Someone already working on this?
>
>
> I am not aware of anyone working on this at the moment, but
> it is possible that someone is that I am not aware of.
-------------------------------------------------------
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
