On Sat, 2002-04-27 at 12:11, E. Joshua Rigler wrote: > Please forgive me if this is something that has been asked (and > answered) many times before...the redhat-list archive is VERY long, and > since it is private, I can't use google to search it.
for a searchable archive try: http://www.prairienet.org/library/redhat/ > > I just installed RH-7.2. I installed "everything". In the installation > process, I turned off firewalling completely (I'm perfectly happy with > xinetd and ssh for my security needs), and I told it to use DHCP for > network identification, and to NOT activate the network at boot time. > THis is ok exactly what I do on my laptop since I hate waiting for the dhcp timeout when I am not connected > Now my problem: X and Gnome work fine on the first boot. I log in as > root, then activate the network interface via either "rp3" or "ifup > eth0". The network starts up. Now, I can no longer start new X > programs. Certain gnome programs will start, but I think this is > because they are somehow child processes of the already running > desktop. Not only that, but even if I bring the network back down (via > "rp3" or "ifdown eth0"), I can still not use X. If I attempt to restart > X via "ctl-alt-backspace", X won't restart, and I'm left at a text-based > login. I have not seen this behavior. I log in as a regular user and issue ifup eth0 from a command prompt. I have in my /etc/sysconfg/network-scripts/ifcfg-eth0: [bhughes@bretsony network-scripts]$ sudo cat ifcfg-eth0 DEVICE=eth0 BOOTPROTO=dhcp ONBOOT=no TYPE=Ethernet USERCTL=yes PEERDNS=no The userctl=yes lets me as a regular user brin it up and down. THe peerdns entry is probably not required for your setup. I am wondering what would happen if you tried it as a user. log in as a user and su to root via su - and then do: ifup eth0 and tell us what happens. HTH Bret _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
