** Branch linked: lp:ubuntu/sysvinit
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1389891
Title:
error during upgrade: cannot create /dev/shm: file exists
Status in
** Changed in: sysvinit (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1389891
Title:
error during upgrade: cannot
This bug was fixed in the package sysvinit - 2.88dsf-53.2ubuntu2
---
sysvinit (2.88dsf-53.2ubuntu2) vivid; urgency=medium
* debian/sysvinit-utils.maintscript: Clean up obsolete
/etc/init/startpar-bridge.conf conffile on upgrades. (LP: #1390726)
* debian/initscripts.postinst:
This is my ubuntu+1 chroot, upgraded from release to release for the
past 7 years or so.
Yes, it appears that /run/shm has gone missing. That would explain
everything.
As a matter of curiosity, which ones of /run/shm or /dev/shm is the
current default standard? I'm wondering whether there might
which ones of /run/shm or /dev/shm is the current default standard?
That's a bit undefined. The upstream glibc standard is /dev/shm/; Debian
introduced /run/shm/ a while ago essentially because it looks nicer
(https://wiki.debian.org/ReleaseGoals/RunDirectory), which led to all
this confusion
CADT has spread to Debian and lead to FHS-deviant release goals. That
definitely explains the confusion.
Anyhow, since the target is is the Ubuntu chroot, I solved this by re-
creating /dev/shm, removing /run/shm and calling it a day.
I'll leave it to you decide whether enforcing something
Indeed /dev/shm/ shouldn't be a symlink at all; at least not if /run/shm
is a symlink or doesn't exist. I get a slightly different, but still
similar problem here as well with my schroots.
** Changed in: sysvinit (Ubuntu)
Status: Incomplete = In Progress
--
You received this bug
$ LC_ALL=C ls -al /dev/shm
lrwxrwxrwx 1 root root 8 Jul 22 2012 /dev/shm - /run/shm
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1389891
Title:
error during upgrade:
Actually, even adding --parents to mkdir in postinst doesn't fix it,
since we're dealing with a symbolic link. Suggestions?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
** Changed in: sysvinit (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1389891
Title:
error during upgrade:
The check does [ -d /dev/shm ], i. e. that means that you don't have a
/run/shm? Can you please tell me what kind of environment that is?
Perhaps a schroot or pbuilder or so with a totally empty /run that
doesn't start any init script?
I think I know how to fix that, but confirming the nature
Also, was this an upgrade from 14.10, or a fresh install?
** Changed in: sysvinit (Ubuntu)
Importance: Undecided = High
** Changed in: sysvinit (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
12 matches
Mail list logo
