Hi All, First of all since my real job is administrator of a multi-server Novell network, I need my DOS. So, I backed up my 70 meg drive and used fdisk to create a bootable 20 meg partition and a 50 meg partition. After booting back up with dos I reformatted the partition and placed a system there then restore 20 meg worth of stuff. I am using Microsoft DOS 5.0, by the way and would not give it up for anything. Next, I downloaded from plains the demo_dsk.ibm file along with rawrite and used that to create a bootable minix1.5 disk. Yes, rawrite can be used to write any kind of file to a disk, just follow the prompts. Using minix I wrote 50 meg fs to /dev/hd2 and then quit. I then used my linux boot, made the same way as the minix boot, and booted up the compter to the insert root system disk. Inserted said disk and let it mount and I was up and running. Mounted /dev/hd2 to user and copied over the stuff from the floppy root disk. Back to DOS, and changed the bootimag file as per instructions so that it would acces the hard disk upon bootup. Made a new boot disk and tried it. Now when the boot disk finished reading it mounted the hd partition as the root, mucho faster. I then used the mread program to copy over all the *.tar files from the dos partition on the hard disk. No problem! Untarred all the files to whatever directories they wanted to go to. Question 1 - after untarring the gccbin file into the gccbin directory, where do I place the individual files so that gcc world.c will compile. Question 2 - can all the files in the utibin tar file be copied to the usr/bin file. Comment 1 - most times when booting linux after running dos I get the following error when booting the boot image disk. --begin error-- invalid TSS: 0000 EIP: 0008:00006718 EFLAGS: 00007206 ESP: 000f:00006719 fs: 0010 base: 00000000, limit: 000A0000 Pid: 0, process nr: 0 cf b8 17 00 00 00 66 8e d8 66 Kernel panic: Trying to free up swapper memory in swapper task - not syncing ---end error--- A second three finger salute will always work. Comment 2 - rarely but it does happen, I will get the following error after putting the root disk in drive a (when using the floppy root) --begin error-- floppy I/O error dev 0208, block 1 Kernel panic: Unable to mount root --end error-- Well that's all got to say and would some please send back the answers to my two questions. -- Patrick L. McGillan Computer Systems Specialist University Of Wisconsin Ph: (715) 394-8191 Superior, Wisconsin pmcgilla@uwsuper.edu
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| David Miller | Slow DOWN, please!!! |
| Peter Zijlstra | [PATCH 00/23] per device dirty throttling -v8 |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Natalie Protasevich | [BUG] New Kernel Bugs |
git: | |
