You are not logged in.
Just ran a system update and had the message about the new rc.conf.pacnew file. Looking at it, i'm not sure i understand the change. I use a wireless connection only using netcfg.
This is my current network settings
# 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
#
WIRELESS_INTERFACE="wlan0"
wlan0="dhcp"
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
#eth0="dhcp"
#INTERFACES=(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)
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"
# 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=( mynetwork )
This is the new rc.conf file for network settings, this is where i am not sure what i need to do next ...
# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
#
# Wired network setup
# - interface: name of device (required)
# - address: IP address (leave blank for DHCP)
# - netmask: subnet mask (ignored for DHCP)
# - gateway: default route (ignored for DHCP)
#
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# gateway=192.168.0.1
#
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=
interface=
address=
netmask=
gateway=
So i am not sure how to set the new rc.conf file. Any help please ?
Many thanks
Last edited by whitetimer (2011-06-08 17:53:10)
Offline
don't drink unwashed fruit juice.
i never make predictions, especially about the future.
Offline
Yes i read that, but still did not understand the change ... Never mind i will stick with the old file
Offline
Never mind i will stick with the old file
I hope you understand that it won't work.
Last edited by karol (2011-06-08 19:29:48)
Offline
Yes but not sure how i need to change to the new rc.conf file
I have changed the new rc.conf file to
# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
#
# Wired network setup
# - interface: name of device (required)
# - address: IP address (leave blank for DHCP)
# - netmask: subnet mask (ignored for DHCP)
# - gateway: default route (ignored for DHCP)
#
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# gateway=192.168.0.1
#
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=
interface=wlan0
address=
netmask=
gateway=
and kept
NETWORKS=( mynetwork )
# -----------------------------------------------------------------------
# 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
#
# If something other takes care of your hardware clock (ntpd, dual-boot...)
# you should disable 'hwclock' here.
#
DAEMONS=(ntpd syslog-ng dbus network net-profiles netfs crond alsa cups samba)
Is that correct ...
Last edited by whitetimer (2011-06-08 19:50:20)
Offline
Yes, also add the banged out (!module1) modules to /etc/modprobe.d/modprobe.conf like "blacklist module1" if you had any in your rc.conf.
Offline
whitetimer wrote:Never mind i will stick with the old file
I hope you understand that it won't work.
Why wouldn't it? As per the http://www.archlinux.org/news/deprecation-of-net-tools/
The old functionality is still preserved for those preferring to stay with that, but do not expect it to gain new features.
Although future changes may or may not break things.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Why wouldn't it? As per the http://www.archlinux.org/news/deprecation-of-net-tools/
Yes, but blacklisting modules with rc.conf doesn't work anymore.
github - tweets
avatar: The Oathmeal
Offline
karol wrote:whitetimer wrote:Never mind i will stick with the old file
I hope you understand that it won't work.
Why wouldn't it? As per the http://www.archlinux.org/news/deprecation-of-net-tools/
The old functionality is still preserved for those preferring to stay with that, but do not expect it to gain new features.
Although future changes may or may not break things.
What about "only supports one wired network device"? Isn't wlan a wireless interface?
Offline
op is already using netcfg for his wireless connection. He is not using net-tools directly to handle the wireless connection although its listed in his rc.conf, the NETWORKS array only has reference to his netcfg profile.
I am not saying that he shouldn't update the rc.conf file, all I am saying is that it won't break anything in the immediate future as long as you aren't handling the wireless connection via net-tools.
I, myself, have been too busy/lazy to move over to the new rc.conf file and everything still works for me. That reminds me to actually search for all the *.pacnew files in my system and update them
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
I'll post this here as it's the same problem - I don't understand the new rc.conf syntax. If it turns out to be different, I'll open a new thread - but can do anyway if that's preferred.
Since the net-tools update, my netcfg is no longer connecting wireless at start-up and I did think it was because I hadn't switched to the new setup. So I did and it still doesn't work. Connects no problem manually. My rc.conf looks like the OP's new one but with eth0 in the interface line, as the comments talk about that being for wired and I sometimes have wired.
I assume I've misunderstood how it should be setup?
#
# /etc/rc.conf - Main Configuration for Arch Linux
#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# Note: Using "localtime" is discouraged.
# 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
# VERBOSE: Verbose level (from 1 to 8). man 3 syslog for level info
#
LOCALE="en_GB.utf8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/London"
KEYMAP="uk"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
VERBOSE="3"
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MODULES: Modules to load at boot-up. See "man modprobe.conf" for blacklisting.
#
MODULES=(hp-wmi acpi_cpufreq cpufreq_ondemand rfkill kvm kvm-intel lp parport parport_pc loop)
# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30
# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"
# Scan for BTRFS volumes at startup
USEBTRFS="no"
# 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="<myhostname>"
# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
#
# Wired network setup
# - interface: name of device (required)
# - address: IP address (leave blank for DHCP)
# - netmask: subnet mask (ignored for DHCP)
# - gateway: default route (ignored for DHCP)
#
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# gateway=192.168.0.1
#
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=
interface=eth0
address=
netmask=
gateway=
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"
# 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=(workwired homewireless)
# -----------------------------------------------------------------------
# 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 sensors @laptop-mode @net-auto-wireless @net-auto-wired @netfs @samba @cups @crond @alsa @adsuck)
Also I notice that netcfg still requires net-tools, which I guess will change at some time?
Last edited by skanky (2011-06-09 08:36:49)
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
Hmmm I seem to be the lucky one then ?
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
I have a similar problem, my network does not start at boot, but does ok when i start it manually in the terminal
Offline
ok, so module blacklisting is now made by /etc/modprobe.d (can I put there file with any name as long as it end by .conf?)
but what about loading modules? is it made by rc.conf or modprobe.d?
Offline
It's made in rc.conf.
Offline
Anyone got Wicd working with the new rc.conf syntax?
Offline
Why would the new rc.conf affect wicd?
Offline
I setup my interface (copying the example for DHCP):
interface=eth0
address=
netmask=
gateway=
and added wicd to daemons, but dhcpcd is not started. I have to manually launch it. Using "network" instead of wicd works fine.
Offline
Anyone got Wicd working with the new rc.conf syntax?
wicd apparently needs net-tools, which I uninstalled upon the initscript update and wicd promptly broke. Re-installing net-tools and all was fine with wicd
Offline
Thank you. I will go report a bug report then.
Offline
wicd apparently needs net-tools, which I uninstalled upon the initscript update and wicd promptly broke. Re-installing net-tools and all was fine with wicd
That sounds like a bug: it's not listed in wicd's dependencies
http://projects.archlinux.org/svntogit/ … k/PKGBUILD
# edit: too slow...
Offline
This may be the wrong place to post this but after I've updated my freshly installed ArchLinux yesterday (not even a week old and nothing more than the basics plus xorg and subtle/scrotwm installed), the (wired) internet connection is no longer working. Or more precisely, it's not working properly. The connection is very unstable and seems to get constantly lost. I can't even successfully do pacman -Syy or -Syu.
I use DHCP and it reports that the link is up and working. My network card (onboard Realtek) is recognized and the module properly loaded. Restarting the network (/etc/rc.d/network restart) is working fine too. But the connection get's lost again almost immediately anyway.
So far I have tried the following without luck:
* downgraded the kernel
* downgraded udev
* reverted back to the old rc.conf
* put the network card module in the MODULES array in rc.conf
I've of course checked pacman's pkg cache but couldn't find any other packages that have been updated and might cause this problem.
Tonight I will re-install Arch again. Hopefully this will solve the problem. Just wanted to add this in case someone is facing similar problems.
Offline
Just updated my laptop (EeePC 901 + wicd): moved blacklist modules into /etc/modprobe.d/blacklist.conf and changed over to the new network settings in /etc/rc.conf. I already had net-tools installed, so rebooted, held my breath and BAM!
+ Shaved at least 20% off my boot time
+ Network came up straight away
+ PROFIT!
Thanks to the devs for the smooth transition
Offline
Just updated my laptop (EeePC 901 + wicd): moved blacklist modules into /etc/modprobe.d/blacklist.conf and changed over to the new network settings in /etc/rc.conf. I already had net-tools installed, so rebooted, held my breath and BAM!
+ Shaved at least 20% off my boot time
+ Network came up straight away
+ PROFIT!Thanks to the devs for the smooth transition
Can you show your new network section from rc.config, please?
I still have to manually start both wired & wireless with netcfg.
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
There is not much to it...
interface=eth0
address=
netmask=
gateway=
and in daemons I have @wicd
Offline