Talk:Resolvconf

This article is rated Stub-class on Wikipedia's content assessment scale.
It is of interest to the following WikiProjects:

Computing

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
???	This article has not yet received a rating on the project's importance scale.
	This article has been automatically rated by a bot or other tool as Stub-class because it uses a stub template. Please ensure the assessment is correct before removing the `\|auto=` parameter.

Untitled

Latest comment: 16 years ago1 comment1 person in discussion

It seems troublesome from a design perspective to assume that /etc is housed in a read-write filesystem. According to the Linux File System Hierarchy Standard (FHS), programs should be designed such that they can run uninhibited with a read-only root filesystem on a thoughtfully-partitioned machine. This is in direct response to /etc/resolvconf/run/resolv.conf. Why not house it under /var/run/resolveconf/resolve.conf? I'll admit that FHS is far from perfect, but it has a lot of good ideas behind it. This does point to a shortcoming involving having a writable place for transient data at boot time. Perhaps a location like /tmp/run could be proposed. How does /etc/mtab handle this condition? Mattp3d (talk) 19:50, 25 January 2010 (UTC)Reply

This page was redesigned at the edge.

A page that knows where it met you.

Talk:Resolvconf

Untitled