Summary: | /etc/udev/hwdb.bin doesn't belong in /etc | ||
---|---|---|---|
Product: | systemd | Reporter: | william.jon.mccann |
Component: | general | Assignee: | systemd-bugs |
Status: | RESOLVED NOTABUG | QA Contact: | systemd-bugs |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
william.jon.mccann
2013-06-30 19:16:03 UTC
Was just pointed to http://lists.freedesktop.org/archives/systemd-devel/2013-June/011354.html It needs to be available during early-boot, just like /etc/ld.so.cache, It cannot be in /var, because /var might be mounted only later. The database consists of data from /etc and /usr/lib, so it cannot be stored in /usr, because we need to be able to share /usr independent of /etc. We have no better place to store it. So, it is a database cache. Is the plan to store others like that in /etc too? This seems like a bad precedent and may not help us define new rules for what can go into /etc. Also, currently this file is "owned" by the systemd package on Fedora which just seems wrong, no? It is a database, yes. Not a cache. Early boot things like systemd/udev needs to live in /etc, we have no better place for it. This rule applies only to things like systemd/udev which bring up the system and can't rely on /var being available, nothing else should use /etc that way. It's systemd's database, so it should be owned by systemd. If you want to change it introduce a top-level /data directory or whatever it would be named, I personally don't thinkit's worth the trouble, will not fight for it, but would change systemd to use it if it would appear. /lib/syscache |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.