Adaptation of the operating system linux mandrake 10 (2)

Adaptation of the operating system linux mandrake 10 (2)


Next Generation Hackers Group | written by Rel4nium | 06/05/2005 (updated 10/11/05)

Many thanks to Gotius for the proposed solution to the problems with
Internet and font display

In the previous article, the problems and their solutions with the Internet and with the display of fonts in Linux mandrake were not disassembled, as promised, I analyze in this article.

Problems connecting to the Internet (ppp, adsl)

Problems can arise from the fact that, for example, the boot connection was disabled (in the case of adsl 'em), so I advise you not to experiment with this, but leave it as it is.
------------------ ppp
Troubleshoot problems with dialp (ppp) connection
To connect to the Internet, mandrek requires kde network-kppp-3.2-17 mdk and ppp-2.4-12 mdk packages (of course, the versions may differ). I already talked about how to create a connection, so let's move on to the problems, I've encountered several related problems With dialup connection:
1) when connecting to the Internet via kppp, the message is not found modem.
In order to eliminate this, go to configure - the device - and change / dev / modem to / dev / ttyS0. Or at :
Type (/ dev): port (com): ttyS0 1
TtyS1 2
TtyS2 3
TtyS3 4
Ps choose by modem type (external - com1, internal com3)
After that, the modem will be determined.
2) after the modem is found and tries to connect to the Internet, it shows: there is no signal on the line.
Check the telephone cable for service, or its connection to the modem.
------------------ adsl
After installing linux mandryka on the screw, and after setting up the connection, boot the system stops at eth0, when it loads, adsl issues a timeout, with the ifconfig command it produces only 2 devices: eth0 and lo, with the command adsl-connect it gives:
/ Usr / sbin / adsl-connect: Check '/etc//ppp/pppoe.conf' - no setting for ETH
"As it is clear from the error, the linusk can not determine the device, it registered in the parameter ETH = eth0, it did not help him, the name of the network trader did not cause any positive results either." How many I did not steal with configs, nothing came out with scripts (after all my knowledge in Linux is not so ) In the logs there was no necessary information, connection errors pleased with their variety, (then iptables was not in the right place, then the ip address was not the way it should be :) , I cut off all the lights, but it did not help either. :( The only idea came to mind only about removing packages necessary for the connection and installing them again (who has an idea for better writing). We will delete: dhcp-client, dhcp-common, rp-pppoe, + remove the connections eth0, adsl.
Creating a connection on the local network does not differ from the one described in the first part of the article, but the creation of the connection is different only in that we put the download of the connection to the boot (that is, when the system starts). After creating both connections (adsl, etho), restarting the network, rebuilt the computer.
Boot loading on time to differ nothing will be, again it stops on eth0 ,,, but about a miracle at connection check up the status OK :) !! Not looking at the allegedly not booted connection over the local network. And for a long boot load, I can be connected locally by cutting its timeout, after all the above mentioned methods, everything began to work.

Problems with fonts

1) After the changes listed in the article (in the one on which I gave the link in part 1) everything remains, as it is, but here the computer load turns into something extraordinary :) You can fix it like this:
"Since there is a lot of articles written about Russification, I will not be rubbing the same one"
LANG = "ru_RU.KOI8-R"
SUPPORTED = "en_US.UTF-8: en_US: en: ru_RU.KOI8-R: en_EN.koi8r: en_US: en"
SYSFONT = "latarcyrheb-sun16"
SYSFONTACM = "koi8-u"
Simply copy this listing and the file / etc / sysconfig / into the i18n file and the download will become a bit clearer than before :) Ie in English.
2) if the documents printed in Linux are not readable in Windows.
For the correct display of fonts in Windows, the documents written in Linux simply put the font Tahoma Western.

Installing the Bootloader

Continuing the series of articles / notes on Linux, I would like to talk about the place of residence of lin loader. In the first article, I wrote that the bootloader should be installed only in the MBR, otherwise there will be problems. But over time, I realized that if several operating systems are installed on the computer, after installing the bootloader in MBR, it turns out that if lin / win loader falls, then the load of another OS will become non-executable. This problem occurs because of the conflict with the Windows loader. To avoid this problem, I propose to install the loader not in the MBR, but in the root, more precisely in the boot sector of the primary partition of the file system. With this choice of the boot loader, it turns out that if the loader of any of the installed OS drops, then we will have the opportunity to boot into another OS.
Now let us consider directly the entire easy "algorithm" of such an operation. We see the point "Where do you want to install the bootloader"? There are 3 points:
/ The first sector of the MBR disk (where the boot loader is installed)
/ The first sector of the root partition (more precisely, we put it where Linux is installed)
/ On a floppy disk
/skip
Choose the first sector of the root partition. Further after installing the bootloader after a few more points, we see a summary (the summary is information about the installation, with the possibility of setting up the system). Some advise to put GRUB, but after installing it the system hangs on the inscription rough and the download does not proceed any further. So we leave everything on the deflot, more precisely lilo with the graphics and everything is loaded normally. After installing Linux, after rebooting we see the standard load of windows, I think it's understandable why it happens (the Linux loader is put into its own section, the winloader is in its own and since the MBR is loaded before the win is started)
After we booted into Windows we install Acronis OS selector (acronis.ru). We reboot, the acronis defines the axes, and displays the main window, here we can choose what to load. Now, if any of the OS falls, then we will be able to boot into another.


I think this article helped you understand the main points of installation and work with the linux operating system. The purpose of the article was to lay the basic knowledge of Linux for further study. Is my goal judged to you.

>> read part 1