Senin, 31 Maret 2014

setting user and group, Usb virtualbox ubuntu

masuk dulu users and groups

sn ink epson

cyan
6UN-Z4S-78N-3MEJ

YELLOW
2A5-QSK-PKT-CWC3

MAGENTA

7TN-5RA-9RF-DXE5

BLACK

FUP-P9L-Y36-7AMZ






































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































Kamis, 27 Maret 2014

uninstall Draftsight in ubuntu

sudo dpkg -r dassault-systemes-draftsight
 
 sudo apt-get autoremove

Selasa, 25 Maret 2014

memindahkan data email dari outlook atau outlook express ke thuderbrid

1. siapkan os windows7 unlimited
2. instal thunderbrid
3. import dari thuderbrid cari forder backup dari outlook maupun outlook express
4. kalau mau improt ke thuderbrid linux ya cari hasil improtnya tadi lalu copas aja ke thunderbrid linux ( bikin folder namanya yang sama)

sharing printer ubuntu

setting saja disini  http://localhost:631/admin.

jangan lupa user & passwd nya

 copasnya

CUPS - Print Server

The primary mechanism for Ubuntu printing and print services is the Common UNIX Printing System (CUPS). This printing system is a freely available, portable printing layer which has become the new standard for printing in most Linux distributions.
CUPS manages print jobs and queues and provides network printing using the standard Internet Printing Protocol (IPP), while offering support for a very large range of printers, from dot-matrix to laser and many in between. CUPS also supports PostScript Printer Description (PPD) and auto-detection of network printers, and features a simple web-based configuration and administration tool.

Installation

To install CUPS on your Ubuntu computer, simply use sudo with the apt-get command and give the packages to install as the first parameter. A complete CUPS install has many package dependencies, but they may all be specified on the same command line. Enter the following at a terminal prompt to install CUPS:
sudo apt-get install cups

Upon authenticating with your user password, the packages should be downloaded and installed without error. Upon the conclusion of installation, the CUPS server will be started automatically.
For troubleshooting purposes, you can access CUPS server errors via the error log file at: /var/log/cups/error_log. If the error log does not show enough information to troubleshoot any problems you encounter, the verbosity of the CUPS log can be increased by changing the LogLevel directive in the configuration file (discussed below) to "debug" or even "debug2", which logs everything, from the default of "info". If you make this change, remember to change it back once you've solved your problem, to prevent the log file from becoming overly large.

Configuration

The Common UNIX Printing System server's behavior is configured through the directives contained in the file /etc/cups/cupsd.conf. The CUPS configuration file follows the same syntax as the primary configuration file for the Apache HTTP server, so users familiar with editing Apache's configuration file should feel at ease when editing the CUPS configuration file. Some examples of settings you may wish to change initially will be presented here.
[Tip]
Prior to editing the configuration file, you should make a copy of the original file and protect it from writing, so you will have the original settings as a reference, and to reuse as necessary.
Copy the /etc/cups/cupsd.conf file and protect it from writing with the following commands, issued at a terminal prompt:
sudo cp /etc/cups/cupsd.conf /etc/cups/cupsd.conf.original
sudo chmod a-w /etc/cups/cupsd.conf.original

  • ServerAdmin: To configure the email address of the designated administrator of the CUPS server, simply edit the /etc/cups/cupsd.conf configuration file with your preferred text editor, and add or modify the ServerAdmin line accordingly. For example, if you are the Administrator for the CUPS server, and your e-mail address is 'bjoy@somebigco.com', then you would modify the ServerAdmin line to appear as such:
    ServerAdmin bjoy@somebigco.com
    

  • Listen: By default on Ubuntu, the CUPS server installation listens only on the loopback interface at IP address 127.0.0.1. In order to instruct the CUPS server to listen on an actual network adapter's IP address, you must specify either a hostname, the IP address, or optionally, an IP address/port pairing via the addition of a Listen directive. For example, if your CUPS server resides on a local network at the IP address 192.168.10.250 and you'd like to make it accessible to the other systems on this subnetwork, you would edit the /etc/cups/cupsd.conf and add a Listen directive, as such:
    Listen 127.0.0.1:631           # existing loopback Listen
    Listen /var/run/cups/cups.sock # existing socket Listen
    Listen 192.168.10.250:631      # Listen on the LAN interface, Port 631 (IPP)
    

    In the example above, you may comment out or remove the reference to the Loopback address (127.0.0.1) if you do not wish cupsd to listen on that interface, but would rather have it only listen on the Ethernet interfaces of the Local Area Network (LAN). To enable listening for all network interfaces for which a certain hostname is bound, including the Loopback, you could create a Listen entry for the hostname socrates as such:
    Listen socrates:631  # Listen on all interfaces for the hostname 'socrates'
    

    or by omitting the Listen directive and using Port instead, as in:
    Port 631  # Listen on port 631 on all interfaces
    
For more examples of configuration directives in the CUPS server configuration file, view the associated system manual page by entering the following command at a terminal prompt:
man cupsd.conf

[Note]
Whenever you make changes to the /etc/cups/cupsd.conf configuration file, you'll need to restart the CUPS server by typing the following command at a terminal prompt:
sudo /etc/init.d/cups restart

Web Interface

