Bug#808364: Workaround

Hi, Started looking at this again due to Dirty Cow.. First the issue is still present in the latest kernel 3.16.36-1+deb8u2 I can confirm that the Ubuntu bug that Tomassino Ferrauto linked is correct. To test I disabled my NFS exports and rebooted. I tried to just unload the nfsd kernel mod

Bug#808364: lxc: lxc-start fails to mount proc (Operation not permitted)

On 2015-12-19 01:29, Ben Hutchings wrote: What mount options are used for /proc in the host system, and in the container? Hi, The container has in its config: lxc.mount.entry = proc proc proc ro,nodev,noexec,nosuid 0 0 I'm not sure why those particular options. I be

Bug#808364: lxc: lxc-start fails to mount proc (Operation not permitted)

Package: src:linux Version: 3.16.7-ckt20-1+deb8u1 Severity: important After some troubleshooting with the help of snapshot.debian.org I found that any kernel newer than 3.16.7-ckt11-1+deb8u6 is not able to start unprivileged lxc containers (as root). Downgrading to 3.16.7-ckt11-1+deb8u6 or older

Bug#708156: nfs-common: Please include /etc/request-key.d/id_resolver.conf

Package: nfs-common Version: 1:1.2.8-1 Severity: normal Hi, Thanks for packaging version 1.2.8 so promptly (re Bug#707258)! I have installed this version, but the request-key errors persist with newer kernels (at least anything newer than 3.7). May 13 11:19:10 hostname request-key: Cannot fin

Bug#707258: nfs-common: New upstream version available

Package: nfs-common Version: 1:1.2.6-3 Severity: wishlist Hi, Please update nfs-common to the latest upstream version. This is required for NFS4 to work on newer kernels. Otherwise syslog is spammed with endless messages like: May 8 12:00:09 host request-key: Cannot find command to construct

Bug#341273: Doesn't understand install and remove directives in modprobe.conf

On Thu, Dec 08, 2005 at 10:51:56PM +0100, Erik van Konijnenburg wrote: > On Thu, Dec 08, 2005 at 04:42:51PM -0500, Norbert Veber wrote: > > On Sat, Dec 03, 2005 at 07:46:34PM +0100, Erik van Konijnenburg wrote: > > > The reason is that install lines in the modprobe

Bug#341273: Doesn't understand install and remove directives in modprobe.conf

On Sat, Dec 03, 2005 at 07:46:34PM +0100, Erik van Konijnenburg wrote: > The reason is that install lines in the modprobe configuration are complete > shell scripts: they can invoke every executable, access every file. Oh I see. How does the old mkinitrd handle this? -- To UNSUBSCRIBE, email t

Bug#341273: Doesn't understand install and remove directives in modprobe.conf

Package: yaird Version: 0.0.11-12 Severity: important Setting up linux-image-2.6.14-2-k7 (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd /usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs. yaird error: modprobe psmou

Bug#320042: Workaround.. sort of

# dpkg -i --force-overwrite /var/cache/apt/archives/linux-doc-2.6.12_2.6.12-3_all.deb Thanks, Norbert signature.asc Description: Digital signature