FC3 eth0 question

[dishawjp]

Hi All,

I installed FC3 today and am working on getting it configured. I did just run into one slight issue which I could probably solve if I had consumed fewer "configuration beers" or were a bit less senile.

Anyway, to get to the point... I like to set my ethernet card up so that users can bring it up or down as needed. In the past, I have (as far as I can remember anyway) just set my ifcfg-eth0 script to include the line "USRCTL=yes" and "ONBOOT=no"

I have done that and get a message telling me that users cannot control the device. I can use the "neat" utility and bring the interface up or down, but have used the simple aliases "net" and "nonet" for this in the past. Below I will post my ifcfg-eth0 and the results of trying to bring it up from the command line:

Code: Select all

[dishawjp@localhost ~]$ more /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=no
TYPE=Ethernet
USRCTL=yes
[dishawjp@localhost ~]$ net
Users cannot control this device.
[dishawjp@localhost ~]$


I still have a lot more setup to do, but would appreciate any input on this.

Otherwise, I am happy with FC3 so far. It is a bit different, but not too different to get along with. My tune on that may change once I try to get my nVIDIA 3D driver installed though. I've read about a lot of people having difficulties there.

As always, thanks in advance for any pointers,

Jim

[Void Main]

Anyway, to get to the point... I like to set my ethernet card up so that users can bring it up or down as needed. In the past, I have (as far as I can remember anyway) just set my ifcfg-eth0 script to include the line "USRCTL=yes" and "ONBOOT=no"

Try "USERCTL=yes" (or system-config-network and check the User control box). It works for me.

Otherwise, I am happy with FC3 so far. It is a bit different, but not too different to get along with. My tune on that may change once I try to get my nVIDIA 3D driver installed though. I've read about a lot of people having difficulties there.

I assume it uses the same nVidia driver that I install for my Geforce4. It was a breeze to install but immediately after installing you have to copy the nvidia* device files to the udev conf directory so the driver will load on reboot:

# cp -a /dev/nvidia* /etc/udev/devices

I mention it in the FC3 sticky thread.

[dishawjp]

Hi Voidmain,

I assume it uses the same nVidia driver that I install for my Geforce4. It was a breeze to install but immediately after installing you have to copy the nvidia* device files to the udev conf directory so the driver will load on reboot:

# cp -a /dev/nvidia* /etc/udev/devices

I mention it in the FC3 sticky thread.

Well, it wasn't quite that simple for me, but I finally did get nVIDIA up and running. I'll post this here just in case I can save someone else some of the grief I went through. In addition to the normal running of the NVIDIA script and editing the /etc/X11/xorg.conf file and the "cp -a /dev/nvidia* /etc/udev/devices" I had another two steps to go through. They were (fortunately) documented in the

/usr/share/doc/NVIDIA_GLX-1.0/README file nVIDIA installed.

The first step was to edit my /etc/security/console.perms file to remove two references to <dri>.

Then I had to:
# chmod 0666 /dev/nvidia*

and then:
# chown root /dev/nvidia*

I was a bit worried for a while, especially when after my first edit of console.perms (I had only removed one reference to <dri>) and I could only log in as root. There was a pam security error on boot up and I couldn't log in as a normal user. The README said that only the line beginning with <dri> had to be removed, but that caused my system much unhappiness. Further down they said that there were reports that all references to <dri> needed to be removed, but that they hadn't verified that. But anyway, removing the second reference (line 79 for anyone else who runs into this) fixed that. Then it was just a matter of resetting the permissions and I was good to go.

HTH,

Jim Dishaw

[Void Main]

Hmmm, I didn't have to remove the <dri> lines from console.perms but I think I might now why. I'll bet you start up in runlevel 3 and then do a startx when you want to start an X session don't you? I run in runlevel 5 on startup which means no user is logged on when X starts. I probably should remove my <dri> lines though or one day I'll start in runlevel 3 and wonder why X doesn't start. :)

I didn't add the "chmod/chown" steps because my files were already owned by root and had proper permissions. Thanks for posting this because someone will surely have this problem in the future.

On a side note, did the USERCTL (with the E) fix your network interface/user issue?

[dishawjp]

Hi Voidmain,

I'll bet you start up in runlevel 3 and then do a startx when you want to start an X session don't you? I run in runlevel 5 on startup which means no user is logged on when X starts

You're right, as usual. I do set my inittab to start in runlevel 3 and only startx if and when I want to. It probably goes back to my old DOS/Windows days where it made things easier if the GUI was hosed. Even with Win98 I still had the "BOOTGUI=NO" or whatever it was to prevent having to do an F8 boot when Windows hosed itself.

On a side note, did the USERCTL (with the E) fix your network interface/user issue?

Well, I took the lazy man's route and set it with the "system-config network" command which worked fine.

I'm just about finished configuring FC3. I mounted my FC 2 partition and got all my files copied over to FC3, edited my /etc/sysconfig/network and /etc/hosts files and got my hostname set. The modem and ethernet card are configured, but I still have to set up minicom. I had some issued with my floppy drive. It mounts in /media/floppy! That took me a while to figure out.

I do have one real newbie question here. When I mounted my FC2 partition, I used the command:

mount /dev/hdd2 /mnt

and everything was cool. But I couldn't umount it. What would the commmand be to unmount a hard drive partition like that? (Told you it was a newbie question)

Thanks again for all the help!

Jim Dishaw

[Void Main]

I do have one real newbie question here. When I mounted my FC2 partition, I used the command:

mount /dev/hdd2 /mnt

and everything was cool. But I couldn't umount it. What would the commmand be to unmount a hard drive partition like that? (Told you it was a newbie question)

# umount /mnt

or

# umount /dev/hdd2

Notice it's not "un" but "u" in front of the "mount". Saved a whole 1 letter there on that 6 letter command! :) Of course like always no files can be open on that partition or you will not be able to unmount it (even being cd'd into a directory on the partition is enough to not be able to unmount it).

[dishawjp]

Voidmain,

# umount /mnt

or

# umount /dev/hdd2

Thanks. I don't know what the heck I was doing wrong last night... I thought that I was issuing the "umount /mnt" command correctly, but was getting error messages like "not in mtab or in fstab" or similar things. I just sat down here to post what I was doing and show the error messages I was getting, but everything was working! Last night sometimes it said it was "busy" but I know that I was not in that directory and didn't have any files from it open. I didn't try "umount /dev/hdd2" though. That might have worked. But anyway, now it's working perfecly. I guess it's a good thing that I don't have to earn a living from my Linux knowledge.

Thanks again, and if I can reproduce the problem, I may post it again. More likely I was just doing something stupid. ( I specialize in stupid)

Jim Dishaw

[Void Main]

I specialize in stupid

Yes but can you hide Easter eggs and then not be able to find them? I specialize in that.