Wednesday, 20 August 2008
Tuesday, 19 August 2008
Tips for new Ubuntu user
Ubuntu has become the most popular Linux distribution for new Linux users. It's easy to install, easy to use, and usually "just works." But moving to a different operating system can be confusing, no matter how well-designed it is.
Here's a list of tips that might save you some time while you're getting used to Ubuntu.
1. Getting multimedia to work
The default Ubuntu install contains free software only, which means that it doesn't support some popular multimedia formats straight out of the box. This is inconvenient, but the Ubuntu folks have good reasons for not shipping with support for MP3, DVDs, and so forth -- including that software could cause them some legal headaches, or incur some serious fees.
Fortunately, as a user, you don't need to worry about fees (though some of the packages may not be legal due to patent restrictions or restrictions on circumventing copy protection, depending on where you live). The Ubuntu wiki has a page on restricted formats that explains how to get the packages you need. However, if you run Ubuntu on AMD64 or PowerPC hardware, you'll still be out in the cold for some of the packages, since some multimedia formats depend on proprietary software that's not available for those hardware platforms.
2. Changing the defaults
Ubuntu comes with a number of defaults that may or may not be to your liking. For example, the default editor is set to Nano, which isn't optimal if you're used to Vim.
The easy way to change this is to use the update-alternatives program, which maintains the symbolic links under /etc/alternatives that determine the default programs for FTP, system editor, rsh, Telnet, window manager, and so forth. Look under the /etc/alternatives directory to see what programs are managed.
To change the default editor, run sudo update-alternatives --config editor. You'll see a dialog like this:
There are 3 alternatives which provide `editor'.
Selection Alternative
-----------------------------------------------
1 /usr/bin/vim
2 /bin/ed
*+ 3 /bin/nano
Press enter to keep the default[*], or type selection number:
Just type 1 to switch to Vim. Note that on my system, I don't have Emacs or many other editors installed; if I did, the utility would offer the other editors as choices.
games_final_batlle.jpg
3. How to install packages
Most of the application software you'll want to add to your system will be available through the Ubuntu repositories using Synaptic, Adept, or another package management tool. What if you want to install something like Opera that is available as a package for Ubuntu, but isn't in the repositories?
In that case, download the application's Debian package (.deb) and right-click on the file. At the top of the context menu, you should see an option to open the package with the GDebi package installer. GDebi will provide a description of the package, what files are included, and other details about the package. The package installer also has a Install Package button; just click that and it will install the package. Note that the package installer also checks to verify whether it can install the package -- if it has dependencies that can't be satisfied, GDebi will give an error and refuse to install it.
If you prefer to install packages at the command line, just use sudo dpkg -i packagename.deb.
4. Sudo and gksudo
If you've used Linux for any amount of time, you might be used to running programs as root directly whenever you need to install packages, modify your system's configuration, and so on. Ubuntu employs a different model, however. The Ubuntu installer doesn't set up a root user -- a root account still exists, but it's set with a random password. Users are meant to do administration tasks using sudo and gksudo.
You probably already know how to use sudo -- just run sudo commandname . But what about running GUI apps that you want to run as root (or another user)? Simple -- use gksudo instead of sudo. For instance, if you'd like to run Ethereal as root, just pop open a run dialog box (Alt-F2) and use gksudo ethereal.
By the way, if you really must do work as root, you can use sudo su -, which will log you in as root. If you really, really want to have a root password that you know, so that you can log in as root directly (i.e., without using sudo), then run passwd when logged in as root, and set the password to whatever you want. I'd recommend using the pwgen package to create a secure password not only for root but for all your user accounts.
5. Add users to sudo
When you set up Ubuntu, it automatically adds the first user to the sudo group, allowing that user to make changes as the super user (root) by typing in their password. However, it doesn't automatically add additional users to the sudo group. If you want to give someone else superuser privileges on your shared system, you'll have to give them sudo access.
To add new users to sudo, the easiest way is to use the usermod command. Run sudo usermod -G admin username . That's all there is to it. However, if the user is already a member of other groups, you'll want to add the -a option, like so: sudo usermod -a -G admin username .
If you prefer the GUI way of doing things, go to System -> Administration -> Users and Groups. Select the user you want to add to sudo, and click Properties. Under the User privileges tab, check the box that says "Executing system administration tasks" and you'll be all set.
6. Adding a new desktop
Many users aren't sure what packages to add in order to run KDE or Xfce window managers on a stock Ubuntu system -- or what packages to add to run GNOME on Kubuntu or Xubuntu. You could add all of the necessary packages one at a time, but there's a much easier way to go about it.
To install all of the packages that come with one of the flavors of Ubuntu, such as Kubuntu, run apt-get install kubuntu-desktop (or edubuntu-desktop, xubuntu-desktop, or xubuntu-desktop).
If the GUI is more your style, the *desktop packages can be installed using Adept, Synaptic, or another package manager
7. How to reconfigure X.org
Most of the time, X.org -- that's the software that drives your video card and provides the foundation for the GUI, whether you're running GNOME, KDE, Xfce, or another window manager -- "just works" when you install Ubuntu. In fact, I'd wager that most Ubuntu users never even have to think about their video settings.
But, sometimes you need to reconfigure X.org because Ubuntu hasn't detected your video card and monitor properly, or maybe you've just purchased a shiny new video card and need to get it working with Ubuntu. Whatever the reason, it's good to know how to reconfigure X without having to edit your /etc/X11/xorg.conf by hand.
To run through the configuration, use dpkg-reconfigure xserver-xorg at the console or in a terminal window. Then you'll have a chance to specify your monitor and video card, the resolutions and color depths you want to run the server at, and so forth.
Since every setup is different, it's hard to give concrete advice for configuring X, but it's generally OK to accept the configuration defaults. Also, you'll be given a choice between Advanced, Medium, and Simple methods for giving your monitor's specifications. As a rule, it's probably best to go with Simple unless you really know what you're doing, or the Simple method doesn't work for you.
8. Log in automagically
By default, when you boot up the computer, Ubuntu will give you a login screen before you get to your X session. From a security perspective, this is a good idea, particularly in multi-user environments or in any situation where other people have physical access to your computer. Still, many users are used to just being logged in automatically, and don't want to fuss with logging in each time they reboot their desktop.
To set this in Ubuntu, go to System -> Administration -> Login Window. You'll need to provide your password, then you'll get the Login Window Preferences window with five tabs. Choose the Security tab and click Enable Automatic Login. If you have more than one regular user, make sure to specify which user should be logged in automatically.
Again, and I can't stress this enough, this is only a good idea for home computers where only one person has access to the computer. I don't recommend this for work computers or laptop/notebook computers, when someone else might have access to the machine.
9. Compiling from source
Ubuntu's package repository is huge, particularly when you factor in packages in the Universe and Multiverse repositories. However, many users find themselves needing to install packages from source, either because they want to use a newer package than is available in the repository, or they want to try something that's not in the Ubuntu repository at all.
If you want to install packages from source, you can use a few shortcuts to make life easier. First, you'll probably want to get the build-essential meta-package if you haven't installed any developer tools. Run sudo apt-get install build-essential; it will grab GCC, the Linux kernel headers, GNU Make, and some other packages that you'll probably need.
Next, if you're going to compile a package such as Gaim because a new version is out, you might be able to satisfy the new version's dependencies with the old version's dependencies. To do this, grab the package's build dependencies with sudo apt-get build-dep packagename . That will grab all of the development packages you need to build the package that's currently available in Ubuntu, and will probably satisfy dependencies for the new version you're compiling.
Finally, don't make install when you compile from source -- use CheckInstall instead. CheckInstall will create a Debian package and install it for you, so you can remove or upgrade the software more easily later on.
Grab CheckInstall with apt-get install checkinstall. After you've run ./configure ; make, just run sudo checkinstall and answer a few simple questions. Note that if you compile packages on AMD64, CheckInstall will select X86_64 as the architecture rather than amd64 -- which will cause the package install to fail, since Ubuntu expects amd64 as the architecture rather than X86_64.
By the way, the packages created by CheckInstall also make it easier to deploy the same package on several machines, if you happen to have several systems running Ubuntu. See Joe Barr's excellent CLI Magic feature on CheckInstall too.
10. A new kernel
Ubuntu will install a 386 kernel for x86 machines, which probably isn't what you'd want if you've got a Pentium II or better CPU. The 386 kernel is compiled to work with just about any x86 CPU, but extensions that appear in later CPUs can give your system a boost, if they're taken advantage of. To replace the kernel, open Synaptic or Adept and search for linux-image. You'll see several choices. Pick the one that best suits your CPU -- probably the linux-image-686 package for Pentium II and later CPUs, and linux-image-k7 for later AMD processors. Note that if you're using the AMD64 line (or Intel's x86-64 CPUs) you should be using the amd64 images.
Of course, once you install the new kernel, you'll need to reboot. Another benefit to the 686 kernels is that they have SMP support, which is a bonus for multi-core and Intel HyperThread CPUs.
If none of the tips cover questions that you have about Ubuntu, try checking out the Ubuntu wiki, forums, and mailing lists. As a rule, the Ubuntu users are a helpful lot, and you'll usually be able to find someone who's run into the same situation that you have questions about.
Now you have to add additional repositories , close synaptic package manager and type the following command in the terminal window (Application -> Accessories -> Terminal )
¨wget -q http://packages.medibuntu.org/medibuntu-key.gpg -O- | sudo apt-key add - ¨
and
¨sudo wget http://medibuntu.sos-sts.com/sources.list.d/feisty.list -O /etc/apt/sources.list.d/medibuntu.list
---------
SOURCE: http://ubuntuland.nireblog.com/post/2008/03/27/ten-tips-for-new-ubuntu-users
Here's a list of tips that might save you some time while you're getting used to Ubuntu.
1. Getting multimedia to work
The default Ubuntu install contains free software only, which means that it doesn't support some popular multimedia formats straight out of the box. This is inconvenient, but the Ubuntu folks have good reasons for not shipping with support for MP3, DVDs, and so forth -- including that software could cause them some legal headaches, or incur some serious fees.
Fortunately, as a user, you don't need to worry about fees (though some of the packages may not be legal due to patent restrictions or restrictions on circumventing copy protection, depending on where you live). The Ubuntu wiki has a page on restricted formats that explains how to get the packages you need. However, if you run Ubuntu on AMD64 or PowerPC hardware, you'll still be out in the cold for some of the packages, since some multimedia formats depend on proprietary software that's not available for those hardware platforms.
2. Changing the defaults
Ubuntu comes with a number of defaults that may or may not be to your liking. For example, the default editor is set to Nano, which isn't optimal if you're used to Vim.
The easy way to change this is to use the update-alternatives program, which maintains the symbolic links under /etc/alternatives that determine the default programs for FTP, system editor, rsh, Telnet, window manager, and so forth. Look under the /etc/alternatives directory to see what programs are managed.
To change the default editor, run sudo update-alternatives --config editor. You'll see a dialog like this:
There are 3 alternatives which provide `editor'.
Selection Alternative
-----------------------------------------------
1 /usr/bin/vim
2 /bin/ed
*+ 3 /bin/nano
Press enter to keep the default[*], or type selection number:
Just type 1 to switch to Vim. Note that on my system, I don't have Emacs or many other editors installed; if I did, the utility would offer the other editors as choices.
games_final_batlle.jpg
3. How to install packages
Most of the application software you'll want to add to your system will be available through the Ubuntu repositories using Synaptic, Adept, or another package management tool. What if you want to install something like Opera that is available as a package for Ubuntu, but isn't in the repositories?
In that case, download the application's Debian package (.deb) and right-click on the file. At the top of the context menu, you should see an option to open the package with the GDebi package installer. GDebi will provide a description of the package, what files are included, and other details about the package. The package installer also has a Install Package button; just click that and it will install the package. Note that the package installer also checks to verify whether it can install the package -- if it has dependencies that can't be satisfied, GDebi will give an error and refuse to install it.
If you prefer to install packages at the command line, just use sudo dpkg -i packagename.deb.
4. Sudo and gksudo
If you've used Linux for any amount of time, you might be used to running programs as root directly whenever you need to install packages, modify your system's configuration, and so on. Ubuntu employs a different model, however. The Ubuntu installer doesn't set up a root user -- a root account still exists, but it's set with a random password. Users are meant to do administration tasks using sudo and gksudo.
You probably already know how to use sudo -- just run sudo commandname . But what about running GUI apps that you want to run as root (or another user)? Simple -- use gksudo instead of sudo. For instance, if you'd like to run Ethereal as root, just pop open a run dialog box (Alt-F2) and use gksudo ethereal.
By the way, if you really must do work as root, you can use sudo su -, which will log you in as root. If you really, really want to have a root password that you know, so that you can log in as root directly (i.e., without using sudo), then run passwd when logged in as root, and set the password to whatever you want. I'd recommend using the pwgen package to create a secure password not only for root but for all your user accounts.
5. Add users to sudo
When you set up Ubuntu, it automatically adds the first user to the sudo group, allowing that user to make changes as the super user (root) by typing in their password. However, it doesn't automatically add additional users to the sudo group. If you want to give someone else superuser privileges on your shared system, you'll have to give them sudo access.
To add new users to sudo, the easiest way is to use the usermod command. Run sudo usermod -G admin username . That's all there is to it. However, if the user is already a member of other groups, you'll want to add the -a option, like so: sudo usermod -a -G admin username .
If you prefer the GUI way of doing things, go to System -> Administration -> Users and Groups. Select the user you want to add to sudo, and click Properties. Under the User privileges tab, check the box that says "Executing system administration tasks" and you'll be all set.
6. Adding a new desktop
Many users aren't sure what packages to add in order to run KDE or Xfce window managers on a stock Ubuntu system -- or what packages to add to run GNOME on Kubuntu or Xubuntu. You could add all of the necessary packages one at a time, but there's a much easier way to go about it.
To install all of the packages that come with one of the flavors of Ubuntu, such as Kubuntu, run apt-get install kubuntu-desktop (or edubuntu-desktop, xubuntu-desktop, or xubuntu-desktop).
If the GUI is more your style, the *desktop packages can be installed using Adept, Synaptic, or another package manager
7. How to reconfigure X.org
Most of the time, X.org -- that's the software that drives your video card and provides the foundation for the GUI, whether you're running GNOME, KDE, Xfce, or another window manager -- "just works" when you install Ubuntu. In fact, I'd wager that most Ubuntu users never even have to think about their video settings.
But, sometimes you need to reconfigure X.org because Ubuntu hasn't detected your video card and monitor properly, or maybe you've just purchased a shiny new video card and need to get it working with Ubuntu. Whatever the reason, it's good to know how to reconfigure X without having to edit your /etc/X11/xorg.conf by hand.
To run through the configuration, use dpkg-reconfigure xserver-xorg at the console or in a terminal window. Then you'll have a chance to specify your monitor and video card, the resolutions and color depths you want to run the server at, and so forth.
Since every setup is different, it's hard to give concrete advice for configuring X, but it's generally OK to accept the configuration defaults. Also, you'll be given a choice between Advanced, Medium, and Simple methods for giving your monitor's specifications. As a rule, it's probably best to go with Simple unless you really know what you're doing, or the Simple method doesn't work for you.
8. Log in automagically
By default, when you boot up the computer, Ubuntu will give you a login screen before you get to your X session. From a security perspective, this is a good idea, particularly in multi-user environments or in any situation where other people have physical access to your computer. Still, many users are used to just being logged in automatically, and don't want to fuss with logging in each time they reboot their desktop.
To set this in Ubuntu, go to System -> Administration -> Login Window. You'll need to provide your password, then you'll get the Login Window Preferences window with five tabs. Choose the Security tab and click Enable Automatic Login. If you have more than one regular user, make sure to specify which user should be logged in automatically.
Again, and I can't stress this enough, this is only a good idea for home computers where only one person has access to the computer. I don't recommend this for work computers or laptop/notebook computers, when someone else might have access to the machine.
9. Compiling from source
Ubuntu's package repository is huge, particularly when you factor in packages in the Universe and Multiverse repositories. However, many users find themselves needing to install packages from source, either because they want to use a newer package than is available in the repository, or they want to try something that's not in the Ubuntu repository at all.
If you want to install packages from source, you can use a few shortcuts to make life easier. First, you'll probably want to get the build-essential meta-package if you haven't installed any developer tools. Run sudo apt-get install build-essential; it will grab GCC, the Linux kernel headers, GNU Make, and some other packages that you'll probably need.
Next, if you're going to compile a package such as Gaim because a new version is out, you might be able to satisfy the new version's dependencies with the old version's dependencies. To do this, grab the package's build dependencies with sudo apt-get build-dep packagename . That will grab all of the development packages you need to build the package that's currently available in Ubuntu, and will probably satisfy dependencies for the new version you're compiling.
Finally, don't make install when you compile from source -- use CheckInstall instead. CheckInstall will create a Debian package and install it for you, so you can remove or upgrade the software more easily later on.
Grab CheckInstall with apt-get install checkinstall. After you've run ./configure ; make, just run sudo checkinstall and answer a few simple questions. Note that if you compile packages on AMD64, CheckInstall will select X86_64 as the architecture rather than amd64 -- which will cause the package install to fail, since Ubuntu expects amd64 as the architecture rather than X86_64.
By the way, the packages created by CheckInstall also make it easier to deploy the same package on several machines, if you happen to have several systems running Ubuntu. See Joe Barr's excellent CLI Magic feature on CheckInstall too.
10. A new kernel
Ubuntu will install a 386 kernel for x86 machines, which probably isn't what you'd want if you've got a Pentium II or better CPU. The 386 kernel is compiled to work with just about any x86 CPU, but extensions that appear in later CPUs can give your system a boost, if they're taken advantage of. To replace the kernel, open Synaptic or Adept and search for linux-image. You'll see several choices. Pick the one that best suits your CPU -- probably the linux-image-686 package for Pentium II and later CPUs, and linux-image-k7 for later AMD processors. Note that if you're using the AMD64 line (or Intel's x86-64 CPUs) you should be using the amd64 images.
Of course, once you install the new kernel, you'll need to reboot. Another benefit to the 686 kernels is that they have SMP support, which is a bonus for multi-core and Intel HyperThread CPUs.
If none of the tips cover questions that you have about Ubuntu, try checking out the Ubuntu wiki, forums, and mailing lists. As a rule, the Ubuntu users are a helpful lot, and you'll usually be able to find someone who's run into the same situation that you have questions about.
Now you have to add additional repositories , close synaptic package manager and type the following command in the terminal window (Application -> Accessories -> Terminal )
¨wget -q http://packages.medibuntu.org/medibuntu-key.gpg -O- | sudo apt-key add - ¨
and
¨sudo wget http://medibuntu.sos-sts.com/sources.list.d/feisty.list -O /etc/apt/sources.list.d/medibuntu.list
---------
SOURCE: http://ubuntuland.nireblog.com/post/2008/03/27/ten-tips-for-new-ubuntu-users
Adding the Medibuntu repos
Add Medibuntu to your sources.list, as well as its GPG key to your keyring. Make sure to use the correct sources.list that corresponds to your current distribution.
*
Ubuntu 8.04 "Hardy Heron":
sudo wget http://www.medibuntu.org/sources.list.d/hardy.list -O /etc/apt/sources.list.d/medibuntu.list
*
Ubuntu 7.10 "Gutsy Gibbon":
sudo wget http://www.medibuntu.org/sources.list.d/gutsy.list -O /etc/apt/sources.list.d/medibuntu.list
*
Ubuntu 7.04 "Feisty Fawn":
sudo wget http://www.medibuntu.org/sources.list.d/feisty.list -O /etc/apt/sources.list.d/medibuntu.list
*
Ubuntu 6.10 "Edgy Eft":
sudo wget http://www.medibuntu.org/sources.list.d/edgy.list -O /etc/apt/sources.list.d/medibuntu.list
*
Ubuntu 6.06 "Dapper Drake":
sudo wget http://www.medibuntu.org/sources.list.d/dapper.list -O /etc/apt/sources.list.d/medibuntu.list
Then, add the GPG Key:
sudo apt-get update && sudo apt-get install medibuntu-keyring && sudo apt-get update
*
Ubuntu 8.04 "Hardy Heron":
sudo wget http://www.medibuntu.org/sources.list.d/hardy.list -O /etc/apt/sources.list.d/medibuntu.list
*
Ubuntu 7.10 "Gutsy Gibbon":
sudo wget http://www.medibuntu.org/sources.list.d/gutsy.list -O /etc/apt/sources.list.d/medibuntu.list
*
Ubuntu 7.04 "Feisty Fawn":
sudo wget http://www.medibuntu.org/sources.list.d/feisty.list -O /etc/apt/sources.list.d/medibuntu.list
*
Ubuntu 6.10 "Edgy Eft":
sudo wget http://www.medibuntu.org/sources.list.d/edgy.list -O /etc/apt/sources.list.d/medibuntu.list
*
Ubuntu 6.06 "Dapper Drake":
sudo wget http://www.medibuntu.org/sources.list.d/dapper.list -O /etc/apt/sources.list.d/medibuntu.list
Then, add the GPG Key:
sudo apt-get update && sudo apt-get install medibuntu-keyring && sudo apt-get update
VMware Server On Ubuntu 8.04 Mini-Howto
When upgrading from Ubuntu 7.10 to 8.04 my VMware server stopped working, this what I had to do to get it up and running:
Needed if upgrading VMware installation:
sudo ./vmware-install.pl
VMware wont compile with the new kernel, use this patch:
wget http://vmkernelnewbies.googlegroups.com/web/vmware-any-any-update-116.tgz
tar -zxf vmware-any-any-update-116.tgz
cd vmware-any-any-update-116
Apply the patch:
sudo ./runme.pl
sudo vmware-config.pl
VMware console wont run without this:
cp /lib/libgcc_s.so.1 /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1
You might need gcc3.4 as well.
-----
SOURCE: http://www.howtoforge.com/vmware-server-on-ubuntu8.04
Needed if upgrading VMware installation:
sudo ./vmware-install.pl
VMware wont compile with the new kernel, use this patch:
wget http://vmkernelnewbies.googlegroups.com/web/vmware-any-any-update-116.tgz
tar -zxf vmware-any-any-update-116.tgz
cd vmware-any-any-update-116
Apply the patch:
sudo ./runme.pl
sudo vmware-config.pl
VMware console wont run without this:
cp /lib/libgcc_s.so.1 /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1
You might need gcc3.4 as well.
-----
SOURCE: http://www.howtoforge.com/vmware-server-on-ubuntu8.04
Monday, 18 August 2008
How to join Ubuntu/Samba to a Windows 2003 Active Directory domain
How to join Ubuntu/Samba to a Windows 2003 Active Directory domain
Ingredients:
*
A Windows network with an Active Directory server (like Windows Server 2003)
*
Ubuntu Linux 5.10 installed
*
TCP/IP setup properly (the Linux machine taking its address by DHCP from the Windows server)
*
No firewall yet on the Linux machine! First get it working, then secure it.
More info:
*
http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/domain-member.html
*
http://justlinux.com/forum/archive/index.php/t-118512.html
1. Installing
We assume that Ubuntu Linux has been installed.
Install the following packages with the Synaptic Package Manager. You may need to specify “universe” as an extra source for packages.
*
Samba (version 3):
o
samba
o
samba-common (installed by default)
o
smbclient (installed by default)
o
winbind
*
Kerberos:
o
krb5-config
o
krb5-user
*
... and any packages that might be needed to meet dependencies.
2. Edit configuration files
Edit the following configuration files. We assume the following:
*
The local DNS domain is mycompany.local
*
The Windows 2003 server is obelix.mycompany.local
/etc/samba/smb.conf
[global]
security = ADS
realm = MYCOMPANY.LOCAL
workgroup = mycompany
password server = obelix.mycompany.local
wins support = no
wins server = 10.0.20.202
invalid users = root
# Winbind settings
idmap uid = 10000-20000
idmap gid = 10000-20000
# For testing
debuglevel = 2
# A shared folder for testing purposes
[SharedFolder]
path = /home/onno2/Shared_Folder
available = yes
public = yes
writable = yes
force create mode = 0666
force directory mode = 0777
Make sure the path (/home/onno2/Shared_Folder or whatever you choose) exists and that the rights are set properly (chmod 777 or something similar)
/etc/krb5.conf
[libdefaults]
default_realm = MYCOMPANY.LOCAL
krb4_config = /etc/krb.conf
krb4_realms = /etc/krb.realms
kdc_timesync = 1
ccache_type = 4
forwardable = true
proxiable = true
# The following libdefaults parameters are only for Heimdal Kerberos.
v4_instance_resolve = false
v4_name_convert = {
host = {
rcmd = host
ftp = ftp
}
plain = {
something = something-else
}
}
[realms]
MYCOMPANY.LOCAL = {
kdc = obelix.mycompany.local
admin_server = obelix.mycompany.local
}
[domain_realm]
.mycompany.local = OBELIX.MYCOMPANY.LOCAL
mycompany.local = OBELIX.MYCOMPANY.LOCAL
[login]
krb4_convert = true
krb4_get_tickets = true
/etc/nsswitch
The only change here was adding winbind twice.
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.
passwd: compat winbind
group: compat winbind
shadow: compat
hosts: files dns
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
3. Start or restart services
/etc/init.d/samba restart
/etc/init.d/winbind restart
4. Join domain
net ads join -U administrator If this doesn’t work, check the logs in Linux (/var/log/samba/*) and Windows.
5. Test your setup
testparm to check if your smb.conf has a correct syntax.
kinit onno@MYCOMPANY.LOCAL test if kerberos works properly.
wbinfo -u should give a list of users.
wbinfo -g should give a list of groups.
getent passwd should give a list of users in the passwd style.
getent group should give a list of groups.
ls -ltr /var/log/samba gives a list of log files, sorted by time of last change.
smbclient -L -U onno should give you a list of available shares.
If this all works properly, try to access the share (/home/onno2/Shared_Folder) from any Windows machine in the domain by using network neighbourhood.
What's next?
If all works, try setting up your favorite firewall. I like Shorewall.
----
SOURCE: http://www.onnoot.com/wiki/how_to_join_ubuntu_samba_to_a_windows_2003_active_%20directory_domain
Ingredients:
*
A Windows network with an Active Directory server (like Windows Server 2003)
*
Ubuntu Linux 5.10 installed
*
TCP/IP setup properly (the Linux machine taking its address by DHCP from the Windows server)
*
No firewall yet on the Linux machine! First get it working, then secure it.
More info:
*
http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/domain-member.html
*
http://justlinux.com/forum/archive/index.php/t-118512.html
1. Installing
We assume that Ubuntu Linux has been installed.
Install the following packages with the Synaptic Package Manager. You may need to specify “universe” as an extra source for packages.
*
Samba (version 3):
o
samba
o
samba-common (installed by default)
o
smbclient (installed by default)
o
winbind
*
Kerberos:
o
krb5-config
o
krb5-user
*
... and any packages that might be needed to meet dependencies.
2. Edit configuration files
Edit the following configuration files. We assume the following:
*
The local DNS domain is mycompany.local
*
The Windows 2003 server is obelix.mycompany.local
/etc/samba/smb.conf
[global]
security = ADS
realm = MYCOMPANY.LOCAL
workgroup = mycompany
password server = obelix.mycompany.local
wins support = no
wins server = 10.0.20.202
invalid users = root
# Winbind settings
idmap uid = 10000-20000
idmap gid = 10000-20000
# For testing
debuglevel = 2
# A shared folder for testing purposes
[SharedFolder]
path = /home/onno2/Shared_Folder
available = yes
public = yes
writable = yes
force create mode = 0666
force directory mode = 0777
Make sure the path (/home/onno2/Shared_Folder or whatever you choose) exists and that the rights are set properly (chmod 777
/etc/krb5.conf
[libdefaults]
default_realm = MYCOMPANY.LOCAL
krb4_config = /etc/krb.conf
krb4_realms = /etc/krb.realms
kdc_timesync = 1
ccache_type = 4
forwardable = true
proxiable = true
# The following libdefaults parameters are only for Heimdal Kerberos.
v4_instance_resolve = false
v4_name_convert = {
host = {
rcmd = host
ftp = ftp
}
plain = {
something = something-else
}
}
[realms]
MYCOMPANY.LOCAL = {
kdc = obelix.mycompany.local
admin_server = obelix.mycompany.local
}
[domain_realm]
.mycompany.local = OBELIX.MYCOMPANY.LOCAL
mycompany.local = OBELIX.MYCOMPANY.LOCAL
[login]
krb4_convert = true
krb4_get_tickets = true
/etc/nsswitch
The only change here was adding winbind twice.
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.
passwd: compat winbind
group: compat winbind
shadow: compat
hosts: files dns
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
3. Start or restart services
/etc/init.d/samba restart
/etc/init.d/winbind restart
4. Join domain
net ads join -U administrator If this doesn’t work, check the logs in Linux (/var/log/samba/*) and Windows.
5. Test your setup
testparm to check if your smb.conf has a correct syntax.
kinit onno@MYCOMPANY.LOCAL test if kerberos works properly.
wbinfo -u should give a list of users.
wbinfo -g should give a list of groups.
getent passwd should give a list of users in the passwd style.
getent group should give a list of groups.
ls -ltr /var/log/samba gives a list of log files, sorted by time of last change.
smbclient -L
If this all works properly, try to access the share (/home/onno2/Shared_Folder) from any Windows machine in the domain by using network neighbourhood.
What's next?
If all works, try setting up your favorite firewall. I like Shorewall.
----
SOURCE: http://www.onnoot.com/wiki/how_to_join_ubuntu_samba_to_a_windows_2003_active_%20directory_domain
Sites to learn linux
http://www.faculty.ucr.edu/~tgirke/Documents/UNIX/linux_manual.html
http://www.cyberciti.biz/
http://www.linuxhomenetworking.com/
http://www.linsec.ca/Home
http://www.linuxworld.com/
http://www.linux-mag.com/
http://www.cyberciti.biz/
http://www.linuxhomenetworking.com/
http://www.linsec.ca/Home
http://www.linuxworld.com/
http://www.linux-mag.com/
Install acrobat reader on ubuntu
CODE:
1. echo "deb http://packages.medibuntu.org/ hardy free non-free" | sudo tee -a /etc/apt/sources.list
2. wget -q http://packages.medibuntu.org/medibuntu-key.gpg -O- | sudo apt-key add - && sudo apt-get update
3. sudo aptitude install acroread
1. echo "deb http://packages.medibuntu.org/ hardy free non-free" | sudo tee -a /etc/apt/sources.list
2. wget -q http://packages.medibuntu.org/medibuntu-key.gpg -O- | sudo apt-key add - && sudo apt-get update
3. sudo aptitude install acroread
Thursday, 14 August 2008
CD/DVD Burning in ubuntu
https://help.ubuntu.com/community/CdDvd/Burning?action=show&redirect=CdDvdBurning
http://ubuntuguide.org/wiki/Ubuntu:Edgy/CDDVDBurning#How_to_burn_Image_.28ISO.29_files_into_CD.2FDVD
http://ubuntuguide.org/wiki/Ubuntu:Edgy/CDDVDBurning#How_to_burn_Image_.28ISO.29_files_into_CD.2FDVD
Wednesday, 13 August 2008
Dual Monitor Setup On Ubuntu 7.10
This is a Howto about getting 2 (or with small modifications more) monitors working on Ubuntu 7.10 as a single big screen.
Get it to work
Connect one monitor to VGA and one to DVI on your computer.
If you see the desktop in mirror mode on both monitors after you connected the second one, then you just have to do some few steps to get it in extended mode.
Don't touch the GUI Setting tool (displayconfig-gtk) for monitors, it won't work correctly and may destroy your xorg.conf
To see the identifier for your monitors you can use:
xrandr -q
See sample output below:
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 3200 x 1200
VGA connected 1280x1024+0+0 (normal left inverted right) 376mm x 301mm
1280x1024 60.0*+ 84.8 75.0 59.9
1280x960 84.9 59.9
1152x864 74.8
1024x768 84.9 75.1 70.1 60.0
832x624 74.6
800x600 84.9 72.2 75.0 60.3 56.2
640x480 84.6 75.0 72.8 66.7 60.0
720x400 70.1
TMDS-1 connected 1280x1024+0+0 (normal left inverted right) 518mm x 324mm
1920x1200 60.0 +
1600x1200 59.9
1680x1050 60.0
1280x1024 75.0* 59.9
1440x900 75.0 59.9
1280x800 74.9 59.8
1024x768 75.1 60.0
800x600 75.0 60.3
640x480 75.0 60.0
720x400 70.1
VGA is the identifier for my old 17" TFT that is connected with a VGA cable and TMDS-1 is my new 24" monitor that is connected with a DVI cable.
To find out, which resolution you have to set for the virtual display, you can use following command instead of calculating yourself ;-)
xrandr --output TMDS-1 --auto --left-of VGA
Sample Output:
xrandr: screen cannot be larger than 1920x1920 (desired size 3200x1200)
This output tells you the needed size of the virtual desktop that you have to enter in xorg.conf.
sudo pico /etc/X11/xorg.conf
There you go all the way down to the section "screen" and add "Virtual {X} {Y}" below the mode line:
Section "Screen"
Identifier "Default Screen"
Device "Intel Corporation Integrated Graphics Controller"
Monitor "Acer X243W"
DefaultDepth 24
SubSection "Display"
Modes "1920x1200" "1680x1680" "1600x1200" "1440x1440"$
Virtual 3200 1200
EndSubSection
EndSection
Now you have to reload your X-Server:
press ctrl+alt+backspace
Log in again and enter the command from the beginning in a console window.
xrandr --output TMDS-1 --auto --left-of VGA
You should now have an extended desktop where the left side of the desktop is on the big 24" monitor and the right side on the old 17" monitor. For xrandr you could also use following arguments for positioning:
--pos {x}x{y}
--left-of output
--right-of output
--above output
--below output
You can add the xrandr command to session startup scripts to have it executed automatically.
Adding to session startup on gnome
Go to: System > Preferences (Einstellungen) > Session (Sitzungen).
Add a task called "dualhead setup" and use the command
xrandr --output TMDS-1 --auto --left-of VGA
or whatever xrandr command you have.
There exists one problem... It's not enabled before you log in. If you know in wich init file you can put the command, please leave a comment or send me a PM.
Get it to work
Connect one monitor to VGA and one to DVI on your computer.
If you see the desktop in mirror mode on both monitors after you connected the second one, then you just have to do some few steps to get it in extended mode.
Don't touch the GUI Setting tool (displayconfig-gtk) for monitors, it won't work correctly and may destroy your xorg.conf
To see the identifier for your monitors you can use:
xrandr -q
See sample output below:
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 3200 x 1200
VGA connected 1280x1024+0+0 (normal left inverted right) 376mm x 301mm
1280x1024 60.0*+ 84.8 75.0 59.9
1280x960 84.9 59.9
1152x864 74.8
1024x768 84.9 75.1 70.1 60.0
832x624 74.6
800x600 84.9 72.2 75.0 60.3 56.2
640x480 84.6 75.0 72.8 66.7 60.0
720x400 70.1
TMDS-1 connected 1280x1024+0+0 (normal left inverted right) 518mm x 324mm
1920x1200 60.0 +
1600x1200 59.9
1680x1050 60.0
1280x1024 75.0* 59.9
1440x900 75.0 59.9
1280x800 74.9 59.8
1024x768 75.1 60.0
800x600 75.0 60.3
640x480 75.0 60.0
720x400 70.1
VGA is the identifier for my old 17" TFT that is connected with a VGA cable and TMDS-1 is my new 24" monitor that is connected with a DVI cable.
To find out, which resolution you have to set for the virtual display, you can use following command instead of calculating yourself ;-)
xrandr --output TMDS-1 --auto --left-of VGA
Sample Output:
xrandr: screen cannot be larger than 1920x1920 (desired size 3200x1200)
This output tells you the needed size of the virtual desktop that you have to enter in xorg.conf.
sudo pico /etc/X11/xorg.conf
There you go all the way down to the section "screen" and add "Virtual {X} {Y}" below the mode line:
Section "Screen"
Identifier "Default Screen"
Device "Intel Corporation Integrated Graphics Controller"
Monitor "Acer X243W"
DefaultDepth 24
SubSection "Display"
Modes "1920x1200" "1680x1680" "1600x1200" "1440x1440"$
Virtual 3200 1200
EndSubSection
EndSection
Now you have to reload your X-Server:
press ctrl+alt+backspace
Log in again and enter the command from the beginning in a console window.
xrandr --output TMDS-1 --auto --left-of VGA
You should now have an extended desktop where the left side of the desktop is on the big 24" monitor and the right side on the old 17" monitor. For xrandr you could also use following arguments for positioning:
--pos {x}x{y}
--left-of output
--right-of output
--above output
--below output
You can add the xrandr command to session startup scripts to have it executed automatically.
Adding to session startup on gnome
Go to: System > Preferences (Einstellungen) > Session (Sitzungen).
Add a task called "dualhead setup" and use the command
xrandr --output TMDS-1 --auto --left-of VGA
or whatever xrandr command you have.
There exists one problem... It's not enabled before you log in. If you know in wich init file you can put the command, please leave a comment or send me a PM.
Ubuntu blogs
All Scrubbed Up - Ubuntu for Medicine in South Africa
Garam Chai - the occasinal post about Ubuntu
Free Software Blog - Most of the posts are about Ubuntu
Arcane Code - a few posts about Ubuntu
Bluebones- the occasional Ubuntu post
Debian Admin - A few posts about Ubuntu too
Everything Else - Some Linux/Ubuntu posts
GrumpyMole - About Ubuntu and Xubuntu
Terminally Incoherent - Ubuntu/Linux Posts
Hawknotes - The occasional Ubuntu Post
Move /home to it’s own partition
Posted by Carthik in administration, guides, ubuntu.
trackback
Having the “/home” directory tree on it’s own partition has several advantages, the biggest perhaps being that you can reinstall the OS (or even a different distro of Linux) without losing all your data. You can do this by keeping the /home partition unchanged and reinstalling the OS which goes in the “/” (root) directory, which can be on a seperate partition.
But you, like me, did not know this when you first installed Ubuntu, and have not created a new partition for “/home” when you first installed Ubuntu. Despair not, it is really simple to move “/home” to its own partition.
First, create a partition of sufficient size for your “/home” directory. You may have to use that new hard drive, or adjust/resize the existing partition on your current hard-drive to do this. Let me skip those details.
Next, mount the new partition:
$mkdir /mnt/newhome
$sudo mount -t ext3 /dev/hda5 /mnt/newhome
(You have to change the “hda5″ in the above to the correct partition label for the new partition. Also, the above assumes that the new partition you created is formatted as an ext3 partition. Change the “ext3″ to whatever filesystem the drive is formatted to.)
Now, Copy files over:
Since the “/home” directory will have hardlinks, softlinks, files and nested directories, a regular copy (cp) may not do the job completely. Therefore, we use something we learn from the Debian archiving guide:
$cd /home/
$find . -depth -print0 | cpio –null –sparse -pvd /mnt/newhome/
Make sure everything copied over correctly. You might have to do some tweaking and honing to make sure you get it all right, just in case.
Next, unmount the new partition:
$sudo umount /mnt/newhome
Make way for the new “home”
$sudo mv /home /old_home
Since we moved /home to /old_home, there is no longer a /home directory. So first we should recreate a new /home by:
sudo mkdir /home
Mount the new home:
$sudo mount /dev/hda5 /home
(Again, you have to change “hda5″ to whatever the new partition’s label is.)
Cursorily verify that everything works right.
Now, you have to tell Ubuntu to mount your new home when you boot. Add a line to the “/etc/fstab” file that looks like the following:
/dev/hda5 /home ext3 nodev,nosuid 0 2
(Here, change the partition label “hda5″ to the label of the new partition, and you may have to change “ext3″ to whatever filesystem you chose for your new “home”)
Once all this is done, and everything works fine, you can delete the “/old_home” directory by using:
$sudo rm -r /old_home
Michael, Russ and Magnus posted this solution on the ubuntu-users mailing list a few months ago.
trackback
Having the “/home” directory tree on it’s own partition has several advantages, the biggest perhaps being that you can reinstall the OS (or even a different distro of Linux) without losing all your data. You can do this by keeping the /home partition unchanged and reinstalling the OS which goes in the “/” (root) directory, which can be on a seperate partition.
But you, like me, did not know this when you first installed Ubuntu, and have not created a new partition for “/home” when you first installed Ubuntu. Despair not, it is really simple to move “/home” to its own partition.
First, create a partition of sufficient size for your “/home” directory. You may have to use that new hard drive, or adjust/resize the existing partition on your current hard-drive to do this. Let me skip those details.
Next, mount the new partition:
$mkdir /mnt/newhome
$sudo mount -t ext3 /dev/hda5 /mnt/newhome
(You have to change the “hda5″ in the above to the correct partition label for the new partition. Also, the above assumes that the new partition you created is formatted as an ext3 partition. Change the “ext3″ to whatever filesystem the drive is formatted to.)
Now, Copy files over:
Since the “/home” directory will have hardlinks, softlinks, files and nested directories, a regular copy (cp) may not do the job completely. Therefore, we use something we learn from the Debian archiving guide:
$cd /home/
$find . -depth -print0 | cpio –null –sparse -pvd /mnt/newhome/
Make sure everything copied over correctly. You might have to do some tweaking and honing to make sure you get it all right, just in case.
Next, unmount the new partition:
$sudo umount /mnt/newhome
Make way for the new “home”
$sudo mv /home /old_home
Since we moved /home to /old_home, there is no longer a /home directory. So first we should recreate a new /home by:
sudo mkdir /home
Mount the new home:
$sudo mount /dev/hda5 /home
(Again, you have to change “hda5″ to whatever the new partition’s label is.)
Cursorily verify that everything works right.
Now, you have to tell Ubuntu to mount your new home when you boot. Add a line to the “/etc/fstab” file that looks like the following:
/dev/hda5 /home ext3 nodev,nosuid 0 2
(Here, change the partition label “hda5″ to the label of the new partition, and you may have to change “ext3″ to whatever filesystem you chose for your new “home”)
Once all this is done, and everything works fine, you can delete the “/old_home” directory by using:
$sudo rm -r /old_home
Michael, Russ and Magnus posted this solution on the ubuntu-users mailing list a few months ago.
Tuesday, 12 August 2008
Install an RPM Package on Ubuntu Linux
Installing software on Ubuntu usually entails using Synaptic or by using an apt-get command from the terminal. Unfortunately, there are still a number of packages out there that are only distributed in RPM format.
There's a utility called Alien that converts packages from one format to the other. This doesn't always mean that an rpm will work on your system, though. You will need to install some prerequisite software packages in order to install alien, however. These packages include gcc and make.
Run this command to install alien and other necessary packages:
sudo apt-get install alien dpkg-dev debhelper build-essential
To convert a package from rpm to debian format, use this command syntax. The sudo may not be necessary, but we'll include it just in case.
sudo alien packagename.rpm
To install the package, you'll use the dpkg utility, which is the internal package management tool behind debian and Ubuntu.
sudo dpkg -i packagename.deb
The package should now be installed, providing it's compatible with your system.
There's a utility called Alien that converts packages from one format to the other. This doesn't always mean that an rpm will work on your system, though. You will need to install some prerequisite software packages in order to install alien, however. These packages include gcc and make.
Run this command to install alien and other necessary packages:
sudo apt-get install alien dpkg-dev debhelper build-essential
To convert a package from rpm to debian format, use this command syntax. The sudo may not be necessary, but we'll include it just in case.
sudo alien packagename.rpm
To install the package, you'll use the dpkg utility, which is the internal package management tool behind debian and Ubuntu.
sudo dpkg -i packagename.deb
The package should now be installed, providing it's compatible with your system.
Install WINE on Ubuntu Gutsy
Latest install instructions are always at: WineHQ.org
Add repository key:
wget -q http://wine.budgetdedicated.com/apt/387EE263.gpg -O- | sudo apt-key add -
Add repository to apt sources:
sudo wget http://wine.budgetdedicated.com/apt/sources.list.d/gutsy.list -O /etc/apt/sources.list.d/winehq.list
Update apt sources:
sudo apt-get update
Install WINE:
sudo apt-get install wine
The program menu then appears in Programs under Wine, or double-click a Windows/DOS .exe file.
Add repository key:
wget -q http://wine.budgetdedicated.com/apt/387EE263.gpg -O- | sudo apt-key add -
Add repository to apt sources:
sudo wget http://wine.budgetdedicated.com/apt/sources.list.d/gutsy.list -O /etc/apt/sources.list.d/winehq.list
Update apt sources:
sudo apt-get update
Install WINE:
sudo apt-get install wine
The program menu then appears in Programs under Wine, or double-click a Windows/DOS .exe file.
Howto: Create ISO File From CD/DVD in Ubuntu Gutsy
Have a CD or DVD lying around that you are sick of putting in the drive every time you need something on the disc How about just making an .iso file that you can mount as you need? Or maybe you just want a “master” copy of the media so you can create another copy at a future date.
At any rate it is rather easy to accomplish in Ubuntu:
sudo umount /dev/cdrom dd if=/dev/cdrom of=file.iso bs=1024
You can also do the same with folders:
mkisofs -r -o file.iso /location_of_folder/
Don’t forget to make a checksum:
md5sum file.iso > file.iso.md5
----------
Source: http://swik.net/Ubuntu/Only+Ubuntu/Howto:+Create+ISO+File+From+CD%2FDVD+in+Ubuntu+Gutsy/b3ibi
At any rate it is rather easy to accomplish in Ubuntu:
sudo umount /dev/cdrom dd if=/dev/cdrom of=file.iso bs=1024
You can also do the same with folders:
mkisofs -r -o file.iso /location_of_folder/
Don’t forget to make a checksum:
md5sum file.iso > file.iso.md5
----------
Source: http://swik.net/Ubuntu/Only+Ubuntu/Howto:+Create+ISO+File+From+CD%2FDVD+in+Ubuntu+Gutsy/b3ibi
Easy way of Mount/Unmount .iso Images in Ubuntu
Gmount-iso is a small tool written using PyGTK and Glade. It allows you to easily mount your cd images. This is a frontend to the ‘mount -o loop -t iso9660 foo.iso /mountpoint’ command.
Install gmountiso in Ubuntu
sudo aptitude install gmountiso
This will complete the installation.
Using gmountiso
If you want to open go to Applications—>System Tools—>Gmount-iso
Once it opens you should see the following screen here you can specify your .iso file and mount point where you want to mount.
Example for gmountiso
I am having dsl-4.0.iso image on my desktop and i want to mount this under dsl directory so i have menctioned all the details and click on mount
This will prompt for root password enter your root password and click on ok
Once it finished mounting you can see these details under mounted images
You can see the files and folders inside dsl directory
If you want to unmount just select the your mount point and click on Unmount
This is very simple and easy process
-----------
Source: http://www.ubuntugeek.com/easy-way-of-mountunmount-iso-images-in-ubuntu.html
Install gmountiso in Ubuntu
sudo aptitude install gmountiso
This will complete the installation.
Using gmountiso
If you want to open go to Applications—>System Tools—>Gmount-iso
Once it opens you should see the following screen here you can specify your .iso file and mount point where you want to mount.
Example for gmountiso
I am having dsl-4.0.iso image on my desktop and i want to mount this under dsl directory so i have menctioned all the details and click on mount
This will prompt for root password enter your root password and click on ok
Once it finished mounting you can see these details under mounted images
You can see the files and folders inside dsl directory
If you want to unmount just select the your mount point and click on Unmount
This is very simple and easy process
-----------
Source: http://www.ubuntugeek.com/easy-way-of-mountunmount-iso-images-in-ubuntu.html
Mount and Unmout ISO images without burning them
Some times you want to use iSO images without burning them.If you don’t want to waste your CD’s/DVD’s here is the simple possible solutions using these tips you can mount and unmount ISO images without burning them.
----------------
Source: http://www.ubuntugeek.com/mount-and-unmout-iso-images-without-burning-them.html
I know two possible solutions
1) Using Nautilus Scripts
2) Using kernel loop module
Now we will see each one in detailed
Using Nautilus Scripts
I am taking this tip from here first you need to download two scripts for mount iso images download from here for unmount iso images download from here
Once you have these two scripts you need to change the permissions using the following commands
sudo chmod +x /home/username/mount.sh
sudo chmod +x /home/username/unmount.sh
Now you need to copy them nautilus scripts
sudo mv /home/username/mount.sh ~/.gnome2/nautilus-scripts/
sudo mv /home/username/unmount.sh ~/.gnome2/nautilus-scripts/
That’s it now you are ready for mounting and unmounting your ISO images.
Example
Mount ISO Image
Now i have one ISO image if you want to mount you need to right click and select scripts —> mount-iso
Now it will prompt for root password and click ok
You can see the Mounter notification like the following
Here is the Successfully mounted message if you want to open this one click ok
This shows you available contents in mounted ISO image
Unmount ISO Image
Now i have one ISO image if you want to mount you need to right click and select scripts—>unmount-iso
Here is the Successfully Unmounted message
Using loop Kernel Module
First you need to make the directory to put the ISO into using the following command
sudo mkdir /media/isoimage
Now you need to add the loop module to your kernel.
What kernel loop module does?
I want to give brief introduction to kernel loop module.Using the module loop it is possible to mount a filesystem file. squashfs is a “loop” with (de)compression (Compressed Loopback Device) and it is possible to mount a compressed filesystem like a block device and seamlessly decompress its data while accessing it.
Use the following command to load loop module
sudo modprobe loop
Mount ISO Image
If you want to mount you need to use the following command
sudo mount debianetch.iso /media/isoimage/ -t iso9660 -o loop
In the above command you can replace debianetch.iso to your own iso image.
Now you should have your iso file mounted, and accessible from your desktop.
Unmount ISO Image
Unmount ISO Image Using the following command
sudo umount /media/isoimage
----------------
Source: http://www.ubuntugeek.com/mount-and-unmout-iso-images-without-burning-them.html
Install Real player on ubuntu gutsy
wget -c http://www.debian-multimedia.org/pool/main/r/realplay/realplayer_10.0.8-0.1_i386.deb
sudo dpkg -i realplayer_10.0.8-0.1_i386.deb
sudo dpkg -i realplayer_10.0.8-0.1_i386.deb
Monday, 11 August 2008
Install Adobe Flash player
Now that the trusted Synaptic had failed me, so I went ahead to install Flash plugin myself.
I went to the Adobe Flash for Linux site and downloaded the Flash Player tar.gz file. The file got downloaded to my Desktop.
From then the installation was as simple as these steps.
1. Open terminal. Applications->Accessories->Terminal
2. Change directory to Dektop by running the command "cd Desktop", without the quotes.
3. run the command "tar zxvf install_flash_player_9_linux.tar.gz".
4. This will create a folder/directory called "install_flash_player_9_linux".
5. "cd install_flash_player_9_linux".
6. Finally run the installer "./flashplayer-installer".
The installer will ask to close any running instance of Firefox and will install the Flash plugin.
You may verify the plugin by againg starting Firefox and typing "about:plugins" in the address bar
I went to the Adobe Flash for Linux site and downloaded the Flash Player tar.gz file. The file got downloaded to my Desktop.
From then the installation was as simple as these steps.
1. Open terminal. Applications->Accessories->Terminal
2. Change directory to Dektop by running the command "cd Desktop", without the quotes.
3. run the command "tar zxvf install_flash_player_9_linux.tar.gz".
4. This will create a folder/directory called "install_flash_player_9_linux".
5. "cd install_flash_player_9_linux".
6. Finally run the installer "./flashplayer-installer".
The installer will ask to close any running instance of Firefox and will install the Flash plugin.
You may verify the plugin by againg starting Firefox and typing "about:plugins" in the address bar
Thursday, 7 August 2008
Wednesday, 6 August 2008
Error when umount cd-rom: unmount: /cdrom device is busy
In order to solve this problem. Run umount command as follows:
# cd /
# umount /cdrom
If problem still continues then forcefully unmount the cdrom:
# cd /
# fuser -km /cdrom
OR try the following command:
# cd /
# umount -l /mnt
# cd /
# umount /cdrom
If problem still continues then forcefully unmount the cdrom:
# cd /
# fuser -km /cdrom
OR try the following command:
# cd /
# umount -l /mnt
Subscribe to:
Posts (Atom)