-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/03/2009 10:23 AM, Sam Varshavchik wrote: > Andre Robatino writes: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 07/03/2009 04:50 AM, Aaron Konstam wrote: >>> On Thu, 2009-07-02 at 18:48 -0400, Andre Robatino wrote: >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> Hash: SHA1 >>>> >>>> On 07/02/2009 06:06 PM, Frank Cox wrote: >>>>> On Thu, 02 Jul 2009 17:21:13 -0400 >>>>> Andre Robatino wrote: >>>>> >>>>>> is there a walkthrough >>>>>> anywhere on how to make the resulting system usable? >>>>> yum grouplist >>>>> >>>>> Pick the groups you want to install, then >>>>> >>>>> yum groupinstall "name of group" "name of another group" >>>>> >>>>> And so on. >>>> Good, that sounds not too difficult. Of course, it assumes that >>>> networking is working. Does anyone know how this is done after a >>>> text-based install? "ifup eth0" didn't work. >>>> >>> If you are using NetworkManager you turn the internet on by choosing the >>> eth0 option in the nm-applet in the upper right corner of the panel. >>> >>> If you are running network then use system-config-network and configure >>> the eth0 interface, That is thew same as choosing the >>> System->Administration->Network option >>> >>> Find out which you are running by using the : chkconfig --list |grep >>> <program name> >>> >>> >>> Only one should be running. I would expect by default it is NM. >> >> There is no GUI available, only 179 packages are installed. I found >> that adding "BOOTPROTO=dhcp" to ifcfg-eth0 lets me use "service network >> start" to get networking up. Unfortunately, seconds after starting a >> yum transaction, the OS freezes completely and I have to power off. > > Boot with the "forcefsck" option, to refsck all your partitions. Until > you do that, with all those freezes, it's fairly likely that you have > some corruption that is going to keep you from accomplishing anything > useful. > > Then, the next step is "rpm --rebuilddb". This will recover your RPM > database. Until you clean up your partition, and your RPM database, you > won't get very far. > > If after all that you still hang, the are only two remaining > possibilities: failing hardware, or you're hitting a kernel bug. Actually, I was duplicating the text-based install on my VirtualBox in order to be able to walk my father through it remotely. But the hang only seems to happen for me using VB. For him, on the real OS, it works fine. He just edited ifcfg-eth0 to change ONBOOT from no to yes, and added a BOOTPROTO=dhcp line. After "service network restart", his network works fine, so he's busy with yum groupinstall right now. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkpOPFUACgkQ0pavuo9EGO/CEQCdGIhd5VjGSeyFlu7QCfIWRhuB ax8Amwc6Z4j/+4OdW1IOl6K7laMXiRPG =0vck -----END PGP SIGNATURE----- -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
