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?
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 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. Greg On Aug 2, 2005, at 9:47 AM, Preston Kutzner wrote: > On Sun, 2005-05-29 at 23:56 -0700, Gregory S. Youngblood wrote: > >> Can anyone else with a failed installation stopping at 20% of the >> EVMS step try with the instructions above and confirm if you are able >> to complete the installation? >> > > I've been trying to get 3.0 (07132005 build) to install on a Dell > OptiPlex GX110. I know it's old hardware, but it's a test-box I > use for > trying new configurations for linux firewalling/routing which, in > general, doesn't need lots of horsepower for what I'm doing. > Unfortunately, install stops at the EVMS screen at 20% like has been > mentioned. > > It's a 600MHz PIII, so it's not *that* out of date and should be > able to > run trustix just fine. I was hoping to be able to use this > release, as > it comes with the 2.6 kernel and, therefore, has some performance > enhancements I would like to take advantage of. So far, however, I'm > forced to look at other options. > > Does anyone else have some information as to why this is happening? > -- > Preston Kutzner | Network Administrator > _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
