Am Donnerstag, 4. November 2010, 10:47:34 schrieb Andreas Jaeger:
On Wednesday 03 November 2010 23:03:41 Brandon Philips wrote:
On 18:58 Wed 03 Nov 2010, Kay Sievers wrote:
On Wed, 2010-11-03 at 14:35 +0100, Ludwig Nussel wrote:
Andreas Jaeger wrote:
Testing today's version, I noticed that the following directories were not created:
d /var/run/screens 0755 root root - d /var/run/uscreens 1777 root root - d /var/run/vi.recover 1777 root root - d /var/run/PolicyKit 0770 polkituser polkituser -
Kay, does systemd-tmpfiles-setup.service replace boot.cleanup? If yes, I'm curious where this is configured... Otherwise, I wonder why it did not get executed...
I guess the right solution would be to create /etc/tmpfiles.d/{screen,vi,PolicyKit} for these?
What about getting rid of the ugly /etc/tmpdirs.d/ then? boot.cleanup could read /etc/tmpfiles.d just as well.
Sounds good, yeah. The Debian guys want to do the same.
Here is a quick implementation of a shell script to do the /etc/tmpfiles.d/ work that we can merge into aaa_base. It implements the verbs that we care about right now: create and remove.
I can send a patch to fix aaa_base to call this script and remove the screen specific stuff too as the Factory version of screen now ships a /etc/tmpfiles.d file.
And also the vim bits. Sounds like a good way to move forward.
Eventually it would be great to move all of the magic for tmp files in aaa_base and have packages ship /etc/tmpfiles.d. This is a place to start.
Right now some files are part of systemd: /etc/tmpfiles.d/systemd.conf /etc/tmpfiles.d/x11.conf
I just fixed PolicyKit and vim to have conf files as well, so the packages part is done but we should double check this later.
So, IMO, we should move the two files from systemd to another package that gets installed on its own and can be used without going to systemd - or we require systemd installation just because of these files,...
moving the files to the packages where they belong sounds like a good idea, I'd think we want to prevent another package getting the "trashcan-syndrome" that aaa_base sometimes has. Can I find the info on the format of these files somewhere (since I possibly have to implement reading the files in boot.cleanup as well) ... ? -- with kind regards (mit freundlichem Grinsen), Ruediger Oertel (ro@novell.com,ro@suse.de,bugfinder@t-online.de) ---------------------------------------------------------------------- Linux fatou 2.6.36-3-default #1 SMP 2010-10-26 21:31:22 +0200 x86_64 Key fingerprint = 17DC 6553 86A7 384B 53C5 CA5C 3CE4 F2E7 23F2 B417 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org