Hello,
While I think there were certainly good points raised about issues with
it, that mv code to migrate /{dev,run}/shm and contents in postinst was
long removed, and nowadays is only left code to set up directories and
symlinks at bootup, when they're still empty. All this `mv /run/shm/*
Package: initscripts
Version: 2.88dsf-34
Severity: important
User: debian-...@lists.debian.org
Usertags: kfreebsd
X-Debbugs-Cc: debian-...@lists.debian.org
Hi,
The initscripts package is failing to upgrade from -32 to -34 in a
GNU/kFreeBSD jailed system:
Preparing to replace initscripts
Hi,
This may have been my fault. I can avoid this by actually mounting /run
as tmpfs (from the host, when constructing the jail). This allows a
successful and sane upgrade:
+ RUNSTATE=mdmd
+ RUNACTION=NONE
+ echo Due to mounts in the chroot, /dev/shm can't be safely symlinked
to /run/shm.
On Sun, Dec 30, 2012 at 06:31:36PM +, Steven Chamberlain wrote:
My jailed system's /dev is rather special (a sort of read-only devfs
mount); it doesn't contain a /dev/shm directory or link, and I'm not
even able to create one as root.
Does /dev/shm exist on a standard kFreeBSD install?
Control: severity -1 minor
On 30/12/12 19:07, Roger Leigh wrote:
Does /dev/shm exist on a standard kFreeBSD install?
It gets created by initscripts as symlink to /run/shm. Otherwise it
would not be there; apparently Linux 2.6 invented it and it didn't seem
too popular with upstream FreeBSD.
On Sun, Dec 30, 2012 at 08:29:51PM +, Steven Chamberlain wrote:
Control: severity -1 minor
On 30/12/12 19:07, Roger Leigh wrote:
Does /dev/shm exist on a standard kFreeBSD install?
It gets created by initscripts as symlink to /run/shm. Otherwise it
would not be there; apparently
6 matches
Mail list logo
