The below is i see in Fedora 15:<br><br>[root@yangyi-dev2 /]# cat /etc/*-release<br>Fedora release 15 (Lovelock)<br>Fedora release 15 (Lovelock)<br>Fedora release 15 (Lovelock)<br>[root@yangyi-dev2 /]# rpm -qf /var/run/<br>
abrt/ cups/ gdm/ lock/ netreport/ openvpn/ ppp/ sepermit/ setroubleshoot/ vpnc/<br>console/ faillock/ libgpod/ lvm/ NetworkManager/ plymouth/ pptp/ setrans/ utmp wpa_supplicant/<br>
[root@yangyi-dev2 /]# rpm -qf /var/run/abrt<br>abrt-2.0.2-5.fc15.x86_64<br>[root@yangyi-dev2 /]# rpm -qf /var/lo<br>local/ lock/ log/<br>[root@yangyi-dev2 /]# rpm -qf /var/lo<br>local/ lock/ log/<br>[root@yangyi-dev2 /]# rpm -qf /var/lock/l<br>
lockdev/ lvm/<br>[root@yangyi-dev2 /]# rpm -qf /var/lock/lvm<br>lvm2-2.02.84-1.fc15.x86_64<br>[root@yangyi-dev2 /]#<br><br>/run is a disk directory, /var/lock -> /run/lock, /var/run -> /run, <a href="http://lwn.net/Articles/436012/">http://lwn.net/Articles/436012/</a> told about /run.<br>
<br><div class="gmail_quote">On Thu, Jul 21, 2011 at 6:14 PM, Kay Sievers <span dir="ltr"><<a href="mailto:kay.sievers@vrfy.org">kay.sievers@vrfy.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On Thu, Jul 21, 2011 at 09:55, <<a href="mailto:yang.y.yi@gmail.com">yang.y.yi@gmail.com</a>> wrote:<br>
> i found some packages installed some files in /var/run and /var/lock, but<br>
> /var/run is symbol linked to /run and /var/lock is symbol linked to<br>
> /run/lock, /run is a tmpfs, it can't save some files permanently, Fedora's<br>
> way is /run is a disk directory, it saves the installed files by some<br>
> packages, in initramfs, init will take responsibility for mounting /run as<br>
> tmpfs and copy /run in disk to this tmpfs, but for MeeGo, we don't have<br>
> initrd/initramfs, so this only can be done by systemd in boot phase, anybody<br>
> knows a good way to do this?<br>
<br>
</div></div>Packages which install files in /run (/var/run) need to be fixed.<br>
Fedora has no packages relying on it. It has nothing to do with<br>
initramfs, /run (/var/run) will always be empty at bootup.<br>
<br>
Packages who rely on pre-existing content in /run (/var/run) need to<br>
ship tmpfiles (man systemd-tmpfiles) instructions to populate /run<br>
(/var/run) at bootup before the services are started.<br>
<br>
Real services which startup as root, ideally create the needed content<br>
themselves, and not use tmpfiles.<br>
<font color="#888888"><br>
Kay<br>
</font></blockquote></div><br>