July 22, 2004 11: 42: 51 ★ ☆ Nuclear upgrade test ☆ ★
SMBMount //10.42.96.28/ftp / pc -o username = PCCD / USR / SRCRM Linuxtar -zvxf /pc/linux-2.4.18.tar.gzcd / usr / srcls // Display presence Linux directory MV Linux Linux-2.4. 18LN -S Linux-2.4.18 Linux // Establish a Symbolic Linkmake MenuConfig - Tips Un installed NCURSES, find ncurses4-5.0-4.i386.2b in redhat7.2b, copy to / pcrpm -ivh ncurses4-5.0-4 .i386.rpm - Install OK, CD / USR / SRC / Linux, Make MenuConfig, still error - find ncurses-devel-5.2-12.i386.rpm, copy to / pc, installed OK, still report error - Find an article online to prompt the two packs of Version to be the same
- Download the two bags of the two bags rpm -uvh ncurses-5.2-26.i386.rpm - Upgrade installation Okrpm -UVH ncurses-wevel-5.2-26.i386.rpm - Upgrade installation OK
- Still not - in the prompt saying that GCC is not installed, find the following packages, install binutils-2.RPMCPP_2_96_98_i386.rpmkernel_Headers_2_4_7_10_i38.rpmglibc-design_10_i38.rpmglibc-devel-2.2.4-13.i386.rpmgcc- 2.96-98.i386.rpm
CD / USR / SRC / Linuxmake MenuConfig - Finally, configuration menu
Make Depmake Cleanmake BzimageMake Modulesmake Modules_Installcp -p Arch / I386 / Boot / Bzimage /Boot/Vmlinuz-2.4.18cp -p system.map /boot/system.map-2.4.18
Mkinitrd /boot/initrd-2.4.18.img 2.4.18 - This has repeatedly failed, prompts no buslogic module, re-make menuconfig multiple times, - Discover /Lib/Modules/2.4.18/kernel doesn't have anything , - then adopting: cp -r /lib/modules/2.4.7-10/kernel /lib/modules/2.4.18/- then mkinitrd /boot/initrd-2.4.18.img 2.4.18 - actually Generated INITRD-2.4.18.IMG
- Modify /etc/grub.conf # grub.conf generated by Anaconda # # Note That You do not have than Run Grub After Making Changes to this file # notice: you do not have a / boot partition. This means That # all KERNEL AND INITRD PATHS Are Relative to /, Eg. # root (HD0, 0) # kernel / boot / vmlinuz-version Ro root = / dev / hda1 # initrd /boot/initrd-version.img # boot = / dev / hda Default = 0 Timeout = 10 SplashImage = (HD0, 0) /BOOT/grub/splash.xpm.gz Title Red Hat Linux (2.4.7-10) root (HD0, 0) kernel /boot/vmlinuz-2.4.7- 10 ro root = / dev / hda1 initrd /boot/initrd-2.4.7-10.img Title Red Hat Linux (2.4.18) root (HD0, 0) kernel /boot/vmlinuz-2.4.18 Ro root = / dev / hda1 initrd /boot/initrd-2.4.18.img - The start to a certain location failed, the test in the 4 and 28 tests have multiple effects, and there is no specific-to -VMware in the network in the Internet. Article
- Nuclear settings are some places to pay attention to: - VMware's virtual network card is amdpcnet, - SCSI wants to choose busLogic, this is also VMware problem - configuring config files can be saved
July 27, 2004 9:58:18
- Finally, the upgrade is successful! ! ! ! ! ! ! ! ! ! ! !
- The problem is still on config. Today, Make OldConfig is used to find that its role is to keep the original configuration, and the new kernel - update provides the choice, so that it does not cause a machine due to module selection errors.
TAR XVFZ Linux-2.4.18.tar.gz MV Linux /usr/src/linux-2.4.18
Cd /usr/src/linux-2.4.18 make mrproperty cp -p /usr/src/linux-2.4/configs/kernel-*-i686.config .config - Configure the old configuration COPY to / usr / src / linux- 2.4.18 make OldConfig - Press this configuration make Dep Make Bzimage 2> Errors Make Modules 2> MOD-Errors CP -P ARCH / I386 / BOOT / BZIMAGE /BOOT/VMLINUZ-2.4.18 cp -p system.map / boot /System.map-2.4.18 make modules_install
New-kernel-pkg --install --Mkinitrd - DepMod 2.4.18 - Successfully generate /boot/initrd-2.4.18.img, then discovered that /boot/grub/grub.conf and - have been modified - Decomposition below to view /boot/initrd-2.4.8.imgmkdir / mnt / initrd gzip -dc /boot/initrd-2.4.8.img> /TMP/Initrd.img mount -o loop /tmp/initrd.img / mnt / initrd - Option -o loop Estimation is LS -R / MNT / Initrd used in its own file system - View Directory Structure Umount / MNT / Initrd
- Mainly referred to the article "Distributed Computer Clusters"
- In the following, we must find out the CONFIG today in Make MenuConfig.
July 28, 2004 10:39:52
- On the .4 virtual machine, put the .config file copying in. On .28, Make Oldconfig, very smooth upgrades.
July 29, 2004 16: 51: 23 ★ ☆ OpenMOSIX Test ☆ ★
- OpenMOSIX patch on the virtual machine in .4
- Install PATCH Command RPM -UVH PATCH-2.5.4-10.I386.rpm
CD / USR / SRC / Linux - Give kernel2.4.18 patch cat /pc/openmosix-2.4.18-4.gz | gzip -d | patch -p1 -l
Make Oldconfig - Now OpenMoSix Options Make Dep && Make Bzimage && Make MODULES
CP -P ARCH / I386 / BOOT / BZIMAGE /BOOT/VMLINUZ-2.4.18-M2 - MM2 is yourself, bringing problems in the back, cp-write system.map /boot/system.map-2.4.18 -Om2 Make Modules_Install
- a little problem, / lib / modules already exists Linux-2.4.18-openmosix directory - delete the om2rm /boot/vmlinuz-2.4.18-om2rm /boot/system.map-2.4.18-om2
Cp -P ARCH / I386 / BOOT / BZIMAGE /BOOT/VMLINUZ-2.4.18-OpenMosixcp -p system.map /boot/system.map-2.4.18-OpenMOSIX
NEW-KERNEL-PKG - ISTALL - MKinitrd - DepMod 2.4.18-OpenMOSIX
- Modify /boot/grub/grub.conf/etc/grub.conf Automatically change - KERNEL with OpenMoSix patch is already available
- Install OpenMosix tool below
RPM -UVH OpenMOSIX-TOOLS-0.2.4-1.i386.rpm
- After installation, some OpenMOSIX tool commands appear in /bin / down, generate a /etc/Mosix.map file - copy, change the address, modify the MOSIX.MAP file - use the mosmon command, appear interface, But find the node - add None / MFS MFS DFSA = 1 0 0 in / etc / fstab, later in http://howto.ipng.be/openmosix-howto/x424.html Tip in Redhat Must - Modify / etc / hosts files Match HostName and IP, after modifying the hostname and / etc / hosts file, / etc / init.d / openmosix start - Start normal /etc/init.d/openmosix status - - Show current status
- At this point, MOSMON has been displayed out of the node - then change the host name when adding a row of hostname omx --root to /root/.bash_profile
- On .4, three machines are prepared, (.11) OM1, (. 12) OM2, (. 13) OM1, after the respective configuration, start -OpenMOSIX, execute the following test: for X IN 1 2 3 4DO awk 'begin {for (i = 0; i <10000; i ) for (j = 0; j <10000; j );}' & done - started 4 AWK processes, use TOP observation There are two CPUs to use 99%, and there are two close to 50%; use MOSMON - observation, the load of the three nodes is relatively stable, the LOAD of the three nodes is higher; use .4 Taskmgr observation, three VMware-VMX Process - CPU usage is around 25%.
- About OpenMOSIX installation, you can also include the way to install the RPM package, such as installation --OpenMosix-kernel-2.4.18-OpenMoSix4.i386.rpm, there is already included in / lib / modules / in the / lib / modules / OpenMOSIX patch compiled kernel directory, corresponding VMLinuz, system.map, initrd.img is also automatically generated, the same - /etc/grub.conf is also changed, but I didn't try this kernel.
July 30, 2004 11:03:26
- Using mosrun -j1-4 / mfs / 1 / seti / setiathome -nolock on OM4 (.27) - but the process migration is not obvious, according to man Mosrun explanation, Flag -j indicates the machine after J Select one in the middle, transferring the process to the machine
- Use whiledo./setiathomeeep 120000done & - seems to display migration, but the CPU is used low
- Two machines have been established in .8, it is. 14 and .15, all of the machines, all machines are OM1 .11Om2.12m3 .13om4 .27 - Master, for foreign communication and submission of process OM5 .14 M6 .15
- Create a seti1-4 directory under / root, COPY four setiathome goes, then first ./setiathome - with the server interact, enter mail, download the data run, then Ctrl C end, then ./setiathome & - Put it in the background, after you get four directories, go to another console, MOSMON, discovery the process has been migrated to another machine, - and LOAD is around 1.0, at this time, the CPU usage is 100. %. - Understanding of the OpenMOSIX cluster: OpenMOSIX is implemented by the process of the process, not the migration of the calculation of a process.
When there are multiple processes in the system to use computing resources, OpenMOSIX automatically looks for idle NODE in the cluster, transferring the calculation of some processes to the Node, for users, all of which is transparent, he only need to submit Tasks without worrying about the computing power of the system.
But for a particular process, its data is not divided, and its calculation can only occur on a separate node, and OpenMOSIX does not calculate it on other Node. However, this may exist, such as a process calls many other processes for its services, then OpenMOSIX estimates will allocate resources for them.
