How to run windows programs and solutions for common faults in linux !! -- Linux general technology-Linux technology and application information. For details, refer to the following section. [I = s] This post was last edited by tangkunyin
For how to install fedora15, see: http://hi.baidu.com/tkystar
When I first installed fedora15, I couldn't connect to the network. After several days of searching, I finally found several ways to connect to the network!
At the same time, I also learned how to run and install some windows programs in linux. (Note: not all programs in windows can be installed and run with wine !!)
All of the following are tested and run under fedora15, so it is not necessarily applicable to other versions. If there are any discrepancies, I hope you can correct them and make common progress !!!
------ Author's note
========================================================== ========================================================== ========
Well, let's talk about how to run windows programs in linux (that is, running is actually a simulation, so not most software can do it )!
Download and install wine address: http://down.qiannao.com/space/file/tangkunyin/-4e0a-4f20-5206-4eab/Linux/linux-76f8-5173-8f6f-4ef6/wine-002d1.3.27.tar.bz2/.page
Installation Method:
# Cd download/
# Ls
Here we can see that you just downloaded the wine Package
# Tar-xvf wine Package name (do not copy it as it is)
# Remove cd wine Package to the folder
#./Tools/wineinstall (this can be copied)
A long installation process starts now. Wait for 30 minutes)
The installation is complete !!
Then test:
# Wine
If:
[Root @ tangkunyin ~] # Wine
Usage: wine PROGRAM [ARGUMENTS...] Run the specified program
Wine -- help Display this help and exit
Wine -- version Output version information and exit
The installation is successful! (In other cases, you can log out or restart it. If not, reinstall it)
After the installation is complete, enter the configuration phase:
# Winecfg
This will bring up a graphical Configuration window, see: http://download.csdn.net/detail/lifewodo/3592340
############
The usage is as follows:
# Wine program name
You can run it! Try it!
========================================================== ========================================================== ======================================
This part is about networking.
####################
Configure the network to several commands: nm-connection-editor
KDE bottom-to-dial: kppp
There are also a few Dialers that have never been used: minicom-s such as pppoe-setup
######################################## ################
I finally successfully connected to the Internet under the Virtual Machine (because I used the campus network of anteng Unicom and used his dial-up program, there is no modem configuration file in my/dev under fc, so kppp has never been successful !)
The following describes how to implement networking under a virtual machine: tutorial address 1
Download related tools: 3
**************************************** **************************************** **********************
**************************************** **************************************** **********************
The following is a question about the music player:
1. No music plug-in (unable to play media to) See: http://www.linuxsight.com/blog/1967
2. The file name in the music player is garbled!
In Debian Linux 3.2:
Apt-get install rhythmbox
In Ubuntu Linux 6.06:
Sudo install rhythmbox
For Fedora Linux 5:
Yum install rhythmbox gstreamer-plugins-uugly
For Mandriva Linux 2006:
Urpmi rhythmbox
Beep Media Player and Rhythmbox display mp3 file id3 Tag Information garbled, because the previously ugly id3v1 tag information does not describe character encoding, the subsequent id3v2 tag information already contains the character encoding. Starting from version 0.8.8, Rhythmbox can be used to set the environment variable stst_id3_tag_encoding = GBK to temporarily solve the mp3 tag garbled problem of id3v1. This method applies to Debian 3.1, Ubuntu 5.10, Fedora 4, and Mandriva 2006. The specific method is as follows:
Ststst_id3_tag_encoding = GBK
Add to the/etc/environment file (applicable to Debian/Ubuntu) or add this line
Export maid = GBK
Add to the. bashrc file of the main directory (applicable to all these Linux distributions ).
However, Rhythmbox has discarded this environment variable since version 0.9.3. Therefore, we recommend that you manually convert the id3tag of the mp3 file from id3v1 to id2v2 to solve this problem once and for all. You can use ID3iconv, a simple java program. First, make sure that you have installed the java environment. If your mp3 file is in the/mnt/music/directory, run this command to convert id3tag:
I did this:
(See http://hi.baidu.com/hywangyc/blo... 1405b0d9335a35.html)
A method that does not need to modify the label encoding, the principle should be to let the player first try to use GBK to decode the label, and then use the UTF-8 to decode, in fact, it is to adjust the decoding order. The specific method is to create a shell under the/etc/profile. d/folder, the content is also very simple:
The file name is random, for example, gst. sh. Log out and then log on to make the sh script take effect (step 1, # cd/etc/profile. d 2, # sh gst. sh ). The important step is to allow Rhythmbox to re-read the information of the music file. I tried to move the music folder somewhere else. After the player was started, the file information recorded in the past was indeed gone. But when I move the folder back, it's still garbled! This is not to say that this method is useless, but Rhythmbox is lazy. It finds that the file recorded in the original database appears again, and the original database is used. The correct method is to delete the database information of Rhythmbox in the home directory ~ /. Local/share/all files in rhythmbox. After the player is deleted, restart the player and the tag will not be garbled :-)
**************************************** **************************************** ***************************
This section describes how to log on with a ROOT user over fedora10:
Note: Since fedora10, the ROOT user is not allowed to log on by default. To enable the user to log on, modify the file as follows:
1. First, su
2. Then vi or gedit/etc/pam. d/TPD
3. comment out the line # auth required pam_succeed_if.so user! = Root quiet
4. Then: Save and exit wq.
5. log out of the current graphic interface. Now you can use root to log on to your GUI. However, we recommend that you do not use the root logon GUI for security purposes.
6. You can also use gedit to modify it. You must have the root permission.
How to log on to fedora as a root user
Since February 10, February 10 prohibits the use of root to log on to the system. This may be due to security considerations. After all, the root permission is too large, and the outsourcecode enhances system security, in addition, a normal account can run normally enough for the user's application. If the root permission is required, the system will automatically prompt you to enter the password. It can be said that the security considerations are quite perfect.
What should I do if I want to log on to the system as root? The solution is as follows:
Enter the su command in the terminal and the root password so that I have the root operation permission in the terminal. Then we can use the gdit command to modify it.
Gdit/etc/pam. d/TPD
In this section, "auth required pam_succeed_if.so user! = Root quiet "+ # comment out.
The same gdit/etc/pam. d/TPD-password
Also in auth required pam_succeed_if.so user! = Add the # comment before root quiet
After saving the file, we can restart or log out of the computer once and then log on to the system as the root user.
Of course, if you use the vi Command, this is the most convenient.
**************************************** **************************************** ***************************
This part is system garbage cleanup (this part is found online and may not be suitable for your machine, so you may need to modify it as appropriate. How to modify it for your own research)
1. Run the following command to clear system garbage
Sudo apt-get autoclean -- clear old software caches
Sudo apt-get clean -- clear all software caches
Sudo apt-get autoremove -- delete isolated software that is no longer used by the System
2. Clear the cache files of opera firefox:
Ls ~ /. Opera/cache4
Ls ~ /. Mozilla/firefox/×. default/Cache
3. Clear isolated packages in Linux:
Use: gtkorphan sudo apt-get install gtkorphan-y in Gui
Run deborphan sudo apt-get install deborphan-y in the terminal command.
4. Uninstall: tracker
This will not only generate a large number of cache files, but also affect the boot speed. So in the new
You just need to delete it.
5. Delete unnecessary kernels:
Terminal: dpkg -- get-selections | grep linux
Kernel files with images
Delete the old kernel file:
Sudo apt-get remove Kernel File name (e.g.: linux-image-2.6.27-2-generic)
Check the current kernel: uname-
Appendix:
Temporary File directory of the package:
/Var/cache/apt/archives
If the download is not completed
/Var/cache/apt/archives/partial
######################################## ##########################
The following is a solution to the Linux Crash:
Anyone familiar with Linux systems knows that Linux is a relatively stable system, and there are fewer crashes in Linux than windows, but they do not, what should we do when it appears?
A method is introduced ~ It is easy to let Linux Crash, but the hard thing is how to safely remove it from the dead state after the crash.
There are many cases of Linux crashes. The most common problem is that the system load is too high. For example, the fork bomb introduced last time is based on this principle. In addition, it can also run programs (such as virtual machines) that consume a lot of memory, which will quickly increase the system load. If the system load is too high, the card will die. The faster the solution, the better! At this point, you must remember that you can no longer rely on anything from a graphical interface, such as Gnome System Monitor (this is my ignorance from Windows ......), This will only aggravate this stuck situation. What should we do?
Don't be afraid. Linux didn't need a graphical interface at first, because it has a very powerful text interface. By Ctrl-Alt-F1 (F1-F6 can generally be), and then wait for a while, will switch to tty, that is, the so-called text interface. In this case, you need to log on with your username and password. Note: The keyboard input speed may be slow, but it should be tolerable. Enter top and press enter at the end of the prompt. A dynamic table is displayed, which lists the processes that consume the most resources. Refresh it once or twice, press q to exit, and then enter kill. You can see the PID in top. At this time, it should be much faster. If you find that it has not ended successfully, enter kill-KILL again. This time it will basically be okay.
In addition to the above situation, some underlying software bugs may also cause some strange crashes. Recently, some of my colleagues force the ext4 partition to be hurt due to an inexplicable force restart on the crash. (Finally, sysreccd is fixed. It seems that the partition table is partially damaged.) It is said that the dead mouse does not respond. In general, crashes caused by high system loads may also respond to the terrible keyboard. Some people say that if the system crashes to the keyboard and does not respond, "the load is infinite ", some people also say that this may be caused by problems in the combination of X Server and driver. But what should we do if this happens?
OK. This is the method that we learned today, called reisub. This method can be used to safely restart the computer in various situations. You can find a key called "Sys Rq" on the keyboard. On the keyboard of the platform, the key is usually used together with the Prt SC, and may be in another location in the notebook, such as Delete. Take a Taiwan machine as an example. to use this method, press Alt-Print (Sys Rq), and then press the keys reisub in sequence. After pressing the keys, the system restarts.
The following explains this method: in fact, Sys Rq is a kind of thing called a system request. Holding down Alt-Print is equivalent to holding down the Sys Rq key, at this time, everything input will be processed directly by the Linux kernel, which can perform many low-level operations. At this time, each letter in the reisub is an independent operation, which indicates:
UnRaw grabs the keyboard control from X Server
TErminate sends SIGTERM signals to all processes so that they can solve the problem on their own.
KIll sends a SIGKILL signal to all processes and forces them to close immediately
Sync synchronizes all data to the disk
Unmount: Mount all partitions in read-only mode.
ReBoot restart
The order of the six letters is wrong. How can we remember it? Here we provide a method that is better thought by one individual: The word busier (busy comparison level, more busy.
This is basically the case. It is rare for a Linux server to crash. Now we can solve the problem with security. How good is it ~
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.