Any Trixbox install guide that I've read has specifically stated that you must hit Enter to perform the default install. In the event that the default install will not boot for you, there are guides that detail what options you must select during a customized install, and how to unpack and run the Trixbox component installer after installation. This isn't poor design... It's a best effort attempt at automation. The Trixbox devs setup a system that should be able to load and install under most circumstances. If it doesn't, there's the fallback of installing CentOS normally and installing the Trixbox components afterwards. Not having a fallback would be a poor design.
Alex -----Original Message----- From: Giles Orr [mailto:[EMAIL PROTECTED] Sent: Saturday, September 23, 2006 11:37 AM To: [email protected] Subject: [on-asterisk] Trixbox v1.2 install report I'm very new to Asterisk and I've never used Trixbox before - on the other hand, I've been using Linux since 1994. I saw the new Trixbox v1.2 and decided it was time to try it. I downloaded and burned the ISO to CD. I deliberately did a minimal install of Debian on a partition to see if I could avoid having it wiped (I've been given to understand that Trixbox wipes the entire HD). Booting the CD there was a big warning that your HD would be completely wiped - at least they make it clear. I chose to use boot options "i586 nofb" instead of just hitting enter because I have a Celeron in the machine and an LCD screen that often disagrees with FB. One of the options that came up shortly was to test the install media. Good idea. "Checking CentOS v4 DVD." This is a CD, not a DVD. The check failed, which is kind of confusing because I have no idea if I have a bad burn or if they failed to change this particular script. I installed from the disk anyway, and got a lovely CentOS graphical install that allowed me to use DiskDruid to partition - it didn't wipe the HD. On reboot, I find myself even more confused because I now have what appears to be a shabby CentOS install with no Asterisk, no FreePBX, no nothing that makes any sense. As it turns out, I stepped off the official Trixbox install path somewhere along the line - it would seem that you HAVE to hit Enter when the GRUB boot menu on the CD comes up to have your HD wiped and Trixbox installed. This is incredibly poor design on their part: they left all the CentOS GRUB boot options visible and active, and didn't modify them. I'm pretty thoroughly unimpressed with their preparation of their install disk. As I've been writing the new Trixbox install has rebooted a couple times and is installing and tweaking its way to happiness. I haven't played with it much yet, but I give them points for creating a computer that has network connectivity but is entirely invisible to other computers on the network. I have to admit that part of my reason for posting here is that I'm leary of posting this as a bug in a Trixbox forum and getting yelled at, but I'm also really pissed. And kind of hoping that this will help someone else on this list ... At the moment I'm working on resizing the Trixbox install so I can use the rest of the space on the drive. I thought "I'll just fire up parted ..." But it's not that easy. I get the infamous "Error: Filesystem has incompatible feature enabled," and this is proving difficult to get around. *sigh* -- Giles http://www.gilesorr.com/ [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
