Contents1 Installation1.1 Base package1.2 GTK+...

New Download Links
New Download Links


Contents1 Installation1.1 Base package1.2 GTK+... D-Bus connection errorContents1 Installation1.1 Base package1.2 GTK+ client1.3 KDE client1.4 Notifications1.5 Alternative2 Getting started2.1 Initial setup2.2 Running Wicd in Desktop Environment2.3 Running Wicd in Text Mode2.4 Switching WPA supplicant driver2.5 Autostart2.6 Scripts2.6.1 Stop ARP spoofing attacks2.6.2 Change MAC using macchanger3 Troubleshooting3.1 Autoconnect on resume from hibernation/suspension3.2 Importing pynotify failed, notifications disabled3.3 D-Bus connection error message3.4 Problems after package update3.5 Note about graphical sudo programs3.6 Eduroam3.7 Two instances of wicd-client (and possibly two icons in tray)3.8 Bad password using PEAP with TKIP/MS-CHAPv23.9 Wicd skips obtaining IP address on wlp3.10 dhcpcd not running4 See also Installation Base packageInstall wicd, available in the official repositories. It includes everything needed to run the wicd daemon and the wicd-cli and wicd-curses interfaces.GTK+ clientFor a GTK+ front-end, install wicd-gtk, available in the official repositories. It includes everything needed to run the GTK interface of wicd and the autostart file for the client to appear in the system tray.KDE clientFor a KDE front-end, install wicd-kdeAUR[ broken link: archived in aur-mirror], available in the AUR.NotificationsTo enable visual notifications about network status, you need to install the packages notification-daemon and python2-notify.If you are not using GNOME, you may want to install xfce4-notifyd instead of the notification-daemon, because it pulls a lot of unnecessary GNOME packages.AlternativeThe wicd-bzrAUR buildscript is available in the AUR, which should build the latest development branch.If you need an alternative version or you just want to roll your own package, you can easily build it using ABS.Getting started Initial setupWicd provides a daemon that must be started.Note: wicd-curses is less stable than wicd-gtk, and is known to crash regularly. Switching WPA supplicant driverWicd still suggests to almost always use Wext as WPA supplicant driver and defaults to it. This is outdated behavior. One should use nl80211 instead, except with old drivers that do not support it. The relevant option is located in Preferences Advanced Settings.AutostartThe wicd-gtk package puts a file in /etc/xdg/autostart/wicd-tray.desktop, which will autostart wicd-client upon login to your DE/WM. If so, enabling the wicd system service is enough:# systemctl enable wicdIf /etc/xdg/autostart/wicd-tray.desktop does not exist, you can add wicd-client to your DE/WM startup to have the application start when you log in.Note: If wicd-client is added to DE/WM startup when /etc/xdg/autostart/wicd-tray.desktop exists, you will have an issue of two wicd-client instances running. ScriptsWicd has the ability to run scripts during all stages of the connection process (post/pre connect/disconnect).Simply place a script inside the relevant stage folder within /etc/wicd/scripts/ and make it executable.The scripts are able to receive three parameters, these being:$1 - the connection type (wireless/wired).$2 - the ESSID (network name).$3 - the BSSID (gateway MAC).Stop ARP spoofing attacksThe script below can be used to set a static ARP, to stop ARP spoofing attacks.Simply change the values within the case statement to match those of the networks you want to set static ARP entries for daemon tools substitute for mac. Launch it as root:#!/bin/bash#Set the parameters passed to this script to meaningful variable names.connection_type=$1essid=$2bssid=$3if [ ${connection_type} == wireless ] then#Change below to match your $essid inYOUR-NETWORK-NAME-ESSID)arp -s 00:11:22:33:44:55Netgear01923)arp -s 10:11:20:33:40:50ANOTHER-ESSID)arp -s 11:33:55:77:99:00*)echo Static ARP not set. No network defined.esacfiChange MAC using macchangerSee MAC address spoofing#systemd + macchanger + dhcpcd (no NetworkManager).The script below can be used to change the MAC address of your network interfaces.To change the MAC whenever you connect to a network, place this script under /etc/wicd/scripts/preconnect/.Take a look at macchanger --help to adjust the macchanger command to your liking.#!/usr/bin/env bashconnection_type=$1if thenip link set wlp2s0 downmacchanger -A wlp2s0ip link set wlp2s0 upelif thenip link set enp1s0 downmacchanger -A enp1s0ip link set enp1s0 upfiTroubleshootingSee Network configuration#Troubleshooting for troubleshooting wired connections and Wireless network configuration#Troubleshooting for troubleshooting wireless connections. This section covers only problems specific to wicd.Autoconnect on resume from hibernation/suspensionIf for some reasons autoconnect on resume from hibernation or suspension does not work automatically, you can manually restart Wicd by enabling the following service file for your user./etc/systemd/system/wicd-resume@.service[Unit]Description=Restart Wicd autoconnect service on[Service]Type=oneshotUser=%iRemainAfterExit=noExecStart=/usr/share/wicd/daemon/[Install]WantedBy=suspend.targetImporting pynotify failed, notifications disabledIn case the python2-notify package did not get installed automatically. You can install it from official repositories.D-Bus connection error messageIf wicd suddenly stopped working and it complains about D-Bus, it is quite likely that you just need to remove wicd fully, including and all its configuration files, and re-install it from scratch:# pacman -R wicd# rm -rf /etc/wicd /var/log/wicd /etc/dbus-1/system.d/wicd*# pacman -S wicdCheck this link for more details: also throws a D-Bus connection error message (Could not connect to wicd's D-Bus interface.) when wicd is not running due to a problem with a config file. It seems that sometimes an empty account gets added to /etc/wicd/wired-settings.conf in which case you simply have to remove the[]and restart wicd.If the above does not work, you could try Problems after package updateSometimes the wicd client fails to load after a package update due to D-Bus errors.A solution is to remove the config files in the /etc/wicd/ directory.# systemctl stop wicd# rm /etc/wicd/*.conf# systemctl start wicdNote about graphical sudo programsIf you are receiving an error about wicd failing to find a graphical sudo program, install one of gksu, ktsussAUR, or kdebase-runtime, then use the relative command:$ ktsuss wicd-client -n$ gksudo wicd-client -n$ kdesu wicd-client -nEduroamSee WPA2 Enterprise#Wicd.Two instances of wicd-client (and possibly two icons in tray)See the note in #Running Wicd about the autostart file in /etc/xdg/autostart and the forum post and bug report provided in #External Links. Essentially, if /etc/xdg/autostart/wicd-tray.desktop exists, remove it. You only need the wicd service enabled in systemd.Bad password using PEAP with TKIP/MS-CHAPv2The connection template PEAP with TKIP/MS-CHAPv2 requires the user to enter the path to a CA certificate besides entering username and password. However this can cause troubles resulting in an error message of a bad password [1]. A possible solution is the usage of PEAP with GTC instead of TKIP/MS-CHAPv2 which does not require one to enter the path of the CA cert.Wicd skips obtaining IP address on wlpThis can be caused by dhcpcd running alongside wicd as systemd service. A solution would be to stop/disable dhcpcd.dhcpcd not runningNormally it should not be required, nor recommended to run the dhcpcd service next to wicd. However, if you encounter the error message that dhcpcd is not running, then you can try running dhcpcd and see if you encounter any incompatibilities when using both services at the same time.# systemctl start dhcpcdAlternatively, as a workaround you might consider switching to dhclient in the Wicd settings.

