From fnaumann@mail.cs.uni-magdeburg.de Mon Jun 28 20:52:31 2004 Date: Mon, 28 Jun 2004 20:40:35 +0200 From: joska@nvg.org (Jo Even Skarstein) Subject: Re: [MiNT] nfs To: mint@fishpool.com ([MiNT] Mailing-List) In-Reply-To: Message-ID: Mime-Version: 1.0 Content-type: text/plain; charset="iso-8859-1" X-Mailer: aMail 1.27b/MiNT X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at fishpool.fi Delivered-To: mint@fishpool.com Delivered-To: mint@lists.fishpool.fi X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: joska@nvg.org Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: X-Milter: ClamAV 0.70/0.70kjel X-Milter: milter-regex 1.5jel X-Milter: ClamAV 0.70/0.70kjel X-Milter: milter-regex 1.5jel Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by prinz.cs.uni-magdeburg.de id i5SIqOga006867 On Mon, 28 Jun 2004 20:22:27 +0200, Jo Even Skarstein wrote: > My "solution" for the past couple of years has been to not run neither > init.prg nor /etc/rc from mint.cnf, but to start the AES from mint.cnf and > then run /etc/rc from the desktop. This will work if memory protection is > disabled, and the system is apparently stable. With memory protection enabled > I get the following error messages: > > pid 29 (syslogd): MEMORY VIOLATION: type=private RW=w AA=300FA2 PC=11F8884 BP=1A70000 > pid 46 (portmap): MEMORY VIOLATION: type=private RW=r AA=310FA0 PC=1AD75B0 BP=1AD0000 > pid 48 (inetd): MEMORY VIOLATION: type=private RW=r AA=310FA0 PC=1AD8764 BP=1AD0000 > > Everything else seems to work fine though, and stability is fine. But I need I was a bit quick there, I was running with mp enabled while writing the above and a couple of minutes after sending it, my Milan just froze while I was using bash... /* ** Jo Even Skarstein http://home.nvg.org/~joska/ */