Needing Root privleges for everyday tasks and Network failing on boot

ucal · 2010-02-20 19:09:05

Two big problems I guess. I need Root privleges for everything, such as changing the time, and connecting to a network. Granted, this could just be because I'm resorting to connecting with iwconfig in Konsole, as I can't find any sort of GUI to do it in KDE.

The next problem is that Network has recently started failing. I don't know if this is important, because i'm still able to access the internet, but it is slowing down the boot process. Is it safe to remove this Daemon from rc.conf?

loafer · 2010-02-20 19:23:44

I don't understand.

Why do you need to be root to connect to a network? Have you created a user, added it to groups, configured stuff etc.? What daemon? How do you connect?

I don't use KDE but I'm sure it has some sort of GUIs.

How can you access the internet if the network has failed? Do you mean a message during boot?

edit: post your rc.conf

Last edited by loafer (2010-02-20 19:28:31)

ucal · 2010-02-20 19:59:52

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="America/Chicago"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="betty"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
# 
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#

#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
#eth0="dhcp"
wlan0="dhcp"
lo="dhcp"
INTERFACES=(wlan0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
 
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng hal network netfs crond alsa kdm)

As for what's happening. The only way I know how to connect to a network in KDE atm is with the iwconfig command. This requires root permissions, which is odd to me. I can't find any network managers in KDE, but I imagine they would have this same problem, if they use the same command.

Network is the daemon, and it fails on boot. All the other daemons pass (they have done status, network has failed status). I'm still able to connect to the internet though. I don't have any idea what this daemon does.

loafer · 2010-02-20 20:08:12

I don't really know what you are trying to do.

Why did you add lo="dhcp"? What does that do?

Last edited by loafer (2010-02-20 20:08:28)

ucal · 2010-02-20 20:16:55

That was when I was still having network troubles with ethernet. I tried that figuring it might be the ethernet module instead of eth0.

anonymous_user · 2010-02-20 20:21:56

I do believe "lo" is the loopback interface.

loafer · 2010-02-20 20:27:02

lo is the loopback interface. I don't understand why you added that to rc.conf. I don't know kde, but if it does not have any way of managing networks try installing wicd, add wicd to the daemons array in rc.conf and use that.

tomk · 2010-02-20 21:16:33

Configure sudo to allow you to run the required commands as user.

Your network init script is failing because you have set it up to acquire a dhcp ip address on the wlan0 interface, without providing any of the additional details required for a successful wireless connection. There is plenty of information on the various network management options in the wiki.

cookiecaper · 2010-02-20 22:31:54

Yeah, you don't need to use a KDE-specific networking interface if you can't find a suitable one. KDE can run GNOME/GTK applications and vice-versa, so just use wicd or networkmanager.

jkastelic · 2010-02-20 22:38:42

"I need Root privleges for everything, such as changing the time,"

Usually you need to be root to set time (as opposed to Microsoft Windows), but as noted above, you should set up sudo:

http://wiki.archlinux.org/index.php/Sudo

Last edited by jkastelic (2010-02-20 22:39:32)

Arch Linux

#1 2010-02-20 19:09:05

Needing Root privleges for everyday tasks and Network failing on boot

#2 2010-02-20 19:23:44

Re: Needing Root privleges for everyday tasks and Network failing on boot

#3 2010-02-20 19:59:52

Re: Needing Root privleges for everyday tasks and Network failing on boot

#4 2010-02-20 20:08:12

Re: Needing Root privleges for everyday tasks and Network failing on boot

#5 2010-02-20 20:16:55

Re: Needing Root privleges for everyday tasks and Network failing on boot

#6 2010-02-20 20:21:56

Re: Needing Root privleges for everyday tasks and Network failing on boot

#7 2010-02-20 20:27:02

Re: Needing Root privleges for everyday tasks and Network failing on boot

#8 2010-02-20 21:16:33

Re: Needing Root privleges for everyday tasks and Network failing on boot

#9 2010-02-20 22:31:54

Re: Needing Root privleges for everyday tasks and Network failing on boot

#10 2010-02-20 22:38:42

Re: Needing Root privleges for everyday tasks and Network failing on boot

Board footer