Chuck_M_Grandgent@cup.portal.com (04/16/88)
I've recently got MINIX 1.2 up and running on my AT clone, and even didn't have too many problems getting it on a hard disk partition. But I've run into the following sticky points which I would appreciate any help on: 1) Even after copying all the /usr/bin stuff to the hard disk and setting PATH so it can find it there, the compiler is still looking for stuff on /usr/bin, though other commands execute fine from /user/bin. Where's the PATH entries for the compiler ? 2) I keep running out of room on /dev/ram when unpacking large shell archives and linking large programs (am trying to get the UNIX version of ARC going). I would like, as much as possible to migrate away from the floppy setup, so most of it's disk-based. Any pointers ? 3) I have high-density floppy as "a:" and low density floppy as "b:" It seems that DOSREAD and DOSWRITE are assuming b: is also high density. If I do a "dosread -a 1 anyfile >anyfile", it works OK the first time, but the second time, my drive starts making LOUD noises and I have to abort the operation, getting unrecoverable I/O error. If I stick to the high-density drive, no problems. 4) Have EGA monitor. Periodically, scrolled lines don't appear. If I then enter maybe 15-20 carriage returns, the whole screen flashes and all the lines show up. Some buffer not getting flushed. Doesn't happen on monochrome (hercules). - Chuck Grandgent, chuck_m_grandgent@cup.portal.com ................
baumann@hope.UUCP (Michael Baumann) (04/21/88)
In article <4543@cup.portal.com> Chuck_M_Grandgent@cup.portal.com writes: ...stuff deleted.. >1) Even after copying all the /usr/bin stuff to the hard disk and >setting PATH so it can find it there, the compiler is still looking >for stuff on /usr/bin, though other commands execute fine from >/user/bin. Where's the PATH entries for the compiler ? The compiler has the path set in the source code, look at cc.c. I had to fix this, as I was running the AT version, and then switched to running on an XT, the AT has cpp and cem in /usr/lib, while the XT wants it in /lib. Look closely for the creation of the daughter processes, including cpp,cem,opt,cg,asld. Change to reflect what you really have. >2) I keep running out of room on /dev/ram when unpacking large shell >archives and linking large programs (am trying to get the UNIX >version of ARC going). I would like, as much as possible to migrate >away from the floppy setup, so most of it's disk-based. Any pointers ? For cc and asld use the -T option to specify where to put the temp files. As for the shell archives, I don't know. ----------------------------------------------------------------------------- "Life is full of little suprises." -- Pandora (as quoted by Robert Asprin) UUCP: {ucbvax!ucdavis,ucsd,ucivax}!ucrmath!hope!baumann or !ucrmath!jinx!baumann
jds@mimsy.UUCP (James DaSilva) (04/22/88)
In article <192@ucrmath.UUCP> baumann@hope.UUCP (Michael Baumann) writes: >In article <4543@cup.portal.com> Chuck_M_Grandgent@cup.portal.com writes: >>2) I keep running out of room on /dev/ram when unpacking large shell >>archives and linking large programs (am trying to get the UNIX >>version of ARC going). > >As for the shell archives, I don't know. The shell has the /tmp directory hard-coded into the source that deals with 'here' files. grep for it. A quick fix for you would be to change it to put the temp file in '.' since you have a hard disk. A better fix would be to add a -T option to sh, to match cc and asld. If you haven't already, you may need to increase the data space for sh to handle some shar files. I keep a special version of sh around, 'unsh', that has been chmem'ed to 32k. To Chuck: have you seen the post-1.2 (1.2a?) patch that allows the loading of the ram disk from a hard disk partition? Makes life easier. You can also change your /etc/rc to mount /usr on the hard disk, avioding the use of floppies (after the boot and root load), even without any kernel patches. - Jaime ---------------------------------------------------------------------- usenet: uunet!mimsy!jds James da Silva internet: jds@mimsy.umd.edu "Stand on each other's shoulders, not on each other's toes."
frank@morgan.com (Frank Wortner) (04/23/88)
James DaSilva <mimsy!jds> writes: >>The shell has the /tmp directory hard-coded into the source that deals with >>'here' files. grep for it. A quick fix for you would be to change it to >>put the temp file in '.' since you have a hard disk. A better fix would be >>to add a -T option to sh, to match cc and asld. My solution to the lack of /tmp space on the ram disk is to make a partition on the hard disk and mount it as /tmp. I think this is a better solution since "sh" is certainly not the only program that creates files in /tmp. Looking for all portential users of /tmp and adding a -T option to each one is not my idea of a good time. Of course, once I've done this, I'll have to remember to use "-T." Moving /tmp to a device with more space is (to my mind) a simpler and more general solution. The only non-obvious problem with my solution is that /etc/update opens /tmp. It does this to keep the inode in core, thereby reducing the amount of time to access this often-accessed directory. You can safely comment out the code that does this. Recompile and install the new update, and now mount /tmp in safety. :-) Regards, Frank ...!uunet!mstan!frank frank@morgan.com