Bug 239914
Summary: | initscripts depends on /usr/bin/find | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rolf Fokkens <rolf> |
Component: | initscripts | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | rvokal, triage |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | bzcl34nup | ||
Fixed In Version: | 8.70-1 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-04-15 17:05:58 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Rolf Fokkens
2007-05-12 10:15:31 UTC
Right, that does eventually need fixed. However, if you're mounting the filesystem read-only, what's the point of splitting out /usr? For me the problem results from the fact that I have /lib/modules and /usr on squashfs, just make things fit on a CF card. So far this wasn't a problem for with FC4 and FC5, but for FC7 it is a problem. In general there may be a problem with (maybe outdated) filesystem standards. Are you using the readonly_root or temporary state? What for (I'm curious). I'm using readonly_root indead, to reduce writes on the CF card which is limited to 100.000 times or so. But to change the config (which resides in /etc) we can remount it rw and afterwards remount it ro again. Also I did some trickery with /etc/mtab whcih now resides in /var wich is ramfs. I'm googling now for "temporary state", I guess I may have missed an interresting feature somewhere :-) I think I understand it now, I found /etc/rwtab. It includes an /etc/mtab entry, which could be a problem: mount creates a /etc/mtab.tmp file and renames it to /etc/mtab. I had to patch util-linux to get around that. Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. |