Hi Charly,
I have modified Bering-rc3 to boot exactly that way.
On the floppy there is
- syslinux
- the kernel
- initrd.lrp
- NIC-drivers
- autoboot.lrp (an extension for linuxrc to load packages
from network)
- a config file for autoboot
when booting, linuxrc gets an IP address via dhcp, fetches
two config files from a ftp server (names depend on the
interface IP and the network IP), which define additional
packages to load. Then the packages are loaded. Finally two config
packages are loaded (network IP, interface IP).
Backup is not available yet. I use curl to put modified files
to an upload directory on the ftp server and add them manually
to the config packages.
This way I can share common configurations between all machines,
e.g. ssh root key and also configure each machine individually.
If a package is updated, I only need to replace the .lrp (if
the configs didn't change too much).
But there is absolutely _NO_ documentation about this.
Manfred
Karl Gaissmaier schrieb:
>
> 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
--
Manfred Schuler
E_Mail: mailto:[EMAIL PROTECTED]
-------------------------------------------------------
This sf.net email is sponsored by: Jabber - The world's fastest growing
real-time communications platform! Don't just IM. Build it in!
http://www.jabber.com/osdn/xim
------------------------------------------------------------------------
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
