On Tuesday 10 August 2010 10:49, Michael MacIsaac wrote:
>> All the issues of the RO compoennt
>> are long since known and solved,
>
>Did that include moving the RPM database from /var/lib/rpm/ to somewhere
>under /etc/? I'm guessing the answer is "no way", but it just seems out
>of place in /var/lib/rpm/.
It really does belong under /var/lib, because it is something that is changed
by the system. If I remember the FHS correctly, /etc is for system config
stuff: namely things an admin makes changes to. /var/lib is for programs to
keep state information around in, and I think the RPM database fits that
description.
I've always thought that LVM maintaining state in /etc/lvm was wrong, but I
can understand why they put it there: /var might well not be around when LVM
actions need to be performed, but /etc almost has to be. If I had been
writing it, I probably would have put it in /dev/lvm instead, because /dev
really does have to be there already for LVM to work.
I'm still wondering what RPM issues with read-only filesystems have been
solved. Russ, are there any docs you can point us to on that? I ended up
doing essentially what you suggested: letting an admin maintain software on
one system using RPM, and having my tool distributing those changes to the
many Linux instances it has created, dealing with R/O filesystems in its own
way.
- MacK.
-----
Edmund R. MacKenty
Software Architect
Rocket Software
275 Grove Street · Newton, MA 02466-2272 · USA
Tel: +1.617.614.4321
Email: [email protected]
Web: www.rocketsoftware.com
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
