On Tue, Jan 13, 2004 at 10:51:19AM -0500, Rohit Kumar Mehta wrote: > > Hi guys, I know googling this topic shows a lot of conversation, but I > am still sketchy on a working > procedure, and I have already burned two bad CDs :( > > I am running Debian stable and using the systemimager packages from the > Debian sites version 2.0.1. > Everything is working great. I have poured my energy into a great image > for a brand new shiny 16 computer lab. > However, the computers have gigabit cards only in them, and the > autoinstalldiskette does nto work. > > So I made a new kernel and modules and used mkinitrd-cd and replaced > the files in /usr/share/systemimager/i386-boot
mkautoinstallcd is the proper comand to use - it may have been called makeautoinstallcd back then. > (kernel and initrd.gz) and wound up with a bootable linux CD! Woo! > However, it didn't go into the awesome > non-interactive hands free seamless install I have come to know and love. well, then what *did* it do? > The documentation seems to refer to tftpboot, that's just for netbooting > and mkinitrd mkinitrd? you should never use that in this process. > and various > other things are very confusing. I don't > want to go through more CDs with dumb trial and error. Can anyone tell > me what I need to learn to do this right? do you have a cdrw you can use? if so, i'd suggest going back to the original kernel/initrd & creating a cd w/ mkautoinstallcd, then try doing the same w/ your binaries. ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
