Good day everyone, i think it is a fantastic idea. I am a system's administrator supporting both Windows and Linux/BSD machines, and as Mr Weigand mentioned, i find myself in the re-installation task quite often. On Windows thats a cinch thanks to Sysprep, something similar on/using Arch would be perfect.
Mr Weigand: I'm very interested in what you implemented there, is there any documentation on it, or even a short-list of steps thats on the Wiki or anywhere else? I would be keen to evaluate it both for my purposes, and in general use. thanks, - viv Volker Wiegand wrote: > Hello, > > I am currently using Arch Linux 0.7.2 on a server in "production" > (providing file, print, internet, firewall, etc. services) for my > family. It works very well - thank you for the good work. My family is > as picky about keeping SLAs (Service Level Agreeements) as my employer, > Deutsche Bahn, could ever be :-) > > For security reasons I usually try to stay current with servers like > Apache, Samba, etc. plus the Kernel and libraries. And I often do > re-installations. Arch Linux is a perfect match for me, and here is my > first question. Is the latest version based on Kernel 2.6.17 regarded > production quality? BTW, I consider Arch Linux 0.7.2 absolutely > "production quality", having been a long term SuSE user (and manager :-) > > My second question is about the Arch Linux CD. Currently I always burn > my own CD, based on the original image, with just one minor change: I > add a (default) entry to the ISOLINUX menu, booting from hard disk (via > "LOCALBOOT -1"). It's the same thing Windows or SuSE do. I have the > commands in /arch/setup scripted, and also the installation and > configuration of the entire system (actually, it is a set of XML files > and an entire configuration system translating these files into all > various config files). In the end, all I have to do is boot the CD, run > the script from floppy (or USB stick), and go for a coffee. The script > will do fdisk, grub, pacman.static, prepare the entire system, reboot, > install users, crontabs, printers, shares, and anything else. With an > ISOLINUX default of "LOCALBOOT", this lets me do a completely unattended > installation. So, here is my question: Is there a chance to have the > LOCALBOOT default included in the standard CD? Or is it against Arch > Linux' philosophy? > > Many thanks > Volker Wiegand > > > _______________________________________________ > arch mailing list > [email protected] > http://www.archlinux.org/mailman/listinfo/arch > _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
