AthlonRob <junkmail@axpr.net> says...

>M. K. <mkup@ozemail.com.au> wrote:
>
>> Cool. You can even do stuff like "mount -t tmpfs tmpfs /tmp"
>
>That wouldn't be such a great idea, though. Sometimes big stuff gets
>put in /tmp...
>
>Right now my server has 244MB of stuff in /tmp, my desktop about 4MB,
>and my laptop about 17MB. I definitely couldn't afford to lose 244MB of
>RAM like that, nor would I want to lose 17MB on my laptop.

I, on the other hand, have 3GB of RAM, and could easily devote a gig
or so to /tmp. I seem to remember some talk about Slackware not using
multiple gigabytes of RAM. but I didn't pay attention, seeing as my
usage patterns never bring me even close to the 1GB RAM usage mark.
Is this still an issue with 9.1?

I also have an 8GB swap partition; It has never been used, but when
you have two 160GB hard disks, who cares if you waste 2.5% if it?



--
Guy Macon, Electronics Engineer & Project Manager for hire.
Remember Doc Brown from the _Back to the Future_ movies? Do you
have an "impossible" engineering project that only someone like
Doc Brown can solve? My resume is at http://www.guymacon.com/

Guy Macon <http://www.guymacon.com/> wrote in message news:<f_qdnan-MKgYXASiRVn-jA@speakeasy.net>...
> Let's review, shall we?
>
> -----------------------------------------
>
> LINUX:
>
> mount -t tmpfs tmpfs /dev/shm
>
> -----------------------------------------
>
> WINDOWS 2000:
>
> Download Ramdisk.exe from
> http://download.microsoft.com/downlo...01/1/NT5/EN-US
> /Ramdisk.exe and hope that it doesn't have a security flaw or fatal bug
> - no source, so you don't know what's in it.
>
> Extract the contents to a "folder."
>
> Open up Control Panel
>
> Select Add New Hardware
>
> Select Other Device
>
> Select Have Disk
>
> Select the .inf file in the "folder" you extracted ramdisk.exe to.
>
> Back up your registry
>
> Use regedit to go to
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Ramdisk\Parameters
>
> Edit DiskSize key to the size you want.
>
> Edit DriveLetter key to the drive letter you want.
>
> Use regedit to go to
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\AFD
>
> Edit ImagePath key to match the drive letter you chose
>
> Use regedit to go to
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip
>
> Edit ImagePath key to match the drive letter you chose
>
> make a batch file named tcp.bat containing:
>
> copy c:\winnt\System32\DRIVERS\tcpip.sys Z:\
> copy c:\winnt\System32\DRIVERS\afd.sys Z:\
> net start afd
> net start tcpip
> net start dhcp
> ipconfig
> pause
>
> (Use the drive letter you chose before)
>
> Save as tcp.bat in your startup folder.
>
> (Windows will probably save it as tcp.bat.txt and hide the .txt
> from you. Fix this)
>
> Reboot with Zone Alarm or other firewall disabled. Note that
> Windows 2000 will take an extra three minutes or so to boot
> and that you may see erropr messages that (we hope) will go
> away later when you set up the snapin.
>
> VerIfy that the ramdisk works. Troubleshoot as needed.
>
> remove the ipconfig and pause lines from tcp.bat
>
> rename tcp.bat to tcp.cmd
>
> move tcp.cmd from your startup folder to your root folder.
>
> Run the Microsoft Manangement Console.
>
> Press CTRL+M
>
> Select Add/Remove Snap-In
>
> Select Add to add tcp.cmd as a snapin.
>
> Select Select Local Computer Policy
>
> Select Computer Configuration
>
> Select Windows Settings
>
> Select Scripts
>
> Select Startup/Shutdown
>
> Select Startup
>
> Select Startup Properties
>
> Select Add a Script
>
> Type in the path to tcp.cmd
>
> Click OK twice.
>
> Reboot, test, and troubleshoot any programs that tank when
> a drive letter is added or removed.
>
> -----------------------------------------
>
> Aren't you glad that Windows is easy to use, not like that
> hard-to-use Linux?
>
>
> (Disclaimer: I got the above procedure from
> http://dslnuts.com/ramdisk.shtml, but was not brave enough
> to try it on my fragile Windows 2000 installation. Don't
> blame me if you hose Windows.)


The script you are looking for is in, "Advanced Bash Scripting Guide"
available at tldp.org

it is: Example 29-3. Creating a ramdisk

Walt R.

Guy Macon <http://www.guymacon.com/> wrote:
> I, on the other hand, have 3GB of RAM, and could easily devote a gig
> or so to /tmp. I seem to remember some talk about Slackware not using
> multiple gigabytes of RAM. but I didn't pay attention, seeing as my
> usage patterns never bring me even close to the 1GB RAM usage mark.
> Is this still an issue with 9.1?

It is a kernel issue. Look at the HIGHMEM settings in the config file
for the kernel. If they are like this:
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_HIGHMEM is not set
you've got a maximum usable memory of about 900 MB.
While the next one allows for 4 GB (at the cost of some speed):
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_HIGHMEM=y
--
************************************************** ******************
** Eef Hartman, Delft University of Technology, dept. EWI/TWA **
** e-mail: E.J.M.Hartman@math.tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
************************************************** ******************