I have attached two files that can be added to /etc/init.d and /etc/conf.d. I found this on the forum, works great, speed things up. Perzy
Created attachment 3618 [details] Configuration file
Created attachment 3619 [details] script to create ramdisk
With what package do you think it should be included ? util-linux ?
I have checked the descriptions of the ebuilds and the description of sys- apps\baselayout is "Base layout for Gentoo Linux filesystem (incl. initscripts and sysvinit)". Seems like the correct place. Perzy
No. It should go with the *main* utilities it use. Like /etc/hdparm goes with sys-apps/hdparm. Baselayout is the core system only.
Hi Martin, I'm not sure if you are waiting for an answer, but I will give one anyway. With this script you can define the behaviour of ramdisks, so there isn't a "main utility". All programs can use the ramdisk (e.g. portage, gcc, kde, etc.). I have checked the contents of util-linux and there isn't a single "init.d- script" in there. In baselayout I see "init.d-scripts" (e.g. net, net-lo, urandom, checkfs, etc.). IMHO a script to manage memory (ramdisks) systemwide is not more or less part of the coresystem then for example the network or filesystem. I'm not a developer so it's up to you. Do you have an idea where to put it? Perzy.
Hi, sorry about the long delay .. I should have gotten back to you earlier. Any change we can get some more documentation into either the script or the config file ? Also, I think it will be nicer if you only specify the mount points, and where the tarballs are, but the script detect what compression was used. You may want to look at the 'epatch()' function in /usr/portage/eclass/eutils.eclass ... Anyhow, if we can get these changes going, I dont mind adding it to baselayout.
And?
This bug has been inactive for more than 250 days. Any feedback?
a user can just as easily add entries to fstab to get same behavior imho, no point in over complicating things