[Tip]
CUPS can be configured and monitored using a web interface, which by default is available at http://localhost:631/admin. The web interface can be used to perform all printer management tasks.
In order to perform administrative tasks via the web interface, you must either have the root account enabled on your server, or authenticate as a user in the lpadmin group. For security reasons, CUPS won't authenticate a user that doesn't have a password.
To add a user to the lpadmin group, run at the terminal prompt:
sudo usermod -aG lpadmin username

Further documentation is available in the Documentation/Help tab of the web interface.

memindahkan contak adreass book thuderbrid di ubuntu

1. jika masih sempat export aja ke csv atau ldif lalu import lagi di thuderbrid baru
2 jika sudah rusak thunderbridnya cari saja file *.mab, backup dan copy ke thunderbird baru

Senin, 24 Maret 2014

sharing folder di partisi kedua di linux ubuntu

1. instal dulu samba di linux
2. partisi hardisk ke  ext4 jangan ntfs atau fat32
3. lalu configure sambanya sharing nya create user jangan everyone

jangan lupa edit forder permition di linux kalau susah instal Eiciel lewat software ubuntu


Kamis, 20 Maret 2014

instal thunderbrid di lubuntu lxle

1. hapus dulu clow mail lewat lubuntu software centre
2 sudo apt-get update
3 sudo apt-get install thunderbird

Rabu, 19 Maret 2014

instal.sh ubuntu

masuk ke direktori folder

  1. Tried; sudo ./install.sh
    sudo: ./install.sh: command not found
  2. Trying to remount the installation disk with exec permission;
    mount /media/user/IFORTRAN2011 -o remount,exec
  3. Trying to change install.sh to executable;
    chmod +x ./install.sh
  4. Tried; su -c 'install.sh'
with root:
bash: install.sh: command not found
with user:
Password: 
su: Authentication failure
and I am sure the password is true. (If it is the same with my user password)
5 . I copied the disk into a folder than compressed it into
file.tar.gz
than extract it with
tar xvzf file.tar.gz
then tried everthing again. No luck.
After I did chmod +x ./install.sh when I look the permissions with: ls -l ./install.sh it still gives: -rw------- 1 user user 14758 Oct 7 2010 ./install.sh
Thanks for any help.

Kamis, 13 Maret 2014

Install Java JDK

Install Java JDK

The easy way

Easiest way to install the JDK is to do it with the Web Up8 Oracle Java OOS, however it is believed that this PPA is sometimes out of date. Also note the dangers of using a PPA.
This installs JDK 7 (which includes Java JDK, JRE and the Java browser plugin).
sudo apt-get install python-software-properties
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java7-installer
 
lebih lenkap
 link http://askubuntu.com/questions/56104/how-can-i-install-sun-oracles-proprietary-java-6-7-jre-or-jdk 

Selasa, 11 Maret 2014

masalah hardisk ubuntu

Error writing on HDD

Hello fellow Linux users, I am running Ubuntu 12.04 32-bit with Xubuntu DE and recently got a hold of Maxtor 6Y080M0 SATA HDD and I formatted it to ext4 filesystem using Gparted tool. But since then I have a problem, I cannot write anything on it nor can I format it. When I try to mount it from Disks tool this is what it says:
Code:
Error mounting system-managed device /dev/sdb1: Command-line `mount "/mnt/088464b0-321b-4690-bde7-9850831f22d4"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb1,       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so


 (udisks-error-quark, 0)
I have no idea anymore why is it not working, so please give me some advice.
My regards, stay brutal.
Last edited by LinuxUser666; October 3rd, 2013 at 06:47 PM.
Avoid the Gates of Hell. Use Linux.
#2
slickymaster's Avatar
slickymaster is offline Alea Jacta Est
Join Date
Nov 2012
Location
Halloween Town
Beans
Hidden!
Distro
Xubuntu Development Release

Re: Error writing on HDD

Quote Originally Posted by LinuxUser666 View Post
Hello fellow Linux users, I am running Ubuntu 12.04 32-bit with Xubuntu DE and recently got a hold of Maxtor 6Y080M0 SATA HDD and I formatted it to ext4 filesystem using Gparted tool. But since then I have a problem, I cannot write anything on it nor can I format it. When I try to mount it from Disks tool this is what it says:
Code:
Error mounting system-managed device /dev/sdb1: Command-line `mount "/mnt/088464b0-321b-4690-bde7-9850831f22d4"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb1,       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so


 (udisks-error-quark, 0)
I have no idea anymore why is it not working, so please give me some advice.
My regards, stay brutal.
Your error message indicates a filesystem failure, which can be caused by several reasons and it's causing it's refuse to mount. First you have to figure out what partition you're dealing with, by running
Code:
sudo fdisk -l
The above will list all the partitions on all the drives in your computer. Then make sure your superblock is the problem, by starting a filesystem check, replacing xxx with your partition name
Code:
sudo fsck.ext4 -v /dev/xxx
If your superblock is corrupt, the output will look something like this
The superblock could not be read or does not describe a correct ext4 filesystem. If the device is valid and it really contains an ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>
You'll have to find where your superblock backups are kept
Code:
sudo mke2fs -n /dev/xxx
Down at the bottom of the output, you should see a list of the backups, something like this
Code:
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
Restore the superblock from the backup, again replacing xxx with your partition name, and block_number with the first backup superblock
Code:
sudo e2fsck -b block_number /dev/xxx
Reboot, and the superblock should be fixed. If it’s not, repeat the steps, but restore a different backup superblock.