"Stephan Lampe [ITXP]" <[EMAIL PROTECTED]> writes: > Let 'the one with the power' move them to the sourceforge doc > section for this project.
I do not much care for the SourceForge "doc" interface; I prefer old-fashioned static Web pages. That said, our Web pages are becoming ever more out of date, and we need to do something... So I think I will create a "FAQ" page mostly containing links to messages from the mail archives like this one. (The theory being that this will take less time and will hold us over until I finally snap and rewrite the documentation completely.) Other ideas are welcome. > The info I'm still looking for is how to get certain things working. > > * PXE boot sounds great, I understand the basics, will dig into it > more and will make a guide to contribute. Our instructions are sound. They lack detail because the details depend on your DHCP and TFTP server. > * How to get the unattended system more unattended. In my case I now > what I want to setup (just the OS for starters) but I still have to > answer a lot of questions before it actually starts. How do I get > more control over that stage. Start by reading the rest of the documentation, especially <http://unattended.sourceforge.net/advanced.html>. :-) > * What about a simple txt file on a bootdisk so the unattended > system knows that it is config #101 you want to get on the computer > you are booting from. Would be great if you have to get a lot of > machines up and running asap. (call it a monkeyproof disk, resque > disk, you get the picture I guess). In general, we prefer to keep configuration information on the network and not the boot disk. If you really mean a single default configuration which you want to use for all of your machines, you just put those defaults in Z:\site\unattend.txt. If you want a configuration which varies between machines but is still automatic, you can write a Z:\site\config.pl. The next release will have an example config.pl from Shad which uses a spreadsheet (indexed by MAC address) to obtain settings for the system. > Bear in mind that I'm no programmer, so scripts take a lot work for > me to understand. Well, your options are static configuration and scripted configuration. We do not have any GUI tool, although I gather some of our users have written Web-based interfaces for generating unattend.txt... > I'm a fan of the Bart network bootdisk > http://www.nu2.nu/bootdisk/network/ mainly because it almost always > works. Yeah, Bart's disk is very cool. Maybe we should switch to using it someday. :-) - Pat ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
