On Tue, 2013-07-30 at 16:32 +, Clint Adams wrote:
> On Tue, Jul 30, 2013 at 09:00:15PM +1200, Andrew Ruthven wrote:
> > Totally agree. The problem is with tools that don't run in a chroot, if
> > they are in a chroot, break horribly. Mostly they're stuff run from
> > init.d...
>
> I think that
On Tue, Jul 30, 2013 at 09:00:15PM +1200, Andrew Ruthven wrote:
> Totally agree. The problem is with tools that don't run in a chroot, if
> they are in a chroot, break horribly. Mostly they're stuff run from
> init.d...
I think that's what /usr/sbin/policy-rc.d is for.
--
To UNSUBSCRIBE, email
On Sun, 2013-07-28 at 00:47 +, Clint Adams wrote:
> On Fri, Mar 15, 2013 at 09:16:45PM +1300, Andrew Ruthven wrote:
> > The big downside to that approach that I can see is that according to
> > the changelog ischroot was implemented to *stop* people having checks
> > spread all over the place.
On Fri, Mar 15, 2013 at 09:16:45PM +1300, Andrew Ruthven wrote:
> The big downside to that approach that I can see is that according to
> the changelog ischroot was implemented to *stop* people having checks
> spread all over the place. And as we've just discovered those checks
> break over time as
On Fri, 2013-03-15 at 03:33 +, Clint Adams wrote:
> > On newer vserver patches a better check is to look for a VxID line in
> > /proc/self/status. If the line is present you're running a vserver
> > kernel. If the value is 0, then you're on the physical host, anything
> > else means you're in
Package: debianutils
Version: 4.3.4
Severity: important
[resubmitting as something seems to have gone wrong with creating the bug]
Dear Maintainer,
The ischroot code checks to see if it can access /proc/1/root to determine
if it is a running inside a chroot. Within vservers you can now read
/pro
6 matches
Mail list logo
