I finally got time to take a look at this and unless I have misunderstood the way it works I'm pretty shocked!
The network-profiles system is woefully inefficient when it comes to wireless setup. I connect to 4 different wifi LANs with 2 different devices - that would require EIGHT separate profiles! I know that people always favour their own approach but I think it is worth mentioning mine again. I used a call to a case statement in a wireless config file to manage the various wireless profiles http://dtw.jiwe.org/share/wireless/wifi/wireless_alt I know case statements are pretty ugly and a clumsy user could break the syntax but this does provide a hugely efficient, flexible and transparent why to configure multiple wireless profiles - allowing you to easily connect all interfaces to one profile with the same settings or set unique settings for each interface but still only using one profile name. Phil > -----Original Message----- > From: Aaron Griffin [mailto:[EMAIL PROTECTED] > Sent: 06 July 2005 15:30 > To: General Discusson about Arch Linux > Subject: Re: [arch] Roaming Network Profiles (another attempt) > > On 7/5/05, Jason Chu <[EMAIL PROTECTED]> wrote: > > On Thu, Jun 30, 2005 at 05:07:00PM -0700, Judd Vinet wrote: > > > 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. > > > > Seems to work well for me. Only one note: > > The comment in rc.conf says you can have profiles with ! in front of > them > > that won't be loaded. It lies. Fairly easy to fix though. > > > > Jason > > > > -- > > If you understand, things are just as they are. If you do not > understand, > > things are just as they are. > > I still need to test this more thouroughly - haven't had alot of > time... I'll do that tonight if I can and give you more feedback 8) > > _______________________________________________ > arch mailing list > [email protected] > http://www.archlinux.org/mailman/listinfo/arch > _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
