![]() |
HowTo.AddAdditionalSwapSpace HistoryHide minor edits - Show changes to markup June 30, 2006, at 09:49 PM
by -- Ungslung Script Added
Changed lines 2-3 from:
to:
To create a swap file in folder /mnt Changed lines 6-8 from:
to:
Changed lines 13-14 from:
to:
Changed lines 24-25 from:
to:
Changed lines 31-33 from:
More permanent swap should probably be in its own partition. Use coreutil's fdisk to set a partitions ID to Linux swap. Then use: to:
For Unslung firmware users the prefered method is to create an Unslung Script using a Unix style text editor such as vi and save this script to the /unslung folder with name rc.local, a similar method to that mentioned above. Changed lines 35-39 from:
to:
Then make the script executable. Changed lines 42-46 from:
where sdb5 is your target partition. you can dynamically add it with to:
More permanent swap should probably be in its own partition. Use coreutil's fdisk to set a partitions ID to Linux swap. Then use: Changed line 49 from:
to:
Changed lines 52-54 from:
will work with openslug. With Unslung this may not work as fstab is overwritten by reboot - need to test and use diversion script to keep the additional swap used permamently. to:
where sdb5 is your target partition. you can dynamically add it with Deleted line 53:
Note: Some people have had problems with mkswap and the error "swapon: swapon: Invalid argument" when trying to use swapon to add it. This can be fixed by using: Added line 55:
Deleted lines 56-57:
Changed lines 58-64 from:
To run mkswap and swapon first you need to install util-linux in OpenSlug and probably any other *Slug to:
will work with openslug. With Unslung this may not work as fstab is overwritten by reboot - need to test and use diversion script to keep the additional swap used permamently.
May 20, 2006, at 12:16 AM
by -- package install
Changed lines 51-54 from:
to:
April 07, 2006, at 08:34 AM
by --
Changed line 51 from:
to:
April 07, 2006, at 08:33 AM
by -- Expanded swap partition. Added note re: mkswap -c
Changed lines 32-51 from:
More permanent swap should probably be in its own partition. Use coreutil's fdisk to set a partitions ID to Linux swap. Then use to:
More permanent swap should probably be in its own partition. Use coreutil's fdisk to set a partitions ID to Linux swap. Then use:
March 10, 2006, at 07:05 PM
by -- Added changing script to be executable
Changed lines 25-26 from:
to:
You then need to make the script executable.
March 02, 2006, at 04:41 PM
by -- Spelling error
Changed line 29 from:
More permanent swap should probably be in its own partition. Use coreutil's fdisk to set a partitions ID to Linux swap. Then use to:
More permanent swap should probably be in its own partition. Use coreutil's fdisk to set a partitions ID to Linux swap. Then use March 01, 2006, at 04:03 PM
by --
Changed line 29 from:
More permanent swap should probably be in its own partition. Use coreutil's fdisk to set a partitions ID to Linux swap. Then use to:
More permanent swap should probably be in its own partition. Use coreutil's fdisk to set a partitions ID to Linux swap. Then use March 01, 2006, at 04:03 PM
by -- added hint about partition based swap
Changed lines 23-29 from:
to:
More permanent swap should probably be in its own partition. Use coreutil's fdisk to set a partitions ID to Linux swap. Then use January 07, 2006, at 03:49 AM
by --
Changed line 14 from:
After the second step your swap space should be increased by 256. You can check this by typing to:
After the second step your swap space should be increased by 256MB. You can check this by typing January 07, 2006, at 03:45 AM
by --
Changed line 23 from:
to:
January 07, 2006, at 03:38 AM
by --
Changed line 19 from:
Since you probably do not want to execute the swapon command every time the slug starts up you can create your own startup script. Create a new startup file in /opt/etc/init.d with the following content: to:
Since you probably do not want to execute the swapon command every time the slug starts up you can create your own startup script. Create a new startup file (e.g. S100addswap) in /opt/etc/init.d with the following content: Added line 21:
\\ January 07, 2006, at 03:37 AM
by --
Added line 16:
\\ January 07, 2006, at 03:36 AM
by --
Deleted line 5:
\\ January 07, 2006, at 03:36 AM
by --
Added line 6:
\\ January 07, 2006, at 03:35 AM
by --
Changed lines 8-9 from:
These commands would create a 256MB swap file- to:
The previous commands would create a 256MB big swap file. January 07, 2006, at 03:34 AM
by --
Changed lines 1-2 from:
In order to run programs that consume large amounts of memory (in my case rsync and >300000 files) I needed to add additional swap space on my Unslug system. I didn't like to idea to play around with the partitions on my hard drive so I just added space space in form of a swap file. to:
In order to run programs that consume large amounts of memory (in my case rsync and >300000 files) I needed to add additional swap space on my Unslug system. I didn't like to idea to play around with the partitions on my hard drive so I just added swap space in form of a swap file. January 07, 2006, at 03:33 AM
by -- Create a swap file in order to increase swap space
Added lines 1-21:
In order to run programs that consume large amounts of memory (in my case rsync and >300000 files) I needed to add additional swap space on my Unslug system. I didn't like to idea to play around with the partitions on my hard drive so I just added space space in form of a swap file.
These commands would create a 256MB swap file-
After the second step your swap space should be increased by 256. You can check this by typing
Since you probably do not want to execute the swapon command every time the slug starts up you can create your own startup script. Create a new startup file in /opt/etc/init.d with the following content:
view ·
edit ·
print ·
history ·
Last edited by RobHam.
Based on work by Krigan, hifi-andrew, fishywishywoo, Init, kaste, and Gregor Zurowski. Originally by Gregor Zurowski. Page last modified on June 30, 2006, at 09:49 PM
|