fatal error: curl/curl.h: No such file or directory
If you’re missing the curl/curl.h header file, chances are you’re just missing the correct dev package file for the curl library.
sudo apt-get install libcurl4-gnutls-dev
That should fix it.
|
|||||
Archive for the ‘Command Line’ CategoryIf you’re getting the following error: fatal error: libconfig.h: No such file or directory
Then you’re probably missing the libconfig-dev package from your system. Simply run the following command and it’ll fix it: sudo apt-get install libconfig-dev
One thing that Linux Guru’s and Terminal Wizards often argue is that it’s way quicker to use the command line to do anything in Linux than it is through menus and what not. While the jury is still out on this, there are a lot of things they know which do help put the ball in their court which can often take a lot of time exploring the terminal to discover. I’ve compiled a list of my favourite commands and tricks that I think that would have saved me a bunch of time if I’d been aware of them when I first ventured in to Linux. 1. Repeat Recent Commands:Let’s say you’ve just ran a command but forgot you needed to run it as sudo, you can use !! to repeat it with the additional sudo at the beginning, as below: alex:~$ apt-get install package
alex:~$ sudo !!
sudo apt-get install package
Additionally you’re able to use this to go back further than the last command by replacing the second ! for -n (where n is the number of commands ago you want to repeat). alex:~$ ls
alex:~$ cd dir
alex:~$ cat file
alex:~$ !-3
ls
How about if you want to reuse the arguments from the last command but not the command itself, well it can do that too: alex:~$ ls /home/alex/Desktop
alex:~$ cd !*
cd /home/alex/Desktop
2. Replace String In Last Command:The use of the following command allows you to repeat the last command but replacing a string within it, useful if you made a mistake or typo. The follow example shows correcting a path for a change directory command. alex:~$ cd /this/dir/is/wrong
alex:~$ ^wrong^right^
cd /this/dir/is/right
3. Reset:Chances are, you’ll come across a situation where you’ve seemingly borked a terminal. Maybe you used cat on the wrong file or a program tried to export some strange characters which changed the settings. The following command should get you back to a fresh terminal quickly and you can often run it even when you don’t think you can. If the screen is really borked, try hitting enter before hand, typing reset and hitting enter again. alex:~$ reset
4. Running A Command In The Background:Adding an & after the command you run allows you to continue to use the terminal screen while keeping the process running. Below shows an example of opening gedit in the background but allowing me to continue using the terminal for other commands. Great for editing and compiling code with the minimal number of terminals open. alex:~$ gedit &
Once ran it’ll give you the process ID which allows you to kill it easily once you’re done with it. 5. Exiting A Terminal & Keeping Background Processes Running:If you’ve opened a bunch of processes in the background (as per previous command) but now you want to close the terminal screen but not these processes you can use the following to release the ownership of the processes and exit. alex:~$ disown -a && exit
6. htop:Similar to ‘top’ (which allows you to view tasks in real-time with other useful info such as memory and CPU usage) but it’s displayed in a much easier to understand and interactive. It allows you to kill tasks without entering its PID, search, filter, sort and a bunch of other features. alex:~$ htop
7. Reverse History Search:Ctrl + r Using this will allow you to start typing and it’ll find the last command that contained the string you’re typing, hitting enter will execute that command. For example: alex:~$ cd /home/alex/this/is/a/dir
ctrl+r & typing "a/dir"
(reverse-i-search)`': cd /home/alex/this/is/a/dir
8. Piping (Combining) Commands:Piping commands allows you to pass the data that would usually be outputted to be directly passed as an input to another command, for example below is a list command being passed in to the less command to allow for scrolling of the data. This will work for most commands and experimentation is the best form of learning in this case. alex:~$ ls | less
9. Auto Complete Command & File Names:Half way through typing a command you can hit the Tab key and it’ll auto complete the word for you, if there are more than one other possible combinations a double tap of it will show you the possibilities. This also works for directory and files and can save some serious typing time. 10. Other useful Keyboard Shortcuts:A few other keyboard shortcuts that are also useful to know (and not always as obvious as they should be): Ctrl + c – kill current process If you’re trying out the latest version of Ubuntu, 12.04 or Precise Pangolin and you want to keep your old /home partition, chances are you’ve come across the installation hanging on a process “Removing conflicting operating system files…”. No worries, this seems to be a common bug and there’s a pretty easy work around. Continue with the installation, without asking for the /home partition to be mounted. Only set the root partition (/) and your swap space. Once the installation is complete, reboot and load it up. Now, you’ll want to find the partition that /home is mounted under, this will likely be /dev/sdxN, where x is the drive letter and N is the partition number (i.e mine is located under /dev/sda5). If you’re unsure, you can list the possible drives using the following command: ls /dev/ | grep sd
And then you can mount each drive under in a temp directory and check what’s in there: mkdir temp
mount /dev/sda1 temp
Once you know which partition you want, it’s time to edit your /etc/fstab/ sudo gedit /etc/fstab
For those who don’t go digging around in the config files of linux, this may look pretty daunting, but it isn’t. All you really need to do is add a new line to mount your home partition. Here’s mine: /dev/sda5 /home/ ext4 defaults 1 2
The first part is the partition that’s being used, next what the partition is. Next is the file system type. Followed by default options and then the dump and pass values. Once you’ve saved this file with the appended line, reboot your system. Now you should find your old home partition is mounted normally and you can get on with your install. Temporary proxy:Where proxy.addr is the proxy address, 4040 is the port number. Some proxies may require “http://” before the address. export http_proxy="proxy.addr:4040"
export ftp_proxy="proxy.addr:4040"
export https_proxy="proxy.addr:4040"
If you run this in a terminal, any programs opened from that terminal will adhere to the proxy you set but any other applications will not. This makes it useful if you just want to launch a browser for a quick browsing session but don’t need the whole system to access the internet. If you do need your entire system to access the network, you can add these to the bottom of “~/.bashrc” this will enable any new programs running and the whole system (after a restart) to use the settings. Essentially ~/.bashrc are commands run when a terminal is opened. NOTE: If you do this, when you remove them your machine will likely need a restart to undo the changes. Proxy with loginIf your proxy server requires a login, this is an addition of the above however the syntax is as follows: user:pass@proxy.addr:4040
APT Proxy:APT (used for system updates) has its own proxy settings, which seem to ignore the above settings. Where nano is the editor, if you prefer use a graphical one such as gedit, kedit etc. sudo nano /etc/apt/apt.conf.d/02proxy
add: Acquire::http::Proxy "http://proxy.addr:4040";
Source : http://naveenubuntu.blogspot.com/2011/09/updating-packages-behind-prxy-in-ubuntu.html After installing Ubuntu on a USB stick with the Ubuntu USB Startup Disk Creator (usb-creator-gtk) you might encounter an error such as the following: stdin: I/O error
stdin: error 0
/init: line 1: can't open /dev/sr0: No medium found
This is actually a bug with the software and isn’t anything you’ve done wrong. It seems to be a bug that’s effecting users running Karmic, Lucid, Maverick and Natty so it’s a pretty wide spread issue. The best way I have found to get around this issue is to install and run unetbootin to create live USBs. If you’re using linux it should be found in the usual place you can install things. Installation:Ubuntu/LinuxMint/Debian: sudo apt-get install unetbootin
Fedora/OpenSuse: sudo yum install unetbootin
Create a live USB:To install a distro it’s pretty simple, either select it from the “Distribution” option and pick a distribution and version, UNetbootin will then actually download it and install it for you. Alternatively you can pick an Diskimage and browse for the ISO file you download (and would usually burn to a CD/DVD) and install from that. Select the USB Drive at the bottom and hit ok and it’ll install a bootloader, the system and you’ll be up and running in no time.
Persistence File:If you wanted a persistence install which allows you to save files, settings and installed programs you’ll have to do a little manual work as it currently doesn’t support that option. Go to http://unetbootin.sourceforge.net/diskimg/ and download one of the files (128mb.zip, 256mb.zip, or 512mb.zip) corresponding to the amount of persistent space you want (make sure the size of the persistent disk image is smaller than the free space you have on your USB drive). You’ll then need to edit the syslinux.cfg file that was created by UNetbootin in the root of the directory (just open it with a text editor) you should see something similar to the following:
So on the line that starts “appen initrd=” you’ll want to add the option of “persistent”, it should then look like the following: NOTE: Wordpress changes my double dash at the end of the last line to a single long dash, this won’t work. It’s easiest just to add the final word before the double dash in the file, do not copy and paste this in to your file. If you do, you will get more errors.
I added this line to all that used the “file=/cdrom/preseed/ubuntu.seed” option, since that’s the image that’s being opened and it should then change all options on the bootloader that will load the ubuntu install. I have a TV and my monitor connected to my PC by a VGA switch box but what’s annoying is they aren’t the same resolution. This causes problems because I can’t see what I’m doing when I have switched to TV and usually have to leave the setting manager open so that when I change between them I just have to hit return and the resolution changes. That’s great and all but it’s far more effort than I want for something I do fairly often. My plan was initially to create two xorg.conf files and switch between them using a script, I figured this would be the easiest way even though I haven’t messed around with xorg stuff for a few years ever since things just started working better in Linux. Turns out I couldn’t even find where they keep the xorg.conf file, it sure isn’t in /etc/X11 where it was the last time I looked.. On the search for this file though I came across another useful tool called xrandr, which essentially allows you to change the resolution from the command line.
For more information on xrandr check out the manual page (or type man xrandr in terminal). It turns out it’s an extremely easy tool to use, with a command as simple as the following changing the resolution: xrandr --output VGA1 --mode 1440x900
So the next thing I did was create the following script which allows the resolution to switch between 1440×900 and 1360×768 (my monitor and my TV native resolutions). #!/bin/bash
TV="1360 x 768"
MONITOR="1440 x 900"
TEST="$(xrandr | grep current | sed -e 's/.*current //;s/, maximum.*//')"
#echo $TEST
if [ "$TEST" == "$MONITOR" ]
then
xrandr --output VGA1 --mode 1360x768
elif [ "$TEST" == "$TV" ]
then
xrandr --output VGA1 --mode 1440x900
else
exit
fi
This script simply checks what the current resolution is being used and then toggles between the two set resolutions.
After installing Ubuntu 11.10 I headed straight for an install of gnome-shell, I’ve been using it for a couple of months without any issue and got used to it enough that it wouldn’t impede on my workflow. That was until this release, when it was officially supported by Canonical and all of a sudden it’s broken and mostly useless. So off to Xfce I go, it’s like gnome2 but way more customisable and actually pretty sweet. However because I installed from a clean Ubuntu install rather than an xubuntu install I noticed that I still have the global menu (or appmenu-*) floating at the top under the default panel. To remove it, since it’s doing nothing and it looks plain stupid with transparency added to the panel. It’s pretty simple to uninstall, just open up a terminal window and use the following command: sudo apt-get remove appmenu-gtk3 appmenu-gtk appmenu-qt
Now just re-start X (log out and in again, restart the computer) and when you return, it should be gone. And if you ever feel the need to want it back, maybe you want to give unity another try then use the following command: sudo apt-get install appmenu-gtk3 appmenu-gtk appmenu-qt
Source: http://www.addictivetips.com/ubuntu-linux-tips/how-to-disable-global-menu-in-ubuntu-11-10-tip/ ifconfig eth0 | sed -n '/^[A-Za-z0-9]/ {N;/dr:/{;s/.*dr://;s/ .*//;p;}}'
So you want to display just your IP address and not all the other stuff that comes with using the ifconfig command. Then use the above command. It’s useful if you need your IP address in a script but you don’t want to set a static address for your machine, it outputs just the IP address on a single line as shown below:
|
  This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License. |
||||
|
Copyright © 2012 Alex Sleat - All Rights Reserved |
|||||
Goodreads
Last.fm