From owner-freebsd-hackers Sat Apr 22 21:19:42 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA13091 for hackers-outgoing; Sat, 22 Apr 1995 21:19:42 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA13085 for ; Sat, 22 Apr 1995 21:19:41 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id VAA25646; Sat, 22 Apr 1995 21:18:42 -0700 From: Poul-Henning Kamp Message-Id: <199504230418.VAA25646@ref.tfs.com> Subject: Re: 2.x and large memory configs To: terry@cs.weber.edu (Terry Lambert) Date: Sat, 22 Apr 1995 21:18:42 -0700 (PDT) Cc: rashid@haven.ios.com, smace@metal-mail.neosoft.com, hackers@FreeBSD.org In-Reply-To: <9504230409.AA10351@cs.weber.edu> from "Terry Lambert" at Apr 22, 95 10:09:13 pm Content-Type: text Content-Length: 943 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > This issue is likely to surface again if FreeBSD decides to support > > > PCMCIA memory cards being ejected. 8-). > > > > I doubt we would even think about that. Considering that you get no warning > > before it's ejected, and that they oftern suffer a big accesstime penalty, > > it is not a good idea to use PCMCIA for main-memory. > > > > We could add it as a "vm-cache", for inactive pages or something, that way > > nothing would turn purple because those pages vanished... > > I was thinking of RAM disk myself, and sysctl'ing it back down before > you eject it manually. How about, hmm, say "umount /my/ramdisk" ? :-) > An interesting idea to consider, anyway. Much more interesting: 80MB flash card and "execute in place" of binaries... -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant'