Ubuntu - Revision history

Franks: /* Setting default browser */

2010-07-05T03:18:37Z

Setting default browser

← Older revision		Revision as of 20:18, 4 July 2010
Line 82:		Line 82:

	$ sudo update-alternatives --config x-www-browser		$ sudo update-alternatives --config x-www-browser

			For a GUI alternative to handle all of the update-alternatives:

			$ sudo apt-get install galternatives

Franks at 02:20, 5 July 2010

2010-07-05T02:20:55Z

← Older revision		Revision as of 19:20, 4 July 2010
Line 78:		Line 78:

	$ dpkg --list \|grep "^rc" \| cut -d " " -f 3 \| xargs sudo dpkg --purge		$ dpkg --list \|grep "^rc" \| cut -d " " -f 3 \| xargs sudo dpkg --purge

			== Setting default browser ==

			$ sudo update-alternatives --config x-www-browser

Franks at 06:19, 4 June 2010

2010-06-04T06:19:19Z

← Older revision		Revision as of 23:19, 3 June 2010
Line 70:		Line 70:

	reboot.		reboot.

			== Cleaning up old files ==

			$ dpkg --list \|grep "^rc"

			If you're comfortable cleaning these files out:

			$ dpkg --list \|grep "^rc" \| cut -d " " -f 3 \| xargs sudo dpkg --purge

Franks at 05:25, 2 May 2010

2010-05-02T05:25:09Z

← Older revision		Revision as of 22:25, 1 May 2010
Line 62:		Line 62:
	$ eject -rv		$ eject -rv
	$ eject -sv		$ eject -sv

			== 10.04 with VirtualBox ==

			If you upgrade to 10.04, you may find the screen stays blank or the computer freezes. This maybe be resolved by added the # to the following line in /etc/fstab while in recovery mode:

			#none /proc/bus/usb usbfs devgid=123,devmode=664 0 0

			reboot.

Franks at 22:38, 28 December 2009

2009-12-28T22:38:59Z

← Older revision		Revision as of 15:38, 28 December 2009
Line 54:		Line 54:
	If you do "apt-get dist-upgrade" and your kernel gets upgraded, you will find when you reboot you are stuck running VESA instead of the nvidia drivers.		If you do "apt-get dist-upgrade" and your kernel gets upgraded, you will find when you reboot you are stuck running VESA instead of the nvidia drivers.
	You have to rerun the nvidia installer to build the necessary modules for your kernel.		You have to rerun the nvidia installer to build the necessary modules for your kernel.


			== CD-ROM ==

			If pushing the physical button and "sudo eject" isn't working, try

			$ eject -rv
			$ eject -sv

Franks at 01:27, 4 December 2008

2008-12-04T01:27:52Z

← Older revision		Revision as of 18:27, 3 December 2008
Line 46:		Line 46:

	My sound now works!		My sound now works!

			Note: I'd love an easy way to see what is using your sound driver and release it when necessary

			== Nvidia ==

			If you're using an nvidia graphics card, you're probably forced to use the [http://www.nvidia.com/object/unix.html proprietary nvidia drivers].
			If you do "apt-get dist-upgrade" and your kernel gets upgraded, you will find when you reboot you are stuck running VESA instead of the nvidia drivers.
			You have to rerun the nvidia installer to build the necessary modules for your kernel.

Franks at 05:49, 20 September 2008

2008-09-20T05:49:27Z

← Older revision		Revision as of 22:49, 19 September 2008
Line 17:		Line 17:

	$ sudo apt-get install manpages-dev		$ sudo apt-get install manpages-dev


			== Sound ==

			$ aplay -l

			If it lists your card, awesome. Instead, mine showed:

			aplay: device_list:205: no soundcards found...

			so on to the next step:

			$ lspci -v

			Hopefully you see an Audio device: entry. In my case I saw:

			00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2)
			Subsystem: Dell Unknown device 01f4
			Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 11
			Memory at fe024000 (32-bit, non-prefetchable) [size=16K]

			So I just need the proper module installed:

			$ sudo apt-get install [[Variables\|linux-ubuntu-modules-2.6.22-14-386]]
			Replace 2.6.22 with the kernel you are using.
			$ modprobe [[Variables\|snd-hda-intel]]
			Replace snd-hda-intel with the driver for your sound card.

			My sound now works!

Franks at 08:34, 23 May 2007

2007-05-23T08:34:49Z

← Older revision		Revision as of 01:34, 23 May 2007
Line 11:		Line 11:

	This will install libc-dev, gcc, g++, make and dpkg-dev for C and/or C++ programming.		This will install libc-dev, gcc, g++, make and dpkg-dev for C and/or C++ programming.
			If you intend on programming, you will probably want the development man pages installed.
			For example, I couldn't find the simple functions:
			$ man scanf
			No manual entry for scanf

			$ sudo apt-get install manpages-dev

Franks: New page: I was trying to compile hello world in C: $ gcc -Wall -o hello hello.c hello.c:1:19: error: stdio.h: No such file or directory hello.c: In function ‘main’: hello.c:5: warning: imp...

2007-05-23T07:21:54Z

New page: I was trying to compile hello world in C: $ gcc -Wall -o hello hello.c hello.c:1:19: error: stdio.h: No such file or directory hello.c: In function ‘main’: hello.c:5: warning: imp...

New page

I was trying to compile hello world in C:
$ gcc -Wall -o hello hello.c
hello.c:1:19: error: stdio.h: No such file or directory
hello.c: In function ‘main’:
hello.c:5: warning: implicit declaration of function ‘printf’
hello.c:5: warning: incompatible implicit declaration of built-in function ‘printf’

If you plan on doing any programming on ubuntu:

$ sudo apt-get install build-essential

This will install libc-dev, gcc, g++, make and dpkg-dev for C and/or C++ programming.