link:
The purpose of Linux Mint is to produce a modern, elegant and comfortable operating system which is both powerful and easy to use.
Started in 2006, Linux Mint is now the 4th most widely used home operating system behind Microsoft Windows, Apple Mac OS and Canonical’s Ubuntu.
Some of the reasons for the success of Linux Mint are:
- It works out of the box, with full multimedia support and is extremely easy to use.
- It’s both free of cost and open source.
- It’s community-driven. Users are encouraged to send feedback to the project so that their ideas can be used to improve Linux Mint.
- Based on Debian and Ubuntu, it provides about 30,000 packages and one of the best software managers.
- It’s safe and reliable. Thanks to a conservative approach to software updates, a unique Update Manager and the robustness of its Linux architecture, Linux Mint requires very little maintenance (no regressions, no antivirus, no anti-spyware…etc).
Download Linux Mint 9 Isadora
Information
Our latest release is Linux Mint 9, codename “Isadora”.
Read the Linux Mint 9 User Guide
See what’s new in Linux Mint 9
Read the release notes
Download links
Main edition (Gnome desktop)
Live CD 32-bit 64-bit The standard version
Live DVD 32-bit 64-bit Contains additional software such as Java, VLC, F-Spot, OpenOffice.org-base, Samba, additional wallpapers and ttf-dejaVu fonts
OEM installation disks 32-bit 64-bit For manufacturers, to pre-install Linux Mint on computers without setting up a user account.
USA/Japan distribution disks 32-bit 64-bit For magazines, companies and distributors in the USA, Japan and countries where the legislation allows patents to apply to software and distribution of restricted technologies may require the acquisition of 3rd party licenses.
Other editions
KDE Live DVD 32-bit 64-bit An edition using the KDE desktop
Xfce Live CD 32-bit 64-bit An edition using the Xfce desktop
Fluxbox Live CD 32-bit An edition using the Fluxbox desktop
LXDE Live CD 32-bit An edition using the LXDE desktop
By: phuchungbhutia on September 7, 2010
at 12:14 pm
problem:
E: Could not get lock /var/cache/apt/archives/lock – open (11 Resource temporarily unavailable)
E: Unable to lock the download directory
solution:
sudo rm /var/cache/apt/archives/lock
By: phuchungbhutia on September 7, 2010
at 12:15 pm
How to fix lock /var/lib/dpkg/lock – open (11 Resource temporarily unavailable) Error
link:
http://www.ubuntugeek.com/how-to-fix-lock-varlibdpkglock-open-11-resource-temporarily-unavailable-error.html
By: phuchungbhutia on September 7, 2010
at 12:16 pm
HOWTO: Setup Samba peer-to-peer with Windows
link:
http://ubuntuforums.org/showthread.php?t=202605
video:
Code:
sudo apt-get install samba
then change workgroup
Code:
sudo gedit /etc/samba/smb.conf
NOTE: If you’re on KDE replace “gedit” with “kate”
Copy / Paste the contents of the code-section below into your editor and read on …
Code:
[global]
; General server settings
netbios name = YOUR_HOSTNAME
server string =
workgroup = YOUR_WORKGROUP
announce version = 5.0
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192
passdb backend = tdbsam
security = user
null passwords = true
username map = /etc/samba/smbusers
name resolve order = hosts wins bcast
wins support = yes
printing = CUPS
printcap name = CUPS
syslog = 1
syslog only = yes
; NOTE: If you need access to the user home directories uncomment the
; lines below and adjust the settings to your hearts content.
;[homes]
;valid users = %S
;create mode = 0600
;directory mode = 0755
;browseable = no
;read only = no
;veto files = /*.{*}/.*/mail/bin/
; NOTE: Only needed if you run samba as a primary domain controller.
; Not needed as this config doesn’t cover that matter.
;[netlogon]
;path = /var/lib/samba/netlogon
;admin users = Administrator
;valid users = %U
;read only = no
; NOTE: Again – only needed if you’re running a primary domain controller.
;[Profiles]
;path = /var/lib/samba/profiles
;valid users = %U
;create mode = 0600
;directory mode = 0700
;writeable = yes
;browseable = no
; NOTE: Inside this place you may build a printer driver repository for
; Windows – I’ll cover this topic in another HOWTO.
[print$]
path = /var/lib/samba/printers
browseable = yes
guest ok = yes
read only = yes
write list = root
create mask = 0664
directory mask = 0775
[printers]
path = /tmp
printable = yes
guest ok = yes
browseable = no
; Uncomment if you need to share your CD-/DVD-ROM Drive
;[DVD-ROM Drive]
;path = /media/cdrom
;browseable = yes
;read only = yes
;guest ok = yes
[MyFiles]
path = /media/samba/
browseable = yes
read only = no
guest ok = no
create mask = 0644
directory mask = 0755
force user = YOUR_USERNAME
force group = YOUR_USERGROUP
Ok, I already mentioned that there are a few simple things you may need to tweak; so here they are:
-> netbios name = YOUR_HOSTNAME
Replace “YOUR_HOSTNAME” with your desired hostname (don’t use spaces!). Best pratice would be to use the same name you configured upon installation.
Example:
netbios name = DAPPER
-> workgroup = YOUR_WORKGROUP
Replace “YOUR_WORKGROUP” with the name of your workgroup, but make sure you’re using the same as configured in Windows.
To find out the Workgroup name in Windows follow these steps:
- Click “START”
- Click “Control Panel”
- Click “System”
- Click the 2nd Tab entitled “Computername” and find the name of the Workgroup there.
By: phuchungbhutia on September 7, 2010
at 12:18 pm
link:
https://help.ubuntu.com/community/Grub2#Reinstalling%20GRUB%202
Reinstalling GRUB 2
There may be times when a user needs to either move or reinstall a GRUB 2 installation. GRUB 2 needs to be reinstalled when a user is presented with a blank screen with only the word “GRUB”, no prompt, and no ability to enter commands. This often happens when the MBR of the booting device is altered and GRUB 2 is removed, such as when Windows is installed after Ubuntu. Additionally, if a user cannot boot into an operating system at all, even using the rescue mode mode, a complete reinstallation of GRUB 2 may be necessary.
Reinstalling from LiveCD
If you cannot boot from GRUB 2 review the section Boot Problems and Rescue Mode. If a reinstall becomes necessary follow these instructions. Two methods are presented; both require booting from a LiveCD (Ubuntu 9.10, Karmic Koala or later version). If the first method does not work, follow the second method, which is more complex and contains more options and instructions.
SIMPLEST – Copy GRUB 2 Files from the LiveCD
This is a quick and simple method of restoring a broken system’s GRUB 2 files. The terminal is used for entering commands and the user must know the device name/partition of the installed system (sda1, sdb5, etc). The problem partition is located and mounted from the LiveCD. The files are then copied from the LiveCD libraries to the proper locations and MBR. It requires the least steps and fewer command line entries than the following methods.
Boot to the LiveCD Desktop (Ubuntu 9.10 or later).
Open a terminal by selecting Applications, Accessories, Terminal from the menu bar.
Determine the partition with the Ubuntu installation. The fdisk option “-l” is a lowercase “L”.
sudo fdisk -l
If the user isn’t sure of the partition, look for one of the appropriate size or formatting.
Running sudo blkid may provide more information to help locate the proper partition, especially if the partitions are labeled. The device/drive is designated by sdX, with X being the device designation. sda is the first device, sdb is the second, etc. For most users the MBR will be installed to sda, the first drive on their system. The partition is designated by the Y. The first partition is 1, the second is 2. Note the devices and partitions are counted differently.
Mount the partition containing the Ubuntu installation.
sudo mount /dev/sdXY /mnt
Example: sudo mount /dev/sda1 Note: If the user has a separate /boot partition, this must be mounted to /mnt/boot Note: If the user has a separate /home partition, this must be mounted to /mnt/home. Encrypted home partitions should work.
Run the grub-install command as described below. This will reinstall the GRUB 2 files on the mounted partition to the proper location and to the MBR of the designated device.
sudo grub-install –root-directory=/mnt/ /dev/sdX
Example: sudo grub-install –root-directory=/mnt/ /dev/sda
Reboot
Refresh the GRUB 2 menu with sudo update-grub
By: phuchung bhutia on September 15, 2010
at 10:29 am
CHROOT GRUB UPDATING AFTER WINDOWS & INSTALLED
This method of installation uses the chroot command to gain access to the broken system’s files. Once the chroot command is issued, the LiveCD treats the broken system’s / as its own. Commands run in a chroot environment will affect the broken systems filesystems and not those of the LiveCD.
Boot to the LiveCD Desktop (Ubuntu 9.10 or later). Please note that the Live CD must be the same as the system you are fixing – either 32-bit or 64-bit (if not then the chroot will fail).
Open a terminal – Applications, Accessories, Terminal.
Determine your normal system partition – (the switch is a lowercase “L”)
sudo fdisk -l
If you aren’t sure, run
df -Th. Look for the correct disk size and ext3 or ext4 format.
Mount your normal system partition:
Substitute the correct partition: sda1, sdb5, etc.
sudo mount /dev/sdXX /mnt # Example: sudo mount /dev/sda1 /mnt
Only if you have a separate boot partition:
sdYY is the /boot partition designation (for example sdb3)
sudo mount /dev/sdYY /mnt/boot
Mount the critical virtual filesystems:
sudo mount –bind /dev /mnt/dev
sudo mount –bind /dev/pts /mnt/dev/pts
sudo mount –bind /proc /mnt/proc
sudo mount –bind /sys /mnt/sys
Chroot into your normal system device:
sudo chroot /mnt
If there is no /boot/grub/grub.cfg or it’s not correct, create one using
update-grub
Reinstall GRUB 2:
Substitute the correct device – sda, sdb, etc. Do not specify a partition number.
grub-install /dev/sdX
Verify the install (use the correct device, for example sda. Do not specify a partition): sudo grub-install –recheck /dev/sdX
Exit chroot: CTRL-D on keyboard
Unmount virtual filesystems:
sudo umount /mnt/dev/pts
sudo umount /mnt/dev
sudo umount /mnt/proc
sudo umount /mnt/sys
If you mounted a separate /boot partition:
sudo umount /mnt/boot
Unmount the LiveCD’s /usr directory:
sudo umount /mnt/usr
Unmount last device:
sudo umount /mnt
Reboot.
sudo reboot
Post-Restoration Commands
Once the user can boot to a working system, try to determine why the system failed to boot. The following commands may prove useful in locating and/or fixing the problem.
To refresh the available devices and settings in /boot/grub/grub.cfg
sudo update-grub
To look for the bootloader location.
grub-probe -t device /boot/grub
To install GRUB 2 to the sdX partition’s MBR (sda, sdb, etc.)
sudo grub-install /dev/sdX
To recheck the installation. (sda, sdb, etc.)
sudo grub-install –recheck /dev/sdX
By: phuchung bhutia on September 15, 2010
at 10:31 am
had this problem of missing bootloader for widows 7 …
error like … vstldr.img missing (fd0)
had to
repair using dvd …
boot dvd
choose repair
then choose
command prompt
type:
bootsect.exe /nt60 SYS /force
then … it starts working again
By: phuchung bhutia on September 15, 2010
at 12:56 pm