(Aug 02 2005 10:14) Gregory S. Youngblood wrote: > Given the issue that evms seems to have on older hardware -- or at > least this scan -- is there any way of making a manual process that > doesn't use evms? Like fdisk or "advanced" options on other > installers, so you can do exactly what you want, how you want it; > and, there is a backup when something goes wrong with the automated > detection part of evms?
Some guys at the forum has found using fdisk to delete the partitions manually helps. It seems to be consistant, and since we also know the cause (not hardware but existing partitions) we are close to a solution in viper/evms as well. I'll look into adding a fdisk option as well. > > I actually ended up having to get some newer hardware, thereby > solving the problem for me. Otherwise, I'd be limited to TSL 2.2. > When I get the other hardware working again. I guess the newer hardware either was completely new or at least did not have troublesome partitions? > I have another idea on getting 3.0 on there, but it's not without > risk, requires two hard drives or two partitions, and requires having > at least one system where the install of TSL 3.0 completes. > Basically, an OS transplant. I would test partitioning with fdisk. Simply change to tty2 (Alt-F2) and run fdisk _before_ entering the installer partition tool. c -- Christian H. Toldnes Trustix Developer _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