Command Line Mac: Vi[m] .

Contents1 Installation1.1 Base package1.2 GTK+... autostart wicd-tray desktopVi is an one of two powerhouse text editors in the Unix world, the other being EMACS daemon tools substitute for mac. While obtuse, vi is extremely powerful and efficient. There may be times when vi is the only text editor available, so it helps to at least know the basics.On Mac OS X (and Linux), vi is symlinked to vim (vi improved), a more modern free software version. Vim It is the default editor when changing a crontab.If you gave vi a whirl and don't see the beauty of it, give the nano editor a try. It also ships with Mac OS X.note: a chunk of this small guide came from a web page I found long ago, but I don't remember where so I can't give proper credit.

I've added and changed things from the original text.Vi has two modes, command and insert (really, three if you count replace mode). Command mode is used to navigate, search, and issue other commands. Insert mode is used to enter text.Vi starts in command mode.You can precede most commands with a number indicating how many times to perform a command. For example, entering 99 followed by the down arrow will move the cursor down 99 lines. 99x will delete 99 characters.

While in command mode (case sensitive)move the cursor with arrow keys if there aren't any arrow keys, use j,k,h,li - change to insert mode (before cursor)a - change to insert mode (after cursor)A - change to insert mode (at end of line)r - replace one characterR - overwrite textx - delete one characterdd - delete one lineyy - yank line (copy)p - paste deleted or yanked text after cursorP - paste deleted or yanked text before cursorG - go to end of the file1G - go to top of the fileJ - merge next line with this one/ - search, follow / with text to find:wq - write file and quit:q! - quit without saving%s/old/new/g - substitute replace old with new on all lines:g/pattern/d - delete all lines that match the pattern While in insert modeESC - change to command modeany text typed is entered at the cursor Typical vi sessionType vi file.txt at command promptMove cursor to where new text will be addedType i to change to insert modeType new textType ESC to go back to command modetype :wq and ENTER to write the file and quit►2012(2)►February(2)►2011(8)►November(1)►October(1)►September(1)►July(1)►May(1)►April(1)►January(2)►2010(8)►September(1)►August(1)►July(1)►May(1)►March(2)►February(1)►January(1)►2009(9)►December(2)►November(1)►October(1)►September(1)►June(1)►April(1)►March(1)►February(1)▼2008(59)▼December(59)Apple System LoggerDisabling hardware via kernel extensionsAnother way to enable and disable rootPower settings from the command lineSpeeding MacBook 802.11g connectionsIntro to ipfwAirport command line utilityDate validation in Ruby using the Date objectBeginning a Rails app -- for beginnersRuby SnippetsBoot CampRubyIntel vs. PowerPC MacsHow to turn off DashboardAdvanced BASH scripting guideAmazon S3 from the command lineSay say sayInstalling a .dmg application from the command lin...Updating Apple software from the command lineSyncing Palm devices with the Mac via BluetoothHow to enable the OS X root userScreenshots from the command lineHow to find out which files were installed with a ...Using hdiutilApache Authentication and Authorization using LDAP...Using diskutilCopy and paste inside a shell scriptDefaults -- setting preferences from the command l...NvramSysctlDiagnostic command line tools30 days with JFSMacPorts, Up and RunningLearn to Talk AWKCron fields and crontabsSpotlight on the command lineSurfing the Keyboard in BASHPostgreSQLMySQLGnu Privacy Guard (GPG)A Bourne Again DaemonPerlRsyncBASH job control: fg, bg, jobs, and Ctrl-ZTarSSHFix a broken terminalDaily aliasesUnix permissions on OS XSMTP testing from the command lineList Open Files (lsof)Vi[m]Sudo vs. Root: The Real StoryFind suid/sgid filesFile TimestampsBASH BasicsDeleting files with bad namesMac/Linux/Windows file name frictionBoot key sequences