On 16/12/13 21:03, William Harrington wrote:
On Dec 16, 2013, at 2:47 PM, William Harrington wrote:
How do we deal with /dev/shm and /run/shm with our current
bootscripts. LFS for the longest time has linked /run/shm to /dev/shm.
I ask because I'm building for raspberry pi and CLFS with our
bootscripts using the PiLFS as a guide.
CLFS and LFS bootscripts have differences.
I ran across this discrepency when building wayland for it.
/run/shm is a link /to /dev/shm
createfiles with LFS bootscripts is to create /run/shm/wayland.
With out bootscripts, /run/shm doesn't even exist so /run/shm/wayland
can't exist.
I have to do this with our bootscript in /etc/rc.d/iinit.d/mountkernfs
after mkdir -p /dev/{pts,shm}:
ln -s /dev/shm /run/shm
mkdir /run/shm/wayland
I am aware of differences when using LFS and CLFS boot scripts and I
can fix this normally, but I'm writing up instructions for a CLFS
build with the Raspberry Pi using CLFS and wayland and well, our
bootscripts need some attention.
Sincerely,
William Harrington
_______________________________________________
Clfs-dev mailing list
Clfs-dev@lists.cross-lfs.org
http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org
They are both tmpfs file systems i.e ram with a file system overlayed on
them, I suspect it's down to individual distro taste whether they are
separate or not. Systemd goes with the latter , i.e a separate
filesystem to /run.
martin
_______________________________________________
Clfs-dev mailing list
Clfs-dev@lists.cross-lfs.org
http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org
