zuloobrooklyn.blogg.se

#Ram disk creator zip file
#Ram disk creator update
#Ram disk creator upgrade
#Ram disk creator password
#Ram disk creator Pc

#Ram disk creator update

Update /etc/fstab to mount /tmp and /var/tmp as tmpfs if your distribution does not use RAM disk for those directories.

#Ram disk creator zip file

Create a ZIP file of /var/warehouse/devtools-home - a home directory image.Īdd an entry in /etc/fstab for a RAM disk ( tmpfs) of required size, mounted on /ramdisk, and mount options as uid=developer,gid=developer,mode=700,default,noatime,nodev,nosuid,noexec. Clean-up anything which is not explicitly required as part of pristine image from /var/warehouse/devtools-home, to keep it as small as possible. This is a must because I also recommend mounting /tmp and /var/tmp on a RAM disk with the lowest possible size (see 5 below), and your auto-update programs may end up corrupting your system.Ĭopy /home/admin to a separate directory, say under /var/warehouse/devtools-home. Once tested, disable the auto-update feature as per instructions applicable for your distribution. bashrc so even temporary directories can be created on the large RAM disk by those programs which honour TMPDIR. Ensure that TMPDIR=/ramdisk/tmp is set in. bashrc and few other configuration files) till everything is working fine. If you are extremely paranoid, you would like to use chroot for developer and do not retain any set-uid programs within the chrooted directory.

#Ram disk creator password

root account password must be locked, so there is no temptation to use su while working under the developer account. developer account must not have sudo privileges. While creating the 2nd account, ensure that it does not create a home directory. Say default account admin and home directory is /home/admin, while 2nd account is say developer, and home directory is set as /ramdisk. Solution 1: In-line with the suggestion by Fabby under Possibility 2 (Low Complexity)Ĭreate two accounts: the first one is the default account created at the time of installation of the distribution (On Ubuntu, generally this account has sudo privileges).

#Ram disk creator upgrade

The Admin user must have a way to upgrade the system as and when needed.It must be installed and manageable by L1 Sys Admin. Solution should also be implementable on any Linux distribution without special hacks. Must work for all distribution supported GUI programs without any hacks (else I would have simply used Docker images).Regular user should not have sudo privileges.System shall always provide a clean image of a home directory - so even configurations changes are not preserved.No traces shall be left under any of those files without explicitly disabling sticky bit on those directories (or else some programs could break) Some programs may use /var/tmp and /tmp in addition to a home directory.Some developer tools may need large memory so you may have to really consider how much RAM you will actually need. (In my case, I also switch off swap for the same reason). Do not leave any traces of any files being processed by any of the applications.(Note: In your case, if you wish to preserve the content of a RAM disk, you will have to use the suggestions by Fabby and Zeiss, and you no longer need to mount /tmp and /var/tmp described below as RAM disk) In your case, GIMP will be replaced by a set of Developer Tools. I am working on two solutions for my team who needs to use GIMP on Ubuntu.

#Ram disk creator Pc

Note 1: I'm using a USB stick as an example, it could also be a partition / disk on your PC but a USB stick would make things easier as you can also duplicate a USB stick to another USB stick to have a backup of that environment.

The time you lose doing the above would outweigh the benefits you gain.

You need to rsync the data you want to be persistent.

It takes an enormous amount of RAM as you need your entire disk or entire home environment in RAM and enough RAM to run the applications you need.

(You want one option to be on in your IDE? Well.

you need to do all your upgrades / system settings on the persistent USB drive¹ and convert to ISO every time you want to change a single persistent byte.

So all that is technologically possible but impractical as: When shutting down, you either lose everything that is in the RAM disk or you have to do the reverse of #3.There! An environment completely in RAM! Possibility 2: /home in RAM: Convert the USB drive¹ to an ISO file using Gnome Disks.You would need an SSD-size amount of RAM: 64G would be small, 128G would be comfortable.You can have your environment completely in RAM, but: