Hi Philip, thank you very much for your quick response. You are right, I did not define correctly my goal: I want to install on the same drive, just on a different directory so that I can serve the image over the network to other machines, without having to partition. thank you in advance mihai > > >I'm trying to create a new install on a secondary disk mounted on a > >machine which already runs Linux (Fedora Core 3). I've been trying ( > >with no success :( ) to figure out a way to start anaconda from the > >command line. Looks like the it is always called by the kernel, right > >(at/after) boot. > > No, there's no magic in the kernel; it launches /sbin/init as always. > init calls loader, loader calls /usr/sbin/anaconda (usually). See > loader2/loader.c for details. Please then reconsider what you're trying > to accomplish and why - running the installer like this is unusual and > unnecessary. Why not simply use the partitioning and bootloader > kickstart options to install onto the secondary disk? > > > Cheers, > Phil > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/kickstart-list
