[lfs-book] [LFS Trac] #2988: /var/lock should be relative

LFS Trac trac at linuxfromscratch.org
Wed Dec 28 13:06:02 PST 2011


#2988: /var/lock should be relative
--------------------+-------------------------------------------------------
 Reporter:  stu     |        Owner:  lfs-book@…                   
     Type:  task    |       Status:  closed                       
 Priority:  normal  |    Milestone:  7.1                          
Component:  Book    |      Version:  SVN                          
 Severity:  normal  |   Resolution:  wontfix                      
 Keywords:          |  
--------------------+-------------------------------------------------------

Comment(by stu):

 Absolute symlinks are categorically bad. This issue isn't about coloring
 outside the lines, this is about teaching LFS readers correct principles.

 You are correct that {LFS}/run/lock does not exist during the LFS creation
 process, but {HOST}/run/lock might. When chroot-ed or booted into the LFS
 system the link does indeed point to the correct place. When inspecting
 the LFS tree from the host system, the link literally points to the host
 system (because it's absolute). If the link created in the commands in
 section 6.5 were relative, it would be correct in all contexts.

-- 
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/2988#comment:2>
LFS Trac <http://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.



More information about the lfs-book mailing list