3. Repair core
3.1. Using repair
The small update of the core is released in a repair. For example, if your version is 1.1.45, and you noticed a "patch46.gz" can be used to upgrade it, this represents you can upgrade the version by using this fix to 1.1.46. You may want to back up Source Tree first ("make clean" and "CD / USR / SRC; TAR CVF Linux | Gzip -c> Old-tree.tar.gz" will create a TAR compressive file for you. The entire original program code and its archive architecture.).
Now, continue the above example, suppose you have obtained "patch46.gz" and put it under / usr / src. CD to / usr / src then execute "Zcat Patch46.GZ | Patch -p0 (if it is not a compressed repair file, then" Patch -P0 Usually, this process is so unable to see its movements carefully, so you will not be able to determine whether it is successfully performed. So you have to find some things that may not be so smooth. CD to / usr / src / linux and find files with .regs. Some version of the repair file (the old version, which may be compiled in the comparative early file system) to record these unsuccessful operations in the file. You can use "find" for you; "Find. -Name '* .reg' -print" will handle this work. If everything is correct, execute the second section "make clean," "" "", ",", ",", ",", "and" dep "as discussed in Section III. There are some options for the Patch command. Patch -s will suppress all other messages other than errors. If you put the core original code code outside / usr / src / linux, use Patch -p1 in this directory to cleanly perform the patch task. Other Patch options have a very detailed description in Manual Pages. 3.2. If there is a mistake Usually the problem that happens is that when Patch modifies a file called "config.in", this file does not look very much, because you have modified some options to cooperate with your machine. This problem has been careful, but some people may encounter this problem on the older version. To fix this problem, check what information in config.in.rej this file. There is a modified part to determine " " and "-" on the place where each row will begin. Check out a few rows of tags, then remember that they are "Y" or "n." Now edit the config.in file, then "Y" change "N" and "n" change in the appropriate place. "Y". Execute "patch -p0 If you still suffer other problems, then you might be you installed a damaged patch. If PATCH is displayed "Previously Applied Patch Detected: Assume -r?" You might use a fixed fixture (not recommended to do this than your favorite version number). To restore a repaired file, perform "patch -r" on the original patch. When the repair of the complement is really fails, the best way is to start from a clean, out-of-the-box source tree, one of the Linux-x.x.tar.gz files, and then re-execute. 3.3. Cut away .orig file As long as you have made several repairs, those .orig files will begin to accumulate. For example, one of my 1.1.51 version of Tree last cleaning is in version 1.1.48 (I think is it). Delete these .orig file will save a lot of disk space. "Find. -Name '* .orig' -EXEC RM -F {} ';'" will take care of you. Some versions of the repair file will use Tilde instead .orig. There are other (better?) Methods to cut off these .orig files. The most used is to replace "Xargs" "-exec:" "" "" "" "" "" "" "" "" - "(later this is more secure.). 3.4. Other repair files There will always be some other repair project issued by Linus (I will call "non-standard"). If you use them, Linus's repair file may not be executed correctly, then you don't have to restore their restraint, so you have to modify the original program code or repair the file. This job is usually very annoying for beginners, so if you have no research on the original program code, you will restore these non-standard fixes before using Linus's repair file. Then you can see if these non-standard repairs can still be implemented. If you can't do it, then you have to continue to use the old core to do it, or wait for someone else to publish the new core non-standard repair file with the new core that you can repair. How many common non-standard repair files? You may have heard them. I use Bill Paul's non-flashing patch to make the cursor on my virtual console because I hate the cursor that will flash. As far as I know, the latest version of this special repair file is to use the core of version 1.0, but I still use it in version 1.1.51 - I have modified it several times, because it usually Driver / char / console.c of chaos Linus repairs. 4. Additional kits Your Linux core has many features in the core of the original program code itself; these features are generally utilized by external software, and some of the most common: 4.1. KBD Linux's console has more features than you can. This includes switching fonts, reflecting your keyboard, switching display mode (new core) capabilities, and so on. KBD has a support process that allows users to do these movements, and a lot of fonts and some keyboard maps that are almost sufficient to apply any keyboard. 4.2. Hdparm Like a lot of software, this is a core repair file and its support procedures. These repairs are recognized as part of the core, while support procedures for optimization and adaming your hard drive are generally distributed. 5. Some traps 5.1. Clear If your new core will do something really strange (this happened to me), it may be because you forgot to make the make clean. Symptoms from your core abnormally collapsed to strange output, until poor execution efficiency, etc., can be anything. It is best to make sure you have confirmation (Make Dep). 5.2. Huge or slow core If your core takes up a lot of memory, or it is really a big big, or it is either using your brand new 486dx6 / 440 to compile, it is like it is always compiled, then it may be because You have configured too much unnecessary thing (device driver, file system, etc.). If you won't use something, don't configure it because it really takes up the memory. If your memory is less than 16 megs, make sure you answer "Y" on the issue of "Limit Memory To Low Ten". This causes a lot of different symptoms, especially if only in a 4 MB system) is the abnormal amount of information exchange between the memory and the disk. Check your core configuration if your disks make a lot of noise. You can find out the number of all memories on your machine, then reduce the number of memories obtained by the "Total Mem" or "Free" instruction inside / proc / meminfo to learn how many memories used. You can also perform "Dmesg" (or view the core record file, which must be in your system). It looks like this: Memory: 15124K / 16384K Available (552K Kernel Code, 384k Reserved, 324K Data) My 386 (profile is very rubbish) is shown below: Memory: 7000k / 8192k Available (496k Kernel Code, 384K Reserved, 312K Data) 5.3. Core is not compiled If it is not compiled, it may be a trimming failure, or if you have a problem from the original code you get from a place. It is also possible because your GCC version is incorrect or broken. Determine that the symbolic links described in the ReadMe are established correctly. Generally speaking, if the core has not been compiled, this means that there is a serious error in some places. 5.4. The core of the new version does not seem to start No LILO is executed, or there is no correct configuration. Once I have encountered the problem is in the configuration file, I use "root = / dev / hda" instead of "root = / dev / hda1" (this is really annoying at the beginning, but once You have a configuration file that can be used, you should don't need to change it again) 5.5. You forgot to perform Lilo, or the system can not start at all Oh! The best way now is to start with a magnetic sheet and prepare another magnetic sheet that can be activated (like "Make ZDisk"). You know the split area where your root directory (/) and its format (SECOND EXTENDED, Minix, etc.) In the following example, you have to know your / usr / src / linux source tree in that split area , Its format, and it usually hang there. In this example, the root directory / / dev / hda1, and the divided area holding / usr / src / linux is / dev / hda3, which is generally hanging under / usr. They are all Second Extended file systems. The core image that can be operated is called zimage, placed under / usr / src / linux. This idea is such that if there is a core image that can work, it is called Zimage under / usr / src / linux, it may be used on a new magnetic piece. Another way to do not necessarily better (this is related to how your system makes it) later discussed after this example. First, boot from the boot / root magnetic or rescue magnetic, then hooks with the operable core: MKDIR / MNT MOUNT -T EXT2 / DEV / HDA3 / MNT If the MKDIR instruction shows that the directory already exists, ignore it doesn't matter if it is. Now, CDs are placed in places where you can operate (Note: / MNT / USR / SRC / Linux - / USR = / MNT / SRC / INUX). Put a formatted magnetic disk into a: disk machine, (determined that you are not your boot / root magnetic!), Pour the image file into the magnetic sheet, then configure your root directory split area. CD / MNT / SRC / Linux DD IF = ZIMAGE OF = / DEV / FD0 RDEV / DEV / FD0 / DEV / HDA1 CD to the root directory / and remove the standard / usr division area: CD / UMOUNT / MNT You should now boot from this magnetic sheet. Don't forget to perform LILO (or if you have done something wrong after this start-up! As mentioned earlier, there is another very common way to do. If the situation is that you have a core that can be operated / (for example / vmlinuz), you can also use it. Assuming that all the conditions are the same as the above example, and my core image is / Vmlinuz, as long as you do these changes to the above example: Change / DEV / HDA3 to / dev / hda1 (/ split area), change / mnt / src / linux to / mnt, and change the if = zimage to IF = VMLinuz. As for the previous part of how to derive it how to derive / MNT / SRC / LINX can be ignored. 5.6. The system means "Warning: BDFlush Not Running" This can be considered a fairly serious problem. From the core of the 1.0 version (I can't remember the indeed version, but probably in April 1994, 20 days), there is a program that will periodically update the file system buffer called "Update" is upgraded. Or replace it. The original program code for "BDFLUSH" (you should be able to find it from the core you get), then compile it (you may want to perform compilation and installation under the core of the old version). It will install itself with "Update", and your new core should work well after this. 5.7. The system shows the strange message about Obsolete Routing Requests Get the new version of the Route program and recompile the old elements. /usr/src/linux/route.h (this is a file under usr / src / linux) has made modifications. 6. □ □ and skill 6.1. Heavy lead Make or the output of the PATCH instruction If you want to record these "make" or "patch" instructions, you can redidize the output of the screen to a file. First, you have to know that you use the shell: "grep root / etc / passwd" and look for things that look like "/ bin / csh". If you use SH or BASH, "(Command) 2> & 1 | Tee (Output file)." Will put a Make's output to "" Output File "file. If you are CSH or Bash, you should use the syntax of "(command) | & TEE (Output file). If it is RC (Note: You should not use RC), syntax is "(Command)> [2 = 1] | TEE (Output File)." 7. MISC 7.1. Author The Original Revision Was -0.1 On 3 October 1994 by Brian Ward (Ward@blah.tu-graz.ac.at). Please send me any Comments, Additions, Corrections, Or Computers. Corrections Are, In Particular, The Most Important To ME! Even though I try to be attentive as possible with mail, please remember that I get a lot of mail per day, so it may take a little time to get back to you. Especially when emailing me with a question, please try extra hard to BE CLEAR AND DETAILED IN YOUR MESSAGE. I'D Like To Than Dayone Who's Given Me Feedback. 7.2. History and other forms of this document I originally wrote this in ASCII, then I put some TeX around it, and then horrified the TeX so that I could convert the TeX into SGML with a perl script. Because of the original in TeX, the first version of this document that appeared on sunsite had two section numbers with each section (It would not have looked that bad if they were not different.). I also realize that it's kind of nonstandard to make revision numbers negative, but oh well. And if any of the above Sounds Kind of Stupid, I don't blame you. 7.3. To do The `` tricks and tips '' section is a little small. I hope to expand on it with suggestions from od. So is `` additional packages. '' More debugging / crash recovery info needed. 7.4. Contriburnions A Small Part of Linus' is Inclusive. (Thanks, Linus!) Uc@brian.lunetix.de (Ulrich Callmeier): patch -s and xargs. Quinlan@yggdrasil.com (Daniel Quinlan): Corrections and additions in many sections.nat@nataa.frmug.fr.net (NAT MakareVitch): MRPROPER The People Who Have Sent Me Mail with Questions and Problems Have Been Helpful, TOO! 7.5. Copyright NOTICE AND COPYING Copyright (c) Brian Ward, 1994, 1995. This document may be distributed in any medium as long as it and this notice remain unaltered Permission is granted for translation into any language, so long as the translator's name is added to the document There is no warranty on this document and its contents..; No One May Be Held Liable for Any Unfortunate Outcome OF ITS Content. Commercial redistribution is allowed and encouraged; however, it is strongly recommended that the redistributor contact the author before the redistribution, in the interest of keeping things up-to-date The same is true for translations.. -------------------------------------------------- ------------------------- Linux 2.0 Kernel Changes -------------------------------------------------- ------------------------- [Introduction] [Current Version] [Upgrade Tips] [How to learn the current program version] [Where to go Collecting these update files] [Other] [Postscript] -------------------------------------- ------------------------------------- Introduction ****** This document consists of some of Linux's latest version of important package. I hope to help the initial contact, upgrade to kernel 1.3.xx users can successfully use new Kernel. Hope (although I know you will want to fall!) Will not see someone in the future: "Why can't I use my make? "" How is PS AUX error each time? " "..... This document is theory should be translated by Linux Kernel Documentation / Changes, but the ability is limited. If you find a place you can't understand, it is recommended to turn over the original text .... :) -------------------------------------------------- -------------------- Current version ********** - KERNEL MODULES Stable Edition: 1.3.57, Test Edition: 1.3.69K - PPP DAEMON Stable Edition: 2.2.0F - Dynamic Linker (ld.so) 1.7.14 - GNU CC 2.7.2 - Binutils 2.6.0.14 - Linux C Library Stabilization: 5.2.18, Beta Test Edition: 5.3.12 - Linux C Library 2.7.1.4 - Termcap 2.0.8 - Procps 0.99A - GPM 1.09 - Sysvinit 2.62 - Util-Linux 2.5 ---------------- -------------------------------------------------- ------------ Upgrade Notice ********* NetWork error ================ The initial setting of many network Script will add a route to localhost (127.0.0.1) when started, but their method is wrong. To solve this problem, find "Route Add -Net 127.0.0.1" from your network setting file and change it to "Route Add -Net 127.0.0.0". This problem appears in the Red Hat and the system extends from it (ex: Caldera). If you are using these systems, modify your / etc / sysconfig / network-scripts / ifup-lo, change "Route Add-Net $ (iPadDR)" to "Route Add -Net 127.0.0.0" . Booting changes ====================================================================================================================================================================================================================== Kernel 1.3.xx's boot program has improved, now you can load larger kernel (BZImage), and can also start RAMDISK (Initrd) directly by Loader. See Documentation / Initrd.txt for some part of INITRD. If you want to compile larger kernel, use the following Make parameters: Bzimage, Bzlilo, Bzdisk (each equivalent to zimage, zlilo, and zdisk). If you want to use this new feature, you must upgrade your bootloader. LILO is upgraded to 0.19 (lilo.19.tar.gz), and Loadlin is upgraded to 1.6 (LODLIN16.TGZ). If you use rare syslinux or Etherboot, the latest version is 1.3 and 2.0, respectively. C library =========== The latest stable version of Linux is 5.2.18. If you upgrade from 5.0.9, please be sure to read Release.LIBC-5.2.18, because Make and some important tools may not be normal due to upgrade jobs. The version currently being in beta is 5.3.12. Some major changes in this version, some □ programs may encounter trouble (former version with free () does not have problems, but the new version of Library is troublesome), so please first Read Release.LIBC-5.3.9 carefully! The new version of Library is Dirent's bug - if there is define use_gnu, it will be wrong to define D-> Reclen as D-> Namlen, but some Gnu packages are wrong, such as GNU Make 3.xx. To correct this error, you must re-compile after Path. (Release.LIBC-5.3.9 There is Make Patch and where to make compiled binary) In addition, libc-5.3.x has a guaranteed vulnerability, while LIBC-5.3.12 has completed this hole. So if you want to use the Library of the beta, remember to use version 5.3.12. If you encounter the following error message: `fcntl_setlk () Called by Process 123 with Broken Flock () emulation ' You must also upgrade to version 5.2.1. 1.3.x version of KERNEL adds the FLOCK system call in the BSD. If you use the old version of library, this error message will be available. However, this message does not have, so you can ignore no matter whether it is. If you feel that this message is annoying, then upgrade your library. If you are annoying and lazy, then directly put the kernel fs / locks.c Printk (kern_warning "fcntl_setlk () Called by Process% D with Broken Flock () emulation / n", current-> pid); Go back and then re-compile. If you are using an AOUT format, you can upgrade to libc-4.7.6 to solve this problem. TERMCAP library ===================================================================================================================================================================================================================================== At present, Termcap version is 2.0.8. If you upgrade into this version, read Readme to get an important message about the Tegtent letter change. Procps utility ================ The kernel 1.3.x / proc structure has been changed, so you must upgrade the PROC to 0.99A, in the latest Kernel, the archive structure is changed again, but ProCPS has no official upgrade version of the reaction, so still use 0.99A. You can also find a Patch that streams to resolve 0.99A can be compatible with Kernel 1.3.94. KERNEL MODULES ================ The Kernel 1.3.x version has almost all modified, and Kerneld is also joined. To use a feature, you must update to the latest version of Modules. At present, the latest stable modules are 1.3.57 (Note), and the beta version is 1.3.69K. These can get in the same place you caught Kernel, or to its homepage: http://www.pi.se/blox/modules/index.html. Note: If you load modules, the following message will appear: gcc2_compiled, undefined failed to load module! The symbols fromkernel 1.3.foo don't match 1.3.foo That is to change to 1.3.69. This error occurs because you use the latest version of Binutil, so most people still stay at 1.3.57. In addition, you should pay attention to it, you can't compile A.out and ELF to modules, otherwise you will be able to load A.out / Elf Modules when you use Insmod to load a.out / elf modules (this is Hey?) If your system is mainly ELF and you will take A.out, you can compile A.out support to modules, otherwise you'd better put it directly into the kernel. If you haven't entered the ELF century (no ..), you can support the ELF directly when compiler kernel. In addition, the FS of the Partition coming up in Mount, Device Driver, remember to compiler to KERNEL, can not make it Modules. Please don't exaggerate to completely modulate, I forget to enter the EXT2FS and IDE DIRVER Compiler into Kernel ... * Note: You can see the version 2.0.0 modules in the kernel directory. PPP driver ============ Your PPPD must be 2.2.0 or update. The latest stable version is 2.2.0f can be ftp://sunsite.unc.edu/pub/linux/system/neetwork/serial/ppp/ppp-2.2.0f.tar.gz . Named pipes (sysvinit) ========================= Linux processes the Named Pipes to change (from the SunOS mode to "correct"), which makes some programs that fail, the most worthless of the sysvinit. If your sysvinit is 2.59 or earlier, although you can work properly, you will see such an error message: init: error reading initRequest or these words are not stopped ... If you use NCSA's httpd, you must set DAEMON's pre-spawn to 0, but I suggest you change directly to Apache's httpd. The new Named Pipes also makes Hylafax problems, if you have Hylafax Daemon, it will continue to use the CPU Time until the system has no IDLE TIME. To correct this error, modify Hylafax's port.h, put config_openfifo = "o_rdonly" Change to Config_openfifo = "o_rdwr" Similar processing methods (change the NAMED PIPE open mode from Read Only) can solve problems caused by this change. FILE LOCKING (Sendmail) ========================== From pre2.0.6 (1.99.6), the File Locking method cannot be mixed, for example: You cannot use flock and fcntl to lock the file at the same time. Please refer to Documentation / Lock.txt A more detailed information. This has an impact on the older version of Sendmail (Note). If you find Sendmail complaints that you can't lock aliases.dir (or other files), you must update sendmail to 8.7.x. The latest version of Sendmail can be ftp://ftp.cs.berkeley.edu/ucb/src/sendmail/sendmail.8.7.5.tar.gz . * Note: This problem will also occur in ELM 2.4 PL 25. Uugetty ========= The old version of uugettys will have problems in the new kernel, please update it. ftp://sunsite.unc.edu/pub/linux/system/serial/getty_ps-2.0.7h.tar.gz KBD ===== Users who use non-ASCII characters / fonts should be upgraded to: ftp.funet.fi:/pub/o/linux/people/linus/kbd-0.91.tar.gz * Note: I don't know much about this, but I have no upgrades. Console ========= Linux's console type (although I know what is something will not turn) change. If your version is too old, use the problem (like Joe can't be used ...), it is time to upgrade Termcap. To correct this problem, add Linux to / etc / termcap, or http://www.ccil.org/~esr/ncurses.html Go shopping. In addition, you also need to update Terminfo. Do the following action in root: LN -S / USR / LIB / TERMINFO / L / Linux / USR / LIB / TERMINFO / C / CONSOLE Of course, the best solution is to catch the latest TERMCAP back to install: ftp://sunsite.unc.edu/pub/linux/gcc/termcap-2.0.8.tar.gz Also, the console driver is now responsible for keeping track of correspondence between character codes and glyph bitmaps. If you encounter problems, try `loadunimap def 'to get back the default correspondence. (Less likely to turn probably say if your screen Originally, the text should be displayed into a bunch of garbled, can be solved with loadunimap def) hdparm ======== HDPARM has been updated in order to use the new features of the new KERNEL, the latest version is: ftp://sunsite.unc.edu/pub/linux/kernel/patches/diskdrives/hdparm-2.7.tar.gz Caouse it. (I have already seen 2.9 version) Ip accounting ============= All IP packets coming in or out via going one of the network interfaces are now passing the accounting chain. So, packets being forwarded are passing this chain twice. Since pre2.0.7 (aka 1.99.7), accounting rules can be defined so that The Will Only Match in One Direction (Either Incoming Or Outgoing). . There also exists a possibility to match on device names and / or device addresses, so that only packets coming in / going out via that device (network interface) match with a rule You'll need to get ipfwadm from ftp: // ftp .xos.nl / pub / linux / ipfwadm / ipfwadm-2.1.tar.gz to use this. IP firewalls ============ The IP firewall code has been changed drastically during 1.3.x. There are now 3 categories of firewall rules:. One for incoming packets, one for outgoing packets, and one for packets being forwarded There also exists a possibility to match on device names and / Or Device Addresses, SO That Only Packets Coming In / Going Out Via That Device (Network Interface) Match with a rule. this is especially useful to prevent spoofing. You'll NEED TO GET ftp://ftp.xos.nl/ Pub / Linux / IPFWADM / IPFWADM-2.1.TAR.GZ To Use this.ip masquerading ================ IP masquerading is now part of the standard kernel. However, you always need to load separate modules (ip_masq_ftp.o and / or ip_masq_irc.o) if you are going to use FTP or IRC in combination with masquerading. You'll need to get ftp://ftp.xos.nl/pub/linux/ipfwadm/ipfwadm-2.1.tar.gz to use this. (Unclear, don't know, don't use it, or don't go all ... but it seems to be related to ipfwadm-2.1.tar.gz ...) ISDN Support =============== The new version of the Kernel support ISDN, you must use ISDN you must: ftp://ftp.franken.de/pub/isdn4linux/IysDn4k-Utils-1.3.97.tar.gz Term is broky ================ TERM (a function similar to Slirp) will not be used after Kernel 1.3.60, and the author is selling in a vacation, so there is no solution. I suggest you learn to use Slirp. NetWorking ============= / Proc / Net has some columns to change in the new kernel, you must upgrade your Net-Tools. The latest stable version is Net-Tools-1.2.0.Tar.gz, and the latest Beta is Net-Tools-1.32-alpha.tar.gz. If you want to upgrade, maybe upgrade to the latest Beta comparison is better. XNTPD ======= The old version of XNTPD and the new version of the Kernel are not coming, please upgrade to xntp3.5f.tar.z Sound driver ============== 1.3.X version of the Sound Driver in Kernel will make VPLAY unused. To solve this problem, please catch the new version of SNDKIT: ftp://ftp.best.com/pub/front/tasd/snd-util-3.5.tar.gz Some users rendered that many sound tool programs (EX: CDD2WAV-SBPCD) must be reroute to use under the new version of Kernel. TCSH ====== If your TCSH is in the new kernel, please, please ftp: //anise.ee.cornell.edu/pub/tcsh Grasp the new version of TSCH SOURCE and modify config_f.h join a line: #define sysmalloc you can ftp://sunsite.unc.edu/pub/linux/system/shells/ Catch the new version of Binary, which should be corrected. Make ====== If the Make is strike after the update, please read your updated libc Release Note. This is not the fault of kernel, but many but mistakenly. When you update Libc to 5.3.9, you have to update make it will work properly. Upgrade LIBC may also make XTERM strike, if this is unfortunate, please re-compile xterm. Loop device ============= 1.3.x's kernel has a loop device that allows you to make a filemount into a file system, then you can do something interesting, like encrypted file system (Encrypted file systems) ... if you want to use this Features, you must update your mount: ftp://ftp.win.tue.nl/pub/linux/util/mount-2.5x.tar.gz The encrypted file system can grab: ftp.funet.fi:/pub/o/linux/beta/loop/des.1.tar.gz Multiple Device ================= The new kernel has support Multiple Device (let you bind a few partition into a logic device). To use this feature, please grab: ftp://sweet-smoke.ufr-info-p7.ibp.fr/pub/linux/md034.tar.gz ARP ===== ARP DAEMON also adds to new Kernel, please come: http://www.loran.com/~layes/arpd/index.html Get more information and arpd. Quota ======= The new Kernel also supports quota. Please grab: FTP: //ftp.funet.fi/pub/linux/people/linus/subsystems/quota/all.tar.gz Then cover the mntent.h inside /usr/include/mntent.h, so you can happy Compile out Quota. Process Accounting ==================== The functionality of Process Accounting is also included in the new version of Kernel. To use this feature, please grab: ftp://iguana.hut.fi/pub/linux/kernel/process_accounting/acct_1.3.73.tar.gz BDFlush ========= The BDFlush feature has been added to the new Kernel, you don't need to go to Patch, you can have this feature directly. AMP ===== The new Kernel supports the AMP (Advanced Power Management). AMP is mainly used in a laptop, allowing you to monitor the current battery usage, or save you battery power. Please grab this feature: ftp://tsx-11.mit.edu/pub/linux/packages/laptops/apm/apmd-2.4.tar.gz IBCS and DOSEMU ================== To support 1.3.x IBCS, please grab: FTP: //TSX-11.Mit.edu/pub/linux/beta/ibcs2/ibcs-1.3-960404-alpha.tar.gz As for Dosemu you can use in new kernel, please grab: ftp: //tsx-11.mit.edu/pub/linux/alpha/dosemu/development/dosemu-0.63.1.19.tgz Remember to update your /usr/include/sys/vm86.h as readme.newkernel, otherwise it will not be compile. Mtools and fdutils ==================== In the 1.3.x kernel, the control program of the flop is changed, but in order to compatibility, the KERNEL old program before 2.0 is still available, but the warning message is displayed, but the old program will be complete when it is 2.1.x. disappear. To avoid problems (or is exempt from that annoying, you must recompile all programs that will be used to flush control, like Mtool and FDUTIL. Please grab: ftp://sunsite.unc.edu/pub/linux/UTILS/disk-management/mtools-3.0.src.tar.gz ftp://sunsite.unc.edu/pub/linux/system/misc/fdutils-4.3.src.tar.gz In the future, FDFormat will completely disappear, so please learn the use of SuperFormat. -------------------------------------------------- -------------------- How to learn the current version of the program ********************** * GNU CC: GCC -V and GCC --Version PPP: PPPD -H (Wrong But It Show The Version) libc: ls -l /lib/libc.so.5 libc : ls -l /usr/lib/libg .so Binutils: ld -v ldd: ldd -v and ldd -v Termcap: ls -l /lib/libtermcap.so.s: ps --Version ------------------------------------------------------ -------------------------------------------------- -------- Where to catch these update files ************************ Please love CCCA FTP and Archie ..... -------------------------------------------------- -------------------- Others ***** These files mentioned above are found on the FTP Server of Taiwan, please search for Archie itself. Cherish the limited bandwidth, try to avoid going abroad ..... If your system is Red Hat, most updates have RPM available. First to the Red Hat's Mirror Site before installing. Note that you may have to use the -force parameter to complete these upgrades. If you find that there is a software that cannot work in Kernel 1.3.x, or those Kernel's features require additional kits to use, please mail to Chris Ricker (gt1355b@prism.gatech.edu). If you find any more mistakes in the translation, please mail give dinosaur.bbs@bbs.ee.nthu.edu.tw
