UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi all, have been running a custom version of LinuxMint 16 mate in ram for the last couple of weeks now, and I must say that I'm very impressed with the speed and overall performance. I found a script called RAM_Booster, which takes your currently installed distro, compresses it into an squashfs filesystem, and then mounts it to ram, then boots from it.
When I run this command, it shows some impressive write speeds.
Code:
sync ; time sh -c "dd if=/dev/zero of=testfile bs=100k count=1k && sync" ; rm testfile
1024+0 records in
1024+0 records out
104857600 bytes (105 MB) copied, 0.0389547 s, 2.7 GB/s
have been running a custom version of LinuxMint 16 mate in ram for the last couple of weeks now, and I must say that I'm very impressed with the speed and overall performance. I found a script called RAM_Booster, which takes your currently installed distro, compresses it into an squashfs filesystem, and then mounts it to ram, then boots from it.
actually, this is what most Live systems have done for the last years. I've never thought about using that principle for a regular system; after all, there are some severe drawback, aren't there? Such as not being able to store configuration changes persistently or run system updates, because then you'd have to write that stuff into the squashfs at runtime.
If you really want to go for an "untouchable", unbreakable system, that may be an interesting concept, though.
Quote:
Originally Posted by fotoguy
When I run this command, it shows some impressive write speeds.
Code:
sync ; time sh -c "dd if=/dev/zero of=testfile bs=100k count=1k && sync" ; rm testfile
1024+0 records in
1024+0 records out
104857600 bytes (105 MB) copied, 0.0389547 s, 2.7 GB/s
real 0m0.243s
user 0m0.000s
sys 0m0.044s
I don't think this is really relevant. Sure, read and write operations with a RAM-resident system are blazingly fast (and I assume that /var and /temp are mounted to a tmpfs in RAM, too). But to actually use the system, you'd require a persistent partition, like /home being mounted to /dev/sda2 or the like. And that's where most write access will take place, apart from temp files or updating logs. Write access to the root filesystem should be negligible in normal operation.
Quote:
Originally Posted by fotoguy
Love to hear some coments, especially if you have been doing the same.
actually, this is what most Live systems have done for the last years. I've never thought about using that principle for a regular system; after all, there are some severe drawback, aren't there? Such as not being able to store configuration changes persistently or run system updates, because then you'd have to write that stuff into the squashfs at runtime.
Hi Doc CPU,
Yeah I know live systems have been doing this for some time now, made a few live distros myself. There are definetly some draw backs to this type of system like the log files being lost everytime you reboot or loose power, a UPS is on the card soon as I can afford one, but for my main desktop PC, that's fine, I certainly wouldn't recommend it for a server.
I am running /home on a seperate partition to hold or my configration files, should have mentioned that as well, programs like firefox still use the cache in the /home directory are still the same unless you move them to ram. I'm using a custom live version that I made so it already has all the software on it i'm going to use, so I don't need to update it all as far as software goes.
The developer of the script wrote an update script that remakes the squashfs filesystem for you, so any updates or new programs that I wont to keep, will then become part of the system permanetly, I also have another spare drive that I use for storage.
Quote:
Originally Posted by Doc CPU
If you really want to go for an "untouchable", unbreakable system, that may be an interesting concept, though.
It is fun to play around with, and I always have a nice clean system everytime I boot.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.