/etc/quickswitch/switchto.conf.sample:55: # iwconfig=/usr/local/sbin/iwconfig The code is correct: /usr/bin/switchto:152: iwconfig => "/sbin/iwconfig",
If someone picks this up, s/maintainer-wanted/maintainer-needed/ in metadata.xml
Something similar, perhaps does not worth different ticket: /usr/share/doc/quickswitch-1.05/README.gz: > It is suggested that you set ONBOOT=no in the config file for your > device in /etc/sysconfig/network-scripts But /etc/sysconfig/network-scripts does not exists and there is no ONBOOT in any files under /etc.
Honestly, I fail to see why do we have this thing in the tree. Last release in 2003. baselayout can handle as many networks as you wish, all configured in one file, this utility generally conflicts with baselayout workings. (As for this bug, the examples are RH specific and useless for Gentoo, not exactly our problem).
Treecleaners, vote :) ++
++ ; useless cruft
I think with baselayout-1.12 being stable, this has no longer a reason to be in the tree (while being broken and unmaintained). So, feel free to mask/punt Raúl.
# Raúl Porcel <armin76@gentoo.org> (09 Apr 2007) # Pending removal 09 Jun 2007, for treecleaners # app-admin/cpu -> bug 173064 # app-admin/quickswitch -> bug 134335 # app-misc/jive -> bug 142838 # app-text/mgv -> bug 154645 # net-misc/dhcp-agent -> bug 168565 # x11-plugins/wmmail -> bug 73987 app-admin/cpu app-admin/quickswitch app-misc/jive app-text/mgv net-misc/dhcp-agent x11-plugins/wmmail
Hi there! I've a question: Jakub Moc wrote: ''' Honestly, I fail to see why do we have this thing in the tree. Last release in 2003. baselayout can handle as many networks as you wish, all configured in one file, this utility generally conflicts with baselayout workings. (As for this bug, the examples are RH specific and useless for Gentoo, not exactly our problem). ''' Ok. I'm a laptop user and i have to connect to several static networks (no DHCP) sometime wired, sometime wireless. Can u please explain me how to manage this as easy as "switchto university" with the baselayout? Or "switchto wireless", with automatically preloading (and later unloading) the necessary modules. If that is really possible, i think we need a better documentation, or a guide for it (there r a lot of laptop users, i guess). I already looked in the net init script, and i didn't understand, how this should work. If there are only this documentation bugs, and you know no better possibility to manage networks, i would offer my help to fix them. greez Björn
If you want to do it the same way, I don't see any difference between 'switchto university' and creating your own softlevel called university/home/offline/whatever; it's already documented: http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=4#doc_chap5 Just check that you have RC_USE_CONFIG_PROFILE="yes" in /etc/conf.d/rc and call your config files as /etc/conf.d/net.<runlevelname> More reading: /etc/conf.d/{net,wireless}.example http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4 http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4&chap=6
Ok, thanks i got it. Really easy than :) So you got my vote , too ;) ++
Ok, but one disadvantage is still there. Normally i've had to standard runlevels: boot and battery, and managed networks with quickswitch. Now i've to maintain 5 default runlevels and 5 battery runlevels (each with different net configs).Imagine i alter my system config, i 've to alter 10 runlevels.. not very comfortable?! is there another magic i can do? greez björn
i know, i don't need a battery runlevel for EACH network, but you see the problem?
Please note that this is not a support forum; see [1] and move to #gentoo, forums.gentoo.org or appropriate mailing list [2] if you have more questions. [1] http://www.gentoo.org/doc/en/power-management-guide.xml [2] http://www.gentoo.org/main/en/lists.xml
Sorry, I don't really want support here. I just thought that this place is the right one to discuss the removal of this packet. I just wanted to say, that this might be an disadvantage.I don't want to manage so many soflevels .. I guess i copy the ebuild to my local overlay and will wait until there is a good solution. Anyway thanks for your help.
I also use quickswitch from my laptop (have used it for years) and if possible would like it to stay in portage. In most cases I only need to switch network IPs/DNS/Gateways, having to setup a complete runlevel is overkill for these. I find the quickswitch configuration much simpler. Is there any chance that this could stay???? It appears to be stable and the only issue I've had with Gentoo was to add the SWITCHTO boot parameter to env_whitelist (this bug report is a non-issue as far as I can see). What would be needed to keep it in portage? Paul Sunners
I'd like to vote against removal. First: this application works perfect and it has all the features needed for use with a laptop. I don't think the lack of new releases is a problem here since the current release still works perfect. Second: I use this app to quickly change network settings by hand. It's much more convenient than doing so with ifconfig,route, setting dns,... --
Same for me: couldn't find another way of doing things (other than quickswitch) that keeps things simple. I use it a lot and, as a laptop user, I find it a pain to use several different runlevels (which grows dramatically in number as I need more REAL runlevels, like battery and ac). If you care, as a software engineer, I find it architecturally wrong to use runlevels for this, since it's really a network configuration issue and not a global system-level services issue. For this we need a far more flexible network configuration system in baselayout. Believe me, as a daylong-notebook-only user ( :p ), at the actual state of the art there's no comparison between quickswitch an runlevels in usability so PLEASE keep it in the tree untill something better comes out! Thanks!
Unmasked and fixed. Péter: please ignore that from the README, i don't think it's worth the change, it just doesn't apply for Gentoo.
