On Sun, Mar 25, 2012 at 9:15 AM, Bruce Dubbs <[email protected]> wrote:
> Lemon Lime wrote:
>> On 03/24/12 17:36, Bruce Dubbs wrote:
>>> Nathan Coulson wrote:
>>>
>>>> What I should actually do on my own build, is break the /var/run
>>>> symlink, and have two folders. Then I can see what is actually going
>>>> where.
>>> That's your choice of course, but there are a couple of issues. We
>>> guarantee that /run is available for other boot scripts and that it is
>>> empty. If someone wanted to mount /var, then there is a possibility it
>>> might not be available when needed and that /var/run would need to be
>>> cleaned out startup. For most people neither of these is a big deal,
>>> but there is a possibility if stale info remaining in /var/run.
>>>
>>> -- Bruce
>>
>> I just noticed that in LFS, 6.6. Creating Essential Files and Symlinks,
>> there are commands that create /var/run/utmp (among other files). If
>> /var/run is a symbolic link to /run, and a tmpfs is mounted at /run, I
>> think this file will not be visible.
>
> It appears that the file is created automatically. At least it is on my
> system:
>
> $ ll /run/utmp
> -rw-rw-r-- 1 root utmp 4992 Mar 23 17:28 /run/utmp
>
> Perhaps we should just remove that portion in the last part of LFS 6.6.
>
> -- Bruce
> --
It is created in /etc/init.d/cleanfs on startup
> /var/run/utmp
if grep -q '^utmp:' /etc/group ; then
chmod 664 /var/run/utmp
chgrp utmp /var/run/utmp
fi
--
Nathan Coulson (conathan)
------
Location: British Columbia, Canada
Timezone: PST (-8)
Webpage: http://www.nathancoulson.com
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
