Hey guys,

I've made another attempt at hacking up some roaming network profiles.

I wanted a system that could be used on top of the existing network
config in rc.conf.  I saw some profile implementations that were nice,
but they actually replaced the existing INTERFACES/ROUTES setup in
rc.conf.  The goal here was to keep the INTERFACES/ROUTES setup in
place, since one of Arch's most cited features is the easy
"all-in-one-file" configuration in rc.conf.  I didn't want to lose that.

The current setup is intended for laptop users who require multiple
profiles.  It's not as flexible or powerful as the rc.conf network
setup, but it should suffice for most laptop/wireless users (works well
for me, anyway).

Here's a quick setup howto:

- In rc.conf, remove your wireless interfaces from INTERFACES and any
  relevant routes from ROUTES.  Leave "lo" stuff in place.
- Add a NET_PROFILES array to rc.conf and in it, put the name of the
  profile(s) you wish to start at bootup.  Profiles are found in
  /etc/network-profiles.

That's it, pretty much.  When rc.d/network is started, it will look for
a non-empty NET_PROFILES array, and if found, it will use the netcfg
script to activate them.  You can also set NET_PROFILES to "menu" and it
will present a dialog/ncurses menu at bootup where you can pick the
profile you want.  Alternatively, you can pass a NET= value on the
kernel boot line, telling netcfg which profile you wish to start with.

eg, vmlinuz root=/dev/hda3 vga=773 devfs=nomount ro NET=school

A new initscripts package is available in Testing.  If you are a
wireless laptop user, please try it out and give me some feedback.


- J


_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch

Reply via email to