On Sat, 9 Jan 1999 04:37:25 -0700 (MST), Bruce Sass <[EMAIL PROTECTED]> said: > Well, ya, a little... I was referring to the error caused by the > random sampling of FS and VM info. Synchronizing the data > collection with the installation will allow sampling at known peaks > in resource use, instead of hoping that I sampled enough during the > correct intervals.
>> Interesting idea -- dunno if we'll get to it for a bit. > Thanks -- Aw, just hack the equiv of `echo $IDstring >> > install.log;df >> install.log;cat /proc/meminfo >> install.log` into > the existing code, it doesn't need to be distributed. Nice stuff > like automatically analysing the data and updating the docs can wait > 'til ya get tired of doing it by hand. ;) Woah, we have an install.log? > Hmmm, I am basing my theory on the fact that if I follow the > directions and set all available RAM as `extended' (or is it > expanded, whatever), Linux thinks I have (4096 + 384)k... this > actually crashes the machine. Wow, that's strange. Maybe you bios is reversed in what it thinks it is doing? > When I leave the 384k block as > `expanded' memory, Linux sees 4096k and I get SEGVs, sometimes, > depending on what I am doing, or how long the machine has been up, > and (curiously, apparently) on how much free disk space there is. > Sometimes I can go for days without a problem, other times dselect > SEGVs as soon as it hands a job off to dpkg. Well, I suggest getting a RAM testing software and testing that you don't in fact have some bad ram. Sometimes particular application events will trigger the problem in a patterned (while still intermittent way). Look at memtest86 from the hwtools package. > Ya, I know, it is > really dpkg SEGVing, but dpkg alone rarely gives me any trouble. > Hmmm, does dselect test for RAM and add --smallmem to dpkg's command > line if available is below some set point (#72 on my todo list). Yes, AFAIK, it does. >> I've been supporting PC installations since DOS 3.1.2, and there's >> always difficulties. I suggest pulling out cards, and even taking >> the stock kernel-image and trying a few different recompiles, >> modifying the selected drivers. The qlogicisp probe seems to kick >> up a lot of problems. > <sigh> I would love to be able to compile a kernel, and pulling > cards is out - it is an old laptop. Unfortunately, anyone with a > computer I know well enough to ask if I can take over their machine > for a few days, so I can learn how to compile a kernel... well, lets > just say that the look that comes over their face is priceless. I > guess that's what happens when you are raised as a user in the M$ > and Mac WIMP world. Oh, well, as long as you set the nice value, no-one should really mind! I'd let you use mind but I'm on dynamic IP PPP, and not always up. -- .....Adam Di [EMAIL PROTECTED]<URL:http://www.onShore.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
