[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
I vote for all aspects of network interfaces; that's what I deal with
most in my
language and keyboard would probably be important for those not
under the defaults...
after that, it occurs to me some form of rc.local.kickstart would be
single place where a whole
lot of other stuff could be done.
Now, how would you deploy such a file? I can see two alternatives: 1)
next to filesys.gz
in the .iso (I put stuff in the iso by unpacking it, adding the stuff
in the unpacked
directory structure, then reassembling wit mkisofs); 2) from a known
tftp or bootp server (?)
On Feb 2, 10:20 pm, Douglas Jerome <[email protected]> wrote:
> Hi all,
> I solicit responses.
> I don't know Red Hat's kick start, but I think I get
> the idea: At the end of the boot process, look at a
> boot parameter to get a configuration file name. Get
> the file and read its content; use this configuration
> data to guide an installation process.
> If I make this for ttylinux, what information is
> required to be in the file? I prefer that ttylinux not
> do the target disk(s)' partitioning, mostly because I
> don't want to add sfdisk and take the time to learn/test
> an automatic partitioning script, but I might be
> The configuration file needs to describe what?
> => describe target drive partitions:
> UUID?, file system type (ext2, etc.), mount point
> => network interfaces to bring up for the installed system?
> => ...?