You are not logged in.
Pages: 1
Hello Everyone,
I today did a clean install of Arch but im getting a error while boot up.Its with the "dbus" daemon.The error im getting is as follows:-
[root@Rajiv-Nair rajiv]# /etc/rc.d/dbus restart
:: Stopping D-BUS system messagebus [DONE]
:: Starting D-BUS system messagebus [BUSY]
Unknown group "network" in message bus configuration file
[DONE]
This is my /etc/rc.conf file:-
#
# /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"
# 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/unimaps
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
TIMEZONE="Asia/Calcutta"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"#
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=()
#
# Modules to load at boot-up (in this order)
# - prefix a module with a ! to blacklist it
#
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="Rajiv-Nair"
#
# 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
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
lo="lo 127.0.0.1"
eth0="eth0 169.254.149.178 netmask 255.255.0.0 broadcast
169.254.255.255"
INTERFACES=(lo eth0)
#
# 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-profiles
#
#NET_PROFILES=(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 acpid dbus !hotplug !pcmcia network netfs crond
portmap fam hal gdm)# End of file
BTW im using Intel Chipset and had to edit out my fstab and /boot/grub/menu.lst for arch to work,i dont know whether its because of that or something else.
Thanks in Advance,
Rajiv Nair
Offline
Does the group "network" exist in /etc/group?
Unthinking respect for authority is the greatest enemy of truth.
-Albert Einstein
Offline
Shouldn't 'network' is before 'dbus' in the module loading order?
Offline
Module order? You mean DAEMONS order? No, I have dbus right after syslog-ng at second position, doesn't require network stuff.
1000
Offline
Module order? You mean DAEMONS order?
Yes, of course. My apologies.
Offline
No i dont have "network" as a group in /etc/group and rearranging daemons doesnt help,ive tried it out and the message comes anyways.
Offline
No i dont have "network" as a group in /etc/group
Update the filesystem package:
pacman -S filesystem
Offline
Thnx Snowman,tht worked,but...
Here's what i have come to see tht when i did a clean install yesterday and upgraded to latest packages,certain files which had "glibc" as their dependencies got installed before glibc and were putting out some error which i'd overlooked.Today i again did a clean install but before upgrading i did a force install of "glibc" and i figured tht all the problems i had earlier were solved.
I am using a Intel Chipset ,so i dont know whether its a hardware specific problem related to kernel 2.6.19 but IMO tht priority thingy of glibc needs to be taken care about.
Offline
Pages: 1