From mint-bounce@lists.fishpool.fi Mon Aug 16 12:57:41 2010 Message-ID: <213496.707470284-sendEmail@descaro> From: "Helmut Karlowski" To: "mint@lists.fishpool.fi" Cc: "helmut.karlowski@ish.de" Subject: Re: [MiNT] ramdisk bug Date: Mon, 16 Aug 2010 16:56:32 +0000 X-Mailer: sendEmail-1.55 MIME-Version: 1.0 Content-Type: multipart/related; boundary="----MIME delimiter for sendEmail-425803.890292631" X-Antivirus: avast! (VPS 100816-0, 16.08.2010), Outbound message X-Antivirus-Status: Clean X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: helmut.karlowski@ish.de Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: This is a multi-part message in MIME format. To properly display this message you need a MIME-Version 1.0 compliant Email program. ------MIME delimiter for sendEmail-425803.890292631 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Alan Hourihane wrote: > On Mon, 2010-08-16 at 16:18 +0000, Helmut Karlowski wrote: > > Helmut Karlowski wrote: > > > > > All that's not working is 2in1 accessing /ram via symlink when there's no alias-drive for > > > /ram. That's what I tested. With the alias I did not test, but it worked > > > > BTW a symlink to /tmp works always, so ramfs must be different. > > So you are saying that if you symlink say /c/ram to /ram it doesn't > work ? > > And that /c/tmp to /tmp works ? No - what I said was more or less nonsense. I did ln -s u:/tmp tmp being in a FAT-dir. This works because the symlink gets resolved into something like u:/f/tmp (->/f/tmp?), unlike u:/ram (->/u/ram). The main reason is that /ram has no drive-letter as all other directories have. But converting /u/* into u:/* should fix it, unless someone manages to have /u, i.e. u:/u in MiNT. I tried with alias u: u:/ram but it doesn't boot. -Helmut ------MIME delimiter for sendEmail-425803.890292631--